Tdoc List
2024-05-03 14:52
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Agenda and Meeting Objectives | S3‑241100 | Agenda | SA WG3 Chair | agenda | Yes |
Yes
| approved | No | |||
S3‑241101 | Process for SA3#115adHoc-e | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
S3‑241102 | Detail agenda planning for SA3#115AdHoc-e | SA WG3 Chair | other | Yes |
Yes
| noted | No | |||||
2 | Meeting Reports | S3‑241656 | Chair notes | SA3 WG Chair | report | Information | Yes |
No
| available | No | ||
3 | Reports and Liaisons from other Groups (selected LS corresponding to topics in the agenda) | S3‑241393 | LS to CT on IANA reservation on Security vulnerability fix for use of AES-GCM and AES-GMAC in 33.203 | Apple | LS out | Yes |
Yes
| withdrawn | Yes | |||
S3‑241484 | LS on vulnerability due to null ciphering request by network | Google Inc. | LS out | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑241495 | Reply LS on request to change integrity algorithm of 256-NIA3 / 256-NCA3 | ETSI SAGE | LS in | Discussion | Yes |
Yes
| noted | No | ||||
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 (Only contributions to resolve the model sharing will be treated). | S3‑241313 | Discussion paper for authorization of AIML model sharing | Huawei, HiSilicon | discussion | Discussion | Yes |
Yes
| noted | No | ||
S3‑241314 | Update procedure for secured and authorized AI/ML model sharing | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, vivo, Intel | CR | Approval | Yes |
Yes
| merged | No | S3‑241501 | |||
S3‑241361 | Discussion of "Update procedure for secured and authorized AI/ML model sharing" | Ericsson | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S3‑241363 | Update procedure for secured and authorized AI/ML model sharing | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S3‑241501 | |||
S3‑241369 | Authorization of NWDAF MTLF to request FL process on behalf of AnLF | Nokia | CR | Agreement | Yes |
Yes
| revised | No | S3‑241562 | |||
S3‑241498 | LS on Security of ML model sharing | vivo Wisdom Technology | LS out | No |
Yes
| revised | No | S3‑241635 | ||||
S3‑241501 | Update procedure for secured and authorized AI/ML model sharing | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, vivo, Intel | CR | Agreement | Yes |
Yes
| agreed | No | S3‑241363 | |||
S3‑241562 | Authorization of NWDAF MTLF to request FL process on behalf of AnLF | Nokia, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S3‑241369 | |||
S3‑241635 | LS on Security of ML model sharing | vivo Wisdom Technology | LS out | Yes |
Yes
| revised | No | S3‑241649 | S3‑241498 | |||
S3‑241649 | LS on Security of ML model sharing | vivo | LS out | Yes |
Yes
| approved | No | S3‑241498 | ||||
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 | S3‑241109 | [33.180] MC migration service authentication and authorization | Motorola Solutions | CR | Approval | Yes |
Yes
| not pursued | No | ||
4.7 | WID on Addition of Milenage-256 algorithm |   | ||||||||||
4.8 | WID on 3GPP profiles for cryptographic algorithms and security protocols | S3‑241107 | Living document for CryptoSP: draftCR to TS 33.210, Updates to cryprographic profiles | Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S3‑241499 | |
S3‑241108 | Living document for CryptoSP: draftCR to TS 33.501, Updates to cryptographic profiles | Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S3‑241500 | |||
S3‑241277 | Updates to the 3GPP TLS profile | Ericsson | other | Approval | Yes |
Yes
| revised | No | S3‑241521 | |||
S3‑241298 | Updates to TLS protocol profiles | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑241305 | update to the Profiling for TLS 1.3 | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑241633 | |||
S3‑241347 | Updates for deprecation of TLS1.0 and TLS1.1 | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑241278 | Clarification that 64-bit random IVs are forbidden in ESP | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑241279 | Implicit Initialization Vector (IV) for Counter-Based Ciphers in ESP | Ericsson | other | Approval | Yes |
Yes
| approved | No | ||||
S3‑241296 | Updates to Profiling of IPsec | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑241306 | Update to IKEv2 authentication | Huawei, HiSilicon | draftCR | Approval | Yes |
Yes
| merged | No | S3‑241508 | |||
S3‑241280 | Correcting terminologies related to DTLS over SCTP | Ericsson | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑241281 | Clarifying vulnerabilities in DTLS over SCTP | Ericsson | other | Approval | Yes |
Yes
| revised | No | S3‑241523 | |||
S3‑241299 | Updates related to references | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S3‑241319 | Updating Obsolete RFC 2252 by RFC 4510 | Huawei, HiSilicon | other | Approval | Yes |
Yes
| merged | No | S3‑241508 | |||
S3‑241438 | Clarifications of privacy options for EAP-TLS | Ericsson LM | other | Approval | Yes |
Yes
| noted | No | ||||
S3‑241487 | Discussion on working procedure for WID on 3GPP profiles for cryptographic algorithms and security protocols | NTT DOCOMO INC. | discussion | Endorsement | Yes |
Yes
| revised | No | S3‑241557 | |||
S3‑241499 | Living document for CryptoSP: draftCR to TS 33.210, Updates to cryprographic profiles | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | S3‑241107 | |||
S3‑241500 | Living document for CryptoSP: draftCR to TS 33.501, Updates to cryptographic profiles | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | S3‑241108 | |||
S3‑241508 | Living document for CryptoSP: draftCR to TS 33.310, Updates to cryptographic profiles | Ericsson Telecomunicazioni SpA | draftCR | Yes |
Yes
| approved | No | |||||
S3‑241521 | Updates to the 3GPP TLS profile | Ericsson | other | Approval | Yes |
Yes
| approved | No | S3‑241277 | |||
S3‑241523 | Clarifying vulnerabilities in DTLS over SCTP | Ericsson | other | Approval | Yes |
Yes
| approved | No | S3‑241281 | |||
S3‑241557 | Discussion on working procedure for WID on 3GPP profiles for cryptographic algorithms and security protocols | NTT DOCOMO INC. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S3‑241487 | |||
S3‑241633 | update to the Profiling for TLS 1.3 | Huawei, HiSilicon | other | Approval | Yes |
Yes
| approved | No | S3‑241305 | |||
4.9 | WID on security aspects of the 5GMSG Service phase 3 | S3‑241230 | Authentication and Authorization in bulk registration scenarios | China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | ||
S3‑241532 | Living document of security aspects of MSGin5G service Ph3 | China Mobile | draftCR | Approval | Yes |
Yes
| approved | No | ||||
4.10 | R19 SCAS WID |   | ||||||||||
5 | Rel-19 Studies |   | ||||||||||
5.1 | Study on enablers for Zero Trust Security | S3‑241341 | Discussion on the exposure of security related data | Huawei, HiSilicon | discussion | Discussion | Yes |
Yes
| noted | No | ||
S3‑241141 | Resolving EN on data exposure | Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| merged | No | S3‑241527 | |||
S3‑241140 | Resolving EN on dynamic security policy enforcement | Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| merged | No | S3‑241527 | |||
S3‑241425 | Update of the security assumptions | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑241527 | |||
S3‑241139 | Updates to Malformed Message Usecase | Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑241570 | |||
S3‑241339 | Evaluation for the use case on malformed messages | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241570 | |||
S3‑241426 | Update on malformed messages in the 5G SBA | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑241570 | |||
S3‑241138 | Updates to Massive number of SBI messages | Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| revised | No | S3‑241568 | |||
S3‑241340 | Evaluation for the use case on number of messages | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241568 | |||
S3‑241154 | Resolve EN and provide updates to use case 3 | MITRE Corporation, US NSA, Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑241537 | |||
S3‑241155 | Resolve EN and provide updates to use case 4 | MITRE Corporation, US NSA, Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑241538 | |||
S3‑241103 | New use case for security evaluation and monitoring: NFV vulnerabilities | Dell Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241104 | New use case for security evaluation and monitoring: API security risks | Dell Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241105 | New use case for security evaluation and monitoring: Man-in-the-Middle (MitM) attacks | Dell Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241106 | New use case for security evaluation and monitoring: Identity spoofing and impersonation (Aka Rogue Elements) | Dell Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241156 | Abnormal SBI Call Flow | US National Security Agency, MITRE Corporation, OTD_US | pCR | Approval | Yes |
Yes
| revised | No | S3‑241604 | |||
S3‑241320 | Data related to failed audience claim in the access token | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241537 | |||
S3‑241137 | Updates to Access control decision enhancement usecase | Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241136 | Updates to KI#1 | Lenovo, Nokia, Nokia Shanghai Bell, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| merged | No | S3‑241525 | |||
S3‑241423 | Adding requirements to KI#1 "Data exposure for security evaluation and monitoring" | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑241525 | |||
S3‑241135 | New KI on dynamic security policy enforcement | Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| merged | No | S3‑241526 | |||
S3‑241424 | Adding Key Issue on WT2 "Security mechanism for dynamic policy enforcement" | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑241526 | |||
S3‑241445 | New Key Issue on data exposure relevant for network level attacks | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241437 | New Solution for Key Issue 1 | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241421 | LS on security data management for continuous security monitoring | Nokia | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑241134 | FS_eZTS Offline Call#3 Minutes | Lenovo, Motorola Mobility | report | Information | Yes |
Yes
| noted | No | ||||
S3‑241525 | Adding requirements to KI#1 "Data exposure for security evaluation and monitoring" | Ericsson, Lenovo, Nokia, Nokia Shanghai Bell, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑241423 | |||
S3‑241526 | Adding Key Issue on WT2 "Security mechanism for dynamic policy enforcement" | Ericsson, Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑241424 | |||
S3‑241527 | Update of the security assumptions | Ericsson, Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility | pCR | Approval | Yes |
Yes
| approved | No | S3‑241425 | |||
S3‑241537 | Resolve EN and provide updates to use case 3 | MITRE Corporation, US NSA, Lenovo, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241154 | |||
S3‑241538 | Resolve EN and provide updates to use case 4 | MITRE Corporation, US NSA, Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑241155 | |||
S3‑241568 | Updates to Massive number of SBI messages | Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241138 | |||
S3‑241570 | Updates to Malformed Message Usecase | Lenovo, MITRE Corporation, OTD_US, Johns Hopkins APL, Motorola Mobility, Ericsson, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241139 | |||
S3‑241604 | Abnormal SBI Call Flow | US National Security Agency, MITRE Corporation, OTD_US | pCR | Approval | Yes |
Yes
| approved | No | S3‑241156 | |||
S3‑241638 | Draft TR 33.794 | Lenovo, Motorola Mobility | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.2 | Study on the security support for the Next Generation Real Time Communication services phase 2 | S3‑241208 | update the scope of TR 33.790 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S3‑241531 | |
S3‑241231 | Updated Scope of NGRTC_Ph2_Sec | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241531 | |||
S3‑241428 | Update of the scope clause | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑241531 | |||
S3‑241209 | new key issue on IMS DC capability exposure | Nokia, Nokia Shanghai Bell, CableLabs | pCR | Approval | Yes |
Yes
| merged | No | S3‑241528 | |||
S3‑241227 | New Key Issue on security aspects of IMS DC capability exposure | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241528 | |||
S3‑241210 | new key issue on authenticity of DC application | Nokia, Nokia Shanghai Bell, CableLabs, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241211 | new sol for KI#1 third_party_id | Nokia, Nokia Shanghai Bell, CableLabs | pCR | Approval | Yes |
Yes
| revised | No | S3‑241605 | |||
S3‑241427 | New solution for the security of 3rd party specific identities | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑241529 | |||
S3‑241434 | Solution for third party identity authorisation and verification | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑241520 | |||
S3‑241212 | new sol for KI#2 Security of IMS based Avatar Communication | Nokia, Nokia Shanghai Bell, CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241213 | new sol for KI on IMS DC capability exposure | Nokia, Nokia Shanghai Bell, CableLabs | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241520 | Solution for third party identity authorisation and verification | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑241434 | |||
S3‑241528 | New Key Issue on security aspects of IMS DC capability exposure | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑241227 | |||
S3‑241529 | New solution for the security of 3rd party specific identities | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑241427 | |||
S3‑241531 | Updated Scope of NGRTC_Ph2_Sec | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑241231 | |||
S3‑241605 | new sol for KI#1 third_party_id | Nokia, Nokia Shanghai Bell, CableLabs | pCR | Approval | Yes |
Yes
| approved | No | S3‑241211 | |||
S3‑241637 | Draft TR 33.790 v0.2.0 Study on the security support for the next generation real time communication services phase 2 | Ericsson Limited | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.3 | Study on security for PLMN hosting a NPN | S3‑241159 | Remove the EN for interface between customer’s AFs and 5G core network | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑241610 | |
S3‑241160 | Remove the EN for management interface | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241550 | |||
S3‑241265 | Resolution of EN concerning including OAM attacks in the study | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑241550 | |||
S3‑241247 | Solve EN of TR 33.757 | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241266 | Resolution EN concerning DoS attack | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241244 | New solution for KI#1 of TR 33.757 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241640 | |||
S3‑241255 | New solution to KI#1- CIWF for N4 interface | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S3‑241596 | |||
S3‑241219 | A new solution on protecting the Hosted NPN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241613 | |||
S3‑241223 | Solution on the security protection to avoid UE information disclosure | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241617 | |||
S3‑241245 | New solution for KI#2 of TR 33.757 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241641 | |||
S3‑241258 | New solution to KI#2- CIWF as a gateway for SBA interface | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S3‑241597 | |||
S3‑241267 | New solution to KI#2- CIWF as an delegate for SBA interface | China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S3‑241598 | |||
S3‑241474 | KI#2 New solution for service and information authorization | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑241560 | |||
S3‑241402 | Solution on NF Authorization in PLMN hosting NPN Scenario | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241403 | Solution for DNS Security in PLMN hosting NPN Scenario | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑241579 | |||
S3‑241475 | KI#2 New solution for topology hiding | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑241561 | |||
S3‑241115 | New solution on SUPI privacy issue in PLMN hosting NPN Scenario | IIT Delhi, IIT Bhilai | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241142 | Solution to address KI#3 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑241571 | |||
S3‑241158 | New solution for SUPI privacy issue | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241246 | New solution for KI#3 of TR 33.757 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241642 | |||
S3‑241404 | Solution for SUPI privacy protection in PLMN hosted NPN scenario | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241157 | Clean up for TR 33.757 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241161 | Add some context for clause 5 | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241550 | Resolution of EN concerning including OAM attacks in the study | Nokia, Nokia Shanghai Bell, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S3‑241265 | |||
S3‑241560 | KI#2 New solution for service and information authorization | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑241474 | |||
S3‑241561 | KI#2 New solution for topology hiding | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑241475 | |||
S3‑241571 | Solution to address KI#3 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑241142 | |||
S3‑241579 | Solution for DNS Security in PLMN hosting NPN Scenario | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241403 | |||
S3‑241592 | New solution to KI#1- CIWF for N4 interface | China Telecommunications | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑241593 | New solution to KI#2- CIWF as a gateway for SBA interface | China Telecommunications | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑241594 | New solution to KI#2- CIWF as an delegate for SBA interface | China Telecommunications | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑241595 | Draft TR 33.757 v0.2.0 | China Telecommunications | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241596 | New solution to KI#1- CIWF for N4 interface | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S3‑241255 | |||
S3‑241597 | New solution to KI#2- CIWF as a gateway for SBA interface | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S3‑241258 | |||
S3‑241598 | New solution to KI#2- CIWF as an delegate for SBA interface | China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S3‑241267 | |||
S3‑241610 | Remove the EN for interface between customer’s AFs and 5G core network | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑241159 | |||
S3‑241611 | Remove the EN for interface between customer’s AFs and 5G core network | ZTE Corporation | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑241612 | Remove the EN for interface between customer’s AFs and 5G core network | ZTE Corporation | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑241613 | A new solution on protecting the Hosted NPN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241219 | |||
S3‑241617 | Solution on the security protection to avoid UE information disclosure | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241223 | |||
S3‑241640 | New solution for key issue 1 | China mobile | pCR | Yes |
Yes
| approved | No | S3‑241244 | ||||
S3‑241641 | New solution for key issue 2 | China mobile | pCR | Yes |
Yes
| approved | No | S3‑241245 | ||||
S3‑241642 | New solution for key issue 3 | China mobile | pCR | Yes |
Yes
| approved | No | S3‑241246 | ||||
5.4 | Study of ACME for Automated Certificate Management in SBA | S3‑241315 | Assumption for use of ACME in 3GPP network | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241600 | |
S3‑241133 | New Key Issue on supporting all 5G SBA certificate types | Google Inc., Charter Communications, US National Security Agency, Cisco Systems | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241149 | New key issue on certificate revocation | Johns Hopkins University APL, Cisco Systems | pCR | Approval | Yes |
Yes
| revised | No | S3‑241650 | |||
S3‑241382 | Addtional limitation in KI#3 on DNS challenge | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241383 | new solution using NF FQDN as ACME identifier | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241384 | new solution using NF instance ID as ACME identifier | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241539 | |||
S3‑241257 | Solution proposal for ACME challenge validation | Cisco Systems | pCR | Approval | Yes |
Yes
| revised | No | S3‑241534 | |||
S3‑241385 | new solution for client-side certificate | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241147 | New Key Issue on supporting all 5G SBA certificate types | Google Inc. | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑241534 | Solution proposal for ACME challenge validation | Cisco Systems, Google | pCR | Approval | Yes |
Yes
| approved | No | S3‑241257 | |||
S3‑241535 | Additional limitation in KI#3 on DNS challenge | Huawei, HiSilicon | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑241536 | Draft TR 33.776 | Cisco Systems | draft TR | Approval | Yes |
Yes
| approved | No | S3‑240982 | |||
S3‑241539 | new solution using NF instance ID as ACME identifier | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241384 | |||
S3‑241600 | Assumption for use of ACME in 3GPP network | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241315 | |||
S3‑241650 | New key issue on certificate revocation | Johns Hopkins University APL, Cisco Systems, Google Inc. | pCR | Approval | Yes |
Yes
| approved | No | S3‑241149 | |||
5.5 | Study on enabling a cryptographic algorithm transition to 256-bits | S3‑241190 | new kew issue on backward compatibility | CableLabs, Charter Communications | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑241276 | Architecture Assumptions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241286 | UE States and Transitions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241116 | New Key Issue on permanent secret key length (K) | KDDI Corporation, Samsung, Xiaomi | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241170 | New Key Issue on authentication parameters in AKA procedure | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241466 | New KI on AKA related 256-bit algorithm update | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241480 | KI on key hiearchy | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241117 | New Key Issue on different cryptographic key lengths in dual connectivity scenarios | KDDI Corporation, CMCC | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241118 | New Key Issue on algorithm negotiation on re-establishing RRC connection | KDDI Corporation, CMCC | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241181 | New key issue on algorithm negotiation for 256-bit algorithms | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241275 | Adaptations to AS and NAS Procedures | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241310 | key issues on introducing 256-bit algorithm in 5GS | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241316 | New Key Issue on different cryptographic key lengths in URLLC scenario | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241359 | Add KI on 256 bits algorithms selection in 5G system | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241390 | New key issue on specifying usage of new encryption and integrity protection algorithms in the 5G system | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241467 | New KI on negotiation for NAS and AS related 256-bit algorithms | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241394 | CAT256 - New KI for CAT_256 on correctly indication | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑241396 | CAT256 - New KI for CAT_256 on Flexibility to adjust the preference on security algorithms | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑241171 | New Key Issue on different length of cryptographic key in EPS and 5GS interworking | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241288 | Introduction of AEAD Algorithm for Air-link Data Protection | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241289 | Introduction of AEAD Algorithm and the Order of Data Protection | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241291 | Discussion on AEAD Properties | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑241172 | New Solution on different length of cryptographic key in EPS and 5GS interworking | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241362 | Add sol on 256 bits algorithm selection in 5G system | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241391 | New solution for specifying usage of new encryption and integrity protection algorithms in the 5G system | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241395 | CAT256 - New solution for CAT_256 on correctly indication | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑241397 | CAT256 - New solution for CAT_256 on Flexibility to adjust the preference on security algorithms | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑241481 | Solution on Key Hierarchy | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241377 | Conclusion on 256 bits algorithms selection in 5G system KI | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241482 | Conclusion on Key Hierarchy KI | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241504 | Draft TR 33.700-41 | KDDI Corporation | draft TR | No |
Yes
| withdrawn | Yes | |||||
5.6 | Study on mitigations against bidding down attacks | S3‑241344 | New key issue on guidance for legacy devices | Huawei, HiSilicon | other | Approval | Yes |
Yes
| revised | No | S3‑241516 | |
S3‑241398 | MiBiDA - New solution for mitigating bidding down attack | Apple | pCR | Yes |
Yes
| revised | No | S3‑241552 | ||||
S3‑241405 | Solution to prevent GERAN/UTRAN bidding down attack | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑241580 | |||
S3‑241439 | New Solution for Key Issue 1 | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S3‑241559 | |||
S3‑241469 | New solution for mitigating GERAN UTRAN bidding down attack | Xiaomi communications | pCR | Approval | Yes |
Yes
| revised | No | S3‑241555 | |||
S3‑241483 | Solution to KI#1 on Bidding down mitigation | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑241574 | |||
S3‑241182 | New solution on Reuse SoR procedure for bidding down attack mitigation | vivo | pCR | Approval | Yes |
Yes
| revised | No | S3‑241634 | |||
S3‑241173 | New Solution for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑241578 | |||
S3‑241338 | Solution for configured operator indication | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241601 | |||
S3‑241342 | Solution for registration-based provisioning of list of decommissioned systems | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241524 | |||
S3‑241343 | Solution for UPU-based provisioning of list of decommissioned systems | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241533 | |||
S3‑241513 | New draft TR 33.701 | Huawei Technologies Sweden AB | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241516 | New key issue on guidance for legacy devices | Huawei, HiSilicon | other | Approval | Yes |
Yes
| approved | No | S3‑241344 | |||
S3‑241524 | Solution for registration-based provisioning of list of decommissioned systems | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241342 | |||
S3‑241533 | Solution for UPU-based provisioning of list of decommissioned systems | Huawei, HiSilicon, Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑241343 | |||
S3‑241552 | MiBiDA - New solution for mitigating bidding down attack | Apple | pCR | Yes |
Yes
| approved | No | S3‑241398 | ||||
S3‑241555 | New solution for mitigating GERAN UTRAN bidding down attack | Xiaomi communications | pCR | Approval | Yes |
Yes
| approved | No | S3‑241469 | |||
S3‑241559 | New Solution for Key Issue 1 | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑241439 | |||
S3‑241574 | Solution to KI#1 on Bidding down mitigation | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑241483 | |||
S3‑241578 | New Solution for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑241173 | |||
S3‑241580 | Solution to prevent GERAN/UTRAN bidding down attack | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241405 | |||
S3‑241601 | Solution for configured operator indication | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241338 | |||
S3‑241634 | New solution on Reuse SoR procedure for bidding down attack mitigation | vivo | pCR | Approval | Yes |
Yes
| approved | No | S3‑241182 | |||
5.7 | Study on security Aspects of 5G Satellite Access Phase 2 | S3‑241307 | Addressing the editor's note on the security assumption | Huawei, HiSilicon, Interdigital, Ericsson, Nokia, Nokia Shanghai Bell, Intel, CATT, Xiaomi, China Telecom | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑241268 | Update KI#1 of TR 33.700-29 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑241583 | |||
S3‑241308 | Addressing the editor's note in the key issue on store and forward Satellite Operation | Huawei, HiSilicon, Interdigital, Ericsson, Nokia, Nokia Shanghai Bell, Intel, Xiaomi, China Telecom | pCR | Approval | Yes |
Yes
| revised | No | S3‑241606 | |||
S3‑241325 | Update to the Store and forward KI | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241352 | pCR to TR33.700-29 Update key issue#1 | CATT | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241162 | New Solution for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S3‑241609 | |||
S3‑241207 | Secure Initial Registration for S&F Satellite Operation | Intel | pCR | Yes |
Yes
| revised | No | S3‑241589 | ||||
S3‑241222 | Solution on the authorization mechanism for uplink NAS message in S&F Satellite Operation | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241616 | |||
S3‑241228 | New solution of onboard UDM | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241530 | |||
S3‑241295 | Solution for Authentication for Store and Forward Satellite Operation | OPPO Beijing | pCR | Approval | Yes |
Yes
| revised | No | S3‑241607 | |||
S3‑241463 | New solution on attach procedure with eNB on board the satellite in TR 33.700-29 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑241627 | |||
S3‑241464 | New solution on authorization method during S&F MO transmission in TR 33.700-29 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑241628 | |||
S3‑241465 | New solution on attach procedure with MME on board the satellite in TR 33.700-29 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑241629 | |||
S3‑241485 | New solution for Key Issue #1 | THALES | pCR | Approval | Yes |
Yes
| revised | No | S3‑241505 | |||
S3‑241486 | New solution based on IOPS for Key Issue #1 | THALES | pCR | Approval | Yes |
Yes
| revised | No | S3‑241506 | |||
S3‑241488 | Solution on store and forward Satellite Operation | Lenovo | pCR | Yes |
Yes
| revised | No | S3‑241519 | ||||
S3‑241309 | solution on the security protection for store and forward Satellite Operation | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241623 | |||
S3‑241348 | pCR to TR33.700-29 New solution UE Attach or Registration method for S&F operation | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑241602 | |||
S3‑241350 | pCR to TR33.700-29 New solution UE context management for S&F operation | CATT | pCR | Approval | Yes |
Yes
| revised | No | S3‑241603 | |||
S3‑241406 | Solution for optimization of authentication procedure in S&F operation | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑241581 | |||
S3‑241407 | New solution on preventing DoS attacks in S&F operation | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑241582 | |||
S3‑241433 | IOPs based solution for S&F between the UE and satellite | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑241518 | |||
S3‑241440 | New Solution : Primary authentication and NAS security context establishment during store-and-forward operations | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S3‑241563 | |||
S3‑241408 | Key issue on privacy attacks in S&F operatio | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑241583 | |||
S3‑241441 | Key issue on security and privacy aspects of emergency reporting during S&F operations | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241259 | Key issue on Security for UE-Satellite-UE communication | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241443 | New KI : Privacy aspects of UE-satellite-UE communication | Nokia, Philips International B.V., Lenovo, InterDigital | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241444 | New KI - UE-satellite-UE communication security | Philips International B.V., Nokia, Lenovo, InterDigital | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241489 | Solution on UE-satellite-UE communication security | Lenovo | pCR | Yes |
Yes
| noted | No | |||||
S3‑241183 | New solution on mitigation of privacy issues of interim GUTI | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241505 | New solution for Key Issue #1 | THALES | pCR | Approval | Yes |
Yes
| approved | No | S3‑241485 | |||
S3‑241506 | New solution based on IOPS for Key Issue #1 | THALES | pCR | Approval | Yes |
Yes
| approved | No | S3‑241486 | |||
S3‑241518 | IOPs based solution for S&F between the UE and satellite | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑241433 | |||
S3‑241519 | Solution on store and forward Satellite Operation | Lenovo | pCR | Yes |
Yes
| approved | No | S3‑241488 | ||||
S3‑241530 | New solution of onboard UDM | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑241228 | |||
S3‑241563 | New Solution : Primary authentication and NAS security context establishment during store-and-forward operations | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑241440 | |||
S3‑241567 | LS to SA2 and RAN2 on selected satellite architecture for Store and Forward | InterDigital, Inc. | LS out | Approval | Yes |
Yes
| approved | No | S3‑241496 | |||
S3‑241575 | Draft TR 33.700-29 | CATT | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241581 | Solution for optimization of authentication procedure in S&F operation | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241406 | |||
S3‑241582 | New solution on preventing DoS attacks in S&F operation | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241407 | |||
S3‑241583 | Key issue on privacy attacks in S&F operatio | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241408 | |||
S3‑241589 | Secure Initial Registration for S&F Satellite Operation | Intel | pCR | Yes |
Yes
| approved | No | S3‑241207 | ||||
S3‑241602 | pCR to TR33.700-29 New solution UE Attach or Registration method for S&F operation | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑241348 | |||
S3‑241603 | pCR to TR33.700-29 New solution UE context management for S&F operation | CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑241350 | |||
S3‑241606 | Addressing the editor's note in the key issue on store and forward Satellite Operation | Huawei, HiSilicon, Interdigital, Ericsson, Nokia, Nokia Shanghai Bell, Intel, Xiaomi, China Telecom | pCR | Approval | Yes |
Yes
| revised | No | S3‑241655 | S3‑241308 | ||
S3‑241607 | Solution for Authentication for Store and Forward Satellite Operation | OPPO Beijing | pCR | Approval | Yes |
Yes
| approved | No | S3‑241295 | |||
S3‑241609 | New Solution for KI#1 | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S3‑241162 | |||
S3‑241616 | Solution on the authorization mechanism for uplink NAS message in S&F Satellite Operation | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241222 | |||
S3‑241623 | Solution on the security protection for store and forward Satellite Operation | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241309 | |||
S3‑241627 | New solution on attach procedure with eNB on board the satellite in TR 33.700-29 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑241463 | |||
S3‑241628 | New solution on authorization method during S&F MO transmission in TR 33.700-29 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑241464 | |||
S3‑241629 | New solution on attach procedure with MME on board the satellite in TR 33.700-29 | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑241465 | |||
S3‑241655 | Addressing the editor's note in the key issue on store and forward Satellite Operation | HUAWEI TECH. GmbH | pCR | Approval | Yes |
Yes
| approved | No | S3‑241606 | |||
S3‑241496 | LS to SA2, RAN2, and RAN3 on selected satellite architecture for Store and Forward | Interdigital | LS out | Approval | No |
Yes
| revised | No | S3‑241567 | |||
5.8 | Study on security for mobility over non-3GPP access to avoid full primary authentication | S3‑241415 | Update on KI#1 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||
S3‑241416 | Update on KI#2 | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑241585 | |||
S3‑241417 | Update on KI#3 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241418 | Update on KI#4 | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241193 | Discussion paper on TNAP Mobility solutions | Nokia | discussion | Information | Yes |
Yes
| revised | No | S3‑241509 | |||
S3‑241145 | Discussion Paper on UE non-3GPP access Security re-establishment Considerations | Lenovo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241430 | Editorial corrections to solution #3 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241196 | solution for N5CW device | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S3‑241510 | |||
S3‑241146 | EAP-5G message alignment with TS 33.501 for Solution 1 and 2 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241194 | update on solution 1 | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241356 | New solution for KI#3 | LG Electronics | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241420 | New solution on N5CW device mobility solution with Nonce | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑241587 | |||
S3‑241144 | Updates to Solution 4 | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑241573 | |||
S3‑241143 | Solution for FBSS Adaptations to align with 5G architecture | Lenovo | pCR | Approval | Yes |
Yes
| revised | No | S3‑241572 | |||
S3‑241490 | Mobility of N5CW devices | Lenovo | pCR | Yes |
Yes
| revised | No | S3‑241522 | ||||
S3‑241357 | New solution for KI#2 | LG Electronics | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241192 | solution for AUN3 device | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241336 | Update Taks 2 in assumption clause | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241337 | Update assumption for NSWOF case by refering to the clasue in 33.501 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241419 | New solution on AUN3 device mobility solution with Nonce | Samsung | pCR | Approval | Yes |
Yes
| revised | No | S3‑241586 | |||
S3‑241148 | Solution for KI#4 UE authentication while connecting to a new WLAN AP through the same NSWOF | Charter Communications, Inc | pCR | Approval | Yes |
Yes
| revised | No | S3‑241653 | |||
S3‑241197 | solution for NSWO | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S3‑241511 | |||
S3‑241431 | Solution to KI#4 using FT | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| revised | No | S3‑241517 | |||
S3‑241198 | solution mapping | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241429 | Clarifications/corrections on linking solutions to key issues | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241432 | Proposed conclusion for key issue #4 | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241195 | Clean up | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241507 | TR 33.702 | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241509 | Discussion paper on TNAP Mobility solutions | Nokia | discussion | Endorsement | Yes |
Yes
| endorsed | No | S3‑241193 | |||
S3‑241510 | solution for N5CW device | Nokia, Lenovo, Charter, Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241196 | |||
S3‑241511 | solution for NSWO | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑241197 | |||
S3‑241517 | Solution to KI#4 using FT | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| approved | No | S3‑241431 | |||
S3‑241522 | Mobility of N5CW devices | Lenovo | pCR | Yes |
Yes
| approved | No | S3‑241490 | ||||
S3‑241572 | Solution for FBSS Adaptations to align with 5G architecture | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑241143 | |||
S3‑241573 | Updates to Solution 4 | Lenovo | pCR | Approval | Yes |
Yes
| approved | No | S3‑241144 | |||
S3‑241585 | Update on KI#2 | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241416 | |||
S3‑241586 | New solution on AUN3 device mobility solution with Nonce | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241419 | |||
S3‑241587 | New solution on N5CW device mobility solution with Nonce | Samsung | pCR | Approval | Yes |
Yes
| approved | No | S3‑241420 | |||
S3‑241653 | Solution for KI#4 UE authentication while connecting to a new WLAN AP through the same NSWOF | Charter Communications, Inc | pCR | Approval | Yes |
Yes
| approved | No | S3‑241148 | |||
5.9 | Study on security Aspect of Ambient IoT Services in 5G | S3‑241476 | Skeleton of TR 33.713 AIoT Security | OPPO | draft TR | Approval | Yes |
Yes
| approved | No | ||
S3‑241477 | Scope of TR 33.713 | OPPO, InterDigital | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241301 | Discussion on Security Aspects on Ambient IoT Service | Huawei, HiSilicon, China Unicom, China Telecom | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S3‑241163 | Add some context to security assumptions | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241353 | pCR to TR33.713 Clause 4 Security Architecture and Assumptions | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241375 | AIoT: Security architecture for Ambient Services in 5G network | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241376 | AIoT: Security assumptions for Ambient IoT services in 5G network | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241401 | AIoT - Security assumption for Ambient IoT | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑241459 | Security assumption of 5G Ambient IoT services | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241114 | New key issue for security procedure efficiency for AIoT device | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241153 | Key Issue on security mechanisms for AIoT system | Xidian University | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241354 | pCR to TR33.713 New key issue on security protection of Ambient IoT system | CATT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241478 | KI on Device Resource Limitation | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241479 | KI on Credential Management | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241112 | New key issue for AIoT device authentication and authorization | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241151 | New KI for TR 33.713 - Security | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241164 | KI for AIoT device authentication and authorization | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241264 | KI Authentication and identity of type A and B device | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241297 | KI on Protection of Information Transfer for AIoT Services | OPPO Beijing | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241282 | New key issue for connectivity authentication in Ambient IoT | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241283 | New key issue for application layer authentication in Ambient IoT | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241284 | New key issue for Authenticated and authorized access to devices in Ambient IoT via 3GPP core | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241303 | key issue on authentication for AIoT devices in network side | Huawei, HiSilicon, China Unicom, China Telecom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241399 | AIoT - New KI for Ambient IoT on Authentication | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑241460 | Key issue for authorization for 5G Ambient IoT services | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑241630 | |||
S3‑241304 | key issue on protection for the command and data transferring | Huawei, HiSilicon, China Unicom, China Telecom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241371 | AIoT: New key issue for Traffic protection of AF - NEF interface | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241372 | AIoT: New key issue for integrity protection of communication messages sent between AIoT device and 5G network | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241373 | AIoT: New key issue for encryption of communication messages sent between AIoT device and 5G network | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241374 | AIoT: New key issue for protection of the transfer of security capability of the AIoT device | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241400 | AIoT - New KI for Ambient IoT on communication security | Apple | pCR | Yes |
Yes
| noted | No | |||||
S3‑241435 | New Key Issue on the protection of information during AIoT service communication | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241113 | New key issue on AIoT device ID privacy | vivo | pCR | Approval | Yes |
Yes
| revised | No | S3‑241636 | |||
S3‑241150 | New KI for TR 33.713 - Privacy | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| merged | No | S3‑241636 | |||
S3‑241165 | KI for AIoT device ID privacy | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241636 | |||
S3‑241285 | New key issue for identity privacy in Ambient IoT | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑241636 | |||
S3‑241300 | Add KI on privacy protection for Ambient IoT device identifier | OPPO | pCR | Approval | Yes |
Yes
| merged | No | S3‑241636 | |||
S3‑241358 | pCR to TR33.713 New key issue on privacy protection of Ambient IoT system | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑241636 | |||
S3‑241436 | New Key Issue on the privacy of information about AIoT device during AIoT service communication | Qualcomm Incorporated | pCR | Approval | Yes |
Yes
| merged | No | S3‑241636 | |||
S3‑241462 | Key issue for security and privacy for Ambient IoT information transmission | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| merged | No | S3‑241636 | |||
S3‑241494 | AIoT device identifier privacy | Lenovo | pCR | Yes |
Yes
| merged | No | S3‑241636 | ||||
S3‑241302 | key issue on the protection for enable/disable device operation | Huawei, HiSilicon, Telecom Italia, China Unicom, China Telecom | pCR | Approval | Yes |
Yes
| revised | No | S3‑241622 | |||
S3‑241370 | AIoT: New key issue for disablingAIoT devices | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑241622 | |||
S3‑241461 | Key issue for disable device operation in 5G Ambient IoT services | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| merged | No | S3‑241622 | |||
S3‑241152 | New KI for TR 33.713 - DOS | InterDigital, Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241392 | Solution for AIoT Lightweight Authentication Based on 5G-AKA | OPPO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241622 | Key issue on the protection for enable/disable device operation | Huawei, HiSilicon, Telecom Italia, China Unicom, China Telecom, Interdigital, Ericsson, Nokia | pCR | Approval | Yes |
Yes
| approved | No | S3‑241302 | |||
S3‑241630 | Key issue for authorization for 5G Ambient IoT services | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑241460 | |||
S3‑241636 | New key issue on AIoT device ID privacy | vivo, Interdigital, ZTE, Ericsson, OPPO, CATT, Qualcomm, Xiaomi, Lenovo, Apple, Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑241113 | |||
S3‑241648 | Draft TR 33.713 v0.1.0 | OPPO | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.10 | SID on security aspects of Usage of User Identities | S3‑241121 | Draft TR 33.700-32 skeleton | InterDigital Belgium. LLC | draft TR | Approval | Yes |
Yes
| revised | No | S3‑241565 | |
S3‑241122 | TR 33.700-32 scope | InterDigital Belgium. LLC | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241124 | TR 33.700-32 security assumptions | InterDigital Belgium. LLC | pCR | Approval | Yes |
Yes
| revised | No | S3‑241514 | |||
S3‑241199 | Security Assumptions | Nokia | pCR | Approval | Yes |
Yes
| merged | No | S3‑241514 | |||
S3‑241232 | Architecture and Security Assumptions in TR 33.700-32 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑241514 | |||
S3‑241329 | New assumption on user ID case | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241514 | |||
S3‑241330 | New assumption on for non-3GPP device case | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241514 | |||
S3‑241447 | 33.700-32: Architecture and Security Assumptions | Xiaomi Technology | pCR | Approval | Yes |
Yes
| merged | No | S3‑241514 | |||
S3‑241327 | New definition: user ID and non-3GPP device ID | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241556 | |||
S3‑241328 | New definition: user authentication and non-3GPP device authentication | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241556 | |||
S3‑241446 | 33.700-32: Terms | Xiaomi Technology | pCR | Approval | Yes |
Yes
| merged | No | S3‑241556 | |||
S3‑241125 | TR 33.700-32 new KI authentication and authorization of human user | InterDigital Belgium. LLC, Nokia | pCR | Approval | Yes |
Yes
| revised | No | S3‑241515 | |||
S3‑241176 | KI on Authentication and Authorization of User Identifiers | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241515 | |||
S3‑241226 | New Key Issue of Authentication and Authorization of User ID | China Mobile | pCR | Approval | Yes |
Yes
| merged | No | S3‑241515 | |||
S3‑241386 | new key issue for user authentication and authorization | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241515 | |||
S3‑241411 | Key issue on User Authentication and Authorization | Samsung | pCR | Approval | Yes |
Yes
| merged | No | S3‑241515 | |||
S3‑241448 | 33.700-32: Key Issue on User Authentication and Authorization | Xiaomi Technology | pCR | Approval | Yes |
Yes
| merged | No | S3‑241515 | |||
S3‑241126 | TR 33.700-32 new KI authentication and authorization of non-3GPP device | InterDigital Belgium. LLC | pCR | Approval | Yes |
Yes
| merged | No | S3‑241566 | |||
S3‑241220 | Key issue #Y: Security of Authentication and Authorization of one or more non-3GPP devices behind one gateway UE or 5G-RG | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241566 | |||
S3‑241233 | Key Issue on authentication and authorization of non-3GPP device behind a UE or 5G-RG | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑241566 | |||
S3‑241127 | TR 33.700-32 new KI privacy of human user identifier | InterDigital Belgium. LLC, Nokia | pCR | Approval | Yes |
Yes
| merged | No | S3‑241543 | |||
S3‑241177 | KI on Privacy Protection of User Identity Profile | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241543 | |||
S3‑241387 | new key issue for user privacy protection | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241543 | |||
S3‑241450 | 33.700-32: Key Issue on User Privacy | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑241543 | |||
S3‑241449 | 33.700-32: Key Issue on Secure Credential Provisioning | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241493 | draft LS to SA2 on the definition of non-3GPP device identifier | Huawei, HiSilicon | LS out | Approval | Yes |
Yes
| noted | No | ||||
S3‑241331 | Propose a LS to SA2 about non-3GPP device identifier | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑241512 | Draft TR 33.700-32 skeleton | InterDigital Belgium. LLC | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑241514 | TR 33.700-32 security assumptions | InterDigital Belgium. LLC, Nokia, China Telecom, Huawei, HiSilicon, Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑241124 | |||
S3‑241515 | TR 33.700-32 new KI authentication and authorization of human user | InterDigital Belgium. LLC, Nokia, ZTE Corporation, China Mobile, Huawei, HiSilicon, Samsung, Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑241125 | |||
S3‑241543 | 33.700-32: Key Issue on User Privacy | Xiaomi, InterDigital, Nokia, ZTE, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241450 | |||
S3‑241545 | Draft TR 33.700-32 | InterDigital Belgium. LLC | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241556 | New definition: user ID and non-3GPP device ID | Huawei, HiSilicon, Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑241327 | |||
S3‑241565 | Draft TR 33.700-32 skeleton | InterDigital Belgium. LLC | draft TR | Approval | Yes |
Yes
| approved | No | S3‑241121 | |||
S3‑241566 | Key issue #Y: Security of Authentication and Authorization of one or more non-3GPP devices behind one gateway UE or 5G-RG | Huawei, HiSilicon, , InterDigital, China Telecom, Charter | pCR | Approval | Yes |
Yes
| approved | No | S3‑241220 | |||
S3‑241614 | Key issue #Y: Security of Authentication and Authorization of one or more non-3GPP devices behind one gateway UE or 5G-RG | Huawei, HiSilicon | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
5.11 | R19 SID on UAS security enhancement | S3‑241224 | Draft TR 33.759 skeleton (UAS) | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||
S3‑241379 | Overview and Security Assumption | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241540 | |||
S3‑241254 | Overview of Uncrewed Aerial Systems (UAS) | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑241540 | |||
S3‑241269 | Scope of TR 33.759 | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S3‑241502 | |||
S3‑241378 | Scope of TR 33.759 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241502 | |||
S3‑241380 | new key issue for security enhancements to NEF | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241551 | |||
S3‑241381 | new key issue for NWDAA security | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241132 | TR 33.759 new KI UAV authorization for multi USS scenario | InterDigital Belgium. LLC | pCR | Approval | Yes |
Yes
| merged | No | S3‑241551 | |||
S3‑241502 | Scope of TR 33.759 | Ericsson, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241269 | |||
S3‑241503 | TR 33.759 UAS3 | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241540 | Overview and Security Assumption | Huawei, HiSilicon, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S3‑241379 | |||
S3‑241551 | new key issue for security enhancements to NEF services in support of multiple USSs | Huawei, HiSilicon, InterDigital | pCR | Approval | Yes |
Yes
| approved | No | S3‑241380 | |||
5.12 | Study on security Aspects of Enhancement for Proximity Based Services in 5GS Phase 3 | S3‑241321 | Draft TR Skeleton of TR 33.743 ProSe Phase 3 | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||
S3‑241322 | TR Scope of TR 33.743 ProSe Phase 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241619 | |||
S3‑241360 | pCR to TR 33.743 Scope | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑241619 | |||
S3‑241234 | Overview and Security assumptions of TR 33.743 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S3‑241558 | |||
S3‑241326 | TR Assumptions of TR 33.743 ProSe Phase 3 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241558 | |||
S3‑241364 | pCR to TR33.743 Clause 4 Overview and Security Assumptions | CATT | pCR | Approval | Yes |
Yes
| merged | No | S3‑241558 | |||
S3‑241128 | TR 33.743 Common References | InterDigital Belgium. LLC | pCR | Approval | Yes |
Yes
| merged | No | S3‑241558 | |||
S3‑241323 | New KI for security and privacy aspects of multi-hop U2N discovery | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241620 | |||
S3‑241457 | Key issue for Security for Multi-hop UE-to-Network Relay | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241248 | New KI on Security and Privacy for multi-hop UE-to-Network Relays | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241250 | Key issue on Security for multi-hop UE-to-Network Relay discovery | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241129 | TR 33.743 new KI multihop U2N security | InterDigital Belgium. LLC | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241130 | TR 33.743 new KI multihop U2N authorization | InterDigital Belgium. LLC | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241131 | TR 33.743 new KI multihop U2N discovery security | InterDigital Belgium. LLC | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241270 | Key issue of multiple hop U2N discovery | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241273 | Key issue of multiple hop U2N communication | Ericsson | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241167 | Key issue on authorization in the multi-hop UE-to-Network Relays scenario | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241169 | Key issue on Security for multi-hop UE-to-Network Relays discovery | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241620 | |||
S3‑241324 | New KI for security and privacy aspects of multi-hop UE-to-UE discovery | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241631 | |||
S3‑241458 | Key issue for Security for Multi-hop UE-to-UE Relay | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| revised | No | S3‑241631 | |||
S3‑241253 | New KI on Security and Privacy for Layer-3 multi-hop UE-to-UE Relays | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑241631 | |||
S3‑241256 | Key issue on Security for multi-hop UE-to-UE relay discovery | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| merged | No | S3‑241631 | |||
S3‑241166 | Key issue on authorization in the layer-3 multi-hop UE-to-UE Relays scenario | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241631 | |||
S3‑241168 | Key issue on Security for layer-3 multi-hop UE-to-UE Relays discovery | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241631 | |||
S3‑241271 | Solution_Security of multiple hop U2N discovery Model A | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241272 | Solution_Security of multiple hop U2N discovery Model B | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241274 | Solution_Security of multiple hop U2N communication | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241558 | Overview and Security assumptions of TR 33.743 | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S3‑241234 | |||
S3‑241618 | Draft TR 33.743 | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241619 | TR Scope of TR 33.743 ProSe Phase 3 | Huawei, HiSilicon, CATT | pCR | Approval | Yes |
Yes
| approved | No | S3‑241322 | |||
S3‑241620 | New KI for security aspects of multi-hop UE-to-Network relay | Huawei, HiSilicon, Xiaomi, China Telecom, InterDigital, Ericsson, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S3‑241323 | |||
S3‑241631 | Key issue for Security for Multi-hop UE-to-UE Relay | Beijing Xiaomi Mobile Software | pCR | Approval | Yes |
Yes
| approved | No | S3‑241458 | |||
5.13 | SID on security aspects of AIML enhancements | S3‑241287 | draft_TR_33.784- skeleton for AIML security | china mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||
S3‑241290 | Scope of TR 33.784 | china mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241292 | Overview of TR 33.784 | china mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241621 | |||
S3‑241442 | Security Assumptions | Nokia | pCR | Approval | Yes |
Yes
| merged | No | S3‑241621 | |||
S3‑241120 | New Key Issue on Authorization of AIML Model Retrieval | InterDigital Communications | pCR | Yes |
Yes
| merged | No | S3‑241639 | ||||
S3‑241178 | KI on Security on Supporting Direct AIML based Positioning | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241639 | |||
S3‑241184 | New key issue for Privacy and Authorization on LCS to support Direct AIML based Positioning | vivo | pCR | Approval | Yes |
Yes
| merged | No | S3‑241639 | |||
S3‑241293 | KI on security aspects on enhancements to LCS to support AIML | china mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241639 | |||
S3‑241351 | Add KI on Security for Direct AI/ML based Positioning | OPPO | pCR | Approval | Yes |
Yes
| merged | No | S3‑241639 | |||
S3‑241468 | New KI on AI model authorization | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241179 | KI on Authorization of Members of The VFL Group | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241625 | |||
S3‑241185 | New key issue on authorization of VFL member selection | vivo | pCR | Approval | Yes |
Yes
| merged | No | S3‑241625 | |||
S3‑241203 | Authorization of members of the VFL group. | Nokia | pCR | Approval | Yes |
Yes
| merged | No | S3‑241625 | |||
S3‑241221 | New KI on authorization mechanism of selection of VFL participants in the VFL group, outside the PLMN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241625 | |||
S3‑241294 | KI on Authorization of selection of members in VFL groups | china mobile | pCR | Approval | Yes |
Yes
| merged | No | S3‑241625 | |||
S3‑241311 | New KI on authorization of data access for supporting VFL | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241625 | |||
S3‑241355 | Add KI on authorization of selection of participant NWDAF and/or AF in VFL | OPPO | pCR | Approval | Yes |
Yes
| merged | No | S3‑241625 | |||
S3‑241186 | New key issue on privacy of VFL data and feature alignment | vivo | pCR | Approval | Yes |
Yes
| merged | No | S3‑241624 | |||
S3‑241312 | New KI on UE ID security and privacy of VFL between VFL members | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241624 | |||
S3‑241119 | New Key Issue on Privacy Protection in VFL Training Data | InterDigital Communications | pCR | Yes |
Yes
| merged | No | S3‑241624 | ||||
S3‑241123 | New Key Issue on Secure AIML Data Transfer | InterDigital Communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241187 | New key issue on security of VFL training | vivo | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241349 | Add KI on security for AI/ML model sharing between NWDAF and AF in VFL | OPPO | pCR | Approval | Yes |
Yes
| merged | No | S3‑241625 | |||
S3‑241346 | Add KI on security for AI/ML model sharing between NWDAF | OPPO | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑241615 | New KI on authorization mechanism of selection of VFL participants in the VFL group, outside the PLMN | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S3‑241621 | Overview of TR 33.784 | china mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑241292 | |||
S3‑241624 | New KI on UE ID security and privacy of VFL between VFL members | Huawei, HiSilicon, Vivo | pCR | Approval | Yes |
Yes
| approved | No | S3‑241312 | |||
S3‑241625 | New KI on authorization mechanism of selection of VFL participants in the VFL group, outside the PLMN | Huawei, HiSilicon, vivo, OPPO, ZTE, China Mobile, Nokia, Ericsson, IDCC | pCR | Approval | Yes |
Yes
| approved | No | S3‑241221 | |||
S3‑241639 | KI on security aspects on enhancements to LCS to support AIML | china mobile | pCR | Approval | Yes |
Yes
| approved | No | S3‑241293 | |||
S3‑241651 | TR_33.784 0.1.0-Study on security aspects of Core Network Enhanced Support for AIML | china mobile,vivo | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.14 | SID_EdgeComputing | S3‑241216 | Overviw of Edge Computing | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | ||
S3‑241217 | Skeleton of Edge Computing | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241225 | Scope of TR 33.749 | China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S3‑241564 | |||
S3‑241368 | pCR KI Security aspects of the traffic exchanged between local and central part of the DN | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241218 | EEC provided information verification | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241367 | pCR KI Secure retrieval of 5G system UE Ids and privacy related information | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241388 | New key issue on EEC provided IP address verification | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241409 | Key issue on EEC provided information verification | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241345 | Move Solution#30 from TR33.739 to TR33.749 | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241389 | New key issue on Edge Node Sharing | Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241215 | New KI on authorization of AF outside the operator domain | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241564 | Scope of TR 33.749 | China Unicom, Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241225 | |||
S3‑241569 | Draft TR 33.749 | China Unicom | draft TR | Approval | Yes |
Yes
| approved | No | ||||
5.15 | SID on security aspects for Multi-Access | S3‑241201 | Draft TR 33.754 skeleton (Multi-Access) | Intel | draft TR | Yes |
Yes
| revised | No | S3‑241591 | ||
S3‑241204 | Scope of TR 33.754 | Intel | pCR | Yes |
Yes
| revised | No | S3‑241590 | ||||
S3‑241191 | Update to New SID on security aspects for Multi-Access (DualSteer + ATSSS Ph-4) | NEC Corporation | SID revised | Yes |
Yes
| noted | No | |||||
S3‑241205 | Security Assumptions | Intel, Nokia | pCR | Yes |
Yes
| noted | No | |||||
S3‑241318 | New key issue about security architecture for non-3GPP access | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241590 | |||
S3‑241335 | New assumption all wifi AP used in ATSSS-Lite are untrusted | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241491 | KI on IPsec on user plane and/or control plane of untrusted non-3GPP access | Lenovo | pCR | Yes |
Yes
| noted | No | |||||
S3‑241180 | KI on Security on simplified ATSSS architecture over non-3GPP access | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241590 | |||
S3‑241365 | pCR KI Authentication of UE in Non-3GPP Access | Nokia, Intel | pCR | Approval | Yes |
Yes
| revised | No | S3‑241577 | |||
S3‑241366 | pCR KI Confidentiality and integrity protection of the communication between UE and 5GCore in Non-3GPP Access | Nokia, Intel | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241317 | New key issue for authentication of UE for non-3GPP access | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241577 | |||
S3‑241471 | New KI on authentication between UE and UPF | Xiaomi communications | pCR | Approval | Yes |
Yes
| merged | No | S3‑241577 | |||
S3‑241472 | New KI on security method negotiation for UE and UPF | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241473 | New KI on UPF topology hiding | Xiaomi communications | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241492 | Solution on IPsec on user plane and/or control plane of untrusted non-3GPP access | Lenovo | pCR | Yes |
Yes
| noted | No | |||||
S3‑241577 | pCR KI Authentication of UE in Non-3GPP Access | Nokia, Intel, Huawei, HiSilicon, Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑241365 | |||
S3‑241590 | Scope of TR 33.754 | Intel | pCR | Yes |
Yes
| approved | No | S3‑241204 | ||||
S3‑241591 | Draft TR 33.754 skeleton (Multi-Access) | Intel | pCR | Yes |
Yes
| approved | No | S3‑241201 | ||||
S3‑241608 | Draft TR 33.754 (Multi-Access) | Intel | draft TR | Yes |
Yes
| approved | No | |||||
5.16 | SID on 5GS enhancements for Energy Saving | S3‑241260 | Skeleton of TR 33.766 – Energy savings | Nokia. Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑241541 | |
S3‑241261 | Scope of TR 33.766 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑241542 | |||
S3‑241451 | 33.766: Architecture and Security Assumptions | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑241546 | |||
S3‑241262 | KI Security and privacy aspects of collection energy consumption information | Nokia. Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑241544 | |||
S3‑241263 | KI Security and privacy aspects of exposure of energy related information | Nokia. Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S3‑241547 | |||
S3‑241206 | Protection of Energy-Related Information Exposure | Intel | pCR | Yes |
Yes
| merged | No | S3‑241547 | ||||
S3‑241470 | New KI on network related energy information exposure authorization | Xiaomi communications | pCR | Approval | Yes |
Yes
| merged | No | S3‑241547 | |||
S3‑241541 | Skeleton of TR 33.766 – Energy savings | Nokia. Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑241260 | |||
S3‑241542 | Scope of TR 33.766 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑241261 | |||
S3‑241544 | KI Security and privacy aspects of collection energy consumption information | Nokia. Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S3‑241262 | |||
S3‑241546 | 33.766: Architecture and Security Assumptions | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑241451 | |||
S3‑241547 | KI Security and privacy aspects of exposure of energy related information | Nokia, Nokia Shanghai Bell, Intel, Xiaomi | pCR | Approval | Yes |
Yes
| approved | No | S3‑241263 | |||
S3‑241654 | Draft TR 33.766 | Ericsson GmbH, Eurolab | draft TR | Yes |
Yes
| approved | No | |||||
5.17 | SID on security aspects of 5G NR Femto | S3‑241188 | Draft Skeleton of TR 33.745 for Femto | ZTE Corporation, China Mobile | draft TR | Approval | Yes |
Yes
| approved | No | ||
S3‑241235 | scope of TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241237 | Add terms and abbriviations to TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241644 | |||
S3‑241236 | Architecture and security assumptions of TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241643 | |||
S3‑241332 | New assumption on try to reuse HeNB scheme as much as possible. | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| revised | No | S3‑241626 | |||
S3‑241111 | pCR on KI for Femto connecting securely with 5G Core | Charter Communications, Inc | pCR | Approval | Yes |
Yes
| revised | No | S3‑241652 | |||
S3‑241238 | New KI on device authentication to TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| merged | No | S3‑241652 | |||
S3‑241251 | New KI on fake 5G NR Femto | China Telecommunications | pCR | Approval | Yes |
Yes
| merged | No | S3‑241652 | |||
S3‑241333 | New key issue on 5G Femto authentication and authorization | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241652 | |||
S3‑241241 | New KI on protection of backhaul link of TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241647 | |||
S3‑241252 | New KI on protection of traffic between 5G NR Femto and operator’s security domain | China Telecommunications | pCR | Approval | Yes |
Yes
| merged | No | S3‑241647 | |||
S3‑241334 | security of communication between 5G Femto and 5GC | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| merged | No | S3‑241647 | |||
S3‑241189 | KI on Security of 5G NR Femto Ownership | ZTE Corporation, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241576 | |||
S3‑241249 | New KI on authorization of provisioning of subscribers allowed to access 5G NR Femto cells | China Telecommunications | pCR | Approval | Yes |
Yes
| merged | No | S3‑241576 | |||
S3‑241110 | pCR on KI for 5GS Core network topology hiding from 5G Femto deployments | Charter Communications, Inc | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241239 | New KI on location security of TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241645 | |||
S3‑241240 | New KI on access contol to TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S3‑241646 | |||
S3‑241242 | New KI on hosting party authentication to TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241410 | Key issue on broadcasting manipulated CAG IDs by the malicious Femto devices | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241243 | Fill out Gap analysis table of TR 33.745 | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241576 | KI on Security of 5G NR Femto Ownership | ZTE Corporation, China Mobile, China Telecom | pCR | Approval | Yes |
Yes
| approved | No | S3‑241189 | |||
S3‑241588 | LS to request clarification on the potential baseline system architecture of 5G NR Femto | China mobile | LS out | Yes |
Yes
| approved | No | |||||
S3‑241599 | Draft TR 33.745 | ZTE Corporation | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S3‑241626 | New assumption on try to reuse HeNB scheme as much as possible. | Huawei, HiSilicon | pCR | Approval | Yes |
Yes
| approved | No | S3‑241332 | |||
S3‑241643 | Architecture and security assumptions of TR 33.745 | China mobile, ZTE Corporation | pCR | Yes |
Yes
| approved | No | S3‑241236 | ||||
S3‑241644 | Add some terms and abbreviations to TR 33.745 | China mobile, ZTE Corporation | pCR | Yes |
Yes
| approved | No | S3‑241237 | ||||
S3‑241645 | Add new key issue on location security to TR 33.745 | China mobile | pCR | Yes |
Yes
| approved | No | S3‑241239 | ||||
S3‑241646 | Add new key issue on UE access control to TR 33.745 | China mobile | pCR | Yes |
Yes
| approved | No | S3‑241240 | ||||
S3‑241647 | Add new key issue on protection of backhaul link to TR 33.745 | China mobile, ZTE Corporation, China Telecommunications, Huawei, HiSilicon | pCR | Yes |
Yes
| approved | No | S3‑241241 | ||||
S3‑241652 | pCR on KI for Femto connecting securely with 5G Core | Charter Communications, Inc | pCR | Approval | Yes |
Yes
| approved | No | S3‑241111 | |||
5.18 | SID on security aspects of 5G Mobile Metaverse services | S3‑241422 | Skeleton for TR 33.721 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||
S3‑241413 | Scope for TR 33.721 | Samsung, OPPO | pCR | Approval | Yes |
Yes
| revised | No | S3‑241584 | |||
S3‑241452 | 33.721: Terms | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑241548 | |||
S3‑241174 | Security assumptions for Study on security aspects of 5G Mobile Metaverse services | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241549 | |||
S3‑241453 | 33.721: Security Assumptions | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑241549 | |||
S3‑241175 | New Key Issue on privacy protection of user sensitive information | ZTE Corporation | pCR | Approval | Yes |
Yes
| merged | No | S3‑241554 | |||
S3‑241202 | Key issue on Security aspects of exposure of user-sensitive information | IIT Delhi, IIT Bhilai, Nokia, Nokia Shanghai Bell, IIT Bombay, IIT Jodhpur, DoT | pCR | Approval | Yes |
Yes
| merged | No | S3‑241554 | |||
S3‑241456 | 33.721: Key Issue on Privacy of User Sensitive Information | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑241554 | |||
S3‑241200 | Key issue on Authentication and Authorization of Digital Identity | IIT Delhi, IIT Bhilai, Nokia, Nokia Shanghai Bell, IIT Bombay, IIT Jodhpur, DoT | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241214 | new key issue on security of digital asset management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241229 | New Key issue on digital identity authentication and authorization | China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241414 | Key issue on Digital ID/Avatar ID Authentication and Authorization | Samsung | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241454 | 33.721: Key Issue on Authentication and Authorization of Digital Asset | Xiaomi Technology | pCR | Approval | Yes |
Yes
| noted | No | ||||
S3‑241455 | 33.721: Key Issue on Authorization supporting Mobile Metaverse Services | Xiaomi Technology | pCR | Approval | Yes |
Yes
| revised | No | S3‑241553 | |||
S3‑241412 | Skeleton for TR 33.721 | Samsung | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S3‑241497 | LS to request clarification on mobile metaverse services | Samsung | LS out | Yes |
Yes
| approved | No | |||||
S3‑241548 | 33.721: Terms | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑241452 | |||
S3‑241549 | 33.721: Security Assumptions | Xiaomi, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S3‑241453 | |||
S3‑241553 | 33.721: Key Issue on Authorization supporting Mobile Metaverse Services | Xiaomi Technology | pCR | Approval | Yes |
Yes
| approved | No | S3‑241455 | |||
S3‑241554 | 33.721: Key Issue on Privacy of User Sensitive Information | Xiaomi, ZTE, IIT Delhi, IIT Bhilai, Nokia, Nokia Shanghai Bell, IIT Bombay, IIT Jodhpur, DoT | pCR | Approval | Yes |
Yes
| approved | No | S3‑241456 | |||
S3‑241584 | Scope for TR 33.721 | Samsung, OPPO | pCR | Approval | Yes |
Yes
| approved | No | S3‑241413 | |||
S3‑241632 | Draft TR 33.721 | Samsung | draft TR | Approval | Yes |
Yes
| approved | No | ||||
6 | New Study/Work item proposals |   | ||||||||||
7 | CVD and research |   | ||||||||||
8 | Any Other Business |   |