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-210810 | Agenda | agenda | WG Chair |
S3-102-e-Bis AI: 1 |
approved | [WTS] [JSN] | |||
S3-210811 | E-meeting procedures | other | WG Chair |
S3-102-e-Bis AI: 1 |
noted | [WTS] [JSN] | |||
S3-210812 | LS on Identification of source PLMN-ID in SBA |
LS in LS reply in S3-211204, S3-210822, S3-211204 |
C4-210249 |
S3-102-e-Bis AI: 2.2 |
replied to | [WTS] [JSN] | |||
S3-210813 | Reply LS on the user consent for trace reporting |
LS in LS reply in S3-211338, S3-211338 |
R2-2010894 |
S3-102-e-Bis AI: 2.14 |
replied to | [WTS] [JSN] | |||
S3-210814 | Reply LS on 5MBS progress and issues to address |
LS in LS reply in S3-211313, S3-211313 |
R2-2102480 |
S3-102-e-Bis AI: 2.11 |
replied to | [WTS] [JSN] | |||
S3-210815 | LS on using MOBIKE in Integrated Access and Backhaul system | LS in | R3-211297 |
S3-102-e-Bis AI: 2.18 |
postponed | [WTS] [JSN] | |||
S3-210816 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-211059 |
S2-2009339 |
S3-102-e-Bis AI: 2.8 |
postponed | [WTS] [JSN] | |||
S3-210817 | LS on propagation of user consent related information during Xn inter-PLMN handover |
LS in LS reply in S3-211330, S3-211330 |
R3-204378 |
S3-102-e-Bis AI: 2.14 |
replied to | [WTS] [JSN] | |||
S3-210818 | Reply to LS on Resynchronisations | LS in | ETSI SAGE |
S3-102-e-Bis AI: 2.5 |
postponed | [WTS] [JSN] | |||
S3-210819 | LS on Security Requirements for Sidelink/PC5 Relays | LS in | S2-2004750 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |||
S3-210820 | New Solution for privacy with Layer-2 based UE-to-UE Relay and Adaptation Layer | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210821 | Privacy considerations for Adaptation Layer and Layer-2 based UE-to-UE Relay | discussion | InterDigital, Inc. |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |||
S3-210822 | Reply-LS on Identification of source PLMN-ID in SBA |
LS out LS is reply to S3-210812 LS To: CT4 revised to S3-211204 |
Ericsson |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] | |||
S3-210823 | DRAFT LS on Layer-2 based UE-to-UE Relay utilizing Adaptation Layer |
LS out LS To: RAN2, SA2 |
InterDigital, Inc. | FS_5G_ProSe | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |
S3-210824 | Solution for privacy handling with Layer-3 based UE-to-UE Relay | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210825 | TR 33.847 Update for solution #10 |
pCR revised to S3-211240 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210826 | TR 33.847 Update for solution #24 |
pCR revised to S3-211242 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210827 | TR 33.847 Update for solution #25 | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-210828 | Updated Solution #22: Representation of identities during broadcast |
pCR revised to S3-211179 |
KPN N.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210829 | Administration of the virtualisation fabric |
pCR revised to S3-211340 |
NCSC | 33.848 0.6.0 | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
revised | [WTS] [JSN] |
S3-210830 | Updated Solution #23: Initial key with validity time |
pCR revised to S3-211185 |
KPN N.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210831 | TR 33.854 Solution#3 evaluation |
pCR revised to S3-211251 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-210832 | TR 33.854 Solution#5 evaluation |
pCR revised to S3-211252 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-210833 | TR 33.854 Solution#12 evaluation |
pCR revised to S3-211254 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-210834 | TR 33.854 Update for KI#4 |
pCR revised to S3-211255 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-210835 | TR 33.854 Update for KI#6 |
pCR revised to S3-211256 |
InterDigital, Europe, Ltd., Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-210836 | TR 33.854 Conclusion for KI#4 | pCR | InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
noted | [WTS] [JSN] |
S3-210837 | TR 33.854 Conclusion for KI#1 | pCR | InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
noted | [WTS] [JSN] |
S3-210838 | TR 33.854 Conclusion for KI#2 | pCR | InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
noted | [WTS] [JSN] |
S3-210839 | Update on Ki#27 Image Snapshot and VNF Mobility. |
pCR revised to S3-211341 |
Nokia, Nokia Shanghai Bell | 33.848 0.6.0 | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
revised | [WTS] [JSN] |
S3-210840 | Resolving UE ID privacy and format EN in solution 16 |
pCR revised to S3-211187 |
Alibaba Group | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-210841 | Editor note removal on SQNms protection by concealment with SUPI with f5 |
pCR revised to S3-211181 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210842 | Update to mapping table | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-210843 | Assuring SUCI generation by legitimiate SUPI owner using KSUCI |
pCR revised to S3-211182 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210844 | Update to Solution 4.5 AUTS SQNMS solution for 5GS to add a note | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-210845 | Evaluation of solution 2.3 Unified authentication response message by UE |
pCR revised to S3-211177 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210846 | Evaluation of solution 2.2 Encryption of authentication failure message types by UE with new keys derived from K_AUSF | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
noted | [WTS] [JSN] |
S3-210847 | Evaluation of solution 2.4 MAC-S based solution |
pCR revised to S3-211178 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210848 | MAC, SYNCH failure cause concealment solution |
pCR revised to S3-211183 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210849 | Key issue risk assessment | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
noted | [WTS] [JSN] |
S3-210850 | TR 33.847: Solution #18 | pCR | THALES | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-210851 | TR 33.846: update of solution #4.7 | pCR | THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
merged | [WTS] [JSN] |
S3-210852 | TR 33.846: evaluation of solution #3.1 |
pCR revised to S3-211210 |
THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210853 | TR 33.846: impacts of solutions |
pCR revised to S3-211211 |
THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210854 | TR 33.846: conclusion for KI #4.1 | pCR | THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
noted | [WTS] [JSN] |
S3-210855 | Discussion paper on GPSI translation to Temperary UE id | discussion | Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |||
S3-210856 | Reply LS on GPSI translation for Edge AS |
LS out LS is reply to S2-2005923,S6-202008 LS To: SA6, SA2 |
Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.8 |
merged | [WTS] [JSN] | |||
S3-210857 | Secure framewrok for MBS key distribution |
pCR revised to S3-211278 |
Nokia, Nokia Shanghai Bell | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-210858 | Direct UE connection to Slice AMF |
pCR revised to S3-211279 |
Nokia, Nokia Shanghai Bell | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-210859 | Discussion paper on LS on MOBIKE in IAB | discussion | Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-210860 | draft reply LS on MOBIKE in IAB |
LS out LS is reply to R3-211297 LS To: RAN3 |
Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-210861 | Key issue on Paging cause security | pCR | Nokia, Nokia Shanghai Bell, Samsung | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-210862 | Solution for secure BUSY indication | pCR | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-210863 | Solution for secure paging cause | pCR | Nokia, Nokia Shanghai Bell | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-210864 | key issue on secure connection to RAN slice | other | Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.21 |
merged | [WTS] [JSN] | |||
S3-210865 | EN resolution for KI#1 | pCR | LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210866 | Update for Sol#13 |
pCR revised to S3-211174 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210867 | Evaluation for Sol#13 |
pCR revised to S3-211175 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210868 | Add evaluation to solution#5 |
pCR revised to S3-211268 |
CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210869 | Add evaluation to solution#6 |
pCR revised to S3-211269 |
CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210870 | Modification on solution #6 | pCR | CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-210871 | Remove EN in solution#5 | pCR | CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-210872 | Add new key issue for user consent in TR 33.867 |
pCR revised to S3-211267 |
CATT | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] |
S3-210873 | Add use case mapping part for Key Issue #1 in TR 33.867 | pCR | CATT | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-210874 | ProSE Direct Discovery Clarification in Out-of-Coverage Scenarios | pCR | MITRE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210875 | Update comparison table for solution 2.7 and 6.4 | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
merged | [WTS] [JSN] |
S3-210876 | EN resolution on null scheme for solution 2.7 |
pCR revised to S3-211213 |
ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210877 | Text editing update on solution 2.7 | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
merged | [WTS] [JSN] |
S3-210878 | Solution of mitigating the SUPI guessing attacks | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-210879 | Resolve the EN in Sol#4.6 | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-210880 | Update mapping table in clause 6.0 | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-210881 | Resolving the EN of solution #7 | pCR | ZTE Corporation | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
S3-210882 | Resolving the EN of solution #17 | pCR | ZTE Corporation | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
S3-210883 | Conclusion for key issue 9 | pCR | ZTE Corporation | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
merged | [WTS] [JSN] |
S3-210884 | Removing ENs of Solution #3 |
pCR revised to S3-211202 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210885 | Removing ENs of Solution #4 |
pCR revised to S3-211203 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210886 | Update Solution#8 |
pCR revised to S3-211188 |
ZTE Corporation | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-210887 | New solution on control plane based provisioning - PS to AUSF | pCR | ZTE Corporation | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210888 | New solution on control plane based provisioning - PS to UDM | pCR | ZTE Corporation | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210889 | Definition of Network Slicing Isolation | pCR | ZTE Corporation | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
S3-210890 | New key issue on Network Slicing Isolation | pCR | ZTE Corporation | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
S3-210891 | Update and add evaluation to Solution #7 in TR 33.847 |
pCR revised to S3-211295 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210892 | Address Editor's Note in Solution #27 |
pCR revised to S3-211296 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210893 | Address Editor's Note in Solution #28 |
pCR revised to S3-211297 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210894 | Update details and add evaluation to Solution #26 in TR 33.847 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-210895 | Propose to resolve EN in KI#16 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-210896 | New solution to prevent malicious revocation | pCR | Huawei, HiSilicon | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-210897 | new solution for PC5 one-to-one rekeying |
pCR revised to S3-211298 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210898 | New solution to provide consisitent PDU session security for C2 | pCR | Huawei, HiSilicon | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
noted | [WTS] [JSN] |
S3-210899 | New Solution for Interworking from 5GS to EPS |
pCR revised to S3-211299 |
Huawei, HiSilicon | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
S3-210900 | Conclusion for Key Issue #7 | pCR | Huawei, HiSilicon | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
noted | [WTS] [JSN] |
S3-210901 | Discussion Paper on Source of User Consent | discussion | Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.14 |
noted | [WTS] [JSN] | ||
S3-210902 | Add Text for Source of User Consent for eNA | pCR | Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-210903 | New Use Case for MEC | pCR | Huawei, HiSilicon, Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-210904 | Analysis for UC3S | pCR | Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-210905 | New Solution for UE Related Analytics of NWDAF |
pCR revised to S3-211300 |
Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] |
S3-210906 | New Solution for Security for Provisioning of SNPN Credentials without Initial Credential | pCR | Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210907 | New Solution for Security for Provisioning of SNPN Credentials with initial credential | pCR | Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210908 | New Solution for Security for Provisioning of PNI-NPN Credentials with initial credential | pCR | Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210909 | Solution Update for Solution #5 |
pCR revised to S3-211301 |
Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-210910 | Solution Update for Solution #12 |
pCR revised to S3-211302 |
Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-210911 | Conclusion for Key Issue #1 | pCR | Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210912 | Solution Update for Solution #2 |
pCR revised to S3-211303 |
Huawei, HiSilicon | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-210913 | F1 interface security for IAB in NR-DC mode | pCR | Huawei, HiSilicon | 33.824 0.8.0 | FS_NR_IAB_Sec | Rel-17 |
S3-102-e-Bis AI: 2.18 |
noted | [WTS] [JSN] |
S3-210914 | New solution to mitigate the SUPI guessing attack |
pCR revised to S3-211304 |
Huawei, HiSilicon | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210915 | Update for solution #3.1 |
pCR revised to S3-211305 |
Huawei, HiSilicon | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210916 | Conclusion on key issue 1 |
pCR revised to S3-211306 |
Huawei, HiSilicon | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-210917 | Conclusion on key issue 4 | pCR | Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-210918 | New solution to update the MBS keys |
pCR revised to S3-211307 |
Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-210919 | Resolving the Editor's Notes in solution 2 |
pCR revised to S3-211308 |
Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-210920 | Updating and resolving the Editor's Notes in solution 8 | pCR | Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-210921 | Update solution#11 to meet privacy requirement | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210922 | Add evaluation to solution#11 |
pCR revised to S3-211309 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210923 | Address Editors Note in evaluation of solution #5 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
merged | [WTS] [JSN] |
S3-210924 | Add conclusion to KI#10 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210925 | Add evaluaition to solution#29 |
pCR revised to S3-211310 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210926 | Add evaluaition to solution#30 |
pCR revised to S3-211311 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210927 | A new solution to protect busy indication | pCR | Huawei, HiSilicon | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-210928 | A new Key issue on paging cause | pCR | Huawei, HiSilicon | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-210929 | Address the remaining ENs in solution 15 |
pCR revised to S3-211312 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210930 | Address Editor's Note in solution 11 | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-210931 | Address Editor's Note in solution 8 | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-210932 | Evaluation of solution #14 | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-210933 | Add evaluation to solution 1 |
pCR revised to S3-211270 |
CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-210934 | Add evaluation to solution 2 |
pCR revised to S3-211271 |
CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-210935 | Add evaluation to solution 8 | pCR | CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-210936 | Scope of SECAM SCAS | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210937 | Scope of VNP evaluation | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210938 | SECAM Assurance Level | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210939 | SECAM Vendor Role | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210940 | VNP SCAS Instantiation |
pCR revised to S3-211257 |
Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-210941 | GVNP Type 2 hardening unnecessary service or protocol | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210942 | GVNP Type 2 hardening unsupported component | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210943 | GVNP Tyype 2 hardening unused function | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210944 | GVNP Type 2 hardening unused software | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210945 | Operational Environmental Security Assumptions | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-210946 | Monitoring | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210947 | Dispute Resolution | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210948 | Operator Acceptance Aspect | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210949 | Discussion on GVNP Type 1 assets protection | discussion | Futurewei Technologies | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] | ||
S3-210950 | GVNP Type 1 assets protection | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210951 | More clarification on scope | pCR | Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
noted | [WTS] [JSN] |
S3-210952 | New Solution for Authentication and Authorization between EEC and ECS/EES |
pCR revised to S3-211326 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210953 | Editor notes removal |
pCR revised to S3-211314 |
Huawei, Hisilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-210954 | Conclusions on KI#5 Roaming-related security mechanisms for SNPNs | pCR | Huawei, Hisilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210955 | Evaluation of solution#9 |
pCR revised to S3-211327 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210956 | NPN: New solution to key issue #1 | pCR | Huawei, Hisilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210957 | AMFReal: Evaluation to solution #1 |
pCR revised to S3-211315 |
Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-210958 | AMFReal: Evaluation to solution #2 | pCR | Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
merged | [WTS] [JSN] |
S3-210959 | AMFReal: Updates to solution #3 |
pCR revised to S3-211316 |
Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-210960 | AMFReal: Evaluation to solution #4 | pCR | Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
merged | [WTS] [JSN] |
S3-210961 | AMFReal: Evaluation to solution #5 | pCR | Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-210962 | AMFReal: Evaluation to solution #6 | pCR | Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
merged | [WTS] [JSN] |
S3-210963 | MBS: Updates to solution #4 | pCR | Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-210964 | MBS: Evaluation to solution #4 |
pCR revised to S3-211317 |
Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-210965 | MBS: Conclusion to key issue #1 | pCR | Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
noted | [WTS] [JSN] |
S3-210966 | Requirement of subscribe-notification key issue | pCR | Huawei, Hisilicon | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210967 | Solution for non-delegated subscribe-notification key issue | pCR | Huawei, Hisilicon | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210968 | Update on Key issue #1 | pCR | Huawei, Hisilicon | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-210969 | EC: Conclusion for KI #9 |
pCR revised to S3-211318 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210970 | EC: Update Solution #13 to include CP option | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-210971 | EC: Discussion for the authorization during EDN relocation | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
S3-210972 | EC: Update of solution #22 |
pCR revised to S3-211319 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210973 | EC: New solution for the authorization during EDN relocation |
pCR revised to S3-211320 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210974 | EC: Conclusion for Key issue #5 | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
S3-210975 | MitM FBS Detection |
pCR revised to S3-211261 |
Huawei, HiSilicon, Philips | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-210976 | add evaluation to solution 1 |
pCR revised to S3-211262 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-210977 | add evaluation to solution 11 |
pCR revised to S3-211263 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-210978 | Proposal for conclusion for Key Issue 1,2,4,6 | pCR | Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
S3-210979 | Updates to solution 4 |
pCR revised to S3-211281 |
Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210980 | Updates to solution 12 |
pCR revised to S3-211282 |
Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-210981 | Key issue on security aspects of Paging Cause | pCR | Intel Deutschland GmbH | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-210982 | Conclusion to Key issue 1 | pCR | Intel Deutschland GmbH | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-210983 | Updates to solution 1 |
pCR revised to S3-211280 |
Intel Deutschland GmbH | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
revised | [WTS] [JSN] |
S3-210984 | Updates to solution 14: Add detailed steps |
pCR revised to S3-211283 |
Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-210985 | Updates to solution 14: Removal of Editor’s notes and Evaluation | pCR | Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210986 | skeleton for eNS2 TR |
other revised to S3-211266 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
revised | [WTS] [JSN] | ||
S3-210987 | Introduction for eNS2 TR | other | Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
noted | [WTS] [JSN] | ||
S3-210988 | Scope of eNS2 study |
other revised to S3-211264 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
revised | [WTS] [JSN] | ||
S3-210989 | New KI - slice authorization under UE quota constraint | other | Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
noted | [WTS] [JSN] | ||
S3-210990 | New KI - privacy issue on broadcasting slice information |
other revised to S3-211265 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
revised | [WTS] [JSN] | ||
S3-210991 | Proposal for conclusion for Key Issue 4 | pCR | Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
withdrawn | [WTS] [JSN] |
S3-210992 | SUCI Linkability attack |
pCR revised to S3-211236 |
NEC | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-210993 | New Solution for User Consent for Exposure of information to Edge Applications in Real Time |
pCR revised to S3-211342 |
China Unicom | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] |
S3-210994 | pCR to TR33.847- Update Solution#29 |
pCR revised to S3-211272 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210995 | pCR to TR33.847- Update Solution#30 |
pCR revised to S3-211273 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210996 | Proposal for conclusion for Key Issue 4 | pCR | Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
withdrawn | [WTS] [JSN] |
S3-210997 | Proposal for conclusion for Key Issue 4 -rev | pCR | Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-210998 | Draft CR 33.501 updates to TSC Annex L | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
withdrawn | [WTS] [JSN] |
S3-210999 | Requirement and solution on multiple working domains |
pCR revised to S3-211226 |
Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211000 | KI4 update on NEF-AF |
pCR revised to S3-211228 |
Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211001 | Solution update on NEF-AF | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211002 | Annex on asmmetric delay attacks |
pCR revised to S3-211227 |
Nokia, Nokia Shanghai Bell, Deutsche Telekom | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211003 | Annex on Security considerations for integration with TSN | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211004 | Solution to KI#2 (Provisioning of credentials) using AKMA | pCR | Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211005 | Resolving CP provisioning EN in solution #10 | pCR | Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211006 | Add evaluation to Solution #10 "Secure initial access to an SNPN onboarding network" | pCR | Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211007 | Updates to solution#10 on PS address |
pCR revised to S3-211206 |
Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-211008 | Solution for privacy protection during initial access | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211009 | Solution for providing secure onboarding without client authentication |
pCR revised to S3-211244 |
Nokia, Nokia Shanghai Bell | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-211010 | Solution for KI#1.3 |
pCR revised to S3-211234 |
Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-211011 | Reply LS on propagation of user consent related information during Xn inter-PLMN handover |
LS out LS is reply to S3-210028 LS To: RAN3 revised to S3-211330 |
Ericsson France S.A.S | Rel-16 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] | ||
S3-211012 | Solution for KI#1.4 | pCR | Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
merged | [WTS] [JSN] |
S3-211013 | Clarifying the GVNP lifecycle in clause 5.2.5.5.7.1 | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211014 | Modifying test case in clause 5.2.5.5.7.2 | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211015 | Clarifying for the security requirements and test cases in clause 5.2.5.7.7.2 and 5.2.5.7.7.3 | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211016 | Adding vendor development and product lifecycle processes and test laboratory accreditation into Clause 6 | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211017 | proposal for way forward | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211018 | Update key issue #2.2 in TR 33.846 |
pCR revised to S3-211049 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-211019 | Solution to Key issue #2.2 in TR 33.846 |
pCR revised to S3-211050 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-211020 | Update key issue #3.2 in TR 33.846 |
pCR revised to S3-211026 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-211021 | Removal of solution without any KI | pCR | China Mobile | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
S3-211022 | Update for KI#1.3 | pCR | Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
S3-211023 | Resolution of Editor’s Notes in Solution#7 |
pCR revised to S3-211232 |
Lenovo, Motorola Mobility | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-211024 | A new onboarding solution addressing KI#2 | pCR | Lenovo, Motorola Mobility | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211025 | Update of Solution#6 |
pCR revised to S3-211233 |
Lenovo, Motorola Mobility | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-211026 | Update key issue #3.2 in TR 33.846 |
pCR revision of S3-211020 |
China Mobile, ZTE, Huawei | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211027 | 5GFBS-Adding evaluation for solution#4 | pCR | Apple | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
S3-211028 | 5GFBS-Adding evaluation for solution#17 | pCR | Apple | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211029 | 5GFBS-Adding evaluation for solution#19 | pCR | Apple | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
S3-211030 | 5GFBS-Conclusion for key issue#2 | pCR | Apple | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
S3-211031 | MUSIM-Addressing the EN in solution#1 | pCR | Apple | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
S3-211032 | ProSe-enhancement on discovery procedure | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211033 | ProSe-Security solution during reselection via UE-to-UE relay | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211034 | ProSe-Editorial in key issue#11 | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211035 | MEC-New key issue on EEC ID privacy protection | pCR | Apple | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
S3-211036 | MEC-New solution for key issue#10 |
pCR revised to S3-211176 |
Apple | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-211037 | MEC-Modification on key issue#4 | pCR | Apple | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
S3-211038 | Update of scope of TR | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211039 | KI on Ensuring restrictive transfer of ML models between authorized NWDAFs |
pCR revised to S3-211237 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-211040 | KI on UE data collection protection | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211041 | Solution on Privacy preservation of data |
pCR revised to S3-211238 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-211042 | Solution on Abnormal NF behaviour detection |
pCR revised to S3-211239 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-211043 | Update of KI on Security protection of data via Message Framework |
pCR revised to S3-211241 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-211044 | High-level conclusions to KI#4 "Securing initial access for UE onboarding between UE and SNPN" | pCR | Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211045 | New Key Issue: Roaming case for token-based authorization in indirect communication | pCR | Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211046 | New Solution to KI#4: Using existing procedures for authorization of SCP to act on behalf of an NF Consumer | pCR | Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211047 | New Solution to KI#5: End-to-end integrity protection of HTTP body and method |
pCR revised to S3-211205 |
Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211048 | Security policy consistency during UE-to-UE relay path switch | pCR | Apple Computer Trading Co. Ltd | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211049 | Update key issue #2.2 in TR 33.846 |
pCR revision of S3-211018 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211050 | Solution to Key issue #2.2 in TR 33.846 |
pCR revision of S3-211019 revised to S3-211324 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-211051 | Solution on Providing the Security protection of data via Messaging |
pCR revised to S3-211207 |
Ericsson | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-211052 | Update on KI on Authorization of consumers for data access via DCCF |
pCR revised to S3-211209 |
Ericsson | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-211053 | Adding the revocation functionality to solution #14 |
pCR revised to S3-211331 |
Qualcomm Incorporated | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-211054 | Adding the revocation functionality to solution #13 |
pCR revised to S3-211333 |
Qualcomm Incorporated | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-211055 | Addressing the ENs on ngKSI in solution #1 |
pCR revised to S3-211334 |
Qualcomm Incorporated | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211056 | Addressing the EN on determining whether there is an AMF re-allocation in solution #1 |
pCR revised to S3-211335 |
Qualcomm Incorporated | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211057 | Some proposed text for the assessment of attack risk table |
pCR revised to S3-211336 |
Qualcomm Incorporated | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-211058 | Discussion on the LS on providing UE identity based on IP address | discussion | Qualcomm Incorporated |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |||
S3-211059 | Reply LS on IP address to GPSI translation |
LS out LS is reply to S3-210816 LS To: SA2 |
Qualcomm Incorporated |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |||
S3-211060 | Using TLS with AKMA to protect EDGE-1 and EDGE-4 |
pCR revised to S3-211337 |
Qualcomm Incorporated | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-211061 | Discussion on the LS on the user consent for trace reporting | discussion | Qualcomm Incorporated |
S3-102-e-Bis AI: 2.14 |
noted | [WTS] [JSN] | |||
S3-211062 | Reply LS on the user consent for trace reporting |
LS out LS is reply to R2-2010894 LS To: RAN2, SA5 revised to S3-211338 |
Qualcomm Incorporated |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] | |||
S3-211063 | Authorization of remote UE in L3 U2N relay |
pCR revised to S3-211291 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211064 | New Key Issue on security policy handling for 5G Prose services |
pCR revision of S3-210482 |
Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211065 | EN resolution for solution #18 | pCR | Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211066 | EN resolution and evaluation for solution #20 |
pCR revised to S3-211292 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211067 | Update the evaluation for solution #3 |
pCR revised to S3-211289 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211068 | Update the evaluation for solution #4 |
pCR revised to S3-211290 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211069 | EN resolution of Solution #1 | pCR | Qualcomm Incorporated | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211070 | 5G MBS traffic protection at service-layer |
pCR revised to S3-211294 |
Qualcomm Incorporated | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-211071 | Conclusions for KI #2 | pCR | Qualcomm Incorporated | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
S3-211072 | Evaluation on UE behavior on detection of false signature | pCR | Qualcomm Incorporated | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
S3-211073 | Evaluation on signing key management | pCR | Qualcomm Incorporated | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
S3-211074 | pCR: Further conclusions for KI #1 | pCR | Qualcomm Incorporated, CableLabs, Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211075 | pCR: Conclusions for KI #4 | pCR | Qualcomm Incorporated, CableLabs | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211076 | pCR: Addressing the EN in solution #4 |
pCR revised to S3-211259 |
Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-211077 | pCR: Addressing the SUPI privacy EN in solution #11 | pCR | Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211078 | pCR: Addressing the PS discovery EN in solution #11 |
pCR revised to S3-211260 |
Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
S3-211079 | IIOT: Resolve EN in solution #2 | pCR | Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211080 | IIOT: Update to KI#3 |
pCR revised to S3-211243 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211081 | IIOT: Conclusion on KI#4 |
pCR revised to S3-211246 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211082 | IIOT: Conclusion on KI#1 | pCR | Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
merged | [WTS] [JSN] |
S3-211083 | KI on Processing user consent depending on the regulatory and regional demands | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
merged | [WTS] [JSN] |
S3-211084 | KI on Modification or revocation of user consent | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
noted | [WTS] [JSN] |
S3-211085 | KI on User consent for data collection | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
merged | [WTS] [JSN] |
S3-211086 | Editorial updates to 33846-0100 |
pCR revised to S3-211184 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-211087 | ProSe: Update to solution #5 |
pCR revised to S3-211328 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211088 | ProSe: Retrieve Discovery keys for UE-to-network relays |
pCR revised to S3-211229 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211089 | ProSe: Update to solution #21 |
pCR revised to S3-211230 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211090 | ProSe: Update to solution #6 | pCR | Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
withdrawn | [WTS] [JSN] |
S3-211091 | AMF reallocation: Update to solution #2 |
pCR revised to S3-211285 |
Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211092 | AMF re-allocation: Definition of isolation | pCR | Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
S3-211093 | AMF re-allocation: New solution with reroute of Registration Request and protected security context via RAN |
pCR revised to S3-211286 |
Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211094 | AMF re-allocation: Notes from offline teleconference | discussion | Ericsson | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] | |
S3-211095 | AMF re-allocation: Update of the assumptions | pCR | Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
S3-211096 | MUSIM: Resolving the EN regarding SA2’s decision on Busy Indication |
pCR revised to S3-211275 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
revised | [WTS] [JSN] |
S3-211097 | MUSIM: Updating the threat analysis in Key Issue #1 |
pCR revised to S3-211276 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
revised | [WTS] [JSN] |
S3-211098 | MUSIM: Updating Key Issue #2 with Threats and Requirements | pCR | Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-211099 | MUSIM: Adding a New Key Issue on User Privacy | pCR | Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-211100 | MUSIM: Updating Solution #1 |
pCR revised to S3-211277 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
revised | [WTS] [JSN] |
S3-211101 | ProSe: Updating Key Issue #1 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211102 | ProSe: Updating Key Issue #9 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211103 | ProSe: Updating Key Issue #12 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211104 | ProSe: Updating Key Issue #16 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211105 | ProSe: Adding a New Key Issue on Security Policies for PC5 Direct Link | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211106 | ProSe: Adding a New Key Issue on Security Policy with UE-to-Network Relay | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211107 | ProSe: Adding a New Key Issue on Security Policy with UE-to-UE Relay | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211108 | Reply LS to LS on Security Requirements for Sidelink/PC5 Relays |
LS out LS To: SA2 |
Xiaomi Technology | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |
S3-211109 | Solution for KI#2 using PKC without requiring tight time sync |
pCR revised to S3-211329 |
Philips International B.V. | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211110 | Secondary authentication for Session Breakout | discussion | Ericsson |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |||
S3-211111 | [Draft] LS on Secondary authentication for Session Breakout |
LS out LS To: SA2 |
Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |
S3-211112 | IIoT: Update to solution #3 |
pCR revised to S3-211215 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211113 | IIoT: Update to and conclusion on KI #2 |
pCR revised to S3-211216 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211114 | EC: Update to solution #17 |
pCR revised to S3-211222 |
Ericsson | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
S3-211115 | UAS: Update to solution #2 |
pCR revised to S3-211212 |
Ericsson | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-211116 | Editorials Solution #24 | pCR | Philips International B.V. | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211117 | Update to Solution#4 |
pCR revised to S3-211245 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211118 | LS on end-to-end protection of HTTP message for Indirect communication |
LS out LS To: CT4 revised to S3-211231 |
CableLabs, Mavenir, Nokia, Nokia Bell Labs | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] | ||
S3-211119 | Update to Solution#6 |
pCR revised to S3-211247 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211120 | Modification to address FFS about key update after re-authentication in Solution 2 | pCR | Philips International B.V. | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
merged | [WTS] [JSN] |
S3-211121 | Solution to enable Reallocated AMF to serve the UE |
pCR revised to S3-211248 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211122 | Update to Solution#7 |
pCR revised to S3-211249 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-211123 | pCR: Conclusion for KI #1 on receiving KAUSF from AAA | pCR | CableLabs | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211124 | Resolving EN on UAVC Change |
pCR revised to S3-211250 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-211125 | Update to Solution#15 |
pCR revised to S3-211253 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
S3-211126 | pCR: Conclusion for KI #1 on addressing security threat against KAUSF | pCR | CableLabs | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
S3-211127 | Improve description of key update in Solution 2 by refering to Solution 9 | pCR | Philips International B.V. | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211128 | New annex of TR 33.809 – attack taxonomy for 5G UE over radio interfaces |
pCR revised to S3-211235 |
CableLabs, NTT Docomo, Philips, Deutsche Telekom AG | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
S3-211129 | [ProSe] Evaluation for solution#1 |
pCR revised to S3-211198 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211130 | [ProSe] Resolving ENs in solution#1 |
pCR revised to S3-211199 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211131 | Discussion for MitM attack | discussion | Samsung | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] | |
S3-211132 | [5GFBS] Identifying MitM attack | pCR | Samsung | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
S3-211133 | New key issue for Restricted Access in AMF re-allocation | pCR | Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
S3-211134 | Resolving ENs in Solution#1 |
pCR revised to S3-211200 |
Samsung | 33.862 0.3.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e-Bis AI: 2.15 |
revised | [WTS] [JSN] |
S3-211135 | Solution on integrity protection of data transferred between AF and NWDAF |
pCR revised to S3-211201 |
Samsung | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
S3-211136 | Correction to clause 5A.1.1 in TR 33.867 | pCR | Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-211137 | Key Issue on user consent for UE data analytics using NWDAF | pCR | Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
merged | [WTS] [JSN] |
S3-211138 | Update on scope of User Consent |
pCR revised to S3-211193 |
Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] |
S3-211139 | Solution on analytics for DoS attack detection | pCR | Samsung | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
S3-211140 | Solution on analytics for MitM attack detection | pCR | Samsung | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
S3-211141 | Removal of Editor’s Note (1 and 5) in Solution #5 |
pCR revised to S3-211194 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211142 | Resolution of Editor’s Notes and clarification on handling of Legacy UEs in Solution #5 |
pCR revised to S3-211195 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211143 | Removal of Editor’s Note (#4) in Solution #5 |
pCR revised to S3-211196 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
S3-211144 | [Solution] Key generation and distribution mechanism for MBS |
pCR revised to S3-211197 |
Samsung | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
S3-211145 | Key issue on User authorization for MUSIM optimizations | pCR | Samsung | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-211146 | Key Issue on home network authorization for MUSIM optimizations | pCR | Samsung | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
S3-211147 | TR 33.846: evaluation of solution #2.2 |
pCR revised to S3-211208 |
THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
S3-211148 | TR 33.846: conclusion for KI #2.1 | pCR | THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
noted | [WTS] [JSN] |
S3-211149 | Resolving editor’s note in solution #32 |
pCR revised to S3-211258 |
Philips International B.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211150 | Update on Solution #21: Interworking handover from EPS to 5GS |
pCR revised to S3-211189 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
S3-211151 | Update on Solution #22: S1 handover |
pCR revised to S3-211190 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
S3-211152 | Update on Solution #23: X2 handover | pCR | Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
S3-211153 | Update on Solution #24: Interworking handover from 5GS to EPS |
pCR revised to S3-211191 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
S3-211154 | pCR to 33.809 - addition of new key issue on false detections | pCR | VODAFONE Group Plc | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
S3-211155 | pCR to 33.809 - addition of solution to False positive detections | pCR | VODAFONE Group Plc | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
withdrawn | [WTS] [JSN] |
S3-211156 | Rapporteurs update to 33.875 |
pCR revised to S3-211224 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211157 | Mapping of solutions to key issues |
pCR revised to S3-211225 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211158 | KI details added to NRF NF authentication in indirect communication |
pCR revised to S3-211170 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211159 | Service request authenticity verification in indirect communication |
pCR revised to S3-211223 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211160 | NF-SCP authorization |
pCR revised to S3-211220 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211161 | Service response verification in indirect communication |
pCR revised to S3-211217 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211162 | Authorization of multiple consumers within a NF set | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211163 | KI on Roaming with token based authorization in indirect communication | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211164 | Trust model | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211165 | NRF service management | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
S3-211166 | More details on SCP deployment models |
pCR revised to S3-211218 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211167 | Update of key issue #7 with X2 handover and S1 handover | pCR | Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
noted | [WTS] [JSN] |
S3-211168 | New solution for source eNB pre-configured with neighbour target eNB’s support of UP IP |
pCR revised to S3-211192 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
S3-211169 | Use of criticality information | pCR | Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
S3-211170 | KI details added to End-to-end integrity protection of HTTP messages |
pCR revision of S3-211158 revised to S3-211221 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
S3-211171 | Study item management and planning | other | WG Chair |
S3-102-e-Bis AI: 1 |
noted | [WTS] [JSN] | |||
S3-211172 | Reply LS on IP address to GPSI translation | LS in | S2-2101307 |
S3-102-e-Bis AI: 2.8 |
postponed | [WTS] [JSN] | |||
S3-211173 | Process and agenda presentation for SA3#102Bis-e | other | SA WG3 chair |
S3-102-e-Bis AI: 1 |
noted | [WTS] [JSN] | |||
S3-211174 | Update for Sol#13 |
pCR revision of S3-210866 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211175 | Evaluation for Sol#13 |
pCR revision of S3-210867 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211176 | MEC-New solution for key issue#10 |
pCR revision of S3-211036 |
Apple | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211177 | Evaluation of solution 2.3 Unified authentication response message by UE |
pCR revision of S3-210845 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211178 | Evaluation of solution 2.4 MAC-S based solution |
pCR revision of S3-210847 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211179 | Updated Solution #22: Representation of identities during broadcast |
pCR revision of S3-210828 |
KPN N.V., MITRE | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211180 | TR 33.846: evaluation of solution #2.2 | pCR | THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
withdrawn | [WTS] [JSN] |
S3-211181 | Editor note removal on SQNms protection by concealment with SUPI with f5 |
pCR revision of S3-210841 |
Nokia, Nokia Shanghai Bell, Thales | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211182 | Assuring SUCI generation by legitimiate SUPI owner using KSUCI |
pCR revision of S3-210843 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211183 | MAC, SYNCH failure cause concealment solution |
pCR revision of S3-210848 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211184 | Editorial updates to 33846-0100 |
pCR revision of S3-211086 |
Nokia, Nokia Shanghai Bell,ZTE | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211185 | Updated Solution #23: Initial key with validity time |
pCR revision of S3-210830 |
TNO | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211186 | TR 33.853 v1.5.0 | draft TR | VODAFONE Group Plc | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] | |
S3-211187 | Resolving UE ID privacy and format EN in solution 16 |
pCR revision of S3-210840 |
Alibaba Group | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211188 | Update Solution#8 |
pCR revision of S3-210886 |
ZTE Corporation | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211189 | Update on Solution #21: Interworking handover from EPS to 5GS |
pCR revision of S3-211150 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
S3-211190 | Update on Solution #22: S1 handover |
pCR revision of S3-211151 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
S3-211191 | Update on Solution #24: Interworking handover from 5GS to EPS |
pCR revision of S3-211153 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
S3-211192 | New solution for source eNB pre-configured with neighbour target eNB’s support of UP IP |
pCR revision of S3-211168 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
S3-211193 | Update on scope of User Consent |
pCR revision of S3-211138 |
Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-211194 | Removal of Editor’s Note (1 and 5) in Solution #5 |
pCR revision of S3-211141 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211195 | Resolution of Editor’s Notes and clarification on handling of Legacy UEs in Solution #5 |
pCR revision of S3-211142 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211196 | Removal of Editor’s Note (#4) in Solution #5 |
pCR revision of S3-211143 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211197 | [Solution] Key generation and distribution mechanism for MBS |
pCR revision of S3-211144 |
Samsung | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211198 | [ProSe] Evaluation for solution#1 |
pCR revision of S3-211129 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211199 | [ProSe] Resolving ENs in solution#1 |
pCR revision of S3-211130 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211200 | Resolving ENs in Solution#1 |
pCR revision of S3-211134 |
Samsung | 33.862 0.3.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e-Bis AI: 2.15 |
approved | [WTS] [JSN] |
S3-211201 | Solution on integrity protection of data transferred between AF and NWDAF |
pCR revision of S3-211135 |
Samsung | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211202 | Removing ENs of Solution #3 |
pCR revision of S3-210884 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211203 | Removing ENs of Solution #4 |
pCR revision of S3-210885 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211204 | Reply-LS on Identification of source PLMN-ID in SBA |
LS out LS is reply to S3-210812 LS To: CT4 revision of S3-210822 |
Ericsson |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] | |||
S3-211205 | New Solution to KI#5: End-to-end integrity protection of HTTP body and method |
pCR revision of S3-211047 |
Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211206 | Updates to solution#10 on PS address |
pCR revision of S3-211007 |
Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211207 | Solution on Providing the Security protection of data via Messaging |
pCR revision of S3-211051 |
Ericsson, Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211208 | TR 33.846: evaluation of solution #2.2 |
pCR revision of S3-211147 |
THALES, Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211209 | Update on KI on Authorization of consumers for data access via DCCF |
pCR revision of S3-211052 |
Ericsson, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211210 | TR 33.846: evaluation of solution #3.1 |
pCR revision of S3-210852 |
THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211211 | TR 33.846: impacts of solutions |
pCR revision of S3-210853 |
THALES, ZTE | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211212 | UAS: Update to solution #2 |
pCR revision of S3-211115 |
Ericsson | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211213 | EN resolution on null scheme for solution 2.7 |
pCR revision of S3-210876 |
ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211214 | KI on Modification or revocation of user consent | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
withdrawn | [WTS] [JSN] |
S3-211215 | IIoT: Update to solution #3 |
pCR revision of S3-211112 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211216 | IIoT: Update to and conclusion on KI #2 |
pCR revision of S3-211113 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211217 | Service response verification in indirect communication |
pCR revision of S3-211161 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211218 | More details on SCP deployment models |
pCR revision of S3-211166 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211219 | New Solution to KI#4: Using existing procedures for authorization of SCP to act on behalf of an NF Consumer | pCR | Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
withdrawn | [WTS] [JSN] |
S3-211220 | NF-SCP authorization |
pCR revision of S3-211160 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211221 | KI details added to End-to-end integrity protection of HTTP messages |
pCR revision of S3-211170 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211222 | EC: Update to solution #17 |
pCR revision of S3-211114 |
Ericsson | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211223 | Service request authenticity verification in indirect communication |
pCR revision of S3-211159 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211224 | Rapporteurs update to 33.875 |
pCR revision of S3-211156 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211225 | Mapping of solutions to key issues |
pCR revision of S3-211157 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211226 | Requirement and solution on multiple working domains |
pCR revision of S3-210999 |
Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211227 | Annex on asmmetric delay attacks |
pCR revision of S3-211002 |
Nokia, Nokia Shanghai Bell, Deutsche Telekom | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211228 | KI4 update on NEF-AF |
pCR revision of S3-211000 |
Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211229 | ProSe: Retrieve Discovery keys for UE-to-network relays |
pCR revision of S3-211088 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211230 | ProSe: Update to solution #21 |
pCR revision of S3-211089 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211231 | LS on end-to-end protection of HTTP message for Indirect communication |
LS out LS To: CT4 revision of S3-211118 |
CableLabs, Mavenir, Nokia, Nokia Bell Labs | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] | ||
S3-211232 | Resolution of Editor’s Notes in Solution#7 |
pCR revision of S3-211023 |
Lenovo, Motorola Mobility | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211233 | Update of Solution#6 |
pCR revision of S3-211025 |
Lenovo, Motorola Mobility | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211234 | Solution for KI#1.3 |
pCR revision of S3-211010 |
Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211235 | New annex of TR 33.809 – attack taxonomy for 5G UE over radio interfaces |
pCR revision of S3-211128 |
CableLabs, NTT Docomo, Philips, Deutsche Telekom AG | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211236 | SUCI Linkability attack |
pCR revision of S3-210992 |
NEC | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211237 | KI on Ensuring restrictive transfer of ML models between authorized NWDAFs |
pCR revision of S3-211039 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211238 | Solution on Privacy preservation of data |
pCR revision of S3-211041 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
S3-211239 | Solution on Abnormal NF behaviour detection |
pCR revision of S3-211042 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211240 | TR 33.847 Update for solution #10 |
pCR revision of S3-210825 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211241 | Update of KI on Security protection of data via Message Framework |
pCR revision of S3-211043 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211242 | TR 33.847 Update for solution #24 |
pCR revision of S3-210826 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211243 | IIOT: Update to KI#3 |
pCR revision of S3-211080 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211244 | Solution for providing secure onboarding without client authentication |
pCR revision of S3-211009 |
Nokia, Nokia Shanghai Bell | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211245 | Update to Solution#4 |
pCR revision of S3-211117 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211246 | IIOT: Conclusion on KI#4 |
pCR revision of S3-211081 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211247 | Update to Solution#6 |
pCR revision of S3-211119 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211248 | Solution to enable Reallocated AMF to serve the UE |
pCR revision of S3-211121 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211249 | Update to Solution#7 |
pCR revision of S3-211122 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211250 | Resolving EN on UAVC Change |
pCR revision of S3-211124 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211251 | TR 33.854 Solution#3 evaluation |
pCR revision of S3-210831 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211252 | TR 33.854 Solution#5 evaluation |
pCR revision of S3-210832 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211253 | Update to Solution#15 |
pCR revision of S3-211125 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211254 | TR 33.854 Solution#12 evaluation |
pCR revision of S3-210833 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211255 | TR 33.854 Update for KI#4 |
pCR revision of S3-210834 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211256 | TR 33.854 Update for KI#6 |
pCR revision of S3-210835 |
InterDigital, Europe, Ltd., Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211257 | VNP SCAS Instantiation |
pCR revision of S3-210940 |
Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
S3-211258 | Resolving editor’s note in solution #32 |
pCR revision of S3-211149 |
Philips International B.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211259 | pCR: Addressing the EN in solution #4 |
pCR revision of S3-211076 |
Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211260 | pCR: Addressing the PS discovery EN in solution #11 |
pCR revision of S3-211078 |
Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211261 | MitM FBS Detection |
pCR revision of S3-210975 |
Huawei, HiSilicon, Philips | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211262 | add evaluation to solution 1 |
pCR revision of S3-210976 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211263 | add evaluation to solution 11 |
pCR revision of S3-210977 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211264 | Scope of eNS2 study |
other revision of S3-210988 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
approved | [WTS] [JSN] | ||
S3-211265 | New KI - privacy issue on broadcasting slice information |
other revision of S3-210990 |
Huawei, HiSilicon, Nokia | Rel-17 |
S3-102-e-Bis AI: 2.21 |
approved | [WTS] [JSN] | ||
S3-211266 | Draft TR for eNS2 Study |
other revision of S3-210986 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
approved | [WTS] [JSN] | ||
S3-211267 | Add new key issue for user consent in TR 33.867 |
pCR revision of S3-210872 |
CATT | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-211268 | Add evaluation to solution#5 |
pCR revision of S3-210868 |
CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211269 | Add evaluation to solution#6 |
pCR revision of S3-210869 |
CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211270 | Add evaluation to solution 1 |
pCR revision of S3-210933 |
CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211271 | Add evaluation to solution 2 |
pCR revision of S3-210934 |
CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211272 | pCR to TR33.847- Update Solution#29 |
pCR revision of S3-210994 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211273 | pCR to TR33.847- Update Solution#30 |
pCR revision of S3-210995 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211274 | Draft TR 33.847 v0.5.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] | |
S3-211275 | MUSIM: Resolving the EN regarding SA2’s decision on Busy Indication |
pCR revision of S3-211096 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
S3-211276 | MUSIM: Updating the threat analysis in Key Issue #1 |
pCR revision of S3-211097 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
S3-211277 | MUSIM: Updating Solution #1 |
pCR revision of S3-211100 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
S3-211278 | Secure framewrok for MBS key distribution |
pCR revision of S3-210857 |
Nokia, Nokia Shanghai Bell | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211279 | Direct UE connection to Slice AMF |
pCR revision of S3-210858 |
Nokia, Nokia Shanghai Bell | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211280 | Updates to solution 1 |
pCR revision of S3-210983 |
Intel Deutschland GmbH | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
S3-211281 | Updates to solution 4 |
pCR revision of S3-210979 |
Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211282 | Updates to solution 12 |
pCR revision of S3-210980 |
Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211283 | Updates to solution 14: Add detailed steps |
pCR revision of S3-210984 |
Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211284 | draft TR Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules | draft TR | Intel Deutschland GmbH | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] | |
S3-211285 | AMF reallocation: Update to solution #2 |
pCR revision of S3-211091 |
Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211286 | AMF re-allocation: New solution with reroute of Registration Request and protected security context via RAN |
pCR revision of S3-211093 |
Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211287 | Draft TR 33.846 v0.11.0 Study on authentication enhancements in the 5G System (5GS) | draft TR | Ericsson Hungary Ltd | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] | |
S3-211288 | Draft TR 33.864 v0.4.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson Hungary Ltd | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] | |
S3-211289 | Update the evaluation for solution #3 |
pCR revision of S3-211067 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211290 | Update the evaluation for solution #4 |
pCR revision of S3-211068 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211291 | Authorization of remote UE in L3 U2N relay |
pCR revision of S3-211063 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211292 | EN resolution and evaluation for solution #20 |
pCR revision of S3-211066 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211293 | Draft TR 33.850 | draft TR | Huawei, HiSilicon | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] | |
S3-211294 | 5G MBS traffic protection at service-layer |
pCR revision of S3-211070 |
Qualcomm Incorporated | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211295 | Update and add evaluation to Solution #7 in TR 33.847 |
pCR revision of S3-210891 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211296 | Address Editor's Note in Solution #27 |
pCR revision of S3-210892 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211297 | Address Editor's Note in Solution #28 |
pCR revision of S3-210893 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211298 | new solution for PC5 one-to-one rekeying |
pCR revision of S3-210897 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211299 | New Solution for Interworking from 5GS to EPS |
pCR revision of S3-210899 |
Huawei, HiSilicon | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
S3-211300 | New Solution for UE Related Analytics of NWDAF |
pCR revision of S3-210905 |
Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-211301 | Solution Update for Solution #5 |
pCR revision of S3-210909 |
Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211302 | Solution Update for Solution #12 |
pCR revision of S3-210910 |
Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211303 | Solution Update for Solution #2 |
pCR revision of S3-210912 |
Huawei, HiSilicon | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
S3-211304 | New solution to mitigate the SUPI guessing attack |
pCR revision of S3-210914 |
Huawei, HiSilicon | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211305 | Update for solution #3.1 |
pCR revision of S3-210915 |
Huawei, HiSilicon | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211306 | Conclusion on key issue 1 |
pCR revision of S3-210916 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell, Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211307 | New solution to update the MBS keys |
pCR revision of S3-210918 |
Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211308 | Resolving the Editor's Notes in solution 2 |
pCR revision of S3-210919 |
Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211309 | Add evaluation to solution#11 |
pCR revision of S3-210922 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211310 | Add evaluaition to solution#29 |
pCR revision of S3-210925 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211311 | Add evaluaition to solution#30 |
pCR revision of S3-210926 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211312 | Address the remaining ENs in solution 15 |
pCR revision of S3-210929 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211313 | Reply LS on 5MBS progress and issues to address |
LS out LS is reply to S3-210814 LS To: RAN2 |
Huawei, HiSilicon |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] | |||
S3-211314 | Editor notes removal |
pCR revision of S3-210953 |
Huawei, Hisilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
S3-211315 | AMFReal: Evaluation to solution #1 |
pCR revision of S3-210957 |
Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211316 | AMFReal: Updates to solution #3 |
pCR revision of S3-210959 |
Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211317 | MBS: Evaluation to solution #4 |
pCR revision of S3-210964 |
Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
S3-211318 | EC: Conclusion for KI #9 |
pCR revision of S3-210969 |
Huawei, Hisilicon, ZTE | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211319 | EC: Update of solution #22 |
pCR revision of S3-210972 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211320 | EC: New solution for the authorization during EDN relocation |
pCR revision of S3-210973 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211321 | TR 33.839 v0.5.0 | draft TR | Huawei, Hisilicon | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] | |
S3-211322 | draft TR 33.866 0.4.0 | draft TR | China Mobile | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] | |
S3-211323 | draft TR 33.862 0.4.0 | draft TR | China Mobile | FS_SEC_5GMSG | Rel-17 |
S3-102-e-Bis AI: 2.15 |
approved | [WTS] [JSN] | |
S3-211324 | Solution to Key issue #2.2 in TR 33.846 |
pCR revision of S3-211050 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211325 | TR 33.818 v0.11.0 | draft TR | China Mobile Com. Corporation | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] | |
S3-211326 | New Solution for Authentication and Authorization between EEC and ECS/EES |
pCR revision of S3-210952 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211327 | Evaluation of solution#9 |
pCR revision of S3-210955 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211328 | ProSe: Update to solution #5 |
pCR revision of S3-211087 |
Ericsson, Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211329 | Solution for KI#2 using PKC without requiring tight time sync |
pCR revision of S3-211109 |
Philips International B.V. | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
S3-211330 | Reply LS on propagation of user consent related information during Xn inter-PLMN handover |
LS out LS is reply to S3-210817 LS To: RAN3 revision of S3-211011 |
Ericsson France S.A.S | Rel-16 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] | ||
S3-211331 | Adding the revocation functionality to solution #14 |
pCR revision of S3-211053 |
Qualcomm Incorporated | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211332 | TR 33.867 | draft TR | Huawei;HiSilicon | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] | |
S3-211333 | Adding the revocation functionality to solution #13 |
pCR revision of S3-211054 |
Qualcomm Incorporated | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
S3-211334 | Addressing the ENs on ngKSI in solution #1 |
pCR revision of S3-211055 |
Qualcomm Incorporated | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211335 | Addressing the EN on determining whether there is an AMF re-allocation in solution #1 |
pCR revision of S3-211056 |
Qualcomm Incorporated | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
S3-211336 | Some proposed text for the assessment of attack risk table |
pCR revision of S3-211057 |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
S3-211337 | Using TLS with AKMA to protect EDGE-1 and EDGE-4 |
pCR revision of S3-211060 |
Qualcomm Incorporated | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
S3-211338 | Reply LS on the user consent for trace reporting |
LS out LS is reply to S3-210813 LS To: RAN2, SA5 revision of S3-211062 |
Qualcomm Incorporated |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] | |||
S3-211339 | TR 33.848 v0.7.0 | draft TR | BT plc | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
approved | [WTS] [JSN] | |
S3-211340 | Administration of the virtualisation fabric |
pCR revision of S3-210829 |
NCSC | 33.848 0.6.0 | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
approved | [WTS] [JSN] |
S3-211341 | Update on Ki#27 Image Snapshot and VNF Mobility. |
pCR revision of S3-210839 |
Nokia, Nokia Shanghai Bell | 33.848 0.6.0 | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
approved | [WTS] [JSN] |
S3-211342 | New Solution for User Consent for Exposure of information to Edge Applications in Real Time |
pCR revision of S3-210993 |
China Unicom | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
S3-211343 | Draft TR 33.851 | draft TR | Nokia | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] | |
S3-211344 | Draft TR 33.875 | draft TR | Nokia | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] | |
S3-211345 | Draft TR 33.809 | draft TR | Apple | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] | |
S3-211346 | Draft TR 33.854 | draft TR | Qualcomm | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] | |
S3-211347 | Draft TR TR 33.857 | draft TR | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
538 documents (0.47320818901062 seconds)