ETSI GSM 12 06-1994 European Digital Cellular Telecommunications System (Phase 2) Network Configuration Management《欧洲数字蜂窝通信系统(第2阶段) 网络配置管理》.pdf

《ETSI GSM 12 06-1994 European Digital Cellular Telecommunications System (Phase 2) Network Configuration Management《欧洲数字蜂窝通信系统(第2阶段) 网络配置管理》.pdf》由会员分享，可在线阅读，更多相关《ETSI GSM 12 06-1994 European Digital Cellular Telecommunications System (Phase 2) Network Configuration Management《欧洲数字蜂窝通信系统(第2阶段) 网络配置管理》.pdf（50页珍藏版）》请在麦多课文档分享上搜索。

1、Released: July 1994 GSM 12.06 Version: , 4.0.0 Date: 1 July, 1994 Work Item No: Key words: European digital cellular telecommunications system (phase 2); Network Configuration Management ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cede

2、x - FRANCE Office address: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Tel.: +33 92 94 42 O0 - Fax: +33 93 65 47 16 This is an unpublished work the copyright in which vests in the European Telecommunications Standards Institute. All rights reserved. The information contained herein is

3、the property of ETSI and no part may be reproduced or used except as authorised by contract or other written permission. The copyright and the foregoing restriction on reproduction and use extend to all media in which the information may be embodied. . . _- _i - . - m 3404583 OLL87L5 568 m Page 3 GS

4、M 12.06 version 4.0.0 Contents Foreword . 7 Introduction 7 1 scope 9 2 Normative references . 9 3 Definitions. symbols and abbreviations 10 3.2 Symbols 1 0 3.3 Abbreviations 11 3.1 Definitions . 10 4 Network configuration management . 12 4.1 General . 12 Installing a PLMN 12 Operating a PLMN . 12 4.

5、1.3.1 System update . 12 4.1.3.2 System upgrade . 13 Operational context for configuration management . 13 4.2.1 Administrative aspects of configuration management 14 4.2.1 . 1 Security aspects 14 4.2.1.2 Data validity 14 4.2.1.3 Data consistency . 14 4.2.1.4 Resource administration . 16 Configurati

6、on management triggers . 17 4.1.1 4.1.2 4.1.3 Growingpruning a PLMN . 12 4.2 4.2.2 5 Configuration management service components 18 5.1 System modification service component . 18 5.2 System monitoring service component 19 Configuration management functions . 20 System modification functions . 20 Cre

7、ation of network elements and network resources 20 Conditioning of network elements and network resources 21 System monitoring functions . 23 Information request function 23 Information report function . 23 Responseheport control function . 23 6 6.1 6.1.1 6.1.2 6.1.3 Deletion of network elements and

8、 network resources . 21 6.1.3.1 Considerations on conditioning mechanisms . 21 6.1.3.2 Network traffic considerations . 22 6.2 6.2.1 6.2.2 6.2.3 . 7 BSS configuration management . 24 Definition of equipment 24 7.1 2.1 7.1.2.2 Equipment utilisation management . 25 7.1 2.3 7.1 Equipment management . 2

9、4 Equipment management functions 25 Equipment availability management . 25 Equipment identification 25 7.1.2.4 Equipment redundancy . 26 7.1.1 7.1.2 Previous page is blank . _- . 3404583 OLL87Lb 4T4 Page 4 GSM 12.06 version 4.0.0 Overload protection 26 7.1 2.5 Replaceability . 26 7.1 2.6 7.1 2.7 Com

10、patibility . 27 7.2 Software management 27 Definition of software . 27 Software management functions . 27 7.2.2.1 Receive the software delivery . 28 7.2.2.2 Transfer the software to the network element 28 7.2.2.3 Identification of the software package . 28 7.2.2.4 Construct a loadable form of the so

11、ftware . 29 7.2.2.5 Load the software and execute . 29 7.2.2.6 Manage the local storage of software 29 Logical configuration management 30 7.3.1 Definition of logical configuration., . 30 7.3.2 Logical parameter management requirements . 30 7.3.2.1 Create initial data elements and values 30 7.3.2.2

12、Modify data values . 31 7.3.2.3 Delete data elements 31 7.3.2.4 Read data values 31 Logical functionality management requirements 32 7.3.3.1 Enabling functionality 33 7.3.3.2 Disabling functionality . 33 7.3.3.3 Cell configuration management function . 33 7.3.3.4 Adjacent cell configuration manageme

13、nt function . 34 7.3.3.5 Power control management function . 34 7.3.3.6 Handover control management function . 35 7.3.3.7 Frequency control management function 35 7.3.3.8 ProtocoVtimer control management function . 36 7 * 3.3.9 Functional building block management . 36 7.4 Modelling notes . 36 Annex

