1、 ETSI TS 132 362 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Information Service (IS) (3GPP TS 32.362 version 15.0.0 Release 15
2、) TECHNICAL SPECIFICATION ETSI ETSI TS 132 362 V15.0.0 (2018-07)13GPP TS 32.362 version 15.0.0 Release 15Reference RTS/TSGS-0532362vf00 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 -
3、 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 electr
4、onic 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 (PDF)
5、 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 https:/portal.etsi.org/TB/ETSIDelivera
6、bleStatus.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
7、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. ETSI 2018. All rights reserved. DECTTM, PLUG
8、TESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks 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. GSMand the GSM logo ar
9、e trademarks registered and owned by the GSM Association. ETSI ETSI TS 132 362 V15.0.0 (2018-07)23GPP TS 32.362 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pe
10、rtaining 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 from the ETSI Secr
11、etariat. 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 (or the updates
12、on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being
13、 the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specificatio
14、n (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 corresponding ETSI deliverables. Th
15、e 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 “cannot“ are to be interpreted as d
16、escribed 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 362 V15.0.0 (2018-07)33GPP TS 32.362 version 15.0.0 Release 15Contents Intellectual Prop
17、erty Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 System Overview . 7g34.1 System Context 7g34.2 Compliance rules 7g35 Information Object Classes 8g35.1 Imp
18、orted information entities and local labels . 8g35.2 Class diagram . 8g35.2.1 Attributes and relationships 8g35.2.2 Inheritance 8g35.3 Information Object Class definitions 8g35.3.1 EPIRP 8g35.3.1.1 Definition 8g35.3.1.2 Attributes . 9g36 Interface definition . 9g36.1 Class diagram representing inter
19、faces 9g36.2 Generic rules 9g36.3 Interface EPIRPOperations (M) . 9g36.3.1 Operation getIRPOutline (M) . 9g36.3.1.1 Definition 9g36.3.1.2 Input parameters 10g36.3.1.3 Output parameters . 10g36.3.1.4 Pre-condition . 10g36.3.1.5 Post-condition . 10g36.3.1.6 Exceptions . 11g36.3.2 Operation getIRPRefer
20、ence (M) 11g36.3.2.1 Definition 11g36.3.2.2 Input parameters 11g36.3.2.3 Output parameters . 11g36.3.2.4 Pre-condition . 11g36.3.2.5 Post-condition . 11g36.3.2.6 Exceptions . 12g36.3.3 Operation releaseIRPReference (M) . 12g36.3.3.1 Definition 12g36.3.3.2 Input parameters 12g36.3.3.3 Output paramete
21、rs . 12g36.3.3.4 Pre-condition . 12g36.3.3.5 Post-condition . 12g36.3.3.6 Exceptions . 12g36.4 Interface EPIRPNotifications (M) 13g36.4.1 Notification notifyIRPInfoChanges (M) 13g36.4.1.1 Definition 13g36.4.1.2 Input Parameters . 13g36.4.1.3 Triggering Event . 13g3ETSI ETSI TS 132 362 V15.0.0 (2018-
22、07)43GPP TS 32.362 version 15.0.0 Release 156.4.1.3.1 From-state 13g36.4.1.3.2 To-state 13g3Annex A (informative): Change history . 14g3History 15g3ETSI ETSI TS 132 362 V15.0.0 (2018-07)53GPP TS 32.362 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGenerat
23、ion 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 date an
24、d 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. technical e
25、nhancements, 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 Aspe
26、cts; Telecommunication management, as identified below: 32.361: “Entry Point (EP) Integration Reference Point (IRP): Requirements“. 32.362: “Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)“. 32.366: “Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) d
27、efintions“. The present document is part of a TS-family defining the Telecommunication Management (TM) of 3G systems. The TM principles are described in 3GPP TS 32.101 1. The TM architecture is described in 3GPP TS 32.102 2. The other specifications define the interface (Itf-N) between the managing
28、system (manager), which is in general the Network Manager (NM) and the managed system (agent), which is either an Element Manager (EM) or the managed NE itself. The Itf-N is composed of a number of Integration Reference Points (IRPs) defining the information in the agent that is visible for the mana
29、ger, the operations that the manager may perform on this information and the notifications that are sent from the agent to the manager. EP (Entry Point) IRP is one of these IRPs with special function. It is difficult for an NM to discover all IRPs in the environment that there are several managed sy
30、stems and/or if there are multiple IRPs related to each managed systems. This Entry Point is proposed to provide a convenient mechanism for NM to discover the managed systems and their related IRPs. ETSI ETSI TS 132 362 V15.0.0 (2018-07)63GPP TS 32.362 version 15.0.0 Release 151 Scope The present do
31、cument defines the Information Service (IS) part of the Entry Point IRP (EPIRP). It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way. The information is specified by means of Information Object Classes (IOCs) and SupportIOCs, and the
32、interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either
33、 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 (including a GSM document), a
34、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; Architecture“. 3 3GPP TS 32.401: “Te
35、lecommunication management; Performance Management (PM); Concept and requirements“. 4 3GPP TS 32.111-1: “Telecommunication management; Fault management; Part 1: 3G fault management requirements“. 5 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration
36、 Reference Point (IRP): Information Service (IS)“. 6 3GPP TS 32.361: “Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): Requirements“. 7 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point
37、 (IRP): Network Resource Model (NRM)“. 8 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management: Information Service (IS)“. 9 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management: Requirements“. 10 3GPP TS 32
38、.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions defined in 3GPP TS 32.101 1, 32.102 2, 32.150 10 32.361 6 and the following apply. IRPV
39、ersion: See 3GPP TS 32.311 9. SupportIOC: See 3GPP TS 32.150 10. ETSI ETSI TS 132 362 V15.0.0 (2018-07)73GPP TS 32.362 version 15.0.0 Release 153.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CORBA Common Object Request Broker Architecture DN Distinguis
40、hed Name EM Element ManagerEP Entry Point EPIRP Entry Point IRP IRP Integration Reference Point IOC Information Object Class IS Information Service NE Network Element NM Network ManagerNRM Network Resource Model PM Performance Management4 System Overview 4.1 System Context The general definition of
41、the System Context for the present IRP is found in 3GPP TS 32.150 10 subclause 4.7. In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below. EM IRPAgent NEs NotificationIRP NM IRPManager Itf-N IRPAgent EPIRP Figure 4.1: System Context A EPIRP Notificatio
42、nIRP NM IRPAgent NE IRPManager Itf-N Figure 4.2: System Context B 4.2 Compliance rules For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for operations, notifications and parameters (of operations and notifications) please refer to 3GPP TS 32.150 10 .
43、 ETSI ETSI TS 132 362 V15.0.0 (2018-07)83GPP TS 32.362 version 15.0.0 Release 155 Information Object Classes 5.1 Imported information entities and local labels Label reference Local label 3GPP TS 32.622 7, information object class, IRPAgent IRPAgent 3GPP TS 32.622 7, information attribute, systemDN
44、systemDN 3GPP TS 32.312 8, SupportIOC, ManagedGenericIRP ManagedGenericIRP 3GPP TS 32.312 8, information attribute, iRPId iRPId 5.2 Class diagram 5.2.1 Attributes and relationships This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for this IRP. This clause
45、 provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes. 5.2.2 Inheritance 5.3 Information Object Class definitions 5.3.1 EPIRP 5.3.1.1 Definition The EPIRP SupportIOC is used as an initial
46、 access point to the managed systems. This interface implements the entry point management capabilities defined by the present document. EPIRP inherits from the ManagedGenericIRP SupportIOC specified in 3GPP TS 32.312 8. How the NM gets the IRP Reference of the EPIRP is outside the scope of the pres
47、ent document. ETSI ETSI TS 132 362 V15.0.0 (2018-07)93GPP TS 32.362 version 15.0.0 Release 155.3.1.2 Attributes The EPIRP does not have any own attributes, only those inherited from ManagedGenericIRP. 6 Interface definition 6.1 Class diagram representing interfaces The following diagram depicts the
48、interfaces of EPIRPwith its corresponding operations and notifications. 6.2 Generic rules Rule 1: each operation with at least one input parameter supports a pre-condition valid_input_parameter which indicates that all input parameters shall be valid with regards to their information type. Additiona
49、lly, each such operation supports an exception operation_failed_invalid_input_parameter which is raised when pre-condition valid_input_parameter is false. The exception has the same entry and exit state. Rule 2: Each operation with at least one optional input parameter supports a set of pre-conditions supported_optional_input_parameter_xxx where “xxx“ is the name of the optional input parameter and the pre-condition indicates that the operation supports the named optional input parameter. Additionally, each such operation
