Difference between revisions of "User-supported intermediation pattern communication diagram"
Jump to navigation
Jump to search
| (13 intermediate revisions by the same user not shown) | |||
| Line 33: | Line 33: | ||
* ''Description:'' The Data Evaluator sends a request to the Connector DR to retrieve an evidence. In the message payload, Data Evaluator and Data Owner identify both components. | * ''Description:'' The Data Evaluator sends a request to the Connector DR to retrieve an evidence. In the message payload, Data Evaluator and Data Owner identify both components. | ||
| − | * ''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary# | + | * ''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceUSIType RequestExtractMultiEvidenceUSIType]'''. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. |
'''Response''' | '''Response''' | ||
| Line 99: | Line 99: | ||
* Description: The asynchronous message will have a response with the result of this communication. | * Description: The asynchronous message will have a response with the result of this communication. | ||
* Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. | * Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. | ||
| + | '''Error handling''' | ||
| + | |||
| + | * If the Connector DT cannot be reached there will be a connection error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE01]] | ||
==9. SMP addressing== | ==9. SMP addressing== | ||
| Line 108: | Line 111: | ||
==10. Node information== | ==10. Node information== | ||
'''Request''' | '''Request''' | ||
| − | + | * ''Description:'' The Connector DR sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’ documentation. | |
| − | * ''Description:'' The Connector DR sends a request to the SMP to get gateway information. Multi evidence approach is available in | ||
* ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document. | * ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document. | ||
| − | |||
'''Response''' | '''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. | * ''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. | * ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document. | ||
| − | |||
'''Error handling''' | '''Error handling''' | ||
| − | + | * If the SMP cannot be reached there will be a connection error. [[Https://wiki.de4a.eu/index.php/DE4A+Logs+and+error+messages+it2#Data+Requestor DRE01]] | |
| − | * If the SMP cannot be reached there will be a connection error. [ | + | * Mandatory fields must be present in the request. [[Https://wiki.de4a.eu/index.php/DE4A+Logs+and+error+messages+it2#Data+Requestor DRE05]] |
| − | + | * 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]]. | |
| − | + | Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ documentation. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | *Mandatory fields must be present in the request. [[ | ||
| − | * If request information does not obtain results, there will be a no data found error. [[ | ||
==11. Redirect user type (DT to DR)== | ==11. Redirect user type (DT to DR)== | ||
| + | '''Request''' | ||
| + | *''Description:'' The Connector DT sends redirection URL to the Connector DR. | ||
| − | + | *''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RedirectUserType RedirectUserType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | |
| − | *''Message | + | '''Response''' |
| − | + | * Description: The asynchronous message will have a response with the result of this communication. | |
| − | '''Error handling''' | + | * Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. |
| − | + | '''Error handling''' | |
| − | *If | + | *If the Data Evaluator cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE01]] |
| − | *Mandatory fields must be present in the request. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2# | + | *Mandatory fields must be present in the request. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE05]] |
==12. Redirect user type (DR to DE)== | ==12. Redirect user type (DR to DE)== | ||
| − | + | '''Request''' | |
| − | *''Description:'' Connector DR sends redirection URL to Data Evaluator. | + | *''Description:'' The Connector DR sends redirection URL to the Data Evaluator. |
*''Message Type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RedirectUserType RedirectUserType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | *''Message Type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RedirectUserType RedirectUserType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | ||
| + | '''Response''' | ||
| + | * Description: The asynchronous message will have a response with the result of this communication. | ||
| + | * Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If Data Evaluator cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2# | + | *If the Data Evaluator cannot be reached there will be a communication error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Requestor DRE01]] |
| − | *Mandatory fields must be present in the request. [[ | + | *Mandatory fields must be present in the request. [[Https://wiki.de4a.eu/index.php/DE4A+Logs+and+error+messages+it2#Data+Requestor DRE05]] |
==13. Extract multi-evidence response== | ==13. Extract multi-evidence response== | ||
| + | '''Request''' | ||
| + | * ''Description:'' The Data Owner sends a response to the Connector DT with the evidence. | ||
| − | *'' | + | * ''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseExtractMultiEvidenceType ResponseExtractMultiEvidenceType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
| + | '''Response''' | ||
| − | * | + | * Description: The asynchronous message will have a response with the result of this communication. |
| + | * Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. | ||
| − | '''Error handling | + | '''Error handling''' |
| − | *If | + | * If the evidence cannot be created there will be an error extracting the evidence. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE02]] |
| − | * | + | * If the evidence is not available when requested there will be an error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE03]] |
| + | * If the identity cannot be matched there will be an identity matching error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE04]] | ||
| + | * If the preview cannot be completed there will be an error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE05]] | ||
| + | * If the user identity cannot be re-established there will be an error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE06]] | ||
| + | * If the preview is rejected by the user there will be an error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE07]] | ||
| + | * If the canonical evidence cannot be generated there will be an error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Owner DOE08]] | ||
==14. SMP addressing== | ==14. SMP addressing== | ||
| − | *''Description:'' Connector | + | * ''Description:'' The Connector DT sends a request to the SML to get the SMP address. Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’ documentation. |
| + | |||
| + | *''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document. | ||
==15. Node information== | ==15. Node information== | ||
| − | '''Request''' | + | '''Request''' |
| + | * ''Description:'' The Connector DT sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 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. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE01]] | ||
| + | * Mandatory fields must be present in the request. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE05]] | ||
| + | * 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_Transferor DTE02]]. | ||
| + | Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ documentation. | ||
| − | *''Description:'' | + | ==16. Evidence response== |
| + | '''Request''' | ||
| + | * ''Description:'' The Connector DT sends a response to the Connector DR with the evidence information. | ||
| + | * ''Message Type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseExtractMultiEvidenceType ResponseExtractMultiEvidenceType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | ||
| + | '''Response''' | ||
| − | * | + | * Description: The asynchronous message will have a response with the result of this communication. |
| + | * Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. | ||
'''Error handling''' | '''Error handling''' | ||
| − | *If | + | * If the Connector DR cannot be reached there will be a connection error. [[https://wiki.de4a.eu/index.php/DE4A_Logs_and_error_messages_it2#Data_Transferor DTE01]] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==17. Forward evidence== | ==17. Forward evidence== | ||
| + | '''Request''' | ||
| + | *''Description:'' The Connector DR sends the response to the Data Evaluator with the evidence information. | ||
| − | *'' | + | * ''Message Type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseExtractMultiEvidenceType ResponseExtractMultiEvidenceType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
| + | '''Response''' | ||
| − | * | + | * Description: The asynchronous message will have a response with the result of this communication. |
| + | * Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]. | ||
| − | '''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]] |
Latest revision as of 08:19, 2 September 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
Request
- Description: The Data Evaluator sends a request to the Connector DR to retrieve an evidence. In the message payload, Data Evaluator and Data Owner identify both components.
- Message type: RequestExtractMultiEvidenceUSIType. 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. Request evidence
Request
- Description: The Connector DR sends a request to the Connector DT to retrieve the evidence.
- Message type: RequestExtractMultiEvidenceUSIType. 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. Extract multi-evidence request
Request
- Description: The Connector DT sends a request to the Data Owner to retrieve the evidence.
- Message type: RequestExtractMultiEvidenceUSIType. 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. Redirect user type (DO to DT)
Request
- Description: The Data Owner sends redirection URL to the Connector DT.
- Message type: RedirectUserType. 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 Connector DT cannot be reached there will be a connection error. [DOE01]
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 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.
11. Redirect user type (DT to DR)
Request
- Description: The Connector DT sends redirection URL to the Connector DR.
- Message type: RedirectUserType. 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 Evaluator cannot be reached there will be a communication error. [DTE01]
- Mandatory fields must be present in the request. [DTE05]
12. Redirect user type (DR to DE)
Request
- Description: The Connector DR sends redirection URL to the Data Evaluator.
- Message Type: RedirectUserType. 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 Evaluator cannot be reached there will be a communication error. [DRE01]
- Mandatory fields must be present in the request. [DRE05]
13. Extract multi-evidence response
Request
- Description: The Data Owner sends a response to the Connector DT with the evidence.
- Message type: ResponseExtractMultiEvidenceType. 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 evidence cannot be created there will be an error extracting the evidence. [DOE02]
- If the evidence 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]
- If the canonical evidence cannot be generated there will be an error. [DOE08]
14. SMP addressing
- Description: The Connector DT 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.
15. 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.
16. Evidence response
Request
- Description: The Connector DT sends a response to the Connector DR with the evidence information.
- Message Type: ResponseExtractMultiEvidenceType. 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 Connector DR cannot be reached there will be a connection error. [DTE01]
17. Forward evidence
Request
- Description: The Connector DR sends the response to the Data Evaluator with the evidence information.
- Message Type: ResponseExtractMultiEvidenceType. 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 Data Evaluator cannot be reached there will be a connection error. [DRE01]