RAN Training Data Collection Through Periodic DCMF Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The application of conventional reinforcement learning model training in Radio Access Networks (RAN) is hindered by latency issues and the infrequent deployment of model updates due to security concerns, leading to inefficiencies in training data collection and model updates.

Innovation Solution

A data collection management function (DCMF) is introduced to control the discontinuous collection of training data, allowing for efficient and scalable training data collection from multiple rollout workers in RAN environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If continuous collection of training data is performed from multiple rollout workers, then the quantity of training data increases, but the latency in model updates and deployment increases

Engineering Contradiction:
Improvequantity of training dataVSAvoidlatency in model updates
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent implements discontinuous collection of training data by introducing periodic data collection cycles controlled by a data collection management function. Instead of continuous data collection from multiple rollout workers, the system collects data in periodic intervals, allowing processing and deployment of model updates between collection periods. This periodic action reduces the latency in model updates while still accumulating sufficient training data over time.

Inventive Principle:
Principle #19Periodic action

2Productivity

If model updates are deployed frequently to improve training efficiency, then the productivity increases, but security concerns and system stability deteriorate

Engineering Contradiction:
Improvetraining efficiencyVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements dynamic control of data collection and model update deployment through a data collection management function. The system dynamically adjusts the frequency and timing of data collection based on training progress, data quality metrics, and system conditions. This dynamic approach allows the system to optimize training efficiency while maintaining stability by adapting update frequencies rather than using fixed frequent updates.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If data collection is performed from multiple rollout workers, then the diversity of training data sets improves, but the device complexity increases

Engineering Contradiction:
Improvediversity of training data setsVSAvoidcomplexity of data collection system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal data collection management function that handles data collection from multiple rollout workers through a single, standardized interface and process. The data collection management function serves multiple purposes: coordinating data collection across workers, managing data aggregation, controlling collection timing, and orchestrating model updates. This multi-functional approach enables diverse data collection from multiple sources without proportionally increasing system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250294375A1Controlling the collection of data for use in training a model
Publication Date: 2025.09.18 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20250294375A1 patent drawing
  • US20250294375A1 patent drawing
  • US20250294375A1 patent drawing

AI summary

A method performed by a first network node for configuring a second network node. The method includes transmitting to the second network node a first message for configuring the second network node with respect to the collection of at least first training data for use in producing (e.g., generating or updating) a first model, wherein the first message comprises first data collection configuration information that comprises (i. e., includes at least) one or more of: a first process identifier (e.g., link adaptation or power control) identifying a first process that uses the first model, a first model identifier identifying the first model, or a first model version identifier identifying a version of the first model.