ETSI TS 103 280 V2.3.1 (2019-04)

Lawful Interception (LI); Dictionary for common parameters

RTS/LI-00169

General Information

• Status: Published
• Publication Date: 03-Apr-2019
• Technical Committee: LI - Lawful Interception
• Current Stage: 12 - Completion
• Due Date: 12-Apr-2019
• Completion Date: 04-Apr-2019

Standards Content (Sample)

ETSI TS 103 280 V2.3.1 (2019-04)






TECHNICAL SPECIFICATION
Lawful Interception (LI);
Dictionary for common parameters



---------------------- Page: 1 ----------------------
2 ETSI TS 103 280 V2.3.1 (2019-04)



Reference
RTS/LI-00169
Keywords
dictionary, lawful interception, security
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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
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 2019.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
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.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 280 V2.3.1 (2019-04)
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 . 6
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 7
4 Release management . 7
5 Parameter requirements . 8
5.0 Introduction . 8
5.1 Parameter attributes . 8
5.2 Parameter naming conventions . 8
5.3 Technology conventions . 9
6 Parameter dictionary. 9
7 Technical implementation . 21
7.1 XSD . 21
7.2 ASN.1 . 21
Annex A (normative): XSD definition . 22
Annex B (normative): ASN.1 definition . 26
Annex C (informative): Change Request history . 28
History . 29


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 280 V2.3.1 (2019-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 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 IPR Policy, no investigation, 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.
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 present 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 deliverables except when used in direct citation.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 280 V2.3.1 (2019-04)
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 specifications 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 required. As such, release management requirements
will be defined.
Before accepting any new common parameter, the present 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, 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
https://docbox.etsi.org/Reference.
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 necessary for the application of the present document.
[1] ETSI TS 102 232-1: "Lawful Interception (LI); Handover Interface and Service-Specific Details
(SSD) for IP delivery; Part 1: Handover specification for IP delivery".
[2] W3C Recommendation 5 April 2012: "W3C XML Schema Definition Language (XSD) 1.1
Part 2: Datatypes".
[3] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[4] Recommendation 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 Telecommunications 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 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".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 280 V2.3.1 (2019-04)
TM
[14] IEEE 802.3 : "IEEE Standard for Ethernet".
[15] IETF RFC 5322: "Internet Message Format".[16] W3C Recommendation, 14 December 2017:
"HTML 5.2".
[17] IETF RFC 4122: "A Universally Unique IDentifier (UUID) URN Namespace".
[18] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions -- Part 1:
Country codes".
[19] IEEE 1003.1-2017: "IEEE Standard for Information Technology--Portable Operating System
Interface (POSIX(R)) Base Specifications, Issue 7".
[20] ISO/IEC 7812-1:2015: "Identification cards -- Identification of issuers -- Part 1: Numbering
system".
[21] IETF RFC 3261: "SIP: Session Initiation Protocol".
[22] IETF RFC 3966: "The tel URI for Telephone Numbers".
[23] NIMA Technical Report 8350.2: "Department of Defense World Geodetic System 1984, Its
Definition and Relationships With Local Geodetic Systems".
[24] ETSI TS 123 501: "5G; System architecture for the 5G System (5GS) (3GPP TS 23.501)".
[25] ETSI TS 133 501: "5G; Security architecture and procedures for 5G System (3GPP TS 33.501)".
[26] IETF RFC 7542: "The Network Access Identifier".
[27] ETSI TS 124 501: "5G; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3
(3GPP TS 24.501)".
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.
Not applicable.
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 280 V2.3.1 (2019-04)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3GPP 3 Generation Partnership Project
ASCII American Standard Code for Information Interchange
ASN.1 Abstract Syntax Notation One
CC Content of Communication
CIDR Classless Inter-Domain Routing
CSP Communications Service Provider
GPSI Generic Public Subscription Identifier
HEX HEXadecimal
HI Handover Interface
HI1 Handover Interface port 1 (for administrative information)
HI2 Handover Interface port 2 (for Intercept Related Information)
HI3 Handover Interface port 3 (for Content of Communication)
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
IEI Information Element Identifier
IETF Internet Engineering Task Force
IMEI International Mobile station Equipment Identity
IMEISV International Mobile station Equipment Identity and Software Version number
IMSI International Mobile Subscriber Identity
IP Internet Protocol
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
IRI Intercept Related Information
ISO International Organization for Standardization
ITU-T International Telecommunication Union - Telecommunication
LEA Law Enforcement Agency
LIID Lawful Interception Identifier
MAC Media Access Control
NAI Network Access Identifier
NIMA National Imagery and Mapping Agency
PEI Permanent Equipment Identifier
POSIX Portable Operating System Interface
RFC Request For Comments
SIP Session Initialization Protocol
SUCI Subscription Concealed Identifier
SUPI Subscription Permanent Identifier
TCP Transmission Control Protocol
UDP User Datagram Protocol
URI Uniform Resource Identifier
UTC Coordinated Universal Time
UUID Universally Unique IDentifier
WGS84 World Geodetic System 1984
XML eXtended Markup Language
XSD XML Schema Definition
4 Release management
This clause 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.
• The patch version should be incremented when fixing a backwards compatible bug.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 280 V2.3.1 (2019-04)
• 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
issued 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 conventions 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 specified 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 parameter
• 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 regular expression
capabilities supported by XSD [2].
• 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.
Camel casing
• The name of the parameter is to be CamelCased, where the first character is uppercased. Any acronyms should
be uppercased.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 280 V2.3.1 (2019-04)
EXAMPLE:
- IPv4Address.
- SIPURI.
- EmailAddress.
5.3 Technology conventions
The used technologies defined in clause 7 may impose requirements that conflict with the 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 special 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 within 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 correlation 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 of 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 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 characters to express the LIID. To correctly handle this, the parameter
accepts both variations.
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-f]{26,50})$
XSD LIID, simpleType
ASN.1 LIID, OCTET STRING

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 280 V2.3.1 (2019-04)
UTCDateTime
Name UTCDateTime
Description A UTC timestamp with second precision.
Usage guidance -
References W3C XML Schema Definition Language [2], section 3.3.7.
Example 2015-12-27T13:37:00Z
Regular expression ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
XSD UTCDateTime, simpleType
ASN.1 Not defined

