3GPP TDocs (written contributions) at meeting
Meeting: S3-97 - 2019-11-18 to 2019-11-22, Reno, Nevada
meeting id: S3-97 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S3‑193900 | Agenda | WG Chairman | imported from 3GU |
| S3‑193901 | Report from SA3#96 | MCC | imported from 3GU |
| S3‑193902 | Report from SA3#96Ad-Hoc | MCC | imported from 3GU |
| S3‑193903 | SA3 Work Plan | MCC | imported from 3GU |
| S3‑193904 | Report from last SA meeting | WG Chairman | imported from 3GU |
| S3‑193905 | SA3 meeting calendar | MCC | imported from 3GU |
| S3‑193906 | Work Plan input from Rapporteurs | MCC | imported from 3GU |
| S3‑193907 | Alignment with TR 33.926 | Futurewei Technologies | imported from 3GU |
| S3‑193908 | Reference Correction | Futurewei Technologies | imported from 3GU |
| S3‑193909 | Adding missing abbreviations | Futurewei Technologies | imported from 3GU |
| S3‑193910 | TCG progress - report from TCG rapporteur | InterDigital Communications | imported from 3GU |
| S3‑193911 | TR 33.813 - update for the evaluation for solution #11 | InterDigital Communications | imported from 3GU |
| S3‑193912 | TR 33.819 – update for the evaluation of Hash based solution for CAG ID privacy | InterDigital Communications | imported from 3GU |
| S3‑193913 | New WID on Security Aspects of PARLOS | SPRINT Corporation | imported from 3GU |
| S3‑193914 | [MCXSec] 33180 R16 Missing Abbreviations (Mirror) | Airbus | imported from 3GU |
| S3‑193915 | [MCXSec] 33180 R16 Reference Addition (Mirror) | Airbus | imported from 3GU |
| S3‑193916 | [MCXSec] 33180 R16 Correction concerning IdM client (Mirror) | Airbus | imported from 3GU |
| S3‑193917 | [eMCSec] 33180 R15 Missing Abbreviations (Mirror) | Airbus | imported from 3GU |
| S3‑193918 | [eMCSec] 33180 R15 Reference Addition (Mirror) | Airbus | imported from 3GU |
| S3‑193919 | [eMCSec] 33180 R15 Correction concerning IdM client (Mirror) | Airbus | imported from 3GU |
| S3‑193920 | [MCSec] 33180 R14 Missing Abbreviations (Mirror) | Airbus | imported from 3GU |
| S3‑193921 | [MCSec] 33180 R14 Reference Addition (Mirror) | Airbus | imported from 3GU |
| S3‑193922 | [MCSec] 33180 R14 Correction concerning IdM client (Mirror) | Airbus | imported from 3GU |
| S3‑193923 | [MCPTT] 33179 R13 Missing Abbreviations | Airbus | imported from 3GU |
| S3‑193924 | [MCPTT] 33179 R13 Reference Addition | Airbus | imported from 3GU |
| S3‑193925 | [MCPTT] 33179 R13 Correction concerning IdM client | Airbus | imported from 3GU |
| S3‑193926 | LS on IANA assigned values for mission critical | C1-195042 | imported from 3GU |
| S3‑193927 | Reply LS on NAS Aspects of Mobile-terminated Early Data Transmission | C1-195111 | imported from 3GU |
| S3‑193928 | Reply LS on Mobile-terminated Early Data Transmission | R2-1911603 | imported from 3GU |
| S3‑193929 | LS on network slice-specific authentication and authorization | C1-196903 | imported from 3GU |
| S3‑193930 | LS on how the IWF obtains key material for interworking group and private communications | C1-196979 | imported from 3GU |
| S3‑193931 | LS on Clarification on the requirement for steering of roaming | C1-197001 | imported from 3GU |
| S3‑193932 | LS on O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs | O-RAN Alliance | imported from 3GU |
| S3‑193933 | Reply LS to “O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs” | SP-190947 | imported from 3GU |
| S3‑193934 | LS on AS key derivation for conditional handover | R2-1911565 | imported from 3GU |
| S3‑193935 | LS on impact on UTRAN of 5G SRVCC | R2-1911753 | imported from 3GU |
| S3‑193936 | Reply LS on bulk authentication issue for IoT devices | R2-1911790 | imported from 3GU |
| S3‑193937 | LS on misalignment in Counter Check Procedure | R2-1911837 | imported from 3GU |
| S3‑193938 | Reply LS on Handling of UE radio network capabilities in 4G and 5G | R2-1911850 | imported from 3GU |
| S3‑193939 | LS on PC5-S Signaling and PC5-RRC connection for NR sidelink communication | R2-1914151 | imported from 3GU |
| S3‑193940 | LS to SA3 on False Base Station Detection | R3-196256 | imported from 3GU |
| S3‑193941 | Reply LS to SA3 on FBS detection | R2-1914224 | imported from 3GU |
| S3‑193942 | LS on security for multi-CU-UP connectivity | R3-194784 | imported from 3GU |
| S3‑193943 | Reply LS on eSBA NF Set | S2-1910148 | imported from 3GU |
| S3‑193944 | Reply LS on LS on the IAB-indication to core network | S2-1910281 | imported from 3GU |
| S3‑193945 | Reply LS on AUSF role in slice specific authentication | S2-1910668 | imported from 3GU |
| S3‑193946 | LS Response Reply LS on support of non-3GPP only UE and support for PEI in IMEI format | S2-1910679 | imported from 3GU |
| S3‑193947 | LS Response on Security Aspects of AMF Re-allocation Procedure | S2-1910724 | imported from 3GU |
| S3‑193948 | Reply LS on RRC Connection Reestablishment for CP for NB-IoT connected to 5GC | S2-1910789 | imported from 3GU |
| S3‑193949 | Reply LS on UP gateway function on the N9 interface | S2-1910808 | imported from 3GU |
| S3‑193950 | 256 bit radio interface algorithm performance | ETSI SAGE | imported from 3GU |
| S3‑193951 | LS on Enhancing Location Information Reporting with Dual Connectivity | S3i190671 | imported from 3GU |
| S3‑193952 | LS on SG17 new work item X.sles “Security measures for location enabled smart office services” | ITU-T SG17 | imported from 3GU |
| S3‑193953 | LS on SG17 new work item X.nsom-sec “Security requirements and architecture for network slice orchestration and management” | ITU-T SG17 | imported from 3GU |
| S3‑193954 | LS on status of draft Recommendation ITU-T Q.SR-Trust “Signalling requirements and architecture for interconnection between trustable network entities” | ITU-T SG11 | imported from 3GU |
| S3‑193955 | LS on SG11 activities related to improvement of the SS7 security including for digital financial services | SP-190586 | imported from 3GU |
| S3‑193956 | LS on SUCI computation from an NSI | CP-192262 | imported from 3GU |
| S3‑193957 | N9HR Regulatory Obligations | S3i190548 | imported from 3GU |
| S3‑193958 | LS on security consideration of performance measurement function protocol | C1-196940 | imported from 3GU |
| S3‑193959 | TR 33.836 – update of evaluation for the solution #2 | InterDigital Communications | imported from 3GU |
| S3‑193960 | 33.836 – update of evaluation for the Solution #1 | InterDigital Communications | imported from 3GU |
| S3‑193961 | TR 33.836 – update of evaluation for the solution #4 | InterDigital Communications | imported from 3GU |
| S3‑193962 | TR 33.836 - proposed conclusion for KI#1 | InterDigital Communications | imported from 3GU |
| S3‑193963 | TR 33.836 - Proposed conclusion for KI#2 | InterDigital Communications | imported from 3GU |
| S3‑193964 | TR 33.813 - update for solution #11 | InterDigital Communications | imported from 3GU |
| S3‑193965 | Draft for ‘proposed structure for network slice security procedures’ | InterDigital Communications | imported from 3GU |
| S3‑193966 | draft Reply LS_on_CHO key derivation | Apple | imported from 3GU |
| S3‑193967 | Discussion on Consecutive CHO key derivation | Apple | imported from 3GU |
| S3‑193968 | 33401-CR on CHO key derivation | Apple | imported from 3GU |
| S3‑193969 | 33501-CR on CHO key derivation | Apple | imported from 3GU |
| S3‑193970 | Discussion on PMF Protocol Security | Apple | imported from 3GU |
| S3‑193971 | draft reply LS on security consideration of PMF | Apple | imported from 3GU |
| S3‑193972 | UP IP-update for solution#9 | Apple | imported from 3GU |
| S3‑193973 | AUTH_Enh-update for solution#9 | Apple | imported from 3GU |
| S3‑193974 | AUTH_Enh-Evaluation for solution#2.4 | Apple | imported from 3GU |
| S3‑193975 | 5GFBS-conclusion of key issue#2 | Apple | imported from 3GU |
| S3‑193976 | 5GFBS-Update for solution#7 | Apple | imported from 3GU |
| S3‑193977 | SID on privacy enhancement of 3GPP access and non-3GPP access in EPS | Apple | imported from 3GU |
| S3‑193978 | Issue of re-authentication when AMF re-allocation via NAS reroute | vivo, Apple | imported from 3GU |
| S3‑193979 | New WID on eV2X security | LG Electronics Inc. | imported from 3GU |
| S3‑193980 | Conclusion for Key issue 10 | LG Electronics Inc. | imported from 3GU |
| S3‑193981 | Conclusion for Key issue 9 | LG Electronics Inc. | imported from 3GU |
| S3‑193982 | Skeleton for TS on eV2X | LG Electronics Inc. | imported from 3GU |
| S3‑193983 | Update to Key Issue #6 | KPN, China Mobile | imported from 3GU |
| S3‑193984 | Update to Key Issue #6 | KPN, China Mobile | imported from 3GU |
| S3‑193985 | End-to-end security | KPN, China Mobile | imported from 3GU |
| S3‑193986 | Authentication subscription data | KPN, Nokia | imported from 3GU |
| S3‑193987 | Introduction of the Inter PLMN UP security function in the architecture | Deutsche Telekom AG | imported from 3GU |
| S3‑193988 | LTKUP: editorial corrections to solution 5 in TR 33.935 | THALES | imported from 3GU |
| S3‑193989 | Reply LS on UP gateway function on the N9 interface | Juniper Networks | imported from 3GU |
| S3‑193990 | Draft LS on PC5 unicast and groupcast security protection | InterDigital Communications | imported from 3GU |
| S3‑193991 | KI 14 Potential Security Requirement | NIST, ATT, Sprint Corporation, CableLabs, Deutsche Telekom AG, Cisco | imported from 3GU |
| S3‑193992 | New Solution for KI #14 | NIST, ATT, Sprint, CableLabs, Deutsche Telekom AG, Cisco | imported from 3GU |
| S3‑193993 | [33.180] R14 - Fix bad reference | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑193994 | [33.180] R15 Fix bad reference (mirror) | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑193995 | [33.180] R16 Fix bad reference (mirror) | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑193996 | [33.180] R16 - Consistent use of off-network | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑193997 | [33.180] R16 KM client to KMS security | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑193998 | [33.180] R16 - TrK ID and InK ID | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑193999 | [33.180] R16 - InterSD KM record | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑194000 | [33.180] R16 ETSI Plugtest clarifications | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑194001 | LS to CT1 on 3rd ETSI MCX Remote Plugtest | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑194002 | DTR 33848 KI1 – clause 5_2_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194003 | DTR 33848 KI2 – clause 5_3_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194004 | DTR 33848 KI3 – clause 5_4_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194005 | DTR 33848 KI4 – clause 5_5_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194006 | DTR 33848 KI5 – clause 5_6_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194007 | DTR 33848 KI6 – clause 5_7_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194008 | DTR 33848 KI7 – clause 5_8_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194009 | DTR 33848 KI8 – clause 5_9_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194010 | DTR 33848 KI9 – clause 5_10_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194011 | DTR 33848 KI11 – clause 5_12_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194012 | DTR 33848 KI12 – clause 5_13_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194013 | DTR 33848 KI13 – clause 5_14_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194014 | DTR 33848 KI14 – clause 5_15_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194015 | DTR 33848 KI15 – clause 5_16_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194016 | DTR 33848 KI16 – clause 5_17_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194017 | DTR 33848 KI17 – clause 5_18_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194018 | DTR 33848 KI18 – clause 5_19_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194019 | DTR 33848 KI19 – clauses 5_20_2 and 3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194020 | DTR 33848 KI20 – clause 5_21_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194021 | DTR 33848 KI21 – clause 5_22_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194022 | DTR 33848 KI22 – clause 5_23_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194023 | DTR 33848 KI23 – clause 5_24_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194024 | DTR 33848 KI24 – clause 5_25_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194025 | Discussion on CHO key derivation | Apple | imported from 3GU |
| S3‑194026 | AUTH_Enh-update for solution#4.1 | Apple | imported from 3GU |
| S3‑194027 | Horizontal derivation when AMF re-allocation | Apple, vivo | imported from 3GU |
| S3‑194028 | 5GFBS-Update for solution#11 | Apple | imported from 3GU |
| S3‑194029 | SID on privacy enhancement of 3GPP access and non-3GPP access in EPS | Apple, Google, AT&T, Verizon UK Ltd, Accuris Networks, Charter Communications, Cablelabs, ARTICLE19, Sprint, Broadcom, Comcast | imported from 3GU |
| S3‑194030 | Removing ENs in annex X in the living document for 5WWC | CableLabs, Charter Communications, Rogers Communications, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194031 | CR-R16-Horizontal derivation when AMF re-allocation | Apple, vivo | imported from 3GU |
| S3‑194032 | Update solution 4 to clarify MIB/SIB Hash report | Huawei, HiSilicon | imported from 3GU |
| S3‑194033 | Reply LS to RAN2 on FBS detection | Huawei, HiSilicon | imported from 3GU |
| S3‑194034 | Preventing UE from Connecting to FBSs | Huawei, HiSilicon | imported from 3GU |
| S3‑194035 | Preventing UE from reselecting to FBS | Huawei, HiSilicon | imported from 3GU |
| S3‑194036 | Handover UE under MitM FBS attacks | Huawei, HiSilicon | imported from 3GU |
| S3‑194037 | Conclusion for Key Issue #3 | Huawei, HiSilicon | imported from 3GU |
| S3‑194038 | Conclusion for Key Issue #4 | Huawei, HiSilicon | imported from 3GU |
| S3‑194039 | Conclusion for Key Issue #8 | Huawei, HiSilicon | imported from 3GU |
| S3‑194040 | Conclusion for Key Issue #9 | Huawei, HiSilicon | imported from 3GU |
| S3‑194041 | New Solution for secure identifier conversion in groupcast | Huawei, HiSilicon | imported from 3GU |
| S3‑194042 | New solution to KI#9 | Huawei, HiSilicon | imported from 3GU |
| S3‑194043 | Addition of security threats and security requirements to KI#9 | Huawei, HiSilicon | imported from 3GU |
| S3‑194044 | Conclusions to KI #6 | Huawei, HiSilicon | imported from 3GU |
| S3‑194045 | Add content to Clause X.X.2 of eNS | Huawei, HiSilicon | imported from 3GU |
| S3‑194046 | Amendment to Clause X.X.3 of Slice specific authentication procedure | Huawei, HiSilicon | imported from 3GU |
| S3‑194047 | Note for the User ID privacy protection in Clause X.X.3 | Huawei, HiSilicon | imported from 3GU |
| S3‑194048 | Discussion on Authentication method negotiation | Huawei, HiSilicon | imported from 3GU |
| S3‑194049 | Authentication method negotiation | Huawei, HiSilicon | imported from 3GU |
| S3‑194050 | Conclusion to KI#3 | Huawei, HiSilicon | imported from 3GU |
| S3‑194051 | Solution 8 update | Huawei, HiSilicon | imported from 3GU |
| S3‑194052 | Overal evaluation to solutions addressing KI#6 | Huawei, HiSilicon | imported from 3GU |
| S3‑194053 | Conclusions to KI #6 | Huawei, HiSilicon | imported from 3GU |
| S3‑194054 | Discussion on LS from SA2 on AUSF role | Huawei, HiSilicon | imported from 3GU |
| S3‑194055 | Discussion paper on LS (R2-1911565) on AS key derivation for Conditional Handovertional | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194056 | Discussion on LS R3-194784 on Disaggregated CU-UPs in different security domains | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194057 | Discussion paper on PMF protocol security S3-193680 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194058 | Proposed text for clause x.2 of living CR for eNS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194059 | Key Issue#7 on revocation of rejected NSSAI | Nokia, Nokia Shnghai Bell, Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194060 | Solution for KI#7 on revocation of rejected NSSAI | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194061 | URLLC living CR: clarifications related to security policy | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194062 | Way forward on key issue 2 in TR 33.809 | CableLabs | imported from 3GU |
| S3‑194063 | Top research papers published in 2019 on 4G and 5G security | CableLabs | imported from 3GU |
| S3‑194064 | LS on security consideration of performance measurement function protocol | ZTE Corporation | imported from 3GU |
| S3‑194065 | Considerations on security handling of registration with AMF re-allocation | ZTE Corporation | imported from 3GU |
| S3‑194066 | Security handling in registration with AMF re-allocation | ZTE Corporation | imported from 3GU |
| S3‑194067 | Editorial correction in TS 33.519 | ZTE Corporation | imported from 3GU |
| S3‑194068 | Update of solution #12 in TR 33.813 | ZTE Corporation | imported from 3GU |
| S3‑194069 | Update of key issue #3.2 in TR 33.846 | ZTE Corporation | imported from 3GU |
| S3‑194070 | Solution of mitigating the SUPI guessing attacks | ZTE Corporation | imported from 3GU |
| S3‑194071 | Update of solution #2.1 in TR 33.846 | ZTE Corporation | imported from 3GU |
| S3‑194072 | Key issue on security attack caused by IAB-node with removable UICC card | ZTE Corporation | imported from 3GU |
| S3‑194073 | Definition of IAB-MT | ZTE Corporation | imported from 3GU |
| S3‑194074 | Add a note to key issue #9 in TR 33.836 | ZTE Corporation | imported from 3GU |
| S3‑194075 | Reply LS on Handling of UE radio network capabilities in 4G and 5G | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194076 | Correction of handling of 5G security contexts during EPS to 5GS idle mode mobility | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194077 | Conclusion for Key issue 15 | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194078 | New SID on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194079 | Security solution for UE Capability Transfer for UE with no AS security. | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194080 | Updates to Key issue Protection of UE capability transfer for UEs without AS security | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194081 | Updates to solution 9 | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194082 | Address the EN in Solution #17 | Huawei, Hisilicon | imported from 3GU |
| S3‑194083 | Conclusion on protection of time synchronization | Huawei, Hisilicon | imported from 3GU |
| S3‑194084 | Address the EN on the reference in key issue 4.1 | Huawei, Hisilicon | imported from 3GU |
| S3‑194085 | Add solution details and evaluation to solutioin 4.1 | Huawei, Hisilicon | imported from 3GU |
| S3‑194086 | Address the EN on the NAS procedure impact in Solution#2.4 | Huawei, Hisilicon | imported from 3GU |
| S3‑194087 | Add the threat and requirement in KI#15 | Huawei, Hisilicon | imported from 3GU |
| S3‑194088 | Protection of UE capability transfer for CP optimization only CIoT UE | Huawei, Hisilicon | imported from 3GU |
| S3‑194089 | Security attack caused by an unauthorized IAB device | Huawei, Hisilicon | imported from 3GU |
| S3‑194090 | resolving editor's note on the move of access point | Huawei, Hisilicon | imported from 3GU |
| S3‑194091 | Discussion on security of 5MBS enhancement | Huawei, Hisilicon | imported from 3GU |
| S3‑194092 | 5MBS_Sec_SID_SA3 | Huawei, Hisilicon | imported from 3GU |
| S3‑194093 | DraftCR_TSC protection | Huawei, Hisilicon | imported from 3GU |
| S3‑194094 | Adding evaluation to solution #10 in TR 33.813 | Huawei, Hisilicon | imported from 3GU |
| S3‑194095 | Providing some updates to Solution #15 in TR 33.836 | Huawei, Hisilicon | imported from 3GU |
| S3‑194096 | Evaluation of Solution #15 in TR 33.836 | Huawei, Hisilicon | imported from 3GU |
| S3‑194097 | Providing analysis to Solution #13 in TR 33.836 | Huawei, Hisilicon | imported from 3GU |
| S3‑194098 | Discussion on Security for truncation of 5G-S-TMSI | Huawei, Hisilicon | imported from 3GU |
| S3‑194099 | Security Procedure for RRCConnectionRe-establishment Procedure for Control Plane Optimization for 5GS CIoT | Huawei, Hisilicon | imported from 3GU |
| S3‑194100 | Reply LS to SA2 on Security Issue on 5G-S-TMSI Truncation Procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑194101 | CIoT Title Modifications to draft CR | Huawei, Hisilicon | imported from 3GU |
| S3‑194102 | Skeleton for Security handling in User Plane CIoT 5GS Optimization | Huawei, Hisilicon | imported from 3GU |
| S3‑194103 | General for Security handling in User Plane CIoT 5GS Optimization | Huawei, Hisilicon | imported from 3GU |
| S3‑194104 | Security handling in Connection Suspend Procedure for User Plane CIoT 5GS Optimization | Huawei, Hisilicon | imported from 3GU |
| S3‑194105 | Security handling in Connection Resume in CM-IDLE with Suspend to a new ng-eNB for User Plane CIoT 5GS Optimization | Huawei, Hisilicon | imported from 3GU |
| S3‑194106 | Security handling in Connection Resume in CM-IDLE with Suspend to the same ng-eNB for User Plane CIoT 5GS Optimization | Huawei, Hisilicon | imported from 3GU |
| S3‑194107 | Conclusion for RRC Resume Request Protection | Huawei, Hisilicon | imported from 3GU |
| S3‑194108 | Conclusion for Key Issue #2 | Huawei, Hisilicon | imported from 3GU |
| S3‑194109 | Evaluation for solution #7 | Huawei, Hisilicon | imported from 3GU |
| S3‑194110 | Address EN in solution 6 and solution 18 | Huawei, Hisilicon | imported from 3GU |
| S3‑194111 | Add Missing Procedure for Security Handling for RRCConnectionRe-establishment Procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑194112 | Mirror for Adding Missing Procedure for Security Handling for RRCConnectionRe-establishment Procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑194113 | Editorial change for trusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S3‑194114 | Update content for trusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S3‑194115 | Corrections on N5CW connects 5GC via trusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S3‑194116 | Using ERP for intra-TNAN mobility | Huawei, Hisilicon | imported from 3GU |
| S3‑194117 | Move Requirement of 5G-RG to clause 5 | Huawei, Hisilicon | imported from 3GU |
| S3‑194118 | Delete an assumption sentence | Huawei, Hisilicon | imported from 3GU |
| S3‑194119 | Add a new clause for N5CW privacy | Huawei, Hisilicon | imported from 3GU |
| S3‑194120 | UE activates UP IP over eUTRA to EPC | Huawei, Hisilicon | imported from 3GU |
| S3‑194121 | Update conclusion clause | Huawei, Hisilicon | imported from 3GU |
| S3‑194122 | Ensure the same setting for UP policy | Huawei, Hisilicon | imported from 3GU |
| S3‑194123 | Clarification on UP security policy preconfiguration | Huawei, Hisilicon | imported from 3GU |
| S3‑194124 | Further clarification on UP activation status | Huawei, Hisilicon | imported from 3GU |
| S3‑194125 | Clean up | Huawei, Hisilicon | imported from 3GU |
| S3‑194126 | Living doc for 5WWC | Huawei, Hisilicon | imported from 3GU |
| S3‑194127 | AKMA network functions | Huawei, Hisilicon | imported from 3GU |
| S3‑194128 | AKMA interface description | Huawei, Hisilicon | imported from 3GU |
| S3‑194129 | AKMA security principles and requirements | Huawei, Hisilicon | imported from 3GU |
| S3‑194130 | AKMA key management | Huawei, Hisilicon | imported from 3GU |
| S3‑194131 | Adding some evidence | Huawei, Hisilicon | imported from 3GU |
| S3‑194132 | Modify the message names | Huawei, Hisilicon | imported from 3GU |
| S3‑194133 | Fix the threat reference numbers for AMF | Huawei, Hisilicon | imported from 3GU |
| S3‑194134 | Amendment on 4.2.2.1.2 on AMF | Huawei, Hisilicon | imported from 3GU |
| S3‑194135 | Fix the threat reference numbers for UPF | Huawei, Hisilicon | imported from 3GU |
| S3‑194136 | Corrections on clause 4.3 | Huawei, Hisilicon | imported from 3GU |
| S3‑194137 | New SID: Study on Security Aspects of Enhancement of Support for Edge Computing in 5GC | China Unicom | imported from 3GU |
| S3‑194138 | Discussion on Security of Multi-CU-UP connectivity | CATT | imported from 3GU |
| S3‑194139 | LS reply to RAN WG3 LS on security for multi-CU-UP connectivity | CATT | imported from 3GU |
| S3‑194140 | Discussion about a new study on 5G Prose security | CATT | imported from 3GU |
| S3‑194141 | Clarifying interfaces in clause 5.2.3.3.4 and clause 5.2.3.4.5 | China Mobile | imported from 3GU |
| S3‑194142 | Discussion on the Xn-Handover message | CATT | imported from 3GU |
| S3‑194143 | Conclusion for KI#7 | Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194144 | Update of Solution#15 | Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194145 | Adding security requirements for GVNP of type 1 | China Mobile | imported from 3GU |
| S3‑194146 | Removal of Editor’s Note and update of the Figure 6.Y.4-1 | Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194147 | Adding security functional requirements deriving virtualisation and related test cases for GVNP of type 1 | China Mobile | imported from 3GU |
| S3‑194148 | Update of solution#14 | Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194149 | Solution#14 Evaluation | Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194150 | Draft CR as a living baseline for 5GS LCS normative work | CATT | imported from 3GU |
| S3‑194151 | Revise the Evaluations for Solution 5 in TR 33.853 | China Mobile | imported from 3GU |
| S3‑194152 | Discussion on the UP IP for 5G RAN connected 5GC | China Mobile | imported from 3GU |
| S3‑194153 | Draft CR for eLCS on access point security | CATT | imported from 3GU |
| S3‑194154 | Add the conclusion on the UP IP for 5G RAN connected to 5GC | China Mobile International Ltd | imported from 3GU |
| S3‑194155 | Solution for destination L2 privacy | Ericsson | imported from 3GU |
| S3‑194156 | Add Abrreviations to TS 33.535 | China Mobile, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194157 | Miscellaneous Editorial clarifications in 33.916 | Huawei, Hisilicon | imported from 3GU |
| S3‑194158 | Miscellaneous Editorial clarifications in 33.926 | Huawei, Hisilicon | imported from 3GU |
| S3‑194159 | Miscellaneous Editorial clarifications in 33.117 | Huawei, Hisilicon | imported from 3GU |
| S3‑194160 | Update on AKMA reference model | China Mobile, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194161 | Update of clause 4 | Huawei, Hisilicon | imported from 3GU |
| S3‑194162 | remove unspecified SDOs | Huawei, Hisilicon | imported from 3GU |
| S3‑194163 | Adding conclusion on KI #6.2 | Huawei, Hisilicon | imported from 3GU |
| S3‑194164 | CAG ID privacy | Huawei, Hisilicon | imported from 3GU |
| S3‑194165 | New KI: Service access authorization for non-delegated subscribe-notify | Huawei, Hisilicon | imported from 3GU |
| S3‑194166 | eSBA: add conclusion on KI #5 | Huawei, Hisilicon | imported from 3GU |
| S3‑194167 | eSBA: conclusion update on KI #22 | Huawei, Hisilicon | imported from 3GU |
| S3‑194168 | eSBA: conclusion update on KI #29 | Huawei, Hisilicon | imported from 3GU |
| S3‑194169 | Conclusion on KI #4.1 | Huawei, Hisilicon | imported from 3GU |
| S3‑194170 | Editoral changes on solution for AKMA change | Huawei, Hisilicon | imported from 3GU |
| S3‑194171 | Resolving the editor’s notes in the solution of AKMA change | Huawei, Hisilicon | imported from 3GU |
| S3‑194172 | AKMA: add conclusion on KI #17 | Huawei, Hisilicon | imported from 3GU |
| S3‑194173 | Resolving the EN and adding the evaluation of solution #17 | Huawei, Hisilicon | imported from 3GU |
| S3‑194174 | eV2X: Conclusion on KI#2 | Huawei, Hisilicon | imported from 3GU |
| S3‑194175 | eV2X: Solution for the UP security activation policy handling in NR PC5 unicast | Huawei, Hisilicon | imported from 3GU |
| S3‑194176 | eV2X: Conclusion on one requirement of KI#2 | Huawei, Hisilicon | imported from 3GU |
| S3‑194177 | eV2X: conclusion on KI #10 | Huawei, Hisilicon | imported from 3GU |
| S3‑194178 | eV2X: Conclusion on KI#2 | Huawei, Hisilicon | imported from 3GU |
| S3‑194179 | Clarification on aspects specific to the network product class UDM and AMF | Huawei, Hisilicon | imported from 3GU |
| S3‑194180 | New WID: Work Item on Security Assurance Specification for IMS | Huawei, Hisilicon | imported from 3GU |
| S3‑194181 | New SID: Study on Security Aspects of Enhancement of Support for Edge Computing in 5GC | Huawei, Hisilicon | imported from 3GU |
| S3‑194182 | New solution for authorization in the non-delegated "Subscribe-Notify" interaction scenarios | Huawei, Hisilicon | imported from 3GU |
| S3‑194183 | Update on solution#15 in TR 33.855 | Huawei, Hisilicon | imported from 3GU |
| S3‑194184 | Conclusion on authorization in the non-delegated Subscribe-Notify interaction scenarios | Huawei, Hisilicon | imported from 3GU |
| S3‑194185 | Conclusion on authorization in the delegated Subscribe-Notify interaction scenarios | Huawei, Hisilicon | imported from 3GU |
| S3‑194186 | Conclusion on service access authorization of a NF Set | Huawei, Hisilicon | imported from 3GU |
| S3‑194187 | Service access authorization of a NF Set | Huawei, Hisilicon | imported from 3GU |
| S3‑194188 | Resolving the ENs of solution#2.5 in the TR 33.846 | Huawei, Hisilicon | imported from 3GU |
| S3‑194189 | Resolving the ENs in KI#3.1 | Huawei, Hisilicon | imported from 3GU |
| S3‑194190 | Resolving the ENs of solution#5 in the TR 33.809 | Huawei, Hisilicon, Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194191 | Conclusion on mitigation against the authentication relay attack | Huawei, Hisilicon, Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194192 | Evaluation on service access authorization of a NF Set in non-roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S3‑194193 | Evaluation on service access authorization of a NF Set in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S3‑194194 | Security requirement on Key Issue #24: service access authorization of a NF Set | Huawei, Hisilicon | imported from 3GU |
| S3‑194195 | Solving registration failure in registration procedure with AMF reallocation | Huawei, Hisilicon | imported from 3GU |
| S3‑194196 | Clarification on AMF reallocation via direct NAS reroute for Rel-15 | Huawei, Hisilicon | imported from 3GU |
| S3‑194197 | Clarification on AMF reallocation via direct NAS reroute for Rel-16 | Huawei, Hisilicon | imported from 3GU |
| S3‑194198 | Clarification on primary authentication in direct NAS reroute for Rel-15 | Huawei, Hisilicon | imported from 3GU |
| S3‑194199 | Clarification on primary authentication in direct NAS reroute for Rel-16 | Huawei, Hisilicon | imported from 3GU |
| S3‑194200 | Add AAnF description into clause 4.2 | China Mobile, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194201 | Add content to clause 4.4 | China Mobile, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194202 | Updates to solution #7 - capability negotiation | Ericsson | imported from 3GU |
| S3‑194203 | Updates to solution #7 - network sharing | Ericsson | imported from 3GU |
| S3‑194204 | Updates to solution #7 - signature schemes and length | Ericsson | imported from 3GU |
| S3‑194205 | [DRAFT] LS out to SA5 about SON poisoning | Ericsson | imported from 3GU |
| S3‑194206 | [DRAFT] Reply LS on false base station detection | Ericsson | imported from 3GU |
| S3‑194207 | Way forward - KI#3 False RBS detection | Ericsson | imported from 3GU |
| S3‑194208 | Updates to solution #17 - resolving Ens | Ericsson | imported from 3GU |
| S3‑194209 | Conclusion on end to end security | China Mobile, KPN | imported from 3GU |
| S3‑194210 | Add abbreviations and editorial changes to TR 33.835 | China Mobile | imported from 3GU |
| S3‑194211 | Conclusion on KI#6 | Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194212 | DraftCR – Proposed call flow for Network Slice Specific Authentication and Authorization | Ericsson | imported from 3GU |
| S3‑194213 | DraftCR - Proposed flow for Re-authentication and Re-authorization | Ericsson | imported from 3GU |
| S3‑194214 | DraftCR - Proposed flow for clarifying primary authentication steps | Ericsson | imported from 3GU |
| S3‑194215 | DraftCR – Proposing a new AUSF service to support NSSAA flow | Ericsson | imported from 3GU |
| S3‑194216 | Cover sheet TR 33.835 | China Mobile International Ltd | imported from 3GU |
| S3‑194217 | Cover sheet TR 33.835 for approval | China Mobile | imported from 3GU |
| S3‑194218 | Discussion on new SID for enhanced security to support new Non Public Network evolvement | Ericsson | imported from 3GU |
| S3‑194219 | New SID: Study on enhanced security support for Non-Public Networks | Ericsson | imported from 3GU |
| S3‑194220 | New solution to preserve CAG-ID privacy | Ericsson | imported from 3GU |
| S3‑194221 | New conclusion to preserve CAG-ID privacy | Ericsson | imported from 3GU |
| S3‑194222 | New conclusion for handling UP security policy in a 5GLAN group | Ericsson | imported from 3GU |
| S3‑194223 | Update test cases for gNB SCAS | Huawei, Hisilicon | imported from 3GU |
| S3‑194224 | Fix some reference numbers | Huawei, Hisilicon | imported from 3GU |
| S3‑194225 | Resolve EN about how to ensure the UP security policy to be the same | Ericsson | imported from 3GU |
| S3‑194226 | Resolve EN about MN being preconfigured with SN capability to perform UP IP | Ericsson | imported from 3GU |
| S3‑194227 | Necessity discussion for security study of eNA phase 2 | China Mobile | imported from 3GU |
| S3‑194228 | Clause 6.X – Deriving AKMA key during UE registration | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S3‑194229 | Clause 6.Y – Deriving AF key for a specific Application function | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S3‑194230 | Add the conclusion on the UP IP for 5G RAN connected to 5GC | China Mobile | imported from 3GU |
| S3‑194231 | Add Definition of Execution Environment Interface in 33.818 | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S3‑194232 | [DRAFT] LS on SECAM Accreditation for Virtualised Network Products (VNPs) | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S3‑194233 | Proposed conclusion to KI#3 | Ericsson | imported from 3GU |
| S3‑194234 | Proposed revision of conclusion to KI#2 | Ericsson | imported from 3GU |
| S3‑194235 | Proposed conclusion to KI#1 | Ericsson | imported from 3GU |
| S3‑194236 | [Draft CR] RRC Connection Re-Establishment for the control plane for NB-IoT radio access connected to 5GC | Ericsson | imported from 3GU |
| S3‑194237 | [Draft CR] RRC Connection Resume and Suspend procedures for the user plane for NB-IoT radio access connected to 5GC | Ericsson | imported from 3GU |
| S3‑194238 | KI#15 - new requirement for handling UEs without AS security | Ericsson | imported from 3GU |
| S3‑194239 | KI#15 - new solution for handling UEs without AS security | Ericsson | imported from 3GU |
| S3‑194240 | Removal of three obsolete Editor’s Notes | Ericsson | imported from 3GU |
| S3‑194241 | DRAFT Reply LS on Handling of UE radio network capabilities in 4G and 5G | Ericsson | imported from 3GU |
| S3‑194242 | DraftCR – Living document for supporting 5G CIoT security | Ericsson | imported from 3GU |
| S3‑194243 | Security of RRC UE capability transfer procedure in EPS | Ericsson | imported from 3GU |
| S3‑194244 | RRC Connection Resume and Suspend procedures | Ericsson | imported from 3GU |
| S3‑194245 | RRC Connection Resume and Suspend procedures | Ericsson | imported from 3GU |
| S3‑194246 | Proposed conclusion to KI #14 | Ericsson | imported from 3GU |
| S3‑194247 | Key issue on Protection of long-term key during storage in UDR | KPN, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194248 | pCR for eV2X TS | Ericsson | imported from 3GU |
| S3‑194249 | Key issue on Protection of long-term key during transfer out of UDR | KPN, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194250 | Editorials and corrections to Security requirements for SeCoP | Ericsson | imported from 3GU |
| S3‑194251 | Editorials and corrections to Protection of N9 interface | Ericsson | imported from 3GU |
| S3‑194252 | Using Rel-15 token-based authorization in indirect communication scenarios | Ericsson | imported from 3GU |
| S3‑194253 | Conclusion of Key Issue #28: Service access authorization in the delegated "Subscribe-Notify" scenarios | Ericsson | imported from 3GU |
| S3‑194254 | Conclusion for Key Issue #5 "NF-NF Authorization" | Ericsson | imported from 3GU |
| S3‑194255 | Update to conclusion on Key issue #23: NF to NF authentication and authorization in Indirect communication | Ericsson | imported from 3GU |
| S3‑194256 | Security for roaming interfaces in indirect communication | Ericsson | imported from 3GU |
| S3‑194257 | Removal of Editor's Notes for Security of indirect communication in roaming scenarios | Ericsson | imported from 3GU |
| S3‑194258 | New Key issue on NF subtypes for authorization granularity | Ericsson | imported from 3GU |
| S3‑194259 | Update of Solution #32: OAuth 2.0 based resource level authorization of NF service consumers | Ericsson | imported from 3GU |
| S3‑194260 | Conclusion on NF subtypes for authorization granularity | Ericsson | imported from 3GU |
| S3‑194261 | Resource Level Authorization using Access Tokens | Ericsson | imported from 3GU |
| S3‑194262 | Authorization using Access Tokens based on NF-Subtype | Ericsson | imported from 3GU |
| S3‑194263 | Certificate and CRL profile update | Ericsson | imported from 3GU |
| S3‑194264 | TLS Recommended Cipher Suites | Ericsson | imported from 3GU |
| S3‑194265 | Required TLS extenstions and algorithms | Ericsson | imported from 3GU |
| S3‑194266 | IKEv2 profile update 33.210 | Ericsson | imported from 3GU |
| S3‑194267 | IKEv2 profile update 33.310 | Ericsson | imported from 3GU |
| S3‑194268 | Using EAP-TLS with TLS 1.3 | Ericsson | imported from 3GU |
| S3‑194269 | New WID on 3GPP profiles for cryptographic algorithms and IETF protocols | Ericsson | imported from 3GU |
| S3‑194270 | Test cases referring to TS 33.117 | Ericsson | imported from 3GU |
| S3‑194271 | Resolving ENs in Draft CR as a living baseline for 5GS LCS normative work | Ericsson | imported from 3GU |
| S3‑194272 | Update of the key hierarchy | Ericsson | imported from 3GU |
| S3‑194273 | Conclusions on Key Management | Ericsson | imported from 3GU |
| S3‑194274 | [Draft CR] Security requirements for F1 interface | Ericsson | imported from 3GU |
| S3‑194275 | [Draft CR] Security requirements on the IAB node, IAB donor and 5GC supporting IAB architecture | Ericsson | imported from 3GU |
| S3‑194276 | [Draft CR] Security mechanisms for the F1 interface between the IAB-node (gNB-DU) and the IAB-donor-CU | Ericsson | imported from 3GU |
| S3‑194277 | [Draft CR] General introduction to IAB-node Integration Procedure | Ericsson | imported from 3GU |
| S3‑194278 | [Draft CR] Authentication of IAB nodes | Ericsson | imported from 3GU |
| S3‑194279 | [Draft CR] Authorization of IAB nodes | Ericsson | imported from 3GU |
| S3‑194280 | [Draft CR] Update of general introduction to IAB | Ericsson | imported from 3GU |
| S3‑194281 | Draft CR - Security for Integrated Access and Backhaul in EN-DC | Ericsson | imported from 3GU |
| S3‑194282 | AMF re-allocation | Ericsson | imported from 3GU |
| S3‑194283 | TNAP mobility using ERP | Ericsson | imported from 3GU |
| S3‑194284 | Trusted access key hierarchy | Ericsson | imported from 3GU |
| S3‑194285 | Trusted access key derivation | Ericsson | imported from 3GU |
| S3‑194286 | Introducing missing definitions of untrusted and trusted non-3GPP accesses | Ericsson | imported from 3GU |
| S3‑194287 | Determining trust relationship in the UE | Ericsson | imported from 3GU |
| S3‑194288 | [DRAFT] Reply to: 256 bit radio interface algorithm performance | Ericsson | imported from 3GU |
| S3‑194289 | UP-IP: Resolving editor's note in solution #7 | Ericsson | imported from 3GU |
| S3‑194290 | Conclusion on Key Issue 6: UE connected to 5GC indicating support of UP IP over eUTRA | Ericsson | imported from 3GU |
| S3‑194291 | ARPF Deployment models | Ericsson | imported from 3GU |
| S3‑194292 | Security Parameter Storage | Ericsson | imported from 3GU |
| S3‑194293 | Idle mode mobility from 5GS to EPS | Ericsson | imported from 3GU |
| S3‑194294 | Idle mode mobility from 5GS to EPS | Ericsson | imported from 3GU |
| S3‑194295 | Idle mode mobility from EPS to 5GS | Ericsson | imported from 3GU |
| S3‑194296 | Idle mode mobility from EPS to 5GS | Ericsson | imported from 3GU |
| S3‑194297 | New KI: Existing authentication procedure lacking the PFS property | Ericsson | imported from 3GU |
| S3‑194298 | Error handling against violation of the basic validation rules | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194299 | 33.216 Corrections for clean-up and alignment R15 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194300 | 33.216 Corrections for clean-up and alignment R16 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194301 | 33.117 Adding abbreviations and corrections for alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194302 | Adding the provisioning of security policy to solution #16 | Qualcomm Incorporated | imported from 3GU |
| S3‑194303 | Resolving the Editor’s note on privacy in the evaluation of solution #8 | Qualcomm Incorporated | imported from 3GU |
| S3‑194304 | Protection of IEs in Direct Communication Request message | Qualcomm Incorporated | imported from 3GU |
| S3‑194305 | Proposal of an evaluation of solution protecting IEs in Direct Communication Request message | Qualcomm Incorporated | imported from 3GU |
| S3‑194306 | Proposal of an evaluation of solution #12 on protecting the traffic at the PDCP layer | Qualcomm Incorporated | imported from 3GU |
| S3‑194307 | Proposal of an evaluation of solution #16 on the activation of user plane security in NR PC5 unicast | Qualcomm Incorporated | imported from 3GU |
| S3‑194308 | Proposal conclusion for key issue #2 on security for eV2X unicast messages over PC5 | Qualcomm Incorporated | imported from 3GU |
| S3‑194309 | Proposed conclusion for Key Issue #1 on Unicast privacy | Qualcomm Incorporated | imported from 3GU |
| S3‑194310 | Proposed conclusion for Key Issue #4 on security of identifier conversion in groupcast communication | Qualcomm Incorporated | imported from 3GU |
| S3‑194311 | Proposed conclusion for Key Issue #6 on Security of the UE service authorization and revocation | Qualcomm Incorporated | imported from 3GU |
| S3‑194312 | Proposed text for the early clauses for V2X TS | Qualcomm Incorporated, LG Electronics | imported from 3GU |
| S3‑194313 | Proposed text for security for V2X over Uu reference point clause | Qualcomm Incorporated, LG Electronics | imported from 3GU |
| S3‑194314 | Proposed inclusion of groupcast and broadcast privacy solutions | Qualcomm Incorporated, LG Electronics | imported from 3GU |
| S3‑194315 | Solving AMF re-allocations issues for via the RAN | Qualcomm Incorporated | imported from 3GU |
| S3‑194316 | Update to the evaluation of solution #4.1 on protecting SQN in AKA re-synchronisations | Qualcomm Incorporated | imported from 3GU |
| S3‑194317 | Clarifications to solution #10 on protecting S-NSSAIs | Qualcomm Incorporated | imported from 3GU |
| S3‑194318 | Update to the evaluation of solution #10 on protecting S-NSSAIs | Qualcomm Incorporated | imported from 3GU |
| S3‑194319 | Removing editor's note on capturing all the details for alternative authentication methods | Qualcomm Incorporated | imported from 3GU |
| S3‑194320 | Reply LS to SA2 on RRC Connection Reestablishment for CP for NB-IoT | Qualcomm Incorporated | imported from 3GU |
| S3‑194321 | CR on clarification of ARFCN in KgNB derivation | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194322 | CR on clarification of ARFCN in KgNB derivation | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194323 | RRC UE capability transfer procedure for CP only CIoT UEs | Qualcomm Incorporated | imported from 3GU |
| S3‑194324 | Security Requirement for KI #15 | Qualcomm Incorporated | imported from 3GU |
| S3‑194325 | AMF verification of the UE radio capabilities for CP optimization only CIoT UE | Qualcomm Incorporated | imported from 3GU |
| S3‑194326 | Hash based UE capability protection for CP optimization only CIoT UE | Qualcomm Incorporated | imported from 3GU |
| S3‑194327 | Shared key based MIB/SIBs integrity information provided by gNB | Qualcomm Incorporated | imported from 3GU |
| S3‑194328 | Evaluation on UE behavior on detection of false signature | Qualcomm Incorporated | imported from 3GU |
| S3‑194329 | Evaluation on signing key management | Qualcomm Incorporated | imported from 3GU |
| S3‑194330 | Solution #4 Evaluation (Enriched MR) | Qualcomm Incorporated | imported from 3GU |
| S3‑194331 | Evaluation on Solution #3.1 | Qualcomm Incorporated, Ericsson | imported from 3GU |
| S3‑194332 | Evaluation on Solution #4.2 | Qualcomm Incorporated, Ericsson | imported from 3GU |
| S3‑194333 | Conclusion on KI #4.1 | Qualcomm Incorporated, Ericsson | imported from 3GU |
| S3‑194334 | Reply LS to SAGE on 256-bit algorithms | Qualcomm Incorporated | imported from 3GU |
| S3‑194335 | Reply LS on SUCI computation from an NSI | Qualcomm Incorporated | imported from 3GU |
| S3‑194336 | Reply LS on PMF | Qualcomm Incorporated | imported from 3GU |
| S3‑194337 | Security aspects of RLOS | Qualcomm Incorporated | imported from 3GU |
| S3‑194338 | Proposed conclusion for KI#6 in TR 33.853 | Qualcomm Incorporated | imported from 3GU |
| S3‑194339 | Proposed way forward for KI#2 in TR 33.809 | Qualcomm Incorporated | imported from 3GU |
| S3‑194340 | pCR: Adding UE – AF interface to the AKMA Reference Model | Qualcomm Incorporated | imported from 3GU |
| S3‑194341 | pCR: pCR: Udpate of AKMA Key Hierarchy | Qualcomm Incorporated | imported from 3GU |
| S3‑194342 | 33.511 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194343 | 33.512 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194344 | 33.513 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194345 | 33.514 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194346 | New KI: Existing authentication procedure lacking the PFS property | Ericsson | imported from 3GU |
| S3‑194347 | 33.515 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194348 | 33.516 Corrections for alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194349 | 33.517 Adding abbreviations and corrections for alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194350 | 33.518 Adding abbreviations and corrections for alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194351 | 33.519 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194352 | Security requirements for UP Gateway Function | Nokia, Nokia Shanghai Bell, Juniper | imported from 3GU |
| S3‑194353 | TR 33.848 Solution – lock-down of infrastructure | NCSC | imported from 3GU |
| S3‑194354 | TR 33.848 Solution – trust domains and separation | NCSC | imported from 3GU |
| S3‑194355 | Protection of N9 interface | Nokia, Nokia Shanghai Bell, Juniper Networks | imported from 3GU |
| S3‑194356 | New WID for User Plane Gateway Function for the Inter-PLMN Security | Juniper Networks | imported from 3GU |
| S3‑194357 | Updates to Counter Check Procedure (Rel-15) | Samsung | imported from 3GU |
| S3‑194358 | Updates to Counter Check Procedure (Rel-16) | Samsung | imported from 3GU |
| S3‑194359 | Security requirements for SeCoP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194360 | Description of CAPIF reference point: 3e,4e,5e,7 and 7e | Samsung | imported from 3GU |
| S3‑194361 | Authentication and authorization between SeCoP and network functions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194362 | Algorithm negotiation procedure for MC Service | Samsung | imported from 3GU |
| S3‑194363 | Authentication and authorization between SeCoPs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194364 | Updates to Solution #2.1 on MT functionality | Samsung, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194365 | Resource Level Authorization using Access Tokens | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194366 | Updates and evaluation of solution #3.1 | Samsung | imported from 3GU |
| S3‑194367 | TLS between NF and SEPP based on custom HTTP header | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194368 | Requirements for Secure environment of the IAB node | Samsung | imported from 3GU |
| S3‑194369 | IAB-node integration procedure | Samsung | imported from 3GU |
| S3‑194370 | Mutual authentication between Network Functions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194371 | IAB-UE part set-up procedure | Samsung | imported from 3GU |
| S3‑194372 | NF consumer authentication by the producer in direct communication scenarios | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194373 | F1 interface set-up procedure | Samsung | imported from 3GU |
| S3‑194374 | TLS entity certificate profile for SBA | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194375 | Solution for IAB Architecture | Samsung | imported from 3GU |
| S3‑194376 | SBA Network Function TLS certificate profile | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194377 | Solution #13 Evaluation and Conclusion | Samsung, Intel | imported from 3GU |
| S3‑194378 | Update to 5G_eSBA WID | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194379 | New Solution to Key Issue #6.2 | Samsung | imported from 3GU |
| S3‑194380 | Discussion paper on authorization for Model D Indirect communications | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194381 | Udpate to Solution #3 | Samsung | imported from 3GU |
| S3‑194382 | Update to conclusion on Key issue #22: Authorization of NF service access in indirect communication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194383 | Key Issue #6.1 conclusion | Samsung | imported from 3GU |
| S3‑194384 | Conclusion for Key Issues #6.1 and #6.2 | Samsung | imported from 3GU |
| S3‑194385 | Updated TR33.845 - includes docs agreed at SA3#95 Adhoc | Vodafone España SA | imported from 3GU |
| S3‑194386 | CAG cell access check | Samsung | imported from 3GU |
| S3‑194387 | Skeleton for SEAL TS 33.434 | Samsung | imported from 3GU |
| S3‑194388 | Scope for SEAL TS 33.434 | Samsung | imported from 3GU |
| S3‑194389 | Adding reference, term, abbreviation to the SEAL TS 33.434 | Samsung | imported from 3GU |
| S3‑194390 | Security requirements for SEAL | Samsung | imported from 3GU |
| S3‑194391 | Security for SEAL interfaces | Samsung | imported from 3GU |
| S3‑194392 | VAL user authentication and authorization | Samsung | imported from 3GU |
| S3‑194393 | Security procedure for S-KMC and S-KMS | Samsung | imported from 3GU |
| S3‑194394 | Annex X: OpenID Connect | Samsung | imported from 3GU |
| S3‑194395 | Annex Y for TS 33.434 | Samsung | imported from 3GU |
| S3‑194396 | Conclusion to Key Issue #5 | Samsung | imported from 3GU |
| S3‑194397 | UPGF - Align with Inter PLMN UP Security Function (IPUPS) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194398 | Requirements for KI#18 The Startup Paradox | Ericsson | imported from 3GU |
| S3‑194399 | Source IP address range check for UPGF | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194400 | Removing ENs in annex X in the living document for 5WWC | CableLabs, Charter Communications,Lenovo, Motorola Mobility, EricssonRogers Communications, Nokia, Nokia Shanghai Bell, | imported from 3GU |
| S3‑194401 | NPN clarifications | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194402 | Removal of ed.note on conformance tests | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194403 | CAG ID privacy conclusion | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194404 | CAG ID privacy | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194405 | Annex 5GLAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194406 | Annex TSC security intro | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194407 | TSC gPTP message protection | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194408 | TSC conclusion | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194409 | Authentication of a TSC enabled UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194410 | UP security in TSC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194411 | UDR study - title correction | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194412 | UDR study - intro | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194413 | Privacy solution for groupcast | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194414 | Evaluation to privacy solution for groupcast | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194415 | Discussion of New Study - eNPN Vertical_LAN_SEC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194416 | Enhanced NPN Security for Vertical and LAN Services.doc | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194417 | [Draft CR]Solution for IAB Architecture (Baseline version) | Samsung | imported from 3GU |
| S3‑194418 | Comment on S3-194061 | Huawei, HiSilicon | imported from 3GU |
| S3‑194419 | Clarification on aspects specific to the network product class UDM and AMF | Huawei, Hisilicon | imported from 3GU |
| S3‑194420 | Comments on S3-194315 | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S3‑194421 | living CR of URLLC | Huawei, Hisilicon | imported from 3GU |
| S3‑194422 | TSC conclusion | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194423 | TSC gPTP message protection | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194424 | UP security in TSC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194425 | Update on solution#15 in TR 33.855 | Huawei, Hisilicon | imported from 3GU |
| S3‑194426 | Forwarding of Reply LS on GUTI allocation for 5G CIoT | C1-198560 | imported from 3GU |
| S3‑194427 | Security for TSC service | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194428 | Annex 5GLAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194429 | Commenting on S3-194222 | Nokia Germany | imported from 3GU |
| S3‑194430 | Commenting contribution on S3-194261 – Resource Level Authorization using Access Tokens | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194431 | Nokia comments on S3-193970 PMF protocol security | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194432 | Comments to S3-194019 DTR 33.848, Key Issue #19 Clauses 5.20.2 and 5.20.3 | Ericsson | imported from 3GU |
| S3‑194433 | Reply LS on how the IWF obtains key material for interworking group and private communications | S6-192194 | imported from 3GU |
| S3‑194434 | LS on Application Architecture for enabling Edge Applications | S6-192399 | imported from 3GU |
| S3‑194435 | LS on native 5G NAS security context activation | C1-199003 | imported from 3GU |
| S3‑194436 | LS on GUTI allocation for MT-EDT in 5G CIoT | C1-199005 | imported from 3GU |
| S3‑194437 | LS on Use of 3gpp-Sbi-Target-apiRoot header in HTTP requests from NFs to SEPP | C4-195375 | imported from 3GU |
| S3‑194438 | Reply LS on GTP Recovery Counter & GSN node behaviour | C4-195518 | imported from 3GU |
| S3‑194439 | LS on ARPF in UDICOM | C4-195553 | imported from 3GU |
| S3‑194440 | LS on usage of IMSI during 3GPP based authentication | C4-195574 | imported from 3GU |
| S3‑194441 | LS on user identity when 5G-AKA or EAP AKA’ is used for SNPN | C6-190468 | imported from 3GU |
| S3‑194442 | Agenda | WG Chairman | imported from 3GU |
| S3‑194443 | Security requirements for UP Gateway Function | Nokia, Nokia Shanghai Bell, Juniper | imported from 3GU |
| S3‑194444 | Protection of N9 interface | Nokia, Nokia Shanghai Bell, Juniper Networks | imported from 3GU |
| S3‑194445 | New WID for User Plane Gateway Function for the Inter-PLMN Security | Juniper Networks | imported from 3GU |
| S3‑194446 | Security requirements for SeCoP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194447 | Reply LS_on_CHO key derivation | Apple | imported from 3GU |
| S3‑194448 | 33501-CR on CHO key derivation | Apple | imported from 3GU |
| S3‑194449 | Updates to Counter Check Procedure (Rel-15) | Samsung | imported from 3GU |
| S3‑194450 | LS reply to RAN WG3 LS on security for multi-CU-UP connectivity | CATT | imported from 3GU |
| S3‑194451 | Reply to: LS on security consideration of performance measurement function protocol | ZTE | imported from 3GU |
| S3‑194452 | Reply LS on UP gateway function on the N9 interface | Juniper Networks | imported from 3GU |
| S3‑194453 | Reply to: LS on Use of 3gpp-Sbi-Target-apiRoot header in HTTP requests from NFs to SEPP | Nokia | imported from 3GU |
| S3‑194454 | Reply to: LS on usage of IMSI during 3GPP based authentication | Nokia | imported from 3GU |
| S3‑194455 | Reply to: LS on user identity when 5G-AKA or EAP AKA’ is used for SNPN | Samsung | imported from 3GU |
| S3‑194456 | Reply to: 256 bit radio interface algorithm performance | Ericsson | imported from 3GU |
| S3‑194457 | Correction of handling of 5G security contexts during EPS to 5GS idle mode mobility | Intel | imported from 3GU |
| S3‑194458 | Correction of handling of 5G security contexts during EPS to 5GS idle mode mobility | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194459 | Adding TSC abbreviation | Nokia | imported from 3GU |
| S3‑194460 | Idle mode mobility from EPS to 5GS | Ericsson | imported from 3GU |
| S3‑194461 | Idle mode mobility from EPS to 5GS | Ericsson | imported from 3GU |
| S3‑194462 | Add Missing Procedure for Security Handling for RRCConnectionRe-establishment Procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑194463 | Source IP address range check for UPGF | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194464 | Description of CAPIF reference point: 3e,4e,5e,7 and 7e | Samsung | imported from 3GU |
| S3‑194465 | Draft CR as a living baseline for 5GS LCS normative work | CATT | imported from 3GU |
| S3‑194466 | Resolving ENs in Draft CR as a living baseline for 5GS LCS normative work | Ericsson,Huawei,CATT | imported from 3GU |
| S3‑194467 | living CR of URLLC | Huawei, Hisilicon | imported from 3GU |
| S3‑194468 | New WID on eV2X security | LG Electronics Inc. | imported from 3GU |
| S3‑194469 | Clean up | Huawei, Hisilicon | imported from 3GU |
| S3‑194470 | Resolve EN about how to ensure the UP security policy to be the same | Ericsson,Huawei | imported from 3GU |
| S3‑194471 | New SID on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194472 | URLLC living CR: clarifications related to security policy | Nokia, Nokia Shanghai Bell,Huawei,Ericsson | imported from 3GU |
| S3‑194473 | 33.511 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194474 | Update test cases for gNB SCAS | Huawei, Hisilicon | imported from 3GU |
| S3‑194475 | 33.512 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell,Huawei | imported from 3GU |
| S3‑194476 | 33.513 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell,Huawei | imported from 3GU |
| S3‑194477 | 33.515 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell,Futurewei | imported from 3GU |
| S3‑194478 | 33.517 Adding abbreviations and corrections for alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194479 | 33.519 Corrections for clean-up and alignment | Nokia, Nokia Shanghai Bell,ZTE | imported from 3GU |
| S3‑194480 | 33.216 Corrections for clean-up and alignment R15 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194481 | 33.216 Corrections for clean-up and alignment R16 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194482 | Reply to: Reply LS on RRC Connection Reestablishment for CP for NB-IoT connected to 5GC | Huawei | imported from 3GU |
| S3‑194483 | DraftCR – Living document for supporting 5G CIoT security | Ericsson | imported from 3GU |
| S3‑194484 | [Draft CR] RRC Connection Re-Establishment for the control plane for NB-IoT radio access connected to 5GC | Ericsson,Huawei | imported from 3GU |
| S3‑194485 | General for Security handling in User Plane CIoT 5GS Optimization | Huawei, Hisilicon | imported from 3GU |
| S3‑194486 | Security handling in Connection Suspend Procedure for User Plane CIoT 5GS Optimization | Huawei, Hisilicon | imported from 3GU |
| S3‑194487 | Security handling in Connection Resume in CM-IDLE with Suspend to a new ng-eNB for User Plane CIoT 5GS Optimization | Huawei, Hisilicon | imported from 3GU |
| S3‑194488 | Reply LS on Handling of UE radio network capabilities in 4G and 5G | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194489 | draft TR 33.861 | Ericsson | imported from 3GU |
| S3‑194490 | KI 14 Potential Security Requirement | NIST, ATT, Sprint Corporation, CableLabs, Deutsche Telekom AG, Cisco | imported from 3GU |
| S3‑194491 | Updates to Key issue Protection of UE capability transfer for UEs without AS security | Intel Corporation (UK) Ltd,Qualcomm,Huawei,Ericsson | imported from 3GU |
| S3‑194492 | New Solution for KI #14 | NIST, ATT, Sprint, CableLabs, Deutsche Telekom AG, Cisco | imported from 3GU |
| S3‑194493 | Protection of UE capability transfer for CP optimization only CIoT UE | Huawei, Hisilicon | imported from 3GU |
| S3‑194494 | Security solution for UE Capability Transfer for UE with no AS security. | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194495 | AMF verification of the UE radio capabilities for CP optimization only CIoT UE | Qualcomm Incorporated | imported from 3GU |
| S3‑194496 | KI#15 - new solution for handling UEs without AS security | Ericsson | imported from 3GU |
| S3‑194497 | Hash based UE capability protection for CP optimization only CIoT UE | Qualcomm Incorporated | imported from 3GU |
| S3‑194498 | Proposed conclusion to KI#1 | Ericsson | imported from 3GU |
| S3‑194499 | Consistent use of off-network | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑194500 | [33.180] R16 - TrK ID and InK ID | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑194501 | LS to CT1 on 3rd ETSI MCX Remote Plugtest | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑194502 | Minutes of the Mission Critical offline session | Qualcomm | imported from 3GU |
| S3‑194503 | Notes from the eSBA break out session | NTT-Docomo | imported from 3GU |
| S3‑194504 | Update to conclusion on Key issue #23: NF to NF authentication and authorization in Indirect communication | Ericsson | imported from 3GU |
| S3‑194505 | Security requirement on Key Issue #24: service access authorization of a NF Set | Huawei, Hisilicon | imported from 3GU |
| S3‑194506 | Evaluation on service access authorization of a NF Set in non-roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S3‑194507 | Evaluation on service access authorization of a NF Set in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S3‑194508 | Conclusion on service access authorization of a NF Set | Huawei, Hisilicon | imported from 3GU |
| S3‑194509 | Update on solution#15 in TR 33.855 | Huawei, Hisilicon | imported from 3GU |
| S3‑194510 | New KI: Service access authorization for non-delegated subscribe-notify | Huawei, Hisilicon | imported from 3GU |
| S3‑194511 | New solution for authorization in the non-delegated "Subscribe-Notify" interaction scenarios | Huawei, Hisilicon | imported from 3GU |
| S3‑194512 | eSBA: conclusion update on KI #29 | Huawei, Hisilicon | imported from 3GU |
| S3‑194513 | New Key issue on NF subtypes for authorization granularity | Ericsson | imported from 3GU |
| S3‑194514 | Conclusion for Key Issue #5 "NF-NF Authorization" | Ericsson | imported from 3GU |
| S3‑194515 | Removal of Editor's Notes for Security of indirect communication in roaming scenarios | Ericsson | imported from 3GU |
| S3‑194516 | Draft TR 33.855 | Ericsson | imported from 3GU |
| S3‑194517 | Editorials and corrections to Security requirements for SeCoP | Ericsson | imported from 3GU |
| S3‑194518 | TLS between NF and SEPP based on custom HTTP header | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194519 | Security for roaming interfaces in indirect communication | Ericsson,Nokia | imported from 3GU |
| S3‑194520 | Mutual authentication between Network Functions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194521 | NF consumer authentication by the producer in direct communication scenarios | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194522 | Using Rel-15 token-based authorization in indirect communication scenarios | Ericsson | imported from 3GU |
| S3‑194523 | Service access authorization of a NF Set | Huawei, Hisilicon | imported from 3GU |
| S3‑194524 | SBA Network Function TLS certificate profile | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194525 | New WID on Security Aspects of PARLOS | SPRINT Corporation | imported from 3GU |
| S3‑194526 | Skeleton for TS on eV2X | LG Electronics Inc. | imported from 3GU |
| S3‑194527 | New WID: Work Item on Security Assurance Specification for IMS | Huawei, Hisilicon | imported from 3GU |
| S3‑194528 | New WID on 3GPP profiles for cryptographic algorithms and IETF protocols | Ericsson | imported from 3GU |
| S3‑194529 | Living doc for 5WWC | Huawei, Hisilicon | imported from 3GU |
| S3‑194530 | Introducing missing definitions of untrusted and trusted non-3GPP accesses | Ericsson | imported from 3GU |
| S3‑194531 | Determining trust relationship in the UE | Ericsson | imported from 3GU |
| S3‑194532 | Editorial change for trusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S3‑194533 | Update content for trusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S3‑194534 | 256 bit algorithm candidates | ETIS SAGE | imported from 3GU |
| S3‑194535 | Reply to: Reply LS on AUSF role in slice specific authentication | Ericsson | imported from 3GU |
| S3‑194536 | Add content to Clause X.X.2 of eNS | Huawei, HiSilicon,Nokia,Ericsson, Interdigital | imported from 3GU |
| S3‑194537 | DraftCR – Proposed call flow for Network Slice Specific Authentication and Authorization | Ericsson,Huawei | imported from 3GU |
| S3‑194538 | Note for the User ID privacy protection in Clause X.X.3 | Huawei, HiSilicon | imported from 3GU |
| S3‑194539 | DraftCR - Proposed flow for Re-authentication and Re-authorization | Ericsson | imported from 3GU |
| S3‑194540 | DraftCR – Proposing a new AUSF service to support NSSAA flow | Ericsson | imported from 3GU |
| S3‑194541 | Living document on slice specific authentication procedures | Nokia | imported from 3GU |
| S3‑194542 | Solution 8 update | Huawei, HiSilicon | imported from 3GU |
| S3‑194543 | Draft TR 33.813 | Nokia | imported from 3GU |
| S3‑194544 | Clarifications to solution #10 on protecting S-NSSAIs | Qualcomm Incorporated | imported from 3GU |
| S3‑194545 | Update to the evaluation of solution #10 on protecting S-NSSAIs | Qualcomm Incorporated | imported from 3GU |
| S3‑194546 | TR 33.813 - update for the evaluation for solution #11 | InterDigital Communications | imported from 3GU |
| S3‑194547 | Update of solution #12 in TR 33.813 | ZTE Corporation | imported from 3GU |
| S3‑194548 | Reply LS on SUCI computation from an NSI | Qualcomm Incorporated | imported from 3GU |
| S3‑194549 | Removing editor's note on capturing all the details for alternative authentication methods | Qualcomm Incorporated | imported from 3GU |
| S3‑194550 | Access security for a TSC-enabled UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194551 | Draft TR 33.819 | Nokia | imported from 3GU |
| S3‑194552 | TSC conclusion | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194553 | UP security in TSC | Nokia, Nokia Shanghai Bell,Huawei | imported from 3GU |
| S3‑194554 | Reply LS on Sending CAG ID in NAS layer | R3-197591 | imported from 3GU |
| S3‑194555 | New conclusion for handling UP security policy in a 5GLAN group | Ericsson,Nokia | imported from 3GU |
| S3‑194556 | Udpate to Solution #3 | Samsung | imported from 3GU |
| S3‑194557 | New Solution to Key Issue #6.2 | Samsung | imported from 3GU |
| S3‑194558 | Solution #13 Evaluation and Conclusion | Samsung, Intel | imported from 3GU |
| S3‑194559 | Reply to: Reply LS on Sending CAG ID in NAS layer | Qualcomm | imported from 3GU |
| S3‑194560 | Notes on the security impacts on the virtualization offline session | NTT-Docomo | imported from 3GU |
| S3‑194561 | Corrections on clause 4.3 | Huawei, Hisilicon | imported from 3GU |
| S3‑194562 | remove unspecified SDOs | Huawei, Hisilicon | imported from 3GU |
| S3‑194563 | Clarifying interfaces in clause 5.2.3.3.4 and clause 5.2.3.4.5 | China Mobile,Nokia | imported from 3GU |
| S3‑194564 | Adding security requirements for GVNP of type 1 | China Mobile | imported from 3GU |
| S3‑194565 | Adding security functional requirements deriving virtualisation and related test cases for GVNP of type 1 | China Mobile | imported from 3GU |
| S3‑194566 | Draft TR 33.824 | Samsung | imported from 3GU |
| S3‑194567 | LS on SECAM Accreditation for Virtualised Network Products (VNPs) | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S3‑194568 | DTR 33848 KI1 – clause 5_2_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194569 | DTR 33848 KI2 – clause 5_3_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194570 | DTR 33848 KI3 – clause 5_4_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194571 | DTR 33848 KI4 – clause 5_5_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194572 | DTR 33848 KI5 – clause 5_6_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194573 | DTR 33848 KI6 – clause 5_7_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194574 | DTR 33848 KI7 – clause 5_8_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194575 | DTR 33848 KI8 – clause 5_9_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194576 | DTR 33848 KI9 – clause 5_10_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194577 | Updates and evaluation of solution #3.1 | Samsung | imported from 3GU |
| S3‑194578 | DTR 33848 KI11 – clause 5_12_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194579 | DTR 33848 KI12 – clause 5_13_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194580 | DTR 33848 KI13 – clause 5_14_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194581 | DTR 33848 KI14 – clause 5_15_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194582 | TR 33.848 Solution – lock-down of infrastructure | NCSC | imported from 3GU |
| S3‑194583 | TR 33.848 Solution – trust domains and separation | NCSC | imported from 3GU |
| S3‑194584 | DTR 33848 KI15 – clause 5_16_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194585 | DTR 33848 KI16 – clause 5_17_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194586 | Evaluation on Solution #4.2 | Qualcomm Incorporated, Ericsson | imported from 3GU |
| S3‑194587 | Requirements for KI#18 The Startup Paradox | Ericsson | imported from 3GU |
| S3‑194588 | Comments to S3-194019 DTR 33.848, Key Issue #19 Clauses 5.20.2 and 5.20.3 | Ericsson,T-Mobile | imported from 3GU |
| S3‑194589 | DTR 33848 KI20 – clause 5_21_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194590 | DTR 33848 KI21 – clause 5_22_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194591 | DTR 33848 KI22 – clause 5_23_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194592 | DTR 33848 KI23 – clause 5_24_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194593 | DTR 33848 KI24 – clause 5_25_3 | T-Mobile USA Inc. | imported from 3GU |
| S3‑194594 | Requirements for Secure environment of the IAB node | Samsung | imported from 3GU |
| S3‑194595 | [Draft CR] Security requirements on the IAB node, IAB donor and 5GC supporting IAB architecture | Ericsson | imported from 3GU |
| S3‑194596 | [Draft CR]Solution for IAB Architecture (Baseline version) | Samsung | imported from 3GU |
| S3‑194597 | IAB-node integration procedure | Samsung,Ericsson | imported from 3GU |
| S3‑194598 | IAB-UE part set-up procedure | Samsung,Ericsson | imported from 3GU |
| S3‑194599 | Solution for IAB Architecture | Samsung .Ericsson | imported from 3GU |
| S3‑194600 | Update to 5G_eSBA WID | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194601 | Updates to Counter Check Procedure (Rel-16) | Samsung | imported from 3GU |
| S3‑194602 | 33401-CR on CHO key derivation | Apple | imported from 3GU |
| S3‑194603 | Reply to: LS on IANA assigned values for mission critical | Motorola Solutions | imported from 3GU |
| S3‑194604 | Proposed conclusion to KI #14 | Ericsson | imported from 3GU |
| S3‑194605 | Notes on the V2X offline session | NTT-Docomo | imported from 3GU |
| S3‑194606 | Trusted access key hierarchy | Ericsson | imported from 3GU |
| S3‑194607 | Trusted access key derivation | Ericsson | imported from 3GU |
| S3‑194608 | Corrections on N5CW connects 5GC via trusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S3‑194609 | Move Requirement of 5G-RG to clause 5 | Huawei, Hisilicon | imported from 3GU |
| S3‑194610 | Removing ENs in annex X in the living document for 5WWC | CableLabs, Charter Communications,Lenovo, Motorola Mobility, EricssonRogers Communications, Nokia, Nokia Shanghai Bell, | imported from 3GU |
| S3‑194611 | LS to CT1 on 3rd ETSI MCX Remote Plugtest | Motorola Solutions UK Ltd. | imported from 3GU |
| S3‑194612 | Draft TR 33.818 | China Mobile | imported from 3GU |
| S3‑194613 | Proposed inclusion of groupcast and broadcast privacy solutions | Qualcomm Incorporated, LG Electronics,Ericsson | imported from 3GU |
| S3‑194614 | Proposed text for the early clauses for V2X TS | Qualcomm Incorporated, LG Electronics | imported from 3GU |
| S3‑194615 | Proposed text for security for V2X over Uu reference point clause | Qualcomm Incorporated, LG Electronics,Ericsson | imported from 3GU |
| S3‑194616 | 33.836 – update of evaluation for the Solution #1 | InterDigital Communications | imported from 3GU |
| S3‑194617 | TR 33.836 – update of evaluation for the solution #4 | InterDigital Communications | imported from 3GU |
| S3‑194618 | Proposed conclusion for Key Issue #1 on Unicast privacy | Qualcomm Incorporated,Interdigital | imported from 3GU |
| S3‑194619 | Updates to solution 9 | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑194620 | TR 33.836 – update of evaluation for the solution #2 | InterDigital Communications | imported from 3GU |
| S3‑194621 | Resolving the Editor’s note on privacy in the evaluation of solution #8 | Qualcomm Incorporated | imported from 3GU |
| S3‑194622 | Proposal of an evaluation of solution #12 on protecting the traffic at the PDCP layer | Qualcomm Incorporated | imported from 3GU |
| S3‑194623 | Adding the provisioning of security policy to solution #16 | Qualcomm Incorporated | imported from 3GU |
| S3‑194624 | Draft TR 33.848 | BT | imported from 3GU |
| S3‑194625 | Draft TS 33.xyz on V2X | Lge | imported from 3GU |
| S3‑194626 | Draft TR 33.836 | Lge | imported from 3GU |
| S3‑194627 | Skeleton for SEAL TS 33.434 | Samsung | imported from 3GU |
| S3‑194628 | Scope for SEAL TS 33.434 | Samsung | imported from 3GU |
| S3‑194629 | Adding reference, term, abbreviation to the SEAL TS 33.434 | Samsung | imported from 3GU |
| S3‑194630 | Draft TR 33.434 | Samsung | imported from 3GU |
| S3‑194631 | Security requirements for SEAL | Samsung | imported from 3GU |
| S3‑194632 | Security for SEAL interfaces | Samsung | imported from 3GU |
| S3‑194633 | Security aspects of RLOS | Qualcomm Incorporated | imported from 3GU |
| S3‑194634 | Draft TR 33.935 | Vodafone | imported from 3GU |
| S3‑194635 | Draft TR 33.835 | China Mobile | imported from 3GU |
| S3‑194636 | Conclusion on end to end security | China Mobile, KPN | imported from 3GU |
| S3‑194637 | Conclusions on Key Management | Ericsson | imported from 3GU |
| S3‑194638 | Editoral changes on solution for AKMA change | Huawei, Hisilicon | imported from 3GU |
| S3‑194639 | AKMA: add conclusion on KI #17 | Huawei, Hisilicon | imported from 3GU |
| S3‑194640 | Draft TS 33.535 | China Mobile | imported from 3GU |
| S3‑194641 | Add AAnF description into clause 4.2 | China Mobile, Nokia, Nokia Shanghai Bel, Huaweil | imported from 3GU |
| S3‑194642 | AKMA interface description | Huawei, Hisilicon | imported from 3GU |
| S3‑194643 | Add content to clause 4.4 | China Mobile, Nokia, Nokia Shanghai Bell,Huawei | imported from 3GU |
| S3‑194644 | AKMA key management | Huawei, Hisilicon | imported from 3GU |
| S3‑194645 | Clause 6.X – Deriving AKMA key during UE registration | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S3‑194646 | Proposal of an evaluation of solution #16 on the activation of user plane security in NR PC5 unicast | Qualcomm Incorporated | imported from 3GU |
| S3‑194647 | Resolving the EN and adding the evaluation of solution #17 | Huawei, Hisilicon | imported from 3GU |
| S3‑194648 | eV2X: Solution for the UP security activation policy handling in NR PC5 unicast | Huawei, Hisilicon | imported from 3GU |
| S3‑194649 | Protection of IEs in Direct Communication Request message | Qualcomm Incorporated | imported from 3GU |
| S3‑194650 | Proposal conclusion for key issue #2 on security for eV2X unicast messages over PC5 | Qualcomm Incorporated,Interdigital,Huawei | imported from 3GU |
| S3‑194651 | Solution#14 Evaluation | Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194652 | Algorithm negotiation procedure for MC Service | Samsung,Motorola Solutions | imported from 3GU |
| S3‑194653 | New Solution for secure identifier conversion in groupcast | Huawei, HiSilicon | imported from 3GU |
| S3‑194654 | Providing analysis to Solution #13 in TR 33.836 | Huawei, Hisilicon | imported from 3GU |
| S3‑194655 | LS on minimizing the impact of privacy protection mechanisms in the application layer | Huawei | imported from 3GU |
| S3‑194656 | Conclusion for Key issue 9 | LG Electronics Inc. | imported from 3GU |
| S3‑194657 | eV2X: conclusion on KI #10 | Huawei, Hisilicon,LG | imported from 3GU |
| S3‑194658 | LS on PC5 unicast and groupcast security protection | InterDigital Communications | imported from 3GU |
| S3‑194659 | Resource Level Authorization using Access Tokens | Ericsson,Nokia | imported from 3GU |
| S3‑194660 | Authentication subscription data | KPN, Nokia | imported from 3GU |
| S3‑194661 | Key issue on Protection of long-term key during storage in UDR | KPN, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194662 | Key issue on Protection of long-term key during transfer out of UDR | KPN, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194663 | Draft TR 33.845 | Vodafone | imported from 3GU |
| S3‑194664 | Security Parameter Storage | Ericsson | imported from 3GU |
| S3‑194665 | Notes from the offline session on false base stations | NTT-Docomo | imported from 3GU |
| S3‑194666 | Reply to: LS on GUTI allocation for MT-EDT in 5G CIoT | Ericsson | imported from 3GU |
| S3‑194667 | Updates to solution #7 - capability negotiation | Ericsson | imported from 3GU |
| S3‑194668 | Updates to solution #17 - resolving Ens | Ericsson | imported from 3GU |
| S3‑194669 | UDR study - title correction | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194670 | UDR study - intro | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194671 | UE activates UP IP over eUTRA to EPC | Huawei, Hisilicon | imported from 3GU |
| S3‑194672 | Draft TR 33.853 | Vodafone | imported from 3GU |
| S3‑194673 | Resolving the ENs in KI#3.1 | Huawei, Hisilicon | imported from 3GU |
| S3‑194674 | LS on deleting invalid autnentication results in UDM | Huawei | imported from 3GU |
| S3‑194675 | AUTH_Enh-update for solution#4.1 | Apple,Huawei | imported from 3GU |
| S3‑194676 | Draft TR 33.846 | Ericsson | imported from 3GU |
| S3‑194677 | AUTH_Enh-Evaluation for solution#2.4 | Apple | imported from 3GU |
| S3‑194678 | Resolving the ENs of solution#2.5 in the TR 33.846 | Huawei, Hisilicon | imported from 3GU |
| S3‑194679 | Add solution details and evaluation to solutioin 4.1 | Huawei, Hisilicon | imported from 3GU |
| S3‑194680 | LS on resynchronization | Qualcomm | imported from 3GU |
| S3‑194681 | Update to the evaluation of solution #4.1 on protecting SQN in AKA re-synchronisations | Qualcomm Incorporated | imported from 3GU |
| S3‑194682 | Updates to solution #7 - network sharing | Ericsson | imported from 3GU |
| S3‑194683 | Updates to solution #7 - signature schemes and length | Ericsson | imported from 3GU |
| S3‑194684 | Draft TR 33.809 | Apple | imported from 3GU |
| S3‑194685 | 5GFBS-Update for solution#11 | Apple | imported from 3GU |
| S3‑194686 | Shared key based MIB/SIBs integrity information provided by gNB | Qualcomm Incorporated | imported from 3GU |
| S3‑194687 | Reply LS to RAN2 on FBS detection | Huawei, HiSilicon | imported from 3GU |
| S3‑194688 | Update solution 4 to clarify MIB/SIB Hash report | Huawei, HiSilicon | imported from 3GU |
| S3‑194689 | Address EN in solution 6 and solution 18 | Huawei, Hisilicon | imported from 3GU |
| S3‑194690 | Resolving the ENs of solution#5 in the TR 33.809 | Huawei, Hisilicon, Lenovo, Motorola Mobility | imported from 3GU |
| S3‑194691 | Clarification on primary authentication in direct NAS reroute for Rel-15 | Huawei, Hisilicon | imported from 3GU |
| S3‑194692 | Clarification on primary authentication in direct NAS reroute for Rel-16 | Huawei, Hisilicon,ZTE | imported from 3GU |
| S3‑194693 | CAG ID privacy conclusion | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑194694 | 5WWC | Huawei | imported from 3GU |
| S3‑194695 | Cover sheet TR 33.835 for approval | China Mobile | imported from 3GU |
| S3‑194696 | Presentation of TR 33.819 to SA plenary | Nokia | imported from 3GU |
| S3‑194697 | New solution to KI#9 | Huawei, HiSilicon | imported from 3GU |
| S3‑194698 | UP IP-update for solution#9 | Apple | imported from 3GU |
| S3‑194699 | Work Plan input from Rapporteurs | MCC | imported from 3GU |
page generated from database: 2024-04-22 07:58:53