Difference between revisions of "Useful information on pilots and participants"
(Undo revision 5145 by Javier.ferrero (talk)) Tag: Undo |
(Undo revision 5144 by Javier.ferrero (talk)) Tag: Undo |
||
Line 987: | Line 987: | ||
At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.[[File:DE4A network IT2-Country set-up A.drawio.png|frame|alt=|left]] | At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.[[File:DE4A network IT2-Country set-up A.drawio.png|frame|alt=|left]] | ||
[[File:DE4A network IT2-Country set-up B.drawio.png|frame|alt=|none]] | [[File:DE4A network IT2-Country set-up B.drawio.png|frame|alt=|none]] | ||
− | |||
− | |||
Revision as of 09:48, 2 June 2022
Useful information about the pilots and the participants in DE4A during the second iteration of the project. This information is intended to serve as a reference for the configuration and operation of the partners' infrastructures and the Playground. Each partner is responsible for entering and keeping the information collected on this Wiki page up-to-date.
Progress of the deployment of DE4A participants' infrastructures in iteration 2
SMP in Member States
MS | Member State | Participant | Own SMP (Deployed & configured / In progress / No, planned for X) |
---|---|---|---|
AT | Austria | ||
ES | Spain | SGAD | Deployed & configured: phoss SMP v5.6.2 |
LU | Luxembourg | ||
NL | The Netherlands | ||
PT | Portugal | ||
RO | Romania | ||
SU | Sweden | ||
SI | Slovenia |
DE4A Connector in Member States
MS | Member State | Participant | Own Connector (Deployed & configured / In progress / No, planned for X) |
---|---|---|---|
AT | Austria | ||
ES | Spain | SGAD | |
LU | Luxembourg | ||
NL | The Netherlands | ||
PT | Portugal | ||
RO | Romania | ||
RO | Romania | ||
SU | Sweden | ||
SI | Slovenia |
Summary of pilots and participants during the second iteration
Summary of DE4A pilots IT2
Iteration 2 | ||||
---|---|---|---|---|
Pilot | Use case | Use case name | Interaction pattern used | Evidence exchanged |
Studying abroad (SA) | UC1.1 | Application to public higher education | User-Supported Intermediation (USI) | Higher Education Diploma
Secondary Education Diploma |
UC1.2 | Applying for study grant | User-Supported Intermediation (USI) | Higher Education Diploma
Large Family Evidence Disability Evidence | |
UC1.3 | Diploma / Certs / Studies / Professional recognition | Verifiable Credentials (VC) | Higher Education Diploma | |
Doing business abroad (DBA) | UC2.1 | Starting a business in another Member State | Intermediation (IM)
Subscription and Notification (S&N) |
Company Registration |
UC2.2 | Doing business in another Member State | Intermediation (IM)
Subscription and Notification (S&N) Lookup (LU) |
Company Registration | |
Moving abroad (MA) | UC3.1 | Request address change | Registration: User-Supported Intermediation (USI)
Deregistration: Notification (S&N) and Lookup (LU) |
Domicile Registration Evidence |
UC3.2 | Request an extract or copy of civil state certificate | User-Supported Intermediation (USI) | Birth Evidence
Marriage Evidence | |
UC3.3 | Request pension information - Claim pension | Intermediation (IM) | Pension Evidence
Unemployment Evidence Working Life Evidence |
DE4A pilot participants IT2
Partner | SA | DBA | MA | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Short name | Name | Country | Participant ID | UC1.1 | UC1.2 | UC1.3 | UC2.1 | UC2.2 | UC3.1 | UC3.2 | UC3.3 | Notes |
BMDW | Bundesministerium fuer Digitalisierung und Wirtschaftsstandort | AT | iso6523-actorid-upis::9991:at000000271 | DE
DO |
DE
DO |
|||||||
BRZ | Bundesrechenzentrum GMBH (Federal Data Center) | AT | iso6523-actorid-upis::9991:at000000027 | DR
DT |
DR
DT |
|||||||
SGAD | Secretaría General de Administración Digital (General Secretariat for Digital Administration) | ES | iso6523-actorid-upis::9920:ess2833002e | DR
DO,DT |
DO,DT | DP | DO,DT | DE,DR
DO,DT |
DO,DT | |||
UJI | Universitat Jaume I de Castellón (Jaume I University of Castellón) | ES | iso6523-actorid-upis::9920:esq6250003h | DE | *Connector provided by SGAD. UJI is also an evidence provider in all SA UCs through SGAD. | |||||||
CTIE | Centre des Technologies de l'Information de l'Etat (State Information Technology Center) | LU | iso6523-actorid-upis::9991:lu000000025 | DE,DR
DO,DT |
DE,DR
DO,DT |
|||||||
RVO | Rijksdienst voor Ondernemend Nederland (Netherlands Enterprise Agency) | NL | iso6523-actorid-upis::9991:nl000000024 | DE,DR
DO,DT |
DE,DR
DO,DT |
|||||||
AMA-IP | Agencia para a Modernizacao Administrativa IP (Administration Modernization Agency) | PT | iso6523-actorid-upis::9991:pt000000026 | DR
DT |
DT | DR
DO,DT |
DR | DR | ||||
INESC-ID | Institute for Systems and Computer Engineering, Technology and Science | PT | iso6523-actorid-upis::9991:pt990000101 | DE
DO |
DO | DC
DP |
*INESC-ID does not directly take part of the DE4A network. It is consulted by AMA-IP when necessary. | |||||
SEF | Serviço de Estrangeiros e Fronteiras (Foreigners and Borders Service) | PT | ¿? | DE | DE | DE | ||||||
MoAI | Ministerul Afacerilor Interne (Ministry of Internal Affairs) | RO | iso6523-actorid-upis::9991:ro000000005 | DE,DR
DO,DT |
DE,DR
DO,DT |
|||||||
ORNC | Oficiul National B22 al Registrului Comertului | RO | iso6523-actorid-upis::9991:ro000000006 | DE,DR
DO,DT |
DE,DR
DO,DT |
|||||||
BVE | Bolagsverket (Companies Registration Office) | SE | iso6523-actorid-upis::9991:se000000013 | DE,DR | DE,DR | |||||||
JSI | Institut Jožef Stefan | SI | iso6523-actorid-upis::9991:si000000018 | DE | ||||||||
MIZŠ | Ministrstvo za Izobraževanje, Znanost in Šport (Ministry of Education, Science and Sport) | SI | iso6523-actorid-upis::9920:si000000016 | DE
DO |
DC
DP |
*The central preview functionality for DO is provided by SI-MPA. | ||||||
SI-MPA | Ministrstvo za javno upravo (Ministry of Public Administration) | SI | iso6523-actorid-upis::9991:si000000015 | DR
DT |
DR | DE,DR
DO,DT |
DE,DR
DO,DT |
Technical information on participants IT2
Test domain (Playground) |
Pilot domain | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
DE4A infrastructure IT2
Playground infrastructure IT2
The following diagram depicts the Playground infrastructure for the second iteration, with the deployment of its corresponding components.
Pilot partners infrastructure flavours IT2
The following two diagrams outline the general infrastructure expected from the Member States and partners involved in the pilots. Each Connector is in turn connected and exchanges data with the corresponding Connector (DR or DT) of the Playground or other partners.
At this stage, all DE4A participants are expected to follow the set-up A, while only Romania is expected to follow set-up B.
Domains and types of participant IDs
DE4A domains
In DE4A, there are two types of participants:
- Imaginary participants: intended to query the examples stored in the Mocked DO.
- Real participants: intended to retrieve data directly returned by partners.
At the same time, for the real participants, there are also two “domains”:
- Test domain: only fake data is used for test purposes. It is the domain related to the DE4A Playground, where participants return datasets from test sources.
- Pilot domain: real data from real citizens and companies is supposed to be used. It is the environment used for the running phase of the pilots, where participants access to their real registries and return real evidence from them.
Finally, the project is divided into two iterations where each of them needs a copy of those two domains, and where some overlap between them occurs.
As the DE4A project uses the dynamic discovery of eDelivery, where there cannot be duplicate participant IDs targeting to different Connectors (depending on the domain concerned), we need to define a different participant ID schema per each domain:
- PRE1a: Imaginary participants stored in the Mocked DO for iteration 1 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
- Scheme identifier used: “9999”.
- Suffix used: “-it1”.
- E.g. iso6523-actorid-upis::9999:ess2833002e-it1
- PRE1b: Simulated data returned by the real participants used for testing in Playground iteration 1. The related evidence is located in each partner’s infrastructure, within their test domain.
- Scheme identifier used: “99XX”, where “XX” depends on the identifier each participant is using.
- Suffix used: “-it1”.
- E.g. iso6523-actorid-upis::9920:ess2833002e-it1
- PRO1: Real data returned by the real participants during the execution of phase 1 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
- Scheme identifier used: “99XX”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
- Suffix used: none, since there is no overlap between phases 1 and 2 of the pilots.
- E.g. iso6523-actorid-upis::9920:ess2833002e
- PRE2a: Imaginary participants stored in the Mocked DO for iteration 2 for testing. The related evidence is stored in the Mocked DO deployed in SGAD (ES).
- Scheme identifier used: “9999”.
- Suffix used: “-mock-it2”.
- E.g. iso6523-actorid-upis::9999:ess2833002e-mock-it2
- PRE2b: Simulated data returned by the real participants used for testing in Playground iteration 2. The related evidence is located in each partner’s infrastructure, within their test domain.
- Scheme identifier used: “99XX”, where “XX” depends on the identifier each participant is using.
- Suffix used: “-test-it2”.
- E.g. iso6523-actorid-upis::9920:ess2833002e-test-it2
- PRO2: Real data returned by the real participants during the execution of phase 2 of the pilot. The related evidence is located in each partner’s infrastructure, within their pilot domain.
- Scheme identifier used: “99XX”, where “XX” depends on the identifier each participant is using. It is the “real” participant ID.
- Suffix used: none, since there is no overlap between phases 1 and 2 of the pilots.
- E.g. iso6523-actorid-upis::9920:ess2833002e
Therefore, DE4A domains are differentiated by the participant ID schema used.
Location of the participant IDs
These different participant IDs must be stored in their corresponding IDKs and SMPs and configured to return the proper information:
- PRE1a: Imaginary participants
- IDK: none (for these participants, the mocked DE knows which the imaginary participants are and which DO to query, namely, the mocked DO of the first iteration).
- SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT1.
- PRE1b: Simulated data from real participants
- IDK: mocked IDK of the Playground IT1.
- SMP: shared SMP of the Playground IT1. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
- PRO1: Real data from real participants
- IDK: mocked IDK of the pilot running environment.
- SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
- For the first pilot running phase, partners who have not yet deployed their own SMPs will be able to use a shared SMP provided by one of the partners with an available SMP. In such cases, the routing information of those partners will be stored in this shared SMP.
- PRE2a: Imaginary participants
- IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
- SMP: shared SMP of the Playground IT2. It returns the routing information of the targeted Connector (DR/DT) of the Playground IT2.
- PRE2b: Simulated data from real participants
- IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
- SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.
- PRO2: Real data from real participants
- IDK: Central IAL. Its information is automatically updated and fed from the SMPs connected to it.
- SMP: national SMP of the requested participant. It returns the routing information of the targeted Connector (DR/DT) of the requested participant.