ETSI TR 103 854 V1.1.1 (2022-03)

LEA support services; Interfaces for Lawful Disclosure of vehicle-related data: scenarios, examples and recommendations

DTR/LI-00214

General Information

• Status: Not Published
• Technical Committee: LI - Lawful Interception
• Current Stage: 12 - Completion
• Due Date: 15-Mar-2022
• Completion Date: 10-Mar-2022

Standards Content (Sample)

ETSI TR 103 854 V1.1.1 (2022-03)






TECHNICAL REPORT
LEA support services;
Interfaces for Lawful Disclosure of vehicle-related data:
scenarios, examples and recommendations

---------------------- Page: 1 ----------------------
2 ETSI TR 103 854 V1.1.1 (2022-03)

Reference
DTR/LI-00214
Keywords
interface, security, trust

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2022.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3 ETSI TR 103 854 V1.1.1 (2022-03)
Contents
Intellectual Property Rights . 4
Foreword. 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definition of terms, symbols and abbreviations . 5
3.1 Terms . 5
3.2 Symbols . 5
3.3 Abbreviations . 6
4 Structure of the present document . 6
5 Reference model . 6
6 Examples of use cases . 7
6.1 Overview . 7
6.2 List of example use cases . 7
6.2.1 Vehicle identification number to international mobile equipment identifier. 7
6.2.2 International mobile equipment identifier to vehicle identification number . 7
6.2.3 Vehicle identification number to international mobile subscriber identifier . 8
6.2.4 International mobile subscriber identifier to vehicle identification number . 8
6.2.5 Vehicle identification number to location . 8
6.2.6 Vehicle identification number to vehicle data . 8
7 Recommended approach for interfacing . 9
7.1 Overview . 9
7.2 Information fields . 9
7.2.1 Request information . 9
7.2.2 Response information . 9
7.2.3 Format for request and response information . 10
7.2.4 Data categories . 10
7.3 Delivery protocols . 11
7.3.1 Use of HTTP . 11
7.3.2 Delivery security details . 11
Annex A: Usage scenarios . 12
A.1 Overview . 12
A.2 Extended vehicle databases . 12
A.3 European Production Order . 12
A.4 Autonomous Vehicles . 12
A.5 EU C-ITS WG6 . 12
A.6 Stolen vehicle recovery . 13
A.7 Cross-border aspects . 13
Annex B: Example of VIN-to-IMEI use case. 14
Annex C: Change History . 15
History . 16


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TR 103 854 V1.1.1 (2022-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the
®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Report (TR) has been produced by ETSI Technical Committee Lawful Interception (LI).
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TR 103 854 V1.1.1 (2022-03)
1 Scope
The present document describes an interface consisting of requests from a Law Enforcement Agency for vehicle-related
data and the responses to those requests. The present document describes some usage scenarios and puts forward some
examples for this interface. The present document includes a recommendation for the details of how the interface could
work.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TR 103 767: "Lawful Interception (LI); Considerations about interfacing with providers of
vehicle information".
[i.2] ETSI TS 123 003: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; 5G; Numbering, addressing and identification
(3GPP TS 23.003)".
[i.3] ISO 20078-1:2021: "Road vehicles - Extended vehicle (ExVe) web services - Part 1: Content and
definitions".
[i.4] ETSI TS 103 280: "Lawful Interception (LI); Dictionary for common parameters".
[i.5] ISO 3779:2009: "Road vehicles - Vehicle identification number (VIN) - Content and structure".
[i.6] COM/2018/225 final: "Proposal for a Regulation of the European Parliament and of the Council
on European Production and Preservation Orders for electronic evidence in criminal matters".
[i.7] SAE J853-2009: "Vehicle Identification Numbers".
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TR 103 854 V1.1.1 (2022-03)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
C-ITS Cooperative Intelligent Transport Systems
ExVe Extended Vehicle
GPS Global Positioning System
HTTP Hyper Text Transfer Protocol
HTTPS Hyper Text Transfer Protocol Secure
ICCID Integrated Circuit Card IDentification
ID IDentifier
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
ISO International Organization for Standardization
JSON JavaScript Object Notation
LEA Law Enforcement Agency
OEM Original Equipment Manufacturer
PEI Permanent Equipment Identifier
RPS Response Processing System
SAE Society of Automotive Engineers
VIN Vehicle Identification Number
XML eXtensible Markup Language
4 Structure of the present document
The present document includes:
• Reference model and description of basic responsibilities (clause 5).
• List of examples of use cases (clause 6).
• Recommendation for how the interface should be implemented (clause 7).
• Usage scenarios (annex A).
• Example data structures (annex B).
5 Reference model
Figure 5.1 shows the reference model for the present document.

Request
Organisation which has vehicle
Law Enforcement Agency
information
(LEA system)
(Response Processing System)
Response


Figure 5.1: Reference model
The Law Enforcement Agency (LEA) is responsible for creating a lawful request. The LEA system delivers the request
to a Response Processing System (RPS). The legal obligation on RPS (for example, what has to be delivered, what has
to be retained) is considered independently of the delivery interface and is out of scope of the present document.
This architecture is designed to address use cases that can be met by transactional requests/responses. The present
document does not attempt to describe use cases that require an ongoing live stream of data from an RPS (such as voice
or video).
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TR 103 854 V1.1.1 (2022-03)
The request sent by the LEA needs to be clear. A request is clear if it is explicit to an RPS whether any particular record
(held by an RPS) matches or does not match the request.
The RPS is responsible for the collection of the data within its organization and produces the data using its own
capabilities and entirely under its control. The RPS identifies the data which matches the request, and only that data.
The RPS is entitled to put in place a human review of the request and delivered material. The RPS packages the data,
attaches relevant information (including a timestamp and the unambiguous reference to the issued request) and delivers
it to the requesting LEA.
The term RPS is used to cover any organization which holds vehicle-related data where there is a lawful reason for it to
respond to requests for information. It is not intended to include only manufacturers and may include any relevant
commercial or government organization.
6 Examples of use cases
6.1 Overview
This clause contains a list of use cases which are intended to provide some useful illustrations. This is not an exhaustive
list and there is no implication that these use cases are lawful or required in any particular jurisdiction (that is a
legislative matter which is out of scope).
6.2 List of example use cases
6.2.1 Vehicle identification number to international mobile equipment
identifier
This use case is called VIN-to-IMEI. In this use case, the LEA knows a Vehicle Identification Number (VIN) and
requests the IMEI(s). An illustration is given in annex B.
Other variants of this use case could include other equipment identifiers beyond an IMEI, specifically including PEI.
For the VIN-to-IMEI use case:
• The request includes the VIN, as a string (checked to be compliant with the relevant standard,
e.g. ISO 3779 [i.5] and SAE J853-2009 [i.7]).
• The response contains zero, one or more IMEI(s) (in the format defined in 3GPP TS 23.003 [i.2]) associated
with the supplied VIN, or an error code.
NOTE 1: As with all use cases, the request and respo
...