1、 ETSI TS 103 280 V2.1.1 (2017-08) Lawful Interception (LI); Dictionary for common parameters floppy3TECHNICAL SPECIFICATION ETSI ETSI TS 103 280 V2.1.1 (2017-08)2 Reference RTS/LI-00146 Keywords dictionary, Lawful Interception, security ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FR
2、ANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be m
3、ade 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,
4、the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. 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
5、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 Copyright Notification No part may be reproduce
6、d 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 ex
7、tend to reproduction in all media. ETSI 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. o
8、neM2M logo is protected for the benefit of its Members. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 103 280 V2.1.1 (2017-08)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normative r
9、eferences . 5g32.2 Informative references 6g33 Abbreviations . 6g34 Release management 7g35 Parameter requirements 7g35.0 Introduction 7g35.1 Parameter attributes 7g35.2 Parameter naming conventions . 8g35.3 Technology conventions . 8g36 Parameter dictionary. 8g37 Technical implementation 16g37.1 XS
10、D 16g37.2 ASN.1 . 16g3Annex A (normative): XSD definition 17g3Annex B (normative): ASN.1 definition . 20g3Annex C (informative): Change Request history . 21g3History 22g3ETSI ETSI TS 103 280 V2.1.1 (2017-08)4 Intellectual Property Rights Essential patents IPRs essential or potentially essential to t
11、he present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is 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 ETS
12、I 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 IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the exis
13、tence 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 cl
14、aims 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
15、associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Lawful Interception (LI). It contains also the XSD technical implementation as attachment to the original document available from the ETSI site. Modal verbs terminology In the p
16、resent document “shall“, “shall not“, “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 deliverab
17、les except when used in direct citation. ETSI ETSI TS 103 280 V2.1.1 (2017-08)5 1 Scope The present document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other sp
18、ecifications to use. It is encouraged to use the present document in the development of new specifications. It is foreseen that regular maintenance of the present document is be required. As such release management requirements will be defined. Before accepting any new common parameter, the present
19、document will provide a set of requirements the parameter has to comply to in order to become a common parameter. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references,
20、 only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While an
21、y hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 ETSI TS 102 232-1: “Lawful Interception (LI); Handover Interface and Service-Spe
22、cific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery“. 2 W3C Recommendation 5 April 2012: “W3C XML Schema Definition Language (XSD)“. 3 Recommendation ITU-T X.680: “Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation“. 4 Recom
23、mendation ITU-T E.164: “The international public telecommunication numbering plan“. 5 Recommendation ITU-T E.212: “The international identification plan for public networks and subscriptions“. 6 ETSI TS 123 003: “Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommu
24、nications System (UMTS); Numbering, addressing and identification (3GPP TS 23.003)“. 7 ETSI TS 102 657: “Lawful Interception (LI); Retained data handling; Handover interface for the request and delivery of retained data“. 8 IETF RFC 791: “Internet Protocol“. 9 IETF RFC 4632: “Classless Inter-domain
25、Routing (CIDR): The Internet Address Assignment and Aggregation Plan“. 10 IETF RFC 8200: “Internet Protocol, Version 6 (IPv6) Specification“. 11 IETF RFC 4291: “IP Version 6 Addressing Architecture“. 12 IETF RFC 793: “Transmission Control Protocol“. 13 IETF RFC 768: “User Datagram Protocol“. 14 IEEE
26、 802.3TM: “IEEE Standard for Ethernet“. ETSI ETSI TS 103 280 V2.1.1 (2017-08)6 15 IETF RFC 5322: “Internet Message Format“. 16 W3C Recommendation 28 October 2014: “HTML5 A vocabulary and associated APIs for HTML and XHTML“. 17 IETF RFC 4122: “A Universally Unique IDentifier (UUID) URN Namespace“. 18
27、 ISO 3166-1: “Codes for the representation of names of countries and their subdivisions - Part 1: Country codes“. 19 IEEE Std 1003.1TM-2008: “IEEE Standard for Information Technology - Portable Operating System Interface (POSIX(R)“. 20 ISO/IEC 7812-1:2015: “Identification cards - Identification of i
28、ssuers - Part 1: Numbering system“. 21 IETF RFC 3261: “SIP: Session Initiation Protocol“. 22 IETF RFC 3966: “The tel URI for Telephone Numbers“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For
29、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
30、. 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. Not applicable. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: ASCII American Standard C
31、ode for Information Interchange ASN.1 Abstract Syntax Notation One CC Content of CommunicationCIDR Classless Inter-Domain Routing CSP Communications Service Provider HEX HEXadecimalHI Handover Interface HI1 Handover Interface port 1 (for administrative information) HI2 Handover Interface port 2 (for
32、 Intercept Related Information) HI3 Handover Interface port 3 (for Content of Communication) IMEI International Mobile station Equipment Identity IMSI International Mobile Subscriber Identity IP Internet Protocol IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 IRI Intercept Related
33、 Information ISO International Organisation for Standardisation ITU-T International Telecommunication Union - Telecommunication LEA Law Enforcement Agency LIID Lawful Interception Identifier MAC Media Access Control POSIX Portable Operating System Interface RFC Request For Comments ETSI ETSI TS 103
34、280 V2.1.1 (2017-08)7 SIP Session Initialization Protocol TCP Transmission Control Protocol UDP User Datagram Protocol URI Uniform Resource Identifier UTC Coordinated Universal Time UUID Universally Unique IDentifier XML eXtended Markup Language XSD XML Schema Definition 4 Release management This cl
35、ause describes the release management requirements. The requirements are: The version of the present document is defined as . The major version should be incremented when making a backwards incompatible change. The minor version should be incremented when adding backwards compatible functionality. T
36、he patch version should be incremented when fixing a backwards compatible bug. Once a major version has been incremented, the previous major version will be supported for 2 years after publication of the new version. Change requests issued to a version that is no longer supported will need to be iss
37、ued for the latest supported major version. 5 Parameter requirements 5.0 Introduction This clause describes the requirements a parameter should comply to in order to be specified as a common parameter. 5.1 Parameter attributes Name The parameter should be assigned a unique name. The naming conventio
38、ns used are described in clause 5.2. Description A description of the parameter should be provided. Usage guidance If there are circumstances in which additional usage guidance is applicable, use cases may be described in this attribute. References to other specifications If the parameter is specifi
39、ed in another specification (such as an RFC), a reference to that specification shall be provided. If possible, the reference should point to the exact clause or clause in the specification. EXAMPLE: Specify one or more sample values of the parameter. Technical means to define and validate the param
40、eter If possible, provide a regular expression to specify the value that is accepted by this parameter. Implementations may be required to perform additional validation on the value. The regular expressions follow the IEEE POSIX 19, section 9 regular expression format but shall be limited to the reg
41、ular expression capabilities supported by XSD 2. ETSI ETSI TS 103 280 V2.1.1 (2017-08)8 Define the parameter in the XSD 2 in section 7.1. Define the parameter in the ASN.1 3 in section 7.2. 5.2 Parameter naming conventions Allowed characters The following characters are allowed: A-Z, a-z and 0-9. Ca
42、mel casing The name of the parameter is to be CamelCased, where the first character is uppercased. Any acronyms should be uppercased. EXAMPLE: - IPv4Address. - SIPURI. - EmailAddress. 5.3 Technology conventions The used technologies defined in clause 7 may impose requirements that conflict with the
43、requirements in clauses 5.1 and 5.2. In the case of a conflict and in exceptional cases, it is allowed to deviate from the requirements above. 6 Parameter dictionary LIID Name LIID Description For each target identity related to an interception measure, the authorized CSP operator shall assign a spe
44、cial Lawful Interception IDentifier (LIID), which has been agreed between the LEA and the CSP. It is used within parameters of all HI interface ports. Using an indirect identification, pointing to a target identity makes it easier to keep the knowledge about a specific interception target limited wi
45、thin the authorized CSP operators and the handling agents at the LEA. The Lawful Interception IDentifier LIID is a component of the CC delivery procedure and of the IRI records. It shall be used within any information exchanged at the Handover Interfaces HI2 and HI3 for identification and correlatio
46、n purposes. The LIID format shall consist of alphanumeric characters. It might for example, among other information, contain a lawful authorization reference number, and the date, when the lawful authorization was issued. The authorized CSP shall either enter a unique LIID for each target identity o
47、f the interception subject or as a national option a single LIID for multiple target identities all pertaining to the same interception subject. EXAMPLE: The interception subject has a telephony service with three telephone numbers. The CSP enters for each telephone number an own LIID, or optionally
48、 enters one LIID for all three telephone numbers. If more than one LEA intercepts the same target identity, there shall be unique LIIDs assigned, relating to each LEA. Usage guidance The LIID is defined as an OCTET STRING in ASN.1. This means it is possible to use binary octets or ASCII printable ch
49、aracters to express the LIID. To correctly handle this, the parameter accepts both variations. ETSI ETSI TS 103 280 V2.1.1 (2017-08)9 References ETSI TS 102 232-1 1, clause 5.2.2. Example ZZZ123 (ASCII printable LIID) 46565527098f6bcd4621d373cade4e832627b4f6ff00ff00ff (Binary LIID, represented in HEX) Regular expression (!-1,25)|(0-9a-f26,50)$ XSD LIID, simpleType ASN.1 LIID, OCTET STRING UTCDateTime Name UTCDateTime Description A UTC timestamp with second precision. Usage guidance
