Tdoc List
2023-01-25 17:12
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Agenda and Meeting Objectives | S3‑230001 | Agenda | SA WG3 Chair | agenda | Yes |
Yes
| approved | No | |||
S3‑230002 | Process for SA3#109Adhoc-e | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
S3‑230003 | Process and agenda planning for SA3#109AdHoc-e | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
2 | Meeting Reports |   | ||||||||||
3 | Reports and Liaisons from other Groups | S3‑230005 | LS on U2N relay direct link setup failure due to RSC mismatch or integrity failure | C1-226908 | LS in | Yes |
Yes
| postponed | No | |||
S3‑230006 | Reply LS on the progress and open issues for NPN enhancements in Rel-18 | C1-227157 | LS in | Yes |
Yes
| noted | No | |||||
S3‑230007 | LS on SL positioning groupcast and broadcast | R2-2213142 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑230008 | LS on user consent of Non-public Network | R3-226006 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑230009 | Reply LS on Progress and open issues for NPN enhancements in Rel-18 | S1-223540 | LS in | Yes |
Yes
| noted | No | |||||
S3‑230010 | Reply LS on the impact of MSK update on MBS multicast session update procedure | S2-2209287 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑230011 | LS on impact of URSP rule enforcement report to 5GC | S2-2209327 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑230012 | Reply LS on how ML model integrity, confidentiality and availability is supported between NWDAFs from different vendors | S2-2210943 | LS in | Yes |
Yes
| noted | No | |||||
S3‑230013 | Slice based Steering of Roaming | S2-2211204 | LS in | Yes |
Yes
| noted | No | |||||
S3‑230014 | Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | S6-223487 | LS in | Yes |
Yes
| noted | No | |||||
S3‑230015 | LS reply on SNAAPP requirements clarifications | S6-223488 | LS in | Yes |
Yes
| noted | No | |||||
S3‑230016 | LS reply on CAPIF authorization roles related to FS_SNAAPP | S6-223489 | LS in | Yes |
Yes
| noted | No | |||||
S3‑230017 | LS on the use of a non-network defined identifier for UE identification | S6-223558 | LS in | Yes |
Yes
| postponed | No | |||||
S3‑230018 | Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | S6-223586 | LS in | Yes |
Yes
| replied to | No | |||||
S3‑230040 | LS on MOCN TMGI ID impacting MSK, MTK | Nokia, Nokia Shanghai Bell | LS out | Yes |
Yes
| noted | No | |||||
S3‑230303 | Reply LS on user consent of Non-public Network | Qualcomm Incorporated | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑230310 | Reply LS to S3-230017/S6-223558 on the use of a non-network defined identifier for UE identification | Apple | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑230311 | Reply LS to S3-230018/S6-223586 on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | Apple | LS out | Approval | Yes |
Yes
| revised | No | S3‑230463 | |||
S3‑230312 | Reply LS to R2-2213142 on SL positioning | Apple | LS out | Approval | Yes |
Yes
| revised | No | S3‑230430 | |||
S3‑230356 | Reply LS on SL positioning groupcast and broadcast | CATT | LS out | Approval | Yes |
Yes
| merged | No | S3‑230430 | |||
S3‑230430 | Reply LS to R2-2213142 on SL positioning | Apple | LS out | Approval | Yes |
Yes
| approved | No | S3‑230312 | |||
S3‑230463 | Reply LS to S3-230018/S6-223586 on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network | Apple | LS out | Approval | Yes |
Yes
| approved | No | S3‑230311 | |||
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 Re17 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 ) |   | ||||||||||
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‑230028 | Evaluation TR 33.740 Sol #1 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230435 | |
S3‑230029 | Evaluation TR 33.740 Sol #12 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230436 | |||
S3‑230030 | Evaluation TR 33.740 Sol #13 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230437 | |||
S3‑230031 | Evaluation TR 33.740 Sol #14 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230032 | Update to TR 33.740 Conclusion for KI#2 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230033 | Update to TR 33.740 Conclusion for KI#4 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230438 | |||
S3‑230103 | Update the KI#6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑230485 | |||
S3‑230104 | New solution for the KI#6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230105 | Conclusion for the KI#6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230126 | Resolving EN for Solution 22 | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230492 | |||
S3‑230185 | Address EN for So#l26 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230478 | |||
S3‑230186 | Evaluate to the solution #20 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230479 | |||
S3‑230187 | Evaluate to the solution #26 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230188 | conclude to KI #2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230191 | Add Evaluation for ProSe Security Sol#6 | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230207 | evaluation of TR33.740 Solution 8 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230212 | evaluation of TR33.740 Solution 11 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230215 | pCR to update TR33.740 Solution 11 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230216 | Conclusion to the KI#1 | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| noted | No | |||||
S3‑230219 | evaluation to TR33.740 Solution 9 | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| noted | No | |||||
S3‑230221 | Update to the evaluation of solution 23 | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| revised | No | S3‑230548 | ||||
S3‑230234 | Update to the evaluation of solution 24 | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| revised | No | S3‑230549 | ||||
S3‑230235 | Update to conclusion of KI#2 in TR 33.740 | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| noted | No | |||||
S3‑230253 | EN removal for solution#27 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230586 | |||
S3‑230586 | EN removal for solution#27 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230253 | |||
S3‑230254 | Resolve EN’s in Solution #27 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230497 | |||
S3‑230255 | Evaluation to Solution #27 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230498 | |||
S3‑230256 | Evaluation to solution #4 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230499 | |||
S3‑230257 | Update to solution #30 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230500 | |||
S3‑230258 | New security solution on discovery integrated into PC5 link establishment when L3 UE-to-UE relay is in coverage | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230501 | |||
S3‑230266 | ProSe - Evaluation Solution #10 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230454 | |||
S3‑230267 | ProSe - Editorials Solution #10 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230268 | ProSe - Evaluation Solution #15 | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230455 | |||
S3‑230292 | Updates on the solution #23 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230293 | Updates on the solution #24 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230294 | LS on UE-to-UE relay discovery direct discovery | Qualcomm Incorporated | LS out | Yes |
Yes
| noted | No | |||||
S3‑230295 | Add an evaluation of solution #8 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230296 | Add an evaluation of solution #9 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230297 | Add an evaluation of solution #11 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230298 | Updates to the solution #25 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑230528 | |||
S3‑230327 | EN Resolution and Evaluation of Sol #19 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230536 | |||
S3‑230328 | EN Resolutions and Evaluation of Sol #29 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230537 | |||
S3‑230345 | pCR to TR33.740 Update Solution16 for removing ENs | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑230550 | |||
S3‑230346 | pCR to TR33.740 Update Solution17 for removing ENs | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑230551 | |||
S3‑230347 | pCR to TR33.740 Update Solution18 for removing ENs and add evaluation | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑230552 | |||
S3‑230348 | pCR to TR33.740 Update Solution28 for removing ENs | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑230553 | |||
S3‑230349 | pCR to TR33.740 Evaluation of Solution28 | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑230554 | |||
S3‑230350 | pCR to TR33.740 Conclusion of key issue #1 | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230351 | pCR to TR33.740 Conclusion of key issue #2 | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230352 | pCR to TR33.740 Conclusion of key issue #3 | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230392 | Update to solution #8 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230393 | Update to solution #9 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230394 | Evaluation of solution #8 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑230556 | |||
S3‑230395 | Evaluation of solution #9 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑230557 | |||
S3‑230396 | Remove the Editor's Note and evaluate the solution #7 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230397 | Remove the Editor's Notes of solution #20 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230398 | Evaluation of solution #30 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑230558 | |||
S3‑230399 | Conclusion on Key Issue #1 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230400 | Conclusion on Key Issue #2 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230401 | Conclusion on Key Issue #3 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230402 | Conclusion on Key Issue #4 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230435 | Evaluation TR 33.740 Sol #1 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230028 | |||
S3‑230436 | Evaluation TR 33.740 Sol #12 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230029 | |||
S3‑230437 | Evaluation TR 33.740 Sol #13 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230030 | |||
S3‑230438 | Update to TR 33.740 Conclusion for KI#4 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230033 | |||
S3‑230454 | ProSe - Evaluation Solution #10 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230266 | |||
S3‑230455 | ProSe - Evaluation Solution #15 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230268 | |||
S3‑230478 | Address EN for So#l26 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230185 | |||
S3‑230479 | Evaluate to the solution #20 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230186 | |||
S3‑230485 | Update the KI#6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑230103 | |||
S3‑230492 | Resolving EN for Solution 22 | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230126 | |||
S3‑230497 | Resolve EN’s in Solution #27 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230254 | |||
S3‑230498 | Evaluation to Solution #27 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230255 | |||
S3‑230499 | Evaluation to solution #4 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230256 | |||
S3‑230500 | Update to solution #30 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230257 | |||
S3‑230501 | New security solution on discovery integrated into PC5 link establishment when L3 UE-to-UE relay is in coverage | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230258 | |||
S3‑230528 | Updates to the solution #25 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑230298 | |||
S3‑230536 | EN Resolution and Evaluation of Sol #19 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230327 | |||
S3‑230537 | EN Resolutions and Evaluation of Sol #29 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230328 | |||
S3‑230548 | Update to the evaluation of solution 23 | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| approved | No | S3‑230221 | ||||
S3‑230549 | Update to the evaluation of solution 24 | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| approved | No | S3‑230234 | ||||
S3‑230550 | pCR to TR33.740 Update Solution16 for removing ENs | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑230345 | |||
S3‑230551 | pCR to TR33.740 Update Solution17 for removing ENs | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑230346 | |||
S3‑230552 | pCR to TR33.740 Update Solution18 for removing ENs and add evaluation | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑230347 | |||
S3‑230553 | pCR to TR33.740 Update Solution28 for removing ENs | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑230348 | |||
S3‑230554 | pCR to TR33.740 Evaluation of Solution28 | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑230349 | |||
S3‑230556 | Evaluation of solution #8 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑230394 | |||
S3‑230557 | Evaluation of solution #9 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑230395 | |||
S3‑230558 | Evaluation of solution #30 in TR 33.740 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑230398 | |||
S3‑230567 | Draft TR 33.740 | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.4 | Study on privacy of identifiers over radio access |   | ||||||||||
5.5 | Study on Standardising Automated Certificate Management in SBA |   | ||||||||||
5.6 | New SID on AKMA phase 2 | S3‑230056 | Discussion on privacy issue in AKMA | Nokia, Nokia Shanghai Bell, Samsung | discussion | Endorsement | Yes |
Yes
| noted | No | ||
S3‑230057 | key issue on AKMA privacy | Nokia, Nokia Shanghai Bell, Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230058 | conclusion updates | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230106 | Add editors note to solution 5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑230487 | |||
S3‑230107 | Add editors note to solution 11 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230108 | Address EN for solution 9 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230109 | AUSF stores SN ID after primary authentication in solution 1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230110 | AUSF stores SN ID after primary authentication in solution 6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230111 | Conclusion for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230112 | update the Key issue of AKMA roaming | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230145 | Minor editorial corrections in Solution #5 | LG Electronics | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230146 | Minor editorial corrections in Solution #12 | LG Electronics | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230147 | Evaluation for Solution #5 | LG Electronics | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230148 | Evaluation for Solution #12 | LG Electronics | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230197 | add new conclusion to key issue#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230270 | AKMA - Evaluation Solution #10 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230271 | AKMA - Editorials Clause 4 | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230274 | Completion of solution #14 | THALES | pCR | Approval | Yes |
Yes
| revised | No | S3‑230458 | |||
S3‑230275 | Conclusion to Key Issue #1 | THALES | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230325 | Key Issue on KAF refresh | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230374 | new Sol on AKMA roaming in multiple registration scenarios | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230375 | TR 33.737 Evaluation for sol #15 | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑230533 | |||
S3‑230376 | TR 33.737 Conclusion for KI #1 | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230420 | adding new use case in KI1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230458 | Completion of solution #14 | THALES | pCR | Approval | Yes |
Yes
| approved | No | S3‑230274 | |||
S3‑230487 | Add editors note to solution 5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑230106 | |||
S3‑230533 | TR 33.737 Evaluation for sol #15 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑230375 | |||
S3‑230584 | Draft TR 33.737 v0.5.0 | China Mobile | draft TR | Approval | No |
No
| reserved | No | ||||
5.7 | Study of Security aspect of home network triggered primary authentication | S3‑230059 | Discussion paper for MPS support over WLAN and relationship with HNTRA | Nokia, Nokia Shanghai Bell | pCR | Discussion | Yes |
Yes
| noted | No | ||
S3‑230060 | Conclusion enhancement for MPS support over WLAN | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230113 | Add conclusion to KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230198 | Delete EN in solution#4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230199 | Delete EN in solution#9 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230200 | Delete EN in solution#12 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230291 | Proposed addition to the conclusions | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230326 | Update on use case clause and solution #6 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230411 | Solution 12 updates | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230532 | TR 33.741v050 | Huawei;HiSilicon | draft TR | Yes |
Yes
| approved | No | |||||
5.8 | Study on security aspects of enablers for Network Automation for 5G – phase 3 | S3‑230064 | Update to Solution #9 in eNA | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230447 | |
S3‑230065 | Cyber attack detection | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230448 | |||
S3‑230080 | New solution addressing KI#6 | Lenovo, Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230081 | Evaluation of Solution#4 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230574 | |||
S3‑230082 | Removal of EN in Solution#4 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230091 | Evaluation for solution#1 | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S3‑230456 | |||
S3‑230101 | Resolving EN in solution#1 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230102 | New solution to KI#2 | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S3‑230457 | |||
S3‑230123 | New solution to KI#5 | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S3‑230459 | |||
S3‑230179 | new pcr | Huawei, HiSilicon | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑230189 | Conclusion for KI#2 | Intel | pCR | Yes |
Yes
| noted | No | |||||
S3‑230203 | Conclusion for KI#3 | Intel | pCR | Yes |
Yes
| merged | No | S3‑230510 | ||||
S3‑230209 | FL GROUP AUTHORIZATION OF NWDAF(S) IN 5GC | Intel | pCR | Yes |
Yes
| revised | No | S3‑230524 | ||||
S3‑230237 | EN related to Key Refresh and revocation | Intel | pCR | Yes |
Yes
| revised | No | S3‑230525 | ||||
S3‑230239 | New solution for KI#2 to support authorization of participant NWDAFs in FL | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230443 | |||
S3‑230240 | ENs resolving and evaluation for solution #10 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230442 | |||
S3‑230241 | Evaluation to Solution #11 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230242 | Evaluation to Solution #12 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230243 | Evaluation to Solution #13 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230244 | Adding conclusion on KI#3 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑230510 | |||
S3‑230262 | LS on data and analytics exchange in roaming case in eNA | China mobile | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑230263 | Evaluation and EN resolving for solution #14 | China mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑230546 | |||
S3‑230264 | Conclusion for key issue#1 | China mobile | pCR | Approval | Yes |
Yes
| merged | No | S3‑230506 | |||
S3‑230265 | Conclusion for key issue#5 | China mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230340 | Evaluation for Solution #6 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230341 | Discussion paper on KI#3 related solutions evaluation. | Nokia, Nokia Shanghai Bell, China Mobile (Suzhou) Software | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑230342 | Adding conclusion on KI#1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230506 | |||
S3‑230343 | Solution for authorization in FL | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230488 | |||
S3‑230344 | Adding conclusion on KI#3 | Nokia, Nokia Shanghai Bell, China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑230510 | |||
S3‑230442 | ENs resolving and evaluation for solution #10 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230240 | |||
S3‑230443 | New solution for KI#2 to support authorization of participant NWDAFs in FL | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230239 | |||
S3‑230447 | Update to Solution #9 in eNA | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230064 | |||
S3‑230448 | Cyber attack detection | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230065 | |||
S3‑230456 | Evaluation for solution#1 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S3‑230091 | |||
S3‑230457 | New solution to KI#2 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S3‑230102 | |||
S3‑230459 | New solution to KI#5 | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S3‑230123 | |||
S3‑230488 | Solution for authorization in FL | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230343 | |||
S3‑230506 | Adding conclusion on KI#1 | Nokia, Nokia Shanghai Bell, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑230342 | |||
S3‑230510 | Adding conclusion on KI#3 | Nokia, Nokia Shanghai Bell, China Mobile, Intel, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230344 | |||
S3‑230524 | FL GROUP AUTHORIZATION OF NWDAF(S) IN 5GC | Intel | pCR | Yes |
Yes
| approved | No | S3‑230209 | ||||
S3‑230525 | EN related to Key Refresh and revocation | Intel | pCR | Yes |
Yes
| approved | No | S3‑230237 | ||||
S3‑230546 | Evaluation and EN resolving for solution #14 | China mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑230263 | |||
S3‑230547 | draft TR 33.738 0.5.0 | China Mobile Com. Corporation | draft TR | Approval | No |
No
| reserved | No | ||||
S3‑230574 | Evaluation of Solution#4 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230081 | |||
5.9 | Study on Security Enhancement of support for Edge Computing — phase 2 | S3‑230037 | New Solution of authorization for EDGE-9 reference point | InterDigital Communications | pCR | Yes |
Yes
| revised | No | S3‑230587 | ||
S3‑230587 | New Solution of authorization for EDGE-9 reference point | InterDigital Communications | pCR | - | Yes |
Yes
| approved | No | S3‑230037 | |||
S3‑230097 | Conclusion on KI#2.1 | Huawei, HiSilicon, Thales | pCR | Approval | Yes |
Yes
| revised | No | S3‑230571 | |||
S3‑230098 | Conclusion on KI#2.2 | Huawei, HiSilicon, Thales | pCR | Approval | Yes |
Yes
| merged | No | S3‑230541 | |||
S3‑230099 | Conclusion on KI#2.6 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230572 | |||
S3‑230100 | Adding the overview of the EDGE | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230114 | Add conclusion to KI#2.2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑230541 | |||
S3‑230115 | Add evaluation to solution #6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑230489 | |||
S3‑230158 | Addressing the ENs in solution 15 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230159 | Addressing the ENs in solution 16 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230160 | Evaluation to solution 15 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230470 | |||
S3‑230161 | Evaluation to solution 16 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230471 | |||
S3‑230162 | A new KI for security about EAS discovery procedure via V-EASDF | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230163 | A new solution to security about EAS discovery procedure via V-EASDF | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230472 | |||
S3‑230164 | Conclusion on KI1.x Security about EAS discovery procedure via V-EASDF | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230192 | Address an EN in Sol #11 | OPPO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230202 | Conclusion for KI 2.2 of EDGE Security | OPPO | pCR | Approval | Yes |
Yes
| merged | No | S3‑230541 | |||
S3‑230204 | Resolving ENs in solution #9 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230495 | |||
S3‑230206 | Resolving ENs in solution #10 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230505 | |||
S3‑230208 | Resolving ENs in solution #11 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230508 | |||
S3‑230210 | Address an EN in Sol #9 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230509 | |||
S3‑230211 | Address an EN in Sol #10 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230511 | |||
S3‑230213 | Address some ENs in Sol #11 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230214 | Add evaluation in Sol#11 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230512 | |||
S3‑230224 | A new solution for EEC authentication utilizing tokens | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230484 | |||
S3‑230225 | Updating solution #17 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230226 | Resolving ENs in solution#13 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230227 | Resolving ENs in solution#14 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230228 | Conclusion for KI#2.1 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑230571 | |||
S3‑230229 | Conclusion for KI#2.2 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑230541 | |||
S3‑230287 | Resolving the ENs in solution #22 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑230440 | |||
S3‑230288 | Providing evaluation for solution #22 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230289 | Common authentication method between EEC and ECS/EES | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | S3‑223363 | |||
S3‑230307 | MEC - New key issue on secure retrieve of UE ID | Apple | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230308 | MEC - Discussion paper on enformcement of AF specific identifier | Apple | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑230309 | MEC - LS to SA2 on enforcement of AF specific identifier | Apple | LS out | Approval | Yes |
Yes
| revised | No | S3‑230462 | |||
S3‑230329 | Resolving EN in solution#3 (TR 33.739) | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230538 | |||
S3‑230330 | Resolving EN and updating evaluation in solution#4 (TR 33.739) | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230539 | |||
S3‑230331 | Solution on Public key signature based authentication | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230540 | |||
S3‑230332 | Evaluation for solution#22 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230333 | Conclusion for KI#2.1 | Samsung | pCR | Approval | Yes |
Yes
| merged | No | S3‑230571 | |||
S3‑230334 | Conclusion for KI#2.2 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230541 | |||
S3‑230377 | Conclusion for KI 2.1 Authentication and authorization of the EEC UE by the ECS EES. | Xiaomi communications | pCR | Approval | Yes |
Yes
| merged | No | S3‑230571 | |||
S3‑230378 | Conclusion for KI 2.2 Authentication mechanism selection between EEC and ECSEES | Xiaomi communications | pCR | Approval | Yes |
Yes
| merged | No | S3‑230541 | |||
S3‑230379 | TR 33.379 Evaluation for Sol #5 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230380 | TR 33.379 Resolve ENs for sol #1 and #2 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230381 | TR 33.379 Resolve ENs for Sol #5 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230440 | Resolving the ENs in solution #22 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑230287 | |||
S3‑230462 | MEC - LS to SA2 on enforcement of AF specific identifier | Apple | LS out | Approval | Yes |
Yes
| approved | No | S3‑230309 | |||
S3‑230470 | Evaluation to solution 15 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230160 | |||
S3‑230471 | Evaluation to solution 16 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230161 | |||
S3‑230472 | A new solution to security about EAS discovery procedure via V-EASDF | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230163 | |||
S3‑230484 | A new solution for EEC authentication utilizing tokens | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230224 | |||
S3‑230489 | Add evaluation to solution #6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑230115 | |||
S3‑230495 | Resolving ENs in solution #9 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230204 | |||
S3‑230505 | Resolving ENs in solution #10 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230206 | |||
S3‑230508 | Resolving ENs in solution #11 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230208 | |||
S3‑230509 | Address an EN in Sol #9 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230210 | |||
S3‑230511 | Address an EN in Sol #10 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230211 | |||
S3‑230512 | Add evaluation in Sol#11 of EDGE security | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230214 | |||
S3‑230538 | Resolving EN in solution#3 (TR 33.739) | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230329 | |||
S3‑230539 | Resolving EN and updating evaluation in solution#4 (TR 33.739) | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230330 | |||
S3‑230540 | Solution on Public key signature based authentication | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230331 | |||
S3‑230541 | Conclusion for KI#2.2 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230334 | |||
S3‑230571 | Conclusion on KI#2.1 | Huawei, HiSilicon, Thales | pCR | Approval | Yes |
Yes
| approved | No | S3‑230097 | |||
S3‑230572 | Conclusion on KI#2.6 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230099 | |||
S3‑230573 | Draft TR 33.739 v0.5.0 | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.10 | Study on Personal IoT Networks Security Aspects | S3‑230042 | New solution for PINE authentiation with information provided by PEMC | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑230043 | New solution for conditional PINE authorization by PEMC | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230044 | New solution for PINE authentiation over 5G UP | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230045 | Update solution for PINE authentication and authorization over 5G CP | vivo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230482 | |||
S3‑230046 | Evaluation on Sol#6 | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230047 | Interim conclusions on KI#1 | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230079 | KI#1 New Sol for local PINE authentication | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230116 | Add conclusion for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230117 | Add conclusion for KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230118 | Add evaluation for solution#4 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230157 | Addressing the editor's note in solution 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230469 | |||
S3‑230201 | Propose conclusion to KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230269 | PIN - Evaluation Solution #4 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230305 | Resolution of EN#1 in Solution#7 for KI#1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230306 | Resolution of EN#2 in Solution#7 for KI#1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230385 | TR 33.882 Resolve ENs for sol #5 | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑230531 | |||
S3‑230386 | KI #2, new Sol on AF authorization in PIN scenarios | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230469 | Addressing the editor's note in solution 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230157 | |||
S3‑230482 | Update solution for PINE authentication and authorization over 5G CP | vivo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230045 | |||
S3‑230529 | TR 33.882 v0.5.0 | vivo Mobile Communication (S) | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230531 | TR 33.882 Resolve ENs for sol #5 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑230385 | |||
5.11 | Study on SNAAPP security | S3‑230069 | Update to Solution #4 in SNAAPPY | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230451 | |
S3‑230070 | Solution to address KI#2 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230452 | |||
S3‑230071 | Conclusion to KI#1 in SNAAPPY | Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230072 | Conclusion to KI#2 in SNAAPPY | Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230074 | Sol#3 Resolution of EN on root certificate provisioning | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230075 | Sol#3 Resolution of EN on cross UE API access | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230076 | Sol#3 Resolution of EN on Uastar protocol | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230077 | Sol#3 Resolution of EN on Mutual Authentication | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230520 | |||
S3‑230078 | Sol#3 Resolution of EN on Client Credential Grant | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230522 | |||
S3‑230172 | Address EN for solution 1: onboarding | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230475 | |||
S3‑230173 | Address EN for solution 1: detail for token | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230174 | Address EN for solution 1: authorization decision | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230476 | |||
S3‑230175 | Evaluation Update on Solution 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230477 | |||
S3‑230176 | New Solution on OAuth2.0 Token Revocation | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230177 | Role mapping from TR 23.700-95 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230178 | Conclusion for key issue #2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230230 | A solution for authorization before allowing access to resources | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230486 | |||
S3‑230337 | Update of Key Issue #2 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230543 | |||
S3‑230338 | New Solution on Resource owner Authorization in API Invocation using OAuth 2.0 Authorization Code Grant | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230544 | |||
S3‑230339 | New Solution on Resource owner Authorization in API Invocation | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230545 | |||
S3‑230389 | KI#2, New Sol OAuth 2.0 based API invocation procedure | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑230534 | |||
S3‑230390 | KI#2, New Sol on User authorization revocation for API invocation procedure | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230391 | KI#2, New Sol UE credential based API invocation procedure | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑230535 | |||
S3‑230421 | pCR to 33.884 updating solution #2 | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230515 | |||
S3‑230422 | pCR to 33.884 adding new solution: PKCE flow | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230517 | |||
S3‑230423 | pCR to 33.884 adding new solution: token validation | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230518 | |||
S3‑230451 | Update to Solution #4 in SNAAPPY | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230069 | |||
S3‑230452 | Solution to address KI#2 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230070 | |||
S3‑230475 | Address EN for solution 1: onboarding | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230172 | |||
S3‑230476 | Address EN for solution 1: authorization decision | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230174 | |||
S3‑230477 | Evaluation Update on Solution 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230175 | |||
S3‑230486 | A solution for authorization before allowing access to resources | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230230 | |||
S3‑230515 | pCR to 33.884 updating solution #2 | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230421 | |||
S3‑230517 | pCR to 33.884 adding new solution: PKCE flow | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230422 | |||
S3‑230518 | pCR to 33.884 adding new solution: token validation | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230423 | |||
S3‑230519 | draft TR 33.884 | NTT DOCOMO INC. | draft TR | Approval | No |
No
| reserved | No | ||||
S3‑230520 | Sol#3 Resolution of EN on Mutual Authentication | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230077 | |||
S3‑230522 | Sol#3 Resolution of EN on Client Credential Grant | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230078 | |||
S3‑230534 | KI#2, New Sol OAuth 2.0 based API invocation procedure | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑230389 | |||
S3‑230535 | KI#2, New Sol UE credential based API invocation procedure | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑230391 | |||
S3‑230543 | Update of Key Issue #2 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230337 | |||
S3‑230544 | New Solution on Resource owner Authorization in API Invocation using OAuth 2.0 Authorization Code Grant | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230338 | |||
S3‑230545 | New Solution on Resource owner Authorization in API Invocation | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230339 | |||
5.12 | Study on enhanced security for network slicing Phase 3 | S3‑230061 | Update to KI#1 Providing VPLMN slice information to roaming UE | Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑230062 | Solution to KI#1 eNS | Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230085 | Discussion on KI#1 | Huawei, HiSilicon | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑230086 | KI#1 update | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230087 | Update to KI#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230088 | New solution to KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230089 | New key issue on SoR AF | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230090 | New solution to prevent S-NSSAI leakage | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230119 | New solution to KI#1 protecting SoR container from UDM to UE | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230120 | New solution to KI#1 protecting UE assistance information | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230121 | Update to KI#1 providing VPLMN slice information to roaming UE | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230249 | update to KI#2 temporary network slice | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230250 | solution for KI#2 temporary network slice for NSSAA | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230251 | update to KI#3 network slice admission control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230252 | security solution for KI#3 network slice admission control | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230276 | Key Issue #1 | THALES | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230387 | KI #2 update for partly allowed rejected S-NSSAI | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230388 | New Sol on authorization mechanism for partly rejected S-NSSAI | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230465 | Draft TR 33.886 for eNS3 | Huawei, HiSilicon | draft TR | Yes |
Yes
| approved | No | |||||
5.13 | Study on Security aspects for 5WWC Phase 2 | S3‑230048 | Draft New WID on Security aspect of 5WWC | Nokia, Nokia Shanghai Bell | WID new | Information | Yes |
Yes
| noted | No | ||
S3‑230049 | Scope section alignment | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230050 | updating the existing solution mapping | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230051 | TNAP mobility architecture assumptions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230052 | new solution for AUN3 device supporting 5G Key hierarchy (i.e. N5CW) | Nokia, Nokia Shanghai Bell, CableLabs | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230053 | update conclusion for KI1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230054 | solution 5 update | Nokia, Nokia Shanghai Bell, Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230426 | |||
S3‑230055 | solution 6 update | Nokia, Nokia Shanghai Bell, Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230427 | |||
S3‑230063 | Evaluation to Solution #8 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230446 | |||
S3‑230193 | A new solution on KI#4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230480 | |||
S3‑230194 | Proposed new threat and requirement to KI#3 | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230195 | New solution to KI#3 | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230196 | conclusion to KI#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230481 | |||
S3‑230285 | Resolving the editor’s note in solution #7 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑230439 | |||
S3‑230286 | Evaluation of solution #7 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230416 | Key issue on authentication of N5CW devices behind RG | CableLabs, Nokia, Nokia Shanghai Bell, Rogers Communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230417 | Key issue on authentication of UE behind RG | CableLabs, Rogers Communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑230526 | |||
S3‑230418 | Solution for authentication of UE behind RG using NSWO | CableLabs, Rogers Communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230419 | Key issue on authentication of AUN3 device without 5G credentials | CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230424 | Solution for authentication of AUN3 device without 5G Creden | CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230425 | Draft 33.887 Study on Security aspects for 5WWC Phase 2 | Nokia, Nokia Shanghai Bell | draft TR | Agreement | Yes |
Yes
| approved | No | ||||
S3‑230426 | solution 5 update | Nokia, Nokia Shanghai Bell, Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230054 | |||
S3‑230427 | solution 6 update | Nokia, Nokia Shanghai Bell, Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230055 | |||
S3‑230439 | Resolving the editor’s note in solution #7 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑230285 | |||
S3‑230446 | Evaluation to Solution #8 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230063 | |||
S3‑230480 | A new solution on KI#4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230193 | |||
S3‑230481 | conclusion to KI#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230196 | |||
S3‑230526 | Key issue on authentication of UE behind RG | CableLabs, Rogers Communications, Charter Communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑230417 | |||
5.14 | Study on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the NG-RAN | S3‑230409 | New Key issue on the security of the information transfer of the RAN AI/ML framework | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑230410 | KI2 conclusion | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230575 | Draft TR 33.877 v0.5.0 Study on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the NG-RAN | Ericsson España S.A. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.15 | Study on security support for Next Generation Real Time Communication services | S3‑230092 | address EN for solution#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑230093 | Adding conclusion on KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230094 | Adding conclusion on KI#3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230095 | address EN for solution#4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230569 | |||
S3‑230096 | Adding conclusion on KI#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230290 | Conclusion for key issue #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230412 | Resolve_EN_solution#5 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230568 | |||
S3‑230413 | Resolve_ENs_solution#1 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230568 | Resolve_EN_solution#5 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230412 | |||
S3‑230569 | address EN for solution#4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230095 | |||
S3‑230570 | Draft TR 33.390 v0.5.0 | 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‑230036 | Key issue on SN Name binding for Kausf in SNPN using AAA server for primary authentication | InterDigital Communications | pCR | Yes |
Yes
| noted | No | |||
S3‑230073 | Solution to Key Issue #2 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230453 | |||
S3‑230083 | Removal of EN in Solution#7 | Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230122 | Add a new solution to KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑230490 | |||
S3‑230190 | Add Usecases to Solution 10 | Intel | pCR | Yes |
Yes
| revised | No | S3‑230523 | ||||
S3‑230205 | Conclusion for KI#2 | Intel | pCR | Yes |
Yes
| merged | No | S3‑230445 | ||||
S3‑230231 | Conclusions for KI#1 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230429 | |||
S3‑230232 | Solution to KI#1 – NSWO in SNPN with CH AUSF/UDM | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230431 | |||
S3‑230233 | Evaluation of Solution#9 – NSWO in SNPN | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230432 | |||
S3‑230245 | Update of Solution #11: Resolving Editor's Note on scenarios in SA2 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230444 | |||
S3‑230246 | Update of Solution #11: Resolving Editor's Note in the evaluation | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230247 | Conclusion for KI#2 "Authentication for UE access to hosting network" | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230445 | |||
S3‑230248 | New WID on Security aspects of enhanced support of Non-Public Networks phase 2 | Ericsson | WID new | Discussion | Yes |
Yes
| noted | No | ||||
S3‑230304 | Solution to KI#1 – NSWO in SNPN with CH AAA | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑230521 | |||
S3‑230318 | Evaluation of solution #5 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230319 | Evaluation of solution #12 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230460 | |||
S3‑230320 | Evaluation of solution #13 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230461 | |||
S3‑230321 | Proposal for a conclusion on KI#1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S3‑230429 | |||
S3‑230322 | Proposal for a conclusion on KI#2 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S3‑230445 | |||
S3‑230323 | Discussion paper concerning conclusion of KI#1 | Nokia, Nokia Shanghai Bell | pCR | Discussion | Yes |
Yes
| noted | No | ||||
S3‑230324 | Discussion paper concerning conclusion of KI#2 | Nokia, Nokia Shanghai Bell | pCR | Discussion | Yes |
Yes
| noted | No | ||||
S3‑230382 | TR 33.858 Evaluation for Sol #1 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230383 | TR 33.858 Evaluation for Sol #2 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230384 | TR 33.858 Evaluation for Sol #4 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230429 | Conclusions for KI#1 | Ericsson, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230231 | |||
S3‑230431 | Solution to KI#1 – NSWO in SNPN with CH AUSF/UDM | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230232 | |||
S3‑230432 | Evaluation of Solution#9 – NSWO in SNPN | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230233 | |||
S3‑230444 | Update of Solution #11: Resolving Editor's Note on scenarios in SA2 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230245 | |||
S3‑230445 | Conclusion for KI#2 "Authentication for UE access to hosting network" | Ericsson, Intel, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230247 | |||
S3‑230453 | Solution to Key Issue #2 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑230073 | |||
S3‑230460 | Evaluation of solution #12 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230319 | |||
S3‑230461 | Evaluation of solution #13 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230320 | |||
S3‑230483 | Draft TR 33.858 v0.4.0 | Ericsson | draft TR | Approval | No |
No
| reserved | No | ||||
S3‑230490 | Add a new solution to KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑230122 | |||
S3‑230521 | Solution to KI#1 – NSWO in SNPN with CH AAA | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑230304 | |||
S3‑230523 | Add Usecases to Solution 10 | Intel | pCR | Yes |
Yes
| approved | No | S3‑230190 | ||||
5.17 | Study on Security of Phase 2 for UAS, UAV and UAM | S3‑230024 | Conclusion TR 33.891 KI #1 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑230449 | |
S3‑230025 | Update conclusion TR 33.891 KI #3 | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230433 | |||
S3‑230026 | Update conclusion TR 33.891 KI #4. | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑230434 | |||
S3‑230027 | LS on support for Restricted ProSe Direct Discovery for UAS | InterDigital, Europe, Ltd. | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑230066 | Conclusion to KI#1 Direct C2 Security | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230449 | |||
S3‑230067 | Conclusion to KI#2 Security of DAA unicast connection | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑230450 | |||
S3‑230068 | Conclusion to KI#3 Direct C2 Authorization | Lenovo | pCR | Approval | Yes |
Yes
| merged | No | S3‑230433 | |||
S3‑230180 | Add conclusion to KI#2 about DAA unicast security | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑230450 | |||
S3‑230181 | Add conclusion to KI#1 about Direct C2 security | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑230449 | |||
S3‑230277 | Resolve EN on discovery in solution #3 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230278 | Resolve EN on pairing in solution #3 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230279 | Evaluation of solution #3 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230280 | Editorial changes to UAS TR | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230281 | Conclusion for key issue #1 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑230449 | |||
S3‑230282 | Conclusion for key issue #2 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑230450 | |||
S3‑230283 | Additional to conclusion for key issue #3 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑230433 | |||
S3‑230284 | Conclusion for key issue #7 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230433 | Update conclusion TR 33.891 KI #3 | InterDigital, Europe, Ltd., Lenovo, Qualcomm | pCR | Approval | Yes |
Yes
| approved | No | S3‑230025 | |||
S3‑230434 | Update conclusion TR 33.891 KI #4. | InterDigital, Europe, Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑230026 | |||
S3‑230441 | Draft TR 33.891 | Qualcomm | draft TR | Approval | Yes |
Yes
| approved | No | S3‑224112 | |||
S3‑230449 | Conclusion to KI#1 Direct C2 Security | Lenovo, Qualcomm, Huawei, Interdigital | pCR | Approval | Yes |
Yes
| approved | No | S3‑230066 | |||
S3‑230450 | Conclusion to KI#2 Security of DAA unicast connection | Lenovo, Huawei, Qualcomm | pCR | Approval | Yes |
Yes
| approved | No | S3‑230067 | |||
5.18 | Study to enable URSP rules to securely identify Applications |   | ||||||||||
5.19 | Study on Security Aspects of Ranging Based Services and Sidelink Positioning | S3‑230038 | New Key issue for Monitoring and detecting attacks on ranging devices and services | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑230125 | New KI on security of ranging usiong assistance UE | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230154 | update to solution 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230467 | |||
S3‑230155 | update the evaluation in solution 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230468 | |||
S3‑230156 | conclusion on key issue 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230182 | New solution of security for the Ranging SL positioning device discovery | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230183 | New solution for protecting direct communnication | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230184 | New solution to select assistant ranging procedure based on privacy requirement | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230236 | Update to solution#6 in TR 33.893 - add authorization check step | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| approved | No | |||||
S3‑230238 | Update to solution#6 in TR 33.893 - SLPK ID usage | China Telecom Corporation Ltd. | pCR | Yes |
Yes
| approved | No | |||||
S3‑230259 | New solution with authorization tokens exchanged after PC5 security establishment | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230502 | |||
S3‑230260 | Update of evaluation to solution #2 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230503 | |||
S3‑230261 | Update of evaluation to solution #3 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230504 | |||
S3‑230272 | Ranging - New solution KI#1, #2, #3 | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230273 | Ranging - Update Key Issue #1- privacy risks of exposing positioning reference signals | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230299 | reply LS on SL positioning groupcast and broadcast | Qualcomm Incorporated | LS out | Approval | Yes |
Yes
| merged | No | S3‑230430 | |||
S3‑230300 | Updates to the Key Issue #4 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑230527 | |||
S3‑230301 | A new solution for groupcast protection for Ranging/SL Positioning services | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230353 | pCR to TR33.893 New key issue on groupcast and broadcast security | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑230566 | |||
S3‑230354 | pCR to TR33.893 New solution for protecting groupcast and broadcast data in coverage | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230355 | pCR to TR33.893 New solution for protecting groupcast and broadcast data in out of coverage | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230357 | [Draft] Reply LS on SL positioning groupcast and broadcast | Xiaomi Technology | LS out | Approval | Yes |
Yes
| merged | No | S3‑230430 | |||
S3‑230358 | 33.893: Additional Evaluation for Solution #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230359 | 33.893: Update to Solution #2 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑230559 | |||
S3‑230360 | 33.893: Resolve the Editor’s Note in Solution #4 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230361 | 33.893: Evaluation for Solution #4 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑230560 | |||
S3‑230362 | 33.893: Evaluation for Solution #6 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑230562 | |||
S3‑230363 | 33.893: Resolve the Editor’s Note in Solution #7 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230364 | 33.893: New Solution on Token-based Authorization of the Role of the UE during Discovery | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230365 | 33.893: New Solution on Role Verification during Discovery based on Discovery Keys | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230366 | 33.893: New Solution on Authorization of SL Positioning Client UE for Obtaining Ranging Result | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑230561 | |||
S3‑230403 | New solution on Ranging/SL Positioning discovery and link establishment procedure for V2X capable UEs | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230404 | Remove the Editor's Note of solution #3 in TR 33.893 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230405 | Remove the Editor's Note of solution #5 in TR 33.893 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑230555 | |||
S3‑230467 | update to solution 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230154 | |||
S3‑230468 | update the evaluation in solution 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230155 | |||
S3‑230502 | New solution with authorization tokens exchanged after PC5 security establishment | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230259 | |||
S3‑230503 | Update of evaluation to solution #2 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230260 | |||
S3‑230504 | Update of evaluation to solution #3 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑230261 | |||
S3‑230527 | Updates to the Key Issue #4 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑230300 | |||
S3‑230555 | Remove the Editor's Note of solution #5 in TR 33.893 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑230405 | |||
S3‑230559 | 33.893: Update to Solution #2 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑230359 | |||
S3‑230560 | 33.893: Evaluation for Solution #4 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑230361 | |||
S3‑230561 | 33.893: New Solution on Authorization of SL Positioning Client UE for Obtaining Ranging Result | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑230366 | |||
S3‑230562 | 33.893: Evaluation for Solution #6 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑230362 | |||
S3‑230564 | draft TR 33.893 v0.5.0 | Xiaomi Technology | draft TR | Approval | No |
No
| reserved | No | ||||
S3‑230566 | pCR to TR33.893 New key issue on groupcast and broadcast security | CATT, Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑230353 | |||
5.20 | Study on Security and Privacy of AI/ML-based Services and Applications in 5G | S3‑230034 | New key issue on Federated Learning AIML model privacy protection | InterDigital Communications | pCR | Yes |
Yes
| noted | No | |||
S3‑230035 | New key issue on Federated Learning AIML model protection | InterDigital Communications | pCR | Yes |
Yes
| noted | No | |||||
S3‑230124 | LS on clarification on user consent for AIML | OPPO | LS out | Approval | Yes |
Yes
| revised | No | S3‑230491 | |||
S3‑230217 | New solution on reusing existing authorization mechanism for 5G assistance information exposure to AF | OPPO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230218 | New solution on authorization for 5GC assistance information exposure to external AF | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230513 | |||
S3‑230220 | New solution on authorization for 5GC assistance information exposure to internal AF | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230514 | |||
S3‑230222 | New solution on authorization for 5GC assistance information exposure to internal AF | OPPO | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑230223 | New solution on privacy protection for 5GC assistance information exposure to AF | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑230516 | |||
S3‑230372 | KI #1, New Sol on OAuth 2.0 based 5GC assistance information exposure authorization | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230373 | TR 33.898 Resolve EN for sol #2 | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230491 | LS on clarification on user consent for AIML | OPPO | LS out | Approval | Yes |
Yes
| approved | No | S3‑230124 | |||
S3‑230494 | Draft TR 33.898 v0.4.0 | OPPO | draft TR | Approval | No |
No
| reserved | No | ||||
S3‑230513 | New solution on authorization for 5GC assistance information exposure to external AF | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230218 | |||
S3‑230514 | New solution on authorization for 5GC assistance information exposure to internal AF | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230220 | |||
S3‑230516 | New solution on privacy protection for 5GC assistance information exposure to AF | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑230223 | |||
5.21 | Study on applicability of the Zero Trust Security principles in mobile networks |   | ||||||||||
5.22 | Study of Security aspects on User Consent for 3GPP Services Phase 2 | S3‑230039 | New key issue on enhancement of user consent for using MDT for NG-RAN AI/ML | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| noted | No | |||
S3‑230084 | 33.896: Updates to Key Issue on User Consent for NTN | Google Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230165 | Key Issue Update on User Consent for NTN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230473 | |||
S3‑230166 | Implict User Consent for NTN feature usage | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230167 | Conclusion for key issue #2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230168 | User consent for roaming scenarios where the data source is in vPLMN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230169 | User consent for roaming scenarios where the data source is in hPLMN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230170 | Conclusion for key issue #1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230474 | |||
S3‑230171 | Conclusion for key issue #4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230370 | 33.896: Evaluation for Solution #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230371 | 33.896: Evaluation for Solution #2 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230406 | Remove the Editor's Note and evaluate the solution #3 in TR 33.896 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230407 | Remove the Editor's Note and evaluate the solution #4 in TR 33.896 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230408 | Conclusion on Key Issue #1 in TR 33.896 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| merged | No | S3‑230474 | |||
S3‑230414 | KI and Solution on user consent in roaming | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| noted | No | |||||
S3‑230415 | Sol update central authorization for user consent handling | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| noted | No | |||||
S3‑230473 | Key Issue Update on User Consent for NTN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230165 | |||
S3‑230474 | Conclusion for key issue #1 | Huawei, HiSilicon, Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑230170 | |||
S3‑230530 | TR 33.896v050 | Huawei;HiSilicon | draft TR | Yes |
Yes
| approved | No | |||||
5.23 | Study on security enhancements for 5G multicast-broadcast services Phase 2 | S3‑230041 | TMGI protection during group Paging | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| noted | No | |||
S3‑230149 | A new solution to address the privacy issue with TMGI | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230150 | conclusion on key issue 2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230151 | Addressing the editor's note in solution 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑230466 | |||
S3‑230152 | Discussion paper on way forward of key issue#1 | Huawei, HiSilicon | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑230153 | conclusion on key issue 1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230302 | A new solution for mitigating privacy attacks exploiting group paging with TMGI | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230335 | Updates to solution#1 in TR 33.883 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑230542 | |||
S3‑230336 | [MBS] Conclusion for Key Issue#1 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230464 | Draft TR 33.883 | Huawei, HiSilicon | draft TR | No |
No
| reserved | No | |||||
S3‑230466 | Addressing the editor's note in solution 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑230151 | |||
S3‑230542 | Updates to solution#1 in TR 33.883 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑230335 | |||
5.24 | Study on enhanced Security Aspects of the 5G Service Based Architecture | S3‑230021 | KI10 solution 25 update on security profiles | BSI (DE), Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230493 | |
S3‑230022 | KI10 update on RHUB | BSI (DE), Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230496 | |||
S3‑230023 | KI12 solution 19 update on hosted SEPP | BSI (DE), Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230507 | |||
S3‑230127 | KI1 corrections | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230128 | KI1 sol13 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230577 | |||
S3‑230129 | KI1 analysis update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230578 | |||
S3‑230130 | KI3 sol12 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230131 | KI4 analysis and conclusion update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230579 | |||
S3‑230132 | KI3 sol15 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230133 | KI5 sol16 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230580 | |||
S3‑230134 | KI6 conclusion update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230581 | |||
S3‑230135 | KI7 Sol17 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230136 | KI8 conclusion update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230582 | |||
S3‑230137 | KI10 analysis and conclusion on RHUB | Nokia, Nokia Shanghai Bell, BSI | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230138 | KI10 sol20 EN resolution – reference to new study | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230139 | KI11 resolution of ENs in sol21 and sol22 by adding the related solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230140 | KI12 sol19 EN resolution – reference to new study | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230141 | KI12 Hosted SEPP solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑230583 | |||
S3‑230142 | KI12 analysis and conclusion on hosted SEPP | Nokia, Nokia Shanghai Bell, BSI | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑230143 | Study on 5G roaming topics | Nokia, Nokia Shanghai Bell | pCR | Endorsement | Yes |
Yes
| revised | No | S3‑230576 | |||
S3‑230144 | SID on 5G roaming issues | Nokia, Nokia Shanghai Bell | SID new | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑230313 | New Solution to KI #11 based on Nnrf_AccesToken Service | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230314 | New Solution to KI #11 based on O&M Provisioning NRF with NFc profile | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230315 | Discussion. Key issue #12: Security in Hosted SEPP scenarios | Ericsson | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑230316 | Update of Key issue #12: Security in Hosted SEPP scenarios | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑230585 | |||
S3‑230585 | Update of Key issue #12: Security in Hosted SEPP scenarios | Ericsson,Nokia, Nokia Shanghai Bell, Mavenir | pCR | Approval | Yes |
Yes
| revised | No | S3‑230588 | S3‑230316 | ||
S3‑230588 | Update of Key issue #12: Security in Hosted SEPP scenarios | Ericsson,Nokia, Nokia Shanghai Bell, Mavenir | pCR | Approval | Yes |
Yes
| approved | No | S3‑230585 | |||
S3‑230317 | Solution for KI#12: Security in Hosted SEPP scenarios | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230428 | TR 33.875-160 | Nokia, Nokia Shanghai Bell | draft TR | Yes |
Yes
| approved | No | |||||
S3‑230493 | KI10 solution 25 update on security profiles | BSI (DE), Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230021 | |||
S3‑230496 | KI10 update on RHUB | BSI (DE), Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230022 | |||
S3‑230507 | KI12 solution 19 update on hosted SEPP | BSI (DE), Nokia, Nokia Shanghai Bell, Deutsche Telekom | pCR | Approval | Yes |
Yes
| approved | No | S3‑230023 | |||
S3‑230576 | Study on 5G roaming topics | Nokia, Nokia Shanghai Bell, Deutsche Telekom | discussion | Endorsement | Yes |
Yes
| endorsed | No | S3‑230143 | |||
S3‑230577 | KI1 sol13 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230128 | |||
S3‑230578 | KI1 analysis update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230129 | |||
S3‑230579 | KI4 analysis and conclusion update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230131 | |||
S3‑230580 | KI5 sol16 EN resolution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230133 | |||
S3‑230581 | KI6 conclusion update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230134 | |||
S3‑230582 | KI8 conclusion update | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230136 | |||
S3‑230583 | KI12 Hosted SEPP solution | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑230141 | |||
5.25 | Study on Security Aspects of Satellite Access | S3‑230019 | Key Issue for NAS UE Registration Procedure | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑230020 | New Key Issue on Protection of 5GS SIB19 | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| noted | No | |||||
S3‑230367 | 33.700-28: Add Potential Requirements for Key Issue #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑230563 | |||
S3‑230368 | 33.700-28: New Key Issue on Protection of UE Unreachability Period retrieved by the UE | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230369 | 33.700-28: New Solution to KI#1 for AF Authorization on per UE Level | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑230563 | 33.700-28: Add Potential Requirements for Key Issue #1 | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑230367 | |||
S3‑230565 | draft TR 33.700-28 v0.3.0 | Xiaomi Technology | draft TR | Approval | No |
No
| reserved | No | ||||
6 | New Study/Work item proposals |   | ||||||||||
7 | CVD and research |   | ||||||||||
8 | Any Other Business | S3‑230004 | Report from SA#98 on SA3 topics | WG Chair | report | Yes |
Yes
| noted | No |