Request event
Datahub does not deliver messages to parties automatically. The messages created are buffered in a delivery queue, from which the party retrieves them one by one. Datahub delivers messages in the order of their creation time (present in the message’s header). A retrieved message remains in the queue until the party has separately informed Datahub that the message has been retrieved. The parties retrieve the messages using the request event. The data content of a request event is as follows:
Data field | Level | Necessity | Note |
|---|---|---|---|
Request event | 1 | 1..1 |
|
Message package | 2 | 1..1 |
In addition to payload, acknowledgement events related to the message package in question are also returned. |
Asynchronous data retrievals, i.e. metering data and invoice row data retrievals, are differentiated to their own separate queues for each party. This way asynchronous retrievals do not get mixed up with other information exchange. Metering data is differentiated for each party separately to two queues: one for DH-211 data forwarded by Datahub and one for DH-220 data requested by the party. Parties can decide themselves how the queues will be unloaded to their own systems.