1、 ETSI TS 132 411 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Requirements (3GPP TS 32.411 version 14.0.0 Release 14)
2、 TECHNICAL SPECIFICATION ETSI ETSI TS 132 411 V14.0.0 (2017-04)13GPP TS 32.411 version 14.0.0 Release 14Reference RTS/TSGS-0532411ve00 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 electro
4、nic 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)
5、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 https:/portal.etsi.org/TB/ETSIDeliverab
6、leStatus.aspx 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 p
7、hotocopying 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 Institu
8、te 2017. 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. oneM2M logo is protected for the ben
9、efit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 411 V14.0.0 (2017-04)23GPP TS 32.411 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to
10、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, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is avai
11、lable from the ETSI Secretariat. Latest updates are available on 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
12、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 Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or report
13、s 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 ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminolog
14、y In the present document “shall“, “shall not“, “should“, “should 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
15、 deliverables except when used in direct citation. ETSI ETSI TS 132 411 V14.0.0 (2017-04)33GPP TS 32.411 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations
16、 . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 PM concept and requirements 6g35 Detailed requirements. 6g35.1 Overall PM concept of Itf-N. 6g35.2 Management of network performance measurements 7g35.3 Management of threshold alarms . 7g35.4 Management of measurement events . 7g35.5 Management of m
17、easurement files . 7g36 Overview of IRPs related to PM 8g3Annex A (informative): Change history . 9g3History 10g3ETSI ETSI TS 132 411 V14.0.0 (2017-04)43GPP TS 32.411 version 14.0.0 Release 14Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP)
18、. 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 numbe
19、r 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, upda
20、tes, 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 managem
21、ent; as identified below: 32.411: “Performance Management (PM) Integration Reference Point (IRP): Requirements“. 32.412: “Performance Management (PM) Integration Reference Point (IRP): Information Service (IS)“. 32.416: “Performance Management (PM) Integration Reference Point (IRP); Solution Set (SS
22、) definitions“. The present document is part of a TS-family which describes the requirements and information model necessary for the Telecommunication Management (TM) of 3G systems. The TM principles and TM architecture are specified in 3GPP TS 32.101 2 and 3GPP TS 32.102 3. A 3G system is composed
23、of a multitude of Network Elements (NE) of various types and, typically, different vendors, which inter-operate in a co-ordinated manner in order to satisfy the network users communication requirements. Any evaluation of PLMN-system behaviour will require performance data collected and recorded by i
24、ts NEs according to a schedule established by the EM. This aspect of the management environment is termed Performance Management (PM). The purpose of any PM activity is to collect performance related data, which can be used to locate potential problems in the network. ETSI ETSI TS 132 411 V14.0.0 (2
25、017-04)53GPP TS 32.411 version 14.0.0 Release 141 Scope The present document specifies the overall requirements for the Performance Management Integration Reference Point (PMIRP) as it applies to the Network Elements (NE), Element Manager (EM) and Network Manager (NM). 2 References The following doc
26、uments 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 reference, subsequent revisions do not apply. -
27、 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 document. 1 3GPP TS 32.6xy: “Telecommunication man
28、agement; Configuration Management (CM)“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.401: “Telecommunication management; Performance Management (PM); Concept and requirements“.
29、5 3GPP TS 32.111-2 to -5: “Telecommunication management; Fault Management; Parts 2-5: Alarm Integration Reference Point (IRP)“. 6 3GPP TS 32.30x: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP)“. 7 3GPP TS 32.341: “Telecommunication manage
30、ment; File Transfer (FT) Integration Reference Point (IRP): Requirements“. 8 3GPP TS 32.412: “Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Information Service (IS)“. 9 ITU-T Recommendation Q.822: “Stage 1, Stage 2 and Stage 3 Description for the Q3 Int
31、erface Performance Management (04/94)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: alarm notification: notification used to inform the recipient about the occurrence of an alarm event: generic term for any type
32、 of occurrence within a network entity A notification or event report may be used to inform one or more OS(s) about the occurrence of the event granularity period: the time between the initiation of two successive gatherings of measurement data measurement job: task for collecting performance measur
33、ements measurement schedule: specifies the time frames during which the measurement job will be active. The measurement schedule contains one or several recording intervals ETSI ETSI TS 132 411 V14.0.0 (2017-04)63GPP TS 32.411 version 14.0.0 Release 14recording interval: the time period during which
34、 the measurement data is collected within the NE. The length of a recording interval will be a multiple of the granularity period 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management EM Element Manager FT File TransferFTIRP File T
35、ransfer Integration Reference Point FTP File Transfer Protocol IRP Integration Reference Point IS Information Service Itf-N management Interface between the Network and the Network Manager NE Network Element NM Network ManagerNRM Network Resource Model OS Operations System PM Performance Management
36、PMIRP Performance Management Integration Reference Point 4 PM concept and requirements Refer to 3GPP TS 32.401 4. 5 Detailed requirements 5.1 Overall PM concept of Itf-N An operations system on the network management layer (i.e. the NM) provides performance management services and functions required
37、 by the 3G operator on top of the element management layer. The N interface (Itf-N) may connect the Network Management system either to Element Managers (EMs) or directly to the Network Elements (NEs). This is done by means of Integration Reference Points (IRPs). In the following, the term “subordin
38、ate entities“ defines either EMs or NEs, which are in charge of supporting the N interface. This clause describes the properties of an interface enabling a NM to supervise a 3G-telecommunication network including - if necessary - the managing EMs. To provide to the NM the Performance Management capa
39、bility for the network implies that the NM and the subordinate entities have to agree on the following: - The identification of the performance measurements for each relevant network resource class, or for instances of a network resource class. - The identification of the network resource instances
40、whose performance measurements are required by NM. - The identification of the performance measurement attributes that can serve as a threshold and the identification of the corresponding threshold value(s). - The identification of the files containing collected performance measurements for retrieva
41、l by NM. - Notification of available files containing collected performance measurements for retrieval by NM. - The network configuration (due to the fact that measurement results, performance alarms and related state change information are always originated by network resources, see the Configurati
42、on Management (CM) NRM IRPs in 3GPP TS 32.6xy 1). This is, however, not part of the PM functionality. ETSI ETSI TS 132 411 V14.0.0 (2017-04)73GPP TS 32.411 version 14.0.0 Release 145.2 Management of network performance measurements The IRPManager shall be able to request the IRPAgent to: - Collect s
43、pecific performance measurements on specific network resources. The network resources, whose performance measurements are to be managed or collected, must have been modelled by the 3GPP Network Resource IRP or vendor-specific extended NRM and must be visible via the Bulk or Basic CM IRP. - Collect t
44、he performance measurements in a file. The data format of this file shall be specified in the 3GPP defined set of PM Specifications. - Emit notification announcing the availability of such file(s). - Create measurement jobs. - Suspend, Resume, and Stop running measurement jobs. - Define measurement
45、job schedule, including the definition of the recording interval(s), job start time and job stop time. - Stop scheduled measurement jobs. - Report status of the running and scheduled measurement jobs (as response to corresponding queries from the IRPManager). It is noted that the IRPAgent can only d
46、erive or determine the value of a performance measurement at the end of a granularity period (status inspection and discrete event registration). The IRPAgent may also have to reset the value of a performance measurement at the beginning of a granularity period. The above IRPAgent behaviours are dep
47、endent on the nature of the performance measurement types (cumulative counter, status inspection, gauge, and discrete event registration). 5.3 Management of threshold alarms The IRPManager shall be able to request the IRPAgent to: - Set threshold values to specific performance measurements of specif
48、ic network resources. - Emit an alarm notification (including clearing) when: - (a) the threshold value(s) have been crossed and not just reached, in a similar fashion as that defined in ITU-T Recommendation Q.822 9 or - (b) the threshold value(s) have been reached. It is the IRPAgents choice to sup
49、port (a) or (b) (but not both). The support is on an IRPAgent system wide basis and is not on a per threshold basis. The IRPAgents behaviour regarding which approach (i.e., (a) or (b) above) to use, shall be the same for emitting alarms and for clearing alarms. 5.4 Management of measurement events The IRPManager shall be able to: Subscribe to notifications that carry threshold alarms and information on the availability of performance measurement data files. 5.5 Management of measurement files The IRPManager shall be able to: Manage the tra
