ETSI TS 132 363-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Entry Point (EP) Integ.pdf

1、 ETSI TS 132 363 V9.0.0 (2010-02)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Entry Point (EP) Integration Reference Point (IRP);Common Object Request Broker Architecture (CORBA)Soluti

2、on Set (SS) (3GPP TS 32.363 version 9.0.0 Release 9)ETSI ETSI TS 132 363 V9.0.0 (2010-02)13GPP TS 32.363 version 9.0.0 Release 9Reference RTS/TSGS-0532363v900 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 Si

3、ret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version

4、or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secret

5、ariat. 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 send

6、 your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications St

7、andards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. L

8、TE is a Trade Mark of ETSI currently being 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 363 V9.0.0 (2010-02)23GPP TS 32.363 version 9.0.0 Release 9Intellectual Pro

9、perty 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, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs);

10、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 (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches,

11、 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. Foreword This Technical Specification (TS) has been produced by

12、 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. The cross reference between G

13、SM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 363 V9.0.0 (2010-02)33GPP TS 32.363 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and

14、 abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Architectural features . 6g34.1 Notifications . 6g34.2 Syntax for Distinguished Names and versions . 6g35 Mapping . 7g35.1 Operation and Notification mapping 7g35.2 Operation parameter mapping 7g35.3 Notification parameter mapping . 8g3

15、6 EPIRPNotification Interface . 10g36.1 Method push (M) 10g3Annex A (normative): IDL specifications 11g3A.1 IDL specification (file name “EPIRPConstDefs.idl“) 11g3A.2 IDL specification (file name “EPIRPSystem.idl“) . 13g3A.3 IDL specification (file name “ EPIRPNotifications.idl“) . 15g3Annex B (info

16、rmative): Convention when using INS to fulfill part of EPIRP functions . 16g3Annex C (informative): Change history . 18g3History 19g3ETSI ETSI TS 132 363 V9.0.0 (2010-02)43GPP TS 32.363 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Pr

17、oject (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 increase in v

18、ersion 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 enhancements, corre

19、ctions, 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 Aspects; Telecommunica

20、tion 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.363: “Entry Point (EP) Integration Reference Point (IRP): Common Object Request Broker Architectu

21、re (CORBA) Solution Set (SS)“ 32.365: “Entry Point (EP) Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“ 32.367: “Entry Point (EP) Integration Reference Point (IRP): SOAP Solution Set (SS)“ The present document is part of a set of technical specifications defining the

22、 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 system (manager), which is in general the Network Manager (NM) and t

23、he 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 manager, the operations that the manager may perform on this information

24、 and the notifications that are sent from the agent to the manager. EP (Entry Point) IRP is one of these IRPs with special function. Its 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 system

25、s. 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 363 V9.0.0 (2010-02)53GPP TS 32.363 version 9.0.0 Release 91 Scope The present document specifies the CORBA Solution Set for the IRP whose semantics are s

26、pecified in the Entry Point IRP: Information Service (3GPP TS 32.362 6). This Solution Set specification is related to 3GPP TS 32.362 V9.0.X. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are e

27、ither 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

28、 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.361: “T

29、elecommunication management; Entry Point (EP) Integration Reference Point (IRP): Requirements“. 4 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP): Information Service (IS)“. 5 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point

30、(IRP): Requirements“. 6 3GPP TS 32.362: “Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)“. 7 3GPP TS 32.303: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request

31、Broker Architecture (CORBA) Solution Set (SS)“. 8 OMG TC Document telecom/98-11-01: “OMG Notification Service“. http:/www.omg.org/technology/documents/ 9 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 10 ITU-T Recommendation Q.816.

32、1 Recommendation “CORBA based TMN services: Extensions to support coarse-grained interfaces“. 11 OMG TC Document telecom/98-12-09: “CORBAservices: Common Object Services Specification“. http:/www.omg.org/technology/documents/ 12 ISO 8859-1: “Information technology - 8-bit single-byte coded graphic c

33、haracter sets - Part 1: Latin alphabet No. 1“. ETSI ETSI TS 132 363 V9.0.0 (2010-02)63GPP TS 32.363 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions defined in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.361

34、 3 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 5. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CORBA Common Object Request Broker Architecture DN Distinguished Name EM Element ManagerEP Entry Poin

35、t EPIRP Entry Point IRP IRP Integration Reference Point IOC Information Object Class IS Information Service NE Network Element NM Network ManagerSS Solution Set 4 Architectural features The overall architectural feature of EPIRP is specified in 3GPP TS 32.362 6. This clause specifies features that a

