ETSI TS 132 509-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Data formats for.pdf

1、 ETSI TS 132 509 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Data formats for multi-vendor plug and play eNode B connection to the network (3GPP TS 32.509 version 14.0.0 Release 1

2、4) TECHNICAL SPECIFICATION ETSI ETSI TS 132 509 V14.0.0 (2017-04)13GPP TS 32.509 version 14.0.0 Release 14Reference RTS/TSGS-0532509ve00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017

3、- 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 made available in electronic versions and/or in print. The content of any elect

4、ronic 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 only prevailing document is the print of the Portable Document Format (PDF

5、) 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 and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliver

6、ableStatus.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

7、 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. European Telecommunications Standards Insti

8、tute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the b

9、enefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 509 V14.0.0 (2017-04)23GPP TS 32.509 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared t

10、o 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 av

11、ailable 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 S

12、R 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or repo

13、rts using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminol

14、ogy 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 ET

15、SI deliverables except when used in direct citation. ETSI ETSI TS 132 509 V14.0.0 (2017-04)33GPP TS 32.509 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviatio

16、ns . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Data formats for Multi-Vendor Plug and Connect (MvPnC) . 6g34.1 MvPnC client identification in DHCP requests 6g34.2 MvPnC entities information in DHCP replies 7g34.2.1 General 7g34.2.2 Certification Authority (CA/RA) server . 8g34.2.3 Security Gate

17、way (SeGW) 8g34.2.4 Element Manager (EM) 10g34.3 MvPnC entities Fully Qualified Domain Names (FQDN) . 11g34.3.1 General 11g34.3.2 Certification Authority (CA/RA) server . 11g34.3.3 Security Gateway (SeGW) 12g34.3.4 Element Manager (EM) 12g3Annex A (informative): Change history . 13g3History 14g3ETSI

18、 ETSI TS 132 509 V14.0.0 (2017-04)43GPP TS 32.509 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG a

19、pproval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval;

20、 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introductio

21、n The present document is part of a TS-family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management; as identified below: TS 32.501: “Self-configuration of network elements; Concepts and requirements“. TS 32.508: “Proc

22、edure flows for multi-vendor plug and play eNB connection to the network“. TS 32.509: “Data formats for multi-vendor plug and play eNB connection to the network“. ETSI ETSI TS 132 509 V14.0.0 (2017-04)53GPP TS 32.509 version 14.0.0 Release 141 Scope The present document describes the data formats us

23、ed between network entities involved in the multi-vendor plug and play eNB connection to network. These data formats are based on requirements and use cases specified in 3GPP TS 32.501 4. The procedure flows where these data exchanged are defined in 3GPP TS 32.508 5. 2 References The following docum

24、ents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - F

25、or a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Spe

26、cifications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.501: “Telecommunication management; Self-configuration of network elements; Concepts and requirements“. 5 3GPP TS 32.50

27、8: “Telecommunications management; Procedure flows for multi-vendor plug and play eNB connection to the network“. 6 3GPP TS 23.003: “Numbering, addressing and identification“. 7 IETF RFC 1035: “Domain Names - Implementation and Specification“. 8 IETF RFC 2131: “Dynamic Host Configuration Protocol“.

28、9 IETF RFC 2132: “DHCP Options and BOOTP Vendor Extensions“. 10 IETF RFC 3396: “Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)“. 11 3GPP TS 33.310: “Network Domain Security (NDS); Authentication Framework (AF)“. 12 IETF RFC 6712: “Internet X.509 Public Key Infrastructure -

29、 HTTP Transfer for the Certificate Management Protocol (CMP)“. ETSI ETSI TS 132 509 V14.0.0 (2017-04)63GPP TS 32.509 version 14.0.0 Release 143 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1, TS 32.501 4 and the

30、following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1 and in TS 32.501 4. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1, TS 32.501 4 and the following apply. An abbrev

31、iation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1 and in TS 32.501 4. 4 Data formats for Multi-Vendor Plug and Connect (MvPnC) 4.1 MvPnC client identification in DHCP requests The eNB performing the Initial IP Autoconfigurati

32、on procedure specified in clause 5.2 of 3GPP TS 32.508 5 identifies itself as MvPnC compatible DHCP client by using the Vendor Class Identifier DHCP option specified in clause 9.13 of RFC 2132 9 in the following way: - DHCP option code 60; - Length 5 bytes; - Vendor class identifier “MvPnC“. The use

33、 of Vendor Class Identifier DHCP option with specific value for MvPnC is illustrated in table 4.1.1. Table 4.1.1: Use of Vendor Class Identifier Code Length Vendor Class Identifier 60 5 M v P n C ETSI ETSI TS 132 509 V14.0.0 (2017-04)73GPP TS 32.509 version 14.0.0 Release 144.2 MvPnC entities inform

