1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommGeneric Integration R(3GPP TS 32.3TECHNICAL SPECIFICATION132 311 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; n Reference Point (IRP) managRequirements .311 version 13.0.0 Release 1316-02) ha
2、se 2+); (UMTS); agement; 13) ETSI ETSI TS 132 311 V13.0.0 (2016-02)13GPP TS 32.311 version 13.0.0 Release 13Reference RTS/TSGS-0532311vd00 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 0001
3、7 - 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 ele
4、ctronic 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 (P
5、DF) 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/sta
6、tus.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 photoco
7、pying 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 201
8、6. 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 regis
9、tered and owned by the GSM Association. ETSI ETSI TS 132 311 V13.0.0 (2016-02)23GPP TS 32.311 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 a
10、ny, 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
11、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 000 314 (or the updates on the ETSI Web server) which are, or
12、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 reports using their 3GPP identities, UMTS identities or GSM identiti
13、es. 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“, “sho
14、uld 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 T
15、S 132 311 V13.0.0 (2016-02)33GPP TS 32.311 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Generic IRP
16、functions over Itf-N . 6g34.1 Version retrieval function . 6g34.2 Profiles retrieval functions . 6g3Annex A (informative): Change history . 7g3History 8g3ETSI ETSI TS 132 311 V13.0.0 (2016-02)43GPP TS 32.311 version 13.0.0 Release 13Foreword This Technical Specification (TS) has been produced by the
17、 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. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of rele
18、ase 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 indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e.
19、technical enhancements, corrections, updates, 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
20、System Aspects; Telecommunication management; as identified below: 32.311: “Generic Integration Reference Point (IRP) management; Requirements“. 32.312: “Generic Integration Reference Point (IRP) management; Information Service (IS)“. 32.316: “ Generic Integration Reference Point (IRP) management; S
21、olution Set (SS) Definitions“. The Itf-N interface is built up by a number of Integration 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.101 1 and 3GPP TS 32.102 2. The IRP
22、s support a set of common services. Those features allow to retrieve IRP profile and IRP supported versions. The present document contains the requirements of those common services. ETSI ETSI TS 132 311 V13.0.0 (2016-02)53GPP TS 32.311 version 13.0.0 Release 131 Scope The purpose of the present docu
23、ment is to define a common service supported by all IRPs such as AlarmIRP. The present document is the “Requirements“ part. It defines the requirements that shall be fulfilled by all IRPs, such as AlarmIRP, supporting this common service. With this common service supported by all IRPs, an IRPManager
24、 shall be able to retrieve the profile of operations and notifications supported by a given IRP which is name-contained by an IRPAgent. An IRPManager shall also be able to retrieve the IRPVersions supported by the given IRP. 2 References The following documents contain provisions which, through refe
25、rence 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. For a non-specific reference, the latest version a
26、pplies. 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.101: “Telecommunication management; Principles and high level requirements“. 2
27、 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2 and the following apply: IRP: see 3GPP TS 32.102 2. IRPAgent: see 3GPP TS 32.
28、102 2. IRPManager: see 3GPP TS 32.102 2. IRP document version number string: the IRP document version number (sometimes called “IRPVersion“) string is used to identify a technology of a particular IRP Solution Set (SS) specification and its version number. For Release 9 and earlier releases, it is d
29、erived using the following rule: Take the 3GPP TS/version number on the front page of the SS specification, such as 3GPP TS 32.111-3 V4.1.0 (2001-09)“. Discard the leading “3GPP TS“. Discard all characters after and including the last period. Eliminate leading and trailing spaces. Reduce multiple co
30、nsecutive spaces to one space. Express the resultant in a string. Capitalise all letters of the string. EXAMPLE 1: If the 3GPP document version number is “3GPP TS 32.111-3 V4.1.0 (2001-09)“, then the IRP document version number shall be “32.111-3 V4.1“. EXAMPLE 2:If the 3GPP document version number
31、is “3GPP TS 32.303 V4.1.0 (2001-09)“, then the IRP document version number shall be “32.303 V4.1“. For Release 10 and later releases, it is derived using the following rule: ETSI ETSI TS 132 311 V13.0.0 (2016-02)63GPP TS 32.311 version 13.0.0 Release 13Take the 3GPP TS/version number on the front pa
32、ge of the SS specification, such as “3GPP TS 32.111-6 V10.1.0 (2011-06)“, Discard the leading “3GPP TS“. Discard all characters after and including the last period. Remove all spaces. Construct a string that is a concatenation of “-“, the identifier of the Annex where the solution set technology is
33、captured (e.g., “A“ for Annex A) and a trailing space. Insert the concatenated string before “V“, Express the resultant in a string. Capitalise all letters of the string. EXAMPLE 3: If the 3GPP document version number is “3GPP TS 32.111-6 V10.1.0 (2011-06)“, then the IRP document version number shal
34、l be: head2right “32.111-6-A V10.1“ for CORBA Solution Set; head2right “32.111-6-B V10.1“ for XML Definitions; head2right “32.111-6-C V10.1“ for SOAP Solution Set. EXAMPLE 4: If the 3GPP document version number is “3GPP TS 32.306 V10.1.0 (2011-09)“, then the IRP document version number shall be: hea
35、d2right “32.306-A V10.1“ for CORBA Solution Set; head2right “32.306-B V10.1“ for XML Defintions; head2right “32.306-C V10.1“ for SOAP Solution Set. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management EM Element Manager IRP Integr
36、ation Reference Point IS Information Service NE Network ElementNM Network Manager SS Solution Set 4 Generic IRP functions over Itf-N The requirements for the generic IRP service over Itf-N are provided in the following clauses. 4.1 Version retrieval function An IRPAgent may support one or multiple I
37、RP instances simultaneously (e.g. AlarmIRP instances, BulkCMIRP instances, etc.). The set of capabilities of each IRP instance is fully identified by the version number of the corresponding IRP specification (i.e. the IRP document version number string or in short, the IRPVersion; see clause 3.1.).
38、An IRP instance shall provide a function to allow IRPManager to retrieve all its (i.e. IRP instance“s) supported IRPVersion(s) over Itf-N. An IRPManager may then decide if it wants to communicate with the IRP instance. 4.2 Profiles retrieval functions Each IRP supported by an IRPAgent provides a set
39、 of operations and notifications. It is possible to define in each IRP Information Service (IS) some operations and notification that are optional, which means that the final implementation of those operations and notifications is vendor dependant. Similarly, some parameters of operations and notifi
40、cations may be defined as optional in the IRP IS. It shall be possible for an IRPManager to retrieve over Itf-N the profile of an IRP of a given version: the profile shall provide information such as name of supported operations and notifications, and the list of supported parameters for each suppor
41、ted operation and notification. ETSI ETSI TS 132 311 V13.0.0 (2016-02)73GPP TS 32.311 version 13.0.0 Release 13Annex A (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New Jun 2001 SA_12 SP-010285 - - Approved at TSG SA #12 and placed under Change Control 2
42、.0.0 4.0.0 Jul 2001 - - - - TS number wrongly shown as 32.312 instead of 32.311 4.0.0 4.0.1 Mar 2002 SA_15 - - - Automatic upgrade to Rel-5 (no Rel-5 CR) 4.0.1 5.0.0 Dec 2002 - - - - Cosmetics 5.0.0 5.0.1 Dec 2003 SA_22 SP-030639 0002 - Align with 32.102 5.0.1 5.1.0 Mar 2004 SA_23 SP-040105 - - Auto
43、matic upgrade to Rel-6 (no CR) 5.1.0 6.0.0 Dec 2004 SA_26 SP-040794 0003 - Update UML diagrams, Add reference to its CORBA/CMIP SSs 6.0.0 6.1.0 Jun 2007 SA_36 - - - Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. 6.1.0 7.0.0 Dec 2008
44、 SA_42 - - - Upgrade to Release 8 7.0.0 8.0.0 Dec 2009 - - - - Update to Rel-9 version (MCC) 8.0.0 9.0.0 Mar 2011 - - - - Update to Rel-10 version (MCC) 9.0.0 10.0.0 Dec 2012 SA_54 SP-110706 0004 4 Enhance definition of IRPVersion 10.0.0 10.1.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.1.0 11.0.0 2014-10 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 ETSI ETSI TS 132 311 V13.0.0 (2016-02)83GPP TS 32.311 version 13.0.0 Release 13History Document history V13.0.0 February 2016 Publication
