Jäljitettävyys ja pilvipalvelut ISOBUS-standardiin valmistajariippumattomasti, Juha Backman, Luke. Teknologiapäivä – Arvo ja liiketoiminta digitaalisessa maataloudessa -webinaari, 13.1.2021.

1. © Luonnonvarakeskus© Luonnonvarakeskus
Juha Backman / LUKE
WP 2: Jäljitettävyys ja
pilvipalvelut ISOBUS-standardiin
valmistajariippumattomasti

2. © Luonnonvarakeskus© Luonnonvarakeskus
WP 2
T 2.1 EFDI
Extended FMIS Data Interface

3. © Luonnonvarakeskus
Ajateltu demonstraatio
13.1.2021
FMIS
3G/4G
WLAN
USB
Juha Backman

4. © Luonnonvarakeskus
Demonstraatio käytännössä
13.1.2021
WLAN
USB
LAN
EFDI Client: TC
EFDI Client: TC
EFDI Client: FMIS
EFDI Server
Juha Backman

5. © Luonnonvarakeskus
CrossControl ISOBUS terminaali
• CrossControl ISOBUS terminaali CCpilot VA
• EFDI
– Taustaohjelma ISOBUS terminaaliin: ”USB-tikun korvaaja”
– Palvelinohjelma tietokoneelle tiedon lähetys/vastaanottoon
• Käytetyt kirjastot
– MQTT-kirjasto: mosquitto-1.4.15
– Protobuf: protobuf-3.5.1
– HTTP-yhteys, XML-parsinta: QT5
13.1.2021Juha Backman

6. © Luonnonvarakeskus
Raspberry Pi Zero W
• Speksit
– 1GHz, single-core CPU
– 512MB RAM
– Mini HDMI and USB On-The-Go ports
– Micro USB power
– 802.11 b/g/n wireless LAN
– Bluetooth 4.1
• Sulautettu Linux
– Voi konfiguroida erilaisiksi USB Gadgeteiksi
→ Näkyy terminaalille USB-tikkuna
→ Siirtää tallennetun XML-tiedoston EFDI
protokollalla
13.1.2021Juha Backman

7. © Luonnonvarakeskus
EFDI Client: FMIS
• EFDI Client prototyyppi toteutettu
– Kirjautuu HTTP-yhteydellä EFDI onboard serverille
– Avaa MQTT yhteyden ja kommunikoinnin EFDI serverille
– Kysyy kaikkia serverille kirjautuneita EFDI Clienttejä 10
sekunnin välein
– Luo jokaiselle Clientille paikalliset kansiot
• /endpoints/<Client ID>/Inbox
• /endpoints/<Client ID>/Outbox
– Tarkkailee Outbox-kansiota: kun TASKDATA.XML
tallennettu kansioon muuttaa XML:n protobuf-muotoon ja
lähettää serverin kautta kyseselle clientille
– Uuden taskin tullessa serveriltä tallentaa sen kyseisen
clientin Inbox-kansioon
13.1.2021Juha Backman

8. © Luonnonvarakeskus
FMIS connects to EFDI Server
13.1.2021Juha Backman

9. © Luonnonvarakeskus
Connect to HTTP-server
Send onboarding request to http://192.168.1.40:3123/onboard
Reply from server
authentication {
certificate: "-----BEGIN RSA PRIVATE KEY----- [ .... ]"
secret: "376f0940c2494a38bdd0208426f4a077”
}
connection_criteria {
client_id: "bdca6a0f-8011-462a-8f74-2f0beac1205e"
commands: "commands/bdca6a0f-8011-462a-8f74-2f0beac1205e"
measures: "measures/bdca6a0f-8011-462a-8f74-2f0beac1205e"
host: "tcp://192.168.1.40"
port: "1883”
}
device_id: "bdca6a0f-8011-462a-8f74-2f0beac1205e”
capability_id: "2b287272-110e-4e0d-907f-63865caed69b”
sensor_id: "2546a359-a704-4ce3-8747-952ecf13255c"
13.1.2021
onboarding-process.flow
/**
* How to onboard to a network.
*
* @flow {id} iso11783.p15.v0.m0.onboarding-process
* @flow {name} "Onboarding process"
* @flow {sequence} iso11783.p15.v0.m0.onboarding-endpoint
*/
onboarding-endpoint.scenario
/**
* Desciption of how to onboard an endpoint.
*
* @scenario {id} iso11783.p15.v0.m0.onboarding-endpoint
* @scenario {name} "Onboarding Endpoint"
* @scenario {request.verb} PROCESS
* @scenario {request.noun}
iso11783.p15.v0.m0.messages.Onboarding
* @scenario {response.verb} ACKNOWLEDGE
* @scenario {response.noun}
iso11783.p15.v0.m0.messages.OnboardingResponse
*/
Juha Backman

