Description
The Configuration Management Server (CMS) is a critical component within the 3GPP management architecture, specifically designed for the secure and efficient handling of configuration data. It operates as a central repository and distribution point for configuration parameters required by various network functions, services, and User Equipment (UE). The CMS architecture is defined to support both pull-based and push-based configuration delivery models, allowing devices to request configuration updates or receive them proactively from the network. It interfaces with other management entities and policy functions to ensure that configuration data aligns with network policies, service profiles, and security requirements.
At its core, the CMS manages Configuration Descriptors, which are structured data objects containing specific sets of parameters for a target entity, such as a UE or a network function. These descriptors are defined using standardized data models and formats to ensure interoperability. The server authenticates and authorizes configuration requests, ensuring that only authorized entities can retrieve or modify configuration data. It also maintains versioning and dependency information for configurations, enabling rollback capabilities and consistent updates across complex systems. The CMS often integrates with subscription databases and policy control functions to tailor configurations based on user subscriptions, device capabilities, and network conditions.
The technical operation involves several key protocols and interfaces. The CMS typically exposes a northbound interface for administration and integration with Operations Support Systems (OSS). Its southbound interface, often based on standardized protocols like OMA DM (Open Mobile Alliance Device Management) adaptations or other 3GPP-specified mechanisms, communicates with managed devices or network elements. Security is paramount; all exchanges are protected using mechanisms defined in 3GPP security specifications, including mutual authentication, integrity protection, and confidentiality. The CMS plays a vital role in lifecycle management, from initial device provisioning (bootstrap configuration) to ongoing updates for feature enablement, parameter optimization, and security patch deployment, thereby reducing operational overhead and minimizing service disruption.
Purpose & Motivation
The CMS was introduced to address the growing complexity of managing configuration data in increasingly heterogeneous and dynamic 3GPP networks. Prior to its standardization, configuration management was often handled through proprietary, vendor-specific solutions or integrated within other network functions, leading to interoperability challenges, security vulnerabilities, and high operational costs. The lack of a unified approach made it difficult to consistently deploy new services, enforce security policies, or update device parameters across multi-vendor environments.
Its creation was motivated by the need for a scalable, secure, and standardized framework for configuration management, particularly with the rise of diverse device types (smartphones, IoT devices, routers) and sophisticated network services. The CMS provides a dedicated, specialized function that separates configuration management from other network processes, enabling more efficient updates, better audit trails, and enhanced security controls. It solves problems related to mass configuration deployment, remote device management, and ensuring compliance with network policies, which are essential for maintaining service quality, security, and operational efficiency in modern telecommunications networks.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (154 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the Configuration Management Server (CMS) function was expanded to support multi-system Mission Critical (MC) service operations. Key introductions included procedures for MC server-initiated group de-affiliation, the definition and configuration of groups for interconnection with a partner MC system, and enhanced resource management between MC service servers. The release also formalized the role of an MC gateway server for interconnection and introduced service configuration for user migration between systems.
- Introduction of MC server initiated group de-affiliation procedure TS 23.280CR0026
- MC server initiated group de-affiliation from group(s) in partner system TS 23.280CR0053
- Resource Management in CFA TS 23.280CR0059
- Group configuration for interconnection TS 23.280CR0074
- Priority between MC service servers TS 23.280CR0071
- Request for resources from MC service server TS 23.280CR0091
+ 26 more changes
In Release 16, the Configuration Management Server (CMS) saw enhancements for Mission Critical (MC) services, including new configuration capabilities for regrouping operations, functional alias management with communication priority support, and restrictions for incoming private communications. It also gained the ability to configure resource priority for MCData emergency calls and to limit the number of authorized clients per user. Furthermore, updates were made to UE configuration parameters, such as adding the Location Management Server URI and aligning configurations with security specifications.
- Regroup group configuration TS 23.280CR0171
- Implicit functional alias management TS 23.280CR0188
- Update user profile configuration to enable restricting of incoming private communications TS 24.484CR0124
- Update service configuration to support communication priority for functional aliases TS 24.484CR0133
- Configuration of resource priority for MCData emergency TS 24.484CR0137
- Update service configuration to support limiting the number of authorized clients per MCPTT/MCData user TS 24.484CR0142
+ 16 more changes
In Release 17, the Configuration Management Server (CMS) enhancements included new Management Object (MO) configurations for functional alias association with groups, user control of communications storage into a message store, and the hostname of MCData notification servers. The release also introduced configuration updates for 5GS/EPS alignment and expanded support for functional alias configurations across MCVideo and MCPTT services, including for call transfer and forwarding in private calls.
- Providing activated functional alias information to the group controlling server TS 23.280CR0207
- Configuration location history reporting TS 23.280CR0251
- Functional alias configuration TS 23.280CR0273
- Request for network resources at session establishment from the MC service server TS 23.280CR0278
- Call transfer for MCPTT private call, Management Object part TS 24.483CR0095
- Management object for APN configuration TS 24.483CR0096
+ 23 more changes
In Release 18, the Configuration Management Server (CMS) was enhanced to support new user profile and service configuration elements for ad-hoc group communications across MCPTT, MCVideo, and MCData services, including configurations for modifying ad-hoc group call participants. Furthermore, the CMS was updated to manage new configuration elements for user migration to a partner MC system and to handle MC gateway UE service configuration for location information management and sharing across MC systems.
- MCGWUE 3GPP access network related location information management TS 23.280CR0300
- Sharing location information across MC systems (configuration) TS 23.280CR0326
- Partner MC service server stores necessary information for communication redirection TS 23.280CR0355
- Migration service de-authorization procedure initiated by MC service server TS 23.280CR0363
- Adhoc group communication related user profile and service configuration for MCPTT TS 24.483CR0160
- Adhoc group communication related user profile and service configuration for MCVideo TS 24.483CR0161
+ 23 more changes
In Release 19, the CMS function expanded to support new administrative configuration exchange procedures between interconnected MC systems and introduced comprehensive configuration management for recording and replay services, including target group configuration and service authorizations. It also added specific configuration data objects for ACM user profiles, ACM group management, and user migration, alongside new Managed Object (MO) configurations for features like multi-talker and emergency remote floor request authorization. These enhancements centralized the management of active and pre-selected user profiles, migration settings, and service-specific authorizations within the Configuration Management Server.
- Adding chapter ‘Sharing administrative configuration between interconnected MC systems’ TS 23.280CR0409
- ACM client user profile configuration data TS 23.280CR0430
- ACM Group configuration management TS 23.280CR0466
- ACM user migration management TS 23.280CR0507
- ACM updating MC service UE initial configuration for migration TS 23.280CR0508
- Adding authorized actions to ACM client user profile configuration data TS 23.280CR0565
+ 34 more changes
In Release 20, the Configuration Management Server (CMS) was enhanced to incorporate additional interactions with the LMS and MC Service Server, as detailed in the revised CSC-15 work item. These updates included refinements to how the CMS stores and makes available profiles, such as the Recording admin and/or replay service user profile, for other network functions. The release also included corrections to location management procedures involving the CMS.
Explore further
Broader topics and technologies where CMS plays a role.
Defining Specifications
3GPP specifications that define or reference CMS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.280 vk10 | Common Architecture for Mission Critical Services | Rel-20 |
| TS 24.483 vj20 | Mission Critical Services Management Object | Rel-19 |
| TS 24.484 vj30 | MCS Configuration Management | Rel-19 |
| TS 33.127 vj50 | Lawful Interception Architecture and Functions | Rel-19 |
| TS 33.180 vk00 | Security of Mission Critical (MC) Service | Rel-20 |
| TS 33.221 vj00 | Subscriber Certificate Distribution via GBA | Rel-19 |