Operation and Maintenance Centre Identity

Description

The Operation and Maintenance Centre Identity (OMC-ID) is a parameter defined within the 3GPP Evolved Packet Core (EPC) architecture, starting from Release 8. It serves as a unique identifier for an Operations and Maintenance Centre, which is a network management system. The OMC-ID is not an address for user data traffic but is used within management and control plane signalling to associate management actions, such as trace activation, with the specific OMC that requested them.

Technically, the OMC-ID is structured and used within management interfaces and procedures. A key use case is in the Trace Control and Configuration Management (TCCM) functionality. When an OMC or a Network Manager (NM) needs to activate a trace on a User Equipment (UE) or a network entity (like an MME or eNodeB), it includes its OMC-ID in the trace activation request. This identifier is then propagated through the network and included in trace records. This allows all collected trace data to be linked back to the originating management system, which is crucial for auditing, troubleshooting, and managing multiple OMCs in a large network.

The OMC-ID is part of the broader management and security framework. It helps in differentiating between management requests coming from different operational domains or different service providers in roaming scenarios. The identifier is typically defined by the network operator and must be unique within the management domain. Its inclusion in standards ensures interoperability between management systems and network elements from different vendors, providing a clear audit trail for network configuration and diagnostic activities.

Purpose & Motivation

The OMC-ID was introduced with the EPS in 3GPP Release 8 to address the need for unambiguous attribution of management actions in increasingly complex and layered network management architectures. As networks evolved from 2G/3G to LTE/EPC, the management systems became more hierarchical (with Element Managers, Network Managers, and OSS), and multiple OMCs could be deployed for scalability or different administrative domains.

Without a unique identifier, it would be impossible to determine which management system initiated a specific trace or configuration change, leading to operational confusion and security audit gaps. The OMC-ID solves this by tagging every management-initiated action with the identity of its source. This is particularly critical for trace functionality, which is used for customer care, fault investigation, and optimisation; knowing the origin of a trace request is essential for context and accountability.

Furthermore, its standardisation supports multi-vendor interoperability in the management plane. By defining a common parameter, it ensures that an OMC from vendor A can successfully initiate a trace on a network element from vendor B, and the trace records will correctly carry the identifier back to the requesting system. This fosters a more open and manageable multi-vendor network environment.

Key Features

• Unique identifier for an Operations and Maintenance Centre within the EPS management domain
• Used to tag the originator of management actions, particularly trace activation requests
• Propagated within trace records to provide an audit trail
• Supports management in multi-vendor and hierarchical OSS environments
• Essential for security auditing and accountability of network configuration changes
• Defined by the network operator and must be unique within its scope of use

Evolution Across Releases

Defining Specifications