Difference between revisions of "Intermediation pattern communication diagram"

From DE4A
Jump to navigation Jump to search
 
(47 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[File:Comm diag it2 ALL v3.5-IM.drawio.png|alt=DE4A Conceptual Schema|center|thumb|945x945px]]
+
[[File:Comm_diag_it2_ALL_v3.6-IM.drawio.png|alt=DE4A Conceptual Schema|center|thumb|945x945px]]
  
== [[Lookup routing information]] ==
+
== 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.
  
=== Request ===
+
* ''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'''
 +
* ''Description:'' The Connector DR sends the response to the Data Evaluator.
  
* Description: Data Evaluator sends a request to the Connector DR.  
+
* ''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'''
  
* Message type: Detailed in the ‘IAL Technical Design’ Document. 4
+
* 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]]
  
=== Response ===
+
==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.
  
* Description: Connector DR sends a response to Data Evaluator.
+
* ''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'''
 +
* ''Description:'' The Central IAL sends a response to the Connector DR providing the routing information.
  
* Message type: Detailed in the ‘IAL Technical Design’ Document. 4
+
* ''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 communication error. [10603]  
+
* If IAL cannot be reached there will be a communication error. [<nowiki/>[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. [<nowiki/>[Https://wiki.de4a.eu/index.php/DE4A+Logs+and+error+messages+it2#Data+Requestor 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.
  
Mandatory fields must be present in the request. [40602]   <blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document.  
+
* ''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceIMType RequestExtractMultiEvidenceIMType]'''. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary].
 +
'''Response'''
  
</blockquote>
+
* 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].
  
==[[Lookup routing information]]==
+
'''Error handling'''
 +
* If Connector DR cannot be reached there will be a connection error. [[Https://wiki.de4a.eu/index.php/DE4A+Logs+and+error+messages+it2#Data+Requestor DRE01]]
  
=== Request ===
+
==4. SMP addressing==
* Description: Connector DR sends a request to the IDK to get routing information.
+
* ''Description:'' The Connector DR 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 the ‘IAL Technical Design’ Document.
+
* ''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 ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’ documentation.
  
=== Response ===
+
* ''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.
  
* Description: IDK sends a response to Connector DR providing the routing information.  
+
* ''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+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]]
 +
* 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.
  
* Message type: Detailed in the ‘IAL Technical Design’ Document.
+
==6. Request evidence==
=== Error handling ===
+
'''Request'''
 +
*''Description:'' The Connector DR sends a request to the Connector DT to retrieve the evidence.
  
* If IDK cannot be reached there will be a communication error. [10303]  
+
* ''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceIMType RequestExtractMultiEvidenceIMType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary].
* Mandatory fields must be present in the request. [40302]  
+
'''Response'''
* If request information does not obtain results, there will be a no data found error. [40306]
 
<blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document.   
 
  
</blockquote>
+
* 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].
  
==[[Request evidence]]==
+
'''Error handling'''
 +
* If Connector DT cannot be reached there will be a connection error. [[Https://wiki.de4a.eu/index.php/DE4A+Logs+and+error+messages+it2#Data+Requestor DRE01]]
  
=== Request ===
+
==7. Extract multi-evidence request==
 +
'''Request'''
 +
*''Description'': The Connector DT sends a request to the Data Owner to retrieve the 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:''  '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceIMType RequestExtractMultiEvidenceIMType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
 +
'''Response'''
  
* Message type: Specified in ‘Data Dictionary’ Document.
+
* 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 Connector DR cannot be reached there will be a communication error. [10603]  
+
* If the Data Owner 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. [40602]  
 
  
<blockquote>* The interfaces are the same as the IAL, that’s why we refer to that document.</blockquote>
+
* 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]]
  
==[[SMP addressing]]==
+
==8. Extract multi-evidence response==
=== Request ===
+
'''Request'''
* Description: Connector DR sends a request to the SML to get the SMP address.  Detailed information is available in ‘eDelivery SMP’ Document. 1
+
* ''Description:'' The Data Owner sends a response to the Connector DT with the evidence.
  
* Message type: Detailed in ‘eDelivery usage in DE4A’ Document. 5
+
* ''Message type:''  '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseExtractMultiEvidenceType ResponseExtractMultiEvidenceType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
==[[Node information]]==
+
'''Response'''
  
=== Request ===
+
* Description: The asynchronous message will have a response with the result of this communication.
* Description: Connector DR sends a request to the SMP to get gateway information. Multi evidence approach is available in ‘eDelivery SMP’ Document. 1
+
* 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: Detailed in ‘eDelivery usage in DE4A’ Document. 5
+
'''Error handling'''  
  
=== Response ===
+
* 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]]
  
* Description: SMP sends a response to Connector DR providing the gateway information.  The destination endpoint and the certificate will be provided.  
+
==9. SMP addressing==
  
* Message type: Detailed in ‘eDelivery usage in DE4A’ Document. 5
+
* ''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 ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’ documentation.
=== Error handling ===
 
  
* If SMP cannot be reached there will be a communication error. [10303]
+
==10. Node information==
* Mandatory fields must be present in the request. [40302]
+
'''Request'''  
* If request information does not obtain results, there will be a no data found error. [40306]  Detailed information is available in ‘eDelivery BDXL’ Document. 3
 
  
==[[Request evidence]]==
+
* ''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 ‘[https://wiki.de4a.eu/index.php/Intermediation_pattern_communication_diagram#NOTE eDelivery usage in DE4A]’.
  
=== Request ===
+
'''Response'''
* Description: Connector DR sends a request to Connector DT to get the evidence. Same request as step 3.
 
  
* Message type: Specified in ‘Data Dictionary’ Document. 6
+
* ''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.
  
=== Error handling ===
+
* ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
  
* If Connector DT cannot be reached there will be a communication error. [10303]
+
'''Error handling'''
* Mandatory fields must be present in the request. [40302]
 
  
==[[Extract multi-evidence request]]==
+
* 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]]
 +
* 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]].
  
==[[Extract multi-evidence response]]==
+
Detailed information is available in ‘eDelivery BDXL’ documentation.
  
==[[SMP addressing]]==
+
==11. 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'''
  
==[[Node information]]==
+
* 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].
  
==[[Evidence response]]==
+
'''Error handling'''
  
==[[Forward evidence]]==
+
* 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]]
 +
 
 +
==12. 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'''
 +
 
 +
* 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 12:59, 12 August 2022

DE4A Conceptual Schema

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.

Response

  • Description: The Connector DR sends the response to the Data Evaluator.

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.

Response

  • Description: The Central IAL sends a response to the Connector DR providing the routing information.

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.

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.

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.

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. Extract multi-evidence response

Request

  • Description: The Data Owner sends a response to the Connector DT with the evidence.

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]

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’ documentation.

10. 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’.

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. [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. Evidence response

Request

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]

12. Forward evidence

Request

  • Description: The Connector DR sends the response to the Data Evaluator with the evidence information.

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]