Subscription pattern communication diagram
Revision as of 10:45, 11 August 2022 by Mpttfp eduardo.moreno (talk | contribs) (→6. Subscription request)
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
- Description: Connector DT sends a subscription request to Data Owner.
- Message type: RequestEventSubscriptionType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10303]
8. Subscription response
- Description: Data Owner sends a response to Connector DT confirming the subscription.
- Message type: Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10503]
9. SMP addressing
- Description: Connector DT sends a request to the SML to get the SMP address. Data Evaluator identifier will be sent as the participant identifier. Detailed information is available in ‘eDelivery SMP’ Document.
10. Node information
Request
- Description: Connector DT sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘SMP query process in DE4A’ Document.
- Message type: Detailed in ‘eDelivery usage in DE4A’ Document. *
Response
- Description: SMP sends a response to Connector DT providing the gateway information. The destination endpoint and the certificate will be provided.
- Message type: Detailed in ‘eDelivery usage in DE4A’ Document. *
Error handling
- If SMP cannot be reached there will be a communication error. [10403]
- If request information does not obtain results, there will be a no data found error. [10201]
Detailed information is available in ‘eDelivery BDXL’ Document.3
11. Subscription response
- Description: Connector DT sends a response to Connector DR with the subscription.
- Message Type: ResponseEventSubscriptionType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10403]
12. Subscription response
- Description: Connector DR sends a response to Data Evaluator with the subscription.
- Message Type: ResponseEventSubscriptionType. Specified in ‘Data Dictionary’.
Error handling
- If Data Evaluator cannot be reached there will be a communication error. [10303]
* Document is under construction.