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-202800 | Agenda | agenda | SA WG3 Chair |
S3-101-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-202801 | Report from SA3#100Bis-e meeting | report | MCC |
S3-101-e AI: 2 |
approved | [WTS] [JSN] | |||
S3-202802 | Report from SA3#100-e meeting | report | MCC |
S3-101-e AI: 2 |
approved | [WTS] [JSN] | |||
S3-202803 | Process for SA3#101e meeting | other | SA WG3 Chair |
S3-101-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-202804 | Report from last SA | report | SA WG3 Chair |
S3-101-e AI: 2 |
noted | [WTS] [JSN] | |||
S3-202805 | Draft LS: Misalignment on requirement for access token request between TS 29.510 and 33.501 |
LS out LS To: CT4 revised to S3-203495 |
Mavenir | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-202806 | SA3 and CT4 misalignment on token request for Discovery and NFManagement | discussion | Mavenir | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-202807 | NRF authorization during NF service consumer Access Token Get Request | draftCR | Mavenir | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
withdrawn | [WTS] [JSN] | |
S3-202808 | NRF authorization during NF service consumer Access Token Get Request |
CR revised to S3-203497 |
Mavenir | 33.501 16.4.0 CR#955 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-202809 | NRF authorization during NF service consumer Access Token Get Request |
CR revised to S3-203496 |
Mavenir | 33.501 15.10.0 CR#956 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-202810 | Editorial corrections to NDS/AF |
CR revised to S3-202819 |
Juniper Networks | 33.31 16.5.0 CR#113 catD | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
revised | [WTS] [JSN] |
S3-202811 | Discussion paper for evaluation update of solution #4.3 in TR 33.846 | discussion | Deutsche Telekom AG | Rel-17 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] | ||
S3-202812 | pCR: Evaluation update of solution #4.3 in TR 33.846 | pCR | Deutsche Telekom AG | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-202813 | Clarification to SEAF |
CR revision of S3-201873 |
Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#8353 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202814 | Clarification to SEAF | CR | Nokia, Nokia Shanghai Bell | 33.501 15.10.0 CR#957 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202815 | TCG progress - report from TCG rapporteur | other | InterDigital Communications |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202816 | Modified KI#5 for TR 33.847 – privacy of identities for UE2N path switc |
pCR revised to S3-203358 |
InterDigital Communications, CableLabs | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202817 | Update of KI#8 for TR 33.847 – privacy of identities for UE2UE Relay path switch |
pCR revised to S3-203362 |
InterDigital Communications, CableLabs | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202818 | New solution for TR 33.847 – Privacy handling for Layer-3 UE-to-UE Relay based on IP routing |
pCR revised to S3-203369 |
InterDigital Communications | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202819 | Editorial corrections to NDS/AF |
CR revision of S3-202810 |
Juniper Networks | 33.31 16.5.0 CR#1131 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
agreed | [WTS] [JSN] |
S3-202820 | TR 33.847 Update for solution #10 |
pCR revised to S3-203269 |
InterDigital Communications | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202821 | LS response to TCCA on Public Safety | LS in | GSMA 5G Joint-Activity (5GJA) |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202822 | Support of UAVs in 3GPP system and interfacing with USS/UTM | LS in | GSMA |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] | |||
S3-202823 | Use of 256-bit block Rijndael in Milenage-256 |
LS in LS reply in S3-203550, S3-203079, S3-203550 |
ETSI SAGE |
S3-101-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-202824 | Answer to ETSI SAGE LS dated 5 June 2020 regarding the use of 256-bit block Rijndael in Milenage-256 | LS in | TCA (Trusted Connectivity Alliance) |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202825 | LS on 5G-GUTI reallocation after paging of a UE in 5GMM-IDLE mode with suspend indication | LS in | C1-200967 |
S3-101-e AI: 4.8 |
postponed | [WTS] [JSN] | |||
S3-202826 | LS on NSSAA at inter-PLMN mobility | LS in | C1-206508 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-202827 | LS on the re-keying procedure for NR SL | LS in | R2-2005978 |
S3-101-e AI: 4.13 |
noted | [WTS] [JSN] | |||
S3-202828 | Reply LS on the re-keying procedure for NR SL |
LS in LS reply in S3-203483 |
C1-206576 |
S3-101-e AI: 4.13 |
replied to | [WTS] [JSN] | |||
S3-202829 | LS on Clarification on processing of messages after NAS security establishment | LS in | C1-206582 |
S3-101-e AI: 5.17 |
noted | [WTS] [JSN] | |||
S3-202830 | LS on MuDe functionality | LS in | C1-206625 |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202831 | LS on AUSF/UDM discovery based on SUCI information | LS in | C4-204337 |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202832 | LS on Misalignments on HTTP message format over N32-f |
LS in LS reply in S3-203522, S3-203522 |
C4-204409 |
S3-101-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-202833 | LS on information of stage 3 aspects for AKMA | LS in | CP-202255 |
S3-101-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-202834 | Reply LS on ETSI Plugtest reports | LS in | ETSI MCX Plugtests |
S3-101-e AI: 4.3 |
noted | [WTS] [JSN] | |||
S3-202835 | Reply LS to SA3 on FBS detection | LS in | R2-1914224 |
S3-101-e AI: 5.1 |
postponed | [WTS] [JSN] | |||
S3-202836 | LS on propagation of user consent related information during Xn inter-PLMN handover | LS in | R3-204378 |
S3-101-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-202837 | LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN |
LS in LS reply in S3-203399, S3-203399 |
S2-2004385 |
S3-101-e AI: 5.12 |
replied to | [WTS] [JSN] | |||
S3-202838 | LS on Security Requirements for Sidelink/PC5 Relays | LS in | S2-2004750 |
S3-101-e AI: 5.9 |
postponed | [WTS] [JSN] | |||
S3-202839 | LS on IP address to GPSI translation | LS in | S2-2005923 |
S3-101-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-202840 | LS on System support for Multi-USIM devices |
LS in LS reply in S3-203356, S3-203356 |
S2-2006011 |
S3-101-e AI: 5.19 |
replied to | [WTS] [JSN] | |||
S3-202841 | LS on method for collection of data from the UE | LS in | S2-2006292 |
S3-101-e AI: 5.16 |
postponed | [WTS] [JSN] | |||
S3-202842 | LS on Clarification on AAA-Server address | LS in | C4-203452 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-202843 | LS Response on Clarification on AAA-Server address | LS in | S2-2007826 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-202844 | LS on NG-RAN broadcast of Onboarding Network information in the SIB |
LS in LS reply in S3-203402, S3-203402 |
S2-2007849 |
S3-101-e AI: 5.12 |
replied to | [WTS] [JSN] | |||
S3-202845 | LS on authorization to access data |
LS in LS reply in S3-203368, S3-203368 |
S2-2007931 |
S3-101-e AI: 5.16 |
replied to | [WTS] [JSN] | |||
S3-202846 | LS on SA2 progress on UE-to-Network Relay and UE-to-UE Relay | LS in | S2-2007945 |
S3-101-e AI: 5.9 |
noted | [WTS] [JSN] | |||
S3-202847 | LS on Reference point interface names for AKMA | LS in | S2-2008003 |
S3-101-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-202848 | Regulatory LI compliance of AKMA |
LS in LS reply in S3-202950 |
S3i200477 |
S3-101-e AI: 4.7 |
replied to | [WTS] [JSN] | |||
S3-202849 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-203360 |
S6-202008 |
S3-101-e AI: 5.8 |
replied to | [WTS] [JSN] | |||
S3-202850 | Reply to LS on Resynchronisations | LS in | ETSI SAGE |
S3-101-e AI: 5.5 |
postponed | [WTS] [JSN] | |||
S3-202851 | Observations and questions on 256-bit security goals |
LS in LS reply in S3-203500 |
ETSI SAGE |
S3-101-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-202852 | Independent evaluation of SNOW V | LS in | ETSI SAGE |
S3-101-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-202853 | LS on Physical layer assisted lightweight AKA (PL-AKA) protocol for the Internet of things |
LS in LS reply in S3-203492 |
ITU-T SG17 |
S3-101-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-202854 | Comments on physical layer assisted lightweight AKA (PL-AKA) protocol for the Internet of things | LS in | ETSI SAGE |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202855 | LS on threats of service disruption, SIP message alteration and content eavesdropping in 5G networks |
LS in LS reply in S3-203498 |
ITU-T SG17 |
S3-101-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-202856 | LS on Security requirements for vertical services supporting Ultra Reliable and Low Latency Communication (URLLC) in the 5G non-public networks | LS in | ITU-T SG17 |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202857 | LS on SG17 new work item 'Security Methodology for Zero-Touch Massive IoT Deployment | LS in | ITU-T SG17 |
S3-101-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-202858 | LS on SG17 new work item “Security aspect on electric vertical take-off and landing (eVTOL) vehicle” | LS in | ITU-T SG17 |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202859 | LS on draft ITU-T X.nsom-sec ‘Security requirements and architecture for network slice management and orchestration’ | LS in | ITU-T SG17 |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202860 | LS on the stage 2 aspects of MINT (SP-200654 / C1-205332) | LS in | SP-200880 |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202861 | LS on 5G GUTI re-allocation | LS in | SP-200883 |
S3-101-e AI: 4.8 |
noted | [WTS] [JSN] | |||
S3-202862 | LS on Rel-17 schedule | LS in | SP-200888 |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202863 | Skeleton for MUSIM TR | other | Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
approved | [WTS] [JSN] | |||
S3-202864 | TR 33.847- new KI on security policy handling in ProSe UE2NW relay | pCR | Samsung, LG Electronics, InterDigital, CableLabs | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-202865 | TR 33.847-Solution for secondary authentication in relay communication |
pCR revised to S3-203351 |
LG Electronics Inc. | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202866 | pCR Update to solution #20 (6.20.2.5.1) Trust Anchors in UE of TR 33.809 | pCR | Deutsche Telekom AG | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202867 | New template for the Terms of Reference (ToR) | other | SA WG3 Chair |
S3-101-e AI: 7 |
noted | [WTS] [JSN] | |||
S3-202868 | New WID on removal AKMA from Rel-16 | WID new | China Mobile | Rel-16 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] | ||
S3-202869 | CR Removal of AKMA changes to TS 33.501 in Rel-16 | CR | China Mobile | 33.501 16.4.0 CR#958 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202870 | CR Removal of AKMA changes to TS 33.220 in Rel-16 |
CR revised to S3-203488 |
China Mobile | 33.22 16.2.0 CR#205 catF | DUMMY | Rel-16 |
S3-101-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-202871 | Revised WID of AKMA |
WID revised revised to S3-203485 |
China Mobile | DUMMY | Rel-17 |
S3-101-e AI: 4.7 |
revised | [WTS] [JSN] | |
S3-202872 | CR for AKMA changes to TS 33.501 in Rel-17 |
CR revised to S3-203486 |
China Mobile International Ltd | 33.501 16.4.0 CR#959 catB | AKMA | Rel-17 |
S3-101-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-202873 | CR for AKMA changes to TS 33.220 in Rel-17 |
CR revised to S3-203487 |
China Mobile | 33.22 16.2.0 CR#206 catB | AKMA | Rel-17 |
S3-101-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-202874 | TR 33.854 Update for solution#3 |
pCR revised to S3-203352 |
InterDigital, Europe, Ltd. | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-202875 | TR 33.854 Update for solution#4 |
pCR revised to S3-203353 |
InterDigital, Europe, Ltd. | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-202876 | TR 33.854 Update for solution#5 |
pCR revised to S3-203354 |
InterDigital, Europe, Ltd. | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-202877 | TR 33.854 Update for KI#2 | pCR | InterDigital, Europe, Ltd. | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-202878 | A threat of service disruption due to unprotected RRC messages reported by 5G Security Forum in South Korea | discussion | SK Telecom |
S3-101-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-202879 | A threat on IMS confidentiality reported by 5G Security Forum in South Korea | discussion | SK Telecom |
S3-101-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-202880 | [33.180] R16 Fix terminology |
CR revised to S3-203551 |
Airbus | 33.18 16.4.0 CR#151 catF | MCXSec | Rel-16 |
S3-101-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-202881 | [33.180] R17 Fix terminology |
CR revised to S3-203552 |
Airbus | 33.18 17.0.0 CR#152 catA | MCXSec | Rel-17 |
S3-101-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-202882 | Corrections on security establishment | CR | InterDigital, Europe, Ltd. | 33.536 16.1.0 CR#17 catF | eV2XARC | Rel-16 |
S3-101-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-202883 | Re-using of access token in indirect communication with delegated discovery |
CR revision of S3-201802 revised to S3-203499 |
Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#9071 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-202884 | Security policy handling | CR | Nokia, Nokia Shanghai Bell | 33.536 16.1.0 CR#18 catF | eV2XARC | Rel-16 |
S3-101-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-202885 | Resolution of editor notes related to usage of MSK vs. EMSK. | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-202886 | [DRAFT] Reply-LS on NG-RAN broadcast of Onboarding Network information in the SIB. |
LS out LS is reply to LS (S2-2007849) on NG-RAN broadcast of Onboarding Network information in the SIB. source LS: S2-2007849 LS To: SA2 |
Nokia, Nokia Shanghai Bell | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
merged | [WTS] [JSN] | |
S3-202887 | Error correction and clarification of Annex O |
CR revised to S3-203507 |
CableLabs | 33.501 16.4.0 CR#960 catF | 5WWC | Rel-16 |
S3-101-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-202888 | Updates to solution #3 |
pCR revised to S3-203468 |
CableLabs | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-202889 | NAS COUNT storage for multiple PLMN |
CR revised to S3-203476 |
Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#961 catF | 5GS_Ph1-SEC, TEI16 | Rel-16 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-202890 | New solution for Key Issue #1 with enhanced security of KAUSF |
pCR revised to S3-203469 |
CableLabs | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-202891 | Additions to Key Issue#7 on MitM detection | pCR | Nokia, Nokia Shanghai Bell | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-202892 | Solution proposal for KI#7MitM detection | pCR | Nokia, Nokia Shanghai Bell | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-202893 | Updates to solution #20 (6.20.4) |
pCR revised to S3-203470 |
CableLabs, Interdigital, Apple, Deutsche Telekom AG, Intel, Rogers Communications, Philips | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-202894 | Key Issue on Generic User consent | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-202895 | LS Reply to SA2 on System support for MUSIM devices |
LS out LS is reply to S2-2006011 LS To: SA2 revised to S3-203356 |
Nokia, Nokia Shanghai Bell |
S3-101-e AI: 5.19 |
revised | [WTS] [JSN] | |||
S3-202896 | Editoral modifications in TR 33.839 | pCR | CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-202897 | Update key issue #1 in TR 33.839 |
pCR revised to S3-203433 |
CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-202898 | Update Key issue #2 in TR 33.839 |
pCR revised to S3-203434 |
CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-202899 | Update Solution #6 in TR 33.839 |
pCR revised to S3-203435 |
CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-202900 | Update the pre-condition in clause 4.2.2.1.1, 4.2.2.1.2, 4.2.2.1.9, 4.2.2.1.10 and 4.2.2.1.11 | CR | ZTE Corporation | 33.511 16.5.0 CR#18 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
not pursued | [WTS] [JSN] |
S3-202901 | Clarification of RID in clause 6.1 for AKMA | CR | ZTE Corporation | 33.535 16.1.0 CR#35 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202902 | A new A-KID derivation after a new primary authentication | CR | ZTE Corporation | 33.535 16.1.0 CR#36 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202903 | AAnF selection by AF | CR | ZTE Corporation | 33.535 16.1.0 CR#37 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202904 | AKMA key lifetime expiration in clause 5.2 | CR | ZTE Corporation | 33.535 16.1.0 CR#38 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202905 | Kakma and A-KID refresh in clause 6.1 | CR | ZTE Corporation | 33.535 16.1.0 CR#39 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-202906 | Kausf storing in AUSF | CR | ZTE Corporation | 33.535 16.1.0 CR#40 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-202907 | Resolution of editor's note on other parameter in clause 6.3 | CR | ZTE Corporation | 33.535 16.1.0 CR#41 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202908 | Rewording Kaf refresh | CR | ZTE Corporation | 33.535 16.1.0 CR#42 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202909 | the lifetime of KAF expiration | CR | ZTE Corporation | 33.535 16.1.0 CR#43 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202910 | UDM notifies AAnF AKMA context removal | CR | ZTE Corporation | 33.535 16.1.0 CR#44 catB | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202911 | Discussion on New WID on security of Access Traffic Steering, Switch and Splitting (ATSSS) support in 5GS | discussion | ZTE Corporation | Rel-17 |
S3-101-e AI: 4.24 |
noted | [WTS] [JSN] | ||
S3-202912 | New WID on security of Access Traffic Steering, Switch and Splitting (ATSSS) support in 5GS | WID new | ZTE Corporation | Rel-17 |
S3-101-e AI: 4.24 |
noted | [WTS] [JSN] | ||
S3-202913 | Discussion on key issue 4.1 in TR 33.846 | discussion | ZTE Corporation | FS_AUTH_ENH | Rel-17 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] | |
S3-202914 | New solution for key issue# 4.1 in TR 33.846 | pCR | ZTE Corporation | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-202915 | Conclusion for Key Issue #4.1 in TR 33.846 | pCR | ZTE Corporation | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-202916 | Solution of Mitigation against the SUPI replay attack | pCR | ZTE Corporation | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-202917 | Update solution#2.1 in TR 33.846 | pCR | ZTE Corporation | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-202918 | Update solution 14 in TR 33.839 | pCR | ZTE Corporation | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-202919 | Add some abbreviations for TR 33.850 |
pCR revised to S3-203422 |
ZTE Corporation | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-202920 | New solution for key issue#1 in TR 33.850 |
pCR revised to S3-203423 |
ZTE Corporation | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-202921 | Update solution#3 in TR 33.850 |
pCR revised to S3-203424 |
ZTE Corporation | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-202922 | New solution on UE onboarding for SNPN with AAA-S as DCS |
pCR revised to S3-203438 |
ZTE Corporation | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-202923 | New solution on UE onboarding for SNPN with UDM as DCS |
pCR revised to S3-203439 |
ZTE Corporation | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-202924 | Reply LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN |
LS out LS is reply to S2-2004385/S3-202837 LS To: SA2 |
ZTE Corporation | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
merged | [WTS] [JSN] | |
S3-202925 | Architecture and security assumptions of AMF re-allocation | pCR | ZTE Corporation | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-202926 | LS on Clarification of requirements and architecture impacts by network slice isolation |
LS out LS To: SA1, SA2 |
ZTE Corporation | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-202927 | Update Solution #10 in TR 33.839 |
pCR revised to S3-203437 |
CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-202928 | Update Solution #15 in TR 33.839 | pCR | CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202929 | Discussion on LS on NG-RAN broadcast of Onboarding Network information in the SIB | discussion | Intel Corporation (UK) Ltd |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-202930 | Reply to LS S2-2007849 on NG-RAN broadcast of Onboarding Network information in the SIB |
LS out LS is reply to S2-2007849 LS To: SA2 |
Intel Corporation (UK) Ltd |
S3-101-e AI: 5.12 |
merged | [WTS] [JSN] | |||
S3-202931 | Authentication and Authorization Framework for EDGE-4 interfaces using Primary authentication and proxy interface |
pCR revised to S3-203412 |
Intel Corporation (UK) Ltd | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-202932 | Updates to Solution 4 |
pCR revised to S3-203413 |
Intel Corporation (UK) Ltd | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-202933 | Updates to Solution 12 |
pCR revised to S3-203414 |
Intel Corporation (UK) Ltd | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-202934 | Introduction for MUSIM TR | other | Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
merged | [WTS] [JSN] | |||
S3-202935 | Key Issue for Busy Indication |
other revised to S3-203408 |
Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
revised | [WTS] [JSN] | |||
S3-202936 | Privacy while roaming | other | Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
noted | [WTS] [JSN] | |||
S3-202937 | Key Issue for UE and Paging Server Communication |
other revised to S3-203409 |
Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
revised | [WTS] [JSN] | |||
S3-202938 | [DRAFT] Reply to LS S2-2006011 on System support for Multi-USIM devices |
LS out LS To: SA2 |
Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
merged | [WTS] [JSN] | |||
S3-202939 | Solution to UE onboarding for non-public networks | pCR | Intel Corporation (UK) Ltd | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-202940 | Scope for MUSIM TR |
other revised to S3-203410 |
Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
revised | [WTS] [JSN] | |||
S3-202941 | NAS Based Solution for Busy Indication | other | Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
noted | [WTS] [JSN] | |||
S3-202942 | Security for Paging Notifications | other | Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
noted | [WTS] [JSN] | |||
S3-202943 | Detection of MiTM False Base Station | pCR | Huawei, HiSilicon | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-202944 | Corrections of clause 6.1 |
CR revised to S3-203535 |
CATT | 33.535 16.1.0 CR#45 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-202945 | Editorial modifications of AKMA | CR | CATT | 33.535 16.1.0 CR#46 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202946 | NAS uplink COUNT used for AS SMC at radio bearer establishment | discussion | MediaTek Inc. | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
noted | [WTS] [JSN] | |
S3-202947 | Correct NAS uplink COUNT for KgNB/KeNB derivation |
CR revised to S3-210073 |
MediaTek Inc. | 33.501 16.4.0 CR#962 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-202948 | Correction to inter-AMF mobility key derivation function |
CR revised to S3-210415 |
MediaTek Inc. | 33.501 16.4.0 CR#963 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-202949 | New Key issue on reporting of base station involved in cyber attack | pCR | NEC | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-202950 | Reply LS on Regulatory LI compliance of AKMA |
LS out LS is reply to S3-202848 LS To: SA3-LI |
China Mobile |
S3-101-e AI: 4.7 |
approved | [WTS] [JSN] | |||
S3-202951 | Handling of new Kausf during authentication procedure | CR | NEC | 33.501 16.4.0 CR#964 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-202952 | Clarification on cross-layer indication triggered by updating the security context |
CR revised to S3-203480 |
Huawei, Hisilicon | 33.536 16.1.0 CR#19 catF | eV2XARC | Rel-16 |
S3-101-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-202953 | Propose to improve the user plane security policy handling logic |
CR revised to S3-203481 |
Huawei, Hisilicon | 33.536 16.1.0 CR#20 catF | eV2XARC | Rel-16 |
S3-101-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-202954 | Update Sol#3 to resolve EN | pCR | Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-202955 | Update Sol#4 to resolve EN | pCR | Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-202956 | Update to Sol#7 to address EN and add evaluation |
pCR revised to S3-203425 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202957 | Propose to resolve EN in the security requirement of KI#12 |
pCR revised to S3-203426 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202958 | New solution to mitigate SUPI guessing and SUCI replay attack | pCR | Huawei, Hisilicon | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-202959 | updating the IAB architecture in key issue#4.1 | pCR | Huawei, Hisilicon | 33.824 0.9.0 | FS_NR_IAB_Sec | Rel-16 |
S3-101-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-202960 | updating the RLF key issue | pCR | Huawei, Hisilicon | 33.824 0.9.0 | FS_NR_IAB_Sec | Rel-16 |
S3-101-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-202961 | key issue on security in Inter-CU handover procedure | pCR | Huawei, Hisilicon | 33.824 0.9.0 | FS_NR_IAB_Sec | Rel-16 |
S3-101-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-202962 | updating the Scope | pCR | Huawei, Hisilicon | 33.824 0.9.0 | FS_NR_IAB_Sec | Rel-16 |
S3-101-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-202963 | Adding details of AKMA key generation in the UE |
CR revised to S3-203482 |
Huawei, Hisilicon | 33.535 16.1.0 CR#47 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-202964 | new key issue on the security protection between content provider and 5GC |
pCR revised to S3-203427 |
Huawei, Hisilicon | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-202965 | new solution on the security protection between content provider and 5GC |
pCR revised to S3-203428 |
Huawei, Hisilicon | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-202966 | Solving the editoral note in solution 2 |
pCR revised to S3-203429 |
Huawei, Hisilicon | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-202967 | Adding AAnF selection | CR | Huawei, Hisilicon | 33.535 16.1.0 CR#48 catF | AKMA | Rel-17 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202968 | security solution for UE-to-Network Relay based on Layer 2 Relay |
pCR revised to S3-203430 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202969 | Missing details in clause 4 | pCR | Huawei, Hisilicon | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-202970 | New Key issue on supporting security flexibility | pCR | Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-202971 | Delete Editor's Note in solution 9 |
pCR revised to S3-203431 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-202972 | living CR to TS 33.511 | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202973 | Living CR toTR33.926 for eSCAS |
draftCR revised to S3-203512 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-202974 | Living CR to TS33.117 |
draftCR revised to S3-203513 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-202975 | skeleton of NSSAAF SCAS |
pCR revised to S3-203514 |
Huawei, Hisilicon | 33.326 0.0.0 | SCAS_5G_NSSAAF | Rel-17 |
S3-101-e AI: 4.21 |
revised | [WTS] [JSN] |
S3-202976 | The scope of NSSAAF SCAS | pCR | Huawei, Hisilicon | 33.326 0.0.0 | SCAS_5G_NSSAAF | Rel-17 |
S3-101-e AI: 4.21 |
approved | [WTS] [JSN] |
S3-202977 | Threat analysis on no new created child SA | pCR | Huawei, Hisilicon | 33.52 0.1.0 | SCAS_5G_N3IWF | Rel-17 |
S3-101-e AI: 4.19 |
noted | [WTS] [JSN] |
S3-202978 | Check whether the N3IWF creats a child SA for PDU session | pCR | Huawei, Hisilicon | 33.52 0.1.0 | SCAS_5G_N3IWF | Rel-17 |
S3-101-e AI: 4.19 |
noted | [WTS] [JSN] |
S3-202979 | UP IP-Update solution #11 |
pCR revised to S3-203454 |
Huawei, Hisilicon | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-202980 | LS to RAN3 on Progress on security study for disaggregated gNB |
LS out LS To: RAN3 |
Huawei, Hisilicon | FS_disagg_gNB_Sec | Rel-17 |
S3-101-e AI: 5.13 |
noted | [WTS] [JSN] | |
S3-202981 | CU-UPs key separation | pCR | Huawei, Hisilicon, China Telecom | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-101-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-202982 | Discussion Paper for virtualization SCAS | pCR | Huawei, Hisilicon | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
withdrawn | [WTS] [JSN] |
S3-202983 | New solution for KI#3 |
pCR revised to S3-203364 |
Philips International B.V., CableLabs | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-202984 | Clarification Solution #23 | pCR | Philips International B.V. | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-202985 | Traffic_Key_Update_Need_And_Solution |
pCR revised to S3-203361 |
Philips International B.V. | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-202986 | Handling of security parameters during authentication procedure | CR | NEC | 33.501 16.4.0 CR#965 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-202987 | New Solution on Authentication for UE onboarding for SNPN | pCR | Huawei, Hisilicon | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-202988 | Solution Update for Solution #5 | pCR | Huawei, Hisilicon | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-202989 | Discussion for Provisioning of Credentials | discussion | Huawei, Hisilicon, China mobile | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] | ||
S3-202990 | Clarification on Key Issue #2 | pCR | Huawei, Hisilicon, Ericsson, Intel, China Mobile, Philips | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-202991 | New Key Issue on Provisioning of PNI-NPN credentials | pCR | Huawei, Hisilicon, China Mobile, Philips | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-202992 | LS on Clarification on the Scope of eNPN for Provisioning Aspect |
LS out LS To: SA |
Huawei, Hisilicon |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-202993 | Add Security Requirement for Key Issue #2.1 |
pCR revised to S3-203449 |
Huawei, Hisilicon | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-202994 | LS on Mitigation Aspects for Cyber-Attack Detection |
LS out LS To: SA2 |
Huawei, Hisilicon |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] | |||
S3-202995 | Scope of eNA Security |
pCR revised to S3-203450 |
Huawei, Hisilicon | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-202996 | Scope of User Consent for 3GPP Services |
pCR revised to S3-203451 |
Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-202997 | System Architecture for User Consent for 3GPP Services in 5G System | pCR | Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-202998 | Background for User Consent | pCR | Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-202999 | Consideration Factors for User Consent | pCR | Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203000 | Add two Use Cases for UC3S | pCR | Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203001 | Structuring key issues per SID objectives | pCR | Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203002 | Adding general clause to key issue part | pCR | Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203003 | Reword the reference description | pCR | Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-203004 | Authentication procedure during Xn handover procedure |
CR revised to S3-203474 |
NEC | 33.501 16.4.0 CR#966 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
revised | [WTS] [JSN] |
S3-203005 | DISC Authentication procedure during Xn handover procedure | discussion | NEC | Rel-16 |
S3-101-e AI: 4.25 |
noted | [WTS] [JSN] | ||
S3-203006 | Draft LS to CT6 on the NAS COUNTs storage |
LS out LS To: CT6 revised to S3-203534 |
Apple | Rel-16 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] | ||
S3-203007 | 5GFBS-Edotorial change in Clause 4 | pCR | Apple | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-203008 | 5GFBS- Edotorial change in Clause 5.2.1 |
pCR revised to S3-203452 |
Apple | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-203009 | UPIP-EN addressing in solution#19 | pCR | Apple | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-203010 | UPIP-Evaluation in Solution#18 |
pCR revised to S3-203453 |
Apple | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203011 | MEC-Addressing the EN on key hierachy in solution#2 | pCR | Apple | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203012 | MEC-Addressing the EN on EEC ID in solution#2 | pCR | Apple | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203013 | MEC-Adding the ENs in solution#7 | pCR | Apple | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203014 | ProSe-Modification in key issue#1 |
pCR revised to S3-203448 |
Apple | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203015 | ProSe-Modification in key issue#6 | pCR | Apple | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203016 | pCR to TR33.847-Rapporteur cleaning up work | pCR | CATT | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203017 | pCR to TR33.847-Update Solution#3 for removing some ENs |
pCR revised to S3-203440 |
CATT | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203018 | TR 33.845: solution #4 | pCR | THALES, KPN | 33.845 0.5.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-203019 | pCR to TR33.847-Update Solution#4 for removing some ENs | pCR | CATT | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203020 | Secondary authentication revocation rel15 |
CR revised to S3-203515 |
Huawei, HiSilicon | 33.501 15.10.0 CR#967 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-203021 | Secondary authentication revocation rel16 |
CR revised to S3-203516 |
Huawei, HiSilicon | 33.501 16.4.0 CR#968 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-203022 | Slice privacy protection in NSSAA related procedure | CR | Huawei, HiSilicon | 33.501 16.4.0 CR#969 catF | eNS | Rel-16 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203023 | Correction to the Nnssaaf_NSSAA_RevocationNotification services | CR | Huawei, HiSilicon | 33.501 16.4.0 CR#970 catF | eNS | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203024 | clean up to the Nnssaaf_NSSAA services | CR | Huawei, HiSilicon | 33.501 16.4.0 CR#971 catF | eNS | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203025 | Aware of AF‘s AKMA service capability in the UE | CR | Huawei, HiSilicon | 33.535 16.1.0 CR#49 catF | AKMA | Rel-17 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-203026 | Solution on key management for UE-to-network relay |
pCR revised to S3-203432 |
Huawei, HiSilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203027 | Add reference TR33.867 and clean up |
pCR revised to S3-203441 |
Huawei, HiSilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-203028 | Security between the SMF and LDNSR | pCR | Huawei, HiSilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203029 | Storage of the AKMA keys in the UE | CR | THALES | 33.535 16.1.0 CR#50 catB | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-203030 | pCR to TR33.840- Add missing references | pCR | CATT | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-101-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-203031 | MBS:Updates to the solutions for 5G MBS authorization revocation | pCR | Huawei, Hisilicon | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-203032 | EC:New key issue on protecting UPF in customer network | pCR | Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-203033 | EC: New Key issue on user privacy for UPF in customer network | pCR | Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-203034 | EC: New key issue on N4 protection for UPF in customer network | pCR | Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-203035 | NPN: New solution to key issue #1 | pCR | Huawei, Hisilicon | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203036 | NPN: Updates to key issue #1 | pCR | Huawei, Hisilicon | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203037 | AKMA: Adding missing service definition |
CR revised to S3-203518 |
Huawei, Hisilicon | 33.535 16.1.0 CR#51 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-203038 | LS reply on clarification on AAA server address |
LS out LS To: CT4, SA2 |
Huawei, Hisilicon | Rel-16 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-203039 | SHA-1 deprecation in GBA |
CR revised to S3-203519 |
Huawei, Hisilicon | 33.22 16.2.0 CR#207 catF | TEI17 | Rel-17 |
S3-101-e AI: 4.25 |
revised | [WTS] [JSN] |
S3-203040 | AMFREAL: Description of AMF reallocation procedure |
pCR revised to S3-203445 |
Huawei, Hisilicon | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203041 | AMFREAL: New key issue on registration failure with AMF reallocation | pCR | Huawei, Hisilicon | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-203042 | AMFREAL: New solution to registration failure with AMF reallocation |
pCR revised to S3-203446 |
Huawei, Hisilicon | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203043 | New requirement on key issue #2 of TR 33.851 | pCR | Huawei, Hisilicon | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203044 | New solution on key issue #2 of TR 33.851 | pCR | Huawei, Hisilicon | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203045 | EC: Editor notes removal |
pCR revised to S3-203457 |
Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-203046 | NPN: New solution to key issue #1 | pCR | Huawei, Hisilicon | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203047 | Discussion on MITM attack in vertical LAN | discussion | Huawei, Hisilicon | Rel-16 |
S3-101-e AI: 4.25 |
noted | [WTS] [JSN] | ||
S3-203048 | LS on MITM Attack in CAG |
LS out LS To: SA2 |
Huawei, Hisilicon | Rel-16 |
S3-101-e AI: 4.25 |
noted | [WTS] [JSN] | ||
S3-203049 | Input parameters of access token request addition and verification |
CR revised to S3-203520 |
Huawei, Hisilicon | 33.501 16.4.0 CR#972 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-203050 | NF information addition in SBA certificate profile | CR | Huawei, Hisilicon | 33.31 16.5.0 CR#114 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-203051 | Clarification on the security policy handling |
CR revised to S3-203521 |
Huawei, Hisilicon | 33.536 16.1.0 CR#21 catF | eV2XARC | Rel-16 |
S3-101-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-203052 | Discussion on verification of PLMN ID | discussion | Huawei, Hisilicon | Rel-15 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-203053 | Clarification on PLMN ID verification in Rel15 | CR | Huawei, Hisilicon | 33.501 15.10.0 CR#973 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203054 | Clarification on PLMN ID verification in Rel16 | CR | Huawei, Hisilicon | 33.501 16.4.0 CR#974 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203055 | Reply LS on Misalignments on HTTP message format over N32-f |
LS out LS To: CT4 revised to S3-203522 |
Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-203056 | Modification policy clarification in Rel15 | CR | Huawei, Hisilicon | 33.501 15.10.0 CR#975 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203057 | Modification policy clarification in Rel16 | CR | Huawei, Hisilicon | 33.501 16.4.0 CR#976 catF | 5GS_Ph1-SEC, TEI16 | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203058 | Clarification on security policy configuration for TSC services | CR | Huawei, Hisilicon | 33.501 16.4.0 CR#977 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-203059 | Threats related to security enforcement configuration for TSC services |
draftCR revised to S3-203524 |
Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-203060 | New test case on security enforcement configuration for TSC services |
draftCR revised to S3-203525 |
Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-203061 | 5G ProSe: New key issue on UE-to-UE Relay or UE-to-Network Relay selection | pCR | Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-203062 | 5G ProSe: New solution on UE-to-UE Relay or UE-to-Network Relay selection | pCR | Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-203063 | 5G ProSe: New solution on e2e authentication between two UE2 in the UE-to-UE relay scenario |
pCR revised to S3-203442 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203064 | EC: New solution on Edge Data Network authentication and authorization for key issue #4 | pCR | Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203065 | EC: New solution on authorization during Edge Data Network change |
pCR revised to S3-203443 |
Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-203066 | EC: new solution on exposure for key issue #8 | pCR | Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203067 | EC: Framework on the EEC authentication and authorization |
pCR revised to S3-203444 |
Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-203068 | Clarification on security policy configuration for 5G LAN services | CR | Huawei, Hisilicon | 33.501 16.4.0 CR#978 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-203069 | Threats related to security enforcement configuration for 5G LAN services |
draftCR revised to S3-203526 |
Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-203070 | New test case on security enforcement configuration for 5G LAN services |
draftCR revised to S3-203527 |
Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-203071 | Discussion paper on TAU reject issue during MME handover | discussion | Huawei, Hisilicon | Rel-15 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-203072 | IMS SCAS: living doc for the threats |
draftCR revised to S3-203528 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] | |
S3-203073 | IMS SCAS: new test case on synchronization failure handling |
pCR revised to S3-203529 |
Huawei, Hisilicon | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-203074 | IMS SCAS: adding threats related to IMS signalling transport |
draftCR revised to S3-203530 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] | |
S3-203075 | IMS SCAS: new test case on the IMS signaling protection |
pCR revised to S3-203531 |
Huawei, Hisilicon | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-203076 | IMS SCAS: adding threats related to Resynchronization failure |
draftCR revised to S3-203532 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] | |
S3-203077 | IMS SCAS: Adding the general requirements |
pCR revised to S3-203533 |
Huawei, Hisilicon | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-203078 | IMS SCAS: Adding the assets and threats of the new NFs | draftCR | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
noted | [WTS] [JSN] | |
S3-203079 | Reply LS to ETSI SAGE on use of 256-bit block Rijndael in Milenage-256 |
LS out LS is reply to S3-202823 LS To: ETSI SAGE, TCA revised to S3-203550 |
THALES | Rel-17 |
S3-101-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-203080 | TR 33.846: evaluation of solution #2.1 | pCR | THALES | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203081 | TR 33.846: evaluation of solution #2.2 |
pCR revised to S3-203393 |
THALES | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-203082 | TR 33.846: evaluation of solution #2.4 | pCR | THALES | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203083 | TR 33.846: conclusion for Key Issue #2.1 | pCR | THALES | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-203084 | TR 33.846: conclusion for Key Issue #4.1 | pCR | THALES | 33.846 0.8.0 | FS_LISE, FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-203085 | Correction of test case for access token verification failure handling in different PLMN |
CR revised to S3-203539 |
Nokia, Nokia Shanghai Bell | 33.117 16.5.0 CR#66 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-203086 | Reference of general SBA/SBI aspect in 33.512 | CR | Nokia, Nokia Shanghai Bell | 33.512 16.3.0 CR#8 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-203087 | A solution for groupcast security and privacy |
pCR revised to S3-203462 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203088 | Addressing EN in KI#2: scope of pairing authorization | pCR | Huawei, HiSilicon | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-203089 | Addressing EN in KI#3: scope of TPAE A&A | pCR | Huawei, HiSilicon | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-203090 | Addressing EN in KI#6: scope of RID security protection | pCR | Huawei, HiSilicon | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-203091 | Addressing EN in KI#7: scope of C2 Security | pCR | Huawei, HiSilicon | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-203092 | A solution to TPAE A&A | pCR | Huawei, HiSilicon | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-203093 | A solutin to UAV and UAV-C pairing authorization |
pCR revised to S3-203387 |
Huawei, HiSilicon, InterDigital | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-203094 | A solution to RID information protection | pCR | Huawei, HiSilicon | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-203095 | A solution to C2 communication security | pCR | Huawei, HiSilicon | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-203096 | Discussion paper for Rel17 SID on network slicing security | discussion | Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT, China Unicom, China Mobile, InterDigital | Rel-17 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] | ||
S3-203097 | Rel17 SID on network slice security | SID new | Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT, China Unicom, China Mobile, InterDigital | Rel-17 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] | ||
S3-203098 | Discussion on SN-ID in NSSAA | discussion | Huawei, HiSilicon | eNS | Rel-16 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-203099 | Serving network ID in NSSAA | CR | Huawei, HiSilicon | 33.501 16.4.0 CR#979 catF | eNS | Rel-16 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203100 | Discussion on validity period of NSSAA results | discussion | Huawei, HiSilicon | eNS | Rel-16 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-203101 | validity peirod of NSSAA result | CR | Huawei, HiSilicon | 33.501 16.4.0 CR#980 catF | eNS | Rel-16 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203102 | Clarification on binding of NSSAI and UE ID at AAA-S | CR | Huawei, HiSilicon | 33.501 16.4.0 CR#981 catF | eNS | Rel-16 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203103 | Reference of general SBA/SBI aspect in 33.513 | CR | Nokia, Nokia Shanghai Bell | 33.513 16.1.0 CR#3 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-203104 | Reference of general SBA/SBI aspect in 33.514 | CR | Nokia, Nokia Shanghai Bell | 33.514 16.3.0 CR#4 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-203105 | Reference of general SBA/SBI aspect in 33.515 | CR | Nokia, Nokia Shanghai Bell | 33.515 16.2.0 CR#6 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-203106 | Addessing EN on transmitting NSSAI to AAA | CR | China Mobile | 33.501 16.4.0 CR#982 catF | eNS | Rel-16 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203107 | Reference of general SBA/SBI aspect in 33.516 | CR | Nokia, Nokia Shanghai Bell | 33.516 16.1.0 CR#2 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-203108 | Reference of general SBA/SBI aspect in 33.519 | CR | Nokia, Nokia Shanghai Bell | 33.519 16.1.0 CR#3 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-203109 | Enforcement of password change after initial login R15 | CR | Nokia, Nokia Shanghai Bell | 33.117 15.5.0 CR#67 catF | SCAS_eNB | Rel-15 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-203110 | Enforcement of password change after initial login R16 | CR | Nokia, Nokia Shanghai Bell | 33.117 16.5.0 CR#68 catA | SCAS_eNB | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-203111 | SCAS IMS: Removal of the sub-clause for SBA |
pCR revised to S3-203540 |
Nokia, Nokia Shanghai Bell | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-203112 | New WID on adapting BEST for use in 5G networks |
WID new revised to S3-203484 |
KPN N.V. | Rel-17 |
S3-101-e AI: 4.24 |
revised | [WTS] [JSN] | ||
S3-203113 | Threat of bidding down attack on security association |
pCR revised to S3-203541 |
Nokia, Nokia Shanghai Bell | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-203114 | SCAS IMS: New Sub-Test Case against Bidding-down on Security Association |
pCR revised to S3-203542 |
Nokia, Nokia Shanghai Bell | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-203115 | Updated Threat Analysis of Incorrect Verification of Access Tokens |
draftCR revised to S3-203543 |
Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-203116 | [DRAFT] LS on DCS mechanisms to authenticate the UE |
LS out LS To: SA2 |
Ericsson | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] | ||
S3-203117 | Update of the Test Case for Access Token Verification Failure Handling |
draftCR revised to S3-203544 |
Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-203118 | Threat analysis of inter-PLMN routing using the incorrect reference | draftCR | Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203119 | Test case for correct handling of inter-PLMN routing | draftCR | Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203120 | Solution to address the Key issue #2.2 in TR 33.846 | pCR | China Mobile | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-203121 | Update to Key issue #2.2 on SUCI Replay in TR 33.846 | pCR | China Mobile | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-203122 | Need a unified solution to the key issue #2.1 and key issue #4.1 in TR 33.846 | discussion | China Mobile | Rel-17 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] | ||
S3-203123 | Propose a conclusion for the key issue #2.1 and key issue #4.1 in TR 33.846 | pCR | China Mobile | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-203124 | Requirements to TR 33.866 on key issue 5.2.1 Cyber-attacks Detection | pCR | China Mobile | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-203125 | Proposal to add introduction and NWDAF-specific security functional requirements |
pCR revised to S3-203489 |
China Mobile | 33.521 0.1.0 | SCAS_5G_NWDAF | Rel-17 |
S3-101-e AI: 4.18 |
revised | [WTS] [JSN] |
S3-203126 | Proposal to add security requirement and test cases for hardening about NWDAF | pCR | China Mobile | 33.521 0.1.0 | SCAS_5G_NWDAF | Rel-17 |
S3-101-e AI: 4.18 |
approved | [WTS] [JSN] |
S3-203127 | Proposal to add security requirement and test cases for basic vulnerability testing about NWDAF | pCR | China Mobile | 33.521 0.1.0 | SCAS_5G_NWDAF | Rel-17 |
S3-101-e AI: 4.18 |
approved | [WTS] [JSN] |
S3-203128 | Editorial correction on TR 33.818 |
pCR revised to S3-203344 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203129 | Adding hardening requirements for GVNP of type 1 |
pCR revised to S3-203346 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203130 | Adding hardening requirements for GVNP of type 2 |
pCR revised to S3-203347 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203131 | Adding hardening requirements for GVNP of type 3 | pCR | China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-203132 | Adding basic vulnerability testing requirements for GVNP |
pCR revised to S3-203348 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203133 | Adding vendor development and product lifecycle processes and test laboratory accreditation into Clause 6 | pCR | China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-203134 | Adding evaluation and SCAS instantiation into clause 7 | pCR | China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-203135 | Adding test case into clause 5.2.5.5.8.5.1 |
pCR revised to S3-203349 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203136 | Adding test case into clause 5.2.5.6.6.1 | pCR | China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203137 | Adding impact to existing SECAM-SCAS documents into clause 8.1 | pCR | China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-203138 | proposal for way forward | pCR | China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-203139 | Key issue on authentication and authorization between MSGin5G Gateway Client and MSGin5G server | pCR | China Mobile | 33.862 0.1.0 | FS_SEC_5GMSG | Rel-17 |
S3-101-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-203140 | Threat analysis of target API root tampering | draftCR | Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203141 | [DRAFT] reply-LS on Misalignments on HTTP message format over N32-f |
LS out LS To: CT4 |
Ericsson |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-203142 | Corrections for the NRF token request service |
CR revised to S3-203537 |
Ericsson | 33.501 15.10.0 CR#983 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-203143 | Corrections for the NRF token request service |
CR revised to S3-203538 |
Ericsson | 33.501 16.4.0 CR#984 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-203144 | Verification of Serving Network Name in AUSF | CR | Ericsson | 33.501 15.10.0 CR#985 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203145 | SEPP including PLMN-ID and verification of Serving Network Name in AUSF | CR | Ericsson | 33.501 16.4.0 CR#986 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-203146 | Resolving Editor's Note on SCP performing token-based authorization on behalf of Network Functions |
CR revised to S3-203536 |
Ericsson | 33.501 16.4.0 CR#987 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-203147 | Resolving Editor's Notes on SCP authorization | CR | Ericsson | 33.501 16.4.0 CR#988 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
merged | [WTS] [JSN] |
S3-203148 | Token-based authorization for subsequent service requests in model D | CR | Ericsson | 33.501 16.4.0 CR#989 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
merged | [WTS] [JSN] |
S3-203149 | Assertions: partial protection of the message | CR | Ericsson | 33.501 16.4.0 CR#990 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-203150 | Assertions: protection of service response | CR | Ericsson | 33.501 16.4.0 CR#991 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-203151 | Assertion requirement by the producer | CR | Ericsson | 33.501 16.4.0 CR#992 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-203152 | Access token requirement by the producer | CR | Ericsson | 33.501 16.4.0 CR#993 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-203153 | Clarification on format for subjectAltName | CR | Ericsson | 33.31 16.5.0 CR#115 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-203154 | New Solution to KI#1, 2, 3, 6: TLS and HTTP Digest with AKMA |
pCR revised to S3-203355 |
Ericsson | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-203155 | New Solution to KI#3: Authentication to IMS Core using credentials generated with AKMA | pCR | Ericsson | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203156 | New Solution to KI#3: Authentication to IMS Core using credentials generated from the KAUSF | pCR | Ericsson | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203157 | Test case for correct handling of the custom HTTP header with PRINS security | draftCR | Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203158 | 5GFBS: Accuracy of Loaction Estimate for Solution#22 | pCR | Nokia, Nokia Shanghai Bell | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-203159 | eNPN: revision of SA3 SID | pCR | THALES, Orange, Idemia | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.2 |
withdrawn | [WTS] [JSN] |
S3-203160 | 5GFBS: Legitimate BS detected as FBS for Solution#22 | pCR | Nokia, Nokia Shanghai Bell | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-203161 | SCAS VNP: Adding Definitions for ETSI NFV Terms |
pCR revised to S3-203403 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203162 | SCAS VNP: DoS Attack via Changing Virtualized Resource |
pCR revised to S3-203404 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203163 | SCAS VNP: Secure Execution Environment |
pCR revised to S3-203405 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203164 | SCAS VNP: Threats on VNF-VNFM Interface |
pCR revised to S3-203406 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203165 | eNPN SID revision | SID revised | THALES, Orange, Idemia | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.2 |
withdrawn | [WTS] [JSN] | |
S3-203166 | SCAS VNP: VM Escape and Hypervisor Escape | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-203167 | SCAS VNP: Security requirements on the interface between VNF and VNFM |
pCR revised to S3-203407 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-203168 | TR 33.857: scope | pCR | THALES, Orange, Idemia | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203169 | Issues during authentication for N5GC and N5CW | discussion | Ericsson | 5WWC | Rel-16 |
S3-101-e AI: 4.9 |
noted | [WTS] [JSN] | |
S3-203170 | Authentication method selection and SUPI retrieval for N5GC | CR | Ericsson | 33.501 16.4.0 CR#994 catF | 5WWC | Rel-16 |
S3-101-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-203171 | Authentication method selection for N5CW | CR | Ericsson | 33.501 16.4.0 CR#995 catF | 5WWC | Rel-16 |
S3-101-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-203172 | Solutions sketches for KI#2 (Provisioning of credentials) | discussion | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] | |
S3-203173 | Resolving the ENs in solution #18 |
pCR revised to S3-203377 |
Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203174 | Resolving EN in solution #19 | pCR | Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-203175 | Best effort UP IP for EPS |
pCR revised to S3-203385 |
Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203176 | Authentication and authorisation of UAVs |
pCR revision of S3-202641 revised to S3-203386 |
Qualcomm Incorporated | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-203177 | Modification of the pairing key issue |
pCR revised to S3-203390 |
Qualcomm Incorporated | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-203178 | Some evaluation of solution #2.2 in TR 33.846 |
pCR revision of S3-202644 revised to S3-203394 |
Qualcomm Incorporated | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-203179 | Proposing a conclusion for key issue #4.1 |
pCR revision of S3-202647 |
Qualcomm Incorporated | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-203180 | AMF re-allocation via RAN using existing security states |
pCR revised to S3-203395 |
Qualcomm Incorporated | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203181 | Specifying existing Ua protocols for use with AKMA | discussion | Qualcomm Incorporated |
S3-101-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-203182 | Solution for secure PC5 link establishment for UE-to-network relay |
pCR revision of S3-202648 revised to S3-203416 |
Qualcomm Incorporated | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203183 | Solution to establish end-to-end security for the L3 UE-to-network relay |
pCR revision of S3-202649 revised to S3-203417 |
Qualcomm Incorporated | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203184 | Solution for secure PC5 link establishment for UE-to-UE relay |
pCR revision of S3-202650 revised to S3-203418 |
Qualcomm Incorporated | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203185 | Key Issue on Impact of Simultaneous CU-UP applying common UP security | pCR | Qualcomm Incorporated | 33.84 0.2.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-101-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-203186 | Extend UPIP support in 5GS for all 5GC connected RAN architecture (NG-RAN) options |
draftCR revised to S3-203511 |
Qualcomm Incorporated | eUPIP_SEC | Rel-16 |
S3-101-e AI: 4.23 |
revised | [WTS] [JSN] | |
S3-203187 | pCR: High-Level Solution framework for KI#4 |
pCR revised to S3-203401 |
Qualcomm Incorporated | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-203188 | Reply LS on NG-RAN broadcast of Onboarding Network information in the SIB |
LS out LS is reply to S2-2007849 LS To: SA2 revised to S3-203402 |
Qualcomm Incorporated |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] | |||
S3-203189 | Multi-USIM security and privacy | discussion | Qualcomm Incorporated |
S3-101-e AI: 5.19 |
noted | [WTS] [JSN] | |||
S3-203190 | Revised SID on IIoT Security | SID revised | Qualcomm Incorporated | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] | |
S3-203191 | Sending UE identifier to the AKMA AF |
CR revised to S3-210489 |
Qualcomm Incorporated | 33.535 16.1.0 CR#52 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-203192 | Addition of UDM sending GPSI of the UE for AKMA | CR | Qualcomm Incorporated | 33.501 16.4.0 CR#996 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-203193 | TR 33.857: security assumptions | pCR | THALES | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203194 | R15 NFc and NFp alignment in static authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 15.10.0 CR#997 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203195 | R16 NFc and NFp alignment in static authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#998 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203196 | R15 Access Token Get Service - removal of ambigiouty | CR | Nokia, Nokia Shanghai Bell | 33.501 15.10.0 CR#999 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-203197 | R16 Access Token Get Service - removal of ambigiouty | CR | Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#1000 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-203198 | R15 Authorization of NF service access - removal of ambigious terminology | CR | Nokia, Nokia Shanghai Bell | 33.501 15.10.0 CR#1001 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203199 | R16 Authorization of NF service access - removal of ambigious terminology | CR | Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#1002 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203200 | R15 Authorization of NF service access - service requst process steps |
CR revised to S3-203502 |
Nokia, Nokia Shanghai Bell | 33.501 15.10.0 CR#1003 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-203201 | R16 Authorization of NF service access - service requst process steps |
CR revised to S3-203503 |
Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#1004 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-203202 | R16 NF Service Consumer authentication | CR | Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#1005 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-203203 | NF-SCP Authorization |
CR revised to S3-203501 |
Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#1006 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-203204 | SCP-SCP Authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#1007 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-203205 | Making NF instance id in SBA certificate profile mandatory to support | CR | Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#1008 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-203206 | FS_eSBA_SEC |
SID new revised to S3-203504 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-101-e AI: 5.2 |
revised | [WTS] [JSN] | ||
S3-203207 | pCR to TR33.840-New key issue for CU-UPs security policy difference | pCR | CATT | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-101-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-203208 | IIoT: Update to solution #1 | pCR | Ericsson | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203209 | IIoT: New solution for protection of time synchronisation messages | pCR | Ericsson | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-203210 | ProSe: Handling of AF’s for key managment |
pCR revised to S3-203373 |
Ericsson | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203211 | Update of the reference point interface names of AKMA |
CR revised to S3-203493 |
Ericsson | 33.535 16.1.0 CR#53 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-203212 | Discussion on the AAnF selection | discussion | Ericsson | AKMA |
S3-101-e AI: 4.7 |
noted | [WTS] [JSN] | ||
S3-203213 | AKMA Anchor Function selection clause | CR | Ericsson | 33.535 16.1.0 CR#54 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-203214 | Assumptions for the AMF re-allocation security study |
pCR revised to S3-203419 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203215 | New key issue for the security of the AMF re-allocation procedures |
pCR revised to S3-203420 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203216 | New solution for AMF re-allocation procedure when 5G NAS security context is rerouted via RAN |
pCR revised to S3-203421 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203217 | New solution for NAS re-route via RAN and the use of a well-connected network function | pCR | Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-203218 | Editorial corrections | pCR | Ericsson | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203219 | Living document for TS 33.220: SBA support for Zh and Zn interfaces |
draftCR revised to S3-203545 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-203220 | Living document for TS 33.223: SBA support for Zpn |
draftCR revised to S3-203546 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-203221 | pCR to living document for TS 33.223: Resolving EN for private ID in Nbsp_Gba_PushInfo service operation response |
draftCR revised to S3-203508 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-203222 | LS on the SBA for GBA |
LS out LS To: SA2 |
Ericsson | GBA_5G |
S3-101-e AI: 4.14 |
noted | [WTS] [JSN] | ||
S3-203223 | pCR to living document for TS 33.220: Resolving EN for GBA AKA | draftCR | Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
noted | [WTS] [JSN] | |
S3-203224 | pCR to living document for TS 33.223: Resolving EN for GBA AKA | draftCR | Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
noted | [WTS] [JSN] | |
S3-203225 | pCR to living document for TS 33.220: Resolving EN for HSS |
draftCR revised to S3-203509 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-203226 | pCR to living document for TS 33.223: Resolving EN for HSS |
draftCR revised to S3-203510 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-203227 | Selection of latest KAUSF for SoR/UPU and storage of KAUSF in the UE and AUSF | CR | Ericsson | 33.501 16.4.0 CR#1009 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-203228 | LS on successful authentication event on the UE for 5G AKA |
LS out LS To: CT1 |
Ericsson | TEI16 |
S3-101-e AI: 4.25 |
noted | [WTS] [JSN] | ||
S3-203229 | New Solution for KI#11: Masked representation of identities |
pCR revised to S3-203341 |
KPN N.V. | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203230 | Optimized_UAS_Enabled_Authentication |
pCR revised to S3-203371 |
Nokia, Nokia Shanghai Bell | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-203231 | DHIES encryption to avoid UAV spoofing | pCR | Nokia, Nokia Shanghai Bell | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-203232 | Requirements for KI on multiple working domains | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203233 | Solution on multiple working domains | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203234 | KI update – time synchronization messages | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203235 | KI details Attacks based on asymmetric channel delay | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203236 | KI details TSN AF to NW-TT DS-TT interface security | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203237 | KI requirements and solution TSN AF to NW-TT DS-TT interface security | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203238 | Annex on Security considerations for integration with TSN | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.2.0 | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-203239 | Authentication and authorization between 5GMSGS client and MSGin5G server |
pCR revised to S3-203365 |
Samsung | 33.862 0.1.0 | FS_SEC_5GMSG | Rel-17 |
S3-101-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-203240 | Authentication and authorization between 5GMSGS client and MSGin5G server using secondary authentication |
pCR revised to S3-203366 |
Samsung | 33.862 0.1.0 | FS_SEC_5GMSG | Rel-17 |
S3-101-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-203241 | Transport security for MSGin5G-1 interface | pCR | Samsung | 33.862 0.1.0 | FS_SEC_5GMSG | Rel-17 |
S3-101-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-203242 | New KI on Authentication and Authorization of Application clients | pCR | Samsung | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-203243 | New KI on Privacy and integrity protection for transmitted data between AF and NWDAF |
pCR revised to S3-203367 |
Samsung | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-203244 | Usecase for User Consent in Edge Computing | pCR | Samsung | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203245 | Exposed user information in Edge computing | pCR | Samsung | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203246 | Potential Requirement on user's consent for exposure of information to Edge Applications | pCR | Samsung | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203247 | User consent for exposure of information to Edge Applications | pCR | Samsung | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203248 | Resolving editor’s note on using TLS based on AKMA PSK | pCR | Samsung | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203249 | [Rel-15]Correction to derivation of KSN for dual connectivity | CR | Samsung | 33.501 15.10.0 CR#1010 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203250 | [Mirror]Correction to derivation of KSN for dual connectivity | CR | Samsung | 33.501 16.4.0 CR#1011 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203251 | Handling of KAUSF upon successful primary authentication | CR | Samsung, Nokia, Nokia Shanghai Bell, Intel | 33.501 16.4.0 CR#1012 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-203252 | Discussion on the UE handling newly generated KAUSF | discussion | Samsung | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
noted | [WTS] [JSN] | |
S3-203253 | Support for mutual authentication between network entities |
CR revised to S3-203491 |
Samsung, Verizon | 33.501 16.4.0 CR#1013 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
revised | [WTS] [JSN] |
S3-203254 | Updates on Rel-16 IAB Conclusions | pCR | Samsung | 33.824 0.6.0 | FS_NR_IAB_Sec | Rel-16 |
S3-101-e AI: 5.18 |
approved | [WTS] [JSN] |
S3-203255 | Clean-up of IAB TR 33.824 | pCR | Samsung | 33.824 0.6.0 | FS_NR_IAB_Sec | Rel-16 |
S3-101-e AI: 5.18 |
approved | [WTS] [JSN] |
S3-203256 | Conclusions for TR 33.845 | pCR | Ericsson | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-203257 | Discussion on the need for a validity timer | discussion | Ericsson | eNS | Rel-16 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-203258 | Discussion on the need for SN ID at the AAA-S side | discussion | Ericsson | eNS | Rel-16 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-203259 | [DRAFT] LS on the need for SN-ID in NSSAA procedure |
LS out LS To: SA2 |
Ericsson | eNS | Rel-16 |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-203260 | Update to key issue 3.1 | pCR | Ericsson | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-203261 | Potential security requirement to KI 2.1 | pCR | Ericsson | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-203262 | [DRAFT] Reply LS on securing data collection from UE |
LS out LS is reply to S2-2006292 LS To: SA2 |
Ericsson | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] | |
S3-203263 | New Key Issue on Provisioning of PNI-NPN credentials | pCR | Ericsson, China Mobile | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203264 | Proposed TR Assumptions on credentials |
pCR revised to S3-203398 |
Ericsson | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-203265 | Adding Subscription Owner terminology | pCR | Ericsson | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-203266 | [DRAFT] LS on AAA based solutions for credentials owned by an entity separate from the SNPN |
LS out LS is reply to S2-2004385 LS To: SA2 revised to S3-203399 |
Ericsson | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] | |
S3-203267 | New Solution: Secure initial access to an SNPN onboarding network |
pCR revised to S3-203397 |
Ericsson | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-203268 | [DRAFT] LS on locating the DCS with the help of SUPI or SUCI |
LS out LS To: SA2 revised to S3-203466 |
Ericsson | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
revised | [WTS] [JSN] | |
S3-203269 | TR 33.847 Update for solution #10 |
pCR revision of S3-202820 revised to S3-203391 |
InterDigital Communications | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203270 | eNA study scope | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-203271 | eNA overview |
pCR revised to S3-203357 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-203272 | KI on Authorization of consumers for data access via DCCF | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-203273 | KI on privacy preservation for transmitted data |
pCR revised to S3-203370 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-203274 | Requirements to KI on privacy preservation for transmitted data |
pCR revised to S3-203363 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-203275 | KI on Abnormal NF behavior detection by NWDAF | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-203276 | Requirements to KI on Abnormal NF behavior detection by NWDAF |
pCR revised to S3-203473 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-203277 | Update to KI Cyber-attacks Detection supported by NWDAF | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203278 | Key issue on processing of tampered data |
pCR revised to S3-203359 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-203279 | Solution on processing of tampered data | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-203280 | UPIP: Remove Editor note in evaluation clause in solution #11 |
pCR revised to S3-203374 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203281 | UPIP: Configuration of the UP IP policy | pCR | Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203282 | UPIP: Resolve EN about X2 HO in Solution #11 |
pCR revised to S3-203375 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203283 | UPIP: Resolve EN in Solution #17 |
pCR revised to S3-203378 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203284 | UPIP: New solutions for interworking handover from EPS to 5GS |
pCR revised to S3-203379 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203285 | UPIP: New solution for S1 handover |
pCR revised to S3-203381 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203286 | UPIP: New solution for X2 handover |
pCR revised to S3-203382 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203287 | UPIP: New solutions for interworking handover from 5GS to EPS |
pCR revised to S3-203384 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-203288 | UPIP: Conclusion on UE connects to EPC via eUTRA | pCR | Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-203289 | Evaluation for Solution #1 |
pCR revised to S3-203342 |
Ericsson | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-203290 | Token-based authorization for indirect communication in roaming case | CR | Ericsson | 33.501 16.4.0 CR#1014 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-203291 | Discussion on performance requirements of crypto algorithms in virtualized gNB implementations | discussion | Ericsson |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-203292 | UAS: Update of solution #2 | pCR | Ericsson | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203293 | Key Issue on Security Context handling issues with AMF re-allocation | pCR | Lenovo, Motorola Mobility | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-203294 | Evaluation for Solution #2 |
pCR revised to S3-203343 |
Ericsson | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-203295 | Solution to enable NAS Security for AMF reallocation and reroute via RAN Scenario |
pCR revised to S3-203465 |
Lenovo, Motorola Mobility | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203296 | Update to KI #2 on Pairing authorization for UAV and UAVC | pCR | Lenovo, Motorola Mobility | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-203297 | user consent in ProSe restricted discovery | pCR | Futurewei Technologies | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-203298 | Update to Solution #7 on UAS Authentication | pCR | Lenovo, Motorola Mobility | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203299 | UE accessing most preferred serving NPN | pCR | Futurewei Technologies | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-203300 | Update to Solution 7 to align on UAS NF | pCR | Lenovo, Motorola Mobility | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203301 | Evaluation for Solution #9 and Solution #11 | pCR | Ericsson | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-203302 | third party gNB-CU-UP | pCR | Futurewei Technologies | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-101-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-203303 | Update to Solution #7 to resolve EN in UAS Authentication | pCR | Lenovo, Motorola Mobility | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
noted | [WTS] [JSN] |
S3-203304 | disaggregated gNB secure environment | pCR | Futurewei Technologies | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-101-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-203305 | Update to Key Issue #12 – Validity and refresh of security context | pCR | KPN N.V. | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-203306 | removal of Editor’s Notes |
pCR revised to S3-203345 |
Ericsson | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-203307 | Update to Key Issue #12 – Out of coverage scenario | pCR | KPN N.V. | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203308 | New Solution for KI#12: Initial key with validity time |
pCR revised to S3-203340 |
KPN N.V. | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203309 | Anonymous SUCI for N5GC | CR | Lenovo, Motorola Mobility | 33.501 16.4.0 CR#1015 catF | 5WWC | Rel-16 |
S3-101-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-203310 | Updates to solution #20 (6.20.2.2.4) |
pCR revised to S3-203471 |
CableLabs | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-203311 | Selecting the authentication method for devices that do not support 5GC NAS over WLAN access | CR | Lenovo, Motorola Mobility | 33.501 16.4.0 CR#1016 catF | 5WWC | Rel-16 |
S3-101-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-203312 | eNA: [DRAFT] Reply LS on securing data collection from UE |
LS out LS To: SA2 |
Ericsson | FS_eNA_SEC |
S3-101-e AI: 5.16 |
withdrawn | [WTS] [JSN] | ||
S3-203313 | Aligning TLS in 33.222 with the current 3GPP TLS profile |
CR revised to S3-203505 |
Ericsson | 33.222 16.0.0 CR#52 catF | CryptPr | Rel-16 |
S3-101-e AI: 4.25 |
revised | [WTS] [JSN] |
S3-203314 | Aligning TLS in 33.310 with the current 3GPP TLS profile | CR | Ericsson | 33.31 16.5.0 CR#116 catF | CryptPr | Rel-16 |
S3-101-e AI: 4.25 |
agreed | [WTS] [JSN] |
S3-203315 | Correcting use of (D)TLS in 33.501 |
CR revised to S3-203506 |
Ericsson | 33.501 16.4.0 CR#1017 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
revised | [WTS] [JSN] |
S3-203316 | Key issue on security of data collection from UE | pCR | Ericsson | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-203317 | Analytics for MitM Attack Detection | pCR | Lenovo, Motorola Mobility | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-203318 | New Key Issue on privacy of PDU session parameters |
pCR revised to S3-203396 |
Philips International B.V., Interdigital | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-203319 | Removal of EN on AMF routing |
pCR revised to S3-203460 |
Lenovo, Motorola Mobility | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-203320 | Removal of EN on ECS in HPLMN |
pCR revised to S3-203461 |
Lenovo, Motorola Mobility | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-203321 | Removal of EN on replay attack | pCR | Lenovo, Motorola Mobility | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203322 | Proposal to introduce draft-ietf-emu-rfc5448bis to TS 33.501 |
discussion revised to S3-210515 |
Ericsson |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-203323 | Reply to LS on authorization to access data |
LS out LS is reply to S3202845 LS To: SA2 revised to S3-203368 |
NTT DOCOMO |
S3-101-e AI: 5.16 |
revised | [WTS] [JSN] | |||
S3-203324 | Notes from conf call on NAS COUNT storage | other | NTT DOCOMO |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-203325 | Notes from second conf call on NAS COUNT storage | other | NTT DOCOMO |
S3-101-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-203326 | Notes from joint ETSI SAGE / SA3 conf call on 256bit keys | other | NTT DOCOMO |
S3-101-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-203327 | Applicability of KIs to Solution on SQNms protection by concealment | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203328 | Ed.note resolution on backward compatibility in solution SQNms protection by concealment | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203329 | Solution update - SQNms protection by concealment in USIM | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203330 | New solution - SQNms protection by concealment in ME |
pCR revised to S3-210336 |
Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-203331 | Extension of KI on linkability attack | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-203332 | KI-Solution mapping table |
pCR revised to S3-203372 |
Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-203333 | Editorial MCC requested correction |
pCR revised to S3-203376 |
Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-203334 | TR 33.847: GBA-based solution to protect PC3 interface | pCR | THALES | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203335 | Draft TR 33.853 v1.2.0 | draft TR | Samsung | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] | |
S3-203336 | Draft TR 33.845 v0.5.0 | draft TR | Samsung R&D Institute UK | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
approved | [WTS] [JSN] | |
S3-203337 | SA3 meeting calendar | other | WG Chair |
S3-101-e AI: 7 |
noted | [WTS] [JSN] | |||
S3-203338 | 256-bit algorithms based on SNOW 3G or SNOW V | LS in | ETSI SAGE |
S3-101-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-203339 | LS on clarification regarding EEC ID |
LS out LS To: SA6 |
Ericsson LM |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] | |||
S3-203340 | New Solution for KI#12: Initial key with validity time |
pCR revision of S3-203308 |
KPN N.V. | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203341 | New Solution for KI#11: Masked representation of identities |
pCR revision of S3-203229 |
KPN N.V. | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203342 | Evaluation for Solution #1 |
pCR revision of S3-203289 |
Ericsson | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-203343 | Evaluation for Solution #2 |
pCR revision of S3-203294 |
Ericsson | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-203344 | Editorial correction on TR 33.818 |
pCR revision of S3-203128 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203345 | removal of Editor’s Notes |
pCR revision of S3-203306 |
Ericsson | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-203346 | Adding hardening requirements for GVNP of type 1 |
pCR revision of S3-203129 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203347 | Adding hardening requirements for GVNP of type 2 |
pCR revision of S3-203130 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203348 | Adding basic vulnerability testing requirements for GVNP |
pCR revision of S3-203132 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203349 | Adding test case into clause 5.2.5.5.8.5.1 |
pCR revision of S3-203135 |
China Mobile | 33.818 0.8.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203350 | draft TR33.818 v0.9.0 | draft TR | China Mobile Com. Corporation | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] | |
S3-203351 | TR 33.847-Solution for secondary authentication in relay communication |
pCR revision of S3-202865 |
LG Electronics Inc. | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203352 | TR 33.854 Update for solution#3 |
pCR revision of S3-202874 |
InterDigital, Europe, Ltd. | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203353 | TR 33.854 Update for solution#4 |
pCR revision of S3-202875 |
InterDigital, Europe, Ltd. | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203354 | TR 33.854 Update for solution#5 |
pCR revision of S3-202876 |
InterDigital, Europe, Ltd. | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203355 | New Solution to KI#1, 2, 3, 6: TLS and HTTP Digest with AKMA |
pCR revision of S3-203154 |
Ericsson | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203356 | LS Reply to SA2 on System support for MUSIM devices |
LS out LS is reply to S3-202840 LS To: SA2 revision of S3-202895 |
Nokia, Nokia Shanghai Bell |
S3-101-e AI: 5.19 |
approved | [WTS] [JSN] | |||
S3-203357 | eNA overview |
pCR revision of S3-203271 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203358 | Modified KI#5 for TR 33.847 – privacy of identities for UE2N path switch |
pCR revision of S3-202816 |
InterDigital Communications | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203359 | Key issue on processing of tampered data |
pCR revision of S3-203278 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203360 | Reply LS on IP address to GPSI translation |
LS out LS is reply to S3-202849 LS To: SA6, SA2 |
Samsung | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] | ||
S3-203361 | Key_Update_Need_And_Solution |
pCR revision of S3-202985 |
Philips International B.V. | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-203362 | Update of KI#8 for TR 33.847 – privacy of identities for UE2UE Relay path switch |
pCR revision of S3-202817 |
InterDigital Communications | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203363 | Requirements to KI on privacy preservation for transmitted data |
pCR revision of S3-203274 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203364 | UE&Network-assisted UE avoidance and Network detection of FBS |
pCR revision of S3-202983 |
Philips International B.V., CableLabs | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-203365 | Authentication and authorization between 5GMSGS client and MSGin5G server |
pCR revision of S3-203239 |
Samsung | 33.862 0.1.0 | FS_SEC_5GMSG | Rel-17 |
S3-101-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-203366 | Authentication and authorization between 5GMSGS client and MSGin5G server using secondary authentication |
pCR revision of S3-203240 |
Samsung | 33.862 0.1.0 | FS_SEC_5GMSG | Rel-17 |
S3-101-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-203367 | New KI on Privacy and integrity protection for transmitted data between AF and NWDAF |
pCR revision of S3-203243 |
Samsung | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203368 | Reply to LS on authorization to access data |
LS out LS is reply to S3-202845 LS To: SA2 revision of S3-203323 |
NTT DOCOMO |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] | |||
S3-203369 | New solution for TR 33.847 – Privacy handling for Layer-3 UE-to-UE Relay based on IP routing |
pCR revision of S3-202818 |
InterDigital Communications | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203370 | KI on privacy preservation for transmitted data |
pCR revision of S3-203273 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203371 | Optimized_UAS_Enabled_Authentication |
pCR revision of S3-203230 |
Nokia, Nokia Shanghai Bell | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203372 | KI-Solution mapping table |
pCR revision of S3-203332 |
Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203373 | ProSe: Handling of AF’s for key managment |
pCR revision of S3-203210 |
Ericsson | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203374 | UPIP: Remove Editor note in evaluation clause in solution #11 |
pCR revision of S3-203280 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203375 | UPIP: Resolve EN about X2 HO in Solution #11 |
pCR revision of S3-203282 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203376 | Editorial MCC requested correction |
pCR revision of S3-203333 |
Nokia, Nokia Shanghai Bell | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203377 | Resolving the ENs in solution #18 |
pCR revision of S3-203173 |
Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203378 | UPIP: Resolve EN in Solution #17 |
pCR revision of S3-203283 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203379 | UPIP: New solutions for interworking handover from EPS to 5GS |
pCR revision of S3-203284 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203380 | Draft TR 33.845 v0.6.0 | draft TR | Vodafone GmbH | FS_5GC_SEC_ARPF | Rel-17 |
S3-101-e AI: 5.6 |
approved | [WTS] [JSN] | |
S3-203381 | UPIP: New solution for S1 handover |
pCR revision of S3-203285 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203382 | UPIP: New solution for X2 handover |
pCR revision of S3-203286 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203383 | Draft TR 33.853 v1.3.0 | draft TR | Vodafone GmbH | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] | |
S3-203384 | UPIP: New solutions for interworking handover from 5GS to EPS |
pCR revision of S3-203287 |
Ericsson | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203385 | Best effort UP IP for EPS |
pCR revision of S3-203175 |
Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203386 | Authentication and authorisation of UAVs |
pCR revision of S3-203176 |
Qualcomm Incorporated | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203387 | A solutin to UAV and UAV-C pairing authorization |
pCR revision of S3-203093 |
Huawei, HiSilicon, InterDigital | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203388 | Draft TR 33.846 v0.9.0 Study on authentication enhancements in the 5G System (5GS) | draft TR | Ericsson España S.A. | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] | |
S3-203389 | TR_33.851_IIoT_Sec | draft TR | Nokia Germany | FS_IIoT_SEC | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-203390 | Modification of the pairing key issue |
pCR revision of S3-203177 |
Qualcomm Incorporated, Interdigital, Huawei, HiSilicon, Lenovo, Motorola Mobility | 33.854 0.2.0 | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-203391 | TR 33.847 Update for solution #10 |
pCR revision of S3-203269 |
InterDigital Communications | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203392 | Draft TR 33.864 v0.2.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson España S.A. | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] | |
S3-203393 | TR 33.846: evaluation of solution #2.2 |
pCR revision of S3-203081 |
THALES | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203394 | Some evaluation of solution #2.2 in TR 33.846 |
pCR revision of S3-203178 |
Qualcomm Incorporated | 33.846 0.8.0 | FS_AUTH_ENH | Rel-16 |
S3-101-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-203395 | AMF re-allocation via RAN using existing security states |
pCR revision of S3-203180 |
Qualcomm Incorporated | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203396 | New Key Issue on privacy of PDU session parameters |
pCR revision of S3-203318 |
Philips International B.V., Interdigital | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203397 | New Solution: Secure initial access to an SNPN onboarding network |
pCR revision of S3-203267 |
Ericsson | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-203398 | Proposed TR Assumptions on credentials |
pCR revision of S3-203264 |
Ericsson | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-203399 | LS on AAA based solutions for credentials owned by an entity separate from the SNPN |
LS out LS is reply to S3-202837 LS To: SA2 revision of S3-203266 |
Ericsson, ZTE | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] | |
S3-203400 | Draft TR 33857 v030 Study on enhanced security support for Non-Public Networks (NPN) | draft TR | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] | |
S3-203401 | pCR: High-Level Solution framework for KI#4 |
pCR revision of S3-203187 |
Qualcomm Incorporated | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-203402 | Reply LS on NG-RAN broadcast of Onboarding Network information in the SIB |
LS out LS is reply to S3-202844 LS To: SA2 revision of S3-203188 |
Qualcomm Incorporated |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] | |||
S3-203403 | SCAS VNP: Adding Definitions for ETSI NFV Terms |
pCR revision of S3-203161 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203404 | SCAS VNP: DoS Attack via Changing Virtualized Resource |
pCR revision of S3-203162 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203405 | SCAS VNP: Secure Execution Environment |
pCR revision of S3-203163 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203406 | SCAS VNP: Threats on VNF-VNFM Interface |
pCR revision of S3-203164 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203407 | SCAS VNP: Security requirements on the interface between VNF and VNFM |
pCR revision of S3-203167 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-101-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-203408 | Key Issue for Busy Indication |
other revision of S3-202935 |
Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
approved | [WTS] [JSN] | |||
S3-203409 | Key Issue for UE and Paging Server Communication |
other revision of S3-202937 |
Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
approved | [WTS] [JSN] | |||
S3-203410 | Scope for MUSIM TR |
other revision of S3-202940 |
Intel Corporation (UK) Ltd |
S3-101-e AI: 5.19 |
approved | [WTS] [JSN] | |||
S3-203411 | draft TR Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules | other | Intel |
S3-101-e AI: 5.19 |
approved | [WTS] [JSN] | |||
S3-203412 | Authentication and Authorization Framework for EDGE-4 interfaces using Primary authentication and proxy interface |
pCR revision of S3-202931 |
Intel Corporation (UK) Ltd | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203413 | Updates to Solution 4 |
pCR revision of S3-202932 |
Intel Corporation (UK) Ltd | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203414 | Updates to Solution 12 |
pCR revision of S3-202933 |
Intel Corporation (UK) Ltd | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203415 | TR33.840 v0.2.0 | draft TR | China Telecommunications | FS_disagg_gNB_Sec | Rel-17 |
S3-101-e AI: 5.13 |
approved | [WTS] [JSN] | |
S3-203416 | Solution for secure PC5 link establishment for UE-to-network relay |
pCR revision of S3-203182 |
Qualcomm Incorporated | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203417 | Solution to establish end-to-end security for the L3 UE-to-network relay |
pCR revision of S3-203183 |
Qualcomm Incorporated | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203418 | Solution for secure PC5 link establishment for UE-to-UE relay |
pCR revision of S3-203184 |
Qualcomm Incorporated | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203419 | Assumptions for the AMF re-allocation security study |
pCR revision of S3-203214 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203420 | New key issue for the security of the AMF re-allocation procedures |
pCR revision of S3-203215 |
Ericsson, Huawei, Hisilicon, China Mobile, Lenovo, Motorola Mobility | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203421 | New solution for AMF re-allocation procedure when 5G NAS security context is rerouted via RAN |
pCR revision of S3-203216 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203422 | Add some abbreviations for TR 33.850 |
pCR revision of S3-202919 |
ZTE Corporation | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-203423 | New solution for key issue#1 in TR 33.850 |
pCR revision of S3-202920 |
ZTE Corporation | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-203424 | Update solution#3 in TR 33.850 |
pCR revision of S3-202921 |
ZTE Corporation | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-203425 | Update to Sol#7 to address EN and add evaluation |
pCR revision of S3-202956 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203426 | Propose to resolve EN in the security requirement of KI#12 |
pCR revision of S3-202957 |
Huawei, Hisilicon, KPN | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203427 | new key issue on the security protection between content provider and 5GC |
pCR revision of S3-202964 |
Huawei, Hisilicon | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-203428 | new solution on the security protection between content provider and 5GC |
pCR revision of S3-202965 |
Huawei, Hisilicon | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-203429 | Solving the editoral note in solution 2 |
pCR revision of S3-202966 |
Huawei, Hisilicon | 33.85 0.2.0 | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-203430 | security solution for UE-to-Network Relay based on Layer 2 Relay |
pCR revision of S3-202968 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203431 | Delete Editor's Note in solution 9 |
pCR revision of S3-202971 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203432 | Solution on key management for UE-to-network relay |
pCR revision of S3-203026 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203433 | Update key issue #1 in TR 33.839 |
pCR revision of S3-202897 |
CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203434 | Update Key issue #2 in TR 33.839 |
pCR revision of S3-202898 |
CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203435 | Update Solution #6 in TR 33.839 |
pCR revision of S3-202899 |
CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203436 | Draft TR 33.839 v0.3.0 | draft TR | HUAWEI TECHNOLOGIES Co. Ltd. | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-203437 | Update Solution #10 in TR 33.839 |
pCR revision of S3-202927 |
CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203438 | New solution on UE onboarding for SNPN with AAA-S as DCS |
pCR revision of S3-202922 |
ZTE Corporation | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-203439 | New solution on UE onboarding for SNPN with UDM as DCS |
pCR revision of S3-202923 |
ZTE Corporation | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-203440 | pCR to TR33.847-Update Solution#3 for removing some ENs |
pCR revision of S3-203017 |
CATT | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203441 | Add reference TR33.867 and clean up |
pCR revision of S3-203027 |
Huawei, Hisilicon, CATT | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203442 | 5G ProSe: New solution on e2e authentication between two UE2 in the UE-to-UE relay scenario |
pCR revision of S3-203063 |
Huawei, Hisilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203443 | EC: New solution on authorization during Edge Data Network change |
pCR revision of S3-203065 |
Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203444 | EC: Framework on the EEC authentication and authorization |
pCR revision of S3-203067 |
Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203445 | AMFREAL: Description of AMF reallocation procedure |
pCR revision of S3-203040 |
Huawei, Hisilicon | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203446 | AMFREAL: New solution to registration failure with AMF reallocation |
pCR revision of S3-203042 |
Huawei, Hisilicon | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203447 | TR 33.809-5GFBS | draft TR | Apple Computer Trading Co. Ltd | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-203448 | ProSe-Modification in key issue#1 |
pCR revision of S3-203014 |
Apple | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203449 | Add Security Requirement for Key Issue #2.1 |
pCR revision of S3-202993 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell, China Mobile | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203450 | Scope of eNA Security |
pCR revision of S3-202995 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203451 | Scope of User Consent for 3GPP Services |
pCR revision of S3-202996 |
Huawei, Hisilicon | 33.867 0.1.0 | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-203452 | 5GFBS- Edotorial change in Clause 5.2.1 |
pCR revision of S3-203008 |
Apple | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-203453 | UPIP-Evaluation in Solution#18 |
pCR revision of S3-203010 |
Apple | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203454 | UP IP-Update solution #11 |
pCR revision of S3-202979 |
Huawei, Hisilicon | 33.853 1.2.0 | FS_UP_IP_Sec | Rel-17 |
S3-101-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-203455 | Draft TR 33.850 | draft TR | Huawei, Hisilicon | FS_5MBS_SEC | Rel-17 |
S3-101-e AI: 5.11 |
approved | [WTS] [JSN] | |
S3-203456 | Draft TR33.824 v0.7.0 | draft TR | Samsung | FS_NR_IAB_Sec | Rel-16 |
S3-101-e AI: 5.18 |
approved | [WTS] [JSN] | |
S3-203457 | EC: Editor notes removal |
pCR revision of S3-203045 |
Huawei, Hisilicon | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203458 | Draft TR 33.867 | draft TR | Huawei,Hisilicon | FS_UC3S | Rel-17 |
S3-101-e AI: 5.14 |
approved | [WTS] [JSN] | |
S3-203459 | Draft TR 33.847 v0.3.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-203460 | Removal of EN on AMF routing |
pCR revision of S3-203319 |
Lenovo, Motorola Mobility | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203461 | Removal of EN on ECS in HPLMN |
pCR revision of S3-203320 |
Lenovo, Motorola Mobility | 33.839 0.2.0 | FS_eEDGE_Sec | Rel-17 |
S3-101-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-203462 | A solution for groupcast security and privacy |
pCR revision of S3-203087 |
Huawei, HiSilicon, Lenovo, Motorola Mobility | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-101-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-203463 | draft TR 33.866 0.2.0 | draft TR | China Mobile International Ltd | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] | |
S3-203464 | draft TR 33.862 0.2.0 | draft TR | China Mobile International Ltd | FS_SEC_5GMSG | Rel-17 |
S3-101-e AI: 5.15 |
approved | [WTS] [JSN] | |
S3-203465 | Solution to enable NAS Security for AMF reallocation and reroute via RAN Scenario |
pCR revision of S3-203295 |
Lenovo, Motorola Mobility | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203466 | LS on locating the DCS with the help of SUPI or SUCI |
LS out LS To: SA2 revision of S3-203268 |
Ericsson | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] | |
S3-203467 | TR 33.854 v0.3.0 |
draft TR revised to S3-210695 |
Qualcomm Incoporated | FS_UAS_SEC | Rel-17 |
S3-101-e AI: 5.7 |
approved | [WTS] [JSN] | |
S3-203468 | Updates to solution #3 |
pCR revision of S3-202888 |
CableLabs | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-203469 | New solution for Key Issue #1 with enhanced security of KAUSF |
pCR revision of S3-202890 |
CableLabs | 33.857 0.2.0 | FS_eNPN_SEC | Rel-17 |
S3-101-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-203470 | Updates to solution #20 (6.20.4) |
pCR revision of S3-202893 |
CableLabs, Interdigital, Apple, Deutsche Telekom AG, Intel, Rogers Communications, Philips | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-203471 | Updates to solution #20 (6.20.2.2.4) |
pCR revision of S3-203310 |
CableLabs | 33.809 0.11.0 | FS_5GFBS | Rel-17 |
S3-101-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-203472 | CVD process update | discussion | WG chair |
S3-101-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-203473 | Requirements to KI on Abnormal NF behavior detection by NWDAF |
pCR revision of S3-203276 |
Nokia, Nokia Shanghai Bell | 33.866 0.1.0 | FS_eNA_SEC | Rel-17 |
S3-101-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-203474 | Authentication procedure during Xn handover procedure |
CR revision of S3-203004 revised to S3-203475 |
NEC | 33.501 16.4.0 CR#9661 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
revised | [WTS] [JSN] |
S3-203475 | Authentication procedure during Xn handover procedure |
CR revision of S3-203474 |
NEC | 33.501 16.4.0 CR#9662 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
not pursued | [WTS] [JSN] |
S3-203476 | NAS COUNT storage for multiple PLMN |
CR revision of S3-202889 |
Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#9611 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203477 | Draft agenda for SA3#101bis-e | agenda | WG chair |
S3-101-e AI: 7 |
noted | [WTS] [JSN] | |||
S3-203478 | Draft agenda for SA3#102-e | agenda | WG chair |
S3-101-e AI: 7 |
noted | [WTS] [JSN] | |||
S3-203479 | Process and agenda presentation for SA3#101e | other | WG chair |
S3-101-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-203480 | Clarification on cross-layer indication triggered by updating the security context |
CR revision of S3-202952 |
Huawei, Hisilicon, LG Electronics | 33.536 16.1.0 CR#191 catF | eV2XARC | Rel-16 |
S3-101-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-203481 | Proposal for improvement of the user plane security policy handling logic |
CR revision of S3-202953 |
Huawei, Hisilicon, Interdigital | 33.536 16.1.0 CR#201 catF | eV2XARC | Rel-16 |
S3-101-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-203482 | Adding details of AKMA key generation in the UE |
CR revision of S3-202963 |
Huawei, Hisilicon | 33.535 16.1.0 CR#471 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-203483 | Reply LS on the re-keying procedure for NR SL |
LS out LS is reply to S3-202828 LS To: RAN2, CT1 |
LG Electronics Inc. |
S3-101-e AI: 4.13 |
approved | [WTS] [JSN] | |||
S3-203484 | New WID on adapting BEST for use in 5G networks |
WID new revision of S3-203112 |
KPN N.V. | Rel-17 |
S3-101-e AI: 4.24 |
agreed | [WTS] [JSN] | ||
S3-203485 | Revised WID of AKMA |
WID revised revision of S3-202871 |
China Mobile | AKMA | Rel-17 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] | |
S3-203486 | CR for AKMA changes to TS 33.501 in Rel-17 |
CR revision of S3-202872 |
China Mobile International Ltd | 33.501 16.4.0 CR#9591 catB | AKMA | Rel-17 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-203487 | CR for AKMA changes to TS 33.220 in Rel-17 |
CR revision of S3-202873 |
China Mobile | 33.22 16.2.0 CR#2061 catB | AKMA | Rel-17 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-203488 | CR Removal of AKMA changes to TS 33.220 in Rel-16 |
CR revision of S3-202870 |
China Mobile | 33.22 16.2.0 CR#2051 catF | RM_AKMA_R16 | Rel-16 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-203489 | Proposal to add introduction and NWDAF-specific security functional requirements |
pCR revision of S3-203125 |
China Mobile | 33.521 0.1.0 | SCAS_5G_NWDAF | Rel-17 |
S3-101-e AI: 4.18 |
approved | [WTS] [JSN] |
S3-203490 | draft TS 33.521v0.2.0 | draft TS | China Mobile Com. Corporation | SCAS_5G_NWDAF | Rel-17 |
S3-101-e AI: 4.18 |
approved | [WTS] [JSN] | |
S3-203491 | Support for mutual authentication between network entities |
CR revision of S3-203253 |
Samsung, Verizon, Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#10131 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
agreed | [WTS] [JSN] |
S3-203492 | LS on Physical layer assisted lightweight AKA (PL-AKA) protocol for the Internet of things |
LS out LS is reply to S3-202853 source LS: ITU-T SG17-TD3365R3 LS To: ITU-T SG17 |
Ericsson España S.A. |
S3-101-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-203493 | Update of the reference point interface names of AKMA |
CR revision of S3-203211 |
Ericsson | 33.535 16.1.0 CR#531 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-203494 | LS on AKMA Anchor Function selection |
LS out LS To: SA2 LS reply in S2-2100671 |
Ericsson España S.A. |
S3-101-e AI: 4.7 |
approved | [WTS] [JSN] | |||
S3-203495 | LS: Misalignment on requirement for access token request between TS 29.510 and 33.501 |
LS out LS To: CT4 revision of S3-202805 |
Mavenir | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-203496 | NRF authorization during NF service consumer Access Token Get Request |
CR revision of S3-202809 |
Mavenir, Nokia, Nokia Shanghai Bell | 33.501 15.10.0 CR#9561 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203497 | NRF authorization during NF service consumer Access Token Get Request |
CR revision of S3-202808 |
Mavenir, Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#9551 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203498 | Reply LS on threats of service disruption, SIP message alternation and content eavesdropping in 5G networks |
LS out LS is reply to S3-202855 source LS: SG17-LS264-TD3331 LS To: ITU-T SG17 |
SK Telecom |
S3-101-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-203499 | Re-using of access token in indirect communication with delegated discovery |
CR revision of S3-202883 |
Nokia, Nokia Shanghai Bell, Ericsson, Mavenir, Huawei, HiSilicon, CableLabs | 33.501 16.4.0 CR#9072 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-203500 | Reply LS on Observations and questions on 256-bit security goals |
LS out LS is reply to S3-202851 LS To: ETSI SAGE |
Ericsson |
S3-101-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-203501 | NF-SCP Authorization |
CR revision of S3-203203 |
Nokia, Nokia Shanghai Bell, Ericsson | 33.501 16.4.0 CR#10061 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-203502 | R15 Authorization of NF service access - service requst process steps |
CR revision of S3-203200 |
Nokia, Nokia Shanghai Bell | 33.501 15.10.0 CR#10031 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203503 | R16 Authorization of NF service access - service requst process steps |
CR revision of S3-203201 |
Nokia, Nokia Shanghai Bell | 33.501 16.4.0 CR#10041 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203504 | FS_eSBA_SEC |
SID new revision of S3-203206 |
Nokia, Nokia Shanghai Bell, Mavenir, CableLabs, Deutsche Telekom, Verizon, Vodafone, T-Mobile, Docomo, China Mobile, Huawei, HiSilicon, Samsung | Rel-17 |
S3-101-e AI: 5.2 |
agreed | [WTS] [JSN] | ||
S3-203505 | Aligning TLS in 33.222 with the current 3GPP TLS profile |
CR revision of S3-203313 |
Ericsson | 33.222 16.0.0 CR#521 catF | CryptPr | Rel-16 |
S3-101-e AI: 4.25 |
agreed | [WTS] [JSN] |
S3-203506 | Correcting use of (D)TLS in 33.501 |
CR revision of S3-203315 |
Ericsson | 33.501 16.4.0 CR#10171 catF | TEI16 | Rel-16 |
S3-101-e AI: 4.25 |
agreed | [WTS] [JSN] |
S3-203507 | Error correction and clarification of Annex O |
CR revision of S3-202887 |
CableLabs | 33.501 16.4.0 CR#9601 catF | 5WWC | Rel-16 |
S3-101-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-203508 | pCR to living document for TS 33.223: Resolving EN for private ID in Nbsp_Gba_PushInfo service operation response |
draftCR revision of S3-203221 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-203509 | pCR to living document for TS 33.220: Resolving EN for HSS |
draftCR revision of S3-203225 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-203510 | pCR to living document for TS 33.223: Resolving EN for HSS |
draftCR revision of S3-203226 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-203511 | Extend UPIP support in 5GS for all 5GC connected RAN architecture (NG-RAN) options |
draftCR revision of S3-203186 revised to S3-210490 |
Qualcomm Incorporated | eUPIP_SEC | Rel-16 |
S3-101-e AI: 4.23 |
approved | [WTS] [JSN] | |
S3-203512 | Living CR toTR33.926 for eSCAS |
draftCR revision of S3-202973 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203513 | Living CR to TS33.117 |
draftCR revision of S3-202974 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203514 | skeleton of NSSAAF SCAS |
draft TS revision of S3-202975 |
Huawei, Hisilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-101-e AI: 4.21 |
approved | [WTS] [JSN] | |
S3-203515 | Secondary authentication revocation rel15 |
CR revision of S3-203020 |
Huawei, HiSilicon | 33.501 15.10.0 CR#9671 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203516 | Secondary authentication revocation rel16 |
CR revision of S3-203021 |
Huawei, HiSilicon | 33.501 16.4.0 CR#9681 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203517 | Draft TS 33.226 v0.3.0 | draft TS | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-203518 | AKMA: Adding missing service definition |
CR revision of S3-203037 |
Huawei, Hisilicon | 33.535 16.1.0 CR#511 catF | AKMA | Rel-17 |
S3-101-e AI: 4.7 |
withdrawn | [WTS] [JSN] |
S3-203519 | SHA-1 deprecation in GBA |
CR revision of S3-203039 |
Huawei, Hisilicon | 33.22 16.2.0 CR#2071 catF | GBA-ext, TEI17 | Rel-17 |
S3-101-e AI: 4.25 |
agreed | [WTS] [JSN] |
S3-203520 | Input parameters of access token request addition and verification |
CR revision of S3-203049 |
Huawei, Hisilicon | 33.501 16.4.0 CR#9721 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.25 |
agreed | [WTS] [JSN] |
S3-203521 | Clarification on the security policy handling |
CR revision of S3-203051 |
Huawei, Hisilicon | 33.536 16.1.0 CR#211 catF | eV2XARC | Rel-16 |
S3-101-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-203522 | Reply LS on Misalignments on HTTP message format over N32-f |
LS out LS is reply to S3-202832 LS To: CT4 revision of S3-203055 |
Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.25 |
approved | [WTS] [JSN] | |
S3-203523 | Modification policy clarification in Rel16 | CR | Huawei, Hisilicon | 33.501 16.4.0 CR#9761 catF | 5GS_Ph1-SEC, TEI16 | Rel-16 |
S3-101-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-203524 | Threats related to security enforcement configuration for TSC services |
draftCR revision of S3-203059 |
Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203525 | New test case on security enforcement configuration for TSC services |
draftCR revision of S3-203060 |
Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203526 | Threats related to security enforcement configuration for 5G LAN services |
draftCR revision of S3-203069 |
Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203527 | New test case on security enforcement configuration for 5G LAN services |
draftCR revision of S3-203070 |
Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203528 | IMS SCAS: living doc for the threats |
draftCR revision of S3-203072 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-203529 | IMS SCAS: new test case on synchronization failure handling |
pCR revision of S3-203073 |
Huawei, Hisilicon | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-203530 | IMS SCAS: adding threats related to IMS signalling transport |
draftCR revision of S3-203074 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-203531 | IMS SCAS: new test case on the IMS signaling protection |
pCR revision of S3-203075 |
Huawei, Hisilicon | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-203532 | IMS SCAS: adding threats related to Resynchronization failure |
draftCR revision of S3-203076 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-203533 | IMS SCAS: Adding the general requirements |
pCR revision of S3-203077 |
Huawei, Hisilicon | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-203534 | LS to CT6 on the NAS COUNTs storage |
LS out LS To: CT6 revision of S3-203006 |
Apple | Rel-16 |
S3-101-e AI: 4.1 |
approved | [WTS] [JSN] | ||
S3-203535 | Corrections of clause 6.1 |
CR revision of S3-202944 |
CATT | 33.535 16.1.0 CR#451 catF | AKMA | Rel-16 |
S3-101-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-203536 | Resolving Editor's Note on SCP performing token-based authorization on behalf of Network Functions |
CR revision of S3-203146 |
Ericsson | 33.501 16.4.0 CR#9871 catF | 5G_eSBA | Rel-16 |
S3-101-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-203537 | Corrections for the NRF token request service |
CR revision of S3-203142 |
Ericsson | 33.501 15.10.0 CR#9831 catF | 5GS_Ph1-SEC | Rel-15 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203538 | Corrections for the NRF token request service |
CR revision of S3-203143 |
Ericsson | 33.501 16.4.0 CR#9841 catA | 5GS_Ph1-SEC | Rel-16 |
S3-101-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-203539 | Correction of test case for access token verification failure handling in different PLMN |
CR revision of S3-203085 |
Nokia, Nokia Shanghai Bell | 33.117 16.5.0 CR#661 catF | SCAS_5G | Rel-16 |
S3-101-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-203540 | SCAS IMS: Removal of the sub-clause for SBA |
pCR revision of S3-203111 |
Nokia, Nokia Shanghai Bell | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-203541 | Threat of bidding down attack on security association |
pCR revision of S3-203113 |
Nokia, Nokia Shanghai Bell | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-203542 | SCAS IMS: New Sub-Test Case against Bidding-down on Security Association |
pCR revision of S3-203114 |
Nokia, Nokia Shanghai Bell | 33.226 0.2.0 | SCAS_IMS | Rel-17 |
S3-101-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-203543 | Updated Threat Analysis of Incorrect Verification of Access Tokens |
draftCR revision of S3-203115 |
Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203544 | Update of the Test Case for Access Token Verification Failure Handling |
draftCR revision of S3-203117 |
Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203545 | Living document for TS 33.220: SBA support for Zh and Zn interfaces |
draftCR revision of S3-203219 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-203546 | Living document for TS 33.223: SBA support for Zpn |
draftCR revision of S3-203220 |
Ericsson | GBA_5G | Rel-16 |
S3-101-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-203547 | Living CR to 33.514 | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203548 | Living CR to 33.517 | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-16 |
S3-101-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-203549 | TS 33.326 | draft TS | Huawei, Hisilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-101-e AI: 4.21 |
approved | [WTS] [JSN] | |
S3-203550 | Reply LS to ETSI SAGE on use of 256-bit block Rijndael in Milenage-256 |
LS out LS is reply to S3-202823 LS To: ETSI SAGE, TCA revision of S3-203079 |
THALES | Rel-17 |
S3-101-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-203551 | [33.180] R16 Fix terminology |
CR revision of S3-202880 |
Airbus | 33.18 16.4.0 CR#1511 catF | MCXSec | Rel-16 |
S3-101-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-203552 | [33.180] R17 Fix terminology |
CR revision of S3-202881 |
Airbus | 33.18 17.0.0 CR#1521 catA | MCXSec | Rel-17 |
S3-101-e AI: 4.3 |
agreed | [WTS] [JSN] |
753 documents (1.060870885849 seconds)