Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

Logical O&M

Logical Operations and Maintenance

Management →

Logical O&M is the signaling within NBAP that enables the RNC to control the logical resources, such as channels and cells, which it owns but are physically implemented in the Node B.

Introduced
Rel-4
Where
Services
Specifications
1 specs
Logical O&M Description Purpose What changed Neighbours Specifications

Description

Logical O&M (Operations and Maintenance) is a concept introduced in 3GPP Release 4 within the UTRAN architecture. It refers to the signalling associated with the control of logical resources—such as channels and cells—that are owned by the Radio Network Controller (RNC) but physically implemented in the Node B (base station). The RNC is responsible for managing these logical resources, while the Node B executes the physical implementation. Because certain O&M procedures executed in the Node B affect these logical resources, an information exchange between the RNC and Node B is required. All messages supporting this exchange are classified as Logical O&M and are an integral part of the Node B Application Part (NBAP) protocol.

In the UTRAN architecture, the RNC controls the radio resources of the Node B. Logical resources are abstractions that represent the configuration and state of physical radio resources. For example, a logical channel or a cell is a logical resource that the RNC configures and manages. However, the actual transmission and reception occur in the Node B. Therefore, when the Node B performs O&M procedures—such as cell setup, channel activation, or fault management—that impact these logical resources, it must inform the RNC and potentially request instructions. This communication is facilitated by Logical O&M messages within NBAP.

NBAP is the signalling protocol between the RNC and Node B in UTRAN. It is divided into two main categories: Node B Control Port (NBCP) and Common Control Port (CCP). Logical O&M messages are part of NBAP and are used for managing logical resources. These messages include procedures for cell configuration, channel management, resource status reporting, and fault management. The RNC uses these messages to configure and control the logical resources, while the Node B uses them to report status and request actions.

The Logical O&M concept ensures that the RNC retains control over logical resources even though they are physically implemented in the Node B. This separation of logical control and physical implementation allows for centralized management and coordination of radio resources across multiple Node Bs. It also enables the RNC to make informed decisions about resource allocation and mobility management based on the status of logical resources.

Logical O&M has been present since Release 4 and continues to be defined in subsequent releases, as evidenced by its inclusion in the 3GPP vocabulary (TS 21.905) through Release 19. Although the definition text has remained unchanged across releases, the underlying NBAP protocol has evolved to support new features and capabilities. Logical O&M remains a fundamental aspect of UTRAN O&M, ensuring efficient and coordinated management of radio resources.

Purpose & Motivation

Logical O&M exists to address the need for centralized control of radio resources in UTRAN while allowing physical implementation in distributed Node Bs. In early cellular networks, base stations were often controlled by a central entity, but the split between logical control and physical implementation became more pronounced with the introduction of the RNC-Node B architecture in UMTS. The RNC owns the logical resources, such as channels and cells, but the Node B physically realizes them. Without a defined mechanism for O&M signalling, the RNC would lack visibility and control over these resources, leading to inefficient resource management and potential conflicts.

Logical O&M solves this problem by defining a set of procedures and messages within NBAP that allow the RNC and Node B to exchange information about logical resources. This enables the RNC to configure, monitor, and control these resources, while the Node B can report status, request actions, and notify the RNC of events. This separation of concerns ensures that the RNC can manage resources across multiple Node Bs in a coordinated manner, which is essential for mobility, load balancing, and overall network performance.

The concept was introduced in Release 4 as part of the UTRAN specifications. Prior to this, O&M functions were often vendor-specific and lacked standardization, leading to interoperability issues. Logical O&M standardized the signalling for logical resource management, facilitating multi-vendor deployments and enabling the RNC to manage Node Bs from different vendors. Over time, the definition has remained stable, indicating that the fundamental architecture and requirements have not changed, even as the protocol has been extended to support new features.

What changed in its specifications

The latest release-to-release comparison of specifications that define Logical O&M. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-4 Initial

Initial definition introduced: Logical O&M is the signalling associated with the control of logical resources (channels, cells) owned by the RNC but physically implemented in the Node B. It forms an integral part of NBAP.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Definition carried over unchanged from Rel-4.

Defining Specifications

3GPP specifications that define or reference Logical O&M, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read