Difference between revisions of "Lookup pattern communication diagram"
Jump to navigation
Jump to search
Hugo.berdon (talk | contribs) |
Hugo.berdon (talk | contribs) |
||
| Line 102: | Line 102: | ||
==7. Evidence lookup== | ==7. Evidence lookup== | ||
| − | * ''Description:'' Connector DT sends a request to Data Owner to get the evidence | + | * ''Description:'' Connector DT sends a request to Data Owner to get the evidence. |
* ''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | * ''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | ||
| Line 160: | Line 160: | ||
==11. Evidence response== | ==11. Evidence response== | ||
| − | *''Description:'' The Connector DT sends a response to the Connector DR with the evidence | + | *''Description:'' The Connector DT sends a response to the Connector DR with the evidence. |
*''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | *''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | ||
| Line 172: | Line 172: | ||
==12. Evidence response== | ==12. Evidence response== | ||
| − | *''Description'': Connector DR sends a response to the Data Evaluator with the evidence | + | *''Description'': Connector DR sends a response to the Data Evaluator with the evidence. |
*''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | *''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. | ||
Revision as of 10:51, 17 May 2022
1. Lookup routing information
Request
- Description: Data Evaluator sends a request to the Connector DR.
- Message type: The message type is detailed in the ‘IAL Technical Design’.
Response
- Description: Connector DR sends a response to Data Evaluator.
- Message type: The message type is detailed in the ‘IAL Technical Design’.
* The interfaces are the same as the IAL, that’s why we refer to that document.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40602]
2. Lookup routing information
Request
- Description: Connector DR sends a request to the IDK to get routing information.
- Message type: The message type is detailed in the ‘IAL Technical Design’.
Response
- Description: IDK sends a response to Connector DR providing the routing information.
- Message type: The message type is detailed in the ‘IAL Technical Design’.
* The interfaces are the same as the IAL, that’s why we refer to that document.
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]
3. Evidence lookup
- Description: Data Evaluator sends a request to the Connector DR to get the updated evidence.
Data Evaluator and Data Owner identifies both components.
- Message type: Specified in ‘Data Dictionary’.
Error handling
- If Connector DR cannot be reached there will be a communication error. [10603]
- Mandatory fields must be present in the request. [40602]
4. SMP addressing
Description: Connector DR sends a request to the SML to get the SMP address.
Data Owner identifier will be sent as the participant identifier.
Detailed information is available in ‘eDelivery SMP’.
5. Node information
Request
- Description: Connector DR 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’ 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. [40302]
- If request information does not obtain results, there will be a no data found error. [40306]
Detailed information is available in eDelivery BDXL.
6. Evidence lookup
- Description: Connector DR sends a request to Connector DT to get the evidence.
Same request as step 3.
- Message type: Specified in ‘Data Dictionary’.
Error handling
- If Connector DT cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40302]
7. Evidence lookup
- Description: Connector DT sends a request to Data Owner to get the evidence.
- Message type: 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. [40402]
- If request information does not obtain results, there will be a no data found error. [40406]
8. Evidence response
- Description: Data Owner sends a response to Connector DT with the evidence.
- Message type: 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’.
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’ Document.
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. [40402]
- If request information does not obtain results, there will be a no data found error. [40406]
Detailed information is available in ‘eDelivery BDXL’.
11. Evidence response
- Description: The Connector DT sends a response to the Connector DR with the evidence.
- Message type: Specified in ‘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. Evidence response
- Description: Connector DR sends a response to the Data Evaluator with the evidence.
- Message type: Specified in ‘Data Dictionary’.
Error handling
- If Data Evaluator cannot be reached there will be a communication error. [10303]
- Mandatory fields must be present in the request. [40302]
* Document is under construction.