ETSI TS 132 501-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Self-configuration of network elements Concepts and requirements (V14 0 0 3G.pdf

《ETSI TS 132 501-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Self-configuration of network elements Concepts and requirements (V14 0 0 3G.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 501-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Self-configuration of network elements Concepts and requirements (V14 0 0 3G.pdf（30页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 501 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Self-configuration of network elements; Concepts and requirements (3GPP TS 32.501 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 501 V14.0.0 (2017-04)13GPP TS

2、 32.501 version 14.0.0 Release 14Reference RTS/TSGS-0532501ve00 Keywords 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 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Gras

3、se (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 wit

4、hout 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) version kept on a specific network drive within ETSI Secretariat. Users of

5、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

6、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 ETS

7、I. 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 Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo

8、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 benefit of its Members GSM and the GSM logo are Trade Marks registered and own

9、ed by the GSM Association. ETSI ETSI TS 132 501 V14.0.0 (2017-04)23GPP TS 32.501 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is public

10、ly 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 W

11、eb 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 ma

12、y 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 GSM identities. These sho

13、uld 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“, “should“, “should not“, “ma

14、y“, “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 ETSI TS 132 501 V14

15、.0.0 (2017-04)33GPP TS 32.501 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Concepts and background 7

16、g34.1 Self-Configuration Concept 7g34.1.1 Logical Function Blocs . 7g34.1.1.1 Address Allocation Function (AAF): 7g34.1.1.2 OAM Connectivity Establishment Function (OAM CO_EF): 7g34.1.1.3 Software Management Function (SW_MF): . 7g34.1.1.4 Inventory Update Function (Inv_UF): 7g34.1.1.5 Self-Test Func

17、tion (ST_F): . 7g34.1.1.6 Self-Configuration Monitoring and Management Function (SC_MMF): . 8g34.1.1.6.1 Self-Configuration Monitoring and Management Function (SC_MMF_NM): . 8g34.1.1.6.2 Self-Configuration Monitoring and Management Function (SC_MMF_EM): . 8g34.1.1.7 Call Processing Link (CPL) Set Up

18、 Function (CPL_SUF): 8g34.1.1.8 Radio Network Configuration Data Function (R_CD_F): 8g34.1.1.9 Transport Network Configuration Data Function (T_CD_F): 8g34.1.1.10 NRM IRP Update Function (NRM_UF): 8g34.1.1.11 Radio Network and Transport Network Configuration Data Preparation Function 8g34.2 Automati

19、c Radio Configuration Data handling Function (ARCF) Concept . 8 g34.2.1 Definitions 8g34.3 Multi-Vendor Plug and Play eNB connection to network Concept 9g34.3.1 General description . 9g34.3.2 Network Scenarios 9g34.3.2.1 eNB connected via a Non-Secure, Operator Controlled Network . 9 g34.3.2.2 eNB c

20、onnected via an External Network 10g34.3.2.3 eNB connection to the OAM Network and multiple CNs via separate SeGWs 10g34.3.3 Security Aspects . 11g34.3.3.1 Root Certificate Acquisition: 11g34.3.3.2 Number of CA servers 12g34.3.3.3 Number of OAM SeGWs 12g35 Business Level Requirements 13g35.1 Self- C

21、onfiguration of eNodeBs 13g35.1.1 Actor roles 13g35.1.2 Telecommunications resources . 13g35.1.3 High-level use cases 13g35.2 Business Requirements for Multi Vendor Plug and Play eNB connection to network 13g36 Specification level requirements 15g36.1 General . 15g36.2 Actor roles 15g36.3 Telecommun

22、ications resources 15g36.4 Use cases 15g36.4.1 Use case for Automatic Radio Network Configuration Data Handling 15g36.4.1.1 Use case radio network configuration data request, transfer and validity check . 15g36.4.2 Use case Self-configuration of a new eNodeB . 15g3ETSI ETSI TS 132 501 V14.0.0 (2017-

23、04)43GPP TS 32.501 version 14.0.0 Release 146.4.3 Use case Multi Vendor Plug and Connect eNB to network 18g36.5 Requirements 20g36.5.1 Automatic Radio Network Configuration Data Handling . 20g36.5.2 Self-configuration of a new eNodeB 20g36.5.2.1 Self-Configuration Management and Monitoring . 20g36.5

24、.2.1.1 Management Part . 20g36.5.2.1.2 Monitoring Part . 21g36.5.2.2 Software Management . 21g36.5.2.3 Address Allocation and OAM Connectivity Establishment 22g36.5.2.4 Inventory Update . 22g36.5.2.5 Self-Test 22g36.5.2.6 Radio Configuration Data . 22g36.5.2.7 Transport Configuration Data . 22g36.5.

25、2.8 Call Processing Link Set-Up . 22g36.5.2.9 NRM IRP Update 22g36.5.3 Specification Requirements for Multi-Vendor Plug and Play eNB connection to network 22g37. Functions and Architecture 23g37.1 Self-Configuration Logical Architecture 23g37.2 Self-Configuration Reference Model . 24g3Annex A (infor

26、mative): Graphical representation of the PnC Use Case . 25g3Annex B (informative): Change history . 28g3History 29g3ETSI ETSI TS 132 501 V14.0.0 (2017-04)53GPP TS 32.501 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP).

27、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 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

28、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 document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, update

29、s, 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-family covering the 3rdGeneration Partnership Project Technical Specification Group Services and System Aspects, Telecommunication management

30、; as identified below: 32.501: Self-Configuration of Network Elements; Concepts and Integration Reference Point (IRP) Requirements; 32.502: Self-Configuration of Network Elements Integration Reference Point (IRP); Information Service (IS); 32.506: Self-Configuration of Network Elements Integration R

31、eference Point (IRP); Solution Set (SS) definitions. ETSI ETSI TS 132 501 V14.0.0 (2017-04)63GPP TS 32.501 version 14.0.0 Release 141 Scope The present document describes the concepts how self-configuration works and what IRP requirements need to be met to support this functionality. The document al

32、so captures if a requirement shall be met via the Itf-N interface or via other protocols. This version of the TS is restricted to self-configuration of eNBs. The requirements in this document are not imposed on HNBs. 2 References The following documents contain provisions which, through reference in

33、 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 version app

34、lies. 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: “Telecommunication

35、management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TR 32.816: “Telecommunication management; Study on Management of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core (EPC)“. 5 3GPP TS 32.531:

36、“Telecommunication management; Architecture; Software Management Concepts and IRP Requirements “. 6 ITU-T Recommendation X.800: “Security architecture for Open Systems Interconnection for CCITT applications“. 7 3GPP TS 33.310: “ Network Domain Security (NDS); Authentication Framework (AF)“. 3 Defini

37、tions and abbreviations For the purposes of the present document, the terms and definitions given in TS 32.101 2, TS 32.102 3 and TS 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TS 32.101 1, TS 32.102 2 and

38、 TS 21.905 5, in that order. 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the 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. Credentials: Data that

39、is transferred to establish the claimed identity of an entity, see ITU-T Recommendation X.800 6. Plug and Play: The process of connecting a minimally preconfigured node to the transport network, whereby the node, with minimum operator attention, can exchange information with the OAM system and other

40、 relevant nodes to an extent that the node is configured and ready to handle traffic. Plug and Connect: The procedure by which an eNodeB gets basic connectivity information after it is powered up and gets connected to its EM system in a multi-vendor environment. Multi-vendor Plug and Connect is part

41、 of the Multi-Vendor Plug and Play. ETSI ETSI TS 132 501 V14.0.0 (2017-04)73GPP TS 32.501 version 14.0.0 Release 14Self Configuration: The process which brings a network element into service requiring minimal human operator intervention or none at all. 3.2 Abbreviations For the purposes of the prese

42、nt document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. CA Certification Authority CMP Certificate Management Protocol DHCP Dynamic Host Configu

43、ration Protocol DNS Doman Name System EM Element ManagerFQDN Fully Qualified Domain Name IP IP address MvPnC Multi-vendor Plug and Connect MvPnP Multi-vendor Plug and Play NAT Network Address Translation PnC Plug and Connect PnP Plug and Play RA Registration Authority SC Self Configuration SeGW Secu

44、rity Gateway TLS Transport Layer Security VLAN Virtual LAN VM Vendor Mediator4 Concepts and background Provide here an update of See TS 32.816 4 5.1.3.1.1 “Establishment of new eNodeB in network” 4.1 Self-Configuration Concept 4.1.1 Logical Function Blocs 4.1.1.1 Address Allocation Function (AAF): T

45、his functional bloc supports the following functions: SC1, SC3. 4.1.1.2 OAM Connectivity Establishment Function (OAM CO_EF): This functional bloc supports the following functions: SC2, SC3, SC4, SC5, SC13. 4.1.1.3 Software Management Function (SW_MF): This functional bloc supports the following func

46、tions: SC3, SC6, SC7, SC8, SC20, SC21. 4.1.1.4 Inventory Update Function (Inv_UF): This functional bloc supports the following functions: SC16. 4.1.1.5 Self-Test Function (ST_F): This functional bloc supports the following functions: SC17. ETSI ETSI TS 132 501 V14.0.0 (2017-04)83GPP TS 32.501 versio

47、n 14.0.0 Release 14This function performs eNodeB self-tests. 4.1.1.6 Self-Configuration Monitoring and Management Function (SC_MMF): This functional bloc supports the following functions: SC18. This function monitors the self-configuration process and provides the operator with this information. Thi

48、s function must be able to get information about all other functional blocs. In addition to this it allows the operator to control the execution of the self-configuration process. 4.1.1.6.1 Self-Configuration Monitoring and Management Function (SC_MMF_NM): SC_MMF_NM (IRP Manager): representing the N

49、M portion of SC_MMF (necessary monitoring and limited interaction capabilities to support an automated optimization), as well as related IRPManager functionality 4.1.1.6.2 Self-Configuration Monitoring and Management Function (SC_MMF_EM): SC_MMF_EM (IRP Agent): representing the portion of SC_MMF operating below Itf-N, as well as related IRPAgent functionality 4.1.1.7 Call Processing Link (CPL) Set Up Function (CPL_SUF): This functional bloc supports the following functions: SC14, SC15. 4.1.1.8 Radio