KTDi

KTDI Pilot
Data Flows
(NLD)
r
- A
5* 4-

/

3

I
i

3

\

\

ï
ri

' L*.
F

i
I

w

1

-. -=2 ■

‘A

N

-egs

e-

*

Xhtü

$-

* h

«

=

W

—

e
m=

sae

Faë

TDi

KTDI Profile

KDTI

Presentation title

KTDI Profile
n

[
Trwvel Derunet

Bmsetonica09esa I
201
00z)
2002-10woei
G ,002)

I

Live Facial image

Saxca UUD

Language of Preference
Bmnod on uou saz
intanaaond hazasung

NOID UUID

Core 88ƒ

Standerds

b

Tavd Dogunvore - Dogumare Twe

d

CortactDeata

Street Number

Decumtert Courtry et bsuante

♦ Q Q

Country of Issuance of Document
Thael Domes Om

Postcode

Town

Dsoueu Nnbe

Region

Document Number
Tievel Daruet

MamaAddrena

Street Name

Type of Document
Travel Doguter

Note
• On the next slides,
references will be made to
the Building Blocks of the
KTDI Profile.

Larguag

Country

Note
• Minor (cosmetic) updates to some Core
Building Blocks (previously: ‘Travel
Document - Holder Data - <data
element>’ changed to ‘Travel
Document - Holder - <data element’ in
order to align with other Core Building
Blocks.
• Changed
‘Boarding
Pass’ according to discussion with KLM
and Schiphol.

Decamet Enphy Dat

Cortact DarnM Phana Wrwake)

Expiry Date ot Document

Phone Number
5.1.2.E

Given Names of Holder

Comtact Dot-lc E

5.1.2.E

E-mail Address

Traval Doduent Moder Sarane

Surname of Halder
Trmal Documart Matdor Nahanat,

Name of Programme

Nationaity of Holder

Level
Trmel Documert Makdor DOB

BaedoniATa

OaC oseDsartrgl anano

Date ot Birth of Holder

Number

Beardng Tohun

Traval Decutart icdar Sa

Boarding Tüken

Sex of Holder
TrenelDocumer

Hete Fi

Facial Image of Holder

!

[

k'

Comparry Name

Department Name

SchanganEry Dadara

Duration of Stay
Purpose of Stay

Expianation

Means of Stay
Buskew Ponla asses
PO, BOX

B»wn Wslng Mi»aai

Street Name

Streel Number

Street Number

Postcode

Postcode

KTDICENEHIC4 KTDI Preha Laca Srutura

Town

Region

Region

Country

Country

5.1.2.E

Streel Name
-Dua aadng lua Te-

Toum

Mlandalory Dala Building
Ekck

•ata Elements Provided tof by Traveller

«Data Elements Prowvided tof Dy Gov.>

- Care Data

Street Number

Postcode
Town

■Om Padng @aok Tim-

cData Elements Proided tof Dy Traveller

Non-Gore Data Euildimg
Stock

_J

Region

Country

Data

Elements

KTDI

Data Flows NLD
CAN

KDTI

Presentation title

KTDI Pilot Process - Departure NLD

First time

O

Oo

KTDI

Book
flight

Invite
traveller

Create
KTDI profile

AT
nTn
177

H

o

:
o

Create
Digital ID

Check-in

Prepare
the trip

Drop-off
bag

Priority access
security

Border
control

KLM
Lounge

Boarding
Access

Departure

Boarding
Access

Departure

Second time or more

©
o

Book
flight

In scope

Qo

a :

Invite
traveller

Check-in

Out of scope

o
o

Prepare
the trip

Drop-off
bag

Priority access
security

Border
control

KLM
Lounge

KTDI Pilot - Data Flow ‘Invite Traveller’
O

Output

Input

Oo
Invite
traveller

KTDI

4

□
o

KTDI Pilot - Data Flow “Create KTDI Profile’
o,

Input - Mandatory*

Input - Optionali*

Username

Contact Details - Home Address

Password

Contact Details - Phone (Private)

Biometric Token (Face,
Fingerprint > if supported by
Travellers’device)

Contact Details - E-mail (Private)

Business - Base

Q

Output

KTDI
Loyalty Programme

KTDI

✓

<None>

Create
KTDI profile

Business - Postal Address
Business - Visiting Address

) Traveller manually enters this Building Blocks using the KTDI App. Building Blocks are stored persistently in the KTDI Wallet on the Travellers’ mobile device.

KTDI Pilot - Data Flow ‘Create Digital ID’
o,

KTDI

