4 System overview

32.106-53GPPConfiguration Management (CM)Part 5: Basic CM Integration Reference Point (IRP): Information model (including Network Resource Model (NRM)Telecommunication managementTS

4.1 System context

Figure 2 and Figure 3 identify system contexts of the subject IRP in terms of its implementation called IRPAgent and the user of the IRPAgent, called IRPManager. For a definition of IRPManager and IRPAgent, see 3GPP TS 32.102 [2].

The IRPAgent implements and supports the Basic CM IRP. The IRPAgent can be an Element Manager (EM) or a mediator that interfaces one or more NEs (see Figure 2), or it can be a Network Element (NE) (see Figure 3). In the former case, the interfaces (represented by a thick dotted line) between the EM and the NEs are not subject of this IRP.

An IRPManager using this IRP shall choose one of the two System Contexts defined here, for each NE. For instance, if an EM is responsible for managing a number of NEs, the NM shall access this IRP through the EM and not directly to those NEs. For another IRP though, the System Context may be different.

NEs

EM

IRPAgent

IRPManager

NM

Itf-N

Notification IRP Basic CM IRP

Figure 2: System Context A

IRPManager

NM

Itf-N

NE

IRPAgent

Notification IRP Basic CM IRP

Figure 3: System Context B

4.2 Compliance rules

For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for operations, notifications and parameters (of operations and notifications) please refer to 3GPP TS 32.102 [2].

The following defines the meaning of Mandatory and Optional MOC attributes and associations between MOCs, in Solution Sets to the Basic CM IRP:

  • The IRPManager shall support all mandatory attributes/associations. The IRPManager shall be prepared to receive information related to mandatory as well as optional attributes/associations without failure; however the IRPManager does not have to support handling of the optional attributes/associations.
  • The IRPAgent shall support all mandatory attributes/associations. It may support optional attributes/associations.

An IRPAgent that incorporates vendor-specific extensions shall support normal communication with a 3GPP SA5‑compliant IRPManager with respect to all Mandatory and Optional managed object classes, attributes, associations, operations, parameters and notifications without requiring the IRPManager to have any knowledge of the extensions.

Given that

  • rules for vendor-specific extensions remain to be fully specified, and
  • many scenarios under which IRPManager and IRPAgent interwork may exist,

it is recognised that in Release 4/5 the IRPManager, even though it is not required to have knowledge of vendor-specific extensions, may be required to be implemented with an awareness that extensions can exist and behave accordingly.