36、re specific to the CORBA SS. 4.1 Notifications Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.303 7). The contents of the EPIRP notifications are defined in the present document. 4.2 Syntax for Distinguished Names and versions The format of a Distinguished Name is

37、 defined in 3GPP TS 32.300 9. The version of this IRP is represented as a string (see also clause 3 for versions). ETSI ETSI TS 132 363 V9.0.0 (2010-02)73GPP TS 32.363 version 9.0.0 Release 95 Mapping 5.1 Operation and Notification mapping EPIRP: IS (3GPP TS 32.362 6) defines semantics of operation

38、and notification visible across the EPIRP. Table 1 indicates the mapping of these operations and notifications to their equivalents defined in this SS. Table 1: Mapping from IS Operations and Notification to SS equivalents IS Operations/ notification TS 32.362 6 SS Method Qualifier getIRPOutline get

39、_irp_outline MgetIRPReference get_irp_reference MreleaseIRPReference release_irp_reference MnotifyIRPInfoChanges push_structured_event (See clause 6.1) M getIRPVersion (see note) get_ep_irp_versions M getOperationProfile (see note) get_ep_irp_operations_profile O getNotificationProfile (see note) ge

40、t_ep_irp_notification_profile O NOTE: This operation is of ManagedGenericIRP IOC specified in 3GPP TS 32.312 4. The EPIRP IOC of 3GPP TS 32.362 6 inherits from it. 5.2 Operation parameter mapping The EPIRP: IS 3GPP TS 32.362 6 defines semantics of parameters carried in operations across the EPIRP. T

41、he following tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS. Table 2: Mapping from IS getIRPOutline parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier iRPVersion ManagedGenericIRPConstDefs:VersionNumber irp_ve

42、rsion MsupportedIRPList EPIRPConstDefs:SupportedIRPList supported_irp_list M status Return value of type EPIRPConstDefs:Result Exception: GetIRPOutline, InvalidIRPVersion M Table 3: Mapping from IS getIRPReference parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier mana

43、gerIdentifier EPIRPConstDefs:ManagerIdentifier manager_identifier M systemDn EPIRPConstDefs:DN system_dn MrDN EPIRPConstDefs:RDN r_DN M iRPReference string irp_reference (stringified IOR) M status Return value of type EPIRPConstDefs:Result Exception: GetIRPReference, ManagedGenericIRPSystem:InvalidP

44、arameter M Table 4: Mapping from IS releaseIRPReference parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier managerIdentifier EPIRPConstDefs:ManagerIdentifier manager_identifier M iRPReference string irp_reference (stringified IOR) M status Return value of type EPIRPCon

45、stDefs:Result Exception: ReleaseIRPReference, UnknownIRPReference M ETSI ETSI TS 132 363 V9.0.0 (2010-02)83GPP TS 32.363 version 9.0.0 Release 9Table 5: Mapping from IS getIRPVersion parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier versionNumberSet Return value of ty

46、pe ManagedGenericIRPConstDefs:VersionNumberSet M status Exception: GetEPIRPVersions M Table 6: Mapping from IS getOperationProfile parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier iRPVersion ManagedGenericIRPConstDefs:VersionNumber irp_version M operationNameProfile,

47、 operationParameterProfile Return value of type ManagedGenericIRPConstDefs:MethodList M status Exception: GetEPIRPOperationsProfile, ManagedGenericIRPSystem:OperationNotSupported, ManagedGenericIRPSystem:InvalidParameter M Table 7: Mapping from IS getNotificationProfile parameters to SS equivalents

48、IS Operation parameter SS Method parameter Qualifier iRPVersion ManagedGenericIRPConstDefs:VersionNumber irp_version M notificationNameProfile, notificationParameterProfile Return value of type ManagedGenericIRPConstDefs:MethodList M status Exception:GetEPIRPNotificationProfile, ManagedGenericIRPSys

49、tem:OperationNotSupported, ManagedGenericIRPSystem:InvalidParameter M 5.3 Notification parameter mapping The EPIRP: IS (3GPP TS 32.362 6) defines semantics of parameters carried in notifications. The following table indicates the mapping of these parameters to their OMG CORBA Structured Event (defined in OMG Notification Service 8) equivalents. The composition of OMG Structured Event, as defined in the OMG Notification Service 8, is: Header Fixed Header domain_name type_name event_name Var