34、ation in DHCP replies 4.2.1 General The information that eNB receives from the DHCP server while performing the Initial IP Autoconfiguration procedure specified in clause 5.2 of 3GPP TS 32.508 5 may be classified in two categories: basic IP configuration and MvPnC specific configuration. The basic I

35、P configuration information is documented in RFC 2131 8 and RFC 2132 9 and may include the following: - IP address (“yiaddr“ field in 8); - Subnet Mask (option 1 in 9); - Router(s) (option 3 in 9); - IP address(es) of the DNS server(s) (option 6 in 9); - Domain Name (option 15 in 9). The MvPnC speci

36、fic configuration information is described in detail in clauses 4.2.2, 4.2.3 and 4.2.4. The DHCP option “Vendor Specific Information“ specified in the clause 8.4 of RFC 2132 9 is used as an opaque container carrying the MvPnC specific configuration from the DHCP server to the eNB performing the MvPn

37、C procedure. The multiple pieces of MvPnC specific configuration within the Vendor Specific Information container are encoded as a sequence of code/length/value fields (also known as “Encapsulated vendor-specific options“ specified in clause 8.4 of RFC 2132 9). The use of Vendor Specific Information

38、 DHCP option container with encapsulated vendor-specific options encoding is illustrated in table 4.2.1.1. Table 4.2.1.1: Use of the Vendor Specific Information Code Length 1-255 Vendor Specific Information Configuration attribute 1 Configuration attribute 2 . 43 n Type1 Lenght1 Data Type2 Length2 D

39、ata . octet octet octet octet n octets octet octet n octets . The content of the configuration attributes (specific type code value, valid length and data type) carried in the format illustrated in table 4.2.1.1 is specified in the clauses 4.2.2, 4.2.3 and 4.2.4 of the present document. If the size

40、of MvPnC configuration data contained in “Vendor Specific Information“ option 43 is greater than 255 bytes, the RFC 3396 10 encoding is used. To avoid ambiguity in the interpretation of string MvPnC configuration attributes, the ASCII character encoding shall be used. Standard network byte order sha

41、ll be used with appropriate conversion function at the eNB (matching the local little-endian / big-endian byte order). Some MvPnC configuration attributes may be missing (e.g. the SeGW FQDN attribute may be not present if the SeGW IP address is present) or just have zero length (type octet followed

42、by length octet with value zero and no data octets). The qualifiers identifying which attributes are mandatory, Optional (O), Conditional Mandatory (CM) or Conditional Optional (CO) and corresponding conditions are defined it the clauses 4.2.2, 4.2.3 and 4.2.4. The order of MvPnC configuration attri

43、butes is not important (e.g. attribute of type “1“ may appear after the attribute of type “5“). ETSI ETSI TS 132 509 V14.0.0 (2017-04)83GPP TS 32.509 version 14.0.0 Release 144.2.2 Certification Authority (CA/RA) server This clause specifies the information about Certification Authority server that

44、eNB receives from DHCP server in Initial IP Autoconfiguration procedure specified in clause 5.2 of 3GPP TS 32.508 5 and uses for Certificate Enrolment procedure. Table 4.2.2.1: CA/RA configuration attributes Attribute name Attribute tag (code) Attribute length Attribute qualifier Attribute descripti

45、on IP address of the CA/RA 01 Variable CO IP address of the CMP server. An IPv4 IP address is usually represented as 4 octets. FQDN of the CA/RA 02 Variable CO ASCII string representing the Fully Qualified Domain Name of the CMP server. In case the FQDN is used, the IP address of the DNS server need

46、s to be made available to the eNB before certificate enrolment. Port number of the CA/RA 03 Variable M Integer representing the port number used by CMP server. The port for HTTP/HTTPSs transfer of CMP messages is not explicitly given in RFC 6712 12, therefore this parameter is required. The port num

47、ber is usually represented as 2 octets. Path to the CA/RA directory 04 Variable M ASCII string representing the path to the CMP server directory. A CMP server may be located in an arbitrary path other than root. Subject name of the CA/RA 05 Variable M ASCII string representing the subject name of th

48、e CA/RA. The use is described in 3GPP TS 33.310 11 clause 9.5.3. Protocol indication 06 Variable CM ASCII string representing the protocol (HTTP or HTTPS) to be used for certificate enrolment. The use is described in 3GPP TS 33.310 11 clause 9.6. Table 4.2.2.2: Attribute constraints Name Definition

49、IP address CO qualifier The IP address is optional if the FQDN is present FQDN CO qualifier The FQDN is optional if the IP address is present Protocol indication CM qualifier The protocol indication is mandatory if HTTPS protocol is used 4.2.3 Security Gateway (SeGW) This clause specifies the information about Security Gateway server that eNB receives from DHCP server in Initial IP Autoconfiguration procedure specified in clause 5.2 of 3GPP TS 32.508 5 and uses for Establishing Secure Connection