Network resource

Description

In 3GPP management specifications, a network resource is defined as a discrete entity represented by an Information Object Class (IOC) for the purpose of network and service management. This definition appears in TS 28.622 and TS 32.612, which are part of the 3GPP management and orchestration framework. The concept is central to the way 3GPP models managed networks: everything that can be managed is represented as a resource, and each resource is an instance of an IOC. This object-oriented approach allows for a consistent and extensible way to describe network elements, their attributes, and their relationships.

An Information Object Class is a template that defines the properties and behaviour of a type of resource. For example, there might be an IOC for a "ManagedElement", which represents a network element such as a base station or a core network node. The IOC defines attributes such as the element's identifier, its operational state, and its capabilities. When a specific network element is deployed, it is represented as an instance of that IOC, i.e., a network resource. This instance has values for the attributes defined in the IOC. The management system can then interact with the resource by reading or modifying its attributes, invoking operations, or receiving notifications.

The use of IOCs and resources is part of the 3GPP management architecture, which is based on the principles of the Telecommunication Management Network (TMN) and the ITU-T's Common Management Information Protocol (CMIP), later adapted to use CORBA and then RESTful interfaces. In modern 3GPP management, the representation is often in the form of YANG models for RESTful APIs, but the underlying concept of IOCs remains. The resource model provides a standardised way to describe network functions, their configuration, and their performance. This enables multi-vendor interoperability, as different vendors' equipment can be managed using the same information model.

Network resources can be physical or logical. Physical resources include hardware components such as antennas, processors, and ports. Logical resources include software functions, network slices, and bearers. The management system can create, modify, and delete resources as needed. For example, in network slicing, a network slice is a resource that can be instantiated and managed. The resource model also supports relationships between resources, such as containment (a resource contains other resources) and association (resources are linked). This allows for a hierarchical representation of the network, from the network level down to individual components.

The definition of network resource was introduced in Release 15, which is the first release of 5G specifications. This timing reflects the increased focus on management and orchestration in 5G, particularly for network slicing and virtualised networks. The definition has remained unchanged through Release 20, indicating its stability. The concept is fundamental to the 3GPP management framework and is used extensively in specifications for fault management, configuration management, performance management, and assurance. As networks become more dynamic and software-driven, the resource model continues to evolve, but the core idea of representing managed entities as IOCs remains.

Purpose & Motivation

The concept of a network resource was created to provide a standardised way to model and manage network elements in 3GPP networks. Before this, management interfaces were often vendor-specific, making it difficult for operators to integrate multi-vendor networks. The introduction of a common information model, based on IOCs, allowed for interoperability and simplified management. The network resource is the concrete representation of a managed entity, enabling operators to configure, monitor, and troubleshoot their networks using a consistent set of operations.

The motivation for this concept became stronger with the advent of 5G, which introduced network slicing, virtualisation, and a service-based architecture. These features require a flexible and dynamic management system that can handle the lifecycle of network functions and slices. The network resource model provides the necessary abstraction to manage these complex entities. It allows the management system to treat physical and logical resources uniformly, and to automate management tasks through standardised APIs. This is essential for achieving the operational efficiency and agility promised by 5G.

Furthermore, the definition of network resource as a discrete entity represented by an IOC aligns with the object-oriented design principles that have been used in telecom management for decades. It provides a clear separation between the information model (the IOCs) and the data model (the instances). This separation allows the information model to be extended without affecting existing implementations, and it facilitates the development of generic management tools. The term has been carried over unchanged since its introduction, demonstrating its fundamental role in the 3GPP management architecture. As networks continue to evolve towards 6G, the concept of a network resource will remain a cornerstone of management and orchestration.