DBA 2nd iteration Solution Architecture

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

Design choices

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

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.

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 table is complete

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

Lookup

DC-specific solution

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