hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.5.2 Potential requirements
| REQ-FL_MGMT-01: A ML training function supporting FL should enable a MnS consumer to request for training in consideration of energy information based selection criteria of FL clients.
REQ-FL_MGMT-02: The 3GPP management system should have a capability allowing an MLTrainingFunction acting as the FL Server to select F... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.5.4 Possible solutions evaluation
| The solution described in clause 5.1.1.5.3 is feasible as it just enhances existing NRM i.e. FLClientSelectionCriteria <<dataType>> with information of renewable energy availability, renewable energy percentage and carbon emission and uses them as criteria for FL client selection in a federated learning.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.6 Enhanced RL training with performance targets
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.6.1 Description
| During RL training, a policy is learnt to maximize a reward aggregated over time. The reward function is defined by the producer from a set of targets set by the consumer. The targets include thresholds such as “Call drop rate(CDR) < 1%”, “Call setup success rate (CSSR) > 90%”, but also optimization instructions such a... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.1.1.6.2 Potential requirements
| REQ-ENH_RL_TRAINING-01: The ML training MnS producer should have a capability to allow an authorized MnS consumer to specify the RL performance targets in an ML model training request.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.2 ML model testing
| Editor’s note: Similar clause structure as in subclause 5.1 will be adopted.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.3 AI/ML inference emulation
| Editor’s note: Similar clause structure as in subclause 5.1 will be adopted.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.4 ML model deployment
| Editor’s note: Similar clause structure as in subclause 5.1 will be adopted.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.4.1 ML model transfer delivery to UE
| Editor’s note: The content in this clause remains for further discussion and depends on further correspondence and confirmation from the relevant RAN WGs.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.4.1.1 Description
| RAN1 and RAN2 started in Rel-18 a joint study on AI/ML for NR air interface (see FS_NR_AIML_air [5]) whose outcomes were reported in TR 38.843 [3], approved in RAN#102 (Dec. 2023). One of the features in scope of this study was ML model transfer/delivery to UE. The clause 7.2.1.4 of TR 38.843 [3] documented several pot... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.4.1.2 Potential requirements
| None.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.4.1.3 Possible solutions
| SA5 should look at conclusion documented in RAN1#120 meeting Chair notes [8] section 9.1.4.2, and should not discuss solution 4b for now, given that RAN has not provided any guidance to SA5 on the need to standardize a solution for this feature.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.4.1.4 Possible solutions evaluation
| With no further action required from RAN, the analysis of the two options defined for Solution 4b would remain as follows:
The option “OAM can transfer/deliver AI/ML models to UE via OAM→UE, e.g., via IP tunnel” in Solution 4b is not feasible, given that the 3GPP management system does not have a direct interface with... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 5.5 AI/ML inference
| Editor’s note: Similar clause structure as in subclause 5.1 will be adopted.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6 AI/ML sustainability
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.0 Sustainable aspects of ML model training and inference
| |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.0.1 Description
| ML model training and AI/ML inference can require substantial computing power and therefore significant energy.
For sustainability goals in AI/ML management, it is valuable for the 3GPP management system to reflect the type of energy supplied to the managed entities that are used for ML model training and AI/ML infer... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.0.2 Potential requirements
| REQ-ML_SUST-01. The 3GPP management system should enable the operator to configure and update the energy related information for the managed entities representing an ML model training function.
REQ-ML_SUST-02. The 3GPP management system should expose the energy information of the managed entities representing an ML mo... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.0.3 Possible solutions
| It is proposed one solution consisting of two parts: one impacting TS 28.310 [9] (see clause 6.0.3.1), and other impacting TS 28.105 [4] (see clause 6.0.3.2).
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.0.3.1 Update Energy Information NRM fragment
| It is proposed to update the Energy Information NRM fragment represented in 8.2.1 of TS 28.310 [9], by adding in ManagedEntity the following:
- The MLTrainingFunction IOC (see clause 7.3a.1.2.1 in TS 28.105 [4])
- The list of IOCs represented by AIMLSupportedFunction (see clause 7.3a.4.1.1 in TS 28.105 [4])
These ad... |
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.0.3.2 Update MLTrainingFunction
| It is proposed to add a new attribute to MLTrainingFunction IOC: “energyInfoGroupRef”. This attribute allows specifying the DN of the energyInfoGroup MOI representing the operator-configured energy information.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.0.4 Possible solutions evaluation
| The solution described in clause 6.0.3 is feasible.
The part of the solution described in clause 6.0.3.1 allows satisfying REQ-ML_SUST-01 and REQ-ML_SUST-03.
The part of the solution described in clause 6.0.3.2 allows satisfying REQ-ML-SUST-02.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.1 Sustainability for ML training
| Editor’s note: Similar clause structure as in subclause 5.1 will be adopted.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 6.2 Sustainability for AI/ML inference
| Editor’s note: Similar clause structure as in subclause 5.1 will be adopted.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 7 Registration and discovery for AI/ML
| Editor’s note: Similar clause structure as in subclause 5.1 will be adopted.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 8 Relation with other management capabilities
|
Editor’s note: Similar clause structure as in subclause 5.1 will be adopted.
|
b4e3b34fa206f18d0c88d81247788555 | 28.882 | 9 Conclusion and recommendations
|
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA5#162
Initial skeleton
0.0.0
2025-10
SA5#163
S5-254664
S5-254666
S5-254667
S5-254744
pCR
pCR
pCR
pCR
pCR TR 28.882 initial ToC
Pseudo-CR on TR 28.882 a... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 1 Scope
| The present document describes use cases, potential requirements, and potential solutions aimed at enhancing the Network Digital Twin (NDT) defined in TS 28.561, with aspects on interaction and collaboration between NDT and network functions/automation functions, multiple NDT collaborations, data collection requirement... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 3 Definitions of terms, symbols and abbreviations
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 4 Concepts and background
| Editor’s note: This clause provides a description of concepts and background.
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5 Use cases
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.1 Use Case #1: NDT support intent pre-evaluation
| 5.1.1 Description
TS 28.312 [1] introduces the intent pre-evaluation which includes Intent Feasibility check and Intent Exploration. Intent feasibility check enables the MnS consumer to check if the proposed intent can be supported by the MnS producer. Intent exploration enables the MnS consumer and the MnS producer ... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.1.2 Potential requirements
| No new requirements
5.1.3 Potential solutions
This solution proposes following updates in TS 28.561[3]:
1. In clause 4.3, add Intent Handling function as one additional example of network automation functions.
2. In clause 5.2.2.1, add the text below:
“NDT can support for Intent Handling Function enabling intent ... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.2 Use Case #2: Improvement of data generation
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.2.1 Description
| TS 28.561 clause 5.4.2.2 [3] introduces the data generation capability provided by NDT to enable ML training. For different ML models, the preferences of its training data are different, which can vary in the dimension of data source object, data type, data quantity. The data source object is used to specify the simula... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.2.2 Potential requirements
| REQ-NDTDG-01: The 3GPP management system should support a capability to allow an authorized MnS consumer to express data generation preferences on data source object, data type, and data quantity.
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.2.3 Potential solutions
| This solution aims to enhance NDT NRMs as shown below:
1. Enhancement for NDTJob IOC
- Add new attribute “nDTDataGenObject” which represents the data source object from which the synthetic data is collected. This attribute allows the MnS consumer to express data generation preferences on data source objects.
- Add ... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.2.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.3 Use case #3: Collaborate with ML training Producer to generate data
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.3.1 Description
| In 3GPP TS 28.561 [3], the existing use case and requirements for using NDT to generate ML training data is described in clause 5.4.2.2. However, using NDT alone to generate data may be insufficient to support the following scenarios:
- Due to the coverage limitations of the physical network simulated by NDT, some ex... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.3.2 Potential requirements
| REQ-NDTDG-AI-1: The 3GPP management system should support a capability that enables an authorized MnS consumer to obtain the enabler information of the NDT data generation.
5.3.3 Potential solutions
5.3.4 Evaluation of potential solutions
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.4 Use Case #4: Enhancement for multiple NDT collaborations
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.4.1 Description
| In 3GPP TS 28.561 [3], the existing use case and requirements for collaboration between NDTs are described in clause 5.5.2.1 and the requirement in clause 5.5.3. The 3GPP management system should support a capability enabling an authorized MnS consumer to configure the relationship between NDTs during simulation/emulat... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.4.2 Potential requirements
| REQ-NDT-Colla-1: The 3GPP management system should support a capability that enables an authorized MnS consumer to request a report on the relationships between NDTs regarding the collaboration of multiple NDTs.
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.4.3 Potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.4.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.5 Use Case #5: Enhancement on NDT reporting method
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.5.1 Description
| In TS 28.561 [3], the reporting method of NDT output is notification based reporting. The NDT MnS consumer receives an NDT report from NDT producer by invoking generic provisioning management service operations and notifications in TS 28.532 [4]. However, different NDT job may have different requirement on reporting me... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.5.2 Potential requirements
| REQ-NDTRM-01: The 3GPP management system should support a capability to allow an authorized MnS consumer to request NDT report to be provided by streaming data reporting service.
REQ-NDTRM-02: The 3GPP management system should support a capability for NDT MnS producer to support delivery of NDT report by streaming dat... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.5.3 Potential solutions
| It is proposed to make the following changes to TS 28.561 [3] clause 6.2.1.3.2:
- update the NDTJob IOC attribute to add a new optional attribute reportingMethod, which can be used to indicate the required reporting method of NDT report, the allowed values of reportingMethod can include streaming and notification. The... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.5.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.6 Use Case #6: Capability Discovery of NDT in NDT Collaboration
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.6.1 Description
| NDT collaboration among different NDTFunctions located in different domain is critical to enable end to end use cases, In Rel-19 the supported domain of NDT is represented by NDTFunctionScope attribute. Then, the NDTFunction that triggers the collaboration can involve NDT(s) that supports modelling of different domain.... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.6.2 Potential requirements
| REQ- NDTAUT-01
The 3GPP management system should support a capability enabling authorized MnS Consumer to discover detailed capability of candidate NDT components for NDT collaboration.
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.6.3 Potential solutions
| Add a new the GenericModellingCapabilites <<dataType>> with the following new attributes to support modelling capability discovery of NDT in NDT collaboration:
• EnviromentModelling, it represents the NDTFunction supports to model the network topology and network infrastructure.
• UETrafficModelling, an ENUM,... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.6.4 Evaluation of potential solutions
| TBD
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.7 Use Case #7 Defining the Lifecycle and Runtime Behaviour of NDT Jobs
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.7.1 Description
| The NDTJob lifecycle is not clear, there are some items open to interpretation and some items missing which are described below.
Issue#1: The MnS Consumer should have a method to know which configuration of NDTJob has produced a given report. In the current specification NDTReport refer to the NDT job (i.e NDTJobRef).... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.7.2 Potential requirements
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.7.3 Potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.7.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.8 Use Case #8: Using external data for NDT modelling
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.8.1 Description
| As defined in TS 28.561[3], Network Digital Twin (NDT) is used as a replica of a mobile network, in order to learn how an actual mobile network would behave in certain scenarios, without causing any changes to the actual mobile network. To provide meaningful results, an NDT needs to model the behaviour of the mobile ne... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.8.2 Potential requirements
| REQ-NDTDG-01: The 3GPP management system should support a capability to allow an authorized MnS consumer to specify external data information used for NDT modelling.
|
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.8.3 Potential solutions
| TS 28.622 defines the ExternalDataType IOC which specifies a type of external management data and the associated meta data. This solution aims to enhance NDTJob IOC and NDTFunction IOC by reusing ExternalDataType IOC to carry the NDT MnS consumer’s external data preference for an NDT job and show the supported external... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.8.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.9 Use Case #9: NDT for Non-Terrestrial Network (NTN) Performance and Optimization Evaluation
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.9.1 Description
| According to 3GPP 38.300 [5] a Non-Terrestrial Network (NTN) is defined as an NG-RAN consisting of gNBs, which provide non-terrestrial NR access to UEs by means of an NTN payload embarked on an airborne or space-borne NTN vehicle and an NTN Gateway. NTN Gateway is an earth station located at the surface of the earth, p... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.9.2 Potential requirements
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.9.3 Potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.9.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.10 Use Case #10: Clarification of NDTJob Modification Behaviour
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.10.1 Description
| The MnS Consumer requires clarity on the conditions and procedures for modifying an existing NDTJob instance. At the moment, the specification leaves this open to interpretation, even though there are clear limitations associated with different implementation techniques for NDTJobs. For instance, if an NDTJob is implem... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.10.2 Potential requirements
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.10.3 Potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.10.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.11 Use Case #11: Create and Execute NDT Job
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.11.1 Description
| The MnS Consumer requires clarity on whether the creation and execution of an NDTJob are distinct phases or a single combined procedure.
By having creation of an NDTJob separate to the execution of the NDTJob, it means certain MnS Consumers can define the NDTJob, and other MnS Consumers could execute the NDT jobs. Thi... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.11.2 Potential requirements
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.11.3 Potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.11.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.12 Use Case #12: Clarification of Suspension and Resumption Capabilities for NDTJobs
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.12.1 Description
| The MnS Consumer requires clarity on whether an NDTJob can be suspended and subsequently resumed, when such capabilities are supported by the NDT MnS Producer.
The MnS Consumer should have the capability to suspend NDTJobs such as an optimization activity in order to free up resources to prioritize different NDTJobs s... |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.12.2 Potential requirements
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.12.3 Potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 5.12.4 Evaluation of potential solutions
| |
282fa1049c2866220729ce3d5d76aa25 | 28.883 | 6 Conclusions and Recommendations
| 6.X Use case #<X>: <use case title>
Editor's note: This clause provides conclusions and recommendations for the corresponding use case.
Annex <X> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA5#162
Initial skeleton
V0.0.0
2025... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 1 Scope
| The present document describes use cases, potential requirements, and potential solutions aimed at enhancing the Service Based Management Architecture (SBMA) in the context of 5G Advanced (5GA). It also presents conclusions and recommendations regarding the next steps in the standardization process.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 3 Definitions of terms, symbols and abbreviations
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 4 Concepts and background
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 4.1 Introduction
| SBMA adopts a modular, service-oriented approach that enables flexible, scalable, and interoperable management solutions.
The architecture for the present study builds upon the SBMA framework in TS 28.533 [2]. All potential enhancements and solutions are expected to comply with the principles outlined in TS 28.533 [2]... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 4.2 Management data streaming based on Message Bus technologies
| 3GPP TS 28.532 [3] defines Stage 2 and Stage 3 of the streaming data reporting service. Currently, the 3GPP management system supports WebSocket-based data streaming for PM, tracing, and analytics, establishing a point-to-point transport connection between the streaming data reporting MnS consumer and MnS producer. The... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.