1、 ETSI TS 1Universal Mobile TelTelecommIntegratioInformati(3GPP TS 32.1TECHNICAL SPECIFICATION132 157 V13.0.0 (2016elecommunications System (LTE; munication management; tion Reference Point (IRP) ation Service (IS) template .157 version 13.0.0 Release 1316-02) (UMTS); 13) ETSI ETSI TS 132 157 V13.0.0
2、 (2016-02)13GPP TS 32.157 version 13.0.0 Release 13Reference RTS/TSGS-0532157vd00 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
3、-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/or print versions of the present document shall n
4、ot 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 kept on a specific network drive within ETSI Secr
5、etariat. 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 If you find errors in the present document, please se
6、nd 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 and microfilm except as authorized by written permissio
7、n 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 rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ET
8、SI 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 and owned by the GSM Association. ETSI ETSI TS 132 157
9、V13.0.0 (2016-02)23GPP TS 32.157 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 publicly available for ETSI members and non-members, a
10、nd 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 Web server (https:/ipr.etsi.org/). Pursuant to th
11、e 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 may become, essential to the present document. For
12、eword 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 should be interpreted as being references to the co
13、rresponding 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“, “may“, “need not“, “will“, “will not“, “can“ and “c
14、annot“ 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 V13.0.0 (2016-02)33GPP TS 32.157 version 13.0.0 Rel
15、ease 13Contents 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.1 General . 6g34.2 Template for NRM IRP IS . 8g3W1
16、 Scope 8g3W2 References 8g3W3 Definitions and abbreviations . 8g3W4 Model . 8g3W4.1 Imported information entities and local labels . 8g3W4.2 Class diagram . 9g3W4.2.1 Relationships. 9g3W4.2.2 Inheritance 9g3W4.3 Class definitions . 9g3W4.3.a InformationObjectClassName. 9g3W4.3.a.1 Definition 9g3W4.3
17、.a.2 Attributes . 10g3W4.3.a.3 Attribute constraints 10g3W4.3.a.4 Notifications 11g3W4.4 Attribute definitions . 12g3W4.4.1 Attribute properties . 12g3W4.4.2 Constraints 13g3W4.5 Common Notifications . 14g3W4.5.1 Alarm notifications . 14g3W4.5.2 Configuration notifications . 14g34.3 Template for Int
18、erface IRP IS 15g3Y1 Scope 15g3Y2 References 15g3Y3 Definitions and abbreviations . 15g3Y4 TBD 15g3Annex A (informative): Change history . 16g3History 17g3ETSI ETSI TS 132 157 V13.0.0 (2016-02)43GPP TS 32.157 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rd
19、Generation 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 release
20、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. tech
21、nical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 132 157 V13.0.0 (2016-02)53GPP TS 32.157 version 13.0.0 Release 131 Scope The present document contains the template to be used for the pro
22、duction of all 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
23、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 (including a GSM document), a non-specific reference imp
24、licitly 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
25、; Integration 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 Se
26、rvice (IS)“. ETSI ETSI TS 132 157 V13.0.0 (2016-02)63GPP TS 32.157 version 13.0.0 Release 133 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, 3GPP TS 32.150 3 and the following apply: IRPAg
27、ent: 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.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 Informatio
28、n Service OMG Object Management Group UML Unified Modelling Language (OMG) 4 Information Service (IS) template 4.1 General The present document contains the templates to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications for Converged Manageme
29、nt. Clause 4.2 is applicable for NRM IRP IS specifications. Clause 4.3 is applicable for Interface IRP IS specifications. 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 template). The IS template uses qualifie
30、rs M, O, 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 s
31、hall be according 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 ETSI ETSI TS 132 157 V13.0.0 (2016-02)73GPP TS 32.157
32、 version 13.0.0 Release 13State names Arial Matching Information Courier New Information Type Courier New Legal Values Courier New NOTE: These font requirements do not apply to UML diagrams. ETSI ETSI TS 132 157 V13.0.0 (2016-02)83GPP TS 32.157 version 13.0.0 Release 134.2 Template for NRM IRP IS W1
33、 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 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
34、 concerned such as “HNS“, “E_UTRAN“, “GERAN“) network resource information that 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
35、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 References TBD W3 Definitions and abbreviations TBD W4 Model W4.1 Imported information entities and local labels This clause identifie
36、s 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 shall be treated as if they are defined locally in the target specification. One us
37、age 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 the information entity is defined, the information entity type and its name. The local label contains the name of the informa
38、tion entity that appears in the target specification. The local label can then be used throughout 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 T
39、S 32.622 71, information object class, Top Top ETSI ETSI TS 132 157 V13.0.0 (2016-02)93GPP TS 32.157 version 13.0.0 Release 13W4.2 Class diagram W4.2.1 Relationships This first set of diagrams represents all classes defined in this IS with all their relationships and all their attributes, including
40、relationships with imported information entities (if any). These diagrams shall contain class cardinalities (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) o
41、f imported information entities need not to be repeated in the diagrams. Allowable classes are specified 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 relatio
42、nships 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
43、 the complete inheritance hierarchy but shall at least contain the parent classes of all classes defined in the present document. By default, a class inherits from the class “top“. Characteristics (attributes, relationships) of imported classes need not to be repeated in the diagrams. NOTE: some inh
44、eritance relationships presented in clause X.2.2 can be repeated in clause X.2.1 to enhance readability. Use “This subclause depicts the inheritance relationships.“ as the first paragraph. W4.3 Class definitions Each class is defined using the following structure. Inherited items (attributes etc.) s
45、hall not be shown, as they are defined in the parent class(es) and thus valid for the subclass. W4.3.a InformationObjectClassName InformationObjectClassName is the name of the information object class. The “a“ represents a number, starting at 1 and increasing by 1 with each new definition of a class
46、. W4.3.a.1 Definition The clause is written in natural language. The clause refers to the class itself. Optionally, information on traceability back to one or more requirements supported by this class can be defined here, in the following form: Referenced TS Requirement label Comment 3GPP TS 32.xyz
47、xy REQ-SM-CON-23 Optional clarification 3GPP TS 32.xyz xy REQ-SM-FUN-11 Optional clarification ETSI ETSI TS 132 157 V13.0.0 (2016-02)103GPP TS 32.157 version 13.0.0 Release 13W4.3.a.2 Attributes The clause presents the list of attributes, which are the manageable properties of the class. Each attrib
48、ute is characterised by some of the attribute properties (see Table 1 of 4), i.e. supportQualifier, isReadable, isWritable, isInvariant and isNotifyable. The legal values and their semantics for attribute properties are defined in 4. This information is provided in a table. An example below indicate
49、s Attribute name Support Qualifier isReadable isWritable isInvariant isNotifyable eNodeBId M M - M M Another example below indicates that the attribute password1 is not readable, is writable, is not an invariant and no notifyAttributeValueChange will be emitted when the attribute value is changed. Attribute name Support Qualifier isReadable isWritable isInvariant isNotifyable password1 O - M - - Another example below indicates that the attribute password2 and password1 (in example above) has same qualifiers for the shown prop
