Description
Life Cycle Management (LCM) in 3GPP refers to the comprehensive set of management procedures and capabilities required to manage the complete life cycle of managed entities within a 3GPP network, particularly in the context of network virtualization and softwarization introduced with 5G. The primary managed entities are Network Functions (NFs), which can be virtualized (VNFs) or cloud-native (CNFs), Network Services (NS) composed of multiple interconnected NFs, and Network Slices which are logical end-to-end networks serving specific business cases. The LCM process is a core function of the Management and Orchestration (MANO) framework, as aligned with ETSI NFV, and is performed by entities like the Network Function Virtualization Orchestrator (NFVO) and the 3GPP Network Slice Management Function (NSMF).
The LCM operation follows a phased model. For a Network Service or Network Slice, it begins with the **instantiation and configuration phase**. This involves validating the deployment template (e.g., a Network Service Descriptor), allocating necessary resources (compute, storage, network), deploying the constituent VNF/CNF packages on the chosen infrastructure, and configuring the initial parameters and connectivity between functions. Following instantiation, the **runtime operation phase** includes continuous performance monitoring, fault supervision, and dynamic actions like **scaling** (in/out, up/down) to adapt to load changes, and **healing** to recover from failures by re-instantiating components. The **update and upgrade phase** manages changes, such as applying software patches or modifying service descriptors, often requiring complex rollback procedures. Finally, the **termination phase** involves gracefully shutting down the service, releasing all allocated resources, and updating the inventory.
Key architectural components involved in LCM include the **Service Management Function (SMF)** for business-level management, the **Network Slice Management Function (NSMF)** and **Network Slice Subnet Management Function (NSSMF)** for slice-specific LCM, the **NFVO** for resource orchestration, and the **Virtualized Infrastructure Manager (VIM)** for infrastructure-level control. LCM works through standardized interfaces (e.g., Os-Ma-nfvo, Or-Vnfm) and data models (e.g., based on YANG) that carry LCM operations. Its role is fundamental to achieving the agility, automation, and efficiency promised by 5G, allowing operators to rapidly deploy and elastically operate services with minimal manual intervention.
Purpose & Motivation
LCM was introduced to address the operational complexity and rigidity of traditional telecom networks built on dedicated, proprietary hardware appliances. Managing the life cycle of physical network elements was a manual, slow, and error-prone process. The shift towards Network Functions Virtualization (NFV), Software-Defined Networking (SDN), and cloud-native principles in 3GPP, starting notably in Release 14 for 5G, created a need for automated, standardized management procedures. Without LCM, the benefits of virtualization—such as rapid service deployment, elastic scaling, and efficient resource usage—could not be realized.
The primary problems LCM solves are the slow time-to-market for new services, the inefficient use of hardware resources due to static provisioning, and the high operational expenditure (OPEX) associated with manual configuration and troubleshooting. It provides a framework for treating network functions and services as software that can be managed programmatically. This was motivated by the desire to compete with web-scale cloud providers in agility and to support the diverse and dynamic requirements of 5G use cases, such as massive IoT, enhanced mobile broadband, and ultra-reliable low-latency communication, each potentially requiring its own uniquely managed network slice.
Furthermore, LCM enables closed-loop automation, where monitoring data automatically triggers LCM operations (e.g., scale-out under load), moving towards self-optimizing networks. It addresses the limitations of traditional OSS/BSS systems by defining a standardized, intent-based management interface that separates the 'what' (service intent) from the 'how' (orchestration details), which is crucial for multi-vendor, cloud-native environments.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (21 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-14, normative work from Rel-15.
In Release 15, enhancements for Life Cycle Management (LCM) were introduced through the addition of management service discovery and a clarified architecture by replacing "MF" with the more precise term "management function." This is reflected within the Service Enabler Architecture Layer (SEAL) framework, where specific management services—such as network slice lifecycle management, spatial anchors server management, and digital asset profile management—gained defined APIs and procedures. Furthermore, the release addressed how LCM capabilities, like VN group management, could be utilized by a trusted Group Management Service (GMS) or Application Function (AF) within the network's trusted domain.
In Release 16, Life Cycle Management (LCM) was enhanced by introducing management service deployment based on the ZSM (Zero-touch Service Management) framework and adding descriptions for management capability support in multi-tenant environments. It also specified new coordination with the NWDAF (Network Data Analytics Function) for management purposes. Furthermore, the release expanded the use of NEF-exposed VN group management service APIs and addressed how a Group Management Service (GMS) deployed as a trusted Application Function can utilize 5G VN group management services.
- Add 3GPP Management Service deployment based on ZSM Framework TS 28.533CR0028
- Add description for management capability support in multiple tenant environment TS 28.533CR0044
- Update Clause 5.3 Management service deployment based on ZSM framework TS 28.533CR0057
- Add management coordination with NWDAF TS 28.533CR0031
- Update of Management service description and diagram TS 28.533CR0039
- Update of Management service description and diagram TS 28.533CR0064
In Release 17, the Life Cycle Management (LCM) function introduced clarifications for the management of vertical application services. Specifically, it removed unnecessary procedural details for the discovery of management services and provided corrections to the description of the Management Data Analytics capability. These refinements aimed to streamline the architecture framework and ensure accurate technical documentation.
In Release 18, Life Cycle Management (LCM) enhancements focused on improving interoperability and management service exposure. Specifically, the release introduced support for using the NEF-exposed VN group management service APIs and addressed how a Group Management Server (GMS) can utilize 5G VN group management services when deployed as a trusted Application Function. Furthermore, it defined new management capabilities for Spatial Anchors and Spatial Map servers, as well as for Digital Asset profile and media management, within the SEAL architecture.
- Add example of RAN domain management capabilities mapped with ZSM TS 28.533CR0120
- Using Management Services to support multiple players interoperability TS 28.533CR0121
- Rel-18 CR TS 28.533 Update Annex F Usage of CRUD operations and NRM fragments to support management capabilities in SBMA TS 28.533CR0124
- Rel-18 CR TS 28.533 Update Annex F Usage of CRUD operations and NRM fragments to support management capabilities in SBMA TS 28.533CR0129
- Rel-18 CR 28.533 Correct A.5 Management Data Analytics Service (MDAS) TS 28.533CR0139
In Release 19, the Life Cycle Management (LCM) function was enhanced by expanding the management capabilities for data management and management services exposure within the architecture framework. The release specifically introduced updates to the illustrative architecture reference model for management and orchestration to support SBMA (Service Based Management Architecture) and added summary descriptions for the supporting functions. Furthermore, the release addressed gaps for enabling a Group Management Service (GMS) to use 5G Virtual Network (VN) group management services when deployed as a trusted Application Function.
- Rel-19 CR TS 28.533 Update Annex F to include the management capabilities related to data management TS 28.533CR0164
- Rel-19 CR TS 28.533 Management services exposure TS 28.533CR0169
- Rel-19 CR TS 28.533 addition of Illustrative architecture reference model for management and orchestration in support of SBMA TS 28.533CR0165
- Rel-19 CR TS 28.533: addition of summary descriptions for functions in support of architecture reference model for management and orchestration TS 28.533CR0166
- Rel-19 CR TS 28.533 Update Annex F to add missing R19 management capabilities TS 28.533CR0172
- Rel-19 TS 28.533 CR Update Annex management features TS 28.533CR0173
Explore further
Broader topics and technologies where LCM plays a role.
Defining Specifications
3GPP specifications that define or reference LCM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 |
| TS 28.500 vj00 | Management of Virtualized Network Functions | Rel-19 |
| TS 28.533 vj30 | Management and orchestration; Architecture framework | Rel-19 |
| TR 28.834 vi01 | Technical Report | Rel-18 |
| TS 28.869 vk00 | Study on cloud aspects of management and orchestration | Rel-20 |
| TS 28.890 vg00 | ONAP-3GPP 5G Management Compatibility Study | Rel-16 |
| TR 33.876 vi01 | Technical Report on Certificate Management | Rel-18 |
| TS 38.843 vj00 | Study on AI/ML for NR Air Interface | Rel-19 |