UTCMicrosecondDateTime
Name UTCMicrosecondDateTime
Description A UTC timestamp with microsecond precision.
Usage guidance -
References W3C XML Schema Definition Language [2], section 3.3.7.
Example 2015-12-27T13:37:00.012345Z
Regular expression ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}\.[0-9]{6}Z$
XSD UTCMicrosecondDateTime, simpleType
ASN.1 Not defined

QualifiedDateTime
Name QualifiedDateTime
Description A timestamp with second precision and timezone qualifier.
Usage guidance -
References W3C XML Schema Definition Language 1.1 Part 2: Datatypes [2], section 3.3.7.
Example 2015-12-27T13:37:00+02:00
Regular expression ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(Z|[+-]
[0-9]{2}:[0-9]{2})$
XSD QualifiedDateTime, simpleType
ASN.1 QualifiedDateTime, GeneralizedTime
Timestamps shall be provided with a timezone qualifier. The fractional part of a second shall not
be present. Local time format shall not be used.

QualifiedMicrosecondDateTime
Name QualifiedMicrosecondDateTime
Description A timestamp with microsecond precision and timezone qualifier.
Usage guidance -
References W3C XML Schema Definition Language 1.1 Part 2: Datatypes [2], section 3.3.7.
Example 2015-12-27T13:37:00.012345+02:00
Regular expression ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}\.[0-9]{6}(Z|
[+-][0-9]{2}:[0-9]{2})$
XSD QualifiedMicrosecondDateTime, simpleType
ASN.1 QualifiedMicrosecondDateTime, GeneralizedTime
Timestamps shall be provided with a timezone qualifier. The fractional part of a second with no
more than 6 digits shall be present. Local time format shall not be used.

