Subscription pattern communication diagram

1. Lookup routing information

Request

• Description: The Data Evaluator sends a request to the Connector DR to obtain the Data Owner identifier. A canonical evidence type must be provided, also an optional country code can be specified to obtain the response.

• Message type: Detailed in the ‘IAL Technical Design’.

Response

• Description: The Connector DR sends the response to the Data Evaluator.

• Message type: ResponseLookupRoutingInformation. Detailed in the ‘IAL Technical Design’.

Error handling

• If Data Evaluator cannot be reached there will be a connection error. [DRE01]
• Mandatory fields must be present in the request. [DRE05]

2. Lookup routing information

Request

• Description: The Connector DR sends a request to the Central IAL to get the routing information. The request received from the Data Evaluator is sent to the IAL.

• Message type: Detailed in the ‘IAL Technical Design’.

Response

• Description: The Central IAL sends a response to the Connector DR providing the routing information.

• Message type: ResponseLookupRoutingInformation. Detailed in the ‘IAL Technical Design'.

Error handling

• If IAL cannot be reached there will be a communication error. [DRE06]
• If request information does not obtain results, there will be a no data found error. [DRE02]

3. Subscription request

Request

• Description: The Data Evaluator sends a subscription request to the Connector DR. In the message payload, Data Evaluator and Data Owner identify both components.

• Message type: RequestEventSubscriptionType. Specified in Data Dictionary.

Response

• Description: The asynchronous message will have a response with the result of this communication.
• Message type: ResponseErrorType. Specified in Data Dictionary.

Error handling

• If Connector DR cannot be reached there will be a connection error. [DRE01]

4. SMP addressing

• Description: The Connector DR sends a request to the SML to get the SMP address. Detailed information is available in ‘eDelivery SMP’ documentation.

• Message type: Detailed in ‘eDelivery usage in DE4A’ document.

5. Node information

Request

• Description: The Connector DR sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘eDelivery SMP’ documentation.

• Message type: Detailed in ‘eDelivery usage in DE4A’ document.

Response

• Description: The SMP sends a response to the Connector DR providing the gateway information. The destination endpoint and the certificate will be provided in the response.

• Message type: Detailed in ‘eDelivery usage in DE4A’ document.

Error handling

• If the SMP cannot be reached there will be a connection error. [DRE01]
• Mandatory fields must be present in the request. [DRE05]
• If request information does not obtain results, there will be a no data found error. [DRE02].

Detailed information is available in ‘eDelivery BDXL’ documentation.

6. Subscription request

Request

• Description: The Connector DR sends a subscription request to the Connector DT. In the message payload, Data Evaluator and Data Owner identify both components.

• Message type: RequestEventSubscriptionType. Specified in Data Dictionary.

Response

• Description: The asynchronous message will have a response with the result of this communication.
• Message type: ResponseErrorType. Specified in Data Dictionary.

Error handling

• If Connector DT cannot be reached there will be a connection error. [DRE01]

7. Subscription request

Request

• Description: The Connector DT sends a subscription request to the Data Owner.

• Message type: RequestEventSubscriptionType. Specified in ‘Data Dictionary’.

Response

• Description: The asynchronous message will have a response with the result of this communication.
• Message type: ResponseErrorType. Specified in Data Dictionary.

Error handling

• If the Data Owner cannot be reached there will be a connection error. [DTE01]

• If request information does not obtain results, there will be a no data found error. [DTE02]

8. Subscription response

Request

• Description: The Data Owner sends a response to the Connector DT confirming the subscription.

• Message type:  ResponseEventSubscriptionType. Specified in ‘Data Dictionary’.

Response

• Description: The asynchronous message will have a response with the result of this communication.
• Message type: ResponseErrorType. Specified in Data Dictionary.

Error handling  

• If the subscription cannot be created there will be an error. [DOE02]
• If the subscription is not available when requested there will be an error. [DOE03]
• If the identity cannot be matched there will be an identity matching error. [DOE04]
• If the preview cannot be completed there will be an error. [DOE05]
• If the user identity cannot be re-established there will be an error. [DOE06]
• If the preview is rejected by the user there will be an error. [DOE07]

9. SMP addressing

• Description: The Connector DR sends a request to the SML to get the SMP address. Detailed information is available in ‘eDelivery SMP’ documentation.

• Message type: Detailed in ‘eDelivery usage in DE4A’ document.

10. Node information

Request

• Description: The Connector DT sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘eDelivery SMP’ documentation.

• Message type: Detailed in ‘eDelivery usage in DE4A’ document.

Response

• Description: The SMP sends a response to the Connector DT providing the gateway information. The destination endpoint and the certificate will be provided in the response.

• Message type: Detailed in ‘eDelivery usage in DE4A’ document.

Error handling

• If the SMP cannot be reached there will be a connection error. [DTE01]
• Mandatory fields must be present in the request. [DTE05]
• If request information does not obtain results, there will be a no data found error. [DTE02].

Detailed information is available in ‘eDelivery BDXL’ documentation.

11. Subscription response

Request

• Description: The Connector DT sends a response to the Connector DR confirming the subscription.

• Message type:  ResponseEventSubscriptionType. Specified in ‘Data Dictionary’.

Response

• Description: The asynchronous message will have a response with the result of this communication.
• Message type: ResponseErrorType. Specified in Data Dictionary.

Error handling

• If Connector DR cannot be reached there will be a connection error. [DTE01]

12. Subscription response

Request

• Description: The Connector DR sends a response to the Data Evaluator confirming the subscription.

• Message type:  ResponseEventSubscriptionType. Specified in ‘Data Dictionary’.

Response

• Description: The asynchronous message will have a response with the result of this communication.
• Message type: ResponseErrorType. Specified in Data Dictionary.

Error handling

• If Connector DR cannot be reached there will be a connection error. [DRE01]