Useful information on pilots and participants - Revision history

Javier.ferrero: Chapter "DE4A infrastructure IT2" removed

2023-03-22T10:50:38Z

Chapter "DE4A infrastructure IT2" removed

Mpttfp eduardo.moreno: /* Domains and types of participant IDs */

2023-03-10T12:05:47Z

Domains and types of participant IDs

Ama tiago.catarino: /* DE4A Connector in Member States */ Changes of IP address SMP + Connector PT

2023-03-09T14:41:51Z

DE4A Connector in Member States: Changes of IP address SMP + Connector PT

Alberto.crespo: /* DE4A pilot participants IT2 */ Added DO Role to AMA in UC1.2

2023-01-23T07:14:14Z

DE4A pilot participants IT2: Added DO Role to AMA in UC1.2

Alberto.crespo: /* DE4A pilot participants IT2 */ Updated NL and RO in UC2.2

2023-01-23T06:55:48Z

DE4A pilot participants IT2: Updated NL and RO in UC2.2

Alberto.crespo: /* DE4A pilot participants IT2 */ Updated roles of AT and NL in UC2.1 removing DE role

2023-01-23T06:44:04Z

DE4A pilot participants IT2: Updated roles of AT and NL in UC2.1 removing DE role

Alberto.crespo: /* DE4A pilot participants IT2 */ Updates to CTIE (DO role TBC in UC3.1, SI-MPA is only DT in UC3.1-3.2

2023-01-23T06:32:31Z

DE4A pilot participants IT2: Updates to CTIE (DO role TBC in UC3.1, SI-MPA is only DT in UC3.1-3.2

Alberto.crespo: Added role for MoAI in UC3.1

2023-01-23T06:28:22Z

Added role for MoAI in UC3.1

Fredrik.linden at 08:41, 7 December 2022

2022-12-07T08:41:32Z

Javier.ferrero: /* SMP in Member States */

2022-11-30T15:08:49Z

SMP in Member States

← Older revision		Revision as of 10:50, 22 March 2023
Line 1,429:		Line 1,429:

	\|}		\|}
−
−	~~==DE4A infrastructure IT2==~~
−	~~===Playground infrastructure IT2===~~
−	The following diagram depicts the Playground infrastructure for the second iteration, with the deployment of its corresponding components.[[File:DE4A network IT2-Playground IT2.drawio.png\|frame\|alt=\|none]]
−
−	~~===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.[[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]]~~

← Older revision		Revision as of 12:05, 10 March 2023
Line 1,441:		Line 1,441:

	[[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]]
−
−
−
−
−
−
−
−
−
−
−	~~== 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.~~
−	~~[[File:Domain overlap.png\|none\|thumb\|910x910px]]~~
−	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::99'''99''':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::99'''20''':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::99'''20''':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::99'''99''':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::99'''20''':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::99'''20''':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.

@@ Line 86: / Line 86: @@
 |Portugal
 |AMA
+|Deployed & Configured: v0.3.3 (Pre-Prod environment)
 |-
 |'''RO'''
@@ Line 474: / Line 474: @@
 |PT
 |AMA
-|[https://pprsmp.iap.gov.pt/ https://pprsmp.iap.gov.pt/smp.iap.gov.pt]
+|https://pprsmp.iap.gov.pt/
+|
 |-
@@ Line 809: / Line 809: @@
 |AMA-IP
+|
-|http://130.61.108.235/de4a-connector-it2/
+|https://pprde4a.iap.gov.pt/
 |-
 |ORNC

@@ Line 297: / Line 297: @@
 |DR
 DO,DT
-|DT
+|DO, DT
+|
+|

@@ Line 273: / Line 273: @@
+|
+|
-|DE,DR
+|
+|
@@ Line 286: / Line 286: @@
+|
 |DO,DT
-|DO,DT
+|DE,DR
+|
+|
@@ Line 343: / Line 343: @@
 DO,DT
-|DE,DR
+|DO,DT
+|
+|

@@ Line 198: / Line 198: @@
+|
+|
-|DE
+|DO
 |DE
@@ Line 273: / Line 272: @@
+|
+|
-|DE,DR
 |DE,DR
+|

@@ Line 261: / Line 261: @@
+|
 |DE,DR
-DO,DT
+DO (TBC),DT
 |DE,DR
 DO,DT
@@ Line 402: / Line 402: @@
+|
+|
-|DR
+|DT
-DT
+|DT
+|
 |-

@@ Line 330: / Line 330: @@
+|
+|
+|DE, DR
+|
+|

@@ Line 96: / Line 96: @@
 |Romania
 |MoAI
+|Deployed v 2.0.6 Phoss
 |-
 |'''SU'''
@@ Line 325: / Line 325: @@
 |RO
 |iso6523-actorid-upis::9991:ro000000005
+|
+|
@@ Line 330: / Line 332: @@
+|
+|
+|
 |-
@@ Line 547: / Line 543: @@
 Birth Evidence
 Marriage Evidence
+|https://hub.mai.gov.ro/
 |-
 |ORNC

@@ Line 18: / Line 18: @@
 | Spain
 |SGAD
-| Deployed and configured: phoss SMP v5.6.2, Telesec Certificates
+| Deployed and configured: phoss SMP v5.6.2, CommisSign2 Certificates
 |-
 |'''LU'''
@@ Line 71: / Line 71: @@
 |Spain
 |SGAD
-|Deployed & configured: v0.3.1
+|Deployed & configured: v0.3.1, CommisSign2 Certificates
 |-
 |'''LU'''