InternationalE164
Name InternationalE164
Description E.164 Number in fully international format, written as decimal digits.
Usage guidance -
References Recommendation ITU-T E.164 [4], clause 6.
Example 31612345678
Regular expression ^[0-9]{1,15}$
XSD InternationalE164, simpleType
ASN.1 NumericString (SIZE(1.15))

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 280 V2.3.1 (2019-04)
IMSI
Name IMSI
Description International Mobile Subscriber Identity, written as decimal digits.
Usage guidance -
References Recommendation ITU-T E.212 [5], clause 6.1
ETSI TS 123 003 [6], clause 2.2 and clause 2.3.
Example 204081234567890
Regular expression ^[0-9]{6,15}$
XSD IMSI, simpleType
ASN.1 NumericString (SIZE(6.15))

IMEI
Name IMEI
Description International Mobile station Equipment Identity, written as decimal digits without the Luhn check
digit, annex B of ISO/IEC 7812-1 [20].
Usage guidance To avoid implementation issues, the IMEI parameter explicitly excludes the Luhn check digit,
annex B of ISO/IEC 7812-1 [20].
(See notes 1 and 2).
References ETSI TS 123 003 [6], clause 6.
Example 35395803121326
Regular expression ^[0-9]{14}$
XSD IMEI, simpleType
ASN.1 NumericString (SIZE(14))
NOTE 1: ETSI TS 102 657 [7], clause E.3 identifies potential issues with the inclusion/exclusion of the check digit. As
such, the IMEI parameter is explicitly specified without the check digit.
NOTE 2: The IMEICheckDigit parameter can be used when the check digit is explicitly required.
IMEICheckDigit
Name IMEICheckDigit
Description International Mobile station Equipment Identity, written as decimal digits with the Luhn check
digit, annex B of ISO/IEC 7812-1 [20].
Usage guidance -
References ETSI TS 123 003 [6], clause 6.
Example 35395803121326
Regular expression ^[0-9]{15}$
XSD IMEICheckDigit, simpleType
ASN.1 NumericString (SIZE(15))

