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

From DE4A
Jump to navigation Jump to search
Line 68: Line 68:
 
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.   
 
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.   
 
[[File:Shared OOPTS.png|none|thumb|547x547px|Shared solution OOP TS]]
 
[[File:Shared OOPTS.png|none|thumb|547x547px|Shared solution OOP TS]]
−
<span style="background:#FFFF00">Image might need an update</span>   
+
<span style="background:#FFFF00">Image might need an update, i.e. depict S&N and LKP shared stuff</span>   
  
 
=== Shared solution ===
 
=== 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.
+
The OOP TS domain (WP5) provide the data requestor and data transferor with the components needed for  
  
−
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 <span style="background:#FFFF00">IEM</span> (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.
+
# cross-border subscription and notification messages
 +
# performing the lookup of an evidence
  
−
The DC will subscribe in one Member state at a time.  
+
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 <span style="background:#FFFF00">IEM</span> (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.  
  
−
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.
+
==== Process realisation ====
 +
work in progress...
 +
{| class="wikitable"
 +
|'''Process'''
 +
|'''Application service'''
 +
|'''Components'''
 +
|-
 +
|Lookup  routing information (DC)
 +
|Inquire  routing information (collaboration : information desk)
 +
|·      DE4A connector
 +
 
 +
·      Evidence service locator (ESL) configuration file
 +
 
 +
·      SMP
 +
 
 +
·      DNS & SML
 +
|-
 +
|Request  evidence (DC)
 +
|Message  encryption
 +
 
 +
e-signature  creation service
 +
 
 +
data  exchange service
 +
|·      DE4A Connector
  
−
==== Process realisation ====
+
·      eDelivery AS4 gateway
 +
|-
 +
|Forward  evidence (DC)
 +
|Message  decryption
 +
 
 +
e-signature  verification and validation service
 +
 
 +
data  exchange service
 +
|·      DE4A Connector
 +
 
 +
·      eDelivery AS4 gateway
 +
|-
 +
|Evaluate  evidence request (DP)
 +
|Message  decryption
 +
 
 +
e-signature  verification and validation service
 +
 
 +
data  exchange service
 +
|·      DE4A Connector
 +
 
 +
·      eDelivery AS4 gateway
 +
|-
 +
|Communicate  non-availability of OOP (DP)
 +
|data  exchange service
 +
|·      DE4A Connector
 +
 
 +
·      eDelivery AS4 gateway
 +
|-
 +
|Transfer  evidence (DP)
 +
|Message  encryption
 +
 
 +
e-signature  creation service
 +
 
 +
data  exchange service
 +
|·      DE4A connector
 +
 
 +
·      Configuration file to find the participant identifier
 +
 
 +
·      SMP
 +
 
 +
·      DNS & SML
 +
|}
  
 
==== Component description ====
 
==== Component description ====

Revision as of 11:02, 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...

Process Application service Components
Lookup routing information (DC) Inquire routing information (collaboration : information desk) ·      DE4A connector

·      Evidence service locator (ESL) configuration file

·      SMP

·      DNS & SML

Request evidence (DC) Message encryption

e-signature creation service

data exchange service

·      DE4A Connector

·      eDelivery AS4 gateway

Forward evidence (DC) Message decryption

e-signature verification and validation service

data exchange service

·      DE4A Connector

·      eDelivery AS4 gateway

Evaluate evidence request (DP) Message decryption

e-signature verification and validation service

data exchange service

·      DE4A Connector

·      eDelivery AS4 gateway

Communicate non-availability of OOP (DP) data exchange service ·      DE4A Connector

·      eDelivery AS4 gateway

Transfer evidence (DP) Message encryption

e-signature creation service

data exchange service

·      DE4A connector

·      Configuration file to find the participant identifier

·      SMP

·      DNS & SML

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=3036’