Difference between revisions of "Subscription pattern communication diagram"

From DE4A
Jump to navigation Jump to search
Line 51: Line 51:
 
==5. 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.  
  
 
*''Message type:'' Detailed in ‘eDelivery usage in DE4A’ Document. *
 
*''Message type:'' Detailed in ‘eDelivery usage in DE4A’ Document. *
Line 61: Line 61:
 
*If SMP cannot be reached there will be a communication error. [10303]
 
*If SMP cannot be reached there will be a communication error. [10303]
 
*Mandatory fields must be present in the request. [40302]
 
*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 ‘[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.  
  
 
==6. 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.  
  
 
*''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
 
*''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
Line 72: Line 72:
  
 
== 7. 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.  
  
 
*''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
 
*''Message type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#RequestEventSubscriptionType RequestEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
Line 93: Line 93:
 
==9. 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.  
  
 
==10. Node information==
 
==10. Node information==
 
'''Request'''  
 
'''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
+
*''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. *
 
*''Message type:''  Detailed in ‘eDelivery usage in DE4A’ Document. *
  
Line 117: Line 117:
 
==11. 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.  
 
*''Message Type:''  '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseEventSubscriptionType ResponseEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
 
*''Message Type:''  '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseEventSubscriptionType ResponseEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
  
Line 127: Line 127:
 
==12. 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.  
  
 
*''Message Type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseEventSubscriptionType ResponseEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.
 
*''Message Type:'' '''[https://wiki.de4a.eu/index.php/Data_Dictionary#ResponseEventSubscriptionType ResponseEventSubscriptionType]'''. Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’.

Revision as of 11:50, 17 May 2022


1. Lookup routing information

Request

  • Description: Data Evaluator sends a request to the Connector DR.

Response

  • Description: Connector DR sends a response to Data Evaluator.

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.

Response

  • Description: IDK sends a response to Connector DR providing the routing information.

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.

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.
  • 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’ Document.

6. Subscription request

  • Description: Connector DR sends a request to Connector DT to get the evidence.

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.

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.

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.

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’ Document.3

11. Subscription response

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.

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.