Tdoc List
2020-03-12 16:24
TDoc | Title | Source | Type | For | Agenda | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|
S3‑200050 | Agenda | WG Chair | agenda |
1Agenda and meeting objectives
| Yes |
Yes
| approved | No | |||
S3‑200051 | LS to 3GPP SA3 to consider appropriate authorization and authentication when providing network slice access | GSMA | LS in |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| replied to | No | |||
S3‑200052 | LS on Sending CAG ID | S2-2001616 | LS in |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200053 | Reply LS on Sending CAG ID in NAS layer | R2-1916349 | LS in |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200054 | Reply LS on PC5S and PC5 RRC unicast message protection | R2-1916461 | LS in |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200055 | Reply LS on LS on PC5S and PC5 RRC unicast message protection | S2-1912002 | LS in |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200056 | Reply LS on PC5 unicast and groupcast security protection | S2-2000971 | LS in |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200057 | LS on NR V2X Security issue and PDCP SN size | R2-1916467 | LS in |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| replied to | No | |||
S3‑200058 | Reply LS on NSI requirements | S1-193596 | LS in |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200059 | Reply LS on NPN clarifications | S1-193605 | LS in |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200060 | Reply LS on SUCI computation from an NSI | S2-1912417 | LS in |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200061 | Reply LS on token-based authorization for indirect communication with delegated discovery (Scenario D) | S2-1912657 | LS in |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200062 | Reply LS on clarification on the requirement for steering of roaming | S2-1912764 | LS in |
2Incoming LSes
| Yes |
Yes
| noted | No | |||
S3‑200063 | LS on Further clarifications on GLI/GCI and Line ID/ HFC_Identifier | S2-1912767 | LS in |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200064 | Reply LS on 5G-S-TMSI Truncation Procedure | S2-2001248 | LS in |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200065 | Reply LS to Transfer the study on service-based support for SMS in 5GC to CT WGs | SP-191362 | LS in |
2Incoming LSes
| Yes |
Yes
| postponed | No | |||
S3‑200066 | Reply LS to LS on analytics support for energy saving | SP-191378 | LS in |
2Incoming LSes
| Yes |
Yes
| noted | No | |||
S3‑200067 | Reply LS on AUSF role in slice specific authentication | S2-1910668 | LS in |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200068 | LS on security consideration of performance measurement function protocol | C1-196940 | LS in |
2Incoming LSes
| Yes |
Yes
| postponed | No | |||
S3‑200069 | Reply LS on how the IWF obtains key material for interworking group and private communications | S6-192194 | LS in |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200070 | LS on native 5G NAS security context activation | C1-199003 | LS in |
2Incoming LSes
| Yes |
Yes
| replied to | No | |||
S3‑200071 | LS on ARPF in UDICOM | C4-195553 | LS in |
2Incoming LSes
| Yes |
Yes
| postponed | No | |||
S3‑200072 | LS on uniqueness of PEI in certain FN-RG configurations | s3i200069 | LS in |
2Incoming LSes
| Yes |
Yes
| postponed | No | |||
S3‑200073 | TS 33.536 - Security procedure for unicast messages over PC5 | InterDigital Communications | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200507 | |
S3‑200074 | TS 33.536 - Privacy protection procedure for unicast messages over PC5 | InterDigital Communications | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200510 | |
S3‑200075 | TS 33.536 - Privacy protection requirements for unicast messages over PC5 | InterDigital Communications | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200496 | |
S3‑200076 | TS 33.536 - Security requirements for unicast messages over PC5 | InterDigital Communications | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200496 | |
S3‑200077 | Security requirements for unicast mode | Oy LM Ericsson AB | pCR | Agreement |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200496 | |
S3‑200078 | Discussion on the Support of Multi-CU-UP connectivity in Rel-17 | China Telecom Corporation Ltd. | discussion | Discussion |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200079 | Study on the security of Multi-CU-UP connectivity | China Telecom,CATT,Xiaomi,vivo | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| revised | No | S3‑200341 | |
S3‑200080 | [33.180] R16 - Formatting corrections | Motorola Solutions Danmark A/S | CR | Agreement |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200081 | [33.180] R16 - MC Gateway security | Motorola Solutions Danmark A/S | CR | Agreement |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| revised | No | S3‑200514 | |
S3‑200082 | [33.434] SEAL key management procedure | Motorola Solutions Danmark A/S | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200083 | AGF-side SEG option | Juniper Networks | CR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200084 | [33.180] R16 MC location authorization | Motorola Solutions Danmark A/S | CR | Agreement |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200085 | TS 33.536 - Common Security Requirement over NR PC5 | LG Electronics Inc. | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200086 | TS 33.536 - Common Security Procedure over NR PC5 | LG Electronics Inc. | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200087 | TS 33.536 - Text for general clauses | LG Electronics Inc. | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200088 | TS 33.536 - Clean-up for broadcast and groupcast | LG Electronics Inc. | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200089 | Reply LS to RAN2 on FBS detection | Huawei, HiSilicon | LS out | Approval |
2Incoming LSes
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200090 | VAL Client authentication | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200091 | [Draft CR]Solution for IAB Architecture (Baseline version) | Samsung | draftCR | Approval |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| revised | No | S3‑200443 | |
S3‑200092 | Security requirement update in clause 5.1 | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200093 | [Draft CR] F1 interface set-up procedure | Samsung, Thales, Nokia, Nokia Shanghai Bell | draftCR |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200094 | Security for SEAL interfaces | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200095 | Annex X: OpenID Connect | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200096 | [Draft CR] Cleanup of IAB draft CR | Samsung | draftCR |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| approved | No | |||
S3‑200097 | Terminology alignment | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200098 | Group key management in SEAL | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200099 | Key generation and distribution in SEAL | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200100 | Security policy handling for NR PC5 | SAMSUNG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200101 | AKMA key derivation | SAMSUNG | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200102 | UP security in TSC | SAMSUNG | CR | Approval |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200103 | Wayforward for UP security in TSC | SAMSUNG | discussion | Discussion |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200104 | Alignment of the term NPN | SAMSUNG | CR | Approval |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200105 | NF and NRF mutual Authentication during Indirect communication | Mavenir, Deutsche Telekom AG | discussion | Endorsement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200106 | Clarification of Indirect Communication Mutual Authentication | Mavenir, Deutsche Telekom AG, Nokia | CR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200107 | V2X UE source IP address randomization | Futurewei Technologies | discussion | Discussion |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200108 | eV2X UE source IP address randomization | Futurewei Technologies | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200109 | Referencing Annex I for non-public networks in untrusted non-3GPP access case | CableLabs, Nokia, Nokia Shanghai Bell, Charter Communications | CR | Approval |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200110 | [33.180] R16 SeGy IWF corrections | Motorola Solutions Danmark A/S | CR | Agreement |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| revised | No | S3‑200515 | |
S3‑200111 | Discussion paper on SA2 LS S2-2001730 on AMF reallocation via RAN r-routing | Nokia Germany | discussion | Endorsement |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200112 | draft reply LS to SA2 LS S2-2001730 on AMF reallocation | Nokia Germany | other | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200113 | draft reply LS to CT1 LS S3-200070 on activating 5G native NAS context | Nokia Germany | other | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200114 | draft reply LS to CT1 on PMF protocol security | Nokia Germany | other | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200115 | draft reply LS to SA2 LS on AUSF role in slice specific authentication | Nokia Germany | other | Agreement |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200116 | Discussion paper on AUSF role for Network Slice specific authentication | Nokia Germany | discussion | Endorsement |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200117 | Enhanced Network Slicing living CR from SA3#97 | Nokia Germany | other |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200118 | draft CR for clause x.x.3 Slice specific authentication of living CR | Nokia Germany | other | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200119 | draft CR for clause x.x.4 of Enhanced Network Slicing Living CR | Nokia Germany | other |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200120 | draft CR for clause x.x.5 AAA triggered revocation of eNS living CR | Nokia Germany | other | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200121 | draft CR for clause 14 AUSF services of eNS living CR | Nokia Germany | other |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200122 | Discussion on GSMA LS 5GSTF20_001 on appropriate authentication for Network slice | Nokia Germany | other | Agreement |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200123 | draft reply to GSMA LS 5GSTF20_001 on NS authentication | Nokia Germany | other | Agreement |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| merged | No | S3‑200442 | |
S3‑200124 | Discussion on V2X LS R2-1916467 | Nokia Germany | other | Agreement |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200125 | draft reply LS to RAN2 on V2X PDCP SN size and security | Nokia Germany | other | Agreement |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200126 | reply LS on security consideration of performance measurement function protocol | ZTE Corporation | LS out | Approval |
2Incoming LSes
| Yes |
Yes
| noted | No | ||
S3‑200127 | Discussion on AMF Reallocation via RAN re-routing | ZTE Corporation | discussion | Endorsement |
2Incoming LSes
| Yes |
Yes
| noted | No | ||
S3‑200128 | reply LS on AMF Reallocation via RAN re-routing | ZTE Corporation | LS out | Approval |
2Incoming LSes
| Yes |
Yes
| noted | No | ||
S3‑200129 | Adding UDM to AKMA reference model | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200511 | |
S3‑200130 | AKMA anchor key identifier update | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200131 | resolve EN in clause 6.1 | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| merged | No | S3‑200513 | |
S3‑200132 | resolve EN in clause 6.2 | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200133 | AKMA anchor Key push | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200134 | network initials AKMA anchor key update | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200135 | UE initials AKMA anchor key update | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200136 | Update 6.2 | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200512 | |
S3‑200137 | Corrections in clause 6.1.2-R16 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200138 | Corrections in clause 6.1.2-R15 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200139 | Clarification for distribution of subscriber identities and security data in clause 6.3.1.2-R16 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200140 | Clarification for distribution of subscriber identities and security data in clause 6.3.1.2-R15 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200141 | remove the EN in clause 6.8.1.2.4-R16 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200142 | remove the EN in clause 6.8.1.2.4-R15 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200143 | Security handling in registration with AMF re-allocation via direct NAS reroute-R16 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200144 | Security handling in registration with AMF re-allocation via direct NAS reroute-R15 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200145 | remove the EN in clause 13.2.3.6-R16 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200146 | remove the EN in clause 13.2.3.6-R15 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200147 | Remove the EN in clause 13.5-R16 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200148 | Remove the EN in clause 13.5-R15 | ZTE Corporation | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200149 | Discussion on AUSF role | Huawei, HiSilicon | discussion | Endorsement |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200150 | Draft LS reply to SA2 on AUSF | Huawei, HiSilicon | LS out | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200151 | Draft LS reply to GSMA on slice access | Huawei, HiSilicon | LS out | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| revised | No | S3‑200442 | |
S3‑200152 | Discussion paper for Rel17 SID on UAS | Huawei, HiSilicon, China Unicom, CATT | discussion | Discussion |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200153 | Study on security aspects of UAS Remote Identification and Application | Huawei, HiSilicon, China Unicom, CATT | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200154 | Discussion paper for Rel17 SID on network slicing security | Huawei, HiSilicon | discussion | Discussion |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200155 | New SID on security aspects of network slicing - RAN and Phase 2 | Huawei, HiSilicon | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200156 | Security procedures for network slices | Huawei, HiSilicon | draftCR | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200157 | Addressing ENs in security procedures for network slices | Huawei, HiSilicon | draftCR | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200158 | Addessing EN on transmitting NSSAI to AAA | Huawei, HiSilicon | draftCR | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200159 | CR to slice management on NSaaS | Huawei, HiSilicon | draftCR | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200160 | Adding UP security policy for 5GLAN groups | Huawei, HiSilicon | draftCR | Approval |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200455 | |
S3‑200161 | Discussion paper on eV2X groupcast privacy | Huawei, HiSilicon | discussion | Discussion |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200162 | Adding privacy procedures for V2X Groupcast communications | Huawei, HiSilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200163 | VAL Client authentication | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| revised | No | S3‑200451 | |
S3‑200164 | Security requirement update in clause 5.1 | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200165 | Security procedure for SEAL interfaces | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| merged | No | S3‑200493 | |
S3‑200166 | Annex X: OpenID Connect | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| revised | No | S3‑200452 | |
S3‑200167 | Terminology alignment | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200168 | Group key management in SEAL | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200169 | Key generation and distribution in SEAL | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200170 | Security policy handling for NR PC5 | SAMSUNG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200507 | |
S3‑200171 | AKMA key derivation | SAMSUNG | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200172 | UP security in TSC | SAMSUNG | CR | Approval |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200173 | Wayforward for UP security in TSC | SAMSUNG | discussion | Discussion |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200174 | Alignment of the term NPN | SAMSUNG | CR | Approval |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200175 | Reply LS to LS on native 5G NAS security context activation | Intel Corporation (UK) Ltd | LS out | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| revised | No | S3‑200517 | |
S3‑200176 | Security of RRC UE capability transfer procedure in 5G for CIoT optimisation | Intel Corporation (UK) Ltd | draftCR |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200177 | Procedure to transfer UE capability for UEs without AS Security | Intel Corporation (UK) Ltd | discussion | Agreement |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200178 | New SID on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) | Intel Corporation (UK) Ltd | SID new |
4New work and study item proposals
| Yes |
Yes
| noted | No | |||
S3‑200179 | Discussion on new SID Security Study on system enablers for devices having multiple USIMS | Intel Corporation (UK) Ltd | discussion |
4New work and study item proposals
| Yes |
Yes
| noted | No | |||
S3‑200180 | Security of RRC UE capability transfer procedure in EPS | Intel Corporation (UK) Ltd | CR |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| revised | No | S3‑200516 | ||
S3‑200181 | Add description of the KAKMA Key ID allocation | CATT | draftCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200182 | Add the functionalities of the AUSF into clause 4.2 | CATT | draftCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200183 | Modification on the RRC connection resume procedure | CATT | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200184 | Discussion for AS rekeying failure on Xn-Handover | CATT | discussion | Decision |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200185 | Clarification on AS rekeying failure | CATT | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200186 | Clarification on the Xn-Handover procedure | CATT | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200187 | LS reply to RAN WG2 LS on NR V2X Security issue and PDCP SN size | CATT | LS out | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200478 | |
S3‑200188 | Adding a clause of "Threats related to key reuse" for the eNB | Nokia, Nokia Shanghai Bell, Telecom Italia, NTT DoCoMo | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200502 | |
S3‑200189 | Draft CR as a living baseline for 5GS LCS normative work | CATT | draftCR | Approval |
3.7Security of the enhancement to the 5GC location services
| Yes |
Yes
| approved | No | ||
S3‑200190 | Removing ENs in Draft CR as a living baseline for 5GS LCS normative work | CATT | draftCR | Approval |
3.7Security of the enhancement to the 5GC location services
| Yes |
Yes
| noted | No | ||
S3‑200191 | Updating the clause of "Key Reuse" for the gNB | Nokia, Nokia Shanghai Bell, Telecom Italia, NTT DoCoMo | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200503 | |
S3‑200192 | Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | CATT | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200193 | Authorization in the Subscribe-Notify interaction scenarios | Huawei, Hisilicon | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200194 | Resource-based authorization | Huawei, Hisilicon | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200195 | Discussion on authentication result removal | Huawei, Hisilicon | discussion | Endorsement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200196 | JSON object modification - R15 | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200197 | JSON object modification - R16 | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200198 | SUCI computation clarification - R15 | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200199 | SUCI computation clarification - R16 | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200200 | compatibility issue in resume request protection | Huawei, Hisilicon | draftCR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200201 | New test case on NAS integrity protection | Huawei, Hisilicon | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200473 | |
S3‑200202 | Solving registration failure in registration procedure with AMF reallocation | Huawei, Hisilicon CMCC,ChinaTelecom | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200203 | Clarification on AMF reallocation via direct NAS reroute | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| No |
Yes
| withdrawn | Yes | ||
S3‑200204 | Clarification on AMF reallocation via direct NAS reroute | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200205 | Discussion on horizontal Kamf derivation in direct NAS reroute | Huawei, Hisilicon | discussion | Endorsement |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200206 | Discussion on AMF reallocation | Huawei, Hisilicon CMCC,ChinaTelecom | discussion | Endorsement |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200207 | Discussion on slice separation | Huawei, Hisilicon | discussion | Endorsement |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200208 | LS reply to SA2 on AMF reallocation | Huawei, Hisilicon | LS out | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200209 | Clarification on confidential IEs replacement handling in original N32-f message | Huawei, Hisilicon | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200210 | Clarification on the clause 4.3.6.4 according to TS 29.501 | Huawei, Hisilicon | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200497 | |
S3‑200211 | eV2X: PC5 UP security policy activation | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200468 | |
S3‑200212 | eV2X: PC5 key hierarchy | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200501 | |
S3‑200213 | Discussion on CAG access control authorization | Huawei, Hisilicon | discussion | Endorsement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200214 | New SID: Study on Security Aspects of Enhancement of Support for Edge Computing in 5GC | Huawei, Hisilicon, China Unicom, CAICT, China Telecom, ZTE | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200215 | Clarification on NF consumer instance ID verification | Huawei, Hisilicon | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200216 | AKMA: Key ID generation | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200499 | |
S3‑200217 | Clarification on exposure of confidential IEs in N32-f message in TR 33.926 | Huawei, Hisilicon | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200218 | eV2X: requirements for algorithm | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200508 | |
S3‑200219 | eV2X: Discussion on LC ID used for PDCP protection | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200220 | Clarification on native 5G NAS security context activation after an inter-system change from S1 mode to N1 mode in idle mode in Rel15 | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200221 | Mirror for clarification on native 5G NAS security context activation after an inter-system change from S1 mode to N1 mode in idle mode in Rel16 | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200222 | [DRAFT] Reply LS on native 5G NAS security context activation | Huawei, Hisilicon | LS out | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200223 | Clarification on PLMN ID verification | Huawei, Hisilicon | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200498 | |
S3‑200224 | Clarification on IPX certificate acquirement in SEPP | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200225 | Mirror for clarification on IPX certificate acquirement in SEPP | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200226 | Address the ENs on Security procedures for Small Data Transfer in Control Plane CIoT 5GS Optimisation | Huawei, Hisilicon | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| revised | No | S3‑200474 | |
S3‑200227 | Address EN for Calculation of ShortResumeMAC-I for UP CIoT Optimisation | Huawei, Hisilicon | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200228 | Address the ENs on Security handling in User Plane CIoT 5GS Optimisation | Huawei, Hisilicon | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| revised | No | S3‑200475 | |
S3‑200229 | Security handling for UP data protection for UP CIoT 5GS Opmitization | Huawei, Hisilicon | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| revised | No | S3‑200476 | |
S3‑200230 | UE handling on CHO key derivation for NR | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| revised | No | S3‑200477 | |
S3‑200231 | UE handling on CHO key derivation for LTE | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| revised | No | S3‑200479 | |
S3‑200232 | Include Resume Request Message to Calculation of ShortResumeMAC-I for INACTIVE | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200233 | Authentication in PNI-NPN | Huawei, Hisilicon | CR | Approval |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200480 | |
S3‑200234 | Adding SEAL security requirements | Huawei, Hisilicon | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| revised | No | S3‑200492 | |
S3‑200235 | Adding security requirements of interfaces for SEAL | Huawei, Hisilicon | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| revised | No | S3‑200493 | |
S3‑200236 | Adding authorization procedures of SEAL system | Huawei, Hisilicon | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| revised | No | S3‑200494 | |
S3‑200237 | Adding SEAl security procedures for interconnection | Huawei, Hisilicon | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| revised | No | S3‑200495 | |
S3‑200238 | adding V2X groupcast privacy requirement | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200239 | Adding V2X unicast security requirements | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200496 | |
S3‑200240 | Adding V2X common requirements | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200241 | Adding abbreviations to the V2X TS | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200242 | Update testcases of eNB SCAS | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200243 | Mirror - Update testcases of eNB SCAS | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200244 | Clarification on UP security activation | Huawei, Hisilicon | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| revised | No | S3‑200472 | |
S3‑200245 | Removing EN | Huawei, Hisilicon | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| revised | No | S3‑200469 | |
S3‑200246 | Living of URLLC | Huawei, Hisilicon | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| revised | No | S3‑200471 | |
S3‑200247 | Living of 5WWC | Huawei, Hisilicon | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| revised | No | S3‑200467 | |
S3‑200248 | Update clause 4.1 | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200249 | Editoral change on clause 4.3 | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200250 | Adding AF under Network element clause | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200460 | |
S3‑200251 | Adding NEF under the Network element clause | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200461 | |
S3‑200252 | Delete EN of clause 4.4 | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200253 | Delete EN of clause 5.2 | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| merged | No | S3‑200447 | |
S3‑200254 | life time of Key identifier | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200255 | The time when the key identifier is generated | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| merged | No | S3‑200486 | |
S3‑200256 | KAKMA Derivation | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| merged | No | S3‑200513 | |
S3‑200257 | AAnF checks the authorization information of AF | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200463 | |
S3‑200258 | Add details on deleting Kakma | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200259 | Kaf update procedure | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200260 | Editoral Change on reference clauses | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| No |
Yes
| withdrawn | Yes | ||
S3‑200261 | Discussion for 5G SCAS Enhancement | Huawei, Hisilicon | discussion | Discussion |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200262 | New WID for 5G SCAS Enhancement | Huawei, Hisilicon | WID new | Approval |
4New work and study item proposals
| Yes |
Yes
| revised | No | S3‑200459 | |
S3‑200263 | CR on requirements for algorithm selection and handover from EPS to 5GS over N26 | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200264 | CR on requirements for algorithm selection and handover from EPS to 5GS over N26 | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200265 | Discussion paper on UE radio capability protection for UEs without AS security | Huawei, HiSilicon,China Mobile | discussion | Discussion |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200266 | Protection of UE radio capability transfer for CIoT UEs that only support CP optimization | Huawei, HiSilicon,China Mobile | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200267 | Discussion on security of 5G multicast-broadcast services | Huawei, Hisilicon | discussion | Endorsement |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200268 | New SID: Study on Security Aspects of Enhancements for 5G Multicast-Broadcast Services | Huawei, Hisilicon | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200269 | Add clarifications to the living CR | Huawei, Hisilicon | draftCR | Approval |
3.7Security of the enhancement to the 5GC location services
| Yes |
Yes
| noted | No | ||
S3‑200270 | Add requirement and feature to the DraftCR | Huawei, Hisilicon | draftCR | Approval |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| revised | No | S3‑200458 | |
S3‑200271 | Correction to security capability negotiation between SEPPs | Huawei, HiSilicon,China Mobile | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200272 | Correction to security capability negotiation between SEPPs | Huawei, HiSilicon,China Mobile | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200273 | Correction to initial EAP Authentication with an external AAA server | Huawei, HiSilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200274 | Correction to initial EAP Authentication with an external AAA server | Huawei, HiSilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200275 | Correction to definition about temporary group call related procedures | Huawei, HiSilicon | CR | Approval |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200276 | Correction to definition about the case of 'Temporary group call – user regroup'' | Huawei, HiSilicon | CR | Approval |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200277 | Security requirements for UP Gateway Function | Huawei, HiSilicon | CR | Approval |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| revised | No | S3‑200481 | |
S3‑200278 | Reply LS to S2-2001727 on UP gateway function on the N9 interface | Huawei, HiSilicon | LS out | Approval |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200279 | New SID: Study on Security Aspects of Enhancement of Support for Edge Applications in 5GC | China Unicom, CAICT, China Telecom, Huawei, Hisilicon, ZTE | SID new |
4New work and study item proposals
| Yes |
Yes
| noted | No | |||
S3‑200280 | New WID on Security Assurance Specification for Non-3GPP InterWorking Function (N3IWF) | China Unicom, CAICT, China Mobile, CATT, ZTE | WID new |
4New work and study item proposals
| Yes |
Yes
| revised | No | S3‑200527 | ||
S3‑200281 | New WID on Study of certificate management for Service Based Architecture (SBA) | Ericsson | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200282 | Resource Level Authorization using Access Tokens | Ericsson, Nokia, Nokia Shanghai Bell | CR | Agreement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| revised | No | S3‑200487 | |
S3‑200283 | Trust model and purpose of token-based authorization in Scenario D | Ericsson | discussion | Information |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200284 | Trust model and token-based authorization for Scenario D | Ericsson | discussion | Endorsement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200285 | Draft-CR as baseline for Token-based authorization for indirect communication with and without delegated discovery | Ericsson | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200286 | Clarifications and corrections for token-based authorization in Scenario C | Ericsson | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200287 | Token-based authorization for Scenario D | Ericsson | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200288 | SCP vs SECOP | Ericsson | discussion | Endorsement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| endorsed | No | ||
S3‑200289 | Identifiers in certificates and authorization tokens | Ericsson | discussion | Endorsement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200290 | Authorization of Subscribe-Notify interactions | Ericsson | discussion | Endorsement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200291 | 3gpp-Sbi_Target-apiRoot header and TLS on N32 | Ericsson | CR | Agreement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| revised | No | S3‑200489 | |
S3‑200292 | draft reply-LS on UP gateway function on the N9 interface | Ericsson | LS out | Approval |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| revised | No | S3‑200482 | |
S3‑200293 | Clarification of implicit lifetime | Ericsson | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200447 | |
S3‑200294 | AUSF selection for AKMA | Ericsson | discussion | Discussion |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200295 | CR to TS 33.501: AUSF Selection for AKMA | Ericsson | draftCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200296 | pCR to TS 33.535: Update of the AKMA procedures | Ericsson | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200297 | pCR to TS 33.535: UE authentication result notification | Ericsson | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200298 | CR to TS 33.501: UE authentication result notification | Ericsson | draftCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200299 | pCR to TS 33.535: Optimization in AKMA key generation | Ericsson | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200300 | CR to TS 33.501: AKMA key generation optimization | Ericsson | draftCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200301 | pCR to TS 33.535: Application function key refresh | Ericsson | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200302 | [Draft CR] Resume identity I-RNTI in RRC Connection Suspend and Resum | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| merged | No | S3‑200475 | |
S3‑200303 | [Draft CR] ShortResumeMAC-I in RRC Connection Suspend and Resume | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| merged | No | S3‑200475 | |
S3‑200304 | [Draft CR] Input to MESSAGE when calculating ShortResumeMAC-I in RRC Connection Suspend and Resume | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200305 | Further evaluation to Solution #25: Security solution for preventing Botnet Attacks from Improper CIOT Device Use | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| No |
Yes
| withdrawn | Yes | ||
S3‑200306 | [Draft CR] Clean up of editor notes from living CR for 5G CIoT | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| merged | No | S3‑200475 | |
S3‑200307 | [Draft CR] Updates to Control Plane CIoT 5GS Optimization | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| revised | No | S3‑200519 | |
S3‑200308 | GUTI allocation for MT-EDT cases | Ericsson | discussion | Endorsement |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200309 | [DRAFT] LS on GUTI allocation for MT-EDT cases | Ericsson | LS out | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200310 | Way forward for UE caps protection and NB-IoT UEs | Ericsson | discussion | Endorsement |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200311 | [Draft CR] RRCReestablishment procedure in 5G CIoT | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200312 | [Draft CR] EDT in User Plane CIoT 5GS Optimization | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| merged | No | S3‑200476 | |
S3‑200313 | CIOT: draft CR Living document | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| revised | No | S3‑200518 | |
S3‑200314 | New SID on Slice isolation | Ericsson | SID new | Agreement |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200315 | VERTICAL: New SID: Study on enhanced security support for Non-Public Networks | Ericsson | SID new | Agreement |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200316 | Informative Annex: Deployment scenarios for end-to-end security | KPN N.V. | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200317 | IKEv2 profile update 33.310 | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| revised | No | S3‑200462 | |
S3‑200318 | Using EAP-TLS with TLS 1.3 | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200319 | ESP profile update | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| revised | No | S3‑200464 | |
S3‑200320 | Recovery from NASC verification failure | MediaTek Inc. | CR |
3.19Other areas (Rel-16)
| Yes |
Yes
| not pursued | No | |||
S3‑200321 | Security requirement for unicast message in PC5 | Apple Computer Trading Co. Ltd | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200496 | |
S3‑200322 | Correction for FN-RG authentication: transport of authentication indication from W-AGF to AMF | Ericsson | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200323 | Corrections for N5CW | Ericsson | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200324 | Corrections for 7B.d | Ericsson | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200325 | Trust indication using UPU | Ericsson | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200326 | Corrections for trusted access | Ericsson | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200327 | TNAP mobility using ERP | Ericsson | discussion | Endorsement |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200328 | Corrections for Annex X | Ericsson, Cablelabs, Charter Communications, Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| revised | No | S3‑200448 | |
S3‑200329 | 3GPP-based access authentication for untrusted non-3GPP access | Ericsson | discussion | Endorsement |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200330 | pCR:3GPP-based access authentication for untrusted non-3GPP access | Ericsson | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200331 | Certificate and CRL profile update | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| revised | No | S3‑200465 | |
S3‑200332 | TLS Recommended Cipher Suites | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200333 | Required TLS extenstions and algorithms | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| revised | No | S3‑200466 | |
S3‑200334 | IKEv2 profile update 33.210 | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200335 | Complete the test cases of key refresh at the eNB | Nokia, Nokia Shanghai Bell, Telecom Italia, NTT DoCoMo | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200504 | |
S3‑200336 | Complete the test cases of key refresh at the gNB | Nokia, Nokia Shanghai Bell, Telecom Italia, NTT DoCoMo | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200505 | |
S3‑200337 | Key derivation for CHO(LTE R16) | Apple Computer Trading Co. Ltd | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| revised | No | S3‑200437 | |
S3‑200338 | Key derivation for CHO(NR R16) | Apple Computer Trading Co. Ltd | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| revised | No | S3‑200436 | |
S3‑200339 | LS on security of eLCS | Ericsson | LS out | Approval |
3.7Security of the enhancement to the 5GC location services
| Yes |
Yes
| noted | No | ||
S3‑200340 | [DRAFT] LS on security consideration of performance measurement function protocol | Apple Computer Trading Co. Ltd | LS out | Approval |
2Incoming LSes
| Yes |
Yes
| noted | No | ||
S3‑200341 | Study on the security of Multi-CU-UP connectivity | China Telecom,China Unicom, CATT, Xiaomi, vivo | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| noted | No | S3‑200079 | |
S3‑200342 | Adding the requirements for the for the security of the NR PC5 unicast link | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200496 | |
S3‑200343 | Proposed solution for the security policy of unicast connections | Qualcomm Incorporated | other | Information |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200344 | Proposed skeleton for the security of unicast link procedures | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200345 | Proposed text for general and overview clauses of NR PC5 unicast security | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200501 | |
S3‑200346 | Proposed text for keying clause of NR PC5 unicast security | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200506 | |
S3‑200347 | Proposed text for security establishment clause of NR PC5 unicast security | Qualcomm Incorporated | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200507 | |
S3‑200348 | Proposed text for security protection clause of NR PC5 unicast security | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200508 | |
S3‑200349 | Annex for key derivation functions in the V2X TS | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200509 | |
S3‑200350 | Allocation of FC values for TS 33.356 | Qualcomm Incorporated, LG | CR | Agreement |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200351 | Proposed requirements for the privacy of NR PC5 unicast connections | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| merged | No | S3‑200496 | |
S3‑200352 | Proposed procedures for the privacy of NR PC5 unicast connections | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200510 | |
S3‑200353 | Discussion on a response LS on AMF Re-allocation | Qualcomm Incorporated | discussion | Information |
2Incoming LSes
| Yes |
Yes
| noted | No | ||
S3‑200354 | Response LS on AMF Reallocation via RAN re-routing | Qualcomm Incorporated | LS out | Approval |
2Incoming LSes
| Yes |
Yes
| noted | No | ||
S3‑200355 | New WID on study of security aspects of Unmanned Aerial Systems | Qualcomm Incorporated | SID new | Agreement |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200356 | Changes made to solution 30 in TR 33.861 | Qualcomm Incorporated | other | Information |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200357 | Protection of UE radio capability transfer for UEs without AS security | Qualcomm Incorporated | other | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200358 | Clarification on native security context activation in handover from EPS to 5GS | Qualcomm Incorporated | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| revised | No | S3‑200490 | |
S3‑200359 | Reply LS on native 5G NAS security context activation | Qualcomm Incorporated | LS out | Approval |
2Incoming LSes
| Yes |
Yes
| noted | No | ||
S3‑200360 | F1 interface set-up procedure | Qualcomm Incorporated, Ericsson | other | Approval |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200361 | Clarification on the use of SUPI as the Identity in EAP-AKA’ key derivation | Qualcomm Incorporated | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200362 | Clarification on the use of SUPI as the Identity in EAP-AKA’ key derivation | Qualcomm Incorporated | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200363 | pCR : Deriving AKMA key after UE is registered to 5GS | Qualcomm Incorporated | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200486 | |
S3‑200364 | pCR : Initiation of AKMA | Qualcomm Incorporated | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200365 | pCR : Requirements on AKMA Key Identifier | Qualcomm Incorporated | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200366 | pCR : Requirements for Ua* | Qualcomm Incorporated | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200367 | URLLC: Resolve EN about MN being preconfigured with SN capability to perform UP IP | Ericsson | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| merged | No | S3‑200469 | |
S3‑200368 | URLLC: Error handling in MN when SN cannot comply with UP security policy | Ericsson | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200369 | URLLC: Pairing of redundant PDU sessions in MN | Ericsson | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200370 | Clarification to TSC UP security policy | Ericsson | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200371 | 5GLAN UP security policy | Ericsson | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200372 | AMF reallocation and slicing | Ericsson | discussion | Endorsement |
3.19Other areas (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200373 | Editoral Change on reference clauses | Huawei, Hisilicon | CR | Approval |
3.3Security aspects of single radio voice continuity from 5GS to UTRAN (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200374 | Reply LS on ARPF in UDICOM | Ericsson | LS out | Approval |
2Incoming LSes
| Yes |
Yes
| noted | No | ||
S3‑200375 | VLAN intro added | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200376 | Resolution of ed note on serving network name | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200377 | KI on interworking NPN and PLMN - security req | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200378 | KI on service continuity - threats and reqs | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200379 | Resolution of editors note on AAA | Nokia, Nokia Shanghai Bell | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200380 | Threats and requirements on AAA | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200381 | Resolution of editor's note in solution 1 | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200382 | Resolution of editor's note in solution 15 | Nokia, Nokia Shanghai Bell | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200383 | UP security policy enforcement in 5GLAN | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200384 | UP security policy enforcement in 5GLAN | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200455 | |
S3‑200385 | Referencing Annex for use of authentication methods | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200456 | |
S3‑200386 | Clarifications on authentication methods selection and key derivation | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200457 | |
S3‑200387 | Modification of CAG ID list | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200388 | Definition of SN Id for standalone non-public networks | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200389 | UP integrity enforcement for gPTP messages | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200454 | |
S3‑200390 | Reference correction in key hierarchy | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200391 | Derivation of KAF | China Mobile, Nokia, Nokia Shanghai Bell | pCR |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200392 | Derivation of KAKMA and related key identifier | China Mobile, Nokia, Nokia Shanghai Bell | pCR |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200513 | ||
S3‑200393 | LS on transformation of S-NSSAI during NSSAA | China Mobile | LS out | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200394 | Work Item on Security Assurance Specification for 5G NWDAF | China Mobile, China Unicom, CAICT, ZTE | WID new | Approval |
4New work and study item proposals
| Yes |
Yes
| revised | No | S3‑200525 | |
S3‑200395 | New SID on security aspects of UAS Connectivity, Identification, and Tracking | China Mobile | SID new | Approval |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200396 | Discussion on new SID for security of UAS Connectivity, Identification, and Tracking | China Mobile | discussion | Discussion |
4New work and study item proposals
| Yes |
Yes
| noted | No | ||
S3‑200397 | A new test case for key update at the gNB on dual connectivity | Nokia, Nokia Shanghai Bell, NTT DoCoMo,Telecom Italia | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200398 | New test cases for key update at the eNB on dual connectivity | Nokia, Nokia Shanghai Bell,Telecom Italia | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200399 | Protection of N9 interface | Nokia, Nokia Shanghai Bell, Juniper Networks | CR | Agreement |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| revised | No | S3‑200530 | S3‑194444 |
S3‑200400 | draftCR on addessing EN on transmitting NSSAI to AAA | China Mobile | other |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200401 | Security requirements for Inter-PLMN User Plane Security (IPUPS) function | Nokia, Nokia Shanghai Bell, Juniper Networks | CR | Agreement |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| merged | No | S3‑200481 | |
S3‑200402 | Resolving editor's note on namespace: pCR against living baseline for 5GS LCS normative work S3-194465 | NTT DOCOMO INC. | other | Agreement |
3.7Security of the enhancement to the 5GC location services
| Yes |
Yes
| noted | No | ||
S3‑200403 | eSBA - pCR to update Solution #21 | Nokia, Nokia Shanghai Bell | pCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200404 | eSBA: pCR to update Conclusion on KI #22 | Nokia, Nokia Shanghai Bell | pCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200405 | Validation of Access Token ownership | Mavenir, Deutsche Telekom AG | CR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200406 | Token Based Authorization – Validation of client ownership of the access token | Mavenir, Deutsche Telekom AG | discussion | Endorsement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200407 | Clarification on Token Based Authorization | Mavenir | discussion | Endorsement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| No |
Yes
| withdrawn | Yes | ||
S3‑200408 | eSBA: Token-based authorization in indirect communication scenario with delegated discovery (Model D) | Nokia, Nokia Shanghai Bell | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200409 | New WID on Security Assurance Specification for Service Communication Proxy (SECOP) | Nokia, Nokia Shanghai Bell, Deutsch Telecom, T-Mobile USA, China Mobile, China Unicom | WID new | Approval |
4New work and study item proposals
| Yes |
Yes
| revised | No | S3‑200526 | |
S3‑200410 | eSBA: Mutual Authentication between NFs | Nokia, Nokia Shanghai Bell | CR | Agreement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200411 | Clarification on Token Based Authorization | Mavenir,Deutsche Telekom | CR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200412 | eSBA: NF consumer authentication by the producer in direct communication scenarios | Nokia, Nokia Shanghai Bell | CR | Agreement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200413 | ERP for TNAP mobility | Motorola Mobility, Lenovo | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200414 | eSBA: Network Function TLS certificate profile | Nokia, Nokia Shanghai Bell, CommScope | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| No |
Yes
| withdrawn | Yes | ||
S3‑200415 | SUCI computation: test data Rel-15 | THALES | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200416 | 5WWC: Update to Subscriber privacy for wireline access | Nokia, Nokia Shanghai Bell, CableLabs | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200417 | SUCI computation: test data Rel-16 | THALES | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200418 | Identifier conversion in groupcast communication | Motorola Mobility, Lenovo | CR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200419 | CryptPr: Update to clause 6.1.1 - Common rules to all certificates | Nokia, Nokia Shanghai Bell, CommScope | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200420 | CryptPr: Update to CRL Profile in clause 6.1a | Nokia, Nokia Shanghai Bell, CommScope | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| not pursued | No | ||
S3‑200421 | eSBA: Network Function TLS certificate profile | Nokia, Nokia Shanghai Bell, CommScope | draftCR | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200422 | LS on AMF Reallocation via RAN re-routing | S2-2001730 | LS in |
3.19Other areas (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200423 | AGF in 5GC trust domain | Juniper Networks, Ericsson | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| withdrawn | Yes | ||
S3‑200424 | Identifier conversion in groupcast communication | Motorola Mobility Germany GmbH | pCR |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| noted | No | |||
S3‑200425 | Comments on S3-200289 Identifiers in certificates and authorization tokens | Huawei, Hisilicon | discussion | Discussion |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200426 | Comments on S3-200290 Authorization of Subscribe-Notify interactions | Huawei, Hisilicon | discussion | Discussion |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| revised | No | S3‑200427 | |
S3‑200427 | Comments on S3-200290 Authorization of Subscribe-Notify interactions | Huawei, Hisilicon | discussion | Discussion |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| noted | No | S3‑200426 | |
S3‑200428 | Process for SA3#98e electronic meeting | WG chair | other | Information |
1Agenda and meeting objectives
| Yes |
Yes
| noted | No | ||
S3‑200429 | Meeting minutes of AKMA conference call for SA3#98e | China Mobile | report | Information |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200430 | Mandatory User Plane Integrity for 5G | GSMA | LS in |
2Incoming LSes
| Yes |
Yes
| postponed | No | |||
S3‑200431 | CR to TS 33.501 to clarify support for User Plane Integrity Protection in NR | VODAFONE Group Plc | CR | Endorsement |
3.19Other areas (Rel-16)
| No |
Yes
| withdrawn | Yes | ||
S3‑200432 | CIoT - meeting minutes of conf call on UE caps and suspend/resume | Nanjing Ericsson Panda Com Ltd | report | Information |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| noted | No | ||
S3‑200433 | LS to SA3 on NR V2X Security issues | R2-2001980 | LS in |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| postponed | No | |||
S3‑200434 | Reply LS to LS S3-194452 on UP gateway function on the N9 interface | S2-2001727 | LS in |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| replied to | No | |||
S3‑200435 | Clarification on native security context activation in handover from EPS to 5GS | Qualcomm Incorporated | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200436 | Key derivation for CHO(NR R16) | Apple Computer Trading Co. Ltd | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200338 | |
S3‑200437 | Key derivation for CHO(LTE R16) | Apple Computer Trading Co. Ltd | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200337 | |
S3‑200438 | draft TS 33.535 | China Mobile | draft TS | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200523 | |
S3‑200439 | WI exception request for eV2X | LG Electronics Inc. | WI exception request |
4New work and study item proposals
| Yes |
Yes
| agreed | No | |||
S3‑200440 | draft_TS 33.536 v0.3.0 | LG Electronics Inc. | draft TS |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| revised | No | S3‑200528 | ||
S3‑200441 | Rel-16 Work Item Exception for 5G_eSBA | Nokia, Nokia Shanghai Bell | WI exception request | Approval |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200442 | LS reply to GSMA on slice access | Huawei, HiSilicon | LS out | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| approved | No | S3‑200151 | |
S3‑200443 | [Draft CR]Solution for IAB Architecture (Baseline version) | Samsung | draftCR | Approval |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| approved | No | S3‑200091 | |
S3‑200444 | Solution for IAB Architecture - 5GC | Samsung, Ericsson, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Thales, Intel, Huawei, HiSilicon, AT&T | CR | Agreement |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200445 | Solution for IAB Architecture - ENDC | Samsung, Ericsson, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Thales, Intel, Huawei, HiSilicon, AT&T | CR |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| agreed | No | |||
S3‑200446 | Rel-16 Work Item Exception for Security for NR IAB | Samsung | WI exception request |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| agreed | No | |||
S3‑200447 | Clarification of implicit lifetime | Ericsson | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200293 | |
S3‑200448 | Corrections for Annex X | Ericsson, Cablelabs, Charter Communications, Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| approved | No | S3‑200328 | |
S3‑200449 | Draft TR 33.434 v0.2.0 | Samsung | draft TS |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | |||
S3‑200450 | Rel-16 Work Item Exception for SEAL security aspects | Samsung | WI exception request |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| agreed | No | |||
S3‑200451 | VAL Client authentication | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | S3‑200163 | |
S3‑200452 | Annex X: OpenID Connect | SAMSUNG | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | S3‑200166 | |
S3‑200453 | WI Exception for Vertical LAN Security | Nokia Germany | WI exception request |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| No |
Yes
| withdrawn | Yes | |||
S3‑200454 | UP integrity enforcement for gPTP messages | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200389 | |
S3‑200455 | UP security policy enforcement in 5GLAN | Nokia, Nokia Shanghai Bell, Interdigital, Huawei, HiSilicon | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200384 | |
S3‑200456 | Referencing Annex for use of authentication methods | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200385 | |
S3‑200457 | Clarifications on authentication methods selection and key derivation | Nokia, Nokia Shanghai Bell, Interdigital | CR | Agreement |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200386 | |
S3‑200458 | Add requirement and feature to the DraftCR | Huawei, Hisilicon | draftCR | Approval |
3.13Security for NR Integrated Access and Backhaul (Rel-16)
| Yes |
Yes
| approved | No | S3‑200270 | |
S3‑200459 | New WID for 5G SCAS Enhancement | Huawei, Hisilicon | WID new | Approval |
4New work and study item proposals
| Yes |
Yes
| agreed | No | S3‑200262 | |
S3‑200460 | Adding AF under Network element clause | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200250 | |
S3‑200461 | Adding NEF under the Network element clause | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200251 | |
S3‑200462 | IKEv2 profile update 33.310 | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200317 | |
S3‑200463 | AAnF checks the authorization information of AF | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200257 | |
S3‑200464 | ESP profile update | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200319 | |
S3‑200465 | Certificate and CRL profile update | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200331 | |
S3‑200466 | Required TLS extensions and algorithms | Ericsson | CR | Agreement |
3.183GPP profiles for cryptographic algorithms and security protocols (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200333 | |
S3‑200467 | Living document of 5WWC | Huawei, Hisilicon | draftCR | Approval |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| approved | No | S3‑200247 | |
S3‑200468 | eV2X: PC5 UP security policy activation | Huawei, Hisilicon | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200211 | |
S3‑200469 | Removing EN | Huawei, Hisilicon | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| approved | No | S3‑200245 | |
S3‑200470 | Exception sheet o fAuthentication and key management for applications based on 3GPP credential in 5G | China Mobile | WI exception request | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| revised | No | S3‑200524 | |
S3‑200471 | Living of URLLC | Huawei, Hisilicon | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| approved | No | S3‑200246 | |
S3‑200472 | Clarification on UP security activation | Huawei, Hisilicon | draftCR | Approval |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200244 | |
S3‑200473 | New test case on NAS integrity protection | Huawei, Hisilicon | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200201 | |
S3‑200474 | Address the ENs on Security procedures for Small Data Transfer in Control Plane CIoT 5GS Optimisation | Huawei, Hisilicon | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| approved | No | S3‑200226 | |
S3‑200475 | Address the ENs on Security handling in User Plane CIoT 5GS Optimisation | Huawei, Hisilicon, Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| approved | No | S3‑200228 | |
S3‑200476 | Security handling for UP data protection for UP CIoT 5GS Opmitization | Huawei, Hisilicon, Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| approved | No | S3‑200229 | |
S3‑200477 | UE handling on CHO key derivation for NR | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200230 | |
S3‑200478 | LS reply to RAN WG2 LS on NR V2X Security issue and PDCP SN size | CATT | LS out | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200187 | |
S3‑200479 | UE handling on CHO key derivation for LTE | Huawei, Hisilicon | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200231 | |
S3‑200480 | Authentication in PNI-NPN | Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | CR | Approval |
3.6Security for 5GS Enhanced support of Vertical and LAN Services (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200233 | |
S3‑200481 | Security requirements for UP Gateway Function | Huawei, Hisilicon, Nokia, Nokia Shanghai Bell, Juniper Networks | CR | Approval |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200277 | |
S3‑200482 | reply-LS on UP gateway function on the N9 interface | Ericsson | LS out | Approval |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| approved | No | S3‑200292 | |
S3‑200483 | exception sheet for 5WWC | Huawei, Hisilicon | WI exception request |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| agreed | No | |||
S3‑200484 | Rel-16 Work Item Exception for CIoT security | Ericsson | WI exception request | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200485 | Security of 5G URLLC | Huawei Device Co., Ltd | CR |
3.5Security of URLLC for 5GS (Rel-16)
| Yes |
Yes
| agreed | No | |||
S3‑200486 | pCR : Deriving AKMA key after UE is registered to 5GS | Qualcomm Incorporated, Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200363 | |
S3‑200487 | Resource Level Authorization using Access Tokens | Ericsson, Nokia, Nokia Shanghai Bell, Huawei | CR | Agreement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200282 | |
S3‑200488 | Rel-16 Network Slice security Exception sheet | Nokia, Nokia Shangahi Bell | WI exception request | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200489 | 3gpp-Sbi_Target-apiRoot header and TLS on N32 | Ericsson, Nokia, Nokia Shanghai Bell | CR | Agreement |
3.8Security Aspects of the 5G Service Based Architecture (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200291 | |
S3‑200490 | Clarification on native security context activation in handover from EPS to 5GS | Qualcomm Incorporated | CR | Approval |
3.19Other areas (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200358 | |
S3‑200491 | Rel-16 Work Item Exception for Security of the enhancement to the 5GC Location Services | CATT | WI exception request | Approval |
3.7Security of the enhancement to the 5GC location services
| Yes |
Yes
| agreed | No | ||
S3‑200492 | Adding SEAL security requirements | Huawei, Hisilicon | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | S3‑200234 | |
S3‑200493 | Adding security requirements of interfaces for SEAL | Huawei, Hisilicon, Samsung | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | S3‑200235 | |
S3‑200494 | Adding authorization procedures of SEAL system | Huawei, Hisilicon | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | S3‑200236 | |
S3‑200495 | Adding SEAl security procedures for interconnection | Huawei, Hisilicon | pCR | Approval |
3.14Security aspects of SEAL (Rel-16)
| Yes |
Yes
| approved | No | S3‑200237 | |
S3‑200496 | Adding the requirements for the for the security of the NR PC5 unicast link | Qualcomm Incorporated, LG, Interdigital, Huawei, Apple | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200342 | |
S3‑200497 | Clarification on the clause 4.3.6.4 according to TS 29.501 | Huawei, Hisilicon | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200210 | |
S3‑200498 | Clarification on PLMN ID verification | Huawei, Hisilicon | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200223 | |
S3‑200499 | AKMA: Key ID generation | Huawei, Hisilicon | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200216 | |
S3‑200500 | Enhanced Network Slicing Living CR | Nokia, Nokia Shangahi Bell, | draftCR | Approval |
3.12Security aspects of Enhancement of Network Slicing (Rel-16)
| Yes |
Yes
| approved | No | ||
S3‑200501 | Proposed text for general and overview clauses of NR PC5 unicast security | Qualcomm Incorporated, LG, Interdigital, Huawei | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200345 | |
S3‑200502 | Adding a clause of "Threats related to key reuse" for the eNB | Nokia, Nokia Shanghai Bell, Telecom Italia, NTT DoCoMo | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200188 | |
S3‑200503 | Updating the clause of "Key Reuse" for the gNB | Nokia, Nokia Shanghai Bell, Telecom Italia, NTT DoCoMo | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200191 | |
S3‑200504 | Complete the test cases of key refresh at the eNB | Nokia, Nokia Shanghai Bell, Telecom Italia, NTT DoCoMo | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200335 | |
S3‑200505 | Complete the test cases of key refresh at the gNB | Nokia, Nokia Shanghai Bell, Telecom Italia, NTT DoCoMo | CR | Approval |
3.1Security Assurance Specification for 5G (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200336 | |
S3‑200506 | Proposed text for keying clause of NR PC5 unicast security | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200346 | |
S3‑200507 | Proposed text for security establishment clause of NR PC5 unicast security | Qualcomm Incorporated, Interdigital, Apple, Huawei, LG, Samsung | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200347 | |
S3‑200508 | Proposed text for security protection clause of NR PC5 unicast security | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200348 | |
S3‑200509 | Annex for key derivation functions in the V2X TS | Qualcomm Incorporated, LG | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200349 | |
S3‑200510 | Proposed procedures for the privacy of NR PC5 unicast connections | Qualcomm Incorporated, LG, Interdigital | pCR | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
Yes
| approved | No | S3‑200352 | |
S3‑200511 | Adding UDM to AKMA reference model | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200129 | |
S3‑200512 | Update 6.2 | ZTE Corporation | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200136 | |
S3‑200513 | Derivation of KAKMA | China Mobile, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Hisilicon, Samsung | pCR | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200392 | |
S3‑200514 | [33.180] R16 - MC Gateway security | Motorola Solutions Danmark A/S | CR | Agreement |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200081 | |
S3‑200515 | [33.180] R16 SeGy IWF corrections | Motorola Solutions Danmark A/S | CR | Agreement |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200110 | |
S3‑200516 | Security of RRC UE capability transfer procedure in EPS | Intel Corporation (UK) Ltd | CR |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200180 | ||
S3‑200517 | Reply LS to LS on native 5G NAS security context activation | Intel Corporation (UK) Ltd | LS out | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| revised | No | S3‑200529 | S3‑200175 |
S3‑200518 | CIOT: draft CR Living document | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| approved | No | S3‑200313 | |
S3‑200519 | [Draft CR] Updates to Control Plane CIoT 5GS Optimization | Ericsson | draftCR | Approval |
3.10Evolution of Cellular IoT security for the 5G System (Rel-16)
| Yes |
Yes
| approved | No | S3‑200307 | |
S3‑200520 | CR on 5G security for 5WWC | Huawei | CR | Agreement |
3.11Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200521 | Cover sheet for TS 33.536 | LG | TS or TR cover | Approval |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
No
| available | No | ||
S3‑200522 | Work Item exception MCXsec | Motorola Solutions | WI exception request | Approval |
3.2Mission Critical security (Rel-16)
| Yes |
Yes
| agreed | No | ||
S3‑200523 | draft TS 33.535 | China Mobile | draft TS | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| approved | No | S3‑200438 | |
S3‑200524 | Exception sheet of Authentication and key management for applications based on 3GPP credential in 5G | China Mobile | WI exception request | Approval |
3.9Authentication and key management for applications based on 3GPP credential in 5G (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200470 | |
S3‑200525 | Work Item on Security Assurance Specification for 5G NWDAF | China Mobile, China Unicom, CAICT, ZTE | WID new | Approval |
4New work and study item proposals
| Yes |
Yes
| agreed | No | S3‑200394 | |
S3‑200526 | New WID on Security Assurance Specification for Service Communication Proxy (SECOP) | Nokia, Nokia Shanghai Bell, Deutsch Telecom, T-Mobile USA, China Mobile, China Unicom | WID new | Approval |
4New work and study item proposals
| Yes |
Yes
| agreed | No | S3‑200409 | |
S3‑200527 | New WID on Security Assurance Specification for Non-3GPP InterWorking Function (N3IWF) | China Unicom, CAICT, China Mobile, CATT, ZTE | WID new | - |
4New work and study item proposals
| Yes |
Yes
| agreed | No | S3‑200280 | |
S3‑200528 | draft_TS 33.536 v0.3.0 | LG Electronics Inc. | draft TS | - |
3.15Security Aspects of 3GPP support for Advanced V2X Services (Rel-16)
| Yes |
No
| available | No | S3‑200440 | |
S3‑200529 | Reply LS to LS on native 5G NAS security context activation | Intel Corporation (UK) Ltd | LS out | Agreement |
3.19Other areas (Rel-16)
| Yes |
Yes
| approved | No | S3‑200517 | |
S3‑200530 | Protection of N9 interface | Nokia, Nokia Shanghai Bell, Juniper Networks | CR | Agreement |
3.16User Plane Gateway Function for Inter-PLMN Security (Rel-16)
| Yes |
Yes
| agreed | No | S3‑200399 |