Q

Output
Travel Document - Document - Type
Travel Document - Document - Country of Issuance
Travel Document - Document - Document Number
Travel Document - Document - Expiry Date
Travel Document - Holder- Given Names

Input

Travel Document - Holder - Surname

<ePassport>

Travel Document - Holder - Nationality
Create
Digital ID

Travel Document - Holder - DOB
Travel Document - Holder- Sex
Travel Document - Holder - Fl

) Stored persistently in NOID database as Core Building Blocks.
**') Stored persistently in the KTDI Wallet on the Travellers’ mobile device.
***) Stored persistently in the KTDI Blockchain.

UUID**
Attestation of the Creation of the Digital ID**

Transaction associated with the Attestation ***

KTDI Pilot - Data Flow ‘Create Digital ID’
o,
KTDI Blockchain

NOID

Travel Ier
1

4

2
3

5

->

4

4

4

6

>

7

1. e Passport (manual action).
2. Interna! processing, including storing
in NOlDs' system.
3.QR Code containing DUID.
4. Store UUID in
- Source - UUID' as part of
the KTDI Profile which Is stored in the KTDI Wallet on the Travellers’ mobile device.
5. Attestation of the creation of the Digital ID.
6. Store the Attestation in the KTDI Wallet on the Travellers' mobile device.
7. Transactiën associated with the Attestation.
KTDI UML-3 NLD Create Digital 1D

KTDI

Q

KTDI Pilot - Data Flow ‘Check In’

- Receive ‘Boarding Token’

Output
Boarding Token*

<None>
Check-in

) Pushed by the Airlin e to the KTDI App of the

appropriate Travellen as a response to Check-in.

KTDI Pilot - Data Flow ‘Check In’ - Receive ‘Boarding Token’
KLM

Traveller
1

4

2

3

>

(1. Check-in.)
2. Intern ai processing.
3. 5.1.2.E arding Token.

KTDI UML-5 NLD Data Flow Check-in

KTDI Pilot - Data Flow ‘Prepare the Trip’ - Request Service ‘Priority
Access to Security’
O
KTDI

Input

Output

Travel Document - Holder- Fl

o

Prepare
the trip

) Retrieved real-time from NOID. Each Core

is encapsulated in a Verifiable Claim.

<None>

KTDI Pilot - Data Flow ‘Prepare the Trip’ - Request Service ‘Cross
NLD Border - Departure'
O
□
KTDI

Input: Core Building Blocks*

Travel Document - Document - Type
Travel Document - Document - Country of Issuance
Travel Document - Document - Document Number
Travel Document - Document - Expiry Date
Output

Travel Document - Holder- Given Names
o

Travel Document - Holder - Surname
Travel Document - Holder - Nationality

Prepare
the trip

Travel Document - Holder - DOB
Travel Document - Holder - Sex
Travel Document - Holder - Fl

) Retrieved real-time from NOID. Each Core

is encapsulated in a Verifiable Claim.

<None>

KTDI Pilot - Data Flow ‘Prepare the Trip’ - Request Service ‘Boarding’
&

Input*
Output

Boarding Pass-Token*
O

Travel Document - Holder- Fl**
Prepare
the trip

*‛

) Pushed by the Airline as a response to Check-in.
**) Retrieved real-time from NOID. This Core

is encapsulated in a Verifiable Claim.

<None>

KTDI

1^^

KTDI Pilot - Data Flow ‘Prepare the Trip’ - Request Service ‘Cross
CAN Border - Arrival’
O
□
KTDI

Input
Travel Document - Document - Type
Travel Document - Document - Country of Issuance
Travel Document - Document - Document Number'
Travel Document - Document - Expiry Date
Output

Travel Document - Holder-Given Names
o

Travel Document - Holder-Surname
Travel Document - Holder - Nationality

Prepare
the trip

Travel Document - Holder - DOB
Travel Document - Holder - Sex
Travel Document - Holder - Fl

) Retrieved real-time from NOID. Each Core

is encapsulated in a Verifiable Claim.

<None>

KTDI Pilot - Data Flow ‘Prepare the Trip’ (Dep).
O
NOID

KMar

KLM

41

2

4

AAS

Traveller

3
4

->
5

6

7

*

&

1. Log-in (biometrics or alternatively username/password).
2. UUID and Live Facial Image.
(3. Interna! processing).
4. All Core Building Blocks.
5. Gore
- Holder- Fl'(and <?)
6. All Core Building Blocks.
7. Boarding Token (already received from Airline after Check-in) & Core
8. All Core Building Blocks.
KTDI UML-6 NLD Data Flow Prepare the Trip Departure NLD

