ETSI TS 132 353-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Communication Surveill.pdf

1、 ETSI TS 132 353 V9.0.0 (2010-02)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Communication Surveillance (CS) Integration Reference Point (IRP);Common Object Request Broker Architectur

2、e (CORBA)Solution Set (SS) (3GPP TS 32.353 version 9.0.0 Release 9)ETSI ETSI TS 132 353 V9.0.0 (2010-02)13GPP TS 32.353 version 9.0.0 Release 9Reference RTS/TSGS-0532353v900 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

3、 93 65 47 16 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 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 elec

4、tronic version 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 wit

5、hin 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/tb/status/status.asp If you find errors in the present docume

6、nt, please send 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 Teleco

7、mmunications Standards 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 Organizatio

8、nal Partners. LTE 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 353 V9.0.0 (2010-02)23GPP TS 32.353 version 9.0.0 Release 9I

9、ntellectual 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, and can be found in ETSI SR 000 314: “Intellectual Property

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

11、g 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. Foreword This Technical Specification (TS) has b

12、een 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. The cross refe

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

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

15、r mapping . 8g36 CSIRPNotification Interface 10g36.1 Method push (M) 10g3Annex A (normative): IDL specifications 11g3A.1 IDL specification (file name “CSIRPConstDefs.idl“) 11g3A.2 IDL specification (file name “CSIRPSystem.idl“) . 12g3A.3 IDL specification (file name “CSIRPNotifications.idl“) 14g3Ann

16、ex B (informative): Change history . 15g3History 16g3ETSI ETSI TS 132 353 V9.0.0 (2010-02)43GPP TS 32.353 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing wor

17、k 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 version number as follows: Version x.y.z where: x the first digit: 1 presented to

18、 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, corrections, updates, etc. z the third digit is incremented when editorial only chang

19、es 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; Telecommunication management; as identified below: TS 32.351: “Communication Surveillance (CS

20、) Integration Reference Point (IRP): Requirements“; TS 32.352: “Communication Surveillance (CS) Integration Reference Point (IRP): Information Service (IS)“; TS 32.353: “Communication Surveillance (CS) Integration Reference Point (IRP): Object Request Broker Architecture (CORBA) Solution Set (SS)“;

21、The present document is part of a set of technical specifications 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

22、 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 number of integration reference points (IRPs) defining the information in the agent that is visible fo

23、r the manager, the operations that the manager may perform on this information and the notifications that are sent from the agent to the manager. CS (Communication Surveillance) IRP is one of these IRPs with special function. To ensure the availability and reliability of the management, an automatic

24、 surveillance of the communication between NM and the managed system are required. CSIRP is defined as a capability to achieve this goal. ETSI ETSI TS 132 353 V9.0.0 (2010-02)53GPP TS 32.353 version 9.0.0 Release 91 Scope The present document specifies the CORBA Solution Set for the IRP whose semant

25、ics are specified in TS 32.352 6 Communication Surveillance IRP: Information Service. This Solution Set specification is related to 3GPP TS 32.352 V9.0.X. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. Ref

26、erences 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, the latest version applies. In the case of a reference to a 3GPP document (including a GSM

27、 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 level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP

28、TS 32.351: “Telecommunication management; Communication Surveillance (CS) 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

29、Integration Reference Point (IRP): Requirements“. 6 3GPP TS 32.352: “Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP): Information Service (IS)“. 7 3GPP TS 32.303: “Telecommunication management; Configuration Management (CM); Notification Integration Re

30、ference Point (IRP): Common Object Request 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 Manag

31、ed Objects“. 3 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.351 3 and 3GPP TS 32.352 6 and the following apply: IRP document version number string (or “IRPVersion“): see 3GPP

32、TS 32.311 5. ETSI ETSI TS 132 353 V9.0.0 (2010-02)63GPP TS 32.353 version 9.0.0 Release 93.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CORBA Common Object Request Broker Architecture CS Communication Surveillance CSIRP Communication Surveillance IRP D

33、N Distinguished Name EM Element ManagerIRP Integration Reference Point IOC Information Object Class IS Information Service NE Network ElementNM Network Manager SS Solution Set 4 Architectural features The overall architectural feature of CSIRP is specified in 3GPP TS 32.352 6. This clause specifies

34、features that are 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 CSIRP notifications are defined in the present document. 4.2 Syntax for Distinguished Names and versions The format of a Distin

35、guished Name is defined in 3GPP TS 32.300 9. The version of this IRP is represented as a string (see also clause 3 for versions). 5 Mapping 5.1 Operation and Notification mapping CSIRP: IS 3GPP TS 32.352 6 defines semantics of operation and notification visible across the CSIRP. Table 1 indicates ma

