hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 28.104: "Management Data Analytics (MDA)".
[3] 3GPP TS 28.541: "5G Network Resource Model (NRM); Stage 2 and stage 3".
[4] 3GPP TS 28.567: "Management aspects of closed control loops".
[5] 3GPP TS 28.552: "5G performance measurements".
[6] 3GPP TS 28.662: "Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM)".
[7] 3GPP TS 38.104: "Base Station (BS) radio transmission and reception".
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 3 Definitions of terms, symbols and abbreviations
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 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.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 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].
CPA Conditional PSCell Addition
CPC Conditional PSCell Change
SN Secondary Node
NSA Non-standalone
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 4 Concept and background
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5 Use cases
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.1 Improvements to interoperability
| 5.1.X Use case X: Use case title
5.1.X.1 Description
5.1.X.2 Potential requirements
5.1.X.3 Potential solutions
5.1.X.4 Evaluation of solutions
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2 Improvements to MDA framework
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.1 Use case 1: Integration of analytics with a network operator’s management system
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.1.1 Description
| A Network Operator (NOP) wishes to integrate Management Data Analytics Service with the NOP’s automated network management system.
To be able to successfully perform this integration, the NOP needs to know which management facilities are provided by MDAS. The NOP also needs to know if MDAS depends on other 3GPP management functions and/or management services, and if these dependencies are mandatory or optional.
The operator uses TS 28.104 [2] to learn the required information about MDAS. Clause 5 of TS 28.104 [2] describes the management facilities which are provided by MDAS. Clause 5 of TS 28.104 [2] describes how MDAS may be combined with other 3GPP management functions and/or management services to satisfy NOP requirements.
Currently, clause 5 of TS 28.104 [2] is lacking description on how MDAS relates to some 3GPP management functions and/or management services (e.g. CCL, NDT). The current description is very abstract and may benefit from adding examples. The current description may also conflict with the content of other technical specifications.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.1.2 Potential requirements
| None.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.1.3 Potential solutions
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.1.3.1 Update description of MDA scope for closed loop control management
| TS 28.104 [2] clause 6.1 states that only analytics are in scope. Other aspects of a management loop (Observation, Decision, Execution) are therefore not in scope. This is in conflict with TS 28.567 [4] figures 5.1.2.2-1 and 5.1.2.2-2, which show that the MDA MnS producer may perform data collection, analytics, and decision making.
It is proposed to update TS 28.567 [4] figure 5.1.2.2-1, figure 5.1.2.2-2 and associated text to clarify that only analytics are in scope of the MDA MnS producer.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.1.4 Evaluation of solutions
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.2 Use case 2: Indicating supported domain information in MDAFunction
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.2.1 Description
| The IOC MDAFunction represents the MDA function which supports one or more MDA capabilities as described in TS 28.104 [2]. It also describes that an MDA function can act as 3GPP domain-specific (e.g. RAN or CN) or as 3GPP cross-domain MDA MnS producer. From MnS consumer perspective, it is reasonable to know not only the support MDA capabilities but also to identify in which domains the MDA Function is supported for corresponding analysis. For example, an MnS consumer may wish to perform analytic for CN, while the MDA producer is only capable to provide report for RAN. There is no way to identify the capability of the MDA producer in advance, and no way to report why the producer cannot satisfy the request.
Currently, in clause 9.3.1.2 in 28.104 [2] the definition of MDAFunction IOC, only contains supportedMDACapabilities attribute without domain information. This makes a MnS consumer difficult to know the actual analysis scope of a MDAFunction.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.2.2 Potential requirements
| REQ-MDA_Fun-01: The MDA MnS producer should have the capability to allow authorized MDA MnS consumer to request the supported analysis of domain information.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.3.3 Potential solutions
| It is proposed to make the following changes to TS 28.104 [2] clause 9.3.1.2:
- update the MDAFunction IOC attribute to add a new attribute supportedMDADomains, which can be used to indicate the domain(s) supported by the MDAFunction.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.2.2.4 Evaluation of solutions
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3 Investigate new and enhanced analytics related capabilities
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.1 Use case 1: Enhance the Mobility performance analysis use case
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.1.1 Description
| This use case is to enhance the existing MDA capability for mobility performance analysis. The enhancements to the existing mobility performance analysis are targeted towards to solve the mobility problems in NSA deployment architecture and to recommend optimization or repair actions.
The existing use case for mobility performance analysis is described in TS 28.104 [2]. This analysis output includes information such as mobility issue root cause, mobility issue location. The descriptions and requirements in the existing use cases also mention performance analysis under NSA deployment scenarios. However, the current solution does not provide additional information (e.g. mobility issue type such as NSA mobility issue and SA mobility issue, or the root cause of NSA mobility issue, or the recommended actions) which may enable the consumer to anticipate the impacts to the network more effectively.
The mobility performance related problems in NSA deployment scenarios may result from too-early/too-late PSCell change or too-early/too-late conditional PSCell addition or change due to inappropriate handover parameters as defined in TS 38.300 [x]. Performance measurements related to NSA need to be defined and used as enabling data for MDA analysis. MDAS can be used to analyse network performance during handover period in different mobility scenarios. The MDAS producer may also be capable to provide the recommendations of optimal handover parameters to MDAS consumer.
Correspondingly, the root cause of mobility issue in NSA deployment scenarios may be of interest to the consumer and can be provided in the analytics report. The root cause can be high interference in both uplink and downlink, wireless resource issues (such as high utilization of uplink and downlink PRBs), transport layer reasons (including insufficient transport resources leading to SN addition failure, such as S1 interface transport, X2 interface transport), and UE capability issues.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.1.2 Potential requirements
| REQ-MRO_MDA-01: MDA capability for mobility performance issue analysis should provide the NSA mobility issue including too-early PSCell change, too-late PSCell change, too Late CPC Execution and too Early CPC/CPA Execution.
REQ-MRO_MDA-02: MDA capability for mobility performance issue analysis should include providing recommended actions to solve the mobility performance issue.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.1.3 Potential solutions
| Reuse the performanceThresholdInfo attribute in the MDARequest IOC with the threshold of mobility related performance measurements for this MDA type, including:
- Thresholds of mobility related performance measurements
The enabling data for this MDA type would introduce the additional NSA mobility measurements as following:
- SN addition related performance measurements.
- SN change related performance measurements.
- Conditional SN addition related performance measurements
- Conditional SN change related performance measurements
The analytics output for this MDA type would include the following:
- The mobility performance issue type including NSA mobility issue and SA mobility issue
- The mobility performance issue including too-early handovers, too-late handovers and ping-pong handovers, too-early PSCell change, too-late PSCell change, too late CPC Execution and too early CPC/CPA execution.
- The mobility performance issue root case can be such as high interference, insufficient transport resources, UE capability issues etc.;
- The recommended actions to resolve the mobility issue (e.g. change the mobility parameters (e.g. CIO) or antenna RF parameters such as downtilt and azimuth etc.).
NOTE: The NSA mobility measurements are subject to be defined in TS 28.552 (FFS).
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.1.4 Evaluation of solutions
| The solution proposed in clause 5.3.1.3 satisfies the requirements and this solution is feasible for normative work.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.2 Use case 2: MDA assisted failure resolution
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.2.1 Description
| As networks become more complex, it becomes more difficult to quickly resolve network failures, where network performance becomes degraded or lost completely. By looking only at the alarm list, it can be difficult to identify the most serious network failures. Network automation is essential to speed up the identification and resolution of network failures, thereby increasing the stability of the network. This use case enables an MDAS consumer (e.g. an automated trouble ticketing system) to automatically perform the steps needed to resolve a network failure.
The MDAS consumer requests the MDAS producer to identify alarms which may relate to network failures. The MDAS producer analyses alarm data and network data to correlate alarms with deteriorating performance in the network. The MDAS producer analyses the cause of deteriorating performance. The MDAS producer reports possible network failures and the possible cause to the MDAS consumer.
The MDAS consumer requests the MDAS producer to diagnose the cause of a network failure. The MDAS producer performs analysis to locate the likely cause of the network failure (e.g. network function, virtualized resource, physical resource). The MDAS producer reports the possible cause of the network failure to the MDAS consumer.
The MDAS consumer requests the MDAS producer to recommend how to resolve a network failure. The MDAS producer performs analysis to identify which domain is causing the network failure. The MDAS producer calculates possible methods (e.g. re-configurations) to resolve the network failure. The MDAS producer simulates or emulates the effect of the possible methods (e.g. by using NDT) to evaluate if the network failure is resolved. The MDAS producer reports the possible methods to the MDAS consumer.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.2.2 Potential requirements
| REQ-FAILURE_RESOLUTION_MDA-01: MDA capability for network failure resolution should be able to provide the analytics output including the probable impact of the network failure.
REQ-FAILURE_RESOLUTION_MDA-02: MDA capability for network failure resolution should be able to provide the analytics output including recommended actions to resolve the network failure.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.2.3 Potential solutions
| Update TS 28.104 [2] to add a new MDA type MDAAssistedFaultManagement.FailureAnalysis to allow an MnS consumer to request analytics related to a network failure.
Update TS 28.104 [2] to add a new analytics output for network failure analysis, including (but not limited to) information related to
- related alarm(s) which are likely to be correlated to the network failure
- managed objects (e.g. NFs, cells) that are impacted by the network failure
- metrics or KPIs that are impacted by the network failure
- probable impacted domain and cause of the network failure
- recommended actions to resolve the network failure
- estimated time to resolve the network failure
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.2.4 Evaluation of solutions
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.3 Use case 3: Radio resource optimization based on per SSB usage
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.3.1 Description
| 5G NR adopts massive MIMO technology, where the base station employs directional beams for both UE initial access on common channels and subsequent connection during the RRC_CONNECTED state. Common signals/channels for initial access are transmitted within the Synchronization Signal Block (SSB). SSBs are designed with different patterns, corresponding to the number of SSB beams and their distinct directions.
In Clause 4.3.39 of TS 28.541[3], <<IOC>>CommonBeamformingFunction is defined to represents common beamforming functionality (eg: SSB beams). The CommonBeamformingFunction provides capability to configure the advanced antenna for a sector carrier. The configuration capability is provided by selection of coverageShape, digitalTilt and digitalAzimuth. These attributes represent the wanted coverage area and radiation pattern on a sector carrier related to an antenna transmission point.
For example, the area where a large outdoor stadium holds some competitions is characterized by a high number of users which is challenging to guarantee enough radio resource in this scenario. It is necessary to consider using MDAS to improve radio resource usage. MnS consumer could request MDAS to acquire beam-level management data and recommend coverage shape based on analysis. The beam-level data includes Number of UE related the SSB beam Index (mean), DL PRB Usage per SSB, etc. The recommendation could be used for 3GPP Management System to update the configuration of the target cell's coverage shape on gNodeB.
Figure 5.3.3.1-1 depicts SSB beams covering full cell coverage area. Figure 5.3.3.1-2 depicts SSB beams modifying to meet the UE centralized coverage after updating the coverage shape for target cell of gNodeB using the recommendation by MDAS.
It is anticipated that MDAS can be used to obtain an analysis of the usage of each SSB. This information can then be used to adjust the coverage shape.
Figure 5.3.3.1-1: Illustration of SSB beams covering full cell coverage area
Figure 5.3.3.1-2: Illustration of SSB beams modifying to meet the UE centralized coverage with MDAS recommendation
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.3.2 Potential requirements
| REQ-RRO-FUN-01: MDA should have capability for radio resource optimization analysis.
REQ-RRO-FUN-02: MDA capability for radio resource optimization analysis should include the capability of the beam-level radio resource utilisation assessment to indicate if coverage shape configuration of gNodeB is proper based on beam-level management data analytics.
REQ-RRO-FUN-03: MDA capability for radio resource optimization analysis should include the capability to recommend coverage shape configuration for target cell of gNodeB.
5.3.3.3 Potential solutions
Update TS 28.104 [2] to add a new MDA type RadioResourceAnalytics.SSBUsageAnalysis. MnS consumer could request MDAS to acquire beam-level management data and recommend coverage shape based on analysis.
The enabling data for RadioResourceAnalytics.SSBUsageAnalysis would include as follows:
- Timing Advance distribution for NR Cell per SSB in TS 28.552[5]
- DL data transmission time per SSB in TS 28.552[5]
- Number of UE related the SSB beam Index (mean) in TS 28.552[5]
- DL PRB Usage per SSB in TS 28.552[5]
The analytics output for RadioResourceAnalytics.SSBUsageAnalysis would include the following:
- The beam-level radio resource utilization issues indicating the efficiency of radio resource
- The recommendation on updating the coverage shape configuration for target cell of gNodeB
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.3.4 Evaluation of solutions
| TBD
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.4 Use case 4: Remote Electrical Tilt (RET) and Transmission Power analytics (TP)
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.4.1 Description
| Operators establish their own guidelines for deploying antenna RET, both mechanical and electrical, in cells, primarily based on LTE/NR layers and traffic management strategies. Initial RET and power configurations may not be optimal for all cells, necessitating ongoing fine-tuning. The initial RET may not account for changes in subscriber movement or infrastructure developments. Factors influencing optimal RET and power can evolve over time, including:
Subscriber Movement: Dynamic changes in user behavior, such as daily commutes from office to home or weekend outings to recreational areas, can impact network performance requiring the modification in the RET.
Infrastructure Growth: The addition of new cell sites can introduce interference with neighboring cells. Interference arises when signals from the new site overlap with or disrupt existing signals. This would affect performance and can be mitigated with modification in the RET.
Weather Conditions: Atmospheric phenomena like rain, snow, and fog can affect radio wave propagation, leading to signal attenuation or distortion. Tilt modification may minimize the impact.
It is desirable to use MDA analytics to generate optimal RET and power configuration over time. It is essential to follow initial antenna RET deployment with subsequent fine-tuning using MDA analytics. The producer employs a machine learning-based model that leverages strong correlations between performance, fault and configuration data of the network. This ML model analyzes the impacts of coverage and interference in relation to user traffic behavior, including mobility and weather conditions. It generates recommendations for fine-tuning RET and optimizing transmission power per cell.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.4.2 Potential requirements
| REQ-RET-DATA-1: MDA capability for RET analysis shall include providing analytics for indicating the recommended change in RET and TP for a specific cell.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.4.3 Possible solutions
| It is proposed to add a new MDA capability for RET and TP analysis. The MDAS Consumer submits an MDARequest, specifying the target cell(s) and the periodic interval at which data should be collected. MDAS Consumer receives the MDA Report for the RET_TPAnalytics. MDAS Producer collects the enabling data and generates the RET_TPAnalytics data. The generated data is returned as MDAReport. After receiving the MDAReport containing the recommended value for RET and TP, the consumer initiates RET and TP configuration.
The managedEntityScope may indicate a geographical area or a specific cell for which the analytics is requested.
The following are the enabling data for this MDA analytics
• Configuration data related with the target cell including latitude, longitude as defined in clause 4.3.2 of [6].
• Configuration data relayed with the cell including azimuth, ARFCN, Antenna height, electrical tilt, minimum electrical tilt, maximum electrical tilt, mechanical tilt and antenna identification as defined in clause 5 of [7].
The MDAReport for this analytic will contain the following information in addition to the common information element of analytics outputs defined in clause 8.3.1 of 3GPP [2].
• Recommended tilt: This specifies the recommended RET value.
• Recommended TP: This specifies the recommended TP value.
Note: the recommendations would apply to the transmission point(s) related with the target cell(s)
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.4.4 Evaluation of solutions
| TBD
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.5 Use case 5: Interference Cell grouping analytics
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.5.1 Description
| For several RAN automation capabilities, it is typically not possible to analyse the entire network with one instance of the automation function. The automation functions need to be configured with the scope of the RAN (the group of cells) for which the automation function should undertake its automation actions. E.g. SON functions for interference minimization or for handover optimization, the MnS consumer needs to configure the set of cells that are within the same neighbourhood and that need to be analysed for interference minimization or for handover optimization. Relatedly, For a closed control loop for automated status monitoring that is responsible for continuous monitoring of the network status and resolution of any detected issues, the closed loop instance needs to be configured with the network scope for which the closed control loop instance is responsible.
The selection of cells to be considered as part of one group, e.g., considered as being in the same neighbourhood for interference minimization, can be generated by an analytics capability and based on constraints set by the MnS consumer. An example constraint could be the maximum number of interferers for each cell. The MnS consumer can request for analytics to satisfy several constraints' values and obtain analytics outcomes of the corresponding grouping of cells for the different constraints' values.
The MnS producer for MDA should include capability to provide an analytics report on cell grouping to support interference minimization.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.5.2 Potential requirements
| REQ-CellGRP-1: The MnS producer for MDA should include capability to provide analytics output on cell grouping for interference minimization.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.5.3 Potential solutions
| To support analytics output on cell grouping:
- introduce a capability for "interference minimization cell grouping analytics" under the "Correlation analytics" MDA capabilities. The MDA type is: CorrelationAnalytics.InterferenceCellGroupingAnalysis.
- The enabling data for CorrelationAnalytics. InterferenceCellGroupingAnalysis may include Configuration data, Geographical data and Performance measurements.
- The analytics output for CorrelationAnalytics. InterferenceCellGroupingAnalysis is a recommendation containing one or more cell groups. Each cell group is a list of DNs of the cells recommended to be within that group.
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 5.3.5.4 Evaluation of solutions
| TBD
|
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 6 Conclusions and recommendations
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 6.1 Improvements to interoperability
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 6.2 Improvements to MDA framework
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 6.3 New and enhanced analytics capabilities
| |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 6.3.1 Enhance the Mobility performance analysis use case
| The use case, requirements and solution for Enhance the Mobility performance analysis is described in clause 5.3.1. It is recommended to enhance the existing Mobility performance analysis capability in TS 28.104 [2] to support MDA analytics for Mobility performance analysis analytics. The detailed solution is described in clause 5.3.1.3.
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
Initial skeleton
0.0.0
2025-08
SA5#162
S5‑253605
pCR
Pseudo-CR on TR 28.886 Add clause structure
0.1.0
2025-08
SA5#162
S5‑254044
pCR
Pseudo-CR on TR 28.886 Enhance the mobility performance analysis use case
0.1.0
2025-08
SA5#162
S5‑254045
pCR
Pseudo-CR on TR 28.886 Add MDA integration use case
0.1.0
2025-08
SA5#162
S5‑254046
pCR
Pseudo-CR on TR 28.886 Add failure resolution use case
0.1.0
2025-10
SA5#163
S5‑254687
pCR
Pseudo-CR on TR 28.886 Add solution for enhance the mobility performance analysis use case
0.2.0
2025-10
SA5#163
S5‑254684
pCR
Pseudo-CR on TR 28.886 Add new use case on domain information for MDAFunction
0.2.0
2025-10
SA5#163
S5‑254685
pCR
Rel-20 pCR TR 28.886 Add new use case on radio resource optimization based on per SSB usage
0.2.0
2025-10
SA5#163
S5‑254686
pCR
Rel-20 pCR 28.886 RET Analytics
0.2.0
2025-10
SA5#163
S5‑254688
pCR
Pseudo-CR on TR 28.886 Add requirements and solution for failure resolution
0.2.0
2025-10
SA5#163
S5‑254782
pCR
Pseudo-CR on TR 28.886 Add solution for MDA scope
0.2.0
2025-11
SA5#164
S5‑255557
pCR
pCR TR28.886 Cell grouping for inference Analytics.docx
0.3.0
2025-11
SA5#164
S5‑255201
pCR
Pseudo-CR on TR 28.886 Add evaluation and conclusion for enhance the mobility performance analysis use case
0.3.0
2025-11
SA5#164
S5‑255558
pCR
Rel-20 pCR TR 28.886 Add solution for radio resource optimization based on per SSB usage
0.3.0
2025-11
SA5#164
S5‑255559
pCR
Rel-20 pCR 28.886 RET Analytics
0.3.0
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 1 Scope
| The present document …
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 28.567: "Management and orchestration; Management aspects of closed control loops"
[3] 3GPP TS 28.312: "Management and orchestration; Intent driven management services for mobile networks"
[Z4] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics (MDA) "
[X] 3GPP TS 28.567: “Management and orchestration; Management Aspects of Closed Control Loops”
[Y5] 3GPP TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[6Z] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 3 Definitions of terms, symbols and abbreviations
| |
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 3.1 Terms
| For the purposes of the present document, the terms given in 3GPP 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 3GPP TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
<ABBREVIATION> <Expansion>
4. Use Cases
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.1 Closed Control Loop for Network Maintenance
| |
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.1.1 Description
| Network maintenance operations (e.g., software upgrades, downgrades, patching of network functions, license renewals, certificate renewals etc.) can significantly affect service continuity, performance, and user experience. Because of this, they need to be planned, validated, executed, and monitored with minimal disruption. CCLs can help in assisting and automating the maintenance operations, in particular when maintenance needs to be performed in complex scenarios with multiple network functions with dependencies among them, in a large-scale network deployment.
This use case describes a scenario in which an MnS consumer requests a CCL for network maintenance, for example, a software upgrade, to achieve automation for network maintenance. The request may include the type of maintenance required ( e.g., software upgrade, software downgrade), target version for maintenance, any constraints for maintenance (e.g., time-window when the maintenance should take place), as well as any policies required for network maintenance the order of NFs for maintenance, whether isolation of NFs is required for network maintenance work, etc.
The intent-driven MnS producer may be MnS consumer of a Network Maintenance CCL MnS producer if the intent-driven MnS producer handles a Network Maintenance Expectation as specified in 3GPP TS 28.312 [3], clause 6.2.2.1.6.
A CCL for network maintenance may also use MDA reports in 3GPP TS 28.104 [4], for example, for the maintenance use-cases described in clause 7.2.6, to decide and execute necessary actions for network maintenance. A CCL for network maintenance may also analyse the impact of requested software update, for example, the impact of upgrading an NF software version. CCL for network maintenance delivering software updates may also coordinate with Conflict Management and Coordination Entity as specified in TS 28.567 [2], clause 6.3.6 whether requested network maintenance cause any conflicts to existing operations. Based on the analysis, CCL may execute required actions to deliver software updates or execute a rollback in case software updates negatively impact operations.
A CCL for network maintenance takes responsibility for a specific scope. In the RAN, the maintenance scope can be for a set of related RAN objects. The scope can be indicated as a list of cells whose nodes (CUs, DUs or radios) are desired to have the same software version. The CCL can be instantiated with a scope indicated a list of cells for which maintenance is required.
The CCL for network maintenance MnS producer reports the result of network maintenance, including the resultant maintenance and any other relevant information.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.1.2 Potential requirements
| REQ-MaintenanceCCL -1: The 3GPP management system should have the capability to allow MnS consumer to request a closed control loop for network maintenance delivering software updates
REQ-MaintenanceCCL-2: The 3GPP management system should have the capability to allow MnS consumer to get a report from the closed control loop regarding the network maintenance delivering software updates.
REQ-MaintenanceCCL -3: The 3GPP management system should have the capability enabling the MnS consumer to instantiate the closed control loop with the scope for the maintenance indicated as a cell list
Note: the cell list may for example be cells which are required to have the same software.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.1.3 Potential solutions
| |
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.1.3.1 Potential solution #1
| This solution includes defining a new IOC for Network Maintenance CCL, which can be represented by CCLPurpose <<ProxyClass>> as specified in 3GPP TS 28.567 [2], clause 6.3.12. This IOC includes attributes for the following information:
• The type of network maintenance that Network Maintenance CCL needs to deliver, e.g. software upgrade, software downgrade, software patches etc.
• Software version which Network Maintenance CCL needs to execute.
• The time window for the Network Maintenance CCL needs to execute their actions
• The maintenance order for NFs/NEs that Network Maintenance CCL needs to execute their actions
• Any requirement for isolating or backing up the managed object that Network Maintenance CCL needs to consider before executing their actions
• Relevant thresholds for the Network Maintenance CCL to start delivering network maintenance or to execute a rollback.
• Information regarding cell(s) for which network maintenance is requested.
This solution also includes defining a new dataType for Network Maintenance CCL result to be supported by CCLReport as specified in 3GPP TS 28.567 [2], clause 6.3.3. This new dataType includes attributes for the following information:
• The time window that the network maintenance took place.
• The delivered software version after network maintenance
• Reporting any rollback
If the Network Maintenance CCL conflicts with other CCLs, this conflict information can be reported by the ConflictManagementAndCoordinationEntity.
TBD
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.2 CCL for network capacity optimization
| |
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.2.1 Description
| Cellular networks have multiple managed objects (existing in RAN, CN and OAM) running together to fulfill the required services. This group of managed objects (MO) need to be monitored to check if the existing capacity of the object is enough for the current or near future demands. Network monitoring mechanisms are used to monitor the network and then manage the available capacity of the network. For example, if the current trends suggest the increase of traffic at a UPF in near future, an additional instance of the UPF is created to cater for the increasing traffic demand. CCL can be used to automate this process and optimize the available capacity of the network.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.2.2 Potential requirements
| REQ-NET-CAP-1: The 3GPP management system should support a capability allowing an authorized MnS Consumer to request for optimization of available network capacity.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.2.3 Possible solutions
| TBD
4.2.3.1 Potential Solution 1
This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support a capacity optimization closed control loop, the following can be introduced:
- An IOC for capacity optimization CCL as a new CCL purpose, say called CapacityOptimizationCCL that inherits from a closed control loop. The CCL is to manage lifecycle of MO (managed object) automatically to optimize the overall network capacity. This requires the definition of CCL metrics pertaining to MO LCM.
- The scope of the IOC may be a managed object instance or a list of managed object instances (e.g. a list of CUs, or DUs ) or cell identifiers
- Attributes related with recommendations for MO LCM.
- Attributes related with reporting of executed LCM operations.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.3 Automated status monitoring
| |
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.3.1 Description
| This use case describes a scenario in which an MnS consumer may request a CCL for continuous monitoring of the network status and resolution of any detected issues, such as performance outliers. The MnS consumer may request to monitor the status of a complete network or a specific subset of the network.
Based on the request, the MnS producer creates a CCL instance and indicates the scope of the network which should be monitored. The scope may be indicated as a list of references to MOIs (e.g. list of network functions or cells. At regular intervals, the CCL instance collects alarm data and performance data from the network. The CCL instance analyses the collected data for indications of possible faults or possible performance problems.
If the analysis indicates a possible fault or a possible performance problem, the CCL instance may decide on a solution for the issue and execute the solution. The MnS producer may provide a report on issues that have been detected and the actions that were executed to resolve the issues.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.3.2 Potential requirements
| REQ-Monitor-CCL -1: The 3GPP management system should have the capability to allow MnS consumer to instantiate a closed control loop for Automated status monitoring
REQ- Monitor-CCL -2: The 3GPP management system should have the capability to enabling the MnS consumer to instantiate the closed control loop with the scope to be monitored indicated as a list of managed object instances or cell identifiers.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.3.3 Potential solutions
| This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support a network maintenance closed control loop, it is proposed to:
- introduce an IOC for status monitoring CCL, say called PerformanceMonitoringCCL. It is a CCL purpose that inherits the capabilities of the closed control loop
- The performance monitoring CCL is a CCL purpose that inherits the capabilities of a closed control loop IOC
- The scope of the IOC may be a managed object instance or a list of managed object instances (e.g. a list of CUs, or DUs ) or cell identifiers
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.3.4 Evaluation of solutions
|
54.X4 CCL for Multi-domain ES Optimization
54.X4.1 Description
TS28.310 [5] and 28.541 [6] have specified capabilities for energy saving management where a distributed or centralized Energy Saving Function (DESF, CESF) decide whether to activate a cell (send a cell into energy saving state) or to deactivate a cell (wake up a cell from an energy saving state). The DESF and CESF are functionalities responsible for cells in individual RAN domains, e.g. specific administrative Ran domains. For multiple domains, e.g. multiple RAN domains, a closed control loop can evaluate and control the ES actions for different elements in different domains, e.g., across several RAN administrative domains. The CCL can for example decide which the times at which ES functionality can be activated in specific geographical areas, reduce CPU frequency in core network functions or implement core sleep modes.
The closed control loop can be composed to include existing capabilities. For example, TS 28.104 [X4] has specified MDA reports on supporting analysis and predictions of potential issues and corresponding relevant causes and recommended actions for preventions, and/or prediction of network and/or service demands, energy saving analysis. The MnS consumer can compose MDA capabilities for service demands and energy savings analysis as part of a closed control loop for multi-domain energy saving optimization. It should be possible for the MnS consumer to compose or instantiate the closed control loop for multi-domain energy saving optimization.
5.X4.4.2 Potential requirements
REQ- CCL-ES-1: The management system should enable the MnS consumer to compose or instantiate the energy savings closed control loop for multi-domain energy saving optimization.
4.45.x.3 Possible solutions
This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support compose or instantiate the energy savings closed control loop for multi-domain energy saving optimization, the following can be introduced:
- an IOC for multi-domain energy savings optimization CCL purpose (MUDESO CCL). It is a CCL purpose and inherits the capabilities of the closed control loop .
- an attribute on the MUDESO CCL for a data collection component for energy savings data that reuses the CCLComponent <<dataType>>.
- datatypes and related attributes on the MUDESO CCL each for service analytics component and energy saving analysis component to be applied as components of the multi-domain energy savings optimization CCL.
- Introduce attributes on each component to represent the analytics output of one component used by other components. The attribute can point to specific analytics outputs from TS28.104
- A datatype and corresponding attribute indicating the actions of the multi-domain energy savings optimization CCL which can be taken towards the domain-specific functionality like the DESF or the CESF. The attributes of this dataType are the control parameters of the DESF and CESF. This is needed to capture and track the decisions taken by the MUDESO CCL.
5.4.4X.4 Evaluation of solutions
.
4.X5 Dynamic CCL for resource optimization
4.X5.1 Description
A CCL may require different kinds of input to address its requirements. 3GPP TS 28.104 [4], specified MDA with reports on different kinds of analysis of network issues, predictions of potential issues and corresponding relevant causes and recommended actions for preventions, and/or prediction of network and/or service demands. The analytics output includes analysis related to network slice resources, for example to optimize, i.e., increase or decrease the capacity of gNB to enhance allocation of the physical resources or to schedule the "scale in" and "scale out" of VNFs via ETSI MANO system to optimize the allocation of the virtualized resources. Other analytics could for example include decisions for when to instantiate new gNBs or when to add gNBs to the scope where a specific network slice can be served.
A closed control loop can be instantiated to optimize the network slice resource reusing where applicable the existing analytics capabilities, e.g. MDA analytics. It should be possible for the MnS consumer to instantiate such a CCL for network slice resource optimization and to indicate cases where analytics capabilities can be used by the CCL instance.
Note: relation of this use case with the assurance closed control if FFS.
4.5.X.2 Potential requirements
REQ- CCL-ES-1: The management system should enable the MnS consumer to compose a network slice resource optimization closed control loop that uses MDA capabilities as analytics components of the CCL
4.5.x.3 Possible solutions
This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support the composition of a CCL on network slicing resource optimization, it is proposed:
- to introduce an IOC for network slice resource optimization closed control loop.
- The network slice resource optimization CCL IOC is CCL purpose that inherits the capabilities of the closed control loop and the assurance closed control loop.
- to introduce attributes on the network slice resource optimization CCL for analysis insight and decision recommendation on resource optimization components.
- to introduce a datatype and an attribute on the network slice resource optimization CCL for indicating the actions which can be taken by the CCL.
NOTE: the usage of the dataTypes can be further investigated
4.5.X.4 Evaluation of solutions
.
Annex <X>:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
-
n/a
-
-
-
Initial skeleton
0.0.0
2025-10
SA5#163
S5‑254702
S5‑254885
S5‑254704
pCR
-
-
pCR on Rel-20 TR 28.889 Add use case description and requirement for Network Maintenance CCL
Rel-20 pCR 28.889 CCL for LCM
Pseudo-CR on TR 28.889 Add status monitoring use case
0.1.0
2025-11
SA5#164
S5‑255570
S5‑255571
S5‑255572
S5‑255574
S5‑255575
S5‑255576
pCR
-
-
pCR TR28.889 CCL for Multi-domain ES Optimization.docx
pCR TR28.889 Dynamic CCL for resource optimization.docx
Rel-20 pCR 28.889 solution for CCL for network capacity optimization
pCR TR28.889 Scope of CCL for Network Maintenance.docx
Pseudo-CR on Rel-20 TR 28.889 Add potential solution for Network Maintenance CCL
pCR TR28.889 Automated status monitoring CCL Scope.docx
0.2.0
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.4 CCL for Multi-domain ES Optimization
| |
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.4.1 Description
| TS28.310 [5] and 28.541 [6] have specified capabilities for energy saving management where a distributed or centralized Energy Saving Function (DESF, CESF) decide whether to activate a cell (send a cell into energy saving state) or to deactivate a cell (wake up a cell from an energy saving state). The DESF and CESF are functionalities responsible for cells in individual RAN domains, e.g. specific administrative Ran domains. For multiple domains, e.g. multiple RAN domains, a closed control loop can evaluate and control the ES actions for different elements in different domains, e.g., across several RAN administrative domains. The CCL can for example decide which the times at which ES functionality can be activated in specific geographical areas, reduce CPU frequency in core network functions or implement core sleep modes.
The closed control loop can be composed to include existing capabilities. For example, TS 28.104 [4] has specified MDA reports on supporting analysis and predictions of potential issues and corresponding relevant causes and recommended actions for preventions, and/or prediction of network and/or service demands, energy saving analysis. The MnS consumer can compose MDA capabilities for service demands and energy savings analysis as part of a closed control loop for multi-domain energy saving optimization. It should be possible for the MnS consumer to compose or instantiate the closed control loop for multi-domain energy saving optimization.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.4.2 Potential requirements
| REQ- CCL-ES-1: The management system should enable the MnS consumer to compose or instantiate the energy savings closed control loop for multi-domain energy saving optimization.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.4.3 Possible solutions
| This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support compose or instantiate the energy savings closed control loop for multi-domain energy saving optimization, the following can be introduced:
- an IOC for multi-domain energy savings optimization CCL purpose (MUDESO CCL). It is a CCL purpose and inherits the capabilities of the closed control loop .
- an attribute on the MUDESO CCL for a data collection component for energy savings data that reuses the CCLComponent <<dataType>>.
- datatypes and related attributes on the MUDESO CCL each for service analytics component and energy saving analysis component to be applied as components of the multi-domain energy savings optimization CCL.
- Introduce attributes on each component to represent the analytics output of one component used by other components. The attribute can point to specific analytics outputs from TS28.104
- A datatype and corresponding attribute indicating the actions of the multi-domain energy savings optimization CCL which can be taken towards the domain-specific functionality like the DESF or the CESF. The attributes of this dataType are the control parameters of the DESF and CESF. This is needed to capture and track the decisions taken by the MUDESO CCL.
4.4.4 Evaluation of solutions
.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.5 Dynamic CCL for resource optimization
| |
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.5.1 Description
| A CCL may require different kinds of input to address its requirements. 3GPP TS 28.104 [4], specified MDA with reports on different kinds of analysis of network issues, predictions of potential issues and corresponding relevant causes and recommended actions for preventions, and/or prediction of network and/or service demands. The analytics output includes analysis related to network slice resources, for example to optimize, i.e., increase or decrease the capacity of gNB to enhance allocation of the physical resources or to schedule the "scale in" and "scale out" of VNFs via ETSI MANO system to optimize the allocation of the virtualized resources. Other analytics could for example include decisions for when to instantiate new gNBs or when to add gNBs to the scope where a specific network slice can be served.
A closed control loop can be instantiated to optimize the network slice resource reusing where applicable the existing analytics capabilities, e.g. MDA analytics. It should be possible for the MnS consumer to instantiate such a CCL for network slice resource optimization and to indicate cases where analytics capabilities can be used by the CCL instance.
Note: relation of this use case with the assurance closed control if FFS.
4.5..2 Potential requirements
REQ- CCL-ES-1: The management system should enable the MnS consumer to compose a network slice resource optimization closed control loop that uses MDA capabilities as analytics components of the CCL
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.5.3 Possible solutions
| This solution proposes to enhance the existing CCL information models defined in 3GPP TS 28.567 [2].
To support the composition of a CCL on network slicing resource optimization, it is proposed:
- to introduce an IOC for network slice resource optimization closed control loop.
- The network slice resource optimization CCL IOC is CCL purpose that inherits the capabilities of the closed control loop and the assurance closed control loop.
- to introduce attributes on the network slice resource optimization CCL for analysis insight and decision recommendation on resource optimization components.
- to introduce a datatype and an attribute on the network slice resource optimization CCL for indicating the actions which can be taken by the CCL.
NOTE: the usage of the dataTypes can be further investigated
4.5.4 Evaluation of solutions
.
Annex <X>:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
-
n/a
-
-
-
Initial skeleton
0.0.0
2025-10
SA5#163
S5‑254702
S5‑254885
S5‑254704
pCR
-
-
pCR on Rel-20 TR 28.889 Add use case description and requirement for Network Maintenance CCL
Rel-20 pCR 28.889 CCL for LCM
Pseudo-CR on TR 28.889 Add status monitoring use case
0.1.0
2025-11
SA5#164
S5‑255570
S5‑255571
S5‑255572
S5‑255574
S5‑255575
S5‑255576
pCR
-
-
pCR TR28.889 CCL for Multi-domain ES Optimization.docx
pCR TR28.889 Dynamic CCL for resource optimization.docx
Rel-20 pCR 28.889 solution for CCL for network capacity optimization
pCR TR28.889 Scope of CCL for Network Maintenance.docx
Pseudo-CR on Rel-20 TR 28.889 Add potential solution for Network Maintenance CCL
pCR TR28.889 Automated status monitoring CCL Scope.docx
0.2.0
3GPP TR 28.889 V0.12.0 (2025-1011)
Technical Report
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Management and orchestration;
Closed control loop management phase2
(Release 20)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
3GPP
Postal address
3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
Contents
Foreword 4
1 Scope 6
2 References 6
3 Definitions of terms, symbols and abbreviations 6
3.1 Terms 6
3.2 Symbols 6
3.3 Abbreviations 7
4. Use Cases 8
4.1 Use case1: Closed Control Loop for Network Maintenance 8
4.1.1 Description 8
4.1.2 Potential requirements 8
4.1.3 Potential solutions 8
4.2 CCL for network capacity optimization 8
4.2.1 Description 8
4.2.2 Potential requirements 9
4.2.3 Possible solutions 9
4.3 Use case Y: Automated status monitoring 9
4.3.1 Description 9
4.3.2 Potential requirements 9
4.3.3 Potential solutions 9
4.3.4 Evaluation of solutions 9
Annex <X>: Change history 10
Foreword
This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
might not indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
|
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.1 Use case1: Closed Control Loop for Network Maintenance
| |
e7b1881890a97eea7f4bc3aaa87148da | 28.889 | 4.3 Use case Y: Automated status monitoring
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 1 Scope
| The present document studies on how Coverged Charging support CAPIF enhancements and new Charging scenarios brought by the CAPIF framework, as defined in 3GPP TS 23.222 [x2].
The following items are studied:
• possible charging scenarios and requirements related to service API/AEF Instantiation and Multiple Provider Interoperability.
• potential charging solutions and impacts for API Invoker authorization and authentication.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs".
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 3 Definitions of terms, symbols and abbreviations
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 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.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 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].
3GPP 3rd Generation Partnership Project
5GS 5g System
AEF API Exposing Function
API Application Programming Interface
CAPIF Common API Framework
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 4 Concepts and background
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 4.1 General Description
|
The CAPIF core function provides the centralized CAPIF APIs that enable onboarding, discovery, security, and monitoring of exposed APIs. API invokers connect to the CAPIF core via CAPIF-1 and CAPIF-2 interfaces for onboarding and discovery of APIs, while CAPIF-1e extend these capabilities by enabling the authorization and authentication, service API discovery by an API Invoker outside the PLMN Trust domain, CAPIF-2e enable the API Invoker to communicate to the service APIS which belong to different trust domains.
The inter-operability of different CAPIF Providers is supported by the CAPIF-6e reference point, which enables integration with CCF of a trusted domain (i.e. 3rd Party, PLMN). This ensures that API invokers from one trust domain can securely discover and consume APIs exposed in another trust domain, preserving interoperability and trust management.
Figure 4.1-1: CAPIF interconnection with multiple CAPIF provider domains
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 4.2 Background
| The Common API Framework defined, in 3GPP TS 23.222 [2], offers a uniform approach for securely provides a standardized solution for exposing and consuming utilizing network APIs in a secure and interoperable manner. It incorporates shared functional components and reference points to facilitate CAPIF introduces common functional entities and reference points that support API invoker verification, permission control, oversight and administrationauthentication, authorization, monitoring, and management. This framework ensures that applicationsetup allows developers and service users to interact with consumers can access APIs via standardized methods, regardless of the network operators or API suppliers involvedthrough consistent procedures, independent of the underlying network functions or API providers.
Under the existing standards In the current specifications (3GPP TS 23.222 [2]), CAPIF is outlined operation between different CAPIF Core Function (via CAPIF-6) within the same trust domain (ilustrated in Figure 4.2-1).primarily described within a sin
Figure 4.2-1 - CAPIF interconnection within a CAPIF provider domain (Figure 6.2.2-2 of 3GPP TS 23.222 [2])
gle provider’s trust domain. The framework defines reference points, as depicted in Figure [4.2-1]
Figure 4.2-1 - AEF Instantiation (Figure H-1 of 3GPP TS 23.222 [2])
Within this frameworkIn this setup, the API Exposing Function serves as key element for making plays a central role in exposing service APIs available through to the CAPIF core. An API Provider can deploy several Multiple AEF instances may be instantiated by an API provider, each responsible for exposing specific sets of APIs.
With the growth As the ecosystem of network-exposed APIs expands, multiple various CAPIF providers are anticipated to operate alongside one another and collaborateexpected to coexist and interoperate. API invokers might require access to APIs from providers in separate administrative areas, necessitating systems for inter-domain trust establishment, verification, permission granting, linkage, and coordination among CAPIF core functions from different providers, which are dependant on the MNO business relationsmay need to consume APIs offered by providers across different administrative domains. This requires mechanisms for cross-domain trust, authentication, authorization, interconnection, and interworking between CAPIF core functions of different providers.
To support enable this, additional new reference points such as CAPIF-2e and CAPIF-6e has been added to support cross-provider verification, permission, and linkage are introduced to enable inter-provider authentication, authorization, and interconnection between CAPIF core functions. These interfaces allowconnections permit API invokers from in one trust area to safely access APIs hosted in another, independent of the specific AEF instance, thereby promoting seamless operation, expandability, and reliable trust oversight (ilustrated in Figure 4.2-2).domain to securely use APIs exposed in another trust domain, regardless of which AEF instance provides the API, ensuring interoperability, scalability, and consistent trust management.
The following figure depicts a business relation between two (2) CAPIF Providers which can be interconnected
Figure 4.2-2 - CAPIF interconnection with multiple CAPIF provider domain (Figure 6.2.2-1 of 3GPP TS 23.222 [2])
This framework and its interconnection aspects are going to be further studied in this document to evaluate potential enhancements, and its Converged Charging support.
Figure 4.2-2 - CAPIF providers interconnection (Figure 4.12.1-1 of 3GPP TS 23.222 [2])
5 CAPIF Charging Scenarios and Topics
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1 Topic #1 CAPIF Converged Charging support for service API/AEF
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.1 General description and assumptions
| The reference points used for the API invoker within and outside the PLMN trust domain and to discover service APIs are the CAPIF-1 and CAPIF-1e reference points (TS 23.222 [2] clauses 6.4.2 and 6.4.3), which exists between the API invoker and the CAPIF core function.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.2 Use Cases
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.2.1 Use Case #1.1: API Invokers Service Charging
| An operator provides CAPIF Core Functions and CAPIF-1 and CAPIF-1e reference points towards API Invokers and wants to be able to charge the API Invokers for services it provides.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.3 Potential charging requirements
| REQ-CH_CAPIF_RP-01: Charging for services provided via the CAPIF-1 and CAPIF-1e reference points shall be supported.
REQ-CH_CAPIF_RP-02: Charging for services provided via the CAPIF-1 and CAPIF-1e reference points shall be supported.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.4 Key Issues
|
Key issue #1.1: Identify the chargeable events for reference point CAPIF-1 and CAPIF-1e.
Key issue #1.2: Identify the placement of the charging trigger function for reference point CAPIF-1 and CAPIF-1e.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.5 Possible Solutions
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.6 Evaluation
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.1.7 Conclusion
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2 Topic #2 CAPIF Converged Charging of multiple API Providers
| |
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.1 General description and assumptions
| Clause 6.2.2 of 3GPP TS 23.222 [2] describes on how CAPIF Interconnection is supported.
The reference points used for publishing the service API information are the CAPIF-4 and CAPIF-4e reference points (TS 23.222 [2] clauses 6.4.7 and 6.4.10), which exists between the API publishing function within the PLMN trust domain or 3rd party trust domain and the CAPIF core function within the PLMN trust domain.
The reference points used for management of service API, API invoker and API provider domain function information are the CAPIF-5 and CAPIF-5e reference points (TS 23.222 [2] clauses 6.4.8 and 6.4.11), which exists between the API management function within the PLMN trust domain or 3rd party trust domain and the CAPIF core function within the PLMN trust domain.
Therefore, it would be necessary to evaluate the possibility to support Converged charging in such a deployment model.
|
5f53d3479ff0f89c2731a65731bf0951 | 28.891 | 5.2.2 Use Cases
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.