Tdoc List
2021-12-01 12:16
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Agenda and Meeting Objectives | S3‑213800 | Agenda | SA WG3 Chair | agenda | Yes |
Yes
| approved | No | |||
S3‑213803 | Process for SA3#105e meeting | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
S3‑213883 | SA3 Procedures and deadlines | SA3 Chair | agenda | Information | Yes |
Yes
| noted | No | ||||
2 | Meeting Reports | S3‑213801 | Report from SA3#104e | MCC | report | Yes |
Yes
| approved | No | |||
S3‑213802 | Report from SA3#104e-Adhoc | MCC | report | Yes |
Yes
| approved | No | |||||
S3‑213804 | Report from last SA | SA WG3 Chair | report | Yes |
Yes
| noted | No | |||||
S3‑213805 | Meeting notes from SA3 leadership | SA WG3 Chair | report | Yes |
Yes
| noted | No | |||||
3 | Reports and Liaisons from other Groups | S3‑213846 | TCG progress - report from TCG rapporteur | InterDigital, Inc. | other | Information | Yes |
Yes
| noted | No | ||
S3‑213806 | LS to 3GPP SA3 working group on 5GS Roaming Hubbing | 5GJA | LS in | Yes |
Yes
| replied to | No | |||||
S3‑214293 | DP of LS from GSMA about roaming hub support | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑213809 | LS on new parameters for SOR | C1-214118 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑214326 | CR to 33.501 to protect additional SoR information (CPSOR-CMCI) | NTT DOCOMO INC. | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214327 | draft-Reply LS on new parameters for SOR | NTT DOCOMO INC. | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑213810 | Reply LS on NAS-based busy indication | C1-214917 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213824 | Reply LS on NAS-based busy indication | R2-2108855 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213811 | LS on user plane integrity protection for UE not supporting NR as primary RAT and supporting E-UTRA | C1-214952 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213876 | Reply LS on user plane integrity protection for UE not supporting NR as primary RAT and supporting E-UTRA | S2-2107794 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213813 | Reply LS on Header Enrichment for HTTPS in PFCP | C4-214531 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑213931 | Reply LS on Header Enrichment for HTTPS in PFCP | ZTE Corporation | LS out | Approval | Yes |
Yes
| merged | No | S3‑214505 | |||
S3‑214075 | Reply LS on Header Enrichment for HTTPS in PFCP | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑214505 | |||
S3‑213814 | LS on Using N32 for interconnect scenarios | C4-214533 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑214333 | Reply LS from 5GJA to 3GPP CT4, SA2 and SA3 on Using N32 for Interconnect Scenarios | GSMA | LS in | Discussion | Yes |
Yes
| noted | No | ||||
S3‑213817 | Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S3‑213818 | LS on broadcast of NTN GW or gNB position | R1-2106332 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑213819 | Reply LS on broadcast of NTN GW or gNB position | S1-213211 | LS in | Yes |
Yes
| noted | No | |||||
S3‑214082 | Reply to LS on broadcast of NTN GW or gNB position | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| merged | No | S3‑214336 | |||
S3‑214260 | Reply to LS on broadcast of NTN GW or gNB position | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S3‑214336 | |||
S3‑214166 | Reply LS (S3-213818) on broadcast of NTN GW or gNB position | Xiaomi Technology | LS out | Approval | Yes |
Yes
| merged | No | S3‑214336 | |||
S3‑213820 | New LS on UE location aspects in NTN | R2-2106543 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑213821 | Reply LS on UE location aspects in NTN | R2-2109216 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213822 | Reply LS on UE location aspects in NTN | R2-2109217 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑213968 | [Draft] Reply LS on UE location aspects in NTN | Intel Sweden AB | LS out | Yes |
Yes
| merged | No | S3‑214394 | ||||
S3‑213985 | Reply LS on UE location aspects in NTN (R2-2106543) | Apple | LS out | Yes |
Yes
| merged | No | S3‑214394 | ||||
S3‑214103 | Reply LS on UE location aspects in NTN | CATT | LS out | Approval | Yes |
Yes
| revised | No | S3‑214360 | |||
S3‑214154 | Reply LS on UE location aspects in NTN | Qualcomm Incorporated | LS out | Approval | Yes |
Yes
| merged | No | S3‑214394 | |||
S3‑214167 | Reply LS (S3-213820) on UE location aspects in NTN | Xiaomi Technology | LS out | Approval | Yes |
Yes
| merged | No | S3‑214394 | |||
S3‑214168 | Reply LS (S3-213822) on UE location aspects in NTN | Xiaomi Technology | LS out | Approval | Yes |
Yes
| revised | No | S3‑214394 | |||
S3‑213823 | LS on NTN specific user consent | R2-2109199 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑214155 | Reply LS on NTN specific User Consent | Qualcomm Incorporated | LS out | Approval | Yes |
Yes
| revised | No | S3‑214349 | |||
S3‑214169 | Reply LS (S3-213823) on NTN specific user consent | Xiaomi Technology | LS out | Approval | Yes |
Yes
| merged | No | S3‑214349 | |||
S3‑213986 | Reply LS on NTN specific user consent (R2-2109199) | Apple | LS out | Yes |
Yes
| merged | No | S3‑214349 | ||||
S3‑213827 | LS on UP security policy updated by intra-cell handover | R3-214464 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213828 | LS to SA3 on support of Pre-shared key derivation for IAB-donor-CU-UP | R3-214465 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑214008 | Reply LS on support of Pre-shared key derivation for IAB-donor-CU-UP | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| approved | No | ||||
S3‑214228 | [Rel-16]Clarification on KIAB generation for CP-UP separation | Samsung, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214229 | [Rel-17]Clarification on KIAB generation for CP-UP separation | Samsung, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑213830 | LS on 5G capabilities exposure for factories of the future | S2-2106683 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213831 | Reply LS to 5G-ACIA on 5G capabilities exposure for factories of the future | SP-211134 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213837 | LS Reply on QoE report handling at QoE pause | S4-211290 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213838 | LS on progress of study items for security on management aspect | S5-214467 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213839 | Reply LS on QoE report handling at QoE pause | S5-214519 | LS in | Yes |
Yes
| noted | No | |||||
S3‑214099 | Evaluation of the potential security issue in QoE report handling at QoE pause | Lenovo, Motorola Mobility | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑214101 | [DRAFT] Reply LS on QoE report handling at QoE pause | Lenovo, Motorola Mobility | LS out | Approval | Yes |
Yes
| revised | No | S3‑214458 | |||
S3‑213841 | Reply LS on RAT type for network monitoring | S6-212146 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213844 | LS on new liaison officer from ITU-T SG17 | ITU-T SG17 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213845 | Reply LS on Inclusive language review | SP-211140 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213850 | LS-Reply on Home Network triggered re-authentication | C4-215437 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑214231 | Discussion paper on need for Re-authentication | Samsung, NEC | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑214232 | CR to 33.501: Network initiated Primary Authentication | Samsung, NEC | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214233 | CR to 33.535: Refresh of KAKMA and KAF | Samsung, NEC | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213874 | LS on MINT functionality for Disaster Roaming | S2-2108172 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑213992 | Discussion on SA2 LS on MINT | LG Electronics Inc. | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑213975 | Reply LS on LS on MINT functionality for Disaster Roaming | LG Electronics | LS out | Approval | Yes |
Yes
| revised | No | S3‑214342 | |||
S3‑213877 | LS to 3GPP SA3 working group on NRF mutual authentication in roaming scenario | GSMA | LS in | Yes |
Yes
| replied to | No | |||||
S3‑213885 | LS on question and feedback about the EVEX Work Item | C3-215316 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213840 | LS on new SID on Application Enablement for Data Integrity Verification Service in IOT | S6-211496 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑213887 | LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S3‑214337 | |||
S3‑213965 | Discussion on Data Integrity Service in IoT | China Unicom | discussion | Information | Yes |
Yes
| noted | No | ||||
S3‑213966 | Reply LS to SA6 on new SID on Application Enablement for Data Integrity Verification Service in IoT | China Unicom | LS out | Approval | Yes |
Yes
| merged | No | S3‑214337 | |||
S3‑214097 | Discussions on ZUC-256 | CATT | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑214100 | LS on ZUC-256 | CATT | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑213843 | LS on information about draft Recommendation ITU-T Y.frd: "Framework and Requirements of Network-oriented Data Integrity Verification Service based on Blockchain in Future Network” | ITU-T SG13 | LS in | No |
Yes
| withdrawn | Yes | |||||
S3‑214336 | Reply to LS on broadcast of NTN GW or gNB position | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S3‑214260 | |||
S3‑214337 | LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | S3‑213887 | |||
S3‑214342 | Reply LS on LS on MINT functionality for Disaster Roaming | LG Electronics | LS out | Approval | Yes |
Yes
| approved | No | S3‑213975 | |||
S3‑214349 | Reply LS on NTN specific User Consent | Qualcomm Incorporated | LS out | Approval | Yes |
Yes
| approved | No | S3‑214155 | |||
S3‑214360 | Reply LS on UE location aspects in NTN | CATT | LS out | Approval | Yes |
Yes
| approved | No | S3‑214103 | |||
S3‑214394 | Reply LS (S3-213822) on UE location aspects in NTN | Xiaomi Technology | LS out | Approval | Yes |
Yes
| approved | No | S3‑214168 | |||
S3‑214416 | Follow up LS on MINT functionality for Disaster Roaming | LG Electronics Inc. | LS out | Approval | Yes |
Yes
| approved | No | ||||
S3‑214425 | Reply LS to GSMA on NRF mutual authentication in roaming scenario | Nokia | LS out | Approval | Yes |
Yes
| approved | No | ||||
S3‑214427 | Reply-LS on Using N32 for interconnect scenarios | Nokia | LS out | Yes |
Yes
| approved | No | |||||
S3‑214456 | Reply LS on 5GS roaming hubbing | NTT DOCOMO INC. | LS out | Approval | Yes |
Yes
| approved | No | ||||
S3‑214458 | LS on QoE report handling at QoE pause | Lenovo, Motorola Mobility | LS out | Approval | Yes |
Yes
| approved | No | S3‑214101 | |||
S3‑214505 | Reply LS on Header Enrichment for HTTPS in PFCP | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| approved | No | S3‑214075 | |||
4 | Work areas |   | ||||||||||
4.1 | Integration of GBA into 5GC (Rel-17) | S3‑214250 | Living document for GBA_5G: draftCR to TS 33.220: SBA support for Zh and Zn interfaces | Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S3‑214449 | |
S3‑214251 | Living document for GBA_5G: draftCR to TS 33.223: SBA support for Zpn | Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S3‑214450 | |||
S3‑213867 | Reply LS to LS on SBA for GBA | S2-2107793 | LS in | Yes |
Yes
| noted | No | |||||
S3‑214252 | pCR to living document of TS 33.220: Update of the interface names and removal of Editor's Notes | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214253 | pCR to living document of TS 33.223: Update of the interface names and removal of Editor's Notes | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214254 | pCR to living document of TS 33.220: Editorial changes | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214255 | pCR to living document of TS 33.223: Editorial changes | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑213932 | TS 33.220 Resolution of editor's note on 5G GBA roaming | ZTE Corporation | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑213933 | TS 33.223 Resolution of editor's note on 5G GBA roaming | ZTE Corporation | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214257 | Discussion about GBA roaming in 5G | Ericsson | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S3‑214258 | pCR to living document of TS 33.220: Roaming | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214259 | pCR to living document of TS 33.223: Roaming | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214053 | Authorizating the use of GBA service | Huawei, HiSilicon | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214256 | pCR to living document of TS 33.220: Update of the new UDM service to a service operation | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214449 | Living document for GBA_5G: draftCR to TS 33.220: SBA support for Zh and Zn interfaces | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | S3‑214250 | |||
S3‑214450 | Living document for GBA_5G: draftCR to TS 33.223: SBA support for Zpn | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | S3‑214251 | |||
S3‑214519 | SBA support for the Zh and Zn interfaces | Ericsson, Huawei, HiSilicon, Thales | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214520 | SBA support for the Zpn interface | Ericsson, Huawei, HiSilicon, Thales | CR | Agreement | Yes |
Yes
| agreed | No | ||||
4.2 | Security Assurance Specification for IMS (Rel-17) | S3‑214072 | Add the threat references in the TS 33.226 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | ||
4.3 | Security Assurance Specification Enhancements for 5G (Rel-17) | S3‑213842 | LS re Penetration Testing of SCAS | GSMA SECAG | LS in | Yes |
Yes
| noted | No | |||
S3‑213875 | 33.512 – Alignment with TS 33.501 Rel-17 | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| revised | No | S3‑214417 | |||
S3‑213878 | AMF – NAS NULL integrity protection clarifications | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑214026 | Correction of testcases in TS 33.511 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214481 | |||
S3‑214135 | Discussion on adding SCAS for the various split gNB cases | Qualcomm Incorporated, Deutsche Telekom AG, AT&T | discussion | Discussion | Yes |
Yes
| noted | No | S3‑212838 | |||
S3‑214136 | Adding SCAS for the various split gNB cases | Qualcomm Incorporated, Deutsche Telekom AG, AT&T | CR | Agreement | Yes |
Yes
| not pursued | No | S3‑212839 | |||
S3‑214210 | SCAS SECOP update to Annex SCP in 33.926 | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S3‑214486 | |||
S3‑214417 | 33.512 – Alignment with TS 33.501 Rel-17 | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | S3‑213875 | |||
S3‑214469 | Minimum set of functions for SCP | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| agreed | No | |||||
S3‑214481 | Update testcases to clause 4.2.2.1.18 and 4.2.2.1.19 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑214026 | |||
S3‑214486 | SCAS SECOP update to Annex SCP in 33.926 | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S3‑214210 | |||
4.4 | Security Assurance Specification for Service Communication Proxy (SECOP) (Rel-17) | S3‑214078 | Living CR on SCP to 33.926 | Nokia, Nokia Shanghai Bell | draftCR | Yes |
Yes
| approved | No | S3‑212293 | ||
S3‑214200 | Cover sheet - SCAS SECOP - Presentation and Approval of TR 33.522 | Nokia, Nokia Shanghai Bell | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S3‑214204 | 01 SCAS SECOP editorials to 33522-030 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑214526 | |||
S3‑214205 | 02 SCAS SECOP Technical baseline | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑214527 | |||
S3‑214206 | SCAS SECOP Operating Systems | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214207 | SCAS SECOP Web Servers | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214208 | SCAS SECOP Network Devices | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214209 | SCAS SECOP Vulnerability testing | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214467 | New Annex with Assets and Threats specific to SCAS SCP | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| agreed | No | |||||
S3‑214468 | 33.522 - 5G Security Assurance Specification (SCAS); Service Communication Proxy (SECOP) | Nokia, Nokia Shanghai Bell | draft TS | Yes |
Yes
| approved | No | |||||
S3‑214526 | SCAS SECOP editorials to 33522-030 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑214204 | |||
S3‑214527 | SCAS SECOP Technical baseline | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑214205 | |||
S3‑214528 | SCAS SECOP Operating Systems | Nokia, Nokia Shanghai Bell | other | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑214529 | SCAS SECOP Web Servers | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
4.5 | Security Assurance Specification for 5G NWDAF (Rel-17) |   | ||||||||||
4.6 | Security Assurance Specification for Non-3GPP InterWorking Function (N3IWF) (Rel- 17) | S3‑214111 | Presentation of Specification to TSG: TS 33.520, Version <0.3.0> for approval | China Unicom, Huawei, Hisilicon | pCR | Yes |
Yes
| approved | No | |||
S3‑214114 | Editorial change on TS 33.520 | China Unicom, Huawei, Hisilicon | pCR | Yes |
Yes
| approved | No | |||||
S3‑214537 | Draft TS 33.520 | China Unicom | draft TS | Approval | Yes |
Yes
| approved | No | ||||
4.7 | Security Assurance Specification for Inter PLMN UP Security (Rel-17) |   | ||||||||||
4.8 | eSCAS_5G for Network Slice-Specific Authentication and Authorization Function (NSSAAF) (Rel-17) |   | ||||||||||
4.9 | Mission critical security enhancements phase 2 (Rel-17) | S3‑213904 | [33.180] R17 Preconfigured group clarification | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||
S3‑214269 | [33.180] MCXSec over 5GS | Ericsson, Motorola Solutions | CR | Agreement | Yes |
Yes
| agreed | No | ||||
4.10 | Enhancements to User Plane Integrity Protection Support in 5GS (Rel-17) |   | ||||||||||
4.11 | Adapting BEST for use in 5G networks (Rel-17) | S3‑213881 | Living document for BEST_5G: draftCR to TS 33.163 | KPN N.V. | draftCR | Approval | Yes |
Yes
| revised | No | S3‑214461 | |
S3‑213882 | pCR to Living document for BEST_5G: resolution of Editor’s notes | KPN N.V., Vodafone | other | Approval | Yes |
Yes
| revised | No | S3‑214419 | |||
S3‑214060 | EN removal about the confidential protection in BEST | Huawei, Hisilicon | other | Approval | Yes |
Yes
| revised | No | S3‑214512 | |||
S3‑214061 | EN removal about the authentication method selection in BEST | Huawei, Hisilicon | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214062 | EN removal about the UE identification in BEST | Huawei, Hisilicon | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214419 | pCR to Living document for BEST_5G: resolution of Editor’s notes | KPN N.V., Vodafone | other | Approval | Yes |
Yes
| approved | No | S3‑213882 | |||
S3‑214461 | Living document for BEST_5G: draftCR to TS 33.163 | KPN N.V. | draftCR | Approval | Yes |
Yes
| approved | No | S3‑213881 | |||
S3‑214500 | EN removal about the UE identification in BEST | Huawei, Hisilicon | other | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑214512 | EN removal about the confidential protection in BEST | Huawei, Hisilicon | other | Approval | Yes |
Yes
| revised | No | S3‑214536 | S3‑214060 | ||
S3‑214536 | EN removal about the confidential protection in BEST | Huawei, Hisilicon | other | Approval | Yes |
Yes
| approved | No | S3‑214512 | |||
S3‑214524 | Update of BEST for 5G including GBA, 5G GBA, AKMA | KPN N.V. | CR | Approval | Yes |
Yes
| revised | No | S3‑214542 | |||
S3‑214542 | Update of BEST for 5G including GBA, 5G GBA, AKMA | KPN N.V. | CR | Approval | Yes |
Yes
| agreed | No | S3‑214524 | |||
4.12 | Authentication and key management for applications based on 3GPP credential in 5G (Rel-17) | S3‑213898 | Clarification on Kaf lifetime in Clause 5.2 | Futurewei Technologies | CR | Agreement | Yes |
Yes
| agreed | No | ||
S3‑213899 | Kaf refresh when lifetime expires | Futurewei Technologies | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213937 | Discussion on refresh of KAF and no Kakma in AAnF | ZTE Corporation | discussion | Endorsement | Yes |
Yes
| not pursued | No | ||||
S3‑213938 | Kaf expiration | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213939 | Kaf is invalid in AF | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214234 | CR to 33.535: Clarification on AKMA Application Key retrieval | Samsung | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213936 | Clean up for clause 6.6.1 | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S3‑214490 | |||
S3‑213940 | No AKMA security context in AAnF | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213941 | Sending UE ID to the AKMA AF | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑213942 | UE stores AKMA subscription data | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214039 | Correction to Deriving AKMA Application Key for a specific AF | Huawei,HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214091 | AKMA roaming | Lenovo, Motorola Mobility | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214096 | LI for AKMA Roaming | Lenovo, Motorola Mobility | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑214235 | Discussion on AKMA Roaming scenario | Samsung | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑214236 | CR to 33.535: AKMA service support for roaming UE | Samsung | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214490 | Clean up for clause 6.6.1 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S3‑213936 | |||
4.13 | User Plane Integrity Protection for LTE (Rel-17) | S3‑214035 | Add clarification in EN-DC scenario | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑214476 | |
S3‑214083 | Add details of algorithms to be supported | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214084 | UE Capability to support UP IP with SeNB in DC | Ericsson | other | Approval | Yes |
Yes
| merged | No | S3‑214476 | |||
S3‑214085 | UE Capability to support UP IP with SgNB in EN-DC | Ericsson | other | Approval | Yes |
Yes
| merged | No | S3‑214476 | |||
S3‑214086 | Updates to clause 7.3.X on UP integrity protection policy | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214087 | Updates to IW HO from EPS to 5GS in TS 33.501 | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214088 | LS on support of User Plane integrity protection in EPS/LTE | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑214139 | Security requirements for UPIP over E-UTRA | Qualcomm Incorporated | other | Approval | Yes |
Yes
| revised | No | S3‑214435 | |||
S3‑214328 | Draft CR to 33.401 - Living document on LTE UPIP | VODAFONE Group Plc | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S3‑214330 | Draft CR to 33.501 - Living document on LTE UPIP | VODAFONE Group Plc | draftCR | Agreement | Yes |
Yes
| noted | No | ||||
S3‑214435 | Security requirements for UPIP over E-UTRA | Qualcomm Incorporated | other | Approval | Yes |
Yes
| approved | No | S3‑214139 | |||
S3‑214454 | Addition of UPIP for LTE | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214455 | User Plane Integrity Protection Policy Handling in IW handover from EPS to 5GS | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214462 | LS on LTE User Plane Integrity Protection | VODAFONE Group Plc | LS out | Approval | Yes |
Yes
| approved | No | ||||
S3‑214476 | Add clarification in EN-DC scenario | Huawei, HiSilicon | other | Approval | Yes |
Yes
| approved | No | S3‑214035 | |||
4.14 | Enhancements of 3GPP profiles for cryptographic algorithms and security protocols (Rel- 17) | S3‑213886 | CR Updating SIP DIGEST IETF references from RFC 2617 to RFC 7616 | T-Mobile USA | CR | Agreement | Yes |
Yes
| merged | No | S3‑214516 | |
S3‑214055 | implementation for living CR for SIP digest changes | Huawei, Hisilicon | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214063 | CR for SIP digest | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214501 | |||
S3‑214133 | Correction to the GBA TLS 1.3 specification | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| not pursued | No | S3‑212842 | |||
S3‑214134 | GBA key re-negotiation with TLS 1.3 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| revised | No | S3‑214451 | |||
S3‑214216 | Introducing support of TLS v1.3 in ProSe TS 33.303 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214305 | Security updates for algorithms and protocols in 33.310 | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214306 | Security updates for algorithms and protocols in 33.328 | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑214428 | |||
S3‑214307 | Security updates for algorithms and protocols in 33.203 | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑214429 | |||
S3‑214308 | Living draftCRSecurity updates for algorithms and protocols for 33.310 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214309 | Living draftCR Security updates for algorithms and protocols for 33.210 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214424 | CR - Security updates for algorithms and protocols for 33.310 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214426 | CR - Security updates for algorithms and protocols for 33.210 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214428 | Security updates for algorithms and protocols in 33.328 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214306 | |||
S3‑214429 | Security updates for algorithms and protocols in 33.203 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214307 | |||
S3‑214451 | GBA key re-negotiation with TLS 1.3 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214134 | |||
S3‑214501 | CR for SIP digest | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214516 | S3‑214063 | ||
S3‑214516 | CR for SIP digest | Huawei, Hisilicon, T-Mobile US, Mavenir | CR | Approval | Yes |
Yes
| agreed | No | S3‑214501 | |||
4.15 | Security Aspects of Enhancements for 5G Multicast-Broadcast Services (Rel-17) | S3‑213872 | LS on Multicast paging with TMGI | S2-2107995 | LS in | Yes |
Yes
| postponed | No | |||
S3‑214009 | living doc for 5MBS WID | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑214422 | |||
S3‑214054 | Authentication and authorization for MBS session | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑214497 | |||
S3‑213934 | Authenticaton and authorization for MBS service | ZTE Corporation | other | Approval | Yes |
Yes
| merged | No | S3‑214497 | |||
S3‑214010 | Update the clause of security mechanisms for MBS traffic transmission | Huawei, HiSilicon | other | Approval | Yes |
Yes
| merged | No | S3‑214436 | |||
S3‑214150 | 5G MBS key management | Qualcomm Incorporated | other | Approval | Yes |
Yes
| revised | No | S3‑214436 | |||
S3‑214295 | Key hierarchy, key distribution and key update in 5MBS | Philips International B.V. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214018 | Security protection for interworking between 5MBS and eMBMS | Huawei, HiSilicon | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑213935 | Security for MBS-eMBMS interworking | ZTE Corporation | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214418 | LS to SA2 on secondary authentication for multicast PDU session | Huawei, Hisilicon | LS out | Yes |
Yes
| revised | No | S3‑214538 | ||||
S3‑214538 | LS to SA2 on secondary authentication for multicast PDU session | Huawei, Hisilicon | LS out | - | Yes |
Yes
| approved | No | S3‑214418 | |||
S3‑214422 | living doc for 5MBS WID | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑214009 | |||
S3‑214436 | 5G MBS key management | Qualcomm Incorporated | other | Approval | Yes |
Yes
| approved | No | S3‑214150 | |||
S3‑214464 | Security aspects of 5MBS | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑214497 | Authentication and authorization for MBS session | Huawei, HiSilicon | other | Approval | Yes |
Yes
| approved | No | S3‑214054 | |||
4.16 | Security for enhanced support of Industrial IoT (Rel-17) |   | ||||||||||
4.17 | Security Aspects of eNPN (Rel-17) | S3‑213807 | Reply LS on UE capabilities indication in UPU | C1-212599 | LS in | Yes |
Yes
| noted | No | |||
S3‑213808 | Reply LS on UE capabilities indication in UPU | S2-2106703 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑213829 | LS on UE capabilities indication in UPU | S2-2101072 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑213833 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection | S2-2106705 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑213873 | LS on IMEI for Non-Public Networks/Private Networks without using USIM | S2-2108093 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213994 | MSK derivation in external authentication | Huawei, HiSilicon | other | Approval | Yes |
Yes
| merged | No | S3‑214515 | |||
S3‑214022 | SUPI handling for EAP | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214023 | Exclude EAP-AKA' from AAA | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214036 | Definition to Anonymous SUPI | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑214483 | |||
S3‑214080 | Resolution to editor’s notes concerning identity sharing | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| merged | No | S3‑214439 | |||
S3‑214081 | Resolution of editor note related to selection of root key | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| revised | No | S3‑214515 | |||
S3‑214157 | Resolution for EN on sending SUPI to SNPN | Qualcomm Incorporated | other | Approval | Yes |
Yes
| revised | No | S3‑214439 | |||
S3‑214158 | Configuration of CH credentials | Qualcomm Incorporated | other | Approval | Yes |
Yes
| merged | No | S3‑214515 | |||
S3‑213928 | Update Nnssaaf_AIW interface | CableLabs | other | Approval | Yes |
Yes
| revised | No | S3‑214484 | |||
S3‑214024 | Initial access using AAA | Ericsson | other | Approval | Yes |
Yes
| merged | No | S3‑214543 | |||
S3‑214079 | Adding methods for authentication during onboarding | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| merged | No | S3‑214543 | |||
S3‑214156 | Securing initial access for UE onboarding | Qualcomm Incorporated | other | Approval | Yes |
Yes
| revised | No | S3‑214543 | |||
S3‑214543 | Securing initial access for UE onboarding | Qualcomm Incorporated | other | Approval | Yes |
Yes
| approved | No | S3‑214156 | |||
S3‑214021 | SUPI privacy for SNPN | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214181 | Protection for eNPN credential provisioning | Xiaomi Technology | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214287 | Living document for eNPN: draftCR to TS 33.501 capturing Security aspects of eNPN | Ericsson, Huawei, HiSilicon, Qualcomm Incorporated, CableLabs, Charter Communications, Intel, Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S3‑214437 | |||
S3‑214165 | Update to Clause 6.15.2.1 Procedure for UE Parameters Update | Lenovo, Motorola Mobility | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214437 | Living document for eNPN: draftCR to TS 33.501 capturing Security aspects of eNPN | Ericsson, Huawei, HiSilicon, Qualcomm Incorporated, CableLabs, Charter Communications, Intel, Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S3‑214287 | |||
S3‑214439 | Resolution for EN on sending SUPI to SNPN | Qualcomm Incorporated | other | Approval | Yes |
Yes
| approved | No | S3‑214157 | |||
S3‑214446 | Security aspects of eNPN | Ericsson, Huawei, HiSilicon, Qualcomm Incorporated, CableLabs, Charter Communications, Intel, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214447 | Reply LS on UE capabilities indication in UPU | Qualcomm India Pvt Ltd | LS out | Approval | Yes |
Yes
| approved | No | ||||
S3‑214483 | Clarification on anonymous SUCI related | Huawei, HiSilicon | other | Approval | Yes |
Yes
| approved | No | S3‑214036 | |||
S3‑214484 | Update Nnssaaf_AIW interface | CableLabs | other | Approval | Yes |
Yes
| approved | No | S3‑213928 | |||
S3‑214515 | Resolution of editor note related to selection of root key | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Qualcomm Incorporated | other | Approval | Yes |
Yes
| approved | No | S3‑214081 | |||
4.18 | Security Aspects of Enhancement of Support for Edge Computing in 5GC (Rel-17) | S3‑213848 | Reply LS on EAS and ECS identifiers | S6-212490 | LS in | Yes |
Yes
| postponed | No | |||
S3‑213943 | Authentication based on AKMA between EEC and ECS in clause 6.2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214067 | Authentication and Authorization between EEC and ECS | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214275 | Authentication and Authorization between EEC and ECS | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214277 | OAuth 2.0 profile for EC | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214271 | Solving the EN in the requirements | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213944 | Authentication based on AKMA between EEC and EES in clause 6.3 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214068 | Authentication and Authorization between EEC and EES | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214276 | Authentication and Authorization between EEC and EES | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213967 | Authentication and Authorization between EES and ECS | Intel Sweden AB | pCR | Approval | Yes |
Yes
| revised | No | S3‑214489 | |||
S3‑214069 | Authentication and Authorization in EES capability exposure for non-CAPIF scenario | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214502 | |||
S3‑214070 | New Annex for Edge computing security | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214503 | |||
S3‑214489 | Authentication and Authorization between EES and ECS | Intel Sweden AB | pCR | Approval | Yes |
Yes
| approved | No | S3‑213967 | |||
S3‑214502 | Authentication and Authorization in EES capability exposure for non-CAPIF scenario | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214069 | |||
S3‑214503 | New Annex for Edge computing security | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑214070 | |||
S3‑214508 | Draft TS 33.558 | Huawei, Hisilicon | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S3‑214509 | Rel-17 Work Item Exception for EDGE_5GC | Huawei, Hisilicon | WI exception request | Approval | Yes |
Yes
| agreed | No | ||||
4.19 | TLS protocols profiles for AKMA (Rel-17) | S3‑213945 | Delete the GBA_Digest in annex B.1.2.2 | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S3‑214491 | |
S3‑214131 | Corrections to the TLS with AKMA specification | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | S3‑212840 | |||
S3‑214132 | Adding TLS 1.3 with AKMA keys | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | S3‑212841 | |||
S3‑214491 | Delete the GBA_Digest in annex B.1.2.2 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S3‑213945 | |||
4.20 | Security aspects of Uncrewed Aerial Systems (Rel-17) | S3‑213900 | AMF skipping UUAA procedure | Futurewei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑213923 | UUAA procedure at registration | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214463 | |||
S3‑214125 | Proposed text for UUAA-MM | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑214463 | S3‑213517 | ||
S3‑214161 | UUAA during Registration | Lenovo, Motorola Mobility | pCR | Yes |
Yes
| merged | No | S3‑214463 | ||||
S3‑213924 | UUAA procedure at PDU session establishment | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214465 | |||
S3‑213925 | Pairing authorizaiton | Huawei, Hisilicon, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑214466 | |||
S3‑214126 | Proposed text for UUAA-SM | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑214465 | S3‑213518 | ||
S3‑214162 | UUAA during PDU Session Establishment | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| merged | No | S3‑214465 | |||
S3‑214127 | Proposed text for UUAA in EPS | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213926 | UUAA re-authentication identification EN | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213927 | addressing EN in revocation procedure | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑214453 | |||
S3‑214121 | Clarifications to UUAA Revocation | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑214453 | |||
S3‑214453 | Clarifications to UUAA Revocation | Lenovo, Motorola Mobility, Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214121 | |||
S3‑214463 | UUAA procedure at registration | Huawei, Hisilicon, Lenovo, Motorola Mobility, Qualcomm, Interdigital | pCR | Approval | Yes |
Yes
| approved | No | S3‑213923 | |||
S3‑214465 | UUAA procedure at PDU session establishment | Huawei, Hisilicon, Lenovo, Motorola Mobility, Qualcomm, Interdigital | pCR | Approval | Yes |
Yes
| approved | No | S3‑213924 | |||
S3‑214466 | Pairing authorization | Huawei, Hisilicon, Lenovo, Motorola Mobility, Interdigital | pCR | Approval | Yes |
Yes
| approved | No | S3‑213925 | |||
S3‑214521 | Draft TS 33.256 | Qualcomm CDMA Technologies | draft TS | Approval | Yes |
Yes
| approved | No | S3‑213710 | |||
S3‑214522 | Cover sheet for TS 33.256 | Qualcomm Incorporated | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S3‑214523 | Exception sheet for UAS | Qualcomm Incorporated | WI exception request | Approval | Yes |
Yes
| agreed | No | ||||
4.21 | Security Aspects of Proximity based services in 5GS ProSe (Rel-17) | S3‑213871 | Reply LS on Layer-3 UE-to-Network Relay authentication and authorization | S2-2107976 | LS in | Yes |
Yes
| replied to | No | |||
S3‑214110 | pCR to TS33.503 Clause 4.2-Change reference point name | CATT | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214043 | Update clause 4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214473 | |||
S3‑213946 | Network domain security | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑214472 | |||
S3‑213947 | Security of Npc2 interface | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑214472 | |||
S3‑213948 | Security of UE 5G DDNMF interface | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑214472 | |||
S3‑214028 | Add content to clause 5 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214472 | |||
S3‑214177 | 33.503: Common Security | Xiaomi Technology | pCR | Approval | Yes |
Yes
| merged | No | S3‑214472 | |||
S3‑214215 | Security for UE to 5G DDNMF communication and for UE to 5G PKMF communication | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑214472 | |||
S3‑213949 | Security requirements for 5G ProSe Direct Discovery | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑214444 | |||
S3‑213950 | Security procedures for 5G ProSe Direct Discovery | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214044 | Add text to clause 6.1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214076 | open discovery | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑214441 | |||
S3‑214077 | restricted discovery | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑214441 | |||
S3‑214147 | CR to ProSe TS – Direct Discovery | Qualcomm Incorporated, CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑214441 | |||
S3‑214148 | CR to ProSe TS – Security Requirements in Direct Discovery | Qualcomm Incorporated, CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑214444 | |||
S3‑214301 | pCR to 5G ProSe draft TS clause 6.1-Security for 5G ProSe Discovery | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214105 | pCR to TS33.503-Remove groupcast related content | CATT | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214006 | Propose text to clause 6.3 about PC5 unicast | Huawei,HiSilicon, LG Electronics | pCR | Approval | Yes |
Yes
| revised | No | S3‑214470 | |||
S3‑214112 | pCR to TS33.503 Clause 6.3-Security for Unicast mode 5G ProSe Direct Communication | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑214470 | |||
S3‑214279 | Add a new clause on security policy provisioning | Huawei, HiSilicon,Xiaomi | pCR | Approval | Yes |
Yes
| noted | No | S3‑214031 | |||
S3‑214045 | Add a new clause on the privacy of DCR | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214178 | 33.503: Security for Unicast Mode Direct Communication | Xiaomi Technology | pCR | Approval | Yes |
Yes
| merged | No | S3‑214470 | |||
S3‑214315 | Refresh of security context for PC5 unicast communication | KPN N.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214214 | Security requirements for UE-to-network relay | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑214488 | |||
S3‑214324 | Add new clauses on privacy protection for UE-to-NW relays | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213912 | NSSAA for Remote UE with L3 U2N relay without N3IWF | InterDigital, Europe, Ltd., LG Electronics | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213971 | Secondary Authentication for Remote UE with L3 U2N relay without N3IWF | LG Electronics, InterDigital | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214042 | Proposal for U2NW relay authentication, authorization and key management | Huawei,HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214140 | User-plane UE-to-network relay connection procedure | Qualcomm Incorporated, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑214438 | |||
S3‑214179 | 33.503: Security for L3 U2N Relay Communication | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑214488 | |||
S3‑214218 | Proposal for U2NW relay authentication, authorization and key management | Samsung, Interdigital, LG Electronics, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑214495 | |||
S3‑214027 | Adding security description for L2 solution | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214471 | |||
S3‑214180 | 33.503: Security for L2 U2N Relay Communication | Xiaomi Technology | pCR | Approval | Yes |
Yes
| merged | No | S3‑214471 | |||
S3‑214031 | Add a new clause on security policy provisioning | Huawei, HiSilicon | pCR | Approval | No |
Yes
| revised | No | S3‑214279 | |||
S3‑214438 | User-plane UE-to-network relay connection procedure | Qualcomm Incorporated, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑214140 | |||
S3‑214441 | CR to ProSe TS – Direct Discovery | Qualcomm Incorporated, CATT, ZTE, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214147 | |||
S3‑214443 | Reply LS on Layer-3 UE-to-Network Relay authentication and authorization | QUALCOMM JAPAN LLC. | LS out | Yes |
Yes
| approved | No | |||||
S3‑214444 | CR to ProSe TS – Security Requirements in Direct Discovery | Qualcomm Incorporated, CATT, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S3‑214148 | |||
S3‑214470 | Propose text to clause 6.3 about PC5 unicast | Huawei; HiSilicon, LG Electronics, CATT, Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑214006 | |||
S3‑214471 | Adding security description for L2 solution | Huawei, HiSilicon, Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑214027 | |||
S3‑214472 | Add content to clause 5 | Huawei, HiSilicon, ZTE, Xiaomi, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑214028 | |||
S3‑214473 | Update clause 4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214043 | |||
S3‑214488 | 33.503: Security for L3 U2N Relay Communication | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑214179 | |||
S3‑214495 | Proposal for U2NW relay authentication, authorization and key management | Samsung, Interdigital, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214218 | |||
S3‑214510 | Rel-17 Work Item Exception for 5G_ProSe Security Aspects | CATT | WI exception request | Approval | Yes |
Yes
| agreed | No | ||||
S3‑214511 | Draft TS 33.503 v0.2.0 Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) | CATT | draft TS | Approval | Yes |
Yes
| approved | No | ||||
4.22 | Security Aspects of User Consent for 3GPP services (Rel-17) | S3‑213862 | Baseline of user conent living CR for SA3#105-e | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||
S3‑213995 | Living CR for UC3S in TS 33.501 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213996 | User consent check | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑214478 | |||
S3‑213997 | User consent revocation | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑214479 | |||
S3‑214017 | User Consent Requirement | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑214480 | |||
S3‑214182 | Validity and revocation of consent | Ericsson | other | Approval | Yes |
Yes
| revised | No | S3‑214434 | |||
S3‑214434 | Validity and revocation of consent | Ericsson | other | Approval | Yes |
Yes
| approved | No | S3‑214182 | |||
S3‑214457 | Living document for UC3S: draftCR to TS 33.501 capturing Security aspects of user consent | Huawei, HiSilicon | draftCR | Yes |
Yes
| approved | No | |||||
S3‑214459 | Security aspects of User Consent | Huawei, HiSilicon | CR | Yes |
Yes
| agreed | No | |||||
S3‑214477 | Living CR for UC3S in TS 33.501 | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑214478 | User consent check | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S3‑213996 | |||
S3‑214479 | User consent revocation | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S3‑213997 | |||
S3‑214480 | User Consent Requirement | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| approved | No | S3‑214017 | |||
4.23 | Security aspects of enablers for Network Automation (eNA) for the 5G system (5GS) (Rel-17) | S3‑214094 | living CR for eNA | China Mobile | draftCR | Agreement | Yes |
Yes
| revised | No | S3‑214493 | |
S3‑214264 | Authorization mechanisms for data consumer to access data from data producer via DCCF | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Mavenir, Verizon | other | Approval | Yes |
Yes
| revised | No | S3‑214513 | |||
S3‑214265 | Authorization mechanisms for data consumer to access data from data producer when notification sent via MFAF | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | other | Approval | Yes |
Yes
| revised | No | S3‑214514 | |||
S3‑214303 | Update on Authorization of NF Service Consumers for data access via DCCF | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑214304 | Security protection of data via Messaging Framework | Ericsson, Lenovo, Motorola Mobility | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑214493 | living CR for eNA | China Mobile | draftCR | Agreement | Yes |
Yes
| approved | No | S3‑214094 | |||
S3‑214494 | CR for eNA | China Mobile E-Commerce Co. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑214513 | Authorization mechanisms for data consumer to access data from data producer via DCCF | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Mavenir, Verizon, Ericsson, Huawei, HiSilicon, China mobile | other | Approval | Yes |
Yes
| approved | No | S3‑214264 | |||
S3‑214514 | Authorization mechanisms for data consumer to access data from data producer when notification sent via MFAF | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | other | Approval | Yes |
Yes
| approved | No | S3‑214265 | |||
4.24 | Security aspects of the 5GMSG Service (Rel-17) | S3‑214108 | living document of 5GMSG | China Mobile | draftCR | Approval | Yes |
Yes
| revised | No | S3‑214430 | |
S3‑214109 | Change request to living document-MSGin5G | China Mobile | other | Approval | Yes |
Yes
| revised | No | S3‑214517 | |||
S3‑214220 | [5gMSG] CR to living document: Authorization of MSG Client | Samsung | other | Agreement | Yes |
Yes
| noted | No | ||||
S3‑214430 | living document of 5GMSG | China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | S3‑214108 | |||
S3‑214517 | Change request to living document-MSGin5G | China Mobile | other | Approval | Yes |
Yes
| approved | No | S3‑214109 | |||
S3‑214518 | Security aspects of MSGin5G | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | ||||
4.25 | New work item proposals for Rel-17/Rel-18 | S3‑213847 | Study of privacy of identities over radio access | InterDigital, Inc., Apple, AT&T, CableLabs, Convida Wireless, Futurewei, Intel, Motorola Mobility, Nokia, Nokia Shanghai Bell, Telefonica, Verizon Wireless | SID new | Approval | Yes |
Yes
| revised | No | S3‑214296 | |
S3‑213888 | New WID on Non-Seamless WLAN offload Authentication in 5GS | Nokia, Nokia Shanghai Bell | WID new | Approval | Yes |
Yes
| revised | No | S3‑214433 | |||
S3‑213903 | Mission Critical R18 WID | Motorola Solutions Danmark A/S | WID new | Agreement | Yes |
Yes
| revised | No | S3‑214485 | |||
S3‑213920 | WID on enhanced security for Phase 2 network slicing | Huawei, Hisilicon | WID new | Agreement | Yes |
Yes
| revised | No | S3‑214460 | |||
S3‑213976 | New WID proposal for MINT | LG Electronics, LG Uplus, KT Corp, SK Telecom | WID new | Approval | Yes |
Yes
| noted | No | ||||
S3‑213981 | WID of 5GFBS | Apple | WID new | Approval | Yes |
Yes
| noted | No | ||||
S3‑214032 | Discuss on a new study on Home network triggerred authenticaiton Huawei, HiSilicon endorsement Approval | Huawei, HiSilicon | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑214033 | New WID on Security Assurance Specification for Management Function | Huawei, HiSilicon | SID new | Approval | Yes |
Yes
| revised | No | S3‑214482 | |||
S3‑214034 | New WID for SCAS work to introduce R-17 features on existing functions | Huawei, HiSilicon | SID new | Approval | Yes |
Yes
| noted | No | ||||
S3‑214092 | New WID on SECAM and SCAS for 3GPP virtualized network products | China Mobile | WID new | Approval | Yes |
Yes
| revised | No | S3‑214492 | |||
S3‑214093 | New SID on interworking between 3GPP NF and security devices | China Mobile | SID new | Approval | Yes |
Yes
| noted | No | ||||
S3‑214201 | FS_eSBA_SEC - SID revision | Nokia, Nokia Shanghai Bell | SID revised | Agreement | Yes |
Yes
| revised | No | S3‑214535 | |||
S3‑214202 | WID_eSBA_SEC | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| noted | No | ||||
S3‑214203 | WID_N32_SEC | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| noted | No | ||||
S3‑214217 | Update to WID on 3GPP profiles for cryptographic algorithms and security protocols | Ericsson | WID revised | Approval | Yes |
Yes
| agreed | No | ||||
S3‑214237 | New WID for SEAL security enhancement | Samsung | WID new | Approval | Yes |
Yes
| revised | No | S3‑214496 | |||
S3‑214238 | SID on user plane security enhancement | Samsung | SID new | Approval | Yes |
Yes
| noted | No | ||||
S3‑214244 | New WID on the security of AMF re-allocation | Ericsson | WID new | Agreement | Yes |
Yes
| noted | No | ||||
S3‑214248 | New WID on Authentication enhancements in 5GS | Ericsson | WID new | Agreement | Yes |
Yes
| revised | No | S3‑214445 | |||
S3‑214296 | Study of privacy of identities over radio access | InterDigital, Inc., Apple, AT&T, CableLabs, Convida Wireless, Futurewei, Intel, Motorola Mobility, Nokia, Nokia Shanghai Bell, Samsung, Telefonica, Verizon Wireless | SID new | Approval | Yes |
Yes
| revised | No | S3‑214487 | S3‑213847 | ||
S3‑214433 | New WID on Non-Seamless WLAN offload Authentication in 5GS | Nokia, Nokia Shanghai Bell | WID new | Approval | Yes |
Yes
| agreed | No | S3‑213888 | |||
S3‑214445 | New WID on Authentication enhancements in 5GS | Ericsson | WID new | Agreement | Yes |
Yes
| agreed | No | S3‑214248 | |||
S3‑214460 | WID on enhanced security for Phase 2 network slicing | Huawei, Hisilicon, Lenovo, Motorola Mobility, China Mobile, China Unicom, CATT, ZTE, CAICT, Xiaomi | WID new | Agreement | Yes |
Yes
| agreed | No | S3‑213920 | |||
S3‑214482 | New WID on Security Assurance Specification for Management Function (MnF) | Huawei, HiSilicon | WID new | Approval | Yes |
Yes
| agreed | No | S3‑214033 | |||
S3‑214485 | Mission Critical R18 WID | Motorola Solutions Danmark A/S | WID new | Agreement | Yes |
Yes
| agreed | No | S3‑213903 | |||
S3‑214487 | New Study of privacy of identifiers over radio access | InterDigital, Inc., Apple, AT&T, CableLabs, CATT, CISA ECD, Convida Wireless, Ericsson, Futurewei, Intel, Johns Hopkins University APL, Mavenir, Motorola Mobility, Nokia, Nokia Shanghai Bell, Peraton Labs, Phillips, Samsung, Telefonica, T-Mobile US, US NI | SID new | Approval | Yes |
Yes
| agreed | No | S3‑214296 | |||
S3‑214492 | New WID on SECAM and SCAS for 3GPP virtualized network products | China Mobile | WID new | Approval | Yes |
Yes
| agreed | No | S3‑214092 | |||
S3‑214496 | New WID for SEAL security enhancement | Samsung | WID new | Approval | Yes |
Yes
| agreed | No | S3‑214237 | |||
S3‑214535 | FS_eSBA_SEC - SID revision | Nokia, Nokia Shanghai Bell | SID revised | Agreement | Yes |
Yes
| agreed | No | S3‑214201 | |||
4.26 | Other work areas (no release restrictions) | S3‑213863 | AMF - Expected result for test case not defined in the specifications | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||
S3‑213864 | AMF - Expected result for test case not defined in the specifications | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑213865 | AMF - NAS protection algorithm selection in AMF change | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑213866 | AMF - NAS protection algorithm selection in AMF change | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑213879 | AMF – precondition bidding down prevention in Xn-handover test | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑213880 | AMF – precondition bidding down prevention in Xn-handover test | Keysight Technologies UK Ltd | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑214115 | Clarification to TEID uniqueness test case | Ericsson | CR | Yes |
Yes
| not pursued | No | |||||
S3‑214116 | Clarification to TEID uniqueness test case | Ericsson | CR | Yes |
Yes
| not pursued | No | |||||
S3‑214113 | Editorial and corrections | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑214420 | |||
S3‑213890 | Support for NSWO in 5GS | Nokia, Nokia Shanghai Bell,AT&T,Lenovo,Motorola Mobility,Qualcomm Incorporated | CR | Approval | Yes |
Yes
| revised | No | S3‑214432 | |||
S3‑213905 | [33.180] R15 KMS message signature clarification | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑213906 | [33.180] R16 KMS message signature clarification (mirror) | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑213907 | [33.180] R17 KMS message signature clarification (mirror) | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑213908 | [33.180] R15 MIKEY signature clarification | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑213909 | [33.180] R16 MIKEY signature clarification (mirror) | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑213910 | [33.180] R17 MIKEY signature clarification (mirror) | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑213921 | clarification on optional EAP ID Request in NSSAA Procedure | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213922 | Serving network ID in NSSAA | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213929 | Verification of NSSAIs for preventing slice attack | CableLabs | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213930 | Verification of NSSAIs for preventing slice attack | CableLabs | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213977 | TS 33.501 Rel-17 security aspects on MINT feature | LG Electronics Inc. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑213987 | Discussion paper on physical layer security | Apple | discussion | Yes |
Yes
| noted | No | |||||
S3‑213989 | Discussion on Integrity check during mobility procedure | NEC Telecom MODUS Ltd. | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S3‑213990 | Integrity check during context transfer scenario 1 | NEC Telecom MODUS Ltd. | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑213991 | Integrity check during context transfer scenario 2 | NEC Telecom MODUS Ltd. | CR | Yes |
Yes
| not pursued | No | |||||
S3‑214007 | Propose to mitigate bidding-down attack | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214014 | Rel17 Clarification about multiple horizontal key derivations upon AMF re-allocation via direct NAS reroute | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214046 | clarification on handling the security context in MR | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214047 | clarification on handling the security context in MR | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214048 | clarification on handling the security context in MR | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214056 | removal of unspecified validity of AV-R16 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214498 | |||
S3‑214057 | removal of unspecified validity of AV-R17 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214499 | |||
S3‑214058 | clarification on NAS count handling-R16 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214059 | clarification on NAS count handling-R17 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214071 | Clarification on the emergency test | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214504 | |||
S3‑214089 | Clarification on the emergency test - Rel15 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214506 | |||
S3‑214090 | Clarification on the emergency test - Rel16 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214507 | |||
S3‑214118 | SUPI in Notifications from NSSAAF | Ericsson | CR | Yes |
Yes
| not pursued | No | |||||
S3‑214122 | SUPI in Notifications from NSSAAF | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214138 | Confirming UE supported algorithms in Path Switch procedure | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| revised | No | S3‑214452 | |||
S3‑214037 | Correction to Authorization for indirect communication with delegated discovery procedure in rel16 | Huawei,HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214474 | |||
S3‑214038 | Correction to Authorization for indirect communication with delegated discovery procedure in rel17 | Huawei,HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑214475 | |||
S3‑214073 | Clarification on the TLS mechanism betwee SEPPs | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214102 | Resolving the EN on the authorization between SCPs | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214187 | SBA CR CCA in roaming R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214188 | SBA CR CCA in roaming R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214189 | SBA CR NRF-NRF mutual auth R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑214530 | |||
S3‑214190 | SBA CR NRF-NRF mutual auth R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑214531 | |||
S3‑214191 | SBA CR Alignment for Oauth2.0 validation R15 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214192 | SBA CR Alignment for Oauth2.0 validation R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214193 | SBA CR Alignment for Oauth2.0 validation R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214194 | SBA CR NRF deployments R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214195 | SBA CR N32 for interconnect R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑214532 | |||
S3‑214196 | SBA CR N32 for interconnect R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑214533 | |||
S3‑214288 | Clarification audience of CCA | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214289 | Clarification audience of CCA | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214290 | Certificate profile for SCP and SEPP | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214291 | Certificate profile for SCP and SEPP | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214292 | SEPP include and verify source PLMN-ID | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214197 | IPUPS overload control R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214230 | KIAB generation for NR-DC scenario | Samsung, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214272 | Security for CoAP interfaces in SEAL | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑214431 | |||
S3‑214130 | Adding MACS as an input parameter to the calculation of AK* to provide freshness | Qualcomm Incorporated, Thales | CR | Agreement | Yes |
Yes
| not pursued | No | S3‑212846 | |||
S3‑214316 | Addition of MAC-S for authentication enhancement | THALES, IDEMIA | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑213895 | Security Protection of SQN during AKA re-synchronisations | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214329 | Avoiding unencrypted radio interface data transfer | Vodafone | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214331 | Avoiding unencrypted radio interface data transfer | Vodafone | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑214074 | Resolving the EN on the authorization between SCPs | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑214261 | Discussion on the SBA services to support NSWO authentication | Ericsson | discussion | Yes |
Yes
| noted | No | |||||
S3‑214262 | SBA services of AUSF/UDM for NSWO authentication | Ericsson | CR | Yes |
Yes
| noted | No | |||||
S3‑214420 | Editorial and corrections | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214113 | |||
S3‑214421 | Editorial and corrections | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214423 | Editorial and corrections | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑214431 | Security for CoAP interfaces in SEAL | Ericsson, Samsung | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214272 | |||
S3‑214432 | Support for NSWO in 5GS | Nokia, Nokia Shanghai Bell,AT&T,Lenovo,Motorola Mobility,Qualcomm Incorporated, Intel, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S3‑213890 | |||
S3‑214440 | Certificate profile for SCP and SEPP | Ericsson, Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214442 | SEPP include and verify source PLMN-ID | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214452 | Confirming UE supported algorithms in Path Switch procedure | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214138 | |||
S3‑214474 | Correction to Authorization for indirect communication | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S3‑214037 | |||
S3‑214475 | Correction to Authorization for indirect communication | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S3‑214038 | |||
S3‑214498 | removal of unspecified validity of AV-R16 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑214056 | |||
S3‑214499 | removal of unspecified validity of AV-R17 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑214057 | |||
S3‑214504 | Clarification on the emergency test | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑214071 | |||
S3‑214506 | Clarification on the emergency test - Rel15 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑214089 | |||
S3‑214507 | Clarification on the emergency test - Rel16 | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑214090 | |||
S3‑214530 | SBA CR NRF-NRF mutual auth R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214189 | |||
S3‑214531 | SBA CR NRF-NRF mutual auth R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214190 | |||
S3‑214532 | SBA CR N32 for interconnect R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214195 | |||
S3‑214533 | SBA CR N32 for interconnect R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214196 | |||
S3‑214534 | SBA CR NRF deployments R17 | Nokia, Nokia Shanghai Bell, Ericsson | draftCR | Agreement | Yes |
Yes
| approved | No | ||||
5 | Studies areas |   | ||||||||||
5.1 | Study on 5G security enhancement against false base stations | S3‑213825 | LS Reply to SA3 on security protection on RRCResumeRequest message | R2-2109121 | LS in | Yes |
Yes
| replied to | No | |||
S3‑213978 | 5GFBS-Conclusion for solution#17 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213979 | 5GFBS-Reply LS to R2-2109121 on protection of RRCResumerequest message | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214016 | Clarifications on solution 17 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214151 | Conclusion for KI #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213980 | 5GFBS- Update solution#27 on UE local security policy | Apple | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑214019 | addressing the editor's notes in sol#27 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214379 | |||
S3‑214152 | Conclusion for KI #2 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214280 | New Solution: Shared key based MIB/SIBs protection with enhanced protection against replay/MitM attacks | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214325 | LS out on authenticity and replay protection of system information | CableLabs | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑213913 | Update to solution #25 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213914 | Evaluation of solution #4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213915 | Conclusion for KI#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214153 | Conclusion for KI #3 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214098 | Detection of MitM attacks with secret paging | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213964 | Update Annex B in TR 33.809 | CableLabs | pCR | Approval | Yes |
Yes
| revised | No | S3‑214392 | |||
S3‑214379 | addressing the editor's notes in sol#27 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214019 | |||
S3‑214392 | Update Annex B in TR 33.809 | CableLabs | pCR | Approval | Yes |
Yes
| approved | No | S3‑213964 | |||
S3‑214408 | Draft TR 33.809 | Apple (UK) Limited | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214525 | LS Reply on security protection of RRCResumeRequest message | NTT DOCOMO INC. | LS out | Yes |
Yes
| revised | No | S3‑214539 | ||||
S3‑214539 | LS Reply on security protection of RRCResumeRequest message | NTT DOCOMO INC. | LS out | - | Yes |
Yes
| approved | No | S3‑214525 | |||
5.2 | Study on User Plane Integrity Protection |   | ||||||||||
5.3 | Study on Security Impacts of Virtualisation | S3‑213884 | New solution: Ticket based access control for administrators | MITRE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑214390 | |
S3‑213896 | New solution for Ki#13: Remote Attestation on 3GPP level | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑214393 | |||
S3‑213897 | New Solution Using Boot Time Attestation for NF Registration | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | pCR | Approval | Yes |
Yes
| revised | No | S3‑214391 | |||
S3‑214390 | New solution: Ticket based access control for administrators | MITRE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑213884 | |||
S3‑214391 | New Solution Using Boot Time Attestation for NF Registration | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD, NIST | pCR | Approval | Yes |
Yes
| approved | No | S3‑213897 | |||
S3‑214393 | New solution for Ki#13: Remote Attestation on 3GPP level | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑213896 | |||
S3‑214406 | draft TR 33.848 | BT plc | draft TR | Agreement | Yes |
Yes
| approved | No | ||||
5.4 | Study on authentication enhancements in 5GS | S3‑213834 | Reply to LS on Resynchronisations | ETSI SAGE | LS in | Yes |
Yes
| postponed | No | |||
S3‑213836 | Reply LS on Security risk evaluation of using long term key for another key derivation than AKA | ETSI SAGE | LS in | Yes |
Yes
| noted | No | |||||
S3‑214249 | Remove Editor's Notes in key issue #3.1 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213851 | Update to solution #2.1 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213852 | Update to solution #2.2 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213853 | Update to solution #2.3 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| revised | No | S3‑214358 | |||
S3‑213854 | Update to solution #2.4 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213855 | Update to solution #2.5 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213859 | Update to solution #2.12 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213892 | Editor note removal for solution#2.8 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213856 | Update to solution #3.1 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213857 | Update to solution #4.3 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213858 | Update to solution #4.7 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213893 | Editors note removal for solution#4.3 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213894 | Conclusion to Key Issue #4.1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213951 | Conclusion on key issue 4.1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214015 | Conclusion on Key Issue #4.1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214129 | Proposed conclusion for key issue #4.1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑214355 | S3‑212843 | ||
S3‑214312 | Conclusion for KI#4.1 | THALES, IDEMIA | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214247 | Authentication enhancements: Discussion about the WID | Ericsson | discussion | Information | Yes |
Yes
| noted | No | ||||
S3‑214319 | Presentation of Report to TSG: TR 33.846, Version 0.14.0 | Ericsson España S.A. | TS or TR cover | Approval | Yes |
Yes
| revised | No | S3‑214352 | |||
S3‑213860 | Conclusions on key issues #2.1, #2.2, #3.2 and #4.1 in TR 33.846 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S3‑213861 | Some problems concerning combination of solutions for key issues in TR 33.846 | JSRPC Kryptonite | discussion | Decision | Yes |
Yes
| not treated | No | ||||
S3‑214352 | Presentation of Report to TSG: TR 33.846, Version 0.14.0 | Ericsson España S.A. | TS or TR cover | Approval | Yes |
Yes
| approved | No | S3‑214319 | |||
S3‑214355 | Proposed conclusion for key issue #4.1 | Qualcomm Incorporated, Thales | pCR | Approval | Yes |
Yes
| approved | No | S3‑214129 | |||
S3‑214358 | Update to solution #2.3 | JSRPC Kryptonite | pCR | Approval | Yes |
Yes
| approved | No | S3‑213853 | |||
S3‑214402 | Draft TR 33.846 v0.14.0 Study on authentication enhancements in the 5G System (5GS) | Ericsson España S.A. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.5 | Study on security aspects of Unmanned Aerial Systems | S3‑214123 | Adding some abbreviations to TR 33.854 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| revised | No | S3‑214343 | |
S3‑214124 | Corrections to TS 33.854 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| revised | No | S3‑214344 | |||
S3‑214343 | Adding some abbreviations to TR 33.854 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214123 | |||
S3‑214344 | Corrections to TS 33.854 | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | S3‑214124 | |||
5.6 | Study on Security Aspects of Enhancement of Support for Edge Computing in 5GC | S3‑213952 | Conclusion on key issue 1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑214385 | |
S3‑214064 | Conclusion on Key issue #1 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214385 | |||
S3‑213982 | MEC- New solution on EEC authentication based on GBA | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214128 | Proposed conclusions for key issue #1 and key issue #2 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | S3‑213522 | |||
S3‑214221 | [EDGE] Discussion paper on need for EEC authentication | Samsung | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑214222 | [EDGE] Discussion on EDGE wayforward | Samsung | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑214270 | Updates to KI#1 and KI#2 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑214347 | |||
S3‑214273 | Updates to conclusion of KI#1 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214317 | Conclusion for KI#1 | THALES | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213953 | Conclusion on key issue 2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑214386 | |||
S3‑213983 | MEC- Discussion paper on the privacy issue EEC ID | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑213984 | MEC- New solution on EEC ID privacy protection | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑214065 | Conclusion on Key issue #2 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214386 | |||
S3‑214274 | Updates to conclusion of KI#2 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214318 | Conclusion for KI#2 | THALES | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214066 | Clarification on the SA2 and SA6 issues | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214347 | Updates to KI#1 and KI#2 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑214270 | |||
S3‑214372 | Presentation of Report to TSG: TR 33.839, Version 0.9.0 (For approval) | Huawei, HiSilicon | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S3‑214385 | Conclusion on Key issue #1 | Huawei, Hisilicon, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S3‑214064 | |||
S3‑214386 | Conclusion on Key issue #2 | Huawei, Hisilicon, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S3‑214065 | |||
S3‑214413 | Draft TR 33.839 | HuaWei Technologies Co., Ltd | draft TR | Yes |
Yes
| approved | No | |||||
5.7 | Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | S3‑213826 | LS on UE ID in adaptation layer | R2-2109227 | LS in | Yes |
Yes
| noted | No | |||
S3‑213972 | Reply LS on Layer-3 UE-to-Network Relay authentication and authorization | LG Electronics | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑214142 | Discussion on SA2 Reply LS on Layer-3 UE-to-Network Relay authentication and authorization | Qualcomm Incorporated | other | Discussion | Yes |
Yes
| noted | No | ||||
S3‑214005 | Update to solution #38 | Huawei,HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214040 | P-TID Privacy protection in solution 39 | Huawei,HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214375 | |||
S3‑214041 | resolving the EN on Kausf desych and key lifetime | Huawei,HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214376 | |||
S3‑214143 | Removing Editor’s Notes in solution #42 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑214346 | |||
S3‑214170 | ProSe: Update to Solution #40 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑214395 | |||
S3‑214171 | ProSe: Evaluation Update for Solution #41 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑214396 | |||
S3‑214211 | ProSe: New solution PC5 anchor key generation via GBA Push | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑214363 | |||
S3‑214219 | ProSe: Resolve EN in solution#1 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214278 | A new solution to address KI#17 | Huawei, HiSilicon,Xiaomi | pCR | Approval | Yes |
Yes
| noted | No | S3‑214029 | |||
S3‑214297 | Update Solution 37: Modification to ensure source authenticity in restricted discovery for relay and group discovery | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑214348 | |||
S3‑214298 | Updates Solution #42 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑214346 | |||
S3‑214299 | Updates Solution #43 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214321 | Update to solution #32 to address privacy issues with User Info ID (KI#5) | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑214354 | |||
S3‑213911 | TR 33.847 Conclusion for NSSAA support with L3 U2N | InterDigital, Europe, Ltd., LG Electronics | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213970 | TR 33.847 Conclusion for Secondary Authentication support with L3 U2N | LG Electronics, InterDigital | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214004 | Update the conclusion to KI#12 | Huawei,HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214374 | |||
S3‑214030 | Conclusion to KI#17 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214104 | pCR to TR33.847- Update conclusions of KI#13 | CATT, Xiaomi, ZTE | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214141 | Additional conclusion of KI #17 – UP security policy | Qualcomm Incorporated, CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214144 | Update of conclusion for KI#5 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214145 | Update of conclusion for Key Issue #13 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214146 | Conclusion of privacy protection of PDU session-related parameters for relaying | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214172 | ProSe: Conclusion Update for Key Issue #3 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214173 | ProSe: Conclusion for Key Issue #13 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214174 | ProSe: Conclusion for Key Issue #17 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214212 | Conclusion for user plane solutions for KI#3, KI#4, KI#9 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214213 | Conclusion for control plane solutions for KI#3, KI#4, KI#9 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑214345 | |||
S3‑214300 | Conclusions KI#1 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214313 | Add Conclusion to Key Issue #12 about unicast communication and key refresh | KPN N.V;.Huawei; HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214322 | Update to conclusion KI#5 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214323 | Conclusion for KI#16 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214029 | A new solution to address KI#17 | Huawei, HiSilicon | pCR | Approval | No |
Yes
| revised | No | S3‑214278 | |||
S3‑214345 | Conclusion for control plane solutions for KI#3, KI#4, KI#9 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑214213 | |||
S3‑214346 | Updates Solution #42 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑214298 | |||
S3‑214348 | Update Solution 37: Modification to ensure source authenticity in restricted discovery for relay and group discovery | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑214297 | |||
S3‑214354 | Update to solution #32 to address privacy issues with User Info ID (KI#5) | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑214321 | |||
S3‑214363 | ProSe: New solution PC5 anchor key generation via GBA Push | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑214211 | |||
S3‑214374 | Update the conclusion to KI#12 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214004 | |||
S3‑214375 | P-TID Privacy protection in solution 39 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214040 | |||
S3‑214376 | resolving the EN on Kausf desych and key lifetime | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214041 | |||
S3‑214395 | ProSe: Update to Solution #40 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑214170 | |||
S3‑214396 | ProSe: Evaluation Update for Solution #41 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑214171 | |||
S3‑214404 | TR 33.847 v0.9.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214409 | Presentation of Report TR 33.847-090 FS 5G ProSe Security | CATT | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S3‑214448 | Update of conclusion for Key Issue #13 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
5.8 | Study on security for enhanced support of Industrial IoT | S3‑214199 | Cover sheet - FS IIOT - Presentation and Approval of Report TR 33.851 | Nokia, Nokia Shanghai Bell | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||
5.9 | Study on Security Aspects of Enhancements for 5G Multicast-Broadcast Services | S3‑214013 | editorial changes to TR 33.850 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑213954 | Conclusion for key issue 1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑214407 | |||
S3‑213956 | Update the solution #6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214149 | Conclusion of KI #1 and KI #2 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑214407 | |||
S3‑213955 | Conclusion for key issue 2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑214407 | |||
S3‑214012 | Update to conclusion on key issue#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214377 | |||
S3‑214011 | Discussion paper on key distribution in interworking between LTE and 5G | Huawei, HiSilicon | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S3‑214020 | Update to conclusion on key issue#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214378 | |||
S3‑214281 | Conclusions KI#3 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214320 | Update Solution#9 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑214412 | |||
S3‑214356 | Presentation of Report to TSG: TR 33.850, Version 0.9.0 | Huawei, HiSilicon | TS or TR cover | Yes |
Yes
| approved | No | |||||
S3‑214368 | TR 33.850 for MBS security | Huawei, Hisilicon | draft TR | Yes |
Yes
| approved | No | |||||
S3‑214377 | Update to conclusion on key issue#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214012 | |||
S3‑214378 | Update to conclusion on key issue#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214020 | |||
S3‑214407 | Conclusion of KI #1 and KI #2 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑214149 | |||
S3‑214412 | Update Solution#9 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑214320 | |||
5.10 | Study on enhanced security support for Non-Public Networks | S3‑213993 | Conclusion for Key Issue #1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214380 | |
S3‑214159 | eNPN: Evaluation of Solution #5 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214160 | pCR: Additional conclusions for KI #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213957 | Resolving ENs in Key Issue #2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213958 | Evaluation of Solution #20 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213959 | Evaluation of Solution #21 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213960 | Conclusion on Key Issue #2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214106 | Conclusion for key issue #2 on PNI-NPN | China Mobile, Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214107 | Add evaluation and system impact to solution#17 | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214175 | eNPN: Conclusion for Key Issue #2 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214283 | Empty conclusion to KI#2 Provisioning of Credentials | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214310 | Conclusion for KI#2 | ORANGE, Deutsche Telekom, Thales, IDEMIA, Giesecke+Devrient | pCR | Approval | Yes |
Yes
| revised | No | S3‑214359 | |||
S3‑214164 | Solution for provisioning PNI-NPN Credential | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214025 | Solution KI#2 using AKMA | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214284 | Empty conclusion to KI#3 Security impacts from supporting IMS voice and IMS services in SNPNs | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑214351 | |||
S3‑213963 | Further conclusion for KI#4 (initial access) | CableLabs | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑213969 | Conclusions for KI#4 (initial access) | Intel Sweden AB,Interdigital, Apple, Philips, Convida, Broadcom, Cablelabs, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑214335 | |||
S3‑213973 | New solution for UE onboarding | LG Electronics | pCR | Approval | Yes |
Yes
| revised | No | S3‑214341 | |||
S3‑213974 | Further conclusion for KI#4 | LG Electronics | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214163 | Update to Solution#23 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑214338 | |||
S3‑214282 | Scope of TR 33.857 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214285 | Presentation of Report to TSG: TR 33.857, Version 0.9.0 | Ericsson | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S3‑214286 | Clean-up of TR 33.857 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214335 | Conclusions for KI#4 (initial access) | Intel Sweden AB,Interdigital, Apple, Philips, Convida, Broadcom, Cablelabs, Lenovo, Motorola Mobility, Qualcomm | pCR | Approval | Yes |
Yes
| approved | No | S3‑213969 | |||
S3‑214338 | Update to Solution#23 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑214163 | |||
S3‑214341 | New solution for UE onboarding | LG Electronics | pCR | Approval | Yes |
Yes
| approved | No | S3‑213973 | |||
S3‑214351 | Empty conclusion to KI#3 Security impacts from supporting IMS voice and IMS services in SNPNs | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑214284 | |||
S3‑214359 | Conclusion for KI#2 | Thales, ORANGE, Deutsche Telekom, Telecom Italia, IDEMIA, Giesecke+Devrient | pCR | Approval | Yes |
Yes
| approved | No | S3‑214310 | |||
S3‑214362 | draft TR 33.857 v0.9.0 | Ericsson | draft TR | Approval | Yes |
Yes
| revised | No | S3‑214540 | |||
S3‑214540 | draft TR 33.857 v0.9.0 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | S3‑214362 | |||
S3‑214380 | Conclusion on KI#1 for key derivation | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑213993 | |||
S3‑214334 | LS on conclusions of authentication methods for initial access for onboarding | Nokia | LS out | Approval | Yes |
Yes
| revised | No | S3‑214541 | |||
S3‑214541 | LS on conclusions of authentication methods for initial access for onboarding | Nokia | LS out | Approval | Yes |
Yes
| approved | No | S3‑214334 | |||
5.11 | Study on User Consent for 3GPP services | S3‑213849 | Test | Test | CR | Approval | No |
Yes
| withdrawn | Yes | ||
S3‑213998 | New solution for naming of purposes | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213999 | Address EN and add evaluation for solution 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214000 | Address EN and add evaluation for solution 4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214381 | |||
S3‑214001 | Conclusion on key issue #3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214382 | |||
S3‑214002 | Conclusion on UDM Service for User Consent Check | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214383 | |||
S3‑214003 | Conclusion on User Consent Check | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214384 | |||
S3‑214225 | [UC3S] Adding evaluation of solution #7 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑214400 | |||
S3‑214226 | [UC3S] Resolving Editor’s Note of solution #7 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214227 | [UC3S] Conclusion for Edge User Consent | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑214401 | |||
S3‑214357 | Presentation of Report to TSG: TR 33.867, Version 0.8.0 | Huawei, HiSilicon | TS or TR cover | Yes |
Yes
| approved | No | |||||
S3‑214364 | Draft TR33.867 | Huawei, HiSilicon | draft TR | Yes |
Yes
| approved | No | |||||
S3‑214381 | Address EN and add evaluation for solution 4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214000 | |||
S3‑214382 | Conclusion on key issue #3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214001 | |||
S3‑214383 | Conclusion on UDM Service for User Consent Check | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑214002 | |||
S3‑214384 | Conclusion on User Consent Check | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214003 | |||
S3‑214400 | [UC3S] Adding evaluation of solution #7 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑214225 | |||
S3‑214401 | [UC3S] Conclusion for Edge User Consent | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑214227 | |||
5.12 | Study on security aspects of the 5GMSG Service | S3‑214370 | Presentation of Report to TSG: TR 33.862, Version 0.7.0 | China Mobile | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||
5.13 | Study on security aspects of enablers for Network Automation (eNA) for the 5G system (5GS) Phase 2 | S3‑214095 | Add conclusion to KI #2.1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑214266 | Inputs to DDoS analysis framework to detect signalling storm | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214267 | Ed Note Removal for KI 1.4 Conclusion | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214268 | Ed Note Removal for Solution 11 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214410 | draft TR 33.866 0.8.0 | China Mobile E-Commerce Co. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214411 | Presentation of Report to TSG: TR 33.866, Version 0.8.0 | China Mobile E-Commerce Co. | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
5.14 | Study on the security of AMF re-allocation | S3‑213832 | LS Response on Clarifications of Network slice selection during AMF Reallocation | S2-2106686 | LS in | Yes |
Yes
| noted | No | |||
S3‑213869 | LS Response on full registration request message to be rerouted via RAN | S2-2107860 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213961 | Update the solution #11 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214119 | Update to Solution #4 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑214339 | |||
S3‑214120 | Update to Solution #12 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑214340 | |||
S3‑213962 | Conclusion for the key issue 1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214117 | Conclusion to KI#1 | Lenovo, Motorola Mobility, Deutsche Telekom, Interdigital, Broadcom, Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214137 | Proposed conclusion for AMF Re-allocation | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | S3‑212850 | |||
S3‑214241 | [AMF re-alloc] Conclution to KI #1 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214245 | Conclusion for the study | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑214350 | |||
S3‑214243 | AMF re-allocation: Discussion about the WID | Ericsson | discussion | Information | Yes |
Yes
| noted | No | ||||
S3‑214242 | Re-route 5G NAS security context via RAN | Samsung | other | Agreement | Yes |
Yes
| noted | No | ||||
S3‑214246 | Security handing of AMF re-allocation via RAN | Ericsson | draftCR | Discussion | Yes |
Yes
| noted | No | ||||
S3‑214339 | Update to Solution #4 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑214119 | |||
S3‑214340 | Update to Solution #12 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑214120 | |||
S3‑214350 | Conclusion for the study | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑214245 | |||
S3‑214353 | Presentation of Report to TSG: TR 33.864, Version 0.7.0 | Ericsson España S.A. | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S3‑214403 | Draft TR 33.864 v0.7.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | Ericsson España S.A. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.16 | Study on Security for NR Integrated Access and Backhaul |   | ||||||||||
5.17 | Study on enhanced Security Aspects of the 5G Service Based Architecture | S3‑214049 | Resolving EN on the subscribe-notify issue | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑214050 | Adding the evaluation for solution #9 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214387 | |||
S3‑214051 | Adding the conclusion for key issue #7 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214052 | Adding the conclusion for key issue #5 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214388 | |||
S3‑214183 | eSBA Editorial updates to 33875-040 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑214184 | eSBA KI#5 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑214365 | |||
S3‑214185 | eSBA KI#4 conclusion | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑214366 | |||
S3‑214186 | eSBA KI#9 Threats | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S3‑214397 | |||
S3‑214198 | Cover sheet - FS eSBA - Presentation of Report TR 33.875 | Nokia, Nokia Shanghai Bell | TS or TR cover | Approval | Yes |
Yes
| revised | No | S3‑214367 | |||
S3‑214223 | [eSBA] KI on inter slice access | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑214397 | |||
S3‑214224 | Solution to KI#9: Authorization for Inter-Slice Access | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑214398 | |||
S3‑214239 | [eSBA] New Solution for Key Issue #3: Authorization of notification endpoint | Samsung, Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑214399 | |||
S3‑214240 | [eSBA] Conclusion for KI#1 | Samsung, Huawei, HisiliconNokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214294 | Solution for Key issue #7: Authorization mechanism determination | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214311 | New KI for Authentication of PLMNs over Roaming Hub | CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214314 | New KI on Authorization of Roaming Hub by PLMN | CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214365 | eSBA KI#5 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑214184 | |||
S3‑214366 | eSBA KI#4 conclusion | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑214185 | |||
S3‑214367 | Presentation of Report TR 33.875-050 FS eSBA Security | Nokia, Nokia Shanghai Bell | TS or TR cover | Approval | Yes |
Yes
| approved | No | S3‑214198 | |||
S3‑214369 | TR 33.875-050 eSBA Security | Nokia, Nokia Shanghai Bell | draft TR | Yes |
Yes
| approved | No | |||||
S3‑214387 | Adding the evaluation for solution #9 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214389 | S3‑214050 | ||
S3‑214388 | Adding the conclusion for key issue #5 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑214052 | |||
S3‑214389 | Adding the evaluation for solution #9 | Huawei, HiSilicon, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑214387 | |||
S3‑214397 | [eSBA] KI on inter slice access | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑214223 | |||
S3‑214398 | Solution to KI#9: Authorization for Inter-Slice Access | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑214224 | |||
S3‑214399 | [eSBA] New Solution for Key Issue #3: Authorization of notification endpoint | Samsung, Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑214239 | |||
5.18 | Study on enhanced security for network slicing Phase 2 | S3‑213916 | update to KI#1 based on RAN progress | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑213870 | Reply LS on NSAC procedure | S2-2107942 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213917 | update to KI#2 based on SA2 LS | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑214176 | eNS2: Key Issue #2 update | Xiaomi Communication | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑213918 | update to Sol#1 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214361 | |||
S3‑213919 | conclusion to KI# 3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑214371 | |||
S3‑214361 | update to Sol#1 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑213918 | |||
S3‑214371 | conclusion to KI# 3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑213919 | |||
S3‑214373 | draft_TR33.874-050 | Huawei, HiSilicon | draft TR | Yes |
Yes
| approved | No | |||||
5.19 | Study on non-seamless WLAN Offload in 5GS using 3GPP credentials | S3‑213868 | Reply LS on proposed NSWO architecture | S2-2107859 | LS in | Yes |
Yes
| postponed | No | |||
S3‑213889 | Coversheet for TR 33.881 | Nokia, Nokia Shanghai Bell | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S3‑213891 | Discussion on SA2 LS reply on proposed NSWO architecture | Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑214263 | NSWO Solution 1 evaluation | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S3‑214405 | draft TR 33.881 | Nokia Hungary | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6 | CVD and research | S3‑213816 | Attack preventing NAS procedures to succeed | GSMA FSAG | LS in | Yes |
Yes
| withdrawn | Yes | |||
S3‑213812 | [FSAG#94 Doc 003] Reply LS on attack preventing NAS procedures to succeed | C1-215153 | LS in | Yes |
Yes
| noted | No | |||||
S3‑213815 | Stealth Pirating Attack by RACH Rebroadcast Overwriting (SPARROW) | GSMA FSAG | LS in | Yes |
Yes
| noted | No | |||||
S3‑213901 | SPARROW Covert Communication Vulnerability in CRI Rebroadcast: Analysis & Remediation Proposal | KEYSIGHT TECHNOLOGIES | discussion | Action | Yes |
Yes
| noted | No | ||||
S3‑213902 | Padding SUPIs in NAI format with Random Length of Characters for non-null schemes | InterDigital Communications | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑214302 | Concealing the length of NAI format SUPI exposed in SUCI by padding the SUPI before using non-null schemes | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | S3‑213003 | |||
S3‑214332 | Countermeasures against a threat of a service disruption due to unprotected RRC messages proposed by 5G Security Forum in South Korea | SK Telecom | discussion | Yes |
Yes
| noted | No | S3‑213988 | ||||
S3‑213835 | Attack preventing NAS procedures to succeed | GSMA | LS in | No |
Yes
| withdrawn | Yes | |||||
S3‑213988 | Countermeasures against a threat of a service disruption due to unprotected RRC messages proposed by 5G Security Forum in South Korea | SK Telecom | discussion | Yes |
Yes
| revised | No | S3‑214332 | ||||
S3‑214414 | Reply to: Attack preventing NAS procedures to succeed | Huawei Technologies Sweden AB | LS out | Yes |
Yes
| approved | No | |||||
S3‑214415 | Attack preventing NAS procedures to succeed | GSMA | LS in | Yes |
Yes
| replied to | No | |||||
7 | Any Other Business |   |