COUNCIL DECISION
2008/616/JHA
of 23 June 2008
on the implementation of Decision 2008/615/JHA on the stepping up of cross-border cooperation, particularly in combating terrorism and cross-border crime
CHAPTER I
GENERAL
Article 1
Aim
Article 2
Definitions
CHAPTER 2
COMMON PROVISIONS FOR DATA EXCHANGE
Article 3
Technical specifications
Article 4
Communications network
Article 5
Availability of automated data exchange
Article 6
Reference numbers for DNA data and dactyloscopic data
CHAPTER 3
DNA DATA
Article 7
Principles of DNA data exchange
Article 8
Rules for requests and answers in connection with DNA data
Article 9
Transmission procedure for automated searching of unidentified DNA profiles in accordance with Article 3 of Decision 2008/615/JHA
Article 10
Transmission procedure for automated search of reference DNA profiles in accordance with Article 3 of Decision 2008/615/JHA
Article 11
Transmission procedure for automated comparison of unidentified DNA profiles in accordance with Article 4 of Decision 2008/615/JHA
CHAPTER 4
DACTYLOSCOPIC DATA
Article 12
Principles for the exchange of dactyloscopic data
Article 13
Search capacities for dactyloscopic data
Article 14
Rules for requests and answers in connection with dactyloscopic data
CHAPTER 5
VEHICLE REGISTRATION DATA
Article 15
Principles of automated searching of vehicle registration data
Article 16
Costs
CHAPTER 6
POLICE COOPERATION
Article 17
Joint patrols and other joint operations
CHAPTER 7
FINAL PROVISIONS
Article 18
Annex and Manual
Article 19
Independent data protection authorities
Article 20
Preparation of decisions as referred to in Article 25(2) of Decision 2008/615/JHA
Article 21
Evaluation of the data exchange
Article 22
Relationship with the Implementing Agreement of the Prüm Treaty
Article 23
Implementation
Article 24
Application
ANNEX
CHAPTER 1:
Exchange of DNA-Data
1. DNA related forensic issues, matching rules and algorithms
1.1. Properties of DNA-profiles
VWA |
TH01 |
D21S11 |
FGA |
D8S1179 |
D3S1358 |
D18S51 |
Amelogenin |
TPOX |
CSF1P0 |
D13S317 |
D7S820 |
D5S818 |
D16S539 |
D2S1338 |
D19S433 |
Penta D |
Penta E |
FES |
F13A1 |
F13B |
SE33 |
CD4 |
GABA |
1.2. Matching rules
1.3. Reporting rules
2. Member State code number table
Member State names |
Code |
Member State names |
Code |
Belgium |
BE |
Luxembourg |
LU |
Bulgaria |
BG |
Hungary |
HU |
Czech Republic |
CZ |
Malta |
MT |
Denmark |
DK |
Netherlands |
NL |
Germany |
DE |
Austria |
AT |
Estonia |
EE |
Poland |
PL |
Greece |
EL |
Portugal |
PT |
Spain |
ES |
Romania |
RO |
France |
FR |
Slovakia |
SK |
Ireland |
IE |
Slovenia |
SI |
Italy |
IT |
Finland |
FI |
Cyprus |
CY |
Sweden |
SE |
Latvia |
LV |
United Kingdom |
UK |
Lithuania |
LT |
|
|
3. Functional analysis
3.1. Availability of the system
3.2. Second step
4. DNA interface control document
4.1. Introduction
4.1.1.
Objectives
4.1.2.
Scope
4.1.3.
XML structure and principles
4.2. XML structure definition
4.2.1.
Schema PRUEMDNAx
Fields |
Type |
Description |
header |
PRUEM_header |
Occurs: 1 |
datas |
PRUEM_datas |
Occurs: 1 … 500 |
4.2.2.
Content of header structure
Fields |
Type |
Description |
direction |
PRUEM_header_dir |
Direction of message flow |
ref |
String |
Reference of the XML file |
generator |
String |
Generator of XML file |
schema_version |
String |
Version number of schema to use |
requesting |
PRUEM_header_info |
Requesting Member State info |
requested |
PRUEM_header_info |
Requested Member State info |
Value |
Description |
R |
Request |
A |
Answer |
Fields |
Type |
Description |
source_isocode |
String |
ISO 3166-2 code of the requesting Member State |
destination_isocode |
String |
ISO 3166-2 code of the requested Member State |
request_id |
String |
unique Identifier for a request |
date |
Date |
Date of creation of message |
time |
Time |
Time of creation of message |
4.2.3.
Content of PRUEM Profile data
Fields |
Type |
Description |
reqtype |
PRUEM request type |
Type of request (Article 3 or 4) |
date |
Date |
Date profile stored |
type |
PRUEM_datas_type |
Type of profile |
result |
PRUEM_datas_result |
Result of request |
agency |
String |
Name of corresponding unit responsible for the profile |
profile_ident |
String |
Unique Member State profile ID |
message |
String |
Error Message, if result = E |
profile |
IPSG_DNA_profile |
If direction = A (Answer) AND result ≠ H (Hit) empty |
match_id |
String |
In case of a HIT PROFILE_ID of the requesting profile |
quality |
PRUEM_hitquality_type |
Quality of Hit |
hitcount |
Integer |
Count of matched Alleles |
rescount |
Integer |
Count of matched profiles. If direction = R (Request), then empty. If quality!=0 (the original requested profile), then empty. |
Value |
Description |
3 |
Requests pursuant to Article 3 of Decision 2008/615/JHA |
4 |
Requests pursuant to Article 4 of Decision 2008/615/JHA |
Value |
Description |
0 |
Referring original requesting profile: Case ‘No Hit’: original requesting profile sent back only; Case ‘Hit’: original requesting profile and matched profiles sent back. |
1 |
Equal in all available alleles without wildcards |
2 |
Equal in all available alleles with wildcards |
3 |
Hit with Deviation (Microvariant) |
4 |
Hit with mismatch |
Value |
Description |
P |
Person profile |
S |
Stain |
Value |
Description |
U |
Undefined, If direction = R (request) |
H |
Hit |
N |
No Hit |
E |
Error |
Fields |
Type |
Description |
ess_issol |
IPSG_DNA_ISSOL |
Group of loci corresponding to the ISSOL (standard group of Loci of Interpol) |
additional_loci |
IPSG_DNA_additional_loci |
Other loci |
marker |
String |
Method used to generate of DNA |
profile_id |
String |
Unique identifier for DNA profile |
Fields |
Type |
Description |
vwa |
IPSG_DNA_locus |
Locus vwa |
th01 |
IPSG_DNA_locus |
Locus th01 |
d21s11 |
IPSG_DNA_locus |
Locus d21s11 |
fga |
IPSG_DNA_locus |
Locus fga |
d8s1179 |
IPSG_DNA_locus |
Locus d8s1179 |
d3s1358 |
IPSG_DNA_locus |
Locus d3s1358 |
d18s51 |
IPSG_DNA_locus |
Locus d18s51 |
amelogenin |
IPSG_DNA_locus |
Locus amelogin |
Fields |
Type |
Description |
tpox |
IPSG_DNA_locus |
Locus tpox |
csf1po |
IPSG_DNA_locus |
Locus csf1po |
d13s317 |
IPSG_DNA_locus |
Locus d13s317 |
d7s820 |
IPSG_DNA_locus |
Locus d7s820 |
d5s818 |
IPSG_DNA_locus |
Locus d5s818 |
d16s539 |
IPSG_DNA_locus |
Locus d16s539 |
d2s1338 |
IPSG_DNA_locus |
Locus d2s1338 |
d19s433 |
IPSG_DNA_locus |
Locus d19s433 |
penta_d |
IPSG_DNA_locus |
Locus penta_d |
penta_e |
IPSG_DNA_locus |
Locus penta_e |
fes |
IPSG_DNA_locus |
Locus fes |
f13a1 |
IPSG_DNA_locus |
Locus f13a1 |
f13b |
IPSG_DNA_locus |
Locus f13b |
se33 |
IPSG_DNA_locus |
Locus se33 |
cd4 |
IPSG_DNA_locus |
Locus cd4 |
gaba |
IPSG_DNA_locus |
Locus gaba |
Fields |
Type |
Description |
low_allele |
String |
Lowest value of an allele |
high_allele |
String |
Highest value of an allele |
5. Application, security and communication architecture
5.1. Overview
5.2. Upper Level Architecture
Figure 1: Topology of DNA Data Exchange
5.3. Security Standards and Data Protection
5.3.1.
Data Level
5.3.2.
Communication Level
5.3.3.
Transmission Level
5.4. Protocols and Standards to be used for encryption mechanism: s/MIME and related packages
5.5. Application Architecture
Figure 2: Overview Application Topology
5.6. Protocols and Standards to be used for application architecture:
5.6.1.
XML
5.6.2.
ODBC
5.6.3.
JDBC
Figure 3: Overview Application Workflow at each Member State's site
5.7. Communication Environment
5.7.1.
Common Communication Network: TESTA and its follow-up infrastructure
5.7.2.
Security Concern
[Bild bitte in Originalquelle ansehen] |
MPLS is an IETF standard technology that speeds up network traffic flow by avoiding packet analysis by intermediate routers (hops). This is done on the basis of so-called labels that are attached to packet by the edge routers of the backbone, on the basis of information stored in the forwarding information base (FIB). Labels are also used to implement virtual private networks (VPNs). |
5.7.3.
Protocols and Standards to be used over the communication network
5.7.4.
Network Address Assignment
Operative environment
Testing Environment
5.7.5.
Configuration Parameters
MS |
Sub Domains |
Comments |
BE |
dna.pruem.be.eu-admin.net |
Setting up a secure local link to the existing TESTA II access point |
fp.pruem.be.eu-admin.net |
|
|
BG |
dna.pruem.bg.eu-admin.net |
|
fp.pruem.bg.eu-admin.net |
|
|
CZ |
dna.pruem.cz.eu-admin.net |
|
fp.pruem.cz.eu-admin.net |
|
|
DK |
dna.pruem.dk.eu-admin.net |
|
fp.pruem.dk.eu-admin.net |
|
|
DE |
dna.pruem.de.eu-admin.net |
Using the existing TESTA II national access points |
fp.pruem.de.eu-admin.net |
|
|
EE |
dna.pruem.ee.eu-admin.net |
|
fp.pruem.ee.eu-admin.net |
|
|
IE |
dna.pruem.ie.eu-admin.net |
|
fp.pruem.ie.eu-admin.net |
|
|
EL |
dna.pruem.el.eu-admin.net |
|
fp.pruem.el.eu-admin.net |
|
|
ES |
dna.pruem.es.eu-admin.net |
Using the existing TESTA II national access point |
fp.pruem.es.eu-admin.net |
|
|
FR |
dna.pruem.fr.eu-admin.net |
Using the existing TESTA II national access point |
fp.pruem.fr.eu-admin.net |
|
|
IT |
dna.pruem.it.eu-admin.net |
|
fp.pruem.it.eu-admin.net |
|
|
CY |
dna.pruem.cy.eu-admin.net |
|
fp.pruem.cy.eu-admin.net |
|
|
LV |
dna.pruem.lv.eu-admin.net |
|
fp.pruem.lv.eu-admin.net |
|
|
LT |
dna.pruem.lt.eu-admin.net |
|
fp.pruem.lt.eu-admin.net |
|
|
LU |
dna.pruem.lu.eu-admin.net |
Using the existing TESTA II national access point |
fp.pruem.lu.eu-admin.net |
|
|
HU |
dna.pruem.hu.eu-admin.net |
|
fp.pruem.hu.eu-admin.net |
|
|
MT |
dna.pruem.mt.eu-admin.net |
|
fp.pruem.mt.eu-admin.net |
|
|
NL |
dna.pruem.nl.eu-admin.net |
Intending to establish a new TESTA II access point at the NFI |
fp.pruem.nl.eu-admin.net |
|
|
AT |
dna.pruem.at.eu-admin.net |
Using the existing TESTA II national access point |
fp.pruem.at.eu-admin.net |
|
|
PL |
dna.pruem.pl.eu-admin.net |
|
fp.pruem.pl.eu-admin.net |
|
|
PT |
dna.pruem.pt.eu-admin.net |
…… |
fp.pruem.pt.eu-admin.net |
…… |
|
RO |
dna.pruem.ro.eu-admin.net |
|
fp.pruem.ro.eu-admin.net |
|
|
SI |
dna.pruem.si.eu-admin.net |
…… |
fp.pruem.si.eu-admin.net |
…… |
|
SK |
dna.pruem.sk.eu-admin.net |
|
fp.pruem.sk.eu-admin.net |
|
|
FI |
dna.pruem.fi.eu-admin.net |
[To be inserted] |
fp.pruem.fi.eu-admin.net |
|
|
SE |
dna.pruem.se.eu-admin.net |
|
fp.pruem.se.eu-admin.net |
|
|
UK |
dna.pruem.uk.eu-admin.net |
|
fp.pruem.uk.eu-admin.net |
|
CHAPTER 2:
Exchange of dactyloscopic data (interface control document)
1. File Content Overview
Type-1 |
→ |
Transaction information |
Type-2 |
→ |
Alphanumeric persons/case data |
Type-4 |
→ |
High resolution greyscale dactyloscopic images |
Type-9 |
→ |
Minutiæ Record |
Type-13 |
→ |
Variable resolution latent image record |
Type-15 |
→ |
Variable resolution palmprint image record |
1.1. Type-1 — File header
1.2. Type-2 — Descriptive text
1.3. Type-4 — High resolution greyscale image
1.4. Type-9 — Minutiæ record
1.5. Type-13 — Variable-Resolution Latent Image Record
1.6. Variable-Resolution Palmprint Image Record
2. Record format
2.1. Information separators
Code |
Type |
Description |
Hexadecimal Value |
Decimal Value |
US |
Unit Separator |
Separates information items |
1F |
31 |
RS |
Record Separator |
Separates subfields |
1E |
30 |
GS |
Group Separator |
Separates fields |
1D |
29 |
FS |
File Separator |
Separates logical records |
1C |
28 |
2.2. Record layout
3. Type-1 Logical Record: the File Header
3.1. Fields for Type-1 Logical Record
3.1.1.
Field 1.001: Logical Record Length (LEN)
3.1.2.
Field 1.002: Version Number (VER)
3.1.3.
Field 1.003: File Content (CNT)
3.1.4.
Field 1.004: Type of Transaction (TOT)
Transaction Type |
Logical Record Type |
|||||
1 |
2 |
4 |
9 |
13 |
15 |
|
CPS |
M |
M |
M |
— |
— |
— |
SRE |
M |
M |
C |
— (C in case of latent hits) |
C |
C |
MPS |
M |
M |
— |
M (1*) |
M |
— |
MMS |
M |
M |
— |
M (1*) |
M |
— |
PMS |
M |
M |
M* |
— |
— |
M* |
ERR |
M |
M |
— |
— |
— |
— |
3.1.5.
Field 1.005: Date of Transaction (DAT)
3.1.6.
Field 1.006: Priority (PRY)
3.1.7.
Field 1.007: Destination Agency Identifier (DAI)
3.1.8.
Field 1.008: Originating Agency Identifier (ORI)
3.1.9.
Field 1.009: Transaction Control Number (TCN)
3.1.10.
Field 1.010: Transaction Control Response (TCR)
3.1.11.
Field 1.011: Native Scanning Resolution (NSR)
3.1.12.
Field 1.012: Nominal Transmitting Resolution (NTR)
3.1.13.
Field 1.013: Domain name (DOM)
3.1.14.
Field 1.014: Greenwich mean time (GMT)
4. Type-2 Logical Record: Descriptive Text
4.1. Fields for Type-2 Logical Record
4.1.1.
Field 2.001: Logical Record Length (LEN)
4.1.2.
Field 2.002: Image Designation Character (IDC)
4.1.3.
Field 2.003: System Information (SYS)
4.1.4.
Field 2.007: Case Number (CNO)
4.1.5.
Field 2.008: Sequence Number (SQN)
4.1.6.
Field 2.009: Latent Identifier (MID)
4.1.7.
Field 2.010: Criminal Reference Number (CRN)
4.1.8.
Field 2.012: Miscellaneous Identification Number (MN1)
4.1.9.
Field 2.013: Miscellaneous Identification Number (MN2)
4.1.10.
Field 2.014: Miscellaneous Identification Number (MN3)
4.1.11.
Field 2.015: Miscellaneous Identification Number (MN4)
4.1.12.
Field 2.063: Additional Information (INF)
4.1.13.
Field 2.064: Respondents List (RLS)
4.1.14.
Field 2.074: Status/Error Message Field (ERM)
Numeric code (1-3) |
Meaning (5-128) |
003 |
ERROR: UNAUTHORISED ACCESS |
101 |
Mandatory field missing |
102 |
Invalid record type |
103 |
Undefined field |
104 |
Exceed the maximum occurrence |
105 |
Invalid number of subfields |
106 |
Field length too short |
107 |
Field length too long |
108 |
Field is not a number as expected |
109 |
Field number value too small |
110 |
Field number value too big |
111 |
Invalid character |
112 |
Invalid date |
115 |
Invalid item value |
116 |
Invalid type of transaction |
117 |
Invalid record data |
201 |
ERROR: INVALID TCN |
501 |
ERROR: INSUFFICIENT FINGERPRINT QUALITY |
502 |
ERROR: MISSING FINGERPRINTS |
503 |
ERROR: FINGERPRINT SEQUENCE CHECK FAILED |
999 |
ERROR: ANY OTHER ERROR. FOR FURTHER DETAILS CALL DESTINATION AGENCY. |
4.1.15.
Field 2.320: Expected Number of Candidates (ENC)
5. Type-4 Logical Record: High Resolution GreyScale Image
5.1. Fields for Type-4 Logical Record
5.1.1.
Field 4.001: Logical Record Length (LEN)
5.1.2.
Field 4.002: Image Designation Character (IDC)
5.1.3.
Field 4.003: Impression Type (IMP)
Code |
Description |
0 |
Live-scan of plain fingerprint |
1 |
Live-scan of rolled fingerprint |
2 |
Non-live scan impression of plain fingerprint captured from paper |
3 |
Non-live scan impression of rolled fingerprint captured from paper |
4 |
Latent impression captured directly |
5 |
Latent tracing |
6 |
Latent photo |
7 |
Latent lift |
8 |
Swipe |
9 |
Unknown |
5.1.4.
Field 4.004: Finger Position (FGP)
Finger position |
Finger code |
Width (mm) |
Length (mm) |
Unknown |
0 |
40,0 |
40,0 |
Right thumb |
1 |
45,0 |
40,0 |
Right index finger |
2 |
40,0 |
40,0 |
Right middle finger |
3 |
40,0 |
40,0 |
Right ring finger |
4 |
40,0 |
40,0 |
Right little finger |
5 |
33,0 |
40,0 |
Left thumb |
6 |
45,0 |
40,0 |
Left index finger |
7 |
40,0 |
40,0 |
Left middle finger |
8 |
40,0 |
40,0 |
Left ring finger |
9 |
40,0 |
40,0 |
Left little finger |
10 |
33,0 |
40,0 |
Plain right thumb |
11 |
30,0 |
55,0 |
Plain left thumb |
12 |
30,0 |
55,0 |
Plain right four fingers |
13 |
70,0 |
65,0 |
Plain left four fingers |
14 |
70,0 |
65,0 |
5.1.5.
Field 4.005: Image Scanning Resolution (ISR)
5.1.6.
Field 4.006: Horizontal Line Length (HLL)
5.1.7.
Field 4.007: Vertical Line Length (VLL)
5.1.8.
Field 4.008: Greyscale Compression Algorithm (GCA)
5.1.9.
Field 4.009: The Image
6. Type-9 Logical Record: Minutiæ Record
6.1. Minutiæ extraction
6.1.1.
Minutia type identification
Type |
Description |
0 |
Other |
1 |
Ridge ending |
2 |
Bifurcation |
6.1.2.
Minutia placement and type
Figure 6.1.2
6.1.3.
Coordinate system
6.1.4.
Minutiæ direction
6.2. Fields for Type-9 Logical record INCITS-378 Format
6.2.1.
Field 9.001: Logical record length (LEN)
6.2.2.
Field 9.002: Image designation character (IDC)
6.2.3.
Field 9.003: Impression type (IMP)
6.2.4.
Field 9.004: Minutiæ format (FMT)
6.2.5.
Field 9.126: CBEFF information
6.2.6.
Field 9.127: Capture equipment identification
6.2.7.
Field 9.128: Horizontal line length (HLL)
6.2.8.
Field 9.129: Vertical line length (VLL)
6.2.9.
Field 9.130: Scale units (SLC)
6.2.10.
Field 9.131: Horizontal pixel scale (HPS)
6.2.11.
Field 9.132: Vertical pixel scale (VPS)
6.2.12.
Field 9.133: Finger view
6.2.13.
Field 9.134: Finger position (FGP)
6.2.14.
Field 9.135: Finger quality
6.2.15.
Field 9.136: number of minutiæ
6.2.16.
Field 9.137: Finger minutiæ data
6.2.17.
Field 9.138: Ridge count information
6.2.18.
Field 9.139: Core information
6.2.19.
Field 9.140: Delta information
7. Type-13 variable-resolution latent image record
Ident |
Cond. code |
Field Number |
Field name |
Char type |
Field size per occurrence |
Occur count |
Max byte count |
||
min. |
max. |
min |
max |
||||||
LEN |
M |
13.001 |
LOGICAL RECORD LENGTH |
N |
4 |
8 |
1 |
1 |
15 |
IDC |
M |
13.002 |
IMAGE DESIGNATION CHARACTER |
N |
2 |
5 |
1 |
1 |
12 |
IMP |
M |
13.003 |
IMPRESSION TYPE |
A |
2 |
2 |
1 |
1 |
9 |
SRC |
M |
13.004 |
SOURCE AGENCY/ORI |
AN |
6 |
35 |
1 |
1 |
42 |
LCD |
M |
13.005 |
LATENT CAPTURE DATE |
N |
9 |
9 |
1 |
1 |
16 |
HLL |
M |
13.006 |
HORIZONTAL LINE LENGTH |
N |
4 |
5 |
1 |
1 |
12 |
VLL |
M |
13.007 |
VERTICAL LINE LENGTH |
N |
4 |
5 |
1 |
1 |
12 |
SLC |
M |
13.008 |
SCALE UNITS |
N |
2 |
2 |
1 |
1 |
9 |
HPS |
M |
13.009 |
HORIZONTAL PIXEL SCALE |
N |
2 |
5 |
1 |
1 |
12 |
VPS |
M |
13.010 |
VERTICAL PIXEL SCALE |
N |
2 |
5 |
1 |
1 |
12 |
CGA |
M |
13.011 |
COMPRESSION ALGORITHM |
A |
5 |
7 |
1 |
1 |
14 |
BPX |
M |
13.012 |
BITS PER PIXEL |
N |
2 |
3 |
1 |
1 |
10 |
FGP |
M |
13.013 |
FINGER POSITION |
N |
2 |
3 |
1 |
6 |
25 |
RSV |
|
13.014 13.019 |
RESERVED FOR FUTURE DEFINITION |
— |
— |
— |
— |
— |
— |
COM |
O |
13.020 |
COMMENT |
A |
2 |
128 |
0 |
1 |
135 |
RSV |
|
13.021 13.199 |
RESERVED FOR FUTURE DEFINITION |
— |
— |
— |
— |
— |
— |
UDF |
O |
13.200 13.998 |
USER-DEFINED FIELDS |
— |
— |
— |
— |
— |
— |
DAT |
M |
13.999 |
IMAGE DATA |
B |
2 |
— |
1 |
1 |
— |
7.1. Fields for the Type-13 logical record
7.1.1.
Field 13.001: Logical record length (LEN)
7.1.2.
Field 13.002: Image designation character (IDC)
7.1.3.
Field 13.003: Impression type (IMP)
7.1.4.
Field 13.004: Source agency/ORI (SRC)
7.1.5.
Field 13.005: Latent capture date (LCD)
7.1.6.
Field 13.006: Horizontal line length (HLL)
7.1.7.
Field 13.007: Vertical line length (VLL)
7.1.8.
Field 13.008: Scale units (SLC)
7.1.9.
Field 13.009: Horizontal pixel scale (HPS)
7.1.10.
Field 13.010: Vertical pixel scale (VPS)
7.1.11.
Field 13.011: Compression algorithm (CGA)
7.1.12.
Field 13.012: Bits per pixel (BPX)
7.1.13.
Field 13.013: Finger/palm position (FGP)
7.1.14.
Field 13.014-019: Reserved for future definition (RSV)
7.1.15.
Field 13.020: Comment (COM)
7.1.16.
Field 13.021-199: Reserved for future definition (RSV)
7.1.17.
Fields 13.200-998: User-defined fields (UDF)
7.1.18.
Field 13.999: Image data (DAT)
7.2. End of Type-13 variable-resolution latent image record
8. Type-15 variable-resolution palmprint image record
8.1. Fields for the Type-15 logical record
8.1.1.
Field 15.001: Logical record length (LEN)
8.1.2.
Field 15.002: Image designation character (IDC)
8.1.3.
Field 15.003: Impression type (IMP)
8.1.4.
Field 15.004: Source agency/ORI (SRC)
8.1.5.
Field 15.005: Palmprint capture date (PCD)
8.1.6.
Field 15.006: Horizontal line length (HLL)
8.1.7.
Field 15.007: Vertical line length (VLL)
8.1.8.
Field 15.008: Scale units (SLC)
8.1.9.
Field 15.009: Horizontal pixel scale (HPS)
8.1.10.
Field 15.010: Vertical pixel scale (VPS)
Ident |
Cond. code |
Field number |
Field name |
Char type |
Field size per occurrence |
Occur count |
Max byte count |
||
min. |
max. |
min |
max |
||||||
LEN |
M |
15.001 |
LOGICAL RECORD LENGTH |
N |
4 |
8 |
1 |
1 |
15 |
IDC |
M |
15.002 |
IMAGE DESIGNATION CHARACTER |
N |
2 |
5 |
1 |
1 |
12 |
IMP |
M |
15.003 |
IMPRESSION TYPE |
N |
2 |
2 |
1 |
1 |
9 |
SRC |
M |
15.004 |
SOURCE AGENCY/ORI |
AN |
6 |
35 |
1 |
1 |
42 |
PCD |
M |
15.005 |
PALMPRINT CAPTURE DATE |
N |
9 |
9 |
1 |
1 |
16 |
HLL |
M |
15.006 |
HORIZONTAL LINE LENGTH |
N |
4 |
5 |
1 |
1 |
12 |
VLL |
M |
15.007 |
VERTICAL LINE LENGTH |
N |
4 |
5 |
1 |
1 |
12 |
SLC |
M |
15.008 |
SCALE UNITS |
N |
2 |
2 |
1 |
1 |
9 |
HPS |
M |
15.009 |
HORIZONTAL PIXEL SCALE |
N |
2 |
5 |
1 |
1 |
12 |
VPS |
M |
15.010 |
VERTICAL PIXEL SCALE |
N |
2 |
5 |
1 |
1 |
12 |
CGA |
M |
15.011 |
COMPRESSION ALGORITHM |
AN |
5 |
7 |
1 |
1 |
14 |
BPX |
M |
15.012 |
BITS PER PIXEL |
N |
2 |
3 |
1 |
1 |
10 |
PLP |
M |
15.013 |
PALMPRINT POSITION |
N |
2 |
3 |
1 |
1 |
10 |
RSV |
|
15.014 15.019 |
RESERVED FOR FUTURE INCLUSION |
— |
— |
— |
— |
— |
— |
COM |
O |
15.020 |
COMMENT |
AN |
2 |
128 |
0 |
1 |
128 |
RSV |
|
15.021 15.199 |
RESERVED FOR FUTURE INCLUSION |
— |
— |
— |
— |
— |
— |
UDF |
O |
15.200 15.998 |
USER-DEFINED FIELDS |
— |
— |
— |
— |
— |
— |
DAT |
M |
15.999 |
IMAGE DATA |
B |
2 |
— |
1 |
1 |
— |
Description |
Code |
Live-scan palm |
10 |
Nonlive-scan palm |
11 |
Latent palm impression |
12 |
Latent palm tracing |
13 |
Latent palm photo |
14 |
Latent palm lift |
15 |
8.1.11.
Field 15.011: Compression algorithm (CGA)
8.1.12.
Field 15.012: Bits per pixel (BPX)
Palm Position |
Palm code |
Image area (mm2) |
Width (mm) |
Height (mm) |
Unknown Palm |
20 |
28 387 |
139,7 |
203,2 |
Right Full Palm |
21 |
28 387 |
139,7 |
203,2 |
Right Writer s Palm |
22 |
5 645 |
44,5 |
127,0 |
Left Full Palm |
23 |
28 387 |
139,7 |
203,2 |
Left Writer s Palm |
24 |
5 645 |
44,5 |
127,0 |
Right Lower Palm |
25 |
19 516 |
139,7 |
139,7 |
Right Upper Palm |
26 |
19 516 |
139,7 |
139,7 |
Left Lower Palm |
27 |
19 516 |
139,7 |
139,7 |
Left Upper Palm |
28 |
19 516 |
139,7 |
139,7 |
Right Other |
29 |
28 387 |
139,7 |
203,2 |
Left Other |
30 |
28 387 |
139,7 |
203,2 |
8.1.13.
Field 15.013: Palmprint position (PLP)
8.1.14.
Field 15.014-019: Reserved for future definition (RSV)
8.1.15.
Field 15.020: Comment (COM)
8.1.16.
Field 15.021-199: Reserved for future definition (RSV
)
8.1.17.
Fields 15.200-998: User-defined fields (UDF)
8.1.18.
Field 15.999: Image data (DAT)
8.2. End of Type-15 variable-resolution palmprint image record
8.3. Additional Type-15 variable-resolution palmprint image records
Type of AFIS Search |
TP/TP |
LT/TP |
LP/PP |
TP/UL |
LT/UL |
PP/ULP |
LP/ULP |
Maximum Number of Candidates |
1 |
10 |
5 |
5 |
5 |
5 |
5 |
9. Appendices to Chapter 2 (exchange of dactyloscopic data)
9.1. Appendix 1 ASCII Separator Codes
ASCII |
Position(2) |
Description |
LF |
1/10 |
Separates error codes in Field 2.074 |
FS |
1/12 |
Separates logical records of a file |
GS |
1/13 |
Separates fields of a logical record |
RS |
1/14 |
Separates the subfields of a record field |
US |
1/15 |
Separates individual information items of the field or subfield |
9.2. Appendix 2 Calculation of Alpha-Numeric Check Character
1-A |
9-J |
17-T |
2-B |
10-K |
18-U |
3-C |
11-L |
19-V |
4-D |
12-M |
20-W |
5-E |
13-N |
21-X |
6-F |
14-P |
22-Y |
7-G |
15-Q |
0-Z |
8-H |
16-R |
|
9.3. Appendix 3 Character Codes
ASCII Character Set |
||||||||||
+ |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
30 |
|
|
|
! |
’ |
# |
$ |
% |
& |
‘ |
40 |
( |
) |
* |
+ |
, |
- |
. |
/ |
0 |
1 |
50 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
: |
; |
60 |
< |
= |
> |
? |
@ |
A |
B |
C |
D |
E |
70 |
F |
G |
H |
I |
J |
K |
L |
M |
N |
O |
80 |
P |
Q |
R |
S |
T |
U |
V |
W |
X |
Y |
90 |
Z |
[ |
] |
^ |
_ |
` |
a |
b |
c |
|
100 |
d |
e |
f |
g |
h |
i |
j |
k |
l |
m |
110 |
n |
o |
p |
q |
r |
s |
t |
u |
v |
w |
120 |
x |
y |
z |
{ |
| |
} |
~ |
|
|
|
9.4. Appendix 4 Transaction Summary
Identifier |
Field number |
Field name |
CPS/PMS |
SRE |
ERR |
LEN |
1.001 |
Logical Record Length |
M |
M |
M |
VER |
1.002 |
Version Number |
M |
M |
M |
CNT |
1.003 |
File Content |
M |
M |
M |
TOT |
1.004 |
Type of Transaction |
M |
M |
M |
DAT |
1.005 |
Date |
M |
M |
M |
PRY |
1.006 |
Priority |
M |
M |
M |
DAI |
1.007 |
Destination Agency |
M |
M |
M |
ORI |
1.008 |
Originating Agency |
M |
M |
M |
TCN |
1.009 |
Transaction Control Number |
M |
M |
M |
TCR |
1.010 |
Transaction Control Reference |
C |
M |
M |
NSR |
1.011 |
Native Scanning Resolution |
M |
M |
M |
NTR |
1.012 |
Nominal Transmitting Resolution |
M |
M |
M |
DOM |
1.013 |
Domain name |
M |
M |
M |
GMT |
1.014 |
Greenwich mean time |
M |
M |
M |
Identifier |
Field number |
Field name |
CPS/PMS |
MPS/MMS |
SRE |
ERR |
LEN |
2.001 |
Logical Record Length |
M |
M |
M |
M |
IDC |
2.002 |
Image Designation Character |
M |
M |
M |
M |
SYS |
2.003 |
System Information |
M |
M |
M |
M |
CNO |
2.007 |
Case Number |
— |
M |
C |
— |
SQN |
2.008 |
Sequence Number |
— |
C |
C |
— |
MID |
2.009 |
Latent Identifier |
— |
C |
C |
— |
CRN |
2.010 |
Criminal Reference Number |
M |
— |
C |
— |
MN1 |
2.012 |
Miscellaneous Identification Number |
— |
— |
C |
C |
MN2 |
2.013 |
Miscellaneous Identification Number |
— |
— |
C |
C |
MN3 |
2.014 |
Miscellaneous Identification Number |
— |
— |
C |
C |
MN4 |
2.015 |
Miscellaneous Identification Number |
— |
— |
C |
C |
INF |
2.063 |
Additional Information |
O |
O |
O |
O |
RLS |
2.064 |
Respondents List |
— |
— |
M |
— |
ERM |
2.074 |
Status/Error Message Field |
— |
— |
— |
M |
ENC |
2.320 |
Expected Number of Candidates |
M |
M |
— |
— |
9.5. Appendix 5 Type-1 Record Definitions
Identifier |
Condition |
Field number |
Field name |
Character type |
Example data |
LEN |
M |
1.001 |
Logical Record Length |
N |
1.001:230{GS} |
VER |
M |
1.002 |
Version Number |
N |
1.002:0300{GS} |
CNT |
M |
1.003 |
File Content |
N |
1.003:1{US}15{RS}2{US}00{RS}4{US}01{RS}4{US}02{RS}4{US}03{RS}4{US}04{RS}4{US}05{RS}4{US}06{RS}4{US}07{RS}4{US}08{RS}4{US}09{RS}4{US}10{RS}4{US}11{RS}4{US}12{RS}4{US}13{RS}4{US}14{GS} |
TOT |
M |
1.004 |
Type of Transaction |
A |
1.004:CPS{GS} |
DAT |
M |
1.005 |
Date |
N |
1.005:20050101{GS} |
PRY |
M |
1.006 |
Priority |
N |
1.006:4{GS} |
DAI |
M |
1.007 |
Destination Agency |
1* |
1.007:DE/BKA{GS} |
ORI |
M |
1.008 |
Originating Agency |
1* |
1.008:NL/NAFIS{GS} |
TCN |
M |
1.009 |
Transaction Control Number |
AN |
1.009:0200000004F{GS} |
TCR |
C |
1.010 |
Transaction Control Reference |
AN |
1.010:0200000004F{GS} |
NSR |
M |
1.011 |
Native Scanning Resolution |
AN |
1.011:19.68{GS} |
NTR |
M |
1.012 |
Nominal Transmitting Resolution |
AN |
1.012:19,68{GS} |
DOM |
M |
1.013 |
Domain Name |
AN |
1.013: INT-I{US}4,22{GS} |
GMT |
M |
1.014 |
Greenwich Mean Time |
AN |
1.014:20050101125959Z |
9.6. Appendix 6 Type-2 Record Definitions
Identifier |
Condition |
Field number |
Field name |
Character type |
Example data |
LEN |
M |
2.001 |
Logical Record Length |
N |
2.001:909{GS} |
IDC |
M |
2.002 |
Image Designation Character |
N |
2.002:00{GS} |
SYS |
M |
2.003 |
System Information |
N |
2.003:0422{GS} |
CRN |
M |
2.010 |
Criminal Reference Number |
AN |
2.010:DE/E999999999{GS} |
INF |
O |
2.063 |
Additional Information |
1* |
2.063:Additional Information 123{GS} |
ENC |
M |
2.320 |
Expected Number of Candidates |
N |
2.320:1{GS} |
Identifier |
Condition |
Field number |
Field name |
Character type |
Example data |
LEN |
M |
2.001 |
Logical Record Length |
N |
2.001:909{GS} |
IDC |
M |
2.002 |
Image Designation Character |
N |
2.002:00{GS} |
SYS |
M |
2.003 |
System Information |
N |
2.003:0422{GS} |
CRN |
C |
2.010 |
Criminal Reference Number |
AN |
2.010:NL/2222222222{GS} |
MN1 |
C |
2.012 |
Miscellaneous Identification Number |
AN |
2.012:E999999999{GS} |
MN2 |
C |
2.013 |
Miscellaneous Identification Number |
AN |
2.013:E999999999{GS} |
MN3 |
C |
2.014 |
Miscellaneous Identification Number |
N |
2.014:0001{GS} |
MN4 |
C |
2.015 |
Miscellaneous Identification Number |
A |
2.015:A{GS} |
INF |
O |
2.063 |
Additional Information |
1* |
2.063:Additional Information 123{GS} |
RLS |
M |
2.064 |
Respondents List |
AN |
2.064:CPS{RS}I{RS}001/001{RS}999999{GS} |
Identifier |
Condition |
Field number |
Field name |
Character type |
Example data |
LEN |
M |
2.001 |
Logical Record Length |
N |
2.001:909{GS} |
IDC |
M |
2.002 |
Image Designation Character |
N |
2.002:00{GS} |
SYS |
M |
2.003 |
System Information |
N |
2.003:0422{GS} |
MN1 |
M |
2.012 |
Miscellaneous Identification Number |
AN |
2.012:E999999999{GS} |
MN2 |
C |
2.013 |
Miscellaneous Identification Number |
AN |
2.013:E999999999{GS} |
MN3 |
C |
2.014 |
Miscellaneous Identification Number |
N |
2.014:0001{GS} |
MN4 |
C |
2.015 |
Miscellaneous Identification Number |
A |
2.015:A{GS} |
INF |
O |
2.063 |
Additional Information |
1* |
2.063:Additional Information 123{GS} |
ERM |
M |
2.074 |
Status/Error Message Field |
AN |
2.074: 201: IDC - 1 FIELD 1.009 WRONG CONTROL CHARACTER {LF} 115: IDC 0 FIELD 2.003 INVALID SYSTEM INFORMATION {GS} |
Identifier |
Condition |
Field number |
Field name |
Character type |
Example data |
LEN |
M |
2.001 |
Logical Record Length |
N |
2.001:909{GS} |
IDC |
M |
2.002 |
Image Designation Character |
N |
2.002:00{GS} |
SYS |
M |
2.003 |
System Information |
N |
2.003:0422{GS} |
CNO |
M |
2.007 |
Case Number |
AN |
2.007:E999999999{GS} |
SQN |
C |
2.008 |
Sequence Number |
N |
2.008:0001{GS} |
MID |
C |
2.009 |
Latent Identifier |
A |
2.009:A{GS} |
INF |
O |
2.063 |
Additional Information |
1* |
2.063:Additional Information 123{GS} |
ENC |
M |
2.320 |
Expected Number of Candidates |
N |
2.320:1{GS} |
9.7. Appendix 7 Greyscale Compression Codes
Compression |
Value |
Remarks |
Wavelet Scalar Quantisation Greyscale Fingerprint Image Compression Specification IAFIS-IC-0010(V3), dated 19 December 1997 |
WSQ |
Algorithm to be used for the compression of greyscale images in Type-4, Type-7 and Type-13 to Type-15 records. Shall not be used for resolutions > 500dpi. |
JPEG 2000 [ISO 15444/ITU T.800] |
J2K |
To be used for lossy and losslessly compression of greyscale images in Type-13 to Type-15 records. Strongly recommended for resolutions > 500 dpi |
9.8. Appendix 8 Mailspecification
CHAPTER 3:
Exchange of vehicle registration data
1. Common data-set for automated search of vehicle registration data
1.1. Definitions
1.2. Vehicle/owner/holder search
1.2.1.
Triggers for the search
1.2.2.
Data set
Item |
M/O(3) |
Remarks |
Prüm Y/N(4) |
Data relating to vehicles |
|
|
|
Licence number |
M |
|
Y |
Chassis number/VIN |
M |
|
Y |
Country of registration |
M |
|
Y |
Make |
M |
(D.1(5)) e.g. Ford, Opel, Renault, etc. |
Y |
Commercial type of the vehicle |
M |
(D.3) e.g. Focus, Astra, Megane |
Y |
EU Category Code |
M |
(J) mopeds, motorbikes, cars, etc. |
Y |
Item |
M/O(6) |
Remarks |
Prüm Y/N |
||||||
Data relating to holders of the vehicle |
|
(C.1(7)) The data refer to the holder of the specific registration certificate. |
|
||||||
Registration holders' (company) name |
M |
(C.1.1.) separate fields will be used for surname, infixes, titles, etc., and the name in printable format will be communicated |
Y |
||||||
First name |
M |
(C.1.2) separate fields for first name(s) and initials will be used, and the name in printable format will be communicated |
Y |
||||||
Address |
M |
(C.1.3) separate fields will be used for Street, House number and Annex, Zip code, Place of residence, Country of residence, etc., and the Address in printable format will be communicated |
Y |
||||||
Gender |
M |
Male, female |
Y |
||||||
Date of birth |
M |
|
Y |
||||||
Legal entity |
M |
individual, association, company, firm, etc. |
Y |
||||||
Place of Birth |
O |
|
Y |
||||||
ID Number |
O |
An identifier that uniquely identifies the person or the company. |
N |
||||||
Type of ID Number |
O |
The type of ID Number (e.g. passport number). |
N |
||||||
Start date holdership |
O |
Start date of the holdership of the car. This date will often be the same as printed under (I) on the registration certificate of the vehicle. |
N |
||||||
End date holdership |
O |
End data of the holdership of the car. |
N |
||||||
Type of holder |
O |
If there is no owner of the vehicle (C.2) the reference to the fact that the holder of the registration certificate:
|
N |
||||||
Data relating to owners of the vehicle |
|
(C.2) |
|
||||||
Owners' (company) name |
M |
(C.2.1) |
Y |
||||||
First name |
M |
(C.2.2) |
Y |
||||||
Address |
M |
(C.2.3) |
Y |
||||||
Gender |
M |
male, female |
Y |
||||||
Date of birth |
M |
|
Y |
||||||
Legal entity |
M |
individual, association, company, firm, etc. |
Y |
||||||
Place of Birth |
O |
|
Y |
||||||
ID Number |
O |
An identifier that uniquely identifies the person or the company. |
N |
||||||
Type of ID Number |
O |
The type of ID Number (e.g. passport number). |
N |
||||||
Start date ownership |
O |
Start date of the ownership of the car. |
N |
||||||
End date ownership |
O |
End data of the ownership of the car. |
N |
||||||
Data relating to vehicles |
|
|
|
||||||
Licence number |
M |
|
Y |
||||||
Chassis number/VIN |
M |
|
Y |
||||||
Country of registration |
M |
|
Y |
||||||
Make |
M |
(D.1) e.g. Ford, Opel, Renault, etc. |
Y |
||||||
Commercial type of the vehicle |
M |
(D.3) e.g. Focus, Astra, Megane. |
Y |
||||||
Nature of the vehicle/EU Category Code |
M |
(J) mopeds, motorbikes, cars, etc. |
Y |
||||||
Date of first registration |
M |
(B) Date of first registration of the vehicle somewhere in the world. |
Y |
||||||
Start date (actual) registration |
M |
(I) Date of the registration to which the specific certificate of the vehicle refers. |
Y |
||||||
End date registration |
M |
End data of the registration to which the specific certificate of the vehicle refers. It is possible this date indicates the period of validity as printed on the document if not unlimited (document abbreviation = H). |
Y |
||||||
Status |
M |
Scrapped, stolen, exported, etc. |
Y |
||||||
Start date status |
M |
|
Y |
||||||
End date status |
O |
|
N |
||||||
kW |
O |
(P.2) |
Y |
||||||
Capacity |
O |
(P.1) |
Y |
||||||
Type of licence number |
O |
Regular, transito, etc. |
Y |
||||||
Vehicle document id 1 |
O |
The first unique document ID as printed on the vehicle document. |
Y |
||||||
Vehicle document id 2(8) |
O |
A second document ID as printed on the vehicle document. |
Y |
||||||
Data relating to insurances |
|
|
|
||||||
Insurance company name |
O |
|
Y |
||||||
Begin date insurance |
O |
|
Y |
||||||
End date insurance |
O |
|
Y |
||||||
Address |
O |
|
Y |
||||||
Insurance number |
O |
|
Y |
||||||
ID number |
O |
An identifier that uniquely identifies the company. |
N |
||||||
Type of ID number |
O |
The type of ID number (e.g. number of the Chamber of Commerce) |
N |
2. Data Security
2.1. Overview
2.2. Security Features related to message exchange
2.3. Security features not related to message exchange
2.3.1.
Authentication of users
2.3.2.
User roles
2.3.3.
Logging and tracing of message exchange
Figure: Message types for logging
2.3.4.
Hardware Security Module
3. Technical conditions of the data exchange
3.1. General description of the Eucaris application
3.1.1.
Overview
3.1.2.
Scope of the system
Eucaris aspects |
M/O(9) |
Remark |
||||||||||||||||
Network concept |
M |
The concept is an ‘any-to-any’ communication. |
||||||||||||||||
Physical network |
M |
TESTA |
||||||||||||||||
Core application |
M |
The core application of Eucaris has to be used to connect to the other Member States. The following functionality is offered by the core:
|
||||||||||||||||
Client application |
O |
In addition to the core application the Eucaris II client application can be used by a Member State. When applicable, the core and client application are modified under auspices of the Eucaris organisation. |
||||||||||||||||
Security concept |
M |
The concept is based on XML-signing by means of client certificates and SSL-encryption by means of service certificates. |
||||||||||||||||
Message specifications |
M |
Every Member State has to comply with the message specifications as set by the Eucaris organisation and this Council Decision. The specifications can only be changed by the Eucaris organisation in consultation with the Member States. |
||||||||||||||||
Operation and Support |
M |
The acceptance of new Member States or a new functionality is under auspices of the Eucaris organisation. Monitoring and help desk functions are managed centrally by an appointed Member State. |
3.2. Functional and Non Functional Requirements
3.2.1.
Generic functionality
No |
Description |
1. |
The system allows the Registration Authorities of the Member States to exchange request and response messages in an interactive way. |
2. |
The system contains a client application, enabling end-users to send their requests and presenting the response information for manual processing |
3. |
The system facilitates ‘broadcasting’, allowing a Member State to send a request to all other Member States. The incoming responses are consolidated by the core application in one response message to the client application (this functionality is called a "Multiple Country Inquiry). |
4. |
The system is able to deal with different types of messages. User roles, authorisation, routing, signing and logging are all defined per specific service. |
5. |
The system allows the Member States to exchange batches of messages or messages containing a large number of requests or replies. These messages are dealt with in an asynchronous way. |
6. |
The system queues asynchronous messages if the recipient Member State is temporarily unavailable and guarantees the deliverance as soon as the recipient is up again. |
7. |
The system stores incoming asynchronous messages until they can be processed. |
8. |
The system only gives access to Eucaris applications of other Member States, not to individual organisations within those other Member States, i.e. each Registration Authority acts as the single gateway between its national end-users and the corresponding Authorities in the other Member States. |
9. |
It is possible to define users of different Member States on one Eucaris server and to authorise them following the rights of that Member State. |
10. |
Information on the requesting Member State, organisation and end user are included in the messages. |
11. |
The system facilitates logging of the exchange of messages between the different Member States and between the core application and the national registration systems. |
12. |
The system allows a specific secretary, which is an organisation or Member State explicitly appointed for this task, to gather logged information on messages sent/received by all the participating Member States, in order to produce statistical reports. |
13. |
Each Member State indicates itself what logged information is made available for the secretary and what information is ‘private’. |
14. |
The system allows the National Administrators of each Member State to extract statistics of use. |
15. |
The system enables addition of new Member States through simple administrative tasks. |
3.2.2.
Usability
No |
Description |
16. |
The system provides an interface for automated processing of messages by back-end systems/legacy and enables the integration of the user interface in those systems (customised user-interface). |
17. |
The system is easy to learn, self explanatory and contains help-text. |
18. |
The system is documented to assist Member States in integration, operational activities and future maintenance (e.g. reference guides, functional/technical documentation, operational guide, …). |
19. |
The user interface is multi-lingual and offers facilities for the end-user to select a preferred language. |
20. |
The user interface contains facilities for a Local Administrator to translate both screen-items and coded information to the national language. |
3.2.3.
Reliability
No |
Description |
21. |
The system is designed as a robust and dependable operational system which is tolerant to operator errors and which will recover cleanly from power cuts or other disasters. It must be possible to restart the system with no or minimal loss of data. |
22. |
The system must give stable and reproducible results. |
23. |
The system has been designed to function reliably. It is possible to implement the system in a configuration that guarantees an availability of 98 % (by redundancy, the use of back-up servers, etc.) in each bilateral communication. |
24. |
It is possible to use part of the system, even during failure of some components (if Member State C is down, Member States A and B are still able to communicate). The number of single points of failure in the information chain should be minimised. |
25. |
The recovery time after a severe failure should be less than one day. It should be possible to minimise down-time by using remote support, e.g. by a central service desk. |
3.2.4.
Performance
No |
Description |
26. |
The system can be used 24x7. This time-window (24x7) is then also required from the Member States' legacy systems. |
27. |
The system responds rapidly to user requests irrespective of any background tasks. This is also required from the Parties legacy systems to ensure acceptable response time. An overall response time of 10 seconds maximum for a single request is acceptable. |
28. |
The system has been designed as a multi-user system and in such a way that background tasks can continue while the user performs foreground tasks. |
29. |
The system has been designed to be scaleable in order to support the potential increase of number of messages when new functionality is added or new organisations or Member States are added. |
3.2.5.
Security
No |
Description |
30. |
The system is suited (e.g. in its security measures) for the exchange of messages containing privacy-sensitive personal data (e.g. car owner/holders), classified as EU restricted. |
31. |
The system is maintained in such a way that unauthorised access to the data is prevented. |
32. |
The system contains a service for the management of the rights and permissions of national end-users. |
33. |
Member States are able to check the identity of the sender (at Member State level), by means of XML-signing. |
34. |
Member States must explicitly authorise other Member States to request specific information. |
35. |
The system provides at application level a full security and encryption policy compatible with the level of security required in such situations. Exclusiveness and integrity of the information is guaranteed by the use of XML-signing and encryption by means of SSL-tunnelling. |
36. |
All exchange of messages can be traced by means of logging. |
37. |
Protection is provided against deletion attacks (a third party deletes a message) and replay or insertion attacks (a third party replays or inserts a message). |
38. |
The system makes use of certificates of a Trusted Third Party (TTP). |
39. |
The system is able to handle different certificates per Member State, depending on the type of message or service. |
40. |
The security measures at application level are sufficient to allow the use of non accredited networks. |
41. |
The system is able to use novice security techniques such as an XML-firewall. |
3.2.6.
Adaptability
No |
Description |
42. |
The system is extensible with new messages and new functionality. The costs of adaptations are minimal. Due to the centralised development of application components. |
43. |
Member States are able to define new message types for bilateral use. Not all Member States are required to support all message types. |
3.2.7.
Support and Maintenance
No |
Description |
44. |
The system provides monitoring facilities for a central service-desk and/or operators concerning the network and servers in the different Member States. |
45. |
The system provides facilities for remote support by a central service-desk. |
46. |
The system provides facilities for problem analysis. |
47. |
The system can be expanded to new Member States. |
48. |
The application can easily be installed by staff with a minimum of IT-qualifications and experience. The installation procedure shall be as much as possible automated. |
49. |
The system provides a permanent testing and acceptance environment. |
50. |
The annual costs of maintenance and support has been minimised by adherence to market standards and by creating the application in such a way that as little support as possible from a central service-desk is required. |
3.2.8.
Design requirements
No |
Description |
51. |
The system is designed and documented for an operational lifetime of many years. |
52. |
The system has been designed in such a way that it is independent of the network provider. |
53. |
The system is compliant with the existing HW/SW in the Member States by interacting with those registration systems using open standard web service technology (XML, XSD, SOAP, WSDL, HTTP(s), Web services, WSS, X.509, etc.). |
3.2.9.
Applicable standards
No |
Description |
54. |
The system is compliant with data protection issues as stated in Regulation EC 45/2001 (Articles 21, 22 and 23) and Directive 95/46/EC. |
55. |
The system complies with the IDA Standards. |
56. |
The system supports UTF8. |