ETSI TR 132 816-2009 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Study on management of_1.pdf

《ETSI TR 132 816-2009 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Study on management of_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 132 816-2009 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Study on management of_1.pdf（40页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 132 816 V8.0.0 (2009-01)Technical Report Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Study on management ofEvolved Universal Terrestrial Radio Access Network (E-UTRAN)and Evolved Packet Core (EPC)(3

2、GPP TR 32.816 version 8.0.0 Release 8)ETSI ETSI TR 132 816 V8.0.0 (2009-01) 13GPP TR 32.816 version 8.0.0 Release 8Reference DTR/TSGS-0532816v800 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

3、 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print.

4、In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users

5、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/status.asp If you find errors in the present document, please send your comment

6、 to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Insti

7、tute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade

8、 Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 132 816 V8.0.0 (2009-01) 23GPP TR 32.816 version 8.0.0 Release 8Intellectual Property Rights

9、 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 publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, o

10、r 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 Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been ca

11、rried 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 may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generatio

12、n Partnership Project (3GPP). The present document may refer to technical specifications or reports 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

13、ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TR 132 816 V8.0.0 (2009-01) 33GPP TR 32.816 version 8.0.0 Release 8Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8

14、g33.1 Definitions 8g33.2 Abbreviations . 8g34 Concepts and background 8g35 Requirements 8g35.1 Business level requirements . 8g35.1.1 Void 8g35.1.2 Void 8g35.1.3 High Level Use Cases . 9g35.1.3.1 Self organising network 9g35.1.3.1.1 Establishment of new eNodeB in network 9g3Optimisation of the neigh

15、bourhood list . 11g35.1.3.1.3 Coverage and capacity optimisation 12g35.1.3.1.4 Optimisation of parameter due to trouble shooting . 13g35.1.3.1.5 Continuous optimisation due to dynamic changes in the network (like traffic variation) . 13g35.1.3.1.6 Void . 13g35.1.3.1.7 Handover Optimisation: 13g35.1.

16、3.1.8 QoS related radio parameters optimization . 14g35.1.3.1.9 MBMS network Optimization . 15g35.1.4 Evolution of existing SA5 specifications 15g35.1.5 Establishment of new eNodeB in network 15g35.1.5.1 Automatic Radio Network configuration data preparation . 15g35.1.5.2 Self-Configuration of a new

17、 eNodeB 16g35.1.6 Trace in E-UTRAN/EPC 16g35.1.7 KPIs in E-UTRAN/EPC . 16g35.1.8 Site Management 16g35.1.9 Void 17g35.1.10 Configuration Management of E-UTRAN/EPC . 17g35.1.10.1 General 17g35.1.10.2 Pool Management . 17g35.1.11 Void 18g35.1.12 Neighbourhood list handling. 18g35.2 Specification level

18、 requirements 18g35.2.1 Void 18g35.2.2 Void 18g35.2.3 Void 18g35.2.4 Use cases . 18g35.2.4.1 SON Use cases 18g35.2.4.1.1 Void . 18g35.2.4.1.2 Establishment of new eNodeB in network 18g35.2.4.1.2.1 Void . 18g35.2.4.1.2.2 Self-Configuration of a new eNodeB . 19g35.2.4.1.3 Void . 20g35.2.4.1.4 Void . 2

19、0g35.2.4.1.5 Void . 20g35.2.4.1.6 Void . 20g3ETSI ETSI TR 132 816 V8.0.0 (2009-01) 43GPP TR 32.816 version 8.0.0 Release 85.2.4.1.7 Void . 20g35.2.4.1.8 Void . 20g35.2.4.1.9 Void . 20g35.2.5 Requirements 21g35.2.5.1 Evolution of existing SA5 specifications 21g35.2.5.2 Automatic installation of NEs .

20、 21g35.2.5.3 Trace in E-UTRAN/EPC . 21g35.2.5.4 KPIs in E-UTRAN/EPC 23g35.2.5.5 Void. 23g35.2.5.6 Fault Management of E-UTRAN/EPC 23g35.2.5.7 Configuration Management of E-UTRAN/EPC . 23g35.2.5.8 Performance Management of E-UTRAN/EPC . 24g35.2.5.9 Establishment of new eNodeB in network 24g35.2.5.10

