Please enter the search related information in the fields below. Partial information works, e.g. "SP-21
" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501
" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP
" gives the same results as "3gpp
".
Download results in JSON format
tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
---|---|---|---|---|---|---|---|---|---|
S3-223140 | Agenda | agenda | SA WG3 Chair |
S3-109 AI: 1 |
approved | [WTS] [JSN] | |||
S3-223141 | Report from SA3#108e | report | MCC |
S3-109 AI: 2 |
approved | [WTS] [JSN] | |||
S3-223142 | Report for SA3#108e ad-Hoc | other | SA WG3 Chair |
S3-109 AI: 2 |
approved | [WTS] [JSN] | |||
S3-223143 | Process for SA3#109 | other | SA WG3 Chair |
S3-109 AI: 1 |
noted | [WTS] [JSN] | |||
S3-223144 | Report from last SA | report | SA WG3 Chair |
S3-109 AI: 2 |
noted | [WTS] [JSN] | |||
S3-223145 | Process and agenda planning for SA3#109 | other | SA WG3 Chair |
S3-109 AI: 1 |
noted | [WTS] [JSN] | |||
S3-223146 | SA3 meeting calendar |
other revised to S3-224105 |
SA WG3 Chair |
S3-109 AI: 8 |
revised | [WTS] [JSN] | |||
S3-223147 | 5G capabilities exposure for factories of the future - identified gaps | LS in | 5G-ACIA |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223148 | LS on clarification for UE_NOT_FOUND cause code for UP in CT1 |
LS in LS reply in S3-223903, S3-223903 |
C1-226279 |
S3-109 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-223149 | LS on user’s consent for EDGEAPP |
LS in LS reply in S3-223904, S3-223904 |
C3-223780 |
S3-109 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-223150 | LS on anonymous user access to an AF |
LS in LS reply in S3-223921, S3-223921 |
C3-224730 |
S3-109 AI: 4.9 |
replied to | [WTS] [JSN] | |||
S3-223151 | LS on Authentication Result Removal |
LS in LS reply in S3-223908, S3-223908 |
C4-224418 |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223152 | Reply LS on PLMN ID used in Roaming Scenarios |
LS in LS reply in S3-223909 |
C4-224444 |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223153 | Reply LS on handling of the modification policy in the IPX and receiving SEPP | LS in | C4-224467 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223154 | LS on Indication of Network Assisted Positioning method | LS in | C4-224626 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223155 | Reply LS on Facilitating roaming adoption across 3GPP NPN deployments | LS in | C6-220475 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223156 | Completion of SGP.22 v3.0 | LS in | GSMA |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223157 | LS to 3GPP - Hosted SEPP |
LS in LS reply in S3-223910, S3-223910 |
GSMA |
S3-109 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-223158 | Research highlighting potential need for granular level checks using ""Additional scope"" under the OAuth2.0 Token Access. | LS in | GSMA |
S3-109 AI: 7 |
postponed | [WTS] [JSN] | |||
S3-223159 | Re-use of CAPIF by ETSI MEC | LS in | ETSI ISG MEC |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223160 | Reply LS on null security algorithm | LS in | R2-2208832 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223161 | Reply LS on authenticity and replay protection of system information |
LS in LS reply in S3-223731 |
R2-2208985 |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223162 | Reply LS on the user consent for trace reporting |
LS in LS reply in S3-223905 |
R3-225250 |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223163 | LS on user consent of Non-public Network |
LS in LS reply in S3-223906, S3-223906 |
R3-226006 |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223164 | Reply LS on Security architecture for 5G multicast/broadcast services |
LS in LS reply in S3-223919, S3-223919 |
S2-2207390 |
S3-109 AI: 4.9 |
replied to | [WTS] [JSN] | |||
S3-223165 | Reply LS On PLMN ID used in Roaming Scenarios |
LS in LS reply in S3-223909 |
S2-2207391 |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223166 | LS on protection of the URSP rules from HPLMN |
LS in LS reply in S3-223911, S3-223911 |
S2-2207501 |
S3-109 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-223167 | Reply LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions | LS in | S2-2207697 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223168 | Questions for SUCI protection requirements for non-3GPP (WLAN) access to SNPN |
LS in LS reply in S3-224175 |
S2-2207700 |
S3-109 AI: 5.16 |
replied to | [WTS] [JSN] | |||
S3-223169 | LS Reply on EAC Mode for NSAC | LS in | S2-2209260 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223170 | Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover | LS in | S2-2209262 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223171 | Response LS on Clarifications for AF specific UE ID retrieval | LS in | S2-2209270 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223172 | Reply LS on the impact of MSK update on MBS multicast session update procedure |
LS in LS reply in S3-223918, S3-223918 |
S2-2209287 |
S3-109 AI: 4.9 |
postponed | [WTS] [JSN] | |||
S3-223173 | LS on impact of URSP rule enforcement report to 5GC |
LS in LS reply in S3-223912, S3-223912 |
S2-2209327 |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223174 | LS on Satellite coverage data transfer to a UE using UP versus CP | LS in | S2-2209684 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223175 | Progress and open issues for NPN enhancements in Rel-18 |
LS in LS reply in S3-224175 |
S2-2209860 |
S3-109 AI: 5.16 |
replied to | [WTS] [JSN] | |||
S3-223176 | LS on Time Synchronization Status notification towards UE(s) |
LS in LS reply in S3-223915, S3-223915 |
S2-2209876 |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223177 | Reply LS on User plane solution for 5GC information exposure to UE | LS in | S2-2209910 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223178 | LS on User consent for Application Detection |
LS in LS reply in S3-223907, S3-223907 |
S2-2209973 |
S3-109 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-223179 | Reply LS on User Consent Updating | LS in | S5-225321 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223180 | Forward on S6-222332, LS on Network federation interface for Telco edge consideration |
LS in LS reply in S3-223914, S3-223914 |
S6-222543 |
S3-109 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-223181 | Reply LS on user’s consent for EDGEAPP | LS in | S6-222555 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223182 | LS on new work item X.5Gsec-ctrl: Security controls for operation and maintenance of 5G network systems | LS in | ITU-T SG17 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223183 | Reply LS on Facilitating roaming adoption across 3GPP NPN deployments | LS in | SP-220985 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223184 | LS from NG to 3GPP SA3 on IMS Data Channel Security Mode |
LS in LS reply in S3-223913, S3-223913 |
GSMA |
S3-109 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-223185 | Facilitating roaming adoption across 3GPP NPN deployment | LS in | WBA |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223186 | [33.180] R18 MC client clarification | CR | Motorola Solutions Danmark A/S | 33.180 17.7.0 CR#195 catF | MCXSec3 | Rel-18 |
S3-109 AI: 4.3 |
withdrawn | [WTS] [JSN] |
S3-223187 | Clarification of hashing | CR | BSI (DE) | 33.117 17.1.0 CR#81 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223188 | Clarification of authorization verification | CR | BSI (DE) | 33.117 17.1.0 CR#82 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223189 | Clarification of brute force mitigation mechanism verification | CR | BSI (DE) | 33.117 17.1.0 CR#83 catF | SCAS | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223190 | Clarification of privilege escalation methods to check for | CR | BSI (DE) | 33.117 17.1.0 CR#84 catF | SCAS | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223191 | Clarification of service reachability restriction verification | CR | BSI (DE) | 33.117 17.1.0 CR#85 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223192 | Clarification of auto-launch verification | CR | BSI (DE) | 33.117 17.1.0 CR#86 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223193 | Clarification of SYN Flood attack prevention test | CR | BSI (DE) | 33.117 17.1.0 CR#87 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223194 | Clarification of privilege verification | CR | BSI (DE) | 33.117 17.1.0 CR#88 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223195 | Reply LS on Re-use of CAPIF by ETSI MEC | LS in | S6-223027 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223196 | LS on Support PIN application architecture and interaction |
LS in LS reply in S3-224068, S3-224068 |
S6-223028 |
S3-109 AI: 5.1 |
replied to | [WTS] [JSN] | |||
S3-223197 | Clarification of CGI/Scripting component directory check | CR | BSI (DE) | 33.117 17.1.0 CR#89 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223198 | Clarification of SSI System Command Excecution test | CR | BSI (DE) | 33.117 17.1.0 CR#90 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223199 | TCG progress - report from TCG rapporteur | other | InterDigital, Inc. |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223200 | PCR to 33.870 Changes to Solution #2 |
pCR revised to S3-224069 |
InterDigital, Inc. | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
revised | [WTS] [JSN] |
S3-223201 | PCR to 33.870 - New clause for mapping solutions and KIs | pCR | InterDigital, Inc. | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
not treated | [WTS] [JSN] |
S3-223202 | CR NRF deployments |
CR revision of S3-221867 |
Nokia, Nokia Shanghai Bell, Ericsson, Mavenir, Huawei, HiSilicon | 33.501 17.7.0 CR#14371 catB | DUMMY | Rel-18 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223203 | Clarification on N32-f connection establishment with TLS |
CR revision of S3-221841 revised to S3-223951 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#14351 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
revised | [WTS] [JSN] |
S3-223204 | Reply LS on PLMN ID used in Roaming Scenarios |
LS out LS is reply to S3-223152, S3-223165 source LS: S3-221214 LS To: CT4, SA2 |
Nokia, Nokia Shanghai Bell |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223205 | New SCAS test case for AUSF | draftCR | Keysight Technologies UK Ltd | SCAS_5G_AAnF | Rel-17 |
S3-109 AI: 4.5 |
noted | [WTS] [JSN] | |
S3-223206 | Clarification for IPSec in UPF interfaces | CR | Keysight Technologies UK Ltd | 33.513 17.0.0 CR#8 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.4 |
not pursued | [WTS] [JSN] |
S3-223207 | Correction of requirement references in UPF test case | CR | Keysight Technologies UK Ltd | 33.513 17.0.0 CR#9 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.4 |
agreed | [WTS] [JSN] |
S3-223208 | Update gNB test case for UP integrity protection | CR | Keysight Technologies UK Ltd | 33.511 17.2.0 CR#33 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.4 |
not pursued | [WTS] [JSN] |
S3-223209 | Update to KI#1 providing VPLMN slice information to roaming UE | pCR | NEC Corporation | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
noted | [WTS] [JSN] |
S3-223210 | New solution to KI#1: Protection of SoR related information from UE to home network | pCR | NEC Corporation | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223211 | Discussion paper on open questions regarding 256-bit algorithms | discussion | KDDI Corporation |
S3-109 AI: 6 |
withdrawn | [WTS] [JSN] | |||
S3-223212 | Study on enabling a cryptographic algorithm transition to 256 bits | SID new | KDDI Corporation |
S3-109 AI: 6 |
withdrawn | [WTS] [JSN] | |||
S3-223213 | Reply LS on Time Synchronization Status notification towards UE(s) |
LS out source LS: S2-2209876 LS To: 3GPP SA WG2 revised to S3-223915 |
Nokia, Nokia Shanghai Bell | Rel-18 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | ||
S3-223214 | Introduction of DTLS 1.3 | CR | Nokia, Nokia Shanghai Bell | 33.210 17.1.0 CR#75 catB | NDS_Backhaul | Rel-17 |
S3-109 AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-223215 | Terminology update of solution #6 | pCR | Lenovo | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-223216 | New solution addressing KI#6 | pCR | Lenovo, Nokia | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
not treated | [WTS] [JSN] |
S3-223217 | Update of solution #4 |
pCR revised to S3-224146 |
Lenovo | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223218 | Solution for Trusted non-3GPP Access for SNPN |
pCR revised to S3-224034 |
Lenovo | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
revised | [WTS] [JSN] |
S3-223219 | Solution for Untrusted non-3GPP Access for SNPN |
pCR revised to S3-224035 |
Lenovo | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
revised | [WTS] [JSN] |
S3-223220 | New SID on QUICK optimization for access traffic steering, switching and splitting support in the 5G system architecture; Phase 3 | SID new | Lenovo | Rel-18 |
S3-109 AI: 6 |
noted | [WTS] [JSN] | ||
S3-223221 | Conclusion for KI#1 | pCR | Lenovo | 33.892 0.3.0 | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
noted | [WTS] [JSN] |
S3-223222 | Evaluation Update of Solution #2 | pCR | Lenovo | 33.892 0.3.0 | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
noted | [WTS] [JSN] |
S3-223223 | PCR to 33.870 - Aggregate changes | pCR | InterDigital, Inc. | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
not treated | [WTS] [JSN] |
S3-223224 | Discussion paper on 5GC AIML system capability | discussion | InterDigital Communications | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] | |
S3-223225 | New key issue on Federated Learning AIML model privacy protection | pCR | InterDigital Communications | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
not treated | [WTS] [JSN] |
S3-223226 | New key issue on Federated Learning AIML model protection | pCR | InterDigital Communications | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
not treated | [WTS] [JSN] |
S3-223227 | Key issue on SN Name binding for Kausf in SNPN using AAA server for primary authentication | pCR | InterDigital Communications | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
not treated | [WTS] [JSN] |
S3-223228 | New Solution of authorization for EDGE-9 reference point | pCR | InterDigital Communications | 33.739 0.2.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223229 | Reply LS to Reply LS on the user consent for trace reporting |
LS out LS is reply to S3-223162/R3-225250 LS To: RAN3 revised to S3-223905 |
Nokia, Nokia Shanghai Bell |
S3-109 AI: 3 |
revised | [WTS] [JSN] | |||
S3-223230 | New Key issue for Detecting ranging triggered DoS attacks | pCR | Nokia, Nokia Shanghai Bell | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223231 | New key issue on enhancement of user consent for using MDT for NG-RAN AI/ML | pCR | Nokia, Nokia Shanghai Bell | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] |
S3-223232 | Key Issue for Secure RRC connection setup procedure | pCR | Nokia, Nokia Shanghai Bell | 33.700-28 0.1.0 | FS_5GSAT_Sec | Rel-18 |
S3-109 AI: 5.25 |
noted | [WTS] [JSN] |
S3-223233 | New Key issue for Updating security policy parameters when device is out of 5G coverage | pCR | Nokia, Nokia Shanghai Bell | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223234 | TMGI protection during group Paging | pCR | Nokia, Nokia Shanghai Bell | 33.883 0.3.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
noted | [WTS] [JSN] |
S3-223235 | LS on MOCN TMGI ID impacting MSK, MTK |
LS out LS To: SA2 |
Nokia, Nokia Shanghai Bell |
S3-109 AI: 5.23 |
noted | [WTS] [JSN] | |||
S3-223236 | EN removal for MOCN solution#2 | pCR | Nokia, Nokia Shanghai Bell | 33.883 0.3.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
noted | [WTS] [JSN] |
S3-223237 | New solution for prevention of detection of priority access | pCR | Nokia, Nokia Shanghai Bell | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
not treated | [WTS] [JSN] |
S3-223238 | EN removal for privacy prevention of NAI solution |
pCR revised to S3-224114 |
Nokia, Nokia Shanghai Bell | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
revised | [WTS] [JSN] |
S3-223239 | Further Analysis for KI#1 in TR 33.875 | pCR | Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
noted | [WTS] [JSN] |
S3-223240 | Conclusion on KI#1 in TR 33.875 |
pCR revised to S3-223984 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223241 | Further Analysis for KI#4 in TR 33.875 |
pCR revised to S3-223988 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223242 | Conclusion for KI#4 in TR 33.875 |
pCR revised to S3-223989 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223243 | Further Analysis for KI#5 in TR 33.875 | pCR | Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
noted | [WTS] [JSN] |
S3-223244 | Conclusion on KI#5 in TR 33.875 |
pCR revised to S3-224100 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223245 | Further Analysis for KI#6 in TR 33.875 | pCR | Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
noted | [WTS] [JSN] |
S3-223246 | Conclusion for KI#6 in TR 33.875 |
pCR revised to S3-224102 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223247 | Update KI#5 |
pCR revised to S3-223963 |
OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223248 | New solution for KI#5 |
pCR revised to S3-224029 |
OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223249 | Update Annex A | pCR | OPPO, Xidian | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
approved | [WTS] [JSN] |
S3-223250 | Key issue on user consent for FL UE members | pCR | OPPO, Nokia, Nokia Shanghai Bell, Inter Digital | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] |
S3-223251 | Discussion on Ambient IoT Security | discussion | OPPO | Rel-19 |
S3-109 AI: 6 |
noted | [WTS] [JSN] | ||
S3-223252 | Discussion paper of WWC SID update for TNAP mobility | discussion | Nokia, Nokia Shanghai Bell,CableLabs, Lenovo, Apple | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] | |
S3-223253 | New SID on Security aspects for 5WWC Phase 2 |
SID revised revised to S3-224047 |
Nokia, Nokia Shanghai Bell, CableLabs, Lenovo, Apple | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] | |
S3-223254 | updating the existing solution mapping | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
not treated | [WTS] [JSN] |
S3-223255 | Scope section alignment | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
not treated | [WTS] [JSN] |
S3-223256 | TNAP mobility architecture assumptions | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
not treated | [WTS] [JSN] |
S3-223257 | TNAP mobility solution with rand value |
pCR revised to S3-224053 |
Nokia, Nokia Shanghai Bell, CableLabs, | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223258 | TNAP mobility solution with count |
pCR revised to S3-224054 |
Nokia, Nokia Shanghai Bell, CableLabs, | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223259 | evaluation for solution 1 |
pCR revised to S3-224048 |
Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223260 | Discussion on authorization issue in inter NF mobility | discussion | Nokia, Nokia Shanghai Bell | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
noted | [WTS] [JSN] | |
S3-223261 | Clarification on authorization for inter NF mobility | CR | Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#1484 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-223262 | Correction in UPU procedure to align with stage 3 | CR | Nokia, Nokia Shanghai Bell | 33.501 16.12.0 CR#1485 catF | TEI16 | Rel-16 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223263 | Correction in UPU procedure to align with stage 3 | CR | Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#1486 catA | TEI16 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223264 | UPU procedure align with stage 3 for AMF not registered case |
CR revised to S3-223938 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#1487 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223265 | LS reply on AKMA API |
LS out LS To: CT3 revised to S3-223921 |
Nokia, Nokia Shanghai Bell | AKMA | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] | |
S3-223266 | AKMA API enhancement based on the LS | CR | Nokia, Nokia Shanghai Bell | 33.535 17.7.0 CR#139 catF | AKMA | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223267 | alignment for solution1 for vAAnF or a new NF | pCR | Nokia, Nokia Shanghai Bell | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-223268 | alignment for solution1 related to internal AF | pCR | Nokia, Nokia Shanghai Bell | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-223269 | solution 1 evaluation |
pCR revised to S3-224078 |
Nokia, Nokia Shanghai Bell | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223270 | KI1 conclusion | pCR | Nokia, Nokia Shanghai Bell, Lenovo, OPPO | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
not treated | [WTS] [JSN] |
S3-223271 | Discussion on privacy issue in AKMA | discussion | Nokia, Nokia Shanghai Bell, Samsung | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
not treated | [WTS] [JSN] | |
S3-223272 | key issue on AKMA privacy | pCR | Nokia, Nokia Shanghai Bell, Samsung | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
not treated | [WTS] [JSN] |
S3-223273 | solution 1 evaluation |
pCR revised to S3-224014 |
Nokia, Nokia Shanghai Bell | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223274 | KI#1 conclusion | pCR | Nokia, Nokia Shanghai Bell | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
merged | [WTS] [JSN] |
S3-223275 | Key issue on Security criteria of UE selection for AIML | pCR | Nokia, Nokia Shanghai Bell, Inter Digital | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] |
S3-223276 | ProSe - Evaluation Solution #10 |
pCR revised to S3-224006 |
Philips International B.V. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223277 | ProSe - Evaluation Solution #15 | pCR | Philips International B.V. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223278 | ProSe - Minnor editorial corrections in Solution #10 | pCR | Philips International B.V. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223279 | ProSe - Minnor updates in Solution #10 | pCR | Philips International B.V. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223280 | PIN - Addressing EN#1 in Solution #4 |
pCR revised to S3-224073 |
Philips International B.V. | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223281 | PIN - Addressing EN#2 in Solution #4 |
pCR revised to S3-224059 |
Philips International B.V. | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223282 | PIN - Addressing EN#3 in Solution #4 |
pCR revised to S3-224074 |
Philips International B.V. | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223283 | PIN - Addressing EN#4 in Solution #4 |
pCR revised to S3-224060 |
Philips International B.V. | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223284 | FBS - Way forward for solutions based on digital signatures addressing KI#2 | pCR | Philips International B.V. | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223285 | FBS - Additions in solution #25 | pCR | Philips International B.V. | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223286 | FBS - Evaluation of solution #25 | pCR | Philips International B.V. | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223287 | AKMA - Evaluation Solution #10 |
pCR revised to S3-224010 |
Philips International B.V. | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223288 | Ranging - New solution KI#1, #2, #3 | pCR | Philips International B.V. | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223289 | Ranging - Update Key Issue #1- privacy risks of exposing positioning reference signals | pCR | Philips International B.V. | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
noted | [WTS] [JSN] |
S3-223290 | Sol#3 Resolution of EN on CAPIF support | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-223291 | Sol#3 Resolution of EN on visibility of application |
pCR revised to S3-224038 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223292 | Sol#3 Resolution of EN on prearranged policies |
pCR revised to S3-224039 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223293 | Sol#3 Resolution of EN on authorization of third party |
pCR revised to S3-224040 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223294 | Sol#3 Resolution of EN on AKMA Usage |
pCR revised to S3-224041 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223295 | Sol#3 Resolution of EN on Mutual Authentication | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223296 | Sol#3 Resolution of EN on Client Credential Grant | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223297 | Sol#3 Adding Evaluation |
pCR revised to S3-224042 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223298 | Reply LS on impact to URSP rules enforcement report to 5GC |
LS out LS is reply to S3-223173 LS To: SA WG2 revised to S3-223912 |
vivo | FS_eUEPO | Rel-18 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | |
S3-223299 | Reply LS on Support PIN application architecture and interaction |
LS out LS is reply to S3-223196 LS To: SA WG6 revised to S3-224068 |
vivo | FS_PINAPP | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] | |
S3-223300 | New solution for AF manipulate PIN |
pCR revised to S3-224064 |
vivo | 33.882 3.0.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223301 | New solution for PINE authentication and authorization by PEMC | pCR | vivo | 33.882 3.0.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] |
S3-223302 | New solution for PINE authentication and authorization over 5G UP | pCR | vivo | 33.882 3.0.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] |
S3-223303 | New solution for remote provisioning of credential for PINE | pCR | vivo | 33.882 3.0.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] |
S3-223304 | Update solution for PINE authentication over CP | pCR | vivo | 33.882 3.0.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] |
S3-223305 | Interim conclusions on KI#1 | pCR | vivo | 33.882 3.0.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] |
S3-223306 | Sol#3 Resolution of EN on authorization of PEGC |
pCR revised to S3-224088 |
Nokia, Nokia Shanghai Bell | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223307 | Sol#3 Resolution of EN on identification of PINE | pCR | Nokia, Nokia Shanghai Bell | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-223308 | Sol#3 Adding Evaluation |
pCR revised to S3-224062 |
Nokia, Nokia Shanghai Bell | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223309 | Ki#1 New Solution using AKMA | pCR | Nokia, Nokia Shanghai Bell | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] |
S3-223310 | Update TR 33.740 solution #1 |
pCR revised to S3-223969 |
InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223311 | Update TR 33.740 solution #2 | pCR | InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223312 | Update TR 33.740 solution #12 |
pCR revised to S3-224000 |
InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223313 | Update TR 33.740 solution #13 |
pCR revised to S3-224001 |
InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223314 | Update TR 33.740 solution #14 |
pCR revised to S3-224007 |
InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223315 | Alignment of Link Identifier Update (LIU) procedure |
CR revised to S3-224170 |
InterDigital, Europe, Ltd. | 33.503 17.1.0 CR#42 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223316 | Handling of PRUK desynchronization issue with 5G ProSe UE-to-Network Relay | CR | InterDigital, Europe, Ltd. | 33.503 17.1.0 CR#43 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-223317 | LS Reply on UE_NOT_FOUND cause code |
LS out LS is reply to S3-223148 LS To: CT1 revised to S3-223903 |
InterDigital, Europe, Ltd. | Rel-17 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | ||
S3-223318 | Resolution of Remote UE permanent identity in Remote UE Report procedure (CP) | CR | InterDigital, Europe, Ltd. | 33.503 17.1.0 CR#44 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
not treated | [WTS] [JSN] |
S3-223319 | Resolution of Remote UE permanent identity in Remote UE Report procedure (UP) | CR | InterDigital, Europe, Ltd. | 33.503 17.1.0 CR#45 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
not treated | [WTS] [JSN] |
S3-223320 | Discussion on Lawful Interception support for 5G ProSe Layer-3 UE-to-Network Relay | discussion | InterDigital, Europe, Ltd. | Rel-17 |
S3-109 AI: 4.8 |
not treated | [WTS] [JSN] | ||
S3-223321 | LS on support for Lawful Intercept target identities for 5G ProSe Remote UE |
LS out LS To: SA3-LI, SA2 |
InterDigital, Europe, Ltd. | Rel-17 |
S3-109 AI: 4.8 |
not treated | [WTS] [JSN] | ||
S3-223322 | Living document to TS 33.503 for Prose Secondary Authentication | draftCR | InterDigital, Europe, Ltd. | PROSESA | Rel-18 |
S3-109 AI: 5.3 |
not treated | [WTS] [JSN] | |
S3-223323 | Evaluation Solution #4 |
pCR revised to S3-224116 |
InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
revised | [WTS] [JSN] |
S3-223324 | Evaluation Solution #5 | pCR | InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-223325 | Conclusion TR 33.891 KI #1 |
pCR revised to S3-224117 |
InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
revised | [WTS] [JSN] |
S3-223326 | Conclusion TR 33.891 KI #3 |
pCR revised to S3-224118 |
InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
revised | [WTS] [JSN] |
S3-223327 | Conclusion TR 33.891 KI #4 |
pCR revised to S3-224119 |
InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
revised | [WTS] [JSN] |
S3-223328 | Resolving Editor’s Note in Solution #20 in TR 33.875 |
pCR revised to S3-224110 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223329 | Analysis for KI#11 in TR 33.875 | pCR | Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
not treated | [WTS] [JSN] |
S3-223330 | Conclusion on KI#11 in TR 33.875 |
pCR revised to S3-223990 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223331 | Clarification to the UPU procedures | CR | Qualcomm Incorporated | 33.501 17.7.0 CR#1488 catF | TEI17, 5GS_Ph1-SEC | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223332 | Resolving the EN on CAA level ID during UUAA procedures |
CR revision of S3-221827 |
Qualcomm Incorporated | 33.256 17.1.0 CR#92 catF | ID_UAS | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223333 | Resolving the ENs on CAA level ID during revocation |
CR revision of S3-221828 revised to S3-223928 |
Qualcomm Incorporated | 33.256 17.1.0 CR#112 catF | ID_UAS | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223334 | Correction to the gNB threats in TR 33.926 | CR | Qualcomm Incorporated | 33.926 16.6.0 CR#62 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223335 | Correction to the gNB threats in TR 33.926 | CR | Qualcomm Incorporated | 33.926 17.5.0 CR#63 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223336 | Corrections to the test cases in TS 33.511 | CR | Qualcomm Incorporated | 33.511 16.8.0 CR#34 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223337 | Corrections to the test cases in TS 33.511 | CR | Qualcomm Incorporated | 33.511 17.2.0 CR#35 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223338 | Corrections to the threat references in TS 33.511 | CR | Qualcomm Incorporated | 33.511 16.8.0 CR#36 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223339 | Corrections to the threat references in TS 33.511 | CR | Qualcomm Incorporated | 33.511 17.2.0 CR#37 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223340 | Adding non-Uu user plane text cases to TS 33.511 | CR | Qualcomm Incorporated | 33.511 16.8.0 CR#38 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223341 | Adding non-Uu user plane text cases to TS 33.511 | CR | Qualcomm Incorporated | 33.511 17.2.0 CR#39 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223342 | Draft CR: Introducing split gNBs into TR 33.926 |
draftCR revision of S3-222322 revised to S3-224169 |
Qualcomm Incoporated | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
revised | [WTS] [JSN] | |
S3-223343 | Proposed text for gNB-CU part of draft CR to TR 33.926 |
other revision of S3-221815 |
Qualcomm Incoporated |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] | |||
S3-223344 | Proposed text for gNB-CU-CP part of draft CR to TR 33.926 |
other revision of S3-221816 |
Qualcomm Incoporated |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] | |||
S3-223345 | Add user plane threats for gNB-DU to the draft CR to TR 33.926 | other | Qualcomm Incoporated |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] | |||
S3-223346 | Correcting the threats references for the gNB-CU | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] |
S3-223347 | Adding user plane test cases for the gNB-CU | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
noted | [WTS] [JSN] |
S3-223348 | Correcting the threats references for the gNB-CU-CP | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] |
S3-223349 | Adding test cases for the gNB-CU-CP | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] |
S3-223350 | Correcting the threats references for the gNB-CU-UP | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] |
S3-223351 | Adding test cases for the gNB-CU-UP | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
noted | [WTS] [JSN] |
S3-223352 | Correcting the threats references for the gNB-DU | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] |
S3-223353 | Adding user plane test cases for the gNB-DU | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] |
S3-223354 | Adding non-501 test cases for the gNB-CU | pCR | Qualcomm Incoporated | 33.742 0.2.0 | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] |
S3-223355 | Proposed key issue on the privacy of 3GPP identifiers used to transport Broadcast Remote ID |
pCR revision of S3-222754 |
Qualcomm Incorporated | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-223356 | Proposed solution on the privacy of 3GPP identifiers used to transport broadcast remote ID |
pCR revision of S3-222756 |
Qualcomm Incorporated | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-223357 | Proposed resolution of pairing EN in solution #3 | pCR | Qualcomm Incorporated | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
noted | [WTS] [JSN] |
S3-223358 | Proposed resolution of DAA credentials EN in solution #3 | pCR | Qualcomm Incorporated | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-223359 | Adding a K_AUSF refresh use case | pCR | Qualcomm Incorporated | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
noted | [WTS] [JSN] |
S3-223360 | Adding an evaluation of solution #5 |
pCR revised to S3-224015 |
Qualcomm Incorporated | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223361 | Proposed conclusion for the study | pCR | Qualcomm Incorporated | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
merged | [WTS] [JSN] |
S3-223362 | Method negotiation using TLS 1.3 |
pCR revised to S3-223940 |
Qualcomm Incorporated | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
revised | [WTS] [JSN] |
S3-223363 | Common authentication method between EEC and ECS/EES |
pCR revised to S3-230289 |
Qualcomm Incorporated | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223364 | Proposed solution for TNAP mobility |
pCR revised to S3-224055 |
Qualcomm Incorporated | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223365 | Clarification on 5G MBS user-plane procedure | CR | Qualcomm Incorporated | 33.501 17.7.0 CR#1489 catF | 5MBS | Rel-17 |
S3-109 AI: 4.9 |
merged | [WTS] [JSN] |
S3-223366 | Reply LS on Security architecture for 5G multicast/broadcast services |
LS out LS is reply to S3-223164 LS To: SA2 |
Qualcomm Incorporated | 5MBS | Rel-17 |
S3-109 AI: 4.9 |
merged | [WTS] [JSN] | |
S3-223367 | LS on Source user info in Direct Communication Request in UE-to-Network Relay |
LS out LS To: SA2, CT1 |
Qualcomm Incorporated | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
noted | [WTS] [JSN] | |
S3-223368 | Corrections in privacy protection of 5G ProSe UE-to-Network relay procedure |
CR revised to S3-223957 |
Qualcomm Incorporated | 33.503 17.1.0 CR#46 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223369 | A new solution for UE-to-UE Relay discovery message protection for Model A discovery |
pCR revised to S3-223997 |
Qualcomm Incorporated | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223370 | A new solution for UE-to-UE Relay discovery message protection for Model B discovery |
pCR revised to S3-223998 |
Qualcomm Incorporated | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223371 | A new solution for secure PC5 link establishment for UE-to-UE Relay |
pCR revised to S3-223999 |
Qualcomm Incorporated | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223372 | Conclusion for KI #2 | pCR | Qualcomm Incorporated | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] |
S3-223373 | Conclusion for KI #3 | pCR | Qualcomm Incorporated | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223374 | SUCI protection for non-3GPP (WLAN) access to SNPN | discussion | Qualcomm Incorporated |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] | |||
S3-223375 | Reply LS on Progress and open issues for NPN enhancements in Rel-18 |
LS out LS is reply to S3-223175 LS To: SA2 revised to S3-224175 |
Qualcomm Incorporated | FS_eNPN_Ph2, eNPN_Ph2 | Rel-18 |
S3-109 AI: 5.16 |
revised | [WTS] [JSN] | |
S3-223376 | Resolution of an EN in solution #8 | pCR | Qualcomm Incorporated | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
not treated | [WTS] [JSN] |
S3-223377 | Evaluation of solution #8 |
pCR revised to S3-224176 |
Qualcomm Incorporated | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
revised | [WTS] [JSN] |
S3-223378 | Solution for KI#1: Authentication and Authorization of PINE |
pCR revised to S3-224067 |
Qualcomm Incorporated | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223379 | Reply LS on protection of the URSP rules from HPLMN |
LS out LS is reply to S3-223173 LS To: SA2 revised to S3-223911 |
Qualcomm Incorporated | FS_eUEPO | Rel-18 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | |
S3-223380 | Evaluation for Solution #3 |
pCR revised to S3-223986 |
Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223381 | Evaluation for Solution #11 |
pCR revised to S3-223987 |
Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223382 | Resolving EN and evaluation for Solution #10 | pCR | Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
noted | [WTS] [JSN] |
S3-223383 | Resolving EN and evaluation for Solution #12 |
pCR revised to S3-223991 |
Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223384 | Solution for ensuring the management of bulk certificate updates |
pCR revised to S3-224139 |
Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223385 | Preliminary conclusion for KI #1 | pCR | Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-223386 | LS to GSMA DESS on SEPP certificates |
LS out LS is reply to S3-223157 LS To: GSMA revised to S3-223910 |
Nokia, Nokia Shanghai Bell | Rel-18 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | ||
S3-223387 | Address EN on PACF and MANO Communication |
pCR revised to S3-224065 |
Johns Hopkins University APL, US National Security Agency, CISA ECD | 33.848 0.14.0 | FS_SIV | Rel-16 |
S3-109 AI: 5.2 |
revised | [WTS] [JSN] |
S3-223388 | Solution for authorization in FL | pCR | Nokia, Nokia Shanghai Bell | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
not treated | [WTS] [JSN] |
S3-223389 | Resolving ENs and evaluation for Solution #7 |
pCR revised to S3-224144 |
Nokia, Nokia Shanghai Bell | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223390 | Evaluation for Solution #6 | pCR | Nokia, Nokia Shanghai Bell | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
not treated | [WTS] [JSN] |
S3-223391 | Evaluation for Solution #5 |
pCR revised to S3-224079 |
Nokia, Nokia Shanghai Bell | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223392 | Evaluation for Solution #3 |
pCR revised to S3-224145 |
Nokia, Nokia Shanghai Bell | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223393 | Address EN on Verifying Attestation Results for NRF and PACF | pCR | Johns Hopkins University APL, US National Security Agency, CISA ECD | 33.848 0.14.0 | FS_SIV | Rel-16 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] |
S3-223394 | User plane security for Non-SBA based interfaces |
CR revision of S3-221789 revised to S3-223949 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#14301 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223395 | 33.896: Updates to Key Issue on User Consent for NTN | pCR | Google Inc. | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
merged | [WTS] [JSN] |
S3-223396 | New KI: Maturity model for ZTS in 5GC | pCR | MITRE Corporation, US National Security Agency | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
noted | [WTS] [JSN] |
S3-223397 | New KI: MFA for NF in 5GC | pCR | MITRE Corporation | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
noted | [WTS] [JSN] |
S3-223398 | Revise the pre-requisite of access token request | CR | China Telecommunications | 33.501 16.12.0 CR#1490 catF | 5G_eSBA | Rel-16 |
S3-109 AI: 4.7 |
withdrawn | [WTS] [JSN] |
S3-223399 | Revise the pre-requisite of access token request(mirror) | CR | China Telecommunications | 33.501 17.7.0 CR#1491 catA | 5G_eSBA | Rel-17 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223400 | Update to solution#5 in TR 33.740 - align with SA2 |
pCR revised to S3-223970 |
China Telecom Corporation Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223401 | Update to solution#5 in TR 33.740 - remove the EN | pCR | China Telecom Corporation Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223402 | Update to solution#6 in TR 33.893 - add authorization check step | pCR | China Telecom Corporation Ltd. | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223403 | Update to solution#6 in TR 33.893 - SLPK ID usage | pCR | China Telecom Corporation Ltd. | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223404 | Revise the pre-requisite of access token request | CR | China Telecommunications | 33.501 16.12.0 CR#1492 catF | 5G_eSBA | Rel-16 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223405 | Update KI #1 Protection of Satellite Coverage Information used by 5GC/EPC | pCR | China Telecom Corporation Ltd. | 33.700-28 0.1.0 | FS_5GSAT_Sec | Rel-18 |
S3-109 AI: 5.25 |
merged | [WTS] [JSN] |
S3-223406 | Remove EN to Key Issue #2 | pCR | Johns Hopkins University APL, US National Security Agency, InterDigital, Apple, CableLabs | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
not treated | [WTS] [JSN] |
S3-223407 | Clarify the use of cross-certificates | pCR | China Telecommunications | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
not treated | [WTS] [JSN] |
S3-223408 | Clarify authorization to non-SBA interfaces | pCR | China Telecommunications | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
noted | [WTS] [JSN] |
S3-223409 | Figure CR in 6.3.3.3.2 of TS33.503 | CR | China Telecom Corporation Ltd.,CATT | 33.503 17.1.0 CR#47 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
merged | [WTS] [JSN] |
S3-223410 | Update to KI#1 | pCR | Huawei, HiSilicon | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
noted | [WTS] [JSN] |
S3-223411 | New solution to KI#1 | pCR | Huawei, HiSilicon | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223412 | Discussion on KI#1 | discussion | Huawei, HiSilicon | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
noted | [WTS] [JSN] | |
S3-223413 | Update to KI#3 | pCR | Huawei, HiSilicon | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223414 | Address EN1 on S-NSSAI mapping | CR | Huawei, HiSilicon | 33.501 17.7.0 CR#1493 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223415 | Address EN2 on AF Authorization | CR | Huawei, HiSilicon | 33.501 17.7.0 CR#1494 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
merged | [WTS] [JSN] |
S3-223416 | Address issue in NSSAA procedures for multiple registration | CR | Huawei, HiSilicon | 33.501 16.12.0 CR#1495 catF | TEI16 | Rel-16 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223417 | Address issue in NSSAA procedures for multiple registration (mirror) | CR | Huawei, HiSilicon | 33.501 17.7.0 CR#1496 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223418 | Address ENs in revocation procedures | CR | Huawei, HiSilicon | 33.256 17.1.0 CR#17 catF | ID_UAS | Rel-17 |
S3-109 AI: 4.9 |
merged | [WTS] [JSN] |
S3-223419 | Address ENs in UUAA procedures | CR | Huawei, HiSilicon | 33.256 17.1.0 CR#18 catF | ID_UAS | Rel-17 |
S3-109 AI: 4.9 |
merged | [WTS] [JSN] |
S3-223420 | Update to solution #25 | pCR | Huawei, HiSilicon | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223421 | Discussion for L2 UE-to-Network Relay Multi-Path Security | discussion | OPPO |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] | |||
S3-223422 | Adding AKMA subscription and AKMA context asynchronization threats to TR 33.926 | draftCR | ZTE Corporation | SCAS_5G_AAnF | Rel-18 |
S3-109 AI: 4.5 |
noted | [WTS] [JSN] | |
S3-223423 | Security Assurance Requirement and Test for AKMA subscription data and AKMA context synchronization | pCR | ZTE Corporation | 33.537 0.2.0 | SCAS_5G_AAnF | Rel-18 |
S3-109 AI: 4.5 |
noted | [WTS] [JSN] |
S3-223424 | Add Context_Remove into table 7.1.1-1 | CR | ZTE Corporation | 33.535 17.7.0 CR#140 catF | AKMA | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223425 | Add MnF in clause 6.6.1and 6.7 | CR | ZTE Corporation | 33.535 17.7.0 CR#141 catF | AKMA | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223426 | Add one note about AKMA subscription data and AKMA context asynchronization in clause 6.6.1 | CR | ZTE Corporation | 33.535 17.7.0 CR#142 catF | AKMA | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223427 | Add a Note to address the subscription synchronization between PAnF and UDM | CR | ZTE Corporation | 33.503 17.1.0 CR#48 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223428 | Add functionality description of PAnF |
CR revised to S3-223961 |
ZTE Corporation | 33.503 17.1.0 CR#49 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223429 | Clarification of subscription information in PAnF |
CR revised to S3-223960 |
ZTE Corporation | 33.503 17.1.0 CR#50 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223430 | Add FC Value in 33.503 | CR | ZTE Corporation | 33.503 17.1.0 CR#51 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-223431 | Allocate FC Value for 33.503 | CR | ZTE Corporation | 33.503 17.1.0 CR#52 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
withdrawn | [WTS] [JSN] |
S3-223432 | Address EN and add evaluation for solution 9 |
pCR revised to S3-224032 |
ZTE Corporation | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223433 | Address EN and update solution 3 | pCR | ZTE Corporation | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-223434 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
not treated | [WTS] [JSN] |
S3-223435 | Update the Key issue of AKMA roaming | pCR | ZTE Corporation | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
not treated | [WTS] [JSN] |
S3-223436 | Update the solution 4 | pCR | ZTE Corporation | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-223437 | Add evaluation to solution #3 | pCR | ZTE Corporation | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-223438 | Add some context to solution #3 |
pCR revised to S3-224017 |
ZTE Corporation | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223439 | Removal of Editor’s Notes of solution #3 | pCR | ZTE Corporation | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-223440 | Add conclusion to KI#2.2 | pCR | ZTE Corporation | 33.739 0.2.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223441 | Add evaluation to solution #6 | pCR | ZTE Corporation | 33.739 0.2.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223442 | Update to KI#1 providing VPLMN slice information to roaming UE | pCR | ZTE Corporation | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223443 | New solution to KI#1 protecting capability indication in UE initiated VPLMN slice-based SoR | pCR | ZTE Corporation | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223444 | New KI - User consent for application layer AIML operation | pCR | ZTE Corporation | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] |
S3-223445 | DTLS for AKMA WID |
WID new revised to S3-223959 |
ZTE Corporation | Rel-18 |
S3-109 AI: 6 |
revised | [WTS] [JSN] | ||
S3-223446 | Remove EN and Provide Evaluation for Solution #4 |
pCR revised to S3-224174 |
China Mobile (Suzhou) Software | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
revised | [WTS] [JSN] |
S3-223447 | KI for L2 UE-to-Network Relay Multi-Path Security | pCR | OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223448 | Resolving ENs in Solution #9 for Edge Security | pCR | OPPO | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223449 | Resolving ENs in Solution #10 for Edge Security | pCR | OPPO | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223450 | Resolving ENs in Solution #11 for Edge Security | pCR | OPPO | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223451 | Update to ProSe Security Sol#6 |
pCR revised to S3-223972 |
OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223452 | Address ENs in Sol#6 for ProSe Security | pCR | OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223453 | Add Evaluation for ProSe Security Sol#6 |
pCR revised to S3-224008 |
OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223454 | Reply LS on User consent for Application Detection |
LS out LS is reply to S3-223178/ S2-2209973 LS To: SA2 |
OPPO |
S3-109 AI: 3 |
merged | [WTS] [JSN] | |||
S3-223455 | Discussion Paper on evaluations and conclusions of key issue#1 | discussion | China Mobile (Suzhou) Software | Rel-18 |
S3-109 AI: 5.6 |
noted | [WTS] [JSN] | ||
S3-223456 | Adding AAnF critical assets and threats to TR 33.926 | CR | China Mobile (Suzhou) Software | 33.926 17.5.0 CR#64 catB | SCAS_5G_AAnF | Rel-18 |
S3-109 AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-223457 | Adding a test case of AKMA key strorage and update | pCR | China Mobile (Suzhou) Software | 33.537 0.2.0 | SCAS_5G_AAnF | Rel-18 |
S3-109 AI: 4.5 |
approved | [WTS] [JSN] |
S3-223458 | Adding description about overview of vendor development and product lifecycle processes and test laboratory accreditation to clause 6.1 |
pCR revised to S3-224080 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
revised | [WTS] [JSN] |
S3-223459 | Adding description about audit and accreditation of vendor development and product lifecycle processes to clause 6.2 |
pCR revised to S3-224081 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
revised | [WTS] [JSN] |
S3-223460 | Adding description about Audit and accreditation of test laboratories to clause 6.3 |
pCR revised to S3-224082 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
revised | [WTS] [JSN] |
S3-223461 | Adding description about monitoring to clause 6.4 | pCR | China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223462 | Clarifies to clause 6.3.5 to include the CP mechanism key identifier | CR | Huawei, HiSilicon | 33.503 17.1.0 CR#53 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
merged | [WTS] [JSN] |
S3-223463 | Clarifies to the match report procedures under UE-to-Network relay scenario | CR | Huawei, HiSilicon | 33.503 17.1.0 CR#54 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
merged | [WTS] [JSN] |
S3-223464 | New solution for protecting direct communnication | pCR | Huawei, HiSilicon | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223465 | New solution of security for the Ranging SL positioning device discovery | pCR | Huawei, HiSilicon | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223466 | Add conclusion to KI#1 about Direct C2 security | pCR | Huawei, HiSilicon | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
merged | [WTS] [JSN] |
S3-223467 | Add conclusion to KI#2 about DAA unicast security |
pCR revised to S3-224093 |
Huawei, HiSilicon | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
revised | [WTS] [JSN] |
S3-223468 | Add conclusion to KI#6 about Privacy for 3GPP ID in DAA | pCR | Huawei, HiSilicon | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-223469 | New solution to establish UE-to-UE security |
pCR revised to S3-223964 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223470 | Conclusion on UE-to-UE relay security |
pCR revised to S3-224095 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223471 | Conclusion on UE-to-UE relay Authorisation |
pCR revised to S3-223995 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223472 | Reply LS about Protection of URSP rules from HPLMN |
LS out LS is reply to S3-223166 source LS: S2-2207501 LS To: SA2 |
Huawei, HiSilicon | Rel-18 |
S3-109 AI: 3 |
merged | [WTS] [JSN] | ||
S3-223473 | Add conclusion to KI#4 about privacy protection over PC5 link for C2 | pCR | Huawei, HiSilicon | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
merged | [WTS] [JSN] |
S3-223474 | Add conclusion to KI#5 about DAA unicast privacy |
pCR revised to S3-224094 |
Huawei, HiSilicon | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
revised | [WTS] [JSN] |
S3-223475 | Evaluate to the solution #3 | pCR | Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
merged | [WTS] [JSN] |
S3-223476 | Evaluate to the solution #5 |
pCR revised to S3-224009 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223477 | Evaluate to the solution #15 |
pCR revised to S3-223968 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223478 | Evaluate to the solution #20 | pCR | Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
not treated | [WTS] [JSN] |
S3-223479 | Update to KI#2 |
pCR revised to S3-224159 |
Huawei, HiSilicon | 33.877 0.3.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-109 AI: 5.14 |
revised | [WTS] [JSN] |
S3-223480 | New Solution reusing exisiting mechanism for privacy protection for 5GC assistance information exposure to AF | pCR | Huawei, HiSilicon | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] |
S3-223481 | New Solution reusing existing mechanism for authorization of 5GC assistance information exposure to AF |
pCR revised to S3-223980 |
Huawei, HiSilicon | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
revised | [WTS] [JSN] |
S3-223482 | Reply LS on User Consent for EDGEAPP |
LS out LS To: CT3 revised to S3-223904 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | ||
S3-223483 | Key Issue Update on User Consent for NTN |
pCR revised to S3-224090 |
Huawei, HiSilicon, Philips International B.V., Xiaomi, Qualcomm, Apple | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
revised | [WTS] [JSN] |
S3-223484 | New solution on User Consent Architecture for RAN as enforcement point | pCR | Huawei, HiSilicon | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] |
S3-223485 | Overview of UC3S_Ph2 |
pCR revised to S3-224091 |
Huawei, HiSilicon | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
revised | [WTS] [JSN] |
S3-223486 | Conclusion for key issue #1 | pCR | Huawei, HiSilicon | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] |
S3-223487 | New WID on UC3S_Ph2 | WID new | Huawei, HiSilicon | Rel-18 |
S3-109 AI: 6 |
noted | [WTS] [JSN] | ||
S3-223488 | Address EN for solution 1 |
pCR revised to S3-224101 |
Huawei, HiSilicon | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223489 | Conclusion for key issue #2 | pCR | Huawei, HiSilicon | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
noted | [WTS] [JSN] |
S3-223490 | New solution on Reusing N3GPP authentication for NPN |
pCR revised to S3-224037 |
Huawei, HiSilicon | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
revised | [WTS] [JSN] |
S3-223491 | Reply LS on Progress and open issues for NPN enhancements in Rel-18 |
LS out LS To: SA2 |
Huawei, HiSilicon | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] | |
S3-223492 | Reply LS on the User Consent for Trace Reportings |
LS out LS To: RAN3 |
Huawei, HiSilicon | Rel-18 |
S3-109 AI: 3 |
merged | [WTS] [JSN] | ||
S3-223493 | New Test Case on UP IP policy selection in S1 Handover | other | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-223494 | New Threat on Bidding down prevention for UP IP Policy | other | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-223495 | New Test Case on Bidding down prevention for UP IP Policy | other | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-223496 | Evaluation on Solution 5 | pCR | Huawei, HiSilicon | 33.848 0.14.0 | FS_SIV | Rel-16 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] |
S3-223497 | A new solution to KI#1 | pCR | Huawei, HiSilicon | 33.877 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
not treated | [WTS] [JSN] |
S3-223498 | conclusion to KI#1 | pCR | Huawei, HiSilicon | 33.877 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
not treated | [WTS] [JSN] |
S3-223499 | Update KI#3 |
pCR revised to S3-224152 |
Huawei, HiSilicon | 33.877 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223500 | Solution to KI#3 |
pCR revised to S3-224153 |
Huawei, HiSilicon | 33.877 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223501 | Conclusion to KI#3 |
pCR revised to S3-224154 |
Huawei, HiSilicon | 33.877 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223502 | Update solution2 |
pCR revised to S3-224018 |
Huawei, HiSilicon | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223503 | update the 5.1 | pCR | Huawei, HiSilicon | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-223504 | New WID on HONTRA |
WID new revised to S3-224173 |
Huawei, HiSilicon | Rel-18 |
S3-109 AI: 6 |
revised | [WTS] [JSN] | ||
S3-223505 | conclusion on AKMA roaming |
pCR revised to S3-224136 |
Huawei, HiSilicon | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223506 | living doc to TR33.926 |
draftCR revised to S3-224155 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
revised | [WTS] [JSN] | |
S3-223507 | living doc to TR33.216 |
draftCR revised to S3-224156 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
revised | [WTS] [JSN] | |
S3-223508 | living doc to TS33.117 | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-223509 | Update requirement and add new test case to clause 4.2.3.4.3.1 | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
noted | [WTS] [JSN] | |
S3-223510 | Update requirement and add new test case to clause 4.2.3.4.3.2 | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
noted | [WTS] [JSN] | |
S3-223511 | Update KI#1 |
pCR revised to S3-224011 |
Huawei, HiSilicon | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223512 | update KI#4 | pCR | Huawei, HiSilicon | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-223513 | a new KI on TNAP mobility with full authentication | pCR | Huawei, HiSilicon | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] |
S3-223514 | address EN for solution #8 and add evaluation |
pCR revised to S3-223992 |
Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223515 | address EN for solution #9 and add evaluation |
pCR revised to S3-223993 |
Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223516 | add conclusion for KI # 6 | pCR | Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
not treated | [WTS] [JSN] |
S3-223517 | Discussion on Kiab handling in IAB migration | discussion | Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-223518 | CR on Kiab handling in IAB migration_new psk | CR | Huawei, HiSilicon | 33.501 17.7.0 CR#1497 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223519 | CR on Kiab handling in IAB migration_old psk |
CR revised to S3-223950 |
Huawei, HiSilicon | 33.501 17.7.0 CR#1498 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223520 | LS on Kiab handling in IAB migration |
LS out LS To: RAN3 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-223521 | Addressing the ENs in solution 1 |
pCR revised to S3-224063 |
Huawei, HiSilicon | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
revised | [WTS] [JSN] |
S3-223522 | Editorial change on USS authorization | CR | Huawei, HiSilicon | 33.256 17.1.0 CR#19 catF | ID_UAS | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223523 | update to key issue 1 | pCR | Huawei, HiSilicon | 33.700-28 0.1.0 | FS_5GSAT_Sec | Rel-18 |
S3-109 AI: 5.25 |
merged | [WTS] [JSN] |
S3-223524 | Editorial change to TR 33.883 | pCR | Huawei, HiSilicon | 33.883 0.3.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
approved | [WTS] [JSN] |
S3-223525 | A new solution on MOCN network sharing scenario |
pCR revised to S3-224182 |
Huawei, HiSilicon | 33.883 0.3.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
revised | [WTS] [JSN] |
S3-223526 | A new solution on TMGI protection | pCR | Huawei, HiSilicon | 33.883 0.3.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
noted | [WTS] [JSN] |
S3-223527 | CR on control-plane procedure in MBS |
CR revised to S3-223917 |
Huawei, HiSilicon | 33.501 17.7.0 CR#1499 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223528 | Reply LS on the impact of MSK update on MBS multicast session update procedure |
LS out LS is reply to S3-223172 source LS: S2-2209287 LS To: SA2 revised to S3-223918 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] | ||
S3-223529 | CR on authentication in user plane procedure in MBS |
CR revised to S3-223920 |
Huawei, HiSilicon | 33.501 17.7.0 CR#1500 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223530 | Reply LS on Security architecture for 5G multicast/broadcast services |
LS out LS is reply to S3-223164 source LS: S2-2207390 LS To: SA2 revised to S3-223919 |
Huawei, HiSilicon | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] | |
S3-223531 | Addressing the editor's note in sol#1 |
pCR revised to S3-223982 |
Huawei, HiSilicon | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
revised | [WTS] [JSN] |
S3-223532 | Adding an editor's note to sol#3 | pCR | Huawei, HiSilicon | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223533 | Editorial changes to the living document for MnF SCAS |
other revised to S3-224121 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-109 AI: 4.1 |
revised | [WTS] [JSN] | |
S3-223534 | New WID on security assurance methodology enhancements | WID new | Huawei, HiSilicon | Rel-18 |
S3-109 AI: 6 |
noted | [WTS] [JSN] | ||
S3-223535 | Discussion | discussion | Huawei, HiSilicon | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
withdrawn | [WTS] [JSN] | |
S3-223536 | Evaluation of tenet 4 on resource access | pCR | Huawei, HiSilicon | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
noted | [WTS] [JSN] |
S3-223537 | Update | pCR | Huawei, HiSilicon | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
withdrawn | [WTS] [JSN] |
S3-223538 | Updates to evaluation of tenet 6 | pCR | Huawei, HiSilicon | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
noted | [WTS] [JSN] |
S3-223539 | Updates to evaluation of tenet 7 | pCR | Huawei, HiSilicon | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
merged | [WTS] [JSN] |
S3-223540 | Updates to solution 3 based on pseudonyms |
pCR revised to S3-224134 |
Huawei, HiSilicon | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
revised | [WTS] [JSN] |
S3-223541 | Updates to clause 4.2 of MnF SCAS | pCR | Huawei, HiSilicon | 33.526 0.3.0 | SCAS_5G_MF | Rel-18 |
S3-109 AI: 4.1 |
approved | [WTS] [JSN] |
S3-223542 | Conclusion on KI#1 and KI#2 in TR 33.741 | pCR | Huawei, HiSilicon | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
merged | [WTS] [JSN] |
S3-223543 | Update to solution #3 |
pCR revised to S3-223994 |
Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223544 | Policy based certificate update/renewal |
pCR revised to S3-224140 |
Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223545 | Conclusion on KI#2.5:Authentication and Authorization between AC and EEC | pCR | Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] |
S3-223546 | Addressing the ENs in solution 15 | pCR | Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223547 | Addressing the ENs in solution 16 | pCR | Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223548 | Evaluation to solution 15 | pCR | Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223549 | Evaluation to solution 16 | pCR | Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223550 | Updates to evalution of solution 2 | pCR | Huawei, HiSilicon | 33.892 0.3.0 | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
noted | [WTS] [JSN] |
S3-223551 | Evaluation to solution 18 |
pCR revised to S3-224028 |
Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
revised | [WTS] [JSN] |
S3-223552 | Update to UE-to-Network relay security procedures | CR | Huawei, HiSilicon | 33.503 17.1.0 CR#55 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
merged | [WTS] [JSN] |
S3-223553 | Adding description about SCAS instantiation documents creation to clause 7.1 | pCR | China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223554 | Adding description about network product development process and network product lifecycle management to clause 7.2 | pCR | China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223555 | Adding description about SCAS instantiation evaluation overview to clause 7.2 | pCR | China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223556 | Adding description about content and process of SCAS instantiation evaluation to clause 7.2 |
pCR revised to S3-224083 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
revised | [WTS] [JSN] |
S3-223557 | Allocate FC Value for 33.503 |
CR revised to S3-224171 |
ZTE Corporation | 33.220 17.3.0 CR#219 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223558 | Access to localized services using existing mechanisms |
pCR revised to S3-224043 |
Intel | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
revised | [WTS] [JSN] |
S3-223559 | Access to localized services using AKMA mechanisms | pCR | Intel | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] |
S3-223560 | FL GROUP AUTHORIZATION OF NWDAF(S) IN 5GC | pCR | Intel | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
not treated | [WTS] [JSN] |
S3-223561 | Policy-based C-RNTI and TMSI refresh | pCR | Intel | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
not treated | [WTS] [JSN] |
S3-223562 | Guidance for Enforcing User Consent |
pCR revised to S3-224092 |
Huawei, HiSilicon | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
revised | [WTS] [JSN] |
S3-223563 | Updates to solution 2: remove EN E2E protection |
pCR revised to S3-224147 |
Intel | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223564 | Adding description about testing to clause 7.2 | pCR | China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223565 | Conclusion for key issue #2 | pCR | Huawei, HiSilicon | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] |
S3-223566 | LS on User Consent for Roaming |
LS out LS To: SA2 |
Huawei, HiSilicon | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] | ||
S3-223567 | Living document for MnF SCAS |
draftCR revised to S3-224122 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-109 AI: 4.1 |
revised | [WTS] [JSN] | |
S3-223568 | New SID on 5G Per-QoS Flow User Plane Security Control | SID new | Intel, Samsung | Rel-18 |
S3-109 AI: 6 |
noted | [WTS] [JSN] | ||
S3-223569 | SCAS process enhancements | CR | Huawei, HiSilicon | 33.916 17.0.0 CR#11 catB | DUMMY | Rel-18 |
S3-109 AI: 6 |
not pursued | [WTS] [JSN] |
S3-223570 | Need for Rel-18 study on UP security enhancement | discussion | Intel, Samsung |
S3-109 AI: 6 |
noted | [WTS] [JSN] | |||
S3-223571 | Updates to clause 4.3 of MnF SCAS |
pCR revised to S3-224123 |
Huawei, HiSilicon | 33.526 0.3.0 | SCAS_5G_MF | Rel-18 |
S3-109 AI: 4.1 |
revised | [WTS] [JSN] |
S3-223572 | Adding description about self-declaration to clause 7.3 | pCR | China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223573 | CR on Remote UE Authorization check before using 5GPRUK generate KNR_ProSe | CR | Huawei, HiSilicon | 33.503 17.1.0 CR#56 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223574 | draft_Reply LS to Progress and open issues for NPN enhancements in Rel-18 |
LS out LS is reply to S3-223175 LS To: SA2 |
Intel |
S3-109 AI: 5.16 |
merged | [WTS] [JSN] | |||
S3-223575 | Adding contents into clause 7.5 and 7.6 | pCR | China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223576 | Solution on prevention of URSP rule misuse by a non-genuine application using home network anchor |
pCR revised to S3-224177 |
Intel | 33.892 0.3.0 | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
revised | [WTS] [JSN] |
S3-223577 | Update of KI #1 | pCR | THALES | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
noted | [WTS] [JSN] |
S3-223578 | Resolution of EN in solution #8 | pCR | THALES, Qualcomm Incorporated | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
not treated | [WTS] [JSN] |
S3-223579 | Resolution of ENs in solution #14 |
pCR revised to S3-224115 |
THALES | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223580 | Update of LI requirements on solution #5 |
pCR revised to S3-224057 |
LG Electronics France | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223581 | Update of LI requirements on solution #12 |
pCR revised to S3-224058 |
LG Electronics France | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223582 | Discussion on IMS SCAS status | discussion | Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-223583 | LS on IMS SCAS to GSMA |
LS out LS To: GSMA NESASG revised to S3-223934 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] | ||
S3-223584 | Reply LS on Network federation interface for Telco edge consideration |
LS out LS To: 3GPP SA6, 3GPP SA2, 3GPP SA5, 3GPP SA revised to S3-223914 |
Huawei, HiSilicon | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | |
S3-223585 | Conclusion on KI2.3 Authentication and Authorization between V-ECS and H-ECS |
pCR revised to S3-224023 |
Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
revised | [WTS] [JSN] |
S3-223586 | Conclusion on KI2.2 Authentication mechanism selection |
pCR revised to S3-223939 |
Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
revised | [WTS] [JSN] |
S3-223587 | Conclusion on KI1.1 How to authorize PDU session to support local traffic routing to access an EHE in the VPLMN | pCR | Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] |
S3-223588 | Addressing authentication and authorization for EDGE-9 | CR | Huawei, HiSilicon | 33.558 17.2.0 CR#8 catF | eEDGE_5GC | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223589 | New WID on Security Aspects of Enhancement of Support for Edge Computing in 5GC — phase 2 | WID new | Huawei, HiSilicon | Rel-18 |
S3-109 AI: 6 |
noted | [WTS] [JSN] | ||
S3-223590 | Discussion on notification URI disclosure in "Subscribe-Notify" scenarios | discussion | Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.7 |
noted | [WTS] [JSN] | ||
S3-223591 | LS on notification URI disclosure |
LS out LS To: CT4 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.7 |
noted | [WTS] [JSN] | ||
S3-223592 | Conclusion on KI#1 | pCR | Huawei, HiSilicon | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
merged | [WTS] [JSN] |
S3-223593 | Solution for authorization negotiation with bootstrapping mechanism | pCR | Huawei, HiSilicon | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-223594 | Conclution on KI#7 |
pCR revised to S3-224104 |
Huawei, HiSilicon | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223595 | LS on authorization negotiation | pCR | Huawei, HiSilicon | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
noted | [WTS] [JSN] |
S3-223596 | Removing EN in KI#3 | pCR | Huawei, HiSilicon | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
merged | [WTS] [JSN] |
S3-223597 | EN addressing for solution#2 |
pCR revised to S3-224157 |
Huawei, HiSilicon | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
revised | [WTS] [JSN] |
S3-223598 | Adding conclusion to KI#3 | pCR | Huawei, HiSilicon | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
noted | [WTS] [JSN] |
S3-223599 | New solution to KI#2 |
pCR revised to S3-224158 |
Huawei, HiSilicon | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
revised | [WTS] [JSN] |
S3-223600 | Discussion on way forward for KI#1 | discussion | Huawei, HiSilicon | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
noted | [WTS] [JSN] | |
S3-223601 | Adding conclusion to KI#1 | pCR | Huawei, HiSilicon | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
noted | [WTS] [JSN] |
S3-223602 | Clarification on TC_ IP_MULTICAST_HANDLING | CR | Huawei, HiSilicon | 33.117 16.8.0 CR#91 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223603 | Clarification on TC_ IP_MULTICAST_HANDLING | CR | Huawei, HiSilicon | 33.117 17.1.0 CR#92 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223604 | Clarification on IP_FWD_DISABLING |
CR revised to S3-223929 |
Huawei, HiSilicon | 33.117 16.8.0 CR#93 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223605 | Clarification on IP_FWD_DISABLING |
CR revised to S3-223930 |
Huawei, HiSilicon | 33.117 17.1.0 CR#94 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223606 | clarification on PLMN ID verification in SNPN |
CR revised to S3-223941 |
Huawei, HiSilicon | 33.501 17.7.0 CR#1501 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223607 | add test case to include SNPN snenario in PLMNID verification | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
noted | [WTS] [JSN] | |
S3-223608 | New solution on boot time attestation at 3GPP function level | pCR | Huawei, HiSilicon | 33.848 0.14.0 | FS_SIV | Rel-16 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] |
S3-223609 | Reply LS on autentication result removal |
LS out LS To: CT4 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 3 |
merged | [WTS] [JSN] | ||
S3-223610 | Discussion paper on way forward for conclusion | discussion | Huawei, HiSilicon | FS_HN_Auth |
S3-109 AI: 5.7 |
noted | [WTS] [JSN] | ||
S3-223611 | A new solution on TNAP mobility with full authentication | pCR | Huawei, HiSilicon | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] |
S3-223612 | LS to inform about the new GSMA Task Force |
LS in LS reply in S3-223916, S3-223916 |
GSMA |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223613 | SERP - LS on security protection on RRCResumeRequest message |
LS out LS To: RAN, RAN2, RAN3 |
Apple | Rel-18 |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-223614 | 5GFBS - Addressing UE bahaviors on signature verification | pCR | Apple | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223615 | 5GFBS - Reply LS on authenticity and replay protection of system information |
LS out LS To: RAN2 |
Apple | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] | ||
S3-223616 | MEC - New key issue on AF specific identifier |
pCR revised to S3-224012 |
Apple | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
revised | [WTS] [JSN] |
S3-223617 | MEC- Addressing the EN#1 in solution#7 | pCR | Apple | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223618 | MEC- Addressing the EN#2 in solution#7 on default authentication mechanism | pCR | Apple | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223619 | CR on AES-GCM/GMAC in IMS SIP security |
CR revised to S3-223925 |
Apple | 33.203 17.1.0 CR#266 catC | eCryptPr | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223620 | Reply LS on user’s consent for EDGEAPP (S3-223149) |
LS out LS To: CT3 |
Apple | Rel-17 |
S3-109 AI: 3 |
merged | [WTS] [JSN] | ||
S3-223621 | Reply LS on the user consent for trace reporting (S3-223162) |
LS out LS To: RAN3 |
Apple | Rel-17 |
S3-109 AI: 3 |
merged | [WTS] [JSN] | ||
S3-223622 | LS on impact of URSP rule enforcement report to 5GC (S3-223173) |
LS out LS To: SA2 |
Apple | Rel-18 |
S3-109 AI: 3 |
merged | [WTS] [JSN] | ||
S3-223623 | New KI: Support for Emergency service over UE-to-Network Relaying |
pCR revised to S3-223996 |
Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223624 | Support Emergency Service over UE-to-Network Relay |
pCR revised to S3-224005 |
Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223625 | [Draft] LS on ProSe Secondary Authentication |
LS out LS To: SA2 |
Ericsson | PROSESA | Rel-18 |
S3-109 AI: 5.3 |
not treated | [WTS] [JSN] | |
S3-223626 | Evaluation to solution #3 |
pCR revised to S3-223973 |
Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223627 | Evaluation to solution #4 | pCR | Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223628 | Resolve EN of U2U determination in target UE in Solution3 | pCR | Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223629 | Resolve EN of Direct Communication Invite in Solution3 |
pCR revised to S3-224002 |
Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223630 | New solution with authorization tokens exchanged after PC5 security establishment | pCR | Ericsson | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223631 | User consent clarification | CR | Ericsson | 33.501 17.7.0 CR#1502 catF | UC3S_SEC | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223632 | Adding description about partial compliance and use of SECAM requirements in network product development cycle to clause 7.4 |
pCR revised to S3-224084 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
revised | [WTS] [JSN] |
S3-223633 | Adding missing content from last implementation | pCR | China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223634 | Adding clause 4.4 in TR 33.927 |
pCR revised to S3-224085 |
China Mobile (Suzhou) Software | 33.927 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
revised | [WTS] [JSN] |
S3-223635 | Central authorization for user consent handling | pCR | Nokia, Nokia Shanghai Bell | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
approved | [WTS] [JSN] |
S3-223636 | pCR to TR33.740 Update Solution16 for removing ENs |
pCR revised to S3-223974 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223637 | Adding clause 5 Generic assets and threats in TR 33.927 | pCR | China Mobile (Suzhou) Software | 33.927 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-223638 | pCR to TR33.740 Update Solution17 for removing ENs |
pCR revised to S3-224003 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223639 | KI and Solution on user consent in roaming | pCR | Nokia, Nokia Shanghai Bell | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] |
S3-223640 | Adding clause 6 in TR 33.927 |
pCR revised to S3-224086 |
China Mobile (Suzhou) Software | 33.927 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
revised | [WTS] [JSN] |
S3-223641 | pCR to TR33.740 Update Solution18 for removing ENs | pCR | CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
not treated | [WTS] [JSN] |
S3-223642 | Proposal to add 4.1 in TS33.527 | pCR | China Mobile (Suzhou) Software | 33.527 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
noted | [WTS] [JSN] |
S3-223643 | pCR to TR33.740 Evaluation of Solution16 |
pCR revised to S3-223975 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223644 | pCR to TR33.740 Evaluation of Solution17 |
pCR revised to S3-224004 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223645 | Add conclusion to key issue #1 | pCR | China Mobile (Suzhou) Software | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
noted | [WTS] [JSN] |
S3-223646 | Rel-15 Correcting the OAuth 2.0 roles in CAPIF |
CR revised to S3-223922 |
Ericsson | 33.122 15.3.0 CR#31 catF | CAPIF-Sec | Rel-15 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223647 | Rel-16 Correcting the OAuth 2.0 roles in CAPIF |
CR revised to S3-223923 |
Ericsson | 33.122 16.3.0 CR#32 catA | CAPIF-Sec | Rel-16 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223648 | Rel-17 Correcting the OAuth 2.0 roles in CAPIF |
CR revised to S3-223924 |
Ericsson | 33.122 17.0.0 CR#33 catA | CAPIF-Sec | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223649 | [DRAFT] Reply LS on user’s consent for EDGEAPP |
LS out LS is reply to C3-223780 LS To: CT3 |
Ericsson | eEDGE_5GC | Rel-17 |
S3-109 AI: 3 |
merged | [WTS] [JSN] | |
S3-223650 | Correction and clarification in user consent requirements | CR | Ericsson | 33.558 17.2.0 CR#9 catF | eEDGE_5GC | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223651 | A new solution for EEC authentication | pCR | Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223652 | Updating solution #17 | pCR | Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223653 | Resolving ENs in solution #13 |
pCR revised to S3-224025 |
Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
revised | [WTS] [JSN] |
S3-223654 | Evaluation of solution #13 |
pCR revised to S3-224026 |
Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
revised | [WTS] [JSN] |
S3-223655 | Evaluation of solution #14 |
pCR revised to S3-224027 |
Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
revised | [WTS] [JSN] |
S3-223656 | Evaluation of solution #17 | pCR | Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223657 | Authorization of AI/ML model sharing between different vendors and usage of one-time URLs |
pCR revised to S3-224148 |
Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223658 | A solution for authorization before allowing access to resources | pCR | Ericsson | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223659 | pCR to TR33.740 Evaluation of Solution18 | pCR | CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
not treated | [WTS] [JSN] |
S3-223660 | Add evaluation to Solution #8 |
pCR revised to S3-224077 |
China Mobile (Suzhou) Software | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223661 | pCR to TR33.740 Update Abbreviations | pCR | CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223662 | SECOP correction |
CR revised to S3-223942 |
Nokia, Nokia Shanghai Bell | 33.310 17.4.0 CR#137 catA | TEI17 | Rel-18 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223663 | New solution on protection of data and analytics exchange in roaming case using Secure Multi-party Computation |
pCR revised to S3-224075 |
China Mobile (Suzhou) Software | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223664 | pCR to TR33.740 Solution for U2U Relay discovery message security |
pCR revised to S3-223965 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223665 | Update to solution#8 |
pCR revised to S3-224076 |
China Mobile (Suzhou) Software | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223666 | pCR to TR33.740 Conclusion of key issue #1 | pCR | CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223667 | pCR to TR33.740 Conclusion of key issue #3 | pCR | CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223668 | Solution to KI#1 – NSWO in SNPN | pCR | Ericsson | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-223669 | Removal of ENs in Sol#3 | pCR | Ericsson | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-223670 | Conclusions for KI#1 | pCR | Ericsson | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] |
S3-223671 | CR to TS33.503 PAnF definition and reference point to UDM | CR | CATT | 33.503 17.1.0 CR#57 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
merged | [WTS] [JSN] |
S3-223672 | Editor's note resolution on NF instance id in cert profile | CR | Nokia, Nokia Shanghai Bell | 33.310 17.4.0 CR#138 catF | 5G_eSBA, TEI17 | Rel-17 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223673 | New WID on Security Aspects of Proximity-based Services in 5GS Phase 2 | WID new | CATT | Rel-18 |
S3-109 AI: 6 |
noted | [WTS] [JSN] | ||
S3-223674 | Adding AAnF critical assets and threats to TR 33.926 | draftCR | China Mobile (Suzhou) Software | SCAS_5G_AAnF | Rel-18 |
S3-109 AI: 4.5 |
approved | [WTS] [JSN] | |
S3-223675 | Conclusion for KI#1 case 2 |
pCR revised to S3-224137 |
China Mobile (Suzhou) Software | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223676 | Discussion paper on SEPP inter-domain certificate on N32 interface | discussion | Ericsson | Rel-18 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | ||
S3-223677 | Correct SCP certificate profile | CR | Ericsson | 33.310 16.11.0 CR#139 catF | 5G_eSBA | Rel-16 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223678 | Correct SCP certificate profile | CR | Ericsson | 33.310 17.4.0 CR#140 catA | 5G_eSBA | Rel-17 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223679 | Clarify SEPP intra-domain certificate profile | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.310 16.11.0 CR#141 catF | 5G_eSBA | Rel-16 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223680 | Clarify SEPP intra-domain certificate profile | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.310 17.4.0 CR#142 catA | 5G_eSBA | Rel-17 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223681 | Correct NF certificate profile | CR | Ericsson | 33.310 17.4.0 CR#143 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223682 | SEPP to include and verify the source PLMN-ID |
CR revision of S3-221998 revised to S3-223953 |
Ericsson, Mavenir, Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#1503 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
revised | [WTS] [JSN] |
S3-223683 | SEPP to include and verify the source PLMN-ID |
draftCR revision of S3-221998 |
Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
noted | [WTS] [JSN] | |
S3-223684 | Clarification on access token requests for NF Producers of a specific NF type and token-based authorization for indirect communication with delegated discovery |
CR revised to S3-223954 |
Ericsson | 33.501 17.7.0 CR#1504 catB | DUMMY | Rel-18 |
S3-109 AI: 4.7 |
revised | [WTS] [JSN] |
S3-223685 | Aligning DNS and ICMP security for non-3GPP access with 3GPP access | CR | Ericsson | 33.402 17.0.0 CR#147 catF | TEI18 | Rel-18 |
S3-109 AI: 4.9 |
endorsed | [WTS] [JSN] |
S3-223686 | Reply LS on User consent for Application Detection |
LS out LS To: SA2 revised to S3-223907 |
Ericsson | Rel-18 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | ||
S3-223687 | New solution for KI#2 to support authorization of participant NWDAFs in FL | pCR | Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
not treated | [WTS] [JSN] |
S3-223688 | Update of Key Issue #3 "Security for AI/ML model storage and sharing" on authorization by the NF which generated the AI/ML model | pCR | Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-223689 | Solution on Token based Authorization of AI/ML Model sharing between different vendors(ADRF) |
pCR revised to S3-224149 |
Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223690 | Solution on Authorization of AI/ML Model sharing between different vendors(MTLF) |
pCR revised to S3-224150 |
Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223691 | New solution for KI#3 to support authorization of AI/ML model sharing By NWDAF containing MTLF(local auth) |
pCR revised to S3-224151 |
Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
revised | [WTS] [JSN] |
S3-223692 | Security aspects of Support for enhanced mobility by enabling support for idle and connected mode mobility between SNPNs without new network selection | pCR | Ericsson | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] |
S3-223693 | New Solution to KI#2: Authentication for UE access to hosting network |
pCR revised to S3-224044 |
Ericsson | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
revised | [WTS] [JSN] |
S3-223694 | Preliminary conclusions to KI#2: Authentication for UE access to hosting network | pCR | Ericsson | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] |
S3-223695 | Update of Key Issue #3: Service access authorization in the "Subscribe-Notify" scenarios | pCR | Ericsson | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
merged | [WTS] [JSN] |
S3-223696 | Evaluation for Solution #21 "Certificate solution for NRF validation of NFc for access token requests" | pCR | Ericsson | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
not treated | [WTS] [JSN] |
S3-223697 | Evaluation and update for Solution #22 "Combined certificate and profile solution for NRF validation of NFc for access token requests" | pCR | Ericsson | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
not treated | [WTS] [JSN] |
S3-223698 | Discussion. Key issue #12: Security in Hosted SEPP scenarios | discussion | Ericsson | Rel-18 |
S3-109 AI: 5.24 |
not treated | [WTS] [JSN] | ||
S3-223699 | Update of Key issue #12: Security in Hosted SEPP scenarios | pCR | Ericsson | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
not treated | [WTS] [JSN] |
S3-223700 | Solution for KI#12: Security in Hosted SEPP scenarios | pCR | Ericsson | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
not treated | [WTS] [JSN] |
S3-223701 | New WID on Security aspects of enhanced support of Non-Public Networks phase 2 | WID new | Ericsson | Rel-18 |
S3-109 AI: 6 |
noted | [WTS] [JSN] | ||
S3-223702 | Correction to authentication mechanism selection |
CR revised to S3-224161 |
Ericsson, Xiaomi | 33.503 17.1.0 CR#58 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223703 | Renaming 5GPRUK, 5GPRUK ID, PRUK and PRUK ID |
CR revised to S3-223956 |
Ericsson | 33.503 17.1.0 CR#59 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223704 | Correcting the handling of synchronisation error |
CR revised to S3-224133 |
Ericsson | 33.503 17.1.0 CR#60 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223705 | Nudm servcie operation correction |
CR revised to S3-223962 |
Ericsson | 33.503 17.1.0 CR#61 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223706 | CP-PRUK refresh | CR | Ericsson | 33.503 17.1.0 CR#62 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-223707 | Clarification to multiple registrations in different PLMNs\access types | CR | Ericsson | 33.501 17.7.0 CR#1505 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223708 | LS on Evaluation of Digital Signature schemes for the false base station study |
LS out LS To: ETSI SAGE |
Oy LM Ericsson AB | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] | ||
S3-223709 | TargetNFServiceSetId to be part of access token claims |
CR revision of S3-221840 revised to S3-223955 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#14341 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
revised | [WTS] [JSN] |
S3-223710 | Trust in service mesh and standalone SCP implementations |
pCR revised to S3-224183 |
Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223711 | AAnF sending GPSI to internal AKMA AF | CR | China Mobile (Suzhou) Software | 33.535 17.7.0 CR#143 catF | AKMA | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223712 | Trust in inter-PLMN communication | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-223713 | Conclusion on KI1 | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
merged | [WTS] [JSN] |
S3-223714 | KI3 update Subscribe-Notify – EN resolution |
pCR revised to S3-223985 |
Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223715 | Key Issue on KAF refresh | pCR | Samsung, Nokia, Nokia Shanghai Bell, OPPO, ZTE | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
noted | [WTS] [JSN] |
S3-223716 | New solution on AKMA KAF refresh | pCR | Samsung | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
not treated | [WTS] [JSN] |
S3-223717 | Resolving EN and adding evaluation for solution#13 |
pCR revised to S3-224030 |
Samsung | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223718 | Resolving EN and adding evaluation for solution#9 | pCR | Samsung | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-223719 | Resolving EN and adding evaluation for solution#6 |
pCR revised to S3-224019 |
Samsung | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223720 | Conclusion on KI#1 | pCR | Samsung | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
merged | [WTS] [JSN] |
S3-223721 | Key Issue for secure ProSe multi-path transmission for UE-to-Network relay | pCR | Samsung | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223722 | New solution for hop-by-hop security establishment for the UE-to-UE Relay |
pCR revised to S3-223966 |
Samsung | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223723 | Updates to solution#19 and resolving EN #2 and #3 | pCR | Samsung | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223724 | Updates to solution#19 and resolving EN #5 |
pCR revised to S3-223976 |
Samsung | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223725 | Resolving EN in solution#4 | pCR | Samsung | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223726 | Resolving EN in solution#3 | pCR | Samsung | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223727 | Resolving EN and adding evaluation for solution#21 | pCR | Samsung | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223728 | Discussion paper on authentication mechanism selection | discussion | Samsung | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
noted | [WTS] [JSN] | |
S3-223729 | Conclusion for KI#2.2 | pCR | Samsung | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223730 | Living document for SERP: draftCR to TS 33.501 on the Protection of the RRC Resume Request message | CR | Samsung | 33.501 17.7.0 CR#1506 catC | SERP | Rel-18 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223731 | Reply LS on authenticity and replay protection of system information |
LS out LS is reply to S3-223161 LS To: RAN2 |
Samsung, Apple, CableLabs | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] | |
S3-223732 | Conclusion for key issue#2 | pCR | Samsung, Intel, Apple | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
noted | [WTS] [JSN] |
S3-223733 | Updates to Solution#7 SI verification using Digital Signatures | pCR | Samsung | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223734 | Resolving EN of solution#7 (TR 33.809) | pCR | Samsung | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223735 | [IAB] IAB inter-CU topology adaptation procedure | CR | Samsung | 33.501 17.7.0 CR#1507 catB | TEI18 | Rel-18 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223736 | [MBS] Updates to solution#1 in TR 33.883 | pCR | Samsung | 33.883 0.3.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
noted | [WTS] [JSN] |
S3-223737 | [MBS] Conclusion for Key Issue#1 | pCR | Samsung | 33.883 0.3.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
noted | [WTS] [JSN] |
S3-223738 | New Solution on User Authorization in API Invocation | pCR | Samsung | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223739 | New Solution on Resource owner Authorization in API Invocation using AKMA | pCR | Samsung | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223740 | Discussion on protection of the URSP rules from HPLMN | discussion | Samsung | TEI18 | Rel-18 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |
S3-223741 | KI4 Sol SCP authorization check by NRF |
pCR revision of S3-222809 revised to S3-224070 |
Nokia, Nokia Shanghai Bell | 33.875 1.3.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223742 | DDNFM Selection during U2N Relay Discovery Security Procedure | CR | Xiaomi Technology, Ericsson | 33.503 17.1.0 CR#63 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223743 | Match Report in U2N Relay Discovery Security Procedure |
CR revised to S3-223958 |
Xiaomi Technology | 33.503 17.1.0 CR#64 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
revised | [WTS] [JSN] |
S3-223744 | Security Method Check during U2N Relay Discovery Procedure | CR | Xiaomi Technology | 33.503 17.1.0 CR#65 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223745 | Updates to Key Definitions | CR | Xiaomi Technology | 33.503 17.1.0 CR#66 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223746 | 33.893: Additional Roles for Authorization in KI#2 |
pCR revised to S3-224128 |
Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
revised | [WTS] [JSN] |
S3-223747 | 33.893: Update to Key Issue #4 | pCR | Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
approved | [WTS] [JSN] |
S3-223748 | 33.893: Resolve the Editor’s Notes in Solution #2 | pCR | Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
approved | [WTS] [JSN] |
S3-223749 | 33.893: Resolve the Editor’s Note in Solution #4 | pCR | Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223750 | 33.893: Evaluation for Solution #4 | pCR | Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223751 | 33.893: Evaluation for Solution #6 | pCR | Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223752 | 33.893: New Solution on Security Policy based Protection for Ranging Communication |
pCR revised to S3-224130 |
Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
revised | [WTS] [JSN] |
S3-223753 | 33.893: New Solution on Security Policy based Protection for Ranging Result sent to SL Positioning Client UE |
pCR revised to S3-224131 |
Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
revised | [WTS] [JSN] |
S3-223754 | 33.893: New Solution on Authorization of SL Positioning Client UE for Obtaining Ranging Result | pCR | Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223755 | 33.893: New Solution on Token-based Authorization of the Role of the UE during Discovery | pCR | Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223756 | 33.893: New Solution on Role Verification during Discovery based on Discovery Keys | pCR | Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223757 | 33.896: Update to Solution #1 | pCR | Xiaomi Technology | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
approved | [WTS] [JSN] |
S3-223758 | 33.896: Update to Solution #2 | pCR | Xiaomi Technology | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
approved | [WTS] [JSN] |
S3-223759 | 33.896: Solution on Obtaining User Consent with Mobility in RAN for KI#2 | pCR | Xiaomi Technology | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] |
S3-223760 | 33.896: Solution on Obtaining User Consent with Mobility in SN for KI#2 | pCR | Xiaomi Technology | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] |
S3-223761 | 33.700-28: Update to Key Issue #1 |
pCR revised to S3-224072 |
Xiaomi Technology | 33.700-28 0.1.0 | FS_5GSAT_Sec | Rel-18 |
S3-109 AI: 5.25 |
revised | [WTS] [JSN] |
S3-223762 | 33.700-28: New Key Issue on Protection of UE Unreachability Period retrieved by the UE | pCR | Xiaomi Technology | 33.700-28 0.1.0 | FS_5GSAT_Sec | Rel-18 |
S3-109 AI: 5.25 |
noted | [WTS] [JSN] |
S3-223763 | Update to solution #8 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
not treated | [WTS] [JSN] |
S3-223764 | Update to solution #9 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
not treated | [WTS] [JSN] |
S3-223765 | Update to solution #20 in TR 33.740 |
pCR revised to S3-223977 |
Beijing Xiaomi Mobile Software | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223766 | New solution on security for discovery integrated into PC5 link establishment |
pCR revised to S3-223967 |
Beijing Xiaomi Mobile Software | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
revised | [WTS] [JSN] |
S3-223767 | New solution on Ranging/SL Positioning discovery and link establishment procedure for V2X capable UEs | pCR | Beijing Xiaomi Mobile Software | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
not treated | [WTS] [JSN] |
S3-223768 | Update to solution #7 in TR 33.741 | pCR | Beijing Xiaomi Mobile Software | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-223769 | Conclusion on KI#1 | pCR | Beijing Xiaomi Mobile Software | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
merged | [WTS] [JSN] |
S3-223770 | New solution on User Consent for UE Data Exposure to HPLMN in the Roaming case | pCR | Beijing Xiaomi Mobile Software | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
approved | [WTS] [JSN] |
S3-223771 | New solution on User Consent for UE Data Exposure to VPLMN in the Roaming case | pCR | Beijing Xiaomi Mobile Software | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
approved | [WTS] [JSN] |
S3-223772 | Correction to privacy protection of UP-PRUK ID and RSC in DCR | CR | Beijing Xiaomi Mobile Software | 33.503 17.1.0 CR#67 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
merged | [WTS] [JSN] |
S3-223773 | CR_33.501 R15 Update A.18 to define SoR-XMAC-IUE | CR | Xiaomi Communication | 33.501 15.16.0 CR#1508 catF | TEI15 | Rel-15 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223774 | CR_33.501 R15 Update A.20 to define UPU-XMAC-IUE | CR | Xiaomi Communication | 33.501 15.16.0 CR#1509 catD | TEI15 | Rel-15 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223775 | CR_33.501 R16 Update A.18 to define SoR-XMAC-IUE (mirror) | CR | Xiaomi Communication | 33.501 16.12.0 CR#1510 catA | TEI15 | Rel-16 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223776 | CR_33.501 R16 Update A.20 to define UPU-XMAC-IUE (mirror) | CR | Xiaomi Communication | 33.501 16.12.0 CR#1511 catD | TEI16 | Rel-16 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223777 | CR_33.501 R17 Remove the redundant part of Figure I.2.3.2-1 | CR | Xiaomi Communication | 33.501 17.7.0 CR#1512 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223778 | CR_33.501 R17 Update A.17 for SoR transparent container |
CR revised to S3-223936 |
Xiaomi Communication | 33.501 17.7.0 CR#1513 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223779 | CR_33.501 R17 Update A.18 to define SoR-XMAC-IUE (mirror) |
CR revised to S3-223935 |
Xiaomi Communication | 33.501 17.7.0 CR#1514 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223780 | CR_33.501 R17 Update A.20 to define UPU-XMAC-IUE (mirror) |
CR revised to S3-223937 |
Xiaomi Communication | 33.501 17.7.0 CR#1515 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223781 | CR_33.501 R17 Update step 15 of clause I.2.2.2.1 | CR | Xiaomi Communication | 33.501 17.7.0 CR#1516 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223782 | CR_33.501 R17 Update Subscription and unsubscription procedure of NSACF notification service | CR | Xiaomi Communication | 33.501 17.7.0 CR#1517 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
merged | [WTS] [JSN] |
S3-223783 | KI #1, New Sol on UE profile based 5GC assistance information exposure authorization |
pCR revised to S3-223981 |
Xiaomi Communication | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
revised | [WTS] [JSN] |
S3-223784 | KI #2.2, New sol on authentication mechanism selection method for edge scenarios | pCR | Xiaomi Communication | 33.739 0.2.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223785 | KI#1 New sol AKMA roaming for external AF in the Data Network |
pCR revised to S3-224071 |
Xiaomi Communication | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223786 | KI#1 New sol on enhanced slice aware information protection | pCR | Xiaomi Communication | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223787 | KI#1 New sol on Integrity protection for network triggered UE capability indication procedure. | pCR | Xiaomi Communication | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223788 | KI#1 New sol on Integrity protection for UE initiated capability indication procedure | pCR | Xiaomi Communication | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223789 | KI#2 New sol Mutual authentication between UE and hosting network | pCR | Xiaomi Communication | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] |
S3-223790 | KI#2, New Sol OAuth 2.0 based API invocation procedure | pCR | Xiaomi Communication | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223791 | KI#2, New Sol on User authorization revocation for API invocation procedure | pCR | Xiaomi Communication | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223792 | KI#2, New Sol UE credential based API invocation procedure | pCR | Xiaomi Communication | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223793 | New KI on Protect prioritized list of hosting networks in hosting network scenarios | pCR | Xiaomi Communication | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] |
S3-223794 | New Sol on Protection of prioritized list of hosting networks | pCR | Xiaomi Communication | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
noted | [WTS] [JSN] |
S3-223795 | Resolve EN in Sol #5 | pCR | Xiaomi Communication | 33.739 0.2.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-223796 | Update to KI#1 | pCR | Xiaomi Communication | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223797 | KI9 update to sol17 on authorization mechanism negotiation | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
noted | [WTS] [JSN] |
S3-223798 | KI10 solution on N32 security profiles |
pCR revised to S3-224108 |
Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223799 | Proposal for a KI on injection of authentication data | pCR | Nokia, Nokia Shanghai Bell | 33.892 0.3.0 | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
withdrawn | [WTS] [JSN] |
S3-223800 | Discussion paper on a way forward for LS on protection of the URSP rules from HPLM | discussion | Nokia, Nokia Shanghai Bell | Rel-18 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | ||
S3-223801 | Reply to LS on protection of the URSP rules from HPLMN |
LS out LS is reply to SA2 LS To: SA2 |
Nokia, Nokia Shanghai Bell | FS_USIA |
S3-109 AI: 3 |
merged | [WTS] [JSN] | ||
S3-223802 | Resolution to editor’s note in solution 1 concerning threat mitigation | pCR | Nokia, Nokia Shanghai Bell | 33.892 0.3.0 | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
noted | [WTS] [JSN] |
S3-223803 | Resolution to editor’s note in solution 1 concerning the provisioning of security material | pCR | Nokia, Nokia Shanghai Bell | 33.892 0.3.0 | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
noted | [WTS] [JSN] |
S3-223804 | Proposal for a solution for KI#1 - Anonymous authentication during connection establishment in trusted non-3GPP network access | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-223805 | Proposal for a solution to KI#2 - PALS authentication through onboarding procedure and afterwards registration |
pCR revised to S3-224045 |
Nokia, Nokia Shanghai Bell | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
revised | [WTS] [JSN] |
S3-223806 | Proposal for a solution to KI#2 - PALS authentication through onboarding procedure and afterwards registration |
pCR revised to S3-224046 |
Nokia, Nokia Shanghai Bell | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
revised | [WTS] [JSN] |
S3-223807 | Discussion paper on restriction for multi registrations in two PLMNs | discussion | Nokia, Nokia Shanghai Bell | TEI16 | Rel-16 |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | |
S3-223808 | Discussin paper on control on NSSAA procedures for multi registrations in two PLMNs | discussion | Nokia, Nokia Shanghai Bell | TEI16 | Rel-16 |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | |
S3-223809 | Add restriction for multi registrations in two PLMNs | CR | Nokia, Nokia Shanghai Bell | 33.501 16.12.0 CR#1518 catF | TEI16 | Rel-16 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223810 | control on NSSAA procedures for multi registrations in two PLMNs | CR | Nokia, Nokia Shanghai Bell | 33.501 16.12.0 CR#1519 catF | TEI16 | Rel-16 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223811 | Add restriction for multi registrations in two PLMNs | CR | Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#1520 catA | TEI16 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223812 | control on NSSAA procedures for multi registrations in two PLMNs | CR | Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#1521 catA | TEI16 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223813 | update to KI#2 temporary network slice | pCR | Nokia, Nokia Shanghai Bell | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223814 | solution for KI#2 temporary network slice for NSSAA | pCR | Nokia, Nokia Shanghai Bell | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223815 | update to KI#3 network slice admission control | pCR | Nokia, Nokia Shanghai Bell | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223816 | security solution for KI#3 network slice admission control | pCR | Nokia, Nokia Shanghai Bell | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223817 | new KI for path switching between two indirect network communication paths | pCR | Nokia, Nokia Shanghai Bell | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223818 | security solution for path switching between two indirect network communication paths | pCR | Nokia, Nokia Shanghai Bell | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223819 | Discussion on Serving Network Name used in ProSe | discussion | Nokia, Nokia Shanghai Bell | TEI17 | Rel-17 |
S3-109 AI: 4.8 |
noted | [WTS] [JSN] | |
S3-223820 | use relay UE SNN to generate AV for ProSe authentication | CR | Nokia, Nokia Shanghai Bell | 33.503 17.1.0 CR#68 catF | TEI17 | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223821 | use remote UE SNN to generate AV for ProSe authentication | CR | Nokia, Nokia Shanghai Bell | 33.503 17.1.0 CR#69 catF | TEI17 | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223822 | Discussion on RID used in ProSe | discussion | Nokia, Nokia Shanghai Bell | TEI17 | Rel-17 |
S3-109 AI: 4.8 |
noted | [WTS] [JSN] | |
S3-223823 | include RID of AUSF in DCR | CR | Nokia, Nokia Shanghai Bell | 33.503 17.1.0 CR#70 catF | TEI17 | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223824 | include RID of AUSF in CP PRUK ID | CR | Nokia, Nokia Shanghai Bell | 33.503 17.1.0 CR#71 catF | TEI17 | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223825 | Clarification on N32-f connection establishment with TLS - SNPN use case |
CR revision of S3-221841 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#14352 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
withdrawn | [WTS] [JSN] |
S3-223826 | Updating Solution #9: Concealing length of SUPIs in SUCIs by padding the SUPIs | pCR | Oy LM Ericsson AB | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
not treated | [WTS] [JSN] |
S3-223827 | PCR to TR33.876 - Addition of Key Issue - Protection of private keys at rest | pCR | Vodafone España SA | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
merged | [WTS] [JSN] |
S3-223828 | PCR to 33.876 - Addition of Key Issue: security of internal NF service communicaitons |
pCR revised to S3-224138 |
Vodafone España SA | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
revised | [WTS] [JSN] |
S3-223829 | WID on SBA security |
WID new revision of S3-222254 revised to S3-224087 |
Nokia, Nokia Shanghai Bell | Rel-18 |
S3-109 AI: 6 |
revised | [WTS] [JSN] | ||
S3-223830 | New Key issue on the security of the information transfer of the RAN AI/ML framework | pCR | Ericsson | 33.877 0.3.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-109 AI: 5.14 |
noted | [WTS] [JSN] |
S3-223831 | KAF lifetime recommendations and Ua* protocol requirements | CR | Ericsson | 33.535 17.7.0 CR#144 catF | AKMA | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223832 | New solution for AKMA roaming with VPLMN AKMA Support NF for inbound roamers |
pCR revised to S3-224141 |
Ericsson | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
revised | [WTS] [JSN] |
S3-223833 | Reply LS on Authentication Result Removal |
LS out LS To: CT4 revised to S3-223908 |
Ericsson | Rel-17 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | ||
S3-223834 | New WID on IETF OSCORE protocol profiles for GBA and AKMA |
WID new revised to S3-224132 |
Ericsson | Rel-18 |
S3-109 AI: 6 |
revised | [WTS] [JSN] | ||
S3-223835 | Living document for DUMMY: draftCR to TS 33.535, IETF OSCORE as AKMA Ua* protocol | draftCR | Ericsson, Deutsche Telekom | DUMMY | Rel-18 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] | |
S3-223836 | Solution #11 updates | pCR | Ericsson | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-223837 | Solution #11 evalution |
pCR revised to S3-224020 |
Ericsson | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223838 | Solution #12 updates | pCR | Ericsson | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-223839 | Solution #12 evalution |
pCR revised to S3-224021 |
Ericsson | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223840 | Conlusions |
pCR revised to S3-224013 |
Ericsson | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223841 | Resolve 4 ENs in Solution#1 |
pCR revised to S3-224142 |
Ericsson | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
revised | [WTS] [JSN] |
S3-223842 | Add Evaluation for Solution#1 |
pCR revised to S3-224143 |
Ericsson | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
revised | [WTS] [JSN] |
S3-223843 | New solution: How to avoid e2ae limitation and achieve e2e security for IMS Data Channel |
pCR revised to S3-224124 |
Ericsson | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
revised | [WTS] [JSN] |
S3-223844 | Reply LS on the IMS Data Channel Security Mode |
LS out LS To: GSMA revised to S3-223913 |
Ericsson | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | |
S3-223845 | Clarification on AF authorization for the NSACF notification procedure |
CR revised to S3-223926 |
Ericsson | 33.501 17.7.0 CR#1522 catF | eNS2_SEC | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223846 | Alignment of NSACF notification procedure with existing procedures | CR | Ericsson | 33.501 17.7.0 CR#1523 catF | eNS2_SEC | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223847 | Living document for SERP: draftCR to TS 33.501 on the Protection of the RRC Resume Request message | draftCR | Ericsson, Apple | SERP | Rel-18 |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | |
S3-223848 | Reply LS on Time Synchronization Status notification towards UE(s) |
LS out LS To: SA2 |
Ericsson | Rel-18 |
S3-109 AI: 3 |
merged | [WTS] [JSN] | ||
S3-223849 | EN deletion in KI5 | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
merged | [WTS] [JSN] |
S3-223850 | pCR to 33.875 - Update of Key Issue 10 |
pCR revised to S3-224111 |
Vodafone España SA | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223851 | Addressing EN in Solution 2 |
pCR revised to S3-224049 |
CableLabs | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223852 | Addressing EN in Solution 3 |
pCR revised to S3-224050 |
CableLabs | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223853 | Addressing EN in Solution 4 |
pCR revised to S3-224051 |
CableLabs | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223854 | Authentication for UE behind 5G-RG and FN-RG using NSWO | CR | CableLabs | 33.501 17.7.0 CR#1524 catF | NSWO_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223855 | KI11 threat clarification | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
not treated | [WTS] [JSN] |
S3-223856 | Conclusions for KI#1 |
pCR revised to S3-224052 |
CableLabs, Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
revised | [WTS] [JSN] |
S3-223857 | Key issue on authentication of UE behind RG | pCR | CableLabs, Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] |
S3-223858 | Solution for authentication of UE behind RG using NSWO | pCR | CableLabs | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] |
S3-223859 | Key issue on authentication of N5CW devices behind RG | pCR | CableLabs, Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] |
S3-223860 | Verification of NSSAIs for preventing slice attack | CR | CableLabs, Ericsson, Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#1525 catB | DUMMY | Rel-18 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223861 | Resolving ENs in solution 6.16 |
pCR revised to S3-224099 |
CableLabs | 33.875 1.3.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
revised | [WTS] [JSN] |
S3-223862 | Response LS on Identifier availability for Lawful Interception during Inter-PLMN handover | LS in | S3i220660 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223863 | Key Issue #1 Update |
pCR revised to S3-224031 |
Lenovo, Nokia, Nokia Shanghai Bell, Rakuten Mobile Inc., Interdigital, US National Security Agency, Motorola Solutions, Johns Hopkins University APL, Intel, Center for Internet Security, China Mobile, ZTE, CableLabs, China Telecom, Verizon, Convida Wirele | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
revised | [WTS] [JSN] |
S3-223864 | Editorial Update for TR 33.894 | pCR | Lenovo | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
approved | [WTS] [JSN] |
S3-223865 | Update to Tenet #5 |
pCR revised to S3-224127 |
Lenovo, US National Security Agency, Charter Communications | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
revised | [WTS] [JSN] |
S3-223866 | Update to Tenet #6 | pCR | Lenovo, US National Security Agency, Charter Communications | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
noted | [WTS] [JSN] |
S3-223867 | New solution: PKCE flow based authorization | pCR | DOCOMO Communications Lab. | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223868 | Update to Tenet #7 |
pCR revised to S3-224126 |
Lenovo, US National Security Agency, Charter Communications | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
revised | [WTS] [JSN] |
S3-223869 | TR rapporteur updates - editorials | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-223870 | Update to Solution #1 in ID Privacy |
pCR revised to S3-224033 |
Lenovo | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
revised | [WTS] [JSN] |
S3-223871 | new solution: Subscriber vs. user authorization | pCR | DOCOMO Communications Lab. | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223872 | Update to Solution #8 in HONTRA |
pCR revised to S3-224022 |
Lenovo | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
revised | [WTS] [JSN] |
S3-223873 | Conclusion to use oAuth based authorization | pCR | DOCOMO Communications Lab. | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
noted | [WTS] [JSN] |
S3-223874 | Update to Solution #9 in eNA Ph3 | pCR | Lenovo | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
not treated | [WTS] [JSN] |
S3-223875 | Cyber attack detection | pCR | Lenovo | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
not treated | [WTS] [JSN] |
S3-223876 | Update to Solution #4 in SNAAPPY | pCR | Lenovo | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223877 | Solution to address KI#2 in SNAAPPY | pCR | Lenovo | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223878 | Update to KI#1 Providing VPLMN slice information to roaming UE | pCR | Lenovo | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109 AI: 5.12 |
not treated | [WTS] [JSN] |
S3-223879 | Update to Solution #2 in UAS | pCR | Lenovo | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-223880 | Remove password complexity criteria, password expiry and password history requirements |
CR revised to S3-223931 |
Ericsson | 33.117 16.8.0 CR#95 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223881 | Solution to address KI#4 in 5WWC | pCR | Lenovo | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-223882 | Resolving ENs in solution 6.13 | pCR | CableLabs | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
noted | [WTS] [JSN] |
S3-223883 | Addressing the editor’s note in 6.27.2.1.1 of Sol#27 | pCR | CableLabs | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223884 | Remove password complexity criteria, password expiry and password history requirements |
CR revised to S3-223932 |
Ericsson | 33.117 17.1.0 CR#96 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223885 | Addressing EN on NR Repeater in 6.27.2.2.4 of Sol#27 | pCR | CableLabs | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223886 | Addressing the editor’s note in 6.27.2.2.1of Sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.20.0 | FS_5GFBS | Rel-18 |
S3-109 AI: 5.1 |
not treated | [WTS] [JSN] |
S3-223887 | Key issue on authentication of AUN3 device without 5G credentials | pCR | CableLabs | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
not treated | [WTS] [JSN] |
S3-223888 | pCR to 33.875 - Update to Key Issue 13 | pCR | Vodafone España SA | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
not treated | [WTS] [JSN] |
S3-223889 | [MCPTT] 33179 R13 Incorrect example |
CR revised to S3-223944 |
Airbus | 33.179 13.11.0 CR#107 catF | MCPTT | Rel-13 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223890 | [MCSec] 33180 R14 Incorrect example | CR | Airbus | 33.180 14.11.0 CR#196 catF | MCSec | Rel-14 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223891 | [eMCSec] Mirror 33180 R14 Incorrect example | CR | Airbus | 33.180 15.12.0 CR#197 catA | MCSec | Rel-15 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223892 | [MCXSec] Mirror 33180 R14 Incorrect example | CR | Airbus | 33.180 16.10.0 CR#198 catA | MCSec | Rel-16 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223893 | [MCXSec2] Mirror 33180 R14 Incorrect example | CR | Airbus | 33.180 17.7.0 CR#199 catA | MCSec | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223894 | KI #3 update: authorization synchronization | pCR | MITRE Corporation | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-223895 | Proposal Solution #XX ACME use in 3GPP | pCR | Google Inc. | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
noted | [WTS] [JSN] |
S3-223896 | [MCPTT] 33179 R13 Incorrect reference | CR | Airbus | 33.179 13.11.0 CR#108 catF | MCPTT | Rel-13 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223897 | [MCSec] 33180 R14 Incorrect reference | CR | Airbus | 33.180 14.11.0 CR#200 catF | MCSec | Rel-14 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223898 | [eMCSec] 33180 R15 Incorrect reference (Mirror) | CR | Airbus | 33.180 15.12.0 CR#201 catA | MCSec | Rel-15 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223899 | [MCXSec] 33180 R16 Incorrect reference (Mirror) | CR | Airbus | 33.180 16.10.0 CR#202 catA | MCSec | Rel-16 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223900 | [MCXSec2] 33180 R17 Incorrect reference (Mirror) | CR | Airbus | 33.180 17.7.0 CR#203 catA | MCSec | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223901 | [MCXSec3] 33180 R18 Incorrect reference (Mirror) | CR | Airbus | 33.180 17.7.0 CR#204 catA | MCXSec3 | Rel-18 |
S3-109 AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-223902 | Specification of the 256-bit air interface algorithms | LS in | ETSI SAGE |
S3-109 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-223903 | LS Reply on UE_NOT_FOUND cause code |
LS out LS is reply to S3-223148 LS To: CT1 revision of S3-223317 |
InterDigital, Europe, Ltd. | Rel-17 |
S3-109 AI: 3 |
revised | [WTS] [JSN] | ||
S3-223904 | Reply LS on User Consent for EDGEAPP |
LS out LS is reply to S3-223149 LS To: CT3 revision of S3-223482 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 3 |
approved | [WTS] [JSN] | ||
S3-223905 | Reply LS to Reply LS on the user consent for trace reporting |
LS out LS is reply to S3-223162/R3-225250 LS To: RAN3 revision of S3-223229 |
Nokia, Nokia Shanghai Bell |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223906 | Reply to: LS on user consent of Non-public Network |
LS out LS is reply to S3-223163 LS To: RAN3 |
Qualcomm |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223907 | Reply LS on User consent for Application Detection |
LS out LS is reply to S3-223178 LS To: SA2 revision of S3-223686 |
Ericsson | Rel-18 |
S3-109 AI: 3 |
approved | [WTS] [JSN] | ||
S3-223908 | Reply LS on Authentication Result Removal |
LS out LS is reply to S3-223151 LS To: CT4 revision of S3-223833 |
Ericsson | Rel-17 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | ||
S3-223909 | Reply LS on PLMN ID used in Roaming Scenarios |
LS out LS is reply to S3-223152, S3-223165 source LS: S3-221214 LS To: CT4, SA2 |
Nokia, Nokia Shanghai Bell |
S3-109 AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-223910 | LS to GSMA DESS on SEPP certificates |
LS out LS is reply to S3-223157 LS To: GSMA revision of S3-223386 |
Nokia, Nokia Shanghai Bell | Rel-18 |
S3-109 AI: 3 |
approved | [WTS] [JSN] | ||
S3-223911 | Reply LS on protection of the URSP rules from HPLMN |
LS out LS is reply to S3-223166 LS To: SA2 revision of S3-223379 |
Qualcomm Incorporated | FS_eUEPO | Rel-18 |
S3-109 AI: 3 |
approved | [WTS] [JSN] | |
S3-223912 | Reply LS on impact to URSP rules enforcement report to 5GC |
LS out LS is reply to S3-223173 LS To: SA WG2 revision of S3-223298 |
vivo | FS_eUEPO | Rel-18 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |
S3-223913 | Reply LS on the IMS Data Channel Security Mode |
LS out LS is reply to S3-223184 LS To: GSMA NG/UPG revision of S3-223844 |
Ericsson | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 3 |
approved | [WTS] [JSN] | |
S3-223914 | Reply LS on Network federation interface for Telco edge consideration |
LS out LS is reply to S3-223180 LS To: 3GPP SA6, 3GPP SA2, 3GPP SA5, 3GPP SA revision of S3-223584 |
Huawei, HiSilicon | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 3 |
approved | [WTS] [JSN] | |
S3-223915 | Reply LS on Time Synchronization Status notification towards UE(s) |
LS out LS is reply to S3-223176 source LS: S2-2209876 LS To: 3GPP SA WG2 revision of S3-223213 |
Nokia, Nokia Shanghai Bell,Ericsson | Rel-18 |
S3-109 AI: 3 |
noted | [WTS] [JSN] | ||
S3-223916 | Reply to: LS to inform about the new GSMA Task Force |
LS out LS is reply to S3-223612 LS To: GSMA |
ORANGE |
S3-109 AI: 3 |
noted | [WTS] [JSN] | |||
S3-223917 | CR on control-plane procedure in MBS |
CR revision of S3-223527 |
Huawei, HiSilicon | 33.501 17.7.0 CR#14991 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223918 | Reply LS on the impact of MSK update on MBS multicast session update procedure |
LS out LS is reply to S3-223172 source LS: S2-2209287 LS To: SA2 revision of S3-223528 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-223919 | Reply LS on Security architecture for 5G multicast/broadcast services |
LS out LS is reply to S3-223164 source LS: S2-2207390 LS To: SA2 revision of S3-223530 |
Huawei, HiSilicon | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
approved | [WTS] [JSN] | |
S3-223920 | CR on authentication in user plane procedure in MBS |
CR revision of S3-223529 |
Huawei, HiSilicon,Qualcomm | 33.501 17.7.0 CR#15001 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223921 | LS reply on AKMA API |
LS out LS is reply to S3-223150 LS To: CT3 revision of S3-223265 |
Nokia, Nokia Shanghai Bell | AKMA | Rel-17 |
S3-109 AI: 4.9 |
approved | [WTS] [JSN] | |
S3-223922 | Rel-15 Correcting the OAuth 2.0 roles in CAPIF |
CR revision of S3-223646 |
Ericsson | 33.122 15.3.0 CR#311 catF | CAPIF-Sec | Rel-15 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223923 | Rel-16 Correcting the OAuth 2.0 roles in CAPIF |
CR revision of S3-223647 |
Ericsson | 33.122 16.3.0 CR#321 catA | CAPIF-Sec | Rel-16 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223924 | Rel-17 Correcting the OAuth 2.0 roles in CAPIF |
CR revision of S3-223648 |
Ericsson | 33.122 17.0.0 CR#331 catA | CAPIF-Sec | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223925 | CR on AES-GCM/GMAC in IMS SIP security |
CR revision of S3-223619 |
Apple | 33.203 17.1.0 CR#2661 catC | eCryptPr | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223926 | Clarification on AF authorization for the NSACF notification procedure |
CR revision of S3-223845 |
Ericsson | 33.501 17.7.0 CR#15221 catF | eNS2_SEC | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223927 | Resolving the EN on CAA level ID during UUAA procedures | CR | Qualcomm Incorporated | 33.256 17.1.0 CR#93 catF | ID_UAS | Rel-17 |
S3-109 AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-223928 | Resolving the ENs on CAA level ID during revocation |
CR revision of S3-223333 |
Qualcomm Incorporated | 33.256 17.1.0 CR#113 catF | ID_UAS | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223929 | Clarification on IP_FWD_DISABLING |
CR revision of S3-223604 |
Huawei, HiSilicon | 33.117 16.8.0 CR#931 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223930 | Clarification on IP_FWD_DISABLING |
CR revision of S3-223605 |
Huawei, HiSilicon | 33.117 17.1.0 CR#941 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223931 | Remove password complexity criteria, password expiry and password history requirements |
CR revision of S3-223880 |
Ericsson | 33.117 16.8.0 CR#951 catF | SCAS_5G | Rel-16 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223932 | Remove password complexity criteria, password expiry and password history requirements |
CR revision of S3-223884 |
Ericsson | 33.117 17.1.0 CR#961 catA | SCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223933 | Adding non-Uu user plane text cases to TS 33.511 | draftCR | Qualcomm Incorporated | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-223934 | LS on IMS SCAS to GSMA |
LS out LS To: GSMA NESASG revision of S3-223583 |
Huawei, HiSilicon | Rel-17 |
S3-109 AI: 4.9 |
approved | [WTS] [JSN] | ||
S3-223935 | CR_33.501 R17 Update A.18 to define SoR-XMAC-IUE (mirror) |
CR revision of S3-223779 |
Xiaomi Communication | 33.501 17.7.0 CR#15141 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223936 | CR_33.501 R17 Update A.17 for SoR transparent container |
CR revision of S3-223778 |
Xiaomi Communication | 33.501 17.7.0 CR#15131 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223937 | CR_33.501 R17 Update A.20 to define UPU-XMAC-IUE (mirror) |
CR revision of S3-223780 |
Xiaomi Communication | 33.501 17.7.0 CR#15151 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223938 | UPU procedure align with stage 3 for AMF not registered case |
CR revision of S3-223264 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#14871 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223939 | Conclusion on KI2.2 Authentication mechanism selection |
pCR revision of S3-223586 |
Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
noted | [WTS] [JSN] |
S3-223940 | Method negotiation using TLS 1.3 |
pCR revision of S3-223362 |
Qualcomm Incorporated | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] |
S3-223941 | clarification on PLMN ID verification in SNPN |
CR revision of S3-223606 |
Huawei, HiSilicon | 33.501 17.7.0 CR#15011 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223942 | SECOP correction |
CR revision of S3-223662 |
Nokia, Nokia Shanghai Bell | 33.310 17.4.0 CR#1371 catA | TEI16 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223943 | SECOP correction | CR | Nokia | 33.310 16.11.0 CR#144 catF | TEI16 | Rel-16 |
S3-109 AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-223944 | [MCPTT] 33179 R13 Incorrect example |
CR revision of S3-223889 revised to S3-224172 |
Airbus | 33.179 13.11.0 CR#1071 catF | MCPTT | Rel-13 |
S3-109 AI: 4.9 |
revised | [WTS] [JSN] |
S3-223945 | Clarification of brute force mitigation mechanism verification | CR | BSI (DE) | 33.117 17.1.0 CR#831 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-223946 | Clarification of privilege escalation methods to check for | CR | BSI (DE) | 33.117 17.1.0 CR#841 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-223947 | Clarification of service reachability restriction verification | CR | BSI (DE) | 33.117 17.1.0 CR#851 catF | eSCAS_5G | Rel-17 |
S3-109 AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-223948 | LS on NSSAA procedures for multiple registrations |
LS out LS To: SA2 |
Huawei |
S3-109 AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-223949 | User plane security for Non-SBA based interfaces |
CR revision of S3-223394 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#14302 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-223950 | CR on Kiab handling in IAB migration_old psk |
CR revision of S3-223519 |
Huawei, HiSilicon | 33.501 17.7.0 CR#14981 catF | TEI17 | Rel-17 |
S3-109 AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-223951 | Clarification on N32-f connection establishment with TLS |
CR revision of S3-223203 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#14353 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223952 | Presentation from ENISA on EU certification scheme | other | ENISA |
S3-109 AI: 8 |
noted | [WTS] [JSN] | |||
S3-223953 | SEPP to include and verify the source PLMN-ID |
CR revision of S3-223682 |
Ericsson, Mavenir, Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#15031 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-223954 | Clarification on access token requests for NF Producers of a specific NF type and token-based authorization for indirect communication with delegated discovery |
CR revision of S3-223684 |
Ericsson | 33.501 17.7.0 CR#15041 catB | DUMMY | Rel-18 |
S3-109 AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-223955 | TargetNFServiceSetId to be part of access token claims |
CR revision of S3-223709 |
Nokia, Nokia Shanghai Bell | 33.501 17.7.0 CR#14342 catF | TEI17 | Rel-17 |
S3-109 AI: 4.7 |
agreed | [WTS] [JSN] |
S3-223956 | Renaming 5GPRUK, 5GPRUK ID, PRUK and PRUK ID |
CR revision of S3-223703 |
Ericsson,China Telecom, Huawei, HiSilicon,CATT | 33.503 17.1.0 CR#591 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-223957 | Corrections in privacy protection of 5G ProSe UE-to-Network relay procedure |
CR revision of S3-223368 |
Qualcomm Incorporated,eijing Xiaomi Mobile Software | 33.503 17.1.0 CR#461 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-223958 | Match Report in U2N Relay Discovery Security Procedure |
CR revision of S3-223743 |
Xiaomi Technology,Huawei, HiSilicon | 33.503 17.1.0 CR#641 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-223959 | DTLS for AKMA WID |
WID new revision of S3-223445 |
ZTE Corporation | Rel-18 |
S3-109 AI: 6 |
agreed | [WTS] [JSN] | ||
S3-223960 | Clarification of subscription information in PAnF |
CR revision of S3-223429 |
ZTE Corporation | 33.503 17.1.0 CR#501 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-223961 | Add functionality description of PAnF |
CR revision of S3-223428 |
ZTE Corporation,CATT | 33.503 17.1.0 CR#491 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-223962 | Nudm servcie operation correction |
CR revision of S3-223705 |
Ericsson | 33.503 17.1.0 CR#611 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-223963 | Update KI#5 |
pCR revision of S3-223247 |
OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223964 | New solution to establish UE-to-UE security |
pCR revision of S3-223469 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223965 | pCR to TR33.740 Solution for U2U Relay discovery message security |
pCR revision of S3-223664 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223966 | New solution for hop-by-hop security establishment for the UE-to-UE Relay |
pCR revision of S3-223722 |
Samsung | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223967 | New solution on security for discovery integrated into PC5 link establishment |
pCR revision of S3-223766 |
Beijing Xiaomi Mobile Software | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223968 | Evaluate to the solution #15 |
pCR revision of S3-223477 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223969 | Update TR 33.740 solution #1 |
pCR revision of S3-223310 |
InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223970 | Update to solution#5 in TR 33.740 - align with SA2 |
pCR revision of S3-223400 |
China Telecom Corporation Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223971 | Draft TR 33.740 | draft TR | CATT | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] | |
S3-223972 | Update to ProSe Security Sol#6 |
pCR revision of S3-223451 |
OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223973 | Evaluation to solution #3 |
pCR revision of S3-223626 |
Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223974 | pCR to TR33.740 Update Solution16 for removing ENs |
pCR revision of S3-223636 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223975 | pCR to TR33.740 Evaluation of Solution16 |
pCR revision of S3-223643 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223976 | Updates to solution#19 and resolving EN #5 |
pCR revision of S3-223724 |
Samsung | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223977 | Update to solution #20 in TR 33.740 |
pCR revision of S3-223765 |
Beijing Xiaomi Mobile Software | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223978 | Draft TR 33.898 | draft TR | OPPO | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
approved | [WTS] [JSN] | |
S3-223979 | LS on clarification for user consent for AI/ML |
LS out LS To: SA2 |
Huawei |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] | |||
S3-223980 | New Solution reusing existing mechanism for authorization of 5GC assistance information exposure to AF |
pCR revision of S3-223481 |
Huawei, HiSilicon | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
approved | [WTS] [JSN] |
S3-223981 | KI #1, New Sol on UE profile based 5GC assistance information exposure authorization |
pCR revision of S3-223783 |
Xiaomi Communication | 33.898 0.2.0 | FS_AIML | Rel-18 |
S3-109 AI: 5.2 |
approved | [WTS] [JSN] |
S3-223982 | Addressing the editor's note in sol#1 |
pCR revision of S3-223531 |
Huawei, HiSilicon | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
approved | [WTS] [JSN] |
S3-223983 | Draft TR 33.875 | draft TR | Nokia | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] | |
S3-223984 | Conclusion on KI#1 in TR 33.875 |
pCR revision of S3-223240 |
Mavenir,Nokia,Huawei | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-223985 | KI3 update Subscribe-Notify – EN resolution |
pCR revision of S3-223714 |
Nokia, Nokia Shanghai Bell, Ericsson, Huaweil | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-223986 | Evaluation for Solution #3 |
pCR revision of S3-223380 |
Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-223987 | Evaluation for Solution #11 |
pCR revision of S3-223381 |
Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-223988 | Further Analysis for KI#4 in TR 33.875 |
pCR revision of S3-223241 |
Mavenir,Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-223989 | Conclusion for KI#4 in TR 33.875 |
pCR revision of S3-223242 |
Mavenir,Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-223990 | Solution on KI#11 in TR 33.875 |
pCR revision of S3-223330 |
Mavenir,Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-223991 | Resolving EN and evaluation for Solution #12 |
pCR revision of S3-223383 |
Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-223992 | address EN for solution #8 and add evaluation |
pCR revision of S3-223514 |
Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-223993 | address EN for solution #9 and add evaluation |
pCR revision of S3-223515 |
Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-223994 | Update to solution #3 |
pCR revision of S3-223543 |
Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-223995 | Conclusion on UE-to-UE relay Authorisation |
pCR revision of S3-223471 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223996 | New KI: Support for Emergency service over UE-to-Network Relaying |
pCR revision of S3-223623 |
Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223997 | A new solution for UE-to-UE Relay discovery message protection for Model A discovery |
pCR revision of S3-223369 |
Qualcomm Incorporated | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223998 | A new solution for UE-to-UE Relay discovery message protection for Model B discovery |
pCR revision of S3-223370 |
Qualcomm Incorporated | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-223999 | A new solution for secure PC5 link establishment for UE-to-UE Relay |
pCR revision of S3-223371 |
Qualcomm Incorporated | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224000 | Update TR 33.740 solution #12 |
pCR revision of S3-223312 |
InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224001 | Update TR 33.740 solution #13 |
pCR revision of S3-223313 |
InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224002 | Resolve EN of Direct Communication Invite in Solution3 |
pCR revision of S3-223629 |
Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224003 | pCR to TR33.740 Update Solution17 for removing ENs |
pCR revision of S3-223638 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224004 | pCR to TR33.740 Evaluation of Solution17 |
pCR revision of S3-223644 |
CATT | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224005 | Support Emergency Service over UE-to-Network Relay |
pCR revision of S3-223624 |
Ericsson | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224006 | ProSe - Evaluation Solution #10 |
pCR revision of S3-223276 |
Philips International B.V. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224007 | Update TR 33.740 solution #14 |
pCR revision of S3-223314 |
InterDigital, Europe, Ltd. | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224008 | Add Evaluation for ProSe Security Sol#6 |
pCR revision of S3-223453 |
OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
noted | [WTS] [JSN] |
S3-224009 | Evaluate to the solution #5 |
pCR revision of S3-223476 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224010 | AKMA - Evaluation Solution #10 |
pCR revision of S3-223287 |
Philips International B.V. | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224011 | Update KI#1 |
pCR revision of S3-223511 |
Huawei, HiSilicon | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224012 | MEC - New key issue on AF specific identifier |
pCR revision of S3-223616 |
Apple | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-224013 | Conlusions |
pCR revision of S3-223840 |
Ericsson | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224014 | solution 1 evaluation |
pCR revision of S3-223273 |
Nokia, Nokia Shanghai Bell | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224015 | Adding an evaluation of solution #5 |
pCR revision of S3-223360 |
Qualcomm Incorporated | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224016 | draft TR 33.741 | draft TR | Huawei | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] | |
S3-224017 | Add some context to solution #3 |
pCR revision of S3-223438 |
ZTE Corporation | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224018 | Update solution2 |
pCR revision of S3-223502 |
Huawei, HiSilicon | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224019 | Resolving EN and adding evaluation for solution#6 |
pCR revision of S3-223719 |
Samsung | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224020 | Solution #11 evalution |
pCR revision of S3-223837 |
Ericsson | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224021 | Solution #12 evalution |
pCR revision of S3-223839 |
Ericsson | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224022 | Update to Solution #8 in HONTRA |
pCR revision of S3-223872 |
Lenovo | 33.741 0.3.0 | FS_HN_Auth | Rel-18 |
S3-109 AI: 5.7 |
approved | [WTS] [JSN] |
S3-224023 | Conclusion on KI2.3 Authentication and Authorization between V-ECS and H-ECS |
pCR revision of S3-223585 |
Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] |
S3-224024 | Draft TR 33.739 | draft TR | Huawei | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] | |
S3-224025 | Resolving ENs in solution #13 |
pCR revision of S3-223653 |
Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] |
S3-224026 | Evaluation of solution #13 |
pCR revision of S3-223654 |
Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] |
S3-224027 | Evaluation of solution #14 |
pCR revision of S3-223655 |
Ericsson | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] |
S3-224028 | Evaluation to solution 18 |
pCR revision of S3-223551 |
Huawei, HiSilicon | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109 AI: 5.9 |
approved | [WTS] [JSN] |
S3-224029 | New solution for KI#5 |
pCR revision of S3-223248 |
OPPO | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224030 | Resolving EN and adding evaluation for solution#13 |
pCR revision of S3-223717 |
Samsung | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224031 | Key Issue #1 Update |
pCR revision of S3-223863 |
Lenovo, Nokia, Nokia Shanghai Bell, Rakuten Mobile Inc., Interdigital, US National Security Agency, Motorola Solutions, Johns Hopkins University APL, Intel, Center for Internet Security, China Mobile, ZTE, CableLabs, China Telecom, Verizon, Convida Wirele | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
approved | [WTS] [JSN] |
S3-224032 | Address EN and add evaluation for solution 9 |
pCR revision of S3-223432 |
ZTE Corporation | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224033 | Update to Solution #1 in ID Privacy |
pCR revision of S3-223870 |
Lenovo | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
approved | [WTS] [JSN] |
S3-224034 | Solution for Trusted non-3GPP Access for SNPN |
pCR revision of S3-223218 |
Lenovo | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-224035 | Solution for Untrusted non-3GPP Access for SNPN |
pCR revision of S3-223219 |
Lenovo | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-224036 | Draft TR 33.858 | draft TR | Ericsson | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] | |
S3-224037 | New solution on Reusing N3GPP authentication for NPN |
pCR revision of S3-223490 |
Huawei, HiSilicon | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-224038 | Sol#3 Resolution of EN on visibility of application |
pCR revision of S3-223291 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224039 | Sol#3 Resolution of EN on prearranged policies |
pCR revision of S3-223292 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224040 | Sol#3 Resolution of EN on authorization of third party |
pCR revision of S3-223293 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224041 | Sol#3 Resolution of EN on AKMA Usage |
pCR revision of S3-223294 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224042 | Sol#3 Adding Evaluation |
pCR revision of S3-223297 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224043 | Access to localized services using existing mechanisms |
pCR revision of S3-223558 |
Intel | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-224044 | New Solution to KI#2: Authentication for UE access to hosting network |
pCR revision of S3-223693 |
Ericsson | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-224045 | Proposal for a solution to KI#2 - PALS authentication through onboarding procedure and afterwards registration |
pCR revision of S3-223805 |
Nokia, Nokia Shanghai Bell | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-224046 | Proposal for a solution to KI#2 - PALS authentication through onboarding procedure and afterwards registration |
pCR revision of S3-223806 |
Nokia, Nokia Shanghai Bell | 33.858 0.2.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] |
S3-224047 | Revised SID on Security aspects for 5WWC Phase 2 |
SID revised revision of S3-223253 |
Nokia, Nokia Shanghai Bell, CableLabs, Lenovo, Apple | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
agreed | [WTS] [JSN] | |
S3-224048 | evaluation for solution 1 |
pCR revision of S3-223259 |
Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-224049 | Addressing EN in Solution 2 |
pCR revision of S3-223851 |
CableLabs | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-224050 | Addressing EN in Solution 3 |
pCR revision of S3-223852 |
CableLabs | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-224051 | Addressing EN in Solution 4 |
pCR revision of S3-223853 |
CableLabs | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-224052 | Conclusions for KI#1 |
pCR revision of S3-223856 |
CableLabs, Nokia, Nokia Shanghai Bell | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-224053 | TNAP mobility solution with rand value |
pCR revision of S3-223257 |
Nokia, Nokia Shanghai Bell, CableLabs, | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-224054 | TNAP mobility solution with count |
pCR revision of S3-223258 |
Nokia, Nokia Shanghai Bell, CableLabs, | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-224055 | Proposed solution for TNAP mobility |
pCR revision of S3-223364 |
Qualcomm Incorporated | 33.887 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] |
S3-224056 | Draft TR 33.887 | draft TR | Nokia, Nokia Shanghai Bell | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
approved | [WTS] [JSN] | |
S3-224057 | Update of LI requirements on solution #5 |
pCR revision of S3-223580 |
LG Electronics France | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224058 | Update of LI requirements on solution #12 |
pCR revision of S3-223581 |
LG Electronics France | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224059 | PIN - Addressing EN#2 in Solution #4 |
pCR revision of S3-223281 |
Philips International B.V. | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224060 | PIN - Addressing EN#4 in Solution #4 |
pCR revision of S3-223283 |
Philips International B.V. | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224061 | Draft TR 33.882 | draft TR | Vivo | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] | |
S3-224062 | Sol#3 Adding Evaluation |
pCR revision of S3-223308 |
Nokia, Nokia Shanghai Bell | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224063 | Addressing the ENs in solution 1 |
pCR revision of S3-223521 |
Huawei, HiSilicon | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224064 | New solution for AF manipulate PIN |
pCR revision of S3-223300 |
vivo | 33.882 3.0.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224065 | Address EN on PACF and MANO Communication |
pCR revision of S3-223387 |
Johns Hopkins University APL, US National Security Agency, CISA ECD | 33.848 0.14.0 | FS_SIV | Rel-16 |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] |
S3-224066 | LS on embedding MnF in PACF security function |
LS out LS To: SA5 |
John Hopkins Univeristy |
S3-109 AI: 5.2 |
noted | [WTS] [JSN] | |||
S3-224067 | Solution for KI#1: Authentication and Authorization of PINE |
pCR revision of S3-223378 |
Qualcomm Incorporated | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224068 | Reply LS on Support PIN application architecture and interaction |
LS out LS is reply to S3-223196 LS To: SA WG6 revision of S3-223299 |
vivo | FS_PINAPP | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] | |
S3-224069 | PCR to 33.870 Changes to Solution #2 |
pCR revision of S3-223200 |
InterDigital, Inc. | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
noted | [WTS] [JSN] |
S3-224070 | KI4 Sol SCP authorization check by NRF |
pCR revision of S3-223741 |
Nokia, Nokia Shanghai Bell | 33.875 1.3.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-224071 | KI#1 New sol AKMA roaming for external AF in the Data Network |
pCR revision of S3-223785 |
Xiaomi Communication | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224072 | 33.700-28: Update to Key Issue #1 |
pCR revision of S3-223761 |
Xiaomi Technology | 33.700-28 0.1.0 | FS_5GSAT_Sec | Rel-18 |
S3-109 AI: 5.25 |
approved | [WTS] [JSN] |
S3-224073 | PIN - Addressing EN#1 in Solution #4 |
pCR revision of S3-223280 |
Philips International B.V. | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224074 | PIN - Addressing EN#3 in Solution #4 |
pCR revision of S3-223282 |
Philips International B.V. | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224075 | New solution on protection of data and analytics exchange in roaming case using Secure Multi-party Computation |
pCR revision of S3-223663 |
China Mobile (Suzhou) Software | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224076 | Update to solution#8 |
pCR revision of S3-223665 |
China Mobile (Suzhou) Software | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224077 | Add evaluation to Solution #8 |
pCR revision of S3-223660 |
China Mobile (Suzhou) Software | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224078 | solution 1 evaluation |
pCR revision of S3-223269 |
Nokia, Nokia Shanghai Bell | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224079 | Evaluation for Solution #5 |
pCR revision of S3-223391 |
Nokia, Nokia Shanghai Bell | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224080 | Adding description about overview of vendor development and product lifecycle processes and test laboratory accreditation to clause 6.1 |
pCR revision of S3-223458 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-224081 | Adding description about audit and accreditation of vendor development and product lifecycle processes to clause 6.2 |
pCR revision of S3-223459 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-224082 | Adding description about Audit and accreditation of test laboratories to clause 6.3 |
pCR revision of S3-223460 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-224083 | Adding description about content and process of SCAS instantiation evaluation to clause 7.2 |
pCR revision of S3-223556 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-224084 | Adding description about partial compliance and use of SECAM requirements in network product development cycle to clause 7.4 |
pCR revision of S3-223632 |
China Mobile (Suzhou) Software | 33.936 0.3.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-224085 | Adding clause 4.4 in TR 33.927 |
pCR revision of S3-223634 |
China Mobile (Suzhou) Software | 33.927 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-224086 | Adding clause 6 in TR 33.927 |
pCR revision of S3-223640 |
China Mobile (Suzhou) Software | 33.927 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] |
S3-224087 | WID on SBA security |
WID new revision of S3-223829 |
Nokia, Nokia Shanghai Bell | Rel-18 |
S3-109 AI: 6 |
agreed | [WTS] [JSN] | ||
S3-224088 | Sol#3 Resolution of EN on authorization of PEGC |
pCR revision of S3-223306 |
Nokia, Nokia Shanghai Bell | 33.882 0.3.0 | FS_PIN_Sec | Rel-18 |
S3-109 AI: 5.1 |
approved | [WTS] [JSN] |
S3-224089 | Clarification for IPSec in UPF interfaces | draftCR | Keysight Technologies UK Ltd | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-224090 | Key Issue Update on User Consent for NTN |
pCR revision of S3-223483 |
Huawei, HiSilicon, Philips International B.V., Xiaomi, Qualcomm, Apple | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
noted | [WTS] [JSN] |
S3-224091 | Overview of UC3S_Ph2 |
pCR revision of S3-223485 |
Huawei, HiSilicon | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
approved | [WTS] [JSN] |
S3-224092 | Guidance for Enforcing User Consent |
pCR revision of S3-223562 |
Huawei, HiSilicon | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
approved | [WTS] [JSN] |
S3-224093 | Add conclusion to KI#2 about DAA unicast security |
pCR revision of S3-223467 |
Huawei, HiSilicon | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
noted | [WTS] [JSN] |
S3-224094 | Add conclusion to KI#5 about DAA unicast privacy |
pCR revision of S3-223474 |
Huawei, HiSilicon | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-224095 | Conclusion on UE-to-UE relay security |
pCR revision of S3-223470 |
Huawei, HiSilicon | 33.740 0.3.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109 AI: 5.3 |
approved | [WTS] [JSN] |
S3-224096 | Draft TR 33.936 | draft TR | China Mobile | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] | |
S3-224097 | Draft TR 33.927 | draft TR | China Mobile | VNP_SECAM_SCAS | Rel-18 |
S3-109 AI: 4.2 |
approved | [WTS] [JSN] | |
S3-224098 | Draft TR 33.537 | draft TR | China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-109 AI: 4.5 |
approved | [WTS] [JSN] | |
S3-224099 | Resolving ENs in solution 6.16 |
pCR revision of S3-223861 |
CableLabs | 33.875 1.3.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-224100 | Conclusion on KI#5 in TR 33.875 |
pCR revision of S3-223244 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-224101 | Address EN for solution 1 |
pCR revision of S3-223488 |
Huawei, HiSilicon | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224102 | Conclusion for KI#6 in TR 33.875 |
pCR revision of S3-223246 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-224103 | Draft TR 33.742 | draft TR | Qualcomm | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] | |
S3-224104 | Conclution on KI#7 |
pCR revision of S3-223594 |
Huawei, HiSilicon | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-224105 | SA3 meeting calendar |
other revision of S3-223146 |
SA WG3 Chair |
S3-109 AI: 8 |
noted | [WTS] [JSN] | |||
S3-224106 | Draft TR 33.884 | draft TR | NTT-Docomo | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] | |
S3-224107 | KI9 update to sol17 on authorization mechanism negotiation | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
withdrawn | [WTS] [JSN] |
S3-224108 | KI10 solution on N32 security profiles |
pCR revision of S3-223798 |
Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-224109 | Draft TR 33.737 | draft TR | China Mobile | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] | |
S3-224110 | Resolving Editor’s Note in Solution #20 in TR 33.875 |
pCR revision of S3-223328 |
Mavenir | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-224111 | pCR to 33.875 - Update of Key Issue 10 |
pCR revision of S3-223850 |
Vodafone España SA,Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-224112 | Draft TR 33.891 |
draft TR revised to S3-230441 |
Qualcomm | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] | |
S3-224113 | New key issue on enhancement of user consent for using MDT for NG-RAN AI/ML | pCR | Nokia, Nokia Shanghai Bell | 33.896 0.3.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
withdrawn | [WTS] [JSN] |
S3-224114 | EN removal for privacy prevention of NAI solution |
pCR revision of S3-223238 |
Nokia, Nokia Shanghai Bell | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
approved | [WTS] [JSN] |
S3-224115 | Resolution of ENs in solution #14 |
pCR revision of S3-223579 |
THALES | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224116 | Evaluation Solution #4 |
pCR revision of S3-223323 |
InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-224117 | Conclusion TR 33.891 KI #1 |
pCR revision of S3-223325 |
InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
noted | [WTS] [JSN] |
S3-224118 | Conclusion TR 33.891 KI #3 |
pCR revision of S3-223326 |
InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-224119 | Conclusion TR 33.891 KI #4 |
pCR revision of S3-223327 |
InterDigital, Europe, Ltd. | 33.891 0.3.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109 AI: 5.17 |
approved | [WTS] [JSN] |
S3-224120 | Draft TR 33.883 | draft TR | Huawei | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
approved | [WTS] [JSN] | |
S3-224121 | Editorial changes to the living document for MnF SCAS |
other revision of S3-223533 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-109 AI: 4.1 |
approved | [WTS] [JSN] | |
S3-224122 | Living document for MnF SCAS |
draftCR revision of S3-223567 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-109 AI: 4.1 |
approved | [WTS] [JSN] | |
S3-224123 | Updates to clause 4.3 of MnF SCAS |
pCR revision of S3-223571 |
Huawei, HiSilicon | 33.526 0.3.0 | SCAS_5G_MF | Rel-18 |
S3-109 AI: 4.1 |
approved | [WTS] [JSN] |
S3-224124 | New solution: How to avoid e2ae limitation and achieve e2e security for IMS Data Channel |
pCR revision of S3-223843 |
Ericsson | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
approved | [WTS] [JSN] |
S3-224125 | Evaluation of tenet 4 on resource access | pCR | Huawei, HiSilicon | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
withdrawn | [WTS] [JSN] |
S3-224126 | Update to Tenet #7 |
pCR revision of S3-223868 |
Lenovo, US National Security Agency, Charter Communications | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
approved | [WTS] [JSN] |
S3-224127 | Update to Tenet #5 |
pCR revision of S3-223865 |
Lenovo, US National Security Agency, Charter Communications | 33.894 0.3.0 | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
noted | [WTS] [JSN] |
S3-224128 | 33.893: Additional Roles for Authorization in KI#2 |
pCR revision of S3-223746 |
Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
approved | [WTS] [JSN] |
S3-224129 | Draft TR 33.893 | draft TR | Xiaomi | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
approved | [WTS] [JSN] | |
S3-224130 | 33.893: New Solution on Security Policy based Protection for Ranging Communication |
pCR revision of S3-223752 |
Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
approved | [WTS] [JSN] |
S3-224131 | 33.893: New Solution on Security Policy based Protection for Ranging Result sent to SL Positioning Client UE |
pCR revision of S3-223753 |
Xiaomi Technology | 33.893 0.3.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109 AI: 5.19 |
approved | [WTS] [JSN] |
S3-224132 | New WID on IETF OSCORE protocol profiles for GBA and AKMA |
WID new revision of S3-223834 |
Ericsson | Rel-18 |
S3-109 AI: 6 |
agreed | [WTS] [JSN] | ||
S3-224133 | Correcting the handling of synchronisation error |
CR revision of S3-223704 |
Ericsson | 33.503 17.1.0 CR#601 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-224134 | Updates to solution 3 based on pseudonyms |
pCR revision of S3-223540 |
Huawei, HiSilicon | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
approved | [WTS] [JSN] |
S3-224135 | Living document for AAnF SCAS – draftCR to TR 33.926 | draftCR | China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-109 AI: 4.5 |
approved | [WTS] [JSN] | |
S3-224136 | conclusion on AKMA roaming |
pCR revision of S3-223505 |
Huawei, HiSilicon | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224137 | Conclusion for KI#1 case 2 |
pCR revision of S3-223675 |
China Mobile (Suzhou) Software | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224138 | PCR to 33.876 - Addition of Key Issue: security of internal NF service communicaitons |
pCR revision of S3-223828 |
Vodafone España SA | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-224139 | Solution for ensuring the management of bulk certificate updates |
pCR revision of S3-223384 |
Nokia, Nokia Shanghai Bell | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-224140 | Policy based certificate update/renewal |
pCR revision of S3-223544 |
Huawei, HiSilicon | 33.876 0.4.0 | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] |
S3-224141 | New solution for AKMA roaming with VPLMN AKMA Support NF for inbound roamers |
pCR revision of S3-223832 |
Ericsson | 33.737 0.3.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109 AI: 5.6 |
approved | [WTS] [JSN] |
S3-224142 | Resolve 4 ENs in Solution#1 |
pCR revision of S3-223841 |
Ericsson | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
approved | [WTS] [JSN] |
S3-224143 | Add Evaluation for Solution#1 |
pCR revision of S3-223842 |
Ericsson | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
approved | [WTS] [JSN] |
S3-224144 | Resolving ENs and evaluation for Solution #7 |
pCR revision of S3-223389 |
Nokia, Nokia Shanghai Bell | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224145 | Evaluation for Solution #3 |
pCR revision of S3-223392 |
Nokia, Nokia Shanghai Bell | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224146 | Update of solution #4 |
pCR revision of S3-223217 |
Lenovo | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224147 | Updates to solution 2: remove EN E2E protection |
pCR revision of S3-223563 |
Intel | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224148 | Authorization of AI/ML model sharing between different vendors and usage of one-time URLs |
pCR revision of S3-223657 |
Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224149 | Solution on Token based Authorization of AI/ML Model sharing between different vendors(ADRF) |
pCR revision of S3-223689 |
Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224150 | Solution on Authorization of AI/ML Model sharing between different vendors(MTLF) |
pCR revision of S3-223690 |
Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224151 | New solution for KI#3 to support authorization of AI/ML model sharing By NWDAF containing MTLF(local auth) |
pCR revision of S3-223691 |
Ericsson | 33.738 0.3.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] |
S3-224152 | Update KI#3 |
pCR revision of S3-223499 |
Huawei, HiSilicon | 33.877 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] |
S3-224153 | Solution to KI#3 |
pCR revision of S3-223500 |
Huawei, HiSilicon | 33.877 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] |
S3-224154 | Conclusion to KI#3 |
pCR revision of S3-223501 |
Huawei, HiSilicon | 33.877 0.3.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109 AI: 5.13 |
noted | [WTS] [JSN] |
S3-224155 | living doc to TR33.926 |
draftCR revision of S3-223506 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-224156 | living doc to TR33.216 |
draftCR revision of S3-223507 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-109 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-224157 | EN addressing for solution#2 |
pCR revision of S3-223597 |
Huawei, HiSilicon | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
approved | [WTS] [JSN] |
S3-224158 | New solution to KI#2 |
pCR revision of S3-223599 |
Huawei, HiSilicon | 33.890 0.3.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
approved | [WTS] [JSN] |
S3-224159 | Update to KI#2 |
pCR revision of S3-223479 |
Huawei, HiSilicon | 33.877 0.3.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-109 AI: 5.14 |
approved | [WTS] [JSN] |
S3-224160 | Draft TR 33.877 | draft TR | Ericsson | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-109 AI: 5.14 |
approved | [WTS] [JSN] | |
S3-224161 | Correction to authentication mechanism selection |
CR revision of S3-223702 |
Ericsson, Xiaomi | 33.503 17.1.0 CR#581 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-224162 | Draft TR 33.894 | draft TR | Lenovo | FS_ZTS | Rel-18 |
S3-109 AI: 5.21 |
approved | [WTS] [JSN] | |
S3-224163 | Draft TS 33.526 | draft TS | Huawei | SCAS_5G_MF | Rel-18 |
S3-109 AI: 4.1 |
approved | [WTS] [JSN] | |
S3-224164 | Draft TR 33.870 | draft TR | Interdigital | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
approved | [WTS] [JSN] | |
S3-224165 | Draft TR 33.876 | draft TR | Nokia | FS_ACM_SBA | Rel-18 |
S3-109 AI: 5.5 |
approved | [WTS] [JSN] | |
S3-224166 | Draft TR 33.700-28 | draft TR | Xiaomi | FS_5GSAT_Sec | Rel-18 |
S3-109 AI: 5.25 |
approved | [WTS] [JSN] | |
S3-224167 | LS reply on CAPIF authorization roles related to FS_SNAAPP | LS in | S6-223489 |
S3-109 AI: 5.11 |
postponed | [WTS] [JSN] | |||
S3-224168 | LS reply on SNAAPP requirements clarifications | LS in | S6-223488 |
S3-109 AI: 5.11 |
postponed | [WTS] [JSN] | |||
S3-224169 | Draft CR: Introducing split gNBs into TR 33.926 |
draftCR revision of S3-223342 |
Qualcomm Incoporated | SCAS_5G_split_gNB | Rel-18 |
S3-109 AI: 4.6 |
approved | [WTS] [JSN] | |
S3-224170 | Alignment of Link Identifier Update (LIU) procedure |
CR revision of S3-223315 |
InterDigital, Europe, Ltd. | 33.503 17.1.0 CR#421 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-224171 | Allocate FC Value for 33.503 |
CR revision of S3-223557 |
ZTE Corporation | 33.220 17.3.0 CR#2191 catF | 5G_ProSe | Rel-17 |
S3-109 AI: 4.8 |
agreed | [WTS] [JSN] |
S3-224172 | [MCPTT] 33179 R13 Incorrect example |
CR revision of S3-223944 |
Airbus | 33.179 13.11.0 CR#1072 catF | MCPTT | Rel-13 |
S3-109 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-224173 | New WID on HONTRA |
WID new revision of S3-223504 |
Huawei, HiSilicon | Rel-18 |
S3-109 AI: 6 |
agreed | [WTS] [JSN] | ||
S3-224174 | Remove EN and Provide Evaluation for Solution #4 |
pCR revision of S3-223446 |
China Mobile (Suzhou) Software | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
noted | [WTS] [JSN] |
S3-224175 | Reply LS on Progress and open issues for NPN enhancements in Rel-18 |
LS out LS is reply to S3-223175,S3-223168 LS To: SA2 revision of S3-223375 |
Qualcomm Incorporated | FS_eNPN_Ph2, eNPN_Ph2 | Rel-18 |
S3-109 AI: 5.16 |
approved | [WTS] [JSN] | |
S3-224176 | Evaluation of solution #8 |
pCR revision of S3-223377 |
Qualcomm Incorporated | 33.870 0.4.0 | FS_Id_Prvc | Rel-18 |
S3-109 AI: 5.4 |
approved | [WTS] [JSN] |
S3-224177 | Solution on prevention of URSP rule misuse by a non-genuine application using home network anchor |
pCR revision of S3-223576 |
Intel | 33.892 0.3.0 | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
approved | [WTS] [JSN] |
S3-224178 | Draft TR 33.738 | draft TR | China Mobile | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109 AI: 5.8 |
approved | [WTS] [JSN] | |
S3-224179 | Draft TR 33.890 | draft TR | Huawei | FS_NG_RTC_SEC | Rel-18 |
S3-109 AI: 5.15 |
approved | [WTS] [JSN] | |
S3-224180 | Draft TR 33.892 | draft TR | Lenovo | FS_USIA | Rel-18 |
S3-109 AI: 5.18 |
approved | [WTS] [JSN] | |
S3-224181 | Draft TR 33.896 | draft TR | Huawei | FS_UC3S_Ph2 | Rel-18 |
S3-109 AI: 5.22 |
approved | [WTS] [JSN] | |
S3-224182 | A new solution on MOCN network sharing scenario |
pCR revision of S3-223525 |
Huawei, HiSilicon | 33.883 0.3.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109 AI: 5.23 |
approved | [WTS] [JSN] |
S3-224183 | Trust in service mesh and standalone SCP implementations |
pCR revision of S3-223710 |
Nokia, Nokia Shanghai Bell | 33.875 1.4.0 | FS_eSBA_SEC | Rel-18 |
S3-109 AI: 5.24 |
approved | [WTS] [JSN] |
S3-230001 | Agenda | agenda | SA WG3 Chair |
S3-109-ad hoc-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-230002 | Process for SA3#109Adhoc-e | other | SA WG3 Chair |
S3-109-ad hoc-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-230003 | Process and agenda planning for SA3#109AdHoc-e | other | SA WG3 Chair |
S3-109-ad hoc-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-230004 | Report from SA#98 on SA3 topics | report | WG Chair |
S3-109-ad hoc-e AI: 8 |
noted | [WTS] [JSN] | |||
S3-230005 | LS on U2N relay direct link setup failure due to RSC mismatch or integrity failure | LS in | C1-226908 |
S3-109-ad hoc-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-230006 | Reply LS on the progress and open issues for NPN enhancements in Rel-18 | LS in | C1-227157 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-230007 | LS on SL positioning groupcast and broadcast |
LS in LS reply in S3-230430, S3-230430 |
R2-2213142 |
S3-109-ad hoc-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-230008 | LS on user consent of Non-public Network | LS in | R3-226006 |
S3-109-ad hoc-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-230009 | Reply LS on Progress and open issues for NPN enhancements in Rel-18 | LS in | S1-223540 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-230010 | Reply LS on the impact of MSK update on MBS multicast session update procedure | LS in | S2-2209287 |
S3-109-ad hoc-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-230011 | LS on impact of URSP rule enforcement report to 5GC | LS in | S2-2209327 |
S3-109-ad hoc-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-230012 | Reply LS on how ML model integrity, confidentiality and availability is supported between NWDAFs from different vendors | LS in | S2-2210943 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-230013 | Slice based Steering of Roaming | LS in | S2-2211204 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-230014 | Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | LS in | S6-223487 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-230015 | LS reply on SNAAPP requirements clarifications | LS in | S6-223488 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-230016 | LS reply on CAPIF authorization roles related to FS_SNAAPP | LS in | S6-223489 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-230017 | LS on the use of a non-network defined identifier for UE identification | LS in | S6-223558 |
S3-109-ad hoc-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-230018 | Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network |
LS in LS reply in S3-230463, S3-230463 |
S6-223586 |
S3-109-ad hoc-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-230019 | Key Issue for NAS UE Registration Procedure | pCR | Nokia, Nokia Shanghai Bell | 33.700-28 0.2.0 | FS_5GSAT_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.25 |
noted | [WTS] [JSN] |
S3-230020 | New Key Issue on Protection of 5GS SIB19 | pCR | Nokia, Nokia Shanghai Bell | 33.700-28 0.2.0 | FS_5GSAT_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.25 |
noted | [WTS] [JSN] |
S3-230021 | KI10 solution 25 update on security profiles |
pCR revised to S3-230493 |
BSI (DE), Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230022 | KI10 update on RHUB |
pCR revised to S3-230496 |
BSI (DE), Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230023 | KI12 solution 19 update on hosted SEPP |
pCR revised to S3-230507 |
BSI (DE), Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230024 | Conclusion TR 33.891 KI #1 | pCR | InterDigital, Europe, Ltd. | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-230025 | Update conclusion TR 33.891 KI #3 |
pCR revised to S3-230433 |
InterDigital, Europe, Ltd. | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-230026 | Update conclusion TR 33.891 KI #4. |
pCR revised to S3-230434 |
InterDigital, Europe, Ltd. | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-230027 | LS on support for Restricted ProSe Direct Discovery for UAS |
LS out LS To: SA2 |
InterDigital, Europe, Ltd. | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
noted | [WTS] [JSN] | ||
S3-230028 | Evaluation TR 33.740 Sol #1 |
pCR revised to S3-230435 |
InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230029 | Evaluation TR 33.740 Sol #12 |
pCR revised to S3-230436 |
InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230030 | Evaluation TR 33.740 Sol #13 |
pCR revised to S3-230437 |
InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230031 | Evaluation TR 33.740 Sol #14 | pCR | InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230032 | Update to TR 33.740 Conclusion for KI#2 | pCR | InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230033 | Update to TR 33.740 Conclusion for KI#4 |
pCR revised to S3-230438 |
InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230034 | New key issue on Federated Learning AIML model privacy protection | pCR | InterDigital Communications | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-230035 | New key issue on Federated Learning AIML model protection | pCR | InterDigital Communications | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-230036 | Key issue on SN Name binding for Kausf in SNPN using AAA server for primary authentication | pCR | InterDigital Communications | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-230037 | New Solution of authorization for EDGE-9 reference point |
pCR revised to S3-230587 |
InterDigital Communications | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230038 | New Key issue for Monitoring and detecting attacks on ranging devices and services | pCR | Nokia, Nokia Shanghai Bell | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230039 | New key issue on enhancement of user consent for using MDT for NG-RAN AI/ML | pCR | Nokia, Nokia Shanghai Bell | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230040 | LS on MOCN TMGI ID impacting MSK, MTK |
LS out LS To: SA2 |
Nokia, Nokia Shanghai Bell |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-230041 | TMGI protection during group Paging | pCR | Nokia, Nokia Shanghai Bell | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-230042 | New solution for PINE authentiation with information provided by PEMC | pCR | vivo | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230043 | New solution for conditional PINE authorization by PEMC | pCR | vivo | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230044 | New solution for PINE authentiation over 5G UP | pCR | vivo | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230045 | Update solution for PINE authentication and authorization over 5G CP |
pCR revised to S3-230482 |
vivo | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-230046 | Evaluation on Sol#6 | pCR | vivo | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230047 | Interim conclusions on KI#1 | pCR | vivo | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230048 | Draft New WID on Security aspect of 5WWC | WID new | Nokia, Nokia Shanghai Bell | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
noted | [WTS] [JSN] | ||
S3-230049 | Scope section alignment | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230050 | updating the existing solution mapping | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230051 | TNAP mobility architecture assumptions | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230052 | new solution for AUN3 device supporting 5G Key hierarchy (i.e. N5CW) | pCR | Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230053 | update conclusion for KI1 | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-230054 | solution 5 update |
pCR revised to S3-230426 |
Nokia, Nokia Shanghai Bell, Lenovo | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-230055 | solution 6 update |
pCR revised to S3-230427 |
Nokia, Nokia Shanghai Bell, Lenovo | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-230056 | Discussion on privacy issue in AKMA | discussion | Nokia, Nokia Shanghai Bell, Samsung | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] | |
S3-230057 | key issue on AKMA privacy | pCR | Nokia, Nokia Shanghai Bell, Samsung | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230058 | conclusion updates | pCR | Nokia, Nokia Shanghai Bell | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230059 | Discussion paper for MPS support over WLAN and relationship with HNTRA | pCR | Nokia, Nokia Shanghai Bell | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-230060 | Conclusion enhancement for MPS support over WLAN | pCR | Nokia, Nokia Shanghai Bell | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-230061 | Update to KI#1 Providing VPLMN slice information to roaming UE | pCR | Lenovo | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230062 | Solution to KI#1 eNS | pCR | Lenovo | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230063 | Evaluation to Solution #8 |
pCR revised to S3-230446 |
Lenovo | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-230064 | Update to Solution #9 in eNA |
pCR revised to S3-230447 |
Lenovo | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230065 | Cyber attack detection |
pCR revised to S3-230448 |
Lenovo | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230066 | Conclusion to KI#1 Direct C2 Security |
pCR revised to S3-230449 |
Lenovo | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-230067 | Conclusion to KI#2 Security of DAA unicast connection |
pCR revised to S3-230450 |
Lenovo | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-230068 | Conclusion to KI#3 Direct C2 Authorization | pCR | Lenovo | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-230069 | Update to Solution #4 in SNAAPPY |
pCR revised to S3-230451 |
Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230070 | Solution to address KI#2 |
pCR revised to S3-230452 |
Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230071 | Conclusion to KI#1 in SNAAPPY | pCR | Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230072 | Conclusion to KI#2 in SNAAPPY | pCR | Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230073 | Solution to Key Issue #2 |
pCR revised to S3-230453 |
Lenovo | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230074 | Sol#3 Resolution of EN on root certificate provisioning | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230075 | Sol#3 Resolution of EN on cross UE API access | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230076 | Sol#3 Resolution of EN on Uastar protocol | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230077 | Sol#3 Resolution of EN on Mutual Authentication |
pCR revised to S3-230520 |
Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230078 | Sol#3 Resolution of EN on Client Credential Grant |
pCR revised to S3-230522 |
Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230079 | KI#1 New Sol for local PINE authentication | pCR | Nokia, Nokia Shanghai Bell | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230080 | New solution addressing KI#6 | pCR | Lenovo, Nokia | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-230081 | Evaluation of Solution#4 |
pCR revised to S3-230574 |
Lenovo | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230082 | Removal of EN in Solution#4 | pCR | Lenovo | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230083 | Removal of EN in Solution#7 | pCR | Lenovo | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-230084 | 33.896: Updates to Key Issue on User Consent for NTN | pCR | Google Inc. | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230085 | Discussion on KI#1 | discussion | Huawei, HiSilicon | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] | |
S3-230086 | KI#1 update | pCR | Huawei, HiSilicon | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230087 | Update to KI#3 | pCR | Huawei, HiSilicon | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230088 | New solution to KI#1 | pCR | Huawei, HiSilicon | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230089 | New key issue on SoR AF | pCR | Huawei, HiSilicon | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230090 | New solution to prevent S-NSSAI leakage | pCR | Huawei, HiSilicon | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230091 | Evaluation for solution#1 |
pCR revised to S3-230456 |
China Telecommunications | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230092 | address EN for solution#2 | pCR | Huawei, HiSilicon | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-230093 | Adding conclusion on KI#1 | pCR | Huawei, HiSilicon | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
noted | [WTS] [JSN] |
S3-230094 | Adding conclusion on KI#3 | pCR | Huawei, HiSilicon | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-230095 | address EN for solution#4 |
pCR revised to S3-230569 |
Huawei, HiSilicon | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-230096 | Adding conclusion on KI#2 | pCR | Huawei, HiSilicon | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
noted | [WTS] [JSN] |
S3-230097 | Conclusion on KI#2.1 |
pCR revised to S3-230571 |
Huawei, HiSilicon, Thales | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230098 | Conclusion on KI#2.2 | pCR | Huawei, HiSilicon, Thales | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-230099 | Conclusion on KI#2.6 |
pCR revised to S3-230572 |
Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230100 | Adding the overview of the EDGE | pCR | Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230101 | Resolving EN in solution#1 | pCR | China Telecommunications | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230102 | New solution to KI#2 |
pCR revised to S3-230457 |
China Telecommunications | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230103 | Update the KI#6 |
pCR revised to S3-230485 |
ZTE Corporation | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230104 | New solution for the KI#6 | pCR | ZTE Corporation | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230105 | Conclusion for the KI#6 | pCR | ZTE Corporation | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230106 | Add editors note to solution 5 |
pCR revised to S3-230487 |
ZTE Corporation | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-230107 | Add editors note to solution 11 | pCR | ZTE Corporation | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230108 | Address EN for solution 9 | pCR | ZTE Corporation | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230109 | AUSF stores SN ID after primary authentication in solution 1 | pCR | ZTE Corporation | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230110 | AUSF stores SN ID after primary authentication in solution 6 | pCR | ZTE Corporation | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230111 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230112 | update the Key issue of AKMA roaming | pCR | ZTE Corporation | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230113 | Add conclusion to KI#1 | pCR | ZTE Corporation | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-230114 | Add conclusion to KI#2.2 | pCR | ZTE Corporation | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-230115 | Add evaluation to solution #6 |
pCR revised to S3-230489 |
ZTE Corporation | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230116 | Add conclusion for KI#1 | pCR | ZTE Corporation | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230117 | Add conclusion for KI#2 | pCR | ZTE Corporation | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230118 | Add evaluation for solution#4 | pCR | ZTE Corporation | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230119 | New solution to KI#1 protecting SoR container from UDM to UE | pCR | ZTE Corporation | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230120 | New solution to KI#1 protecting UE assistance information | pCR | ZTE Corporation | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230121 | Update to KI#1 providing VPLMN slice information to roaming UE | pCR | ZTE Corporation | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230122 | Add a new solution to KI#2 |
pCR revised to S3-230490 |
ZTE Corporation | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230123 | New solution to KI#5 |
pCR revised to S3-230459 |
China Telecommunications | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230124 | LS on clarification on user consent for AIML |
LS out LS To: SA2 revised to S3-230491 |
OPPO |
S3-109-ad hoc-e AI: 5.2 |
revised | [WTS] [JSN] | |||
S3-230125 | New KI on security of ranging usiong assistance UE | pCR | OPPO | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230126 | Resolving EN for Solution 22 |
pCR revised to S3-230492 |
OPPO | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230127 | KI1 corrections | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230128 | KI1 sol13 EN resolution |
pCR revised to S3-230577 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230129 | KI1 analysis update |
pCR revised to S3-230578 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230130 | KI3 sol12 EN resolution | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230131 | KI4 analysis and conclusion update |
pCR revised to S3-230579 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230132 | KI3 sol15 EN resolution | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230133 | KI5 sol16 EN resolution |
pCR revised to S3-230580 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230134 | KI6 conclusion update |
pCR revised to S3-230581 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230135 | KI7 Sol17 EN resolution | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230136 | KI8 conclusion update |
pCR revised to S3-230582 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230137 | KI10 analysis and conclusion on RHUB | pCR | Nokia, Nokia Shanghai Bell, BSI | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230138 | KI10 sol20 EN resolution – reference to new study | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230139 | KI11 resolution of ENs in sol21 and sol22 by adding the related solution | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-230140 | KI12 sol19 EN resolution – reference to new study | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230141 | KI12 Hosted SEPP solution |
pCR revised to S3-230583 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230142 | KI12 analysis and conclusion on hosted SEPP | pCR | Nokia, Nokia Shanghai Bell, BSI | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230143 | Study on 5G roaming topics |
pCR revised to S3-230576 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230144 | SID on 5G roaming issues | SID new | Nokia, Nokia Shanghai Bell |
S3-109-ad hoc-e AI: 5.24 |
noted | [WTS] [JSN] | |||
S3-230145 | Minor editorial corrections in Solution #5 | pCR | LG Electronics | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230146 | Minor editorial corrections in Solution #12 | pCR | LG Electronics | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230147 | Evaluation for Solution #5 | pCR | LG Electronics | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230148 | Evaluation for Solution #12 | pCR | LG Electronics | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230149 | A new solution to address the privacy issue with TMGI | pCR | Huawei, HiSilicon | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-230150 | conclusion on key issue 2 | pCR | Huawei, HiSilicon | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-230151 | Addressing the editor's note in solution 3 |
pCR revised to S3-230466 |
Huawei, HiSilicon | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
revised | [WTS] [JSN] |
S3-230152 | Discussion paper on way forward of key issue#1 | discussion | Huawei, HiSilicon | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
noted | [WTS] [JSN] | |
S3-230153 | conclusion on key issue 1 | pCR | Huawei, HiSilicon | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-230154 | update to solution 3 |
pCR revised to S3-230467 |
Huawei, HiSilicon | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230155 | update the evaluation in solution 1 |
pCR revised to S3-230468 |
Huawei, HiSilicon | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230156 | conclusion on key issue 1 | pCR | Huawei, HiSilicon | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230157 | Addressing the editor's note in solution 1 |
pCR revised to S3-230469 |
Huawei, HiSilicon | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-230158 | Addressing the ENs in solution 15 | pCR | Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230159 | Addressing the ENs in solution 16 | pCR | Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230160 | Evaluation to solution 15 |
pCR revised to S3-230470 |
Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230161 | Evaluation to solution 16 |
pCR revised to S3-230471 |
Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230162 | A new KI for security about EAS discovery procedure via V-EASDF | pCR | Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230163 | A new solution to security about EAS discovery procedure via V-EASDF |
pCR revised to S3-230472 |
Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230164 | Conclusion on KI1.x Security about EAS discovery procedure via V-EASDF | pCR | Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-230165 | Key Issue Update on User Consent for NTN |
pCR revised to S3-230473 |
Huawei, HiSilicon | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-230166 | Implict User Consent for NTN feature usage | pCR | Huawei, HiSilicon | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230167 | Conclusion for key issue #2 | pCR | Huawei, HiSilicon | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230168 | User consent for roaming scenarios where the data source is in vPLMN | pCR | Huawei, HiSilicon | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230169 | User consent for roaming scenarios where the data source is in hPLMN | pCR | Huawei, HiSilicon | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230170 | Conclusion for key issue #1 |
pCR revised to S3-230474 |
Huawei, HiSilicon | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-230171 | Conclusion for key issue #4 | pCR | Huawei, HiSilicon | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230172 | Address EN for solution 1: onboarding |
pCR revised to S3-230475 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230173 | Address EN for solution 1: detail for token | pCR | Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230174 | Address EN for solution 1: authorization decision |
pCR revised to S3-230476 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230175 | Evaluation Update on Solution 1 |
pCR revised to S3-230477 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230176 | New Solution on OAuth2.0 Token Revocation | pCR | Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230177 | Role mapping from TR 23.700-95 | pCR | Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230178 | Conclusion for key issue #2 | pCR | Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230179 | new pcr | pCR | Huawei, HiSilicon | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-230180 | Add conclusion to KI#2 about DAA unicast security | pCR | Huawei, HiSilicon | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-230181 | Add conclusion to KI#1 about Direct C2 security | pCR | Huawei, HiSilicon | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-230182 | New solution of security for the Ranging SL positioning device discovery | pCR | Huawei, HiSilicon | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230183 | New solution for protecting direct communnication | pCR | Huawei, HiSilicon | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230184 | New solution to select assistant ranging procedure based on privacy requirement | pCR | Huawei, HiSilicon | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230185 | Address EN for So#l26 |
pCR revised to S3-230478 |
Huawei, HiSilicon | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230186 | Evaluate to the solution #20 |
pCR revised to S3-230479 |
Huawei, HiSilicon | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230187 | Evaluate to the solution #26 | pCR | Huawei, HiSilicon | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230188 | conclude to KI #2 | pCR | Huawei, HiSilicon | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230189 | Conclusion for KI#2 | pCR | Intel | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-230190 | Add Usecases to Solution 10 |
pCR revised to S3-230523 |
Intel | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230191 | Add Evaluation for ProSe Security Sol#6 | pCR | OPPO | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230192 | Address an EN in Sol #11 | pCR | OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230193 | A new solution on KI#4 |
pCR revised to S3-230480 |
Huawei, HiSilicon | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-230194 | Proposed new threat and requirement to KI#3 | pCR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230195 | New solution to KI#3 | pCR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230196 | conclusion to KI#3 |
pCR revised to S3-230481 |
Huawei, HiSilicon | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-230197 | add new conclusion to key issue#1 | pCR | Huawei, HiSilicon | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230198 | Delete EN in solution#4 | pCR | Huawei, HiSilicon | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-230199 | Delete EN in solution#9 | pCR | Huawei, HiSilicon | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-230200 | Delete EN in solution#12 | pCR | Huawei, HiSilicon | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-230201 | Propose conclusion to KI#1 | pCR | Huawei, HiSilicon | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230202 | Conclusion for KI 2.2 of EDGE Security | pCR | OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-230203 | Conclusion for KI#3 | pCR | Intel | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-230204 | Resolving ENs in solution #9 of EDGE security |
pCR revised to S3-230495 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230205 | Conclusion for KI#2 | pCR | Intel | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-230206 | Resolving ENs in solution #10 of EDGE security |
pCR revised to S3-230505 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230207 | evaluation of TR33.740 Solution 8 | pCR | China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230208 | Resolving ENs in solution #11 of EDGE security |
pCR revised to S3-230508 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230209 | FL GROUP AUTHORIZATION OF NWDAF(S) IN 5GC |
pCR revised to S3-230524 |
Intel | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230210 | Address an EN in Sol #9 of EDGE security |
pCR revised to S3-230509 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230211 | Address an EN in Sol #10 of EDGE security |
pCR revised to S3-230511 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230212 | evaluation of TR33.740 Solution 11 | pCR | China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230213 | Address some ENs in Sol #11 of EDGE security | pCR | OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230214 | Add evaluation in Sol#11 of EDGE security |
pCR revised to S3-230512 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230215 | pCR to update TR33.740 Solution 11 | pCR | China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230216 | Conclusion to the KI#1 | pCR | China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230217 | New solution on reusing existing authorization mechanism for 5G assistance information exposure to AF | pCR | OPPO | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-230218 | New solution on authorization for 5GC assistance information exposure to external AF |
pCR revised to S3-230513 |
OPPO | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-230219 | evaluation to TR33.740 Solution 9 | pCR | China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230220 | New solution on authorization for 5GC assistance information exposure to internal AF |
pCR revised to S3-230514 |
OPPO | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-230221 | Update to the evaluation of solution 23 |
pCR revised to S3-230548 |
China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230222 | New solution on authorization for 5GC assistance information exposure to internal AF | pCR | OPPO | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
withdrawn | [WTS] [JSN] |
S3-230223 | New solution on privacy protection for 5GC assistance information exposure to AF |
pCR revised to S3-230516 |
OPPO | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-230224 | A new solution for EEC authentication utilizing tokens |
pCR revised to S3-230484 |
Ericsson | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230225 | Updating solution #17 | pCR | Ericsson | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230226 | Resolving ENs in solution#13 | pCR | Ericsson | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230227 | Resolving ENs in solution#14 | pCR | Ericsson | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230228 | Conclusion for KI#2.1 | pCR | Ericsson | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-230229 | Conclusion for KI#2.2 | pCR | Ericsson | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-230230 | A solution for authorization before allowing access to resources |
pCR revised to S3-230486 |
Ericsson | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230231 | Conclusions for KI#1 |
pCR revised to S3-230429 |
Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230232 | Solution to KI#1 – NSWO in SNPN with CH AUSF/UDM |
pCR revised to S3-230431 |
Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230233 | Evaluation of Solution#9 – NSWO in SNPN |
pCR revised to S3-230432 |
Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230234 | Update to the evaluation of solution 24 |
pCR revised to S3-230549 |
China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230235 | Update to conclusion of KI#2 in TR 33.740 | pCR | China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230236 | Update to solution#6 in TR 33.893 - add authorization check step | pCR | China Telecom Corporation Ltd. | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230237 | EN related to Key Refresh and revocation |
pCR revised to S3-230525 |
Intel | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230238 | Update to solution#6 in TR 33.893 - SLPK ID usage | pCR | China Telecom Corporation Ltd. | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230239 | New solution for KI#2 to support authorization of participant NWDAFs in FL |
pCR revised to S3-230443 |
Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230240 | ENs resolving and evaluation for solution #10 |
pCR revised to S3-230442 |
Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230241 | Evaluation to Solution #11 | pCR | Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230242 | Evaluation to Solution #12 | pCR | Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230243 | Evaluation to Solution #13 | pCR | Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230244 | Adding conclusion on KI#3 | pCR | Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-230245 | Update of Solution #11: Resolving Editor's Note on scenarios in SA2 |
pCR revised to S3-230444 |
Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230246 | Update of Solution #11: Resolving Editor's Note in the evaluation | pCR | Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-230247 | Conclusion for KI#2 "Authentication for UE access to hosting network" |
pCR revised to S3-230445 |
Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230248 | New WID on Security aspects of enhanced support of Non-Public Networks phase 2 | WID new | Ericsson | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-230249 | update to KI#2 temporary network slice | pCR | Nokia, Nokia Shanghai Bell | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230250 | solution for KI#2 temporary network slice for NSSAA | pCR | Nokia, Nokia Shanghai Bell | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230251 | update to KI#3 network slice admission control | pCR | Nokia, Nokia Shanghai Bell | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-230252 | security solution for KI#3 network slice admission control | pCR | Nokia, Nokia Shanghai Bell | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230253 | EN removal for solution#27 |
pCR revised to S3-230586 |
Nokia, Nokia Shanghai Bell | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230254 | Resolve EN’s in Solution #27 |
pCR revised to S3-230497 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230255 | Evaluation to Solution #27 |
pCR revised to S3-230498 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230256 | Evaluation to solution #4 |
pCR revised to S3-230499 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230257 | Update to solution #30 |
pCR revised to S3-230500 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230258 | New security solution on discovery integrated into PC5 link establishment when L3 UE-to-UE relay is in coverage |
pCR revised to S3-230501 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230259 | New solution with authorization tokens exchanged after PC5 security establishment |
pCR revised to S3-230502 |
Ericsson | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230260 | Update of evaluation to solution #2 |
pCR revised to S3-230503 |
Ericsson | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230261 | Update of evaluation to solution #3 |
pCR revised to S3-230504 |
Ericsson | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230262 | LS on data and analytics exchange in roaming case in eNA |
LS out LS To: 3GPP SA2 |
China mobile | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
noted | [WTS] [JSN] | |
S3-230263 | Evaluation and EN resolving for solution #14 |
pCR revised to S3-230546 |
China mobile | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230264 | Conclusion for key issue#1 | pCR | China mobile | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-230265 | Conclusion for key issue#5 | pCR | China mobile | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-230266 | ProSe - Evaluation Solution #10 |
pCR revised to S3-230454 |
Philips International B.V. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230267 | ProSe - Editorials Solution #10 | pCR | Philips International B.V. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230268 | ProSe - Evaluation Solution #15 |
pCR revised to S3-230455 |
Philips International B.V. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230269 | PIN - Evaluation Solution #4 | pCR | Philips International B.V. | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230270 | AKMA - Evaluation Solution #10 | pCR | Philips International B.V. | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230271 | AKMA - Editorials Clause 4 | pCR | Philips International B.V. | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230272 | Ranging - New solution KI#1, #2, #3 | pCR | Philips International B.V. | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230273 | Ranging - Update Key Issue #1- privacy risks of exposing positioning reference signals | pCR | Philips International B.V. | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230274 | Completion of solution #14 |
pCR revised to S3-230458 |
THALES | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-230275 | Conclusion to Key Issue #1 | pCR | THALES | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230276 | Key Issue #1 | pCR | THALES | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230277 | Resolve EN on discovery in solution #3 | pCR | Qualcomm Incorporated | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230278 | Resolve EN on pairing in solution #3 | pCR | Qualcomm Incorporated | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230279 | Evaluation of solution #3 | pCR | Qualcomm Incorporated | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230280 | Editorial changes to UAS TR | pCR | Qualcomm Incorporated | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230281 | Conclusion for key issue #1 | pCR | Qualcomm Incorporated | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-230282 | Conclusion for key issue #2 | pCR | Qualcomm Incorporated | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-230283 | Additional to conclusion for key issue #3 | pCR | Qualcomm Incorporated | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-230284 | Conclusion for key issue #7 | pCR | Qualcomm Incorporated | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230285 | Resolving the editor’s note in solution #7 |
pCR revised to S3-230439 |
Qualcomm Incorporated | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-230286 | Evaluation of solution #7 | pCR | Qualcomm Incorporated | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-230287 | Resolving the ENs in solution #22 |
pCR revised to S3-230440 |
Qualcomm Incorporated | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230288 | Providing evaluation for solution #22 | pCR | Qualcomm Incorporated | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-230289 | Common authentication method between EEC and ECS/EES |
pCR revision of S3-223363 |
Qualcomm Incorporated | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-230290 | Conclusion for key issue #1 | pCR | Qualcomm Incorporated | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
noted | [WTS] [JSN] |
S3-230291 | Proposed addition to the conclusions | pCR | Qualcomm Incorporated | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-230292 | Updates on the solution #23 | pCR | Qualcomm Incorporated | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230293 | Updates on the solution #24 | pCR | Qualcomm Incorporated | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230294 | LS on UE-to-UE relay discovery direct discovery |
LS out LS To: SA2 |
Qualcomm Incorporated | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] | |
S3-230295 | Add an evaluation of solution #8 | pCR | Qualcomm Incorporated | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230296 | Add an evaluation of solution #9 | pCR | Qualcomm Incorporated | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230297 | Add an evaluation of solution #11 | pCR | Qualcomm Incorporated | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230298 | Updates to the solution #25 |
pCR revised to S3-230528 |
Qualcomm Incorporated | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230299 | reply LS on SL positioning groupcast and broadcast |
LS out LS is reply to S3-230007 LS To: RAN2 |
Qualcomm Incorporated | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
merged | [WTS] [JSN] | |
S3-230300 | Updates to the Key Issue #4 |
pCR revised to S3-230527 |
Qualcomm Incorporated | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230301 | A new solution for groupcast protection for Ranging/SL Positioning services | pCR | Qualcomm Incorporated | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230302 | A new solution for mitigating privacy attacks exploiting group paging with TMGI | pCR | Qualcomm Incorporated | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-230303 | Reply LS on user consent of Non-public Network |
LS out LS is reply to S3-230008 LS To: RAN3 |
Qualcomm Incorporated | NR_ENDC_SON_MDT_enh2-Core | Rel-18 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | |
S3-230304 | Solution to KI#1 – NSWO in SNPN with CH AAA |
pCR revised to S3-230521 |
Qualcomm Incorporated | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230305 | Resolution of EN#1 in Solution#7 for KI#1 | pCR | Qualcomm Incorporated | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230306 | Resolution of EN#2 in Solution#7 for KI#1 | pCR | Qualcomm Incorporated | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-230307 | MEC - New key issue on secure retrieve of UE ID | pCR | Apple | 33.739 0.3.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-230308 | MEC - Discussion paper on enformcement of AF specific identifier | discussion | Apple | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
noted | [WTS] [JSN] | ||
S3-230309 | MEC - LS to SA2 on enforcement of AF specific identifier |
LS out LS To: SA2 revised to S3-230462 |
Apple | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] | ||
S3-230310 | Reply LS to S3-230017/S6-223558 on the use of a non-network defined identifier for UE identification |
LS out LS To: SA6 |
Apple | Rel-18 |
S3-109-ad hoc-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-230311 | Reply LS to S3-230018/S6-223586 on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network |
LS out LS To: SA6 revised to S3-230463 |
Apple | Rel-18 |
S3-109-ad hoc-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-230312 | Reply LS to R2-2213142 on SL positioning |
LS out LS To: RAN2 revised to S3-230430 |
Apple | Rel-18 |
S3-109-ad hoc-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-230313 | New Solution to KI #11 based on Nnrf_AccesToken Service | pCR | Ericsson LM | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-230314 | New Solution to KI #11 based on O&M Provisioning NRF with NFc profile | pCR | Ericsson LM | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-230315 | Discussion. Key issue #12: Security in Hosted SEPP scenarios | discussion | Ericsson | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
noted | [WTS] [JSN] | |
S3-230316 | Update of Key issue #12: Security in Hosted SEPP scenarios |
pCR revised to S3-230585 |
Ericsson | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230317 | Solution for KI#12: Security in Hosted SEPP scenarios | pCR | Ericsson | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-230318 | Evaluation of solution #5 | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230319 | Evaluation of solution #12 |
pCR revised to S3-230460 |
Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230320 | Evaluation of solution #13 |
pCR revised to S3-230461 |
Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-230321 | Proposal for a conclusion on KI#1 | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-230322 | Proposal for a conclusion on KI#2 | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-230323 | Discussion paper concerning conclusion of KI#1 | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-230324 | Discussion paper concerning conclusion of KI#2 | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-230325 | Key Issue on KAF refresh | pCR | Samsung | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230326 | Update on use case clause and solution #6 | pCR | Samsung | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-230327 | EN Resolution and Evaluation of Sol #19 |
pCR revised to S3-230536 |
Samsung | 33.740 0.4.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230328 | EN Resolutions and Evaluation of Sol #29 |
pCR revised to S3-230537 |
Samsung | 33.740 0.4.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230329 | Resolving EN in solution#3 (TR 33.739) |
pCR revised to S3-230538 |
Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230330 | Resolving EN and updating evaluation in solution#4 (TR 33.739) |
pCR revised to S3-230539 |
Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230331 | Solution on Public key signature based authentication |
pCR revised to S3-230540 |
Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230332 | Evaluation for solution#22 | pCR | Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-230333 | Conclusion for KI#2.1 | pCR | Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-230334 | Conclusion for KI#2.2 |
pCR revised to S3-230541 |
Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-230335 | Updates to solution#1 in TR 33.883 |
pCR revised to S3-230542 |
Samsung | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
revised | [WTS] [JSN] |
S3-230336 | [MBS] Conclusion for Key Issue#1 | pCR | Samsung | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-230337 | Update of Key Issue #2 |
pCR revised to S3-230543 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230338 | New Solution on Resource owner Authorization in API Invocation using OAuth 2.0 Authorization Code Grant |
pCR revised to S3-230544 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230339 | New Solution on Resource owner Authorization in API Invocation |
pCR revised to S3-230545 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230340 | Evaluation for Solution #6 | pCR | Nokia, Nokia Shanghai Bell | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-230341 | Discussion paper on KI#3 related solutions evaluation. | discussion | Nokia, Nokia Shanghai Bell, China Mobile (Suzhou) Software | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
noted | [WTS] [JSN] | ||
S3-230342 | Adding conclusion on KI#1 |
pCR revised to S3-230506 |
Nokia, Nokia Shanghai Bell | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230343 | Solution for authorization in FL |
pCR revised to S3-230488 |
Nokia, Nokia Shanghai Bell | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230344 | Adding conclusion on KI#3 |
pCR revised to S3-230510 |
Nokia, Nokia Shanghai Bell, China Mobile (Suzhou) Software | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-230345 | pCR to TR33.740 Update Solution16 for removing ENs |
pCR revised to S3-230550 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230346 | pCR to TR33.740 Update Solution17 for removing ENs |
pCR revised to S3-230551 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230347 | pCR to TR33.740 Update Solution18 for removing ENs and add evaluation |
pCR revised to S3-230552 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230348 | pCR to TR33.740 Update Solution28 for removing ENs |
pCR revised to S3-230553 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230349 | pCR to TR33.740 Evaluation of Solution28 |
pCR revised to S3-230554 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230350 | pCR to TR33.740 Conclusion of key issue #1 | pCR | CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230351 | pCR to TR33.740 Conclusion of key issue #2 | pCR | CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230352 | pCR to TR33.740 Conclusion of key issue #3 | pCR | CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230353 | pCR to TR33.893 New key issue on groupcast and broadcast security |
pCR revised to S3-230566 |
CATT | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230354 | pCR to TR33.893 New solution for protecting groupcast and broadcast data in coverage | pCR | CATT | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230355 | pCR to TR33.893 New solution for protecting groupcast and broadcast data in out of coverage | pCR | CATT | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230356 | Reply LS on SL positioning groupcast and broadcast |
LS out LS is reply to R2-2213142 LS To: RAN2 |
CATT | Rel-18 |
S3-109-ad hoc-e AI: 3 |
merged | [WTS] [JSN] | ||
S3-230357 | [Draft] Reply LS on SL positioning groupcast and broadcast |
LS out LS is reply to S3-230007 source LS: R2-2213142 LS To: RAN2 |
Xiaomi Technology | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
merged | [WTS] [JSN] | |
S3-230358 | 33.893: Additional Evaluation for Solution #1 | pCR | Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230359 | 33.893: Update to Solution #2 |
pCR revised to S3-230559 |
Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230360 | 33.893: Resolve the Editor’s Note in Solution #4 | pCR | Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230361 | 33.893: Evaluation for Solution #4 |
pCR revised to S3-230560 |
Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230362 | 33.893: Evaluation for Solution #6 |
pCR revised to S3-230562 |
Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230363 | 33.893: Resolve the Editor’s Note in Solution #7 | pCR | Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230364 | 33.893: New Solution on Token-based Authorization of the Role of the UE during Discovery | pCR | Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230365 | 33.893: New Solution on Role Verification during Discovery based on Discovery Keys | pCR | Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-230366 | 33.893: New Solution on Authorization of SL Positioning Client UE for Obtaining Ranging Result |
pCR revised to S3-230561 |
Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230367 | 33.700-28: Add Potential Requirements for Key Issue #1 |
pCR revised to S3-230563 |
Xiaomi Technology | 33.700-28 0.2.0 | FS_5GSAT_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.25 |
revised | [WTS] [JSN] |
S3-230368 | 33.700-28: New Key Issue on Protection of UE Unreachability Period retrieved by the UE | pCR | Xiaomi Technology | 33.700-28 0.2.0 | FS_5GSAT_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.25 |
noted | [WTS] [JSN] |
S3-230369 | 33.700-28: New Solution to KI#1 for AF Authorization on per UE Level | pCR | Xiaomi Technology | 33.700-28 0.2.0 | FS_5GSAT_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.25 |
noted | [WTS] [JSN] |
S3-230370 | 33.896: Evaluation for Solution #1 | pCR | Xiaomi Technology | 33.896 0.4.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230371 | 33.896: Evaluation for Solution #2 | pCR | Xiaomi Technology | 33.896 0.4.0 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230372 | KI #1, New Sol on OAuth 2.0 based 5GC assistance information exposure authorization | pCR | Xiaomi communications | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-230373 | TR 33.898 Resolve EN for sol #2 | pCR | Xiaomi communications | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-230374 | new Sol on AKMA roaming in multiple registration scenarios | pCR | Xiaomi communications | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230375 | TR 33.737 Evaluation for sol #15 |
pCR revised to S3-230533 |
Xiaomi communications | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-230376 | TR 33.737 Conclusion for KI #1 | pCR | Xiaomi communications | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230377 | Conclusion for KI 2.1 Authentication and authorization of the EEC UE by the ECS EES. | pCR | Xiaomi communications | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-230378 | Conclusion for KI 2.2 Authentication mechanism selection between EEC and ECSEES | pCR | Xiaomi communications | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-230379 | TR 33.379 Evaluation for Sol #5 | pCR | Xiaomi communications | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230380 | TR 33.379 Resolve ENs for sol #1 and #2 | pCR | Xiaomi communications | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230381 | TR 33.379 Resolve ENs for Sol #5 | pCR | Xiaomi communications | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230382 | TR 33.858 Evaluation for Sol #1 | pCR | Xiaomi communications | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230383 | TR 33.858 Evaluation for Sol #2 | pCR | Xiaomi communications | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230384 | TR 33.858 Evaluation for Sol #4 | pCR | Xiaomi communications | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230385 | TR 33.882 Resolve ENs for sol #5 |
pCR revised to S3-230531 |
Xiaomi communications | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-230386 | KI #2, new Sol on AF authorization in PIN scenarios | pCR | Xiaomi communications | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-230387 | KI #2 update for partly allowed rejected S-NSSAI | pCR | Xiaomi communications | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230388 | New Sol on authorization mechanism for partly rejected S-NSSAI | pCR | Xiaomi communications | 33.886 0.2.0 | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-230389 | KI#2, New Sol OAuth 2.0 based API invocation procedure |
pCR revised to S3-230534 |
Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230390 | KI#2, New Sol on User authorization revocation for API invocation procedure | pCR | Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230391 | KI#2, New Sol UE credential based API invocation procedure |
pCR revised to S3-230535 |
Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230392 | Update to solution #8 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230393 | Update to solution #9 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230394 | Evaluation of solution #8 in TR 33.740 |
pCR revised to S3-230556 |
Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230395 | Evaluation of solution #9 in TR 33.740 |
pCR revised to S3-230557 |
Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230396 | Remove the Editor's Note and evaluate the solution #7 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230397 | Remove the Editor's Notes of solution #20 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230398 | Evaluation of solution #30 in TR 33.740 |
pCR revised to S3-230558 |
Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-230399 | Conclusion on Key Issue #1 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230400 | Conclusion on Key Issue #2 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230401 | Conclusion on Key Issue #3 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230402 | Conclusion on Key Issue #4 in TR 33.740 | pCR | Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-230403 | New solution on Ranging/SL Positioning discovery and link establishment procedure for V2X capable UEs | pCR | Beijing Xiaomi Mobile Software | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230404 | Remove the Editor's Note of solution #3 in TR 33.893 | pCR | Beijing Xiaomi Mobile Software | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230405 | Remove the Editor's Note of solution #5 in TR 33.893 |
pCR revised to S3-230555 |
Beijing Xiaomi Mobile Software | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-230406 | Remove the Editor's Note and evaluate the solution #3 in TR 33.896 | pCR | Beijing Xiaomi Mobile Software | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-230407 | Remove the Editor's Note and evaluate the solution #4 in TR 33.896 | pCR | Beijing Xiaomi Mobile Software | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230408 | Conclusion on Key Issue #1 in TR 33.896 | pCR | Beijing Xiaomi Mobile Software | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
merged | [WTS] [JSN] |
S3-230409 | New Key issue on the security of the information transfer of the RAN AI/ML framework | pCR | Ericsson | 33.877 0.4.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-230410 | KI2 conclusion | pCR | Ericsson | 33.877 0.4.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-230411 | Solution 12 updates | pCR | Ericsson | 33.741 0.4.0 | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-230412 | Resolve_EN_solution#5 |
pCR revised to S3-230568 |
Ericsson | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-230413 | Resolve_ENs_solution#1 | pCR | Ericsson | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-230414 | KI and Solution on user consent in roaming | pCR | Nokia, Nokia Shanghai Bell | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230415 | Sol update central authorization for user consent handling | pCR | Nokia, Nokia Shanghai Bell | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-230416 | Key issue on authentication of N5CW devices behind RG | pCR | CableLabs, Nokia, Nokia Shanghai Bell, Rogers Communications | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-230417 | Key issue on authentication of UE behind RG |
pCR revised to S3-230526 |
CableLabs, Rogers Communications | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-230418 | Solution for authentication of UE behind RG using NSWO | pCR | CableLabs, Rogers Communications | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230419 | Key issue on authentication of AUN3 device without 5G credentials | pCR | CableLabs | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-230420 | adding new use case in KI1 | pCR | Nokia, Nokia Shanghai Bell | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-230421 | pCR to 33.884 updating solution #2 |
pCR revised to S3-230515 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230422 | pCR to 33.884 adding new solution: PKCE flow |
pCR revised to S3-230517 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230423 | pCR to 33.884 adding new solution: token validation |
pCR revised to S3-230518 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230424 | Solution for authentication of AUN3 device without 5G Creden | pCR | CableLabs | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-230425 | Draft 33.887 Study on Security aspects for 5WWC Phase 2 | draft TR | Nokia, Nokia Shanghai Bell | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] | |
S3-230426 | solution 5 update |
pCR revision of S3-230054 |
Nokia, Nokia Shanghai Bell, Lenovo | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230427 | solution 6 update |
pCR revision of S3-230055 |
Nokia, Nokia Shanghai Bell, Lenovo | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230428 | TR 33.875-160 | draft TR | Nokia, Nokia Shanghai Bell | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] | |
S3-230429 | Conclusions for KI#1 |
pCR revision of S3-230231 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230430 | Reply LS to R2-2213142 on SL positioning |
LS out LS is reply to S3-230007 LS To: RAN2,SA2 revision of S3-230312 |
Apple | Rel-18 |
S3-109-ad hoc-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-230431 | Solution to KI#1 – NSWO in SNPN with CH AUSF/UDM |
pCR revision of S3-230232 |
Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230432 | Evaluation of Solution#9 – NSWO in SNPN |
pCR revision of S3-230233 |
Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230433 | Update conclusion TR 33.891 KI #3 |
pCR revision of S3-230025 |
InterDigital, Europe, Ltd., Lenovo, Qualcomm | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230434 | Update conclusion TR 33.891 KI #4. |
pCR revision of S3-230026 |
InterDigital, Europe, Ltd. | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230435 | Evaluation TR 33.740 Sol #1 |
pCR revision of S3-230028 |
InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230436 | Evaluation TR 33.740 Sol #12 |
pCR revision of S3-230029 |
InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230437 | Evaluation TR 33.740 Sol #13 |
pCR revision of S3-230030 |
InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230438 | Update to TR 33.740 Conclusion for KI#4 |
pCR revision of S3-230033 |
InterDigital, Europe, Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230439 | Resolving the editor’s note in solution #7 |
pCR revision of S3-230285 |
Qualcomm Incorporated | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230440 | Resolving the ENs in solution #22 |
pCR revision of S3-230287 |
Qualcomm Incorporated | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230441 | Draft TR 33.891 |
draft TR revision of S3-224112 |
Qualcomm | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] | |
S3-230442 | ENs resolving and evaluation for solution #10 |
pCR revision of S3-230240 |
Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230443 | New solution for KI#2 to support authorization of participant NWDAFs in FL |
pCR revision of S3-230239 |
Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230444 | Update of Solution #11: Resolving Editor's Note on scenarios in SA2 |
pCR revision of S3-230245 |
Ericsson | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230445 | Conclusion for KI#2 "Authentication for UE access to hosting network" |
pCR revision of S3-230247 |
Ericsson, Intel, Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230446 | Evaluation to Solution #8 |
pCR revision of S3-230063 |
Lenovo | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230447 | Update to Solution #9 in eNA |
pCR revision of S3-230064 |
Lenovo | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230448 | Cyber attack detection |
pCR revision of S3-230065 |
Lenovo | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230449 | Conclusion to KI#1 Direct C2 Security |
pCR revision of S3-230066 |
Lenovo, Qualcomm, Huawei, Interdigital | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230450 | Conclusion to KI#2 Security of DAA unicast connection |
pCR revision of S3-230067 |
Lenovo, Huawei, Qualcomm | 33.891 0.4.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-230451 | Update to Solution #4 in SNAAPPY |
pCR revision of S3-230069 |
Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230452 | Solution to address KI#2 |
pCR revision of S3-230070 |
Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230453 | Solution to Key Issue #2 |
pCR revision of S3-230073 |
Lenovo | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230454 | ProSe - Evaluation Solution #10 |
pCR revision of S3-230266 |
Philips International B.V. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230455 | ProSe - Evaluation Solution #15 |
pCR revision of S3-230268 |
Philips International B.V. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230456 | Evaluation for solution#1 |
pCR revision of S3-230091 |
China Telecommunications | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230457 | New solution to KI#2 |
pCR revision of S3-230102 |
China Telecommunications | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230458 | Completion of solution #14 |
pCR revision of S3-230274 |
THALES | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230459 | New solution to KI#5 |
pCR revision of S3-230123 |
China Telecommunications | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230460 | Evaluation of solution #12 |
pCR revision of S3-230319 |
Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230461 | Evaluation of solution #13 |
pCR revision of S3-230320 |
Nokia, Nokia Shanghai Bell | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230462 | MEC - LS to SA2 on enforcement of AF specific identifier |
LS out LS To: SA2 revision of S3-230309 |
Apple | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] | ||
S3-230463 | Reply LS to S3-230018/S6-223586 on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network |
LS out LS is reply to S3-230018 LS To: SA6 revision of S3-230311 |
Apple | Rel-18 |
S3-109-ad hoc-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-230464 | Draft TR 33.883 | draft TR | Huawei, HiSilicon | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
approved | [WTS] [JSN] | |
S3-230465 | Draft TR 33.886 for eNS3 | draft TR | Huawei, HiSilicon | FS_eNS_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.12 |
approved | [WTS] [JSN] | |
S3-230466 | Addressing the editor's note in solution 3 |
pCR revision of S3-230151 |
Huawei, HiSilicon | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
approved | [WTS] [JSN] |
S3-230467 | update to solution 3 |
pCR revision of S3-230154 |
Huawei, HiSilicon | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230468 | update the evaluation in solution 1 |
pCR revision of S3-230155 |
Huawei, HiSilicon | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230469 | Addressing the editor's note in solution 1 |
pCR revision of S3-230157 |
Huawei, HiSilicon | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-230470 | Evaluation to solution 15 |
pCR revision of S3-230160 |
Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230471 | Evaluation to solution 16 |
pCR revision of S3-230161 |
Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230472 | A new solution to security about EAS discovery procedure via V-EASDF |
pCR revision of S3-230163 |
Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230473 | Key Issue Update on User Consent for NTN |
pCR revision of S3-230165 |
Huawei, HiSilicon | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-230474 | Conclusion for key issue #1 |
pCR revision of S3-230170 |
Huawei, HiSilicon, Xiaomi | 33.896 0.4.1 | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-230475 | Address EN for solution 1: onboarding |
pCR revision of S3-230172 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230476 | Address EN for solution 1: authorization decision |
pCR revision of S3-230174 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230477 | Evaluation Update on Solution 1 |
pCR revision of S3-230175 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230478 | Address EN for So#l26 |
pCR revision of S3-230185 |
Huawei, HiSilicon | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230479 | Evaluate to the solution #20 |
pCR revision of S3-230186 |
Huawei, HiSilicon | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230480 | A new solution on KI#4 |
pCR revision of S3-230193 |
Huawei, HiSilicon | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230481 | conclusion to KI#3 |
pCR revision of S3-230196 |
Huawei, HiSilicon | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230482 | Update solution for PINE authentication and authorization over 5G CP |
pCR revision of S3-230045 |
vivo | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-230483 | Draft TR 33.858 v0.4.0 | draft TR | Ericsson | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] | |
S3-230484 | A new solution for EEC authentication utilizing tokens |
pCR revision of S3-230224 |
Ericsson | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230485 | Update the KI#6 |
pCR revision of S3-230103 |
ZTE Corporation | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230486 | A solution for authorization before allowing access to resources |
pCR revision of S3-230230 |
Ericsson | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230487 | Add editors note to solution 5 |
pCR revision of S3-230106 |
ZTE Corporation | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230488 | Solution for authorization in FL |
pCR revision of S3-230343 |
Nokia, Nokia Shanghai Bell | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230489 | Add evaluation to solution #6 |
pCR revision of S3-230115 |
ZTE Corporation | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230490 | Add a new solution to KI#2 |
pCR revision of S3-230122 |
ZTE Corporation | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230491 | LS on clarification on user consent for AIML |
LS out LS To: SA2 revision of S3-230124 |
OPPO |
S3-109-ad hoc-e AI: 5.2 |
approved | [WTS] [JSN] | |||
S3-230492 | Resolving EN for Solution 22 |
pCR revision of S3-230126 |
OPPO | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230493 | KI10 solution 25 update on security profiles |
pCR revision of S3-230021 |
BSI (DE), Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230494 | Draft TR 33.898 v0.4.0 | draft TR | OPPO | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
approved | [WTS] [JSN] | |
S3-230495 | Resolving ENs in solution #9 of EDGE security |
pCR revision of S3-230204 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230496 | KI10 update on RHUB |
pCR revision of S3-230022 |
BSI (DE), Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230497 | Resolve EN’s in Solution #27 |
pCR revision of S3-230254 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230498 | Evaluation to Solution #27 |
pCR revision of S3-230255 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230499 | Evaluation to solution #4 |
pCR revision of S3-230256 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230500 | Update to solution #30 |
pCR revision of S3-230257 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230501 | New security solution on discovery integrated into PC5 link establishment when L3 UE-to-UE relay is in coverage |
pCR revision of S3-230258 |
Ericsson | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230502 | New solution with authorization tokens exchanged after PC5 security establishment |
pCR revision of S3-230259 |
Ericsson | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230503 | Update of evaluation to solution #2 |
pCR revision of S3-230260 |
Ericsson | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230504 | Update of evaluation to solution #3 |
pCR revision of S3-230261 |
Ericsson | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230505 | Resolving ENs in solution #10 of EDGE security |
pCR revision of S3-230206 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230506 | Adding conclusion on KI#1 |
pCR revision of S3-230342 |
Nokia, Nokia Shanghai Bell, China Mobile | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230507 | KI12 solution 19 update on hosted SEPP |
pCR revision of S3-230023 |
BSI (DE), Nokia, Nokia Shanghai Bell, Deutsche Telekom | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230508 | Resolving ENs in solution #11 of EDGE security |
pCR revision of S3-230208 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230509 | Address an EN in Sol #9 of EDGE security |
pCR revision of S3-230210 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230510 | Adding conclusion on KI#3 |
pCR revision of S3-230344 |
Nokia, Nokia Shanghai Bell, China Mobile, Intel, Ericsson | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230511 | Address an EN in Sol #10 of EDGE security |
pCR revision of S3-230211 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230512 | Add evaluation in Sol#11 of EDGE security |
pCR revision of S3-230214 |
OPPO | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230513 | New solution on authorization for 5GC assistance information exposure to external AF |
pCR revision of S3-230218 |
OPPO | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-230514 | New solution on authorization for 5GC assistance information exposure to internal AF |
pCR revision of S3-230220 |
OPPO | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-230515 | pCR to 33.884 updating solution #2 |
pCR revision of S3-230421 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230516 | New solution on privacy protection for 5GC assistance information exposure to AF |
pCR revision of S3-230223 |
OPPO | 33.898 0.3.0 | FS_AIML | Rel-18 |
S3-109-ad hoc-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-230517 | pCR to 33.884 adding new solution: PKCE flow |
pCR revision of S3-230422 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230518 | pCR to 33.884 adding new solution: token validation |
pCR revision of S3-230423 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230519 | draft TR 33.884 | draft TR | NTT DOCOMO INC. | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] | |
S3-230520 | Sol#3 Resolution of EN on Mutual Authentication |
pCR revision of S3-230077 |
Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230521 | Solution to KI#1 – NSWO in SNPN with CH AAA |
pCR revision of S3-230304 |
Qualcomm Incorporated | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230522 | Sol#3 Resolution of EN on Client Credential Grant |
pCR revision of S3-230078 |
Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230523 | Add Usecases to Solution 10 |
pCR revision of S3-230190 |
Intel | 33.858 0.3.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-230524 | FL GROUP AUTHORIZATION OF NWDAF(S) IN 5GC |
pCR revision of S3-230209 |
Intel | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230525 | EN related to Key Refresh and revocation |
pCR revision of S3-230237 |
Intel | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230526 | Key issue on authentication of UE behind RG |
pCR revision of S3-230417 |
CableLabs, Rogers Communications, Charter Communications | 33.887 0.4.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-230527 | Updates to the Key Issue #4 |
pCR revision of S3-230300 |
Qualcomm Incorporated | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230528 | Updates to the solution #25 |
pCR revision of S3-230298 |
Qualcomm Incorporated | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230529 | TR 33.882 v0.5.0 | draft TR | vivo Mobile Communication (S) | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-230530 | TR 33.896v050 | draft TR | Huawei;HiSilicon | FS_UC3S_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.22 |
approved | [WTS] [JSN] | |
S3-230531 | TR 33.882 Resolve ENs for sol #5 |
pCR revision of S3-230385 |
Xiaomi communications | 33.882 0.4.0 | FS_PIN_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-230532 | TR 33.741v050 | draft TR | Huawei;HiSilicon | FS_HN_Auth | Rel-18 |
S3-109-ad hoc-e AI: 5.7 |
approved | [WTS] [JSN] | |
S3-230533 | TR 33.737 Evaluation for sol #15 |
pCR revision of S3-230375 |
Xiaomi communications | 33.737 0.4.0 | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-230534 | KI#2, New Sol OAuth 2.0 based API invocation procedure |
pCR revision of S3-230389 |
Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230535 | KI#2, New Sol UE credential based API invocation procedure |
pCR revision of S3-230391 |
Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230536 | EN Resolution and Evaluation of Sol #19 |
pCR revision of S3-230327 |
Samsung | 33.740 0.4.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230537 | EN Resolutions and Evaluation of Sol #29 |
pCR revision of S3-230328 |
Samsung | 33.740 0.4.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230538 | Resolving EN in solution#3 (TR 33.739) |
pCR revision of S3-230329 |
Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230539 | Resolving EN and updating evaluation in solution#4 (TR 33.739) |
pCR revision of S3-230330 |
Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230540 | Solution on Public key signature based authentication |
pCR revision of S3-230331 |
Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230541 | Conclusion for KI#2.2 |
pCR revision of S3-230334 |
Samsung | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230542 | Updates to solution#1 in TR 33.883 |
pCR revision of S3-230335 |
Samsung | 33.883 0.4.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.23 |
approved | [WTS] [JSN] |
S3-230543 | Update of Key Issue #2 |
pCR revision of S3-230337 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230544 | New Solution on Resource owner Authorization in API Invocation using OAuth 2.0 Authorization Code Grant |
pCR revision of S3-230338 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230545 | New Solution on Resource owner Authorization in API Invocation |
pCR revision of S3-230339 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230546 | Evaluation and EN resolving for solution #14 |
pCR revision of S3-230263 |
China mobile | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230547 | draft TR 33.738 0.5.0 | draft TR | China Mobile Com. Corporation | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-230548 | Update to the evaluation of solution 23 |
pCR revision of S3-230221 |
China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230549 | Update to the evaluation of solution 24 |
pCR revision of S3-230234 |
China Telecom Corporation Ltd. | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230550 | pCR to TR33.740 Update Solution16 for removing ENs |
pCR revision of S3-230345 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230551 | pCR to TR33.740 Update Solution17 for removing ENs |
pCR revision of S3-230346 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230552 | pCR to TR33.740 Update Solution18 for removing ENs and add evaluation |
pCR revision of S3-230347 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230553 | pCR to TR33.740 Update Solution28 for removing ENs |
pCR revision of S3-230348 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230554 | pCR to TR33.740 Evaluation of Solution28 |
pCR revision of S3-230349 |
CATT | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230555 | Remove the Editor's Note of solution #5 in TR 33.893 |
pCR revision of S3-230405 |
Beijing Xiaomi Mobile Software | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230556 | Evaluation of solution #8 in TR 33.740 |
pCR revision of S3-230394 |
Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230557 | Evaluation of solution #9 in TR 33.740 |
pCR revision of S3-230395 |
Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230558 | Evaluation of solution #30 in TR 33.740 |
pCR revision of S3-230398 |
Beijing Xiaomi Mobile Software | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230559 | 33.893: Update to Solution #2 |
pCR revision of S3-230359 |
Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230560 | 33.893: Evaluation for Solution #4 |
pCR revision of S3-230361 |
Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230561 | 33.893: New Solution on Authorization of SL Positioning Client UE for Obtaining Ranging Result |
pCR revision of S3-230366 |
Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230562 | 33.893: Evaluation for Solution #6 |
pCR revision of S3-230362 |
Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230563 | 33.700-28: Add Potential Requirements for Key Issue #1 |
pCR revision of S3-230367 |
Xiaomi Technology | 33.700-28 0.2.0 | FS_5GSAT_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.25 |
approved | [WTS] [JSN] |
S3-230564 | draft TR 33.893 v0.5.0 | draft TR | Xiaomi Technology | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] | |
S3-230565 | draft TR 33.700-28 v0.3.0 | draft TR | Xiaomi Technology | FS_5GSAT_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.25 |
approved | [WTS] [JSN] | |
S3-230566 | pCR to TR33.893 New key issue on groupcast and broadcast security |
pCR revision of S3-230353 |
CATT, Xiaomi Technology | 33.893 0.4.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-109-ad hoc-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-230567 | Draft TR 33.740 | draft TR | CATT | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] | |
S3-230568 | Resolve_EN_solution#5 |
pCR revision of S3-230412 |
Ericsson | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-230569 | address EN for solution#4 |
pCR revision of S3-230095 |
Huawei, HiSilicon | 33.890 0.4.0 | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-230570 | Draft TR 33.390 v0.5.0 | draft TR | Huawei, HiSilicon | FS_NG_RTC_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.15 |
approved | [WTS] [JSN] | |
S3-230571 | Conclusion on KI#2.1 |
pCR revision of S3-230097 |
Huawei, HiSilicon, Thales | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230572 | Conclusion on KI#2.6 |
pCR revision of S3-230099 |
Huawei, HiSilicon | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230573 | Draft TR 33.739 v0.5.0 | draft TR | Huawei, HiSilicon | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-230574 | Evaluation of Solution#4 |
pCR revision of S3-230081 |
Lenovo | 33.738 0.4.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-109-ad hoc-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-230575 | Draft TR 33.877 v0.5.0 Study on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the NG-RAN | draft TR | Ericsson España S.A. | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.14 |
approved | [WTS] [JSN] | |
S3-230576 | Study on 5G roaming topics |
discussion revision of S3-230143 |
Nokia, Nokia Shanghai Bell, Deutsche Telekom | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
endorsed | [WTS] [JSN] | |
S3-230577 | KI1 sol13 EN resolution |
pCR revision of S3-230128 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230578 | KI1 analysis update |
pCR revision of S3-230129 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230579 | KI4 analysis and conclusion update |
pCR revision of S3-230131 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230580 | KI5 sol16 EN resolution |
pCR revision of S3-230133 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230581 | KI6 conclusion update |
pCR revision of S3-230134 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230582 | KI8 conclusion update |
pCR revision of S3-230136 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230583 | KI12 Hosted SEPP solution |
pCR revision of S3-230141 |
Nokia, Nokia Shanghai Bell | 33.875 1.5.0 | 5G_eSBA | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-230584 | Draft TR 33.737 v0.5.0 | draft TR | China Mobile | FS_AKMA_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.6 |
approved | [WTS] [JSN] | |
S3-230585 | Update of Key issue #12: Security in Hosted SEPP scenarios |
pCR revision of S3-230316 revised to S3-230588 |
Ericsson,Nokia, Nokia Shanghai Bell, Mavenir | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-230586 | EN removal for solution#27 |
pCR revision of S3-230253 |
Nokia, Nokia Shanghai Bell | 33.740 0.4.1 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-230587 | New Solution of authorization for EDGE-9 reference point |
pCR revision of S3-230037 |
InterDigital Communications | 33.739 0.4.0 | FS_EDGE_Ph2 | Rel-18 |
S3-109-ad hoc-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-230588 | Update of Key issue #12: Security in Hosted SEPP scenarios |
pCR revision of S3-230585 |
Ericsson,Nokia, Nokia Shanghai Bell, Mavenir | 33.875 1.5.0 | FS_eSBA_SEC | Rel-18 |
S3-109-ad hoc-e AI: 5.24 |
approved | [WTS] [JSN] |
1632 documents (1.0886969566345 seconds)