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

Shared solution

The OOP TS domain (WP5) shall provide the data requestor and data transferor with the components needed for cross-border subscription and notification messages.

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. 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, which is the authentic source of company information.

The DC will subscribe in one Member state at a time.

Although the explicit request and the preview functions will be implemented by the DC in its eProcedure portal, DBA expects guidelines for doing so (MVP) and reference software to ease the implementation (second pilot run). That’s why the requirements for these functionalities have been included in this section.

DC-specific solution

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