Difference between revisions of "Notification pattern communication diagram"
Jump to navigation
Jump to search
Hugo.berdon (talk | contribs) |
Hugo.berdon (talk | contribs) |
||
Line 3: | Line 3: | ||
== Make notification == | == Make notification == | ||
− | * ''Description'': Data Owner sends a message to the Connector DT with the notification. | + | * ''Description'': Data Owner sends a message to the Connector DT with the notification. Data Evaluator and Data Owner identify both components. |
− | * ''Message type'': Specified in | + | * ''Message type'': Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
Line 15: | Line 15: | ||
== SMP addressing == | == 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. 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]’. |
== Node information == | == Node information == | ||
Line 45: | Line 45: | ||
* ''Description:'' The Connector DT sends a message to the Connector DR with the notification. Same message as step 1. | * ''Description:'' The Connector DT sends a message to the Connector DR with the notification. Same message as step 1. | ||
− | * ''Message type:'' Specified in | + | * ''Message type:'' Specified in ‘[https://wiki.de4a.eu/index.php/Data_Dictionary Data Dictionary]’. |
'''Error handling''' | '''Error handling''' | ||
Line 56: | Line 56: | ||
* ''Description:'' Connector DR sends a message to the Data Evaluator with the notification. Same message as step 1. | * ''Description:'' Connector DR sends a message to the Data Evaluator with the notification. Same message as step 1. | ||
− | * ''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 11:13, 4 May 2022
Make notification
- Description: Data Owner sends a message to the Connector DT with the notification. Data Evaluator and Data Owner identify both components.
- 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’.
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’.
Send notification
- Description: The Connector DT sends a message to the Connector DR with the notification. Same message as step 1.
- 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]
Forward notification
- Description: Connector DR sends a message to the Data Evaluator with the notification. Same message as step 1.
- 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]