- Holder - Fl'.

KTDI

CBSA

Q

KTDI Pilot - Data Flow ‘Priority Access to Security’
O

Input

Output

Live Facial Image

<None>

Priority access
security

) Captured real-time by Seamless Flow Security Access Touchpoint

KTDI

KTDI Pilot - Data Flow ‘Priority Access to Security’
O
AAS (using SF)

Traveller
1

4

2
3

->

1. Live Facial Image.
2. Interna! processing, including matching
with Care
Travellers’ eligibility to access the security restricted areas.
3. Acknowledge eligibility to access the security restricted areas.

KTDI UML-8 NLD Data Flow Priority Access to Security

- Holder - Fl’ and determining the

KTDI

□

KTDI Pilot - Data Flow ‘Border Control - Departure NLD’
Og

4

□
o

Output
Input
Attestation of the Border Crossing**

Live Facial Image*
Transaction associated with the Attestation***
Border
control

k)

) Captured real-time by Seamless Flow Border Control Touchpoint
) Stored persistently in the KTDI Wallet on the Travellers' mobile device.
***) Stored persistently in the KTDI Blockchain.
**)

KTDI Pilot - Data Flow ‘Border Control - Departure NLD’
O
KTDI Blockchain

KMar (using SF)

KMar

KTDI

Traveller
1

4

2

3

4

4

5

->
6

4

7

8

1. Live Facial Image.
2. Interna! processing, including mate hing
with Gore
Control Token>.
3. <Border Control Token».
(4. Intern al processing.)
5. Acknowledge eligibility to cross border (CAN Traveller needs exit stamp!).
6. Attestation of border Crossing.
7. Store the Attestation in the KTDI Wallet on the Trave He rs' mobile device.
8. Transaction associated with the Attestation.

KTDI UML-9 NLD Data Flow Border Control - Departure NLD

- Holder - FT and retrieving cBorder

□

O

KTDI Pilot - Data Flow ‘Boarding Access’
Oo

KTDI
E

□
o

Output

Input

Attestation of Traveller having boarded the plane**

Live Facial Image*
Transaction associated to the Attestation***

Boarding
Access

) Captured real-time by Seamless Flow Boarding Touchpoint
) Stored persistently in the KTDI Wallet on the Travellers’ mobile device.
***) Stored persistently in the KTDI Blockchain.
k*

KTDI Pilot - Data Flow Boarding Access’
KLM (using DCS)

KTDI Blockchain

KLM (using SF)

Oo

Travel Ier

1

4

3

4

2

4
5

->

6

4

7

8

1. Live Facial Image.
2. Intern al processing, including mate hing
with Gore
Block 'Boarding Pass - loken'.
3. Boarding Token.
(4. Interna! processing.)
5. Acknowledge eligibility te board.
6. Attestation of boarding.
7. Store the Attestation in the KTDI Wallet on the Travellers’ mobile device.
8. Transact!on associaled with the Attestation.

KTDI UML-11 NLD Dala Flow Boarding Access

- Holder - Fl' and retrieving Building

KTDI

□

KTDI

Data Flows CAN
NLD

KDTI

Presentation title

KTDI Pilot Process - Arrival NLD

KDTI

Oo

o

Invite
passenger

Prepare
the trip

RTP
NL
Arrival
flight

RTP_NL
Registration

Presentation title

Border
control

KTDI Pilot - Data Flow ‘Prepare the Trip’ - Request Service ‘RTP-NL
Application’
[

Input:*

Travel Document - Document-Type**
Travel Document - Document - Country of Issuance**
Travel Document - Document - Document Number**
Travel Document - Document - Expiry Date**
Output

Travel Document - Holder - Given Names**

o
Travel Document - Holder - Surname**
Travel Document - Holder - Nationality**
Travel Document - Holder - DOB**

Schengen Entry Declaration***
Contact Details - E-mail (Private)***

*) Only applicable for Canadian 'First Timer' who not already is RTP-NL member.
**) Each Core
is encapsulated in a Verifiable Claim.
***) Canadian Traveller manually fills in this
Block.

KDTI

Presentation title

Prepare
the trip

<None>

RTP
NL

