ETSI TS 132 157-2017 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Integration Reference Point (IRP) Information Service (IS) template (V14 0 1.pdf

1、 ETSI TS 132 157 V14.0.1 (2017-05) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template (3GPP TS 32.157 version 14.0.1 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 157 V14.0.1 (2017-05)13GPP

2、TS 32.157 version 14.0.1 Release 14Reference RTS/TSGS-0532157ve01 Keywords 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 C Association but non lucratif enregistre la Sous-Prfecture de Gr

3、asse (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/or print versions of the present document shall not be modified w

4、ithout 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 kept on a specific network drive within ETSI Secretariat. Users o

5、f 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.aspx If you find errors in the present document, please send you

6、r 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 and microfilm except as authorized by written permission of E

7、TSI. 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. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI log

8、o 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 its Members GSM and the GSM logo are Trade Marks registered and o

9、wned by the GSM Association. ETSI ETSI TS 132 157 V14.0.1 (2017-05)23GPP TS 32.157 version 14.0.1 Release 14Intellectual 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 publ

10、icly 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 ETSI

11、 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, or

12、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. These s

13、hould 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 157 V

15、14.0.1 (2017-05)33GPP TS 32.157 version 14.0.1 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Information Service (IS) template 6g34.

16、1 General . 6g34.2 Template for NRM IRP IS . 7g34.3 Template for Interface IRP IS 14g3Annex A (informative): Change history . 28g3History 29g3ETSI ETSI TS 132 157 V14.0.1 (2017-05)43GPP TS 32.157 version 14.0.1 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Pa

17、rtnership 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 i

18、ncrease 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 enhance

19、ments, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 132 157 V14.0.1 (2017-05)53GPP TS 32.157 version 14.0.1 Release 141 Scope The present document contains the template to be used for the production of al

20、l Integration Reference Point (IRP) Information Service (IS) specifications for Converged Management. 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

21、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 (including a GSM document), a non-specific reference implicitly

22、 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; Architecture“. 3 3GPP TS 32.150: “Telecommunication management; Integ

23、ration Reference Point (IRP) Concept and definitions“. 4 3GPP TS 32.156: “Telecommunication management; Fixed Mobile Convergence (FMC) Model Repertoire 5 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service

24、(IS)“. 6 ITU-T Recommendation M.3020 (07/2011): “Management interface specification methodology“ Annex E “Information type definitions type repertoire“. ETSI ETSI TS 132 157 V14.0.1 (2017-05)63GPP TS 32.157 version 14.0.1 Release 143 Definitions and abbreviations 3.1 Definitions For the purposes of

25、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 of the present document, the abbreviations given in 3GPP TS 32.1

26、01 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 (IS) template 4.1 General The present document contains the tem

27、plates to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications for Converged Management. Clause 4.2 is applicable for NRM IRP IS specifications. Clause 4.3 is applicable for Interface IRP IS specifications. The IS template uses qualifiers M, O,

28、CM, CO and C. The semantics of these qualifiers are defined in 4. The IS template uses type definition as one characteristic to describe class attributes and operation/notification parameters. The valid type definitions that can be used and their semantics are defined in 4. Usage of fonts shall be a

29、ccording to the following table. Item Font 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

30、Type Courier New Legal Values Courier New NOTE: These font requirements do not apply to UML diagrams. ETSI ETSI TS 132 157 V14.0.1 (2017-05)73GPP TS 32.157 version 14.0.1 Release 144.2 Template for NRM IRP IS W1 Scope The following quoted text is relevant for all NRM IRP ISs. It shall be copied as t

31、he first two paragraphs of this clause in the NRM 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 NRM IRP IS concerned such as HNS, E_UTRAN, GERAN) network resource information that

32、can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks. This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a pr

33、otocol and technology neutral way. It does not define their syntax and encoding. “ W2 References The following text from the standard 3GPP TS template shall be copied into the NRM IRP IS specification, followed by the TS/TR references used in the specification: “ The following documents contain prov

34、isions 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. - For a non-specific

35、 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 2 “ W3 Definitions and abbreviations The following text f

36、rom the standard 3GPP TS template shall be copied into the NRM IRP IS specification, completed by the definitions and abbreviations used in the specification: “ W3.1 Definitions ETSI ETSI TS 132 157 V14.0.1 (2017-05)83GPP TS 32.157 version 14.0.1 Release 14For the purposes of the present document, t

37、he terms and definitions given in 3GPP TR 21.905 1 and the following apply. For terms and definitions not found here, please refer to 3GPP TS . A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1 and . : . W3.2 Abbreviations For t

38、he purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. “ W4 Model W4.1 Imported and associated information en

39、tities W4.1.1 Imported information entities and local labels This clause identifies a list of information entities (e.g. information object class, interface, attribute) that have been defined in other specifications and that are imported in the present (target) specification. All imported entities s

40、hall be treated as if they are defined locally in the target 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 original specification where the information entity is defined,

41、 the information entity type and its name. The local label contains the name of the information entity that appears in the target specification, and the entity name in the local label shall be kept identical to the name defined in the original specification. The local label can then be used througho

42、ut the target specification instead of that which appears in the label reference. This information is provided in a table. An example of such a table is given here below: Label reference Local label 3GPP TS 32.622 xy, information object class, Top Top W4.1.2 Associated information entities and local

43、 labels This clause identifies a list of information entities (e.g. information object class, interface, attribute) that have been defined in other specifications and that are associated with the information entities defined in the present (target) specification. For the associated information entit

44、y, only its properties (e.g., DN (see 5.2.2 of 32.156 4), attribute (see 5.2.1 of 32.156 4) of an instance of the associated information entity) used as associated information needs to be supported locally in the target specification. Each element of this list is a pair (label reference, local label

45、). The label reference contains the name of the original specification where the information entity is defined, the information entity type and its name. The local label contains the name of the information entity that appears in the target specification. The local label can then be used throughout

46、the target specification instead of that which appears in the label reference. This information is provided in a table. An example of such a table is given here below: Label reference Local label 3GPP TS 28.705 12, IOC, HSSFunction HSSFunction W4.2 Class diagram ETSI ETSI TS 132 157 V14.0.1 (2017-05

47、)93GPP TS 32.157 version 14.0.1 Release 14W4.2.1 Relationships This first set of diagrams represents all classes defined in this IS with all their relationships and all their attributes, including relationships with imported information entities (if any). These diagrams shall contain class cardinali

48、ties (for associations as well as containment relationships) and may also contain role names. These shall be UML compliant class diagrams (see also 4). Characteristics (attributes, relationships) of imported information entities need not to be repeated in the diagrams. Allowable classes are specifie

49、d in 4. Use this as the first paragraph: “This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for this IRP. This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes.“ W4.2.2 Inheritance This second set of diagrams represents the inheritance hierarchy of all classes defined in this specification. These diagrams do not need to contain the complete