Tdoc List
2021-06-14 17:03
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Agenda and Meeting Objectives | S3‑211350 | Agenda | SA WG3 Chair | agenda | Yes |
Yes
| approved | No | |||
S3‑211352 | Process for SA3#103e meeting | SA WG3 Chair | other | Yes |
Yes
| revised | No | S3‑211989 | ||||
S3‑211354 | Process and agenda presentation for SA3#103-e | SA3 VC | other | Information | Yes |
Yes
| noted | No | ||||
S3‑211989 | Process for SA3#103e meeting | SA WG3 Vice Chairs | other | Yes |
Yes
| noted | No | S3‑211352 | ||||
2 | Meeting Reports | S3‑211351 | Report from SA3#102Bis-e meeting | MCC | report | Yes |
Yes
| approved | No | |||
S3‑211353 | Report from last SA | SA WG3 Chair | report | Yes |
Yes
| noted | No | |||||
S3‑211361 | Report from SA3#102e | MCC | report | Yes |
Yes
| approved | No | |||||
S3‑212396 | Chair notes of the e-meeting | WG Chair | report | Information | Yes |
No
| available | No | ||||
3 | Reports and Liaisons from other Groups | S3‑211881 | Clarification to SoR transparent container | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| revised | No | S3‑212339 | |
S3‑211366 | 5G capabilities exposure for factories of the future - revised | 5G Alliance for Connected Industries and Automation (5G-ACIA) | LS in | Yes |
Yes
| noted | No | |||||
S3‑211367 | Misalignment on usage of OAuth within 3GPP 29.510 | GSMA | LS in | Yes |
Yes
| postponed | No | |||||
S3‑211368 | AMF transparency for SOR | C1-207736 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211369 | Reply LS on AMF transparency for SOR | C4- 211701 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211370 | LS on extraterritorial use of MCC for satellite access | C1-210439 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211371 | Reply LS on extraterritorial use of MCC for satellite access | S1-210358 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211372 | LS on broadcasting from other PLMN in case of Disaster Condition | C1-211189 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211375 | Reply LS on storage of KAUSF | C1-211518 | LS in | Yes |
YesThe following change captured the CRs S3-212103 (7th change) & S3-212104 (7th change) to TS 33.501 needs to be revisited (for updating it or removing it), based on the feedback from CT1 (c.f., S3-211375 LS from SA3 to CT1).
If UE receives more than one authentication requests via different access types simultaneously (e.g. initial registration after UE powers on, UE initiate the service request procedures simultaneously via both NAS connections), the UE should process the authentication challenges in sequence. The UE should respond to the second authentication challenge after completion of the first authentication procedure. In case if the first authentication procedure is 5G-AKA, then after sending the Authentication Response message to the network the UE should respond to the second authentication challenge and in case if the first authentication procedure is EAP-AKA', then after receiving EAP Success/Failure from the network the UE should respond to the second authentication challenge.
| replied to | No | |||||
S3‑211376 | LS on Secondary AUTH for 5GS interworking with EPS | C3-210377 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211377 | LS on Changes to SoR Delivery Mechanism | C4-205696 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211378 | LS on the Security consideration to support L2TP with CUPS | C4-210171 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211379 | LS on the support of L2TP with CUPS | C4-211624 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211380 | LS on Header Enrichment for HTTPS in PFCP | C4-211662 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211381 | Reply LS on port allocation for the W1 interface | C4-211700 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211384 | Attack preventing NAS procedures to succeed | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S3‑211387 | LS on UE location aspects in NTN | R2-2102055 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211388 | Reply LS on broadcasting gNB ID length in system information block | R2-2102449 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211389 | Remove the user message size limitation for DTLS over SCTP | R3-211274 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211397 | Reply LS on Secondary AUTH for 5GS interworking with EPS | S2-2101305 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211399 | LS on PAP/CHAP and other point-to-point protocols usage in 5GS | S2-2101309 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211407 | 256-bit algorithms based on SNOW 3G or SNOW V | ETSI SAGE | LS in | Yes |
Yes
| postponed | No | |||||
S3‑211408 | Choice of cryptographic algorithm in 256-bit Milenage | ETSI SAGE | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211410 | LS on progress of ongoing work item ITU-T TR-USSD | ITU-T SG11 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211411 | Reply LS on UE location aspects in NTN | S3i210282 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211416 | Reply LS on the support of L2TP with CUPS | S2-2103232 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211419 | Reply to LS on UE location aspects in NTN | S2-2103550 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211420 | Reply LS to SA2 on UE Data Collection | S4-210644 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211421 | LS on Media-Related Services and Requirements | S4-210680 | LS in | Yes |
Yes
| withdrawn | Yes | |||||
S3‑211426 | LS to SA3 on Small data transmissions | R2-2104401 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑211430 | Reply LS on the support of L2TP with CUPS | C3-212569 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211438 | Reply LS on choice of cryptographic algorithm in 256-bit Milenage | THALES, Idemia | LS out | Approval | Yes |
Yes
| merged | No | S3-211500 | |||
S3‑211440 | LS on integrity protection between the UE and the HPLMN of additional fields in SOR transparent container carrying SOR acknowledgement | C1-212523 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211456 | TCG progress - report from TCG rapporteur | InterDigital, Inc. | other | Information | Yes |
Yes
| noted | No | ||||
S3‑211497 | DRAFT Response LS on 256-bit algorithms based on SNOW 3G or SNOW V | VODAFONE Group Plc | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑212397 | Response LS on 256-bit algorithms based on SNOW 3G or SNOW V | VODAFONE Group Plc | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211498 | Alternative 1 DRAFT Response LS on 256-bit Milenage | VODAFONE Group Plc | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211499 | Alternative 2 DRAFT Response LS on 256-bit Milenage | VODAFONE Group Plc | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211500 | Alternative 3 DRAFT Response LS on 256-bit Milenage | VODAFONE Group Plc | LS out | Approval | Yes |
Yes
| revised | No | S3‑212329 | |||
S3‑211523 | Reply LS to LS on broadcasting from other PLMN in case of Disaster Condition | LG Electronics Inc. | LS out | Approval | Yes |
Yes
| revised | No | S3‑212258 | |||
S3‑211530 | Discussion document on replies to ETSI SAGE | VODAFONE Group Plc | discussion | Information | Yes |
Yes
| noted | No | ||||
S3‑211537 | LS on PAP/CHAP and other point-to-point protocols usage in 5GS | China Telecommunications | LS out | Yes |
Yes
| noted | No | |||||
S3‑211539 | Discussion on security of Small data transmissions | ZTE Corporation | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211540 | Reply LS on Header Enrichment for HTTPS in PFCP | ZTE Corporation | LS out | Approval | Yes |
Yes
| merged | No | S3‑212344 | |||
S3‑211541 | Reply LS on Small data transmissions | ZTE Corporation | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211545 | Reply LS on Small data transmission | Intel K.K. | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211549 | Discussion on Security Issues with SDT | Intel K.K. | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S3‑211639 | Reply LS on UE location aspects in NTN | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑212306 | |||
S3‑211660 | Reply LS on Security of Small Data Transmissions | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211716 | MINT-Discussion paper on MINT | Apple | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211717 | MINT-draft Reply LS to CT1 on MINT. | Apple | LS out | Approval | Yes |
Yes
| merged | No | S3‑212258 | |||
S3‑211745 | Discussion on Security consideration to support L2TP with CUPS | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211746 | [DRAFT] Reply-LS on the Security consideration to support L2TP with CUPS | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S3‑212365 | |||
S3‑211747 | [DRAFT] Reply-LS on Secondary AUTH for 5GS interworking with EPS | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S3‑212366 | |||
S3‑211750 | Discussion on integrity protection between the UE and the HPLMN of additional fields in SOR transparent container carrying SOR acknowledgement | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211751 | [Draft] Reply-LS on integrity protection between the UE and the HPLMN of additional fields in SOR transparent container carrying SOR acknowledgement | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S3‑212272 | |||
S3‑211884 | Draft Reply LS on Security consideration to support L2TP with CUPS | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| merged | No | S3‑212365 | |||
S3‑211899 | Draft LS on TAU reject issue during MME handover | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑212343 | |||
S3‑211900 | Draft Reply LS on Header Enrichment for HTTPS in PFCP | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑212344 | |||
S3‑211992 | Discussion on 256-bit algorithms based on SNOW 3G or SNOW V | Ericsson, AT&T, BT plc, Deutsche Telekom AG | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑212025 | Reply LS on 256-bit algorithms based on SNOW 3G or SNOW V | Ericsson, AT&T, BT plc, Deutsche Telekom AG | LS out | Approval | Yes |
Yes
| merged | No | S3-211497 | |||
S3‑212257 | LS reply on Small data transmissions | InterDigital, Inc. | LS out | Yes |
Yes
| noted | No | |||||
S3‑212258 | Reply LS to LS on broadcasting from other PLMN in case of Disaster Condition | LG Electronics Inc. | LS out | Approval | Yes |
Yes
| approved | No | S3‑211523 | |||
S3‑212272 | Reply-LS on integrity protection between the UE and the HPLMN of additional fields in SOR transparent container carrying SOR acknowledgement | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S3‑211751 | |||
S3‑212291 | Reply LS on Storage of KAUSF | Samsung | LS out | Approval | Yes |
Yes
| approved | No | ||||
S3‑212305 | Reply LS on User location identification from Carrier Aggregation secondary cell activation messages | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| approved | No | S3‑211638 | |||
S3‑212306 | Reply LS on UE location aspects in NTN | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| approved | No | S3‑211639 | |||
S3‑212329 | Response LS on 256-bit Milenage | VODAFONE Group Plc | LS out | Approval | Yes |
Yes
| approved | No | S3‑211500 | |||
S3‑212343 | LS on TAU reject issue during MME handover | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| approved | No | S3‑211899 | |||
S3‑212344 | Reply LS on Header Enrichment for HTTPS in PFCP | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| approved | No | S3‑211900 | |||
S3‑212365 | Reply-LS on the Security consideration to support L2TP with CUPS | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S3‑211746 | |||
S3‑212366 | Reply-LS on Secondary AUTH for 5GS interworking with EPS | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S3‑211747 | |||
4 | Work Areas |   | ||||||||||
4.1 | Integration of GBA into 5GC (Rel-17) | S3‑211356 | Living document for TS 33.220: UDM services for GBA | THALES | draftCR | Approval | Yes |
Yes
| noted | No | ||
S3‑211357 | Living document for TS 33.223: UDM services for GBA | THALES | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211875 | Discussion paper on GBA authentication vector service | Huawei, Hisilicon | discussion | Approval | Yes |
Yes
| noted | No | ||||
S3‑211876 | UDM support of GBA service | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211925 | Living document for GBA_5G: draftCR to TS 33.220: SBA support for Zh and Zn interfaces | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211926 | Living document for GBA_5G: draftCR to TS 33.223: SBA support for Zpn | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211927 | Discussion on GBA support in UDM | Ericsson | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211928 | pCR to living document for TS 33.220: Support for GBA in UDM | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑211929 | pCR to living document for TS 33.223: Support for GBA in UDM | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑211930 | DRAFT LS on SBA for GBA | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
4.2 | Security Assurance Specification for IMS (Rel-17) | S3‑211534 | Adding test case on the confidentiality configuration in P-CSCF | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑211536 | Adding a new threat related to SPI allocation in the P-CSCF | China Telecommunications | draftCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑211538 | Adding a new threat related to SPI allocation in the P-CSCF | China Telecommunications | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211902 | IMS SCAS: living doc for the threats | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211903 | IMS SCAS: Adding the assets and threats of the new NFs and update existing threats | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211904 | IMS SCAS: living doc for the threats | Huawei, Hisilicon | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211905 | Update the test case on bidding down and add reqirements on new NFs | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211906 | Editorial change on TS 33.516 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211907 | Presentation of Specification to TSG: TS 33.226, Version 0.5.0 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212262 | IMS SCAS: Adding the assets and threats | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑212263 | Presentation of Specification to TSG: TS 33.226 for approval | Huawei, HiSilicon | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S3‑212345 | Draft TS 33.226 | Huawei, Hisilicon | draft TS | Approval | Yes |
Yes
| approved | No | ||||
4.3 | Security Assurance Specification Enhancements for 5G (Rel-17) | S3‑211409 | LS re Penetration Testing of SCAS | GSMA | LS in | Yes |
Yes
| postponed | No | |||
S3‑211542 | Add a new test case in clause 4.2.2.1.18 | ZTE Corporation | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211673 | liviing CR to 33.511 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑212375 | |||
S3‑211674 | liviing CR to 33.512 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑212376 | |||
S3‑211675 | liviing CR to 33.514 | Huawei, HiSilicon,Nokia,Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211676 | liviing CR to 33.517 | Huawei, HiSilicon,Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211677 | liviing CR to 33.117 | Huawei, HiSilicon,Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211678 | liviing CR to 33.926 | Huawei, HiSilicon,Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S3‑212377 | |||
S3‑211679 | Add textcase of NAS based redirection | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211680 | Add testcase to UP security activation in Inactive scenario | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211792 | Discussion on adding SCAS for the various split gNB cases | Qualcomm Incorporated | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211793 | Adding SCAS for the various split gNB cases | Qualcomm Incorporated | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑211857 | Threats related to session establishment procedure | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211858 | New test case on validation of S-NSSAIs in PDU session establishment | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑212332 | |||
S3‑211870 | New test case on de-registering UE after NSSAA revocation | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211871 | New security threats on unauthorized slice access | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212332 | New test case on validation of S-NSSAIs in PDU session establishment | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211858 | |||
S3‑212375 | living CR to 33.511 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211673 | |||
S3‑212376 | living CR to 33.512 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211674 | |||
S3‑212377 | living CR to 33.926 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211678 | |||
S3‑212379 | CR to include R-16 feature of gNB to 33.511 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑212380 | CR to include R-16 feature of AMF to 33.512 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑212381 | CR to include R-16 feature of UDM to 33.514 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑212382 | CR to include R-16 feature of SEPP to 33.517 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑212383 | CR to include new test cases and fix editorial in33.117 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑212384 | CR to add threat related to R-16 features of network products to 33.926 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
4.4 | Security Assurance Specification for Service Communication Proxy (SECOP) (Rel-17) | S3‑211936 | SCP-specific adaptations - technical baseline | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||
S3‑211937 | SCP-specific adaptations - Operating systems | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211938 | SCP-specific adaptations - Web servers | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211939 | SCP-specific adaptations - Network devices | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211940 | SCP-specific adaptations - NFs in SBA | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211941 | SCP test cases | Nokia, Nokia Shanghai Bell, NTT Docomo | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211942 | Assets and Threats specific to SCP | Nokia, Nokia Shanghai Bell | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S3‑211943 | SCP Test on Token forwarded to the correct NFp | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211944 | SCP Test on Correct token forwarded to NFp | Nokia, Nokia Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211945 | SCP-specific adaptations - technical baseline | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211946 | SCP-specific adaptations - Operating systems | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211947 | SCP-specific adaptations - Web servers | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211948 | SCP-specific adaptations - Network devices | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211949 | SCP-specific adaptations - NFs in SBA | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211950 | SCP test cases | Nokia, Nokia Shanghai Bell, NTT Docomo | pCR | Approval | Yes |
Yes
| revised | No | S3‑212121 | |||
S3‑211951 | Assets and Threats specific to SCP | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211952 | SCP Test on Token forwarded to the correct NFp | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211953 | SCP Test on Correct token forwarded to NFp | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211955 | SCP Requirement and test case for protection over internal interfaces | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| noted | No | |||||
S3‑212121 | SCP test cases | Nokia, Nokia Shanghai Bell, NTT Docomo | pCR | Approval | Yes |
Yes
| revised | No | S3‑212295 | S3‑211950 | ||
S3‑212293 | Living CR on SCP to 33.926 | Nokia, Nokia Shanghai Bell | draftCR | Yes |
Yes
| approved | No | |||||
S3‑212294 | TS 33.522 SCAS SCP | Nokia, Nokia Shanghai Bell | draft TS | Yes |
Yes
| approved | No | |||||
S3‑212295 | SCP test cases | Nokia, Nokia Shanghai Bell, NTT Docomo | pCR | Approval | Yes |
Yes
| approved | No | S3‑212121 | |||
4.5 | Security Assurance Specification for 5G NWDAF (Rel-17) | S3‑211640 | Corrections on TS 33.521 | Huawei, HiSilicon, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑211641 | Execution Step for Finding the right NF instance serving the UE | Huawei, HiSilicon, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑212307 | |||
S3‑211842 | Adding asset, description and threats to TR 33.926 for NWDAF SCAS | China Mobile | CR | Approval | Yes |
Yes
| revised | No | S3‑212321 | S3‑210775 | ||
S3‑211843 | Execution Step for Data Masking on Integration Analysis | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑212322 | |||
S3‑211844 | Address ENs in TS 33.521 | China Mobile, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211845 | Presentation of TR33.521 to SA plenary | China Mobile | TS or TR cover | Approval | Yes |
Yes
| revised | No | S3‑212387 | |||
S3‑212307 | Execution Step for Finding the right NF instance serving the UE | Huawei, HiSilicon, China Mobile, Nokia, Nokia Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211641 | |||
S3‑212321 | Adding asset, description and threats to TR 33.926 for NWDAF SCAS | China Mobile | CR | Approval | Yes |
Yes
| agreed | No | S3‑211842 | |||
S3‑212322 | Execution Step for Data Masking on Integration Analysis | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑211843 | |||
S3‑212323 | TS 33.521 v0.4.0 | China Mobile Com. Corporation | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S3‑212387 | Presentation of TS33.521 to SA plenary | China Mobile | TS or TR cover | Approval | Yes |
Yes
| approved | No | S3‑211845 | |||
4.6 | Security Assurance Specification for Non-3GPP InterWorking Function (N3IWF) (Rel- 17) |   | ||||||||||
4.7 | Security Assurance Specification for Inter PLMN UP Security (Rel-17) | S3‑211543 | Living document for SCAS_5G_IPUPS draftCR to TR 33.926 | ZTE Corporation | other | Approval | Yes |
Yes
| revised | No | S3‑212385 | |
S3‑211544 | Living document for SCAS_5G_IPUPS draftCR to TS 33.513 | ZTE Corporation | other | Approval | Yes |
Yes
| revised | No | S3‑212386 | |||
S3‑211868 | New test case on malformatted message for IPUPS | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑212334 | |||
S3‑211869 | New security threats on IPUPS malformatted message | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑212335 | |||
S3‑212334 | New test case on malformatted message for IPUPS | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211868 | |||
S3‑212335 | New security threats on IPUPS malformatted message | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211869 | |||
S3‑212385 | Living document for SCAS_5G_IPUPS draftCR to TR 33.926 | ZTE Corporation | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211543 | |||
S3‑212386 | Living document for SCAS_5G_IPUPS draftCR to TS 33.513 | ZTE Corporation | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211544 | |||
4.8 | eSCAS_5G for Network Slice-Specific Authentication and Authorization Function (NSSAAF) (Rel-17) |   | ||||||||||
4.9 | Mission critical security enhancements phase 2 (Rel-17) | S3‑211404 | LS on Plugtest issues | S6-210203 | LS in | Yes |
Yes
| noted | No | |||
S3‑211479 | [33.180] R17 Group subscription | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211480 | [33.180] R17 Limited Service | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211481 | [33.180] R17 Preconfigured group clarification | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211625 | Security solution for temporary group – broadcast group call procedure | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑212053 | Security for user regroup | CATT | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212091 | CR on signalling Algorithm Selection | Samsung | CR | Agreement | Yes |
Yes
| agreed | No | ||||
4.10 | Enhancements to User Plane Integrity Protection Support in 5GS (Rel-17) | S3‑211820 | UP integrity protection in options 4,5 and 7 | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||
4.11 | Adapting BEST for use in 5G networks (Rel-17) | S3‑211412 | Living document for TS 33.163 | KPN N.V. | draftCR | Approval | Yes |
Yes
| revised | No | S3‑212271 | |
S3‑211429 | Discussion paper BEST key hierarchy based on AKMA | Deutsche Telekom AG | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211461 | pCR to Living document for TS 33.163: update for 3G, 4G, and 5G key agreement | KPN N.V. | other | Approval | Yes |
Yes
| revised | No | S3‑212270 | |||
S3‑211934 | Work Item Exception sheet for BEST_5G Rel 17 | VODAFONE Group Plc | WI exception request | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑212270 | pCR to Living document for TS 33.163: update for 3G, 4G, and 5G key agreement | KPN N.V. | other | Approval | Yes |
Yes
| approved | No | S3‑211461 | |||
S3‑212271 | Living document for TS 33.163 | KPN N.V. | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211412 | |||
4.12 | Authentication and key management for applications based on 3GPP credential in 5G (Rel-17) | S3‑211546 | Clarification on how AF select AAnF | ZTE Corporation | CR | Agreement | Yes |
Yes
| merged | No | S3‑212313 | |
S3‑211547 | Clarification on how AUSF select AAnF | ZTE Corporation | CR | Agreement | Yes |
Yes
| merged | No | S3‑212313 | |||
S3‑211671 | Clarification on AAnF Selection | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212313 | |||
S3‑211908 | AKMA Anchor Function selection clause | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑212359 | |||
S3‑211550 | Resolution of EN on other parameter in clause 6.3 | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211817 | Sending UE identifier to the AKMA AF | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211585 | Add an abbreviation to AKMA | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S3‑212320 | |||
S3‑211672 | Editoral change in clause 6.1 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑211785 | Profiling the GBA TLS protocols for use with AKMA | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| revised | No | S3‑212353 | S3‑210477 | ||
S3‑211910 | IETF OSCORE as AKMA Ua* protocol | Ericsson, DT | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211911 | Extending the Ua security protocol namespace to include AKMA Ua* protocols | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211913 | AKMA UE aspects | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑212328 | |||
S3‑211548 | Clarification on how the AUSF get RID | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211551 | UDM notifies AAnF AKMA context removal | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S3‑212319 | |||
S3‑211552 | Update clause 6.1 refer to Kausf stored in AUSF | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211553 | Add Routing indicator in Authentication response | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211575 | Handle the failure cause by UE | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212074 | Refresh of Kaf and Kakma | Samsung | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212076 | Network provides authorization to AF for Kaf key refresh | Samsung | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211396 | Reply LS on AKMA Anchor Function selection | S2-2101304 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211912 | Handling of AKMA keys in the UE | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑212073 | Discussion on refresh of Kaf and Kakma | Samsung | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑212075 | Discussion on authorization of Kaf refresh | Samsung | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑212313 | Clarification on AAnF Selection | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑211671 | |||
S3‑212319 | UDM notifies AAnF AKMA context removal | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211551 | |||
S3‑212320 | Add an abbreviation to AKMA | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211585 | |||
S3‑212328 | AKMA UE aspects | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211913 | |||
S3‑212353 | Profiling the GBA TLS protocols for use with AKMA | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211785 | |||
S3‑212359 | AKMA Anchor Function selection clause | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211908 | |||
4.13 | User Plane Integrity Protection for LTE (Rel-17) | S3‑211374 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | C1-211461 | LS in | Yes |
Yes
| noted | No | |||
S3‑211398 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | S2-2101306 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211472 | CR to TS 33.401 - addition of UPIP to LTE | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211642 | User Plane Integrity Protection Policy Handling in LTE | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑212308 | |||
S3‑211643 | UP Integrity protection Handling for Option 3 | Huawei, HiSilicon | draftCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212308 | User Plane Integrity Protection Policy Handling in LTE | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑211642 | |||
4.14 | Enhancements of 3GPP profiles for cryptographic algorithms and security protocols (Rel- 17) | S3‑211855 | recommendation of SHA256 in SIP digest | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||
S3‑212061 | Security updates for algorithms and protocols in 33.220 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑212062 | Security updates for algorithms and protocols in 33.222 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑212063 | Security updates for algorithms and protocols in 33.223 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑212064 | Security updates for algorithms and protocols in 33.210 | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212065 | Security updates for algorithms and protocols in 33.203 | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212066 | Security updates for algorithms and protocols in 33.310 | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212067 | Security updates for algorithms and protocols in 33.501 | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212261 | recommendation of SHA256 in SIP digest | Huawei, HiSilicon | draftCR | Approval | No |
Yes
| revised | No | S3‑212333 | |||
S3‑212264 | Security updates for algorithms and protocols in 33.310 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212269 | Security updates for algorithms and protocols in 33.210 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212333 | recommendation of SHA256 in SIP digest | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑212261 | |||
4.15 | Security Assurance Specification for 5G (Rel-16) | S3‑211554 | Clarification on external file system mount restrictions R16 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||
S3‑211555 | Clarification on external file system mount restrictions R17 | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211556 | Editorial correction in clause 4.2.2.1.5 R16 | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211557 | Editorial correction in clause 4.2.2.1.5 R17 | ZTE Corporation | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211681 | Update testcases in gNB SCAS | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212314 | |||
S3‑211883 | Resolving EN on the error handling | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑211935 | Alignment of requirements with specification updates | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑212395 | |||
S3‑212395 | Alignment of requirements with specification updates | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | S3‑211935 | |||
S3‑212314 | Update testcases in gNB SCAS | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑211681 | |||
4.16 | Security Aspects of the 5G Service Based Architecture (Rel-16) | S3‑211459 | CR to 33.501 R16 - Clarification on the number of PLMN IDuse by SEPP over N32 | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| revised | No | S3‑212287 | |
S3‑211460 | CR to 33.501 R17 - Clarification on the number of PLMN IDuse by SEPP over N32 | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| revised | No | S3‑212288 | |||
S3‑211980 | N32-c and N32-f clarification R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑212282 | |||
S3‑211981 | N32-c and N32-f clarification R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑212284 | |||
S3‑211759 | Clarify the usage of TLS and PRINS between SEPPs | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑212367 | |||
S3‑211760 | Clarify the usage of TLS and PRINS between SEPPs | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑212368 | |||
S3‑211761 | Clarify the usage of TLS and PRINS between SEPPs | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑212369 | |||
S3‑211626 | Correction to Authorization for indirect communication with delegated discovery procedure | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑211762 | Correction to NF Certificate profile: Format of the apiRoot | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211763 | Correction to JOSE profile Reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211764 | Correction to JOSE profile Reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211982 | Deployment models R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑212285 | |||
S3‑211983 | Deployment models R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S3‑212286 | |||
S3‑211446 | LS to 3GPP SA3 N32 and multiple PLMN IDs | GSMA | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211457 | Discussion on SEPP to SEPP communication on 5GSA networks | VODAFONE Group Plc | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211458 | draft response LS to GSMA on 3GPP SA3 N32 and multiple PLMN IDs | VODAFONE Group Plc | LS out | Agreement | Yes |
Yes
| revised | No | S3‑212392 | |||
S3‑212392 | Response LS to GSMA on 3GPP SA3 N32 and multiple PLMN IDs | VODAFONE Group Plc | LS out | Approval | Yes |
Yes
| approved | No | S3‑211458 | |||
S3‑211462 | Draft CR to TS 33.501 to resolve security hole when IPX SEPP is used | VODAFONE Group Plc | draftCR | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211748 | Discussion on "LS to 3GPP SA3 N32 and multiple PLMN IDs" | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211749 | [DRAFT] Reply-LS on N32 and multiple PLMN IDs | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑212282 | N32-c and N32-f clarification R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211980 | |||
S3‑212284 | N32-c and N32-f clarification R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211981 | |||
S3‑212285 | Deployment models R16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211982 | |||
S3‑212286 | Deployment models R17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211983 | |||
S3‑212287 | CR to 33.501 R16 - Clarification on the number of PLMN IDuse by SEPP over N32 | VODAFONE Group Plc, Nokia, Nokia Shanghai Bell, Mavenir | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211459 | |||
S3‑212288 | CR to 33.501 R17 - Clarification on the number of PLMN IDuse by SEPP over N32 | VODAFONE Group Plc, Nokia, Nokia Shanghai Bell, Mavenir | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211460 | |||
S3‑212367 | Clarify the usage of TLS and PRINS between SEPPs | Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211759 | |||
S3‑212368 | Clarify the usage of TLS and PRINS between SEPPs | Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211760 | |||
S3‑212369 | Clarify the usage of TLS and PRINS between SEPPs | Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211761 | |||
4.17 | Evolution of Cellular IoT security for the 5G System (Rel-16) |   | ||||||||||
4.18 | Security of the Wireless and Wireline Convergence for the 5G system architecture (Rel-16) | S3‑211644 | Assign FC Value for KTIPSec and KTNAP Derivation in R16 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212309 | |
S3‑211645 | Assign FC Value for KTIPSec and KTNAP Derivation in R17 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212310 | |||
S3‑211646 | FC Value Change because of KTIPSec and KTNAP Derivation in R16 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑211647 | FC Value Change because of KTIPSec and KTNAP Derivation in R17 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212311 | |||
S3‑212309 | Assign FC Value for KTIPSec and KTNAP Derivation in R16 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑211644 | |||
S3‑212310 | Assign FC Value for KTIPSec and KTNAP Derivation in R17 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑211645 | |||
S3‑212311 | FC Value Change because of KTIPSec and KTNAP Derivation in R17 | Huawei, HiSilicon, Samsung | CR | Approval | Yes |
Yes
| agreed | No | S3‑211647 | |||
4.19 | Security aspects of Enhancement of Network Slicing (Rel-16) | S3‑211512 | CR to Delete NSSAA Editor Notes (Rel-16) | Nokia, Nokia Shangahai-Bell | CR | Approval | Yes |
Yes
| merged | No | S3‑212280 | |
S3‑211513 | CR to Delete NSSAA Editor Notes (Rel-17) | Nokia, Nokia Shanghai-Bell | CR | Approval | Yes |
Yes
| merged | No | S3‑212281 | |||
S3‑211624 | Slice privacy protection in NSSAA related procedures | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212280 | |||
S3‑211602 | Serving network ID in NSSAA | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211603 | validity peirod of NSSAA result | Huawei, HiSilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211662 | Change the procedure of network slice re-authentication and revocation by AAA-S | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212312 | |||
S3‑211685 | Addressing impersonate attack from AAA-S | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑211686 | Mirror- Addressing impersonate attack from AAA-S | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑211985 | Prevention of attacks on slice core by CCA modifications - Rel-16 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211986 | Prevention of attacks on slice core by CCA modifications - Rel-17 | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211383 | Prevention of attacks on sliced core network | GSMA | LS in | Yes |
Yes
| postponed | No | |||||
S3‑211393 | Reply LS on NSSAA at inter-PLMN mobility | S2-2101052 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211415 | Reply LS on Prevention of attacks on sliced core network | S2-2103213 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211511 | Discussion paper on ENs in Network Slicing clause 16.3 | Nokia, Nokia Shanghai-Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211527 | Reply LS to GSMA on prevention of attacks on sliced core network | CableLabs | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211601 | Discussion on SN-ID in NSSAA | Huawei, HiSilicon | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211611 | Discussion on slice issues in core networks | Huawei, HiSilicon | discussion | Endorsement | Yes |
Yes
| revised | No | S3‑212187 | |||
S3‑211689 | EAP ID Request in NSSAA Procedure | Ericsson | CR | Yes |
Yes
| not pursued | No | |||||
S3‑211700 | EAP ID Request in NSSAA Procedure (Rel-17) | Ericsson | CR | Yes |
Yes
| not pursued | No | |||||
S3‑211984 | Discussion of GSMA LS S3-211383 Prevention of attacks on sliced core | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑212187 | Discussion on slice issues in core networks | Huawei, HiSilicon | discussion | Endorsement | Yes |
Yes
| noted | No | S3‑211611 | |||
S3‑212280 | Slice privacy protection in NSSAA related procedures | Huawei, HiSilicon, Nokia, Nokia Shangahai-Bell | CR | Approval | Yes |
Yes
| agreed | No | S3‑211624 | |||
S3‑212281 | Slice privacy protection in NSSAA related procedures (Rel-17) | Huawei, HiSilicon, Nokia, Nokia Shangahai-Bell | CR | Yes |
Yes
| agreed | No | |||||
S3‑212312 | Change the procedure of network slice re-authentication and revocation by AAA-S | Huawei, HiSilicon, Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S3‑211662 | |||
4.20 | Security Aspects of 3GPP support for Advanced V2X Services (Rel-16) | S3‑211373 | Reply LS on the re-keying procedure and security indication for NR SL | C1-211228 | LS in | Yes |
Yes
| noted | No | |||
S3‑211413 | LS on the latest results on the Vehicular Multimedia deliverables from ITU FG-VM | ITU-T Focus Group on Vehicular Multimedia (FG-VM) | LS in | Yes |
Yes
| noted | No | |||||
S3‑211882 | Clarification on a figure and the key activation | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212341 | |||
S3‑212341 | Clarification on a figure and the key activation | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212348 | S3‑211882 | ||
S3‑212348 | Clarification on a figure and the key activation | Huawei, Hisilicon, Interdigtal | CR | Approval | Yes |
Yes
| agreed | No | S3‑212341 | |||
4.21 | New work item proposals | S3‑211452 | WID on IIoT | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| revised | No | S3‑212318 | |
S3‑211630 | New WID on Security enhancements for 5G multicast-broadcast services (5MBS) | Huawei, Hisilicon,China Broadcasting Network | WID new | Approval | Yes |
Yes
| revised | No | S3‑212304 | |||
S3‑211701 | 5GFBS-WID for 5GFBS | Apple | WID new | Approval | Yes |
Yes
| noted | No | ||||
S3‑211771 | Security aspects of eNPN: draft skeleton for draft CR | Ericsson, Huawei, InterDigital | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211772 | New WID on Security Aspects of eNPN | Ericsson, Alibaba, China Mobile, InterDigital, ZTE | WID new | Agreement | Yes |
Yes
| revised | No | S3‑212371 | |||
S3‑211773 | New WID on certificate profiles for SBA | Ericsson | WID new | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211774 | New WID on Security aspects of Uncrewed Aerial Systems | Qualcomm Incorporated, Interdigital, Huawei, HiSilicon | WID new | Agreement | Yes |
Yes
| revised | No | S3‑212354 | |||
S3‑211783 | Information on the updates to the proposed WID on TLS protocol profiles for AKMA | Qualcomm Incorporated | discussion | Information | Yes |
Yes
| noted | No | ||||
S3‑211784 | New WID on TLS protocols profiles for AKMA | Qualcomm Incorporated | WID new | Agreement | Yes |
Yes
| revised | No | S3‑212352 | S3‑210479 | ||
S3‑211892 | New WID on Study on Security Aspects of Enhancement of Support for Edge Computing in 5GC | Huawei, Hisilicon | WID new | Approval | Yes |
Yes
| revised | No | S3‑212342 | |||
S3‑211909 | New WID on IoT Ua* protocol profiles for AKMA | Ericsson, China Mobile | WID new | Agreement | Yes |
Yes
| noted | No | ||||
S3‑211919 | New WID on the security of AMF re-allocation | Ericsson | WID new | Agreement | Yes |
Yes
| noted | No | ||||
S3‑211923 | New WID on Authentication enhancements in 5GS | Ericsson | WID new | Agreement | Yes |
Yes
| noted | No | ||||
S3‑212304 | New WID on Security enhancements for 5G multicast-broadcast services (5MBS) | Huawei, Hisilicon,China Broadcasting Network | WID new | Approval | Yes |
Yes
| agreed | No | S3‑211630 | |||
S3‑212318 | WID on IIoT | Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| agreed | No | S3‑211452 | |||
S3‑212342 | New WID on Security Aspects of Enhancement of Support for Edge Computing in 5GC | Huawei, Hisilicon | WID new | Approval | Yes |
Yes
| agreed | No | S3‑211892 | |||
S3‑212352 | New WID on TLS protocols profiles for AKMA | Qualcomm Incorporated, Ericsson, CMCC, ZTE, Nokia | WID new | Agreement | Yes |
Yes
| agreed | No | S3‑211784 | |||
S3‑212354 | New WID on Security aspects of Uncrewed Aerial Systems | Qualcomm Incorporated, Interdigital, Huawei, HiSilicon, Ericsson, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| agreed | No | S3‑211774 | |||
S3‑212371 | New WID on Security Aspects of eNPN | Ericsson, Alibaba, China Mobile, InterDigital, ZTE | WID new | Agreement | Yes |
Yes
| agreed | No | S3‑211772 | |||
4.22 | Other work areas (no release restrictions) | S3‑211988 | Removal of ENs for draft-ietf-emu-rfc5448bis - Rel-15 | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑212330 | |
S3‑211990 | Removal of ENs for draft-ietf-emu-rfc5448bis -Rel-16 | Ericsson | CR | Yes |
Yes
| revised | No | S3‑212331 | ||||
S3‑211991 | Removal of ENs for draft-ietf-emu-rfc5448bis- Rel-17 | Ericsson | CR | Yes |
Yes
| revised | No | S3‑212346 | ||||
S3‑211474 | [33.180] R14 UID encoding | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211475 | [33.180] R15 UID encoding (mirror) | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211476 | [33.180] R16 UID encoding (mirror) | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211478 | [33.180] R17 UID encoding (mirror) | Motorola Solutions Danmark A/S | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211720 | UE procedures at TAU reject in idle mode mobility from 5GS to EPS over N26 | MediaTek Inc. / Marko | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑211722 | UE procedures at TAU reject in idle mode mobility from 5GS to EPS over N26 | MediaTek Inc. / Marko | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑211753 | Clarification on the NRF services authorization | Ericsson, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211754 | Clarification on the NRF services authorization | Ericsson, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211755 | Clarification on the NRF services authorization | Ericsson, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211756 | Clarification on the OAuth 2.0 client registration | Ericsson, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211757 | Clarification on the OAuth 2.0 client registration | Ericsson, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211758 | Clarification on the OAuth 2.0 client registration | Ericsson, Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211888 | Clarification on the Oauth client registration | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211889 | Clarification on the Oauth client registration and authorization | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211891 | Clarification on the static authorization | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑211795 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover | Qualcomm Incorporated, Huawei, HiSilicon, CATT, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211796 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover | Qualcomm Incorporated, Huawei, HiSilicon, CATT, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211797 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover | Qualcomm Incorporated, Huawei, HiSilicon, CATT, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211818 | Clarifying the support for authentication methods in an SNPN | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211819 | Clarifying the support for authentication methods in an SNPN | Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211886 | Editor's note of the security of 5GLAN services removal in R16 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211887 | Editor's note of the security of 5GLAN services removal in R17 | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑211684 | Clarify on ngKSI used in NAS SMC in Kausf storage | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑212103 | Rel16-Handling of Kausf upon successful primary authentication | Samsung, NEC, Nokia, Nokia Shanghai Bell, Intel | CR | Agreement | Yes |
Yes
| revised | No | S3‑212289 | |||
S3‑212104 | Rel17-Handling of Kausf upon successful primary authentication | Samsung, NEC, Nokia, Nokia Shanghai Bell, Intel | CR | Agreement | Yes |
Yes
| revised | No | S3‑212290 | |||
S3‑211648 | Address ENs in TS 33.216 | Huawei, HiSilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑211822 | Correction of Annex A.13 | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212119 | Correction of Annex A.13 | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑211873 | Clarifications to 5G CIoT K_NG-RAN derivation | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑211874 | Claifications on mapped security | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| revised | No | S3‑212337 | |||
S3‑211885 | UP Security policy requirement on the IMS data network | Huawei, Hisilicon | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S3‑212092 | Correction to FC values in range for future use in 3GPP specifications | Samsung | CR | Agreement | Yes |
Yes
| merged | No | S3‑212311 | |||
S3‑211355 | Agenda and notes from the SA3/IETF joint call | SA WG3 Chair | other | Information | Yes |
Yes
| noted | No | ||||
S3‑211453 | WID IIoT Draft CR PTP aspects | Nokia, Nokia Shanghai Bell | draftCR | Endorsement | Yes |
Yes
| revised | No | S3‑212316 | |||
S3‑211454 | WID IIoT Draft CR NEF-AF aspects | Nokia, Nokia Shanghai Bell | draftCR | Endorsement | Yes |
Yes
| revised | No | S3‑212317 | |||
S3‑211455 | WID IIoT Draft CR Security considerations - informative | Nokia, Nokia Shanghai Bell | draftCR | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211683 | EAP ID Request in NSSAA procedure | Ericsson | discussion | Discussion | No |
Yes
| withdrawn | Yes | ||||
S3‑211687 | EAP ID Request in NSSAA procedure | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211719 | DRAFT LS on EAP ID Request in NSSAA Procedure | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211752 | NRF services authorization and OAuth 2.0 client registration from Rel-15 onwards | Ericsson, Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211821 | Correction of Annex A.13 | Ericsson | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S3‑211872 | Reply LS on changes to SoR | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑212336 | |||
S3‑211965 | Way forward for draft-ietf-emu-rfc5448bis | Ericsson | discussion | Yes |
Yes
| noted | No | |||||
S3‑212249 | Summary of discussion: NRF services authorization and OAuth 2.0 client registration from Rel-15 onwards | Nokia, Nokia Shanghai Bell | discussion | Yes |
Yes
| not treated | No | |||||
S3‑212260 | WID IIoT CR NEF-AF aspects | Nokia, Nokia Shanghai Bell | draftCR | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S3‑212265 | PTP aspects | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑212266 | NEF-AF aspects | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S3‑212289 | Rel16-Handling of Kausf upon successful primary authentication | Samsung, NEC, Nokia, Nokia Shanghai Bell, Intel, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑212103 | |||
S3‑212290 | Rel17-Handling of Kausf upon successful primary authentication | Samsung, NEC, Nokia, Nokia Shanghai Bell, Intel, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑212104 | |||
S3‑212316 | WID IIoT Draft CR PTP aspects | Nokia, Nokia Shanghai Bell | draftCR | Endorsement | Yes |
Yes
| approved | No | S3‑211453 | |||
S3‑212317 | WID IIoT Draft CR NEF-AF aspects | Nokia, Nokia Shanghai Bell | draftCR | Endorsement | Yes |
Yes
| approved | No | S3‑211454 | |||
S3‑212330 | Removal of ENs for draft-ietf-emu-rfc5448bis - Rel-15 | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211988 | |||
S3‑212331 | Removal of ENs for draft-ietf-emu-rfc5448bis -Rel-16 | Ericsson | CR | Yes |
Yes
| agreed | No | S3‑211990 | ||||
S3‑212336 | Reply LS on changes to SoR | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑212378 | S3‑211872 | ||
S3‑212393 | Reply LS on changes to SoR | Huawei, Hisilicon | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212337 | Claifications on mapped security | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑211874 | |||
S3‑212338 | Claifications on mapped security | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | ||||
S3‑212339 | Clarification to SoR transparent container | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| agreed | No | S3‑211881 | |||
S3‑212340 | Clarifications to 5G CIoT K_NG-RAN derivation | Huawei, Hisilicon | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑212346 | Removal of ENs for draft-ietf-emu-rfc5448bis- Rel-17 | Ericsson | CR | Yes |
Yes
| agreed | No | S3‑211991 | ||||
S3‑212378 | Reply LS on changes to SoR | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| approved | No | S3‑212336 | |||
5 | Study Areas |   | ||||||||||
5.1 | Study on 5G security enhancement against false base stations | S3‑211427 | Reply LS to SA3 on FBS detection | R2-2104626 | LS in | Yes |
Yes
| noted | No | |||
S3‑211522 | Updating annex B in TR 33.809 | CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211576 | Additions in Solution #25 | Philips International B.V. | pCR | Yes |
Yes
| noted | No | |||||
S3‑211582 | Updates in Solution #23 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212358 | |||
S3‑211584 | Updates in Appendix B | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211586 | Remarks_in_Solution_14 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212356 | |||
S3‑211588 | Update_in_solution_26 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212357 | |||
S3‑211598 | Update to solution #25 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212283 | |||
S3‑211599 | Evaluation of solution #4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211600 | Conclusion for KI#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211702 | 5GFBS-Adding evaluation for solution#4 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211703 | 5GFBS-Adding a new clause on Evaluations for key issues | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211704 | 5GFBS-Conclusion for key issue#2 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211705 | 5GFBS-Conclusion for key issue#3 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211706 | 5GFBS-Draft LS to RAN2 on Solution#17 | Apple | LS out | Approval | Yes |
Yes
| revised | No | S3‑212349 | |||
S3‑212105 | Updates to KI#1 & KI#7 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212106 | [Draft] LS on feasibility of addressing the attacks against 5G UE over radio interfaces | Samsung | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑212283 | Update to solution #25 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211598 | |||
S3‑212349 | 5GFBS-LS to RAN2 on Solution#17 | Apple | LS out | Approval | Yes |
Yes
| approved | No | S3‑211706 | |||
S3‑212351 | draft TR 33.809 | Apple (UK) Limited | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212356 | Remarks_in_Solution_14 | Philips International B.V. | pCR | Yes |
Yes
| approved | No | S3‑211586 | ||||
S3‑212357 | Update_in_solution_26 | Philips International B.V. | pCR | Yes |
Yes
| approved | No | S3‑211588 | ||||
S3‑212358 | Updates in Solution #23 | Philips International B.V. | pCR | Yes |
Yes
| approved | No | S3‑211582 | ||||
5.2 | Study on SECAM and SCAS for 3GPP virtualized network products | S3‑211825 | Clarification on GVNP and 3GPP functinoality in 4.1.1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑211826 | resolving EN about the GVNP lifecycle in clause 5.2.5.5.7.1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211827 | editorial modification in clause 5.2.5.6.8.5.3 and 5.2.5.7.6 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211828 | Adding threat reference in clause 5.2.5.7.7.2 and 5.2.5.7.7.3 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211829 | Modifying contents about decoupling scenarios | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211830 | Resolving EN about Figure 5.2.5.1-1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211831 | Adding vendor development and product lifecycle processes and test laboratory accreditation into Clause 6 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211832 | proposal for way forward | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211833 | Clean up to existing editor's note | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211834 | Presentation of TR33.818 to SA plenary | China Mobile | TS or TR cover | Approval | Yes |
Yes
| revised | No | S3‑212324, S3‑212326 | |||
S3‑212069 | Type 1 threat | Futurewei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212070 | Typye 2 Threats | Futurewei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212071 | Type 3 Threats | Futurewei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212110 | Clause 6.1 | Futurewei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212324 | Presentation of TR33.818 to SA plenary | China Mobile | TS or TR cover | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212325 | TR 33.818 v0.12.0 | China Mobile Com. Corporation | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212326 | Presentation of TR33.818 to SA plenary | China Mobile | TS or TR cover | Approval | Yes |
Yes
| approved | No | S3‑211834 | |||
5.3 | Study on User Plane Integrity Protection | S3‑211425 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | R2-2104349 | LS in | Yes |
Yes
| noted | No | |||
S3‑211468 | pCR to 33.853 - update to 7.2 following liaisons | VODAFONE Group Plc | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211469 | pCR to 33.853 - Removal of template sections ready for specification approval | VODAFONE Group Plc | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211470 | pCR to 33.853: editorial updates | VODAFONE Group Plc | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211587 | pCR to TR33.853 - editorial corrections | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211593 | Cover sheet for approval of TR33.853 | VODAFONE Group Plc | TS or TR cover | Agreement | Yes |
Yes
| approved | No | ||||
S3‑211612 | pCR to TR33.845 - Resolution of editors notes for solution#2 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211613 | pCR to TR33.845 - Resolution of editors notes for solution#3 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211614 | pCR to TR33.845 - Resolution of editors notes for solutions 5 and 6 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211616 | pCR to TR33.845 - Resolution of editors notes for solutions 9 and 10 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211649 | Solution Update for Solution #28 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212194 | |||
S3‑211650 | Conclusion for Key Issue #7 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212195 | |||
S3‑211651 | LS on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑212196 | |||
S3‑211682 | pCR to TR33.845 - Resolution of editors notes for solutions 11 13 14 and 15 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211688 | pCR to TR33.845 - Resolution of editors notes for solutions 18 19 20 and 21 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211690 | pCR to TR33.845 - Resolution of editors notes for solutions 22 23 24 26 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211718 | pCR to TR33.845 - Resolution of editors notes for solutions 28 29 30 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| revised | No | S3‑212217 | |||
S3‑211721 | pCR to TR33.853 - removal of template sections | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211736 | pCR to TR33.853 - Resolution of editors notes in Conclusions and Recommendations | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| revised | No | S3‑212218 | |||
S3‑212115 | UP IP: Update to solution #21 (Interworking handover from EPS to 5GS) | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212133 | |||
S3‑212116 | UP IP: Update to solution #24 Interworking handover from 5GS to EPS | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212134 | |||
S3‑212117 | UP IP: Update to solution #30 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212133 | UP IP: Update to solution #21 (Interworking handover from EPS to 5GS) | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑212115 | |||
S3‑212134 | UP IP: Update to solution #24 Interworking handover from 5GS to EPS | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑212116 | |||
S3‑212194 | Solution Update for Solution #28 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211649 | |||
S3‑212195 | Conclusion for Key Issue #7 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211650 | |||
S3‑212196 | LS on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| approved | No | S3‑211651 | |||
S3‑212217 | pCR to TR33.845 - Resolution of editors notes for solutions 28 29 30 | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | S3‑211718 | |||
S3‑212218 | pCR to TR33.853 - Resolution of editors notes in Conclusions and Recommendations | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | S3‑211736 | |||
S3‑212219 | new draft TR33.853 v1.6.0 | VODAFONE Group Plc | draft TR | Agreement | Yes |
Yes
| approved | No | ||||
5.4 | Study on Security Impacts of Virtualisation | S3‑212120 | Addition of Key Issue 26 Text | BT plc | pCR | Agreement | Yes |
Yes
| revised | No | S3‑212388 | |
S3‑212122 | Addition of Key Issue 25 Text | BT plc | pCR | Agreement | Yes |
Yes
| revised | No | S3‑212389 | |||
S3‑212388 | Addition of Key Issue 26 Text | BT plc | pCR | Agreement | Yes |
Yes
| approved | No | S3‑212120 | |||
S3‑212389 | Addition of Key Issue 25 Text | BT plc | pCR | Agreement | Yes |
Yes
| approved | No | S3‑212122 | |||
S3‑212391 | TR 33.848 | BT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.5 | Study on authentication enhancements in 5GS | S3‑211364 | Reply to LS on Resynchronisations | ETSI SAGE | LS in | Yes |
Yes
| postponed | No | |||
S3‑211434 | pCR to TR 33.846: Clarification on Key Issue #2.2 | THALES | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211435 | pCR to TR 33.846: Clarification on Key Issue #3.2 | THALES | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211436 | pCR to TR 33.846: update of assessment of attack risk | THALES, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211437 | pCR to 33.846: update of impact of solutions | THALES | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211442 | pCR to 33.846: update to solution #2.4 | THALES | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211471 | pCR to TR 33.853 - resolution of editors notes | VODAFONE Group Plc | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211496 | Draft reply to ETSI SAGE on Resynchronisations | VODAFONE Group Plc | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211503 | Discussion on the solution#4.1 in TR 33.846 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211504 | Evaluation of sol#4.1 using MACS as freshness in calculation of AK | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211505 | Editor note removal on solution #2.9 MAC, SYNCH failure cause concealment | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212267 | |||
S3‑211506 | Conclusion on Key issue #2.1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211507 | Conclusion on Key issue #3.2 SUPI guessing attack | Nokia, Nokia Shanghai Bell,THALES | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211508 | Conclusion on Key issue #4.1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211509 | EN removal on SUCI generation by legitimate SUPI owner using KSUCI | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211510 | LS on Security risk evaluation of using long term key for another key derivation than AKA | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S3‑212268 | |||
S3‑211528 | Resolving ENs of solution 6.2.10 | NEC Corporation | pCR | Agreement | Yes |
Yes
| revised | No | S3‑212296 | |||
S3‑211529 | Evaluation of key issue 2.2 SUCI replay attack. | NEC Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211535 | Evaluation of solution #2.10 | NEC Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211558 | Add evaluation and update comparison table for solution 3.2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212276 | |||
S3‑211559 | Add evaluation for solution 4.5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212277 | |||
S3‑211560 | EN resolution on null scheme for solution 2.7 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212274 | |||
S3‑211561 | Update to mapping table | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212273 | |||
S3‑211562 | Update to solution 2.7 and evaluation table | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212275 | |||
S3‑211563 | Update to solution 4.5 for the scenario of UE triggered service request | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212278 | |||
S3‑211564 | Conclusion for the key issue#4.1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211636 | Update to the solution 3.3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212327 | |||
S3‑211786 | Some proposed text for the assessment of attack risk table | Qualcomm Incorporated, Vodafone | pCR | Approval | Yes |
Yes
| noted | No | S3‑211057 | |||
S3‑211787 | Proposed conclusion for key issue #4.1 | Qualcomm Incorporated, Vodafone | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211788 | Proposed conclusion for the linkability parts of key issues #2.1 and 2.2 | Qualcomm Incorporated, Vodafone, DoCoMo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211835 | Assessment of attack risk | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211836 | Solution to mitgate the SUPI guessing attack without changing the format of SUCI | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211837 | Solution to mitigate the SUPI guessing attack and SUCI replay attack by adding new MAC tag in SUCI | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211921 | Authentication enhancements: TR editorials | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211922 | Authentication enhancements: Clause 4 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211924 | Authentication enhancements: Discussion about the WID | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211966 | pCR to 33.846: conclusion for KI #2.1 | THALES | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211967 | pCR to 33.846: conclusion for KI#4.1 | THALES | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212267 | Editor note removal on solution #2.9 MAC, SYNCH failure cause concealment | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211505 | |||
S3‑212268 | LS on Security risk evaluation of using long term key for another key derivation than AKA | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | S3‑211510 | |||
S3‑212273 | Update to mapping table | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211561 | |||
S3‑212274 | EN resolution on null scheme for solution 2.7 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211560 | |||
S3‑212275 | Update to solution 2.7 and evaluation table | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211562 | |||
S3‑212276 | Add evaluation and update comparison table for solution 3.2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211558 | |||
S3‑212277 | Add evaluation for solution 4.5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211559 | |||
S3‑212278 | Update to solution 4.5 for the scenario of UE triggered service request | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211563 | |||
S3‑212296 | Resolving ENs of solution 6.2.10 | NEC Corporation | pCR | Agreement | Yes |
Yes
| approved | No | S3‑211528 | |||
S3‑212315 | Draft TR 33.846 v0.12.0 Study on authentication enhancements in the 5G System (5GS) | Ericsson España S.A. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212327 | Update to the solution 3.3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211636 | |||
5.6 | Study on storage and transport of 5GC security parameters for ARPF authentication | S3‑211531 | pCR to TR 33.845 - editorial corrections | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| revised | No | S3‑212347 | |
S3‑211532 | Cover Sheet for approval of TR 33.845 | VODAFONE Group Plc | TS or TR cover | Agreement | Yes |
Yes
| approved | No | ||||
S3‑211533 | pCR to TR 33.845 - removal of template sections | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211581 | pCR to TR33.845 - removal of editors notes | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| revised | No | S3‑212350 | |||
S3‑212347 | pCR to TR 33.845 - editorial corrections | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | S3‑211531 | |||
S3‑212350 | pCR to TR33.845 - removal of editors notes | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| approved | No | S3‑211581 | |||
S3‑212360 | TR33.845 v1.1.0 | VODAFONE Group Plc | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.7 | Study on security aspects of Unmanned Aerial Systems | S3‑211385 | Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM | GSMA | LS in | Yes |
Yes
| postponed | No | |||
S3‑211386 | 3GPP SA1 clarifications on problematic UAV | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S3‑211487 | TR 33.854 KI#1 conclusion | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑212183 | |||
S3‑211488 | TR 33.854 KI#2 conclusion | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑212184 | |||
S3‑211489 | TR 33.854 KI#4 conclusion | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212128 | |||
S3‑211606 | Evaluation of solution #3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212181 | |||
S3‑211607 | Evaluation of solution #5 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212211 | |||
S3‑211608 | Conclusion for KI#1 (AA) | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212183 | |||
S3‑211609 | Conclusion for KI#2 (pairing) | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212184 | |||
S3‑211610 | Conclusion for KI#7 (C2) | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212185 | |||
S3‑211617 | propose evaluation to Solution #16 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211740 | Mapping of Key Issues | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211775 | Update to solution #6 on obtaining UAV location information from the PLMN | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212244 | |||
S3‑211776 | Update to solution #10 on authentication and authorisation of UAVs | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211777 | Update to solution #13 on authorisation of UAV/UAVC when connected to EPS | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212245 | |||
S3‑211778 | Update to solution #14 on authorisation of UAV/UAVC pairing when connected to 5GS | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212246 | |||
S3‑212050 | Update to solution #2 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212222 | |||
S3‑212128 | TR 33.854 KI#4 conclusion | InterDigital, Europe, Ltd., Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211489 | |||
S3‑212181 | Evaluation of solution #3 | Huawei, HiSilicon, InterDigital | pCR | Approval | Yes |
Yes
| approved | No | S3‑211606 | |||
S3‑212182 | Evaluation of solution #5 | Huawei, HiSilicon, InterDigital | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑212183 | Conclusion for KI#1 (AA) | Huawei, HiSilicon, InterDigital, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑211608 | |||
S3‑212184 | Conclusion for KI#2 (pairing) | Huawei, HiSilicon, InterDigital, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑211609 | |||
S3‑212185 | Conclusion for KI#7 (C2) | Huawei, HiSilicon, InterDigital, Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑211610 | |||
S3‑212211 | Evaluation of solution #5 | Huawei, HiSilicon, InterDigital | pCR | Approval | Yes |
Yes
| approved | No | S3‑211607 | |||
S3‑212222 | Update to solution #2 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑212050 | |||
S3‑212244 | Update to solution #6 on obtaining UAV location information from the PLMN | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211775 | |||
S3‑212245 | Update to solution #13 on authorisation of UAV/UAVC when connected to EPS | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211777 | |||
S3‑212246 | Update to solution #14 on authorisation of UAV/UAVC pairing when connected to 5GS | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211778 | |||
S3‑212247 | Draft TR 33.854 | Qualcomm | draft TR | Approval | Yes |
Yes
| approved | No | S3‑211346 | |||
5.8 | Study on Security Aspects of Enhancement of Support for Edge Computing in 5GC | S3‑211363 | Reply LS on IP address to GPSI translation | S2-2009339 | LS in | No |
Yes
| withdrawn | Yes | |||
S3‑211365 | Reply LS on IP address to GPSI translation | S2-2101307 | LS in | No |
Yes
| withdrawn | Yes | |||||
S3‑211391 | Reply LS on IP address to GPSI translation | S2-2009339 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211392 | Reply LS on IP address to GPSI translation | S2-2101307 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211405 | LS on EDGEAPP | S6-210630 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211406 | Reply LS on clarification regarding EEC ID | S6-210707 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211423 | 3GPP Edge Computing coordination | S6-210978 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211424 | Reply LS on IP address to GPSI translation | S6-211082 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211444 | pCR to 33.839: GBA-based solution for EEC authentication and authorization framework with ECS and EES | THALES | pCR | Approval | Yes |
Yes
| revised | No | S3‑212223 | |||
S3‑211445 | pCR to 33.839: Using TLS with GBA to protect edge interfaces | THALES | pCR | Approval | Yes |
Yes
| revised | No | S3‑212224 | |||
S3‑211501 | Changes to TR 33.839 | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211514 | Discussion on UE IP address to GPSI translation | Nokia, Nokia Shanghai-Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211565 | S3-21XXXX Authentication and Authorization with ECS EES EAS | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211566 | Conclusion for the key issue#6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212180 | |||
S3‑211567 | Editorial correction in the references clause | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211568 | Evaluation of solution #13 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211580 | Updates to solution 4 | Intel K.K. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211583 | Proposal for conclusion for Key Issue 1,2,4,6 | Intel K.K. | pCR | Yes |
Yes
| noted | No | |||||
S3‑211589 | Updates to solution 12 | Intel K.K. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212167 | |||
S3‑211628 | Solution Evaluation for solution 8 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212190 | |||
S3‑211629 | Solution Evaluation for solution 11 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212191 | |||
S3‑211707 | MEC-New key issue on EEC ID privacy protection | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211708 | MEC-Adding evaluation on Solution#8 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211709 | MEC-Adding evaluation on Solution#9 | Apple | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211710 | MEC-Adding evaluation on Solution#11 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211711 | MEC-Adding evaluation on Solution#17 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211712 | MEC-New solution on authentication between EEC and ECS | Apple | pCR | Approval | Yes |
Yes
| revised | No | S3‑212253 | |||
S3‑211713 | MEC-Kedge ID generation method | Apple | pCR | Approval | Yes |
Yes
| revised | No | S3‑212254 | |||
S3‑211779 | Discussion on an SA2 LS on IP address to GPSI translation | Qualcomm Incorporated | discussion | Information | Yes |
Yes
| noted | No | ||||
S3‑211780 | Proposed reply LS on IP address to GPSI translation | Qualcomm Incorporated | LS out | Approval | Yes |
Yes
| merged | No | S3‑212355 | |||
S3‑211781 | Proposed evaluation text for solution #23 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑212234 | |||
S3‑211782 | Proposed evaluation for solution #24 and partial conclusion for key issue #6 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212243 | |||
S3‑211853 | add evaluation to solution #23 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212234 | |||
S3‑211859 | EN removal of solution #9 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212235 | |||
S3‑211890 | Discussion on the Authentication, Authorization and Data Protection between EEC and EES/ECS | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211893 | EC: Conclusion for Key issue #1 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211894 | EC: Conclusion for Key issue #2 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211895 | EC: Conclusion for Key issue #3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑212167 | |||
S3‑211896 | EC: Conclusion for Key issue #4 and Key issue #5 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212236 | |||
S3‑211897 | EC: Conclusion for Key issue #7 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211898 | EC: Conclusion for Key issue #10 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211987 | pCR to TR 33.839: Using TLS with Edge Security Service to protect edge interfaces | THALES | pCR | Approval | Yes |
Yes
| revised | No | S3‑212225 | |||
S3‑211993 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #5 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211994 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211995 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑212206 | |||
S3‑211996 | eEDGE: Conclusion for Key Issue #4 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| merged | No | S3‑212236 | |||
S3‑212009 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #5 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212010 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212011 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212012 | eEDGE: Conclusion for Key Issue #4 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212026 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212027 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212028 | eEDGE: Conclusion for Key Issue #4 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212041 | Conclusions for KI#10 "Authorization during Edge Data Network change" | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212042 | Conclusions for KI#7 "Security of Network Information Provisioning to Local Applications with low latency procedure" | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212043 | Update Solution #17: Resolving EN on TLS ID | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212044 | Update to Solution #17: Resolving EN on Token Usage | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212045 | Update to Solution #17: Resolving EN on Multiple GPSI | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212226 | |||
S3‑212046 | Evaluation of Solution #17 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212227 | |||
S3‑212047 | Discussion on IP address to GPSI translation | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑212048 | Reply LS on IP address to GPSI translation | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S3‑212355 | |||
S3‑212049 | LS on EAS and ECS identifiers | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑212051 | Update to Solution #17: Handling multiple GPSI in IP address to GPSI translation | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212068 | Removal of Editor’s Notes | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212082 | [EDGE] Resolving EN1 in Solution#3 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212083 | [EDGE] Resolving EN3 in Solution#3 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212084 | [EDGE] Evaluation for solution#3 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212109 | [EDGE] Conclusion for KI#1, KI#2 and KI#6 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212112 | eEDGE: Additional Threat and Requirement for KI #10 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212167 | Updates to solution 12 | Intel K.K.,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S3‑211589 | |||
S3‑212180 | Conclusion for the key issue#6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211566 | |||
S3‑212190 | Solution Evaluation for solution 8 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211628 | |||
S3‑212191 | Solution Evaluation for solution 11 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211629 | |||
S3‑212206 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑211995 | |||
S3‑212223 | pCR to 33.839: GBA-based solution for EEC authentication and authorization framework with ECS and EES | THALES | pCR | Approval | Yes |
Yes
| approved | No | S3‑211444 | |||
S3‑212224 | pCR to 33.839: Using TLS with GBA to protect edge interfaces | THALES | pCR | Approval | Yes |
Yes
| approved | No | S3‑211445 | |||
S3‑212225 | pCR to TR 33.839: Using TLS with Edge Security Service to protect edge interfaces | THALES | pCR | Approval | Yes |
Yes
| approved | No | S3‑211987 | |||
S3‑212226 | Update to Solution #17: Resolving EN on Multiple GPSI | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑212045 | |||
S3‑212227 | Evaluation of Solution #17 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑212046 | |||
S3‑212234 | add evaluation to solution #23 | Huawei, Hisilicon, Qualcomm | pCR | Approval | Yes |
Yes
| approved | No | S3‑211853 | |||
S3‑212235 | EN removal of solution #9 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211859 | |||
S3‑212236 | EC: Conclusion for Key issue #4 and Key issue #5 | Huawei, Hisilicon,Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑211896 | |||
S3‑212240 | Draft TR 33.839 v0.6.0 | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212243 | Proposed evaluation for solution #24 and partial conclusion for key issue #6 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211782 | |||
S3‑212251 | MEC-Adding evaluation on Solution#9 | Apple | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212252 | MEC-Adding evaluation on Solution#9 | Apple | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212253 | MEC-New solution on authentication between EEC and ECS | Apple | pCR | Approval | Yes |
Yes
| approved | No | S3‑211712 | |||
S3‑212254 | MEC-Kedge ID generation method | Apple | pCR | Approval | Yes |
Yes
| approved | No | S3‑211713 | |||
S3‑212355 | Reply LS on IP address to GPSI translation | Ericsson, Qualcomm Incorporated | LS out | Approval | Yes |
Yes
| approved | No | S3‑212048 | |||
5.9 | Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | S3‑211358 | New KI: Secure Direct Discovery codes and filters renewal for the out-of-coverage scenario | MITRE Corporation | pCR | Approval | Yes |
YesMITRE asked to be recorded in the minutes the following statement: The companies who supported the contribution were KPN, CATT, and Interdigital. Meanwhile, Qualcomm proposed to note the document with the reasoning being that it should be addressed in SA2, and only then, security could be addressed in SA3
| noted | No | ||
S3‑211401 | LS on Layer-3 UE-to-Network Relay authentication and authorization | S2-2101623 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑211432 | LS on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism | R2-2104654 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211443 | pCR to 33.847: editorial correction to solution #11 | THALES | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211463 | Updated Solution #22: Representation of identities during broadcast | KPN N.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212132 | |||
S3‑211483 | Changes to TR 33.847 | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211484 | TR 33.847 sol#10 update | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212129 | |||
S3‑211485 | TR 33.847 sol#24 evaluation | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212130 | |||
S3‑211486 | TR 33.847 sol#25 evaluation | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212131 | |||
S3‑211524 | Updates in Solution 4 | LG Electronics Inc. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212176 | |||
S3‑211525 | Evaluation of Solution 13 | LG Electronics Inc. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212175 | |||
S3‑211526 | Remove editor's notes in key issue 1 | LG Electronics Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211569 | New solution for Key issue#4 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212177 | |||
S3‑211591 | Remark_in_solution_4 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212231 | |||
S3‑211592 | Updated Solution #23: Initial key with validity time | TNO | pCR | Approval | No |
Yes
| withdrawn | Yes | S3‑211185 | |||
S3‑211597 | Updated Solution #23: Initial key with validity time | KPN N.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212127 | |||
S3‑211618 | New solution for one-to-one communication | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211619 | Resolve EN and add evaluation to Solution #27 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211620 | Resolve EN and add evaluation to Solution #28 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211621 | Propose evaluation to Solution #32 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212188 | |||
S3‑211622 | Address Ens in Solution #33 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211623 | Add conclusions about UE-to-Network relay | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211627 | Solution Evaluation for solution 15 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212189 | |||
S3‑211663 | Add conclusion to KI#10 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212203 | |||
S3‑211664 | Discussion on security of 5G-TMSI-RNTI used for paging and UE ID in adaptation layer in 5G Prose | Huawei, HiSilicon | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211665 | Draft rely LS on R17 Layer-2 SL Relay | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑212204 | |||
S3‑211743 | LS reply on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism | OPPO | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211798 | Evaluation of Solution #18 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212169 | |||
S3‑211799 | Evaluation of Solution #19 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211800 | Conclusion of KI #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211801 | Evaluation of Solution #13 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211802 | EN resolution of Solution #19 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212170 | |||
S3‑211803 | New Key Issue on security policy handling for 5G Prose services | Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212171 | |||
S3‑211804 | EN resolution of Solution #34 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212172 | |||
S3‑211805 | Conclusion of PC5 security setup for the Layer-3 UE-to-Network relay scenario | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211806 | Evaluation of Solution #24 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211807 | Add an evaluation for solution #10 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212213 | |||
S3‑211808 | Add an evaluation for solution #15 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑212189 | |||
S3‑211809 | Update an evaluation for solution #30 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211810 | Update of solution #18 to support privacy protection | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211811 | Add an evaluation for solution #32 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211824 | pCR to TR33.847- Update Solution#3 | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211846 | pCR to TR33.847- Update Solution#4 | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211847 | pCR to TR33.847- Update Solution#29 | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑212152 | |||
S3‑211848 | pCR to TR33.847- Update Solution#30 | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑212153 | |||
S3‑211849 | pCR to TR33.847- Conclusion of KI#1 | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211850 | pCR to TR33.847- Conclusion of KI#3 | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211851 | pCR to TR33.847- Conclusion of KI#10 | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑212203 | |||
S3‑211931 | pCR to TR33.847- Conclusion of KI#12 | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211956 | Update to solution #6 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212143 | |||
S3‑211957 | Update to solution #21 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212144 | |||
S3‑211958 | Update to solution #35 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212145 | |||
S3‑211959 | Conclusion on key issue #3 and key issue #4 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211960 | Update to evaluation to solution #1 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211961 | Update to evaluation to solution #15 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑212189 | |||
S3‑211962 | Update to evaluation to solution #10 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212146 | |||
S3‑211963 | Update to evaluation to solution #13 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211964 | Conclusion on key issue #2 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211997 | ProSe: Resolving an Editor’s Note in KI #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211998 | ProSe: New Key Issue on Security Policies for PC5 Connection | Xiaomi Technology | pCR | Approval | Yes |
Yes
| merged | No | S3‑212171 | |||
S3‑211999 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212013 | ProSe: Resolving an Editor’s Note in KI #1 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212014 | ProSe: New Key Issue on Security Policies for PC5 Connection | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212015 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212029 | ProSe: Resolving an Editor’s Note in KI #1 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212030 | ProSe: New Key Issue on Security Policies for PC5 Connection | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212031 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212085 | Update for solution#1: Optimized Authorization | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212135 | |||
S3‑212114 | Update to solution #32 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212147 | |||
S3‑212127 | Updated Solution #23: Initial key with validity time | KPN N.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211597 | |||
S3‑212129 | TR 33.847 sol#10 update | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211484 | |||
S3‑212130 | TR 33.847 sol#24 evaluation | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211485 | |||
S3‑212131 | TR 33.847 sol#25 evaluation | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211486 | |||
S3‑212132 | Updated Solution #22: Representation of identities during broadcast | KPN N.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211463 | |||
S3‑212135 | Update for solution#1: Optimized Authorization | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212085 | |||
S3‑212143 | Update to solution #6 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑211956 | |||
S3‑212144 | Update to solution #21 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑211957 | |||
S3‑212145 | Update to solution #35 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑211958 | |||
S3‑212146 | Update to evaluation to solution #10 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑211962 | |||
S3‑212147 | Update to solution #32 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑212114 | |||
S3‑212152 | pCR to TR33.847- Update Solution#29 | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑211847 | |||
S3‑212153 | pCR to TR33.847- Update Solution#30 | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑211848 | |||
S3‑212154 | Draft TR 33.847 v0.6.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212169 | Evaluation of Solution #18 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211798 | |||
S3‑212170 | EN resolution of Solution #19 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211802 | |||
S3‑212171 | New Key Issue on security policy handling for 5G Prose services | Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑211803 | |||
S3‑212172 | EN resolution of Solution #34 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211804 | |||
S3‑212175 | Evaluation of Solution 13 | LG Electronics Inc. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211525 | |||
S3‑212176 | Updates in Solution 4 | LG Electronics Inc. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211524 | |||
S3‑212177 | New solution for Key issue#4 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211569 | |||
S3‑212188 | Propose evaluation to Solution #32 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211621 | |||
S3‑212189 | Solution Evaluation for solution 15 | Huawei, HiSilicon, Ericsson, Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211627 | |||
S3‑212203 | Add conclusion to KI#10 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211663 | |||
S3‑212204 | Reply LS on R17 Layer-2 SL Relay | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| approved | No | S3‑211665 | |||
S3‑212213 | Add an evaluation for solution #10 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211807 | |||
S3‑212231 | Remark to address a potential security issue in Solution #4 (LTE security-based mechanism for 5G ProSe restricted discovery) | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211591 | |||
5.10 | Study on security for enhanced support of Industrial IoT | S3‑211447 | Presentation of Report TR 33.851 | Nokia, Nokia Shanghai Bell | pCR | Presentation | Yes |
Yes
| approved | No | ||
S3‑211448 | Conclusion on UE-UE | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212125 | |||
S3‑211449 | Update of solution applicability to KI | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211450 | Update of mapping table related to documented solution in Annex | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211451 | Update to asymmetric delay attacks annex | Nokia, Nokia Shanghai Bell, | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212125 | Conclusion on UE-UE | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211448 | |||
S3‑212126 | TR_33.851_IIoT_Sec | Nokia, Nokia Shanghai Bell | draft TR | Yes |
Yes
| approved | No | |||||
5.11 | Study on Security Aspects of Enhancements for 5G Multicast-Broadcast Services | S3‑211403 | Reply LS on 5MBS progress and issues to address | S2-2102077 | LS in | Yes |
Yes
| withdrawn | Yes | |||
S3‑211590 | Update_in_solution_9 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212232 | |||
S3‑211631 | Discussion paper on MBS traffic protection | Huawei, Hisilicon | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211632 | Update to the solution 11 | Huawei, Hisilicon,China Broadcasting Network | pCR | Approval | Yes |
Yes
| revised | No | S3‑212192 | |||
S3‑211633 | Conclusion for key issue 2 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211634 | Conclusion for key issue 3 | Huawei, Hisilicon,China Broadcasting Network | pCR | Approval | Yes |
Yes
| revised | No | S3‑212193 | |||
S3‑211635 | Update to the overview | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211714 | MBS-New solution on Key distribution | Apple | pCR | Approval | Yes |
Yes
| revised | No | S3‑212255 | |||
S3‑211723 | MBS conclusions | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211812 | EN resolution of Solution #12 | Qualcomm Incorporated | pCR | Yes |
Yes
| revised | No | S3‑212173 | ||||
S3‑211813 | Evaluation of Solution #2 | Qualcomm Incorporated | pCR | Yes |
Yes
| revised | No | S3‑212174 | ||||
S3‑211814 | Evaluation of Solution #11 | Qualcomm Incorporated | pCR | Yes |
Yes
| merged | No | S3‑212192 | ||||
S3‑211877 | Updates to solutoin #3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212239 | |||
S3‑211878 | Updates to solutoin #4 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211879 | Updates to solutoin #5 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211880 | Add conclusion for key issue #1 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211932 | Editor Note removal for Solution#10 | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212250 | |||
S3‑211933 | Evaluation for Solution#10 | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212096 | Updates to solution#13 on Key refresh mechanism | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212097 | Updates to solution#13 on support for multiple MB-SMF | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212139 | |||
S3‑212098 | Updates to solution#13 on MBS security algorithm selection | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212140 | |||
S3‑212139 | Updates to solution#13 on support for multiple MB-SMF | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212097 | |||
S3‑212140 | Updates to solution#13 on MBS security algorithm selection | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212098 | |||
S3‑212173 | EN resolution of Solution #12 | Qualcomm Incorporated | pCR | Yes |
Yes
| approved | No | S3‑211812 | ||||
S3‑212174 | Evaluation of Solution #2 | Qualcomm Incorporated | pCR | Yes |
Yes
| approved | No | S3‑211813 | ||||
S3‑212178 | TR 33.850 for MBS security | Huawei, Hisilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212192 | Update to the solution 11 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211632 | |||
S3‑212193 | Conclusion for key issue 3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | S3‑211634 | |||
S3‑212232 | Additions in Solution #9 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211590 | |||
S3‑212239 | Updates to solutoin #3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211877 | |||
S3‑212250 | Editor Note removal for Solution#10 | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211932 | |||
S3‑212255 | MBS-New solution on Key distribution | Apple | pCR | Approval | Yes |
Yes
| approved | No | S3‑211714 | |||
5.12 | Study on enhanced security support for Non-Public Networks | S3‑211390 | LS on support of PWS over SNPN | S1-210368 | LS in | Yes |
Yes
| postponed | No | |||
S3‑211394 | LS on UE capabilities indication in UPU | S2-2101072 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑211395 | LS on updating the Credentials Holder controlled lists for SNPN selection | S2-2101077 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211414 | Reply LS on support of PWS over SNPN | S2-2102963 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211428 | Reply LS on support of PWS over SNPN | R2-2104640 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211439 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection | C1-212419 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211441 | Reply LS on UE capabilities indication in UPU | C1-212599 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑211467 | Changes to TR 33.857 | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211521 | Further conclusions for KI #1 | CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211570 | New solution on control plane based provisioning PS to AUSF | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211571 | New solution on control plane based provisioning PS to UDM | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211573 | Updates to solution 14: Removal of Editor's notes: Certificate Handling | Intel K.K. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212166 | |||
S3‑211574 | Updates to solution 14: Removal of Editor’s notes: One-Way | Intel K.K. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211577 | Proposal for conclusion for Key Issue 4 | Intel K.K. | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑211578 | Proposal for conclusion for Key Issue 4 | Intel K.K. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211579 | Updates to solution 14: Removal of Editor’s notes: Three Authentication | Intel K.K. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211652 | Solution Update for Solution #5 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212197 | |||
S3‑211653 | Evaluation for Solution #12 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212198 | |||
S3‑211724 | Solution for privacy protection during initial access | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211725 | Analysis of security properties of architectural options | Nokia, Nokia Shanghai Bell | pCR | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211726 | Proposal for a conclusion on KI#4 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211727 | Resolution of editor’s note in solution 19 related to bidding down attacks. | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211728 | Resolution of Editor's Note in Solution 19 related to provisioning of server certificate the the onboarding UE. | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212241 | |||
S3‑211729 | Resolution of an Editor's Note in Solution 19 related to security implications of the solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211730 | Resolution of Editor's Note in Solution 19 related to construction of SUCI. | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211731 | Resolution of Editor's Note in Solution 19 related to UDM involvementUpdate | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211732 | Evalution and system impact for soluiton 19 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212248 | |||
S3‑211733 | Update to Solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211734 | LS on Feedback on Key Issue #1 "Enhancements to Support SNPN along with credentials owned by an entity separate from the SNPN" | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211735 | LS on architectural clarifications related to onboarding without client authentication | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211741 | Discussion capability negotiation for the parameters contained in UPU | Ericsson Japan K.K. | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211744 | draft LS reply: UE capabilities indication in UPU | Ericsson Japan K.K. | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211767 | Conclusions for KI#1 (external entity) on SUPI privacy and usage of MSK | Ericsson, Huawei, Interdigital, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211768 | Conclusions for KI#1 (external entity) on AAA interworking | Ericsson, China Mobile, Huawei, InterDigital, Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211769 | Conclusions for KI#4 (initial access) | Ericsson, Huawei, InterDigital, Lenovo, Motorola Mobility, Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211770 | Conclusions for KI#2 on secure provisioning of PNI-NPN credentials | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211815 | Discussion on SA2 LS on UE capabilities indication in UPU | Qualcomm Incorporated | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211816 | pCR: Additional conclusions for KI #1 | Qualcomm Incorporated | pCR | Yes |
Yes
| noted | No | |||||
S3‑211856 | reply LS on UE capabilities indication in UPU | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211860 | Discussion on UE capabilities indication in UPU | Huawei, Hisilicon | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211861 | Conclusion on KI#5 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑212207 | |||
S3‑212000 | eNPN: Conclusion on KI#8 with Solution#18 Updating | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑212207 | |||
S3‑212001 | eNPN: Solution of Security Mechansim for UP Provisioning of Credentials | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212002 | eNPN: New KI of Security Protection for the Update of Preferred SNPN List | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212003 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection | Xiaomi Technology | LS out | Approval | Yes |
Yes
| revised | No | S3‑212208 | |||
S3‑212016 | eNPN: Conclusion on KI#8 with Solution#18 Updating | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212017 | eNPN: Solution of Security Mechansim for UP Provisioning of Credentials | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212018 | eNPN: New KI of Security Protection for the Update of Preferred SNPN List | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212019 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection | Xiaomi Technology | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212032 | eNPN: Conclusion on KI#8 with Solution#18 Updating | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212033 | eNPN: Solution of Security Mechansim for UP Provisioning of Credentials | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212034 | eNPN: New KI of Security Protection for the Update of Preferred SNPN List | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212035 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection | Xiaomi Technology | LS out | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212054 | pCR: Conclusion for KI #1 on addressing security threat against KAUSF | CableLabs | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212056 | pCR: Conclusion for KI #1 on addressing security threat against KAUSF | CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212072 | A new onboarding solution addressing KI#2 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212166 | Updates to solution 14: Removal of Editor's notes: Certificate Handling | Intel K.K. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211573 | |||
S3‑212197 | Solution Update for Solution #5 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211652 | |||
S3‑212198 | Evaluation for Solution #12 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211653 | |||
S3‑212207 | eNPN: Conclusion on KI#8 with Solution#18 Updating | Xiaomi Technology,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S3‑212000 | |||
S3‑212208 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection | Xiaomi Technology | LS out | Approval | Yes |
Yes
| approved | No | S3‑212003 | |||
S3‑212220 | draft TR 33.857 v0.6.0 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212241 | Resolution of Editor's Note in Solution 19 related to provisioning of server certificate the the onboarding UE. | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211728 | |||
S3‑212248 | Evalution and system impact for soluiton 19 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211732 | |||
5.13 | Study on security aspects of the Disaggregated gNB Architecture |   | ||||||||||
5.14 | Study on User Consent for 3GPP services | S3‑211654 | Solution Update for Solution #2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212199 | |
S3‑211655 | Update on Observations related to Regulations | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212200 | |||
S3‑211656 | Add Security Requirement for Key Issue #3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212201 | |||
S3‑211715 | UC3S-Requirement on revoking user consent | Apple | pCR | Approval | Yes |
Yes
| revised | No | S3‑212256 | |||
S3‑211852 | Address ENs for User Consent for Exposure of information to Edge Applications in Real Time | China Unicom | pCR | Yes |
Yes
| noted | No | |||||
S3‑212052 | Intro update | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| approved | No | |||||
S3‑212080 | Solution on user's consent for exposure of information to Edge Applications | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212081 | Solution on user consent for UE data collection | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212108 | [UC3S] Update to Conclusion | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212142 | |||
S3‑212123 | S on user consent revocation to SA2 | Nokia | LS out | Yes |
Yes
| approved | No | |||||
S3‑212142 | [UC3S] Update to Conclusion | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212108 | |||
S3‑212199 | Solution Update for Solution #2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211654 | |||
S3‑212200 | Update on Observations related to Regulations | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211655 | |||
S3‑212201 | Add Security Requirement for Key Issue #3 | Huawei, HiSilicon, Apple, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211656 | |||
S3‑212205 | Draft TR 33.867 | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212256 | UC3S-Requirement on revoking user consent | Apple | pCR | Approval | Yes |
Yes
| approved | No | S3‑211715 | |||
5.15 | Study on security aspects of the 5GMSG Service | S3‑211838 | Add evaluation to solution #4 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑212216 | |
S3‑212086 | [5gmsg] Transport security protection for MSGin5G-3 interface | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212087 | [5gmsg] Resolving ENs in solution#1 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212088 | [5gmsg] Resolving ENs in solution#5 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212089 | [5gmsg] Resolving ENs in solution#6 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212136 | |||
S3‑212090 | [5gmsg] Resolving ENs in solution#7 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212137 | |||
S3‑212136 | [5gmsg] Resolving ENs in solution#6 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212089 | |||
S3‑212137 | [5gmsg] Resolving ENs in solution#7 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212090 | |||
S3‑212215 | draft TR 33.862 0.5.0 | China Mobile E-Commerce Co. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212216 | Add evaluation to solution #4 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑211838 | |||
5.16 | Study on security aspects of enablers for Network Automation (eNA) for the 5G system (5GS) Phase 2 | S3‑211400 | LS Response on Network Slice PA Charging per maximum utilized bandwidth | S2-21001347 | LS in | Yes |
Yes
| withdrawn | Yes | |||
S3‑211417 | Reply LS on RAT type for network monitoring | S2-2103237 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211418 | LS on security aspects for the method of collection of data from the UE | S2-213263 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑211422 | LS on Transaction Information - Dispersion Analytics | S2-2103268 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑211464 | Solution on Remote Attestation for 5GS | Johns Hopkins University APL, US National Security Agency, CISA ECD, InterDigital, Fraunhofer SIT, CableLabs, AT&T, Verizon Wireless, NIST | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211465 | Discussion on Remote Attestation for 5GS | Johns Hopkins University APL, US National Security Agency, CISA ECD, InterDigital, Fraunhofer SIT, CableLabs, AT&T, Verizon Wireless, NIST | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211466 | Changes to TR 33.866 | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211657 | Conclusion for Key Issue #3.1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211658 | Conclusion for Key Issue #3.2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211659 | Conclusion for Key Issue #1.1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211661 | Delete EN of Solution#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212202 | |||
S3‑211691 | EN Resolution Anomolous NF Behaviour | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212163 | |||
S3‑211692 | Output analytics from NWDAF to detect Anomalous NF Behaviour | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211693 | Solution on Processing of tampered data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212160 | |||
S3‑211694 | EN on solution relation with user consent study | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211695 | EN resolution on solution privacy preservation of transmitted data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211696 | Solution on Authorization of NF Service Consumers for data access via DCCF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212161 | |||
S3‑211697 | Solution on Authorization of NF Service Consumers to access data from ADRF via DCCF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212162 | |||
S3‑211698 | Reply LS on Transaction Information - Dispersion Analytics | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S3‑212159 | |||
S3‑211699 | KI update Dispersion Analytics against DDoS | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211823 | Reply-LS on security aspects for the method of collection of data from the UE | OPPO | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑211839 | Add evaluation to solution #1 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211840 | Add deatails to solution #6 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211841 | Add evaluation to solution #6 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211854 | add ENs to solution#5 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211865 | New solution to key issue #3.3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212237 | |||
S3‑211866 | New solution to key issue #2.1 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211867 | New solution to key issue #1.5 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑212238 | |||
S3‑212055 | Removal of Editor’s Note of Solution#5 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212057 | Solution on Authorization of Data Consumers for data access via DCCF | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212221 | |||
S3‑212058 | Solution on Authorization of Data Consumers for data access via DCCF through Messaging Framework | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212059 | New KI Untrusted DCCF for secure data collection | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212060 | Solution for Untrusted DCCF for secure data collection | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212077 | Discussion on detection of MitM attack using NWDAF | Samsung | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑212078 | Solution on analytics for MitM attack detection | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212079 | Solution on analytics for DoS attack detection | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212118 | Removal of Editor’s Note of Solution#4 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212158 | Reply LS on RAT type for network monitoring | S2-2103237 | LS out | Yes |
Yes
| approved | No | |||||
S3‑212159 | Reply LS on Transaction Information - Dispersion Analytics | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | S3‑211698 | |||
S3‑212160 | Solution on Processing of tampered data | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211693 | |||
S3‑212161 | Solution on Authorization of NF Service Consumers for data access via DCCF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211696 | |||
S3‑212162 | Solution on Authorization of NF Service Consumers to access data from ADRF via DCCF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211697 | |||
S3‑212163 | EN Resolution Anomolous NF Behaviour | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211691 | |||
S3‑212202 | Delete EN of Solution#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211661 | |||
S3‑212214 | draft TR 33.866 0.5.0 | China Mobile E-Commerce Co. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212221 | Solution on Authorization of Data Consumers for data access via DCCF | Ericsson, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑212057 | |||
S3‑212237 | New solution to key issue #3.3 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211865 | |||
S3‑212238 | New solution to key issue #1.5 | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑211867 | |||
5.17 | Study on the security of AMF re-allocation | S3‑211502 | Solution#8 Clarifications | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑211572 | New solution for AMF re-allocation | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑212179 | |||
S3‑211737 | Update to Solution #4 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑212228 | |||
S3‑211738 | Update to Solution #6 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑212229 | |||
S3‑211739 | Update to Solution #7 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑212230 | |||
S3‑211742 | Conclusion on Key Issue #1 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211789 | Addressing the Editors’ Note in solution #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑212242 | |||
S3‑211790 | Missing details on handling of possible unprotected messages in solution #3 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211791 | ABBA parameter handling in solutions #6 and #7 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211914 | Update to solution #2 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212156 | |||
S3‑211915 | AMF reallocation via direct NAS reroute: handling of UL NAS COUNT corresponding to RR message derivation | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211916 | AMF re-allocation: Analysis of solutions | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑211917 | AMF re-allocation: Conclusion | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211918 | AMF re-allocation: Solution #9 updates | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212157 | |||
S3‑211920 | AMF re-allocation: Discussion about the WID | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑212093 | Update to solution#9 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212138 | |||
S3‑212099 | Comparison of solutions and propose way forward | Samsung | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑212100 | Updates to solution#5 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212101 | Removal of Editor's Note in Solution#5 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212102 | Updates to evaluation in solution#5 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212124 | LS on Clarification of AMF Reallocation and network slice selection | Lenovo | LS out | Approval | Yes |
Yes
| approved | No | ||||
S3‑212138 | Solution to reroute 5G NAS security context via RAN | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212093 | |||
S3‑212155 | Draft TR 33.864 v0.5.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | Ericsson España S.A. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212156 | Update to solution #2 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑211914 | |||
S3‑212157 | AMF re-allocation: Solution #9 updates | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑211918 | |||
S3‑212179 | New solution for AMF re-allocation | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑211572 | |||
S3‑212228 | Update to Solution #4 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑211737 | |||
S3‑212229 | Update to Solution #6 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑211738 | |||
S3‑212230 | Update to Solution #7 | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑211739 | |||
S3‑212242 | Addressing the Editors’ Note in solution #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑211789 | |||
5.18 | Study on Security for NR Integrated Access and Backhaul | S3‑211362 | LS on using MOBIKE in Integrated Access and Backhaul system | R3-211297 | LS in | Yes |
Yes
| replied to | No | |||
S3‑211519 | Discussion on R3 LS on MOBIKE | Nokia, Nokia Shanghai-Bell | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S3‑211520 | REly LS on MOBIKE usage in IAB | Nokia, Nokia Shanghai-Bell | LS out | Approval | Yes |
Yes
| revised | No | S3‑212164 | |||
S3‑211637 | Clarification to protect F1 interface security for IAB in NR-DC mode | Huawei, Hisilicon | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212107 | [IAB] Unprotected BAP Control PDU exchange | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212141 | |||
S3‑212141 | [IAB] Unprotected BAP Control PDU exchange | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212107 | |||
S3‑212164 | Reply LS on MOBIKE usage in IAB | Nokia, Nokia Shanghai-Bell | LS out | Approval | Yes |
Yes
| approved | No | S3‑211520 | |||
S3‑212233 | Draft 33.824 v0.9.0 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.19 | Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules | S3‑211402 | LS on System support for Multi-USIM devices | S2-2102039 | LS in | Yes |
Yes
| noted | No | |||
S3‑211431 | LS on NAS-based busy indication | R2-2104354 | LS in | Yes |
Yes
| noted | No | |||||
S3‑211594 | Updates to solution 1 | Intel K.K. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211595 | Conclusion to Key issue 1,2 | Intel K.K. | pCR | Approval | Yes |
Yes
| revised | No | S3‑212165 | |||
S3‑211596 | Key issue on security aspects of Paging Cause | Intel K.K. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211666 | A new Key issue on paging cause | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211667 | A new solution to paging cause | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212004 | MUSIM: New Solution for Key Issue #1 for RRC_Idle UE | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212005 | MUSIM: New Solution for Key Issue #1 for RRC_Inactive UE | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212006 | MUSIM: Conclusion for Key Issue #2 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑212209 | |||
S3‑212020 | MUSIM: New Solution for Key Issue #1 for RRC_Idle UE | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212021 | MUSIM: New Solution for Key Issue #1 for RRC_Inactive UE | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212022 | MUSIM: Conclusion for Key Issue #2 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212036 | MUSIM: New Solution for Key Issue #1 for RRC_Idle UE | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212037 | MUSIM: New Solution for Key Issue #1 for RRC_Inactive UE | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212038 | MUSIM: Conclusion for Key Issue #2 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212165 | Conclusion to Key issue 1,2 | Intel K.K. | pCR | Approval | Yes |
Yes
| approved | No | S3‑211595 | |||
S3‑212168 | draft TR Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules | Intel K.K. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑212209 | MUSIM: Conclusion for Key Issue #2 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑212006 | |||
S3‑212259 | Cover sheet TR 33.873 | Intel K.K. | TS or TR cover | Yes |
Yes
| revised | No | S3‑212374 | ||||
S3‑212374 | Cover sheet TR 33.873 | Intel K.K. | TS or TR cover | Yes |
Yes
| approved | No | S3‑212259 | ||||
5.20 | Study on enhanced Security Aspects of the 5G Service Based Architecture | S3‑211765 | Update Solution #5: End-to-end integrity protection of HTTP body and method | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑211766 | Evaluation of Solution #3 "Using existing procedures for authorization of SCP to act on behalf of an NF Consumer" | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑212372 | |||
S3‑211862 | Discussion on NF Domain granularity authorization | Huawei, Hisilicon | discussion | Approval | Yes |
Yes
| noted | No | ||||
S3‑211863 | Update to the SID of eSBA for NF Domain granularity authorization | Huawei, Hisilicon | SID revised | Approval | Yes |
Yes
| noted | No | ||||
S3‑211864 | New KI on NF Domain granularity authorization | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211901 | Requirement of subscribe-notification key issue | Huawei, Hisilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211968 | KI1 Security requirements for authentication of NRF and NFp in indirect commuication | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211969 | Sol1 deployment scenarios | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212298 | |||
S3‑211970 | ENs on Sol1 Service response verification in model C | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212299 | |||
S3‑211971 | Threats and requirements to KI3 on Service access authorization in Subscribe-Notify | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211972 | Solution on URI verification and notification acceptance | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211973 | KI on Access token usage by all NFs of an NF Set | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑211974 | Solution on Access token request for NF Set | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212302 | |||
S3‑211975 | EN resolution on sol 2 - NFc authorizing SCP to act on its behalf | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212300 | |||
S3‑211976 | Evaluation on sol 2 - NFc authorizing SCP to act on its behalf | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212301 | |||
S3‑211977 | Evaluation to sol 3 - proof of possession of CCA NFc authorizes the SCP to act on behalf of an NFc | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S3‑212372 | |||
S3‑211978 | KI on Roaming case for token-based authorization | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211979 | Trust model | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212303 | |||
S3‑212094 | New solution for key issue#1: Authentication of NF service producer in indirect communication | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑212292 | |||
S3‑212095 | New solution for key issue#3: Authorization of notification request | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212292 | New solution for key issue#1: Authentication of NF service producer in indirect communication | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑212094 | |||
S3‑212297 | TR 33.875-030 | Nokia Germany | draft TR | Yes |
Yes
| approved | No | |||||
S3‑212298 | Sol1 deployment scenarios | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211969 | |||
S3‑212299 | ENs on Sol1 Service response verification in model C | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211970 | |||
S3‑212300 | EN resolution on sol 2 - NFc authorizing SCP to act on its behalf | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211975 | |||
S3‑212301 | Evaluation on sol 2 - NFc authorizing SCP to act on its behalf | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211976 | |||
S3‑212302 | Solution on Access token request for NF Set | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212394 | S3‑211974 | ||
S3‑212394 | Solution on Access token request for NF Set | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑212302 | |||
S3‑212303 | Trust model | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211979 | |||
S3‑212372 | Evaluation of Solution #3 "Using existing procedures for authorization of SCP to act on behalf of an NF Consumer" | Ericsson, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211766 | |||
5.21 | Study on enhanced security for network slicing Phase 2 | S3‑211482 | New KI: DoS on Network Slice Quota | US National Security Agency, Johns Hopkins University APL, CISA ECD, NIST | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||
S3‑211604 | update to KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑212212 | |||
S3‑211605 | new key issue proposal | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑211794 | Some analysis for key issue #1 | Qualcomm Incorporated | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑211954 | New KI: DoS on Network Slice Quota | US National Security Agency, Johns Hopkins University APL, CISA ECD, NIST | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212007 | eNS2: Add Threat Analysis to KI #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑212210 | |||
S3‑212008 | eNS2: New Key Issue on Primary Authentication with NSAC | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212023 | eNS2: Add Threat Analysis to KI #1 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212024 | eNS2: New Key Issue on Primary Authentication with NSAC | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212039 | eNS2: Add Threat Analysis to KI #1 | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212040 | eNS2: New Key Issue on Primary Authentication with NSAC | Xiaomi Technology | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑212186 | Draft TR33.874 eNS2_SEC | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| revised | No | S3‑212279 | |||
S3‑212210 | eNS2: Add Threat Analysis to KI #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑212212 | S3‑212007 | ||
S3‑212212 | eNS2: Add Threat Analysis to KI #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑212210 | |||
S3‑212279 | draft TR 33.874 | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | S3‑212186 | |||
5.22 | Study on non-seamless WLAN Offload in 5GS using 3GPP credentials | S3‑211515 | Skeleton for 5G NSWO TR | Nokia, Nokia Shanghai-Bell | draft TR | Yes |
Yes
| approved | No | |||
S3‑211516 | Scope for 5G NSWO TR | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212148 | |||
S3‑211517 | Introduction for 5G NSWO TR | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212149 | |||
S3‑211518 | KI: Support of EAP Authentication for 5G NSWO | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑212150 | |||
S3‑212111 | Key Issue on subscription identifier privacy | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| merged | No | S3‑212150 | |||
S3‑212113 | Solution on NSWO authentication | Lenovo, Motorola Mobility | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑212148 | Scope for 5G NSWO TR | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211516 | |||
S3‑212149 | Introduction for 5G NSWO TR | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211517 | |||
S3‑212150 | KI: Support of EAP Authentication for 5G NSWO | Nokia, Nokia Shanghai-Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑211518 | |||
S3‑212151 | New TR33.811 for 5G NSWO | Nokia, Nokia Shanghai Bell | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.23 | New study item proposals | S3‑211477 | Standardising Automated TLS Certificate Management in SBA | BT plc | SID new | Discussion | Yes |
Yes
| revised | No | S3‑212390 | |
S3‑212390 | Standardising Automated TLS Certificate Management in SBA | BT plc | SID new | Agreement | Yes |
Yes
| agreed | No | S3‑211477 | |||
S3‑211668 | Discussion on penetration testing | Huawei, HiSilicon | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑211669 | A new SID - penetration testing | Huawei, HiSilicon | SID new | Approval | Yes |
Yes
| noted | No | ||||
S3‑211670 | Draft rely LS to GSMA on penetration testing | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| noted | No | ||||
5.24 | Other study areas (no release restrictions) |   | ||||||||||
6 | CVD and research | S3‑211382 | User location identification from Carrier Aggregation secondary cell activation messages | GSMA | LS in | Yes |
Yes
| replied to | No | |||
S3‑211473 | CR to TS 43.020 - R16 - Removal of support for GEA2 | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| revised | No | S3‑212361 | |||
S3‑211490 | Discussion document on the use of GEA1 and GEA2 | VODAFONE Group Plc | discussion | Information | Yes |
Yes
| noted | No | ||||
S3‑211491 | CR to TS 43.020 - R11 - Removal of GEA1 and GEA2 due to security concerns | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| revised | No | S3‑212362 | |||
S3‑211492 | CR to TS 43.020 - R12 - Depreciation of GEA2 due to security concerns | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| revised | No | S3‑212363 | |||
S3‑211493 | CR to TS 43.020 - R13 - Removal of GEA1 and GEA2 due to security concerns - mirror | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| revised | No | S3‑212364 | |||
S3‑211494 | CR to TS 43.020 - R14 - Removal of GEA1 and GEA2 due to security concerns - mirror | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| revised | No | S3‑212370 | |||
S3‑211495 | CR to TS 43.020 - R15 - Removal of GEA1 and GEA2 due to security concerns - mirror | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| revised | No | S3‑212373 | |||
S3‑211615 | Reply LS on SLIC | Nanjing Ericsson Panda Com Ltd | LS out | Approval | Yes |
Yes
| merged | No | S3‑212305 | |||
S3‑211638 | Reply LS on User location identification from Carrier Aggregation secondary cell activation messages | Huawei, Hisilicon | LS out | Approval | Yes |
Yes
| revised | No | S3‑212305 | |||
S3‑212361 | CR to TS 43.020 - R16 - Removal of support for GEA2 | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211473 | |||
S3‑212362 | CR to TS 43.020 - R11 - Removal of GEA1 and GEA2 due to security concerns | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211491 | |||
S3‑212363 | CR to TS 43.020 - R12 - Depreciation of GEA2 due to security concerns | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211492 | |||
S3‑212364 | CR to TS 43.020 - R13 - Removal of GEA1 and GEA2 due to security concerns - mirror | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211493 | |||
S3‑212370 | CR to TS 43.020 - R14 - Removal of GEA1 and GEA2 due to security concerns - mirror | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211494 | |||
S3‑212373 | CR to TS 43.020 - R15 - Removal of GEA1 and GEA2 due to security concerns - mirror | VODAFONE Group Plc | CR | Agreement | Yes |
Yes
| agreed | No | S3‑211495 | |||
7 | Any Other Business | S3‑211359 | SA3 meeting calendar | SA WG3 Chair | other | Information | Yes |
Yes
| revised | No | S3‑211433 | |
S3‑211360 | Draft agenda for SA3 104-e | SA WG3 Chair | agenda | Discussion | No |
Yes
| withdrawn | Yes | ||||
S3‑211433 | SA3 meeting calendar | SA WG3 Chair | other | Information | Yes |
Yes
| noted | No | S3‑211359 |