21、Optimisation of neighbourhood list . 24g36 E-UTRAN/EPC Management Architecture . 25g36.1 Generic requirements for the management architecture . 25g36.2 Management Reference Models . 26g36.2.1 Existing Management Reference Model . 26g36.2.2 Use Case Specific Management Reference Models 26g36.2.3 E-UT

22、RAN / EPC Management Reference Model 26g36.3 Procedure for the specification of the E-UTRAN/EPC Function Specific Management Reference Models 27g36.4 Specification of the E-UTRAN/EPC Use Case Specific Management Reference Model 28g36.4.1 Requirements 28g36.4.2 Use Case Specific Logical Architecture

23、. 28g36.4.2.1. Use case self-configuration of eNodeBs . 28g36.4.2.x Use case X . 29g36.4.3 Void 30g36.4.3.1 Use case self-configuration of eNodeBs . 30g36.4.3.x Void. 30g36.5 Void 30g37 Conclusions and recommendations 31g37.1 Establishment of new eNodeB in network . 31g37.1.1 Automatic Radio Network

24、 configuration data preparation . 31g3Self-configuration of a new eNodeB . 31g37.2 Optimisation of the neighbourhood list 31g37.3 Coverage and capacity optimisation . 31g37.4 Optimisation of parameter due to trouble shooting 31g37.5 Continuous optimisation of due to dynamic changes in the network .

25、31g37.6 Handover optimisation . 31g37.7 QoS related radio parameters optimisation 31g37.8 MBMS network optimisation . 32g37.9 Evolution of existing SA5 specifications . 32g37.10 Trace in E-UTRAN/EPC 32g37.11 KPIs in E-UTRAN/EPC . 32g37.12 Site management 32g37.13 Fault management of E-UTRAN/EPC . 32

26、g37.14 Configuration of E-UTRAN/EPC 32g37.14.1 Pool management 32g37.15 Performance management of E-UTRAN/EPC . 32g3Annex A: Reuse of 3GPP TSs for E-UTRAN and EPC management . 33g3A.1 TSs to be reused . 33g3Annex B: Use case comparison to NGMN SON 37g3Annex C: Change history 38g3History 39g3ETSI ETS

27、I TR 132 816 V8.0.0 (2009-01) 53GPP TR 32.816 version 8.0.0 Release 8Foreword This Technical Report 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. Shou

28、ld 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; 3 or greater

29、 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. Introduction The E-UTRAN

30、 and EPC systems need to be managed. As E-UTRAN and EPC are evolvements of UMTS, the management should also evolve from UMTS. A reuse of the existing UMTS management standard solutions will have the following benefits: It is proven in operation; It will minimise both the standardisation and product

31、development efforts (i.e. the cost and time); It provides a base for on which more functionality can be developed (compared with making everything new from the start); It will shorten the time to market for E-UTRAN and EPC systems; It will facilitate a seamless coexistence with UMTS management syste

32、ms. The complexity of the E-UTRAN/ EPC network will also place new demands on the Operations and Maintenance of the Network, therefore as well as re-using and evolving existing Management solutions, Management solutions for E-UTRAN/ EPC will also need to encompass some new functionality (e.g. Auto-C

33、onfiguration, Auto-Optimisation, Information Model Discovery, and development of P2P Interfaces) Functionality shall be supported by clear use cases or other documented justification. Best Practice in O Subscriber and equipment trace; Trace concepts and requirements“. 3 3GPP TS 32.422: “Telecommunic

34、ation management; Subscriber and equipment trace; Trace control and configuration management“. 4 3GPP TS 32.423: “Telecommunication management; Subscriber and equipment trace; Trace data definition and management“. 5 3GPP TS 32.441: “Telecommunication management; Trace Management Integration Referen

35、ce Point (IRP): Requirements“. 6 3GPP TS 32.442: “Telecommunication management; Trace Management Integration Reference Point (IRP): Information service (IS)“. 7 3GPP TS 32.443: “Telecommunication management; Trace Management Integration Reference Point (IRP): Common Object Request Broker Architectur

