3GPP TDocs (written contributions) at meeting
Meeting: S3-104-e - 2021-08-16 to 2021-08-27, Online
meeting id: S3-104-e (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S3‑212400 | Agenda | SA WG3 Chair | imported from 3GU |
S3‑212401 | Report from SA3#103e | MCC | imported from 3GU |
S3‑212402 | Process for SA3#104e meeting | SA WG3 Chair | imported from 3GU |
S3‑212403 | Report from last SA | SA WG3 Chair | imported from 3GU |
S3‑212404 | Meeting notes from SA3 leadership | SA WG3 Chair | imported from 3GU |
S3‑212405 | Observations on TR 33.846 | JSRPC Kryptonite | imported from 3GU |
S3‑212406 | New solution proposal | JSRPC Kryptonite | imported from 3GU |
S3‑212407 | Observations on TR 33.846 | JSRPC Kryptonite | imported from 3GU |
S3‑212408 | New solution proposal | JSRPC Kryptonite | imported from 3GU |
S3‑212409 | LS on OAuth2 misalignments between SA3 and CT4 specifications | CP-211326 | imported from 3GU |
S3‑212410 | Misalignment on usage of OAuth within 3GPP 29.510 | GSMA | imported from 3GU |
S3‑212411 | LS on UE capabilities indication in UPU | S2-2101072 | imported from 3GU |
S3‑212412 | Reply LS on UE capabilities indication in UPU | C1-212599 | imported from 3GU |
S3‑212413 | LS reply on SDP attribute a=key-mgmt:mikey | C1-213548 | imported from 3GU |
S3‑212414 | LS on support of PWS over SNPN | S1-210368 | imported from 3GU |
S3‑212415 | Reply LS on support of PWS over SNPN | C1-213640 | imported from 3GU |
S3‑212416 | Reply LS on support of PWS over SNPN in R17 | R3-212863 | imported from 3GU |
S3‑212417 | Reply LS on support of PWS over NPN | SP-210584 | imported from 3GU |
S3‑212418 | Reply LS on end-to-end protection of HTTP message for Indirect communication | C4-213369 | imported from 3GU |
S3‑212419 | Reply to LS on Resynchronisations | ETSI SAGE | imported from 3GU |
S3‑212420 | Prevention of attacks on sliced core network | GSMA | imported from 3GU |
S3‑212421 | Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM | GSMA | imported from 3GU |
S3‑212422 | Reply LS on Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM | S2-214895 | imported from 3GU |
S3‑212423 | Reply LS to GSMA-ACJA: 3GPP SA1 clarifications on problematic UAV | S2-214916 | imported from 3GU |
S3‑212424 | LS on Layer-3 UE-to-Network Relay authentication and authorization | S2-2101623 | imported from 3GU |
S3‑212425 | 256-bit algorithms based on SNOW 3G or SNOW V | ETSI SAGE | imported from 3GU |
S3‑212426 | LS re Penetration Testing of SCAS | GSMA | imported from 3GU |
S3‑212427 | LS on security aspects for the method of collection of data from the UE | S2-213263 | imported from 3GU |
S3‑212428 | LS to SA3 on Small data transmissions | R2-2104401 | imported from 3GU |
S3‑212429 | LS for clarification on managing expired or multiple Protection Scheme and Home Network keys used for SUCI calculation. | C6-210180 | imported from 3GU |
S3‑212430 | LS on new work item on draft Recommendation ITU-T F.VG-VMA "Architecture of vehicular multimedia systems" [to various organizations] | ITU-T Focus Group on Vehicular Multimedia (FG-VM) | imported from 3GU |
S3‑212431 | LS on broadcast of NTN GW or gNB position | R1-2106332 | imported from 3GU |
S3‑212432 | New LS on UE location aspects in NTN | R2-2106543 | imported from 3GU |
S3‑212433 | Reply LS on UE location aspects in NTN | R3-212917 | imported from 3GU |
S3‑212434 | LS to SA3 on SLIC | R2-2106516 | imported from 3GU |
S3‑212435 | S on QoE report handling at QoE pause | R2-2106775 | imported from 3GU |
S3‑212436 | Reply LS to LS on User Plane Integrity Protection for eUTRA connected to EPC | R3-212812 | imported from 3GU |
S3‑212437 | Reply LS on NAS-based busy indication | R3-212877 | imported from 3GU |
S3‑212438 | Reply LS on NAS-based busy indication | S2-2105150 | imported from 3GU |
S3‑212439 | LS on 5G capabilities exposure for factories of the future | S2-2104794 | imported from 3GU |
S3‑212440 | LS on 5G capabilities exposure for factories of the future | S6-211497 | imported from 3GU |
S3‑212441 | Reply LS to SA4 on UE Data Collection | S2-2104864 | imported from 3GU |
S3‑212442 | Reply LS to SA2 on UE Data Collection | S4-210961 | imported from 3GU |
S3‑212443 | LS on progress of study items for security on management aspect | S5-213456 | imported from 3GU |
S3‑212444 | LS on new SID on Application Enablement for Data Integrity Verification Service in IOT | S6-211496 | imported from 3GU |
S3‑212445 | LS on ITU-T SG17 new work item X.5Gsec-message: Security requirements for 5G message service | ITU-T SG17 | imported from 3GU |
S3‑212446 | LS on ITU-T SG17 new work item X.sa-ec ‘Security architecture for edge cloud’ | ITU-T SG17 | imported from 3GU |
S3‑212447 | LS on UAS terminology alignment | SP-210579 | imported from 3GU |
S3‑212448 | Reply LS on the conclusion of FS_MINT-CT | SP-210581 | imported from 3GU |
S3‑212449 | Attack preventing NAS procedures to succeed | GSMA | imported from 3GU |
S3‑212450 | OAuth2.0 misalignmnet | Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung | imported from 3GU |
S3‑212451 | OAuth2.0 misalignmnet | Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung | imported from 3GU |
S3‑212452 | Stealth Pirating Attack by RACH Rebroadcast Overwriting (SPARROW) | GSMA | imported from 3GU |
S3‑212453 | Evaluation of Solution #22: Representation of identities during broadcast | KPN N.V. | imported from 3GU |
S3‑212454 | Correction of message name in SMF | Keysight Technologies UK Ltd | imported from 3GU |
S3‑212455 | AMF – NAS NULL integrity protection clarifications (Rel-16) | Keysight Technologies UK Ltd | imported from 3GU |
S3‑212456 | AMF – NAS NULL integrity protection clarifications (Rel-17) | Keysight Technologies UK Ltd | imported from 3GU |
S3‑212457 | Conclusion on Key Issue #11: UE identity protection during ProSe discover | KPN N.V. | imported from 3GU |
S3‑212458 | Living document for BEST_5G: draftCR to TS 33.163 | KPN N.V. | imported from 3GU |
S3‑212459 | Correction of message name in SMF | Keysight Technologies UK Ltd | imported from 3GU |
S3‑212460 | Process and agenda for SA3#104-e | SA WG3 Chair | imported from 3GU |
S3‑212461 | TCG progress - report from TCG rapporteur | InterDigital, Inc. | imported from 3GU |
S3‑212462 | New WID for Study of privacy of Over the Air identities | InterDigital, Inc., Apple, AT&T, CableLabs, Futurewei, Verizon Wireless | imported from 3GU |
S3‑212463 | Reply LS to GSMA on prevention of attacks on sliced core network | CableLabs | imported from 3GU |
S3‑212464 | New solution: Keying procedures for Group Member and Relay discovery: public safety case | MITRE Corporation | imported from 3GU |
S3‑212465 | Update to KI #17 | MITRE Corporation | imported from 3GU |
S3‑212466 | New solution: Hardware Mediated Execution Enclave (HMEE) | MITRE Corporation | imported from 3GU |
S3‑212467 | [33.180] R17 Group subscription | Motorola Solutions Danmark A/S | imported from 3GU |
S3‑212468 | [33.180] R17 Preconfigured group clarification | Motorola Solutions Danmark A/S | imported from 3GU |
S3‑212469 | Conclusion on Key Issue #12: Security of one-to-one communication over PC5 | KPN N.V. | imported from 3GU |
S3‑212470 | Clean-up for KI#1 | LG Electronics Inc. | imported from 3GU |
S3‑212471 | Updates on sol#10 | LG Electronics Inc. | imported from 3GU |
S3‑212472 | Evaluation for sol#13 | LG Electronics Inc. | imported from 3GU |
S3‑212473 | Editorial corrections for sol#10 | LG Electronics Inc. | imported from 3GU |
S3‑212474 | New solution for UE onboarding | LG Electronics Inc. | imported from 3GU |
S3‑212475 | New WID on Authentication enhancements in 5GS | Ericsson | imported from 3GU |
S3‑212476 | Authentication enhancements: Discussion about the WID | Ericsson | imported from 3GU |
S3‑212477 | Reply LS to SA6 on new SID on Application Enablement for Data Integrity Verification Service in IoT | China Unicom | imported from 3GU |
S3‑212478 | TR 33.847 Update for solution #10 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑212479 | TR 33.847 Update for solution #24 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑212480 | New Solution Using Attestation for Key Issue #13 | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | imported from 3GU |
S3‑212481 | TR 33.847 Update for solution #25 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑212482 | New Key Issue on Network Slice Quota DoS | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD, Verizon | imported from 3GU |
S3‑212483 | New Solution to Network Slice Quota DoS | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD, Verizon | imported from 3GU |
S3‑212484 | Way forward for L3 U2N Relay Authorization and security conclusions | InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212485 | Conclusions for U2N relay Key Issues | InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212486 | Conclusion for Key Issue #3 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑212487 | Conclusion for Key Issue #5 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑212488 | Conclusion for Key Issue #6 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑212489 | New WID on IETF OSCORE Ua* protocol profile for AKMA | Ericsson | imported from 3GU |
S3‑212490 | IETF OSCORE as AKMA Ua* protocol | Ericsson | imported from 3GU |
S3‑212491 | Extending the Ua security protocol namespace to include the AKMA OSCORE Ua* protocol | Ericsson | imported from 3GU |
S3‑212492 | Updates to solution #2 | Ericsson | imported from 3GU |
S3‑212493 | Updates to solution #9 | Ericsson | imported from 3GU |
S3‑212494 | Updates to terminology in the architecture assumptions | Ericsson | imported from 3GU |
S3‑212495 | Rel16 Clarification about multiple horizontal key derivations upon AMF re-allocation via direct NAS reroute | Ericsson | imported from 3GU |
S3‑212496 | Rel17 Clarification about multiple horizontal key derivations upon AMF re-allocation via direct NAS reroute | Ericsson | imported from 3GU |
S3‑212497 | New WID on the security of AMF re-allocation | Ericsson | imported from 3GU |
S3‑212498 | AMF re-allocation: Discussion about the WID | Ericsson | imported from 3GU |
S3‑212499 | Conclusion for the study | Ericsson | imported from 3GU |
S3‑212500 | Living document for GBA_5G: draftCR to TS 33.220: SBA support for Zh and Zn interfaces | Ericsson | imported from 3GU |
S3‑212501 | Living document for GBA_5G: draftCR to TS 33.223: SBA support for Zpn | Ericsson | imported from 3GU |
S3‑212502 | pCR to living document for TS 33.220: Support of GBA in UDM | Ericsson | imported from 3GU |
S3‑212503 | pCR to living document for TS 33.223: Support for GBA in UDM | Ericsson | imported from 3GU |
S3‑212504 | DRAFT LS on SBA for GBA | Ericsson | imported from 3GU |
S3‑212505 | pCR to living document for TS 33.220: Correction of references | Ericsson | imported from 3GU |
S3‑212506 | Rel16 Align KAUSF handling for 5G AKA and EAP-AKA' | Ericsson | imported from 3GU |
S3‑212507 | Rel17 Align KAUSF handling for 5G AKA and EAP-AKA' for Release 17 | Ericsson | imported from 3GU |
S3‑212508 | Addressing security threat against KAUSF derived from MSK | CableLabs | imported from 3GU |
S3‑212509 | Update to solution#4.7 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212510 | Conclusion to Key Issue #4.1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212511 | Conclusion on Key issue #3.2 SUPI guessing attacks | Nokia, Nokia Shanghai Bell, Thales, NTT DOCOMO, NEC | imported from 3GU |
S3‑212512 | Editor note removal and update for solution#10 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212513 | LS on proposed NSWO architecture | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212514 | Non-Seamless WLAN offload Authentication in 5GS | Nokia, Nokia Shanghai Bell, AT&T | imported from 3GU |
S3‑212515 | New WID on Non-Seamless WLAN offload Authentication in 5GS | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212516 | Updates on sol#13 | LG Electronics Inc. | imported from 3GU |
S3‑212517 | Concept of User Consent | China Unicom | imported from 3GU |
S3‑212518 | Update for Conclusion on Key Issue #4 | China Telecommunications, Huawei, HiSilicon | imported from 3GU |
S3‑212519 | Authorization of IPX by PLMN in indirect roaming | CableLabs | imported from 3GU |
S3‑212520 | pCR: updating annex B in TR 33.809 | CableLabs | imported from 3GU |
S3‑212521 | Further conclusions for KI #1 | CableLabs,Ericsson, Charter Communications, Intel | imported from 3GU |
S3‑212522 | Update for Conclusion on Key Issue #4 | China Telecommunications, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212523 | Short-lived public key-based solution for KI#2 | CableLabs,Deutsche Telekom AG, InterDigital, Johns Hopkins University APL, US National Security Agency | imported from 3GU |
S3‑212524 | Discussion on security of Small data transmissions | ZTE Corporation | imported from 3GU |
S3‑212525 | Reply LS on Small data transmissions | ZTE Corporation | imported from 3GU |
S3‑212526 | Living document for SCAS_5G_IPUPS draftCR to TR 33.926 | ZTE Corporation | imported from 3GU |
S3‑212527 | Living document for SCAS_5G_IPUPS draftCR to TS 33.513 | ZTE Corporation | imported from 3GU |
S3‑212528 | Add Routing indicator in Authentication response | ZTE Corporation | imported from 3GU |
S3‑212529 | Resolution of EN on other parameter in clause 6.3 | ZTE Corporation | imported from 3GU |
S3‑212530 | Resolve the Kaf update issue | ZTE Corporation | imported from 3GU |
S3‑212531 | UDM notifies AAnF AKMA context removal and performs AAnF selection | ZTE Corporation | imported from 3GU |
S3‑212532 | Update clause 6.1 about RID | ZTE Corporation | imported from 3GU |
S3‑212533 | Update clause 6.1 refer to Kausf stored in AUSF | ZTE Corporation | imported from 3GU |
S3‑212534 | Discussion on refresh of KAF and no Kakma in AAn | ZTE Corporation | imported from 3GU |
S3‑212535 | Add step 4 in annex B.1.2.2 | ZTE Corporation | imported from 3GU |
S3‑212536 | Add TLS1.3 to annex B.1.3 | ZTE Corporation | imported from 3GU |
S3‑212537 | Delete the GBA_Digest in annex B.1.2.2 | ZTE Corporation | imported from 3GU |
S3‑212538 | Correct the description of KAUSF handling upon successful primary authentication-R16 | ZTE Corporation | imported from 3GU |
S3‑212539 | Correct the description of KAUSF handling upon successful primary authentication-R17 | ZTE Corporation | imported from 3GU |
S3‑212540 | Add evaluation for solution 3.3 | ZTE Corporation | imported from 3GU |
S3‑212541 | Conclusion on key issue 3.2 | ZTE Corporation | imported from 3GU |
S3‑212542 | Conclusion on key issue 4.1 | ZTE Corporation | imported from 3GU |
S3‑212543 | Conclusion on key issue 1 | ZTE Corporation | imported from 3GU |
S3‑212544 | Conclusion on key issue 2 | ZTE Corporation | imported from 3GU |
S3‑212545 | Conclusion on key issue 7 | ZTE Corporation | imported from 3GU |
S3‑212546 | Conclusion of Key Issue #1 | ZTE Corporation | imported from 3GU |
S3‑212547 | Update to Solution #5 | ZTE Corporation | imported from 3GU |
S3‑212548 | Conclusion for UE to UE relay | ZTE Corporation | imported from 3GU |
S3‑212549 | Solution for key issue #17 | ZTE Corporation | imported from 3GU |
S3‑212550 | Update the key issue#2 | ZTE Corporation | imported from 3GU |
S3‑212551 | Update the solution#36 | ZTE Corporation | imported from 3GU |
S3‑212552 | Add the evaluation of the solution #6 | ZTE Corporation | imported from 3GU |
S3‑212553 | Conclusion for the key issue 1 | ZTE Corporation | imported from 3GU |
S3‑212554 | Conclusion for the key issue 2 | ZTE Corporation | imported from 3GU |
S3‑212555 | Update the solution #12 | ZTE Corporation | imported from 3GU |
S3‑212556 | Update the solution #6 | ZTE Corporation | imported from 3GU |
S3‑212557 | New solution on control plane based provisioning PS to AUSF | ZTE Corporation | imported from 3GU |
S3‑212558 | New solution on control plane based provisioning PS to UDM | ZTE Corporation | imported from 3GU |
S3‑212559 | Resolving ENs in Key Issue #2 | ZTE Corporation | imported from 3GU |
S3‑212560 | Conclusion for the key issue 1 | ZTE Corporation | imported from 3GU |
S3‑212561 | Resolve the EN about the GUTI collision in solution #11 | ZTE Corporation | imported from 3GU |
S3‑212562 | Update the solution #11 | ZTE Corporation | imported from 3GU |
S3‑212563 | Concept of User Consent | China Unicom, Huawei, HiSilicon | imported from 3GU |
S3‑212564 | Annex X on EAP_TTLS for SNPN | CableLabs, Ericsson, Charter Communications, Intel | imported from 3GU |
S3‑212565 | Storage of Kausf | NEC Corporation | imported from 3GU |
S3‑212566 | modification to the solution 6.2.10 | NEC Corporation | imported from 3GU |
S3‑212567 | conclusion to key issue 2.2 | NEC Corporation | imported from 3GU |
S3‑212568 | Update to solution #25 | Huawei, HiSilicon | imported from 3GU |
S3‑212569 | Evaluation of solution #4 | Huawei, HiSilicon | imported from 3GU |
S3‑212570 | Conclusion for KI#3 | Huawei, HiSilicon | imported from 3GU |
S3‑212571 | Serving network ID in NSSAA | Huawei, HiSilicon | imported from 3GU |
S3‑212572 | Validity peirod of NSSAA result | Huawei, HiSilicon | imported from 3GU |
S3‑212573 | Clarification on optional EAP ID Request in NSSAA Procedure | Huawei, HiSilicon | imported from 3GU |
S3‑212574 | Update to KI#1 (NSSAI analysis) | Huawei, HiSilicon | imported from 3GU |
S3‑212575 | New KI on DoS to NSAC procedure | Huawei, HiSilicon | imported from 3GU |
S3‑212576 | New KI on AF authentication and authorization | Huawei, HiSilicon | imported from 3GU |
S3‑212577 | New KI on simultaneous use of network slice | Huawei, HiSilicon | imported from 3GU |
S3‑212578 | Draft LS to GSMA on interfacing with USS/UTM | Huawei, HiSilicon | imported from 3GU |
S3‑212579 | Conclusion to KI#3 (TPAE AA) | Huawei, HiSilicon | imported from 3GU |
S3‑212580 | Conclusion to KI#5 (privacy of UAS identities) | Huawei, HiSilicon | imported from 3GU |
S3‑212581 | Conclusion to KI#6 (UAV to UTM) | Huawei, HiSilicon | imported from 3GU |
S3‑212582 | Overview on UAV authentication and authorization (UAA) | Huawei, HiSilicon | imported from 3GU |
S3‑212583 | UAA procedure at registration (5G) | Huawei, HiSilicon | imported from 3GU |
S3‑212584 | UAA procedure at PDU session establsihment (5G) | Huawei, HiSilicon | imported from 3GU |
S3‑212585 | UAA re-authentication procedure (5G) | Huawei, HiSilicon | imported from 3GU |
S3‑212586 | Revocation of UAA | Huawei, HiSilicon | imported from 3GU |
S3‑212587 | Pairing authorizaiton of UAS and UAV | Huawei, HiSilicon | imported from 3GU |
S3‑212588 | Solution on AF authorization | Huawei, HiSilicon | imported from 3GU |
S3‑212589 | Skeloton for clause UAA | Huawei, HiSilicon | imported from 3GU |
S3‑212590 | Solution to prevent information leakage between mutual exclusive slices | Huawei, HiSilicon | imported from 3GU |
S3‑212591 | Solution of NSAC based on slice usage | Huawei, HiSilicon | imported from 3GU |
S3‑212592 | Solution to decouple NSAC and NSSAA status | Huawei, HiSilicon | imported from 3GU |
S3‑212593 | Solution on restriction in EAC inactive modes | Huawei, HiSilicon | imported from 3GU |
S3‑212594 | A new solution to address KI#1 | Huawei, HiSilicon | imported from 3GU |
S3‑212595 | A new testcase to NSSAAF SCAS | Huawei, HiSilicon | imported from 3GU |
S3‑212596 | An editoral change to TS 33.216 | Huawei, HiSilicon | imported from 3GU |
S3‑212597 | Clairfication on AS key generation after runing NAS SMC | Huawei, HiSilicon | imported from 3GU |
S3‑212598 | Clarification on Kausf storage in multi-NAS connection | Huawei, HiSilicon | imported from 3GU |
S3‑212599 | Clarification on Kausf storage in multi-NAS connection | Huawei, HiSilicon | imported from 3GU |
S3‑212600 | Clarification on AAnF selection | Huawei, HiSilicon | imported from 3GU |
S3‑212601 | NSSAAF SCAS cleanup | Huawei, HiSilicon | imported from 3GU |
S3‑212602 | CR to 33.926 threat analysis on select AAA-P and AAA-S | Huawei, HiSilicon | imported from 3GU |
S3‑212603 | conclusion to KI#2 | Huawei, HiSilicon | imported from 3GU |
S3‑212604 | conclusion to KI#5 to KI#8 | Huawei, HiSilicon | imported from 3GU |
S3‑212605 | conclusion to KI#11 | Huawei, HiSilicon | imported from 3GU |
S3‑212606 | add reference to TS 33.512 | Huawei, HiSilicon | imported from 3GU |
S3‑212607 | Add a new procedure to enable the AF to refresh the Kaf | Huawei, HiSilicon | imported from 3GU |
S3‑212608 | Resolve EN in Sol#27 | Huawei, HiSilicon | imported from 3GU |
S3‑212609 | Resolve EN in Sol#28 | Huawei, HiSilicon | imported from 3GU |
S3‑212610 | New solution for one-to-one communication | Huawei, HiSilicon | imported from 3GU |
S3‑212611 | Add conclusion to Key Issue #1 | Huawei, HiSilicon | imported from 3GU |
S3‑212612 | Add conclusion to Key Issue #3 | Huawei, HiSilicon | imported from 3GU |
S3‑212613 | Add conclusion to key Issue #9 | Huawei, HiSilicon | imported from 3GU |
S3‑212614 | Add conclusion to Key Issue #12 | Huawei, HiSilicon | imported from 3GU |
S3‑212615 | Add conclusion to key Issue #16 | Huawei, HiSilicon | imported from 3GU |
S3‑212616 | Propose evaluation to sol #1 | Huawei, HiSilicon | imported from 3GU |
S3‑212617 | Propose evaluation to sol #5 | Huawei, HiSilicon | imported from 3GU |
S3‑212618 | UAV location information verification | Huawei, HiSilicon | imported from 3GU |
S3‑212619 | New solution to avoid policy mismatch | Huawei, HiSilicon | imported from 3GU |
S3‑212620 | Discussion on the bidding down attack during one-to-one communication establishment | Huawei, HiSilicon | imported from 3GU |
S3‑212621 | Security solution for temporary group call | Huawei,HiSilicon | imported from 3GU |
S3‑212622 | Correction to Authorization for indirect communication with delegated discovery procedure in rel16 | Huawei,HiSilicon | imported from 3GU |
S3‑212623 | Correction to Authorization for indirect communication with delegated discovery procedure in rel17 | Huawei,HiSilicon | imported from 3GU |
S3‑212624 | Correction to Deriving AKMA Application Key for a specific AF | Huawei,HiSilicon | imported from 3GU |
S3‑212625 | New solution on UE-to-network relay Key management based on primary authentication | Huawei,HiSilicon | imported from 3GU |
S3‑212626 | Resolving the EN about the multiple EECs issues in solution 8 | Huawei,HiSilicon | imported from 3GU |
S3‑212627 | Add the missing references | Huawei,HiSilicon | imported from 3GU |
S3‑212628 | Add the missing references for Rel 16 | Huawei,HiSilicon | imported from 3GU |
S3‑212629 | Add the missing references for Rel 15 | Huawei,HiSilicon | imported from 3GU |
S3‑212630 | add evaluation for solution#3 | Huawei, HiSilicon | imported from 3GU |
S3‑212631 | update evaluation for solution#13 | Huawei, HiSilicon | imported from 3GU |
S3‑212632 | resovle EN for solution#3 | Huawei,HiSilicon | imported from 3GU |
S3‑212633 | Add a new procedure to enable the AF to refresh the Kaf | Huawei, HiSilicon | imported from 3GU |
S3‑212634 | Discussion on UE capabilities indication in UPU | Huawei, HiSilicon | imported from 3GU |
S3‑212635 | reply LS on UE capabilities indication in UPU | Huawei, HiSilicon | imported from 3GU |
S3‑212636 | Editorial change in SIP digest | Huawei, HiSilicon | imported from 3GU |
S3‑212637 | roaming-related security mechanisms | Huawei, HiSilicon | imported from 3GU |
S3‑212638 | EN romoval for solution#23 | Huawei, HiSilicon | imported from 3GU |
S3‑212639 | Solution on Authorization of Data Consumers for data access via DCCF | Huawei, HiSilicon | imported from 3GU |
S3‑212640 | Discussion on NF Domain granularity authorization | Huawei, HiSilicon | imported from 3GU |
S3‑212641 | New KI on NF Domain granularity authorization | Huawei, HiSilicon | imported from 3GU |
S3‑212642 | UP Security policy requirement on the IMS data network | Huawei, HiSilicon | imported from 3GU |
S3‑212643 | EC: Conclusion for Key issue #1 | Huawei, HiSilicon | imported from 3GU |
S3‑212644 | EC: Conclusion for Key issue #2 | Huawei, HiSilicon | imported from 3GU |
S3‑212645 | EC : Conclusion for Key issue #7 | Huawei, HiSilicon | imported from 3GU |
S3‑212646 | EC: Conclusion for Key issue #10 | Huawei, HiSilicon | imported from 3GU |
S3‑212647 | EC: Skeleton for the new TS 33.558 | Huawei, HiSilicon | imported from 3GU |
S3‑212648 | TS 33.558: Security requirements | Huawei, HiSilicon | imported from 3GU |
S3‑212649 | TS 33.558: Security for the EDGE interfaces | Huawei, HiSilicon | imported from 3GU |
S3‑212650 | TS 33.558: adding the scope | Huawei, HiSilicon | imported from 3GU |
S3‑212651 | New Key issue on authorization mechanism negotiation | Huawei, HiSilicon; China Mobile | imported from 3GU |
S3‑212652 | New solution for the authorization mechanism negotiation | Huawei, HiSilicon; China Mobile | imported from 3GU |
S3‑212653 | Requirement of subscribe-notification key issue | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | imported from 3GU |
S3‑212654 | Clarification on SoR transparent container | Huawei, HiSilicon | imported from 3GU |
S3‑212655 | MBS:Discussion paper on Authentication and authorization for multicast service | Huawei, HiSilicon | imported from 3GU |
S3‑212656 | Conclusion on authentication and authorization for multicast service | Huawei, HiSilicon | imported from 3GU |
S3‑212657 | Conclusion on key issue #1.2 | Huawei, HiSilicon | imported from 3GU |
S3‑212658 | Update to solution #14 to ML restrictive transfer of ML models | Huawei, HiSilicon | imported from 3GU |
S3‑212659 | Conclusion on key issue #3.3 on restrictive transfer of ML models | Huawei, HiSilicon | imported from 3GU |
S3‑212660 | Udpates to key issue #3.1 on attacker model | Huawei, HiSilicon | imported from 3GU |
S3‑212661 | Conclusion on key issue #3.2 on protection of UE data in transit | Huawei, HiSilicon | imported from 3GU |
S3‑212662 | Updates to solutoin #3 | Huawei, HiSilicon | imported from 3GU |
S3‑212663 | Discussion on registraiton request messgae being rerouted | Huawei, HiSilicon | imported from 3GU |
S3‑212664 | Updates to clause #4.3 | Huawei, HiSilicon | imported from 3GU |
S3‑212665 | Discussion on exposing NAS security context to RAN | Huawei, HiSilicon | imported from 3GU |
S3‑212666 | Adding for NSSAAF network product class description and assets and critical assets | Huawei, HiSilicon | imported from 3GU |
S3‑212667 | New threat related to unauthorized slice-specific authorization revocatoin | Huawei, HiSilicon | imported from 3GU |
S3‑212668 | Comparison of services for providing GBA 5G AV | Huawei, HiSilicon | imported from 3GU |
S3‑212669 | New service on 5G GBA AV | Huawei, HiSilicon | imported from 3GU |
S3‑212670 | Claifications on SoR enablement | Huawei, HiSilicon | imported from 3GU |
S3‑212671 | New key issue on service authorization in request redirection | Huawei, HiSilicon | imported from 3GU |
S3‑212672 | New solution on AF authorization | Huawei, HiSilicon | imported from 3GU |
S3‑212673 | New key issue on AF authorization | Huawei, HiSilicon | imported from 3GU |
S3‑212674 | New solution on AF authorization | Huawei, HiSilicon | imported from 3GU |
S3‑212675 | Conclusion to key issue on unauthorized MBS session operation | Huawei, HiSilicon | imported from 3GU |
S3‑212676 | Discussion paper on 256-bit algorithms based on ZUC-256 | CAICT, China Mobile, China Unicom, China Telecom, CBN | imported from 3GU |
S3‑212677 | Updates to solution #17 capability negotiation | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212678 | Solution 4: Clarify and update EN related Secondary authentication | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212679 | [DRAFT] Reply-LS on security aspects for the method of collection of data from the UE | Guangdong OPPO Mobile Telecom. | imported from 3GU |
S3‑212680 | Solution 4: Clarify and update EN Application Client | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212681 | LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212682 | Cleanup MUSIM TR | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212683 | Editorial Clarifications for Trusted non-3GPP Access using TNGF | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212684 | pCR to Living doc on addition of 5G to BEST - addition of EMSDP updates | VODAFONE Group Plc | imported from 3GU |
S3‑212685 | Reply LS on Small data transmission | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212686 | Response LS on 256-bit algorithms based on SNOW 3G or SNOW V | VODAFONE Group Plc | imported from 3GU |
S3‑212687 | Key issue on security aspects of Paging Cause | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212688 | Updates to solution 14: Removal of Editor’s notes: Security Issues | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212689 | Updates to solution 14: Removal of Editor’s notes: Three Authentication | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212690 | Updates to solution 14: Removal of Editor’s notes: One-Way | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212691 | Proposal for conclusion for Key Issue 4 | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑212692 | Clarification on RRCConnectionRe-establishment Procedure in Control Plane CIoT EPS Optimization | Huawei, HiSilicon | imported from 3GU |
S3‑212693 | Clarification on RRCConnectionRe-establishment Procedure in Control Plane CIoT 5GS Optimization | Huawei, HiSilicon | imported from 3GU |
S3‑212694 | UP Security Activation Mechanism in LTE | Huawei, HiSilicon | imported from 3GU |
S3‑212695 | UP Security Policy Handling for Option 3 | Huawei, HiSilicon | imported from 3GU |
S3‑212696 | Clarification on UP IP indication based on RAN3 LS | Huawei, HiSilicon | imported from 3GU |
S3‑212697 | Clarification on Finding the right NF instance are serving the UE | Huawei, HiSilicon, China Mobile | imported from 3GU |
S3‑212698 | Reply LS for Small Data Transfer | Huawei, HiSilicon | imported from 3GU |
S3‑212699 | Evaluation on indication of key derivation | Huawei, HiSilicon | imported from 3GU |
S3‑212700 | Conclusion on KI#1 for key derivation | Huawei, HiSilicon | imported from 3GU |
S3‑212701 | New solution for User Consent for 3GPP service exposure | Huawei, HiSilicon | imported from 3GU |
S3‑212702 | General Conclusion on UDM service for User Consent Check | Huawei, HiSilicon | imported from 3GU |
S3‑212703 | General Conclusion on Generic Requirement for the Procedures for User Consent Check | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212704 | General Conclusion on UDM service for User Consent Revocation | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212705 | New WID for UC3S | Huawei, HiSilicon, China Mobile, China Unicom, China Telecom, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212706 | Draft skeleton for UC3S WID | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212707 | General Conclusion on Generic Requirement for the Procedure for User Consent Revocation | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212708 | Solution for user consent revocation | Huawei, HiSilicon | imported from 3GU |
S3‑212709 | Solution Update and Evaluation for Solution 3 | Huawei, HiSilicon | imported from 3GU |
S3‑212710 | Conclusion on KI#2 for User Plane Provisioning | Huawei, HiSilicon | imported from 3GU |
S3‑212711 | Skeleton for UC3S Conclusion | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212712 | Conclusion for Key Issue #1 | Huawei, HiSilicon | imported from 3GU |
S3‑212713 | Conclusion for Key Issue #2 | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212714 | Conclusion for Key Issue #3 | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212715 | skeleton for the new annex | Huawei, HiSilicon | imported from 3GU |
S3‑212716 | Security protection between AF and 5GC | Huawei, HiSilicon | imported from 3GU |
S3‑212717 | Discussion paper on MBS traffic protection | Huawei, HiSilicon | imported from 3GU |
S3‑212718 | Conclusion for key issue 2 | Huawei, HiSilicon | imported from 3GU |
S3‑212719 | Conclusion for key issue 3 | Huawei, HiSilicon | imported from 3GU |
S3‑212720 | addressing the EN in solution#11 | Huawei, HiSilicon | imported from 3GU |
S3‑212721 | addressing the EN in solution#12 | Huawei, HiSilicon | imported from 3GU |
S3‑212722 | Conclusion for key issue 3.2 | Huawei, HiSilicon | imported from 3GU |
S3‑212723 | [draft] Reply LS for clarification on managing expired or multiple Protection Scheme and Home Network keys used for SUCI calculation. | NTT DOCOMO INC. | imported from 3GU |
S3‑212724 | Reply LS on Small data transmissions | CATT | imported from 3GU |
S3‑212725 | Reply LS on UE location aspects in NTN | CATT | imported from 3GU |
S3‑212726 | Replay LS on UE location aspects in NTN | Huawei, HiSilicon | imported from 3GU |
S3‑212727 | New WID on Security Aspects of Proximity based Services (ProSe) in the 5G | CATT | imported from 3GU |
S3‑212728 | pCR to TR33.847- Conclusion of KI#1 | CATT | imported from 3GU |
S3‑212729 | pCR to TR33.847- Conclusion of KI#2 | CATT | imported from 3GU |
S3‑212730 | Living CR for UPIP for LTE | Huawei, HiSilicon | imported from 3GU |
S3‑212731 | pCR to TR33.847- Conclusion of KI#3 | CATT | imported from 3GU |
S3‑212732 | pCR to TR33.847- Conclusion of KI#6-KI#8 | CATT | imported from 3GU |
S3‑212733 | Further conclusions for KI #1 | Ericsson, Huawei, Interdigital, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
S3‑212734 | Change request to living document: EAP flow | Ericsson | imported from 3GU |
S3‑212735 | Change request to living document: Key hierarchy | Ericsson | imported from 3GU |
S3‑212736 | Discussion on protection of UE capabilities indication in UPU and "ME support of SOR-CMCI" indicator in SoR | Ericsson | imported from 3GU |
S3‑212737 | UE parameters update data set types supported by the UE | Ericsson | imported from 3GU |
S3‑212738 | Protection of “ME support of SOR-CMCI” indication | Ericsson | imported from 3GU |
S3‑212739 | Clarification on AMF transparency for UPU | Ericsson | imported from 3GU |
S3‑212740 | draft reply LS on UE capabilities indication in UPU | Ericsson | imported from 3GU |
S3‑212741 | UDM Service correction | Ericsson | imported from 3GU |
S3‑212742 | UDM Service correction | Ericsson | imported from 3GU |
S3‑212743 | FBS - Clarification in Solution 4 | Philips International B.V. | imported from 3GU |
S3‑212744 | FBS - Clarification quantum-resistance | Philips International B.V. | imported from 3GU |
S3‑212745 | pCR to TR33.847- Conclusion of KI#12 | CATT | imported from 3GU |
S3‑212746 | FBS - Conclusions Solution 23 | Philips International B.V. | imported from 3GU |
S3‑212747 | FBS - Conclusions Solution 24 | Philips International B.V. | imported from 3GU |
S3‑212748 | FBS - Discussion about the stealthy FBSMitM attack and minor modifications in Solution 14 to deal with it | Philips International B.V. | imported from 3GU |
S3‑212749 | MBS - Conclusions KI 3 | Philips International B.V. | imported from 3GU |
S3‑212750 | MBS - Conclusions Solution 9 | Philips International B.V. | imported from 3GU |
S3‑212751 | pCR to TR33.847- Conclusion of KI#13 | CATT | imported from 3GU |
S3‑212752 | Security aspects of eNPN (skeleton for living document) | Ericsson | imported from 3GU |
S3‑212753 | Change request to living document: Credentials holder using AUSF and UDM for primary authentication | Ericsson | imported from 3GU |
S3‑212754 | Conclusions for KI#4 (initial access) | Ericsson, Huawei, InterDigital, Lenovo, Motorola Mobility, Qualcomm Incorporated | imported from 3GU |
S3‑212755 | Source PLMN-ID solution when using same N32 connection for multiple PLMN-IDs belonging to same PLMN | Ericsson | imported from 3GU |
S3‑212756 | SEPP to verify the source PLMN-ID | Ericsson | imported from 3GU |
S3‑212757 | SEPP to verify the source PLMN-ID | Ericsson | imported from 3GU |
S3‑212758 | NF to always insert PLMN-ID enabling roaming scenario | Ericsson | imported from 3GU |
S3‑212759 | NF to always insert PLMN-ID enabling roaming scenario | Ericsson | imported from 3GU |
S3‑212760 | Misalignment between TS 33.501 and TS 29.500 on audience claim of CCAs | Ericsson | imported from 3GU |
S3‑212761 | Update to Solution #3 "Using existing procedures for authorization of SCP to act on behalf of an NF Consumer" | Ericsson | imported from 3GU |
S3‑212762 | Conclusion to Key Issue #4 "Authorization of SCP to act on behalf of an NF or another SCP" | Ericsson | imported from 3GU |
S3‑212763 | Correction of implementation of S3-211046 | Ericsson | imported from 3GU |
S3‑212764 | Update Solution #5: End-to-end integrity protection of HTTP body and method | Ericsson | imported from 3GU |
S3‑212765 | MBS - Update Solution 11 | Philips International B.V. | imported from 3GU |
S3‑212766 | pCR to TR33.847- Update Solution#29 | CATT | imported from 3GU |
S3‑212767 | Proposal for a conclusion on KI#4 – one way authentication. | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212768 | Proposal for a conclusion on KI#4 – OSNPN authentication. | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212769 | Proposal for a solution to KI#4. | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212770 | Update to solution #19 – Authorization added. | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212771 | User Plane Integrity Protection Policy Handling in EN-DC | Ericsson | imported from 3GU |
S3‑212772 | User Plane Integrity Protection Policy Handling in IW handover from 5GS to EPS | Ericsson | imported from 3GU |
S3‑212773 | User Plane Integrity Protection Policy Handling in DC | Ericsson | imported from 3GU |
S3‑212774 | User Plane Integrity Protection Policy Handling in IW handover from EPS to 5GS | Ericsson | imported from 3GU |
S3‑212775 | User Plane Integrity Protection | Ericsson | imported from 3GU |
S3‑212776 | User Plane Integrity Protection: Correction to A.7 | Ericsson | imported from 3GU |
S3‑212777 | Add details of UPIP algorithms to be supported | Ericsson | imported from 3GU |
S3‑212778 | [DRAFT] LS on use of LTE algorithms or NR algorithms for UP integrity protection with NR PDCP | Ericsson | imported from 3GU |
S3‑212779 | New WID on 5GFBS | Apple | imported from 3GU |
S3‑212780 | 5GFBS-Update of solution#17 | Apple | imported from 3GU |
S3‑212781 | 5GFBS-Conclusion on key issue#2 | Apple | imported from 3GU |
S3‑212782 | 5GFBS-Conclusion on key issue#1 on solution#17 | Apple | imported from 3GU |
S3‑212783 | MEC- Discussion paper on the privacy issue EEC ID | Apple | imported from 3GU |
S3‑212784 | MEC-Discussion paper on including EEC ID in the authentication procedure | Apple | imported from 3GU |
S3‑212785 | MEC- New solution on EEC ID privacy protection | Apple | imported from 3GU |
S3‑212786 | MEC - Conclusion on the key issue 2 on the authentication between EEC and ECS | Apple | imported from 3GU |
S3‑212787 | MEC- Addressing the EN in solution#28 on EEC ID authentication | Apple | imported from 3GU |
S3‑212788 | UC3S-User consent update | Apple | imported from 3GU |
S3‑212789 | MBS-new solution for key issue#2 | Apple | imported from 3GU |
S3‑212790 | Discussion paper on the FSAG Doc 92_003 on NAS messages attack | Apple | imported from 3GU |
S3‑212791 | CR on TS 33.501 on adding requirement to mitigate the attack of selectively dropping NAS messages | Apple | imported from 3GU |
S3‑212792 | Reply to GSMA on FSAG Doc 92_003 on NAS messages attack | Apple | imported from 3GU |
S3‑212793 | Discussion paper on GSMA LS of SPARROW attack | Apple | imported from 3GU |
S3‑212794 | Draft reply LS to RAN2 on SDT security | Apple | imported from 3GU |
S3‑212795 | Discussion paper on the security context handling in IRAT | Apple | imported from 3GU |
S3‑212796 | CR on TS 33.501 on the security context handling in IRAT | Apple | imported from 3GU |
S3‑212797 | CR on TS 33.501 on SOR-MAC calculation | Apple | imported from 3GU |
S3‑212798 | New WID on Security Assurance Specification for Management Function | Huawei, HiSilicon | imported from 3GU |
S3‑212799 | New WID on security aspects of MSGin5G | China Mobile, Samsung, Huawei, Hisilicon | imported from 3GU |
S3‑212800 | draftCR for the skeleton for MSGin5G_SEC | China Mobile | imported from 3GU |
S3‑212801 | Add conclusion to KI #1 | China Mobile | imported from 3GU |
S3‑212802 | Transport security of MSGin5G-1 interface | China Mobile | imported from 3GU |
S3‑212803 | Solution to the transport security of MSGin5G-2 and MSGin5G-4 | China Mobile | imported from 3GU |
S3‑212804 | Add conclusion to KI#2 | China Mobile | imported from 3GU |
S3‑212805 | Solution to key issue#3 | China Mobile | imported from 3GU |
S3‑212806 | Solution to key issue#4 | China Mobile | imported from 3GU |
S3‑212807 | Editorial corrections for TR33.862 | China Mobile | imported from 3GU |
S3‑212808 | Deleting the EN of solution#4 | China Mobile | imported from 3GU |
S3‑212809 | Update and evaluation of solution #32 | Philips International B.V. | imported from 3GU |
S3‑212810 | New WID on security aspects of eNA | China Mobile | imported from 3GU |
S3‑212811 | Draft_skeleton_for_draft_CR_eNA_SEC | China Mobile | imported from 3GU |
S3‑212812 | Solution to abnormal behaviour detection of IoT SIM card | China Mobile | imported from 3GU |
S3‑212813 | Add conclusion to KI #1.2 | China Mobile | imported from 3GU |
S3‑212814 | Add conclusion to KI #1.5 | China Mobile | imported from 3GU |
S3‑212815 | Add conclusion to KI #2.1 | China Mobile | imported from 3GU |
S3‑212816 | Add conclusion to KI #3.2 | China Mobile | imported from 3GU |
S3‑212817 | Add evaluation to solution #3 | China Mobile | imported from 3GU |
S3‑212818 | Discussion on the conclusion of KI#1.3 | China Mobile | imported from 3GU |
S3‑212819 | Add conclusion to KI #6 | China Mobile | imported from 3GU |
S3‑212820 | Clean up the editorial issues | China Mobile | imported from 3GU |
S3‑212821 | Clarification on Data Masking on Integration Analysis | China Mobile | imported from 3GU |
S3‑212822 | Deleting the NOTE of roaming | China Mobile | imported from 3GU |
S3‑212823 | Prevention of attacks on slice core by CCA modifications - Rel-16 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212824 | Prevention of attacks on slice core by CCA modifications - Rel-17 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212825 | KAF refresh | China Mobile | imported from 3GU |
S3‑212826 | IPUPS overload control | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212827 | Editorial corrections to the UAS TR | Qualcomm Incorporated | imported from 3GU |
S3‑212828 | Resolution of EN in solutions | Qualcomm Incorporated | imported from 3GU |
S3‑212829 | Proposed conclusion for key issue #3 | Qualcomm Incorporated | imported from 3GU |
S3‑212830 | Proposed conclusion for key issue #5 | Qualcomm Incorporated | imported from 3GU |
S3‑212831 | Proposed common conclusion for key issues #6 and #7 | Qualcomm Incorporated | imported from 3GU |
S3‑212832 | Resolution of EN in general clauses | Qualcomm Incorporated | imported from 3GU |
S3‑212833 | Cover sheet | Qualcomm Incorporated | imported from 3GU |
S3‑212834 | TS 33.256 skeleton | Qualcomm Incorporated | imported from 3GU |
S3‑212835 | Proposed text for scope and overview of UAS TS | Qualcomm Incorporated | imported from 3GU |
S3‑212836 | Proposed text on UUAA for UAS TS | Qualcomm Incorporated | imported from 3GU |
S3‑212837 | Proposed text on location security for UAS TS | Qualcomm Incorporated | imported from 3GU |
S3‑212838 | Discussion on adding SCAS for the various split gNB cases | Qualcomm Incorporated, Deutsche Telekom AG | imported from 3GU |
S3‑212839 | Adding SCAS for the various split gNB cases | Qualcomm Incorporated, Deutsche Telekom AG | imported from 3GU |
S3‑212840 | Corrections to the TLS with AKMA specification | Qualcomm Incorporated | imported from 3GU |
S3‑212841 | Adding TLS 1.3 with AKMA keys | Qualcomm Incorporated | imported from 3GU |
S3‑212842 | Correction to the GBA TLS 1.3 specification | Qualcomm Incorporated | imported from 3GU |
S3‑212843 | Proposed conclusion for key issue #4.1 | Qualcomm Incorporated, Thales | imported from 3GU |
S3‑212844 | Some proposed text for the assessment of attack risk table | Qualcomm Incorporated | imported from 3GU |
S3‑212845 | Proposed conclusion for the linkability parts of key issues #2.1 and 2.2 | Qualcomm Incorporated | imported from 3GU |
S3‑212846 | Adding MACS as an input parameter to the calculation of AK* to provide freshness | Qualcomm Incorporated, Thales | imported from 3GU |
S3‑212847 | Discussion on proposed response to RAN3 LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated | imported from 3GU |
S3‑212848 | LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated | imported from 3GU |
S3‑212849 | Proposed conclusions for key issue #1 and key issue #2 | Qualcomm Incorporated | imported from 3GU |
S3‑212850 | Proposed conclusion for AMF Re-allocation | Qualcomm Incorporated | imported from 3GU |
S3‑212851 | Conclusion on KI #3, KI #4 and KI #9 related to security for the Layer-3 UE-to-Network relay scenario | Qualcomm Incorporated, MITRE, AT&T | imported from 3GU |
S3‑212852 | Conclusion of KI #1 | Qualcomm Incorporated | imported from 3GU |
S3‑212853 | EN resolution of Solution #34 | Qualcomm Incorporated | imported from 3GU |
S3‑212854 | Evaluation of Solution #34 | Qualcomm Incorporated | imported from 3GU |
S3‑212855 | Evaluation of Solution #24 | Qualcomm Incorporated | imported from 3GU |
S3‑212856 | EN resolution of Solution #18 | Qualcomm Incorporated | imported from 3GU |
S3‑212857 | Conclusion of KI #3 | Qualcomm Incorporated | imported from 3GU |
S3‑212858 | Conclusion of KI #4 | Qualcomm Incorporated | imported from 3GU |
S3‑212859 | Update of solution #18 to support privacy protection | Qualcomm Incorporated | imported from 3GU |
S3‑212860 | Update an evaluation for solution #10 | Qualcomm Incorporated | imported from 3GU |
S3‑212861 | Conclusion of security and privacy of groupcast communication | Qualcomm Incorporated | imported from 3GU |
S3‑212862 | Way forward for the 5G MBS security | Qualcomm Incorporated | imported from 3GU |
S3‑212863 | Update of Solution #12 | Qualcomm Incorporated | imported from 3GU |
S3‑212864 | Evaluation of Solution #12 | Qualcomm Incorporated | imported from 3GU |
S3‑212865 | Conclusion for the KI#2 | Qualcomm Incorporated | imported from 3GU |
S3‑212866 | Solution #4 Evaluation (Enriched MR) | Qualcomm Incorporated | imported from 3GU |
S3‑212867 | eNPN: Evaluation of Solution #5 | Qualcomm Incorporated | imported from 3GU |
S3‑212868 | pCR: Additional conclusions for KI #1 | Qualcomm Incorporated | imported from 3GU |
S3‑212869 | Sending UE identifier to the AKMA AF | Qualcomm Incorporated | imported from 3GU |
S3‑212870 | Solution for 5G NSWO authentication | Qualcomm Incorporated | imported from 3GU |
S3‑212871 | Alignment of requirements with specification updates | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212872 | Alignment of requirements with specification updates | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212873 | Solution to KI#1 (Support of EAP-AKA’ authentication for NSWO) using credentials retrieved from UDM | Ericsson | imported from 3GU |
S3‑212874 | Solution Privacy preservation of transmitted data | Nokia Germany | imported from 3GU |
S3‑212875 | Solution to KI#1 (Support of EAP-AKA’ authentication for NSWO) using credentials retrieved from UDM/ARPF via HSS | Ericsson | imported from 3GU |
S3‑212876 | Reply LS on Misalignment on usage of OAuth within 3GPP 29.510 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212877 | LS on N32 and multiple PLMN IDs | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212878 | KI and solution to NRF deployments | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212879 | vNRF-hNRF mutual authentication in service access authorization | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212880 | Way forward SID eSBA | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212881 | WID eSBA | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212882 | Sol 1 NFp verification – EN resolutions and evaluation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212883 | Editorial update on trust clause | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212884 | EN resolution on trust model for SCP | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212885 | Access token request for NF Set – EN resolution | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212886 | Access token request for NF Set – RFC clarification | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212887 | SCP authorization | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212888 | SCP authorization solution evaluation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212889 | SCP authorization conclusion | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212890 | KI and Solution for verification of NFc by NF producers | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212891 | NRF service definition R15 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212892 | NRF service definition R16 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212893 | NRF service definition R17 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212894 | SBA NRF roaming clarification | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212895 | OAuth misalignment - R15 | Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | imported from 3GU |
S3‑212896 | OAuth misalignment - R16 | Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | imported from 3GU |
S3‑212897 | OAuth misalignment - R17 | Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | imported from 3GU |
S3‑212898 | Alignment for Oauth2.0 validation R15 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212899 | Alignment for Oauth2.0 validation R16 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212900 | Alignment for Oauth2.0 validation R17 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212901 | Discussion on Refresh of KAKMA and KAF | Samsung, China Mobile | imported from 3GU |
S3‑212902 | [CR] Refresh of KAF and KAKMA | Samsung | imported from 3GU |
S3‑212903 | [CR] HN triggering Primary (Re)Authentication | Samsung | imported from 3GU |
S3‑212904 | [5GMSG] Evaluation of Solution#1 | Samsung | imported from 3GU |
S3‑212905 | [5GMSG] Evaluation of Solution#3 | Samsung | imported from 3GU |
S3‑212906 | [5GMSG] Evaluation of Solution#5 | Samsung | imported from 3GU |
S3‑212907 | [5GMSG] Evaluation of Solution#8 | Samsung | imported from 3GU |
S3‑212908 | [5GMSG] Conclusion for KI#1 and KI#2 | Samsung | imported from 3GU |
S3‑212909 | [ProSe] Updates to Solution#1 | Samsung | imported from 3GU |
S3‑212910 | [ProSe] Updates to evaluation of solution#1 | Samsung | imported from 3GU |
S3‑212911 | [EDGE] Update to Solution#3 | Samsung | imported from 3GU |
S3‑212912 | [EDGE] Update to evaluation of Solution#3 | Samsung | imported from 3GU |
S3‑212913 | [EDGE] Conclusion for KI#1 | Samsung | imported from 3GU |
S3‑212914 | [EDGE] Conclusion for KI#2 | Samsung, Lenovo, Motorola Mobility | imported from 3GU |
S3‑212915 | [UC3S] Solution on user's consent for exposure of information to Edge Applications | Samsung | imported from 3GU |
S3‑212916 | KI on Authorization for Inter-Slice Access | Samsung | imported from 3GU |
S3‑212917 | New Solution to KI #X: Authorization for Inter-Slice Access | Samsung | imported from 3GU |
S3‑212918 | [AMF Re-alloc] Proposed Way Forward | Samsung | imported from 3GU |
S3‑212919 | Removal of Editor’s Note in Solution #5 | Samsung | imported from 3GU |
S3‑212920 | Discussion on MBS Security | Samsung | imported from 3GU |
S3‑212921 | [MBS] Solution#13 Evaluation | Samsung | imported from 3GU |
S3‑212922 | [IAB] Add requirement to Key Issue #2.4 | Samsung | imported from 3GU |
S3‑212923 | [IAB] Solution on authenticity verification of BH-RLF indication | Samsung | imported from 3GU |
S3‑212924 | [IAB] Solution to protect the BAP control PDU exchange | Samsung | imported from 3GU |
S3‑212925 | [IAB] Conclusion for KI#2.4 | Samsung | imported from 3GU |
S3‑212926 | Update to Solution #10 | Samsung | imported from 3GU |
S3‑212927 | Update on Solution 6 | Samsung | imported from 3GU |
S3‑212928 | New solution on key issue #5 | Samsung | imported from 3GU |
S3‑212929 | Evaluation for solution 1 | Samsung | imported from 3GU |
S3‑212930 | Evaluation for solution 4 | Samsung | imported from 3GU |
S3‑212931 | Evaluation for solution 5 | Samsung | imported from 3GU |
S3‑212932 | Conclusion for KI#1 | Samsung | imported from 3GU |
S3‑212933 | Conclusion for KI#5 | Samsung | imported from 3GU |
S3‑212934 | Conclusion on key issue #3 and key issue #4 | Ericsson | imported from 3GU |
S3‑212935 | Update to solution #21 | Ericsson | imported from 3GU |
S3‑212936 | Update to Solution#4 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212937 | Conclusions for KI#10 "Authorization during Edge Data Network change" | Ericsson | imported from 3GU |
S3‑212938 | Conclusions for KI#7 "Security of Network Information Provisioning to Local Applications with low latency procedure" | Ericsson | imported from 3GU |
S3‑212939 | Update to Solution #17: Resolving EN on Token Usage | Ericsson | imported from 3GU |
S3‑212940 | LS on EAS and ECS identifiers | Ericsson | imported from 3GU |
S3‑212941 | Update to conclusion #1 | Ericsson | imported from 3GU |
S3‑212942 | Conclusion on KI#1 | Ericsson | imported from 3GU |
S3‑212943 | Conclusion on KI#2 | Ericsson | imported from 3GU |
S3‑212944 | Update to Solution #17: Resolving ENs | Ericsson | imported from 3GU |
S3‑212945 | Discussion on Mission Critical Security over 5G System | Ericsson | imported from 3GU |
S3‑212946 | Solution to address KI#1 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212947 | Solution to address KI#1 and KI#4 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212948 | Conclusion for KI#6 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212949 | Conclusion to KI#1 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212950 | EAP ID Request in NSSAA Procedure (Rel-16) | Ericsson | imported from 3GU |
S3‑212951 | eEDGE: Corrections in Solution #13 | Xiaomi Technology | imported from 3GU |
S3‑212952 | eEDGE: Add Clarifications for Solutions covering Application Layer | Xiaomi Technology | imported from 3GU |
S3‑212953 | ProSe: Addional Evaluation for Solution #9 | Xiaomi Technology | imported from 3GU |
S3‑212954 | ProSe: Addional Evaluation for Solution #10 | Xiaomi Technology | imported from 3GU |
S3‑212955 | ProSe: Addional Evaluation for Solution #14 | Xiaomi Technology | imported from 3GU |
S3‑212956 | ProSe: Addional Evaluation for Solution #15 | Xiaomi Technology | imported from 3GU |
S3‑212957 | ProSe: Addional Evaluation for Solution #18 | Xiaomi Technology | imported from 3GU |
S3‑212958 | ProSe: Addional Evaluation for Solution #22 | Xiaomi Technology | imported from 3GU |
S3‑212959 | ProSe: Add Evaluation for Solution #27 | Xiaomi Technology | imported from 3GU |
S3‑212960 | ProSe: Add Evaluation for Solution #28 | Xiaomi Technology | imported from 3GU |
S3‑212961 | ProSe: Addional Evaluation for Solution #30 | Xiaomi Technology | imported from 3GU |
S3‑212962 | ProSe: Conclusions for Key Issues #6, #7, #8 | Xiaomi Technology | imported from 3GU |
S3‑212963 | ProSe: Conclusion for Key Issue #13 | Xiaomi Technology | imported from 3GU |
S3‑212964 | ProSe: Conclusion for Key Issue #16 | Xiaomi Technology | imported from 3GU |
S3‑212965 | ProSe: New Solution for Key Issue #17 | Xiaomi Technology | imported from 3GU |
S3‑212966 | ProSe: Conclusion for Key Issue #17 | Xiaomi Technology | imported from 3GU |
S3‑212967 | ProSe: New Solution for Key Issue #3 | Xiaomi Technology | imported from 3GU |
S3‑212968 | ProSe: Conclusion for Key Issue #3 | Xiaomi Technology | imported from 3GU |
S3‑212969 | eNPN: Conclusion Update for Key Issue #1 | Xiaomi Technology | imported from 3GU |
S3‑212970 | eNPN: New Solution for Key Issue #2 | Xiaomi Technology | imported from 3GU |
S3‑212971 | eNPN: Resolution of the Editor’s Notes in Key Issue #2 | Xiaomi Technology, Lenovo, Motorola Mobility | imported from 3GU |
S3‑212972 | eNPN: Conclusion for Key Issue #2 | Xiaomi Technology | imported from 3GU |
S3‑212973 | New KI on Secrets in Container Images | Altiostar | imported from 3GU |
S3‑212974 | EAP ID Request in NSSAA Procedure (Rel-17) | Ericsson | imported from 3GU |
S3‑212975 | New KI on Container breakouts | Altiostar | imported from 3GU |
S3‑212976 | Security for temporary calls | CATT | imported from 3GU |
S3‑212977 | LS on EAP ID Request in NSSAA Procedure | Ericsson | imported from 3GU |
S3‑212978 | Ed Note Removal for Solution 11 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212979 | Ed Note Removal to include mechanism when notification sent via MFAF for Solution 11 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212980 | Evaluation to the Solution 11 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212981 | Ed Note Removal for Solution 10 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212982 | Conclusion to KI 1.3 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212983 | Evaluation to the Solution 10 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212984 | Editorial Notes Removal for Solution 10 to address authorization mechanisms when data is sent via MFAF | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212985 | Enhancement to the solution on Detection of anomalous NF behaviour by NWDAF | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212986 | Evaluation to the Solution 7 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212987 | Conclusion to KI 2.2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212988 | Evaluation on Sol 14 - Solution to ML restrictive transfer Framework | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212989 | Update KI 3.3 - Ensuring restrictive transfer of ML models between authorized NWDAF instances | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212990 | Evaluation on Sol 5- Providing the Security protection of data via Messaging Framework | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212991 | Update to KI 1.4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212992 | Conclusion to KI 1.4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212993 | Solution on Protection of data sent via MFAF using existing SBA mechanisms | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | imported from 3GU |
S3‑212994 | LS on NF Service Producer Meta Data Addition by ADRF | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑212995 | Removal of Editor’s Note of Solution#4 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212996 | Adding Evaluation to Solution#4 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212997 | Removal of Editor’s Note of Solution#5 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212998 | Adding Evaluation to Solution#5 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑212999 | Solution on NSWO authentication with AAA-Server | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213000 | Tracking, enforcement, and validity of user consent | Ericsson | imported from 3GU |
S3‑213001 | Solution on NSWO authentication via an interworking function | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213002 | Evaluation of the potential security issue in QoE report handling at QoE pause | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213003 | Padding SUPIs in NAI format for non-null schemes | Ericsson, AT&T, CableLabs | imported from 3GU |
S3‑213004 | [DRAFT] Reply LS on QoE report handling at QoE pause | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213005 | A new onboarding solution addressing KI#2 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213006 | pCR to 33.846: impacts on the USIM of solution #4.6 | THALES | imported from 3GU |
S3‑213007 | pCR to 33.846: assessment of attack risk | THALES | imported from 3GU |
S3‑213008 | pCR to 33.839: solution #26 | THALES | imported from 3GU |
S3‑213009 | pCR to 33.839: solution #27 | THALES | imported from 3GU |
S3‑213010 | pCR to 33.839: conclusion for Key Issue #1 | THALES | imported from 3GU |
S3‑213011 | pCR to 33.839: Conclusion for Key Issue #2 | THALES | imported from 3GU |
S3‑213012 | Recovering NSSAI and ENSI mapping (Rel-16) | Samsung | imported from 3GU |
S3‑213013 | Recovering NSSAI and ENSI mapping (Rel-17) | Samsung | imported from 3GU |
S3‑213014 | Comment on 256-bit algorithms based on Snow-V | CATT | imported from 3GU |
S3‑213015 | Update_on_Key_issue#1.4 | Ericsson | imported from 3GU |
S3‑213016 | Update_on_Solution#5 | Ericsson | imported from 3GU |
S3‑213017 | Update_on_Solution#12 | Ericsson | imported from 3GU |
S3‑213018 | Conclusion on KI#1.3 | Ericsson | imported from 3GU |
S3‑213019 | Conclusion on KI#1.4 | Ericsson | imported from 3GU |
S3‑213020 | eCryptPr 01 CR 33.310 R17 Security updates for algorithms and protocols | Ericsson | imported from 3GU |
S3‑213021 | eCryptPr 02 CR 33.203 R17 Security updates for algorithms and protocols | Ericsson | imported from 3GU |
S3‑213022 | Security updates for algorithms and protocols for 33.310 | Ericsson | imported from 3GU |
S3‑213023 | Security updates for algorithms and protocols for 33.210 | Ericsson | imported from 3GU |
S3‑213024 | User consent: New key issue on naming of purposes | NTT DOCOMO INC. | imported from 3GU |
S3‑213025 | draft CR to 33.401 - addition of UPIP requirements (NEA and NIA based) | VODAFONE Group Plc | imported from 3GU |
S3‑213026 | draft CR to 33.401 - addition of UPIP requirements (EEA and EIA based) | VODAFONE Group Plc | imported from 3GU |
S3‑213027 | [Draft] Reply LS on UE location aspects in NTN | Xiaomi Technology | imported from 3GU |
S3‑213028 | Addressing Editor's notes of KI#2 | Philips International B.V., Lenovo, Motorola Mobility | imported from 3GU |
S3‑213029 | New KI on Compromised slice information | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213030 | Update to Key Issue #1 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213031 | Clarification on UP IP indication based on RAN3 LS | Huawei, HiSilicon | imported from 3GU |
S3‑213032 | SA3 meeting calendar | WG Chair | imported from 3GU |
S3‑213033 | Reply LS on Security risk evaluation of using long term key for another key derivation than AKA | ETSI SAGE | imported from 3GU |
S3‑213034 | Reply LS on Small data transmissions | InterDigital, Inc. | imported from 3GU |
S3‑213035 | LS on full registration request in AMF reallocation via RAN | Huawei, HiSilicon | imported from 3GU |
S3‑213036 | LS on NSAC procedure | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
S3‑213037 | Non-Seamless WLAN offload Authentication in 5GS | Nokia, Nokia Shanghai Bell, AT&T,Lenovo, Motorola Mobility, Huawei, HiSilicon, Samsung, Intel, Qualcomm Incorporated, Thales | imported from 3GU |
S3‑213038 | Editor note removal and update for solution#10 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213039 | Ed Note Removal for Solution 10 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213040 | Reply LS on Header Enrichment for HTTPS in PFCP | C4-214531 | imported from 3GU |
S3‑213041 | Editorial Notes Removal for Solution 10 to address authorization mechanisms when data is sent via MFAF | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213042 | Solution to address KI#4 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213043 | Update to Solution #3 "Using existing procedures for authorization of SCP to act on behalf of an NF Consumer" | Ericsson | imported from 3GU |
S3‑213044 | Evaluation to the Solution 10 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213045 | Solution on Protection of data sent via MFAF using existing SBA mechanisms | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | imported from 3GU |
S3‑213046 | Update KI 3.3 - Ensuring restrictive transfer of ML models between authorized NWDAF instances | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213047 | Evaluation to the Solution 7 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213048 | Ed Note Removal for Solution 11 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213049 | Solution to address KI#1 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213050 | Conclusion to KI 1.3 | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | imported from 3GU |
S3‑213051 | Evaluation to the Solution 11 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213052 | Ed Note Removal to include mechanism when notification sent via MFAF for Solution 11 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213053 | Sol 1 NFp verification – EN resolutions and evaluation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213054 | SCP authorization | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213055 | Access token request for NF Set – EN resolution | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213056 | Access token request for NF Set – RFC clarification | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213057 | KI and solution to NRF deployments | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213058 | EN resolution on trust model for SCP | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213059 | TR 33.847 Update for solution #10 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑213060 | TR 33.847 Update for solution #24 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑213061 | Way forward SID eSBA | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213062 | TR 33.847 Update for solution #25 | InterDigital, Europe, Ltd. | imported from 3GU |
S3‑213063 | Conclusions for U2N relay Key Issues | InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon , Qualcomm Incorporated, MITRE, AT&T, Ericsson | imported from 3GU |
S3‑213064 | Adding Evaluation to Solution#4 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213065 | A new onboarding solution addressing KI#2 | Lenovo, Motorola Mobility | imported from 3GU |
S3‑213066 | Further conclusions for KI #1 | CableLabs,Ericsson, Charter Communications, Intel | imported from 3GU |
S3‑213067 | Editorial corrections to the UAS TR | Qualcomm Incorporated | imported from 3GU |
S3‑213068 | Resolution of EN in solutions | Qualcomm Incorporated | imported from 3GU |
S3‑213069 | Cover sheet | Qualcomm Incorporated | imported from 3GU |
S3‑213070 | Updates to solution 14: Removal of Editor’s notes: Security Issues | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑213071 | User consent: New key issue on naming of purposes | NTT DOCOMO INC. | imported from 3GU |
S3‑213072 | Draft TR 33.864 v0.6.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | Ericsson Hungary Ltd | imported from 3GU |
S3‑213073 | Updates to terminology in the architecture assumptions | Ericsson | imported from 3GU |
S3‑213074 | Update and evaluation of solution #32 | Philips International B.V. | imported from 3GU |
S3‑213075 | TR 33.881 revision for NSWO | Nokia Corporation | imported from 3GU |
S3‑213076 | Evaluation of Solution #34 | Qualcomm Incorporated | imported from 3GU |
S3‑213077 | Update of Solution #12 | Qualcomm Incorporated | imported from 3GU |
S3‑213078 | Conclusion for the KI#2 | Qualcomm Incorporated | imported from 3GU |
S3‑213079 | Add conclusion to KI #6 | China Mobile, Lenovo, Motorola Mobility, InterDigital, Europe, Ltd., Qualcomm Incorporated, Huawei, HiSilicon | imported from 3GU |
S3‑213080 | TR 33.850 for 5MBS security | Huawei, Hisilicon | imported from 3GU |
S3‑213081 | Update to Solution #5 | ZTE Corporation | imported from 3GU |
S3‑213082 | New solution on control plane based provisioning PS to AUSF | ZTE Corporation | imported from 3GU |
S3‑213083 | Update for Conclusion on Key Issue #4 | China Telecommunications, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213084 | Add the evaluation of the solution #6 | ZTE Corporation | imported from 3GU |
S3‑213085 | Update the solution #6 | ZTE Corporation | imported from 3GU |
S3‑213086 | Update the solution #11 | ZTE Corporation | imported from 3GU |
S3‑213087 | Evaluation for sol#13 | LG Electronics Inc. | imported from 3GU |
S3‑213088 | Updates on sol#13 | LG Electronics Inc. | imported from 3GU |
S3‑213089 | LS on EAS and ECS identifiers | Ericsson | imported from 3GU |
S3‑213090 | Update to Solution #17: Resolving ENs | Ericsson | imported from 3GU |
S3‑213091 | Solution to KI#1 (Support of EAP-AKA’ authentication for NSWO) using credentials retrieved from UDM | Ericsson | imported from 3GU |
S3‑213092 | pCR to TR33.847- Conclusion of KI#3 | CATT | imported from 3GU |
S3‑213093 | pCR to TR33.847- Conclusion of KI#13 | CATT | imported from 3GU |
S3‑213094 | draft TR 33.866 0.6.0 | China Mobile Com. Corporation | imported from 3GU |
S3‑213095 | New Solution for Check of User Consent for 3GPP service Exposure | Huawei, HiSilicon | imported from 3GU |
S3‑213096 | General Conclusion on UDM service for User Consent Check | Huawei, HiSilicon | imported from 3GU |
S3‑213097 | General Conclusion on Generic Requirement for the Procedures for User Consent Check | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213098 | General Conclusion on UDM service for User Consent Revocation | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericssion | imported from 3GU |
S3‑213099 | General Conclusion on Generic Requirement for the Procedure for User Consent Revocation | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213100 | Solution for user consent revocation | Huawei, HiSilicon | imported from 3GU |
S3‑213101 | Solution Update and Evaluation for Solution 3 | Huawei, HiSilicon | imported from 3GU |
S3‑213102 | Conclusion for Key Issue #2 | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericssion | imported from 3GU |
S3‑213103 | Conclusion for Key Issue #3 | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213104 | addressing the EN in solution#12 | Huawei, HiSilicon | imported from 3GU |
S3‑213105 | conclusion to KI#2 | Huawei, HiSilicon, CATT | imported from 3GU |
S3‑213106 | conclusion to KI#5 to KI#8 | Huawei, HiSilicon, ZTE Corporation, CATT, Xiaomi Technology | imported from 3GU |
S3‑213107 | Resolve EN in Sol#27 | Huawei, HiSilicon | imported from 3GU |
S3‑213108 | Resolve EN in Sol#28 | Huawei, HiSilicon | imported from 3GU |
S3‑213109 | Add conclusion to Key Issue #1 | Huawei, HiSilicon, ZTE Corporation, CATT, Qualcomm Incorporated | imported from 3GU |
S3‑213110 | New solution to avoid policy mismatch | Huawei, HiSilicon | imported from 3GU |
S3‑213111 | New solution on UE-to-network relay Key management based on primary authentication | Huawei,HiSilicon | imported from 3GU |
S3‑213112 | Resolving the EN about the multiple EECs issues in solution 8 | Huawei,HiSilicon | imported from 3GU |
S3‑213113 | add evaluation for solution#3 | Huawei, HiSilicon, China Mobile | imported from 3GU |
S3‑213114 | draft TR 33.862 0.6.0 | China Mobile Com. Corporation | imported from 3GU |
S3‑213115 | TR 33.839for Edge computing security | Huawei, HiSilicon | imported from 3GU |
S3‑213116 | EN romoval for solution#23 | Huawei, HiSilicon | imported from 3GU |
S3‑213117 | EC : Conclusion for Key issue #7 | Huawei, HiSilicon, Ericsson, ZTE | imported from 3GU |
S3‑213118 | EC: Conclusion for Key issue #1 | Huawei, HiSilicon | imported from 3GU |
S3‑213119 | EC: Conclusion for Key issue #2 | Huawei, HiSilicon | imported from 3GU |
S3‑213120 | New Key issue on authorization mechanism negotiation | Huawei, HiSilicon; China Mobile | imported from 3GU |
S3‑213121 | New solution for the authorization mechanism negotiation | Huawei, HiSilicon; China Mobile | imported from 3GU |
S3‑213122 | Requirement of subscribe-notification key issue | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | imported from 3GU |
S3‑213123 | Conclusion on authentication and authorization for multicast service | Huawei, HiSilicon | imported from 3GU |
S3‑213124 | Conclusion on key issue #1.2 | Huawei, HiSilicon, China Mobile | imported from 3GU |
S3‑213125 | Conclusion on key issue #3.2 on protection of UE data in transit | Huawei, HiSilicon, China Mobile | imported from 3GU |
S3‑213126 | Evaluation Solution 9 | Philips International B.V. | imported from 3GU |
S3‑213127 | Update Solution 11 for reduced key update overhead | Philips International B.V. | imported from 3GU |
S3‑213128 | Reply LS on Layer-3 UE-to-Network Relay authentication and authorization | CATT | imported from 3GU |
S3‑213129 | Draft TR 33.847 v0.7.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | CATT | imported from 3GU |
S3‑213130 | Conclusion to KI#3 (TPAE AA) | Huawei, HiSilicon, InterDigital Europe Ltd., Qualcomm Incorporated | imported from 3GU |
S3‑213131 | [EDGE] Update to Solution#3 | Samsung | imported from 3GU |
S3‑213132 | Conclusion to KI#5 (privacy of UAS identities) | Huawei, HiSilicon, InterDigital Europe Ltd., Qualcomm Incorporated | imported from 3GU |
S3‑213133 | Update to KI#1 (NSSAI analysis) | Huawei, HiSilicon | imported from 3GU |
S3‑213134 | New KI on DoS to NSAC procedure | Huawei, HiSilicon | imported from 3GU |
S3‑213135 | [EDGE] Update to evaluation of Solution#3 | Samsung | imported from 3GU |
S3‑213136 | [MBS] Solution#13 Evaluation | Samsung | imported from 3GU |
S3‑213137 | [ProSe] Updates to Solution#1 | Samsung | imported from 3GU |
S3‑213138 | [ProSe] Updates to evaluation of solution#1 | Samsung | imported from 3GU |
S3‑213139 | KI on Authorization for Inter-Slice Access | Samsung | imported from 3GU |
S3‑213140 | New KI on AF authentication and authorization | Huawei, HiSilicon | imported from 3GU |
S3‑213141 | Update on Solution 6 | Samsung | imported from 3GU |
S3‑213142 | Evaluation for solution 1 | Samsung | imported from 3GU |
S3‑213143 | Evaluation for solution 5 | Samsung | imported from 3GU |
S3‑213144 | Solution on AF authorization | Huawei, HiSilicon | imported from 3GU |
S3‑213145 | draft TR 33.874-030 | Huawei; HiSilicon | imported from 3GU |
S3‑213146 | Draft TR 33.867 | Huawei; HiSilicon | imported from 3GU |
S3‑213147 | Update to solution #19 – Authorization added. | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213148 | Draft TR 33.854 | Qualcomm | imported from 3GU |
S3‑213149 | LS on 256-bit algorithms based on ZUC-256 | CAICT | imported from 3GU |
S3‑213150 | Reply to LS on broadcast of NTN GW or gNB position | Ericsson Hungary Ltd | imported from 3GU |
S3‑213151 | Update_on_Key_issue#1.4 | Ericsson | imported from 3GU |
S3‑213152 | Update_on_Key_issue#1.4 | Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213153 | Update_on_Solution#12 | Ericsson | imported from 3GU |
S3‑213154 | Update_on_Solution#5 | Ericsson, Lenovo, Motorola Mobility | imported from 3GU |
S3‑213155 | Cleanup MUSIM TR | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑213156 | Key issue on security aspects of Paging Cause | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑213157 | conclusion to KI#5 to KI#8 | Huawei, HiSilicon, ZTE Corporation, CATT, Xiaomi Technology | imported from 3GU |
S3‑213158 | ProSe: Addional Evaluation for Solution #10 | Xiaomi Technology | imported from 3GU |
S3‑213159 | ProSe: Addional Evaluation for Solution #15 | Xiaomi Technology | imported from 3GU |
S3‑213160 | ProSe: Addional Evaluation for Solution #18 | Xiaomi Technology | imported from 3GU |
S3‑213161 | ProSe: Add Evaluation for Solution #27 | Xiaomi Technology | imported from 3GU |
S3‑213162 | ProSe: Add Evaluation for Solution #28 | Xiaomi Technology | imported from 3GU |
S3‑213163 | ProSe: Conclusion for Key Issue #16 | Xiaomi Technology | imported from 3GU |
S3‑213164 | ProSe: New Solution for Key Issue #17 | Xiaomi Technology | imported from 3GU |
S3‑213165 | ProSe: New Solution for Key Issue #3 | Xiaomi Technology | imported from 3GU |
S3‑213166 | Requirement of subscribe-notification key issue | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | imported from 3GU |
S3‑213167 | Draft TR 33.875 | Nokia Germany | imported from 3GU |
S3‑213168 | LS Reply to SA3 on security protection on RRCResumeRequest message | R2-2109121 | imported from 3GU |
S3‑213169 | Reply LS on Storage of KAUSF | C1-214800 | imported from 3GU |
S3‑213170 | LS on Home Network triggered re-authentication | Samsung R&D Institute UK | imported from 3GU |
S3‑213171 | LS on use of 4G algorithm identifier in NR-PDCP for UP IP | Huawei Technologies Sweden AB | imported from 3GU |
S3‑213172 | Reply LS on Storage of KAUSF | Samsung R&D Institute UK | imported from 3GU |
S3‑213173 | Conclusion on Key issue #3.2 SUPI guessing attacks | Nokia, Nokia Shanghai Bell, Thales, NTT DOCOMO, NEC | imported from 3GU |
S3‑213174 | LS on proposed NSWO architecture | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213175 | New solution: Keying procedures for Group Member and Relay discovery: public safety case | MITRE Corporation | imported from 3GU |
S3‑213176 | Update to KI #17 | MITRE Corporation | imported from 3GU |
S3‑213177 | OAuth2.0 misalignmnet | Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | imported from 3GU |
S3‑213178 | OAuth2.0 misalignmnet | Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility | imported from 3GU |
S3‑213179 | [33.180] R17 Group subscription | Motorola Solutions Danmark A/S | imported from 3GU |
S3‑213180 | Mirror for Rel-16 Editorial Clarifications for Trusted non-3GPP Access using TNGF | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑213181 | Way forward for U2N Relay authentication and authorization | CATT | imported from 3GU |
S3‑213182 | New KI on Secrets in Container Images | Altiostar | imported from 3GU |
S3‑213183 | SCAS_5G_IPUPS: New threats to IPUPS to TR 33.926 | ZTE Corporation | imported from 3GU |
S3‑213184 | SCAS_5G_IPUPS: New test cases of IPUPS to TS 33.513 | ZTE Corporation | imported from 3GU |
S3‑213185 | LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213186 | Correction of message name in SMF | Keysight Technologies UK Ltd | imported from 3GU |
S3‑213187 | eCryptPr 02 CR 33.203 R17 Security updates for algorithms and protocols | Ericsson | imported from 3GU |
S3‑213188 | New KI on Container breakouts | Altiostar | imported from 3GU |
S3‑213189 | OAuth misalignment - R17 | Nokia, Nokia Shanghai Bell, Ericsson, AT&T, Interdigital, Xiaomi, HPE, Lenovo, Motorola Mobility, Mavenir, Huawei, HiSilicon, Deutsche Telekom AG, China Mobile, CableLabs, Verizon, Samsung | imported from 3GU |
S3‑213190 | New KI on Container breakouts | Altiostar | imported from 3GU |
S3‑213191 | Clarification on Kausf storage in multi-NAS connection | Huawei, HiSilicon | imported from 3GU |
S3‑213192 | Reply LS on Misalignment on usage of OAuth within 3GPP 29.510 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213193 | Reply LS on OAuth2 misalignments between SA3 and CT4 specifications | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213194 | Clarification on Kausf storage in multi-NAS connection | Huawei, HiSilicon | imported from 3GU |
S3‑213195 | Clarification on Kausf storage in multi-NAS connection | Huawei, HiSilicon | imported from 3GU |
S3‑213196 | NRF service definition R15 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213197 | NRF service definition R16 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213198 | Alignment for Oauth2.0 validation R15 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213199 | NRF service definition R17 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213200 | Clarification on AMF transparency for UPU | Ericsson | imported from 3GU |
S3‑213201 | Change request to living document: Key hierarchy | Ericsson | imported from 3GU |
S3‑213202 | Draft TR 33.848 | BT plc | imported from 3GU |
S3‑213203 | Change request to living document: EAP flow | Ericsson | imported from 3GU |
S3‑213204 | Security aspects of eNPN (skeleton for living document) | Ericsson | imported from 3GU |
S3‑213205 | Change request to living document: Credentials holder using AUSF and UDM for primary authentication | Ericsson | imported from 3GU |
S3‑213206 | Security aspects of eNPN (living document) | Ericsson, Huawei, HiSilicon | imported from 3GU |
S3‑213207 | Living document for BEST_5G: draftCR to TS 33.163 | KPN N.V. | imported from 3GU |
S3‑213208 | draft TR 33.857 v0.7.0 | Ericsson | imported from 3GU |
S3‑213209 | Reply LS to GSMA on prevention of attacks on sliced core network | CableLabs, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
S3‑213210 | Short-lived public key-based solution for KI#2 | CableLabs,Deutsche Telekom AG, InterDigital, Johns Hopkins University APL, US National Security Agency | imported from 3GU |
S3‑213211 | pCR to 33.839: solution #26 | THALES | imported from 3GU |
S3‑213212 | pCR to 33.839: solution #27 | THALES | imported from 3GU |
S3‑213213 | SCAS_5G_IPUPS: New threats to IPUPS to TR 33.926 | ZTE Corporation | imported from 3GU |
S3‑213214 | SCAS_5G_IPUPS: New test cases of IPUPS to TS 33.513 | ZTE Corporation | imported from 3GU |
S3‑213215 | LS on SBA for GBA | Ericsson | imported from 3GU |
S3‑213216 | New solution proposal | JSRPC Kryptonite | imported from 3GU |
S3‑213217 | New solution: Hardware Mediated Execution Enclave (HMEE) | MITRE Corporation | imported from 3GU |
S3‑213218 | Reply LS for clarification on managing expired or multiple Protection Scheme and Home Network keys used for SUCI calculation. | NTT DOCOMO INC. | imported from 3GU |
S3‑213219 | Overview on UAV authentication and authorization (UUAA) | Huawei, HiSilicon, Qualcomm, InterDigital, Lenovo, Motorola Mobility | imported from 3GU |
S3‑213220 | UAV location information verification | Huawei, HiSilicon, Qualcomm Incorporated, InterDigitalal | imported from 3GU |
S3‑213221 | UP Security Activation Mechanism in LTE | Huawei, HiSilicon | imported from 3GU |
S3‑213222 | Clarification on UP IP indication based on RAN3 LS | Huawei, HiSilicon | imported from 3GU |
S3‑213223 | New WID for UC3S | Huawei, HiSilicon, China Mobile, China Unicom, China Telecom, Nokia, Nokia Shanghai Bell, FutureWei | imported from 3GU |
S3‑213224 | Update to clause 7.02 | Huawei, HiSilicon | imported from 3GU |
S3‑213225 | TS 33.558: Security requirements | Huawei, HiSilicon | imported from 3GU |
S3‑213226 | TS 33.558: Security for the EDGE interfaces | Huawei, HiSilicon | imported from 3GU |
S3‑213227 | draft TS 33.558: Edge computing security | Huawei, HiSilicon | imported from 3GU |
S3‑213228 | Adding for NSSAAF network product class description and assets and critical assets | Huawei, HiSilicon | imported from 3GU |
S3‑213229 | New threat related to unauthorized slice-specific authorization revocatoinsue #1.2 | Huawei, HiSilicon | imported from 3GU |
S3‑213230 | New service on 5G GBA AV | Huawei, HiSilicon, Ericsson, Thales | imported from 3GU |
S3‑213231 | Clarification on UP IP indication based on RAN3 LS | Huawei, HiSilicon | imported from 3GU |
S3‑213232 | New WID on security aspects of eNA | China Mobile | imported from 3GU |
S3‑213233 | Draft TR 33.846 v0.13.0 Study on authentication enhancements in the 5G System (5GS) | Ericsson Hungary Ltd | imported from 3GU |
S3‑213234 | New service on 5G GBA AV | Huawei, HiSilicon, Ericsson, Thales | imported from 3GU |
S3‑213235 | roaming-related security mechanisms | Huawei, HiSilicon | imported from 3GU |
S3‑213236 | New WID on Security Aspects of Proximity based Services (ProSe) in the 5G | CATT | imported from 3GU |
S3‑213237 | Editorial Clarifications for Trusted non-3GPP Access using TNGF | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑213238 | 5GFBS-Update of solution#17 | Apple, CableLabs, Intel | imported from 3GU |
S3‑213239 | CR on TS 33.501 on the security context handling in IRAT | Apple | imported from 3GU |
S3‑213240 | FBS - Clarification quantum-resistance | Philips International B.V. | imported from 3GU |
S3‑213241 | Clarification in Solution 4 | Philips International B.V. | imported from 3GU |
S3‑213242 | FBS - Evaluation Solution 23 | Philips International B.V. | imported from 3GU |
S3‑213243 | FBS - Evaluation Solution 24 | Philips International B.V. | imported from 3GU |
S3‑213244 | TR 33.809-5GFBS | Apple Computer Trading Co. Ltd | imported from 3GU |
S3‑213245 | Living document for GBA_5G: draftCR to TS 33.220: SBA support for Zh and Zn interfaces | Ericsson | imported from 3GU |
S3‑213246 | Living document for GBA_5G: draftCR to TS 33.223: SBA support for Zpn | Ericsson | imported from 3GU |
S3‑213247 | Draft TS 33.326 | Huawei, HiSilicon | imported from 3GU |
S3‑213248 | Coversheet for TS 33.326 | Huawei, Hisilicon | imported from 3GU |
S3‑213249 | A new testcase to NSSAAF SCAS | Huawei, HiSilicon | imported from 3GU |
S3‑213250 | Clarification on AS key generation after runing NAS SMC | Huawei, HiSilicon | imported from 3GU |
S3‑213251 | CR to 33.926 threat analysis on select AAA-P and AAA-S | Huawei, HiSilicon | imported from 3GU |
S3‑213252 | Clarification on AAnF selection | Huawei, HiSilicon | imported from 3GU |
S3‑213253 | User Plane Integrity Protection Policy Handling in EN-DC | Ericsson | imported from 3GU |
S3‑213254 | User Plane Integrity Protection Policy Handling in IW handover from 5GS to EPS | Ericsson | imported from 3GU |
S3‑213255 | User Plane Integrity Protection Policy Handling in DC | Ericsson | imported from 3GU |
S3‑213256 | User Plane Integrity Protection Policy Handling in IW handover from EPS to 5GS | Ericsson | imported from 3GU |
S3‑213257 | Clarification on Data Masking on Integration Analysis | China Mobile | imported from 3GU |
S3‑213258 | LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated | imported from 3GU |
S3‑213259 | Updates to solution #17 capability negotiation | Intel Corporation (UK) Ltd | imported from 3GU |
S3‑213260 | Draft TS 33.256 | Qualcomm CDMA Technologies | imported from 3GU |
S3‑213261 | Rel16 Align KAUSF handling for 5G AKA and EAP-AKA' | Ericsson | imported from 3GU |
S3‑213262 | Rel17 Align KAUSF handling for 5G AKA and EAP-AKA' for Release 17 | Ericsson | imported from 3GU |
S3‑213263 | pCR to Living doc on addition of 5G to BEST - addition of EMSDP updates | VODAFONE Group Plc | imported from 3GU |
S3‑213264 | Security updates for algorithms and protocols for 33.310 | Ericsson | imported from 3GU |
S3‑213265 | Security updates for algorithms and protocols for 33.210 | Ericsson | imported from 3GU |
S3‑213266 | Living CR for UPIP for LTE | Vodafone | imported from 3GU |
S3‑213267 | Response LS on 256-bit algorithms based on SNOW 3G or SNOW V | VODAFONE Group Plc | imported from 3GU |
S3‑213268 | Add step 4 in annex B.1.2.2 | ZTE Corporation | imported from 3GU |
S3‑213269 | Draft_skeleton_for_draft_CR_eNA_SEC | China Mobile | imported from 3GU |
S3‑213270 | Living document for 5BMS | Huawei | imported from 3GU |
S3‑213271 | Reply-LS on security aspects for the method of collection of data from the UE | Guangdong OPPO Mobile Telecom. | imported from 3GU |
S3‑213272 | LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated | imported from 3GU |
page generated from database: 2024-04-22 07:58:53