ETSI TS 132 600-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf

1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommConfiguraConcept an(3GPP TS 32.6TECHNICAL SPECIFICATION132 600 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; ration Management (CM); and high-level requirements .600 version 13.0.0 Release 131

2、6-02) hase 2+); (UMTS); 13) ETSI ETSI TS 132 600 V13.0.0 (2016-02)13GPP TS 32.600 version 13.0.0 Release 13Reference RTS/TSGS-0532600vd00 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 elec

4、tronic 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 (PD

5、F) 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/status/stat

6、us.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, including photocop

7、ying 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 Institute 2016

8、. 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 Marks regist

9、ered and owned by the GSM Association. ETSI ETSI TS 132 600 V13.0.0 (2016-02)23GPP TS 32.600 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 IPRs, if an

10、y, 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 o

11、n 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 m

12、ay 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 GSM identitie

13、s. 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“, “should“, “shou

14、ld 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 ETSI TS

15、 132 600 V13.0.0 (2016-02)33GPP TS 32.600 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Network Confi

16、guration Management (CM) . 7g34.1 General . 7g34.1.1 Installing a PLMN network 7g34.1.2 Operating a PLMN network 8g34.1.3 Growing/pruning a PLMN network 8g34.1.3.1 System up-date 8g34.1.3.2 System up-grade 8g34.2 Operational context for CM 9g34.2.1 Administrative aspects of CM 9g34.2.1.1 Security as

17、pects . 9g34.2.1.2 Data validity 9g34.2.1.3 Data consistency and distribution of the MIB . 9g35 CM service components . 12g35.1 System modification service component 12g35.2 System monitoring service component. 13g36 CM functions 13g36.1 System modification functions . 13g36.1.1 Creation of NEs and

18、NRs 14g36.1.2 Deletion of NEs and NRs 14g36.1.3 Conditioning of NEs and NRs 14g36.1.3.1 Considerations on conditioning mechanisms 15g36.1.3.2 Network traffic considerations 15g36.2 System monitoring functions 16g36.2.1 Information request function. 16g36.2.2 Information report function. 16g36.2.3 Re

19、sponse/report control function 16g37 Itf-N Interface . 17g37.1 CM principles . 17g37.2 Overview of IRPs related to CM 18g37.3 Kernel CM 18g37.4 Basic CM 19g37.4.1 Passive CM Retrieval/synchronisation of CM-related information . 19g37.4.2 Active CM 19g37.5 Bulk CM . 19g37.6 Common CM and NRM IRP Requ

20、irements . 20g37.6.1 General 20g3Annex A: Change history 21g3History 22g3ETSI ETSI TS 132 600 V13.0.0 (2016-02)43GPP TS 32.600 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 su

21、bject 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 as follows: Version x.y.z where: x the firs

22、t 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, updates, etc. z the third digit is incremented wh

23、en editorial only changes have been incorporated in the document. Introduction Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the PLMN network as it evolves. CM actions have the objective to control and monitor the actua

24、l configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs. CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation p

25、rogramme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as single actions on single NEs of the PLMN network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs. Clauses 4 to 6 give an in

26、troduction and description of the main concepts of CM, which are not mandatory for compliance with this specification. Clause 7 contains the specific definitions for the standardised interface Itf-N, which are necessary to follow for compliance. Clause 4 provides a brief background of CM, while Clau

27、se 5 explains CM services available to the operator. Clause 6 breaks these services down into individual CM functions, which support the defined services. Clause 7 defines the Itf-N (see 3GPP TS 32.102 2) to be used for CM. ETSI ETSI TS 132 600 V13.0.0 (2016-02)53GPP TS 32.600 version 13.0.0 Release

28、 131 Scope The present document describes the Configuration Management (CM) aspects of managing a PLMN network. This is described from the management perspective in 3GPP TS 32.101 1 and 3GPP TS 32.102 2. The present document defines a set of controls to be employed to effect set-up and changes to a

29、PLMN network in such a way that operational capability and Quality Of Service (QOS), network integrity and system inter working are ensured. In this way, the present document describes the interface definition and behaviour for the management of relevant NEs in the context of the described managemen

