Tdoc List
2025-01-29 11:36
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Agenda and Meeting Objectives | S3‑250001 | Agenda | SA WG3 Chair | agenda | Yes |
Yes
| approved | No | |||
S3‑250002 | Process for SA3#119AdHoc-e | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
S3‑250003 | Detailed agenda planning | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
2 | Meeting Reports |   | ||||||||||
2.1 | Previous SA3 meeting report/s and SA report |   | ||||||||||
2.2 | SA3-LI Report |   | ||||||||||
3 | Reports and Liaisons from other Groups |   | ||||||||||
3.1 | Reports and Liaisons related to topics in agenda | S3‑250004 | LS on security aspects of Ambient IoT | S2-2411049 | LS in | Yes |
Yes
| postponed | No | |||
S3‑250005 | LS on RAN2 outcome of Ambient IoT study | R2-2411263 | LS in | Yes |
Yes
| noted | No | |||||
S3‑250006 | Reply to LS on Further Clarification for Ambient IoT Security | S1-244920 | LS in | Yes |
Yes
| noted | No | |||||
S3‑250007 | LS on A-IoT Conclusions in SA WG2 | S2-2413035 | LS in | Yes |
Yes
| noted | No | |||||
S3‑250008 | Reply LS on terminology alignment between SA6 and SA3 | S6-245644 | LS in | Yes |
Yes
| noted | No | |||||
S3‑250009 | Reply LS on clarifications on consent management | SP-241934 | LS in | Yes |
Yes
| noted | No | |||||
S3‑250043 | Reply LS on security aspects of Ambient IoT | OPPO | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑250071 | LS reply to LS on security aspects of Ambient IoT | Nokia | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑250130 | LS on User Consent aspects for Energy Saving | Ericsson | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑250237 | SA3 leadership meeting notes | MCC | report | Information | Yes |
No
| available | No | ||||
3.2 | Follow up topics from LSs |   | ||||||||||
4 | Work areas |   | ||||||||||
4.1 | Maintenance (Rel-15/16/17/18) |   | ||||||||||
4.1.1 | Security Assurance |   | ||||||||||
4.1.2 | Service Based Architecture |   | ||||||||||
4.1.3 | Security Aspects of Proximity based services in 5GS ProSe |   | ||||||||||
4.1.4 | Mission Critical |   | ||||||||||
4.1.5 | Authentication and key management for applications based on 3GPP credential in 5G |   | ||||||||||
4.1.6 | Enhancements to User Plane Integrity Protection Support in 5GS |   | ||||||||||
4.1.7 | Security Aspects of Enhancements for 5G Multicast-Broadcast Services |   | ||||||||||
4.1.8 | Security for enhanced support of Industrial IoT |   | ||||||||||
4.1.9 | Security Aspects of eNPN |   | ||||||||||
4.1.10 | Security Aspects of Enhancement of Support for Edge Computing in 5GC |   | ||||||||||
4.1.11 | Security aspects of Uncrewed Aerial Systems |   | ||||||||||
4.1.12 | Security Aspects of Ranging Based Services and Sidelink Positioning |   | ||||||||||
4.1.13 | Security Aspects of eNA. |   | ||||||||||
4.1.14 | Modified PRINS for roaming service providers in 5G |   | ||||||||||
4.1.15 | All other maintenance topics (not listed above) |   | ||||||||||
4.2 | WID on 5G Security Assurance Specification (SCAS) for the Unified Data Repository (UDR). |   | ||||||||||
4.3 | WID on SCAS for Rel-18 features on existing functions. |   | ||||||||||
4.4 | WID on 5G Security Assurance Specification (SCAS) for the Short Message Service Function (SMSF). |   | ||||||||||
4.5 | WID on Addition of 256-bit security Algorithms. |   | ||||||||||
4.6 | WID on mission critical security enhancements for release 19 |   | ||||||||||
4.7 | WID on Addition of Milenage-256 algorithm |   | ||||||||||
4.8 | WID on 3GPP profiles for cryptographic algorithms and security protocols |   | ||||||||||
4.9 | WID on security aspects of the 5GMSG Service phase 3 |   | ||||||||||
4.10 | R19 SCAS WID |   | ||||||||||
4.11 | TEI19 topics (restricted to agreed topics only) |   | ||||||||||
4.12 | WID on Security aspects of NR mobility enhancement Phase 4 |   | ||||||||||
4.13 | WID on Security for mobility over non-3GPP access to avoid full primary authentication |   | ||||||||||
4.14 | WID on WID on Security for MonStra |   | ||||||||||
5 | Rel-19 Studies |   | ||||||||||
5.1 | Study on enablers for Zero Trust Security |   | ||||||||||
5.2 | Study on the security support for the Next Generation Real Time Communication services phase 2 | S3‑250089 | Updates to solution#6 | Samsung | other | Approval | Yes |
Yes
| revised | No | S3‑250184 | |
S3‑250090 | Evaluation updates for solution#6 | Samsung | other | Approval | Yes |
Yes
| revised | No | S3‑250185 | |||
S3‑250091 | Conclusion for Key issue#2 | Samsung | other | Approval | Yes |
Yes
| merged | No | S3‑250192 | |||
S3‑250131 | Solution#5 update for alignment with SA2 and addressing EN | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑250207 | |||
S3‑250132 | Conclusion to KI#2 of NG_RTC | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑250192 | |||
S3‑250133 | Conclusion to KI#3 of NG_RTC | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑250210 | |||
S3‑250154 | Conclusion for KI2 IMS based Avatar Communication | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| merged | No | S3‑250192 | |||
S3‑250155 | Update KI#1: Third party specific user identities to include NEF-AF interface security | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑250156 | LS on IMS support for AF authorization | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S3‑250170 | |||
S3‑250157 | Conclusion for KI3 IMS DC capability exposure | Nokia, Nokia Shanghai Bell | other | Approval | Yes |
Yes
| merged | No | S3‑250210 | |||
S3‑250170 | LS on IMS support for AF authorization and IMS avatar communication | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S3‑250156 | |||
S3‑250184 | Updates to solution#6 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑250089 | |||
S3‑250185 | Evaluation updates for solution#6 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑250090 | |||
S3‑250192 | Conclusion to KI#2 of NG_RTC | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑250132 | |||
S3‑250205 | Draft TR 33.790 v1.1.0 Study on the security support for the next generation real time communication services phase 2 | Ericsson Hungary Ltd | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250207 | Solution#5 update for alignment with SA2 and addressing EN | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑250131 | |||
S3‑250210 | Conclusion to KI#3 of NG_RTC | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑250133 | |||
5.3 | Study on security for PLMN hosting a NPN |   | ||||||||||
5.4 | Study of ACME for Automated Certificate Management in SBA |   | ||||||||||
5.5 | Study on enabling a cryptographic algorithm transition to 256-bits |   | ||||||||||
5.6 | Study on mitigations against bidding down attacks |   | ||||||||||
5.7 | Study on security Aspects of 5G Satellite Access Phase 2 |   | ||||||||||
5.8 | Study on security for mobility over non-3GPP access to avoid full primary authentication |   | ||||||||||
5.9 | Study on security Aspect of Ambient IoT Services in 5G | S3‑250010 | New KI: Reader Authorization for 5G Ambient IoT Services | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑250011 | KI#3, Conclusions | Sony | pCR | Approval | Yes |
Yes
| merged | No | S3‑250224 | |||
S3‑250012 | KI#5, Conclusions | Sony | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250013 | Conclusion to key issue#1 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑250195 | |||
S3‑250014 | Conclusion to key issue#3 | Lenovo | pCR | Approval | Yes |
Yes
| merged | No | S3‑250224 | |||
S3‑250015 | Conclusion to key issue#4 | Lenovo | pCR | Approval | Yes |
Yes
| merged | No | S3‑250206 | |||
S3‑250016 | Conclusion to key issue#5 | Lenovo | pCR | Approval | Yes |
Yes
| merged | No | S3‑250226 | |||
S3‑250024 | Resolving ENs in sol#6 in TR 33.713 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250025 | Evaluation for solution 6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑250208 | |||
S3‑250026 | Update the KI#2 in TR 33.713 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250027 | Update the KI#3 in TR 33.713 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250028 | Update the scope in TR 33.713 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑250209 | |||
S3‑250029 | Conclusion for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑250195 | |||
S3‑250030 | Conclusion for KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑250223 | |||
S3‑250031 | Conclusion for KI#3 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑250224 | |||
S3‑250032 | Conclusion for KI#4 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑250206 | |||
S3‑250033 | Conclusion for KI#5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑250226 | |||
S3‑250041 | Conclusion on AIOT KI#3 | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑250224 | |||
S3‑250042 | Update AIOT KI#3 | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250044 | addressing the editor's note in solution#4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑250203 | |||
S3‑250045 | Discussion paper on the conclusion on key issue#5 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250046 | conclusion on key issue#4 | Huawei, HiSilicon, OPPO, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S3‑250206 | |||
S3‑250047 | Generic conclusion on AIoT | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑250204 | |||
S3‑250054 | Adding evaluation for solution#3 | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑250055 | Update solution#8 | Apple | pCR | Yes |
Yes
| revised | No | S3‑250175 | ||||
S3‑250056 | Update solution#28 | Apple | pCR | Yes |
Yes
| revised | No | S3‑250176 | ||||
S3‑250057 | Update solution#31 | Apple | pCR | Yes |
Yes
| approved | No | |||||
S3‑250058 | Conclusion on KI#5 AIoT Authentication | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑250226 | |||
S3‑250059 | pCR to TR33.713 Update solution#9 to remove EN | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑250231 | |||
S3‑250060 | pCR to TR33.713 New solution AIoT command message security protection procedure | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250061 | pCR to TR33.713 Generic conclusion | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑250204 | |||
S3‑250066 | Proposal for a conclusion | Nokia | pCR | Approval | Yes |
Yes
| merged | No | S3‑250204 | |||
S3‑250067 | Proposal for a resolution to an EN concerning counter synchronisation | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250068 | Proposal for a resolution of an EN concerning alignment with RAN specifications | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250069 | Proposal for a resolution to an EN concerning device constrains | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S3‑250174 | |||
S3‑250070 | Proposal for a resolution to an EN concerning key identification | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250072 | pCR to TR33.713 Conclusion#3 | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑250224 | |||
S3‑250073 | pCR to TR33.713 Conclusion#4 | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑250206 | |||
S3‑250074 | pCR to TR33.713 Conclusion#5 | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑250226 | |||
S3‑250075 | Conclusion for KI#2 in TR 33.713 | OPPO, Xiaomi | pCR | Approval | Yes |
Yes
| revised | No | S3‑250223 | |||
S3‑250076 | pCR to TR33.713 Update solution#30 to remove EN | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250077 | Resolving ENs for AIoT Security Sol#37 | Xidian, OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑250225 | |||
S3‑250078 | Resolving ENs in Solution #42 of TR 33.713 | KPN N.V. | pCR | Yes |
Yes
| revised | No | S3‑250183 | ||||
S3‑250079 | New Solution to KI#5 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑250177 | |||
S3‑250080 | New key issue for secure storage in AIoT devices | Ericsson, Thales | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250081 | New Key Issue on Amplification of resource exhaustion by exploiting AIoT paging messages | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250082 | New key issue for Authenticated and authorized access to devices in Ambient IoT via 3GPP core | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250083 | Pseudo-CR-General conclusion for the architecture of AIoT | China mobile | pCR | Yes |
Yes
| revised | No | S3‑250232 | ||||
S3‑250084 | Pseudo-CR-System architecture and security assumptions for AIoT services | China mobile | pCR | Yes |
Yes
| revised | No | S3‑250233 | ||||
S3‑250085 | Pseudo-CR on New solution on AIoT privacy | China mobile | pCR | Yes |
Yes
| noted | No | |||||
S3‑250092 | Resolving EN in solution #22 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑250186 | |||
S3‑250093 | Evaluation update for solution#22 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250094 | Resolving EN in solution #38 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250095 | Evaluation to solution #38 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250110 | Conclusion for KI#4 in TR 33.713 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| merged | No | S3‑250206 | |||
S3‑250111 | Conclusion for KI#5 in TR 33.713 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| merged | No | S3‑250226 | |||
S3‑250120 | Solution#1 update: Addressing ENs | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑250230 | |||
S3‑250121 | Solution#1 evaluation update | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑250229 | |||
S3‑250122 | KI#1 update: Addressing EN | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250123 | KI#3 update: Addressing ENs | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑250228 | |||
S3‑250124 | KI#4 update: Addressing ENs | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S3‑250227 | |||
S3‑250125 | KI#3 conclusions | Philips International B.V. | pCR | Approval | Yes |
Yes
| merged | No | S3‑250224 | |||
S3‑250126 | KI#4 conclusions | Philips International B.V. | pCR | Approval | Yes |
Yes
| merged | No | S3‑250206 | |||
S3‑250127 | KI#5 conclusions | Philips International B.V. | pCR | Approval | Yes |
Yes
| merged | No | S3‑250226 | |||
S3‑250134 | Update on Key Issue#6 | vivo | pCR | Approval | Yes |
Yes
| revised | No | S3‑250217 | |||
S3‑250135 | Sol#10 update | vivo | pCR | Approval | Yes |
Yes
| revised | No | S3‑250218 | |||
S3‑250136 | Sol#40 update | vivo | pCR | Approval | Yes |
Yes
| revised | No | S3‑250219 | |||
S3‑250137 | Sol#41 update | vivo | pCR | Approval | Yes |
Yes
| revised | No | S3‑250220 | |||
S3‑250138 | Conclusion for Key Issue#4 Information Protection | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250139 | Conclusion for Key Issue#5 AIoT Authentication | vivo | pCR | Approval | Yes |
Yes
| merged | No | S3‑250226 | |||
S3‑250140 | Conclusion to KI#1 | OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑250193 | |||
S3‑250141 | Solution#3 update | OPPO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250142 | Solution#18 update | OPPO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250143 | Solution#19 update | OPPO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250144 | Authorization of external AF for Inventory | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| revised | No | S3‑250194 | S3‑245132 | ||
S3‑250145 | KI on attacking via external carrier wave | NTT DOCOMO INC. | pCR | Yes |
Yes
| noted | No | |||||
S3‑250158 | Comments on S3-250145, “KI on attacking via external carrier wave” | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250159 | Generic conclusion for AIoT | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑250204 | |||
S3‑250174 | Proposal for a resolution to an EN concerning device constrains | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑250069 | |||
S3‑250175 | Update solution#8 | Apple | pCR | Yes |
Yes
| approved | No | S3‑250055 | ||||
S3‑250176 | Update solution#28 | Apple | pCR | Yes |
Yes
| approved | No | S3‑250056 | ||||
S3‑250177 | New Solution to KI#5 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑250079 | |||
S3‑250183 | Resolving ENs in Solution #42 of TR 33.713 | KPN N.V. | pCR | Yes |
Yes
| approved | No | S3‑250078 | ||||
S3‑250186 | Resolving EN in solution #22 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑250092 | |||
S3‑250193 | Conclusion to KI#1 | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑250140 | |||
S3‑250194 | Authorization of external AF for Inventory | NTT DOCOMO INC. | pCR | Approval | Yes |
Yes
| approved | No | S3‑250144 | |||
S3‑250195 | Conclusion to key issue#1 | Lenovo, ZTE, OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑250013 | |||
S3‑250202 | draft TR 33.713 v0.6.0 | OPPO | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250203 | addressing the editor's note in solution#4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑250044 | |||
S3‑250204 | Generic conclusion on AIoT | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑250047 | |||
S3‑250206 | conclusion on key issue#4 | Huawei, HiSilicon, OPPO, China Unicom, Lenovo, ZTE, CATT, Xiaomi, Philips | pCR | Approval | Yes |
Yes
| noted | No | S3‑250046 | |||
S3‑250208 | Evaluation for solution 6 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑250025 | |||
S3‑250209 | Update the scope in TR 33.713 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑250028 | |||
S3‑250217 | Update on Key Issue#6 | vivo | pCR | Approval | Yes |
Yes
| approved | No | S3‑250134 | |||
S3‑250218 | Sol#10 update | vivo | pCR | Approval | Yes |
Yes
| approved | No | S3‑250135 | |||
S3‑250219 | Sol#40 update | vivo | pCR | Approval | Yes |
Yes
| approved | No | S3‑250136 | |||
S3‑250220 | Sol#41 update | vivo | pCR | Approval | Yes |
Yes
| approved | No | S3‑250137 | |||
S3‑250223 | Conclusion for KI#2 in TR 33.713 | OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑250075 | |||
S3‑250224 | Conclusion on AIOT KI#3 | OPPO | pCR | Approval | Yes |
Yes
| noted | No | S3‑250041 | |||
S3‑250225 | Resolving ENs for AIoT Security Sol#37 | Xidian, OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑250077 | |||
S3‑250226 | Conclusion on KI#5 AIoT Authentication | OPPO, Huawei, HiSilicon, Apple | pCR | Approval | Yes |
Yes
| approved | No | S3‑250058 | |||
S3‑250227 | KI#4 update: Addressing ENs | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑250124 | |||
S3‑250228 | KI#3 update: Addressing ENs | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑250123 | |||
S3‑250229 | Solution#1 evaluation update | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑250121 | |||
S3‑250230 | Solution#1 update: Addressing ENs | Philips International B.V. | pCR | Approval | Yes |
Yes
| approved | No | S3‑250120 | |||
S3‑250231 | pCR to TR33.713 Update solution#9 to remove EN | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑250059 | |||
S3‑250232 | Pseudo-CR-General conclusion for the architecture of AIoT | China mobile | pCR | Yes |
Yes
| approved | No | S3‑250083 | ||||
S3‑250233 | Pseudo-CR-System architecture and security assumptions for AIoT services | China mobile | pCR | Yes |
Yes
| approved | No | S3‑250084 | ||||
5.10 | Study on security aspects of Usage of User Identities |   | ||||||||||
5.11 | Study on UAS security enhancement |   | ||||||||||
5.12 | Study on security Aspects of Enhancement for Proximity Based Services in 5GS Phase 3 |   | ||||||||||
5.13 | Study on security aspects of AIML enhancements |   | ||||||||||
5.14 | Study on EdgeComputing |   | ||||||||||
5.15 | Study on security aspects for Multi-Access |   | ||||||||||
5.16 | Study on 5GS enhancements for Energy Saving | S3‑250048 | Resolve various EN's for KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑250173 | |
S3‑250049 | Conclusion for KI#1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑250171 | |||
S3‑250050 | conclusion to KI#2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑250172 | |||
S3‑250062 | Proposal for a conclusion to KI#1 | Nokia, Deutsche Telekom, BMWK, IIT Bombay | pCR | Approval | Yes |
Yes
| revised | No | S3‑250171 | |||
S3‑250063 | Proposal for a conclusion to KI#2 | Nokia, Deutsche Telekom, IIT Bombay | pCR | Approval | Yes |
Yes
| revised | No | S3‑250172 | |||
S3‑250064 | TR cleanup | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S3‑250173 | |||
S3‑250065 | Presentation of Report to TSG: TR 33.766, Version 1.0.0 | Nokia | TS or TR cover | Information | Yes |
Yes
| endorsed | No | ||||
S3‑250128 | Conclusion for KI#1 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑250171 | |||
S3‑250129 | Conclusion for KI#2 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑250172 | |||
S3‑250171 | Proposal for a conclusion to KI#1 | Nokia, Deutsche Telekom, BMWK, IIT Bombay, Ericsson, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑250062 | |||
S3‑250172 | Proposal for a conclusion to KI#2 | Nokia, Deutsche Telekom, IIT Bombay, Ericsson, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑250063 | |||
S3‑250173 | TR cleanup | Nokia, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑250064 | |||
S3‑250221 | Draft TR 33.766 v0.6.0 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.17 | Study on security aspects of 5G NR Femto |   | ||||||||||
5.18 | Study on security aspects of 5G Mobile Metaverse services | S3‑250034 | Conclusion for KI#3 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑250211 | |
S3‑250051 | Update on Solution #6-Digital asset request validation | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250052 | Conclusion to KI#3 in TR 33.721 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑250211 | |||
S3‑250088 | [TR 33.721] Update to solution#6 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑250190 | |||
S3‑250112 | 33.721: Evaluation of Solution 10 | Xiaomi EV Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑250213 | |||
S3‑250113 | 33.721: Update to Conclusion on Key Issue #2 | Xiaomi EV Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑250214 | |||
S3‑250114 | 33.721: Conclusion on Key Issue #4 | Xiaomi EV Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑250215 | |||
S3‑250146 | Evaluation for Sol2 Authorization supporting spatial localization service with CCF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250147 | Update Sol3 Authorization supporting spatial localization service with CCF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑250178 | |||
S3‑250148 | Update Sol5 Privacy protection during metaverse service discovery | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑250179 | |||
S3‑250149 | Update Sol7 authorize avatar by metaverse service provider | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250150 | Update Sol8 authenticate and authorize DA client to create a digital asset | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑250180 | |||
S3‑250151 | Update Sol9 authenticate and authorize DA client to access a digital asset | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑250181 | |||
S3‑250152 | Conclusion for KI3 Security aspects of digital asset container in 5G | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S3‑250211 | |||
S3‑250153 | Conclusion for KI4 Authentication and authorization of digital representation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S3‑250215 | |||
S3‑250178 | Update Sol3 Authorization supporting spatial localization service with CCF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑250147 | |||
S3‑250179 | Update Sol5 Privacy protection during metaverse service discovery | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑250148 | |||
S3‑250180 | Update Sol8 authenticate and authorize DA client to create a digital asset | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑250150 | |||
S3‑250181 | Update Sol9 authenticate and authorize DA client to access a digital asset | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑250151 | |||
S3‑250190 | [TR 33.721] Update to solution#6 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑250088 | |||
S3‑250211 | Conclusion for KI#3 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑250034 | |||
S3‑250213 | 33.721: Evaluation of Solution 10 | Xiaomi EV Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑250112 | |||
S3‑250214 | 33.721: Update to Conclusion on Key Issue #2 | Xiaomi EV Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑250113 | |||
S3‑250215 | 33.721: Conclusion on Key Issue #4 | Xiaomi EV Technology, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑250114 | |||
S3‑250234 | Draft TR 33.721 v0.6.0 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.19 | Study on security aspects of CAPIF Phase 3 | S3‑250017 | KI#1.1-Further conclusions on ROF authentication | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑250182 | |
S3‑250018 | KI#1.2-Further conclusions on authorization information | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑250182 | |||
S3‑250019 | KI#1.3-Further conclusions on granularity | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑250222 | |||
S3‑250020 | remove EN for KI#1.1 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250021 | remove EN for KI#1.2 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250022 | remove EN in clause 6.4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑250212 | |||
S3‑250023 | editorial corrections in clauses 6.2 and 6.10 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑250216 | |||
S3‑250035 | Update to the conclusion for KI#1.2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑250182 | |||
S3‑250036 | Update to the conclusion for KI#2 | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑250189 | |||
S3‑250037 | Updates to Solution#21 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑250187 | |||
S3‑250038 | Solution to address KI#6 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑250191 | |||
S3‑250039 | Conclusion for KI#2 | China Telecom | pCR | Approval | Yes |
Yes
| merged | No | S3‑250189 | |||
S3‑250040 | Update sol#17 to resolve EN | China Telecom | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑250053 | Conclusion on key issue #1.2 in TR 33.700-22 | China Telecom | pCR | Approval | Yes |
Yes
| merged | No | S3‑250182 | |||
S3‑250086 | Update to solution#27 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑250188 | |||
S3‑250087 | Updates to conclusion for key issue#2 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑250189 | |||
S3‑250096 | New solution for Authorization of API invoker on one UE accessing resources related to another UE | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑250198 | |||
S3‑250097 | Resolving EN in key issue #1.2 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250098 | Resolving ENs and evaluation of solution #11 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑250199 | |||
S3‑250099 | Resolving ENs and evaluation of solution #22 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑250200 | |||
S3‑250100 | Resolving ENs and evaluation of solution #26 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑250201 | |||
S3‑250101 | Conclusion reformulation for key issue #1.2 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑250196 | |||
S3‑250102 | Further conclusion for key issue #1.1 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑250182 | |||
S3‑250103 | Further conclusion for key issue #1.2 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑250196 | |||
S3‑250104 | Further conclusion for key issue #1.3 | Ericsson | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑250105 | Further conclusion for key issue #2 | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑250189 | |||
S3‑250106 | Conclusion for key issue #3 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑250197 | |||
S3‑250107 | Conclusion for key issue #4 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250108 | Conclusion for key issue #5 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250109 | Conclusion for key issue #6 | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250115 | Draft CR on TS 33.122 | Xiaomi communications | draftCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑250116 | TR 33.700-22KI#1.1 conclusion update | Xiaomi communications | pCR | Approval | Yes |
Yes
| merged | No | S3‑250182 | |||
S3‑250117 | TR 33.700-22KI#1.2 conclusion update | Xiaomi communications | pCR | Approval | Yes |
Yes
| merged | No | S3‑250196 | |||
S3‑250118 | TR 33.700-22KI#1.3 conclusion update | Xiaomi communications | pCR | Approval | Yes |
Yes
| merged | No | S3‑250222 | |||
S3‑250119 | TR 33.700-22KI#2 conclusion update | Xiaomi communications | pCR | Approval | Yes |
Yes
| merged | No | S3‑250189 | |||
S3‑250160 | KI1.1 ROF authentication conclusion | Nokia | pCR | Yes |
Yes
| merged | No | S3‑250182 | ||||
S3‑250161 | KI1.1 ROF authentication | Nokia | pCR | Yes |
Yes
| approved | No | |||||
S3‑250162 | KI1.1 Solution 3 update | Nokia | pCR | Yes |
Yes
| approved | No | |||||
S3‑250163 | KI1.2 EN resolution in solution 7 | Nokia | pCR | Yes |
Yes
| approved | No | |||||
S3‑250164 | KI1.3 conclusion | Nokia | pCR | Yes |
Yes
| revised | No | S3‑250222 | ||||
S3‑250165 | KI2 interconnect conclusion | Nokia | pCR | Yes |
Yes
| merged | No | S3‑250189 | ||||
S3‑250166 | KI3 conclusion | Nokia | pCR | Yes |
Yes
| merged | No | S3‑250197 | ||||
S3‑250167 | KI4 Nested API invocation conclusion | Nokia | pCR | Yes |
Yes
| noted | No | |||||
S3‑250168 | KI5 muliple API infovoker same RO conclusion | Nokia | pCR | Yes |
Yes
| noted | No | |||||
S3‑250169 | TR correction | Nokia | pCR | Yes |
Yes
| merged | No | S3‑250216 | ||||
S3‑250182 | KI#1.1-Further conclusions on ROF authentication | Huawei, HiSilicon, Ericsson, Xiaomi, Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑250017 | |||
S3‑250187 | Updates to Solution#21 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑250037 | |||
S3‑250188 | Update to solution#27 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑250086 | |||
S3‑250189 | Updates to conclusion for key issue#2 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑250087 | |||
S3‑250191 | Solution to address KI#6 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑250038 | |||
S3‑250196 | Further conclusion for key issue #1.2 | Ericsson, Huawei, HiSilicon, ZTE Corporation, China Telecom, Xiaomi communications, Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑250103 | |||
S3‑250197 | Conclusion for key issue #3 | Ericsson, Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑250106 | |||
S3‑250198 | New solution for Authorization of API invoker on one UE accessing resources related to another UE | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑250096 | |||
S3‑250199 | Resolving ENs and evaluation of solution #11 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑250098 | |||
S3‑250200 | Resolving ENs and evaluation of solution #22 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑250099 | |||
S3‑250201 | Resolving ENs and evaluation of solution #26 | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑250100 | |||
S3‑250212 | remove EN in clause 6.4 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑250022 | |||
S3‑250216 | editorial corrections in clauses 6.2 and 6.10 | Huawei, HiSilicon, Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑250023 | |||
S3‑250222 | KI1.3 conclusion | Nokia, Huawei, HiSilicon, Xiaomi | pCR | Yes |
Yes
| noted | No | S3‑250164 | ||||
S3‑250235 | Study on security aspects of CAPIF Phase3 | Ericsson LM | draft TR | Approval | Yes |
Yes
| revised | No | S3‑250236 | |||
S3‑250236 | Study on security aspects of CAPIF Phase3 | Ericsson LM | draft TR | Approval | Yes |
Yes
| approved | No | S3‑250235 | |||
6 | New Study/Work item proposals |   | ||||||||||
7 | CVD and research |   | ||||||||||
8 | Any Other Business |   |