id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
23.700-48
|
5G System Enhancements for Edge Computing; Phase 2
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-48/23700-48-i00.zip
|
The present document describes key issues and solutions for the phase 2 of the system enhancements for Edge Computing in 5GS.
Edge Computing is supported in 5GS since Rel-15. During Rel-17 FS_enh_EC study described in TR 23.748 [4] , further enhancements for supporting Edge Computing have been studied, including discovery and re-discovery of EAS, edge relocation etc. 4 key issues from FS_enh_EC study have been concluded and progressed in TS 23.548 [3]. Some other issues were raised during the Rel-17 study but not studied due to the time limitation in Rel-17.
This technical report will document the study of potential system enhancements for enhanced edge computing support, including:
- improvements to roaming, to support access to EHE in a VPLMN (WT#1);
- defining use cases that may benefit from exposure of additional data via the Local UPF/NEF including describing (on a high level) the characteristics of the data and data delivery to fulfil the use cases; investigating the solutions and their feasibility and suitability for improved network exposure of UE traffic related information to common Edge Application Server via Local UPF/NEF, such as network congestion status (WT#3);
NOTE 1: XR/media and AI/ML services specific QoS information exposure are to be studied in corresponding study items with considering the same exposure framework as defined by this study.
NOTE 2: This objective will look at the use cases and the data to be exposed but not at the actual UPF exposure mechanism or UPF-originated data, if/when already covered by FS_UPEAS.
- investigating the potential need and solutions for supporting offload policies to match more granular sets of UE(s) without exposing operator-internal configurations to 3rd party AFs (WT#5);
- investigating the potential need and solutions to influence of PSA-UPF and EAS (re)location for collection of UEs, e.g. in scenarios when UE(s) should use the same EAS and are not members of a pre-defined group (WT#6);
- investigating potential impacts related to the GSMA Operator Platform Group work, and potential improvements related with 5GC and EHE being operated by different organizations (WT#7);
- investigating the potential need and solutions to avoid the UE to switch the EC traffic away from the EC PDU Session and 5GS altogether, due to conflicting connectivity preferences in the device (e.g. via means outside of 3GPP connectivity, e.g. non-integrated Wifi) (WT#8);
- investigating the potential solutions for the AF to be able to obtain/determine the DNAI that is associated to a certain selected EAS, for subsequent use with already defined services provided to the AF (WT#9).
|
23.700-55
|
Study on enhanced Application Architecture for UAS applications
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-55/23700-55-i00.zip
|
The present document analyze requirements and identify key issues and develop potential enhancements to the UAS application architecture. The study includes identification of potential enhancements to the UAS architecture, potential enhancements to the Service Enabler Architecture Layer (SEAL) and corresponding application requirements.
The study bases its work on the existing stage 1 work within 3GPP related to UAS as specified in 3GPP TS 22.125 [2].
The conclusions of the study will be aligned with 3GPP TR 23.700-58 [6]. The recommendations from the study include solutions for the UAS architecture and SEAL that will be considered for normative work.
|
23.700-27
|
Study on 5G System with Satellite Backhaul
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-27/23700-27-i00.zip
|
The scope of this Technical Report is to study the following aspects of 5GS with satellite backhaul:
1: Architecture enhancements for support of a backhaul with changing delay (e.g. brought by ISL in satellite networks or changed satellite backhaul on the UP path), and possibly limited bandwidth in case of a gNB with satellite backhaul only (e.g. restricted by the maximum data rate of a satellite beam):
- Policy/QoS control enhancements based on the detected packet delivery latency and/or bandwidth of the satellite backhaul on the UP path;
- Exposure of backhaul information to AFs.
2: Architecture enhancements for support of UPF deployed on GEO satellite with gNB on the ground:
- Whether and how to enable satellite edge computing services via UPF on-board e.g. to reduce the latency for data transmission, and minimize the backhaul resources consumption.
- How to enhance local switch for UEs in a communication when they are served by UPF on-board, e.g. to reduce end to end delay comparing with existing 5G LAN local switch at PSA on the ground.
|
23.700-61
|
Study on Seamless UE context recovery
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-61/23700-61-i00.zip
|
This study will focus on the mechanism to determine the "unavailability period" in the 5G system for the UE.
|
23.700-62
|
Study on UPF enhancement for Exposure And SBA
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-62/23700-62-i00.zip
|
The Technical Report studies on key issue description, solution and conclusion on the support of better integration of UPF into the 5GC SBA. The objectives include:
- Study UPF event exposure service(s) registration/deregistration, and discovery via the NRF.
- Study UPF event exposure service(s) that would support, e.g.:
- Consumption of UPF exposure services by the PCF, NWDAF, CHF, NEF, Trusted AF and other NFs (if needed).
- (To support the UPF exposure service, if needed) Use of SMF services, PCF services, NWDAF services, CHF services, NEF services, Trusted AF services by the UPF.
NOTE 1: This will not define solutions where UPF exposes information that it is not originator of, i.e. not re-expose information owned and exposed by other NFs.
- Relevant Event IDs.
- Evaluate usage of UPF event exposure service(s) as defined in WT#2 also considering the architectural impacts.
NOTE 2: SMF is responsible for controlling UPF packet processing.
NOTE 3: The performance of UP traffic handling shall not be degraded due to mechanisms defined in this study.
NOTE 4: The study shall address generic UPF data exposure mechanisms via SBA based mechanisms, and the coordination with other SIDs for this aspect may be needed in study phase.
This study shall maintain the Rel‑17 backward compatibility on the N3, N6, N9, N4 interfaces.
|
23.700-60
|
Study on XR (Extended Reality) and media services
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-60/23700-60-i00.zip
|
The Technical Report studies key issues, solutions and conclusions on the support of advanced media services, e.g. High Data Rate Low Latency (HDRLL) services, AR/VR/XR services, and tactile/multi-modality communication services. The objectives include:
Enhancements for supporting multi-modality service:
- Study whether and how to enable delivery of related tactile and multi-modal data (e.g. audio, video and haptic data related to a specific time) with an application to the user at a similar time, focusing on the need for policy control enhancements (e.g. QoS policy coordination).
Enhancements of network exposure to support interaction between 5GS and application:
- Study whether and how interaction between AF and 5GS is needed for application synchronization and QoS policy coordination among multiple UEs or between multiple QoS flows per UE.
- Study exposure of 5GS QoS information (e.g. QoS capabilities) and network conditions to the Application to enable quick codec/rate adaptation help to provide desired QoE (e.g. such as assist in alleviating 5GS congestion).
Study whether and how the following QoS and policy enhancements for XR service and media service transmission are performed:
- Study the traffic characteristics of media service enabling improved network resources usage and QoE.
- Enhance QoS framework to support PDU Set granularity (e.g. video/audio frame/tile, Application Data Unit, control information), where a PDU Set consists of PDUs that have the same QoS requirements.
- Support differentiated QoS handling considering different importance of PDU Sets. e.g. eligible drop packets belong to a less important PDU Set to reduce the resource wasting.
- Whether and how to support uplink-downlink transmission coordination to meet RTT (Round-Trip Time) latency requirements between UE and N6 termination point at the UPF.
- Potential policy enhancements to minimize the jitter, focusing on i.e. requirement provisioning from AF, extension of PCC rule.
Study potential enhancements of power management considering traffic pattern of media services:
- Power saving enhancement e.g. support trade-off of throughput/latency/reliability considering device battery life, whether and how to enhance CDRX, considering XR/media traffic pattern.
NOTE: Whether to define a network slice type supporting media services can be determined during normative phase.
|
23.700-68
|
Study on Support of reduced capability NR devices; Phase 2
|
TR
|
18.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-68/23700-68-i10.zip
|
The scope of the present document is to investigate solutions to support of RRC INACTIVE state with extended DRX cycle longer than 10.24s to enrich the power saving function as studied in TR 38.875 [5].
This study will address the following objective:
Support for enabling of eDRX cycle that is longer than 10.24s in RRC_INACTIVE state with following two aspects:
1) Study the support of the eDRX cycle that is longer than 10.24s and up to 10485.76s for RRC_INACTIVE state for RAN paging (e.g. PTW and eDRX cycle values).
2) Study the MT signalling and data handling for UE with long eDRX cycle in RRC_INACTIVE state.
|
23.700-71
|
Study on enhancement to the 5GC LoCation Services (LCS); Phase 3
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-71/23700-71-i00.zip
|
The scope of this Technical Report is to study further enhancements to the to the 5GC LoCation Services including the following aspects:
- Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. support Positioning Signalling via user plane.
- Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. reduction of location service latency, signalling overhead and location estimate exposure.
- Study how the location services can benefit from NWDAF reporting and how the NWDAF use cases can benefit from location services, e.g. enhanced accuracy in certain UE location or population flow statistics data that require UE locations smaller than TA/cell
- Study enhancements to support low power positioning (e.g. for RedCap) including the requirements related to low power high accuracy positioning described in TS 22.104 [7].
- Study necessary enhancement to support regulatory requirement i.e. the network should not notify the UE by any means during the LCS session.
- Study enhancement to support the Flexible and Efficient Periodic and Triggered Location for UE power saving purpose.
- In collaboration with RAN, study specific network functionality related to use of Positioning Reference Units (PRUs) as defined by RAN WGs and study how 5GS to support a specific UE (i.e. Reference UE) to improve the accuracy of positioning, and reduce the signalling:
- Study enhancements to support the location service continuity for UE mobility, i.e. between EPS and 5GS;
- For 5G with satellite access, in collaboration with RAN, study LCS architectural enhancement to support network verified UE location, and to meet location services related requirements defined in TS 22.261 [8].
|
23.700-64
|
Study on enhancements to application layer support for V2X services; Phase 2
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-64/23700-64-i10.zip
|
The present document is a technical report which identifies the enhancements to the application architecture to support V2X services specified in 3GPP TS 23.286 [6] considering advanced V2X services like V2P, ToD, etc and edge computing deployments for V2X services.
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to advanced V2X services and edge computing in 3GPP TS 22.185 [2], 3GPP TS 22.186 [3], 3GPP TS 23.285 [5], 3GPP TS 23.287 [7], 3GPP TS 23.548 [10] and 3GPP TS 23.558 [11].
The study also takes into consideration the V2X application specific services and recommendations specified by automotive industry bodies (5GAA, ETSI ITS and AECC) related to advanced V2X services for VRU, Haptics/ToD and edge deployments for V2X services.
This document will provide recommendations for normative work.
|
23.700-81
|
Study of Enablers for Network Automation for the 5G System (5GS); Phase 3
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-81/23700-81-i00.zip
|
This study focuses on key issue description, solution and evaluation/conclusion on further enhancement for network automation, as documented in TS 23.288 [5], by covering the following objectives:
- Study possible mechanisms for improved correctness of NWDAF analytics;
- Investigate whether and how NWDAF can assist application detection;
- Investigate whether and how to support data and analytics exchange in roaming case;
- Investigate data collection and data storage enhancements (including DCCF and ADRF enhancements, e.g. DCCF relocation, ADRF selection, ML model storage);
- Study whether and how to enhance trained ML Model sharing for different vendors;
- Study whether and how interactions between NWDAF can leverage MDAS/MDAF functionality for data collection and analytics;
- Investigate NWDAF-assisted URSP;
- Study whether and how to enhance the QoS sustainability analytics with finer granularity and additional input data;
- Study whether and how to enhance architecture to support federated learning in the 5GC; and
- Study NWDAF enhancements considering the finer granularity of location information than TA and cell level.
|
23.700-78
|
Study on Application layer support for Personal IoT Network
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-78/23700-78-i10.zip
|
The present document is a technical report capturing the study on application layer support for Personal IoT networks (PIN). The aspects of the study include analyzing application layer architecture requirements of PIN, identifying key issues and supporting PIN application layer functional model. The study also includes information and support from 3GPP network to PIN, service or applications discovery within a PIN or by the UE outside of a PIN via 3GPP network.
The study takes into consideration the work done for PIN in 3GPP TS 23.700-88 [4] and other related work in 3GPP.
|
23.700-76
|
Study on ad hoc group communication support for mission critical services
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-76/23700-76-i00.zip
|
The present document studies solutions to satisfy the requirements identified to support Ad hoc group communication for MCX services. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support Ad hoc group communications. Requirements for this study are taken from 3GPP TS 22.280 [3].
|
23.700-79
|
Study of gateway User Equipment (UE) function for Mission Critical (MC) communications
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-79/23700-79-i00.zip
|
The present document studies solutions to satisfy the requirements for a Gateway UE function. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support mission critical communications. Requirements for this study are taken from stage 1 requirements, including 3GPP TS 22.179 [2] and 3GPP TS 22.280 [3].
|
23.700-89
|
Study on 5G AM Policy
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-89/23700-89-i00.zip
|
The aim of this Technical Report is to study and evaluation of potential enhancements for Access and Mobility Policy Management with the following objective(s):
- To study the mechanisms to provide AM policy control on RFSP Index consistency when UE moves from 5GC to EPC, and define enhancements in R17 mechanism if needed.
|
23.700-85
|
Study on enhancement of 5G User Equipment (UE) policy
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-85/23700-85-i00.zip
|
This study focuses on key issue description, solution and conclusion on the enhancement of 5G UE Policy aspect by covering following objectives:
- URSP rule provisioning and updating procedures for home-routed and LBO roaming scenario, while keeping the existing framework of policy control based on HPLMN.
- Investigate whether and how the network can be made aware when the UE enforces URSP rule and investigate whether and what actions the 5G network can perform.
- Investigate if enhancements are needed for provisioning UE with consistent URSP across 5GC and EPC, and study the mechanism if needed.
- Investigate how to support standardized and operator-specific traffic categories in the traffic descriptor of URSP.
|
23.700-86
|
Study on Architecture Enhancement to support Ranging based services and sidelink positioning
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-86/23700-86-i00.zip
|
The present document is to study 5GC architecture enhancements to enable Ranging-based services and sidelink positioning for commercial, V2X and public safety use cases in in-coverage, partial coverage, and out-of-coverage of 5G network, which include:
- Authorization and policy/parameter provisioning for a UE or a group of UEs;
- Ranging device discovery and service operation procedures between two UEs, between one UE and multiple UEs or via the assistance of another UE;
- Ranging and sidelink positioning service exposure to a UE or an Application Server who has requested the service.
|
23.700-87
|
Study on system architecture enhancement for next generation real time communication
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-87/23700-87-i00.zip
|
The scope of this document is to study IMS architecture enhancements to support new real time communication services based on requirements of e.g. eMMTEL and 5G_MEDIA_MTSI_ext.
The study in this document includes the following aspects:
1) Study the enhancement of IMS architecture and procedures to support Data Channel usage in IMS network, including whether and which functionalities are defined in IMS architecture for Data Channel server, with separate control plane and media plane, and Data Channel application repository, which procedures are needed between Data channel server and IMS AS to support call event notifications.
2) Study whether and how IMS architecture and functions are supported for the requirements from SA WG1 Rel-18 eMMTEL WID impacts:
- to support AR telephony communication.
- to support 3rd party to verify via operator network that the caller is authorized to use or reference specific identity information which can be securely signalled to the callee when placing a call.
3) Study whether and which IMS media control interfaces can be potentially applied for service based architecture, supporting both existing capabilities and new capabilities for possible new applications and efficient media processing.
|
23.700-74
|
Study on generic group management, exposure and communication enhancements
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-74/23700-74-i00.zip
|
The scope of this Technical Report is to study potential enhancements on generic group management, exposure and communication. Specifically, the following aspects are in the scope of the study:
- Enhance group attribute management and group status event reporting:
- set/modify the group attributes: provisioning of service area or QoS applicable to each UE of a given group;
- subscribe to group status event reporting for the event "newly registered or (de)-registered group member".
- Study whether and how to enhance NEF exposure framework to enable capability exposure for provisioning of traffic characteristics and monitoring of performance characteristics applicable to each UE of a given group.
- Support group communication for a 5G VN, which supports multiple SMFs, including support of SMF redundancy for reliability of the 5G VN group communication.
- Whether additional mechanism or enhancement is needed and how to support group communication allowing UE to simultaneously send data to different groups, where each group has a different QoS policy (requirement regarding 5SEI as indicated in clause 6.13.2 of TS 22.261 [6]).
|
23.700-88
|
Study on architecture enhancements for Personal IoT Network (PIN)
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-88/23700-88-i00.zip
|
The scope of this Technical Report is to study the enhancement of 5G System to support Personal IoT Network (PIN). The study addresses the service requirements documented in TS 22.261 [5] for the Personal IoT Networks. The following aspects needs to be studied:
- Architecture enhancement:
- To study the potential architectural enhancements for supporting management of PIN, access of PIN via PIN Element with Gateway Capability (PEGC), and communication of PIN (e.g. PIN Element communicates with other PIN Elements directly or via PEGC or via PEGC and 5GS).
- To study the potential architecture enhancements for supporting identifying PIN and the PIN Elements.
- Security related:
NOTE: The study may need cooperation with SA3. If solutions are related to security impact, they will be studied in SA WG3.
- To study how to identify PIN and the PIN Elements in the PIN at 5GC level to serve for authentication/authorization.
- Management as well as policy and routing control enforcement:
- To study the management of a PIN.
- To study the procedures for PIN discovery, PIN Element discovery.
|
23.700-90
|
Study on interconnection and migration aspects for railways
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-90/23700-90-i00.zip
|
The present document studies solutions to satisfy interconnection and migration needs for railways. It identifies enhancements to be included in the technical specifications for MCPTT (3GPP TS 23.379 [2]), MCVideo (3GPP TS 23.281 [3]), MCData (3GPP TS 23.282 [4]) and in the common functional architecture (3GPP TS 23.280 [5]) to support mission critical communications.
|
23.700-95
|
Study on application enablement aspects for subscriber-aware northbound API access
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-95/23700-95-i10.zip
|
The present document studies the potential enhancements in CAPIF and application enablement frameworks (e.g. SEAL, EDGEAPP, vertical enabler layers) to support the subscriber-aware northbound API access (SNA), whose requirements are specified in TS 22.261 [2].
This study takes into consideration the existing works for CAPIF (3GPP TS 23.222 [3]), SEAL (3GPP TS 23.434 [4]), and EDGEAPP (3GPP TS 23.558 [5]).
Any potential enhancements to security procedures related to CAPIF and application enablement frameworks (e.g. EDGEAPP, SEAL, vertical enabler layers) to support SNA are not in the scope of this study.
|
23.700-96
|
Study on 5G-enabled fused location service capability
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-96/23700-96-i00.zip
|
The present document studies and evaluates the application architecture aspects and solutions to address potential new and enhanced location capabilities for vertical application enabler, including the following aspects:
- Enabling location performance (accuracy, availability and latency) enhancements through combined use and fusion of 3GPP and non-3GPP location technologies at the application layer;
- Identification and classification of location related requirements (including location QoS) for vertical application services;
- Architecture enhancement leveraging 5G positioning and location services;
- Enabling location sources and positioning methods selection based on the requested location QoS;
- Initialization and configuration for fused location service;
- Enabling value-added location service capabilities exposure to vertical applications;
- Enhancements on SEAL location management addressing the aspects above.
NOTE: This study will not duplicate solutions already available in Core Network and RAN.
|
23.700-97
|
Study on Application Capability Exposure for IoT Platforms
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-97/23700-97-i10.zip
|
The present document is a technical report which identifies SEAL functionality to support application capability exposure to general purpose servers or 3rd party IoT applications via IoT Platforms. Key issues and corresponding solutions necessary to ensure efficient use and deployment of IoT Platforms in the 5G network are included.
The study takes into consideration the existing work for Core Network exposure in 3GPP TS 23.502 [2] and provides recommendations for normative work.
|
23.700-98
|
Study on enhanced Architecture for enabling Edge Applications
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-98/23700-98-i10.zip
|
The present document is a technical report capturing the study on enhanced architecture for enabling edge applications over 3GPP networks. The study bases the enhancements on the work done in 3GPP TS 23.558 [2] and takes into consideration other related work done within and outside 3GPP i.e. ETSI MEC [3] and GSMA OP [4].
The aspects of the study include identifying new key issues, architecture requirements, related architecture enhancements and solutions, cardinality rules, deployment options, and involved entities and relationships to enhance the Rel-17 architecture for enabling edge applications.
|
23.700-99
|
Study on Network Slice Capability Exposure for Application Layer Enablement
|
TR
|
18.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-99/23700-99-i20.zip
|
The study identifies the SA1 requirements and potential vertical requirements of network slice capability exposure that have yet to be realized, and proposes application architecture aspects solutions and enhancements to SEAL. Based on any gaps found between requirements and existing capabilities, the present document includes: identification of key issues, solutions, corresponding evaluations and conclusions to ensure the efficient network slice capability exposure.
The study takes into consideration the SEAL architecture specified in 3GPP TS 23.434 [2], network slicing related architecture and services(such as services of NEF) specified in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4], network slicing management capability provisioning and architecture specified in 3GPP TS 28.531 [5] and 3GPP TS 28.533 [6], requirements specified in TS 22.261 [7].
|
23.783
|
Study on Mission Critical services support over 5G System
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.783/23783-i00.zip
|
The present document analyses how to ensure that the set of Mission Critical services is supported over the 5GS. Key issues are derived and solutions are developed for the impacts on existing or new Stage 2 Mission Critical specifications.
|
23.700-80
|
Study on 5G system support for AI/ML-based services
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-80/23700-80-i00.zip
|
This Technical Report will study, based on requirements as specified in clauses 6.40 and 7.10 of TS 22.261 [2], 5GS assistance to support Artificial Intelligence (AI) / Machine Learning (ML) model distribution, transfer, training for various applications, e.g. video/speech recognition, robot control, automotive, etc.
The scope of this study is on how the AI/ML service providers could leverage 5GS as the platform to provide the intelligent transmission support for application layer AI/ML operation based on the following objectives.
1. Study the possible architectural and functional extensions to support the Application layer AI/ML operations defined in TS 22.261 [2], more specifically:
a. Support monitoring of network resource utilization in the 5G system relevant to the UE in order to support Application AI/ML operation.
b. Whether and how to extend 5GS information exposure for 5GC NF(s) to expose UE and/or network conditions and performance prediction (e.g. location, QoS, load, congestion, etc.) to the UE and/or to the authorized 3rd party to assist the Application AI/ML operation.
c. Enhancements of external parameter provisioning to 5GC (e.g. expected UE activity behaviours, expected UE mobility, etc.) based on Application AI/ML operation.
d. Investigate the enhancements of other 5GC features that could be used to assist the Application AI/ML operations as described in clause 6.40 of TS 22.261 [2].
2. Study possible QoS, Policy enhancements to support Application AI/ML operational traffic while supporting regular (non Application-AI/ML) 5GS user traffic.
3. Study whether and how 5GS provides assistance to AF and the UE for the AF and UE to manage the Federated Learning (FL) operation and model distribution/redistribution (i.e. FL members selection, group performance monitoring, adequate network resources allocation and guarantee) to facilitate collaborative Application AI/ML based Federated Learning operation between the application clients running on the UEs and the Application Servers.
|
25.101
|
User Equipment (UE) radio transmission and reception (FDD)
|
TS
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.101/25101-i00.zip
|
The present document establishes the minimum RF characteristics of the FDD mode of UTRA for the User Equipment (UE).
|
25.102
|
User Equipment (UE) radio transmission and reception (TDD)
|
TS
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.102/25102-i00.zip
|
This document establishes the minimum RF characteristics of all three options of the TDD mode of UTRA. The three options are the 3.84 Mcps, 1.28 Mcps and 7.68 Mcps options respectively. The requirements are listed in different subsections only if the parameters deviate.
|
25.123
|
Requirements for support of radio resource management (TDD)
|
TS
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.123/25123-i00.zip
|
This Technical Specification specifies requirements for support of Radio Resource Management for TDD. These requirements include requirements on measurements in UTRAN and the UE as well as requirements on node dynamic behaviour and interaction, in terms of delay and response characteristics.
|
25.133
|
Requirements for support of radio resource management (FDD)
|
TS
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.133/25133-i00.zip
|
The present document specifies requirements for support of Radio Resource Management for FDD. These requirements include requirements on measurements in UTRAN and the UE as well as requirements on node dynamical behaviour and interaction, in terms of delay and response characteristics.
|
25.331
|
Radio Resource Control (RRC); Protocol specification
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.331/25331-i00.zip
|
The present document specifies the Radio Resource Control protocol for the UE-UTRAN radio interface.
The scope of the present document also includes:
- the information to be transported in a transparent container between source RNC and target RNC in connection with SRNC relocation;
- the information to be transported in a transparent container between a target RNC and another system.
|
25.423
|
UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling
|
TS
|
18.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.423/25423-i00.zip
|
The present document specifies the radio network layer signalling procedures of the control plane between RNCs in UTRAN, between RNC in UTRAN and BSS in GERAN Iu mode and between BSSs in GERAN Iu mode.
|
25.433
|
UTRAN Iub interface Node B Application Part (NBAP) signalling
|
TS
|
18.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.433/25433-i00.zip
|
The present document specifies the radio network layer signalling protocol called Node B Application Part (NBAP) specification to be used for Control Plane over Iub Interface.
|
26.251
|
Codec for Immersive Voice and Audio Services (IVAS); C code (fixed-point)
|
TS
|
1.0.2
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.251/26251-102.zip
|
Attached to this document is an electronic copy of the fixed-point C code for the Immersive Voice and Audio Services (IVAS) Codec. This C code is the unique alternative reference specification besides the floating-point C code for the IVAS Codec (3GPP TS 26.258) for a standard compliant implementation of the IVAS Codec (3GPP TS 26.253), Rendering (3GPP TS 26.254), Error Concealment of Lost Packets (3GPP TS 26.255) and Jitter Buffer Management (JBM) (3GPP TS 26.256).
The bit-exact fixed-point C code is the preferred implementation for all applications, but the floating-point codec as specified in 3GPP TS 26.258 may be used instead of the fixed-point codec when the implementation platform is better suited for a floating-point implementation.
Requirements for any implementation of the IVAS codec to be standard compliant are specified in 3GPP TS 26.252 (Test sequences).
|
26.806
|
Study on Tethering AR Glasses – Architectures, QoS and Media Aspects
|
TR
|
18.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.806/26806-i00.zip
|
The present document addresses architectures, QoS and media handling aspects of when tethering AR Glasses to 5G UEs based on initial discussions in TR 26.998 [2]. In particular, the following aspects are in scope:
- Definition of different tethering architectures for AR Glasses including 5G sidelink and non-5G access based on existing 5G System functionalities
- Documentation of the relationship between AR Glasses tethering and AR glasses considered as PIN (Personal IoT Network) elements according to TR 22.859 [3] and the derived service requirements in TS 22.261 [4].
- Documentation of end-to-end call flows for session setup and handling
- Identification media handling aspects of different tethering architectures
- Identification of end-to-end QoS-handling for different tethering architectures and define supporting mechanisms to compensate for the non-5G link between the UE and the AR glasses
- Providing recommendations for suitable architectures to meet typical AR requirements such as low power consumption, low latency, high bitrates, security and reliability.
- Collaboration with relevant other 3GPP groups on this matter
- Identification of potential follow-up work on this matter
|
26.857
|
5G Media Service Enablers
|
TR
|
18.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.857/26857-i00.zip
|
The present document introduces and defines the concept of Media Service Enablers which includes among others:
- Definition of the principal properties of Media Service Enablers.
- Definition of minimum and typical functionalities of Media Service Enablers.
- Definition of a specification template for Media Service Enablers.
- Identification of possibly relevant stage-2 and stage-3 work for Media Service Enablers.
- Collection of a set of initially relevant Media Service Enablers for normative work.
|
26.865
|
Immersive Audio for Split Rendering Scenarios; Requirements
|
TR
|
18.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.865/26865-i00.zip
|
The present document identifies relevant guidelines and IVAS [2] related requirements associated with split rendering scenarios for immersive audio. It covers:
- Design guidelines/constraints related to complexity and memory as well as constraints related to relevant interfaces between presentation engine and End Device such as bit rate, latency, down- and upstream traffic characteristics.
- Design guidelines/constraints related to functional capability requirements such as rendering of non-diegetic sounds, 3DoF rendering of diegetic immersive sounds.
- Performance guidelines/requirements.
|
26.812
|
QoE metrics for AR/MR services
|
TR
|
18.1.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.812/26812-i10.zip
|
This document addresses information collection and QoE metrics definition aspects when the XR (e.g. AR/MR) devices are based on the architecture defined in MeCAR WI. The following details are in scope:
- Collect relevant external information on QoE Metrics for AR and XR services, for example taking into account information in ITU-T, MPEG or other groups dealing with quality measurements, include device related QoE metrics, network transmission related QoE metrics, content handling related QoE metrics, and other immersiveness/presence related QoE metrics.
- Documentation of subjective tests results on XR QoE metrics, if considered relevant.
- Identification of relevant XR QoE Metrics and their impacts on the user experience.
- Identification of relevant observation points and define the measurement and derivation of relevant XR QoE metrics in the device architecture based on MeCAR WI.
- Collaboration with relevant groups or specifications on NWDAF, RRC-based metrics configuration and collection.
- Provide recommendation on normative work for new XR QoE metrics based on the findings in this study.
|
26.955
|
5G Video Codec Characteristics
|
TR
|
18.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.955/26955-i00.zip
|
The present technical report documents relevant interoperability requirements, performance characteristics and implementation constraints of video codecs in 5G services, and characterizes video codecs, in particular 3GPP defined codecs H.264/AVC and H.265/HEVC in order to have a benchmark for the addition of potential future video codecs. For this purpose, the document:
- Collects a summary of the video coding capabilities in 3GPP services.
- Collects a subset of relevant scenarios for video codecs in 5G-based services and applications, including video formats (resolution, frame rates, colour space, etc.), encoding and decoding requirements, adaptive streaming requirements.
- Collects relevant and exemplary test conditions and material for such scenarios, including test sequences.
- Defines performance metrics for such scenarios with focus on objective performance metrics.
- Collects relevant interoperability functionalities and enabling elements for video codecs in different 5G services such as MTSI and Telepresence (i.e. RTP based conversational communications), or 5G media streaming (e.g. based on DASH/CMAF) supporting the identified scenarios.
- Collects relevant criteria and key performance indicators for the integration of video codecs in 5G processing platforms, taking into account factors such as encoding and decoding complexity in the context of the defined scenarios.
- Provides anchors for the existing codecs H.264/AVC and H.265/HEVC in the context of the above scenarios and document the findings in a consistent manner and characterizes H.265/HEVC against H.264/AVC
- Provides initial information on EVC video codec developed in ISO/IEC SC29 WG 4 and H.266/VVC video codec developed in JVET (ITU-T SG16 Q6 and ISO/IEC SC29 WG 5) in the context of the above scenarios, including test streams and characterization results.
- Provides initial information AV1 video codec developed by the Alliance for Open Media in the context of the above scenarios, including test streams and characterization results.
|
28.204
|
Charging management; Network slice-specific authentication and authorization charging in the 5G System (5GS)
|
TS
|
18.1.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.204/28204-i11.zip
|
The present document specifies the Converged Charging description for network slice-specific authentication and authorization charging in the 5G System (5GS) based on Network Slice-Specific Authentication and Authorization Function (NSSAAF) of 5GS architecture and procedures specified in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4].
The scope is the Network Slice-Specific Authentication and Authorization as specified in TS 23.502 [4] with a AAA Server (AAA-S).
|
28.203
|
Charging management; Network slice admission control charging in the 5G System (5GS)
|
TS
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.203/28203-i10.zip
|
The present document specifies the Converged Charging description for Network Slice Admission Control charging in the 5G System (5GS), based on Network Slice Admission Control Function (NSACF) of 5GS architecture and procedures specified in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4].
The charging aspect of Network Slice Admission Control charging is based on charging principles specified in 3GPP TS 32.240 [2].
The following functionalities of Network Slice Admission Control are within the scope:
- number of registered UEs per network slice;
- number of PDU Sessions per network slice.
|
26.997
|
Codec for Immersive Voice and Audio Services (IVAS); Performance characterization
|
TR
|
18.1.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.997/26997-i10.zip
|
The present document provides information on the Immersive Voice and Audio Services (IVAS) codec Selection Phase which was run using the floating point (3GPP TS 26.258). Experimental test results from the subjective quality testing are reported to illustrate the behaviour of the IVAS codec. Additional information is provided on implementation complexity of the IVAS codec and objective test results.
|
28.819
|
Study on continuous integration continuous delivery support for 3GPP NFs
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.819/28819-i00.zip
|
The present document studies key issues in automating CI-CD based testing of 3GPP NFs after delivery to the operator's operation environment. The present document describes the support the 3GPP system provides for CI-CD and other testing such as:
1) Support for operational and simulation testing
2) Information relating to NFs required for testing
3) Feedback on the new NF's performance
|
28.826
|
Study on Nchf charging services phase 2 improvements and optimizations
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.826/28826-i10.zip
|
The present document studies the potential use cases, requirements, and solutions for the enhancements of the Nchf converge charging service.
The study will cover and identify gaps for:
- optimizations regarding amount of information in the request and number of requests;
- enhancement of input to rating;
- cancelling of chargeable events for unsuccessful scenarios;
- enhancement of non-blocking mechanism;
- enhancements of triggers having more consistent triggers and use of NF specific triggers.
Improvements on how to maintain the source code presentations (yaml and ASN.1) the document structure for these will be studied,
|
28.827
|
Study on 5G charging for additional roaming scenarios and actors
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.827/28827-i00.zip
|
The present document studies the potential use cases, requirements, and solutions for the 5G charging for additional roaming scenarios and actors, in regards to roaming local break out and home routed and taking the requirements brought by adoption of GSMA BCE (Billing Charging Evolution), as a replacement for TAP.
The study will cover and identify gaps for:
- charging in the visited MNO network for the purpose of wholesale charging towards the home MNO
- capabilities for reconciliation of wholesale charging reports from the visited MNO network with MNO home network information
- charging in the visited MNO network and convey it to the home MNO network for the purpose of retail charging
- charging in the MNO’s network for the purpose of wholesale charging towards an additional charging model actor e.g. MVNO
- charging in the visited MNO network and convey it to the home MNO’s network for the purpose of home MNO wholesale charging towards an additional charging model actor e.g. MVNO
- charging in the visited MNO network and convey it to an MVNO hosted by a home MNO for the purpose of retail charging
|
28.828
|
Study on charging aspects for enhanced support of non-public networks
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.828/28828-i00.zip
|
The present document studies the charging aspects for enhanced support of non-public networks on the TS 23.501 [2], TS 23.502 [3], TS 23.503 [4], TS 23.228 [5] and TS 23.167 [6] incorporating conclusions from TR 23.734 [7] and TR 23.700-07 [8].
The following is studied:
- Charging scenarios and potential charging requirements for Non-Public Networks (i.e. Stand-alone Non-Public Network (SNPN) or Public Network Integrated NPN (PNI-NPN)).
- Possible charging solutions for Non-Public Networks with potential impact on charging architecture, charging functions and charging procedures.
- End user charging and Inter-Provider charging by considering the different business roles.
|
28.829
|
Study on network and service operations for energy utilities
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.829/28829-i01.zip
|
The present document considers service requirements introduced by the SEI work item related to telecom management [2] and [3]. This feasibility study identifies use cases and requirements for exposing capabilities of the 3GPP management system to external energy utility service providers. The study further considers how management capabilities or what information can be provided to MNOs by the external energy utility service providers. The study will consider both energy utility use cases and requirements. The study of FS_NSCE [4] can be considered for the technical investigation.
|
28.831
|
Study on basic Service-Based Management Architecture (SBMA) enabler enhancements
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.831/28831-i00.zip
|
The present document …
|
28.832
|
Study on management aspects of Ultra-Reliable and Low Latency Communications (URLLC)
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.832/28832-i01.zip
|
The present document investigates the potential requirements related to management of the URLLC features defined in RAN side. It documents key issues related to configuration management of URLLC features and to the performance measurements for URLLC service. It provides potential solutions and recommendations for the normative work.
|
28.833
|
Study on management aspects of 5GLAN
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.833/28833-i01.zip
|
The present document studies the potential use cases, requirements, and enhancements for the management (e.g. performance measurement and related new KPIs regarding VN group communication) to support 5G-LAN capabilities defined by TS 23.501 [2]. The present document provides conclusions and recommendations on standardization phase.
|
28.834
|
Study on management of cloud-native Virtualized Network Functions (VNF)
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.834/28834-i01.zip
|
The present document studies potential use cases, requirements and solutions for the management of cloud-native virtualized network function and the impacts on the 3GPP management system. The present document provides conclusions and recommendations on the next steps in the standardization.
|
28.830
|
Study on Fault Supervision Evolution
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.830/28830-i10.zip
|
The present document investigates potential use cases, requirements and solutions for the fault supervision evolution, its relation with performance management and fault supervision, relation and interaction with MDAS and COSLA, and potential enhancements for MDA assisted fault management. The present document provides conclusions and recommendations on the normative work.
|
28.836
|
Study on intent-driven management for network slicing
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.836/28836-i00.zip
|
The present document specifies potential use cases, requirements, and solutions for intent driven management for network slicing. The document provides conclusions and recommendations on the next steps in the standardization.
|
28.837
|
Study on management of trace/ Minimization of Drive Tests (MDT) phase 2
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.837/28837-i00.zip
|
The present document studies potential enhancements for the management of Trace/MDT based on the existing 5G data collection job "TraceJob" specified in TS 28.621 (stage 1) [2], TS 28.622 (stage 2) [3], TS 28.623 (stage 3) [4] and the Trace/MDT management framework specified in TS 32.421 (stage 1) [5], TS 32.422 (stage 2) [6] and TS 32.423 (stage 3) [7]. The document provides conclusions and recommendations on the next steps in the standardization.
|
28.838
|
Study on measurement data collection to support RAN intelligence
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.838/28838-i00.zip
|
The present document contains the concept, use cases, requirements, and potential solutions for collecting the measurement data to support AI/ML enabled RAN with the AI/ML functions residing in OAM.
|
28.835
|
Study on management aspects of 5G Multiple Operator Core Network (MOCN) network sharing phase 2
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.835/28835-i01.zip
|
The present document studies on potential requirements, impact on interaction between MOP and POP/NEP, and management architecture and more potential performance measurements of 5G MOCN network sharing.
|
28.839
|
Study on charging aspects for time sensitive networking
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.839/28839-i10.zip
|
The present document studies the charging aspects for the support of Time Sensitive Networking based on requirements from TS 22.261 [2] and TS 22.104 [7] of 5G system and vertical domains, the architecture, functional and protocol to enable Time Sensitive Communication and Time Synchronization, described in TS 23.501 [3], TS 23.502 [4], TS 23.503 [5], TR 23.734 [6] and TS 24.519 [8].
The following are studied:
- possible charging scenarios and requirements for 5G System integration as a bridge in TSN network;
- possible charging scenarios and requirements for the Time Sensitive Communications and Time Synchronization service;
- possible new charging aspects for the following key items:
- QoS requirements for TSN (e.g. support for TSC QoS Flows, QoS mapping from TSN QoS information to 5GS QoS profile);
- Edge computing scenario support in TSN Transport (e.g. DS-TT and NW-TT);
- charging enhancement (e.g. new triggers) due to policy control for TSN traffic which may impact the charging;
- potential charging solutions for the above charging scenarios and requirements and taking in account TSN application requirements (e.g. instance survival time).
|
28.841
|
Study on management aspects of Internet of Things (IoT) Non-Terrestrial Networks (NTN) enhancements
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.841/28841-i01.zip
|
The present document studies on management aspects of IoT NTN enhancements. It investigates specific IoT NTN related parameters which should be considered by O&M, investigates NRM enhancement, performance measurement and related new KPIs of IoT NTN. It studies the key issues associated with service and network management of IoT NTN enhancements (whether as NG-RAN or E-UTRAN) and potential solutions, and provides recommendations for the further normative work.
|
28.842
|
Study on data management phase 2
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.842/28842-i10.zip
|
The present document studies potential enhancements related to management of management data, specifically enhancing mechanisms for discovery and reporting of management data, retrieval of stored management data, and managing external management data.
|
28.840
|
Study on CHF segmentation
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.840/28840-i10.zip
|
The present document studies the CHF discovery and selection in order to support the discovery of a CHF by the NF consumers like SMF, AMF, SMSF and PCF based on information about network segments that the CHF belongs to.
The following are studied:
- possible charging scenarios and requirements which makes use of CHF Segmentation.
- potential charging solutions which make use of CHF Segmentation.
|
28.843
|
Study on structure of charging for verticals
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.843/28843-i10.zip
|
The present document studies the charging aspects to better support vertical scenarios, which is different with the existing customer charging baseline, specified in TS 32.240 [2], and makes the evolution of charging specifications clearer, which focuses on studying the charging principles and references of verticals charging, and aims to provides an guideline for other charging management TSs that specify the verticals charging.
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [1].
|
28.844
|
Study on charging aspects of satellite in the 5G System (5GS)
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.844/28844-i00.zip
|
The present document studies on charging aspects of satellite in 5GS based on the TS 23.501 [2] and TS 23.502 [3]:
This study item is to investigate the following aspects of the satellite access:
- Possible business scenarios;
- Possible charging scenarios and potential charging requirements;
- Identify the potential charging solutions.
This study item is to investigate the following aspects of the satellite backhaul:
- Possible business scenarios;
- Possible charging scenarios and potential charging requirements, e.g. related to PCC/QoS control enhancement;
- Identify the potential charging solutions.
|
28.863
|
Study on Key Quality Indicators (KQIs) for 5G service experience
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.863/28863-i00.zip
|
The present document investigates the definition and scenarios for KQI. The KQIs and the evaluation of the KQIs for each of the identified scenarios will be investigated. It also provides the analysis for the relation of KQI with the SLS requirements.
|
28.845
|
Study on charging aspects of ranging based services and sidelink positioning
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.845/28845-i00.zip
|
The present document studies the charging aspects for Ranging based services and Sidelink Positioning
The following are in the scope:
• Identify the business roles of the Ranging based services and Sidelink Positioning;
• Identify the potential charging scenarios and requirements of the Ranging based services and Sidelink Positioning;
• Identify the potential charging solutions for the Ranging based services and Sidelink Positioning.
|
28.824
|
Study on network slice management capability exposure
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.824/28824-i01.zip
|
The present document describes use cases, potential requirements and solutions for exposure of management services to external network slice consumers, e.g. verticals and service providers. The present document provides conclusions and recommendations on the next steps for the standardization.
|
28.864
|
Study on Enhancement of the management aspects related to NetWork Data Analytics Functions (NWDAF)
|
TR
|
18.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.864/28864-i01.zip
|
The present document studies the management enhancement for NWDAF (Network Data Analytics Function).
In the present document, with regarding to the analytic, data management and trained ML model provisioning services provided by the NWDAF, also considering different NWDAF deployment scenarios, some fundamental key issues related the management enhancement for NWDAF are discussed. And the corresponding potential solutions are provided and evaluated.
The present document also provides recommendations for the normative specifications work.
|
28.865
|
Study on Deterministic Communication Service Assurance (DCSA)
|
TR
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.865/28865-i10.zip
|
The present document studies potential key issues and solutions for provisioning and assurance of deterministic communication services, e.g. management of related network functions, potential new service requirements and new performance measurements, etc. The present document provides conclusions and recommendations on the normative work.
|
29.002
|
Mobile Application Part (MAP) specification
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.002/29002-i00.zip
|
It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified by CCITT is used to transfer this information.
The present document describes the requirements for the signalling system and the procedures needed at the application level in order to fulfil these signalling needs.
Clauses 1 to 6 are related to general aspects such as terminology, mobile network configuration and other protocols required by MAP.
MAP consists of a set of MAP services that are provided to MAP service-users by a MAP service-provider.
Figure 1.1/1: Modelling principles
Clauses 7 to 13A of the present document describe the MAP services.
Clauses 14 to 17 define the MAP protocol specification and the behaviour of service provider (protocol elements to be used to provide MAP services, mapping on to TC service primitives, abstract syntaxes, etc.).
Clauses 18 to 25 describe the MAP user procedures that make use of MAP services.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
|
29.831
|
Study on NRF API enhancements to avoid signalling and storing of redundant data
|
TR
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.831/29831-i00.zip
|
The present document identifies deficiencies of the NRF APIs as specified in 3GPP TS 29.510 [2] and studies potential optimization solutions. The document will focus on the following aspects:
-avoid data storage overhead in the NRF due to many NFs (especially NFs from the same NF set) registering with identical information,
-avoid signalling overhead (both in terms of payload size and number of HTTP requests) due to discovery responses containing lots of duplicate information and due to the number of data change notification sent when duplicated data are changed one by one.
-avoid processing overhead (both at NRF and its consumers) resulting e.g. from signalling overhead.
|
29.893
|
Study on IETF QUIC Transport for 5GC Service Based Interfaces
|
TR
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.893/29893-i00.zip
|
The present document analyses the IETF QUIC protocol and its potential use as a transport protocol for the 5GC Service Based Interfaces.
This technical report provides an analysis of the following aspects:
- Features of transport protocol required for 5GC SBI;
- Features of QUIC applicable to 5GC SBI;
- Comparison of the applicable features of QUIC against TCP for the 5GC SBI;
- Key requirements for 5GC SBI in order to support QUIC as a transport protocol;
- Solutions for supporting the key requirements;
- Impacts to 5GC Service Based Interfaces due to introduction of QUIC.
|
31.822
|
Study on GBA_U Based APIs
|
TR
|
18.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.822/31822-i10.zip
|
The present document studies the GBA_U based APIs.
|
31.826
|
Study on new UICC application for NSSA
|
TR
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.826/31826-i00.zip
|
The aim of this Technical Report is to study the aspects for any potential enhancements on the UICC to be developed by CT6 based on the outcome of 3GPP TS 33.501. This work does not include selecting or standardizing any specific EAP method or associated EAP credential types for NSSAA.
For each of the objectives in the scope of the CT6 study, the UICC aspects that are to be covered in this study are as follows:
- Enhancements to support network slice-specific authentication and authorization using the UICC
- Study potential solutions for slice-specific authentication using new specific UICC application
- Study information the UICC application for NSSAA needs to contain
- Study information needed by the ME to select the correct UICC application used for NSSAA, in the case where multiple such UICC applications are available on the UICC. This information will not include UICC application selection based on a specific EAP method or type of EAP credentials.
- Study the interface that the new UICC application should feature in order to support NSSAA
Note: The study item in CT6 will not cover any security-related aspects within SA3's remit.
|
32.282
|
Charging management; Time-Sensitive Networking (TSN) charging
|
TS
|
18.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.282/32282-i20.zip
|
The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240 [1].
The present document specifies the converged charging description for the time sensitive networking domain based on the functional stage 2 description in TS 23.501 [11], TS 23.502 [12] and TS 23.503 [13].
This charging description includes the converged charging architecture, principles, requirements and scenarios specific to the time sensitive networking, with focus on the following charging scenarios: .
- the TSN 5GS bridge configuration and management charging.
- the enabler for time sensitive communication and time synchronization charging.
- the time sensitive communication traffic charging.
It further specifies the structure and content of the CDRs and the charging events for converged charging.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [8]. Those that are common across charging management in 3GPP networks/domains, services or subsystems are provided in the umbrella TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
|
32.847
|
Study on Charging Aspects for Network Slicing Phase 2
|
TR
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.847/32847-i00.zip
|
The present document continues the study on charging aspects of network slicing covered by TR 32.845 [2] but no longer limited to charging data collection functionalities without quota management as specified for Network Slice management charging in TS 28.202 [3] and for Network slice performance and analytics charging in 3GPP TS 28.201 [4].
The following is studied:
- Network slice converged charging for Network Slices enabled over 3GPP 5GS;
- Correlation aspects between Network Slice charging and the end user charging accessing the Network Slice;
- Inter-Provider (B2B) charging aspects by considering the different Organizations (e.g. MNO, Verticals).
The Converged Charging service aspects associated to the TR 23.700-40 [5] conclusion on network slice information is also considered.
|
33.700-28
|
Study on security aspects of satellite access
|
TR
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.700-28/33700-28-i00.zip
|
The present document investigates the security and privacy aspects of satellite access/NTN. The study is based on the architectural and functional requirements on integration of satellite components in the 5GS/EPS architecture, so as to ensure that the proposed solutions address the security and privacy implications on the architecture enhancements agreed in TR 23.700-28 [x]. Specifically, it covers the following:
- The identified security and privacy issues, threats, and potential requirements for protecting the UE in the enhanced 5GS/EPS architecture supporting discontinuous coverage with satellite access;
- The potential solutions addressing the identified security and privacy issues as above.
|
33.737
|
Study on Authentication and Key Management for Applications (AKMA) phase 2
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.737/33737-i10.zip
|
The present document studies key issues and potential solutions to support roaming aspects and the Authentication Proxy in AKMA, which is specified in TS 33.535 [2]. Specifically, the present document:
- Investigates AKMA roaming architecture and requirements by taking regulatory compliance into account;
- Studies the architecture impact and procedures of introducing the Authentication Proxy (similar as the AP specified in GBA) into AKMA.
|
33.738
|
Study on security aspects of enablers for network automation for the 5G system phase 3
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.738/33738-i10.zip
|
The present document studies the security aspects of enablers for network automation for the 5G system based on the outcome of TR 23.700-81 [6]. More specifically, the present document will identify security issues and requirements and provide corresponding security solutions related to the following scenarios:
- Security aspects of potential architecture enhancement: roaming, supporting federated learning, interaction between NWDAF and MDAS/MDAF, etc.
- Handling of sensitive information inherent to application detection, roaming and location information.
- KIs from R17 which do not have enough time to proceed, e.g. NWDAF detection related issues.
- Any further security enhancements which need to be studied based upon the ongoing SA2 eNA Phase 3 work
|
33.739
|
Study on security enhancement of support for edge computing phase 2
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.739/33739-i10.zip
|
The present document studies the security aspects related to the new features and procedures resulting from the continuation of the work on Edge Computing support in 5G Systems, i.e. 5G System Enhancements for Edge Computing in 3GPP TR 23.700-48 [2], and enhanced architecture for enabling Edge Applications in 3GPP TR 23.700-98 [3]. The study bases on the work done in the 3GPP TS 33.558 [4] and 3GPP TR 33.839 [5].
|
33.740
|
Study on security aspects of Proximity Based Services (ProSe) in 5G System (5GS) phase 2
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.740/33740-i10.zip
|
The present document studies the security and privacy aspects of proximity based services in 5G system phase 2. It ensures that the security solutions are aligned with the work in SA2 (i.e. TR 23.700-33 [2]), RANs, SA1 (i.e. TS 22.278 [3], TS 22.261 [4], and TS 22.115 [5]) and SA3 (i.e. TS 33.503 [6] and TR 33.870 [7]). The present document covers the following issues:
- Security and privacy key issues, threats and potential requirements of proximity based services in 5G system phase 2.
- Potential security solutions to cover these potential requirements.
Both roaming and non-roaming scenarios are considered.
|
33.741
|
Study on home network triggered primary authentication
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.741/33741-i01.zip
|
The present document studies the use cases which needs Home Network initiated primary authentication and the associated security threats and requirements. As part of this investigation, the study aims at identifying which network function in the HN is better suitable to trigger the primary authentication, corresponding procedures, the potential impacts on visited and home network, and the potential impacts on existing procedures. Moreover, solutions for potential normative work are also in the scope of this study.
|
33.809
|
Study on 5G security enhancements against False Base Stations (FBS)
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.809/33809-i10.zip
|
The present document studies the potential threats and privacy issues associated with false base station scenarios.
The present document identifies the potential solutions for mitigating the risks caused by false base station.
|
33.848
|
Study on security impacts of virtualisation
|
TR
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.848/33848-i00.zip
|
The present document considers the consequences of virtualisation on 3GPP architectures, in order to identify threats and subsequent security requirements. 3GPP function security relies on the underlying implementation technology and physical environment being secure. In legacy deployments, physical rack security and separation implicitly provides underlying security. Many legacy physical security requirements are not formally documented in 3GPP standards and rely on proprietary domain knowledge by 3GPP operators and manufacturers. Legacy core network security models also assume that threats primarily apply at the edge of the function or network only, where the network or physical network functions are exposed by external interfaces.
To provide equivalent security in virtualised deployments, the underlying infrastructure needs to provide minimum security capabilities, in a standardized form, which can be requested and or consumed at the 3GPP layer. This is necessary since virtual functions need to co-exist in shared virtualisation environments and the legacy physical security models do not address the new threat vectors introduced by virtualisation.
While a number of the key issues identified in the present document may not necessarily fully be within the scope of 3GPP to resolve, in order to implement 3GPP functions securely, it is necessary for 3GPP to set requirements that may be addressed outside 3GPP.
The present document identifies security requirements which need to be addressed outside of 3GPP in order for 3GPP to specify fully secure virtualised 3GPP functions. The present document identifies extensions to 3GPP security capabilities which are required to provide direct, explicit, security visibility of the underlying virtualised infrastructure platform to the 3GPP layer. It also identifies extensions to 3GPP functions to make use of such capabilities.
The wider requirements captured within the present document are intended to allow external groups such as ETSI or open-source groups to develop any necessary capabilities and fill identified standardization gaps.
Identification of requirements for the standardization of the overall security framework (e.g. top to bottom, 3GPP, NFVI, hardware, SDN) and minimum-security capabilities which should be used by a virtualised implementation to meet Critical National Infrastructure (CNI) or other regulatory requirements are outside the scope of the present document.
Since there is no single approach to virtualisation, the security threats and risks will vary depending on the deployment use case and virtualisation technology choices. The present document considers both virtualisation threats and risks, that apply to specific implementations (e.g. Virtual Machine or Container based) and more generic threat and risks that apply in all use cases.
|
33.858
|
Study on security aspects of enhanced support of Non-Public Networks (NPN) phase 2
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.858/33858-i10.zip
|
The aim of the present document is to study the security aspects for any potential enhancements to be developed based on the outcome of the study in TR 23.700-08 [2]. For each of the objectives in the scope of the study in TR 23.700-08 [2], potential security aspects that are to be covered in this study are as follows:
- Support for enhanced mobility by enabling support for idle and connected mode mobility between SNPNs without new network selection.
- Study if existing security mechanisms for mobility between PLMNs can be reused for SNPNs or if new security mechanisms are needed.
- Support for non-3GPP access for SNPN
- Study if existing security mechanisms for enabling non-3GPP access in a PLMN can be reused for enabling non-3GPP access in an SNPN or if new security mechanisms are needed.
- Address new requirements (e.g., TS 22.261 [3] requirements for Providing Access to Local Services) related to NPN
- Study the trust model for the resulting architecture for enabling Localized Services via a local hosting NPN.
- Study if existing mechanisms for a UE to access an NPN can be reused for enabling a UE to authenticate with and access the local hosting NPN and the localized services via the hosting NPN with proper authorization, or if new security mechanisms are needed.
|
33.870
|
Study of privacy of identifiers over radio access
|
TR
|
0.8.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.870/33870-080.zip
|
The present document achieves the following objectives:
Analysis of 3GPP identifiers that represent either targets of privacy attacks themselves or may aid adversaries in privacy attacks.
Analysis of the feasibility of privacy attacks; the analysis should consider newer methodologies such as those involving AI/ML
Analysis of available countermeasures, including technical remedies, security guidance, to the identified and feasible privacy attacks; the analysis should consider newer methodologies such as those involving AI/ML
Recommendations to the identified and feasible privacy attacks. Recommendations may include but are not limited to non-technical remedies, architectural recommendations, and procedural fixes.
|
33.874
|
Study on enhanced security for network slicing phase 2
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.874/33874-i10.zip
|
The present document identifies key issues, potential security and privacy requirements and solutions with respect to network slicing Phase 2 work TS 23.501 [2], TS 23.502 [3], TS 23.503 [4] and studies TR 23.700-40 [5] and TR 38.832 [6], specifically,
- Define the security requirements and security services for new NF(s) introduced for UEs' network slice access control.
- Study potential security risks/threats (i.e. DoS, sensitive information leakage) and solutions if needed with respect to slice-related quota management, data rate limitation, and constraints on simultaneous use of slices.
- Study potential security risks/threats related to broadcasting slice-related cell selection/reselection info, and provide security solutions if needed.
|
33.875
|
Study on enhanced security aspects of the 5G Service Based Architecture (SBA)
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.875/33875-i10.zip
|
The present document studies enhanced security aspects of the 5G Service Based Architecture. It will analyse potential threats, study necessary security enhancements, and document decisions of solutions to be adopted or not adopted after evaluating the risks versus the complexity.
In particular, the following topics are addressed:
- Need and mechanism of enabling end to end authentication in roaming case if no cross-certification between operators is enabled;
- Need and mechanism of enabling NF Service Consumer authentication of NRF and the NF Service Producer;
- Need for addressing potential security impact of different deployment scenarios including the several SCPs;
- Verification of URI in subscription/notification;
- Dynamic authorization between SCPs or NF and SCP;
- End-to-End Critical HTTP headers/body parts integrity protection;
- Access token usage in NF Sets;
- Authorization mechanism determination;
- Security of NRF service management;
- Inter-Slice access authorization;
- N32 roaming security considerations for deployment scenarios including roaming hub and hosted SEPP.
|
33.876
|
Study on automated certificate management in Service-Based Architecture (SBA)
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.876/33876-i01.zip
|
The objectives of this study are to identify key issues, potential security and privacy requirements and solutions with respect to
- Standardise the use of a single automated certificate management protocol and procedures for certificate life cycle events within intra-PLMN 5G SBA (i.e. to be used by all 5GC NFs including NRF, SCP, SEPP etc.).
- Study the impact of service mesh in certificate management within 5G SBA.
- Study which lifecycle events (e.g., enrolment, renewal, revocation (e.g., OCSP, CRLs), status monitoring) of a certificate need to be covered.
- Study the relation between certificate management lifecycle and NF management lifecycle.
- Study to reference at minimum following principles:
- Principle to be reusable when 5G SBA is for NPN (standalone and PNI)
- Principles standardised to be able to support NFs doing mutual TLS in Slicing.
- Principles standardised to support both intra and inter PLMN, in the latter referring to SEPP certificates in N32 interfaces and potential cross-certification considerations.
- Principles involving 'Chain of Trust' of Certificate Authorities hierarchies.
- Principles for security of CA's cryptographic private key.
|
33.877
|
Study on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the Next Generation Radio Access Network (NG-RAN)
|
TR
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.877/33877-i00.zip
|
The study aims at identifying key issues and solutions in order to address the security aspects of employing AI/ML techniques in RAN. The motivation of this study is to provide potential security handling for the procedures of the NG-RAN AI/ML framework [2]. The NG-RAN AI/ML framework includes functional entities and information flows between functions in order to realize an AI/ML architecture for data collection, model training, data inference and actions/feedback for the NG-RAN and UEs. The NG-RAN AI/ML framework is also accompanied by three RAN-related use cases.
The study aims at studying the following aspects:
- The applicability of existing security mechanisms for the NG-RAN AI/ML framework.
- Whether user privacy issues exist for the selected use cases in the related RAN group studies, not disrupting the current system designs. Use cases not selected in AI/ML for NG RAN by RAN groups are out of scope of this study. The need for alignment with the study of privacy of identifiers over radio access would also be assessed.
- Security aspects of the RAN use cases from the point of view of AI/ML robustness in the face of AI/ML adversaries in AI/ML for NG-RAN.
|
33.882
|
Study on personal Internet of Things (IoT) networks security aspects
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.882/33882-i01.zip
|
The present document studies how 5G security architecture and procedures can be enhanced to support Personal IoT Network. The aim of the present document is to study the security aspects of Personal IoT Networks for any potential enhancements in alignment with the outcome of SA2 study in TR 23.700-88 [2]. The study will look at the following aspects, performing gap analysis where necessary:
1) Study potential security enhancements for authentications required to secure Personal IoT Networks.
2) Study the security protection and access control for communications required to secure Personal IoT Networks.
3) Study the security enhancements for privacy required to secure Personal IoT Networks.
4) Other security aspects for any potential enhancements in alignment with the outcome of SA2 study in TR 23.700-88 [2].
|
33.883
|
Study on security enhancements for 5G multicast-broadcast services phase 2
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.883/33883-i01.zip
|
The present document is to identify key issues, potential security and privacy requirements and solutions with respect to enhancement for 5G multicast-broadcast services. Specifically:
- Study the security enhancement enabling UE's receiving Multicast MBS Session data in RRC Inactive state. Analysis whether existing security mechanisms for UE in RRC connected state can be reused or new security enhancement are needed.
- Study the security impact and potential enhancement if supporting feasible and efficient resource utilization for the same broadcast content to be provided to 5G MOCN network sharing scenarios.
- Other security issues if identified.
|
33.884
|
Study on security of application enablement aspects for subscriber-aware northbound API access
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.884/33884-i01.zip
|
The scope of present document is based on the requirements for SNA (TS 22.261 clause 6.10.2) [2] and on the Study on application enablement aspects for subscriber-aware northbound API access (TR 23.700-95) [3].
The objective of this study is to:
1. Identify potential new security requirements related to API invocation (such as user authorization) and define potential solutions to fulfil these requirements. This encompasses:
- Whether and how CAPIF functions can determine the resource owner upon CAPIF invocation.
- Whether and how CAPIF can support obtaining authorization from the resource owner.
- Whether and how CAPIF can support revocation of authorization by the resource owner.
- Whether and how CAPIF can support security procedures with the aim to reduce authorization inquiries for a nested API invocation.
The study is not exclusively tailored to CAPIF, but should align with widely deployed authorization frameworks.
2. Identify potential security requirements for APIs used in SNAAPP and define potential solutions to fulfil these requirements.
This objective includes UE-originated API invocation.
|
33.886
|
Study on enhanced security for network slicing phase 3
|
TR
|
18.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.886/33886-i10.zip
|
The present document identifies key security issues, potential security and privacy requirements and solutions with respect to network slicing Phase 3 work. Specifically,
- It studies potential security impact/requirements/solutions (e.g. Steering of Roaming) to support the HPLMN to provide a roaming UE the VPLMN slice information in a secure manner
- It studies potential security impact/requirements/solutions to support temporary slices, slice service areas mismatched with Tracking Area (TA) boundaries, and slices where Network Slice Selection Assistance Information (NSSAI) are not available in some TAs of a Registration Areas (RA).
- It studies potential security impact/requirements/solutions to support secured Network Slice Admission Control (NSAC) procedures in the cases of NSAC for multiple service areas and network controlled UE behaviours.
|
33.887
|
Study on security aspects for support for 5G Wireless and Wireline Convergence (5WWC) phase 2
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.887/33887-i01.zip
|
The objectives of the present document are to identify key issues, potential security and privacy requirements and solutions with respect to:
- Whether and how to identify, authenticate and authorize the Authenticable Non-3GPP devices behind the Residential Gateway (RG) connecting to the network.
- Whether and how to identify, authenticate and authorize the 3GPP devices (UE or N5CW devices) behind the Residential Gateway (RG) connecting to the network.
- Security aspects of supporting slice in 5WWC.
- Whether and how the security aspects for UE TNAP mobility can be supported in the 5GS without performing the full authentication.
|
33.890
|
Study on security support for next generation real time communication services
|
TR
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.890/33890-i00.zip
|
The present document studies security aspects for any potential enhancements based on the ongoing study in TR 23.700-87 [2]. For each of the key issues in the scope of the SA WG2 study, the security aspects that are to be covered in this study are as follows:
- Analysing the potential security aspects on how to verify and authorize the 3rd party specific identity information during a call both on originating and terminating sides.
- Analysing potential security impacts from supporting service-based architecture in IMS media control interfaces.
- Analysing potential security aspects to support Data Channel usage in IMS network.
|
33.891
|
Study on security of phase 2 for Uncrewed Aerial System (UAS), Uncrewed Aerial Vehicle (UAV) and Urban Air Mobility (UAM)
|
TR
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.891/33891-i00.zip
|
The present document investigates and identifies the security and privacy threats and corresponding security requirements for Uncrewed Aerial Vehicles (UAVs) and Urban Air Mobility (UAM) that derive from the architecture and system level enhancements studied in TR 23.700-58 [2]. Furthermore, the present document considers solutions and analyses these to make recommendations for possible normative work taking into consideration the conclusions of TR 23.700-58 [2].
|
33.892
|
Study on UE Route Selection Policy (URSP) rules to securely identify applications
|
TR
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.892/33892-i00.zip
|
The present document analyses mechanisms to ensure the identity of a genuine application in order to apply the URSP rule accordingly, such that malicious applications cannot get access towards the operator regulated resources. The present document identifies key issues and develops solutions for enhancements that enables a URSP rule to securely identify the application for which the URSP rule should be applied.
|
33.893
|
Study on security aspects of ranging-based services and sidelink positioning
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.893/33893-i01.zip
|
The present document investigates the security and privacy aspects of Ranging based services and sidelink positioning in 5G system. The study is based on the architectural and functional requirements on Ranging based services and sidelink positioning services, so as to ensure that the proposed solutions address the security and privacy implications on the architecture enhancements studied in TR 23.700-86 [2]. Specifically, it covers the following:
- The identified security and privacy issues, threats, and potential requirements for Ranging based services and sidelink positioning.
- The gap analysis in security and privacy issues between Ranging based services and ProSe/V2X applications.
- The potential solutions addressing the security and privacy issues specific to Ranging based services and sidelink positioning.
|
33.894
|
Study on applicability of the zero trust security principles in mobile networks
|
TR
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.894/33894-i00.zip
|
The present document studies some Zero Trust Security principles that can be applied to the 5G System core network. The present document will further analyse potential threats, study necessary security enhancements, and document various decisions related to solutions as to be adopted or not adopted after evaluating the associated risks and the complexity. The present document specifically covers the following aspects:
- Analyse the 3GPP 5GS security scenarios related to the 5G core network that may benefit from a Zero Trust principle and identify the associated threats.
- Analyse the suitable Zero Trust security mechanisms (i.e. for enabling trust evaluation and ensuring trust) to address the threats identified where potential security risk exists.
- Provide recommendations for support of additional Zero Trust principles in 5GS security architecture with suitable future normative work directions, where such recommendations may include 3GPP 5G security requirements, technical enhancements, and procedural enhancements.
|
33.896
|
Study of security aspects on user consent for 3GPP services phase 2
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.896/33896-i01.zip
|
The present document is to investigate potential enhancements of 5GS that would enable broader use cases in relation with user consent.
The following aspects are in the scope of the study:
1. Investigating the potential issues and solutions with user consent for:
- eNA in case of roaming.
- MEC in case of roaming.
- NTN.
- AI/ML for NG-RAN.
2. Investigating the potential generic security requirements, services and guidance for user consent derived from objective 1.
NOTE 1: Principles, regulations, and definitions related to privacy, which are recognized differently in each different country or area, are taken into account when deriving the concept of user consent for 3GPP users.
Even where solutions exist to obtain user consent, collection and exposure of user sensitive data should be minimized and identification of the users should only be allowed where critical to the operation of the related feature.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.