IMEISV
Name IMEISV
Description International Mobile station Equipment Identity and Software Version Number as defined in
ETSI TS 123 003 [6], clause 6.2.2, written as decimal digits including a software version
number instead of a Luhn check digit.
Usage guidance -
References ETSI TS 123 003 [6], clause 6.2.2.
Example 3539580312132601
Regular expression ^[0-9]{16}$
XSD IMEISV, simpleType
ASN.1 NumericString (SIZE(16))
IPv4Address
Name IPv4Address
Description IPv4 address, written in dotted decimal notation.
Usage guidance -
References IETF RFC 791 [8].
Example 192.0.2.1
Regular expression ^((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}(25[0-5]|2[0-4]
[0-9]|[01]?[0-9]?[0-9])$
XSD IPv4Address, simpleType
ASN.1 Not defined

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 280 V2.3.1 (2019-04)
IPv4CIDR
Name IPv4CIDR
Description IPv4 CIDR, written in dotted decimal notation followed by CIDR notation.
Usage guidance -
References IETF RFC 791 [8] and IETF RFC 4632 [9].
Example 192.0.2.0/24
Regular expression ^((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}(25[0-5]|2[0-4]
[0-9]|[01]?[0-9]?[0-9])/([1-2]?[0-9]|3[0-2])$
XSD IPv4CIDR, simpleType
ASN.1 Not defined

IPv6Address
Name IPv6Address
Description IPv6 address, written as eight groups of four hexadecimal digits separated by a colon.
Usage guidance It is recognized that IPv6 address formatting has various options. To reduce complexity in
technical implementations, the IPv6Address parameter restricts the address to the fully
uncompressed representation of the IPv6 address.
References IETF RFC 8200 [10].
Example 2001:0db8:0000:0000:0000:0000:0000:0001
Regular expression ^([0-9a-f]{4}:){7}([0-9a-f]{4})$
XSD IPv6Address, simpleType
ASN.1 Not defined

IPv6CIDR
Name IPv6CIDR
Description IPv6 CIDR, written as eight groups of four hexadecimal digits separated by a colon followed by
CIDR notation.
Usage guidance See IPv6Address parameter for usage guidance.
References IETF RFC 8200 [10], IETF RFC 4632 [9] and IETF RFC 4291 [11].
Example 2001:0db8:0000:0000:0000:0000:0000:0000/48
Regular expression ^([0-9a-f]{4}:){7}([0-9a-f]{4})/(([1-9][0-9]?)|(1[0-1][0-9])|
(12[0-8]))$
XSD IPv6CIDR, simpleType
ASN.1 Not defined

IPAddress
Name IPAddress
Description Either a IPv4Address parameter or IPv6Address parameter.
Usage guidance -
References -
Example XSD


  192.0.2.1


or

  2001:0db8:0000:0000:0000:0000:0000:0001

Regular expression -
XSD IPAddress, complexType
ASN.1 Not defined

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 280 V2.3.1 (2019-04)
IPCIDR
Name IPCIDR
Description Either a IPv4CIDR parameter or IPv6CIDR parameter.
Usage guidance -
References -
Example XSD


  192.0.2.0/24


or


  2001:0db8:0000:0000:0000:0000:0000:0000/48

Regular expression -
XSD IPCIDR, complexType
ASN.1 Not defined

TCPPort
Name TCPPort
Description TCP port, written in decimal notation.
Usage guidance -
References IETF RFC 793 [12].
Example 22
Regular expression ^([1-9][0-9]{0,3}|[1-5][0-9]{4}|6[0-4][0-9]{3}|65[0-4][0-9]{2}|
655[0-2][0-9]|6553[0-5])$
XSD TCPPort, simpleType
ASN.1 TCPPort, INTEGER

TCPPortRange
Name TCPPortRange
Description TCP port range, consists of a 'start' TCPPort parameter and an 'end' TCPPort parameter.
Usage guidance The start and end values are inclusive.
References -
Example Regular expression
1024-2048

XSD

  1024
  2048

Regular expression ^([1-9][0-9]{0,3}|[1-5][0-9]{4}|6[0-4][0-9]{3}|65[0-4][0-9]{2}|
655[0-2][0-9]|6553[0-5])-([1-9][0-9]{0,3}|[1-5][0-9]{4}|6[0-4]
[0-9]{3}|65[0-4][0-9]{2}|655[0-2][0-9]|6553[0-5])$
XSD TCPPortRange, complexType
ASN.1 TCPPortRange, SEQUENCE

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 103 280 V2.3.1 (2019-04)
UDPPort
Name UDPPort
Description UDP port, written in decimal notation.
Usage guidance -
References IETF RFC 768 [13].
Example 53
Regular expression ^([0-9]{1,4}|[1-5][0-9]{4}|6[0-4][0-9]{3}|65[0-4][0-9]{2}|655[0-2]
[0-9]|6553[0-5])$
XSD UDPPort, simpleType
ASN.1 UDPPort, INTEGER

UDPPortRange
Name UDPPortRange
Description UDP port range, consists of a 'start' UDPPort parameter and an 'end' UDPPort parameter.
Usage guidance The start and end values are inclusive.
References -
Example Regular expression
2048-4096
XSD

  2048
  4096

Regular expression ^([0-9]{1,4}|[1-5][0-9]{4}|6[0-4][0-9]{3}|65[0-4][0-9]{2}|655[0-2]
[0-9]|6553[0-5])-([0-9]{1,4}|[1-5][0-9]{4}|6[0-4][0-9]{3}|65[0-4]
[0-9]{2}|655[0-2][0-9]|6553[0-5])$
XSD UDPPortRange, complexType
ASN.1 UDPPortRange, SEQUENCE

Port
Name Port
Description Either a TCPPort parameter or a UDPPort parameter.
Usage guidance -
References -
Example XSD

  22

Regular expression ^([0-9]{1,4}|[1-5][0-9]{4}|6[0-4][0-9]{3}|65[0-4][0-9]{2}|655[0-2]
[0-9]|6553[0-5])$
XSD Port, complexType
ASN.1 Port, CHOICE

PortRange
Name PortRange
Description Either a TCPPortRange parameter or a UDPPortRange parameter.
Usage guidance The start and end values are inclusive.
References -
Example XSD

  
    2048
    4096
  

Regular expression -
XSD PortRange, complexType
ASN.1 PortRange, CHOICE

ETSI

---------------------- Page:
...