Difference between revisions of "User-supported intermediation pattern communication diagram"

From DE4A
Jump to navigation Jump to search
 
(34 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[File:Comm diag it2 ALL v3.5-USI.drawio.png|center|thumb|945x945px]]
+
[[File:Comm diag it2 ALL v3.6-USI.drawio.png|alt=|center|thumb|945x945px]]
  
 
==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:'' Connector DR sends a response to Data Evaluator.
+
*''Description:'' The Connector DR sends the response to the Data Evaluator.
  
−
*''Message type:''  '''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 communication error. [10603]  
+
* 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. [40602]    <blockquote><nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document.  
 
−
 
 
−
</blockquote>
 
  
 
==2. Lookup routing information==
 
==2. Lookup routing information==
 
'''Request'''
 
'''Request'''
−
*''Description:'' Connector DR sends a request to the IDK to get routing information.
+
*''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:'' IDK sends a response to Connector DR providing the routing information.
+
*''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 IDK cannot be reached there will be a communication error. [10303]
 
−
*Mandatory fields must be present in the request. [40302]
 
−
*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>
+
* 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/DE4A+Logs+and+error+messages+it2#Data+Requestor DRE02]]
  
 
==3. Request evidence==
 
==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:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceUSIType RequestExtractMultiEvidenceUSIType]'''. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary].
 +
'''Response'''
  
−
*''Description:'' Data Evaluator sends a request to the Connector DR to get the evidence.   Data Evaluator and Data Owner identify both components.
+
* 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#RequestExtractMultiEvidenceUSIType RequestExtractMultiEvidenceUSIType]'''. 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 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]]
−
*Mandatory fields must be present in the request. [40602]
 
  
 
==4. SMP addressing==
 
==4. SMP addressing==
−
*''Description:'' 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]’ Document.
+
* ''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 ‘eDelivery usage in DE4A’ document.
  
−
*''Message type:'' Detailed in ‘eDelivery usage in DE4A’ Document. 5
 
 
==5. Node information==
 
==5. Node information==
 
'''Request'''
 
'''Request'''
−
*''Description:'' 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]’ Document.
+
* ''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.
  
−
*''Message type:'' Detailed in ‘eDelivery usage in DE4A’ Document. 5
+
* ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
 
'''Response'''
 
'''Response'''
−
*''Description:'' SMP sends a response to Connector DR providing the gateway information.   The destination endpoint and the certificate will be provided.
+
* ''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. 5
+
* ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
 
'''Error handling'''
 
'''Error handling'''
−
*If SMP cannot be reached there will be a communication error. [10303]
+
* 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. [40302]
+
* 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. [40306]     Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document. 3
+
* 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.
  
 
==6. Request evidence==
 
==6. Request evidence==
−
*''Description:'' Connector DR sends a request to Connector DT to get the evidence. Same request as step 3.
+
'''Request'''
 +
*''Description:'' The Connector DR sends a request to the Connector DT to retrieve the evidence.
  
 
*''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceUSIType RequestExtractMultiEvidenceUSIType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary 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'''
 +
 +
* 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 DT cannot be reached there will be a communication error. [10303]
+
* 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]]
−
*Mandatory fields must be present in the request. [40302]
 
  
 
==7. Extract multi-evidence request==
 
==7. Extract multi-evidence request==
 +
'''Request'''
 +
*''Description'': The Connector DT sends a request to the Data Owner to retrieve the evidence.
  
−
*''Description'': Connector DT sends a request to Data Owner to get the evidence. Same request as step 3.
+
*''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'''
  
−
*''Message type:''  '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestExtractMultiEvidenceUSIType RequestExtractMultiEvidenceUSIType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
+
* 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 Owner cannot be reached there will be a communication error. [10403]
+
* 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. [40402]
 
  
−
*If request information does not obtain results, there will be a no data found error. [40406]
+
* 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]]
  
−
==8. Redirect user type (DO to DT) ==
+
==8. Redirect user type (DO to DT)==
−
 
+
'''Request'''
−
*''Description:'' Data Owner sends redirection URL to Connector DT.  
+
*''Description:'' The Data Owner sends redirection URL to the Connector DT.
  
 
*''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 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]]
  
−
*If Connector DT cannot be reached there will be a communication error. [10503]
+
==9. SMP addressing==
−
*Mandatory fields must be present in the request. [40502]
 
  
−
==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.
  