10. © Luonnonvarakeskus
Connect to MQTT and EFDI server
Connecting to MQTT broker HOST:192.168.1.40 PORT:1883
Connected to MQTT broker
Subscribe TOPIC commands/bdca6a0f-8011-462a-8f74-2f0beac1205e
Send status to EFDI server
application_message_id: "{6bbeb8cf-be0e-48c1-9d94-a800347b05df}”
application_message_seq_no: 1
sensor_id: "2546a359-a704-4ce3-8747-952ecf13255c”
capability_id: "2b287272-110e-4e0d-907f-63865caed69b”
mode: PUBLISH
timestamp { seconds: 1574244348 }
reference: "{d9b6efb6-92b7-4028-a986-a0db53717aed}”
verb: NOTIFY
noun {
[type.googleapis.com/iso11783.p15.v0.m0.messages.ClientStatus] {
event: ONLINE
}
}
13.1.2021
client-information-exchange.flow
/**
* To exchange information about the current client status.
* The client status is sent with mode PUBLISH when
* - Connection to the server was established successfully (status ONLINE)
* - The client wants to disconnecte (status EXPECTED_OFFLINE)
* - The client has los its connection to the server (status UNEXPECTED_OFFLINE)
*
* @flow {id} iso11783.p15.v0.m0.client-information-exchange
* @flow {name} "Client Information Exchange"
* @flow {sequence} iso11783.p15.v0.m0.client-information
* @flow {sequence} [iso11783.p10.v1.m0.reference-request]
*/
client-information.scenario
/**
* The client must send this message when it is successfully connected to the server.
* The reception of a client status message must be confirmed by the server.
* The message does not need to be confirmed by the server when the client is
unintentionally offline (in case of UNEXPECTED_OFFLINE).
*
* @scenario {id} iso11783.p15.v0.m0.client-status
* @scenario {name} "Client Status"
* @scenario {request.verb} NOTIFY
* @scenario {request.noun} iso11783.p15.v0.m0.messages.ClientStatus
* @scenario {response.verb} CONFIRM
* @scenario {response.noun}
*/ Juha Backman

11. © Luonnonvarakeskus
MQTT communication with protobuf: ”Send”
13.1.2021
request.proto
syntax = "proto3";
package iso11783.p15.v0.m0.messages;
import "google/protobuf/any.proto";
import "google/protobuf/timestamp.proto";
import "iso11783/p15/v0/m0/messages/chunk-component.proto";
import "iso11783/p15/v0/m0/messages/mode.proto";
import "iso11783/p15/v0/m0/messages/verb.proto";
/**
* Message for ALL requests sent to the messaging component.
*/
message Request {
string application_message_id = 1; // Client generated message ID. Used to uniquely identify the message on sender side
int64 application_message_seq_no = 2; // Sequence number from the client indicates the order in which the messages were sent
string sensor_id = 3; // ToDo
string capability_id = 4; // ToDo
Mode mode = 5; // The sending mode so the messaging component can properly process the message
repeated string recipients = 6; // Directly addressed endpoints. Addressed by the messaging component message IDs
ChunkComponent chunk_info = 7; // Used when transferring chunked messages. If the sent content inside the noun is not
chunked, this must be empty
google.protobuf.Timestamp timestamp = 8; // Client generated UTC timestamp at which the client sent the message
string reference = 9; // ToDo uuid reference to description (like stream description)
Verb verb = 10; // Verb for the scenario
google.protobuf.Any noun = 11; // Noun and data of the scenario
repeated google.protobuf.Any extension = 2048; // Used for proprietary purposes
}
Juha Backman

