Difference between revisions of "Subscription pattern communication diagram"
Jump to navigation
Jump to search
Hugo.berdon (talk | contribs) |
|||
Line 4: | Line 4: | ||
==1. Lookup routing information== | ==1. Lookup routing information== | ||
'''Request''' | '''Request''' | ||
− | *''Description'': Data Evaluator sends a request to the Connector DR. | + | * ''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 ‘[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/IAL%20design%20(2nd%20iteration)&fileid=1144261 IAL Technical Design]’. | + | * ''Message type:'' Detailed in the ‘[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/IAL%20design%20(2nd%20iteration)&fileid=1144261 IAL Technical Design]’. |
'''Response''' | '''Response''' | ||
− | *''Description:'' | + | * ''Description:'' The Connector DR sends the response to the Data Evaluator. |
− | *''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseLookupRoutingInformationType ResponseLookupRoutingInformation]'''. Detailed in the ‘[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/IAL%20design%20(2nd%20iteration)&fileid=1144261 IAL Technical Design]’. | + | * ''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseLookupRoutingInformationType ResponseLookupRoutingInformation]'''. Detailed in the ‘[https://newrepository.atosresearch.eu/index.php/apps/files/?dir=/DE4A-Project/06%20Workpackages/WP5%20Components%20design/IAL%20design%20(2nd%20iteration)&fileid=1144261 IAL Technical Design]’. |
'''Error handling''' | '''Error handling''' | ||
− | If Data Evaluator cannot be reached there will be a | + | * If Data Evaluator cannot be reached there will be a connection error. [[Https://wiki.de4a.eu/index.php/DE4A Logs and error messages it2#Data Requestor DRE01]] |
− | + | * Mandatory fields must be present in the request. [[Https://wiki.de4a.eu/index.php/DE4A Logs and error messages it2#Data Requestor DRE05]] | |
− | Mandatory fields must be present in the request. [[ | ||
− | |||
− | |||
==2. Lookup routing information== | ==2. Lookup routing information== |
Revision as of 10:37, 11 August 2022
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: Connector DR sends a request to the IDK to get routing information.
- Message type: Detailed in the ‘IAL Technical Design’.
Response
- Description: IDK sends a response to Connector DR providing the routing information.
- Message type: ResponseLookupRoutingInformation. Detailed in the ‘IAL Technical Design’.
Error handling
- If IDK cannot be reached there will be a communication error. [10303]
- If request information does not obtain results, there will be a no data found error. [10101]
* The interfaces are the same as the IAL, that’s why we refer to that document.
3. Subscription request
- Description: Data Evaluator sends a subscription request to the Connector DR. Data Evaluator and Data Owner identify both components.
- Message type: RequestEventSubscriptionType. Specified in Data Dictionary.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10603]
4. SMP addressing
- Description: Connector DR sends a request to the SML to get the SMP address. Data Owner identifier will be sent as the participant identifier.
- Message type: Detailed information is available in ‘eDelivery SMP’.
5. Node information
Request
- Description: Connector DR 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 DR 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. [10303]
- Mandatory fields must be present in the request. [10207]
- If request information does not obtain results, there will be a no data found error. [10201] Detailed information is available in ‘eDelivery BDXL’ Document.
6. Subscription request
- Description: Connector DR sends a request to Connector DT to get the evidence.
- Message type: RequestEventSubscriptionType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10303]
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.