KTDI Pilot - Data Flow ‘Prepare the Trip’ - Request Service ‘Cross
NLD Border-Arrival’
[

Input: Core Building Blocks*

Travel Document - Document-Type
Travel Document - Document - Country of Issuance
Travel Document - Document - Document Number
Travel Document - Document - Expiry Date
Output

Travel Document - Holder - Given Names

o
Travel Document - Holder - Surname
Travel Document - Holder - Nationality
Travel Document - Holder - DOB
Travel Document - Holder - Sex
Travel Document - Holder - Fl

*) Each Core
is encapsulated in a Verifiable Claim.
In case of NLD Traveller: Core Building Blocks are retrieved real-time from NOID.

KDTI

Presentation title

Prepare
the trip

<None>

RTP
NL

KTDI Pilot - Data Flow ‘Prepare the Trip’ (Arr)
[
NOID

NLD Traveller

41

2

4

CAN Traveller
(second timer)

KMar

3
4

>
5
6
7

8

1. Log-in (biometrics or alternatively username/password).
2. UUID and Live Facial Image.
(3. Internal processing).
4. AH Core Building Blocks.
5. AH Core Building Blocks (necessary for Service 'Cross NLD Border - Arrival).
6. AH Core Building Blocks (necessary for Service 'Cross NLD Border - Arrival).
7. Building Blocks (necessary for Service ’ RTP-NL Application").
8. AH Core Building Blocks (necessary for Service 'Cross NLD Border - Arrival).
KTDI UML-6 NLD Data Flow Prepare the Trip Arrival NLD

KDTI

Presentation title

CAN Traveller
(first timer)

RTP
NL

KTDI Pilot- Data Flow ‘Arrival Flight’

Q

Input:

Output

Notification informing Traveller where to proceed to upon
arrival at Schiphol Airport.*

<None>

Arrival
flight

*) Possible notifications:
1. Go to Seamless Flow Border Control Touchpoint.
2. Go to RTP-NL desk in order to finalize RPT-NL membership (CAN first timer only).

KDTI

Presentation title

RTP
NL

KTDI Pilot- Data Flow ‘Arrival Flight’
Q
KMar (using SF)

4

Travel Ier

1
2

1. Intern ai processing: determine next touchpoint of Travel Ier:
- NLD Travel Ier: SF Border Contrei Touchpoint.
- CAN first timer: RTP-NL desk.
- CAN second timer. SF Border Contrei Touchpoint.
2.Send notification lo Travellen

KTDI UML-<X> NLD Data Flow Arrival Flight- Arrival NLD

KDTI

Presentation title

RTP
NL

KTDI Pilot - Data Flow ‘Border Control - Finalize RTP-NL Application’

0

Output
Input

E-passport

RTP
CNL
RTP_NL
Registration

*) Stored persistently in the KTDI Wallet on the Travellers' mobile device.
**) Stored persistently in the KTDI Blockchain.

KDTI

Presentation title

Attestation of RTP-NL membership*

Transaction associated with the Attestation**

KTDI Pilot - Data Flow ‘Border Control - Finalize RTP-NL Application 7

0
KTDI Blockchain

Traveller

KMar (using SF)
1

4

2
3

4

4

5

1.. E-passport.
(2.lnternal processing.)
3. Attestation of active RTP-NL membership.
4. Store the Attestation in the KTDI Wallet on the Travellers' mobile device.
5. Transaction associated with the Attestation.

KTDI UML-«X> NLD Data Flow Finalize RTP-NL Application - Arrival NLD

KDTI

Presentation title

KTDI Pilot - Data Flow ‘Border Control - Arrival NLD’

Q

Output
Input

Attestation of the Border Crossing**
Live Facial Image*

Transaction associated with the Attestation***

Border
control

*) Captured real-time by Seamless Flow Border Control Touchpoint
**) Stored persistently in the KTDI Wallet on the Travellers' mobile device.
***) Stored persistently in the KTDI Blockchain.

KDTI

Presentation title

RTP
NL

KTDI Pilot - Data Flow ‘Border Control - Arrival NLD 7

Q
KTDI Blockchain

KMar

Traveller

KMar (using SF)
1

4

2

3

4

4
5

>
6

4

7

8

1. Live Facial Image.
2. Interna! processing, including matching
with Core
membesrchip (CAN Traveller only) and retrieving <Border Control T
3. <Border Control Token>.
(4. Internal processing.)
5. Acknowledge eligibility to cross border (CAN Traveller needs entry stamp!).
6. Attestation of border Crossing.
7. Store the Attestation in the KTDI Wallet on the Travellers' mobile device.
8. Transaction associated with the Attestation.
KTDI UML-9 NLD Data Flow Border Control - Arrival NLD

KDTI

Presentation title

- Holder - Fl', checking RTP-NL

RTP
NL