Difference between revisions of "Subscription pattern communication diagram"
Jump to navigation
Jump to search
Hugo.berdon (talk | contribs) |
Hugo.berdon (talk | contribs) |
||
| Line 2: | Line 2: | ||
| − | ==Lookup routing information== | + | ==1. Lookup routing information== |
'''Request''' | '''Request''' | ||
*''Description'': Data Evaluator sends a request to the Connector DR. | *''Description'': Data Evaluator sends a request to the Connector DR. | ||
| Line 19: | Line 19: | ||
</blockquote> | </blockquote> | ||
| − | ==Lookup routing information== | + | ==2. Lookup routing information== |
'''Request''' | '''Request''' | ||
*''Description:'' Connector DR sends a request to the IDK to get routing information. | *''Description:'' Connector DR sends a request to the IDK to get routing information. | ||
| Line 36: | Line 36: | ||
</blockquote> | </blockquote> | ||
| − | ==Subscription request== | + | ==3. Subscription request== |
*''Description:'' Data Evaluator sends a subscription request to the Connector DR. Data Evaluator and Data Owner identify both components. | *''Description:'' Data Evaluator sends a subscription request to the Connector DR. Data Evaluator and Data Owner identify both components. | ||
| Line 45: | Line 45: | ||
*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. Data Owner identifier will be sent as the participant identifier. | *''Description:'' Connector DR sends a request to the SML to get the SMP address. Data Owner identifier will be sent as the participant identifier. | ||
*''Message type:'' Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 eDelivery SMP]’. | *''Message type:'' 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''' | ||
*''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 | *''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 | ||
| Line 63: | Line 63: | ||
*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. [40306] Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document. 3 | ||
| − | ==Subscription request== | + | ==6. Subscription request== |
*''Description:'' Connector DR sends a request to Connector DT to get the evidence. Same request as step 3. | *''Description:'' Connector DR sends a request to Connector DT to get the evidence. Same request as step 3. | ||
| Line 71: | Line 71: | ||
*Mandatory fields must be present in the request. [40302] | *Mandatory fields must be present in the request. [40302] | ||
| − | == Subscription request == | + | == 7. Subscription request == |
*''Description:'' Connector DT sends a subscription request to Data Owner. Same request as step 3. | *''Description:'' Connector DT sends a subscription request to Data Owner. Same request as step 3. | ||
| Line 79: | Line 79: | ||
*Mandatory fields must be present in the request. [40402] | *Mandatory fields must be present in the request. [40402] | ||
| − | == Subscription response == | + | == 8. Subscription response == |
* ''Description:'' Data Owner sends a response to Connector DT confirming the subscription. | * ''Description:'' Data Owner sends a response to Connector DT confirming the subscription. | ||
| Line 91: | Line 91: | ||
* 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. 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. 1 | *''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. 1 | ||
| − | ==Node information== | + | ==10. Node information== |
'''Request''' | '''Request''' | ||
| Line 115: | Line 115: | ||
Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document.3 | Detailed information is available in ‘[https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 eDelivery BDXL]’ Document.3 | ||
| − | ==Subscription response== | + | ==11. Subscription response== |
*''Description:'' Connector DT sends a response to Connector DR with the subscription. Same response as step 8. | *''Description:'' Connector DT sends a response to Connector DR with the subscription. Same response as step 8. | ||
| Line 125: | Line 125: | ||
*Mandatory fields must be present in the request. [40402] | *Mandatory fields must be present in the request. [40402] | ||
| − | ==Subscription response== | + | ==12. Subscription response== |
*''Description:'' Connector DR sends a response to Data Evaluator with the subscription. Same response as step 8. | *''Description:'' Connector DR sends a response to Data Evaluator with the subscription. Same response as step 8. | ||
Revision as of 09:15, 9 May 2022
1. Lookup routing information
Request
- Description: Data Evaluator sends a request to the Connector DR.
- Message type: Detailed in the ‘IAL Technical Design’ Document. 4
Response
- Description: Connector DR sends a response to Data Evaluator.
- Message type: Detailed in the ‘IAL Technical Design’ Document. 4
Error handling
If Data Evaluator cannot be reached there will be a communication error. [10603]
Mandatory fields must be present in the request. [40602]
* The interfaces are the same as the IAL, that’s why we refer to that document.
2. Lookup routing information
Request
- Description: Connector DR sends a request to the IDK to get routing information.
- Message type: Detailed in the ‘IAL Technical Design’ Document.
Response
- Description: IDK sends a response to Connector DR providing the routing information.
- Message type: Detailed in the ‘IAL Technical Design’ 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]
* The interfaces are the same as the IAL, that’s why we refer to that document.
3. Subscription request
- Description: Data Evaluator sends a subscription request to the Connector DR. Data Evaluator and Data Owner identify 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.
- Message type: 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’ Document. 3
6. Subscription request
- 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. Subscription request
- Description: Connector DT sends a subscription request to Data Owner. 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. [40402]
8. Subscription response
- Description: Data Owner sends a response to Connector DT confirming the subscription.
- Message type: Specified in ‘Data Dictionary’ Document. 6
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’ Document. 1
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’ Document.3
11. Subscription response
- Description: Connector DT sends a response to Connector DR with the subscription. 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. Subscription response
- Description: Connector DR sends a response to Data Evaluator with the subscription. 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]