Difference between revisions of "Intermediation pattern communication diagram"
Jump to navigation
Jump to search
Hugo.berdon (talk | contribs) |
Hugo.berdon (talk | contribs) |
||
| Line 28: | Line 28: | ||
* ''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 IDK cannot be reached there will be a communication error. [<nowiki/>10303] | + | * If IDK cannot be reached there will be a communication error. [<nowiki/>[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Error_messages_2 10303]] |
| − | * If request information does not obtain results, there will be a no data found error. [<nowiki/>10101] | + | * If request information does not obtain results, there will be a no data found error. [<nowiki/>[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Error_messages_2 10101]] |
<blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | <blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | ||
| Line 41: | Line 41: | ||
'''Error handling''' | '''Error handling''' | ||
* If Connector DR cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10603]] | * If Connector DR cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10603]] | ||
| − | |||
<blockquote>* The interfaces are the same as the IAL, that’s why we refer to that document.</blockquote> | <blockquote>* The interfaces are the same as the IAL, that’s why we refer to that document.</blockquote> | ||
| Line 60: | Line 59: | ||
'''Error handling''' | '''Error handling''' | ||
* If SMP cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10303]] | * If SMP cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10303]] | ||
| − | * Mandatory fields must be present in the request. [10207] | + | * Mandatory fields must be present in the request. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Error_messages_2 10207]] |
| − | * If request information does not obtain results, there will be a no data found error. [10201] Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document. | + | * 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#Error_messages_2 10201]] Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document. |
==6. Request evidence== | ==6. Request evidence== | ||
| Line 79: | Line 78: | ||
* If Data Owner cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10403]] | * If Data Owner cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10403]] | ||
| − | * Mandatory fields must be present in the request. [10507] | + | * Mandatory fields must be present in the request. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Error_messages_2 10507]] |
| − | * If request information does not obtain results, there will be a no data found error. [10501] | + | * 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#Error_messages_2 10501]] |
==8. Extract multi-evidence response== | ==8. Extract multi-evidence response== | ||
| Line 113: | Line 112: | ||
* If SMP cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10403]] | * If SMP cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Connector 10403]] | ||
| − | * Mandatory fields must be present in the request. [10207] | + | * Mandatory fields must be present in the request. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Error_messages_2 10207]] |
| − | * If request information does not obtain results, there will be a no data found error. [10501] | + | * 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#Error_messages_2 10501]] |
Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document. | Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document. | ||
Revision as of 11:12, 23 May 2022
1. Lookup routing information
Request
- Description: Data Evaluator sends a request to the Connector DR.
- Message type: Detailed in the ‘IAL Technical Design’.
Response
- Description: Connector DR sends a response to Data Evaluator.
- Message type: ResponseLookupRoutingInformation. Detailed in the ‘IAL Technical Design’.
Error handling
If Data Evaluator cannot be reached there will be a communication error. [10603]
Mandatory fields must be present in the request. [40602]
* The interfaces are the same as the IAL, that’s why we refer to that document.
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. 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: RequestExtractMultiEvidenceIMType. Specified in Data Dictionary.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10603]
* The interfaces are the same as the IAL, that’s why we refer to that document.
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: RequestExtractMultiEvidenceIMType. 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: RequestExtractMultiEvidenceIMType. 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. Extract multi-evidence response
- Description: Data Owner sends a response to Connector DT with the evidence.
- 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]
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’.
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]
- 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. Evidence response
- Description: Connector DT sends a response to Connector DR with the evidence.
- Message Type: ResponseExtractMultiEvidenceType. Specified in ‘Data Dictionary’.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10403]
12. Forward evidence
- Description: Connector DR sends a response to Data Evaluator with the evidence.
- Message Type: ResponseExtractMultiEvidenceType. Specified in ‘Data Dictionary’.
Error handling
- If Data Evaluator cannot be reached there will be a communication error. [10303]
* Document is under construction.