36、pping 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.352 6 SS Method Qualifier getHeartbeatPeriod get_heartbeat_period MsetHeartbeatPeriod set_heartbeat_period Otr

37、iggerHeartbeat trigger_heartbeat MnotifyHeartbeat push_structured_event (See clause 6.1) M getIRPVersion (see note) get_cs_irp_versions M getOperationProfile (see note) get_cs_irp_operations_profile O getNotificationProfile (see note) get_cs_irp_notification_profile O NOTE: This operation is of Mana

38、gedGenericIRP IOC specified in 3GPP TS 32.312 4. The CSIRP IOC of TS 32.352 6 inherits from it. ETSI ETSI TS 132 353 V9.0.0 (2010-02)73GPP TS 32.353 version 9.0.0 Release 95.2 Operation parameter mapping The CSIRP: IS 3GPP TS 32.352 6 defines semantics of parameters carried in operations across the

39、CSIRP. The following tables indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS. Table 2: Mapping from IS getHeartbeatPeriod parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier heartbeatPeriod CSIRPConstDefs:HeartbeatPerio

40、d heartbeat_period Mstatus Return value of type CSIRPConstDefs:Result Exception: GetHeartbeatPeriod M Table 3: Mapping from IS setHeartbeatPeriod parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier heartbeatPeriod CSIRPConstDefs:HeartbeatPeriod heartbeat_period Mstatus

41、Return value of type CSIRPConstDefs:Result Exception: SetHeartbeatPeriod, InvalidHeartbeatPeriod, ConflictingHeartbeatPeriod, ManagedGenericIRPSystem:ValueNotSupported, ManagedGenericIRPSystem:OperationNotSupported M Table 4: Mapping from IS triggerHeartbeat parameters to SS equivalents IS Operation

42、 parameter SS Method parameter Qualifier managerIdentifier CSIRPConstDefs:ManagerIdentifier manager_identifier Mstatus Return value of type CSIRPConstDefs:Result Exception: TriggerHeartbeat, InvalidManagerIdentifier M NOTE: For CORBA SS, the managerIdentifier of triggerHeartbeat operation shall be m

43、apped to managerReference which is same as what IRPManager used to subscribe notifications 7. Table 5: Mapping from IS getIRPVersion parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier versionNumberSet Return value of type ManagedGenericIRPConstDefs:VersionNumberSet M s

44、tatus Exception: GetCSIRPVersions M Table 6: Mapping from IS getOperationProfile parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier iRPVersion ManagedGenericIRPConstDefs:VersionNumber irp_version MoperationNameProfile, operationParameterProfile Return value of type Man

45、agedGenericIRPConstDefs:MethodList M status Exception: GetCSIRPOperationsProfile, ManagedGenericIRPSystem:OperationNotSupported, ManagedGenericIRPSystem:InvalidParameter M Table 7: Mapping from IS getNotificationProfile parameters to SS equivalents IS Operation parameter SS Method parameter Qualifie

46、r iRPVersion ManagedGenericIRPConstDefs:VersionNumber irp_version MnotificationNameProfile, notificationParameterProfile Return value of type ManagedGenericIRPConstDefs:MethodList M status Exception: GetCSIRPNotificationProfile, ManagedGenericIRPSystem:OperationNotSupported, ManagedGenericIRPSystem:

47、InvalidParameter M ETSI ETSI TS 132 353 V9.0.0 (2010-02)83GPP TS 32.353 version 9.0.0 Release 95.3 Notification parameter mapping The semantics of parameters carried in notifications are defined in CSIRP IS (3GPP TS 32.352 6). Table 8 indicates the mapping of these parameters to their OMG CORBA Stru

48、ctured Event 8 equivalents. The composition of OMG Structured Event, as defined in 8 is: Header Fixed Header domain_name type_name event_name Variable Header Body filterable_body_fields remaining_body Table 8 lists in the second column all OMG Structured Event attributes. The first column identifies

49、 the notification parameters defined in CSIRP IS (3GPP TS 32.352 6). ETSI ETSI TS 132 353 V9.0.0 (2010-02)93GPP TS 32.353 version 9.0.0 Release 9Table 8: Mapping for notifyHeartBeat IS Parameters OMG CORBA Structured Event attribute Qualifier Comment There is no corresponding IS attribute. domain_name M It carries the IRP document version number string. See clause 3.1. It indicates the syntax and semantics of the Structured Event as defined by the present document. notificationType type_name M