Difference between revisions of "Lookup pattern communication diagram"
Hugo.berdon (talk | contribs) |
Hugo.berdon (talk | contribs) |
||
| Line 1: | Line 1: | ||
[[File:Comm diag it2 ALL v3.5-Lookup.drawio.png|center|thumb|930x930px]] | [[File:Comm diag it2 ALL v3.5-Lookup.drawio.png|center|thumb|930x930px]] | ||
| − | ==Lookup routing information== | + | ==1. Lookup routing information== |
'''Request''' | '''Request''' | ||
| Line 13: | Line 13: | ||
''Message type:'' The message type is detailed in the ‘IAL Technical Design’ Document. 4 | ''Message type:'' The message type is detailed in the ‘IAL Technical Design’ Document. 4 | ||
| − | |||
| − | |||
<nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | <nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | ||
| Line 23: | Line 21: | ||
*Mandatory fields must be present in the request. [40602] | *Mandatory fields must be present in the request. [40602] | ||
| − | ==Lookup routing information== | + | ==2. Lookup routing information== |
'''Request''' | '''Request''' | ||
| Line 35: | Line 33: | ||
''Message type:'' The message type is detailed in the ‘IAL Technical Design’ Document. 4 | ''Message type:'' The message type is detailed in the ‘IAL Technical Design’ Document. 4 | ||
| − | |||
| − | |||
<nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | <nowiki>*</nowiki> The interfaces are the same as the IAL, that’s why we refer to that document. | ||
| Line 47: | Line 43: | ||
*If request information does not obtain results, there will be a no data found error. [40306] | *If request information does not obtain results, there will be a no data found error. [40306] | ||
| − | ==Evidence lookup== | + | ==3. Evidence lookup== |
''Description:'' Data Evaluator sends a request to the Connector DR to get the updated evidence. | ''Description:'' Data Evaluator sends a request to the Connector DR to get the updated evidence. | ||
| Line 59: | Line 55: | ||
*Mandatory fields must be present in the request. [40602] | *Mandatory fields must be present in the request. [40602] | ||
| − | ==SMP addressing== | + | ==4. SMP addressing== |
''Description:'' Connector DR sends a request to the SML to get the SMP address. | ''Description:'' Connector DR sends a request to the SML to get the SMP address. | ||
| Line 66: | Line 62: | ||
Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’. | Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’. | ||
| − | ==Node information== | + | ==5. Node information== |
'''Request''' | '''Request''' | ||
| Line 92: | Line 88: | ||
Detailed information is available in [https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]. | Detailed information is available in [https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]. | ||
| − | ==Evidence lookup== | + | ==6. Evidence lookup== |
''Description:'' Connector DR sends a request to Connector DT to get the evidence. | ''Description:'' Connector DR sends a request to Connector DT to get the evidence. | ||
| Line 104: | Line 100: | ||
*Mandatory fields must be present in the request. [40302] | *Mandatory fields must be present in the request. [40302] | ||
| − | ==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. | ||
| Line 117: | Line 113: | ||
*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. [40406] | ||
| − | ==Evidence response== | + | ==8. Evidence response== |
''Description:'' Data Owner sends a response to Connector DT with the evidence. | ''Description:'' Data Owner sends a response to Connector DT with the evidence. | ||
| Line 128: | Line 124: | ||
*Mandatory fields must be present in the request. [40502] | *Mandatory fields must be present in the request. [40502] | ||
| − | ==SMP addressing== | + | ==9. SMP addressing== |
''Description:'' Connector DT sends a request to the SML to get the SMP address. | ''Description:'' Connector DT sends a request to the SML to get the SMP address. | ||
| Line 135: | Line 131: | ||
Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’. | Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’. | ||
| − | ==Node information== | + | ==10. Node information== |
'''Request''' | '''Request''' | ||
| Line 162: | Line 158: | ||
Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’. | Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’. | ||
| − | ==Evidence response== | + | ==11. Evidence response== |
*''Description:'' The Connector DT sends a response to the Connector DR with the evidence. Same response as step 8. | *''Description:'' The Connector DT sends a response to the Connector DR with the evidence. Same response as step 8. | ||
| Line 174: | Line 170: | ||
*Mandatory fields must be present in the request. [40402] | *Mandatory fields must be present in the request. [40402] | ||
| − | ==Evidence response== | + | ==12. Evidence response== |
*''Description'': Connector DR sends a response to the Data Evaluator with the evidence. Same response as step 8. | *''Description'': Connector DR sends a response to the Data Evaluator with the evidence. Same response as step 8. | ||
Revision as of 09:16, 9 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’ Document. 4
Response
Description: Connector DR sends a response to Data Evaluator.
Message type: The message type is detailed in the ‘IAL Technical Design’ Document. 4
* 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’ Document. 4
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’ Document. 4
* 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. 2
Message type: Detailed in ‘eDelivery usage in DE4A’ Document. 5
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. 5
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.
Same request as step 3.
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. 2
Message type: Detailed in ‘eDelivery usage in DE4A’ Document. 5
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. 5
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. Same response as step 8.
- 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. Same response as step 8.
- 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]