−
*''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]’ Document.
+
* ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
  
 
==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:'' Connector DT sends a request to the SMP to get gateway information.    Multi evidence approach is available in ‘SMP query process in DE4A’ Document. 2
+
* ''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
−
*''Message type:''  Detailed in ‘eDelivery usage in DE4A’ Document. 5
+
'''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.
  
−
'''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+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.
  
−
*''Description:'' SMP sends a response to Connector DT with the gateway information. The destination endpoint and the certificate will be provided.
+
==11. Redirect user type (DT to DR)==
 +
'''Request'''
 +
*''Description:'' The Connector DT sends redirection URL to the Connector DR.
  
−
*''Message type:'' Detailed in ‘eDelivery usage in DE4A’ Document. 5
+
*''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'''
 +
*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#Data_Transferor DTE05]]
  
−
'''Error handling'''
+
==12. Redirect user type (DR to DE)==
−
 
+
'''Request'''
−
*If SMP cannot be reached there will be a communication error. [10403]
+
*''Description:'' The Connector DR sends redirection URL to the Data Evaluator.
−
*Mandatory fields must be present in the request. [40402]
 
−
*If request information does not obtain results, there will be a no data found error. [40406] Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document.3
 
−
 
 
−
==11. Redirect user type (DT to DR) ==
 
−
 
 
−
*''Description:''Connector DT sends redirection URL to 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]’.
 
−
 
 
−
'''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. Same response as step 8.
 
  
 
*''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. [10303]
+
*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. [40302]
+
*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:'' Data Owner sends a response to Connector DT with the evidence list.  
+
* ''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]’.
 
* ''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'''
  
−
'''Error handling  '''
+
* 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].
  
−
* If Connector DT cannot be reached there will be a communication error. [10503]
+
'''Error handling'''  
−
* Mandatory fields must be present in the request. [40502]
 
  
−
== 14. SMP addressing ==
+
* 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]]
−
*''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 ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’ Document.
+
* 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]]
  
−
== 15. Node information ==
+
==14. SMP addressing==
−
'''Request'''  
+
* ''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.
  
−
*''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. 2
+
*''Message type:'' Detailed in ‘eDelivery usage in DE4A’ document.
−
*''Message type:''  Detailed in ‘eDelivery usage in DE4A’ Document. 5
 
  
−
'''Response'''  
+
==15. Node information==
 +
'''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.
  
−
*''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.
 +
'''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. 5
+
*''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.
  
−
'''Error handling'''  
+
==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'''
  
−
*If SMP cannot be reached there will be a communication error. [10403]
+
* Description: The asynchronous message will have a response with the result of this communication.
−
*Mandatory fields must be present in the request. [40402]
+
* Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary].
−
*If request information does not obtain results, there will be a no data found error. [40406] Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document.3
 
  
−
== 16. Evidence response ==
+
'''Error handling'''
  
−
* ''Description:'' Connector DT sends a response to Connector DR with the evidence. Same response as step 8.  
+
* 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]]
  
−
* ''Message type:''  '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseExtractMultiEvidenceType ResponseExtractMultiEvidenceType]'''. Specified in ‘Data Dictionary’ Document. 6
+
==17. Forward evidence==
 +
'''Request'''
 +
*''Description:'' The Connector DR sends the response to the Data Evaluator with the evidence information.
  
−
'''Error handling'''  
+
* ''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'''
  
−
* If Connector DR cannot be reached there will be a communication error. [10403]  
+
* Description: The asynchronous message will have a response with the result of this communication.
−
* Mandatory fields must be present in the request. [40402]  
+
* Message type: [https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseErrorType ResponseErrorType]. Specified in [https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary].
  
−
== 17. Forward evidence ==
+
'''Error handling'''  
−
 
 
−
* ''Description:'' Connector DR sends a response to the Data Evaluator with the evidence. Same response as step 8.
 
−
 
 
−
* ''Message type:''  '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseExtractMultiEvidenceType ResponseExtractMultiEvidenceType]'''. Specified in ‘Data Dictionary’ Document.  
 
−
 
 
−
'''Error handling'''  
 
  
−
* If Data Evaluator cannot be reached there will be a communication error. [10303]  
+
* 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. [40302]
 

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.

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. Redirect user type (DO to DT)

Request

  • Description: The Data Owner sends redirection URL to the Connector DT.

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.

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.

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.

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

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.

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]
Retrieved from ‘https://wiki.de4a.eu/index.php?title=User-supported_intermediation_pattern_communication_diagram&oldid=5485’