5 NRM IRP SS template

32.1533GPPIntegration Reference Point (IRP) technology specific templates, rules and guidelinesRelease 17Telecommunication managementTS

This clause contains the NRM IRP SS template.

The clauses in this template (that shall be used in the SS specifications) are numbered starting with "X", which in general should correspond to clause 4 that is the beginning of the normative part of a TS. However, if there is a need in a specific SS to introduce additional clauses in the TS body, X may correspond to a number higher than 4.

The introductory clauses (from clause 1 to clause 3) for the SS should be modelled similarly to that of this specification.

Usage of fonts shall be according to the following table.

Table: Usage of fonts

Item	Font
Class names	Courier New
Attribute names	Courier New
Assertion names	Courier New
Notification names	Courier New
State names	Arial
Enumerated values	Arial

X Architectural Features

"X" represents a clause number in the actual SS. It contains at least the following subclause:

X.1 General

This subclause contains the following paragraph:

"The overall architectural feature of <subject IRP> is specified in 3GPP TS <relevant specification number> [<relevant reference>]. This clause specifies features that are specific to the <specific technology> SS.".

Example:

"The overall architectural feature of UTRAN Network Resources IRP is specified in 3GPP TS 28.652 [17].
This clause specifies features that are specific to the CORBA SS."

X.a <Feature [a-1]>

<Description of architectureal feature “a”>

"a" represents a number, starting at 2 and increasing by 1 with each new feature.

NOTE: This subclause is optional.

Y Mapping

"Y" represents a number, immediately following "X".

Y.1 General

This subclause contains a general introduction to the mapping.

For CORBA SSs, it contains the following paragraph:

"Attributes modelling associations as defined in the NRM (here also called "reference attributes") are in this SS mapped to attributes. The names of the reference attributes in the NRM are mapped to the corresponding attribute names in the MOC. When the cardinality for an association is 0..1 or 1..1 the datatype for the reference attribute is defined as an MOReference. The value of an MO reference contains the distinguished name of the associated MO. When the cardinality for an association allows more than one referred MO, the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references."

For XML FF specifications, it contains the following paragraph:

“An IOC maps to an XML element of the same name as the IOC’s name in the IS. An IOC attribute maps to a sub-element of the corresponding IOC’s XML element, and the name of this sub-element is the same as the attribute’s name in the IS.”

Y.2 Information Object Class (IOC) mapping

This subclause is only applicable to NRM IRP CORBA Solution Sets. This clause contains the mapping tables of all iS-defined IOCs to corresponding SS-level MOCs, excluding those inherited.

Y.2.a IOC <IOC name >

It contains one table with Mapping from NRM IS IOC attribute name to the SS equivalent MOC attribute name and attribute types.

"a" in the subclause heading represents a number, starting at 1 and increasing by 1 for each IOC.

Attribute of IOC <IOC name > in 3GPP TS <relevant TS number> [<relevant reference number>]	SS Attribute	SS Type	Support Qualifier	Read Qualifier	Write Qualifier
attribute-a	attribute-1	<type>	…	…	…
attribute-b	attribute-2	<type>	…	…	…
…	…	…	…	…	…

Y.2 Information Object Class (IOC) mapping

This subclause is only applicable to NRM IRP XML FF specifications. This subclause describes the mapping of all IS-defined IOCs to corresponding XML definitions, excluding the inherited IOCs.

Note: This subclause is also numbered Y.2, directly following Y.1, since every NRM SS-level TS is made for only one SS technology.

Annex A (normative):
General rules for Solution Sets (SS)