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-212400 | Agenda | agenda | SA WG3 Chair |
S3-104-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-212401 | Report from SA3#103e | report | MCC |
S3-104-e AI: 2 |
approved | [WTS] [JSN] | |||
S3-212402 | Process for SA3#104e meeting | other | SA WG3 Chair |
S3-104-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-212403 | Report from last SA | report | SA WG3 Chair |
S3-104-e AI: 2 |
noted | [WTS] [JSN] | |||
S3-212404 | Meeting notes from SA3 leadership | report | SA WG3 Chair |
S3-104-e AI: 2 |
noted | [WTS] [JSN] | |||
S3-212405 | Observations on TR 33.846 | discussion | JSRPC Kryptonite | FS_AUTH_ENH |
S3-104-e AI: 5.5 |
withdrawn | [WTS] [JSN] | ||
S3-212406 | New solution proposal | pCR | JSRPC Kryptonite | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
withdrawn | [WTS] [JSN] |
S3-212407 | Observations on TR 33.846 | discussion | JSRPC Kryptonite | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] | |
S3-212408 | New solution proposal |
pCR revised to S3-213216 |
JSRPC Kryptonite | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-212409 | LS on OAuth2 misalignments between SA3 and CT4 specifications |
LS in LS reply in S3-213193 |
CP-211326 |
S3-104-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-212410 | Misalignment on usage of OAuth within 3GPP 29.510 |
LS in LS reply in S3-213192, S3-213192 |
GSMA |
S3-104-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-212411 | LS on UE capabilities indication in UPU | LS in | S2-2101072 |
S3-104-e AI: 4.17 |
postponed | [WTS] [JSN] | |||
S3-212412 | Reply LS on UE capabilities indication in UPU | LS in | C1-212599 |
S3-104-e AI: 4.17 |
postponed | [WTS] [JSN] | |||
S3-212413 | LS reply on SDP attribute a=key-mgmt:mikey | LS in | C1-213548 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212414 | LS on support of PWS over SNPN | LS in | S1-210368 |
S3-104-e AI: 5.12 |
postponed | [WTS] [JSN] | |||
S3-212415 | Reply LS on support of PWS over SNPN | LS in | C1-213640 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-212416 | Reply LS on support of PWS over SNPN in R17 | LS in | R3-212863 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-212417 | Reply LS on support of PWS over NPN | LS in | SP-210584 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-212418 | Reply LS on end-to-end protection of HTTP message for Indirect communication | LS in | C4-213369 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] | |||
S3-212419 | Reply to LS on Resynchronisations | LS in | ETSI SAGE |
S3-104-e AI: 5.5 |
postponed | [WTS] [JSN] | |||
S3-212420 | Prevention of attacks on sliced core network |
LS in LS reply in S3-213209, S3-213209 |
GSMA |
S3-104-e AI: 4.25 |
replied to | [WTS] [JSN] | |||
S3-212421 | Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM | LS in | GSMA |
S3-104-e AI: 5.7 |
postponed | [WTS] [JSN] | |||
S3-212422 | Reply LS on Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM | LS in | S2-214895 |
S3-104-e AI: 5.7 |
noted | [WTS] [JSN] | |||
S3-212423 | Reply LS to GSMA-ACJA: 3GPP SA1 clarifications on problematic UAV | LS in | S2-214916 |
S3-104-e AI: 5.7 |
noted | [WTS] [JSN] | |||
S3-212424 | LS on Layer-3 UE-to-Network Relay authentication and authorization |
LS in LS reply in S3-212424, S3-213128 |
S2-2101623 |
S3-104-e AI: 5.9 |
replied to | [WTS] [JSN] | |||
S3-212425 | 256-bit algorithms based on SNOW 3G or SNOW V |
LS in LS reply in S3-213267 |
ETSI SAGE |
S3-104-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-212426 | LS re Penetration Testing of SCAS | LS in | GSMA |
S3-104-e AI: 4.3 |
postponed | [WTS] [JSN] | |||
S3-212427 | LS on security aspects for the method of collection of data from the UE |
LS in LS reply in S3-213271, S3-212679, S3-213271 |
S2-213263 |
S3-104-e AI: 5.16 |
replied to | [WTS] [JSN] | |||
S3-212428 | LS to SA3 on Small data transmissions |
LS in LS reply in S3-213034 |
R2-2104401 |
S3-104-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-212429 | LS for clarification on managing expired or multiple Protection Scheme and Home Network keys used for SUCI calculation. |
LS in LS reply in S3-213218, S3-212723, S3-213218 |
C6-210180 |
S3-104-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-212430 | LS on new work item on draft Recommendation ITU-T F.VG-VMA "Architecture of vehicular multimedia systems" [to various organizations] | LS in | ITU-T Focus Group on Vehicular Multimedia (FG-VM) |
S3-104-e AI: 4.26 |
noted | [WTS] [JSN] | |||
S3-212431 | LS on broadcast of NTN GW or gNB position |
LS in LS reply in S3-213150 |
R1-2106332 |
S3-104-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-212432 | New LS on UE location aspects in NTN |
LS in LS reply in S3-213027 |
R2-2106543 |
S3-104-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-212433 | Reply LS on UE location aspects in NTN | LS in | R3-212917 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212434 | LS to SA3 on SLIC | LS in | R2-2106516 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212435 | S on QoE report handling at QoE pause |
LS in LS reply in S3-213004 |
R2-2106775 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212436 | Reply LS to LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS in LS reply in S3-213258, S3-213258, S3-213272 |
R3-212812 |
S3-104-e AI: 4.13 |
replied to | [WTS] [JSN] | |||
S3-212437 | Reply LS on NAS-based busy indication |
LS in LS reply in S3-212848, S3-213258 |
R3-212877 |
S3-104-e AI: 5.19 |
noted | [WTS] [JSN] | |||
S3-212438 | Reply LS on NAS-based busy indication | LS in | S2-2105150 |
S3-104-e AI: 5.19 |
noted | [WTS] [JSN] | |||
S3-212439 | LS on 5G capabilities exposure for factories of the future | LS in | S2-2104794 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212440 | LS on 5G capabilities exposure for factories of the future | LS in | S6-211497 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212441 | Reply LS to SA4 on UE Data Collection | LS in | S2-2104864 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212442 | Reply LS to SA2 on UE Data Collection | LS in | S4-210961 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212443 | LS on progress of study items for security on management aspect | LS in | S5-213456 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212444 | LS on new SID on Application Enablement for Data Integrity Verification Service in IOT |
LS in LS reply in S3-213185 |
S6-211496 |
S3-104-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-212445 | LS on ITU-T SG17 new work item X.5Gsec-message: Security requirements for 5G message service | LS in | ITU-T SG17 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212446 | LS on ITU-T SG17 new work item X.sa-ec ‘Security architecture for edge cloud’ | LS in | ITU-T SG17 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212447 | LS on UAS terminology alignment | LS in | SP-210579 |
S3-104-e AI: 5.7 |
noted | [WTS] [JSN] | |||
S3-212448 | Reply LS on the conclusion of FS_MINT-CT | LS in | SP-210581 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212449 | Attack preventing NAS procedures to succeed | LS in | GSMA |
S3-104-e AI: 6 |
postponed | [WTS] [JSN] | |||
S3-212450 | OAuth2.0 misalignmnet |
CR revised to S3-213177 |
Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung | 33.501 16.7.0 CR#1145 catA | 5GS_Ph1-SEC | Rel-16 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212451 | OAuth2.0 misalignmnet |
CR revised to S3-213178 |
Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung | 33.501 15.13.0 CR#1146 catF | 5GS_Ph1-SEC | Rel-15 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212452 | Stealth Pirating Attack by RACH Rebroadcast Overwriting (SPARROW) | LS in | GSMA |
S3-104-e AI: 6 |
postponed | [WTS] [JSN] | |||
S3-212453 | Evaluation of Solution #22: Representation of identities during broadcast | pCR | KPN N.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212454 | Correction of message name in SMF | CR | Keysight Technologies UK Ltd | 33.515 16.3.0 CR#7 catD | SCAS_5G | Rel-16 |
S3-104-e AI: 4.21 |
withdrawn | [WTS] [JSN] |
S3-212455 | AMF – NAS NULL integrity protection clarifications (Rel-16) | CR | Keysight Technologies UK Ltd | 33.512 16.5.0 CR#11 catF | SCAS_5G | Rel-16 |
S3-104-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-212456 | AMF – NAS NULL integrity protection clarifications (Rel-17) | CR | Keysight Technologies UK Ltd | 33.512 17.0.0 CR#12 catA | SCAS_5G | Rel-17 |
S3-104-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-212457 | Conclusion on Key Issue #11: UE identity protection during ProSe discover | pCR | KPN N.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212458 | Living document for BEST_5G: draftCR to TS 33.163 |
draftCR revised to S3-213207 |
KPN N.V. | BEST_5G | Rel-17 |
S3-104-e AI: 4.11 |
revised | [WTS] [JSN] | |
S3-212459 | Correction of message name in SMF |
CR revised to S3-213186 |
Keysight Technologies UK Ltd | 33.515 16.3.0 CR#8 catF | SCAS_5G | Rel-16 |
S3-104-e AI: 4.21 |
revised | [WTS] [JSN] |
S3-212460 | Process and agenda for SA3#104-e | agenda | SA WG3 Chair |
S3-104-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-212461 | TCG progress - report from TCG rapporteur | report | InterDigital, Inc. |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212462 | New WID for Study of privacy of Over the Air identities | SID new | InterDigital, Inc., Apple, AT&T, CableLabs, Futurewei, Verizon Wireless | Rel-18 |
S3-104-e AI: 7 |
noted | [WTS] [JSN] | ||
S3-212463 | Reply LS to GSMA on prevention of attacks on sliced core network |
LS out LS is reply to GSMA source LS: S3-212420 LS To: GSMA revision of S3-211527 revised to S3-213209 |
CableLabs | Rel-16 |
S3-104-e AI: 4.25 |
revised | [WTS] [JSN] | ||
S3-212464 | New solution: Keying procedures for Group Member and Relay discovery: public safety case |
pCR revised to S3-213175 |
MITRE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212465 | Update to KI #17 |
pCR revised to S3-213176 |
MITRE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212466 | New solution: Hardware Mediated Execution Enclave (HMEE) |
pCR revised to S3-213217 |
MITRE Corporation | 33.848 0.8.0 | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-212467 | [33.180] R17 Group subscription |
CR revised to S3-213179 |
Motorola Solutions Danmark A/S | 33.18 17.3.0 CR#173 catF | MCXSec2 | Rel-17 |
S3-104-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-212468 | [33.180] R17 Preconfigured group clarification | CR | Motorola Solutions Danmark A/S | 33.18 17.3.0 CR#174 catB | MCXSec2 | Rel-17 |
S3-104-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-212469 | Conclusion on Key Issue #12: Security of one-to-one communication over PC5 | pCR | KPN N.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212470 | Clean-up for KI#1 | pCR | LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212471 | Updates on sol#10 | pCR | LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212472 | Evaluation for sol#13 |
pCR revised to S3-213087 |
LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212473 | Editorial corrections for sol#10 | pCR | LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212474 | New solution for UE onboarding | pCR | LG Electronics Inc. | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212475 | New WID on Authentication enhancements in 5GS | WID new | Ericsson | Rel-17 |
S3-104-e AI: 4.27 |
noted | [WTS] [JSN] | ||
S3-212476 | Authentication enhancements: Discussion about the WID | discussion | Ericsson | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] | |
S3-212477 | Reply LS to SA6 on new SID on Application Enablement for Data Integrity Verification Service in IoT |
LS out LS To: SA6 |
China Unicom |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212478 | TR 33.847 Update for solution #10 |
pCR revised to S3-213059 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212479 | TR 33.847 Update for solution #24 |
pCR revised to S3-213060 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212480 | New Solution Using Attestation for Key Issue #13 | pCR | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | 33.848 0.8.0 | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-212481 | TR 33.847 Update for solution #25 |
pCR revised to S3-213062 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212482 | New Key Issue on Network Slice Quota DoS | pCR | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD, Verizon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-212483 | New Solution to Network Slice Quota DoS | pCR | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD, Verizon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-212484 | Way forward for L3 U2N Relay Authorization and security conclusions | discussion | InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] | ||
S3-212485 | Conclusions for U2N relay Key Issues |
pCR revised to S3-213063 |
InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212486 | Conclusion for Key Issue #3 | pCR | InterDigital, Europe, Ltd. | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-212487 | Conclusion for Key Issue #5 | pCR | InterDigital, Europe, Ltd. | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-212488 | Conclusion for Key Issue #6 | pCR | InterDigital, Europe, Ltd. | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-212489 | New WID on IETF OSCORE Ua* protocol profile for AKMA | WID new | Ericsson | Rel-17 |
S3-104-e AI: 4.27 |
noted | [WTS] [JSN] | ||
S3-212490 | IETF OSCORE as AKMA Ua* protocol | CR | Ericsson | 33.535 17.2.1 CR#84 catB | DUMMY | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212491 | Extending the Ua security protocol namespace to include the AKMA OSCORE Ua* protocol | CR | Ericsson | 33.22 17.1.0 CR#213 catB | DUMMY | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212492 | Updates to solution #2 | pCR | Ericsson | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212493 | Updates to solution #9 | pCR | Ericsson | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212494 | Updates to terminology in the architecture assumptions |
pCR revised to S3-213073 |
Ericsson | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-212495 | Rel16 Clarification about multiple horizontal key derivations upon AMF re-allocation via direct NAS reroute | CR | Ericsson | 33.501 16.7.1 CR#1147 catF | TEI16 | Rel-16 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212496 | Rel17 Clarification about multiple horizontal key derivations upon AMF re-allocation via direct NAS reroute | CR | Ericsson | 33.501 17.2.1 CR#1148 catA | TEI16 | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212497 | New WID on the security of AMF re-allocation | WID new | Ericsson | Rel-17 |
S3-104-e AI: 4.27 |
noted | [WTS] [JSN] | ||
S3-212498 | AMF re-allocation: Discussion about the WID | discussion | Ericsson | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-212499 | Conclusion for the study | pCR | Ericsson | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212500 | Living document for GBA_5G: draftCR to TS 33.220: SBA support for Zh and Zn interfaces |
draftCR revised to S3-213245 |
Ericsson | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-212501 | Living document for GBA_5G: draftCR to TS 33.223: SBA support for Zpn |
draftCR revised to S3-213246 |
Ericsson | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-212502 | pCR to living document for TS 33.220: Support of GBA in UDM | other | Ericsson | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
merged | [WTS] [JSN] | |
S3-212503 | pCR to living document for TS 33.223: Support for GBA in UDM | other | Ericsson | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-212504 | DRAFT LS on SBA for GBA |
LS out LS To: SA2 revised to S3-213215 |
Ericsson | Rel-17 |
S3-104-e AI: 4.1 |
revised | [WTS] [JSN] | ||
S3-212505 | pCR to living document for TS 33.220: Correction of references | other | Ericsson | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-212506 | Rel16 Align KAUSF handling for 5G AKA and EAP-AKA' |
CR revised to S3-213261 |
Ericsson | 33.501 16.7.1 CR#1149 catF | TEI16 | Rel-16 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212507 | Rel17 Align KAUSF handling for 5G AKA and EAP-AKA' for Release 17 |
CR revised to S3-213262 |
Ericsson | 33.501 17.2.1 CR#1150 catA | TEI16 | Rel-17 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212508 | Addressing security threat against KAUSF derived from MSK | pCR | CableLabs | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212509 | Update to solution#4.7 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212510 | Conclusion to Key Issue #4.1 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-212511 | Conclusion on Key issue #3.2 SUPI guessing attacks |
pCR revised to S3-213173 |
Nokia, Nokia Shanghai Bell, Thales, NTT DOCOMO, NEC | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-212512 | Editor note removal and update for solution#10 |
pCR revised to S3-213038 |
Nokia, Nokia Shanghai Bell | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212513 | LS on proposed NSWO architecture |
LS out LS To: SA2 revised to S3-213174 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 5.22 |
revised | [WTS] [JSN] | ||
S3-212514 | Non-Seamless WLAN offload Authentication in 5GS |
pCR revised to S3-213037 |
Nokia, Nokia Shanghai Bell, AT&T | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-212515 | New WID on Non-Seamless WLAN offload Authentication in 5GS | WID new | Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 4.27 |
noted | [WTS] [JSN] | ||
S3-212516 | Updates on sol#13 |
pCR revised to S3-213088 |
LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212517 | Concept of User Consent | pCR | China Unicom | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
withdrawn | [WTS] [JSN] |
S3-212518 | Update for Conclusion on Key Issue #4 | pCR | China Telecommunications, Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
withdrawn | [WTS] [JSN] |
S3-212519 | Authorization of IPX by PLMN in indirect roaming | pCR | CableLabs | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212520 | pCR: updating annex B in TR 33.809 | pCR | CableLabs | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-212521 | Further conclusions for KI #1 |
pCR revision of S3-211521 revised to S3-213066 |
CableLabs,Ericsson, Charter Communications, Intel | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-212522 | Update for Conclusion on Key Issue #4 |
pCR revised to S3-213083 |
China Telecommunications, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212523 | Short-lived public key-based solution for KI#2 |
pCR revised to S3-213210 |
CableLabs,Deutsche Telekom AG, InterDigital, Johns Hopkins University APL, US National Security Agency | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-212524 | Discussion on security of Small data transmissions | discussion | ZTE Corporation | Rel-17 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-212525 | Reply LS on Small data transmissions |
LS out LS is reply to R2-2104401/S3-212428 source LS: R2-2104401/S3-212428 LS To: RAN2 |
ZTE Corporation | Rel-17 |
S3-104-e AI: 3 |
merged | [WTS] [JSN] | ||
S3-212526 | Living document for SCAS_5G_IPUPS draftCR to TR 33.926 | draftCR | ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-104-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-212527 | Living document for SCAS_5G_IPUPS draftCR to TS 33.513 | draftCR | ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-104-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-212528 | Add Routing indicator in Authentication response | CR | ZTE Corporation | 33.501 17.2.1 CR#1151 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-212529 | Resolution of EN on other parameter in clause 6.3 | CR | ZTE Corporation | 33.535 17.2.1 CR#85 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212530 | Resolve the Kaf update issue | CR | ZTE Corporation | 33.535 17.2.1 CR#86 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212531 | UDM notifies AAnF AKMA context removal and performs AAnF selection | CR | ZTE Corporation | 33.535 17.2.1 CR#87 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212532 | Update clause 6.1 about RID | CR | ZTE Corporation | 33.535 17.2.1 CR#88 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-212533 | Update clause 6.1 refer to Kausf stored in AUSF | CR | ZTE Corporation | 33.535 17.2.1 CR#89 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212534 | Discussion on refresh of KAF and no Kakma in AAn | discussion | ZTE Corporation | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
noted | [WTS] [JSN] | |
S3-212535 | Add step 4 in annex B.1.2.2 |
CR revised to S3-213268 |
ZTE Corporation | 33.535 17.2.1 CR#90 catF | AKMA_TLS | Rel-17 |
S3-104-e AI: 4.19 |
revised | [WTS] [JSN] |
S3-212536 | Add TLS1.3 to annex B.1.3 | CR | ZTE Corporation | 33.535 17.2.1 CR#91 catB | AKMA_TLS | Rel-17 |
S3-104-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-212537 | Delete the GBA_Digest in annex B.1.2.2 | CR | ZTE Corporation | 33.535 17.2.1 CR#92 catF | AKMA_TLS | Rel-17 |
S3-104-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-212538 | Correct the description of KAUSF handling upon successful primary authentication-R16 | CR | ZTE Corporation | 33.501 16.7.1 CR#1152 catF | TEI16 | Rel-16 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212539 | Correct the description of KAUSF handling upon successful primary authentication-R17 | CR | ZTE Corporation | 33.501 17.2.1 CR#1153 catA | TEI16 | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212540 | Add evaluation for solution 3.3 | pCR | ZTE Corporation | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-212541 | Conclusion on key issue 3.2 | pCR | ZTE Corporation | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-212542 | Conclusion on key issue 4.1 | pCR | ZTE Corporation | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-212543 | Conclusion on key issue 1 | pCR | ZTE Corporation | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-212544 | Conclusion on key issue 2 | pCR | ZTE Corporation | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-212545 | Conclusion on key issue 7 | pCR | ZTE Corporation | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-212546 | Conclusion of Key Issue #1 | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212547 | Update to Solution #5 |
pCR revised to S3-213081 |
ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212548 | Conclusion for UE to UE relay | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212549 | Solution for key issue #17 | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212550 | Update the key issue#2 | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212551 | Update the solution#36 | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212552 | Add the evaluation of the solution #6 |
pCR revised to S3-213084 |
ZTE Corporation | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212553 | Conclusion for the key issue 1 | pCR | ZTE Corporation | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-212554 | Conclusion for the key issue 2 | pCR | ZTE Corporation | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
merged | [WTS] [JSN] |
S3-212555 | Update the solution #12 | pCR | ZTE Corporation | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212556 | Update the solution #6 |
pCR revised to S3-213085 |
ZTE Corporation | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212557 | New solution on control plane based provisioning PS to AUSF |
pCR revised to S3-213082 |
ZTE Corporation | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-212558 | New solution on control plane based provisioning PS to UDM | pCR | ZTE Corporation | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212559 | Resolving ENs in Key Issue #2 | pCR | ZTE Corporation | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212560 | Conclusion for the key issue 1 | pCR | ZTE Corporation | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212561 | Resolve the EN about the GUTI collision in solution #11 | pCR | ZTE Corporation | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212562 | Update the solution #11 |
pCR revised to S3-213086 |
ZTE Corporation | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-212563 | Concept of User Consent | pCR | China Unicom, Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-212564 | Annex X on EAP_TTLS for SNPN | draftCR | CableLabs, Ericsson, Charter Communications, Intel | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
noted | [WTS] [JSN] | |
S3-212565 | Storage of Kausf | CR | NEC Corporation | 33.501 17.2.1 CR#1154 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212566 | modification to the solution 6.2.10 | pCR | NEC Corporation | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212567 | conclusion to key issue 2.2 | pCR | NEC Corporation | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-212568 | Update to solution #25 | pCR | Huawei, HiSilicon | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-212569 | Evaluation of solution #4 | pCR | Huawei, HiSilicon | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-212570 | Conclusion for KI#3 | pCR | Huawei, HiSilicon | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-212571 | Serving network ID in NSSAA | CR | Huawei, HiSilicon | 33.501 16.7.1 CR#1155 catF | eNS | Rel-16 |
S3-104-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-212572 | Validity peirod of NSSAA result | CR | Huawei, HiSilicon | 33.501 16.7.1 CR#1156 catF | eNS | Rel-16 |
S3-104-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-212573 | Clarification on optional EAP ID Request in NSSAA Procedure | CR | Huawei, HiSilicon | 33.501 16.7.1 CR#1157 catF | eNS | Rel-16 |
S3-104-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-212574 | Update to KI#1 (NSSAI analysis) |
pCR revised to S3-213133 |
Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
revised | [WTS] [JSN] |
S3-212575 | New KI on DoS to NSAC procedure |
pCR revised to S3-213134 |
Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
revised | [WTS] [JSN] |
S3-212576 | New KI on AF authentication and authorization |
pCR revised to S3-213140 |
Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
revised | [WTS] [JSN] |
S3-212577 | New KI on simultaneous use of network slice | pCR | Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-212578 | Draft LS to GSMA on interfacing with USS/UTM |
LS out LS To: GSMA |
Huawei, HiSilicon | Rel-17 |
S3-104-e AI: 5.7 |
noted | [WTS] [JSN] | ||
S3-212579 | Conclusion to KI#3 (TPAE AA) |
pCR revised to S3-213130 |
Huawei, HiSilicon | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-212580 | Conclusion to KI#5 (privacy of UAS identities) |
pCR revised to S3-213132 |
Huawei, HiSilicon | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-212581 | Conclusion to KI#6 (UAV to UTM) | pCR | Huawei, HiSilicon | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-212582 | Overview on UAV authentication and authorization (UAA) |
pCR revised to S3-213219 |
Huawei, HiSilicon | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-212583 | UAA procedure at registration (5G) | pCR | Huawei, HiSilicon | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-212584 | UAA procedure at PDU session establsihment (5G) | pCR | Huawei, HiSilicon | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-212585 | UAA re-authentication procedure (5G) | pCR | Huawei, HiSilicon | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-212586 | Revocation of UAA | pCR | Huawei, HiSilicon | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-212587 | Pairing authorizaiton of UAS and UAV | pCR | Huawei, HiSilicon | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-212588 | Solution on AF authorization |
pCR revised to S3-213144 |
Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
revised | [WTS] [JSN] |
S3-212589 | Skeloton for clause UAA | pCR | Huawei, HiSilicon | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-212590 | Solution to prevent information leakage between mutual exclusive slices | pCR | Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-212591 | Solution of NSAC based on slice usage | pCR | Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-212592 | Solution to decouple NSAC and NSSAA status | pCR | Huawei, HiSilicon | 33.874 0.0.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-212593 | Solution on restriction in EAC inactive modes | pCR | Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-212594 | A new solution to address KI#1 | pCR | Huawei, HiSilicon | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
merged | [WTS] [JSN] |
S3-212595 | A new testcase to NSSAAF SCAS |
pCR revised to S3-213249 |
Huawei, HiSilicon | 33.326 0.2.0 | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-212596 | An editoral change to TS 33.216 | CR | Huawei, HiSilicon | 33.216 16.6.0 CR#23 catF | SCAS_5G | Rel-17 |
S3-104-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-212597 | Clarification on AS key generation after runing NAS SMC |
CR revised to S3-213250 |
Huawei, HiSilicon | 33.501 17.2.1 CR#1158 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212598 | Clarification on Kausf storage in multi-NAS connection |
CR revised to S3-213191 |
Huawei, HiSilicon | 33.501 17.2.1 CR#1159 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212599 | Clarification on Kausf storage in multi-NAS connection |
CR revised to S3-213194 |
Huawei, HiSilicon | 33.501 16.7.1 CR#1160 catF | TEI16 | Rel-16 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212600 | Clarification on AAnF selection |
CR revised to S3-213252 |
Huawei, HiSilicon | 33.535 17.2.1 CR#93 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-212601 | NSSAAF SCAS cleanup | pCR | Huawei, HiSilicon | 33.326 0.2.0 | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
approved | [WTS] [JSN] |
S3-212602 | CR to 33.926 threat analysis on select AAA-P and AAA-S |
CR revised to S3-213251 |
Huawei, HiSilicon | 33.926 17.1.0 CR#46 catF | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-212603 | conclusion to KI#2 |
pCR revised to S3-213105 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212604 | conclusion to KI#5 to KI#8 |
pCR revised to S3-213106 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212605 | conclusion to KI#11 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212606 | add reference to TS 33.512 | CR | Huawei, HiSilicon | 33.512 17.0.0 CR#13 catF | eSCAS_5G | Rel-17 |
S3-104-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-212607 | Add a new procedure to enable the AF to refresh the Kaf | CR | Huawei, HiSilicon | 33.501 17.2.1 CR#1161 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
withdrawn | [WTS] [JSN] |
S3-212608 | Resolve EN in Sol#27 |
pCR revised to S3-213107 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212609 | Resolve EN in Sol#28 |
pCR revised to S3-213108 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212610 | New solution for one-to-one communication | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212611 | Add conclusion to Key Issue #1 |
pCR revised to S3-213109 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212612 | Add conclusion to Key Issue #3 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212613 | Add conclusion to key Issue #9 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212614 | Add conclusion to Key Issue #12 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212615 | Add conclusion to key Issue #16 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212616 | Propose evaluation to sol #1 | pCR | Huawei, HiSilicon | 33.862 0.6.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212617 | Propose evaluation to sol #5 | pCR | Huawei, HiSilicon | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
noted | [WTS] [JSN] |
S3-212618 | UAV location information verification |
pCR revised to S3-213220 |
Huawei, HiSilicon | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-212619 | New solution to avoid policy mismatch |
pCR revised to S3-213110 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212620 | Discussion on the bidding down attack during one-to-one communication establishment | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212621 | Security solution for temporary group call | CR | Huawei,HiSilicon | 33.18 17.3.0 CR#175 catB | MCXSec2 | Rel-17 |
S3-104-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-212622 | Correction to Authorization for indirect communication with delegated discovery procedure in rel16 | CR | Huawei,HiSilicon | 33.501 16.7.1 CR#1162 catF | 5G_eSBA | Rel-16 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212623 | Correction to Authorization for indirect communication with delegated discovery procedure in rel17 | CR | Huawei,HiSilicon | 33.501 17.2.1 CR#1163 catA | 5G_eSBA | Rel-17 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212624 | Correction to Deriving AKMA Application Key for a specific AF | CR | Huawei,HiSilicon | 33.535 17.2.1 CR#94 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212625 | New solution on UE-to-network relay Key management based on primary authentication |
pCR revised to S3-213111 |
Huawei,HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212626 | Resolving the EN about the multiple EECs issues in solution 8 |
pCR revised to S3-213112 |
Huawei,HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212627 | Add the missing references | CR | Huawei,HiSilicon | 33.501 17.2.1 CR#1164 catA | TEI15 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-212628 | Add the missing references for Rel 16 | CR | Huawei,HiSilicon | 33.501 16.7.1 CR#1165 catA | TEI15 | Rel-16 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-212629 | Add the missing references for Rel 15 | CR | Huawei,HiSilicon | 33.501 15.13.0 CR#1166 catF | TEI15 | Rel-15 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-212630 | add evaluation for solution#3 |
pCR revised to S3-213113 |
Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212631 | update evaluation for solution#13 | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212632 | resovle EN for solution#3 | pCR | Huawei,HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212633 | Add a new procedure to enable the AF to refresh the Kaf | CR | Huawei, HiSilicon | 33.535 17.2.1 CR#95 catB | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212634 | Discussion on UE capabilities indication in UPU | discussion | Huawei, HiSilicon | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 4.17 |
noted | [WTS] [JSN] | |
S3-212635 | reply LS on UE capabilities indication in UPU |
LS out LS is reply to S2-2101072/C1-212599 LS To: SA2, CT1 |
Huawei, HiSilicon | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 4.17 |
noted | [WTS] [JSN] | |
S3-212636 | Editorial change in SIP digest | draftCR | Huawei, HiSilicon | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-212637 | roaming-related security mechanisms |
draftCR revised to S3-213235 |
Huawei, HiSilicon | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
revised | [WTS] [JSN] | |
S3-212638 | EN romoval for solution#23 |
pCR revised to S3-213116 |
Huawei, HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212639 | Solution on Authorization of Data Consumers for data access via DCCF | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212640 | Discussion on NF Domain granularity authorization | pCR | Huawei, HiSilicon | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212641 | New KI on NF Domain granularity authorization | pCR | Huawei, HiSilicon | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212642 | UP Security policy requirement on the IMS data network | CR | Huawei, HiSilicon | 33.501 17.2.1 CR#1167 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212643 | EC: Conclusion for Key issue #1 | pCR | Huawei, HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212644 | EC: Conclusion for Key issue #2 | pCR | Huawei, HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212645 | EC : Conclusion for Key issue #7 |
pCR revised to S3-213117 |
Huawei, HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212646 | EC: Conclusion for Key issue #10 | pCR | Huawei, HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212647 | EC: Skeleton for the new TS 33.558 | draft TS | Huawei, HiSilicon | eEDGE_5GC | Rel-17 |
S3-104-e AI: 4.18 |
approved | [WTS] [JSN] | |
S3-212648 | TS 33.558: Security requirements |
pCR revised to S3-213225 |
Huawei, HiSilicon | 33.558 0.0.0 | eEDGE_5GC | Rel-17 |
S3-104-e AI: 4.18 |
revised | [WTS] [JSN] |
S3-212649 | TS 33.558: Security for the EDGE interfaces |
pCR revised to S3-213226 |
Huawei, HiSilicon | 33.558 0.0.0 | eEDGE_5GC | Rel-17 |
S3-104-e AI: 4.18 |
revised | [WTS] [JSN] |
S3-212650 | TS 33.558: adding the scope | pCR | Huawei, HiSilicon | 33.558 0.0.0 | eEDGE_5GC | Rel-17 |
S3-104-e AI: 4.18 |
approved | [WTS] [JSN] |
S3-212651 | New Key issue on authorization mechanism negotiation |
pCR revised to S3-213120 |
Huawei, HiSilicon; China Mobile | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212652 | New solution for the authorization mechanism negotiation |
pCR revised to S3-213121 |
Huawei, HiSilicon; China Mobile | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212653 | Requirement of subscribe-notification key issue |
pCR revised to S3-213122 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212654 | Clarification on SoR transparent container | CR | Huawei, HiSilicon | 33.501 17.2.1 CR#1168 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-212655 | MBS:Discussion paper on Authentication and authorization for multicast service | discussion | Huawei, HiSilicon | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
endorsed | [WTS] [JSN] | |
S3-212656 | Conclusion on authentication and authorization for multicast service |
pCR revised to S3-213123 |
Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212657 | Conclusion on key issue #1.2 |
pCR revised to S3-213124 |
Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212658 | Update to solution #14 to ML restrictive transfer of ML models | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212659 | Conclusion on key issue #3.3 on restrictive transfer of ML models | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212660 | Udpates to key issue #3.1 on attacker model | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212661 | Conclusion on key issue #3.2 on protection of UE data in transit |
pCR revised to S3-213125 |
Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212662 | Updates to solutoin #3 | pCR | Huawei, HiSilicon | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212663 | Discussion on registraiton request messgae being rerouted | discussion | Huawei, HiSilicon | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-212664 | Updates to clause #4.3 | pCR | Huawei, HiSilicon | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212665 | Discussion on exposing NAS security context to RAN | discussion | Huawei, HiSilicon | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-212666 | Adding for NSSAAF network product class description and assets and critical assets |
draftCR revised to S3-213228 |
Huawei, HiSilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
revised | [WTS] [JSN] | |
S3-212667 | New threat related to unauthorized slice-specific authorization revocatoin |
draftCR revised to S3-213229 |
Huawei, HiSilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
revised | [WTS] [JSN] | |
S3-212668 | Comparison of services for providing GBA 5G AV | discussion | Huawei, HiSilicon | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-212669 | New service on 5G GBA AV |
draftCR revised to S3-213230 |
Huawei, HiSilicon | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-212670 | Claifications on SoR enablement | CR | Huawei, HiSilicon | 33.501 17.2.1 CR#1169 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212671 | New key issue on service authorization in request redirection | pCR | Huawei, HiSilicon | 33.857 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212672 | New solution on AF authorization | pCR | Huawei, HiSilicon | 33.857 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
withdrawn | [WTS] [JSN] |
S3-212673 | New key issue on AF authorization | pCR | Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-212674 | New solution on AF authorization | pCR | Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-212675 | Conclusion to key issue on unauthorized MBS session operation | pCR | Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-212676 | Discussion paper on 256-bit algorithms based on ZUC-256 | discussion | CAICT, China Mobile, China Unicom, China Telecom, CBN |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212677 | Updates to solution #17 capability negotiation |
pCR revised to S3-213259 |
Intel Corporation (UK) Ltd | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-212678 | Solution 4: Clarify and update EN related Secondary authentication | pCR | Intel Corporation (UK) Ltd | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212679 | Reply-LS on security aspects for the method of collection of data from the UE |
LS out LS is reply to S3-212427 LS To: SA WG2 revised to S3-213271 |
Guangdong OPPO Mobile Telecom. | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] | ||
S3-212680 | Solution 4: Clarify and update EN Application Client | pCR | Intel Corporation (UK) Ltd | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212681 | LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT |
LS out LS is reply to 3GPP TSG SA WG6 source LS: S6-211496 LS To: 3GPP TSG SA WG6 revised to S3-213185 |
Nokia, Nokia Shanghai Bell | Rel-18 |
S3-104-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-212682 | Cleanup MUSIM TR | draftCR | Intel Corporation (UK) Ltd | FS_MUSIM_SEC | Rel-17 |
S3-104-e AI: 5.19 |
approved | [WTS] [JSN] | |
S3-212683 | Editorial Clarifications for Trusted non-3GPP Access using TNGF |
CR revised to S3-213237 |
Intel Corporation (UK) Ltd | 33.501 17.2.1 CR#1170 catF | 5GS_Ph1-SEC, TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212684 | pCR to Living doc on addition of 5G to BEST - addition of EMSDP updates |
other revised to S3-213263 |
VODAFONE Group Plc | BEST_5G |
S3-104-e AI: 4.11 |
revised | [WTS] [JSN] | ||
S3-212685 | Reply LS on Small data transmission |
LS out LS is reply to S3-212428 LS To: RAN2 |
Intel Corporation (UK) Ltd |
S3-104-e AI: 3 |
merged | [WTS] [JSN] | |||
S3-212686 | Response LS on 256-bit algorithms based on SNOW 3G or SNOW V |
LS out LS is reply to S3-212425 LS To: ETSI SAGE revised to S3-213267 |
VODAFONE Group Plc | FS_256_Algo | Rel-18 |
S3-104-e AI: 3 |
revised | [WTS] [JSN] | |
S3-212687 | Key issue on security aspects of Paging Cause | draftCR | Intel Corporation (UK) Ltd | FS_MUSIM_SEC | Rel-17 |
S3-104-e AI: 5.19 |
approved | [WTS] [JSN] | |
S3-212688 | Updates to solution 14: Removal of Editor’s notes: Security Issues |
pCR revised to S3-213070 |
Intel Corporation (UK) Ltd | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-212689 | Updates to solution 14: Removal of Editor’s notes: Three Authentication | pCR | Intel Corporation (UK) Ltd | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212690 | Updates to solution 14: Removal of Editor’s notes: One-Way | pCR | Intel Corporation (UK) Ltd | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212691 | Proposal for conclusion for Key Issue 4 | pCR | Intel Corporation (UK) Ltd | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212692 | Clarification on RRCConnectionRe-establishment Procedure in Control Plane CIoT EPS Optimization | CR | Huawei, HiSilicon | 33.401 14.6.0 CR#699 catF | TEI14 | Rel-14 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212693 | Clarification on RRCConnectionRe-establishment Procedure in Control Plane CIoT 5GS Optimization | CR | Huawei, HiSilicon | 33.501 16.7.1 CR#1171 catF | 5G_CIoT | Rel-16 |
S3-104-e AI: 4.23 |
not pursued | [WTS] [JSN] |
S3-212694 | UP Security Activation Mechanism in LTE |
draftCR revised to S3-213221 |
Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
revised | [WTS] [JSN] | |
S3-212695 | UP Security Policy Handling for Option 3 | draftCR | Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
merged | [WTS] [JSN] | |
S3-212696 | Clarification on UP IP indication based on RAN3 LS | draftCR | Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
noted | [WTS] [JSN] | |
S3-212697 | Clarification on Finding the right NF instance are serving the UE | CR | Huawei, HiSilicon | 33.521 17.0.0 CR#1 catF | SCAS_5G_NWDAF | Rel-17 |
S3-104-e AI: 4.5 |
not pursued | [WTS] [JSN] |
S3-212698 | Reply LS for Small Data Transfer |
LS out LS To: RAN2 |
Huawei, HiSilicon | Rel-17 |
S3-104-e AI: 3 |
merged | [WTS] [JSN] | ||
S3-212699 | Evaluation on indication of key derivation | pCR | Huawei, HiSilicon | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212700 | Conclusion on KI#1 for key derivation | pCR | Huawei, HiSilicon | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212701 | New solution for User Consent for 3GPP service exposure |
pCR revised to S3-213095 |
Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212702 | General Conclusion on UDM service for User Consent Check |
pCR revised to S3-213096 |
Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212703 | General Conclusion on Generic Requirement for the Procedures for User Consent Check |
pCR revised to S3-213097 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212704 | General Conclusion on UDM service for User Consent Revocation |
pCR revised to S3-213098 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212705 | New WID for UC3S |
WID new revised to S3-213223 |
Huawei, HiSilicon, China Mobile, China Unicom, China Telecom, Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 4.27 |
revised | [WTS] [JSN] | ||
S3-212706 | Draft skeleton for UC3S WID | draftCR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | FS_UC3S | Rel-17 |
S3-104-e AI: 4.27 |
approved | [WTS] [JSN] | |
S3-212707 | General Conclusion on Generic Requirement for the Procedure for User Consent Revocation |
pCR revised to S3-213099 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212708 | Solution for user consent revocation |
pCR revised to S3-213100 |
Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212709 | Solution Update and Evaluation for Solution 3 |
pCR revised to S3-213101 |
Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212710 | Conclusion on KI#2 for User Plane Provisioning | pCR | Huawei, HiSilicon | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212711 | Skeleton for UC3S Conclusion | pCR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-212712 | Conclusion for Key Issue #1 | pCR | Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-212713 | Conclusion for Key Issue #2 |
pCR revised to S3-213102 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212714 | Conclusion for Key Issue #3 |
pCR revised to S3-213103 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212715 | skeleton for the new annex | draftCR | Huawei, HiSilicon | 5MBS | Rel-17 |
S3-104-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-212716 | Security protection between AF and 5GC | draftCR | Huawei, HiSilicon | 5MBS | Rel-17 |
S3-104-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-212717 | Discussion paper on MBS traffic protection | discussion | Huawei, HiSilicon | Rel-17 |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] | ||
S3-212718 | Conclusion for key issue 2 | pCR | Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
merged | [WTS] [JSN] |
S3-212719 | Conclusion for key issue 3 | pCR | Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-212720 | addressing the EN in solution#11 | pCR | Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212721 | addressing the EN in solution#12 |
pCR revised to S3-213104 |
Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212722 | Conclusion for key issue 3.2 |
pCR revised to S3-213224 |
Huawei, HiSilicon | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-212723 | [draft] Reply LS for clarification on managing expired or multiple Protection Scheme and Home Network keys used for SUCI calculation. |
LS out LS is reply to S3-212429 LS To: CT6 revised to S3-213218 |
NTT DOCOMO INC. | Rel-17 |
S3-104-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-212724 | Reply LS on Small data transmissions |
LS out LS To: RAN2 |
CATT |
S3-104-e AI: 3 |
merged | [WTS] [JSN] | |||
S3-212725 | Reply LS on UE location aspects in NTN |
LS out LS To: RAN2 |
CATT |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212726 | Replay LS on UE location aspects in NTN |
LS out LS To: RAN2, RAN3, SA2, SA3-LI, CT1 |
Huawei, HiSilicon | Rel-17 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-212727 | New WID on Security Aspects of Proximity based Services (ProSe) in the 5G |
WID new revised to S3-213236 |
CATT | Rel-17 |
S3-104-e AI: 4.27 |
revised | [WTS] [JSN] | ||
S3-212728 | pCR to TR33.847- Conclusion of KI#1 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212729 | pCR to TR33.847- Conclusion of KI#2 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212730 | Living CR for UPIP for LTE |
draftCR revised to S3-213266 |
Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
revised | [WTS] [JSN] | |
S3-212731 | pCR to TR33.847- Conclusion of KI#3 |
pCR revised to S3-213092 |
CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212732 | pCR to TR33.847- Conclusion of KI#6-KI#8 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212733 | Further conclusions for KI #1 | pCR | Ericsson, Huawei, Interdigital, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212734 | Change request to living document: EAP flow |
other revised to S3-213203 |
Ericsson | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
revised | [WTS] [JSN] | |
S3-212735 | Change request to living document: Key hierarchy |
other revised to S3-213201 |
Ericsson | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
revised | [WTS] [JSN] | |
S3-212736 | Discussion on protection of UE capabilities indication in UPU and "ME support of SOR-CMCI" indicator in SoR | discussion | Ericsson | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
noted | [WTS] [JSN] | |
S3-212737 | UE parameters update data set types supported by the UE | CR | Ericsson | 33.501 17.2.1 CR#1172 catB | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
not pursued | [WTS] [JSN] |
S3-212738 | Protection of “ME support of SOR-CMCI” indication | CR | Ericsson | 33.501 17.2.1 CR#1173 catB | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212739 | Clarification on AMF transparency for UPU |
CR revised to S3-213200 |
Ericsson | 33.501 17.2.1 CR#1174 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212740 | draft reply LS on UE capabilities indication in UPU |
LS out LS is reply to S2-2101072, C1-212599 LS To: SA2, CT1 |
Ericsson | Rel-17 |
S3-104-e AI: 4.17 |
noted | [WTS] [JSN] | ||
S3-212741 | UDM Service correction | CR | Ericsson | 33.501 16.7.1 CR#1175 catF | TEI16 | Rel-16 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-212742 | UDM Service correction | CR | Ericsson | 33.501 17.2.1 CR#1176 catA | TEI16 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-212743 | FBS - Clarification in Solution 4 |
pCR revised to S3-213241 |
Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-212744 | FBS - Clarification quantum-resistance |
pCR revised to S3-213240 |
Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-212745 | pCR to TR33.847- Conclusion of KI#12 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212746 | FBS - Conclusions Solution 23 |
pCR revised to S3-213242 |
Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-212747 | FBS - Conclusions Solution 24 |
pCR revised to S3-213243 |
Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-212748 | FBS - Discussion about the stealthy FBSMitM attack and minor modifications in Solution 14 to deal with it | pCR | Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-212749 | MBS - Conclusions KI 3 | pCR | Philips International B.V. | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-212750 | MBS - Conclusions Solution 9 |
pCR revised to S3-213126 |
Philips International B.V. | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212751 | pCR to TR33.847- Conclusion of KI#13 |
pCR revised to S3-213093 |
CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212752 | Security aspects of eNPN (skeleton for living document) |
draftCR revised to S3-213204 |
Ericsson | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
revised | [WTS] [JSN] | |
S3-212753 | Change request to living document: Credentials holder using AUSF and UDM for primary authentication |
other revised to S3-213205 |
Ericsson |
S3-104-e AI: 4.17 |
revised | [WTS] [JSN] | |||
S3-212754 | Conclusions for KI#4 (initial access) | pCR | Ericsson, Huawei, InterDigital, Lenovo, Motorola Mobility, Qualcomm Incorporated | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212755 | Source PLMN-ID solution when using same N32 connection for multiple PLMN-IDs belonging to same PLMN | discussion | Ericsson |
S3-104-e AI: 4.22 |
noted | [WTS] [JSN] | |||
S3-212756 | SEPP to verify the source PLMN-ID | CR | Ericsson | 33.501 16.7.1 CR#1177 catF | 5G_eSBA | Rel-16 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212757 | SEPP to verify the source PLMN-ID | CR | Ericsson | 33.501 17.2.1 CR#1178 catA | 5G_eSBA | Rel-17 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212758 | NF to always insert PLMN-ID enabling roaming scenario | CR | Ericsson | 33.501 16.7.1 CR#1179 catF | 5G_eSBA | Rel-16 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212759 | NF to always insert PLMN-ID enabling roaming scenario | CR | Ericsson | 33.501 17.2.1 CR#1180 catA | 5G_eSBA | Rel-17 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212760 | Misalignment between TS 33.501 and TS 29.500 on audience claim of CCAs | discussion | Ericsson |
S3-104-e AI: 4.22 |
noted | [WTS] [JSN] | |||
S3-212761 | Update to Solution #3 "Using existing procedures for authorization of SCP to act on behalf of an NF Consumer" |
pCR revised to S3-213043 |
Ericsson | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212762 | Conclusion to Key Issue #4 "Authorization of SCP to act on behalf of an NF or another SCP" | pCR | Ericsson | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212763 | Correction of implementation of S3-211046 | pCR | Ericsson | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212764 | Update Solution #5: End-to-end integrity protection of HTTP body and method | pCR | Ericsson | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212765 | MBS - Update Solution 11 |
pCR revised to S3-213127 |
Philips International B.V. | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212766 | pCR to TR33.847- Update Solution#29 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212767 | Proposal for a conclusion on KI#4 – one way authentication. | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212768 | Proposal for a conclusion on KI#4 – OSNPN authentication. | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212769 | Proposal for a solution to KI#4. | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212770 | Update to solution #19 – Authorization added. |
pCR revised to S3-213147 |
Nokia, Nokia Shanghai Bell | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-212771 | User Plane Integrity Protection Policy Handling in EN-DC |
draftCR revised to S3-213253 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
revised | [WTS] [JSN] | |
S3-212772 | User Plane Integrity Protection Policy Handling in IW handover from 5GS to EPS |
draftCR revised to S3-213254 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
revised | [WTS] [JSN] | |
S3-212773 | User Plane Integrity Protection Policy Handling in DC |
draftCR revised to S3-213255 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
revised | [WTS] [JSN] | |
S3-212774 | User Plane Integrity Protection Policy Handling in IW handover from EPS to 5GS |
draftCR revised to S3-213256 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
revised | [WTS] [JSN] | |
S3-212775 | User Plane Integrity Protection | draftCR | Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-212776 | User Plane Integrity Protection: Correction to A.7 | draftCR | Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-212777 | Add details of UPIP algorithms to be supported | draftCR | Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
noted | [WTS] [JSN] | |
S3-212778 | [DRAFT] LS on use of LTE algorithms or NR algorithms for UP integrity protection with NR PDCP |
LS out LS To: RAN2, RAN3 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
noted | [WTS] [JSN] | |
S3-212779 | New WID on 5GFBS | WID new | Apple, AT&T, Deutsche Telekom, Charter Communication, China Telecom, China Unicom, NIST, CableLabs, Interdigital, Ericsson, Samsung, CAICT, CATT, Intel, vivo, MITRE, Philips | Rel-17 |
S3-104-e AI: 4.27 |
noted | [WTS] [JSN] | ||
S3-212780 | 5GFBS-Update of solution#17 |
pCR revised to S3-213238 |
Apple, CableLabs, Intel | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-212781 | 5GFBS-Conclusion on key issue#2 | pCR | Apple | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-212782 | 5GFBS-Conclusion on key issue#1 on solution#17 | pCR | Apple | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-212783 | MEC- Discussion paper on the privacy issue EEC ID | pCR | Apple | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212784 | MEC-Discussion paper on including EEC ID in the authentication procedure | pCR | Apple | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212785 | MEC- New solution on EEC ID privacy protection | pCR | Apple | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212786 | MEC - Conclusion on the key issue 2 on the authentication between EEC and ECS | pCR | Apple | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212787 | MEC- Addressing the EN in solution#28 on EEC ID authentication | pCR | Apple | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212788 | UC3S-User consent update | pCR | Apple | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-212789 | MBS-new solution for key issue#2 | pCR | Apple | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
withdrawn | [WTS] [JSN] |
S3-212790 | Discussion paper on the FSAG Doc 92_003 on NAS messages attack | discussion | Apple |
S3-104-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-212791 | CR on TS 33.501 on adding requirement to mitigate the attack of selectively dropping NAS messages | CR | Apple | 33.501 17.2.1 CR#1181 catC | TEI17 | Rel-17 |
S3-104-e AI: 6 |
not pursued | [WTS] [JSN] |
S3-212792 | Reply to GSMA on FSAG Doc 92_003 on NAS messages attack |
LS out LS is reply to GSMA source LS: S3-211384 LS To: GSMA |
Apple |
S3-104-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-212793 | Discussion paper on GSMA LS of SPARROW attack | discussion | Apple |
S3-104-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-212794 | Draft reply LS to RAN2 on SDT security |
LS out LS is reply to RAN2 source LS: S3-212428 /R2-2104401 LS To: RAN2 |
Apple |
S3-104-e AI: 3 |
merged | [WTS] [JSN] | |||
S3-212795 | Discussion paper on the security context handling in IRAT | discussion | Apple |
S3-104-e AI: 4.28 |
noted | [WTS] [JSN] | |||
S3-212796 | CR on TS 33.501 on the security context handling in IRAT |
CR revised to S3-213239 |
Apple | 33.501 17.2.1 CR#1182 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212797 | CR on TS 33.501 on SOR-MAC calculation | CR | Apple | 33.501 17.2.1 CR#1183 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212798 | New WID on Security Assurance Specification for Management Function | WID new | Huawei, HiSilicon | Rel-18 |
S3-104-e AI: 4.28 |
noted | [WTS] [JSN] | ||
S3-212799 | New WID on security aspects of MSGin5G | WID new | China Mobile, Samsung, Huawei, Hisilicon | Rel-17 |
S3-104-e AI: 4.27 |
agreed | [WTS] [JSN] | ||
S3-212800 | draftCR for the skeleton for MSGin5G_SEC | draftCR | China Mobile | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 4.27 |
approved | [WTS] [JSN] | |
S3-212801 | Add conclusion to KI #1 | pCR | China Mobile | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212802 | Transport security of MSGin5G-1 interface | pCR | China Mobile | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212803 | Solution to the transport security of MSGin5G-2 and MSGin5G-4 | pCR | China Mobile | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212804 | Add conclusion to KI#2 | pCR | China Mobile | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
noted | [WTS] [JSN] |
S3-212805 | Solution to key issue#3 | pCR | China Mobile | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212806 | Solution to key issue#4 | pCR | China Mobile | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212807 | Editorial corrections for TR33.862 | pCR | China Mobile | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212808 | Deleting the EN of solution#4 | pCR | China Mobile | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212809 | Update and evaluation of solution #32 |
pCR revised to S3-213074 |
Philips International B.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212810 | New WID on security aspects of eNA |
WID new revised to S3-213232 |
China Mobile | Rel-17 |
S3-104-e AI: 4.27 |
revised | [WTS] [JSN] | ||
S3-212811 | Draft_skeleton_for_draft_CR_eNA_SEC |
other revised to S3-213269 |
China Mobile | Rel-17 |
S3-104-e AI: 4.27 |
revised | [WTS] [JSN] | ||
S3-212812 | Solution to abnormal behaviour detection of IoT SIM card | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212813 | Add conclusion to KI #1.2 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212814 | Add conclusion to KI #1.5 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212815 | Add conclusion to KI #2.1 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212816 | Add conclusion to KI #3.2 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212817 | Add evaluation to solution #3 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212818 | Discussion on the conclusion of KI#1.3 | discussion | China Mobile | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] | |
S3-212819 | Add conclusion to KI #6 |
pCR revised to S3-213079 |
China Mobile | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-212820 | Clean up the editorial issues | CR | China Mobile | 33.818 17.0.0 CR#1 catF | FS_VNP_SECAM_SCAS | Rel-17 |
S3-104-e AI: 5.2 |
agreed | [WTS] [JSN] |
S3-212821 | Clarification on Data Masking on Integration Analysis |
CR revised to S3-213257 |
China Mobile | 33.521 17.0.0 CR#2 catF | SCAS_5G_NWDAF | Rel-17 |
S3-104-e AI: 4.5 |
revised | [WTS] [JSN] |
S3-212822 | Deleting the NOTE of roaming | CR | China Mobile | 33.535 17.2.1 CR#96 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212823 | Prevention of attacks on slice core by CCA modifications - Rel-16 |
CR revision of S3-211985 |
Nokia, Nokia Shanghai Bell | 33.501 16.7.1 CR#11311 catF | 5G_eSBA | Rel-16 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212824 | Prevention of attacks on slice core by CCA modifications - Rel-17 |
CR revision of S3-211986 |
Nokia, Nokia Shanghai Bell | 33.501 17.2.1 CR#11321 catA | 5G_eSBA | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212825 | KAF refresh | CR | China Mobile | 33.535 17.2.1 CR#97 catB | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212826 | IPUPS overload control | CR | Nokia, Nokia Shanghai Bell | 33.501 17.2.1 CR#1184 catB | DUMMY | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212827 | Editorial corrections to the UAS TR |
pCR revised to S3-213067 |
Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-212828 | Resolution of EN in solutions |
pCR revised to S3-213068 |
Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-212829 | Proposed conclusion for key issue #3 | pCR | Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-212830 | Proposed conclusion for key issue #5 | pCR | Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-212831 | Proposed common conclusion for key issues #6 and #7 | pCR | Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-212832 | Resolution of EN in general clauses | pCR | Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212833 | Cover sheet |
TS or TR cover revised to S3-213069 |
Qualcomm Incorporated | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
revised | [WTS] [JSN] | |
S3-212834 | TS 33.256 skeleton | draft TS | Qualcomm Incorporated | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
noted | [WTS] [JSN] | |
S3-212835 | Proposed text for scope and overview of UAS TS | other | Qualcomm Incorporated |
S3-104-e AI: 4.2 |
noted | [WTS] [JSN] | |||
S3-212836 | Proposed text on UUAA for UAS TS | other | Qualcomm Incorporated |
S3-104-e AI: 4.2 |
merged | [WTS] [JSN] | |||
S3-212837 | Proposed text on location security for UAS TS | other | Qualcomm Incorporated |
S3-104-e AI: 4.2 |
merged | [WTS] [JSN] | |||
S3-212838 | Discussion on adding SCAS for the various split gNB cases |
discussion revision of S3-211792 |
Qualcomm Incorporated, Deutsche Telekom AG |
S3-104-e AI: 4.3 |
noted | [WTS] [JSN] | |||
S3-212839 | Adding SCAS for the various split gNB cases | CR | Qualcomm Incorporated, Deutsche Telekom AG | 33.511 17.0.0 CR#25 catB | eSCAS_5G | Rel-17 |
S3-104-e AI: 4.3 |
not pursued | [WTS] [JSN] |
S3-212840 | Corrections to the TLS with AKMA specification | CR | Qualcomm Incorporated | 33.535 17.2.1 CR#98 catF | AKMA_TLS | Rel-17 |
S3-104-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-212841 | Adding TLS 1.3 with AKMA keys | CR | Qualcomm Incorporated | 33.535 17.2.1 CR#99 catB | AKMA_TLS | Rel-17 |
S3-104-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-212842 | Correction to the GBA TLS 1.3 specification | CR | Qualcomm Incorporated | 33.222 17.0.0 CR#55 catF | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-212843 | Proposed conclusion for key issue #4.1 | pCR | Qualcomm Incorporated, Thales | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-212844 | Some proposed text for the assessment of attack risk table | pCR | Qualcomm Incorporated | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-212845 | Proposed conclusion for the linkability parts of key issues #2.1 and 2.2 | pCR | Qualcomm Incorporated | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212846 | Adding MACS as an input parameter to the calculation of AK* to provide freshness |
CR revision of S3-201936 |
Qualcomm Incorporated, Thales | 33.102 16.0.0 CR#2773 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
not pursued | [WTS] [JSN] |
S3-212847 | Discussion on proposed response to RAN3 LS on User Plane Integrity Protection for eUTRA connected to EPC | discussion | Qualcomm Incorporated |
S3-104-e AI: 4.28 |
noted | [WTS] [JSN] | |||
S3-212848 | LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS out LS To: RAN3 revised to S3-213258 |
Qualcomm Incorporated |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] | |||
S3-212849 | Proposed conclusions for key issue #1 and key issue #2 | pCR | Qualcomm Incorporated | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212850 | Proposed conclusion for AMF Re-allocation | pCR | Qualcomm Incorporated | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212851 | Conclusion on KI #3, KI #4 and KI #9 related to security for the Layer-3 UE-to-Network relay scenario | pCR | Qualcomm Incorporated, MITRE, AT&T | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212852 | Conclusion of KI #1 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212853 | EN resolution of Solution #34 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212854 | Evaluation of Solution #34 |
pCR revised to S3-213076 |
Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212855 | Evaluation of Solution #24 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212856 | EN resolution of Solution #18 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212857 | Conclusion of KI #3 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212858 | Conclusion of KI #4 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212859 | Update of solution #18 to support privacy protection | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212860 | Update an evaluation for solution #10 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212861 | Conclusion of security and privacy of groupcast communication | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212862 | Way forward for the 5G MBS security | discussion | Qualcomm Incorporated | FS_5MBS_SEC |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] | ||
S3-212863 | Update of Solution #12 |
pCR revised to S3-213077 |
Qualcomm Incorporated | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212864 | Evaluation of Solution #12 | pCR | Qualcomm Incorporated | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
merged | [WTS] [JSN] |
S3-212865 | Conclusion for the KI#2 |
pCR revised to S3-213078 |
Qualcomm Incorporated | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212866 | Solution #4 Evaluation (Enriched MR) | pCR | Qualcomm Incorporated | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-212867 | eNPN: Evaluation of Solution #5 | pCR | Qualcomm Incorporated | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212868 | pCR: Additional conclusions for KI #1 | pCR | Qualcomm Incorporated | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212869 | Sending UE identifier to the AKMA AF |
CR revision of S3-211817 |
Qualcomm Incorporated | 33.535 17.2.1 CR#781 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212870 | Solution for 5G NSWO authentication | pCR | Qualcomm Incorporated | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
merged | [WTS] [JSN] |
S3-212871 | Alignment of requirements with specification updates |
CR revision of S3-211935 |
Nokia, Nokia Shanghai Bell | 33.117 16.7.0 CR#712 catF | SCAS_5G | Rel-16 |
S3-104-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-212872 | Alignment of requirements with specification updates |
CR revision of S3-212395 |
Nokia, Nokia Shanghai Bell | 33.117 16.7.0 CR#713 catF | SCAS_5G | Rel-16 |
S3-104-e AI: 4.3 |
not pursued | [WTS] [JSN] |
S3-212873 | Solution to KI#1 (Support of EAP-AKA’ authentication for NSWO) using credentials retrieved from UDM |
pCR revised to S3-213091 |
Ericsson | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-212874 | Solution Privacy preservation of transmitted data | pCR | Nokia Germany | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-212875 | Solution to KI#1 (Support of EAP-AKA’ authentication for NSWO) using credentials retrieved from UDM/ARPF via HSS | pCR | Ericsson | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-212876 | Reply LS on Misalignment on usage of OAuth within 3GPP 29.510 |
LS out LS is reply to S3-211367 source LS: S3-211367 LS To: GSMA FASG RIFS / 5GIS revised to S3-213192 |
Nokia, Nokia Shanghai Bell |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] | |||
S3-212877 | LS on N32 and multiple PLMN IDs |
LS out LS To: GSMA NG 5GJA |
Nokia, Nokia Shanghai Bell |
S3-104-e AI: 4.22 |
noted | [WTS] [JSN] | |||
S3-212878 | KI and solution to NRF deployments |
pCR revised to S3-213057 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212879 | vNRF-hNRF mutual authentication in service access authorization | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212880 | Way forward SID eSBA |
pCR revised to S3-213061 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212881 | WID eSBA | WID new | Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 4.27 |
noted | [WTS] [JSN] | ||
S3-212882 | Sol 1 NFp verification – EN resolutions and evaluation |
pCR revised to S3-213053 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212883 | Editorial update on trust clause | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212884 | EN resolution on trust model for SCP |
pCR revised to S3-213058 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212885 | Access token request for NF Set – EN resolution |
pCR revised to S3-213055 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212886 | Access token request for NF Set – RFC clarification |
pCR revised to S3-213056 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212887 | SCP authorization |
pCR revised to S3-213054 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212888 | SCP authorization solution evaluation | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212889 | SCP authorization conclusion | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212890 | KI and Solution for verification of NFc by NF producers | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212891 | NRF service definition R15 |
CR revised to S3-213196 |
Nokia, Nokia Shanghai Bell | 33.501 15.13.0 CR#1185 catF | 5G_eSBA | Rel-15 |
S3-104-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-212892 | NRF service definition R16 |
CR revised to S3-213197 |
Nokia, Nokia Shanghai Bell | 33.501 16.7.1 CR#1186 catA | 5G_eSBA | Rel-16 |
S3-104-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-212893 | NRF service definition R17 |
CR revised to S3-213199 |
Nokia, Nokia Shanghai Bell | 33.501 17.2.1 CR#1187 catA | 5G_eSBA | Rel-17 |
S3-104-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-212894 | SBA NRF roaming clarification | CR | Nokia, Nokia Shanghai Bell | 33.501 17.2.1 CR#1188 catF | 5G_eSBA | Rel-17 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212895 | OAuth misalignment - R15 | CR | Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | 33.501 15.13.0 CR#1189 catF | TEI15 | Rel-15 |
S3-104-e AI: 4.28 |
merged | [WTS] [JSN] |
S3-212896 | OAuth misalignment - R16 | CR | Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | 33.501 16.7.1 CR#1190 catA | TEI15 | Rel-16 |
S3-104-e AI: 4.28 |
merged | [WTS] [JSN] |
S3-212897 | OAuth misalignment - R17 |
CR revised to S3-213189 |
Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | 33.501 17.2.1 CR#1191 catA | TEI15 | Rel-17 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-212898 | Alignment for Oauth2.0 validation R15 |
CR revised to S3-213198 |
Nokia, Nokia Shanghai Bell | 33.501 15.13.0 CR#1192 catF | 5G_eSBA | Rel-15 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212899 | Alignment for Oauth2.0 validation R16 | CR | Nokia, Nokia Shanghai Bell | 33.501 16.7.1 CR#1193 catA | 5G_eSBA | Rel-16 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212900 | Alignment for Oauth2.0 validation R17 | CR | Nokia, Nokia Shanghai Bell | 33.501 17.2.1 CR#1194 catA | 5G_eSBA | Rel-17 |
S3-104-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212901 | Discussion on Refresh of KAKMA and KAF | discussion | Samsung, China Mobile | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
noted | [WTS] [JSN] | |
S3-212902 | [CR] Refresh of KAF and KAKMA | CR | Samsung | 33.535 17.2.0 CR#100 catB | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212903 | [CR] HN triggering Primary (Re)Authentication | CR | Samsung | 33.501 17.2.1 CR#1195 catB | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212904 | [5GMSG] Evaluation of Solution#1 | pCR | Samsung | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212905 | [5GMSG] Evaluation of Solution#3 | pCR | Samsung | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212906 | [5GMSG] Evaluation of Solution#5 | pCR | Samsung | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212907 | [5GMSG] Evaluation of Solution#8 | pCR | Samsung | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212908 | [5GMSG] Conclusion for KI#1 and KI#2 | pCR | Samsung | 33.862 0.5.0 | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
noted | [WTS] [JSN] |
S3-212909 | [ProSe] Updates to Solution#1 |
pCR revised to S3-213137 |
Samsung | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212910 | [ProSe] Updates to evaluation of solution#1 |
pCR revised to S3-213138 |
Samsung | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212911 | [EDGE] Update to Solution#3 |
pCR revised to S3-213131 |
Samsung | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212912 | [EDGE] Update to evaluation of Solution#3 |
pCR revised to S3-213135 |
Samsung | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212913 | [EDGE] Conclusion for KI#1 | pCR | Samsung | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212914 | [EDGE] Conclusion for KI#2 | pCR | Samsung, Lenovo, Motorola Mobility | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212915 | [UC3S] Solution on user's consent for exposure of information to Edge Applications | pCR | Samsung | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-212916 | KI on Authorization for Inter-Slice Access |
pCR revised to S3-213139 |
Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212917 | New Solution to KI #X: Authorization for Inter-Slice Access | pCR | Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212918 | [AMF Re-alloc] Proposed Way Forward | discussion | Samsung | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-212919 | Removal of Editor’s Note in Solution #5 | pCR | Samsung | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212920 | Discussion on MBS Security | discussion | Samsung | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
noted | [WTS] [JSN] | |
S3-212921 | [MBS] Solution#13 Evaluation |
pCR revised to S3-213136 |
Samsung | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212922 | [IAB] Add requirement to Key Issue #2.4 | pCR | Samsung | 33.824 0.9.0 | FS_NR_IAB_Sec | Rel-17 |
S3-104-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-212923 | [IAB] Solution on authenticity verification of BH-RLF indication | pCR | Samsung | 33.824 0.9.0 | FS_NR_IAB_Sec | Rel-17 |
S3-104-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-212924 | [IAB] Solution to protect the BAP control PDU exchange | pCR | Samsung | 33.824 0.9.0 | FS_NR_IAB_Sec | Rel-17 |
S3-104-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-212925 | [IAB] Conclusion for KI#2.4 | pCR | Samsung | 33.824 0.9.0 | FS_NR_IAB_Sec | Rel-17 |
S3-104-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-212926 | Update to Solution #10 | pCR | Samsung | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212927 | Update on Solution 6 |
pCR revised to S3-213141 |
Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212928 | New solution on key issue #5 | pCR | Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212929 | Evaluation for solution 1 |
pCR revised to S3-213142 |
Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212930 | Evaluation for solution 4 | pCR | Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212931 | Evaluation for solution 5 |
pCR revised to S3-213143 |
Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212932 | Conclusion for KI#1 | pCR | Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212933 | Conclusion for KI#5 | pCR | Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212934 | Conclusion on key issue #3 and key issue #4 | pCR | Ericsson | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212935 | Update to solution #21 | pCR | Ericsson | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212936 | Update to Solution#4 | pCR | Lenovo, Motorola Mobility | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212937 | Conclusions for KI#10 "Authorization during Edge Data Network change" | pCR | Ericsson | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212938 | Conclusions for KI#7 "Security of Network Information Provisioning to Local Applications with low latency procedure" | pCR | Ericsson | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-212939 | Update to Solution #17: Resolving EN on Token Usage | pCR | Ericsson | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212940 | LS on EAS and ECS identifiers |
LS out LS To: SA6 revised to S3-213089 |
Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] | |
S3-212941 | Update to conclusion #1 | pCR | Ericsson | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-212942 | Conclusion on KI#1 | pCR | Ericsson | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212943 | Conclusion on KI#2 | pCR | Ericsson | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212944 | Update to Solution #17: Resolving ENs |
pCR revised to S3-213090 |
Ericsson | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212945 | Discussion on Mission Critical Security over 5G System | discussion | Ericsson | MCXSec2 | Rel-17 |
S3-104-e AI: 4.9 |
noted | [WTS] [JSN] | |
S3-212946 | Solution to address KI#1 |
pCR revised to S3-213049 |
Lenovo, Motorola Mobility | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-212947 | Solution to address KI#1 and KI#4 |
pCR revised to S3-213042 |
Lenovo, Motorola Mobility | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-212948 | Conclusion for KI#6 | pCR | Lenovo, Motorola Mobility | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-212949 | Conclusion to KI#1 | pCR | Lenovo, Motorola Mobility | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212950 | EAP ID Request in NSSAA Procedure (Rel-16) | CR | Ericsson | 33.501 16.7.1 CR#1196 catF | eNS | Rel-16 |
S3-104-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-212951 | eEDGE: Corrections in Solution #13 | pCR | Xiaomi Technology | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212952 | eEDGE: Add Clarifications for Solutions covering Application Layer | pCR | Xiaomi Technology | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212953 | ProSe: Addional Evaluation for Solution #9 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212954 | ProSe: Addional Evaluation for Solution #10 |
pCR revised to S3-213158 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212955 | ProSe: Addional Evaluation for Solution #14 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212956 | ProSe: Addional Evaluation for Solution #15 |
pCR revised to S3-213159 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212957 | ProSe: Addional Evaluation for Solution #18 |
pCR revised to S3-213160 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212958 | ProSe: Addional Evaluation for Solution #22 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212959 | ProSe: Add Evaluation for Solution #27 |
pCR revised to S3-213161 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212960 | ProSe: Add Evaluation for Solution #28 |
pCR revised to S3-213162 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212961 | ProSe: Addional Evaluation for Solution #30 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212962 | ProSe: Conclusions for Key Issues #6, #7, #8 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212963 | ProSe: Conclusion for Key Issue #13 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212964 | ProSe: Conclusion for Key Issue #16 |
pCR revised to S3-213163 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212965 | ProSe: New Solution for Key Issue #17 |
pCR revised to S3-213164 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212966 | ProSe: Conclusion for Key Issue #17 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212967 | ProSe: New Solution for Key Issue #3 |
pCR revised to S3-213165 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212968 | ProSe: Conclusion for Key Issue #3 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212969 | eNPN: Conclusion Update for Key Issue #1 | pCR | Xiaomi Technology | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212970 | eNPN: New Solution for Key Issue #2 | pCR | Xiaomi Technology | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212971 | eNPN: Resolution of the Editor’s Notes in Key Issue #2 | pCR | Xiaomi Technology, Lenovo, Motorola Mobility | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212972 | eNPN: Conclusion for Key Issue #2 | pCR | Xiaomi Technology | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212973 | New KI on Secrets in Container Images |
pCR revised to S3-213182 |
Altiostar | 33.848 0.8.0 | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-212974 | EAP ID Request in NSSAA Procedure (Rel-17) | CR | Ericsson | 33.501 17.2.1 CR#1197 catA | eNS | Rel-17 |
S3-104-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-212975 | New KI on Container breakouts |
pCR revised to S3-213188 |
Altiostar | 33.848 0.8.0 | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-212976 | Security for temporary calls | CR | CATT | 33.18 17.3.0 CR#176 catB | MCXSec2 | Rel-17 |
S3-104-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-212977 | LS on EAP ID Request in NSSAA Procedure |
LS out LS To: SA2 |
Ericsson | eNS | Rel-16 |
S3-104-e AI: 4.25 |
noted | [WTS] [JSN] | |
S3-212978 | Ed Note Removal for Solution 11 |
pCR revised to S3-213048 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212979 | Ed Note Removal to include mechanism when notification sent via MFAF for Solution 11 |
pCR revised to S3-213052 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212980 | Evaluation to the Solution 11 |
pCR revised to S3-213051 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212981 | Ed Note Removal for Solution 10 |
pCR revised to S3-213039 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212982 | Conclusion to KI 1.3 |
pCR revised to S3-213050 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212983 | Evaluation to the Solution 10 |
pCR revised to S3-213044 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212984 | Editorial Notes Removal for Solution 10 to address authorization mechanisms when data is sent via MFAF |
pCR revised to S3-213041 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212985 | Enhancement to the solution on Detection of anomalous NF behaviour by NWDAF | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212986 | Evaluation to the Solution 7 |
pCR revised to S3-213047 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212987 | Conclusion to KI 2.2 | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212988 | Evaluation on Sol 14 - Solution to ML restrictive transfer Framework | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212989 | Update KI 3.3 - Ensuring restrictive transfer of ML models between authorized NWDAF instances |
pCR revised to S3-213046 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212990 | Evaluation on Sol 5- Providing the Security protection of data via Messaging Framework | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212991 | Update to KI 1.4 | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212992 | Conclusion to KI 1.4 | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212993 | Solution on Protection of data sent via MFAF using existing SBA mechanisms |
pCR revised to S3-213045 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212994 | LS on NF Service Producer Meta Data Addition by ADRF |
LS out LS To: SA2 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-212995 | Removal of Editor’s Note of Solution#4 | pCR | Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212996 | Adding Evaluation to Solution#4 |
pCR revised to S3-213064 |
Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212997 | Removal of Editor’s Note of Solution#5 | pCR | Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212998 | Adding Evaluation to Solution#5 | pCR | Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212999 | Solution on NSWO authentication with AAA-Server | pCR | Lenovo, Motorola Mobility | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
merged | [WTS] [JSN] |
S3-213000 | Tracking, enforcement, and validity of user consent | pCR | Ericsson | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
merged | [WTS] [JSN] |
S3-213001 | Solution on NSWO authentication via an interworking function | pCR | Lenovo, Motorola Mobility | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-213002 | Evaluation of the potential security issue in QoE report handling at QoE pause | discussion | Lenovo, Motorola Mobility |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-213003 | Padding SUPIs in NAI format for non-null schemes | CR | Ericsson, AT&T, CableLabs | 33.501 17.2.1 CR#1198 catC | TEI17 | Rel-17 |
S3-104-e AI: 6 |
not pursued | [WTS] [JSN] |
S3-213004 | [DRAFT] Reply LS on QoE report handling at QoE pause |
LS out LS is reply to S3-212435 LS To: RAN2 |
Lenovo, Motorola Mobility |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-213005 | A new onboarding solution addressing KI#2 |
pCR revised to S3-213065 |
Lenovo, Motorola Mobility | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-213006 | pCR to 33.846: impacts on the USIM of solution #4.6 | pCR | THALES | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-213007 | pCR to 33.846: assessment of attack risk | pCR | THALES | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-213008 | pCR to 33.839: solution #26 |
pCR revised to S3-213211 |
THALES | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-213009 | pCR to 33.839: solution #27 |
pCR revised to S3-213212 |
THALES | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-213010 | pCR to 33.839: conclusion for Key Issue #1 | pCR | THALES | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-213011 | pCR to 33.839: Conclusion for Key Issue #2 | pCR | THALES | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-213012 | Recovering NSSAI and ENSI mapping (Rel-16) | CR | Samsung | 33.501 16.7.1 CR#1199 catF | eNS | Rel-16 |
S3-104-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-213013 | Recovering NSSAI and ENSI mapping (Rel-17) | CR | Samsung | 33.501 17.2.1 CR#1200 catA | eNS | Rel-17 |
S3-104-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-213014 | Comment on 256-bit algorithms based on Snow-V | discussion | CATT |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-213015 | Update_on_Key_issue#1.4 |
pCR revised to S3-213152 |
Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-213016 | Update_on_Solution#5 |
pCR revised to S3-213154 |
Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-213017 | Update_on_Solution#12 |
pCR revised to S3-213153 |
Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-213018 | Conclusion on KI#1.3 | pCR | Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-213019 | Conclusion on KI#1.4 | pCR | Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-213020 | eCryptPr 01 CR 33.310 R17 Security updates for algorithms and protocols | CR | Ericsson | 33.31 16.8.0 CR#120 catB | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-213021 | eCryptPr 02 CR 33.203 R17 Security updates for algorithms and protocols | CR | Ericsson | 33.203 16.1.0 CR#259 catB | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-213022 | Security updates for algorithms and protocols for 33.310 |
draftCR revised to S3-213264 |
Ericsson | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-213023 | Security updates for algorithms and protocols for 33.210 |
draftCR revised to S3-213265 |
Ericsson | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-213024 | User consent: New key issue on naming of purposes |
pCR revised to S3-213071 |
NTT DOCOMO INC. | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-213025 | draft CR to 33.401 - addition of UPIP requirements (NEA and NIA based) | draftCR | VODAFONE Group Plc | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
noted | [WTS] [JSN] | |
S3-213026 | draft CR to 33.401 - addition of UPIP requirements (EEA and EIA based) | draftCR | VODAFONE Group Plc | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
noted | [WTS] [JSN] | |
S3-213027 | [Draft] Reply LS on UE location aspects in NTN |
LS out LS is reply to S3-212432 source LS: R2-2106543 LS To: RAN2 |
Xiaomi Technology | Rel-17 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-213028 | Addressing Editor's notes of KI#2 | pCR | Philips International B.V., Lenovo, Motorola Mobility | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-213029 | New KI on Compromised slice information | pCR | Lenovo, Motorola Mobility | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-213030 | Update to Key Issue #1 | pCR | Lenovo, Motorola Mobility | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
approved | [WTS] [JSN] |
S3-213031 | Clarification on UP IP indication based on RAN3 LS |
draftCR revised to S3-213231 |
Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
revised | [WTS] [JSN] | |
S3-213032 | SA3 meeting calendar | other | WG Chair |
S3-104-e AI: 7 |
noted | [WTS] [JSN] | |||
S3-213033 | Reply LS on Security risk evaluation of using long term key for another key derivation than AKA | LS in | ETSI SAGE |
S3-104-e AI: 5.5 |
postponed | [WTS] [JSN] | |||
S3-213034 | Reply LS on Small data transmissions |
LS out LS is reply to S3-212428 source LS: S3-212428/R2-2104401 LS To: RAN2 |
InterDigital, Inc. | NR_SmallData_INACTIVE-Core | Rel-17 |
S3-104-e AI: 3 |
approved | [WTS] [JSN] | |
S3-213035 | LS on full registration request in AMF reallocation via RAN |
LS out LS To: SA2 |
Huawei, HiSilicon | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
approved | [WTS] [JSN] | |
S3-213036 | LS on NSAC procedure |
LS out LS To: SA2 |
Huawei, HiSilicon | Rel-17 |
S3-104-e AI: 5.21 |
approved | [WTS] [JSN] | ||
S3-213037 | Non-Seamless WLAN offload Authentication in 5GS |
pCR revision of S3-212514 |
Nokia, Nokia Shanghai Bell, AT&T,Lenovo, Motorola Mobility, Huawei, HiSilicon, Samsung, Intel, Qualcomm Incorporated, Thales | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-213038 | Editor note removal and update for solution#10 |
pCR revision of S3-212512 |
Nokia, Nokia Shanghai Bell | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213039 | Ed Note Removal for Solution 10 |
pCR revision of S3-212981 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213040 | Reply LS on Header Enrichment for HTTPS in PFCP |
LS in LS is reply to S3-212344 |
C4-214531 |
S3-104-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-213041 | Editorial Notes Removal for Solution 10 to address authorization mechanisms when data is sent via MFAF |
pCR revision of S3-212984 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213042 | Solution to address KI#4 |
pCR revision of S3-212947 |
Lenovo, Motorola Mobility | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-213043 | Update to Solution #3 "Using existing procedures for authorization of SCP to act on behalf of an NF Consumer" |
pCR revision of S3-212761 |
Ericsson | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213044 | Evaluation to the Solution 10 |
pCR revision of S3-212983 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213045 | Solution on Protection of data sent via MFAF using existing SBA mechanisms |
pCR revision of S3-212993 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213046 | Update KI 3.3 - Ensuring restrictive transfer of ML models between authorized NWDAF instances |
pCR revision of S3-212989 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213047 | Evaluation to the Solution 7 |
pCR revision of S3-212986 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213048 | Ed Note Removal for Solution 11 |
pCR revision of S3-212978 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213049 | Solution to address KI#1 |
pCR revision of S3-212946 |
Lenovo, Motorola Mobility | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-213050 | Conclusion to KI 1.3 |
pCR revision of S3-212982 |
Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213051 | Evaluation to the Solution 11 |
pCR revision of S3-212980 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213052 | Ed Note Removal to include mechanism when notification sent via MFAF for Solution 11 |
pCR revision of S3-212979 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213053 | Sol 1 NFp verification – EN resolutions and evaluation |
pCR revision of S3-212882 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213054 | SCP authorization |
pCR revision of S3-212887 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213055 | Access token request for NF Set – EN resolution |
pCR revision of S3-212885 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213056 | Access token request for NF Set – RFC clarification |
pCR revision of S3-212886 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213057 | KI and solution to NRF deployments |
pCR revision of S3-212878 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213058 | EN resolution on trust model for SCP |
pCR revision of S3-212884 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213059 | TR 33.847 Update for solution #10 |
pCR revision of S3-212478 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213060 | TR 33.847 Update for solution #24 |
pCR revision of S3-212479 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213061 | Way forward SID eSBA |
pCR revision of S3-212880 |
Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-213062 | TR 33.847 Update for solution #25 |
pCR revision of S3-212481 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213063 | Conclusions for U2N relay Key Issues |
pCR revision of S3-212485 |
InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon , Qualcomm Incorporated, MITRE, AT&T, Ericsson | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213064 | Adding Evaluation to Solution#4 |
pCR revision of S3-212996 |
Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213065 | A new onboarding solution addressing KI#2 |
pCR revision of S3-213005 |
Lenovo, Motorola Mobility | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-213066 | Further conclusions for KI #1 |
pCR revision of S3-212521 |
CableLabs,Ericsson, Charter Communications, Intel | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-213067 | Editorial corrections to the UAS TR |
pCR revision of S3-212827 |
Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-213068 | Resolution of EN in solutions |
pCR revision of S3-212828 |
Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-213069 | Cover sheet TR 33.854 |
TS or TR cover revision of S3-212833 |
Qualcomm Incorporated | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
approved | [WTS] [JSN] | |
S3-213070 | Updates to solution 14: Removal of Editor’s notes: Security Issues |
pCR revision of S3-212688 |
Intel Corporation (UK) Ltd | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-213071 | User consent: New key issue on naming of purposes |
pCR revision of S3-213024 |
NTT DOCOMO INC. | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213072 | Draft TR 33.864 v0.6.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson Hungary Ltd | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
approved | [WTS] [JSN] | |
S3-213073 | Updates to terminology in the architecture assumptions |
pCR revision of S3-212494 |
Ericsson | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-213074 | Update and evaluation of solution #32 |
pCR revision of S3-212809 |
Philips International B.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213075 | TR 33.881 revision for NSWO | draft TR | Nokia Corporation | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
approved | [WTS] [JSN] | |
S3-213076 | Evaluation of Solution #34 |
pCR revision of S3-212854 |
Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213077 | Update of Solution #12 |
pCR revision of S3-212863 |
Qualcomm Incorporated | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213078 | Conclusion for the KI#2 |
pCR revision of S3-212865 |
Qualcomm Incorporated | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213079 | Add conclusion to KI #6 |
pCR revision of S3-212819 |
China Mobile, Lenovo, Motorola Mobility, InterDigital, Europe, Ltd., Qualcomm Incorporated, Huawei, HiSilicon | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-213080 | TR 33.850 for 5MBS security | draft TR | Huawei, Hisilicon | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] | |
S3-213081 | Update to Solution #5 |
pCR revision of S3-212547 |
ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213082 | New solution on control plane based provisioning PS to AUSF |
pCR revision of S3-212557 |
ZTE Corporation | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-213083 | Update for Conclusion on Key Issue #4 |
pCR revision of S3-212522 |
China Telecommunications, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213084 | Add the evaluation of the solution #6 |
pCR revision of S3-212552 |
ZTE Corporation | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213085 | Update the solution #6 |
pCR revision of S3-212556 |
ZTE Corporation | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213086 | Update the solution #11 |
pCR revision of S3-212562 |
ZTE Corporation | 33.864 0.5.0 | FS_AMFREAL_SEC | Rel-17 |
S3-104-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-213087 | Evaluation for sol#13 |
pCR revision of S3-212472 |
LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213088 | Updates on sol#13 |
pCR revision of S3-212516 |
LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213089 | LS on EAS and ECS identifiers |
LS out LS To: SA6 revision of S3-212940 |
Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-213090 | Update to Solution #17: Resolving ENs |
pCR revision of S3-212944 |
Ericsson | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-213091 | Solution to KI#1 (Support of EAP-AKA’ authentication for NSWO) using credentials retrieved from UDM |
pCR revision of S3-212873 |
Ericsson | 33.881 0.1.0 | FS_NSWO_5G | Rel-17 |
S3-104-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-213092 | pCR to TR33.847- Conclusion of KI#3 |
pCR revision of S3-212731 |
CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213093 | pCR to TR33.847- Conclusion of KI#13 |
pCR revision of S3-212751 |
CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213094 | draft TR 33.866 0.6.0 | draft TR | China Mobile Com. Corporation | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] | |
S3-213095 | New Solution for Check of User Consent for 3GPP service Exposure |
pCR revision of S3-212701 |
Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213096 | General Conclusion on UDM service for User Consent Check |
pCR revision of S3-212702 |
Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213097 | General Conclusion on Generic Requirement for the Procedures for User Consent Check |
pCR revision of S3-212703 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213098 | General Conclusion on UDM service for User Consent Revocation |
pCR revision of S3-212704 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericssion | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213099 | General Conclusion on Generic Requirement for the Procedure for User Consent Revocation |
pCR revision of S3-212707 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213100 | Solution for user consent revocation |
pCR revision of S3-212708 |
Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213101 | Solution Update and Evaluation for Solution 3 |
pCR revision of S3-212709 |
Huawei, HiSilicon | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213102 | Conclusion for Key Issue #2 |
pCR revision of S3-212713 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericssion | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213103 | Conclusion for Key Issue #3 |
pCR revision of S3-212714 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-213104 | addressing the EN in solution#12 |
pCR revision of S3-212721 |
Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213105 | conclusion to KI#2 |
pCR revision of S3-212603 |
Huawei, HiSilicon, CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213106 | conclusion to KI#5 to KI#8 |
pCR revision of S3-212604 |
Huawei, HiSilicon, ZTE Corporation, CATT, Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213107 | Resolve EN in Sol#27 |
pCR revision of S3-212608 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213108 | Resolve EN in Sol#28 |
pCR revision of S3-212609 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213109 | Add conclusion to Key Issue #1 |
pCR revision of S3-212611 |
Huawei, HiSilicon, ZTE Corporation, CATT, Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213110 | New solution to avoid policy mismatch |
pCR revision of S3-212619 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213111 | New solution on UE-to-network relay Key management based on primary authentication |
pCR revision of S3-212625 |
Huawei,HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213112 | Resolving the EN about the multiple EECs issues in solution 8 |
pCR revision of S3-212626 |
Huawei,HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-213113 | add evaluation for solution#3 |
pCR revision of S3-212630 |
Huawei, HiSilicon, China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213114 | draft TR 33.862 0.6.0 | draft TR | China Mobile Com. Corporation | FS_SEC_5GMSG | Rel-17 |
S3-104-e AI: 5.15 |
approved | [WTS] [JSN] | |
S3-213115 | TR 33.839for Edge computing security | draft TR | Huawei, HiSilicon | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-213116 | EN romoval for solution#23 |
pCR revision of S3-212638 |
Huawei, HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-213117 | EC : Conclusion for Key issue #7 |
pCR revision of S3-212645 |
Huawei, HiSilicon, Ericsson, ZTE | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-213118 | EC: Conclusion for Key issue #1 | pCR | Huawei, HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-213119 | EC: Conclusion for Key issue #2 | pCR | Huawei, HiSilicon | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-213120 | New Key issue on authorization mechanism negotiation |
pCR revision of S3-212651 |
Huawei, HiSilicon; China Mobile | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213121 | New solution for the authorization mechanism negotiation |
pCR revision of S3-212652 |
Huawei, HiSilicon; China Mobile | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213122 | Requirement of subscribe-notification key issue |
pCR revision of S3-212653 revised to S3-213166 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-213123 | Conclusion on authentication and authorization for multicast service |
pCR revision of S3-212656 |
Huawei, HiSilicon | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213124 | Conclusion on key issue #1.2 |
pCR revision of S3-212657 |
Huawei, HiSilicon, China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213125 | Conclusion on key issue #3.2 on protection of UE data in transit |
pCR revision of S3-212661 |
Huawei, HiSilicon, China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213126 | Evaluation Solution 9 |
pCR revision of S3-212750 |
Philips International B.V. | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213127 | Update Solution 11 for reduced key update overhead |
pCR revision of S3-212765 |
Philips International B.V. | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213128 | Reply LS on Layer-3 UE-to-Network Relay authentication and authorization |
LS out LS is reply to S3-212424 LS To: SA2 |
CATT | FS_5G_ProSe | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-213129 | Draft TR 33.847 v0.7.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-213130 | Conclusion to KI#3 (TPAE AA) |
pCR revision of S3-212579 |
Huawei, HiSilicon, InterDigital Europe Ltd., Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-213131 | [EDGE] Update to Solution#3 |
pCR revision of S3-212911 |
Samsung | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-213132 | Conclusion to KI#5 (privacy of UAS identities) |
pCR revision of S3-212580 |
Huawei, HiSilicon, InterDigital Europe Ltd., Qualcomm Incorporated | 33.854 0.6.0 | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-213133 | Update to KI#1 (NSSAI analysis) |
pCR revision of S3-212574 |
Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
approved | [WTS] [JSN] |
S3-213134 | New KI on DoS to NSAC procedure |
pCR revision of S3-212575 |
Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
approved | [WTS] [JSN] |
S3-213135 | [EDGE] Update to evaluation of Solution#3 |
pCR revision of S3-212912 |
Samsung | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-213136 | [MBS] Solution#13 Evaluation |
pCR revision of S3-212921 |
Samsung | 33.85 0.6.0 | FS_5MBS_SEC | Rel-17 |
S3-104-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-213137 | [ProSe] Updates to Solution#1 |
pCR revision of S3-212909 |
Samsung | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213138 | [ProSe] Updates to evaluation of solution#1 |
pCR revision of S3-212910 |
Samsung | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213139 | KI on Authorization for Inter-Slice Access |
pCR revision of S3-212916 |
Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213140 | New KI on AF authentication and authorization |
pCR revision of S3-212576 |
Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
approved | [WTS] [JSN] |
S3-213141 | Update on Solution 6 |
pCR revision of S3-212927 |
Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213142 | Evaluation for solution 1 |
pCR revision of S3-212929 |
Samsung,Nokia, Nokia Shanghai Bell | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213143 | Evaluation for solution 5 |
pCR revision of S3-212931 |
Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213144 | Solution on AF authorization |
pCR revision of S3-212588 |
Huawei, HiSilicon | 33.874 0.2.0 | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
approved | [WTS] [JSN] |
S3-213145 | draft TR 33.874-030 | draft TR | Huawei; HiSilicon | FS_eNS2_SEC | Rel-17 |
S3-104-e AI: 5.21 |
approved | [WTS] [JSN] | |
S3-213146 | Draft TR 33.867 | draft TR | Huawei; HiSilicon | FS_UC3S | Rel-17 |
S3-104-e AI: 5.14 |
approved | [WTS] [JSN] | |
S3-213147 | Update to solution #19 – Authorization added. |
pCR revision of S3-212770 |
Nokia, Nokia Shanghai Bell | 33.857 0.6.0 | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-213148 | Draft TR 33.854 |
draft TR revision of S3-212247 |
Qualcomm | FS_UAS_SEC | Rel-17 |
S3-104-e AI: 5.7 |
approved | [WTS] [JSN] | |
S3-213149 | LS on 256-bit algorithms based on ZUC-256 |
LS out LS To: ETSI SAGE |
CAICT |
S3-104-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-213150 | Reply to LS on broadcast of NTN GW or gNB position |
LS out LS is reply to S3-212431 LS To: RAN1 |
Ericsson Hungary Ltd |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-213151 | Update_on_Key_issue#1.4 | pCR | Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
withdrawn | [WTS] [JSN] |
S3-213152 | Update_on_Key_issue#1.4 |
pCR revision of S3-213015 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213153 | Update_on_Solution#12 |
pCR revision of S3-213017 |
Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213154 | Update_on_Solution#5 |
pCR revision of S3-213016 |
Ericsson, Lenovo, Motorola Mobility | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213155 | Cleanup MUSIM TR | CR | Intel Corporation (UK) Ltd | 33.873 17.0.0 CR#1 catF | FS_MUSIM_SEC | Rel-17 |
S3-104-e AI: 5.19 |
agreed | [WTS] [JSN] |
S3-213156 | Key issue on security aspects of Paging Cause | CR | Intel Corporation (UK) Ltd | 33.873 17.0.0 CR#2 catB | FS_MUSIM_SEC | Rel-17 |
S3-104-e AI: 5.19 |
agreed | [WTS] [JSN] |
S3-213157 | conclusion to KI#5 to KI#8 | pCR | Huawei, HiSilicon, ZTE Corporation, CATT, Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-213158 | ProSe: Addional Evaluation for Solution #10 |
pCR revision of S3-212954 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213159 | ProSe: Addional Evaluation for Solution #15 |
pCR revision of S3-212956 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213160 | ProSe: Addional Evaluation for Solution #18 |
pCR revision of S3-212957 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213161 | ProSe: Add Evaluation for Solution #27 |
pCR revision of S3-212959 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213162 | ProSe: Add Evaluation for Solution #28 |
pCR revision of S3-212960 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213163 | ProSe: Conclusion for Key Issue #16 |
pCR revision of S3-212964 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213164 | ProSe: New Solution for Key Issue #17 |
pCR revision of S3-212965 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213165 | ProSe: New Solution for Key Issue #3 |
pCR revision of S3-212967 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213166 | Requirement of subscribe-notification key issue |
pCR revision of S3-213122 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | 33.875 0.3.0 | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-213167 | Draft TR 33.875 | draft TR | Nokia Germany | FS_eSBA_SEC | Rel-17 |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] | |
S3-213168 | LS Reply to SA3 on security protection on RRCResumeRequest message | LS in | R2-2109121 |
S3-104-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-213169 | Reply LS on Storage of KAUSF |
LS in LS reply in S3-213172 |
C1-214800 |
S3-104-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-213170 | LS on Home Network triggered re-authentication |
LS out LS To: CT4 |
Samsung R&D Institute UK |
S3-104-e AI: 4.28 |
approved | [WTS] [JSN] | |||
S3-213171 | LS on use of 4G algorithm identifier in NR-PDCP for UP IP |
LS out LS To: RAN2 |
Huawei Technologies Sweden AB |
S3-104-e AI: 4.13 |
noted | [WTS] [JSN] | |||
S3-213172 | Reply LS on Storage of KAUSF |
LS out LS is reply to S3-213169 LS To: CT1 |
Samsung R&D Institute UK |
S3-104-e AI: 4.28 |
approved | [WTS] [JSN] | |||
S3-213173 | Conclusion on Key issue #3.2 SUPI guessing attacks |
pCR revision of S3-212511 |
Nokia, Nokia Shanghai Bell, Thales, NTT DOCOMO, NEC | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-213174 | LS on proposed NSWO architecture |
LS out LS To: SA2 revision of S3-212513 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 5.22 |
approved | [WTS] [JSN] | ||
S3-213175 | New solution: Keying procedures for Group Member and Relay discovery: public safety case |
pCR revision of S3-212464 |
MITRE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213176 | Update to KI #17 |
pCR revision of S3-212465 |
MITRE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213177 | OAuth2.0 misalignmnet |
CR revision of S3-212450 |
Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | 33.501 16.7.0 CR#11451 catA | 5GS_Ph1-SEC | Rel-16 |
S3-104-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-213178 | OAuth2.0 misalignmnet |
CR revision of S3-212451 |
Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | 33.501 15.13.0 CR#11461 catF | 5GS_Ph1-SEC | Rel-15 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213179 | [33.180] R17 Group subscription |
CR revision of S3-212467 |
Motorola Solutions Danmark A/S | 33.18 17.3.0 CR#1731 catF | MCXSec2 | Rel-17 |
S3-104-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-213180 | Mirror for Rel-16 Editorial Clarifications for Trusted non-3GPP Access using TNGF | CR | Intel Corporation (UK) Ltd | 33.501 16.7.1 CR#1201 catF | TEI16 | Rel-16 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213181 | Way forward for U2N Relay authentication and authorization | discussion | CATT | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] | ||
S3-213182 | New KI on Secrets in Container Images |
pCR revision of S3-212973 |
Altiostar | 33.848 0.8.0 | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-213183 | SCAS_5G_IPUPS: New threats to IPUPS to TR 33.926 | CR | ZTE Corporation | 33.926 17.1.0 CR#47 catB | SCAS_5G_IPUPS | Rel-17 |
S3-104-e AI: 4.7 |
withdrawn | [WTS] [JSN] |
S3-213184 | SCAS_5G_IPUPS: New test cases of IPUPS to TS 33.513 | CR | ZTE Corporation | 33.513 16.2.0 CR#4 catB | SCAS_5G_IPUPS | Rel-17 |
S3-104-e AI: 4.7 |
withdrawn | [WTS] [JSN] |
S3-213185 | LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT |
LS out LS is reply to S3-212444 source LS: S6-211496 LS To: 3GPP TSG SA WG6, 3GPP TSG SA WG1 revision of S3-212681 |
Nokia, Nokia Shanghai Bell | Rel-18 |
S3-104-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-213186 | Correction of message name in SMF |
CR revision of S3-212459 |
Keysight Technologies UK Ltd | 33.515 16.3.0 CR#81 catF | SCAS_5G | Rel-16 |
S3-104-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-213187 | eCryptPr 02 CR 33.203 R17 Security updates for algorithms and protocols | draftCR | Ericsson | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
withdrawn | [WTS] [JSN] | |
S3-213188 | New KI on Container breakouts |
pCR revision of S3-212975 revised to S3-213190 |
Altiostar | 33.848 0.8.0 | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-213189 | OAuth misalignment - R17 |
CR revision of S3-212897 |
Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility, Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung | 33.501 17.2.1 CR#11911 catA | 5GS_Ph1-SEC | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213190 | New KI on Container breakouts |
pCR revision of S3-213188 |
Altiostar | 33.848 0.8.0 | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-213191 | Clarification on Kausf storage in multi-NAS connection |
CR revision of S3-212598 revised to S3-213195 |
Huawei, HiSilicon | 33.501 17.2.1 CR#11591 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] |
S3-213192 | Reply LS on Misalignment on usage of OAuth within 3GPP 29.510 |
LS out LS is reply to S3-212410 source LS: 5GIS Doc 17_04 LS To: GSMA FASG RIFS 5GIS revision of S3-212876 |
Nokia, Nokia Shanghai Bell |
S3-104-e AI: 5.2 |
approved | [WTS] [JSN] | |||
S3-213193 | Reply LS on OAuth2 misalignments between SA3 and CT4 specifications |
LS out LS is reply to S3-212409 source LS: CP-211326 LS To: CT, CT4 |
Nokia, Nokia Shanghai Bell |
S3-104-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-213194 | Clarification on Kausf storage in multi-NAS connection |
CR revision of S3-212599 |
Huawei, HiSilicon | 33.501 16.7.1 CR#11601 catF | TEI16 | Rel-16 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213195 | Clarification on Kausf storage in multi-NAS connection |
CR revision of S3-213191 |
Huawei, HiSilicon | 33.501 17.2.1 CR#11592 catA | TEI16 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213196 | NRF service definition R15 |
CR revision of S3-212891 |
Nokia, Nokia Shanghai Bell | 33.501 15.13.0 CR#11851 catF | TEI15 | Rel-15 |
S3-104-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-213197 | NRF service definition R16 |
CR revision of S3-212892 |
Nokia, Nokia Shanghai Bell | 33.501 16.7.1 CR#11861 catA | TEI15 | Rel-16 |
S3-104-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-213198 | Alignment for Oauth2.0 validation R15 |
CR revision of S3-212898 |
Nokia, Nokia Shanghai Bell | 33.501 15.13.0 CR#11921 catF | 5G_eSBA | Rel-15 |
S3-104-e AI: 4.22 |
withdrawn | [WTS] [JSN] |
S3-213199 | NRF service definition R17 |
CR revision of S3-212893 |
Nokia, Nokia Shanghai Bell | 33.501 17.2.1 CR#11871 catA | TEI15 | Rel-17 |
S3-104-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-213200 | Clarification on AMF transparency for UPU |
CR revision of S3-212739 |
Ericsson | 33.501 17.2.1 CR#11741 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213201 | Change request to living document: Key hierarchy |
other revision of S3-212735 |
Ericsson | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
approved | [WTS] [JSN] | |
S3-213202 | Draft TR 33.848 | draft TR | BT plc | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
approved | [WTS] [JSN] | |
S3-213203 | Change request to living document: EAP flow |
other revision of S3-212734 |
Ericsson | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
approved | [WTS] [JSN] | |
S3-213204 | Security aspects of eNPN (skeleton for living document) |
draftCR revision of S3-212752 revised to S3-213206 |
Ericsson | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
revised | [WTS] [JSN] | |
S3-213205 | Change request to living document: Credentials holder using AUSF and UDM for primary authentication |
other revision of S3-212753 |
Ericsson |
S3-104-e AI: 4.17 |
approved | [WTS] [JSN] | |||
S3-213206 | Security aspects of eNPN (living document) |
draftCR revision of S3-213204 |
Ericsson, Huawei, HiSilicon | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
approved | [WTS] [JSN] | |
S3-213207 | Living document for BEST_5G: draftCR to TS 33.163 |
draftCR revision of S3-212458 |
KPN N.V. | BEST_5G | Rel-17 |
S3-104-e AI: 4.11 |
approved | [WTS] [JSN] | |
S3-213208 | draft TR 33.857 v0.7.0 | draft TR | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-104-e AI: 5.12 |
approved | [WTS] [JSN] | |
S3-213209 | Reply LS to GSMA on prevention of attacks on sliced core network |
LS out LS is reply to S3-212420 source LS: S3-212420 LS To: GSMA revision of S3-212463 |
CableLabs, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell | Rel-16 |
S3-104-e AI: 4.25 |
approved | [WTS] [JSN] | ||
S3-213210 | Short-lived public key-based solution for KI#2 |
pCR revision of S3-212523 |
CableLabs,Deutsche Telekom AG, InterDigital, Johns Hopkins University APL, US National Security Agency | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-213211 | pCR to 33.839: solution #26 |
pCR revision of S3-213008 |
THALES | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-213212 | pCR to 33.839: solution #27 |
pCR revision of S3-213009 |
THALES | 33.839 0.6.0 | FS_eEDGE_Sec | Rel-17 |
S3-104-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-213213 | SCAS_5G_IPUPS: New threats to IPUPS to TR 33.926 | CR | ZTE Corporation | 33.926 17.1.0 CR#48 catB | SCAS_5G_IPUPS | Rel-17 |
S3-104-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-213214 | SCAS_5G_IPUPS: New test cases of IPUPS to TS 33.513 | CR | ZTE Corporation | 33.513 16.2.0 CR#5 catB | SCAS_5G_IPUPS | Rel-17 |
S3-104-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-213215 | LS on SBA for GBA |
LS out LS To: SA2 revision of S3-212504 |
Ericsson | Rel-17 |
S3-104-e AI: 4.1 |
approved | [WTS] [JSN] | ||
S3-213216 | New solution proposal |
pCR revision of S3-212408 |
JSRPC Kryptonite | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-213217 | New solution: Hardware Mediated Execution Enclave (HMEE) |
pCR revision of S3-212466 |
MITRE Corporation | 33.848 0.8.0 | FS_SIV | Rel-16 |
S3-104-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-213218 | Reply LS for clarification on managing expired or multiple Protection Scheme and Home Network keys used for SUCI calculation. |
LS out LS is reply to S3-212429 LS To: CT6 revision of S3-212723 |
NTT DOCOMO INC. | Rel-17 |
S3-104-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-213219 | Overview on UAV authentication and authorization (UUAA) |
pCR revision of S3-212582 |
Huawei, HiSilicon, Qualcomm, InterDigital, Lenovo, Motorola Mobility | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-213220 | UAV location information verification |
pCR revision of S3-212618 |
Huawei, HiSilicon, Qualcomm Incorporated, InterDigitalal | 33.256 0.0.0 | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-213221 | UP Security Activation Mechanism in LTE |
draftCR revision of S3-212694 |
Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-213222 | Clarification on UP IP indication based on RAN3 LS | draftCR | Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
withdrawn | [WTS] [JSN] | |
S3-213223 | New WID for UC3S |
WID new revision of S3-212705 |
Huawei, HiSilicon, China Mobile, China Unicom, China Telecom, Nokia, Nokia Shanghai Bell, FutureWei | Rel-17 |
S3-104-e AI: 4.27 |
agreed | [WTS] [JSN] | ||
S3-213224 | Update to clause 7.02 |
pCR revision of S3-212722 |
Huawei, HiSilicon | 33.846 0.12.0 | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-213225 | TS 33.558: Security requirements |
pCR revision of S3-212648 |
Huawei, HiSilicon | 33.558 0.0.0 | eEDGE_5GC | Rel-17 |
S3-104-e AI: 4.18 |
approved | [WTS] [JSN] |
S3-213226 | TS 33.558: Security for the EDGE interfaces |
pCR revision of S3-212649 |
Huawei, HiSilicon | 33.558 0.0.0 | eEDGE_5GC | Rel-17 |
S3-104-e AI: 4.18 |
approved | [WTS] [JSN] |
S3-213227 | draft TS 33.558: Edge computing security | draft TS | Huawei, HiSilicon | eEDGE_5GC | Rel-17 |
S3-104-e AI: 4.18 |
approved | [WTS] [JSN] | |
S3-213228 | Adding for NSSAAF network product class description and assets and critical assets |
draftCR revision of S3-212666 |
Huawei, HiSilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
approved | [WTS] [JSN] | |
S3-213229 | New threat related to unauthorized slice-specific authorization revocatoinsue #1.2 |
draftCR revision of S3-212667 |
Huawei, HiSilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
approved | [WTS] [JSN] | |
S3-213230 | New service on 5G GBA AV |
draftCR revision of S3-212669 revised to S3-213234 |
Huawei, HiSilicon, Ericsson, Thales | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-213231 | Clarification on UP IP indication based on RAN3 LS |
draftCR revision of S3-213031 |
Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-213232 | New WID on security aspects of eNA |
WID new revision of S3-212810 |
China Mobile | Rel-17 |
S3-104-e AI: 4.27 |
agreed | [WTS] [JSN] | ||
S3-213233 | Draft TR 33.846 v0.13.0 Study on authentication enhancements in the 5G System (5GS) | draft TR | Ericsson Hungary Ltd | FS_AUTH_ENH | Rel-17 |
S3-104-e AI: 5.5 |
approved | [WTS] [JSN] | |
S3-213234 | New service on 5G GBA AV |
other revision of S3-213230 |
Huawei, HiSilicon, Ericsson, Thales | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-213235 | roaming-related security mechanisms |
other revision of S3-212637 |
Huawei, HiSilicon | eNPN | Rel-17 |
S3-104-e AI: 4.17 |
approved | [WTS] [JSN] | |
S3-213236 | New WID on Security Aspects of Proximity based Services (ProSe) in the 5G |
WID new revision of S3-212727 |
CATT | Rel-17 |
S3-104-e AI: 4.27 |
agreed | [WTS] [JSN] | ||
S3-213237 | Editorial Clarifications for Trusted non-3GPP Access using TNGF |
CR revision of S3-212683 |
Intel Corporation (UK) Ltd | 33.501 17.2.1 CR#11701 catA | TEI16 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213238 | 5GFBS-Update of solution#17 |
pCR revision of S3-212780 |
Apple, CableLabs, Intel | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-213239 | CR on TS 33.501 on the security context handling in IRAT |
CR revision of S3-212796 |
Apple | 33.501 17.2.1 CR#11821 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213240 | FBS - Clarification quantum-resistance |
pCR revision of S3-212744 |
Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-213241 | Clarification in Solution 4 |
pCR revision of S3-212743 |
Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-213242 | FBS - Evaluation Solution 23 |
pCR revision of S3-212746 |
Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-213243 | FBS - Evaluation Solution 24 |
pCR revision of S3-212747 |
Philips International B.V. | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-213244 | TR 33.809-5GFBS | draft TR | Apple Computer Trading Co. Ltd | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-213245 | Living document for GBA_5G: draftCR to TS 33.220: SBA support for Zh and Zn interfaces |
draftCR revision of S3-212500 |
Ericsson | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-213246 | Living document for GBA_5G: draftCR to TS 33.223: SBA support for Zpn |
draftCR revision of S3-212501 |
Ericsson | GBA_5G | Rel-17 |
S3-104-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-213247 | Draft TS 33.326 | draft TS | Huawei, HiSilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
approved | [WTS] [JSN] | |
S3-213248 | Coversheet for TS 33.326 | TS or TR cover | Huawei, Hisilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
approved | [WTS] [JSN] | |
S3-213249 | A new testcase to NSSAAF SCAS |
pCR revision of S3-212595 |
Huawei, HiSilicon | 33.326 0.2.0 | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
approved | [WTS] [JSN] |
S3-213250 | Clarification on AS key generation after runing NAS SMC |
CR revision of S3-212597 |
Huawei, HiSilicon | 33.501 17.2.1 CR#11581 catF | TEI17 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213251 | CR to 33.926 threat analysis on select AAA-P and AAA-S |
CR revision of S3-212602 |
Huawei, HiSilicon | 33.926 17.1.0 CR#461 catF | SCAS_5G_NSSAAF | Rel-17 |
S3-104-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-213252 | Clarification on AAnF selection |
CR revision of S3-212600 |
Huawei, HiSilicon | 33.535 17.2.1 CR#931 catF | AKMA | Rel-17 |
S3-104-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-213253 | User Plane Integrity Protection Policy Handling in EN-DC |
draftCR revision of S3-212771 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-213254 | User Plane Integrity Protection Policy Handling in IW handover from 5GS to EPS |
draftCR revision of S3-212772 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-213255 | User Plane Integrity Protection Policy Handling in DC |
draftCR revision of S3-212773 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-213256 | User Plane Integrity Protection Policy Handling in IW handover from EPS to 5GS |
draftCR revision of S3-212774 |
Ericsson | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-213257 | Clarification on Data Masking on Integration Analysis |
CR revision of S3-212821 |
China Mobile | 33.521 17.0.0 CR#21 catF | SCAS_5G_NWDAF | Rel-17 |
S3-104-e AI: 4.5 |
agreed | [WTS] [JSN] |
S3-213258 | LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS out LS is reply to S3-212436 LS To: RAN3 revision of S3-212848 revised to S3-213272 |
Qualcomm Incorporated |
S3-104-e AI: 4.28 |
revised | [WTS] [JSN] | |||
S3-213259 | Updates to solution #17 capability negotiation |
pCR revision of S3-212677 |
Intel Corporation (UK) Ltd | 33.809 0.15.0 | FS_5GFBS | Rel-17 |
S3-104-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-213260 | Draft TS 33.256 | draft TS | Qualcomm CDMA Technologies | ID_UAS | Rel-17 |
S3-104-e AI: 4.2 |
approved | [WTS] [JSN] | |
S3-213261 | Rel16 Align KAUSF handling for 5G AKA and EAP-AKA' |
CR revision of S3-212506 |
Ericsson | 33.501 16.7.1 CR#11491 catF | TEI16 | Rel-16 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213262 | Rel17 Align KAUSF handling for 5G AKA and EAP-AKA' for Release 17 |
CR revision of S3-212507 |
Ericsson | 33.501 17.2.1 CR#11501 catA | TEI16 | Rel-17 |
S3-104-e AI: 4.28 |
agreed | [WTS] [JSN] |
S3-213263 | pCR to Living doc on addition of 5G to BEST - addition of EMSDP updates |
other revision of S3-212684 |
VODAFONE Group Plc | BEST_5G |
S3-104-e AI: 4.11 |
approved | [WTS] [JSN] | ||
S3-213264 | Security updates for algorithms and protocols for 33.310 |
draftCR revision of S3-213022 |
Ericsson | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-213265 | Security updates for algorithms and protocols for 33.210 |
draftCR revision of S3-213023 |
Ericsson | eCryptPr | Rel-17 |
S3-104-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-213266 | Living CR for UPIP for LTE |
draftCR revision of S3-212730 |
Vodafone | UPIP_SEC_LTE | Rel-17 |
S3-104-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-213267 | Response LS on 256-bit algorithms based on SNOW 3G or SNOW V |
LS out LS is reply to S3-212425 LS To: ETSI SAGE revision of S3-212686 |
VODAFONE Group Plc | FS_256_Algo | Rel-18 |
S3-104-e AI: 3 |
approved | [WTS] [JSN] | |
S3-213268 | Add step 4 in annex B.1.2.2 |
CR revision of S3-212535 |
ZTE Corporation | 33.535 17.2.1 CR#901 catF | AKMA_TLS | Rel-17 |
S3-104-e AI: 4.19 |
agreed | [WTS] [JSN] |
S3-213269 | Draft_skeleton_for_draft_CR_eNA_SEC |
other revision of S3-212811 |
China Mobile | Rel-17 |
S3-104-e AI: 4.27 |
approved | [WTS] [JSN] | ||
S3-213270 | Living document for 5BMS | draftCR | Huawei | 5MBS | Rel-17 |
S3-104-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-213271 | Reply-LS on security aspects for the method of collection of data from the UE |
LS out LS is reply to S3-212427 LS To: SA WG2 revision of S3-212679 |
Guangdong OPPO Mobile Telecom. | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] | ||
S3-213272 | LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS out LS is reply to S3-212436 LS To: RAN3 revision of S3-213258 |
Qualcomm Incorporated |
S3-104-e AI: 4.28 |
approved | [WTS] [JSN] |
873 documents (1.0824460983276 seconds)