hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.2.1 General
| This section describes how entities from the EDGEAPP and SEAL frameworks integrate with CAPIF. Each subsection identifies the roles that different entities play within CAPIF, whether as API Providers offering APIs for discovery and consumption or API Invokers discovering and consuming APIs published by others.
Underst... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.2.2 EDGEAPP Roles in CAPIF
| In the context of the overall CAPIF–EDGEAPP integration, it is important to distinguish between the perspectives of the application developer, typically working for an Application Service Provider, and the edge compute service provider operating the EDGEAPP framework itself.
An application developer is mainly concerne... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.2.2 SEAL Roles in CAPIF
| In SEAL, the SEAL Server can onboard as a CAPIF API Provider. It can expose enabler APIs such as Group Management, Configuration Management, and Location Management, which provide reusable context and management capabilities to vertical applications. Publishing these APIs in CAPIF enables VAL Servers or other authorize... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3 Example Application Flows
| The following flows will be considered “CAPIF + EDGEAPP”, “CAPIF + SEAL” and “CAPIF + EDGEAPP + SEAL”
|
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.1 CAPIF+EDGEAPP Application Flow
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2 CAPIF+SEAL Application Flow
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2.1 General
| This clause describes the logical flow of interactions between the SEAL Server, VAL Server, and VAL Client when CAPIF is used to enable secure API exposure, discovery, and invocation.
|
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2.2 SEAL Server Onboarding and Registration
| The onboarding procedure allows the SEAL Server to become a trusted entity within the CAPIF ecosystem. By performing this process, the SEAL Server obtains its official API invoker identity.
By the Registration process, the SEAL server obtains its official provider identity, operator and the authorization to later publ... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2.3 SEAL Server Publish APIs
| After registration with the CAPIF Core Function (CCF), the SEAL Server (acting as an APF) publishes its service APIs to the CAPIF catalogue. Publication makes the service APIs discoverable to authorized API invokers using CAPIF procedures. SEAL APIs represent one example of service APIs that may be exposed via CAPIF by... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2.4 VAL Server Onboarding
| Discovery of published service APIs, including SEAL APIs, may be performed subject to operator policy. Before invoking protected APIs, a VAL Server onboards to the CAPIF framework as an API invoker. During onboarding, the CCF authenticates the VAL Server and assigns an identifier representing the invoker within the CAP... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2.5 VAL Server Discover
| A VAL Server may discover published service APIs, including SEAL APIs, using CAPIF discovery procedures. API invoker onboarding is not a prerequisite for discovery, and open discovery may be supported subject to operator policy. The CCF returns descriptive API metadata in accordance with operator policy. Discovery itse... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2.6 VAL Server requesting token
| Prior to invoking protected service APIs, the VAL Server requests an authorization token from the CCF using CAPIF authorization procedures. The CCF validates the request against operator policy and issues a scoped access token for API invocation.
From a developer perspective, token-based authorization provides a consi... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2.7 VAL Client Requesting VAL Server Service
| A VAL Client may request services that rely on SEAL APIs through the SEAL client–server architecture. The VAL Server invokes the required SEAL APIs using CAPIF authorization mechanisms. Interaction between VAL Clients and VAL services remains outside the scope of 3GPP specifications.
From a developer perspective, this... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.3 CAPIF+EDGEAPP+SEAL Application Flow
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.4 Multi-CAPIF Considerations
| Relevant information to consider when several CAPIF are deployed
|
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 7 Security Considerations
| Aspects such as identity management across frameworks, secure onboarding and trust models, framework-specific and integrated authorization will be considered
Annex A:
Infrastructure Topology Diagrams Examples
Will show CAPIF+ EDGEAPP, CAPIF+SEAL and CAPIF+EDGEAPP+SEAL
A.1 CAPIF plus EDGEAPP Topology
Editor's not... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 4.54 Inter-framework Relationships Overview
| The integration of CAPIF, EDGEAPP, and SEAL within the 3GPP system enables a unified service enablement environment for vertical applications. Each framework addresses a specific functional domain (API exposure, edge application management, and service enabler support) while remaining interoperable under a consistent t... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.3.2.6 VAL Server Security Context
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 1 Scope
| The present document …
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 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.
-... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 3 Definitions of terms, symbols and abbreviations
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 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].
Management Service (MnS): defined in TS 28.533 [2].
External MnS consumer: defined in TS 28.533 [2... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 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].
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4 Concepts and background
| Editor’s note: This clause provides a description of concepts and background.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4.1 Overview
| The study builds upon the management services exposure scenarios defined in clause 5.6 of TS 28.533 [2], which serves as the primary reference for exposing management services to external consumers. In addition, the Management Exposure framework described in TS 28.579 [3] introduces an optional approach based on CAPIF.... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4.2 Authorization of external MnS consumers using CAPIF
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4.2.1 Introduction
| As noted in clause 5.6 of TS 28.533 [2], an operator can decide to expose 3GPP management system capabilities to external MnS consumers using existing MnS interfaces (e.g. external MnS consumer Y1), or using CAPIF (e.g. external MnS consumer Y2).
When CAPIF is not used, an external MnS consumer gets access to MnS API... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4.2.2 Authorization in CAPIF Framework
| 3GPP TS 33.122 [7] specifies security aspects of the CAPIF Framework.
CAPIF has defined three possible formats for access token’s scope. These formats are specified in the “scope” attribute in AccessTokenReq (see clause 8.5.4.2.6 of TS 29.222 [8]) and AccessTokenRsp (see clause 8.5.4.2.7 of TS 29.222 [8]).
4.3 Acces... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5 Use cases and potential solutions
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1 Use case #1: Authorization of the service API invocation request from the external MnS consumer using CAPIF
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1.1 Description
| Editor's note: This clause provides a description of use case.
For an external MnS consumer to be able to invoke service APIs at the MSED AEF, first they send the service API authorization request (over the CAPIF-1e interfaced) to the CCF to request for the authorization to access one or more service APIs. If the serv... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1.2 Potential requirements
| Editor's note: This clause provides potential requirements for the corresponding use case.
PREQ-FS_EnExpo-AuthCCF-01: The exposure of management services using CAPIF shall provide the capability enabling the authorization of the service API invocation request(s) at the MSED AEF.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1.3 Potential solutions
| Editor's note: This clause provides one or more solutions. Further (sub-)clause(s) may be added to capture details.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1.4 Evaluation of potential solutions
| Editor's note: This clause provides evaluation of potential solutions.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2 Use case #2: Access control on notifications
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2.1 Description
| Editor's note: This clause provides a description of use case.
When an MnS consumer subscribes to receive notifications using the NtfSubscriptionControl IOC (see clause 4.3), the 3GPP management system needs to be able to determine whether a given MnS consumer is authorized to receive notifications on a set of managed... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2.2 Potential requirements
| Editor's note: This clause provides potential requirements for the corresponding use case.
PREQ-FS_EnExpo-Ntf-01: The 3GPP Management System should provide the capability to configure, per role (as defined in clause 7.3.2 of TS 28.319[4]), the set of notification types that the MnS consumer is authorized to receive.
... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2.3 Potential solutions
| Editor's note: This clause provides one or more solutions. Further (sub-)clause(s) may be added to capture details.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2.4 Evaluation of potential solutions
| Editor's note: This clause provides evaluation of potential solutions.
5.X Use case #3: Transformation of MnS information for external MnS consumers
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.3.1 Description
| Editor's note: This clause provides a description of use case.
When an external MnS consumer which is located outside the PLMN trust domain requests access to network information, 3GPP management system needs to ensure that internal 5G information is not revealed. For instance, the relevant "S-NSSAI" need to be transf... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.3.2 Potential requirements
| Editor's note: This clause provides potential requirements for the corresponding use case.
REQ-EnExpo-Trans-01: The 3GPP management system should support a transformation to replace S‑NSSAI with AF‑Service‑Identifier before exposure to external MnS consumers.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.3.3 Potential solutions
| Editor's note: This clause provides one or more solutions. Further (sub-)clause(s) may be added to capture details.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.3.4 Evaluation of potential solutions
| Editor's note: This clause provides evaluation of potential solutions.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 6 Conclusions and recommendations
| 6.X Use case #<X>: <use case title>
Editor's note: This clause provides conclusions and recommendations for the corresponding use case.
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
202... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 1 Scope
| The present document studies the charging aspects of 6G system. This includes new charging business models and potential charging metrics, 6G charging architecture and charging mechanism, and the charging aspects of 6G services and frameworks.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 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.
-... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 3 Definitions of terms, symbols and abbreviations
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 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.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 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].
ABMF Account Balance Management Function
CDR Charging Data Record
CGF Ch... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4 High-level description
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.1 Background
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.1.1 5G Converged Charging System
| The converged charging online and offline charging system is introduced for 5G system, as described in the TS 32.240 [2] clause 4.3.3.2. The following figure 4.1.1-1 specified the converged charging architecture.
Figure 4.1.1-1: Logical ubiquitous converged charging architecture
The Converged charging system inclu... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.1.2 Potential SA1 requirements
| A set of charging requirements are identified in SA1 TR 22.870 [3] and copied below:
- [PR 5.5.9.6-1] Subject to operator policy and user consent, the 6G system shall support means to provide users with differentiation of QoS and charging based on users’ digital identity information issued by a third party and users’ ... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.1.3 Potential New Services with Charging Concern
| Table 4.1.3-1: Potential New Services with Charging Concern
Potential New Services
Description
UE assisted services
services involving UE contributions, e.g., certain types of sensing services
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.1.3.1 UE assisted services
| The new services enabled by 6G networks will be different from the legacy communication services. In legacy networks, the UE acts as a service consumer. However, in 6G networks, the UE will assist MNO to provide new services, contributing capabilities such as sensing and the 6G service consumers will expand beyond the ... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.2 Business Model for 6G Charging
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.2.1 Considerations
| The 6G network will introduce new and enhanced services that may lead to new charging business models. To enable 6G, it is essential to support new capabilities and services, engage new ecosystem stakeholders, and evaluate the associated business models. Therefore, the following are considered in the 6G business model:... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.2.2 Business roles
| This clause analyzes the business roles, including charging party (who to charge) and charged party (who to be charged).
Table 4.2.2-1: Description and Examples of Business roles in 6G
Business Role
Description
Examples
Charged party
The entity that is charged for the consumed 6G service or resource.
Individual... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 4.2.3 Business models
| This clause aims to explore innovative business models required to monetize the new capabilities and services introduced by the 6G system. The potential models may move beyond the traditional volume/time/event-based charging of 5G to incorporate value, quality and specific resource utilization.
Table 4.2.3-1: Descript... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5 Topics
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1 Topic 1: Charging Architecture
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.1 General description
| This topic focuses on the 6G charging architecture which defines the charging network functions and interfaces. The 6G charging architecture will need to handle increased traffic and data with diverse value generated by new services, and to be in line with the overall 6G system architecture studied in TR 23.801-01 [4].... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.2 Use cases
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.2.1 Use Case #1.1: Charging for edge applications
| In the 6G era, the MNOs can provide the customized industry/vertical private network services to enterprises/companies (e.g., smart factories, mines, ports). For example, in the low-latency charging scenario, edge applications demand extremely fast response times and low-latency for charging control from 6G charging sy... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.2.2 Use Case #1.2: 6G charging architecture
| Considering the evolution of 6G system (e.g. increased traffic and data with diverse value generated by new services), the 6G charging architecture should support the charging scenarios for 6G charging systems.
The potential charging requirements for this UC is: REQ-3GPP6GCH-ARC-02.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.2.3 Use Case #1.3: Refund
| In the 6G era, the MNOs may provide 6G services with assistance from UEs. So when charging for this kind of services, the 6G charging system should consider the UE’s contribution. For example, the UE's involvement can be evaluated based on the volume of data it contributes. Therefore, timely refund for UEs is required.... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.3 Potential charging requirements
| The following are potential charging requirements:
- REQ-3GPP6GCH-ARC-01: The 6G charging system may support charging for edge applications.
- REQ-3GPP6GCH-ARC-02: The 6G charging system shall support evolved charging architecture.
- REQ-3GPP6GCH-ARC-03: The 6G charging system may support refund.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.4 Key issues
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.4.1 Key Issue #1.1: Charging for edge applications
| This key issue addresses the REQ-3GPP6GCH-ARC-01, to investigate charging for edge applications, including
- The interaction and coordination for low-latency charging scenario
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.4.2 Key Issue #1.2: Charging architecture
| This key issue addresses the REQ-3GPP6GCH-ARC-02, to investigate charging architecture including
- Whether and how to define the charging functionalities in the 6G charging system.
- The reference points provided by 6G charging architecture.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.4.3 Key Issue #1.3: Refund
| This key issue addresses the REQ-3GPP6GCH-ARC-03, to investigate the refund, including
• when to get the UE’s contribution information
- the detailed definition of UE’s contribution information
- where to get and process the UE’s contribution information
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.5 Solutions
| 5.1.5.1 Solution #1.1: Distributed Charging Architecture with Local CHS for Edge Applications
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.5.1.1 General description
| This solution addresses Key Issue #1.1 by introducing a distributed charging architecture. The traditional centralized charging system is divided into a Central CHarging System (C-CHS) and a Local CHarging System (L-CHS). C-CHS is located in the central core network while L-CHS is deployed at the network edge.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.5.1.2 Procedure description
| The figure 5.1.5.1.2-1 describes the high-level procedure for distributed charging architecture with local CHS for edge applications.
Figure 5.1.5.1.2-1: Message flow for Distributed Charging Architecture with Local CHS for Edge Applications
1. When a 6G UE uses an edge service, the CTF interacts with the nearest C... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.6 Evaluation
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.7 Conclusion
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2 Topic 2: Charging Mechanism
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.1 General Description
| This topic focuses on the necessary enhancements to the charging mechanisms which are used for charging services. This is specifically driven by the need to support requirements of the charging mechanism, and to enable the introduction of 6G services. The charging mechanism covers the following aspects:
- Charging ser... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2 Use cases
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2.1 Use Case #2.1: Unified Charging Data
| A MNO has a service that relies on the combined functionality and resources of both 6G NFs and existing 5G NFs within the core network. The MNO wants the charging mechanism to ensure that all service charging information generated across the coexisting 5G and 6G domains is uniformly collected, correlated and processed.... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2.2 Use Case #2.2: Organization and structuring of OpenAPI
| Precondition is that OpenAPI will be used for 6G.
The stage 2 definitions of the Information Elements for the domains, subsystem, and services are described in the 5G service charging specifications (e.g., TS 32.254 [5], TS 32.255 [6], and TS 32.256 [7]) and stage 3 definitions of the OpenAPI resource attributes in th... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2.3 Use Case #2.3: Organization and structuring of ASN.1
| Precondition is that ASN.1 will be used for 6G.
The stage 2 definitions of the Information Elements for the domains, subsystem, and services are described in the 5G service charging specifications (e.g., TS 32.254 [5], TS 32.255 [6], and TS 32.256 [7]) and stage 3 definitions of the ASN.1 attributes in the TS 32.298 [... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2.4 Use Case #2.4: Charging for Multi-dimensional Resources
| A 6G service may require a bundle of composite capabilities that includes not only network resources but also computing, AI, data or other capabilities, i.e. a multi-dimensional resources. When a UE triggers a 6G service instance, one or multiple 6G NFs may generate charging information. The MNO requires the charging s... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2.5 Use Case #2.5: Optimization Charging information collection and reporting
| In the 6G era, the number of on simultaneous ongoing sessions and other chargable events will be huge, and thereby the charging information carried in the charging requests. The following charging information collection and reporting issues will become increasingly prominent:
- What charging information that is useful... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2.6 Use Case #2.6: Minimizing the number of charging request
| In the 6G era the number of on simultaneous ongoing data sessions and other events will be huge, and thereby the number of charging requests. Today the number of requests from the network function to the charging is controlled by the number events that require immediate charging triggering. This means that being able t... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2.7 Use Case #2.7: Optimization of charging sessions
| In the 6G era the number of on simultaneous ongoing data sessions will be huge. Today there is a one-to-one relationship between a data session and a charging session meaning, it may even be more since one data session may trigger exposure charging etc. Therefore, an MNO would like to have the possibility to optimise t... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.2.8 Use Case #2.8: Charging for service with burst traffic
| Emerging services, such as those enabled by GenAI applications, are typically characterized by burst traffic with dynamic QoS requirements. These services introduce traffic patterns and service expectations distinct from traditional applications. It requires 6G system to provide efficient charging mechanisms for burst ... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.3 Potential charging requirements
| The following are potential charging requirements:
- REQ-3GPP6GCH-DAT-01: The 6G charging system shall support unified charging data that are interoperable for 5G and 6G.
- REQ-3GPP6GCH-DOC-01: The OpenAPI specification shall support keeping the stage 2 definitions of domains, subsystem, and services information elem... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.4 Key issues
| |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.4.1 Key Issue #2.1: Charging Data Interoperability
| This key issue is for investigating on how to support unified charging data to address REQ-3GPP6GCH-DAT-01.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.4.2 Key Issue #2.2: Optimize the handling of the OpenAPI resource attributes
| This key issue addresses REQ-3GPP6GCH-DOC-01.
Optimize the handling of the information elements and OpenAPI resource attributes for domains, subsystem, and service in specifications.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.4.3 Key Issue #2.3: Optimize the handling of the ASN.1 attributes
| This key issue addresses REQ-3GPP6GCH-DOC-02.
Optimize the handling of the information elements and ASN.1 attributes for domains, subsystem, and service in specifications.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.4.4 Key Issue #2.4: Charging Mechanism for Multi-dimensional Resources
| This key issue addresses REQ-3GPP6GCH-MDR-01 and is to investigate how to support charging for multi-dimensional resources.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.4.5 Key Issue #2.5: The charging information collection and reporting mechanism
| This key issue addresses REQ-3GPP6GCH-EFF-01.
- Investigate and identify possible optimizations for charging information at collection and reporting for 6G charging system.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.1.5.6 Key Issue #2.6: Optimize the number of charging triggering
| Optimize the number of charging triggering required to support the 6G charging.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.5.7 Key Issue #2.7: Optimize the number of charging sessions
| Optimize the number of charging sessions required to support the 6G charging.
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.4.8 Key Issue #2.8: Charging for service with burst traffic
| This key issue addresses the REQ-3GPP6GCH-BST-01, to investigate charging mechanism for service with burst type traffic.
5.2.5 Solutions
|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.5.1 Solution #2.1: Enhanced CHF for Unified Charging Data
| This solution addresses Key Issue #2.1 and proposes enhancing the existing CHF to natively support 6G charging service interfaces while maintaining backward compatibility with 5G charging messages. This enhanced CHF will process and correlate cross-generation charging data uniformly.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.