Difference between revisions of "User-supported intermediation pattern communication diagram"
Jump to navigation
Jump to search
Hugo.berdon (talk | contribs) |
|||
| Line 3: | Line 3: | ||
==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. [[https://wiki.de4a.eu/index.php/ | ||
| − | |||
| − | |||
==2. Lookup routing information== | ==2. Lookup routing information== | ||
'''Request''' | '''Request''' | ||
| − | *''Description:'' Connector DR sends a request to the | + | *''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 ‘[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 Central IAL sends a response to the Connector DR providing the routing information. |
*''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 | + | * If IAL cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A+Logs+and+error+messages+it2#Data+Requestor DRE06]] |
| − | * If request information does not obtain results, there will be a no data found error. [[https://wiki.de4a.eu/index.php/ | + | * If request information does not obtain results, there will be a no data found error. [[https://wiki.de4a.eu/index.php/DE4A+Logs+and+error+messages+it2#Data+Requestor DRE02]] |
== 3. Request evidence== | == 3. Request evidence== | ||
Revision as of 10:59, 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: 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. Request evidence
- Description: Data Evaluator sends a request to the Connector DR to get the evidence. Data Evaluator and Data Owner identify both components.
- Message type: RequestExtractMultiEvidenceUSIType. Specified in Data Dictionary.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10603]
- Mandatory fields must be present in the request. [40602]
4. SMP addressing
- Description: Connector DR sends a request to the SML to get the SMP address. Detailed information is available in ‘eDelivery SMP’ Document.
- Message type: Detailed in ‘eDelivery usage in DE4A’ Document. *
5. Node information
Request
- Description: Connector DR sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘eDelivery SMP’ 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. Request evidence
- Description: Connector DR sends a request to Connector DT to get the evidence.
- Message type: RequestExtractMultiEvidenceUSIType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10303]
7. Extract multi-evidence request
- Description: Connector DT sends a request to Data Owner to get the evidence.
- Message type: RequestExtractMultiEvidenceUSIType. Specified in ‘Data Dictionary’.
Error handling
- If Data Owner cannot be reached there will be a communication error. [10403]
- Mandatory fields must be present in the request. [10507]
- If request information does not obtain results, there will be a no data found error. [10501]
8. Redirect user type (DO to DT)
- Description: Data Owner sends redirection URL to Connector DT.
- Message type: RedirectUserType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10503]
- Mandatory fields must be present in the request. [40502]
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 with 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]
- Mandatory fields must be present in the request. [10207]
- If request information does not obtain results, there will be a no data found error. [10501] Detailed information is available in ‘eDelivery BDXL’ Document.
11. Redirect user type (DT to DR)
- Description:Connector DT sends redirection URL to Connector DR.
- Message Type: RedirectUserType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10403]
- Mandatory fields must be present in the request. [40402]
12. Redirect user type (DR to DE)
- Description: Connector DR sends redirection URL to Data Evaluator.
- Message Type: RedirectUserType. Specified in ‘Data Dictionary’.
Error handling
- If Data Evaluator cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40302]
13. Extract multi-evidence response
- Description: Data Owner sends a response to Connector DT with the evidence list.
- Message type: ResponseExtractMultiEvidenceType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10503]
- Mandatory fields must be present in the request. [40502]
14. SMP addressing
- Description: Connector DR 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.
15. 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 with 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]
- Mandatory fields must be present in the request. [10207]
- If request information does not obtain results, there will be a no data found error. [10501] Detailed information is available in ‘eDelivery BDXL’ Document.
16. Evidence response
- Description: Connector DT sends a response to Connector DR with the evidence.
- Message type: ResponseExtractMultiEvidenceType. Specified in ‘Data Dictionary’ Document.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10403]
17. Forward evidence
- Description: Connector DR sends a response to the Data Evaluator with the evidence.
- Message type: ResponseExtractMultiEvidenceType. Specified in ‘Data Dictionary’ Document.
Error handling
- If Data Evaluator cannot be reached there will be a communication error. [10303]
* Document is under construction.