4.2 MnS components

28.5333GPPArchitecture frameworkManagement and orchestrationRelease 17TS

4.2.1 Introduction

A MnS is specified using different independent components. A concrete MnS is composed of at least two of these components. Three different component types are defined, called MnS component type A, MnS component type B and MnS component type C. These components are defined in the following clauses.

4.2.2 MnS component type A

The MnS component type A is a group of management operations and/or notifications that is agnostic with regard to the entities managed. The operations and notifications as such are hence not involving any information related to the managed network. These operations and notifications are called generic or network agnostic.

For example, operations for creating, reading, updating and deleting managed object instances, where the managed object instance to be manipulated is specified only in the signature of the operation, are generic.

4.2.3 Management information

4.2.3.1 MnS component type B

MnS component type B refers to management information represented by information models representing the managed entities. A MnS component type B is also called Network Resource Model (NRM).

MnS component type B examples are:

1) Network resource models as defined in TS 28.622 [32].

2) Network resource models as defined in TS 28.541 [4]

4.2.3.2 MnS component type C

MnS component type C is performance information of the managed entity and fault information of the managed entity.

The following are examples of Management service component type C:

1. Alarm information as defined in TS 28.532 [9] and TS 28.545 [28].

2. Performance data as defined in TS 28.552 [5], TS 28.554 [6] and TS 32.425 [7].

4.2.4 MnS producer profile

A MnS producer is described by a set of meta data called MnS producer profile. The profile holds information about the supported MnS components and their version numbers. This may include also information about support of optional features. For example, a read operation on a complete subtree of managed object instances may support applying filters on the scoped set of objects as optional feature. In this case the MnS profile should include the information if filtering is supported.