1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommEntry Point (EP) InInfor(3GPP TS 32.3TECHNICAL SPECIFICATION132 362 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; ) Integration Reference Point (ormation Service (IS) .362 version 13.0.0 Relea
2、se 1316-02) hase 2+); (UMTS); t (IRP); 13) ETSI ETSI TS 132 362 V13.0.0 (2016-02)13GPP TS 32.362 version 13.0.0 Release 13Reference RTS/TSGS-0532362vd00 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 34
3、8 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 print. The cont
4、ent 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 Portable Docu
5、ment 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:/portal.etsi.org
6、/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 mechanical, inc
7、luding 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 Telecommunications Standards
8、 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 logo are Tra
9、de Marks registered and owned by the GSM Association. ETSI ETSI TS 132 362 V13.0.0 (2016-02)23GPP TS 32.362 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 essent
10、ial 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. Latest updates
11、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 Web server)
12、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 identities o
13、r 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“, “shall not“,
14、“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 direct citatio
15、n. ETSI ETSI TS 132 362 V13.0.0 (2016-02)33GPP TS 32.362 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g3
16、4 System Overview . 7g34.1 System Context 7g34.2 Compliance rules 7g35 Information Object Classes 8g35.1 Imported 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 9g35.3.1 EPIRP 9g35.
17、3.1.1 Definition 9g35.3.1.2 Attributes . 9g36 Interface definition . 9g36.1 Class diagram representing interfaces 9g36.2 Generic rules 9g36.3 Interface EPIRPOperations (M) . 10g36.3.1 Operation getIRPOutline (M) . 10g36.3.1.1 Definition 10g36.3.1.2 Input parameters 10g36.3.1.3 Output parameters . 11
18、g36.3.1.4 Pre-condition . 11g36.3.1.5 Post-condition . 11g36.3.1.6 Exceptions . 11g36.3.2 Operation getIRPReference (M) 12g36.3.2.1 Definition 12g36.3.2.2 Input parameters 12g36.3.2.3 Output parameters . 12g36.3.2.4 Pre-condition . 12g36.3.2.5 Post-condition . 12g36.3.2.6 Exceptions . 12g36.3.3 Oper
19、ation releaseIRPReference (M) . 13g36.3.3.1 Definition 13g36.3.3.2 Input parameters 13g36.3.3.3 Output parameters . 13g36.3.3.4 Pre-condition . 13g36.3.3.5 Post-condition . 13g36.3.3.6 Exceptions . 13g36.4 Interface EPIRPNotifications (M) 14g36.4.1 Notification notifyIRPInfoChanges (M) 14g36.4.1.1 D
20、efinition 14g3ETSI ETSI TS 132 362 V13.0.0 (2016-02)43GPP TS 32.362 version 13.0.0 Release 136.4.1.2 Input Parameters . 14g36.4.1.3 Triggering Event . 14g36.4.1.3.1 From-state 14g36.4.1.3.2 To-state 14g3Annex A (informative): Change history . 15g3History 16g3ETSI ETSI TS 132 362 V13.0.0 (2016-02)53G
21、PP TS 32.362 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration 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 co
22、ntents of the present document, it will be re-released by the TSG with an identifying change of release 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
23、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 incorporated in the document. Introduction The present document is part of a T
24、S-family covering the 3rdGeneration Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management, as identified below: 32.361: “Entry Point (EP) Integration Reference Point (IRP): Requirements“ 32.362: “Entry Point (EP) Integration Reference Point (IRP
25、): Information Service (IS)“ 32.366: “Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) defintions“ 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 i
26、s described in 3GPP TS 32.102 2. The other specifications define the interface (Itf-N) between the managing 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 numb
27、er of Integration Reference Points (IRPs) defining the information in the agent that is visible for the manager, 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 f
28、unction. It is difficult for an NM to discover all IRPs in the environment that there are several managed systems 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
29、 IRPs. ETSI ETSI TS 132 362 V13.0.0 (2016-02)63GPP TS 32.362 version 13.0.0 Release 131 Scope The present document 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 independe
30、nt way. The information is specified by means of Information Object Classes (IOCs) and SupportIOCs, and the 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 w
31、hich, 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 reference, th
32、e 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 3GPP TS 32.101: “Telecommunication management; Principles and high leve
33、l requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.401: “Telecommunication management; Performance Management (PM); Concept and requirements“. 4 3GPP TS 32.111-1: “Telecommunication management; Fault management; Part 1: 3G fault management requirements“. 5
34、3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration 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: “Telecommunic
35、ation management; Configuration Management (CM); Generic network resources Integration Reference Point (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: “Telecommun
36、ication management; Generic Integration Reference Point (IRP) management: Requirements“. 10 3GPP TS 32.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 a
37、nd definitions defined in 3GPP TS 32.101 1, 32.102 2, 32.150 10 32.361 6 and the following apply. IRPVersion: See 3GPP TS 32.311 9. ETSI ETSI TS 132 362 V13.0.0 (2016-02)73GPP TS 32.362 version 13.0.0 Release 13SupportIOC: See 3GPP TS 32.150 10. 3.2 Abbreviations For the purposes of the present docu
38、ment, the following abbreviations apply: CORBA Common Object Request Broker Architecture DN Distinguished 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 R
39、esource Model PM Performance Management4 System Overview 4.1 System Context The general definition of 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
40、 NEs NotificationIRP NM IRPManager Itf-N IRPAgent EPIRP Figure 4.1: System Context A EPIRP NotificationIRP 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 operatio
41、ns, notifications and parameters (of operations and notifications) please refer to 3GPP TS 32.150 10 . 3GPP TS 32.362 version 13.0.0 Release 135 Information Obje5.1 Imported informatiLabel re3GPP TS 32.622 7, information object class,3GPP TS 32.622 7, information attribute, sy3GPP TS 32.312 8, Suppo
42、rtIOC, ManagedG3GPP TS 32.312 8, information attribute, iR5.2 Class diagram 5.2.1 Attributes and relatioThis clause depicts the set of classes (e.g. IOCprovides an overview of the relationships betwspecification of various aspects of these classe5.2.2 Inheritance ETSI ETSI TS 132 3628bject Classes a
43、tion entities and local labels reference IRPAgent IRPAgestemDN systemenericIRP ManagePId iRPId onships OCs) that encapsulates the information relevant for this IRet een relevant classes in UML. Subsequent clauses provss s. 6 V13.0.0 (2016-02)Local label nt DN dGenericIRP IRP. This clause ovide more
44、detailed 3GPP TS 32.362 version 13.0.0 Release 135.3 Information Objec5.3.1 EPIRP 5.3.1.1 Definition The EPIRP SupportIOC is used as an initial apoint management capabilities defined by theSupportIOC specified in 3GPP TS 32.312 8of the present document. 5.3.1.2 Attributes The EPIRP does not have any
45、 own attributes6 Interface definiti6.1 Class diagram repThe following diagram depicts the interfaces 6.2 Generic rules Rule 1: each operation with at least onindicates that all input parameters shaloperation supports an exception operatvalid_input_parameter is false. The ex Rule 2: Each operation wi
46、th at least onsupported_optional_input_parameter_condition indicates that the operation soperation supports an exception operatwhen (a) the pre-condition supported_parameter is carrying information. TheETSI ETSI TS 132 3629ect Class definitions al access point to the managed systems. This interface
47、impt e present document. EPIRP inherits from the Managed. How the NM gets the IRP Reference of the EPIRP ises, only those inherited from ManagedGenericIRP. ition representing interfaces es of EPIRPwith its corresponding operations and notificaone input parameter supports a pre-condition valid_input_
48、all be valid with regards to their information type. Additioration_failed_invalid_input_parameter which is raised whexception has the same entry and exit state. t one optional input parameter supports a set of pre-conditir_xxx where “xxx“ is the name of the optional input paramupports the named opti
49、onal input parameter. Additionalration_failed_unsupported_optional_input_parameter_xxxd_optional_input_parameter_xxx is false and (b) the namee exception has the same entry and exit state. 6 V13.0.0 (2016-02)m lements the entry GenericIRP outside the scope ications. u _parameter which nally, each such when pre-condition ditions ra eter and the pre-nally, each such xxx which is raised d optional input ETSI ETSI TS 132 362 V13.0.0 (2016-02)103GPP TS 32.362 version 13.0.0 Release 13 Rule 3: each operation shall suppor