14、 A (informative): Examples of management procedures 38 A . 1 Network element and network resource management examples . 38 A.l . 1 A.1.2 Network resource creation scenario (BTS) . 43 A.1.3 Network resource deletion scenario (TRX) . 44 A.1.4 Network resource deletion scenario (BTS) . 45 Network eleme

15、nt and network resource conditioning examples . 46 A.2.1 Network elemennetwork resource conditioning scenario without traffic A.2.2 Network elementlnetwork resource conditioning scenario with throughput A.2.3 Network elemennetwork resource conditioning scenario with traffic A.2.4 Network elemennetwo

16、rk resource conditioning scenario with traffic impact on multiple network elementdnetwork resources . 49 7.2.1 7.2.2 7.3 7.3.3 Network resource creation scenario (TRX) . 38 A.2 impact . 46 impact . 47 impact on one network elementlnetwork resource . 48 Annex B (informative): Bibliography . 50 Regist

17、er . 51 . History . 53 Figure 1 : Figure 2: Figure 3: Figure 4: Figure 5: Figure 6: Figure 7: Figure 8: Figure 9: Figure 10: - - - _. 3404583 OLL87L7 330 = Page 5 GSM 12.06 version 4.0.0 Figures NE - OS data relationship . 16 Detailed flow chart on Network Resource Creation . 40 Network Resource Cre

18、ation (TRX) . 43 Network Resource Creation (BTS) 44 Network Resource Deletion (TRX) . . 45 Network Resource Deletion (BTS) . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 NUNR Conditioning Scenario without traffic impact . 47 NENR Conditioning Scenario with throughput impac

19、t 48 NUNR Conditioning Scenario with traffic impact on one NUNR 49 NUNR Conditioning Scenario with traffic impact on multiple NEdNRs . SO _I I_ - ._ - m 3404583 0338738 277 m Page 7 GSM 12.06 version 4.0.0 Foreword To be drafied by the ETSI Secretariat. Introduction Configuration Management (CM), in

20、 general, provides the operator with the ability to perform effective network management as the PLMN evolves. CM is initiated by the operator in various network elements of the PLMN to meet the operator objectives. CM actions may be requested as part of an implementation programme (ag. additions and

21、 deletions), as part of an optirnication programme (ag. modifications), and to maintain the overall Quality of Service. The CM actions are initiated either as a direct action on a network element of the PLMN or as part of a complex procedure involving actions on many network elements. Chapter 4 will

22、 provide a brief background of CM while Chapter 5 will explain CM services available to the operator. Chapter 6 will break these services down into individual CM functions which will support the defined services. Chapter 7 describes the application of these services and functions to the BSS NE in a

23、GSM PLMN. In Annex A there are informative examples to illustrate the combination of CM functions to completed scenarios. Previous page is blank _ _- -l_l_ - _ - _ W 3404583 OLL8720 925 = Page 9 GSM 12.06 version 4.0.0 1 Scope GSM 12.06 describes the CM aspects of NEs which conHitute a PLMN with ini

24、tial emphasis on the BSS management. This is described from a management perspective being decomposed into constituent functionalities, which in turn will allow the construction of a management object model using the object oriented paradigm to support open systems management (see 14). The specifica

25、tion will follow the methodology described in lo. GSM 12.06 defines a set of controls to be employed to effect Set-up and changes to a PLMN, in such a way that operational capability, network integrity and inter working co-operation are ensured. In this way, GSM 12.06 describes the interface behavio

26、ur for the management of PLMN NEs in the context of the described management environment. The context is described for both the OS and NE functionality. The standardisation of specific controls is outside of the scope of this specification. 2 Nonnative references This ETS incorporates by dated or un

27、dated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references subsequent amendments to, or revisions of, any of these publications apply to this ETS only when incorporate

28、d in it by amendment or revision. For undated references the latest edition of the publication referred to applies. Ref. No. Title 1 GSM O1 .4, Vocabulary In A GSM PLMN. Pl GSM 04.06, MS-BSS Data Link Layer Specification. 31 GSM 04.08, Mobile Radio Interface Layer 3 Specification. *- 141 GSM 05.02,

29、Multiplexing and Multiple Access on the Radio Path. 151 GSM 05.05, Transmission and Reception. 161 GSM 05.08, Radio SubSystem Link Control. m GSM 08.08, Mobile Switching Centre (MSC) to Base Station System (BSS) Interface; Layer 3 Specification. Pl GSM 08.52, BSC-BTS Layer 2 Specification. QI GSM 08

30、.58, BSC-BTS Layer 3 Specification. 1 o1 GSM 12.00, Objectives and Structure of GSM PLMN Management. u11 GSM 12.01 , Common Aspects of PLMN Network Management. i121 GSM 12.03, Security Management. i 31 GSM 12.04, Performance Management and Measurements for a GSM PLMN. 11 41 GSM 12.20, BSS Management

