hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a0af2a6390198051f207bb132b271100 | 28.885 | 5.4.4.4 Evaluation of potential solutions
| Editor's Note: This clause provides the evaluation of potential solutions listed in 5.4.4.3.
5.4.X Use case #<X>: <Use case title>
5.4.X.1 Description
Editor’s note: This clause provides a description of the use case.
5.4.X.2 Potential requirements
Editor’s note: This clause captures potential requirements for the... |
a0af2a6390198051f207bb132b271100 | 28.885 | 6 Conclusions and recommendations
| |
a0af2a6390198051f207bb132b271100 | 28.885 | 6.1 Enhancements to support energy efficiency as a service criteria
| Editor’s Note: This clause is to summarize the identified use cases and to add conclusions and recommendations for a potential Work Item.
6.1.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 6.2 Enhancements to support the information required by Energy Information Function (EIF)
| 6.2.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 6.3 Improve energy saving, energy efficiency and reducing carbon footprint of 5G network
| 6.3.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
|
a0af2a6390198051f207bb132b271100 | 28.885 | 6.4 Enhancements to Energy Consumption and Energy Efficiency measurements and KPIs
| 6.4.x Use case #<X>: <Use case title>
Editor’s note: This clause captures conclusions and recommendations for the use case.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
-
N/A
-
-
-
TR skeleton
0.0.0
2025-10
SA5#163
S5-254683
pCR
-
-
... |
a7bb9a6ded530712c26c2a441a3b4d71 | 28.886 | 1 Scope
| The present document …
|
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.
-... |
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 Second... |
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 manage... |
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 dec... |
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 th... |
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 mobilit... |
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... |
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 fol... |
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 identificat... |
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 recomme... |
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) wh... |
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 ... |
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 bea... |
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 ... |
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 th... |
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. ... |
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. InterferenceCellGroup... |
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... |
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.
-... |
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 disrup... |
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 contr... |
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... |
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 use... |
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 CapacityOptimizatio... |
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 r... |
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 sc... |
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 clo... |
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 ... |
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... |
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 ... |
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 ... |
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 optimizat... |
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 Provi... |
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.
-... |
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 ... |
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 authorizatio... |
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... |
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.