Difference between revisions of "DBA 2nd iteration Solution Architecture"

From DE4A
Jump to navigation Jump to search
Line 81: Line 81:
 
work in progress...
 
work in progress...
  
−
Subscription
+
'''''Subscription'''''
  
−
<span style="background:#FFFF00">Based on definition on MVP some rows might disappear, i.e. for now the table is complete</span>
+
<span style="background:#FFFF00">Based on definition on MVP some rows might disappear, i.e. for now the tables are complete w.r.t. PSA</span>
 
{| class="wikitable"
 
{| class="wikitable"
 
|'''Process'''
 
|'''Process'''
Line 89: Line 89:
 
|'''Components'''
 
|'''Components'''
 
|-
 
|-
−
|'''Initiate subscription (DC)'''
+
|Initiate subscription (DC)
 
|Subscription Initiation
 
|Subscription Initiation
 
|
 
|
 
|-
 
|-
−
|'''Change subscription (DC)'''
+
|Change subscription (DC)
 
|Subscription Initiation
 
|Subscription Initiation
 
|
 
|
 
|-
 
|-
−
|'''Lookup event provider routing information (DC)'''
+
|Lookup event provider routing information (DC)
 
|Inquire Routing Information
 
|Inquire Routing Information
 
|
 
|
 
|-
 
|-
−
|'''Send subscription request (DC)'''
+
|Send subscription request (DC)
 
|
 
|
 
*  
 
*  
 
|
 
|
 
|-
 
|-
−
|'''Validate subscription request (DP)'''
+
|Validate subscription request (DP)
 
|
 
|
 
* eSignature Validation Service
 
* eSignature Validation Service
Line 113: Line 113:
 
|
 
|
 
|-
 
|-
−
|'''Evaluate subscription request (DP)'''
+
|Evaluate subscription request (DP)
 
|Subscription Evaluation
 
|Subscription Evaluation
 
|
 
|
 
|-
 
|-
−
|'''Exception: Prepare subscription error message (DP)'''
+
|Exception: Prepare subscription error message (DP)
 
|Subscription Error Handling
 
|Subscription Error Handling
 
|
 
|
 
|-
 
|-
−
|'''Exception Send subscription error message (DP)'''
+
|Exception Send subscription error message (DP)
 
|
 
|
 
* Message Encryption
 
* Message Encryption
Line 128: Line 128:
 
|
 
|
 
|-
 
|-
−
|'''Exception: Forward subscription error (DC)'''
+
|Exception: Forward subscription error (DC)
 
|n/a
 
|n/a
 
|
 
|
 
|-
 
|-
−
|'''Exception: Investigate reason for subscription error (DC)'''
+
|Exception: Investigate reason for subscription error (DC)
 
|n/a
 
|n/a
 
|
 
|
 
|-
 
|-
−
|'''Register subscription (DP)'''
+
|Register subscription (DP)
 
|Subscription Creation and Update
 
|Subscription Creation and Update
 
|
 
|
 
|-
 
|-
−
|'''Confirm subscription (DP)'''
+
|Confirm subscription (DP)
 
|Subscription Confirmation
 
|Subscription Confirmation
 
|
 
|
 
|-
 
|-
−
|'''Send subscription confirmation (DP)'''
+
|Send subscription confirmation (DP)
 
|
 
|
 
* Message Encryption
 
* Message Encryption
Line 151: Line 151:
 
|
 
|
 
|-
 
|-
−
|'''Forward confirmation (DC)'''
+
|Forward confirmation (DC)
 
|n/a
 
|n/a
 
|
 
|
 
|-
 
|-
−
|'''Log subscription information (DC)'''
+
|Log subscription information (DC)
 
|n/a
 
|n/a
 
|
 
|
 
|}
 
|}
−
Notification
+
'''''Notification'''''
 +
{| class="wikitable"
 +
|'''Process'''
 +
|'''Application Service'''
 +
|'''Components'''
 +
|-
 +
|Identify event
 +
|DO
 +
|Service
 +
|-
 +
|Check subscriptions
 +
|DO
 +
|Service
 +
|-
 +
|Prepare notification message and subscriber list
 +
|DO
 +
|Service
 +
|-
 +
|Exception trigger: Request from DE to resend event notifications
 +
|DE
 +
|User
 +
|-
 +
|Exception: Resend past events
 +
|DT
 +
|User
 +
|-
 +
|Resolve service metadata
 +
|DT
 +
|Service
 +
|-
 +
|Exception: Resolve subscriber participant ID and inform National Contact Point
 +
|DT
 +
|User
 +
|-
 +
|Send event notification
 +
|DT
 +
|Service
 +
|-
 +
|Validate event notification
 +
|DR
 +
|Service
 +
|-
 +
|Determine event response
 +
|DE
 +
|Service
 +
|-
 +
|Request change of subscription
 +
|DE
 +
|Subprocess
 +
|-
 +
|Dismiss event
 +
|DE
 +
|Service
 +
|-
 +
|Trigger evidence lookup
 +
|DE
 +
|Service
 +
|-
 +
|Identify business response and notify responsible party
 +
|DE
 +
|Subprocess
 +
|}
  
  
−
Lookup
+
'''''Lookup'''''
  
 
==== Component description ====
 
