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