36、e (CORBA) Solution Set (SS)“. 8 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 9 3GPP TS 32.102: “Telecommunication management; Architecture“. 10 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects

37、“. 11 3GPP TS 32.155: “Telecommunication management; Requirements template“. ETSI ETSI TR 132 816 V8.0.0 (2009-01) 83GPP TR 32.816 version 8.0.0 Release 83 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 apply. Se

38、archlist List of frequencies and supporting information to be used for neighbour cell measurements. The Searchlist contains entries for E-UTRAN and supported IRATs. Edtor“s note: This definition is provisional and subject to alignment with RAN2 and RAN3. 3.2 Abbreviations For the purposes of the pre

39、sent document, the following abbreviations apply. DM Domain Manager EPC Evolved Packet Core E-UTRAN Evolved UTRAN FFS For Further Study IE Information Elements IP Internet ProtocolMME Mobile Management Entity OSS Operation Support System UMTS Universal Mobile Telecommunications System 4 Concepts and

40、 background 5 Requirements 5.1 Business level requirements 5.1.1 Void 5.1.2 Void ETSI ETSI TR 132 816 V8.0.0 (2009-01) 93GPP TR 32.816 version 8.0.0 Release 85.1.3 High Level Use Cases 5.1.3.1 Self organising network REQ-MVR-CON-001 Self-configuration and self-optimisation should be supported in a m

41、ultiple vendor environment. Standardised procedures and O It will minimise both the standardisation and product development efforts (i.e. the cost and time); It provides a base for on which more functionality can be developed (compared with making everything new from the start); It will shorten the

42、time to market for E-UTRAN and EPC systems; It will facilitate a seamless coexistence with UMTS management systems. 5.1.5 Establishment of new eNodeB in network 5.1.5.1 Automatic Radio Network configuration data preparation REQ_EST_CON_1 Radio parameters for the new eNodeB should be generated as muc

43、h as possible without manual intervention. REQ_EST_CON_2 Radio parameters of network nodes already existing and operating in the field, and whose configuration requires updates due to the insertion of the new eNodeB, should be updated in an automated manner. ETSI ETSI TR 132 816 V8.0.0 (2009-01) 163

44、GPP TR 32.816 version 8.0.0 Release 8REQ_EST_CON_3 The generation of the radio configuration of the new eNodeB should work in a multi-vendor environment. 5.1.5.2 Self-Configuration of a new eNodeB The following requirements apply to the macro eNB only. Requirements for the HNB can be found in TR 32.

45、821. The following requirements apply to the software download into the eNB REQ_EST_CON_01 The software download should be automated as much as possible so that no or only minimal manual intervention is required. REQ_EST_CON_02 The actor at NM level should have monitoring and interaction capabilitie

46、s regarding the software download into the eNB. REQ_EST_CON_03 The software download functions used during the establishment of a new eNodeB in the network should be reused as much as possible for software upgrade. The following requirements apply to the automatic OAM connectivity establishment REQ_

47、EST_CON_04 The OAM connectivity (incl. the IP address allocation) shall be established in a fully automated manner. REQ_EST_CON_05 The amount of parameters that needs to be preconfigured should be minimized. REQ_EST_CON_06 The automatic establishment of the OAM connectivity shall be fully secured. 5

48、.1.6 Trace in E-UTRAN/EPC The need for trace functionality is the same as for a UMTS system (non E-UTRAN/EPC). Scenarios are described in TS 32.421 2. A fault can be due to node internal (vendor specific) decision, why it is beneficial to trace vendor specific data as well. To allow for this we need

49、 to have the possibility to add vendor specific data to the Equipment trace for E-UTRAN. This requires 3 new depth levels. To allow for such data to be recorded in the trace file, vendor specific data should be allowed in the trace file for E-UTRAN. 5.1.7 KPIs in E-UTRAN/EPC The following guidelines and principles shall be valid for the E-UTRAN KPIs specified in SA5: REQ-KPI-CON-001 Measure properties that the operator can control by means of dimensioning and optimisation REQ-KPI-CON-002 Measure properties