3GPP TDocs (written contributions) at meeting
Meeting: S3-88b - 2017-10-09 to 2017-10-13, Singapore
meeting id: S3-88b (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S3‑172200 | Agenda | SA WG3 Chair | imported from 3GU |
S3‑172201 | SA3 Work Plan | MCC | imported from 3GU |
S3‑172202 | SA3 meeting calendar | MCC | imported from 3GU |
S3‑172203 | Way for protecting sensitive information transmitted between operators | ZTE Corporation, China Mobile, CATR | imported from 3GU |
S3‑172204 | Reply LS on algorithm selection in E-UTRA-NR Dual Connectivity | C1-173748 | imported from 3GU |
S3‑172205 | Reply LS to LS on PLMN and RAT selection policies for roaming | C1-173751 | imported from 3GU |
S3‑172206 | LS on applicability of service based interface for legacy core network elements | C1-173753 | imported from 3GU |
S3‑172207 | Reply LS on 5G signalling protocol requirements | C4-174311 | imported from 3GU |
S3‑172208 | LS on Conclusion on Service Based Architecture Protocol Selection | C3-174370,C4-174343 | imported from 3GU |
S3‑172209 | LS to SA3 on RAN2 agreements on jumbo frames | R2-1709804 | imported from 3GU |
S3‑172210 | Reply LS on NR security input parameters | R2-1709969 | imported from 3GU |
S3‑172211 | LS reply on Support for fake gNB detection mechanisms | R2-1709980 | imported from 3GU |
S3‑172212 | LS on secure storage and processing of subscription credentials | S1-173475 | imported from 3GU |
S3‑172213 | LS on PLMN and RAT selection policies for roaming | S1-173478 | imported from 3GU |
S3‑172214 | Reply LS on Address Mapping Requirements | S2-176561 | imported from 3GU |
S3‑172215 | LS Response on Service Based Architecture | S2-176692 | imported from 3GU |
S3‑172216 | LS on Undetectability of LI Data stored in a UDSF | S3i170259 | imported from 3GU |
S3‑172217 | Address Mapping Requirements | S3i170260 | imported from 3GU |
S3‑172218 | Reply LS on 5GS Security aspects seeking resolution | S2-175309 | imported from 3GU |
S3‑172219 | LS on PLMN and RAT selection policies for roaming | S2-175286 | imported from 3GU |
S3‑172220 | Remove editor notes related to privacy requirements | CATT, CATR | imported from 3GU |
S3‑172221 | Add new requirement related to visibility and configurability | CATT, CATR | imported from 3GU |
S3‑172222 | Remove editor note related to SIDF and text corrections | CATT | imported from 3GU |
S3‑172223 | Moving Serving Network Name construction into it's own clause | KPN N.V. | imported from 3GU |
S3‑172224 | Rewriting Clause 6.1.2 and 6.1.3 in normative language and adding Annex A | KPN N.V. | imported from 3GU |
S3‑172225 | Discussion on provision of SUPI from home to visited network | VODAFONE Group Plc | imported from 3GU |
S3‑172226 | Rewriting Clause 6.1.2 and 6.1.3 in normative language and adding Annex A | KPN N.V. | imported from 3GU |
S3‑172227 | Security Considerations for Service Based Architecture in 5G | Deutsche Telekom AG | imported from 3GU |
S3‑172228 | PCR to 33.501 – typos and language in multiple clauses. | InterDigital, Inc. | imported from 3GU |
S3‑172229 | PCR to 33.501 – Clause 6.7.2 – rephrased for clarity | InterDigital, Inc. | imported from 3GU |
S3‑172230 | PCR to 33.501 – Clause 6.1.3.1 – rephrased for clarity | InterDigital, Inc. | imported from 3GU |
S3‑172231 | Corrections to MCData security procedures | SAMSUNG | imported from 3GU |
S3‑172232 | Corrections to SgNB security procedures | SAMSUNG | imported from 3GU |
S3‑172233 | pCR on signalling procedure for periodic local authentication | SAMSUNG | imported from 3GU |
S3‑172234 | Discussion on Securing the Network Steering Information | SAMSUNG | imported from 3GU |
S3‑172235 | pCR for Securing the Network Steering Information | SAMSUNG | imported from 3GU |
S3‑172236 | Discussion on user plane protection | SAMSUNG | imported from 3GU |
S3‑172237 | Discussion on UDM term consistency | SAMSUNG | imported from 3GU |
S3‑172238 | Update the skeleton of TS 33.501 for service based architecture | Huawei, Hisilicon | imported from 3GU |
S3‑172239 | Security requirements for service based architecture | Huawei, Hisilicon | imported from 3GU |
S3‑172240 | NF registration and authentication procedure of Service Based Architecture | Huawei, Hisilicon | imported from 3GU |
S3‑172241 | Authorization of NF service discovery | Huawei, Hisilicon | imported from 3GU |
S3‑172242 | Authorization of NF service access | Huawei, Hisilicon | imported from 3GU |
S3‑172243 | Protection of the connection between NFs | Huawei, Hisilicon | imported from 3GU |
S3‑172244 | Update the skeleton of TS 33.501 for service based architecture | Huawei, Hisilicon, CATR | imported from 3GU |
S3‑172245 | Address EN in requirements for gNB setup and configuration | Huawei, Hisilicon, | imported from 3GU |
S3‑172246 | Flexible retaining AS keys solution | Huawei, Hisilicon, China Mobile | imported from 3GU |
S3‑172247 | Requirements for UP and CP for the gNB | Huawei, Hisilicon, China Mobile | imported from 3GU |
S3‑172248 | Support NIA0 algorithm for UP data | Huawei, Hisilicon | imported from 3GU |
S3‑172249 | Meeting SUPI privacy and LI Requirements | Huawei, Hisilicon, Intel | imported from 3GU |
S3‑172250 | Intra-gNB meaning in 5G RAN architecture | Huawei, Hisilicon, China Mobile | imported from 3GU |
S3‑172251 | Subscriber Privacy under Home network control | Huawei, Hisilicon | imported from 3GU |
S3‑172252 | Security Algorithms Negotiation for Initial AS security context | Huawei, Hisilicon, China Mobile | imported from 3GU |
S3‑172253 | Updates security handling in mobility | Huawei, Hisilicon, Deutsche Telekom AG | imported from 3GU |
S3‑172254 | Moving UE handling SUCI to SUCI clause | Huawei, Hisilicon, China Mobile | imported from 3GU |
S3‑172255 | Adding Forward & Backward Security definition to TS33.501 | Huawei, Hisilicon | imported from 3GU |
S3‑172256 | Security Procedures between 5G Network Functions | Huawei, Hisilicon | imported from 3GU |
S3‑172257 | pCR to TS 33.501 KDF negotiation | Huawei; Hisilicon | imported from 3GU |
S3‑172258 | Security Handling for RRC Connection Re-establishment | Huawei; Hisilicon | imported from 3GU |
S3‑172259 | Discussion on flexibility of retaining or changing AS security key | Huawei; Hisilicon | imported from 3GU |
S3‑172260 | Draft LS on Discussion on flexibility of retaining or changing AS security key | Huawei; Hisilicon | imported from 3GU |
S3‑172261 | pCR to TS 33.501: Security Handling at Transition from RRC-INACTIVE to RRC-CONNECTED transition | Huawei; Hisilicon | imported from 3GU |
S3‑172262 | pCR to TS 33.501: reusing {NCC, NH} to key derivation for handover | Huawei; Hisilicon | imported from 3GU |
S3‑172263 | Delete allowed NSSAI in NAS SMC | Huawei; Hisilicon | imported from 3GU |
S3‑172264 | Discussion on security of interworking | Huawei; Hisilicon | imported from 3GU |
S3‑172265 | regestration procedures in 5G-RAN during interworking from EPC to 5GC | Huawei; Hisilicon | imported from 3GU |
S3‑172266 | TAU procedures in E-UTRAN during interworking from 5GC to EPC | Huawei; Hisilicon | imported from 3GU |
S3‑172267 | handover procedures during interworking from EPC to 5GC | Huawei; Hisilicon | imported from 3GU |
S3‑172268 | handover procedures during interworking from 5GC to EPC | Huawei; Hisilicon | imported from 3GU |
S3‑172269 | Discussion on the reception of UE NR security capabilities | Huawei; Hisilicon | imported from 3GU |
S3‑172270 | Reception of UE NR security capabilities | Huawei; Hisilicon | imported from 3GU |
S3‑172271 | key isolation between AMFs during idle mode mobility | Huawei; Hisilicon | imported from 3GU |
S3‑172272 | Adding the definition of NEA0 and NIA0(5.6.1) | Huawei; Hisilicon | imported from 3GU |
S3‑172273 | Adding the content on security contexts(6.3) | Huawei; Hisilicon | imported from 3GU |
S3‑172274 | Adding the content on Subscription identification procedure(6.8.4) | Huawei; Hisilicon | imported from 3GU |
S3‑172275 | Clarification NULL Integirity algorithm for OPtion3 | Huawei; Hisilicon | imported from 3GU |
S3‑172276 | Discussion on a framework of AS security | Huawei; Hisilicon | imported from 3GU |
S3‑172277 | AS Security Negotiation and Activation | Huawei, Hisilicon | imported from 3GU |
S3‑172278 | UP security policy | Huawei; Hisilicon | imported from 3GU |
S3‑172279 | UP protection features | Huawei; Hisilicon | imported from 3GU |
S3‑172280 | Corrections on 33501 | Huawei; Hisilicon | imported from 3GU |
S3‑172281 | pCR to TS 33.501 add management plane protection to 7.2 | Huawei; Hisilicon | imported from 3GU |
S3‑172282 | pCR to TS 33.501 add reference to management plane to 5.2.4 | Huawei; Hisilicon | imported from 3GU |
S3‑172283 | Remove editor note related to SUCI | CATT | imported from 3GU |
S3‑172284 | Raw public key provisioning | CATT | imported from 3GU |
S3‑172285 | 5G-RAN Key Setting | Huawei & Hisilicon | imported from 3GU |
S3‑172286 | Providing details on the authentication vector and calculation of keys | Huawei & Hisilicon | imported from 3GU |
S3‑172287 | Discussion on secondary authentication | Huawei & Hisilicon | imported from 3GU |
S3‑172288 | Secondary authentication via NEF | Huawei & Hisilicon | imported from 3GU |
S3‑172289 | Security Procedures with EAP-TLS | Huawei & Hisilicon | imported from 3GU |
S3‑172290 | EAP Framework | Huawei & Hisilicon | imported from 3GU |
S3‑172291 | Confidentiality of NSSAI | Huawei & Hisilicon | imported from 3GU |
S3‑172292 | DN authorization grant and revocation | Huawei & Hisilicon | imported from 3GU |
S3‑172293 | ID linkage verification in secondary authentication | Huawei & Hisilicon | imported from 3GU |
S3‑172294 | Secondary authentication for multiple PDU sessions | Huawei & Hisilicon | imported from 3GU |
S3‑172295 | Interworking with EPC without N26 | Huawei; Hisilicon | imported from 3GU |
S3‑172296 | Adding content to NAS security | Huawei; Hisilicon | imported from 3GU |
S3‑172297 | Caculation of SUCI in ME | Huawei; Hisilicon | imported from 3GU |
S3‑172298 | Editorial corrections for Annex E | Huawei; Hisilicon | imported from 3GU |
S3‑172299 | pCR on editorial correction of TS 33.501 | NEC EUROPE LTD | imported from 3GU |
S3‑172300 | [MCSec] 33180 R14 client check at GMK provisioning | Motorola Mobility Germany GmbH | imported from 3GU |
S3‑172301 | [MCSec] 33180 R14 add transmission control for MCVideo | Motorola Mobility Germany GmbH | imported from 3GU |
S3‑172302 | [MCSec] 33180 R14 MCPTT to MCX fixes | Motorola Mobility Germany GmbH | imported from 3GU |
S3‑172303 | [MCSec] 33180 R14 SIP MESSAGE clarification for MCData | Motorola Mobility Germany GmbH | imported from 3GU |
S3‑172304 | [eMCSec] 33180 R15 client check at GMK provisioning (mirror) | Motorola Mobility Germany GmbH | imported from 3GU |
S3‑172305 | [eMCSec] 33180 R15 add transmission control for MCVideo (mirror) | Motorola Mobility Germany GmbH | imported from 3GU |
S3‑172306 | [eMCSec] 33180 R15 MCPTT to MCX fixes (mirror) | Motorola Mobility Germany GmbH | imported from 3GU |
S3‑172307 | [eMCSec] 33180 R15 SIP MESSAGE clarification for MCData (mirror) | Motorola Mobility Germany GmbH | imported from 3GU |
S3‑172308 | Draft skeleton proposal for TR33.811 | Huawei, Hisilicon, China Mobile | imported from 3GU |
S3‑172309 | Adding references to TR 33.811 | Huawei, Hisilicon, China Mobile | imported from 3GU |
S3‑172310 | Introduction section for TR33.811 | Huawei, Hisilicon, China Mobile | imported from 3GU |
S3‑172311 | A proposal for the scope of the TR33.811 | Huawei, Hisilicon | imported from 3GU |
S3‑172312 | A key issue of interface security for TR33.811 | Huawei, Hisilicon, CATR | imported from 3GU |
S3‑172313 | A key issue on security capabilities for TR33.811 | Huawei, Hisilicon | imported from 3GU |
S3‑172314 | A key issue on security protection of messages exchanged with customers | Huawei, Hisilicon | imported from 3GU |
S3‑172315 | A key issue on security isolation of network slices | Huawei, Hisilicon | imported from 3GU |
S3‑172316 | Changes to Initiation of Authentication and subscription identity procedure. | Intel | imported from 3GU |
S3‑172317 | Secondary Re-Authentication | Intel | imported from 3GU |
S3‑172318 | Solution to prevent unauthorized access to external Data Network | Intel | imported from 3GU |
S3‑172319 | Binding Primary and Secondary authentication | Intel | imported from 3GU |
S3‑172320 | Security key handling during Xn handover | Intel | imported from 3GU |
S3‑172321 | Clause 8.3.1.1.1 (key handling in handover, general, access stratum) - Disc | Ericsson | imported from 3GU |
S3‑172322 | Clause 8.3.1.1.1 (key handling in handover, general, access stratum) - pCR | Ericsson | imported from 3GU |
S3‑172323 | Clause 8.3.1.1.1 (key derivation in handover key chaining model) - Disc | Ericsson | imported from 3GU |
S3‑172324 | Clause 8.3.1.1.1 (key derivation in handover, general, access stratum) - pCR | Ericsson | imported from 3GU |
S3‑172325 | Clause 8.3.1.1.2 (key handling in handover, general, non access stratum) | Ericsson | imported from 3GU |
S3‑172326 | Clause 8.3.1.2 (key derivation for context modification procedure) | Ericsson | imported from 3GU |
S3‑172327 | Clause 8.3.1.3.1 (key derivation during handover, intra-gNB) | Ericsson | imported from 3GU |
S3‑172328 | Clause 8.3.1.3.2/8.3.1.3.2 (key derivation during handover, Xn/N2) - Discussion | Ericsson | imported from 3GU |
S3‑172329 | Clause 8.3.1.3.2 (key derivation during handover, Xn) - pCR | Ericsson | imported from 3GU |
S3‑172330 | Clause 8.3.1.3.3 (key derivation during handover, N2) - pCR | Ericsson | imported from 3GU |
S3‑172331 | Clause 8.3.1.3.4 (key derivation during handover, UE handling) | Ericsson | imported from 3GU |
S3‑172332 | Clause 8.3.1.4.1 (key change on fly, general) | Ericsson | imported from 3GU |
S3‑172333 | Clause 8.3.1.4.2 (key change on fly, AS key re-keying) | Ericsson | imported from 3GU |
S3‑172334 | Clause 8.3.1.4.3 (key change on fly, AS key refresh) | Ericsson | imported from 3GU |
S3‑172335 | Clause 8.3.1.4.4 (key change on fly, NAS key re-keying) | Ericsson | imported from 3GU |
S3‑172336 | Clause 8 (open issues in AS security) - Disc | Ericsson | imported from 3GU |
S3‑172337 | Clause 8.1.2.1.1 (AS algo. initial context) for RRC | Ericsson | imported from 3GU |
S3‑172338 | Clause 8.1.2.2 (AS security mode command procedure) for RRC | Ericsson | imported from 3GU |
S3‑172339 | Clause 8 (user plane security - integrity protection) | Ericsson | imported from 3GU |
S3‑172340 | Clause 8 (user plane security - confidentiality) | Ericsson | imported from 3GU |
S3‑172341 | Clause 8 (relation between RRC and user plane security algorithms) | Ericsson | imported from 3GU |
S3‑172342 | Clause 8 (conflict between RAN and CN) | Ericsson | imported from 3GU |
S3‑172343 | UE-assisted network-based detection of false base station - disc | Ericsson | imported from 3GU |
S3‑172344 | UE-assisted network-based detection of false base station - pCR | Ericsson | imported from 3GU |
S3‑172345 | Clauses 6.1.3 and 6.7.2 (auth procedures and NAS SMC, SUPI from UE for LI) | Ericsson, Telecom Italia | imported from 3GU |
S3‑172346 | Clauses 6.8.3 (5G-GUTI refresh at periodic registration update) | Ericsson, Telecom Italia | imported from 3GU |
S3‑172347 | Clauses 6.8.3 (5G-GUTI refresh at network triggered service request) | Ericsson, Telecom Italia | imported from 3GU |
S3‑172348 | Selection of SUCI null-scheme | Ericsson | imported from 3GU |
S3‑172349 | (Resubmission) Discussion for drafting reply to S2-175309, relates NSSAI privacy | Ericsson | imported from 3GU |
S3‑172350 | (Resubmission) draft Reply LS on Reply LS on 5GS Security aspects seeking resolution | Ericsson | imported from 3GU |
S3‑172351 | (Resubmission) Annex X.3 (SUCI, ECIES scheme normative Annex) | Ericsson | imported from 3GU |
S3‑172352 | Privacy requirements on the UE | Nokia | imported from 3GU |
S3‑172353 | Requirement on AMF | Nokia | imported from 3GU |
S3‑172354 | Merging and enhancing 6.8.1 and 6.8.2 | Nokia | imported from 3GU |
S3‑172355 | SIDF purpose in initiation of authentication | Nokia | imported from 3GU |
S3‑172356 | SIDF functionality | Nokia | imported from 3GU |
S3‑172357 | Null scheme clarifications - resolving ed.note | Nokia | imported from 3GU |
S3‑172358 | UDM requirements - key management and privacy | Nokia | imported from 3GU |
S3‑172359 | LI conformity when privacy is used | Nokia | imported from 3GU |
S3‑172360 | was S3-171950 TS - NSSAI privacy | Nokia | imported from 3GU |
S3‑172361 | was S3-171949 Discussion of NSSAI privacy | Nokia | imported from 3GU |
S3‑172362 | Cleaning up sections 6.8.1 and 6.8.2 about Subscription (Concealed) Identifier | KPN N.V. | imported from 3GU |
S3‑172363 | Procedure for Visited Network to request SUPI attach | KPN N.V. | imported from 3GU |
S3‑172364 | Annex C: Adding Creation of the 'visited network requests null-scheme message' | KPN N.V. | imported from 3GU |
S3‑172365 | Comments on S3-172225 | KPN N.V. | imported from 3GU |
S3‑172366 | Dealing with the text that moves from TS 33.401 to TS 33.501 in EDCE5 | Qualcomm Incorporated | imported from 3GU |
S3‑172367 | Completing the specification of the algorithms to use between UE and SgNB in EDCE5 | Qualcomm Incorporated | imported from 3GU |
S3‑172368 | Providing full details of the integrity and ciphering algorithms for TS 33.501 | Qualcomm Incorporated | imported from 3GU |
S3‑172369 | Aligning the specification of the key derivation function for key to use in security algorithms between UE and SgNB in EDCE5 with the 5G specification | Qualcomm Incorporated | imported from 3GU |
S3‑172370 | Providing details of the key derivation for the security algorithm keys | Qualcomm Incorporated | imported from 3GU |
S3‑172371 | Assigning an FC value for EDCE5 key derivations | Qualcomm Incorporated | imported from 3GU |
S3‑172372 | Discussion of possible methods and proposed solution for negotiating the algorithms for use between a UE and SgNB in EDCE5 | Qualcomm Incorporated | imported from 3GU |
S3‑172373 | Using AS layer signalling to negotiate the algorithm used between the UE and SgNB | Qualcomm Incorporated | imported from 3GU |
S3‑172374 | Using NAS layer signalling to negotiate the algorithm used between the UE and SgNB | Qualcomm Incorporated | imported from 3GU |
S3‑172375 | Clarifying the security algorithms that are used between the UE and MeNB and the UE and SgNB | Qualcomm Incorporated | imported from 3GU |
S3‑172376 | Adding a reference to RAN procedures on EDCE5 | Qualcomm Incorporated | imported from 3GU |
S3‑172377 | Clarifying the behaviour of UE to SgNB connection at a MeNB handover | Qualcomm Incorporated | imported from 3GU |
S3‑172378 | Specifying the usage of EMSK as the key used to derive the 5G keys when using EAP as an authentication method | Qualcomm Incorporated | imported from 3GU |
S3‑172379 | Discussion on sending S-NSSAIs to the network unprotected | Qualcomm Incorporated | imported from 3GU |
S3‑172380 | Identifying a problem with secondary authentication | Qualcomm Incorporated | imported from 3GU |
S3‑172381 | Proposed re-wording to the bidding down requirement | Qualcomm Incorporated | imported from 3GU |
S3‑172382 | Specifying the key derivation when using 5G AKA | Qualcomm Incorporated | imported from 3GU |
S3‑172383 | Aligning the protection of initial NAS messages and the NAS Security Mode procedure subclauses | Qualcomm Incorporated | imported from 3GU |
S3‑172384 | Discussion on bidding down of security features | Qualcomm Incorporated | imported from 3GU |
S3‑172385 | Security handling for interworking between NextGen Core and EPC | Qualcomm Incorporated | imported from 3GU |
S3‑172386 | pCR to provide a solution for interworking between NextGen Core and EPC | Qualcomm Incorporated | imported from 3GU |
S3‑172387 | pCR to provide a normative text for the AMF key derivation/refresh | Qualcomm Incorporated | imported from 3GU |
S3‑172388 | pCR to provide a normative text for AS key derivation | Qualcomm Incorporated | imported from 3GU |
S3‑172389 | pCR to provide a normative text for AS key hierarchy | Qualcomm Incorporated | imported from 3GU |
S3‑172390 | pCR: Security for Non-3GPP access to 5GC | Qualcomm Incorporated | imported from 3GU |
S3‑172391 | Discussion on Security for Non-3GPP access to 5GC | Qualcomm Incorporated | imported from 3GU |
S3‑172392 | pCR: Calculation of SUCI | Qualcomm Incorporated | imported from 3GU |
S3‑172393 | Discussion on the signalling and negotiation of the NR security capabilities | Ericsson | imported from 3GU |
S3‑172394 | UE supported NR security algorithms indicated in NAS protocol | Ericsson | imported from 3GU |
S3‑172395 | Registration state transitions in TS 33.501 | Ericsson | imported from 3GU |
S3‑172396 | Introducing clause for Secrity Aspects of Service Based Architecture | Ericsson | imported from 3GU |
S3‑172397 | Authentication and Authorization – requirements and more | Nokia | imported from 3GU |
S3‑172398 | Re-authentication in Solution 1.49 | Ericsson | imported from 3GU |
S3‑172399 | Visibility and configurability supporting serving network authorization | Nokia | imported from 3GU |
S3‑172400 | Exception lists of NAS and RRC message to be integrity protected and encrypted | Ericsson | imported from 3GU |
S3‑172401 | Preventing bidding down between 5G releases - discussion | Nokia | imported from 3GU |
S3‑172402 | EAP framework | Ericsson, Nokia, Samsung, Qualcomm Incorporated, Intel, Huawei | imported from 3GU |
S3‑172403 | Preventing bidding down between 5G releases - pCR | Nokia | imported from 3GU |
S3‑172404 | Discussion on the security for interworking between EPC and 5GC | Ericsson | imported from 3GU |
S3‑172405 | Key hierarchy | Nokia | imported from 3GU |
S3‑172406 | New requirements for algorithm selection in TS 33.501 | Ericsson | imported from 3GU |
S3‑172407 | Proposal for a new subclause 9.X on mapping of security contexts during interworking between 4G and 5G | Ericsson | imported from 3GU |
S3‑172408 | Handling security contexts within the serving network | Nokia | imported from 3GU |
S3‑172409 | Proposal for a new subclause 9.Y on interworking security in idle mode | Ericsson | imported from 3GU |
S3‑172410 | Distribution of security contexts | Nokia | imported from 3GU |
S3‑172411 | Clause 6.3.2 (Handling security contexts within the serving network) | Ericsson | imported from 3GU |
S3‑172412 | Security handling in state transitions | Nokia | imported from 3GU |
S3‑172413 | New UE requirement to store two 5G security contexts in TS 33.501 | Ericsson | imported from 3GU |
S3‑172414 | Security handling in mobility | Nokia | imported from 3GU |
S3‑172415 | CR to resolve EDCE5 ENs | Nokia | imported from 3GU |
S3‑172416 | Computation of key left at the AUSF for 5G AKA | Nokia | imported from 3GU |
S3‑172417 | Clause 5.2.9 CU-DU interface requirements | Nokia | imported from 3GU |
S3‑172418 | Key Management of end-to-end encryption for mission critical communications between LMR users and 3GPP users | Sepura PLC | imported from 3GU |
S3‑172419 | Clause 8.4 UP security mechanisms | Nokia | imported from 3GU |
S3‑172420 | Clause 6.6.3 NAS integrity | Nokia | imported from 3GU |
S3‑172421 | Clause 6.6.5 Handling of NAS counts | Nokia | imported from 3GU |
S3‑172422 | Skeleton for Security for IMS Emergency session | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172423 | Clause 6.7.1.2 AMF change | Nokia | imported from 3GU |
S3‑172424 | Security for Authenticated IMS Emergency sessions | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172425 | Clause 6.7.2 NAS SMC procedure | Nokia | imported from 3GU |
S3‑172426 | Security for unauthenticated IMS Emergency sessions | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172427 | Annex A key derivation function | Nokia | imported from 3GU |
S3‑172428 | Editorial updates in TS 33.501 | NEC EUROPE LTD | imported from 3GU |
S3‑172429 | Idle mode mobility from 4G to 5G | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172430 | Connection state transitions in TS 33.501 | Ericsson | imported from 3GU |
S3‑172431 | 5G Key Hierarchy | NEC EUROPE LTD | imported from 3GU |
S3‑172432 | Security for Idle mode mobility from 5G to 4G | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172433 | Key Hierarchy to support multiple NAS security | NEC EUROPE LTD | imported from 3GU |
S3‑172434 | Security for Handover from 4G to 5G | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172435 | [eMCSEC] Update to KMS Discovery Solution in TR 33.880 | NCSC | imported from 3GU |
S3‑172436 | 5G Key Derivation and distribution scheme | NEC EUROPE LTD | imported from 3GU |
S3‑172437 | Clause 6.2 (key hierarchy from K to KSEAF) | Ericsson | imported from 3GU |
S3‑172438 | Security for Handover from 5G to 4G | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172439 | Discussion on skeleton for clause 6.5 and related contents in clauses 6 and 8 | NEC EUROPE LTD, Lenovo, Motorola Mobility, Samsung, AT&T, KPN | imported from 3GU |
S3‑172440 | Clause 6.2 (key hierarchy, from KSEAF downwards) | Ericsson, Huawei | imported from 3GU |
S3‑172441 | [eMCSEC] KMS Discovery Use cases for TR 33.880 | NCSC | imported from 3GU |
S3‑172442 | [eMCSEC] Evaluation of KMS Discovery in TR 33.880 | NCSC | imported from 3GU |
S3‑172443 | [eMCSEC] Adding KMS Redirect Responses to TS 33.180 | NCSC | imported from 3GU |
S3‑172444 | [eMCSEC] KMS enhancement, including Migration KMS, for TS 33.180 | NCSC | imported from 3GU |
S3‑172445 | [eMCSEC] KMS Lookup (DNSSec) solution for TR 33.880 | NCSC | imported from 3GU |
S3‑172446 | [eMCSEC] Key Issues on Interworking and Interconnetion security for TR 33.880 | NCSC | imported from 3GU |
S3‑172447 | [eMCSEC] Five solutions on Interworking security for TR 33.880 | NCSC | imported from 3GU |
S3‑172448 | [eMCSEC] Addition of Clause on Logging, Audit and Discreet Monitoring for TS 33.180 | NCSC | imported from 3GU |
S3‑172449 | [eMCSEC] Update of Signalling Proxies solution (#1.5) for TR 33.880 | NCSC | imported from 3GU |
S3‑172450 | [eMCSEC] Evaluation of Signalling Proxies for TR 33.880 | NCSC | imported from 3GU |
S3‑172451 | [eMCSEC] Addition of signalling Proxies to TS 33.180 | NCSC | imported from 3GU |
S3‑172452 | [MCSEC] Clarification on SSRC use in group communications in TS 33.180 Rel-14 | NCSC | imported from 3GU |
S3‑172453 | [eMCSEC] Clarification on SSRC use in group communications in TS 33.180 Rel-15 | NCSC | imported from 3GU |
S3‑172454 | [eMCSEC] Update to EAR solution in TR 33.880 | NCSC | imported from 3GU |
S3‑172455 | [eMCSEC] LS to SA6 on configuration parameters | NCSC | imported from 3GU |
S3‑172456 | Skeleton for clause 6.5 Security handling in mobility | NEC EUROPE LTD, Lenovo, Motorola Mobility, Samsung, AT&T, KPN | imported from 3GU |
S3‑172457 | Secondary authentication - Clause 12.1.2 - Resolve EN on use of Normative language | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172458 | Computation of key left at the AUSF for EAP-AKA’ | Nokia | imported from 3GU |
S3‑172459 | Update to clause 6.5 Security handling in mobility | NEC EUROPE LTD, Lenovo, Motorola Mobility, Samsung, AT&T, KPN | imported from 3GU |
S3‑172460 | Secondary Authentication - Resolve Editor’s Notes | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172461 | Update to clause 8.3 Security handling in mobility | NEC EUROPE LTD, Lenovo, Motorola Mobility, Samsung, AT&T, KPN | imported from 3GU |
S3‑172462 | Discussion on 5G UE Security Capabilities with KDF identifiers | NEC EUROPE LTD | imported from 3GU |
S3‑172463 | Secondary Authentication - Update text with corresponding service operations used to carry EAP messages | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172464 | Derivation of anchor key for EAP-AKA’ | Nokia | imported from 3GU |
S3‑172465 | Discussion on necessity and way forward of security study for 5G core network with SBA | China Mobile Com. Corporation | imported from 3GU |
S3‑172466 | 5G UE Security Capabilities with KDF identifiers | NEC EUROPE LTD | imported from 3GU |
S3‑172467 | New WID for enhanced security function to 5GC Service Based Architecture | China Mobile Com. Corporation | imported from 3GU |
S3‑172468 | Skeleton for clause 11 | NEC EUROPE LTD | imported from 3GU |
S3‑172469 | Interworking - Discussion paper on security context | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172470 | Discussion and pCR on authorization issue for 5G core network with SBA | China Mobile Com. Corporation | imported from 3GU |
S3‑172471 | Security aspects of Non-3GPP access using 5G Core Network | NEC EUROPE LTD | imported from 3GU |
S3‑172472 | 5G AKA to be used over all access network types – clause 6 | Nokia | imported from 3GU |
S3‑172473 | SUCI calculation | Gemalto, G&D, Morpho & Oberthur (IDEMIA) | imported from 3GU |
S3‑172474 | 5G AKA to be used over all access network types – clause 11 | Nokia | imported from 3GU |
S3‑172475 | Conveying authentication result from AUSF to UDM | Nokia | imported from 3GU |
S3‑172476 | Clarification of requirements on e2e core interconnection network security | Nokia | imported from 3GU |
S3‑172477 | Interworking - Discussion paper on issues when Interworking with a legacy MME | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172478 | 5G AKA Discussion of Option 1 and Option 2 | Huawei, HiSilicon | imported from 3GU |
S3‑172479 | Skeleton for interconnection network security | Nokia | imported from 3GU |
S3‑172480 | AKA Procedure in Interworking and Migration Scenarios | Huawei, HiSilicon | imported from 3GU |
S3‑172481 | Security for multiple NAS connections with single anchor key | Ericsson | imported from 3GU |
S3‑172482 | Discussion on protection of Network Steering Information | Ericsson | imported from 3GU |
S3‑172483 | Details of EAP-5G Solution for registration via untrusted non-3GPP access | Motorola Mobility, Lenovo, Broadcom, Brocade, Rogers Wireless, Samsung, ITRI, CATT, Cisco | imported from 3GU |
S3‑172484 | Editorials against 33.501 | NTT DOCOMO | imported from 3GU |
S3‑172485 | pCR to 33.501 6.1.3.2 – Mandate sending of AC | NTT DOCOMO | imported from 3GU |
S3‑172486 | pCR to 33.501 5.4.1 - Clarification of security indication | NTT DOCOMO, Department of Commerce | imported from 3GU |
S3‑172487 | pCR to 33.501 6.1.2, 6.1.3.2 – only one authentication vector at a time | NTT DOCOMO | imported from 3GU |
S3‑172488 | pCR to 33.501 6.1.3.1, 6.1.3.2 – SUPI assurance in SEAF | NTT DOCOMO | imported from 3GU |
S3‑172489 | pCR to 33.501 6.1.3.2 – Mandate signalling of expiry time of | NTT DOCOMO | imported from 3GU |
S3‑172490 | Drawbacks of the NAS-over-IKE solution | Motorola Mobility, Lenovo, Broadcom, Brocade, Rogers Wireless, Samsung, ITRI, CATT, Cisco | imported from 3GU |
S3‑172491 | Multiple registrations | Ericsson | imported from 3GU |
S3‑172492 | Interworking - Discussion paper on integrity protection of idle mobility MM message during interworking | Nokia Solutions & Networks (I) | imported from 3GU |
S3‑172493 | NSSAI Privacy Discussion | LG Electronics | imported from 3GU |
S3‑172494 | NSSAI Privacy handling | LG Electronics | imported from 3GU |
S3‑172495 | Security Visibility clarification | LG Electronics | imported from 3GU |
S3‑172496 | Clarification on network slice access authentication and authorization | LG Electronics | imported from 3GU |
S3‑172497 | SUCI calculation | Gemalto, G&D, Morpho & Oberthur (IDEMIA), Vodafone | imported from 3GU |
S3‑172498 | New SID on 256-bit algorithms for 5G | VODAFONE Group Plc | imported from 3GU |
S3‑172499 | Response to LS from SA3 to TC Cyber regarding 256-bit key lengths | ETSI TC CYBER | imported from 3GU |
S3‑172500 | Integrity for UP, RRC and NAS | Huawei; Hisilicon | imported from 3GU |
S3‑172501 | Confidentiality for UP, RRC and NAS | Huawei; Hisilicon | imported from 3GU |
S3‑172502 | Replay protection for UP, RRC and NAS | Huawei; Hisilicon | imported from 3GU |
S3‑172503 | pCR: Calculation of SUCI | Qualcomm Incorporated | imported from 3GU |
S3‑172504 | Security key handling during Xn handover | Intel | imported from 3GU |
S3‑172505 | First response on ECIES for concealing IMSI or SUPI | ETSI SAGE | imported from 3GU |
S3‑172506 | LI conformity when privacy is used | Nokia | imported from 3GU |
S3‑172507 | Comments to "New SID on 256-bit algorithms for 5G" | Ericsson | imported from 3GU |
S3‑172508 | New SID on 256-bit algorithms for 5G – with Nokia comments | Nokia | imported from 3GU |
S3‑172509 | Privacy requirements on the UE | Nokia | imported from 3GU |
S3‑172510 | Drawbacks of the NAS-over-IKE solution | Motorola Mobility, Lenovo, Broadcom, Brocade, Rogers Wireless, Samsung, ITRI, CATT, Cisco | imported from 3GU |
S3‑172511 | Details of EAP-5G Solution for registration via untrusted non-3GPP access | Motorola Mobility, Lenovo, Broadcom, Brocade, Rogers Wireless, Samsung, ITRI, CATT, Cisco | imported from 3GU |
S3‑172512 | Work status of EDCE5 post SA3#88Bis | Qualcomm | imported from 3GU |
S3‑172513 | Assigning an FC value for EDCE5 key derivations | Qualcomm Incorporated | imported from 3GU |
S3‑172514 | Editorial corrections for Annex E | Huawei; Hisilicon | imported from 3GU |
S3‑172515 | Reply to: LS to SA3 on RAN2 agreements on jumbo frames | Ericsson | imported from 3GU |
S3‑172516 | Reply to: LS on PLMN and RAT selection policies for roaming | Huawei | imported from 3GU |
S3‑172517 | Reply to: Reply LS on 5GS Security aspects seeking resolution | Qualcomm | imported from 3GU |
S3‑172518 | pCR on editorial correction of TS 33.501 | NEC EUROPE LTD | imported from 3GU |
S3‑172519 | Corrections on 33501 | Huawei; Hisilicon | imported from 3GU |
S3‑172520 | Editorials against 33.501 | NTT DOCOMO | imported from 3GU |
S3‑172521 | PCR to 33.501 – typos and language in multiple clauses. | InterDigital, Inc. | imported from 3GU |
S3‑172522 | Draft TS 33.501 | NTT-Docomo | imported from 3GU |
S3‑172523 | Providing full details of the integrity and ciphering algorithms for TS 33.501 | Qualcomm Incorporated | imported from 3GU |
S3‑172524 | Security for Authenticated IMS Emergency sessions | Nokia | imported from 3GU |
S3‑172525 | Security for unauthenticated IMS Emergency sessions | Nokia | imported from 3GU |
S3‑172526 | [eMCSEC] Update to KMS Discovery Solution in TR 33.880 | NCSC | imported from 3GU |
S3‑172527 | [eMCSEC] KMS Discovery Use cases for TR 33.880 | NCSC | imported from 3GU |
S3‑172528 | [eMCSEC] Adding KMS Redirect Responses to TS 33.180 | NCSC | imported from 3GU |
S3‑172529 | [eMCSEC] Five solutions on Interworking security for TR 33.880 | NCSC | imported from 3GU |
S3‑172530 | SUCI calculation | Gemalto, G&D, Morpho & Oberthur (IDEMIA), Vodafone | imported from 3GU |
S3‑172531 | Revised WID 5G security phase one | China Mobile | imported from 3GU |
S3‑172532 | Corrections to MCData security procedures | SAMSUNG | imported from 3GU |
S3‑172533 | Security Considerations for Service Based Architecture in 5G | Deutsche Telekom AG | imported from 3GU |
S3‑172534 | Skeleton for interconnection network security | Nokia | imported from 3GU |
S3‑172535 | [eMCSEC] KMS enhancement, including Migration KMS, for TS 33.180 | NCSC | imported from 3GU |
S3‑172536 | Clarification of requirements on e2e core interconnection network security | Nokia | imported from 3GU |
S3‑172537 | [eMCSEC] Addition of Clause on Logging, Audit and Discreet Monitoring for TS 33.180 | NCSC | imported from 3GU |
S3‑172538 | Discussion and pCR on authorization issue for 5G core network with SBA | China Mobile Com. Corporation | imported from 3GU |
S3‑172539 | Authorization of NF service access | Huawei, Hisilicon | imported from 3GU |
S3‑172540 | Living document on SBA | China Mobile | imported from 3GU |
S3‑172541 | [MCSEC] Clarification on SSRC use in group communications in TS 33.180 Rel-14 | NCSC | imported from 3GU |
S3‑172542 | Draft TR 33.880 | NCSC | imported from 3GU |
S3‑172543 | LS to SA6 on the use of signalling proxies as a deployment option | NCSC | imported from 3GU |
S3‑172544 | [eMCSEC] Addition of signalling Proxies to TS 33.180 | NCSC | imported from 3GU |
S3‑172545 | LS to SA6 on end to end encryption for mission critical communications between LMR users and 3GPP users. | NCSC | imported from 3GU |
S3‑172546 | LS on N3GPP access | Ericsson | imported from 3GU |
S3‑172547 | Key hierarchy | Nokia, Ericsson, Huawei,NEC | imported from 3GU |
S3‑172548 | draft TR 33.811 | Huawei | imported from 3GU |
S3‑172549 | A proposal for the scope of the TR33.811 | Huawei, Hisilicon | imported from 3GU |
S3‑172550 | A key issue of interface security for TR33.811 | Huawei, Hisilicon, CATR | imported from 3GU |
S3‑172551 | A key issue on security capabilities for TR33.811 | Huawei, Hisilicon | imported from 3GU |
S3‑172552 | EAP Framework | Huawei & Hisilicon | imported from 3GU |
S3‑172553 | LS on support of jumbo frames using EIA3 | Vodafone | imported from 3GU |
S3‑172554 | Security for multiple NAS connections with single anchor key | Ericsson | imported from 3GU |
S3‑172555 | Multiple registrations | Ericsson | imported from 3GU |
S3‑172556 | New SID on 256-bit algorithms for 5G | Nokia | imported from 3GU |
S3‑172557 | Annex A key derivation function | Nokia | imported from 3GU |
S3‑172558 | Skeleton for clause 6.5 Security handling in mobility | NEC EUROPE LTD, Lenovo, Motorola Mobility, Samsung, AT&T, KPN | imported from 3GU |
S3‑172559 | Security handling in mobility | Nokia | imported from 3GU |
S3‑172560 | pCR to TS33.501 clause 5.4.2 taken from S3-172484 | NTT-Docomo | imported from 3GU |
S3‑172561 | Clause 8.3.1.1.2 (key handling in handover, general, non access stratum) | Ericsson | imported from 3GU |
S3‑172562 | Clause 8.3.1.2 (key derivation for context modification procedure) | Ericsson | imported from 3GU |
S3‑172563 | Clause 8.3.1.3.1 (key derivation during handover, intra-gNB) | Ericsson | imported from 3GU |
S3‑172564 | pCR to TS 33.501: reusing {NCC, NH} to key derivation for handover | Huawei; Hisilicon | imported from 3GU |
S3‑172565 | LS on handling concurrent running of security procedures | Ericsson | imported from 3GU |
S3‑172566 | Clause 8.3.1.3.2 (key derivation during handover, Xn) - pCR | Ericsson,NEC | imported from 3GU |
S3‑172567 | Clause 8.3.1.3.3 (key derivation during handover, N2) - pCR | Ericsson,NEC | imported from 3GU |
S3‑172568 | Clause 8.3.1.4.2 (key change on fly, AS key re-keying) | Ericsson | imported from 3GU |
S3‑172569 | Rewriting Clause 6.1.2 and 6.1.3 in normative language and adding Annex A | KPN N.V. | imported from 3GU |
S3‑172570 | Changes to Initiation of Authentication and subscription identity procedure. | Intel | imported from 3GU |
S3‑172571 | Moving Serving Network Name construction into it's own clause | KPN N.V. | imported from 3GU |
S3‑172572 | Authentication and Authorization – requirements and more | Nokia | imported from 3GU |
S3‑172573 | Conveying authentication result from AUSF to UDM | Nokia | imported from 3GU |
S3‑172574 | pCR to 33.501 6.1.3.2 – Mandate signalling of expiry time of | NTT DOCOMO | imported from 3GU |
S3‑172575 | CR to resolve EDCE5 ENs | Nokia | imported from 3GU |
S3‑172576 | Aligning the specification of the key derivation function for key to use in security algorithms between UE and SgNB in EDCE5 with the 5G specification | Qualcomm Incorporated | imported from 3GU |
S3‑172577 | Specifying the usage of EMSK as the key used to derive the 5G keys when using EAP as an authentication method | Qualcomm Incorporated | imported from 3GU |
S3‑172578 | Providing details on the authentication vector and calculation of keys | Huawei & Hisilicon | imported from 3GU |
S3‑172579 | EAP framework | Ericsson, Nokia, Samsung, Qualcomm Incorporated, Intel, Huawei | imported from 3GU |
S3‑172580 | Key open issues | WG Chair | imported from 3GU |
S3‑172581 | Reply to: LS on PLMN and RAT selection policies for roaming | Huawei | imported from 3GU |
page generated from database: 2024-09-26 11:02:35