1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelTelecommIntegration Referentemplate(3GPP TS 32.1TECHNICAL SPECIFICATION132 153 V13.1.0 (2016mmunications system (Phase elecommunications System (LTE; munication management; ence Point (IRP) technology sptes, rules and guidelines .153 version 13.
2、1.0 Release 1316-04) e 2+) (GSM); (UMTS); specific 13) ETSI ETSI TS 132 153 V13.1.0 (2016-04)13GPP TS 32.153 version 13.1.0 Release 13Reference RTS/TSGS-0532153vd10 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 1
3、6 Siret N 348 623 562 00017 - 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 pri
4、nt. The content of any electronic 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 P
5、ortable Document Format (PDF) 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:/por
6、tal.etsi.org/tb/status/status.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 mec
7、hanical, including photocopying 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 Telecommunicatio
8、ns Standards Institute 2016. 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
9、logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 153 V13.1.0 (2016-04)23GPP TS 32.153 version 13.1.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to
10、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 from the ETSI Secretariat. Lat
11、est 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 (or the updates on the ETSI
12、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 their 3GPP identities, UMTS
13、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 present document “shall“, “
14、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 deliverables except when used in di
15、rect citation. ETSI ETSI TS 132 153 V13.1.0 (2016-04)33GPP TS 32.153 version 13.1.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbrevi
16、ations . 7g34 Interface IRP SS template 8g35 NRM IRP SS template . 14g3Annex A (normative): General rules for Solution Sets (SS) . 16g3A.1 Introduction 16g3A.2 Solution Set (SS) versioning 16g3A.3 Referenced Information Service (IS) specification 16g3Annex B (normative): Technology specific rules 2
17、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, updates, etc. z the third digit is incremented when editorial only changes have been incorporate
18、d 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 management; as identified below: TS 32.150 “Integration Reference Point (IRP) Concept and definitio
19、ns“ 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) repertoire“ TS 32.153 “Integration Reference Point (IRP) technology specific templates, rules and guidelines“ TS
20、32.154 “Backward and Forward Compatibility (BFC); Concept and definitions“ TS 32.155 “Requirements template“. ETSI ETSI TS 132 153 V13.1.0 (2016-04)63GPP TS 32.153 version 13.1.0 Release 131 Scope The present document contains the templates to be used for the production of Integration Reference Poin
21、t (IRP) technology-specific specifications. 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 publication, edition number, version number, etc.) or non-sp
22、ecific. 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 refers to the latest version of that document in the same Relea
23、se 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; Integration Reference Point (IRP) Concept and definitions“. 4 Void 5
24、Void 6 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 7 Void 8 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/). 9 OMG IDL Style Guide, ab/98-06-03, June 17, 1998. 10 W3C WSDL 1.1 specificat
25、ion (http:/www.w3.org/TR/wsdl) 11 Void. 12 Void. 13 Void. 14 Void. 15 Void. 16 IETF RFC 3629 (http:/tools.ietf.org/html/rfc3629#ref-UNICODE). 17 3GPP TS 28.652: “Telecommunication management; Universal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM) Integration Reference Point
26、(IRP); Information Service (IS)“. ETSI ETSI TS 132 153 V13.1.0 (2016-04)73GPP TS 32.153 version 13.1.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 f
27、ollowing apply: IRPAgent: See 3GPP TS 32.150 3. IRPManager: See 3GPP TS 32.150 3. SOAP: See 8. 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: CM Conditional Mandatory CM Configuratio
28、n ManagementCO Conditional Optional CORBA Common Object Request Broker Architecture (OMG) FF File Format IDL Interface Definition Language IOC Information Object Class IOC Information Object Class IRP Integration Reference Point IS Information Service M MandatoryMO Managed Object MOC Managed Object
29、Class NRM Network Resource Model O Optional OMG Object Management Group TS Technical Specification SOAP W3C acronym SS Solution SetSuM Subscription Management UML Unified Modelling Language (OMG) URI Uniform Resource Identifier WSDL Web Service Description Language XML eXtensible Markup Language XSD
30、 XML Schema Definition ETSI ETSI TS 132 153 V13.1.0 (2016-04)83GPP TS 32.153 version 13.1.0 Release 134 Interface IRP SS template This clause contains the Interface IRP SS template. The clauses in this template (that shall be used in the SS specifications) are numbered starting with “X“, which in ge
31、neral should correspond to clause 4 that is the beginning of the normative part of a TS. However, if there is a need in a specific SS to introduce additional clauses in the TS body, X may correspond to a number higher than 4. The SS templates use qualifiers M, O, CM and CO. The semantics of these qu
32、alifiers are defined in TS 32.150 3. The introductory clauses (from clause 1 to clause 3) for the SS should be modelled similarly to that of clause 1 to 3 of this specification. Instructions are written in italics. Usage of fonts shall be according to the following table. Table: Usage of fonts Item
33、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 Arial Enumerated values Arial ETSI ETSI TS 132 153 V13.1.0 (2016-04)93GPP TS 32.153 vers
34、ion 13.1.0 Release 13X Architectural Features “X“ represents a clause number in the actual SS. It contains at least the following this subclause: X.1 General This subclause contains the following paragraph: “The overall architectural feature of is specified in 3GPP TS . This clause specifies feature
35、s that are specific to the SS.“ Example: “The overall architectural feature of Alarm IRP is specified in 3GPP TS 32.111-2 6. This clause specifies features that are specific to the CORBA SS.“ Specific for SOAP SS: the supported XSD, WSDL and SOAP versions shall be indicated together with the style a
36、nd encoding style, and the namespaces with corresponding prefixes used in the WSDL specifications. Therefore the SOAP SS also contains the information quoted below: The SOAP specification relevant reference, XSD specification relevant reference and WSDL specification relevant reference are supported
37、. This specification uses “ style in WSDL file. This specification uses “ encoding style in WSDL file. This specification uses a number of namespace prefixes which are listed in Table X.1. Prefix Namespace http http:/schemas.xmlsoap.org/wsdl/http/ soap http:/schemas.xmlsoap.org/wsdl/soap/ xs or xsd
38、http:/www.w3.org/2001/XMLSchema xsi http:/www.w3.org/2001/XMLSchema-instance Table X.1: Prefixes and Namespaces used in this specification X.a “a“ represents a number, starting at 2 and increasing by 1 with each new feature. NOTE: This subclause is optional. ETSI ETSI TS 132 153 V13.1.0 (2016-04)103
39、GPP TS 32.153 version 13.1.0 Release 13Y Mapping “Y“ represents a clause number, immediately following “X“. Y.1 Operation and Notification mapping It contains this leading paragraph: “The : IS (see 3GPP TS ) defines semantics of operation and notification visible across the Itf-N. Table Y.1.1 indica
40、tes mapping of these operations and notifications to their equivalents defined in this SS.“ Example: “Alarm IRP: IS 3GPP TS 32.111-2 6 defines semantics of operation and notification visible across the Itf-N. Table Y.1.1 indicates mapping of these operations and notifications to their equivalents de
41、fined in this SS.“ The table includes all operations and notifications, including those inherited. The table lists the operations first and then the notifications. The list order is the same as the one used in the IS. Semantics for the Qualifier is defined in Ref x. Table Y.1.1: Mapping from IS Oper
42、ation/Notification to SS equivalents IS Operation/Notification in 3GPP TS SS Method Qualifier M, O, CM or CO od2 M, O, CM or CO notify M, O, CM or CO ETSI ETSI TS 132 153 V13.1.0 (2016-04)113GPP TS 32.153 version 13.1.0 Release 13Y.2 Operation parameter mapping It contains this leading paragraph: “R
43、eference 3GPP TS defines semantics of parameters carried in operations across the Itf-N. The following set of tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS.“ Example: “Reference 3GPP TS 32.111-2 6 defines semantics of parameters carried in
44、 operations across the Itf-N. The following set of tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS.“ Table Y.2.1: Mapping from IS parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier M, O, CM or CO M, O, CM or CO
45、 . status M Table Y.2.2: Mapping from IS parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier M, O, CM or CO status M Table Y.2.x: IS Operation parameter SS Method parameter Qualifier . . status M ETSI ETSI TS 132 153 V13.1.0 (2016-04)123GPP TS 32.153 version 13.1.0 Rele
46、ase 13Y.3 Notification parameter mapping It contains this leading paragraph: “Reference 3GPP TS ) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service , is: Header Fixed Header domain_name type_name event_name Variable Header Body filterable_body_fields re
47、maining_body The following tables list all OMG Structured Event attributes in the second column. The first column identifies the IRP: IS defined notification parameters. “ Table Y.3.1: Mapping for notifyKkk IS Parameters Parameters Qualifier Comment M or O M or O M or O ETSI ETSI TS 132 153 V13.1.0
48、(2016-04)133GPP TS 32.153 version 13.1.0 Release 13Z Notification Interface “Z“ represents a number, immediately following “Y“. This sub-clause captures SS technology specific details required to realize the IS-defined for notifications. Specific for CORBA SS: The SS contains this: “ OMG CORBA Notif
49、ication push operation is used to realise the notification of AlarmIRPNotifications. All the notifications in this interface are implemented using this push_structured_event method. Z.1 Method push (M) module CosNotifyComm Interface SequencePushConsumer : NotifyPublish void push_structured_events( in CosNotification:EventBatch notifications) raises( CosEventComm:Disconnected); ; / SequencePushConsumer ; / CosNotifyComm
