Content for TS 32.101 Word version: 17.0.0
5.5 Converged Management |R11| p. 26
5.5.1 Introduction to FNIM p. 26
On-going industry convergence and pressure to reduce cost is placing an ever-increasing emphasis on the need to rationalize and align various network management aspects across boundaries of standards/specifications producing organizations. The cost, resulting from integration and management challenges, of the lack of a coherent treatment of the whole network has becoming increasingly apparent to the point where operators of networks are demanding action.
The Federated Network Information Model [119] is covering all key aspects of a solution to the on-going industry convergence challenge. It focuses on Information Model federation and is constructed to best deal with the various contradictory pressures of the current environment providing a pragmatic and realizable approach.
5.5.2 FNIM Features p. 26
The following FNIM features are essential for the maintenance of the integrity of a large and scalable FMC network model:
- An FMC network model that is partitioned into model components.
- Defines an Umbrella Information Model (UIM) that is further partitioned to allow broad industry participation.
- Enables navigation among instances of different model components.
- Has the ability to import model elements designed elsewhere.
- Provides independence of tools and platforms.
- Is independent of solution technologies and access protocol designs.
- Utilizes industry experience.
- Supports release handling per model components.
5.5.3 FNIM Elements p. 27
5.5.3.1 FNIM components p. 27
The Umbrella Information Model (UIM) provides abstract definitions applicable across Domain/Technology-specific Concrete Models to enable end-to-end consistency of such definitions (it is described as 'abstract' in the sense that its components are used via "special linkages" by Domain/Technology-specific Concrete Models, and that it is not designed for the purpose of partial or full instantiation of its components and is not sufficient to provide meaningful network management service).
Domain/Technology-specific Concrete Models are described as 'concrete models' in the sense that their instantiation is necessary to provide meaningful management services. These Domain/Technology-specific Concrete Models uses "special linkages" with the common definitions of the Umbrella Information Model (UIM) for the purpose of end-to-end consistency of management information semantics. In addition, these Domain/Technology-specific Concrete Models have specified relationships between each other to enable end-to-end monitoring and management of a converged network.
5.5.3.2 Relations between model components (including UIM) p. 27
This section provides a graphical representation of the FNIM in terms of relation between model components.
There are two areas considered:
- The definitions of the classes inside the UIM model component.
- The definitions of relation (R0 in Figure 5.5.3.2-1) used between various classes in UIM model component and other model components.
Figure 5.5.3.2-1: Relation between UIM model component and other model components
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Taking the example of "3GPP wireless network classes" and the UIM, 3GPP model components would import relevant UIM classes and make derivatives for their use. R0 in this case is an inheritance relation. There are other forms of relations that could be defined.
5.5.3.3 Relations among pairs of model components p. 28
This section provides a graphical representation of the FNIM in terms of bilateral relation between each pair of model components, neither of which is a UIM model component.
The relation between pairs of model components may not be same. Each relation may or may not be symmetrical. UIM may not be involved in such pair-wise relations.
Figure 5.5.3.3-1: Relation between pairs of model components (not involving UIM model component)
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Taking the example of a relation between 3GPP model components and BBF ATM model components (i.e. R3 in the Figure above): the 3GPP model component would create a necessary 3GPP defined "ExternalIOC" representing one of the classes of "BBF ATM network and device classes". This type of relation is used extensively in the 3GPP IRP framework for the purpose of navigation from one managed domain to another.
