A.3 IDL specification (file name " EPIRPNotifications.idl")

32.3633GPPCommon Object Request Broker Architecture (CORBA) Solution Set (SS)Entry Point (EP) Integration Reference Point (IRP)Release 9Telecommunication managementTS

//File: EPIRPNotifications.idl

#ifndef _EP_IRP_NOTIFICATIONS_IDL_

#define _EP_IRP_NOTIFICATIONS_IDL_

#include <NotificationIRPNotifications.idl>

#include <EPIRPConstDefs.idl>

// This statement must appear after all include statements

#pragma prefix "3gppsa5.org"

/* ## Module: EPIRPNotifications

*/

module EPIRPNotifications

{

interface NotifyIRPInfoChanges: NotificationIRPNotifications::Notify

{

const string ET_IRPINFO_CHANGES = "notifyIrpInfoChanges";

/**

* This constant defines the name of the iRPDn property.

* The data type for the value of this property

* is DN.

*/

const string IRP_DN =

EPIRPConstDefs::AttributeNameValue::IRP_DN;

/**

* This constant defines the name of the changeMode property.

* The data type for the value of this property is ChangeMode.

*/

const string CHANGE_MODE =

EPIRPConstDefs::AttributeNameValue::CHANGE_MODE;

/**

* This constant defines the name of the additionalText property.

* The data type for the value of this property is string.

*/

const string ADDITIONAL_TEXT =

EPIRPConstDefs::AttributeNameValue::ADDITIONAL_TEXT;

};

};

#endif // _EP_IRP_NOTIFICATIONS_IDL_

Annex B (informative):
Convention when using INS to fulfill part of EPIRP functions

The implementation of the EPIRP and in particular, the management of CORBA object references within EPIRP, is not a subject matter for 3GPP standardization.

ITU-T SG4 Framework for CORBA-Based Telecommunications Management Network Interfaces (ITU-T Recommendation Q.816.1 [10]) uses OMG Interoperable Naming Service (INS) [11] for the management of CORBA object references. Furthermore, it specifies a convention to name and populate the CORBA object entries within the INS.

This Annex notes that, in the event that an EPIRP implementation uses INS to fulfill part of EPIRP functions, it is advantageous to populate the INS using the ITU-T defined convention.

Convention

The OMG INS CORBA name component (in short, called CORBA compound name) has the following IDL definition:

// IDL

typedef string Istring;

struct NameComponent {

Istring id;

Istring kind;

};

Istring is a placeholder for a future IDL internationalized string. The id and kind attributes must be composed of characters from the ISO 8859-1 [12] character set, excluding the null character and other non-printable characters. The strings cannot exceed 255 characters. The id attribute cannot be an empty string but the kind attribute can be an empty string.

The CORBA compound name (see Name below) is defined as a sequence of name components:

// IDL

typedef sequence<NameComponent> Name;

The 3GPP defined DN (in short, called DN) of a managed object is represented by the CORBA compound name. For example, a DN, quoted from 3GPP TS 32.300 [9], say “DC=se.companyZ.lmc,Network=9,SubNetwork=1,IRPAgent=1,AlarmIRP.iRPId=2”, shall be represented by a sequence of 6 name components where the id and kind of the first name component shall be “se_companyZ_lmc” and “DC” respectively. The CORBA compound name, shall be:

index

kind

id

0

“DC”

“se_companyZ_lmc”

1

“Network”

“9”

2

“SubNetwork”

“1”

3

“IRPAgent”

“1”

4

“AlarmIRP.iRPId”

“2”

5

“”

“Object”

The CORBA compound name, in stringified name form, shall be “se_companyZ_lmc.DC/9.Network/1.SubNetwork/1.IRPAgent/2.AlarmIRP.iRPId/Object”.

NOTE 1: DN appears in interactions (e.g. operations, notifications) across the Itf‑N.

NOTE 2: The CORBA compound name is used internally with the IRPAgent (and its INS) and does not appear in interactions across the Itf-N.

The use of the last row of the CORBA compound name, i.e. kind == “” and id ==”Object”, is in accordance to the convention standardized by ITU-T Recommendation Q.816.1 [10]. According to convention standardized by ITU-T Recommendation Q.816.1 [10], the use of index 0 to 4 inclusive is to indicate the naming context of the object and the use of index 0 to 5 inclusive is to indicate the object itself.

DN DC component is composed of multiple words separated by separator, i.e. a dot. It is suggested that the applications (e.g. IRPAgent codes) that process CORBA compound name and DN should map the dot, used as separator in DN DC component, with underscore. This mapping is necessary because in the stringified CORBA compound name, the dot is used for the separation of id and kind. This replacement rule also implies that underscore should not be used as character of DC words.

Annex C (informative):
Change history

Change history

Date

TSG #

TSG Doc.

CR

Rev

Subject/Comment

Cat

Old

New

Sep 2003

SA_21

SP-030425

Submitted to TSG SA#21 for Information

1.0.0

Dec 2003

SA_22

SP-030636

Submitted to TSG SA#22 for Approval

2.0.0

6.0.0

Jun 2004

SA_24

SP-040248

0001

Clarification of return value of getIRPReference and Correction of Distinguished Name (DN) and IDL errors

F

6.0.0

6.1.0

Dec 2004

SA_26

SP-040877

0002

1

Correct mapping of IS-defined non-filterable parameters to SS-defined non-filterable fields, Eliminate new definitions in EP IRP CORBA SS

F

6.1.0

6.2.0

Mar 2005

SA_27

SP-050039

0003

IDL incompliant to the style guide

F

6.2.0

6.3.0

Mar 2005

SA_27

SP-050039

0004

Align EPIRPSystem IDL structure with TS 32.150

F

6.2.0

6.3.0

Sep 2005

SA_29

SP-050461

0005

Align the CORBA SS IDL with TS 32.150 Style Guide

F

6.3.0

6.4.0

Jun 2007

SA_36

Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards.

6.4.0

7.0.0

Sep 2007

SA_37

SP-070614

0006

Use IRP class name to method parameter – Align with 32.362 IS

C

7.0.0

8.0.0

Mar 2009

SA_43

SP-090207

0007

Include reference to SOAP Solution Set specification

D

8.0.0

8.1.0

Sep 2009

SA-45

SP-090534

0008

Correction of rDN attribute in IDL for CORBA compliance.

F

8.1.0

8.2.0

2009-12

Update to Rel-9 version (MCC)

8.2.0

9.0.0