1. Interoperability Common Identity Repository
European Commission – Directorate-General Migration & Home Affairs
Unit B3 – Information Systems for Borders and Security 1

2. sBMS (without templates)
ESP
MID
ID info
ID info
ID info
ID info
ID info
Interpol
Europol
SIS
EES
ETIAS
VIS
Eurodac
ECRIS-TCN
sBMS (without templates)
S&D proposal

4. Programmable Matching
Storage & processing of biometrics in our current systems
SIS
VIS
Eurodac
server/db
SIS images
VIS images
SIS-AFIS
BMS
Programmable Matching
Accelerators
Templates only!
A biometric search or verification takes place here!
BMS & SIS-AFIS are Morpho systems (now Idemia)
Eurodac PMA are from Cogent (->3M->Gemalto)
SIS, VIS and Eurodac server are STERIA/HP systems

5. Apple Touch ID example Secure Enclave
The chip in your device includes an advanced security architecture called the Secure Enclave, which was developed to protect your passcode and fingerprint data. Touch ID doesn't store any images of your fingerprint, and instead relies only on a mathematical representation. It isn't possible for someone to reverse engineer your actual fingerprint image from this stored data.

6. ESP MID ID info ID info ID info ID info ID info ID info Interpol
Data Indexer
Data Indexer
Data Indexer
Data Indexer
Data Indexer
Data Indexer
ID info
ID info
ID info
ID info
ID info
ID info
Interpol
Europol
SIS
EES
ETIAS
VIS
Eurodac
ECRIS-TCN
Biometric images
Biometric images
Biometric images
Biometric images
Biometric images
sBMS (templates only)
S&D proposal
(modified)
The ‘data indexer’ - more commonly known as ‘search engine’ - is the data processor component of a database allowing to search data contained in the database.
This indexer/engine needs to be closely coupled with the database holding the data to prevent inconsistencies.

7. ESP MID ID info ID info ID info ID info ID info ID info Interpol
Oracle Full-Text
QWANT
CONDUIT
ELISE
YANDEX
BING
ID info
ID info
ID info
ID info
ID info
ID info
Interpol
Europol
SIS
EES
ETIAS
VIS
Eurodac
ECRIS-TCN
Biometric images
Biometric images
Biometric images
Biometric images
Biometric images
sBMS (templates only)
S&D proposal
(modified)
Each company (or consortium) has specific experience with a limited number of engines (or often only one). Public procurement often leads to different engines (VIS and SIS are already different; EES and ETIAS will probably be built by different companies; same for Eurodac and ECRIS-TCN).
They form the most expensive part of a system.
Each system has different requirements, different response times, different availabilities, different possibilities, different accuracies, etc.

8. ESP MID ID info ID info ID info ID info ID info ID info Interpol
QWANT
CONDUIT
ELISE
YANDEX
BING
Oracle Full-Text
ID info
ID info
ID info
ID info
ID info
ID info
Interpol
Europol
SIS
EES
ETIAS
VIS
Eurodac
ECRIS-TCN
Biometric images
Biometric images
Biometric images
Biometric images
Biometric images
sBMS (templates only)
S&D proposal
(modified)
For the use of an ESP, this concept will work ok but requires adaptations on each individual system (harmonisation of response times and availability)
For Article 20 (police identification), this concept will work but requires adaptations on each individual system (new transaction, logfile, limit data in response)
For Article 22 (law-enforcement first search), this concept will lead to errors, mismatches, inconsistencies. It also requires adaptations on each individual system (new transaction, logfile, limit data in response, harmonisation of response times/availability/functionality)
For the Multiple-Identity Detector, this concept of different indexers/engines will not work

9. MID needs a CIR indexer/engine MID ID info ID info ID info ID info
Data Indexer/Engine
Oracle Full-Text
QWANT
CONDUIT
ELISE
YANDEX
BING
ID info
ID info
ID info
ID info
ID info
ID info
SIS
EES
ETIAS
VIS
Eurodac
ECRIS-TCN
Biometric images
Biometric images
Biometric images
Biometric images
Biometric images
sBMS (templates only)
The MID must rely on one single indexer/engine with the exact same behaviour for all biographic identity data; this will minimise errors, mismatches and inconsistencies
It will have the same response time, the same availability for all biographic data
This single indexer will be cheaper than five full-blown different solutions
It will facilitate the work of eu-LISA
All improvements, corrections will be done on one engine, positively affecting the quality of all data
It will process biographical identity data in the exact same way, regardless of the person

10. MID needs a CIR MID ID info ID info EES ETIAS VIS Eurodac ECRIS-TCN
Police
Identification
MID
Data Indexer/Engine
Law Enforcement
1st step
ID info
Biometric images
access
log
ID info
Oracle Full-Text
EES
ETIAS
VIS
Eurodac
ECRIS-TCN
ID info
SIS
Biometric images
Biometric images
sBMS (templates only)
The storage of biographical identity data should follow the exact same structure, format, content, transliteration rules. Using the CIR as a new component will simplify eu-LISA’s work while working with one contractor doing this work
The “ID info” is ‘removed’ from the systems and ‘moved’ to the CIR
The storage of the identity data in the CIR will improve coherence & consistency and reduce errors for links in the MID as these links only concern two data sources (CIR & SIS)
Storage of identity data in the CIR is required to support the new functionality of police identifications and the law enforcement first step; by design, it limits available data to identity data or a simple hit/no-hit
In accordance with Article 21, if a possible link is detected, the authority is ONLY given access to the identity data in the CIR, nothing else.
The specific access log of the CIR greatly facilitates auditing the use of the CIR for purposes of MID, police identifications, law enforcement first step, etc.
Biometric images will be moved into the CIR for coherence with the biographical identity data and to support the new Art.20/22 functionalities by design. All sBMS transactions are then also logged by the CIR access log (except SIS)

11. Common Identity Repository for TCNs
What data is stored where?
(some examples)
Common Identity Repository for TCNs
Frank SMITH M
16/06/1946
USA
Frank SMITH M
16/06/1946
USA
Lea Tolstoy M
08/10/1952
RUS
EES
ETIAS
VIS
Entry Rome, IT 23/05/2018
Exit Palermo, IT 27/05/2017
Entry Warsaw, PL 05/07/2017
Exit Hamburg, DE 08/07/2017
Born in New York (US)
Address Washington
Professional visit
No major diseases
Sufficient funds
Health insurance: xyz
Born in Tula (RU)
Address Moscow Tourism visit
No invitation
Sufficient funds
Port of first entry: Berlin, DE
Multiple-Entry visa
Shared BMS

12. SIS data complex/costly to put in CIR
MID
Data Indexer/Engine
ID info
N-SIS
Oracle Full-Text
EES
ETIAS
VIS
Eurodac
ECRIS-TCN
ID info
SIS
Biometric images
sBMS (templates only)
The ideal situation would have been to put the SIS identity data of ‘person-alerts’ also in the CIR
The various national copies (full, partial, technical, with/without biometrics) would render this very complex (if not impossible) and very costly as all copies would need modifications 12