hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.5.2 Solution #2.2: Have separate YAML-files for the domains, subsystem, and services level attributes
| Having one common OpenAPI part for the Nchf which then references all the domains, subsystem, and services level YAML-files. Using the current TS 32.291 [8] as an example, it would mean that the current TS32.291_NchfConvergedCharging.yaml it would mean to change from $ref: '#/components/schemas/SMSChargingInformation' ... |
00c451130b9f238c19a047316e4c6866 | 32.801-02 | 5.2.5.3 Solution #2.3: Have separate ASN.1-files for the domains, subsystem, and services level attributes
| Having one common ASN.1 part for the 6G CDR which then references all the domains, subsystem, and services level ASN.1-files. Using the current TS 32.298 [9] as an example, it would mean that the current TS32.298_CHFChargingDataTypes.asn would import SMSChargingInformation from SMSChargingDataTypes {itu-t (0) identifie... |
00c451130b9f238c19a047316e4c6866 | 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
|
4a06dc4229dc25b316c875df092e67bd | 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... |
4a06dc4229dc25b316c875df092e67bd | 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.
-... |
4a06dc4229dc25b316c875df092e67bd | 33.502 | 3 Definitions of terms, symbols and abbreviations
| |
4a06dc4229dc25b316c875df092e67bd | 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.
|
4a06dc4229dc25b316c875df092e67bd | 33.502 | 3.2 Symbols
| Void.
|
4a06dc4229dc25b316c875df092e67bd | 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].
|
4a06dc4229dc25b316c875df092e67bd | 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) which 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 dema... |
4a06dc4229dc25b316c875df092e67bd | 33.502 | 5 Security related events requirements
| |
4a06dc4229dc25b316c875df092e67bd | 33.502 | 5.1 General Requirements
| The NFs in the 5G system shall support the generation of security related events.
|
4a06dc4229dc25b316c875df092e67bd | 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.
|
4a06dc4229dc25b316c875df092e67bd | 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... |
4a06dc4229dc25b316c875df092e67bd | 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... |
4a06dc4229dc25b316c875df092e67bd | 33.502 | 6 Security related Events
| |
4a06dc4229dc25b316c875df092e67bd | 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... |
4a06dc4229dc25b316c875df092e67bd | 33.502 | 6.7 Security events related to SBA parameters configuration
| An NF configuration is received in which related SBA level parameters (e.g., the SBA NF certificate) are changed/updated.
The NF shall detect a reconfiguration event. The event shall be reported to the security related event collection entity as described in clause 4 and clause 5.4.
The event should be delivered to ... |
4a06dc4229dc25b316c875df092e67bd | 33.502 | 6.8 Security events related to Unexpected communication model flow
| Unexpected communication model flows can be detected when an NRF, SCP or an NF Producer receive requests not complying with the specified procedures related to communication models.
Editor’s note: It is for FFS what (additional) events are reported by NF (NRF, SCP or NF producer).
|
4a06dc4229dc25b316c875df092e67bd | 33.502 | 7 Protection of Security related events
| |
4a06dc4229dc25b316c875df092e67bd | 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... |
4a06dc4229dc25b316c875df092e67bd | 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
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.1 Use cases
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.1.1 Use case #1: Failures detected between the CTF and the V-CHF
| In the LBO N40+N107 charging architecture, for a specific PDU session, there is a charging session between the V-SMF(CTF) and V-CHF, and there is also a charging session between the V-CHF and H-CHF. When a failure detected between V-SMF(CTF) and V-CHF, How the charging system handles the failure should be studied.
F... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.1.2 Use case #2: Failures detected between the CTF and the V-CHF
| In the LBO N40+N107 architecture, for a specific PDU session, there is a charging session between the V-SMF(CTF) and V-CHF, and there is also a charging session between the V-CHF and H-CHF. When a failure detected between V-CHF and H-CHF, How the charging system handles the failure should be studied.
Figure 5.1.1.2... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.2 Potential charging requirements
| REQ-3GPPCH-LBIC-1: Charging system shall support failure handling for the Local Breakout charging scenario in which a failure is detected between the CTF and the V-CHF.
REQ-3GPPCH-LBIC-2: charging system shall support failure handling for the Local Breakout charging scenario in which a failure is detected between the ... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.3 Key issues
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.3.1 Key issue #1: Failure handling enhancement for failures detected between the CTF and the V-CHF
| This key issue is for investigating how to support REQ-3GPPCH-LBIC-1. This investigation covers the following:
- Identification of the failure handling enhancement for the scenario in which a failure is detected between the CTF and the V-CHF;
|
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.3.2 Key issue #2: Failure handling enhancement for failures detected between the V-CHF and the H-CHF
| This key issue is for investigating how to support REQ-3GPPCH-LBIC-2. This investigation covers the following:
- Identification of the failure handling enhancement for the scenario in which a failure is detected between the V-CHF and the H-CHF;
|
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.4 Possible solutions
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.4.1 Solution #1.1: Handling of the charging session between V-CHF and H-CHF when V-CHF detected failure of charging session with CTF
| A possible solution for key issue #1 covering requirements REQ-3GPPCH-LBIC-1, enhanced failure handling for scenarios where a failure is detected between the CTF and the V-CHF.
When the V-CHF detects that an expected charging data request for a particular session has not been received within a period of time, the char... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.4.3 Solution #1.3: CTF detected failure
| A possible solution for key issue #1 covering requirements REQ-3GPPCH-LBIC-1, enhanced failure handling for scenarios where a failure is detected between the CTF and the V-CHF. This solution only applicable on application level failure handling.
When the V-CHF is determined not reachable by V-SMF(CTF), V-SMF(CTF) uses... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.4.4 Solution #1.4: V-CHF release the charging session with CTF when V-CHF detected failure of charging session with H-CHF
| A possible solution for key issue #2 covering requirements REQ-3GPPCH-LBIC-2, enhanced failure handling for scenarios where a failure is detected between the V-CHF and the H-CHF.
When the V-CHF, acting as an NF consumer, detects a failure of the H-CHF, it determines how to handle the charging session with the NF (CTF)... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.4.5 Solution #1.5: V-CHF suspend quota management when V-CHF detected failure of charging session with H-CHF
| A possible solution for key issue #2 covering requirements REQ-3GPPCH-LBIC-2, enhanced failure handling for scenarios where a failure is detected between the V-CHF and the H-CHF. This solution only applicable for online charging.
When the V-CHF, acting as an NF consumer, detects a failure of the H-CHF, it determines h... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.4.6 Solution #1.6: Handling of abnormal messages received by H-CHF
| A possible solution for key issue #2 covering requirements REQ-3GPPCH-LBIC-2, enhanced failure handling for scenarios where a failure is detected between the V-CHF and the H-CHF.
When a Charging Data Request [Initial] is received by the H-CHF, which can be associated to an existing charging session, the H-CHF handles ... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.4.7 Solution #1.7: Handling of messages received by H-CHF from alternative V-CHF
| A possible solution for key issue #2 covering requirements REQ-3GPPCH-LBIC-2, enhanced failure handling for scenarios where a failure is detected between the V-CHF and the H-CHF. This solution only applicable for application level failure handling.
When the V-CHF is determined not reachable by V-SMF(CTF), the V-SMF(CT... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.5 Evaluation
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.1.6 Conclusion
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2 Topic 2: Home Routed charging scenario
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.1 Use cases
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.1.1 Use case #1: Failure of one charging session
| In the HR roaming charging architecture, for a specific PDU session, there are two charging sessions simultaneously. When a failure is detected in one of the charging sessions, How the charging system handles the failure should be studied.
Figure 5.2.1.1-1: An example of the failure between H-SMF and H-CHF in HR roa... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.2 Potential charging requirements
| REQ-3GPPCH-LBHR-01: Charging system shall support failure handling for the Home Routed charging scenario in which a failure is detected in one of the charging sessions.
|
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.3 Key issues
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.3.1 Key issue #1: Failure is detected in one of the charging sessions
| This key issue is for investigating how to support REQ-3GPPCH-LBHR-01. This investigation covers the following:
- Whether and how to handle when failure is detected in one of the charging sessions;
|
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.4 Possible solutions
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.4.1 Solution #2.1: Failures detected between the H-CHF and the H-CTF
| A possible solution for key issue #1 covering requirements REQ-3GPPCH-LBHR-1, failure is detected in one of the charging sessions. This solution only applicable for application level failure handling.
When the H-CHF detects that an expected charging data request for a particular session has not been received within a ... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.4.2 Solution #2.2: Failures detected between the V-CHF and the V-CTF
| A possible solution for key issue #1 covering requirements REQ-3GPPCH-LBHR-1, failure is detected in one of the charging sessions. This solution only applicable for application level failure handling.
When the V-CHF detects that an expected charging data request for a particular session has not been received within a ... |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.5 Evaluation
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.2.6 Conclusion
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.3 Topic 3: Local Breakout V-SMF to H-CHF scenario
| |
0fef1d486bbb01c68f1249794e896413 | 32.872 | 5.3.1 Use cases
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.