3GPP TDocs (written contributions) at meeting
Meeting: S3-93 - 2018-11-12 to 2018-11-16, Spokane
meeting id: S3-93 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S3‑183200 | Agenda | WG Chairman | imported from 3GU |
| S3‑183201 | Report from SA3#92 | MCC | imported from 3GU |
| S3‑183202 | SA3 Work Plan | MCC | imported from 3GU |
| S3‑183203 | Report from last SA meeting | WG Chairman | imported from 3GU |
| S3‑183204 | SA3 meeting calendar | MCC | imported from 3GU |
| S3‑183205 | Work Plan input from Rapporteurs | MCC | imported from 3GU |
| S3‑183206 | Report from SA3#92Ad-Hoc | MCC | imported from 3GU |
| S3‑183207 | Intra-gNB-CU term synchronization | Huawei, HiSilicon | imported from 3GU |
| S3‑183208 | Update RNA Update Procedure Security | Huawei, HiSilicon | imported from 3GU |
| S3‑183209 | N2 HO: Handling source algorithms for RRC Reestablishment procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑183210 | Handling of UP security policy in MR-DC | Huawei, Hisilicon, Qualcomm Incorporated, Ericsson | imported from 3GU |
| S3‑183211 | Delete EN in SBA Requirements | Huawei, Hisilicon | imported from 3GU |
| S3‑183212 | Clarifications on AccessToken_Get Response message | Huawei, Hisilicon | imported from 3GU |
| S3‑183213 | Editorial corrections on Authorization of NF service access | Huawei, Hisilicon | imported from 3GU |
| S3‑183214 | Add discover procedure as a pre-requisite for obtaining access token | Huawei, Hisilicon | imported from 3GU |
| S3‑183215 | correction on the mobility from 5G to 4G | Huawei, Hisilicon | imported from 3GU |
| S3‑183216 | Clarification on handover from EPS to 5GS | Huawei, Hisilicon | imported from 3GU |
| S3‑183217 | Editorial corrections on the 5GS to EPS handover procedure | Huawei, HiSilicon | imported from 3GU |
| S3‑183218 | Clarification for Target to Source container | Huawei, HiSilicon | imported from 3GU |
| S3‑183219 | Multiple NAS connections: clarification on the action of MAC verification in registration request over non-3gpp access | Huawei, HiSilicon | imported from 3GU |
| S3‑183220 | Interworking – correcting keying material in HO request message (EPS to 5GS) | Ericsson | imported from 3GU |
| S3‑183221 | Length of IV salt and sequence counter | Ericsson | imported from 3GU |
| S3‑183222 | Correction to the Security Service for Steering of Roaming | Ericsson | imported from 3GU |
| S3‑183223 | Mobility – Clarification of downlink NAS COUNT in N2 handover | Ericsson | imported from 3GU |
| S3‑183224 | NAS key refresh | Ericsson | imported from 3GU |
| S3‑183225 | Caching access tokens | Ericsson | imported from 3GU |
| S3‑183226 | Addition of multiple instance IDs to OAuth2.0 access token claims | Ericsson | imported from 3GU |
| S3‑183227 | Corrections to references for security related service in clause 14 | CATT | imported from 3GU |
| S3‑183228 | Correction to Nudm_UEAuthentication_ResultConfirmation service | CATT | imported from 3GU |
| S3‑183229 | Correction to 5G AKA procedure – no need for "SUPI or SUCI" (in step 10) | Orange, Ericsson, Nokia | imported from 3GU |
| S3‑183230 | Adding references for the TLS Protocol Profiles clause | Juniper Networks, Ericsson | imported from 3GU |
| S3‑183231 | Update NDS/IP scope with application layer crypto profiles | Juniper Networks, Ericsson | imported from 3GU |
| S3‑183232 | Move TLS crypto profiles to TS 33.210 | Juniper Networks, Ericsson | imported from 3GU |
| S3‑183233 | Adjusting the description of the initial NAS protection method | Qualcomm Incorporated, ZTE, China Mobile | imported from 3GU |
| S3‑183234 | Acknowledging possibility of early calculation of EMSK | Qualcomm Incorporated, Huawei, Hsilicon | imported from 3GU |
| S3‑183235 | Precedence of protection policies on the N32 interface^^ | Telekom Deutschland GmbH | imported from 3GU |
| S3‑183236 | Handling of encrypted IEs on the N32 interface | Telekom Deutschland GmbH | imported from 3GU |
| S3‑183237 | Corrections and additions in definitions and related clauses | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183238 | Clarification to AUSF key derivation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183239 | Clarification to support of authentication methods | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183240 | Adding reference to 33.501 in 33.102 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183241 | Alignment regarding KEY reference to 33.220 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183242 | Misleading text with reference regarding serving network name | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183243 | Clarification on first bits of EMSK | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183244 | Removing mandatory text from note | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183245 | Reference correction | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183246 | Remove EN in 13.2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183247 | Clarifications to clause 13.2.1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183248 | Remove EN in 13.2.2.1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183249 | Correction in step 2 of 13.2.2.2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183250 | Corrections in 13.2.2.4 on N32-f context ID | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183251 | Clarifications and corrections in clause 13.2.4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183252 | pCR to TS 33.841 - restructure of section 4 as agreed in conf call | VODAFONE Group Plc | imported from 3GU |
| S3‑183253 | Agenda | WG Chairman | imported from 3GU |
| S3‑183254 | Multiple NAS Connection: Correcting NAS link identifier | Nokia | imported from 3GU |
| S3‑183255 | CR to 33210 r15 adding references for the TLS Protocol Profiles clause | Juniper Networks, Ericsson | imported from 3GU |
| S3‑183256 | CR to 33210 r16 adding Other 3GPP Profiles clause and references | Juniper Networks, Ericsson | imported from 3GU |
| S3‑183257 | CR to 33310 r16 removing annex e | Juniper Networks, Ericsson | imported from 3GU |
| S3‑183258 | CR to 33310 r15 corrections of references and annex | Juniper Networks, Ericsson | imported from 3GU |
| S3‑183259 | CR to 33310 r16 corrections of references | Juniper Networks, Ericsson | imported from 3GU |
| S3‑183260 | Reply LS on Control Plane Solution for Steering of Roaming in 5GS | C1-186841 | imported from 3GU |
| S3‑183261 | Reply LS on the Impacts of increasing the MAC-I and NAS-MAC size | R2-1816012 | imported from 3GU |
| S3‑183262 | Reply LS on LS on the Impacts of increasing the MAC-I and NAS-MAC size | C1-186961 | imported from 3GU |
| S3‑183263 | LS on Observations from 2nd MCPTT Plugtests | C1-186964 | imported from 3GU |
| S3‑183264 | Reply LS on maximum output size of SUPI concealment schemes | C1-186992 | imported from 3GU |
| S3‑183265 | LS on Scenarios with multiple registrations to the same AMF | C1-186993 | imported from 3GU |
| S3‑183266 | Reply LS on inclusion of selected PLMN into the complete message | C1-186994 | imported from 3GU |
| S3‑183267 | Reply LS on initial NAS security agreements | R2-1816022 | imported from 3GU |
| S3‑183268 | LS on initial NAS message protection | C1-186995 | imported from 3GU |
| S3‑183269 | LS on EAS-C&U support | C3-186313 | imported from 3GU |
| S3‑183270 | LS on security method negotiation | C3-186335 | imported from 3GU |
| S3‑183271 | LS on API invoker onboarding | C3-186414 | imported from 3GU |
| S3‑183272 | LS on N32 error signalling | C4-187145 | imported from 3GU |
| S3‑183273 | Reply LS on Maximum output size of SUPI concealment schemes | C4-187633 | imported from 3GU |
| S3‑183274 | LS on Control Plane Solution for Steering of Roaming in 5GS | CP-182234 | imported from 3GU |
| S3‑183275 | Response to 3GPP SA2 liaison S2-189038 on ‘general status of work’ | BBF | imported from 3GU |
| S3‑183276 | LS to 3GPP TSG-SA WG6 on Use of ITS Dedicated Spectrum within V2X UE | ETSI TC ITS | imported from 3GU |
| S3‑183277 | LS on Joint ETSI - OSA Workshop: Open Implementations & Standardization | ETSI | imported from 3GU |
| S3‑183278 | Observations on standards and technical constraints from 2nd MCPTT Plugtests | ETSI CTI | imported from 3GU |
| S3‑183279 | Reply LS on " LS on Using same counter in EDCE5" | R2-1816010 | imported from 3GU |
| S3‑183280 | Reply LS on security requirements for RRC connection release | R2-1816053 | imported from 3GU |
| S3‑183281 | LS on security requirements for Integrity protection for DRBs in MR-DC | R2-1816054 | imported from 3GU |
| S3‑183282 | Reply LS on devices behind 5G-RG accessing the 5GC | S2-1810989 | imported from 3GU |
| S3‑183283 | Reply LS on Secondary Re-Authentication | S2-1811431 | imported from 3GU |
| S3‑183284 | Reply LS on Clarifications on SUPI definition and NAI format | S2-1811525 | imported from 3GU |
| S3‑183285 | LS Reply on Control Plane Solution for Steering of Roaming in 5GS | GSMA | imported from 3GU |
| S3‑183286 | LS on SG17 work item X.5Gsec-q: Security guidelines for applying quantum-safe algorithms in 5G systems | ITU-T SG17 | imported from 3GU |
| S3‑183287 | Reply LS on initial NAS security agreements | S2-1811568 | imported from 3GU |
| S3‑183288 | Reply LS on 5WWC status of work and interim agreements | S2-1811575 | imported from 3GU |
| S3‑183289 | LS on separate HSS and UDM and security credentials storage | S2-1811603 | imported from 3GU |
| S3‑183290 | Potential Requirements for TR 33.841 | NCSC | imported from 3GU |
| S3‑183291 | Conclusions for TR 33.841 | NCSC | imported from 3GU |
| S3‑183292 | Update to Impacted NextGen Areas - TR 33.841 | NCSC | imported from 3GU |
| S3‑183293 | Editorials for TR 33.841 | NCSC | imported from 3GU |
| S3‑183294 | Modifications and Clarifications for TR 33.841 | NCSC | imported from 3GU |
| S3‑183295 | Draft Reply LS to ITU-T SG17 on X.5Gsec-q study | NCSC | imported from 3GU |
| S3‑183296 | Discussion of Potential threats caused by false base station | Apple Computer Trading Co. Ltd | imported from 3GU |
| S3‑183297 | Key issue of authenticating gNB on broadcast and unicast message | Apple Computer Trading Co. Ltd | imported from 3GU |
| S3‑183298 | Corrections to definition of 5G NAS security context | CMCC | imported from 3GU |
| S3‑183299 | Key issue of security protection on the unicast message from the UE before security activation | Apple Computer Trading Co. Ltd | imported from 3GU |
| S3‑183300 | skeleton of TR 33.809-Study on 5G Security Enhancement against False Base Station | Apple Computer Trading Co. Ltd | imported from 3GU |
| S3‑183301 | Key issue of security overhead and complexity | Apple Computer Trading Co. Ltd | imported from 3GU |
| S3‑183302 | Discussion on one potential way to improve the efficiency of IP | Apple Computer Trading Co. Ltd | imported from 3GU |
| S3‑183303 | Unify the name of RAN network in 33.501 | CMCC | imported from 3GU |
| S3‑183304 | Replace 5G-RAN with NG-RAN in 33.501 | China Mobile | imported from 3GU |
| S3‑183305 | Add symmetric key distribution mechanisms to TS 33.180 | Airbus DS SLC | imported from 3GU |
| S3‑183306 | Key Issue on secure communication between UE and application server | Alibaba (China) group., Ltd., China Mobile | imported from 3GU |
| S3‑183307 | AKMA candidate solution for non-3GPP credential download | Alibaba (China) group., Ltd., China Mobile | imported from 3GU |
| S3‑183308 | Algorithm Agility | NIST | imported from 3GU |
| S3‑183309 | pCR Discussing mitigating of risks by using larger keys | NIST | imported from 3GU |
| S3‑183310 | pCR to Include content discussing forward security | NIST | imported from 3GU |
| S3‑183311 | VERTICAL_LAN_SEC skeleton | Nokia Germany | imported from 3GU |
| S3‑183312 | New Key Issue: Authentication and Authorization for Interworking, Roaming between NPN and PLMN | InterDigital Europe. Ltd. | imported from 3GU |
| S3‑183313 | Modification of initial NAS message protection | ZTE Corporation | imported from 3GU |
| S3‑183314 | Modification on NAS SMC procedure | ZTE Corporation | imported from 3GU |
| S3‑183315 | Handling of initial NAS message other than RR when failure occur | ZTE Corporation | imported from 3GU |
| S3‑183316 | Editorial modification on initial NAS message protection | ZTE Corporation | imported from 3GU |
| S3‑183317 | Editorial modification on gNB requirement | ZTE Corporation | imported from 3GU |
| S3‑183318 | AS subscription temperary identifier privacy | ZTE Corporation | imported from 3GU |
| S3‑183319 | Scope of TS 33.519 | ZTE Corporation | imported from 3GU |
| S3‑183320 | References of TS 33.519 | ZTE Corporation | imported from 3GU |
| S3‑183321 | Authentication on application functions | ZTE Corporation | imported from 3GU |
| S3‑183322 | Proposal about improvement of the UP security policy | China Mobile | imported from 3GU |
| S3‑183323 | Corrections to definition of 5G AS security context for 3GPP access | China Mobile | imported from 3GU |
| S3‑183324 | Replace 5G-RAN with NG-RAN in TS 33.501 | China Mobile | imported from 3GU |
| S3‑183325 | Discussion on i/c LS S2-1811543 NSSAI in RRC message | Nokia, AT&T, Verizon Wireless, Inter Digital | imported from 3GU |
| S3‑183326 | draft-LS out reply to i/c LS on NSSAI in RRC message | Nokia | imported from 3GU |
| S3‑183327 | Discussion on LS (S3-183289) on separate HSS and UDM credential storage | Nokia | imported from 3GU |
| S3‑183328 | Clarify SUPI format in KAMF computation | Nokia | imported from 3GU |
| S3‑183329 | Editorial correction in Clause 6.9.3.2 | Nokia | imported from 3GU |
| S3‑183330 | Key issue false base station detection and isolation | Nokia | imported from 3GU |
| S3‑183331 | Add security requirements to key issue#6 | Nokia | imported from 3GU |
| S3‑183332 | Adding Key issue for Connectionless service security | Nokia | imported from 3GU |
| S3‑183333 | Skeleton proposal for TR for Enhanced Network Slicing | Nokia | imported from 3GU |
| S3‑183334 | eNet Slice TR content for scope | Nokia | imported from 3GU |
| S3‑183335 | pCR to TR 33.813 content for references | Nokia | imported from 3GU |
| S3‑183336 | pCR to TR33.813 content for definitions and abbreviations | Nokia | imported from 3GU |
| S3‑183337 | pCR to TR 33.813 Adding key issue for Slice specific authentication | Nokia | imported from 3GU |
| S3‑183338 | Solution proposal for FS_CIoT_sec_5G | NEC Corporation | imported from 3GU |
| S3‑183339 | Key issue proposal for security aspects of enhanced support of network slices | NEC Corporation | imported from 3GU |
| S3‑183340 | Key issue proposal for security of URLLC for 5GS | NEC Corporation | imported from 3GU |
| S3‑183341 | Correction/enhancement in CAPIF TS | NEC Corporation | imported from 3GU |
| S3‑183342 | Update RRC reestablishment security procedure based on RAN2 agreement | Huawei, Hisilicon | imported from 3GU |
| S3‑183343 | eNB allowing Unauthenticated UEs in LSM | Huawei, Hisilicon | imported from 3GU |
| S3‑183344 | Adding UP security policy in SN Addition/modification Request message | Huawei, Hisilicon | imported from 3GU |
| S3‑183345 | Clarification on how AMF confirm UE SUPI | Huawei, Hisilicon | imported from 3GU |
| S3‑183346 | Solution for protecting gNB from RRC re-establishment DDoS attack | Huawei, Hisilicon | imported from 3GU |
| S3‑183347 | Key Issue on spoofing system informations | Huawei, Hisilicon | imported from 3GU |
| S3‑183348 | Key Issue on HO failure caused by fake base station | Huawei, Hisilicon | imported from 3GU |
| S3‑183349 | Key Issue on Spoofing UE paging messages | Huawei, Hisilicon | imported from 3GU |
| S3‑183350 | Protecting UE from connnecting to fake basestation during HO | Huawei, Hisilicon | imported from 3GU |
| S3‑183351 | Aoviding unnecessary HO caused by fake base station | Huawei, Hisilicon | imported from 3GU |
| S3‑183352 | Solution for protecting gNB from RRC re-establishment DDoS attack | Huawei, Hisilicon | imported from 3GU |
| S3‑183353 | Key Issue on spoofing system informations | Huawei, Hisilicon | imported from 3GU |
| S3‑183354 | Key Issue on HO failure caused by fake base station | Huawei, Hisilicon | imported from 3GU |
| S3‑183355 | Key Issue on Spoofing UE paging messages | Huawei, Hisilicon | imported from 3GU |
| S3‑183356 | IoT Group Authentication | Huawei, Hisilicon | imported from 3GU |
| S3‑183357 | Solution for pretecting UE from HO to fake base station | Huawei, Hisilicon | imported from 3GU |
| S3‑183358 | Protecting UE from connnecting to fake basestation during HO | Huawei, Hisilicon | imported from 3GU |
| S3‑183359 | Aoviding unnecessary HO caused by fake base station | Huawei, Hisilicon | imported from 3GU |
| S3‑183360 | Clarification: AMF confirming UE SUPI in case NAS SMC failed | Huawei, Hisilicon | imported from 3GU |
| S3‑183361 | UP IP handling for split PDU session in MR-DC scenarios | Huawei, Hisilicon | imported from 3GU |
| S3‑183362 | Adding NR-DC to the scenarios of MR-DC | Huawei, Hisilicon | imported from 3GU |
| S3‑183363 | Reply LS on security requirements for Integrity protection for DRBs in MR-DC | Huawei, Hisilicon | imported from 3GU |
| S3‑183364 | IoT Group Authentication | Huawei, Hisilicon | imported from 3GU |
| S3‑183365 | Solution for pretecting UE from HO to fake base station | Huawei, Hisilicon | imported from 3GU |
| S3‑183366 | Key issue on security protection of Location service exposure for TR33.814 | CATR, China Unicom, CATT | imported from 3GU |
| S3‑183367 | New WID on security aspects of single radio voice continuity from 5G to 3G | China Unicom, Huawei, HiSilicon, ZTE, CATT, OPPO, CATR | imported from 3GU |
| S3‑183368 | Impacts on existing nodes and functionality for the solution "Return from UTRAN to E-UTRAN or NR" | China Unicom | imported from 3GU |
| S3‑183369 | Evaluation for the solution "Return from UTRAN to E-UTRAN or NR" | China Unicom | imported from 3GU |
| S3‑183370 | Conclusion for the solution "Return from UTRAN to E-UTRAN or NR" | China Unicom | imported from 3GU |
| S3‑183371 | Scope of FS_eLCS_Sec | China Unicom | imported from 3GU |
| S3‑183372 | key issue on protect distribution positioning assistance data | China Unicom | imported from 3GU |
| S3‑183373 | Correction on LTE suspend/resume procedure for EDT capable UE | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑183374 | Initial NAS Discussion on privacy solutions | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑183375 | draft reply LS on security requirements for RRC connection release | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑183376 | Key Issue: Requirement of Trust mechanism of Non 3GPP UEs | China Telecom Corporation Ltd. | imported from 3GU |
| S3‑183377 | URLLC pCR - new key issue on security of redundant transmission in user plane | LG Electronics | imported from 3GU |
| S3‑183378 | Discussion about a new SI for 5G V2X security | LG Electronics | imported from 3GU |
| S3‑183379 | Corrections to 5.2 Requirements on the UE | LG Electronics | imported from 3GU |
| S3‑183380 | Corrections to 5.3 Requirements on the gNB | LG Electronics | imported from 3GU |
| S3‑183381 | Corrections to 9. Security procedures for non-service based interfaces | LG Electronics | imported from 3GU |
| S3‑183382 | IP protection for SN terminated bearers | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑183383 | 5G inclusion in TS 33.117 | Nokia, Nokia Shanghai Bell, Telekom Deutschland GmbH | imported from 3GU |
| S3‑183384 | Incorporating general SBA aspects in TS 33.117 | Nokia, Nokia Shanghai Bell, Telekom Deutschland GmbH | imported from 3GU |
| S3‑183385 | Test Case of transport layer protection for SBI | Nokia, Nokia Shanghai Bell, Telekom Deutschland GmbH | imported from 3GU |
| S3‑183386 | Editorial corrections in TS 33.117 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183387 | Skeleton of SCAS SEPP TS 33.517 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183388 | Scope of SCAS SEPP TS 33.517 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183389 | Reference of SCAS SEPP TS 33.517 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183390 | Skeleton of SCAS NRF TS 33.518 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183391 | Scope of SCAS NRF TS 33.518 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183392 | Reference of SCAS NRF TS 33.518 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183393 | pCR to TR 33.841 draft conclusion | CATT | imported from 3GU |
| S3‑183394 | Protecting SUPI for user privacy | ZTE Corporation | imported from 3GU |
| S3‑183395 | Proposed change to the solution #1.1 of TR 33.856 | Huawei, Hisilicon | imported from 3GU |
| S3‑183396 | clean up the EN of subclause 6.4.3 in TR 33.856 | Huawei, Hisilicon | imported from 3GU |
| S3‑183397 | clean up the EN of subclause 7 in TR 33.856 | Huawei, Hisilicon | imported from 3GU |
| S3‑183398 | add evaluation to solution #5 | Huawei, Hisilicon | imported from 3GU |
| S3‑183399 | editorial modification on TR 33.856 | Huawei, Hisilicon | imported from 3GU |
| S3‑183400 | correction on handover procedure from 5G to 4G | Huawei, Hisilicon | imported from 3GU |
| S3‑183401 | Editorial corrections on the UP integrity mechanisms | Huawei, Hisilicon | imported from 3GU |
| S3‑183402 | Editorial corrections on NAS SMC procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑183403 | Key issue for encryption protection of location data | Huawei, Hisilicon | imported from 3GU |
| S3‑183404 | Key issue for integrity protection of location and assistance data | Huawei, Hisilicon | imported from 3GU |
| S3‑183405 | Mapping requirements and test cases from 33.216 to 33.511 | Huawei, Hisilicon | imported from 3GU |
| S3‑183406 | Add the evidences of the test cases | Huawei, Hisilicon | imported from 3GU |
| S3‑183407 | CR-to-TS33501-RRC Reestablishment security handling when N2 Handover happens | Huawei, Hisilicon | imported from 3GU |
| S3‑183408 | Discussion on Support AS Security Algorithms Negotiation during INACTIVE transition and RRC Reestablishment in R15 | Huawei, Hisilicon | imported from 3GU |
| S3‑183409 | Discussion on UP Integrity protection for small data in Early Data Transfer | Huawei, Hisilicon | imported from 3GU |
| S3‑183410 | LS to RAN23 on UP Integrity Protection for Small Data in Early Data Transfer | Huawei, Hisilicon | imported from 3GU |
| S3‑183411 | User Plane Integrity Protection for EDT | Huawei, Hisilicon | imported from 3GU |
| S3‑183412 | Key Issue on KDF negotiation between UE and AMF | Huawei, Hisilicon | imported from 3GU |
| S3‑183413 | Key Issue on Avoiding Bidding down attack on KDF negotiation | Huawei, Hisilicon | imported from 3GU |
| S3‑183414 | Scope for TR 33.808 KDF negotiation | Huawei, Hisilicon | imported from 3GU |
| S3‑183415 | Key Issue on Classification of IoT UE based on Attack Method | Huawei, Hisilicon | imported from 3GU |
| S3‑183416 | Capture IoT Security Related Requirement in other 3GPP Document | Huawei, Hisilicon | imported from 3GU |
| S3‑183417 | Key Issue on Authentication of a UE for Non-public network | Huawei, Hisilicon | imported from 3GU |
| S3‑183418 | Key Issue on Protection of interfaces that 5GS interact with TSN | Huawei, Hisilicon | imported from 3GU |
| S3‑183419 | Security solution for temporary group – broadcast group call procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑183420 | Solution for bootstrapping authentication of AKMA | Huawei, Hisilicon | imported from 3GU |
| S3‑183421 | Delete information during API invoker offboarding | Huawei, Hisilicon | imported from 3GU |
| S3‑183422 | Editorial corrections on Application layer security on the N32 interface | Huawei, Hisilicon | imported from 3GU |
| S3‑183423 | Secure storage of UICC | Huawei, Hisilicon | imported from 3GU |
| S3‑183424 | secure boot of 5G-RG | Huawei, Hisilicon | imported from 3GU |
| S3‑183425 | Prevent from 5G-RG cheating | Huawei, Hisilicon | imported from 3GU |
| S3‑183426 | solution on 5G-RG authentication | Huawei, Hisilicon | imported from 3GU |
| S3‑183427 | Editoral Change of Solution 1 | Huawei, Hisilicon | imported from 3GU |
| S3‑183428 | Add EDCE5 realted requirements and testcases to 33.216 | Huawei, Hisilicon | imported from 3GU |
| S3‑183429 | Adding Execution Steps to in 4.2.2.1.1, 4.2.2.1.2, and 4.2.2.1.7 | Huawei, Hisilicon | imported from 3GU |
| S3‑183430 | UPdate test cases in 33.511 | Huawei, Hisilicon | imported from 3GU |
| S3‑183431 | New requirements and testcases on UP security policy related | Huawei, Hisilicon | imported from 3GU |
| S3‑183432 | Update requirements in 4.2.3.2.2 in 33.117 | Huawei, Hisilicon | imported from 3GU |
| S3‑183433 | Draft skeleton for TR 33.814 | CATT | imported from 3GU |
| S3‑183434 | pCR to TR33.814 - Scope | CATT | imported from 3GU |
| S3‑183435 | pCR to TR33.814 - Key issue for ciphering key delivery | CATT | imported from 3GU |
| S3‑183436 | New SID on User Plane Integrity Protection | VODAFONE Group Plc | imported from 3GU |
| S3‑183437 | Reply LS on security requirements for Integrity protection for DRBs in MR-DC | Huawei, Hisilicon | imported from 3GU |
| S3‑183438 | CR to TS33.501-Registration related text correction | CATT | imported from 3GU |
| S3‑183439 | Security requirements on the CAPIF-3e/4e/5e reference points | China Telecommunications | imported from 3GU |
| S3‑183440 | New SID on LTKUP Detailed Solutions | VODAFONE Group Plc | imported from 3GU |
| S3‑183441 | Telescopic FQDN creation within the SEPP | Telekom Deutschland GmbH, Nokia | imported from 3GU |
| S3‑183442 | Corrections to N32 Protection Policies | Telekom Deutschland GmbH, Nokia | imported from 3GU |
| S3‑183443 | Verification of the PLMN-ID by the receiving SEPP | Telekom Deutschland GmbH, Nokia | imported from 3GU |
| S3‑183444 | Adopting more normative language in clause 13 | Telekom Deutschland GmbH, Nokia | imported from 3GU |
| S3‑183445 | pCR to TR 33.834 - Update to LTKUP Conclusions | VODAFONE Group Plc | imported from 3GU |
| S3‑183446 | Adding unique names to test cases | Telekom Deutschland GmbH | imported from 3GU |
| S3‑183447 | pCR to TR 33 841 Performance aspects for the new 256-bit algorithms | CATT | imported from 3GU |
| S3‑183448 | pCR to TR 33 841 Potential requirements | CATT | imported from 3GU |
| S3‑183449 | pCR to TR 33 841 Study of individual algorithm details | CATT | imported from 3GU |
| S3‑183450 | New WID - Updates and enhancements to BEST for 5G | VODAFONE Group Plc | imported from 3GU |
| S3‑183451 | pCR to TR 33 841 Threat details to symmetric cryptography | CATT | imported from 3GU |
| S3‑183452 | New test case: No code execution or inclusion of external ressources by JSON parsers | Telekom Deutschland GmbH | imported from 3GU |
| S3‑183453 | Scope for TR33.825 on URLLC security | Huawei, HiSilicon | imported from 3GU |
| S3‑183454 | Key issue authentication adaptions | Huawei, HiSilicon | imported from 3GU |
| S3‑183455 | Key issue security for redundant transmissions | Huawei, HiSilicon | imported from 3GU |
| S3‑183456 | Key issue security policy for URLLC service | Huawei, HiSilicon | imported from 3GU |
| S3‑183457 | Key issue security aspect of low latency handover procedures | Huawei, HiSilicon | imported from 3GU |
| S3‑183458 | Key issue QoS monitoring protection | Huawei, HiSilicon | imported from 3GU |
| S3‑183459 | Key issue considerations of security algorithms for URLLC | Huawei, HiSilicon | imported from 3GU |
| S3‑183460 | Improvement for key issue on the signalling overload due to malicious applications on the UE | Huawei, HiSilicon | imported from 3GU |
| S3‑183461 | New KI on security features for NSaaS | Huawei, HiSilicon | imported from 3GU |
| S3‑183462 | New KI on monitored security features | Huawei, HiSilicon | imported from 3GU |
| S3‑183463 | New KI on slice authentication | Huawei, HiSilicon | imported from 3GU |
| S3‑183464 | New KI on slice isolation | Huawei, HiSilicon | imported from 3GU |
| S3‑183465 | New KI on NSSAI confidentiality | Huawei, HiSilicon | imported from 3GU |
| S3‑183466 | Discussion on LS from SA2 on 2nd Authentication | Huawei, HiSilicon | imported from 3GU |
| S3‑183467 | CR on Secondary Re-authentication | Huawei, HiSilicon | imported from 3GU |
| S3‑183468 | Discussion on verification of PLMN ID in N32 message | Huawei, Hisilicon | imported from 3GU |
| S3‑183469 | Verification of PLMN ID in N32 message | Huawei, Hisilicon | imported from 3GU |
| S3‑183470 | Key issue on Authentication relay attack | Huawei, Hisilicon | imported from 3GU |
| S3‑183471 | Study on mitigation of the charging fraud attack | Huawei, Hisilicon | imported from 3GU |
| S3‑183472 | Discussion on UE Parameters Update via UDM Control Plane Procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑183473 | pCR to TR 33.841 draft conclusion | CAICT, CATT, China Mobile, China Telecom, China Unicom, Huawei, HiSilicon, ZTE, OPPO, Qihoo 360 | imported from 3GU |
| S3‑183474 | Solution for UE Parameters Update via UDM Control Plane Procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑183475 | pCR to TR 33 841 Potential requirements | CAICT, CATT, China Mobile, China Telecom, China Unicom, Huawei, HiSilicon, ZTE, OPPO | imported from 3GU |
| S3‑183476 | Clarification on interworking | Huawei, Hisilicon | imported from 3GU |
| S3‑183477 | pCR to TR 33 841 Study of individual algorithm details | CATT, CAICT, China Mobile, China Telecom, China Unicom, Huawei, HiSilicon, ZTE, OPPO | imported from 3GU |
| S3‑183478 | Update on access token in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S3‑183479 | Remove the shared secret based token protection mechanism from the token related procedure | Huawei, Hisilicon | imported from 3GU |
| S3‑183480 | CR to TS 33.501 regarding N32-f key hierarchy | China Mobile | imported from 3GU |
| S3‑183481 | pCR to TR 33 841 regarding key derivation function | China Mobile; Vodafone | imported from 3GU |
| S3‑183482 | LS_to_LS on SG17 work item X 5Gsec-q | China Mobile | imported from 3GU |
| S3‑183483 | enhance the security of the authentication procedure | China Mobile | imported from 3GU |
| S3‑183484 | Discussing ToE of security assurance for 3GPP virtualized network products | China Mobile,CATR,ZTE | imported from 3GU |
| S3‑183485 | Discussing gaps from applying current SECAM to 3GPP virtualized network products | China Mobile, CATR, ZTE | imported from 3GU |
| S3‑183486 | Security Impacts of Virtualisation | BT plc | imported from 3GU |
| S3‑183487 | VERTICAL study - Scope | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183488 | VERTICAL study - Background to and key issues for VERTICAL_LAN_SEC study | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183489 | VERTICAL study - High-level overview of security aspects | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183490 | VERTICAL study - KI1 on primary authentication using EAP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183491 | VERTICAL study - KI2 on primary authentication in NPN using Rel-15 authentication methods | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183492 | VERTICAL study - KI3 on authentication framework for NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183493 | VERTICAL study - KI4 on Security implications for accessing PLMN services via NPN and vice versa | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183494 | VERTICAL study - KI5 on verification of the integrity of a message | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183495 | VERTICAL study - KI6 on non-repudiation of the sender of a message | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183496 | VERTICAL study - definitions and abbreviations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183497 | VERTICAL study - reference | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183498 | Formatting issue | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183499 | Shift of text from SEPP intro to subclause | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183500 | Clarification to protection scheme identifier | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183501 | Clarification to the transfer of authentication success result to the UDM | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183502 | Intro of subclauses to clause 6.12.2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183503 | Correction of formatting error | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183504 | Alignment on KEY | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183505 | Alignment on Home Network Public Key | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183506 | Skeleton of TR 33.818 | China Mobile, CATR | imported from 3GU |
| S3‑183507 | pCR to 33.841 (256bit) - Update section 4 with new drivers | VODAFONE Group Plc | imported from 3GU |
| S3‑183508 | Key issue on Need for UE capability based KDF negotiation in 5GS | NEC Corporation | imported from 3GU |
| S3‑183509 | Scope of TR 33.818 | China Mobile, CATR | imported from 3GU |
| S3‑183510 | Key Issue on Need for Flexible KDF negotiation | NEC Corporation | imported from 3GU |
| S3‑183511 | Discussion and pCR of Candidate Solution: Transport independent procedure using existing protocols | China Mobile; Alibaba (China) Group., Ltd. | imported from 3GU |
| S3‑183512 | Key Issue on Need for Bidding down protection | NEC Corporation | imported from 3GU |
| S3‑183513 | Discussion and pCR of candidate solution: UE implementation schemes in achieving AKMA procedures | China Mobile; Alibaba (China) Group., Ltd. | imported from 3GU |
| S3‑183514 | Key issue for authentication and authorization of 5GLAN UE in 5GLAN group communication | NEC Corporation | imported from 3GU |
| S3‑183515 | Adding missing references in TS 33.117 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183516 | Clause 13.1.1: AES modes | Ericsson | imported from 3GU |
| S3‑183517 | Update of Key Issue #2: FN-RG authentication and authorization | Ericsson | imported from 3GU |
| S3‑183518 | New solution for Key Issue #2: FN-RG authentication and authorization | Ericsson | imported from 3GU |
| S3‑183519 | New KI: Authentication of 5G capable UE behind a RG | Ericsson | imported from 3GU |
| S3‑183520 | New KI: User plane data handling for 5G capable UE behind a RG | Ericsson | imported from 3GU |
| S3‑183521 | New Solution: 5GC-capable UEs behind 5G-RG/FN-RG using N3GPP-access solutions | Ericsson | imported from 3GU |
| S3‑183522 | N32: remove redundant references to encrypted IEs | Ericsson | imported from 3GU |
| S3‑183523 | pSEPP-pNF authentication | Ericsson | imported from 3GU |
| S3‑183524 | Maximum output size of SUPI concealment scheme | Ericsson | imported from 3GU |
| S3‑183525 | Maximum output size of SUPI concealment schemes | Ericsson | imported from 3GU |
| S3‑183526 | WLAN positioning - new KI for the upcoming TR on FS_eLCS_Sec | Ericsson | imported from 3GU |
| S3‑183527 | Bluetooth positioning - new KI for the upcoming TR on FS_eLCS_Sec | Ericsson | imported from 3GU |
| S3‑183528 | TBS positioning - new KI for the upcoming TR on FS_eLCS_Sec | Ericsson | imported from 3GU |
| S3‑183529 | New key issue for key refreshment in 5GLAN group communication | NEC Corporation | imported from 3GU |
| S3‑183530 | A key issue on Slice-specific security features in NSaaS | China Mobile | imported from 3GU |
| S3‑183531 | A key issue: Security and privacy aspects related to Network Slice specific access authentication and authorization | China Mobile | imported from 3GU |
| S3‑183532 | New key issue for securing the communication between 5GLAN UE and GMF | NEC Corporation | imported from 3GU |
| S3‑183533 | Key Issue on Compliance with Local Rules and Regulations | NEC Corporation | imported from 3GU |
| S3‑183534 | Key Issue on Access Independent Security for 5WWC | NEC Corporation | imported from 3GU |
| S3‑183535 | Security solution for small data sent with EDT in RRC Resume Request for E-UTRA connected to 5GC | Ericsson | imported from 3GU |
| S3‑183536 | Security solution for small data included in initial NAS to handle AMF reallocation | Ericsson LM | imported from 3GU |
| S3‑183537 | Security solution for MO SMS in initial NAS message - handling AMF re-allocation | Ericsson LM | imported from 3GU |
| S3‑183538 | New Key Issue: Remote (de)provisioning of credentials | KPN | imported from 3GU |
| S3‑183539 | Key Issue #4 – Signalling overload due to Malicious Applications on the UE | KPN | imported from 3GU |
| S3‑183540 | Editorial corrections in 13.2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183541 | New KI: Protection of interface used by NIDD procedures | Ericsson LM | imported from 3GU |
| S3‑183542 | New Solution for Key Issue #4: Use of UE Configuration Update | KPN | imported from 3GU |
| S3‑183543 | New solution for protection of interface used by NIDD procedures | Ericsson LM | imported from 3GU |
| S3‑183544 | New Key Issue: Generic battery efficient end-to-end security | KPN | imported from 3GU |
| S3‑183545 | New KI: Privacy protection of the NIDD API between UPF/NEF and AF | Ericsson LM | imported from 3GU |
| S3‑183546 | Issue with using wildcard certificates in SEPP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183547 | Security between SEPP and IPX | Nokia, Nokia Shanghai Bell, Telekom Deutschland GmbH | imported from 3GU |
| S3‑183548 | Telescopic FQDN for callback URIs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183549 | Two parallel N32-c connections between SEPPs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183550 | Discussion on the Reply LSs on initial NAS security agreements | Samsung | imported from 3GU |
| S3‑183551 | Key issue on AS security during RRC Idle mode | Samsung | imported from 3GU |
| S3‑183552 | Solution for AS security during RRC Idle mode | Samsung | imported from 3GU |
| S3‑183553 | Draft-Reply LS on Control Plane Solution for Steering of Roaming in 5GS | Samsung | imported from 3GU |
| S3‑183554 | Correction to Key hierarchy diagram | Samsung | imported from 3GU |
| S3‑183555 | RES* verification failure test case | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183556 | Corrections to KSEAF derivation in Key distribution and derivation | Samsung | imported from 3GU |
| S3‑183557 | Association of security context | Samsung | imported from 3GU |
| S3‑183558 | Missing subclause headings | Samsung | imported from 3GU |
| S3‑183559 | [DRAFT] LS on API invoker onboarding | Samsung | imported from 3GU |
| S3‑183560 | [DRAFT] LS on Security method negotiation | Samsung | imported from 3GU |
| S3‑183561 | New KI: Key Lifetimes | Ericsson India Private Limited | imported from 3GU |
| S3‑183562 | New solution: Access independent architecture solution for AKMA | Ericsson India Private Limited | imported from 3GU |
| S3‑183563 | New KI: API for AKMA keys in UE | Ericsson India Private Limited | imported from 3GU |
| S3‑183564 | New solution: Stand-alone architecture solution for AKMA | Ericsson India Private Limited | imported from 3GU |
| S3‑183565 | New option for 33.855 solution #8 | Ericsson India Private Limited | imported from 3GU |
| S3‑183566 | NF-SEPP TLS handling | Ericsson India Private Limited | imported from 3GU |
| S3‑183567 | Update of PARLOS solution #1 | Motorola Mobility, Lenovo | imported from 3GU |
| S3‑183568 | Clause #4 for the upcoming TR on FS_5GFBS | Ericsson | imported from 3GU |
| S3‑183569 | SON security - new KI for the upcoming TR on FS_5GFBS | Ericsson | imported from 3GU |
| S3‑183570 | Enhancing detection - new KI for the upcoming TR on FS_5GFBS | Ericsson | imported from 3GU |
| S3‑183571 | Enhancing untraceability - new KI for the upcoming TR on FS_5GFB | Ericsson | imported from 3GU |
| S3‑183572 | Privacy visibility - new KI for the upcoming TR on FS_5GFB | Ericsson | imported from 3GU |
| S3‑183573 | KI for security keys for redundant data | Ericsson | imported from 3GU |
| S3‑183574 | KI for UP security policy handling for redundant data | Ericsson | imported from 3GU |
| S3‑183575 | Security solution for handling UP security policy for redundant data | Ericsson | imported from 3GU |
| S3‑183576 | Service visibility - new KI for the upcoming TR on FS_5GFB | Ericsson | imported from 3GU |
| S3‑183577 | KI for retaining AS security key | Ericsson | imported from 3GU |
| S3‑183578 | Solution for flexibility to retain or to change AS security keys | Ericsson | imported from 3GU |
| S3‑183579 | SI replay - new KI for the upcoming TR on FS_5GFB | Ericsson | imported from 3GU |
| S3‑183580 | SI integrity - new KI for the upcoming TR on FS_5GFB | Ericsson | imported from 3GU |
| S3‑183581 | Rogue REJECTS - new KI for the upcoming TR on FS_5GFB | Ericsson | imported from 3GU |
| S3‑183582 | Radio jamming - placeholder-only KI for the upcoming TR on FS_5GFB | Ericsson | imported from 3GU |
| S3‑183583 | New key issue on key separation between Network Slices | Ericsson | imported from 3GU |
| S3‑183584 | Multiple NAS connections and algorithm change | Ericsson | imported from 3GU |
| S3‑183585 | Multiple NAS connecions: mobility with horizontal KAMF derivation | Ericsson | imported from 3GU |
| S3‑183586 | Support of UP security policy in ng-eNB | Ericsson | imported from 3GU |
| S3‑183587 | E-UTRA connected to 5GC | Ericsson | imported from 3GU |
| S3‑183588 | Handling of initial NAS protection failures | Ericsson | imported from 3GU |
| S3‑183589 | Way forward on how to address mobility cases for the initial NAS protection mechanism | Ericsson | imported from 3GU |
| S3‑183590 | Handling of mobility scenarios involving an AMF key change for the initial NAS protection mechanism | Ericsson | imported from 3GU |
| S3‑183591 | Handling of mobility scenarios involving an AMF key change for the initial NAS protection mechanism | Ericsson | imported from 3GU |
| S3‑183592 | EDCE5 – Fixing contradicting and insecure scg/sk counter handling in 33.401 from 36.331 | Ericsson | imported from 3GU |
| S3‑183593 | LTE EDT – integrity protection of uplink EDT data | Ericsson | imported from 3GU |
| S3‑183594 | Update of EAP-AKA’ reference to make it compatible with 5G | Ericsson | imported from 3GU |
| S3‑183595 | Update of EAP-AKA’ RFC 5448 in progress | Ericsson | imported from 3GU |
| S3‑183596 | Update of EAP-AKA PFS work in progress | Ericsson | imported from 3GU |
| S3‑183597 | New SID on authentication enhancements in 5GS | Ericsson | imported from 3GU |
| S3‑183598 | Work on improving perfect forward secrecy in 5G network access | Ericsson | imported from 3GU |
| S3‑183599 | discussion on security credential storage | Ericsson | imported from 3GU |
| S3‑183600 | DRAFT Reply LS on Separate HSS and UDM and security credentials storage | Ericsson | imported from 3GU |
| S3‑183601 | Handling of NAS COUNTs | Ericsson | imported from 3GU |
| S3‑183602 | Discussion on the applicability of gNB requirements to ng-eNB | Ericsson | imported from 3GU |
| S3‑183603 | NG-RAN – clause 6.9.2.2 | Ericsson | imported from 3GU |
| S3‑183604 | NG-RAN – clause 6.9.2.3.3 | Ericsson | imported from 3GU |
| S3‑183605 | NG-RAN – clause 6.9.2.3.4 | Ericsson | imported from 3GU |
| S3‑183606 | Draft CR to S3-183210 (Handling of UP security policy in MR-DC) | Ericsson | imported from 3GU |
| S3‑183607 | draft TS 33.516 (AUSF SCAS) | Ericsson India Private Limited | imported from 3GU |
| S3‑183608 | SCAS discussion | Ericsson India Private Limited | imported from 3GU |
| S3‑183609 | Discussion on the CT1 LS on initial NAS security | Qualcomm Incorporated | imported from 3GU |
| S3‑183610 | Adjusting the description of the initial NAS protection method | Qualcomm Incorporated | imported from 3GU |
| S3‑183611 | LS on initial NAS message protection | Qualcomm Incorporated | imported from 3GU |
| S3‑183612 | Discussion on the SA2 LS on initial NAS security | Qualcomm Incorporated | imported from 3GU |
| S3‑183613 | LS on initial NAS message protection | Qualcomm Incorporated | imported from 3GU |
| S3‑183614 | Network control of sending S-NSSAIs in the RRC signalling | Qualcomm Incorporated | imported from 3GU |
| S3‑183615 | Discussion on CT1 on Scenarios with multiple registrations to the same AMF | Qualcomm Incorporated | imported from 3GU |
| S3‑183616 | Addressing possible security context mismatch on non-3GPP acces when multiply registered on one PLMN | Qualcomm Incorporated | imported from 3GU |
| S3‑183617 | Addressing the editor’s notes in the conclusions clause of TR 33.856 | Qualcomm Incorporated | imported from 3GU |
| S3‑183618 | Corrections on the number of bits of downlink NAS COUNT value to be delivered in the 5GS to EPS handover procedure | Qualcomm Incorporated | imported from 3GU |
| S3‑183619 | Clarification on storing the selected EPS NAS algorithms | Qualcomm Incorporated | imported from 3GU |
| S3‑183620 | KgNB derivation in EPS to 5GS handover | Qualcomm Incorporated | imported from 3GU |
| S3‑183621 | Clarification on RRC Inactive procedure support by ng-eNB | Qualcomm Incorporated | imported from 3GU |
| S3‑183622 | NR-NR Dual Connectivity | Qualcomm Incorporated | imported from 3GU |
| S3‑183623 | KgNB derivation in N2 handover | Qualcomm Incorporated | imported from 3GU |
| S3‑183624 | Security mechanism for UE Parameters Update via UDM Control Plane Procedure | Qualcomm Incorporated | imported from 3GU |
| S3‑183625 | Clarifications to SUPI and SUCI | Qualcomm Incorporated | imported from 3GU |
| S3‑183626 | General SCAS API requirements | Ericsson India Private Limited | imported from 3GU |
| S3‑183627 | New SID on data rate enhancements for user plane integrity protection | Motorola Mobility, Lenovo | imported from 3GU |
| S3‑183628 | Clarifications to SUPI and SUCI | Qualcomm Incorporated | imported from 3GU |
| S3‑183629 | TR 33.841: complete clause on OTA mechanism | Gemalto N.V. | imported from 3GU |
| S3‑183630 | P-CR describing current manual roaming in US^^ | Sprint Corporation | imported from 3GU |
| S3‑183631 | Key Issue on secure communication between ME and UICC | Alibaba (China) group., Ltd., China Mobile | imported from 3GU |
| S3‑183632 | Discussion on one potential way to improve the efficiency of IP | Apple Computer Trading Co. Ltd | imported from 3GU |
| S3‑183633 | Resolution of Editor’s note on wildcard certificates in S3-183441 | Nokia, Nokia Shanghai Bell, Telekom Deutschland GmbH | imported from 3GU |
| S3‑183634 | TS 33 127 v110 | BT plc | imported from 3GU |
| S3‑183635 | Cover sheet for presentation of TS 33.127 to SA Plenary | SA3 (SA3-LI) | imported from 3GU |
| S3‑183636 | Comments on S3-183624 | NEC Corporation | imported from 3GU |
| S3‑183637 | PCR to TR33.514 SUCI test case correction | CATT | imported from 3GU |
| S3‑183638 | Scenarios that require generation of telescopic FQDN in SEPP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183639 | Verification of PLMN ID in N32 message | Huawei, Hisilicon | imported from 3GU |
| S3‑183640 | LS-Reply proposal - Commenting on S3-183599, S3-183600, S3-183327 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183641 | Comments on S3-183550 NSSAI inclusion in NAS | Nokia, Nokia Shangahi bell | imported from 3GU |
| S3‑183642 | Comments on S3-183374 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183643 | Discussion on the changes proposed in S3-183620 and S3-183623 | Qualcomm Incorporated | imported from 3GU |
| S3‑183644 | NG-RAN – clause 6.9.2.2 | Ericsson | imported from 3GU |
| S3‑183645 | NG-RAN – clause 6.9.2.3.3 | Ericsson | imported from 3GU |
| S3‑183646 | NG-RAN – clause 6.9.2.3.4 | Ericsson | imported from 3GU |
| S3‑183647 | NF-SEPP TLS handling | Ericsson Hungary Ltd | imported from 3GU |
| S3‑183648 | Draft CR Corrections to N32 Protection Policies | Telekom Deutschland | imported from 3GU |
| S3‑183649 | Draft CR Adopting more normative language in clause 13 | Telekom Deutschland | imported from 3GU |
| S3‑183650 | Correction on LTE suspend/resume procedure for EDT capable UE | Intel Corporation (UK) Ltd | imported from 3GU |
| S3‑183651 | User Plane Integrity Protection for EDT | Huawei, Hisilicon,Ericsson | imported from 3GU |
| S3‑183652 | LS to RAN23 on UP Integrity Protection for Small Data in Early Data Transfer | Huawei, Hisilicon | imported from 3GU |
| S3‑183653 | 3GPP SA3 statement | SA3 WG vice chair (NTT-Docomo) | imported from 3GU |
| S3‑183654 | Reply LS to ITU-T SG17 on X.5Gsec-q study | NCSC | imported from 3GU |
| S3‑183655 | Two parallel N32-c connections between SEPPs | Nokia | imported from 3GU |
| S3‑183656 | Security between SEPP and IPX | Nokia | imported from 3GU |
| S3‑183657 | Editorial corrections in 13.2 | Nokia | imported from 3GU |
| S3‑183658 | Response LS on maximum output size of SUPI concealment schemes | Ericsson | imported from 3GU |
| S3‑183659 | Reply to:LS on initial NAS security agreements | Intel | imported from 3GU |
| S3‑183660 | Reply LS on security requirements for Integrity protection for DRBs in MR-DC | Huawei, Hisilicon | imported from 3GU |
| S3‑183661 | CR on Secondary Re-authentication | Huawei, HiSilicon | imported from 3GU |
| S3‑183662 | Reply to: Reply LS on Clarifications on SUPI definition and NAI format | Qualcomm | imported from 3GU |
| S3‑183663 | AS subscription temperary identifier privacy | ZTE Corporation | imported from 3GU |
| S3‑183664 | Update RRC reestablishment security procedure based on RAN2 agreement | Huawei, Hisilicon | imported from 3GU |
| S3‑183665 | Clarification on RRC Inactive procedure support by ng-eNB | Qualcomm Incorporated | imported from 3GU |
| S3‑183666 | Proposal about improvement of the UP security policy | China Mobile | imported from 3GU |
| S3‑183667 | Support of UP security policy in ng-eNB | Ericsson | imported from 3GU |
| S3‑183668 | Adding NR-DC to the scenarios of MR-DC | Huawei, Hisilicon,Qualcomm,Ericsson | imported from 3GU |
| S3‑183669 | Draft CR to S3-183210 (Handling of UP security policy in MR-DC) | Ericsson | imported from 3GU |
| S3‑183670 | NG-RAN – clause 6.9.2.2 | Ericsson | imported from 3GU |
| S3‑183671 | NG-RAN – clause 6.9.2.3.3 | Ericsson | imported from 3GU |
| S3‑183672 | NG-RAN – clause 6.9.2.3.4 | Ericsson | imported from 3GU |
| S3‑183673 | Aligning the description of the initial NAS security procedures based on the CT1 agreements | Qualcomm Incorporated,ZTE | imported from 3GU |
| S3‑183674 | Handling of NAS COUNTs | Ericsson | imported from 3GU |
| S3‑183675 | Clarify SUPI format in KAMF computation | Nokia | imported from 3GU |
| S3‑183676 | Clarification: AMF confirming UE SUPI in case NAS SMC failed | Huawei, Hisilicon,Nokia | imported from 3GU |
| S3‑183677 | Editorial correction in Clause 6.9.3.2 | Nokia | imported from 3GU |
| S3‑183678 | Correction to Key hierarchy diagram | Samsung | imported from 3GU |
| S3‑183679 | Update of EAP-AKA’ reference to make it compatible with 5G | Ericsson | imported from 3GU |
| S3‑183680 | Clarification on interworking | Huawei, Hisilicon | imported from 3GU |
| S3‑183681 | Inter PLMN routing | Nokia | imported from 3GU |
| S3‑183682 | Inter PLMN routing | Nokia | imported from 3GU |
| S3‑183683 | Verification of PLMNid by the receiving SEPP | Deutsche Telekom | imported from 3GU |
| S3‑183684 | Corrections to N32 Protection Policies | Telekom Deutschland GmbH, Nokia | imported from 3GU |
| S3‑183685 | N32: remove redundant references to encrypted IEs | Ericsson | imported from 3GU |
| S3‑183686 | Security between SEPP and IPX | Nokia, Nokia Shanghai Bell, Telekom Deutschland GmbH | imported from 3GU |
| S3‑183687 | Two parallel N32-c connections between SEPPs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183688 | Adopting more normative language in clause 13 | Telekom Deutschland GmbH, Nokia | imported from 3GU |
| S3‑183689 | Editorial corrections in 13.2 | Nokia, Nokia Shanghai Bell,Huawei | imported from 3GU |
| S3‑183690 | Shift of text from SEPP intro to subclause | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183691 | IoT Group Authentication | Huawei, Hisilicon | imported from 3GU |
| S3‑183692 | Maximum output size of SUPI concealment scheme | Ericsson | imported from 3GU |
| S3‑183693 | Clarification to protection scheme identifier | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183694 | Alignment on Home Network Public Key | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183695 | Corrections to definition of 5G AS security context for 3GPP access | China Mobile | imported from 3GU |
| S3‑183696 | UPdate test cases in 33.511 | Huawei, Hisilicon | imported from 3GU |
| S3‑183697 | Draft TS 33.511 | Huawei | imported from 3GU |
| S3‑183698 | Adding Execution Steps to in 4.2.2.1.1, 4.2.2.1.2, and 4.2.2.1.7 | Huawei, Hisilicon | imported from 3GU |
| S3‑183699 | Mapping requirements and test cases from 33.216 to 33.511 | Huawei, Hisilicon | imported from 3GU |
| S3‑183700 | draft TS 33.512 | Deutsche Telekom | imported from 3GU |
| S3‑183701 | PCR to TR33.514 SUCI test case correction | CATT | imported from 3GU |
| S3‑183702 | Draft TS 33.514 | NEC | imported from 3GU |
| S3‑183703 | Draft TS 33.517 | Nokia | imported from 3GU |
| S3‑183704 | Draft TS 33.518 | Nokia | imported from 3GU |
| S3‑183705 | Draft TS 33.519 | ZTE | imported from 3GU |
| S3‑183706 | LS on IAB security | R2-1818748 | imported from 3GU |
| S3‑183707 | Authentication on application functions | ZTE Corporation | imported from 3GU |
| S3‑183708 | Minutes of SBA Offline Discussion | Deutsche Telekom | imported from 3GU |
| S3‑183709 | Draft CR Incorporating general SBA aspects in TS 33.117 | Nokia | imported from 3GU |
| S3‑183710 | Add EDCE5 realted requirements and testcases to 33.216 | Huawei, Hisilicon | imported from 3GU |
| S3‑183711 | Reply to: LS on IAB security | Ericsson | imported from 3GU |
| S3‑183712 | EDCE5 – Fixing contradicting and insecure scg/sk counter handling in 33.401 from 36.331 | Ericsson | imported from 3GU |
| S3‑183713 | Correction/enhancement in CAPIF TS | NEC Corporation | imported from 3GU |
| S3‑183714 | Reply to: LS on EAS-C&U support | Vodafone | imported from 3GU |
| S3‑183715 | LS on Control Plane Solution for Steering of Roaming in 5GS | Vodafone | imported from 3GU |
| S3‑183716 | Delete information during API invoker offboarding | Huawei, Hisilicon | imported from 3GU |
| S3‑183717 | LS on authentication of group of IoT devices | NTT-Docomo | imported from 3GU |
| S3‑183718 | New SID on User Plane Integrity Protection | VODAFONE Group Plc | imported from 3GU |
| S3‑183719 | Study on mitigation of the charging fraud attack | Huawei, Hisilicon | imported from 3GU |
| S3‑183720 | LS to GSMA on mitigation of the charging fraud attack | Huawei | imported from 3GU |
| S3‑183721 | New SID on authentication enhancements in 5GS | Ericsson | imported from 3GU |
| S3‑183722 | Security Impacts of Virtualisation | BT plc | imported from 3GU |
| S3‑183723 | New option for 33.855 solution #8 | Ericsson India Private Limited | imported from 3GU |
| S3‑183724 | Draft TR 33.855 | Deutsche Telekom | imported from 3GU |
| S3‑183725 | Update of PARLOS solution #1 | Motorola Mobility, Lenovo | imported from 3GU |
| S3‑183726 | Draft TR 33.815 | Sprint | imported from 3GU |
| S3‑183727 | P-CR describing current manual roaming in US | Sprint Corporation | imported from 3GU |
| S3‑183728 | Proposed change to the solution #1.1 of TR 33.856 | Huawei, Hisilicon | imported from 3GU |
| S3‑183729 | Draft TR 33.856 | China Unicom | imported from 3GU |
| S3‑183730 | Evaluation for the solution "Return from UTRAN to E-UTRAN or NR" | China Unicom | imported from 3GU |
| S3‑183731 | Conclusion for the solution "Return from UTRAN to E-UTRAN or NR" | China Unicom | imported from 3GU |
| S3‑183732 | clean up the EN of subclause 7 in TR 33.856 | Huawei, Hisilicon | imported from 3GU |
| S3‑183733 | Cover sheet TR 33.856 | Huawei | imported from 3GU |
| S3‑183734 | Protecting SUPI for user privacy | ZTE Corporation | imported from 3GU |
| S3‑183735 | Draft TR 33.835 | China Mobile | imported from 3GU |
| S3‑183736 | New Key Issue: Generic battery efficient end-to-end security | KPN | imported from 3GU |
| S3‑183737 | New KI: Key Lifetimes | Ericsson India Private Limited | imported from 3GU |
| S3‑183738 | CR to TS33.501-Registration related text correction | CATT | imported from 3GU |
| S3‑183739 | New WID on security aspects of single radio voice continuity from 5G to 3G | China Unicom, Huawei, HiSilicon, ZTE, CATT, OPPO, CATR | imported from 3GU |
| S3‑183740 | Adding UP security policy in SN Addition/modification Request message | Huawei, Hisilicon | imported from 3GU |
| S3‑183741 | LS on initial NAS message protection | Qualcomm Incorporated | imported from 3GU |
| S3‑183742 | Security mechanism for UE Parameters Update via UDM Control Plane Procedure | Qualcomm Incorporated,Huawei | imported from 3GU |
| S3‑183743 | Update on access token in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S3‑183744 | pCR to TR33.814 - Scope | CATT | imported from 3GU |
| S3‑183745 | New SID on authentication enhancements in 5GS | Ericsson | imported from 3GU |
| S3‑183746 | New KI: API for AKMA keys in UE | Ericsson India Private Limited | imported from 3GU |
| S3‑183747 | Solution for bootstrapping authentication of AKMA | Huawei, Hisilicon | imported from 3GU |
| S3‑183748 | Discussion and pCR of Candidate Solution: Transport independent procedure using existing protocols | China Mobile; Alibaba (China) Group., Ltd. | imported from 3GU |
| S3‑183749 | Discussion and pCR of candidate solution: UE implementation schemes in achieving AKMA procedures | China Mobile; Alibaba (China) Group., Ltd. | imported from 3GU |
| S3‑183750 | New solution: Access independent architecture solution for AKMA | Ericsson India Private Limited | imported from 3GU |
| S3‑183751 | New solution: Stand-alone architecture solution for AKMA | Ericsson India Private Limited | imported from 3GU |
| S3‑183752 | pCR to TR 33.834 - Update to LTKUP Conclusions | VODAFONE Group Plc | imported from 3GU |
| S3‑183753 | Draft TR 33.834 | Vodafone | imported from 3GU |
| S3‑183754 | cover sheet TR 33.834 | Vodafone | imported from 3GU |
| S3‑183755 | New SID on LTKUP Detailed Solutions | VODAFONE Group Plc | imported from 3GU |
| S3‑183756 | LS to SAGE on 256bit algorithms | Vodafone | imported from 3GU |
| S3‑183757 | pCR to TR 33 841 Threat details to symmetric cryptography | CATT | imported from 3GU |
| S3‑183758 | Draft TR 33.841 | Vodafone | imported from 3GU |
| S3‑183759 | pCR to Include content discussing forward security | NIST | imported from 3GU |
| S3‑183760 | Update to Impacted NextGen Areas - TR 33.841 | NCSC | imported from 3GU |
| S3‑183761 | pCR to TR 33 841 regarding key derivation function | China Mobile; Vodafone | imported from 3GU |
| S3‑183762 | TR 33.841: complete clause on OTA mechanism | Gemalto N.V. | imported from 3GU |
| S3‑183763 | pCR to TR 33 841 Study of individual algorithm details | CATT, CAICT, China Mobile, China Telecom, China Unicom, Huawei, HiSilicon, ZTE, OPPO | imported from 3GU |
| S3‑183764 | Clause 13.1.1: AES modes | Ericsson | imported from 3GU |
| S3‑183765 | Modifications and Clarifications for TR 33.841 | NCSC | imported from 3GU |
| S3‑183766 | Potential Requirements for TR 33.841 | NCSC, CAICT, CATT, China Mobile, China Telecom, China Unicom, Huawei, HiSilicon, ZTE, OPPO | imported from 3GU |
| S3‑183767 | Conclusions for TR 33.841 | NCSC, CAICT, CATT, China Mobile, China Telecom, China Unicom, Huawei, HiSilicon, ZTE, OPPO, Qihoo 360 | imported from 3GU |
| S3‑183768 | Editorials for TR 33.841 | NCSC | imported from 3GU |
| S3‑183769 | Cover sheet TR 33.841 | Vodafone | imported from 3GU |
| S3‑183770 | Key issue for encryption protection of location data | Huawei, Hisilicon | imported from 3GU |
| S3‑183771 | Key issue for integrity protection of location and assistance data | Huawei, Hisilicon | imported from 3GU |
| S3‑183772 | Improvement for key issue on the signalling overload due to malicious applications on the UE | Huawei, HiSilicon,KPN | imported from 3GU |
| S3‑183773 | New KI: Protection of interface used by NIDD procedures | Ericsson LM | imported from 3GU |
| S3‑183774 | Draft TR 33.861 | Ericsson | imported from 3GU |
| S3‑183775 | Adding Key issue for Connectionless service security | Nokia | imported from 3GU |
| S3‑183776 | New KI: Privacy protection of the NIDD API between UPF/NEF and AF | Ericsson LM | imported from 3GU |
| S3‑183777 | Solution proposal for FS_CIoT_sec_5G | NEC Corporation | imported from 3GU |
| S3‑183778 | Security solution for MO SMS in initial NAS message - handling AMF re-allocation | Ericsson LM | imported from 3GU |
| S3‑183779 | Security solution for small data sent with EDT in RRC Resume Request for E-UTRA connected to 5GC | Ericsson | imported from 3GU |
| S3‑183780 | Security solution for small data included in initial NAS to handle AMF reallocation | Ericsson LM | imported from 3GU |
| S3‑183781 | New Solution for Key Issue #4: Use of UE Configuration Update | KPN | imported from 3GU |
| S3‑183782 | Solution for protecting gNB from RRC re-establishment DDoS attack | Huawei, Hisilicon | imported from 3GU |
| S3‑183783 | New solution for protection of interface used by NIDD procedures | Ericsson LM | imported from 3GU |
| S3‑183784 | Draft TR 33.807 | Huawei | imported from 3GU |
| S3‑183785 | LS on FN-RG authentication and related questions | Ericsson | imported from 3GU |
| S3‑183786 | New KI: Authentication of 5G capable UE behind a RG | Ericsson | imported from 3GU |
| S3‑183787 | New KI: User plane data handling for 5G capable UE behind a RG | Ericsson,NEC | imported from 3GU |
| S3‑183788 | Key Issue on Access Independent Security for 5WWC | NEC Corporation | imported from 3GU |
| S3‑183789 | LS on verification of PLMN-ID in the SEPP | Deutsche Telekom | imported from 3GU |
| S3‑183790 | Clarifications to SUPI and SUCI | Qualcomm,Nokia | imported from 3GU |
| S3‑183791 | New Solution: 5GC-capable UEs behind 5G-RG/FN-RG using N3GPP-access solutions | Ericsson | imported from 3GU |
| S3‑183792 | Draft TR 33.808 | Huawei | imported from 3GU |
| S3‑183793 | Reply-LS on work item "X.5Gsec-q" | ETSI TC Cyber WG QSC | imported from 3GU |
| S3‑183794 | Liaison Statement to ITU-T SG17: Response to proposal for ITU-T SG17 question on quantum-safe communication | ETSI TC Cyber WG QSC | imported from 3GU |
| S3‑183795 | LS on Security method negotiation | Samsung | imported from 3GU |
| S3‑183796 | Key Issue on KDF negotiation between UE and AMF | Huawei, Hisilicon | imported from 3GU |
| S3‑183797 | KgNB derivation in EPS to 5GS handover | Qualcomm Incorporated | imported from 3GU |
| S3‑183798 | Proposal for key issue structure | Nokia | imported from 3GU |
| S3‑183799 | Draft TR 33.809 | Apple | imported from 3GU |
| S3‑183800 | Clause #4 for the upcoming TR on FS_5GFBS | Ericsson | imported from 3GU |
| S3‑183801 | SI integrity - new KI for the upcoming TR on FS_5GFB | Ericsson,Samsung,Apple,Huawei | imported from 3GU |
| S3‑183802 | Key issue false base station detection and isolation | Nokia,Ericsson | imported from 3GU |
| S3‑183803 | Key issue of security protection on the unicast message from the UE before security activation | Apple Computer Trading Co. Ltd,Ericsson | imported from 3GU |
| S3‑183804 | SON security - new KI for the upcoming TR on FS_5GFBS | Ericsson | imported from 3GU |
| S3‑183805 | Key issue on Authentication relay attack | Huawei, Hisilicon | imported from 3GU |
| S3‑183806 | Radio jamming - placeholder-only KI for the upcoming TR on FS_5GFB | Ericsson | imported from 3GU |
| S3‑183807 | Draft TR 33.813 | Nokia | imported from 3GU |
| S3‑183808 | pCR to TR 33.813 Adding key issue for Slice specific authentication | Nokia,Huawei | imported from 3GU |
| S3‑183809 | New key issue on key separation between Network Slices | Ericsson | imported from 3GU |
| S3‑183810 | New KI on security features for NSaaS | Huawei, HiSilicon,China Mobile | imported from 3GU |
| S3‑183811 | Draft skeleton for TR 33.814 | CATT | imported from 3GU |
| S3‑183812 | Draft TR 33.814 | CATT | imported from 3GU |
| S3‑183813 | WLAN positioning - new KI for the upcoming TR on FS_eLCS_Sec | Ericsson | imported from 3GU |
| S3‑183814 | TBS positioning - new KI for the upcoming TR on FS_eLCS_Sec | Ericsson | imported from 3GU |
| S3‑183815 | Scope for TR33.825 on URLLC security | Huawei, HiSilicon | imported from 3GU |
| S3‑183816 | TR 33.825 | Huawei | imported from 3GU |
| S3‑183817 | Key issue proposal for security of URLLC for 5GS | NEC Corporation | imported from 3GU |
| S3‑183818 | Key issue security for redundant transmissions | Huawei, HiSilicon,Ericsson,LG | imported from 3GU |
| S3‑183819 | Key issue security policy for URLLC service | Huawei, HiSilicon | imported from 3GU |
| S3‑183820 | Key issue security aspect of low latency handover procedures | Huawei, HiSilicon | imported from 3GU |
| S3‑183821 | KI for retaining AS security key | Ericsson | imported from 3GU |
| S3‑183822 | Security solution for handling UP security policy for redundant data | Ericsson | imported from 3GU |
| S3‑183823 | Solution for flexibility to retain or to change AS security keys | Ericsson | imported from 3GU |
| S3‑183824 | Scope of TR 33.818 | China Mobile, CATR | imported from 3GU |
| S3‑183825 | Draft TR 33.818 | China Mobile | imported from 3GU |
| S3‑183826 | Draft TR 33.819 | Nokia | imported from 3GU |
| S3‑183827 | VERTICAL study - Scope | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S3‑183828 | New Key Issue: Authentication and Authorization for Interworking, Roaming between NPN and PLMN | InterDigital Europe. Ltd.,Nokia | imported from 3GU |
| S3‑183829 | Key issue for authentication and authorization of 5GLAN UE in 5GLAN group communication | NEC Corporation | imported from 3GU |
| S3‑183830 | Assigning additional FC values to TS 33.501 | Qualcomm | imported from 3GU |
| S3‑183831 | Key Issue on Authentication of a UE for Non-public network | Huawei, Hisilicon,Nokia | imported from 3GU |
| S3‑183832 | Reply LS on UP Integrity Protection for Small Data in Early Data Transfer | R3-187230 | imported from 3GU |
| S3‑183833 | Reply LS on UP Integrity Protection for Small Data in Early Data Transfer | R2-1818666 | imported from 3GU |
| S3‑183834 | Reply LS on Separate HSS and UDM and security credentials storage | Nokia | imported from 3GU |
| S3‑183835 | Handling of UP security policy in MR-DC | Huawei, Hisilicon, Qualcomm Incorporated, Ericsson | imported from 3GU |
| S3‑183836 | Interworking – correcting keying material in HO request message (EPS to 5GS) | Ericsson,Huawei | imported from 3GU |
| S3‑183837 | Work Plan input from Rapporteurs | MCC | imported from 3GU |
| S3‑183838 | SA3 meeting calendar | MCC | imported from 3GU |
| S3‑183839 | Key issue on Authentication relay attack | Huawei, Hisilicon | imported from 3GU |
page generated from database: 2024-04-22 07:58:53