Description
The Machine Learning (ML) model lifecycle is the comprehensive framework that governs the management of an ML model throughout its existence in a 3GPP network. It typically consists of six key phases: model training, model testing, model deployment, model inference, model monitoring, and model maintenance. This lifecycle ensures that ML models are developed, validated, integrated, operated, and maintained in a controlled and standardized manner. In the context of 3GPP, the lifecycle is being standardized in Release 19 to facilitate multi-vendor interoperability and to enable the widespread adoption of AI/ML in network operations.
Model training involves using historical data to teach the model to perform a specific task, such as predicting network traffic or classifying anomalies. This phase requires large datasets and significant computational resources. Model testing validates the trained model against a separate dataset to ensure it meets performance requirements and does not exhibit undesirable behavior. Model deployment involves integrating the model into the network, which may include packaging, distribution, and configuration. Model inference is the operational phase where the model is used to make decisions based on live data. Model monitoring continuously tracks the model's performance and detects issues like drift or degradation. Model maintenance includes actions such as retraining, updating, or deactivating the model based on monitoring insights.
In 3GPP, the ML model lifecycle is managed by various entities, including the Management Data Analytics Function (MDAF), the Network Data Analytics Function (NWDAF), and the network functions that consume the ML model. The lifecycle is supported by management services and interfaces that allow for the coordination of activities across different domains. For example, the MDAF may be responsible for training and deploying models, while the NWDAF handles inference and monitoring for core network analytics. The lifecycle also involves the ML model itself, which is a software artifact with metadata describing its purpose, version, and performance characteristics.
Key components of the ML model lifecycle include the ML model repository, which stores models and their metadata; the ML model management function, which orchestrates lifecycle operations; and the ML model consumer, which uses the model for inference. The lifecycle is iterative: monitoring may trigger maintenance, which could lead to retraining and redeployment. This closed-loop approach ensures that models remain aligned with network conditions and continue to deliver value. Standardization efforts aim to define the stages, roles, and interfaces for each phase, enabling automation and interoperability.
The role of the ML model lifecycle in the network is to provide a structured approach to managing AI/ML assets, reducing the risk of model failures and ensuring that models contribute positively to network performance. It is a foundational element for autonomous networks, where ML models are expected to be managed with minimal human intervention. By defining the lifecycle, 3GPP enables operators to deploy ML at scale, with confidence that models can be effectively governed throughout their useful life.
Purpose & Motivation
The ML model lifecycle exists to provide a standardized, end-to-end framework for managing machine learning models in 3GPP networks. As AI/ML becomes integral to network operations, the need for a structured approach to model management is critical. Without a defined lifecycle, models could be deployed without proper testing, leading to poor performance or even network outages. The lifecycle ensures that models are trained, tested, deployed, monitored, and maintained in a controlled manner, reducing risks and maximizing benefits.
The motivation for defining the ML model lifecycle in Release 19 is to enable multi-vendor interoperability and to support the automation of network operations. Previous releases introduced isolated ML concepts, but a holistic lifecycle was missing. By standardizing the lifecycle, 3GPP provides a common language and set of procedures that vendors and operators can follow, facilitating the integration of ML models from different sources. This is essential for the vision of autonomous networks, where ML models are expected to be managed dynamically and efficiently.
Historically, network functions were static and did not require lifecycle management. With the advent of AI/ML, models can become outdated or perform poorly as network conditions change. The lifecycle addresses this by including monitoring and maintenance phases, which allow for timely updates or deactivation. It also addresses regulatory and security concerns by ensuring that models are tested and monitored. The ML model lifecycle is thus a key enabler for the trustworthy and scalable adoption of AI/ML in telecommunications.
What changed in its specifications
The latest release-to-release comparison of specifications that define ML model lifecycle. Each summary describes the whole specification, not only this term.
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 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced in 3GPP TR 21.905: 'The end-to-end process typically consisting of model training, model testing, model deployment, model inference, model monitoring and model maintenance.' This release formalized the lifecycle concept, providing a standardized framework for managing ML models in 3GPP networks.
Defining Specifications
3GPP specifications that define or reference ML model lifecycle, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |