1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommIntegration Reference P(3GPP TS 32.1TECHNICAL SPECIFICATION132 103 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; e Point (IRP) overview and us.103 version 13.0.0 Release 1316-01) hase 2+); (UM
2、TS); usage guide 13) ETSI ETSI TS 132 103 V13.0.0 (2016-01)13GPP TS 32.103 version 13.0.0 Release 13Reference RTS/TSGS-0532103vd00 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 - NAF
3、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 electronic
4、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 (PDF) vers
5、ion 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/status.asp
6、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 photocopying an
7、d 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. All r
8、ights 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 registered an
9、d owned by the GSM Association. ETSI ETSI TS 132 103 V13.0.0 (2016-01)23GPP TS 32.103 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 any, is p
10、ublicly 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 E
11、TSI 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 may be,
12、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 identities. Thes
13、e 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“, “should not“
14、, “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 132 10
15、3 V13.0.0 (2016-01)33GPP TS 32.103 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 IRP Framework 7g34.1
16、 Introduction 7g34.2 IRP Framework Highlights. 8g34.2.1 IRP Concept 8g34.2.2 Relationships between IRPs 9g34.2.3 IRP Development Principles . 10g34.2.4 IRP Specification Structure 10g34.2.5 Essential IRP Definitions 2 11g34.3 IRP related High-level Requirements 2 presented to TSG for approval; 3 or
17、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 when editorial only changes have been incorporated in the document. Introduction This
18、 specification provides the IRP Overview for 3GPP specifications, addressing Interface IRPs, NRM IRPs, Measurement / Trace /SON specifications, as well as their relationships with each other. ETSI ETSI TS 132 103 V13.0.0 (2016-01)63GPP TS 32.103 version 13.0.0 Release 131 Scope The present document
19、gives an overview about 3GPPs management interface capabilities and related functionality. It provides high-level information about IRP Framework, available IRPs as well as their relationship with each other. This document is intended to be a guide into the world of 3GPP management specifications, e
20、nabling also non-subject matter experts to gain an understanding about 3GPPs management solutions. In addition Annex A provides IRP packaging suggestions, intended to guide service providers as well as equipment and solutions providers to identify and choose suitable standardized management interfac
21、e capabilities. 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-specific. - For a specific r
22、eference, 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 Release as the present docu
23、ment. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 3 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 Definitions and abbreviations 3.1 Def
24、initions For the purposes of the present document, the terms and definitions given in TR 21.905 1, TS 32.150 2. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence
25、 over the definition of the same abbreviation, if any, in TR 21.905 1. FMC Fixed Mobile Convergence FNIM Federated Network Information Model IF Interface IRP Integration Reference Point IS Information Service SS Solution SetUIM Umbrella Information Model ETSI ETSI TS 132 103 V13.0.0 (2016-01)73GPP T
26、S 32.103 version 13.0.0 Release 134 IRP Framework 4.1 Introduction For the purpose of management interface development 3GPP has developed an interface concept known as Integration Reference Point (IRP) to promote the wider adoption of standardized management interfaces in telecommunication networks.
27、 The IRP concept and associated methodology employs model-driven development, protocol and technology neutral modelling methods as well as protocol specific solution sets to achieve its goals. IRP Framework and Methodology related 3GPP specifications: - 32.150: Integration Reference Point (IRP) Conc
28、ept and definitions - 32.151: IRP Information Service (IS) template (applicable to 32-series IRPs) - 32.152: IRP IS Unified Modeling Language (UML) repertoire - 32.153: IRP technology specific templates, rules and guidelines - 32.154: Backward and Forward Compatibility Concept and definitions - 32.1
29、55: Requirements template - 32.156: Fixed Mobile Convergence (FMC) Model repertoire - 32.157: IRP Information Service (IS) template (applicable for FMC) ETSI ETSI TS 132 103 V13.0.0 (2016-01)83GPP TS 32.103 version 13.0.0 Release 134.2 IRP Framework Highlights 4.2.1 IRP Concept IRP specifications ar
30、e specified using a 3-level approach: Requirements, IS-level and SS-level. Figure 4.2-1: The IRP 3-Level Specifications Approach combined with the three IRP categories 2. Solution Set Definitions (other/future e.g. JAVA , SNMP)Requirements / Use CasesSolution Set Definitions (CORBA, SOAP, XML, CMIP)
31、Relative stableover longperiod of timeChanges withnew/betterTechnologiesChanges only withrespect to additionand extensionsInterface IRPs Notification IRPAlarm IRPBulkCMIRP KernelCM IRPBasicCMIRPetcNRM IRPs Generic NRMCoreNWNRMUMTS NRMs CDMA NRMs Inventory NRMetcData Definition IRPs State Mgmt IRPetc
32、Information Service Definitions (UML)ETSI ETSI TS 132 103 V13.0.0 (2016-01)93GPP TS 32.103 version 13.0.0 Release 13Requirements-level: The “Requirements-level“ intends to provide conceptual and use cases definitions for a specific management interface aspect as well as defining subsequent requireme
33、nts for this IRP. IS-level: The “IS-level“ provides the technology independent specification of an IRP. SS-level: The “SS-level“ finally provides the mapping of IS definitions into one or more technology-specific Solution Sets. This concept provides support for multiple interface technologies as app
34、licable on a vendor and/or network type basis and also enables accommodation of future interface technologies - without the need to redefine requirements and IS-level definitions. 4.2.2 Relationships between IRPs There are three categories of IRP specifications: Interface IRPs NRM IRPs Data Definiti
35、on IRPs Each category is partitioned into Requirements, IS-level and SS-level specifications. Relationships between various kinds of IRPs: - Some Interface IRPs and NRM IRPs are used together. Such Interface IRPs operate on entities modelled by NRM IRPs. For example, operations defined in Basic CM I
36、RP are used together with E- UTRAN NRM IRP to support E-UTRAN configuration management function. - Interface IRPs are network/radio technology independent and can operate on entities modelled by NRM IRPs of different network technologies. For example, operations defined in Basic CM IRP are used toge
37、ther with E- UTRAN NRM IRP or UTRAN NRM IRP to support E- UTRAN or UTRAN configuration management functions. - Interface IRPs are Converged Management ready (e.g. support management of fixed and/or mobile) and can operate on modelled mobile and/or fixed network entities. - A Data Definition IRP prov
38、ides common data definitions, referenced by specifications of Interface IRPs and NRM IRPs. 3GPP TS 32.103 version 13.0.0 Release 13Figure 4.2-2: R4.2.3 IRP Development PrNRM IRP Extendibility - Enabling Technol Rule-based NRM Extensions (e.g. Su vsDataContainer Interface IRP Flexibility - Enabling:
39、wide ap(not just for wireless) via Flexible use of qualifiers “mandatory NRM/Technology-neutrality and b) specific to network techniques such as GSM and UMTS networks. ETSI ETSI TS 132 103 V13.0.0 (2016-01)223GPP TS 32.103 version 13.0.0 Release 13E-UTRAN KPIs 32.451 This specification defines requi
40、rements (business level requirements, specification level requirements and use case descriptions) related to KPIs for E-UTRAN. IMS KPIs 32.454 This specification defines KPIs for the IP Multimedia Subsystem (IMS). EPC KPIs 32.455 This specification defines KPIs for the Evolved Packet Core(EPC).netwo
41、rk. PM File Format 32.43x This set of specifications describe the general semantics of performance measurement result and collection. It defines the report file format, report file conventions, and the file transfer procedure. 3GPP TS 32.103 version 13.0.0 Release 137.2 Trace Specificatio7.2.1 Overv
42、iew and relatioFigure 7.2.1-2:7.2.2 Trace SpecificationsTrace Control - Automatic Neighbour Relation Management: Related requirements are defined in TS 32.511; - Self-Optimisation Management: Related requirements are defined in TS 32.521 or TS 28.627; - Self-Healing Management: Related requirements
43、are defined in TS 32.541; - Energy Saving Management: Related requirements are defined in TS 32.551; - Minimization of Drive Tests: Related requirements are defined in TS 32.421 and TS 32.441. Each SON use case can involve multiple IRPs when corresponding management scenarios are applied. As to IRP
44、solution fulfilment, Self-Optimization Management, Self-Healing Management and Energy Saving Management share the common information model of SON policy NRM (TS 32.522), while each one also has RAT-dependent information model in E-UTRAN NRM (TS 32.76 x /28.657/8/9) or UTRAN NRM (TS 32.64 x /28.651/2
45、/3). The IRP relationships of SON functions and measurement definitions are addressed case by case as follows, Self-establishment of an eNodeB Interface IRPs: - SC IRP (32.50x) - Software Management IRP (32.53x) - Generic IRP (32.31x) - Alarm IRP (32.111-x) - Test Management IRP (32.32x) - Basic CM
46、IRP (32.60x) or Bulk CM IRP (32.61x) - Kernel CM IRP (32.66x) - Notification IRP (32.30x) - File Transfer IRP (for ARCF data download) (32.34x) NRM IRPs: - Umbrella Information Model (28.620) - Generic NRM IRP (32.62x or 28.621/2/3) - E-UTRAN NRM IRP (32.76x or 28.657/8/9) Automatic Neighbour Relati
47、on Management Interface IRP: - Basic CM IRP (32.60x) or Bulk CM IRP (32.61x) - Alarm IRP (32.111-x) - Kernel CM IRP (32.66x) - Notification IRP (32.30x) NRM IRP: - Generic NRM IRP (32.62x or 28.620/28.621/2/3) ETSI ETSI TS 132 103 V13.0.0 (2016-01)253GPP TS 32.103 version 13.0.0 Release 13- E-UTRAN
48、NRM IRP (32.76x or 28.657/6/9) - UTRAN NRM IRP (32.64x) Self-Optimisation Management Interface IRP: - Basic CM IRP (32.60x) or Bulk CM IRP (32.61x) - Alarm IRP (32.111-x) - PM IRP (32.41x) - File Transfer IRP (for PM data upload) (32.34x) - Kernel CM IRP (32.66x) - Notification IRP (32.30x) NRM IRP:
49、 - SON Policy NRM IRP (32.52x or 28.627/8/9) - Generic NRM IRP (32.62x or 28.620/28.621/2/3) - E-UTRAN NRM IRP (32.76x or 28.657/6/9) Measurement Definitions: - E-UTRAN Performance Measurements (32.425) Self-Healing Management Interface IRP: - Basic CM IRP (32.60x) or Bulk CM IRP (32.61x) - Alarm IRP (32.111-x) - Kernel CM IRP (32.66x) - Notification IRP (32.30x) NRM IRP: - SON Policy NRM IRP (32.52x or 28.627/8/9) - Generic NRM IRP (32.62x or 28.620/28.621/2/3) - E-UTRAN NRM IRP (32.76x or 28.657/6/9) Energy Savi