30、t environment. The context is described for both the management system (OS) and Network Element (NE) functionality. Clause 7 contains the specific definitions for the standardised Itf-N, which are necessary to follow for compliance to this specification. The Itf-N for CM is built up by a number of I

31、ntegration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.150 9. For CM, a number of IRPs (and a Name Convention 8) are defined, used by this as well as by other specificat

32、ions for Telecom Management produced by 3GPP. 2 References The following documents 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-

33、specific. For a specific reference, subsequent revisions do not apply. For 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 Rel

34、ease as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integratio

35、n Reference Point (IRP): Network Resource Model (NRM)“. 4 ITU-T Recommendation X.721: “Information technology - Open Systems Interconnection - Structure of management information: Definition of management information“. 5 ITU-T Recommendation X.730: “Information technology - Open Systems Interconnect

36、ion - Systems Management: Object Management Function“. 6 ITU-T Recommendation X.731: “Information technology - Open Systems Interconnection - Systems Management: State management function“. 7 ITU-T Recommendation X.734: “Information technology - Open Systems Interconnection - Systems Management: Eve

37、nt report management function“. 8 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 9 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. ETSI ETSI TS 132 600 V13.0.0 (2016-02)63G

38、PP TS 32.600 version 13.0.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. For terms and definitions not found here, please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2 and 3GPP TS 32.150 9. Data: is any i

39、nformation or set of information required to give software or equipment or combinations thereof a specific state of functionality. Element Manager (EM): See 3GPP TS 32.101 1. Firmware: is a term used in contrast to software to identify the hard-coded program, which is not downloadable on the system.

40、 Hardware: is each and every tangible item. Managed Object (MO): See 3GPP TS 32.150 9. Managed Object Class (MOC): See 3GPP TS 32.150 9. Managed Object Instance (MOI): See 3GPP TS 32.150 9. Management Information Base (MIB): the set of existing managed objects in a management domain, together with t

41、heir attributes, constitutes that management domains MIB. The MIB may be distributed over several OS/NEs. Network Element (NE): See 3GPP TS 32.101 1. Network Manager (NM): See 3GPP TS 32.101 1. Network Resource (NR): is a component of a NE, which can be identified as a discrete separate entity and i

42、s in an object oriented environment for the purpose of management represented by an abstract entity called Managed Object (MO). Object Management Group (OMG): see http:/www.omg.org. Operations System (OS): indicates a generic management system, independent of its location level within the management

43、 hierarchy. Operator: is either a human being controlling and managing the network; or a company running a network (the PLMN network operator). Optimisation: of the network is each up-date or modification to improve the network handling and/or to enhance subscriber satisfaction. The aim is to maximi

44、se the performance of the system. Re-configuration: is the re-arrangement of the parts, hardware and/or software that make up the PLMN network. A re-configuration can be of the parts of a single NE or can be the re-arrangement of the NEs themselves, as the parts of the PLMN network. A re-configurati

45、on may be triggered by a human operator or by the system itself. Reversion: is a procedure by which a configuration, which existed before changes were made, is restored. Software: is a term used in contrast to firmware to refer to all programs which can be loaded to and used in a particular system.

46、Up-Dates: generally consist of software, firmware, equipment and hardware, designed only to consolidate one or more modifications to counter-act errors. As such, they do not offer new facilities or features and only apply to existing NEs. Up-Grades: can be of the following types: enhancement - the a

47、ddition of new features or facilities to the PLMN network; ETSI ETSI TS 132 600 V13.0.0 (2016-02)73GPP TS 32.600 version 13.0.0 Release 13 extension - the addition of replicas of existing entities. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Conf

48、iguration Management CORBA Common Object Request Broker Architecture EM Element Manager FM Fault ManagementFW FirmwareHW Hardware IOC Information Object Class IRP Integration Reference Point ITU-T International Telecommunication Union, Telecommunication Standardisation Sector MIB Management Informat

49、ion Base MOC Managed Object Class MOI Managed Object Instance NE Network Element NM Network ManagerNR Network Resource NRM Network Resource Model OMG Object Management Group OS Operations System OSF Operations System Function PM Performance Management RNC Radio Network Controller SW Software TM Telecom Management TRX Transceiver UML Unified Modelling Language (OMG) 4 Network Configuration Management (CM) 4.1 General In the development of a PLMN network, three general phases can be described which represent diffe