Tdoc List
2023-04-27 14:29
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Agenda and Meeting Objectives | S3‑231700 | Agenda | SA WG3 Chair | agenda | Yes |
Yes
| approved | No | |||
S3‑231701 | Process for SA3#110AdHoc-e | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
S3‑231702 | Process and agenda planning for SA3#110AdHoc-e | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
2 | Meeting Reports |   | ||||||||||
3 | Reports and Liaisons from other Groups (related to Rel-18 release content only) | S3‑231703 | LS on user consent for UE location sharing | S6-230351 | LS in | Yes |
Yes
| postponed | No | |||
S3‑231704 | LS on UE event reporting over a user plane connection to LCS client or AF | S2-2301789 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑231705 | LS on LPP message and supplementary service event report over a user plane connection between UE and LMF | S2-2301857 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑231706 | LS Reply to 3GPP on SEPP Certificates | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S3‑231707 | LS on UE specific data and analytics exchange between HPLMN and VPLMN | S2-2303548 | LS in | Yes |
Yes
| noted | No | |||||
S3‑231708 | Reply LS on Support PIN application architecture and interaction | S2-2303698 | LS in | Yes |
Yes
| noted | No | |||||
S3‑231709 | Reply LS on SNAAPP requirements clarifications | S1-230591 | LS in | Yes |
Yes
| noted | No | |||||
S3‑231710 | Reply LS on the data and analytics exchange between two NWDAFs in different PLMNs | S2-2303563 | LS in | Yes |
Yes
| noted | No | |||||
S3‑231711 | Reply LS on Progress and open issues for NPN enhancements in Rel-18 | S2-2303689 | LS in | Yes |
Yes
| noted | No | |||||
S3‑231712 | Reply LS on clarification on user consent for AI/ML | S2-2303834 | LS in | Yes |
Yes
| noted | No | |||||
S3‑231713 | LS reply to Reply LS on Network federation interface for Telco edge consideration | S5-233146 | LS in | Yes |
Yes
| noted | No | |||||
S3‑231714 | LS on Alignment of SA3 security aspects for Personal IoT Networks | S6-230792 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑231715 | Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | S6-231061 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑231716 | LS to SA2 on Sidelink positioning procedure | R2-2302285 | LS in | Yes |
Yes
| noted | No | |||||
S3‑231717 | LS to 3GPP on GSMA requirements regarding intermediaries in the roaming ecosystem (Roaming Hub, IPX and RVAS Providers) | GSMA | LS in | Yes |
Yes
| postponed | No | |||||
S3‑231718 | LS response to 3GPP on IPX Requirements for 5GS Roaming | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S3‑231719 | LS Roaming Value Added Service Requirements | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S3‑231720 | LS with Roaming Hubbing requirements and LS response to 3GPP SA3 LS(S3-214456) on 5GS Roaming Hubbing | GSMA | LS in | Yes |
Yes
| noted | No | |||||
S3‑231721 | LS on GSMA 5GMRR Working Solution Assumption L-PRINS and Data Session Control | GSMA | LS in | Yes |
Yes
| postponed | No | |||||
S3‑231758 | Reply LS on LPP message and supplementary service event report over a user plane connection between UE and LMF and LS on UE event reporting over a user plane connection to LCS client or AF | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S3‑232232 | |||
S3‑231902 | Reply LS on user plane connection between UE and LCS client, AF or LMF | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| merged | No | S3‑232232 | |||
S3‑231919 | Reply LS on user consent for UE location sharing | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑231964 | Reply LS on IPX Requirements for 5GS Roaming from GSMA | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑231965 | Reply LS on AFId parameter value in EES invocation of Nnef_UEId_Get service | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑231966 | Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑231973 | Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | Apple | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑231974 | Reply LS on user consent for UE location sharing | Apple | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑232090 | LS reply on LPP message and supplementary service event report over a user plane connection between UE and LMF | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| merged | No | S3‑232232 | |||
S3‑232091 | LS reply on UE event reporting over a user plane connection to LCS client or AF | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| merged | No | S3‑232232 | |||
S3‑232155 | LS on Roaming architecture updates | NTT DOCOMO INC. | LS out | Yes |
Yes
| approved | No | |||||
S3‑232232 | Reply LS on LPP message and supplementary service event report over a user plane connection between UE and LMF and LS on UE event reporting over a user plane connection to LCS client or AF | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S3‑231758 | |||
4 | Work areas (Rel-18) |   | ||||||||||
4.1 | New WID on Security Assurance Specification for Management Function (MnF) |   | ||||||||||
4.2 | New WID on SECAM and SCAS for 3GPP virtualized network products |   | ||||||||||
4.3 | New WID on Mission critical security enhancements phase 3 |   | ||||||||||
4.4 | New WID on Security Assurance Specification (SCAS) for 5G Rel-17 Features |   | ||||||||||
4.5 | New WID on Security Assurance Specification for the Authentication and Key Management for Applications (AKMA) Anchor Function Function (AAnF) |   | ||||||||||
4.6 | New WID on SCAS for split-gNB product classes |   | ||||||||||
4.7 | Service Based Architecture (Rel-15/16/17) |   | ||||||||||
4.8 | Security Aspects of Proximity based services in 5GS ProSe (Rel-17) |   | ||||||||||
4.9 | All topics (Rel-15/16/17/18 ) |   | ||||||||||
4.10 | ProSe Secondary Authentication | S3‑231772 | Living document to TS 33.503 for Prose Secondary Authentication | InterDigital, Europe, Ltd. | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232114 | |
S3‑231773 | Clearing EN on Remote UE Report | InterDigital, Europe, Ltd. | other | Approval | Yes |
Yes
| revised | No | S3‑232104 | |||
S3‑231774 | Clearing EN on Remote UE Subscription update | InterDigital, Europe, Ltd. | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑231775 | Clearing EN on Remote UE GPSI | InterDigital, Europe, Ltd. | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑231776 | Clearing EN on Revocation procedure | InterDigital, Europe, Ltd. | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑231777 | Naming alignment from 5GPRUK to CP-PRUK | InterDigital, Europe, Ltd. | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑231778 | draft LS on Prose Secondary Authentication | InterDigital, Europe, Ltd. | LS out | Approval | Yes |
Yes
| revised | No | S3‑232108 | |||
S3‑231887 | Update the PDU Session secondary authentication of Remote UE | China Telecom Corporation Ltd. | other | Approval | Yes |
Yes
| merged | No | S3‑232104 | |||
S3‑231931 | update the procedure to align with the R-17 agreement | Huawei, HiSilicon | other | Approval | Yes |
Yes
| merged | No | S3‑232104 | |||
S3‑231935 | Addressing Editor's Note on remote UE's subscription update notification | Huawei, HiSilicon | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑231936 | pCR on introducing another PC5-S message to the Remote UE | Huawei, HiSilicon | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑231952 | [Draft] LS on ProSe Secondary Authentication | Ericsson | LS out | Approval | Yes |
Yes
| merged | No | S3‑232108 | |||
S3‑231953 | Discussion of secondary authentication & authorization for Layer-3 UE-to-Network relaying | Ericsson | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑232104 | Clearing EN on Remote UE Report | InterDigital, Europe, Ltd., China Telecom, Huawei, HiSilicon | other | Approval | Yes |
Yes
| approved | No | S3‑231773 | |||
S3‑232108 | LS on Prose Secondary Authentication | InterDigital, Europe, Ltd., Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S3‑231778 | |||
S3‑232114 | Living document to TS 33.503 for Prose Secondary Authentication | InterDigital, Europe, Ltd. | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231772 | |||
4.11 | New WID on DTLS protocol profile for AKMA and GBA | S3‑231791 | Proposed updates to the DTLS text | Qualcomm Incorporated | other | Approval | Yes |
Yes
| merged | No | S3‑232135 | |
S3‑231827 | Changes to living document for GBA DTLS | THALES | other | Approval | Yes |
Yes
| revised | No | S3‑232135 | |||
S3‑231841 | Living document for AKMA DTLS to TS 33.535 | ZTE Corporation | draftCR | Yes |
Yes
| noted | No | |||||
S3‑231842 | Living document for GBA DTLS to TS 33.220 | ZTE Corporation | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232128 | |||
S3‑232064 | Enable DTLS in Ua star protocol | Xiaomi communications | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232128 | Living document for GBA DTLS to TS 33.220 | ZTE Corporation | draftCR | Approval | Yes |
Yes
| email approval | No | S3‑231842 | |||
S3‑232135 | Changes to living document for GBA DTLS | THALES | other | Approval | Yes |
Yes
| approved | No | S3‑231827 | |||
4.12 | New WID on Security Aspects of the 5G Service Based Architecture Phase 2 |   | ||||||||||
4.13 | New WID on IETF OSCORE protocol profiles for GBA and AKMA | S3‑231766 | Living document for AKMA_GBA_OSCORE: draftCR to TS 33.220, IETF OSCORE as GBA Ua protocol | Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232213 | |
S3‑231767 | pCR to GBA OSCORE living doc: Clarifications | Ericsson | other | Approval | Yes |
Yes
| revised | No | S3‑232212 | |||
S3‑231768 | Proposal for a living document for AKMA_GBA_OSCORE: draftCR to TS 33.535, IETF OSCORE as AKMA Ua* protocol | Ericsson | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231826 | Changes to living document for GBA OSCORE | THALES | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑232068 | Enable OSCORE in Ua star protocol | Xiaomi communications | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232069 | Resolve EN for choosing GBA_U GBA_ME | Xiaomi communications | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑232212 | pCR to GBA OSCORE living doc: Clarifications | Ericsson | other | Approval | Yes |
Yes
| approved | No | S3‑231767 | |||
S3‑232213 | Living document for AKMA_GBA_OSCORE: draftCR to TS 33.220, IETF OSCORE as GBA Ua protocol | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231766 | |||
4.14 | New WID on Security aspect of home network triggered primary authentication | S3‑231765 | pCR to living document to TS 33.501: Clarifications and removals of Editor's Notes | Ericsson | other | Approval | Yes |
Yes
| revised | No | S3‑232211 | |
S3‑231815 | EN removal on UE reachability scenario | Nokia, Nokia Shanghai Bell | other | Agreement | Yes |
Yes
| merged | No | S3‑232211 | |||
S3‑231816 | EN removal multiple AMF scenarios Veriant1 | Nokia, Nokia Shanghai Bell | other | Agreement | Yes |
Yes
| revised | No | S3‑232123 | |||
S3‑231817 | EN removal multiple AMF scenarios Veriant2 | Nokia, Nokia Shanghai Bell | other | Agreement | Yes |
Yes
| merged | No | S3‑232123 | |||
S3‑231818 | addition of SoR use case | Nokia, Nokia Shanghai Bell | other | Agreement | Yes |
Yes
| noted | No | ||||
S3‑231819 | addition of UPU use case | Nokia, Nokia Shanghai Bell | other | Agreement | Yes |
Yes
| noted | No | ||||
S3‑231843 | Discussion on home network triggered primary authentication procedure | ZTE Corporation | discussion | Discussion | Yes |
Yes
| merged | No | S3‑232211 | |||
S3‑231846 | Update home network triggered primary authentication procedure | ZTE Corporation | other | Approval | Yes |
Yes
| merged | No | S3‑232211 | |||
S3‑231848 | Draft CR to TS 33.535-Kakma refresh | ZTE Corporation | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑231926 | living document for HNA | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232168 | |||
S3‑231927 | New UDM service | Huawei, HiSilicon | other | Approval | Yes |
Yes
| merged | No | S3‑232110 | |||
S3‑231928 | New AMF service | Huawei, HiSilicon | other | Approval | Yes |
Yes
| merged | No | S3‑232110 | |||
S3‑231929 | Addressing Editor’s Note on multiple AMFs registered to the UDM | Huawei, HiSilicon | other | Approval | Yes |
Yes
| merged | No | S3‑232123 | |||
S3‑231930 | Updating the NOTE1 | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑232169 | |||
S3‑231972 | EN removal for multiple AMFs case | LG Electronics | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑231987 | [draftCR] Adding a new security sevice operation provided by the UDM and AMF | Samsung | draftCR | Approval | Yes |
Yes
| merged | No | S3‑232110 | |||
S3‑231988 | [draftCR] Adding details on the operator policy and the trigger for the primary authentication | Samsung | draftCR | Approval | Yes |
Yes
| merged | No | S3‑232211 | |||
S3‑231989 | [draftCR] Modifying the Editor’s Note on UE reachability | Samsung | draftCR | Approval | Yes |
Yes
| merged | No | S3‑232211 | |||
S3‑232026 | HONTRA Clarifications | Lenovo | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232110 | |||
S3‑232062 | Remove the Editor’s Note related to the message type between AMF and UDM in the HONTRA | Beijing Xiaomi Mobile Software | other | Approval | Yes |
Yes
| revised | No | S3‑232193 | |||
S3‑232063 | Remove the Editor’s Note related to the multiple registrations in the HONTRA | Beijing Xiaomi Mobile Software | other | Approval | Yes |
Yes
| merged | No | S3‑232123 | |||
S3‑232110 | HONTRA Clarifications | Lenovo | draftCR | Approval | Yes |
Yes
| approved | No | S3‑232026 | |||
S3‑232123 | EN removal multiple AMF scenarios Veriant1 | Nokia, Nokia Shanghai Bell | other | Agreement | Yes |
Yes
| approved | No | S3‑231816 | |||
S3‑232168 | living document for HNA | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231926 | |||
S3‑232169 | Updating the NOTE1 | Huawei, HiSilicon | other | Approval | Yes |
Yes
| approved | No | S3‑231930 | |||
S3‑232193 | Remove the Editor’s Note related to the message type between AMF and UDM in the HONTRA | Beijing Xiaomi Mobile Software, Huawei,HiSilicon | other | Approval | Yes |
Yes
| approved | No | S3‑232062 | |||
S3‑232211 | pCR to living document to TS 33.501: Clarifications and removals of Editor's Notes | Ericsson, Lenovo, Nokia, Nokia Shanghai Bell, Samsung, ZTE | other | Approval | Yes |
Yes
| approved | No | S3‑231765 | |||
4.15 | New WID on 5G Security Assurance Specification (SCAS) for the Policy Control Function (PCF) | S3‑231759 | Skeleton draft TS 33.528 | BSI (DE) | draft TS | Yes |
Yes
| approved | No | |||
S3‑232227 | Skeleton draft TS 33.528 | BSI (DE) | draft TS | Approval | No |
Yes
| withdrawn | Yes | ||||
4.16 | New WID on Security aspects for 5WWC Phase 2 | S3‑231745 | Skeleton for 5WWC_Ph2_Sec:DraftCR to 33501 | Nokia, Nokia Shanghai Bell | draftCR | Agreement | Yes |
Yes
| noted | No | ||
4.17 | Proposed WID for UAS Phase 2 security | S3‑231789 | Draft Skeleton for UAS | Qualcomm Incorporated | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232100 | |
S3‑232100 | Draft Skeleton for UAS | Qualcomm Incorporated | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231789 | |||
4.18 | New WID on Automated certicate management in SBA | S3‑231739 | Skeleton_ACM_SBA_informative annex | Nokia, Nokia Shanghai Bell | draftCR | Agreement | Yes |
Yes
| merged | No | S3‑232147 | |
S3‑231740 | Skeleton_ACM_SBA_normative | Nokia, Nokia Shanghai Bell | draftCR | Agreement | Yes |
Yes
| revised | No | S3‑232147 | |||
S3‑232147 | Skeleton_ACM_SBA_normative | Nokia, Nokia Shanghai Bell | draftCR | Agreement | Yes |
Yes
| approved | No | S3‑231740 | |||
4.19 | New WID on security enhancements for NGRTC | S3‑231969 | Skeleton for NG_RTC_SEC | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232219 | |
S3‑232219 | Skeleton for NG_RTC_SEC | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231969 | |||
4.20 | New WID on Security Aspects of Enhancement of Support for Edge Computing in 5GC — phase 2 | S3‑231961 | living CR of EDGE_Ph2 on TS 33.501 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232216 | |
S3‑231963 | Living CR of EDGE_Ph2 on TS 33.558 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232217 | |||
S3‑232216 | living CR of FS_EDGE_Ph2 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231961 | |||
S3‑232217 | living CR of FS_EDGE_Ph2 | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231963 | |||
4.21 | New WID on AKMA phase 2 | S3‑231981 | Skeleton for AKMA ph2 WID | China Mobile | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232126 | |
S3‑232126 | Skeleton for AKMA ph2 WID | China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231981 | |||
4.22 | New WID on security aspects of MSGin5G Ph2 |   | ||||||||||
4.23 | New WID on security aspects of enablers for Network Automation for 5G - phase 3 | S3‑231886 | Authorization of selection of participant NWDAF instances in the Federated Learning group. | Intel | draftCR | Yes |
Yes
| withdrawn | Yes | |||
S3‑231980 | Skeleton for Security aspects of enablers for Network Automation for 5G - phase 3 | China Mobile | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232189 | |||
S3‑232189 | Skeleton for Security aspects of enablers for Network Automation for 5G - phase 3 | China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | S3‑231980 | |||
4.24 | New WID on Security aspects of enhanced support of Non-Public Networks phase 2 | S3‑231748 | Skeleton for Security aspects of enhanced support of Non-Public Networks phase 2 | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||
4.25 | New WID on Security Aspects of Proximity-based Services in 5GS Phase 2 | S3‑231950 | Security for U2U relay in 3GPP coverage | Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S3‑231982 | |
S3‑231951 | Emergency service via Layer 2 and Layer 3 UE-to-network relay | Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232010 | |||
S3‑231982 | Security for U2U relay in 3GPP coverage | Ericsson, China Telecom | draftCR | Information | Yes |
Yes
| noted | No | S3‑231950 | |||
S3‑232007 | Draft skeleton for ProSe Ph2 normative work | CATT | draftCR | Approval | Yes |
Yes
| revised | No | S3‑232142 | |||
S3‑232010 | Emergency service via Layer 2 and Layer 3 UE-to-network relay | Ericsson | draftCR | Information | Yes |
Yes
| noted | No | S3‑231951 | |||
S3‑232142 | Draft skeleton for ProSe Ph2 normative work | CATT | draftCR | Approval | Yes |
Yes
| approved | No | S3‑232007 | |||
4.26 | New WID on Security Aspects of Ranging Based Services and Sidelink Positioning | S3‑232027 | Skeleton for TS 33.533 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232194 | |
S3‑232028 | Scope for TS 33.533 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232194 | Skeleton for TS 33.533 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232027 | |||
S3‑232195 | Draft TS 33.533 v0.0.0 | Xiaomi Technology | draft TS | Approval | Yes |
Yes
| approved | No | ||||
4.27 | New WID on enhanced security aspects of SEAL for vertical | S3‑231994 | [draftCR] Living document for SEAL security for network domain interfaces | Samsung | draftCR | Approval | Yes |
Yes
| approved | No | ||
4.28 | New WID on application enablement aspects for subscriber-aware northbound API access | S3‑231957 | skeleton draft CR 33.122 on SNAAPPY | NTT DOCOMO INC. | draftCR | Yes |
Yes
| revised | No | S3‑232152 | ||
S3‑232152 | skeleton draft CR 33.122 on SNAAPPY | NTT DOCOMO INC. | draftCR | Yes |
Yes
| approved | No | S3‑231957 | ||||
5 | Rel-18 Studies |   | ||||||||||
5.1 | Study on 5G security enhancement against false base stations |   | ||||||||||
5.2 | Study on Security Impacts of Virtualisation |   | ||||||||||
5.3 | Study on Security Aspects of Proximity Based Services in 5GS Phase 2 | S3‑231779 | Update to Conclusion to KI #1 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑231780 | Update to TR 33.740 Conclusion for KI#2 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231781 | Update to TR 33.740 Conclusion for KI#4 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231782 | Evaluation TR 33.740 Sol #12 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231783 | New Solution using Re-keying for L2 U2U Relay selection | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑232111 | |||
S3‑231784 | New solution KNRP ID privacy L2 U2U Relay reselection | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑232112 | |||
S3‑231785 | New solution Model A Relay discovery using multiple key sets | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑232113 | |||
S3‑231798 | Discussion on ProSe UE-to-UE Relay discovery security | Qualcomm Incorporated, Deutsche Telekom, Philips International B.V. | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑231799 | Conclusion of KI#1 | Qualcomm Incorporated, Deutsche Telekom, Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑232202 | |||
S3‑231800 | Updates on the solution #23 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑232203 | |||
S3‑231801 | Updates on the solution #24 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑232204 | |||
S3‑231802 | Update the evaluation of solution #8 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231803 | Update the evaluation of solution #9 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231804 | Add an evaluation of solution #11 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231805 | Conclusion of KI#5 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231820 | ProSe - Conclusion on KI#2 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231821 | ProSe - Conclusion on KI#3 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231822 | ProSe - ProSe - New solution KI#1, 2 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑232125 | |||
S3‑231844 | Conclusion for the KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑232167 | |||
S3‑231845 | Conclusion for the KI#3 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231847 | Update the conclusion for the KI#6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231855 | Conclusion for KI #1 in TR 33.740 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231860 | pCR to update TR33.740 Solution 11 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231864 | Evaluation of TR33.740 Solution 11 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231866 | Update to the evaluation of TR33.740 Solution 23 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231867 | Update to the evaluation of TR33.740 Solution 24 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231868 | Update to conclusion of KI#2 in TR 33.740 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑232167 | |||
S3‑231869 | Update to conclusion of KI#3 in TR 33.740 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231870 | Update to conclusion of KI#4 in TR 33.740 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231871 | Update to conclusion of KI#6 in TR 33.740 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231923 | Conclude the KI#1 in TR 33.740 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231924 | Update to the KI#2 conclusion in TR 33.740 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232167 | |||
S3‑231956 | Update to conclusions on KI#2 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑232167 | |||
S3‑231998 | EN Resolution of Sol #33 | Samsung, KT | pCR | Approval | Yes |
Yes
| revised | No | S3‑232221 | |||
S3‑231999 | Conclusion on KI #5 | Samsung, KT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232008 | pCR to TR33.740 Update Solution16 for removing EN | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑232140 | |||
S3‑232009 | pCR to TR33.740 Update Solution28 for removing ENs | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑232141 | |||
S3‑232011 | pCR to TR33.740 Conclusion of key issue #1 | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑232202 | |||
S3‑232048 | Conclusion on Key Issue #1 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232049 | Conclusion on Key Issue #2 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232050 | Conclusion on Key Issue #3 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232051 | Discussion on the provisioning of long term credentials in the UE-to-UE Relay Communication | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232052 | Provision the long term credentials during the discovery procedure | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232053 | Provision the long term credentials during the service authorization procedure | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232054 | Remove the Editor's Note and evaluate the solution #7 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑232191 | |||
S3‑232055 | Remove the Editor's Notes of solution #20 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232056 | Update to solution #30 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑232192 | |||
S3‑232057 | Update evaluation to solution #32 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232082 | Conclusion for KI#5 | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232083 | Further Conclusion on KI#2 | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232111 | New Solution using Re-keying for L2 U2U Relay selection | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑231783 | |||
S3‑232112 | New solution KNRP ID privacy L2 U2U Relay reselection | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑231784 | |||
S3‑232113 | New solution Model A Relay discovery using multiple key sets | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑231785 | |||
S3‑232125 | ProSe - ProSe - New solution KI#1, 2 | Philips International B.V. | pCR | Yes |
Yes
| approved | No | S3‑231822 | ||||
S3‑232140 | pCR to TR33.740 Update Solution16 for removing EN | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑232008 | |||
S3‑232141 | pCR to TR33.740 Update Solution28 for removing ENs | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑232009 | |||
S3‑232146 | Draft TR 33.740 | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232167 | Update to the KI#2 conclusion in TR 33.740 | Huawei, HiSilicon, ZTE, China Telecom, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231924 | |||
S3‑232191 | Remove the Editor's Note and evaluate the solution #7 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑232054 | |||
S3‑232192 | Update to solution #30 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑232056 | |||
S3‑232202 | Conclusion of KI#1 | Qualcomm Incorporated, Deutsche Telekom, Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑231799 | |||
S3‑232203 | Updates on the solution #23 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑231800 | |||
S3‑232204 | Updates on the solution #24 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑231801 | |||
S3‑232221 | EN Resolution of Sol #33 | Samsung, KT | pCR | Approval | Yes |
Yes
| approved | No | S3‑231998 | |||
5.4 | Study on privacy of identifiers over radio access |   | ||||||||||
5.5 | Study on Standardising Automated Certificate Management in SBA | S3‑231735 | pCR Resolving EN in conclusion of ACM_SBA KI#5 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑232129 | |
S3‑231736 | pCR Conclusion of ACM_SBA KI#9 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑232132 | |||
S3‑231737 | pCR Conclusion of ACM_SBA KI#8 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑232131 | |||
S3‑231738 | pCR Conclusion of ACM_SBA KI#6 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑232130 | |||
S3‑231769 | KI#2 conclusion update | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S3‑231840 | Updating evaluation for solution#3 | China Telecommunications, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231906 | Add evaluation to solution #18 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232101 | |||
S3‑231907 | Add conclusion for key issue #9 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑232132 | |||
S3‑231937 | Resolution of ENs and evaluation of Sol#7 KI#6 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232099 | |||
S3‑231938 | Analysis and conclusion for key issue #8 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑232131 | |||
S3‑231939 | Conclusion for key issue #6 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑232130 | |||
S3‑232061 | Conclusion on Key Issue #4 in TR 33.876 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑232175 | |||
S3‑232099 | Resolution of ENs and evaluation of Sol#7 KI#6 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231937 | |||
S3‑232101 | Add evaluation to solution #18 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231906 | |||
S3‑232129 | pCR Resolving EN in conclusion of ACM_SBA KI#5 | Nokia, Nokia Shanghai Bell, Orange | pCR | Approval | Yes |
Yes
| approved | No | S3‑231735 | |||
S3‑232130 | pCR Conclusion of ACM_SBA KI#6 | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231738 | |||
S3‑232131 | pCR Conclusion of ACM_SBA KI#8 | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231737 | |||
S3‑232132 | pCR Conclusion of ACM_SBA KI#9 | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231736 | |||
S3‑232171 | Resolution of ENs and evaluation of Sol#7 KI#6 | Huawei, HiSilicon | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑232175 | Conclusion on Key Issue #4 in TR 33.876 | Beijing Xiaomi Mobile Software, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑232061 | |||
S3‑232225 | New draft TR 33.876 | Nokia Poland | draft TR | Approval | Yes |
Yes
| email approval | No | ||||
5.6 | New SID on AKMA phase 2 | S3‑231760 | Discussion on handling of LI for AKMA ph2 services | NDRE | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||
S3‑231761 | Discussion on handling of LI for AKMA ph2 services | NDRE, Nokia, Nokia Shanghai Bell, Lenovo | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑231812 | solution 7 correction | Nokia, Nokia Shanghai Bell, | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231813 | solution 7 enhancement | Nokia, Nokia Shanghai Bell, | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231814 | KI1 conclusion for case 1 and case3 | Nokia, Nokia Shanghai Bell, Xiaomi, Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231851 | Conclusion for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231875 | Adding evaluation to Solution#8 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231925 | Conclusion to KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
5.7 | Study of Security aspect of home network triggered primary authentication |   | ||||||||||
5.8 | Study on security aspects of enablers for Network Automation for 5G – phase 3 | S3‑231729 | Resolution of EN related to encryption in KI#3 conclusion in eNA_SEC_Ph3 | Nokia, Nokia Shanghai Bell, Lenovo, Intel | pCR | Approval | Yes |
Yes
| revised | No | S3‑232151 | |
S3‑231730 | pCR_Resolution of ENs of KI#1 conclusion in eNA_SEC_Ph3 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231731 | pCR Conclusion of eNA_SEC_Ph3 KI#4 | Nokia, Nokia Shanghai Bell, Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231732 | pCR Resolution of EN of KI#2 conclusion in eNA_SEC_Ph3 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231733 | Discussion paper on eNA_SEC_Ph3 KI#1 conclusions | Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑231734 | LS Out on Authorization of NF service consumer for AIML model storage and sharing in eNA | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑231746 | Resolve first EN to conclusion to KI#3 "Security for AI/ML model storage and sharing" | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231747 | Resolve second EN to conclusion to KI#3 "Security for AI/ML model storage and sharing" | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑232151 | |||
S3‑231836 | Editorial update to conclusion on KI#5 | China Telecommunications | pCR | Approval | Yes |
Yes
| merged | No | S3‑232186 | |||
S3‑231837 | Editorial update to KI#3 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231838 | Updating conclusion on KI#1 | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S3‑232117 | |||
S3‑231839 | Updating conclusion on KI#2 | China Telecommunications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231853 | New solution for KI#5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231856 | Add conclusion for KI#5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231903 | Add conclusion for key issue #2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231915 | Add Evaluation for Solution for Authorization for eNA Roaming | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232164 | |||
S3‑231916 | Conclusion Update for key issue #1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231978 | Update conclusion for key issue #5 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑232186 | |||
S3‑231979 | Conclusion for key issue #1 | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232021 | Update to Solution #9 in eNA | Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232022 | Update to Solution #20 in eNA | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑232105 | |||
S3‑232105 | Update to Solution #20 in eNA | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑232022 | |||
S3‑232117 | Updating conclusion on KI#1 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S3‑231838 | |||
S3‑232151 | Resolution of EN related to encryption in KI#3 conclusion in eNA_SEC_Ph3 | Nokia, Nokia Shanghai Bell, Lenovo, Intel, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231729 | |||
S3‑232164 | Add Evaluation for Solution for Authorization for eNA Roaming | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231915 | |||
S3‑232186 | Update conclusion for key issue #5 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑231978 | |||
S3‑232229 | draft TR 33.738 0.7.0 | China Mobile | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑232230 | draft TR 33.738 1.1.0 | China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.9 | Study on Security Enhancement of support for Edge Computing — phase 2 | S3‑231787 | Updates for Solution #26 | InterDigital Communications | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑231788 | A new solution for KI#2.3 | InterDigital Communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231859 | Update solution#6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231876 | New key issue on EEC provided IP address verification | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑232209 | |||
S3‑231877 | A solution for EEC provided IP address verification | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑232210 | |||
S3‑231878 | Update the key issue on EAS discovery security | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑232206 | |||
S3‑231879 | Update solution #23 EAS discovery procedure protection | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑232207 | |||
S3‑231880 | Update conclusion on EAS discovery security | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231881 | Resolving EN in solution #25 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑232208 | |||
S3‑231882 | Resolving ENs in solution #27 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231883 | Conclusion for EEC provided IP address verification | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231885 | Update conclusion on authorization between EESes | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231943 | Resolving the EN about the security of the communication between V-EASDF and H-EASDF/DNS | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231944 | Resolving the EN about non-roaming case on the configuration of EASDF | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231945 | update to conclusion for KI#1.2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232174 | |||
S3‑231958 | Adding evalution for Sol#26 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232214 | |||
S3‑231959 | Adding evalution for sol#27 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232215 | |||
S3‑231960 | Resolving EN of Conclusion of KI#2.6 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231962 | Resolving EN of Conclusion of KI#2.1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231975 | MEC-Resolving the EN of the conclusion of KI#2.2 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231976 | MEC-New key issue on verification of UE provided information | Apple | pCR | Approval | Yes |
Yes
| merged | No | S3‑232209 | |||
S3‑231990 | Discussion paper on performing only server side authentication | Samsung | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑231991 | [draft] LS on mutual authentication requirement in EDGE | Samsung | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑231992 | Updates to conclusion#2.1 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231993 | Updates to conclusion#2.2 | Samsung, Huawei, HiSilicon, Intel, ZTE, Thales, CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232065 | Update KI#2.1 conclusion of TR 33.739 | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232174 | update to conclusion for KI#1.2 | Huawei,HiSilicon, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑231945 | |||
S3‑232206 | Update the key issue on EAS discovery security | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231878 | |||
S3‑232207 | Update solution #23 EAS discovery procedure protection | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231879 | |||
S3‑232208 | Resolving EN in solution #25 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231881 | |||
S3‑232209 | New key issue on EEC provided IP address verification | Ericsson, Apple | pCR | Approval | Yes |
Yes
| approved | No | S3‑231876 | |||
S3‑232210 | A solution for EEC provided IP address verification | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231877 | |||
S3‑232214 | Adding evalution for Sol#26 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231958 | |||
S3‑232215 | Adding evalution for sol#27 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231959 | |||
S3‑232218 | new draft TR 33.739 | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.10 | Study on Personal IoT Networks Security Aspects | S3‑231724 | DP on the need and means of alignment between PIN work in SA3 and SA6 | InterDigital, Inc. | discussion | Endorsement | Yes |
Yes
| noted | No | ||
S3‑231725 | Draft Reply LS on Alignment of SA3 security aspects for Personal IoT Networks | InterDigital, Inc. | LS out | Approval | Yes |
Yes
| revised | No | S3‑232118 | |||
S3‑231726 | PCR TR 33.882 New KI#Y | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231727 | PCR TR 33.882 New KI#X | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231728 | PCR TR 33.882 KI#1 Modification | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231811 | Conclusion for KI#1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231825 | Conclusion for KI#1 | THALES | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231831 | Conclusions to KI#1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231832 | Conclusions to KI#2 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231833 | Editorial changes in solution 3 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231834 | Resolution of editor’s note in solution 10 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231849 | Add conclusion for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231850 | Add conclusion for KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231872 | Conclusion for KI#2: Authorization of PIN capabilities. | Intel | pCR | Yes |
Yes
| noted | No | |||||
S3‑231934 | add conclusion to KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232070 | Add conclusion for KI #2 of TR 33.882 | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232071 | Add conclusion to KI #1 of TR 33.882 | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232072 | New Sol for KI #2 of TR 33.882 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232118 | Reply LS on Alignment of SA3 security aspects for Personal IoT Networks | InterDigital, Inc. | LS out | Approval | Yes |
Yes
| approved | No | S3‑231725 | |||
S3‑232156 | Draft TR 33.882 v0.7.0 for FS_PIN_Sec | vivo | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.11 | Study on SNAAPP security | S3‑231884 | Resolving ENs in solution #6 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑232205 | |
S3‑231908 | New Solution on Revocation using Short-lived Token | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232160 | |||
S3‑231909 | Conclusion on Revocation for key issue#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232161 | |||
S3‑231910 | Update on solution #1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232162 | |||
S3‑231911 | New Solution on Resource Owner Authorization using Authorization Code Grant | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231912 | Address EN on solutiion #1 username mapping | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231913 | Address EN on solutiion #1 message of scope | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232163 | |||
S3‑231914 | Conclusion on Authorization for key issue#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231946 | Sol#1 Adding evaluation - being not in line with OAuth 2.0 architecture | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| revised | No | S3‑232119 | ||||
S3‑231947 | Sol#3 Resolving ENs on scopes and claims | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| revised | No | S3‑232120 | ||||
S3‑231948 | Sol#3 Evaluation related to additional scope and its restriction | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| revised | No | S3‑232121 | ||||
S3‑231949 | Sol#3 Evaluation on exposure of UE identity | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| revised | No | S3‑232122 | ||||
S3‑232000 | Resolving EN on Sol#11 | Samsung | pCR | Approval | Yes |
Yes
| merged | No | S3‑232222 | |||
S3‑232001 | Updates to Sol#11 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑232222 | |||
S3‑232002 | Updates to Sol#12 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑232224 | |||
S3‑232003 | Conclusion | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232023 | Update to Solution #4 in Snaappy | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑232106 | |||
S3‑232024 | Update to Solution #5 in Snaappy | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑232107 | |||
S3‑232074 | Add evaluation to Sol #9 of TR 33.884 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232075 | Add evaluation to Sol #10 of TR 33.884 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232076 | KI#1 and KI#2 New Sol on resource owner policies based authorization mechanism | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑232144 | |||
S3‑232077 | KI#2 New Sol on User authorization revocation for API invocation procedure | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑232145 | |||
S3‑232078 | Resolve EN for Sol #9 of TR 33.884 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232079 | Update conclusion of TR 33.884 | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232095 | Addressing editor's notes for solution 6.2 | NTT DOCOMO INC. | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S3‑232096 | Addressing editor's notes for solution 6.7 | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| revised | No | S3‑232153 | |||
S3‑232097 | New solution: authorization revocation for persistent changes | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| revised | No | S3‑232154 | |||
S3‑232106 | Update to Solution #4 in Snaappy | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑232023 | |||
S3‑232107 | Update to Solution #5 in Snaappy | Lenovo, Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑232024 | |||
S3‑232119 | Sol#1 Adding evaluation - being not in line with OAuth 2.0 architecture | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| approved | No | S3‑231946 | ||||
S3‑232120 | Sol#3 Resolving ENs on scopes and claims | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| approved | No | S3‑231947 | ||||
S3‑232121 | Sol#3 Evaluation related to additional scope and its restriction | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| approved | No | S3‑231948 | ||||
S3‑232122 | Sol#3 Evaluation on exposure of UE identity | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| approved | No | S3‑231949 | ||||
S3‑232144 | KI#1 and KI#2 New Sol on resource owner policies based authorization mechanism | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑232076 | |||
S3‑232145 | KI#2 New Sol on User authorization revocation for API invocation procedure | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑232077 | |||
S3‑232153 | Addressing editor's notes for solution 6.7 | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| approved | No | S3‑232096 | |||
S3‑232154 | New solution: authorization revocation for persistent changes | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| approved | No | S3‑232097 | |||
S3‑232160 | New Solution on Revocation using Short-lived Token | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231908 | |||
S3‑232161 | Conclusion on Revocation for key issue#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231909 | |||
S3‑232162 | Update on solution #1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231910 | |||
S3‑232163 | Address EN on solutiion #1 message of scope | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231913 | |||
S3‑232200 | new draft TR 33.884 | NTT DOCOMO INC. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232205 | Resolving ENs in solution #6 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231884 | |||
S3‑232222 | Updates to Sol#11 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑232001 | |||
S3‑232224 | Updates to Sol#12 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑232002 | |||
5.12 | Study on enhanced security for network slicing Phase 3 | S3‑231751 | Conclusion for KI#2 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑231752 | Conclusion for KI#3 | Ericsson | pCR | Yes |
Yes
| noted | No | |||||
S3‑231792 | Adding some evaluation to solution #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231793 | Adding some evaluation to solution #2 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑232226 | |||
S3‑231862 | Update KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231863 | New solution for KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231865 | Add conclusion for KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231888 | KI#1 update | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231889 | new solution to KI#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231890 | conclusions to KI#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231891 | update to solution#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231892 | conclusions to KI#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231970 | EN addition to solution #2 | LG Electronics | pCR | Approval | Yes |
Yes
| merged | No | S3‑232226 | |||
S3‑231971 | Minor editorial correction to solution #1 | LG Electronics | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232073 | New Sol for KI #3 of TR 33.886 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232084 | update to KI#2 temporary network slice | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232085 | solution for KI#2 temporary network slice for NSSAA | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232086 | evaluation for KI#2 temporary network slice for NSSAA | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232087 | conclusion for KI#2 temporary network slice for NSSAA | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232088 | evaluation for KI#3 network slice admission control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑232226 | |||
S3‑232089 | conclusion for KI#3 network slice admission control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232134 | Draft TR 33.886 for eNS3 | Huawei Tech.(UK) Co.. Ltd | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232226 | evaluation for KI#3 network slice admission control | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, LG Electronics | pCR | Approval | Yes |
Yes
| approved | No | S3‑232088 | |||
5.13 | Study on Security aspects for 5WWC Phase 2 |   | ||||||||||
5.14 | Study on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the NG-RAN |   | ||||||||||
5.15 | Study on security support for Next Generation Real Time Communication services | S3‑231762 | Conclusion for key issue #1 | Ericsson, BT | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑231763 | Resolve EN for conclusion for key issue #2 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑232098 | |||
S3‑231764 | LS on third party specific user identities in IMS | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑231790 | Update of the conclusion on data channel security | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑232098 | |||
S3‑231967 | conclusion on key issue 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231968 | Resolving EN in Conclusions for KI #2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑232098 | |||
S3‑232098 | Update of the conclusion on data channel security | Qualcomm Incorporated, Huawei, HiSilicon, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231790 | |||
S3‑232220 | new draft TR 33.890 | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.16 | Study on security aspects of enhanced support of Non-Public Networks phase 2 | S3‑231749 | Updated conclusion of KI#2 Authentication for UE access to hosting network | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑231753 | Discussion for removal of Editor's note in conclusion for trusted N3GPP access | Ericsson | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑231754 | Updated conclusion for KI#1 regarding trusted access | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231755 | Updated conclusion for KI#1 regarding untrusted access | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑232223 | |||
S3‑231756 | Updated conclusion for KI#1 regarding N5CW access | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231757 | Removing Editor’s notes in Solution #14 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231829 | Resolution of EN – conclusion to KI#1 – Untrusted access | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑232223 | |||
S3‑231830 | Resolution of EN – conclusion to KI#1 – Trusted access | Nokia, Nokia Shanghai Bell, Lenovo, Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231917 | New Solution on Implicit Authentication for Serving Network for NSWO support in SNPN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231918 | Conclusion for Implicit Authentication for Serving Network related to NSWO | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231932 | Delete Editor's Note to sol#18 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232170 | |||
S3‑231933 | Update conclusion 7.1.3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232025 | Update to Solution #16 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑232109 | |||
S3‑232066 | Update conclusion of NSWO support in SNPN | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232067 | Update solution #2 of TR 33.85 | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑232143 | |||
S3‑232092 | Solutions using credential holder for KI#1 | CableLabs | pCR | Approval | Yes |
Yes
| revised | No | S3‑232136 | |||
S3‑232093 | Additional conclusions on credential holder for KI#1 | CableLabs | pCR | Approval | Yes |
Yes
| revised | No | S3‑232137 | |||
S3‑232109 | Update to Solution #16 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑232025 | |||
S3‑232133 | draft TR 33.858 v1.1.0 | Ericsson | draft TR | Yes |
Yes
| approved | No | |||||
S3‑232136 | Solutions using credential holder for KI#1 | CableLabs, Charter Communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑232092 | |||
S3‑232137 | Additional conclusions on credential holder for KI#1 | CableLabs, Charter Communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑232093 | |||
S3‑232143 | Update solution #2 of TR 33.85 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑232067 | |||
S3‑232170 | Delete Editor's Note to sol#18 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231932 | |||
S3‑232223 | Resolution of EN – conclusion to KI#1 – Untrusted access | Nokia, Nokia Shanghai Bell, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑231829 | |||
5.17 | Study on Security of Phase 2 for UAS, UAV and UAM |   | ||||||||||
5.18 | Study to enable URSP rules to securely identify Applications | S3‑231770 | Conclusion for KI#1 | Lenovo, AT&T, Broadcom, CableLabs, CATT, China Mobile, Intel, LGE, NEC, Nokia Shanghai Bell, Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑231828 | Resolution of editor’s note in solution 1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231874 | Adding evaluation to Solution#3 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231893 | new solution to KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231894 | conclusions to KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231977 | USIA- Adding the evaluation for solution#1 | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
5.19 | Study on Security Aspects of Ranging Based Services and Sidelink Positioning | S3‑231771 | Protection of broadcast communication | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑232233 | |
S3‑231806 | Update of a conclusion for KI #3 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231807 | Updates on the solution #15 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑232201 | |||
S3‑231808 | Updates on the solution #12 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231809 | Update on solution #9 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231810 | conclusion for KI#5 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231823 | Ranging - New solution KI#5 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑232124 | |||
S3‑231824 | Ranging - Update KI#1 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231852 | Update the key issue 5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231854 | A new solution for the key issue 5 (broadcast) | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231857 | A new solution for the key issue 5 (groupcast) | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231858 | Add conclusion for KI#3 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231861 | Conclusion for the key issue 5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231873 | New Key issue for Monitoring and detecting attacks on ranging devices and services | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231895 | update to solution 15 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232157 | |||
S3‑231896 | update to solution 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232158 | |||
S3‑231897 | conclusion on key issue 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231920 | Address EN and update evaluation to Sol#13 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232165 | |||
S3‑231921 | update to the conclusion of KI#3 in TR 33.893 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231922 | conclusion for the KI#4 in TR 33.893 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232166 | |||
S3‑231954 | New solution with Network assisted SL positioning discovery security material provisioning | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231955 | New solution with Network assisted SL positioning provisioning long term key | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232004 | New solution on security of Ranging or SL positioning groupcast communication | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑232127 | |||
S3‑232005 | New solution on security of Ranging or SL positioning broadcast communication | OPPO | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑232006 | New solution on Protecting Ranging/SL Positioning discovery out of network coverage | BUPT, OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑232138 | |||
S3‑232012 | pCR to TR33.893 New solution for provisioning broadcast protection keys in coverage | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑232148 | |||
S3‑232013 | pCR to TR33.893 New solution for provisioning groupcast/broadcast protection keys out of coverage | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑232149 | |||
S3‑232015 | pCR to TR33.893 New solution for protecting groupcast/broadcast messages | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑232150 | |||
S3‑232029 | 33.893: Additional Evaluation for Solution #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232179 | |||
S3‑232030 | 33.893: Update to Solution #2 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232183 | |||
S3‑232031 | 33.893: Resolve the Editor’s Note in Solution #8 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232180 | |||
S3‑232032 | 33.893: Resolve the Editor’s Note in Solution #14 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232188 | |||
S3‑232033 | 33.893: New Solution on Privacy Protection of Located UE during its Discovery and Selection | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232181 | |||
S3‑232034 | 33.893: New Solution on Client UE Authorization for Service Exposure through the Network | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232184 | |||
S3‑232035 | 33.893: New Solution on Client UE Authorization for Service Exposure through PC5 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232036 | 33.893: New Solution on Protection for Groupcast of SLPP Signalling | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232037 | 33.893: New Solution on Protection for Broadcast of SLPP Signalling | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232038 | 33.893: Conclusion on Key Issue #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232182 | |||
S3‑232039 | 33.893: Further Conclusions for KI#2 on Authorization for Service Exposure | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232185 | |||
S3‑232040 | 33.893: Further Conclusions for KI#2 on Authorization of UE Role | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232187 | |||
S3‑232041 | 33.893: Further Conclusions for KI#3 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232042 | 33.893: Conclusion on Key Issue #4 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232190 | |||
S3‑232058 | Update to conclusion for KI#2 in TR 33.893 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232059 | Remove the Editor’s Note of solution #9 in TR 33.893 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232060 | New solution on authorization of MO-LR procedure for Network assisted SL Positioning in TR 33.893 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232094 | New solution on KI#5 protection of broadcast communication | BUPT | pCR | Approval | Yes |
Yes
| revised | No | S3‑232139 | |||
S3‑232124 | Ranging - New solution KI#5 | Philips International B.V. | pCR | Yes |
Yes
| approved | No | S3‑231823 | ||||
S3‑232127 | New solution on security of Ranging/SL positioning groupcast communication | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑232004 | |||
S3‑232138 | New solution on Protecting Ranging/SL Positioning discovery out of network coverage | BUPT, OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑232006 | |||
S3‑232139 | New solution on KI#5 protection of broadcast communication | BUPT | pCR | Approval | Yes |
Yes
| approved | No | S3‑232094 | |||
S3‑232148 | pCR to TR33.893 New solution for provisioning broadcast protection keys in coverage | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑232012 | |||
S3‑232149 | pCR to TR33.893 New solution for provisioning groupcast/broadcast protection keys out of coverage | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑232013 | |||
S3‑232150 | pCR to TR33.893 New solution for protecting groupcast/broadcast messages | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑232015 | |||
S3‑232157 | update to solution 15 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231895 | |||
S3‑232158 | update to solution 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231896 | |||
S3‑232165 | Address EN and update evaluation to Sol#13 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231920 | |||
S3‑232166 | conclusion for the KI#4 in TR 33.893 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231922 | |||
S3‑232179 | 33.893: Additional Evaluation for Solution #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232029 | |||
S3‑232180 | 33.893: Resolve the Editor’s Note in Solution #8 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232031 | |||
S3‑232181 | 33.893: New Solution on Privacy Protection of Located UE during its Discovery and Selection | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232033 | |||
S3‑232182 | 33.893: Conclusion on Key Issue #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232038 | |||
S3‑232183 | 33.893: Update to Solution #2 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232030 | |||
S3‑232184 | 33.893: New Solution on Client UE Authorization for Service Exposure through the Network | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232034 | |||
S3‑232185 | 33.893: Further Conclusions for KI#2 on Authorization for Service Exposure | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232039 | |||
S3‑232187 | 33.893: Further Conclusions for KI#2 on Authorization of UE Role | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232040 | |||
S3‑232188 | 33.893: Resolve the Editor’s Note in Solution #14 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232032 | |||
S3‑232190 | 33.893: Conclusion on Key Issue #4 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232042 | |||
S3‑232197 | Draft TR 33.893 v0.7.0 | Xiaomi Technology | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232201 | Updates on the solution #15 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑231807 | |||
S3‑232233 | Protection of broadcast communication | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑231771 | |||
5.20 | Study on Security and Privacy of AI/ML-based Services and Applications in 5G | S3‑231786 | Authorization of AF for Policy Management | InterDigital Communications | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑231904 | Add evaluation for solution # 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231905 | Add conclusion for key issue #1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232159 | |||
S3‑231983 | Add evaluation on sol#3 | OPPO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑231984 | Further evaluation on sol#4 | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231985 | Add evaluation on sol#5 | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231986 | Update Sol #6 for AIML Security | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232080 | User Consent in AI/ML | OPPO | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑232081 | Further Conclusion on KI#1 | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232159 | Add conclusion for key issue #1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231905 | |||
S3‑232231 | Draft TR 33.898 v0.6.0 | OPPO | draft TR | Yes |
Yes
| approved | No | |||||
5.21 | Study on applicability of the Zero Trust Security principles in mobile networks | S3‑231722 | Alignment of 3GPP’s 5G Security to the fifth NIST Tenet of ZTA | Ericsson | pCR | Yes |
Yes
| merged | No | S3‑232102 | ||
S3‑231723 | Alignment of 3GPP’s 5G Security to the sixth NIST Tenet of ZTA | Ericsson | pCR | Yes |
Yes
| noted | No | |||||
S3‑231835 | New Key Issue: Support for Policy Decision Points within 5GC SBA | MITRE Corporation, Nokia, Nokia Shanghai Bell, Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231940 | Evaluation of tenet 4 on resource access | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231941 | Additions to the evaluation of tenet 5 on security posture | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232102 | |||
S3‑231942 | Updates to the evaluation of tenet 6 on access security | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232103 | |||
S3‑232014 | Update to Tenet #5 | Lenovo, US National Security Agency, Charter Communications, Rakuten Mobile, Center for Internet Security, Cablelabs, Intel | pCR | Approval | Yes |
Yes
| merged | No | S3‑232102 | |||
S3‑232016 | Update to Tenet #6 | Lenovo, US National Security Agency, Charter Communications, Rakuten Mobile, Center for Internet Security, Cablelabs, Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232017 | Cleanup of Tenet #7 | Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232018 | Update to Key Issue #1 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232019 | Data collection for Security Monitoring | Lenovo, Charter Communications, US National Security Agency, Telefonica, Rakuten Mobile, Center for Internet Security, Cablelabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232020 | NF State related data collection for Security Monitoring | Lenovo, Charter Communications, US National Security Agency, Telefonica, Rakuten Mobile, Center for Internet Security, Cablelabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232102 | Additions to the evaluation of tenet 5 on security posture | Huawei, HiSilicon, Ericsson, Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑231941 | |||
S3‑232103 | Updates to the evaluation of tenet 6 on access security | Huawei, HiSilicon,Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑231942 | |||
S3‑232172 | Additions to the evaluation of tenet 5 on security posture | Huawei, HiSilicon, Ericsson, Lenovo | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑232173 | Updates to the evaluation of tenet 6 on access security | Huawei, HiSilicon, Lenovo | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑232228 | draft TR 33.894 v0.6.0 | Lenovo | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.22 | Study of Security aspects on User Consent for 3GPP Services Phase 2 | S3‑231741 | LS out on user consent in roaming scenarios | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| noted | No | ||
5.23 | Study on security enhancements for 5G multicast-broadcast services Phase 2 | S3‑231750 | Conclusion for KI#2 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑231794 | A new solution for mitigating privacy attacks exploiting group paging with TMGI | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231795 | Conclusion for Key Issue #2 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231796 | An update on the evaluations of solution #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231797 | Conclusion for Key Issue #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231898 | A new solution to address the privacy issue with TMGI | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231899 | conclusion on key issue 2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231900 | Update to the solution 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑232116 | |||
S3‑231901 | conclusion on key issue 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231995 | [MBS] Updates to solution#1 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231996 | [MBS] Evaluation for solution#3 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑231997 | [MBS] Conclusion for Key Issue#1 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232115 | TR 33.883 for 5MBS security | Huawei, HiSilicon | draft TR | Yes |
Yes
| approved | No | |||||
S3‑232116 | Update to the solution 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑231900 | |||
5.24 | Study on enhanced Security Aspects of the 5G Service Based Architecture |   | ||||||||||
5.25 | Study on Security Aspects of Satellite Access | S3‑231742 | Discussion on NTN AF Authorization (Rel18) | Nokia, Nokia Shanghai Bell | discussion | Discussion | Yes |
Yes
| noted | No | ||
S3‑231743 | Solution for AF Authorization | Nokia, Nokia Shanghai Bell | discussion | Approval | Yes |
Yes
| merged | No | S3‑232198 | |||
S3‑231744 | Conclusion for KI #1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S3‑232199 | |||
S3‑232043 | 33.700-28: Update to Key Issue #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232176 | |||
S3‑232044 | 33.700-28: Solution on AF Authorization for Providing Satellite Coverage Information | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232198 | |||
S3‑232045 | 33.700-28: Conclusion on Key Issue #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑232199 | |||
S3‑232046 | 33.700-28: New Key Issue on Protection of Satellite Coverage Info received by the UE | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232047 | 33.700-28: Solution on Protection of PDU Session carrying Satellite Coverage Information | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑232176 | 33.700-28: Update to Key Issue #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑232043 | |||
S3‑232177 | 33.700-28: Solution on AF Authorization for Providing Satellite Coverage Information | Xiaomi Technology | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑232178 | 33.700-28: Conclusion on Key Issue #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑232196 | Draft TR 33.700-28 v0.4.0 | Xiaomi Technology | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑232198 | 33.700-28: Solution on AF Authorization for Providing Satellite Coverage Information | Xiaomi Technology, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑232044 | |||
S3‑232199 | 33.700-28: Conclusion on Key Issue #1 | Xiaomi Technology, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑232045 | |||
6 | New Study/Work item proposals |   | ||||||||||
7 | CVD and research |   | ||||||||||
8 | Any Other Business |   |