hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 4 High-level description
| |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 4.1 Background
| |
96f8bdc68da73f6fda85234415019d6f | 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... |
96f8bdc68da73f6fda85234415019d6f | 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’ ... |
96f8bdc68da73f6fda85234415019d6f | 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
|
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 4.1.3.1 UE assisted services
| The new services enabled by 6G networks will be different from the legacy connectivity services. In legacy systems, the UE acts as a service consumer. In 6G, the UE will assist MNO to provide new services, contributing capabilities such as sensing and the 6G new service consumers will expand beyond the UE to include an... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 4.2 Business Model for 6G Charging
| |
96f8bdc68da73f6fda85234415019d6f | 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:... |
96f8bdc68da73f6fda85234415019d6f | 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... |
96f8bdc68da73f6fda85234415019d6f | 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... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5 Topics
| |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.1 Topic 1: Charging Architecture
| |
96f8bdc68da73f6fda85234415019d6f | 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].... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.1.2 Use cases
| |
96f8bdc68da73f6fda85234415019d6f | 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... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.1.3 Potential charging requirements
| The following are potential charging requirements for Use Case #1.1:
- REQ-3GPP6GCH-ARC-01: The 6G charging system may support charging for edge applications.
|
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.1.4 Key issues
| |
96f8bdc68da73f6fda85234415019d6f | 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;
|
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.1.5 Solutions
| 5.1.5.Y Solution #1.Y: <Solution Title>
|
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.1.6 Evaluation
| |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.1.7 Conclusion
| |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.2 Topic 2: Charging Mechanism
| |
96f8bdc68da73f6fda85234415019d6f | 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... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.2.2 Use cases
| |
96f8bdc68da73f6fda85234415019d6f | 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.... |
96f8bdc68da73f6fda85234415019d6f | 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... |
96f8bdc68da73f6fda85234415019d6f | 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 [... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.2.3 Potential charging requirements
| The following are potential charging requirements for Use Case #2.1:
- REQ-3GPP6GCH-DAT-01: The 6G charging system shall support unified charging data that are interoperable for 5G and 6G.
The following are potential charging requirements for Use Case #2.2:
- REQ-3GPP6GCH-DOC-01: The OpenAPI specification shall supp... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 5.2.4 Key issues
| |
96f8bdc68da73f6fda85234415019d6f | 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.
|
96f8bdc68da73f6fda85234415019d6f | 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.
|
96f8bdc68da73f6fda85234415019d6f | 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.
5.2.5 Solutions
5.2.5.1 Solution #2.1: Enhanced CHF for Unified Charging Data
This solution addresses Key Issue #2.1 and proposes enhancing t... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 6 Conclusions and Recommendations
|
Annex <X> :
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-10
SA5#163
S5‑254357
Initial skeleton
0.0.0
2025-10
SA5#163
S5‑254818
S5‑254816
S5‑254817
S5‑254819
S5‑254820
S5‑254821
Update of the skeleton
Update of the Scope
Add backg... |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 1 Scope
| The present document contains requirements and test cases that are specific to the NR Femto network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases. It also specifies the requirements and test cases unique to the N... |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 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.
-... |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 3 Definitions of terms, symbols and abbreviations
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 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].
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 3.2 Symbols
| Void.
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 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].
Void.
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4 NR Femto-specific security requirements and related test cases
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.1 Introduction
| NR Femto-specific security requirements include both requirements derived from NR Femto-specific security functional requirements as well as security requirements derived from threats specific to NR Femto as described in TR 33.926 [2]. Generic security requirements and test cases common to other network product classes... |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2 NR Femto-specific adaptations of security functional requirements and related test cases
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.1 Introduction
| The present clause contains NR Femto-specific security functional adaptations of requirements and related test cases.
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.2 Security functional requirements on the NR Femto deriving from 3GPP specifications and related test cases
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.2.0 General
| The general approach in TS 33.117 [3] clause 4.2.2.1 applies to the NR Femto network product class.
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.2.1 NR Femto Device Authentication failure
| Requirement Name: NR Femto device authentication failure
Requirement Reference: TS 33.545 [4], clause 5.21
Requirement Description: Device mutual authentication between NR Femto and SeGW shallis expected to be performed using IKEv2 certificate-based authentication as specified in TS 33.545 [4], clause 5.21 and in TS... |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.2.2 Hosting Party Mutual Authentication
| Requirement Name: Hosting party mutual authentication
Requirement Reference: TS 33.545 [4], clause 5.32
Requirement Description: The hosting party mutual authentication is optionally performed by the operator’s network following successful device mutual authentication between NR Femto and SeGW.The authentication of ... |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3 Technical Baseline
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.1 Introduction
| The present clause provides baseline technical requirements.
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.2 Protecting data and information
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.2.1 Protecting data and information – general
| There are no NR Femto-specific additions to clause 4.2.3.2.1 of TS 33.511[6]
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.2.2 Protecting data and information – unauthorized viewing
| There are no NR Femto-specific additions to clause 4.2.3.2.2 of TS 33.511[6]
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.2.3 Protecting data and information in storage
| There are no NR Femto-specific additions to clause 4.2.3.2.3 of TS 33.511[6]
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.2.4 Protecting data and information in transfer
| There are no NR Femto-specific additions to clause 4.2.3.2.4 of TS 33.511[6]
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.2.5 Logging access to personal data
| There are no NR Femto-specific additions to clause 4.2.3.2.5 of TS 33.511[6]
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.3 Protecting availability and integrity
| There are no NR Femto-specific additions to clause 4.2.3.3 of TS 33.511[6]
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.4 Authentication and authorization
| Editor’s Note: This clause is FFS.
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.5 Protecting sessions
| There are no NR Femto-specific additions to clause 4.2.3.5 of TS 33.511[6]
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.3.6 Logging
| Editor’s Note: This clause is FFS.
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.4 Operating systems
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.5 Web servers
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.2.6 Network devices
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.3 NR Femto-specific adaptations of hardening requirements and related test cases.
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.3.1 Introduction
| The present clause contains NR Femto-specific adaptations of hardening requirements and related test cases.
|
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.3.2 Technical Baseline
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.3.3 Operating Systems
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.3.4 Web Servers
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.3.5 Network Devices
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.3.6 Network Functions in service-based architecture
| |
73bbea4dcc9f984a76108dc2c2f9575d | 33.546 | 4.4 NR Femto-specific adaptations of basic vulnerability testing requirements and related test cases
| Annex <X> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-10
SA3#124
TS skeleton
0.0.0
2025-10
SA3#124
S3-253766
Incorporated accepted contributions: S3-253765, S3-253440
0.1.0
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 1 Scope
| The present document specifies general requirements for security related events handling and collection as well as the general requirements to transfer or communicate the security related events occurring at the SBA layer of the 5G system. The protection mechanisms to be applied for configuration and delivery of the ev... |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 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.
-... |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 3 Definitions of terms, symbols and abbreviations
| |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 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.
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 3.2 Symbols
| Void.
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 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].
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 4 Overview of Security related Events handling
| The Service Based Architecture (SBA) is the dominant method for control plane as well as the Service Based Management Architecture (SBMA) is for management communications. In addition to the many benefits of using SBA, e.g. agility to increase and decrease the number of service instances in coordination with demand, po... |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 5 Security related events requirements
| Editor’s Note: This clause addresses the general requirements to secure the procedures to configure, collect and deliver security related events.
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 5.1 General Requirements
| The NFs in the 5G system shall support the generation of security related events.
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 5.2 Requirements on events storage
| Security related events data shall be securely stored with confidentiality and integrity protection.
Access to security related events data shall be authorized.
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 5.3 Requirements on configuration for security related events
| The capability to configure the NFs shall be supported.
The Management entity in charge of configuring the NFs shall support configuring the security related events for event detection and for events delivery.
The Management entity in charge of configuring the NFs shall support activating and deactivating the securit... |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 5.4 Requirements on delivery of security related events
| The delivery of security related events shall be protected against unauthorized parties. Mutual authentication shall be supported between the end entities of such a delivery.
The delivery of security related events shall be confidentiality, integrity and replay protected.
The delivery of the security related events s... |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 6 Security related Events
| Editor’s Note: This clause addresses the list and description of the events as well as naming convention for the events.
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 6.1 General
| The security related event consists of two parts: common information elements, and specific information elements. The common information elements are specified in section 6.2, and specific information elements are specified in separated clauses.
6.2 Common information elements
The common information elements for all... |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 6.7 Security events related to SBA parameters configuration
| An NF configuration is received in which related SBA level parameters are changed/updated.
Editor’s Note: This event including its details is for FFS.
|
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 7 Protection of Security related events
| |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 7.1 Protection for the configuration and enabling/disabling detection of security related events
| TLS shall be supported and used to provide mutual authentication, integrity protection, replay protection and confidentiality protection for the interface handling the configuration and the enabling/disabling of events collection.
NOTE 1: If the interface is trusted (e.g. physically protected), it is for the PLMN-ope... |
24c1742a2173dbd2ae075b250ab714cd | 33.502 | 7.2 Protection for the delivery of security related events
| The protection mechanism to provide mutual authentication, integrity protection, replay protection and confidentiality protection is to be implemented at transport layer.
When UDP is used as transport protocol for the delivery of security related events, DTLS shall be supported to provide mutual authentication, integ... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 1 Scope
| The present document focuses on the roaming charging aspects related to the reliability and recoverability enhancement of roaming charging interactions, including Local Breakout roaming and Home Routed roaming.
The following items are studied:
- Identify the roaming charging reliability enhancement scenarios and requ... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 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.
-... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 3 Definitions of terms, symbols and abbreviations
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 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].
|
0fef1d486bbb01c68f1249794e896413 | 32.872 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
N40 Reference point between SMF and the CHF.
N16 Reference point between two SMFs.
N47 Reference point between V-SMF and H-CHF.
N107 Reference point between V-CHF and H-CHF.
N42 Reference point between AMF and the CHF in the same PLMN.
N41 Ref... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 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].
AMF Access and Mobility Management Function
CHF Charging Functi... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 4 Background
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 4.1 General
| 5G roaming charging are specified in middle tier charging specifications. Take data connectivity as an example, the home routed roaming charging, LBO roaming charging with N47 and LBO roaming charging with N107 are specified in 3GPP TS 32.255[2]. The common failure handling includes CTF detected failure, CHF detected f... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 4.2 Home routed Roaming charging
| Figure 4.2-1 illustrates the Home Routed roaming charging architecture depicted in clause 4.2 of 3GPP TS 32.255[2]. The N40 reference point is defined for the interactions between H-SMF and H-CHF and between V-SMF and V-CHF in the reference point representation.
Figure 4.2-1: 5G data connectivity converged charging... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 4.3 Local Breakout Roaming charging
| Figure 4.3-1 illustrates the Local Breakout roaming charging with N47 architecture, as specified in clause 4.2.6 of 3GPP TS 32.255[2]. The N47 reference point is defined for the interactions between V-SMF and H-CHF.
Figure 4.3-1: 5G data connectivity converged charging architecture in Local Breakout V-SMF to H-CHF ... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5 Scenarios and key issues
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1 Topic 1: Local Breakout inter CHFs scenario
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.