12. © Luonnonvarakeskus
MQTT communication with protobuf: ”Receive”
13.1.2021
response.proto
syntax = "proto3";
package iso11783.p15.v0.m0.messages;
import "google/protobuf/any.proto";
import "google/protobuf/timestamp.proto";
import "iso11783/p15/v0/m0/messages/verb.proto";
/**
* Message for ALL messages sent from the messaging component.
*/
message Response {
enum ResponseBodyType {
MESSAGES = 0;
}
int32 response_code = 1; // HTTP Response Codes will be used here (200, 400, 201, etc)
ResponseBodyType type = 2; // The Type of the body so that it can be decoded
string application_message_id = 3; // ID generated by the endpoint
string message_id = 4; // ID generated by messaging component
google.protobuf.Timestamp timestamp = 5; // UTC Timestamp when this message was generated by the messaging component.
Verb verb = 6; // Verb for the scenario
google.protobuf.Any noun = 7; // Noun and data of the scenario
string reference = 8; // Referenced object
string sender_id = 9; // Initial sender of the message
repeated google.protobuf.Any extension = 2048; // Used for proprietary purposes
}
void EFDIClient::MQTTMessageHandler(char * /* topic is not used */, int len, void *data)
{
// Handle received messages
Response response;
if(response.ParseFromArray(data,len))
{
if(response.has_noun())
{
qPrint() << "Received response " << response.noun().type_url().c_str() << endl;
// TODO: What to do with this?
if(response.noun().type_url() == "type.googleapis.com/iso11783.p15.v0.m0.messages.Reference")
{
Reference reference;
if(!reference.ParseFromString(response.noun().value()))
{
qWarning() << "Unable to parse reference response" << endl;
return;
}
SendReference(reference.reference().c_str(), response.sender_id().c_str());
}
[…….]
Juha Backman

13. © Luonnonvarakeskus
Capabilities response
Topic: commands/bdca6a0f-8011-462a-8f74-2f0beac1205e
Received response type.googleapis.com/iso11783.p15.v0.m0.messages.Reference
Send reference response
verb: SHOW
noun {
[type.googleapis.com/iso11783.p15.v0.m0.messages.ReferenceResponse] {
reference: "{d9b6efb6-92b7-4028-a986-a0db53717aed}"
referenced_object {
[type.googleapis.com/iso11783.p15.v0.m0.messages.Capabilities] {
capabilities {
noun_type_url: "type.googleapis.com/iso11783.p10.v1.m0.messages.FinishedWorkOrder"
verb_direction_list {
verb: PROCESS
direction: SEND_RECEIVE
}
}
}
} }}
13.1.2021
reference-request.scenario
/**
* Endpoint A sends a reference request to endpoint B.
* The reference was sent by endpoint B.
* Endpoint A wants to know to which message endpoint B references.
* Endpoint B responds with the message that is referenced by the sent reference.
* The request must be sent with mode DIRECT and endpoint B must be the recipient.
* The response must be sent with mode DIRECT and endpoint A must be the
recipient.
*
* @scenario {id} iso11783.p15.v0.m0.reference-request
* @scenario {name} "Reference Request"
* @scenario {request.verb} GET
* @scenario {request.noun} iso11783.p15.v0.m0.messages.Reference
* @scenario {response.verb} SHOW
* @scenario {response.noun} iso11783.p15.v0.m0.messages.ReferenceResponse
*/
Juha Backman

14. © Luonnonvarakeskus
Send subscriptions to EFDI server
Send subscriptions to EFDI server
mode: PUBLISH
verb: PROCESS
noun {
[type.googleapis.com/iso11783.p15.v0.m0.messages.Subscriptions] {
subscriptions {
noun_verb_list {
noun_type_url: "type.googleapis.com/iso11783.p10.v1.m0.messages.FinishedWorkOrder”
verbs: PROCESS
}
}
}}
Topic: commands/bdca6a0f-8011-462a-8f74-2f0beac1205e
Received response type.googleapis.com/iso11783.p15.v0.m0.messages.SubscriptionsResponse
13.1.2021
subscriptions-exchange.flow
/**
* The subscriptions should be exchanged when the client connects to the server for
the first time.
* Before removing subscriptions by sending an unsubscriptions message, the
endpoint needs to send a subscriptions message.
*
* @flow {id} iso11783.p15.v0.m0.subscriptions-exchange
* @flow {name} "Subscriptions Exchange"
* @flow {sequence} iso11783.p15.v0.m0.send-subscriptions
* @flow {sequence} [iso11783.p15.v0.m0.send-unsubscriptions]
*/
send-subscriptions.scenario
/**
* Messages that are sent with mode PUBLISH or PUBLISH_WITH_DIRECT are not
forwarded to any endpoint by default.
* An endpoint needs to subscribe to these messages in order to receive them.
* By sending a subscriptions message the endpoint announces that it want to
receive these messages.
*
* @scenario {id} iso11783.p15.v0.m0.send-subscriptions
* @scenario {name} "Send Subscriptions"
* @scenario {request.verb} PROCESS
* @scenario {request.noun} iso11783.p15.v0.m0.messages.Subscriptions
* @scenario {response.verb} ACKNOWLEDGE
* @scenario {response.noun} iso11783.p15.v0.m0.messages.SubscriptionsResponse
*/ Juha Backman

15. © Luonnonvarakeskus
Request information from EFDI server
Send endpointlist request to EFDI server
application_message_id: "{d56e03c9-544b-4504-9b54-d795b7e0c99c}”
application_message_seq_no: 4
sensor_id: "2546a359-a704-4ce3-8747-952ecf13255c”
capability_id: "2b287272-110e-4e0d-907f-63865caed69b”
mode: PUBLISH
timestamp { seconds: 1574244358 }
verb: GET
noun {
[type.googleapis.com/iso11783.p15.v0.m0.messages.ListEndpoints] {
capabilities {
noun_type_url: "type.googleapis.com/iso11783.p10.v1.m0.messages.WorkOrder”
verb_direction_list {
verb: PROCESS
direction: SEND_RECEIVE
}
}
}}
Topic: commands/bdca6a0f-8011-462a-8f74-2f0beac1205e
Received response type.googleapis.com/iso11783.p15.v0.m0.messages.ListEndpointsResponse
13.1.2021
list-endpoints-exchange.flow
/**
* How to request a list of endpoints.
*
* @flow {id} iso11783.p15.v0.m0.list-endpoints-exchange
* @flow {name} "List Endpoints Exchange"
* @flow {sequence} iso11783.p15.v0.m0.send-list-endpoints
*/
send-list-endpoints.scenario
/**
* To get a list of endpoints currently available on the server network.
*
* @scenario {id} iso11783.p15.v0.m0.send-list-endpoints
* @scenario {name} "Send List Endpoints"
* @scenario {request.verb} GET
* @scenario {request.noun} iso11783.p15.v0.m0.messages.ListEndpoints
* @scenario {response.verb} SHOW
* @scenario {response.noun} iso11783.p15.v0.m0.messages.ListEndpointsResponse
*/
Juha Backman

16. © Luonnonvarakeskus
TC Connect to EFDI Server
13.1.2021Juha Backman

17. © Luonnonvarakeskus
Connect to HTTP, MQTT and EFDI server
Send onboarding request to http://192.168.1.40:3123/onboard
Reply from server
Connecting to MQTT broker HOST:192.168.1.40 PORT:1883
Subscribe TOPIC commands/2141219c-af95-47e9-bbdb-e0145d616642
Send status to EFDI server
Send subscriptions to EFDI server
Send reference response
referenced_object {
[type.googleapis.com/iso11783.p15.v0.m0.messages.Capabilities] {
capabilities {
noun_type_url: "type.googleapis.com/iso11783.p10.v1.m0.messages.WorkOrder”
verb_direction_list {
verb: PROCESS
direction: SEND_RECEIVE
}
}
13.1.2021Juha Backman

18. © Luonnonvarakeskus
TC and FMIS are now connected to EFDI Server
13.1.2021Juha Backman

19. © Luonnonvarakeskus
FMIS continues polling TC clients…
Send endpointlist request to EFDI server
Topic: commands/bdca6a0f-8011-462a-8f74-2f0beac1205e
Received response type.googleapis.com/iso11783.p15.v0.m0.messages.ListEndpointsResponse
List of known endpoints:
id: 7125d634-5bb7-47fe-b6c4-6ee0e17741ce name: type: status:
13.1.2021Juha Backman

20. © Luonnonvarakeskus
FMIS send WorkOrder to TC
Send WorkOder to 7125d634-5bb7-47fe-b6c4-6ee0e17741ce
Topic: commands/bdca6a0f-8011-462a-8f74-2f0beac1205e
Received response type.googleapis.com/iso11783.p15.v0.m0.messages.ForwardInfo
Topic: commands/bdca6a0f-8011-462a-8f74-2f0beac1205e
Received response type.googleapis.com/iso11783.p10.v1.m0.messages.WorkOrderResponse
13.1.2021
Topic: commands/2141219c-af95-47e9-bbdb-e0145d616642
Received response type.googleapis.com/iso11783.p10.v1.m0.messages.WorkOrder
Send WorkOderResponse to 28fa24a0-b623-41bd-91ae-9f35d089c40b
Topic: commands/2141219c-af95-47e9-bbdb-e0145d616642
Received response type.googleapis.com/iso11783.p15.v0.m0.messages.ForwardInfo
TC receives WorkOrder
task-work.flow
/**
* Describes the handling of tasks between multiple endpoints.
* A planned task can be send to an endpoint.
* This planned task or any other task could be modified.
* In the end the completed work order is sent.
*
* @flow {id} iso11783.p10.v1.m0.task-work
* @flow {name} "Task Work"
* @flow {sequence} [iso11783.p10.v1.m0.planned-work-order]
* @flow {sequence} [iso11783.p10.v1.m0.modified-work-order]
* @flow {sequence} iso11783.p10.v1.m0.completed-work-order
*/
planned-work-order.scenario
/**
* A created task that shall be processed by the receiver.
*
* @scenario {id} iso11783.p15.v0.m0.planned-work-order
* @scenario {name} "Planned Work Order"
* @scenario {request.verb} PROCESS
* @scenario {request.noun} iso11783.p15.v0.m0.messages.WorkOrder
* @scenario {response.verb} ACKNOWLEDGE
* @scenario {response.noun} iso11783.p15.v0.m0.messages.WorkOrderResponse
*/
Juha Backman

21. © Luonnonvarakeskus
TC send FinishedWorkOrder to FMIS
Send FinishedWorkOder to Topic:commands/2141219c-af95-47e9-bbdb-e0145d616642
Received response type.googleapis.com/iso11783.p15.v0.m0.messages.ForwardInfo
13.1.2021
FMIS receives FinishedWorkOrder
Topic: commands/bdca6a0f-8011-462a-8f74-2f0beac1205e
Received response type.googleapis.com/iso11783.p10.v1.m0.messages.FinishedWorkOrder
completed-work-order.scenario
/**
* The endpoint completed a task.
* The task can be created by another endpoint but also be created by the endpoint
itself.
*
* @scenario {id} iso11783.p15.v0.m0.completed-work-order
* @scenario {name} "Completed Work Order"
* @scenario {request.verb} PROCESS
* @scenario {request.noun} iso11783.p15.v0.m0.messages.FinishedWorkOrder
* @scenario {response.verb} ACKNOWLEDGE
* @scenario {response.noun} iso11783.p15.v0.m0.messages.WorkOrderResponse
*/
Juha Backman

22. © Luonnonvarakeskus
TC disconnects from EFDI server
Send status to EFDI server
application_message_id: "{9e9c1302-b2ff-44e4-8e6f-e12c39ba876b}”
application_message_seq_no: 6
sensor_id: "b8fa65c4-cfd5-4308-a334-99fcfc4ea7d5”
capability_id: "0f00da34-187c-4885-b59c-a64ba953b7b9”
mode: PUBLISH
timestamp { seconds: 1551976533}
verb: NOTIFY
noun {
[type.googleapis.com/iso11783.p15.v0.m0.messages.ClientStatus] {
event: EXPECTED_OFFLINE
}}
13.1.2021Juha Backman

23. © Luonnonvarakeskus13.1.2021Juha Backman