1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommProcedure flowseNode B c(3GPP TS 32.5TECHNICAL SPECIFICATION132 508 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; s for multi-vendor plug-and-pconnection to the network .508 version 13.0.0 Rel
2、ease 1316-02) hase 2+); (UMTS); lay 13) ETSI ETSI TS 132 508 V13.0.0 (2016-02)13GPP TS 32.508 version 13.0.0 Release 13Reference RTS/TSGS-0532508vd00 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 6
3、23 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 made available in electronic versions and/or in print. The content
4、 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 only prevailing document is the print of the Portable Documen
5、t 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 and other ETSI documents is available at http:/portal.etsi.org/tb
6、/status/status.asp 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, includ
7、ing 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 In
8、stitute 2016. 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. GSM and the GSM logo are Trade
9、Marks registered and owned by the GSM Association. ETSI ETSI TS 132 508 V13.0.0 (2016-02)23GPP TS 32.508 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential
10、 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
11、 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) whi
12、ch 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 reports using their 3GPP identities, UMTS identities or G
13、SM 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 terminology In the present document “shall“, “shall not“, “sh
14、ould“, “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.
15、ETSI ETSI TS 132 508 V13.0.0 (2016-02)33GPP TS 32.508 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 A
16、rchitecture for multi-vendor plug-and-play . 6g34.1 Functional architecture . 6g34.2 Functional elements 6g34.2.1 IP Autoconfiguration services. 6g34.2.2 DNS server 6g34.2.3 Certification Authority server . 6g34.2.4 Element Manager (EM) 7g34.2.5 Security Gateway (SeGW) 7g35 Procedure flows 8g35.1 Hi
17、gh-level plug-and-connect 8g35.2 Initial IP Autoconfiguration . 11g35.3 Certificate enrolment 13g35.4 Establishing secure connection. 15g35.5 Establishing connection to Element Manager (EM) . 17g3Annex A (informative): Change history . 20g3History 21g3ETSI ETSI TS 132 508 V13.0.0 (2016-02)43GPP TS 3
18、2.508 version 13.0.0 Release 13Foreword 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 approval. Should the TSG modify the contents
19、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; 3 or greater indicates TSG approved documen
20、t 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. Introduction The present document is part of a TS-famil
21、y covering the 3rdGeneration 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: “Procedure flows for multi-vendor plug-and-play eN
22、B connection to the network“. TS 32.509: “Data format for multi-vendor plug-and-play eNB connection to the network“. ETSI ETSI TS 132 508 V13.0.0 (2016-02)53GPP TS 32.508 version 13.0.0 Release 131 Scope The present document describes the procedure flows between network entities involved in the mult
23、i-vendor plug-and-play eNB connection to network. These procedures are based on requirements and use cases specified in 3GPP TS 32.501 4. The format of the data exchanged in these procedures is defined in 3GPP TS 32.509 5. 2 References The following documents contain provisions which, through refere
24、nce 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. - For a non-specific reference, the latest versi
25、on 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 Specifications“. 2 3GPP TS 32.101: “Telecommunic
26、ation 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.509: “Telecommunications management; Data forma
27、t for multi-vendor plug-and-play eNB connection to the network“. 3 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 following apply. A term defined in the present document takes precedence over
28、 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 abbreviation defined in the present document takes precedence over the definition o
29、f the same abbreviation, if any, in TR 21.905 1 and in TS 32.501 4. ETSI ETSI TS 132 508 V13.0.0 (2016-02)63GPP TS 32.508 version 13.0.0 Release 134 Architecture for multi-vendor plug-and-play 4.1 Functional architecture The functional architecture for multi-vendor plug-and-play connection of eNB to
30、 the network is described in 3GPP TS 32.501 4 clause 4.3.2. It covers the scenarios where eNB is connected to the Secure Operator Network either via an External Network or via a Non-Secure Operator Network. The entities (functional elements) involved in the PnC are listed and described in detail in
31、clause 4.2. 4.2 Functional elements 4.2.1 IP Autoconfiguration services The IP Autoconfiguration services such as DHCP servers and Router Advertisements are used primarily to provide the eNB with basic IP configuration information (e.g. IP address, netmask, default gateway, domain name, IP address(e
32、s) of DNS servers, time servers). IP Autoconfiguration services may recognize the eNB as a client (using, for example, the vendor class identifier DHCP option) and provide with information such as IP address or FQDN of CA/RA server, IP address or FQDN of SeGW, IP address or FQDN of EM, etc. The spec
33、ific data formats used by IP Autoconfiguration services for multi-vendor plug-and-play procedures are described in 3GPP TS 32.509 5. From the multi-vendor plug-and-play feature perspective, the IP Autoconfiguration services may be categorized into secure (those located within a Secure Operator Netwo
34、rk) and public (those located either within a Non-Secure Operator Network or within an External Network). 4.2.2 DNS server DNS servers are used to resolve FQDNs into IP addresses. The FQDNs used for multi-vendor plug-and-play may be factory programmed, provided by IP Autoconfiguration services, conf
35、igured by EM, or derived/generated within the eNB using the vendor information, operator network domain name and name of the functional element. The specific FQDN formats used in multi-vendor plug-and-play procedures are described in 3GPP TS 32.509 5. From the multi-vendor plug-and-play feature pers
36、pective, the DNS servers may be categorized into secure (those located within a Secure Operator Network) and public (those located either within a Non-Secure Operator Network or within an External Network). The DNS server is an optional functional element and is only required if particular Operator
37、deployment scenario relies on resolution of FQDNs (e.g. FQDNs are configured at the IP Autoconfiguration services, eNB and/or EM, while IP addresses are configured at DNS servers). 4.2.3 Certification Authority server The Certification Authority server (CA/RA) is used in the in the multi-vendor plug
38、-and-play procedures for security certificate enrolment (e.g. to provision operator certificates at the eNB using the factory-installed vendor certificates). There could be one or more CA/RA depending on a particular operator deployment scenario (e.g. one CA/RA per vendor). ETSI ETSI TS 132 508 V13.
39、0.0 (2016-02)73GPP TS 32.508 version 13.0.0 Release 134.2.4 Element Manager (EM) The EM is a vendor-specific functional element that is used in multi-vendor plug-and-play procedures to provide the eNB with correct software and configuration information. There could be one or more EM depending on a p
40、articular Operator deployment scenario (e.g. initial EM, serving EM). The configuration may contain an IP address or FQDN of (another) EM that this specific eNB shall use as EM. The configuration may contain an IP address or FQDN of (another) SeGW that should be used before connecting to the EM. 4.2
41、.5 Security Gateway (SeGW) The SeGW is used to establish a secure connection between the eNB and the Secure Operator Network. Depending on a particular operator deployment scenario, there could be separate SeGW for connection to the OAM network and to the CN. The OAM SeGW and CN SeGW may or may not
42、be in practice separate physical entities. Depending on a particular operator deployment scenario, there could be more than one OAM SeGW (e.g. one per vendor). ETSI ETSI TS 132 508 V13.0.0 (2016-02)83GPP TS 32.508 version 13.0.0 Release 135 Procedure flows 5.1 High-level plug-and-connect The high le
43、vel procedure for “multi-vendor plug-and connect“ is described next and illustrated in figure 5.1-1. Operators may deploy their management infrastructure in different ways. The following options are possible: - One or multiple EMs for each vendor (e.g. an Initial EM and zero or more Serving EMs); -
44、One or more SeGW (e.g. one SeGW for OAM and one or more for each CN, and/or one SeGW per vendor); - Zero or more IP Autoconfiguration services in the Secure Operator Network; - Zero or more DNS servers in the Secure Operator Network; - One or more IP Autoconfiguration services in the External Networ
45、k / non-Secure Operator Network; - Zero or more DNS servers in the External Network / non-Secure Operator Network; - One or more CA/RA (e.g. one per vendor). The procedure described in this clause applies to all deployment options listed above. The procedure begins when the eNB is powered up and end
46、s when all mandatory steps in this procedure are completed or when an exception occurs. The pre-conditions for this procedure are: - The eNB is physically installed; - IP connectivity exists between involved telecom resources (functional elements listed in clause 4.2); - The involved telecom resourc
47、es (functional elements listed in clause 4.2) are functional; - The relevant information is stored and available. The post-conditions for this procedure are: - One or more secure connection exists between eNB and EM and the Core Network(s); - Via the connection to the EM the eNB can receive further
48、instructions to become operational and carry user traffic (e.g. the administrativeState is set to “unlocked“). The exceptions: - One of the steps outlined in the procedure fails. Procedure steps: 1) If a VLAN ID is available the eNB uses it. Otherwise the eNB uses the native VLAN where PnP traffic i
49、s sent and received untagged. 2) In this step eNB invokes the “Initial IP Autoconfiguration“ procedure (described in clause 5.2) and acquires its IP address through stateful or stateless IP Autoconfiguration. There may be additional information provided to the eNB. 3) In this step eNB invokes the “Certificate Enrolment“ procedure (described in clause 5.3). 4) In this step eNB invokes the “Establishing Secure Connection“ procedure (described in clause 5.4) and connects to the OAM SeGW. 5) In this step eNB invokes the “Establishing Connection
