1、 ETSI TS 132 151 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template (3GPP TS 32.151 version 14.0.0 Release 14) TECHNIC
2、AL SPECIFICATION ETSI ETSI TS 132 151 V14.0.0 (2017-04)13GPP TS 32.151 version 14.0.0 Release 14Reference RTS/TSGS-0532151ve00 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 742
3、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 and/
4、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) version
5、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/ETSIDeliverableStatus
6、.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 photocopy
7、ing 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 2017.
8、 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 benefit of
9、its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 151 V14.0.0 (2017-04)23GPP TS 32.151 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. Th
10、e 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 available fr
11、om 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 000 314
12、(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 reports using
13、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 terminology In the
14、 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 deliver
15、ables except when used in direct citation. ETSI ETSI TS 132 151 V14.0.0 (2017-04)33GPP TS 32.151 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.
16、1 Definitions 7g33.2 Abbreviations . 7g34 Information Service (IS) template 7g3W1 Scope 9g3W2 Scope 9g3X Information Object Classes 9g3X.1 Imported information entities and local labels . 9g3X.2 Class diagram . 10g3X.2.1 Attributes and relationships 10g3X.2.2 Inheritance 10g3X.3 Information object c
17、lass definitions . 11g3X.3.a InformationObjectClassName 11g3X.3.a.1 Definition 11g3X.3.a.2 Attributes . 11g3X.3.a.3 Attribute constraints 12g3X.3.a.4 Relationships . 12g3X.3.a.5 State diagram. 12g3X.3.a.6 Notifications 13g3X.4 Information relationship definitions . 14g3X.4.a InformationRelationshipN
18、ame (supportQualifier) 14g3X.4.a.1 Definition 14g3X.4.a.2 Roles . 14g3X.4.a.3 Constraints 14g3X.5 Information attribute definitions . 15g3X.5.1 Definition and Legal Values . 15g3X.5.2 Constraints 15g3X.6 Common Notifications . 15g3X.7 System State Model 15g3Y Interface Definition 16g3Y.1 Class diagr
19、am representing interfaces 16g3Y.2 Generic rules 16g3Y.b InterfaceName Interface (supportQualifier) . 16g3Y.b.a Operation OperationName (supportQualifier) 17g3Y.b.a.1 Definition 17g3Y.b.a.2 Input parameters 17g3Y.b.a.3 Output parameters . 17g3Y.b.a.4 Pre-condition . 19g3Y.b.a.5 Post-condition . 19g3
20、Y.b.a.6 Exceptions . 19g3Y.b.a.6.c exceptionName 20g3Y.b.a.7 Constraints 20g3Y.b.a Notification NotificationName (supportQualifier) 21g3ETSI ETSI TS 132 151 V14.0.0 (2017-04)43GPP TS 32.151 version 14.0.0 Release 14Y.b.a.1 Definition 21g3Y.b.a.2 Input parameters 21g3Y.b.a.3 Triggering event 21g3Y.b.
21、a.3.1 From state 22g3Y.b.a.3.2 To state 22g3Y.b.a.4 Constraints 22g3Y.c Scenario 22g3Annex A (informative): Change history . 23g3History 24g3ETSI ETSI TS 132 151 V14.0.0 (2017-04)53GPP TS 32.151 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Par
22、tnership 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 release date and an in
23、crease 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. technical enhancem
24、ents, 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 System Aspects; Te
25、lecommunication management; as identified below: TS 32.150: Integration Reference Point (IRP) Concept and definitions TS 32.151: Integration Reference Point (IRP) Information Service (IS) template TS 32.152: Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML)
26、repertoire TS 32.153 Integration Reference Point (IRP) technology specific templates TS 32.154 Backward and Forward Compatibility (BFC); Concept and definitions TS 32.155 Requirements template ETSI ETSI TS 132 151 V14.0.0 (2017-04)63GPP TS 32.151 version 14.0.0 Release 141 Scope The present document
27、 contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present documen
28、t. - 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 applies. In the case of a reference to a 3GPP document (inc
29、luding 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 3GPP TS 32.102: “Telecommunication management; Architectu
30、re“. 3 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 4 3GPP TS 32.152: “Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire“. 5 3GPP TS 32.622: “Telecommunica
31、tion management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 6 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service“. 7 3GPP TS 32.302: “T
32、elecommunication Management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 8 ITU-T Recommendation M.3020 (2009): Management interface specification methodology Annex E Information type definitions type repertoire. 9 3GPP TS 32.602: “Telecom
33、munication Management; Configuration Management (CM): Basic CM IRP: Information Service (IS)“. 10 3GPP TS 32.612: “Telecommunication Management; Configuration Management (CM): Bulk CM IRP: Information Service (IS)“. ETSI ETSI TS 132 151 V14.0.0 (2017-04)73GPP TS 32.151 version 14.0.0 Release 143 Def
34、initions 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, 3GPP TS 32.150 3 and the following apply: IRPAgent: See 3GPP TS 32.150 3. IRPManager: See 3GPP TS 32.150 3. 3.2 Abbreviations For the purposes o
35、f the present document, the abbreviations given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.150 3 and the following apply: IOC Information Object Class IRP Integration Reference Point IS Information Service OMG Object Management Group UML Unified Modelling Language (OMG) 4 Information Service
36、(IS) template The present document contains the templates to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series. For the introductory clause 1 (Scope) of all NRM IRP ISs, clause W1 shall be used. For the introductory
37、clause 1 (Scope) of all Interface IRP ISs, clause W2 shall be used. For the introductory clauses 2 and 3 of all IRP ISs, the text shall be written conforming to the standard 3GPP TS template (i.e. not this IRP IS template). The other clauses in this template that shall be used in the IS specificatio
38、ns following their introductory clauses are numbered starting with “X“, which in general should correspond to clause 4 that is the beginning of the main part of the TS. However, if there is a need in a specific IS to introduce additional clauses in the body, X may correspond to a number higher than
39、4. For a NRM IRP IS, only clause X shall be used. For an Interface IRP IS, both clauses X and Y shall be used. The IS template uses qualifiers M, O, CM, CO and C. The semantics of these qualifiers are defined in TS 32.150 3. The IS template uses Information Type as one characteristic to describe IOC
40、 attributes and operation/notification parameters. The valid Information Type(s) that can be used and their semantics are defined in ITU-T M.3020 Annex E 8. Usage of fonts shall be according to the following table. ETSI ETSI TS 132 151 V14.0.0 (2017-04)83GPP TS 32.151 version 14.0.0 Release 14Item F
41、ont Class names Courier New Attribute names Courier New Operation names Courier New Parameter names Courier New Assertion names Courier New Notification names Courier New Exception names Courier New State names ArialMatching Information Courier New Information Type Courier New Legal Values Courier N
42、ew NOTE: These font requirements do not apply to UML diagrams. ETSI ETSI TS 132 151 V14.0.0 (2017-04)93GPP TS 32.151 version 14.0.0 Release 14W1 Scope The following quoted text is relevant for all NRM IRP ISs. It shall be copied as the first two paragraphs of the NRM IRP IS specification. IRP IS aut
43、hor may add additional paragraph(s) if necessary. “ The present document specifies the (where shall be substituted by the name of the NRM IRP IS concerned such as HNS, E_UTRAN, GERAN) network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network
44、 management purposes. This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. “ W2 Scope The following quoted text is relevant f
45、or all Interface IRP ISs. It shall be copied as the first two paragraphs of the Interface IRP IS specification. IRP IS author may add additional paragraph(s) if necessary. “ The present document specifies the (where shall be substituted by the name of the Interface IRP IS concerned such as “Alarm”,
46、“Test”,” Entry Point”) management operations and notifications that can be communicated between an IRPAgent and one or several IRPManagers. This document specifies the semantics and behaviour of operations, notifications and their parameters visible across the reference point in a protocol and techn
47、ology neutral way. It does not define their syntax and encoding. “ X Information Object Classes This “X” clause shall be used for NRM IRP ISs. This “X” clause shall also be used for Interface IRP ISs. “X“ represents a clause number in the actual Information Service TS. X.1 Imported information entit
48、ies and local labels This clause identifies a list of information entities (e.g. information object class, interface, information relationship, information attribute) that have been defined in other specifications and that are imported in the present specification. All imported entities shall be tre
49、ated as if it is defined locally in present specification. One usage of import is for inheritance purpose. Each element of this list is a pair (label reference, local label). The label reference contains the name of the specification where it is defined, the type of the information entity and its name. The local label of imported information entities can then be used throughout the specification instead of the label reference. This information is provided in a table. An example of such a table is given here below: Label refere
