Difference between revisions of "Lookup pattern communication diagram"
Hugo.berdon (talk | contribs) |
Hugo.berdon (talk | contribs) |
||
| Line 35: | Line 35: | ||
''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. | ||
| − | |||
'''Error handling''' | '''Error handling''' | ||
| Line 52: | Line 52: | ||
Data Evaluator and Data Owner identifies both components. | Data Evaluator and Data Owner identifies both components. | ||
| − | ''Message type:'' Specified in | + | ''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
'''Error handling''' | '''Error handling''' | ||
| Line 97: | Line 97: | ||
Same request as step 3. | Same request as step 3. | ||
| − | ''Message type:'' Specified in | + | ''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
'''Error handling''' | '''Error handling''' | ||
| Line 109: | Line 109: | ||
Same request as step 3. | Same request as step 3. | ||
| − | ''Message type:'' Specified in | + | ''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
'''Error handling''' | '''Error handling''' | ||
| Line 120: | Line 120: | ||
''Description:'' Data Owner sends a response to Connector DT with the evidence. | ''Description:'' Data Owner sends a response to Connector DT with the evidence. | ||
| − | ''Message type:'' Specified in | + | ''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
'''Error handling''' | '''Error handling''' | ||
| Line 166: | Line 166: | ||
*''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. | ||
| − | *''Message type:'' Specified in | + | *''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
'''Error handling''' | '''Error handling''' | ||
| Line 178: | Line 178: | ||
*''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. | ||
| − | *''Message type:'' Specified in | + | *''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
'''Error handling''' | '''Error handling''' | ||
Revision as of 15:50, 4 May 2022
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]
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]
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]
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’ Document. 1
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.3
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]
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]
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]
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’ Document. 1
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’ Document. 3
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]
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]