==== Component description ====

Revision as of 12:22, 27 July 2021

Introduction

Approach: we follow the SA as was done for Intermediation (1st iteration)

Scope and focus

  • Within scope
    • Modify DO/DE Mocks for S&N en Lookup patterns
    • Common component voor Cross-border subscriptions (optional for MS to use, i.e. not mandatory)
    • Event Notification + Evidence Lookup flavour, in line with PSA 2nd iteration
  • Outside scope
    • Resend a subscription request in case of an error (instead the possibility to inspect the logs and manually resend a request is deemed sufficient (MVP))
    • Include the Evidence in the notification (instead pure notification + lookup)
    • Attribute Lookup

DE4A preconditions

Design choices

Describe what WON'T be implemented for the pilot as well as design choices (see also scope section)

eIDAS and OOP TS

DBA eIDAS solution

Shared solution

Process realisation

Mapping processes/activities to application services and components (PSA --> tables).

Component description

Classify components: DE/DO/Common component.

Requirements

Describe the requirements for application services.

Component Implementation

Describe the implementation of the components.

Expected logical interfaces

Describe the (logical) interfaces between the components.

DC specific solution

Process realisation

Component description

Requirements

Component implementation

Expected logical interfaces

DP specific solution

Process realisation

Component description

Requirements

Component implementation

Expected logical interfaces

DBA OOP TS solution

Maybe this is the place to insert explanation of the subscription application collaboration (and notification?), i.e. front-end/back-end w.r.t. notifications.

The shared solution for the OOP TS consists of all common functionality of the OOP technical system. Most of the common OOP TS components need to be implemented by the data requestor and data transferor, although the OOP TS uses central components as well.

Shared solution OOP TS

Image might need an update, i.e. depict S&N and LKP shared stuff

Shared solution

The OOP TS domain (WP5) provide the data requestor and data transferor with the components needed for

  1. cross-border subscription and notification messages
  2. performing the lookup of an evidence

In the MVP the DBA pilot uses one type of subscription message and one type on notification message that all DC’s and DP’s involved will use. The subscription message is for subscribing to cross-border events generated at the DP. The notification message is for notifying the DC of such events. If the DC desires the Evidence can be retrieved using the Lookup. This implies an update of the IEM (WP3). There will be just one data provider per Member state: the business register, where the subscription will be recored and where the cross border events are generated, i.e.is the authentic source of company information. The DC will subscribe in one Member State at a time. The DP will notify one Member State at the time. The explicit request and the preview functions won't be needed, in both interaction patterns there is no user involvement.

Process realisation

work in progress...

Subscription

Based on definition on MVP some rows might disappear, i.e. for now the tables are complete w.r.t. PSA

Process Application Service Components
Initiate subscription (DC) Subscription Initiation
Change subscription (DC) Subscription Initiation
Lookup event provider routing information (DC) Inquire Routing Information
Send subscription request (DC)
Validate subscription request (DP)
  • eSignature Validation Service
  • Message Decryption
  • Authority Check
Evaluate subscription request (DP) Subscription Evaluation
Exception: Prepare subscription error message (DP) Subscription Error Handling
Exception Send subscription error message (DP)
  • Message Encryption
  • e-Signature Creation Service
  • Data Exchange Service
Exception: Forward subscription error (DC) n/a
Exception: Investigate reason for subscription error (DC) n/a
Register subscription (DP) Subscription Creation and Update
Confirm subscription (DP) Subscription Confirmation
Send subscription confirmation (DP)
  • Message Encryption
  • e-Signature Creation Service
  • Data Exchange Service
Forward confirmation (DC) n/a
Log subscription information (DC) n/a

Notification

Process Application Service Components
Identify event DO Service
Check subscriptions DO Service
Prepare notification message and subscriber list DO Service
Exception trigger: Request from DE to resend event notifications DE User
Exception: Resend past events DT User
Resolve service metadata DT Service
Exception: Resolve subscriber participant ID and inform National Contact Point DT User
Send event notification DT Service
Validate event notification DR Service
Determine event response DE Service
Request change of subscription DE Subprocess
Dismiss event DE Service
Trigger evidence lookup DE Service
Identify business response and notify responsible party DE Subprocess


Lookup

Component description

Requirements

Component implementation

Expected logical interfaces

DC-specific solution

Probably makes sense to split (two images) in notification and subscription

Process realization

Component description

Requirements

Component implementation

Expected logical interfaces

DP-specific solution

Process realisation

Component description

Requirements

Component implementation

Expected logical interfaces

Appendix: archimate component diagrams

DBA eIDAS solution architecture

OOP TS solution architecture

Retrieved from ‘https://wiki.de4a.eu/index.php?title=DBA_2nd_iteration_Solution_Architecture&oldid=3042’