Message structure
All Datahub messages contain the following parts:
Message header data
Process data
Payload
Header
Message header data includes the following:
Data field | Level | Necessity | Note |
|---|---|---|---|
Header data | 1 | 1..1 | In Datahub’s messaging, an acknowledgement message is constructed for each received message. No acknowledgement request is used in the message header. |
Message identification | 2 | 1..1 | A unique identifier for the message The message ID must always be unique to the sender. Datahub will reject a message if a message has already been received from the same sender with the same message ID and the event is asynchronous (see Event synchronicity/asynchronicity and Datahub external interface specification). Resending is always done with a new message ID, both for corrected data and when the same data is re-sent. |
Message type | 2 | 1..1 |
|
Message creation time | 2 | 1..1 |
|
Technical sender of message | 2 | 1..1 | Included fields are described in the message type descriptions. The technical actor of a message is the party that delivers or receives the message. The juridical actor of a message is the party whose data is handled in the message. For example, if the service provider takes care of the collection and delivery of metering data to Datahub (on behalf of the DSO), the technical sender is the service provider and the juridical sender is the DSO. The technical actor must always have an authorisation for the process in question from the juridical actor.
|
Juridical sender of message | 2 | 1..1 | |
Technical recipient of message | 2 | 1..1 | |
Juridical recipient of message | 2 | 1..1 | |
Sender’s routing data | 2 | 0..1 | Routing data set by the sender The message sender may set routing data for the message. This data is returned in an acknowledgement message. Routing data can be utilised in the routing of the received acknowledgement to the system sending the original message. |
Message number | 2 | 0..1 | In the Datahub processes DH-22X the reply might contain a large amount of information. In this case, the reply will be divided into multiple messages, keeping the size of the single message down. The fields Message number and Total number of messages contain the values for how many messages there are in total and what number the specific message has. |
Total number of messages | 2 | 0..1 | |
Registration time | 2 | 0..1 | The registration time of the data in Datahub. Used in process DH-211 to indicate the time when the metering data was stored in Datahub. |
A more detailed description of the header can be found on the Header page.
Process
Message process data includes the following:
Data field | Level | Necessity | Note |
|---|---|---|---|
Process | 1 | 1..1 |
|
Process identification | 2 | 1..1 | Uses Datahub event identifications (e.g. DH-111-1) |
Information exchange role | 2 | 1..1 |
|
Industry | 2 | 1..1 | Electricity |
A technical description of the process data can be found on the Process page.
Payload (Transaction)
Events and data content for processes are described separately for each event. Technical descriptions of general message types can be found under message type descriptions.