User-supported intermediation pattern communication diagram

From DE4A
Revision as of 08:19, 2 September 2022 by Mpttfp eduardo.moreno (talk | contribs) (→‎3. Request evidence)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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’