31、 Information. i 51 CCITT RecX.721 , Definition of Management Information (ISO/IEC 10165-1). CCITT Rec. X.731 , State Management Function for CCIlT Applications (ISO/IEC 10164-2) Previous page is blank . Page 10 GSM 12.06 version 4.0.0 3 Definitions, symbols and abbreviations 3.1 Definitions Data: is

32、 any information or set of information required to give software or equipment or combinations thereof a specific state of funclionality. Equipment: is one or more hardware items which correspond to a manageable or supervisable unit or is described in an equipment model. Firmware: is a term used in c

33、ontrast to software to identify the hard-coded program which is not Hardware: is each and every tangible item. . downloadable on the system. Network Element: is a discrete telecommunications entity which can be managed over a specific interface e.g. the BSS. Network Resource: is a component of a Net

34、work Element which can be identified as a discrete separate unit e.g. BSC, BTS or TRX . Operator: is either * * a human being controlling and managing the network ; or, a company running a network (the PLMN operator). Optimisation: of the network is each update or modification to improve the network

35、 handling and/or to enhance subscriber satisfaction. The aim is to maximise the performance of the system. Reconfiguration: is the re-arrangement of the parts, hardware and/or software that make up the PLMN. A re-configuration can be of the parts of a single NE or can be the re-arrangement of the NE

36、s themselves, as the parts of the PLMN. 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. Up-Dates: generally consi

37、st 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: Q Q enhancement - the addition of new featur

38、es or facilities to the PLMN; extension - the addition of replicas of existing entities. 3.2 Symbols None Page 11 GSM 12.06 version 4.0.0 3.3 Abbreviations For basic abbreviations: refer to l BSIC CM FM FW HW MIB MOC NE NR os sw TRX Base Station Identification Code Configuration Management Fault Man

39、agement Firmware Hardware Management Information Base Managed Object Class Network Element Network Resource Operation System SoAvare Transceiver - _ _ 1-3404583 EL8722 7TB = Page 12 GSM 12.06 version 4.0.0 4 Network configuration management 4.1 General In the development of a PLMN, three general pha

40、ses can be described which represent different degrees of stability. Once the first stage is over the system will cycle between the second and the third phase. This is known as the network life-cycle and includes: I. the PLMN will be installed and put into service; 2. the PLMN reaches certain stabil

41、ity and is only modified (dynamically) to satisfy short term requirements, e.g. by (dynamic) re-configuration of resources or parameter modification; the stable state of a PLMN cannot be regarded as the final one because each equipment or SW modification will let the PLMN progress to an unstable sta

42、te and require optimisation actions again; 3. the PLMN is being adjusted to meet the long term requirements of the network operator and the customer, e.g. with regard to performance, capacity and customer satisfaction through the enhancement of the network or equipment upgrade. During these phases,

43、the operators will require adequate management fundions to perform the necessary tasks. 4.1.1 Installing a PLMN When a PLMN is installed and initialised for the first time, all NEs need to be introduced to the OS, the data for initialisation and SW for proper functioning need to be provided. All the

44、se actions are carried out to create NEs and to initialise them. 4.1.2 Operating a PLMN _- Whilst in service, the operator will need to react to short term incidents such as traffic load requirements which are different from the current network capabilities, NEs/NRs need to be re-configured and para

45、meters need to be adapted to follow these day-to-day requirements. 4.1.3 Growingpntning a PLMN As the PLMN grows and matures new equipment is installed and understanding of system behaviour increases. Subscriber requirementshvishes may demand that operators modify their system. In addition. manufact

46、urers improve the infrastructure components and add features to their products hence the operator will start modifying the PLMN to proM from these modifications and to improve subscriber satisfaction. Additionally, the PLMN configuration will be modified (.e. it will be updated or upgraded) to cope

47、with a need for increasing or decreasing network capacity. These actions are carried out for the long term strategy of the operators to optimise the network. 4.1 3.1 System update Whenever the PLMN needs to be improved for reasons of reducing failures, the system will be updated. In this case SW or

48、equipment will be replaced without adding new functionaties or resources to the network. The basic function required is: the modification of existing SW/equipment; it may be necessary to introduce a different set of data to cope with the modified SW/equipment. For system update the network shall not

49、 be disturbed in its function until the required modification is activated. This requires mechanisms to a- do SW/data downloading in parallel with on-going traffic; * isolate the affected NEs/NRs from traffic before the actual modificatiorl is done. 4.1.3.2 System up-grade System up-grade may affect all areas of PLMN activities and can be described as enhancements, whereby either new features or new facilities are implemented. Also extensions, reductions or further replications of existing facilities are covered by this CM aspect