Please enter the search related information in the fields below. Partial information works, e.g. "SP-21
" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501
" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP
" gives the same results as "3gpp
".
Download results in JSON format
tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
---|---|---|---|---|---|---|---|---|---|
S3-202300 | Agenda |
agenda revised to S3-202352 |
SA WG3 Chair |
S3-100-bis-e AI: 1 |
revised | [WTS] [JSN] | |||
S3-202301 | Process for SA3#100Bis-e meeting | other | SA WG3 Chair |
S3-100-bis-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-202302 | Skeleton of TR 33.866 | pCR | China Mobile | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.14 |
withdrawn | [WTS] [JSN] |
S3-202303 | Scope for TR 33.866 | pCR | China Mobile | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202304 | Skeleton for TR 33.862 | draft TR | China Mobile | FS_SEC_5GMSG | Rel-17 |
S3-100-bis-e AI: 2.15 |
approved | [WTS] [JSN] | |
S3-202305 | Evaluation of Solution 2 |
pCR revised to S3-202675 |
NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
revised | [WTS] [JSN] |
S3-202306 | Evaluation of Solution 3 |
pCR revised to S3-202676 |
NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
revised | [WTS] [JSN] |
S3-202307 | Evaluation of Solution 4 |
pCR revised to S3-202677 |
NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
revised | [WTS] [JSN] |
S3-202308 | New solution for KI2: Storage of LTK in UDR |
pCR revised to S3-202680 |
NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
revised | [WTS] [JSN] |
S3-202309 | Skeleton for TR 33.866 |
draft TR revised to S3-202674 |
China Mobile | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
revised | [WTS] [JSN] | |
S3-202310 | Skeleton of TR 33.864 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson Hungary Ltd | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
approved | [WTS] [JSN] | |
S3-202311 | New Solution for KI3: Transfer of LTK between UDR and UDM/ARPF | pCR | NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202312 | New KI for TR 33.847 – privacy of identities for UE2N path switch | pCR | InterDigital Communications, CableLabs | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202313 | evaluation of solution 2.1 | pCR | ZTE Corporation | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202314 | Security requirement of SUCI replay | pCR | ZTE Corporation | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202315 | update solution 4.3 | pCR | ZTE Corporation | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202316 | update solution 4.4 | pCR | ZTE Corporation | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202317 | Solution of Mitigation against the SUPI replay attack | pCR | ZTE Corporation | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202318 | NEF discovers AUSF in solution 2 of TR33.839 | pCR | ZTE Corporation | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202319 | Derivation of Kedge ID in UE | pCR | ZTE Corporation | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202320 | Add some references and abbrevations | pCR | ZTE Corporation | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202321 | Clean up | pCR | ZTE Corporation | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202322 | New solution for key issue 6 Edge3 protection | pCR | ZTE Corporation | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
merged | [WTS] [JSN] |
S3-202323 | New solution for key issue 6 type B interface protection | pCR | ZTE Corporation | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
merged | [WTS] [JSN] |
S3-202324 | New solution for key issue #1 |
pCR revised to S3-202739 |
ZTE Corporation | 33.851 0.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202325 | Updates to key issue #1 Credentials owned by an external entity | pCR | ZTE Corporation | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202326 | Reply LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN |
LS out LS is reply to S2-2004385 LS To: SA2 |
ZTE Corporation | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] | |
S3-202327 | New key issue on UE onboarding for SNPN | pCR | ZTE Corporation | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
merged | [WTS] [JSN] |
S3-202328 | Reply LS on on-boarding and remote provisioning |
LS out LS is reply to S2-2005949 LS To: SA2 |
ZTE Corporation | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] | |
S3-202329 | Security requirements on AMF re-allocation | pCR | ZTE Corporation | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202330 | Scope for TR 33.840 |
pCR revised to S3-202660 |
China Telecom, Huawei, HiSilicon, CATT, Nokia, Nokia Shanghai Bell | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
revised | [WTS] [JSN] |
S3-202331 | key issue on security configuration differentiation in CU-UPs | pCR | China Telecom | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
noted | [WTS] [JSN] |
S3-202332 | New Key Issue on Provisioning of PNI-NPN credentials |
pCR revised to S3-202748 |
Huawei, Hisilicon, Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202333 | Clarification on Key Issue #2 |
pCR revised to S3-202749 |
Huawei, Hisilicon, Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202334 | New Solution for Network Access Authentication with Credentials owned by an AAA external to the SNPN |
pCR revised to S3-202750 |
Huawei, Hisilicon | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202335 | New Key Issue on Secure Connection Establishment for UE Onboarding for SNPN | pCR | Huawei, Hisilicon | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
withdrawn | [WTS] [JSN] |
S3-202336 | Reply LS on security issue for on-boarding and remote provisioning |
LS out LS To: SA2 revised to S3-202751 |
Huawei, Hisilicon |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] | |||
S3-202337 | System Information Protection using SNPN Credentials | pCR | Huawei, Hisilicon | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202338 | Skeleton of User Consent for 3GPP services |
pCR revised to S3-202752 |
Huawei, Hisilicon | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
revised | [WTS] [JSN] |
S3-202339 | Scope of User Consent for 3GPP Services | pCR | Huawei, Hisilicon | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
noted | [WTS] [JSN] |
S3-202340 | Comparison with TR 33.849 | pCR | Huawei, Hisilicon | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
noted | [WTS] [JSN] |
S3-202341 | New Key Issue on Enabling User Consent for NF service consumption | pCR | Huawei, Hisilicon | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
noted | [WTS] [JSN] |
S3-202342 | New Key Issue on Enabling User Consent for NF capability exposure | pCR | Huawei, Hisilicon | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
noted | [WTS] [JSN] |
S3-202343 | Reply LS for IP address to GPSI translation |
LS out LS To: SA6 revised to S3-202753 |
Huawei, Hisilicon |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] | |||
S3-202344 | Clarification for Solution 11 | pCR | Huawei, Hisilicon | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
approved | [WTS] [JSN] |
S3-202345 | Update ot KI#6 | pCR | Huawei, Hisilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202346 | New key issue on security of one-to-one communication over PC5 |
pCR revised to S3-202754 |
Huawei, Hisilicon | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202347 | New solution on security establishment of one-to-one PC5 communication |
pCR revised to S3-202755 |
Huawei, Hisilicon | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202348 | New solution on Authentication between EEC and EES |
pCR revised to S3-202756 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202349 | New solution on Authentication between EEC and ECS |
pCR revised to S3-202757 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202350 | update to KI#10 User's consent for exposure of information to Edge Applications | pCR | Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
withdrawn | [WTS] [JSN] |
S3-202351 | New solution on Security of Network Information Provisioning to Local Applications |
pCR revised to S3-202759 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202352 | Agenda |
agenda revision of S3-202300 revised to S3-202397 |
SA WG3 Chair |
S3-100-bis-e AI: 1 |
revised | [WTS] [JSN] | |||
S3-202353 | LS on ETSI Plugtest reports | LS in | C1-204693 |
S3-100-bis-e AI: 4 |
noted | [WTS] [JSN] | |||
S3-202354 | LS on mandatory support of full rate user plane integrity protection for 5G | LS in | C1-205392 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] | |||
S3-202355 | Reply LS on N32-f Error Responses – Mapping | LS in | C4-204391 |
S3-100-bis-e AI: 4 |
noted | [WTS] [JSN] | |||
S3-202356 | Reply LS on N32-f Protection Policy IE Data-Type Mapping | LS in | C4-204392 |
S3-100-bis-e AI: 4 |
noted | [WTS] [JSN] | |||
S3-202357 | Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G | LS in | R2-2008643 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] | |||
S3-202358 | LS on propagation of user consent related information during Xn inter-PLMN handover | LS in | R3-204378 |
S3-100-bis-e AI: 2.14 |
postponed | [WTS] [JSN] | |||
S3-202359 | Reply LS on mandatory support of full rate user plane integrity protection for 5G | LS in | R3-205653 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] | |||
S3-202360 | LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN | LS in | S2-2004385 |
S3-100-bis-e AI: 2.12 |
postponed | [WTS] [JSN] | |||
S3-202361 | LS on user consent requirements for analytics |
LS in LS reply in S3-202789 |
S2-2004560 |
S3-100-bis-e AI: 2.16 |
replied to | [WTS] [JSN] | |||
S3-202362 | Reply LS on AS rekeying handling | LS in | S2-2005909 |
S3-100-bis-e AI: 4 |
noted | [WTS] [JSN] | |||
S3-202363 | LS on security issue for on-boarding and remote provisioning |
LS in LS reply in S3-202751, S3-202751 |
S2-2005949 |
S3-100-bis-e AI: 2.12 |
replied to | [WTS] [JSN] | |||
S3-202364 | LS on checking security issue for Solution 22 in TR 23.748 |
LS in LS reply in S3-202570, S3-202570, S3-202678 |
S2-2006033 |
S3-100-bis-e AI: 2.8 |
replied to | [WTS] [JSN] | |||
S3-202365 | Reply LS on Updated User Plane Integrity Protection advice | LS in | S2-2006180 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] | |||
S3-202366 | LS on mandatory support of full rate user plane integrity protection for 5G | LS in | S2-2006181 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] | |||
S3-202367 | LS on method for collection of data from the UE | LS in | S2-2006292 |
S3-100-bis-e AI: 2.16 |
postponed | [WTS] [JSN] | |||
S3-202368 | LS on security issues for 5G ProSe |
LS in LS reply in S3-202689, S3-202689 |
S2-2006589 |
S3-100-bis-e AI: 2.9 |
replied to | [WTS] [JSN] | |||
S3-202369 | Reply LS on the user consent for trace reporting | LS in | S5-204542 |
S3-100-bis-e AI: 2.14 |
noted | [WTS] [JSN] | |||
S3-202370 | LS on IP address to GPSI translation |
LS in LS reply in S3-202753, S3-202753 |
S6-200947 |
S3-100-bis-e AI: 2.8 |
replied to | [WTS] [JSN] | |||
S3-202371 | Re LS on Accreditation for Virtualised Network Products (VNPs) | LS in | GSMA SECAG |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] | |||
S3-202372 | LS on Misalignments on HTTP message format over N32-f | LS in | C4-204409 |
S3-100-bis-e AI: 4 |
postponed | [WTS] [JSN] | |||
S3-202373 | Reply LS to SA3 on FBS detection | LS in | R2-1914224 |
S3-100-bis-e AI: 2.1 |
postponed | [WTS] [JSN] | |||
S3-202374 | Reply to LS on Resynchronisations | LS in | ETSI SAGE |
S3-100-bis-e AI: 2.5 |
postponed | [WTS] [JSN] | |||
S3-202375 | Solution for authorization and security with UE-to-Network relay using Remote | pCR | InterDigital Communications | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
withdrawn | [WTS] [JSN] |
S3-202376 | New KI for TR 33.847 – privacy of identities for UE2UE Relay path switch | pCR | InterDigital Communications, CableLabs | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202377 | New KI for TR 33.847 – security for UE2N path switch |
pCR revised to S3-202705 |
InterDigital Communications, CableLabs | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202378 | New KI for TR 33.847 – security for UE2UE Relay path switch |
pCR revised to S3-202706 |
InterDigital Communications, CableLabs | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202379 | TR 33.847 - New key issue on security protection misalignment in L3 UE2NW relay | pCR | LG Electronics Inc. | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202380 | TR 33.847 - Solution for handling security policy misalignment over ProSe L3 UE2NW relay | pCR | LG Electronics Inc. | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202381 | TR 33.847 - KI on authorization for UE2NW relay | pCR | LG Electronics Inc. | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202382 | TR 33.866 - new KI on user consent for NWDAF | pCR | LG Electronics Inc. | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202383 | Reply LS to RAN2 on FBS detection |
LS out LS is reply to RAN2 LS To: RAN2 |
Huawei, HiSilicon | FS_5GFBS | Rel-17 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] | |
S3-202384 | Discussion paper for Rel17 SID on network slicing security | discussion | Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT, China Unicom, China Mobile | Rel-17 |
S3-100-bis-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-202385 | Rel17 SID on network slice security | SID new | Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT, China Unicom, China Mobile | Rel-17 |
S3-100-bis-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-202386 | A solution to UAV/UAV-C pairing authorization | pCR | Huawei, HiSilicon, InterDigital | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202387 | A solution to TPAE authentication and authorization | pCR | Huawei, HiSilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202388 | A solution to C2 communication security | pCR | Huawei, HiSilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202389 | A solution to RID information protection | pCR | Huawei, HiSilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202390 | A solution to UAS ID privacy protection | pCR | Huawei, HiSilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202391 | Addressing EN in Sol1 on UAS registration IE | pCR | Huawei, HiSilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202392 | Addressing EN in Sol1 on UAS registration Accept |
pCR revised to S3-202692 |
Huawei, HiSilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
revised | [WTS] [JSN] |
S3-202393 | New key issue on groupcast security |
pCR revised to S3-202763 |
Huawei, HiSilicon | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202394 | New key issue on authentication and authorization | pCR | Huawei, HiSilicon | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202395 | New KI - Operator control of ProSe direct communication | pCR | KPN | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202396 | Reply LS on user consent requirements for analytics |
LS out LS is reply to S3-202361 source LS: S2-2004560 LS To: SA WG2 revised to S3-202789 |
Nokia | Rel-17 |
S3-100-bis-e AI: 2.16 |
revised | [WTS] [JSN] | ||
S3-202397 | Agenda |
agenda revision of S3-202352 |
SA WG3 Chair |
S3-100-bis-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-202398 | LS on the stage 2 aspects of MINT | LS in | C1-205332 |
S3-100-bis-e AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-202399 | LS on System support for Multi-USIM devices | LS in | S2-2006011 |
S3-100-bis-e AI: 2.18 |
postponed | [WTS] [JSN] | |||
S3-202400 | LS on System support for Multi-USIM devices |
LS in LS reply in S3-202687, S3-202687 |
S2-2006037 |
S3-100-bis-e AI: 2.18 |
replied to | [WTS] [JSN] | |||
S3-202401 | LS on ATSSS Phase 2 Requirements to IETF QUIC Working Group | LS in | S2-2006331 |
S3-100-bis-e AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-202402 | LS on study items for security on management aspect |
LS in LS reply in S3-202688, S3-202688 |
S5-204407 |
S3-100-bis-e AI: 2.18 |
replied to | [WTS] [JSN] | |||
S3-202403 | New KI - UE identity protection during ProSe discovery |
pCR revised to S3-202673 |
KPN N.V. | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202404 | New solution for KI4 - Encrypted storage of OPc in UDR |
pCR revised to S3-202671 |
KPN N.V. | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
revised | [WTS] [JSN] |
S3-202405 | New solution for KI5 - Encrypted transfer of OPc out of UDR | pCR | KPN N.V. | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202406 | New solution for KI6 - Encrypted storage of OP in UDR |
pCR revised to S3-202672 |
KPN N.V. | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
revised | [WTS] [JSN] |
S3-202407 | New solution for KI7 - Encrypted transfer of OP out of UDR | pCR | KPN N.V. | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202408 | Draft LS reply to SA WG2 LS on security issues for 5G ProSe |
LS out LS To: SA2 |
CATT |
S3-100-bis-e AI: 2.9 |
merged | [WTS] [JSN] | |||
S3-202409 | pCR to TR33.847- Reuse LTE security mechanism for 5G ProSe open discovery |
pCR revised to S3-202773 |
CATT | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202410 | pCR to TR33.847- Reuse LTE security mechanism for 5G ProSe restricted discovery |
pCR revised to S3-202774 |
CATT | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202411 | pCR to TR33.847- Key Issue on security of one-to-many communications | pCR | CATT | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
merged | [WTS] [JSN] |
S3-202412 | pCR to TR33.847- Group communication for commercial services | pCR | CATT | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202413 | New KI for TR 33.847 – security for support of Non-IP traffic |
pCR revised to S3-202708 |
InterDigital Communications | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202414 | New KI for TR 33.847 – privacy of ProSe entities while supporting Non-IP traffic |
pCR revised to S3-202713 |
InterDigital Communications | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202415 | Solution for UAV A&A during registration |
pCR revised to S3-202702 |
InterDigital, Europe, Ltd. | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
revised | [WTS] [JSN] |
S3-202416 | Solution for UAV A&A using EAP-based PDU Secondary authentication |
pCR revised to S3-202703 |
InterDigital, Europe, Ltd. | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
revised | [WTS] [JSN] |
S3-202417 | Solution for UAV A&A using API-based PDU Secondary authentication |
pCR revised to S3-202704 |
InterDigital, Europe, Ltd. | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
revised | [WTS] [JSN] |
S3-202418 | Update for KI#5 Privacy protection of UAS identities | pCR | InterDigital, Europe, Ltd. | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202419 | Structuring key issues per SID objectives | pCR | Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
merged | [WTS] [JSN] |
S3-202420 | KI on UE data collection protection | pCR | Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202421 | KI on NF data collection protection | pCR | Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202422 | KI on Abnormal UE behavior detection by NWDAF | pCR | Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
merged | [WTS] [JSN] |
S3-202423 | KI on Abnormal NF behavior detection by NWDAF | pCR | Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
merged | [WTS] [JSN] |
S3-202424 | KI on Protection of data in transit between multiple NWDAF instances | pCR | Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202425 | KI on Privacy preservation for transmitted data between multiple NWDAF instances |
pCR revised to S3-202790 |
Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
revised | [WTS] [JSN] |
S3-202426 | KI on user consent and authorization for inter-NWDAF data transfer | pCR | Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202427 | Discussion on LS S2-2006037 MUSIM busy indication | discussion | Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-202428 | Discussion on LS S2-2006011 on MUSIM | discussion | Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-202429 | Reply LS to S2-2006037 MUSIM busy indication |
LS out LS is reply to S2-2006037 LS To: SA2 revised to S3-202687 |
Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.18 |
revised | [WTS] [JSN] | |||
S3-202430 | Reply LS to S2-2006011 on MUSIM |
LS out LS is reply to S2-2006011 LS To: SA2 |
Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-202431 | Discussion on S5-204407 Study items on management aspects | discussion | Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-202432 | Reply LS to SA5 LS on study items for security management aspect |
LS out LS is reply to S5-204407 LS To: SA5 revised to S3-202688 |
Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.18 |
revised | [WTS] [JSN] | |||
S3-202433 | Discussion on S2-2006589 on PRoSe L2 and L3 solutions in SA2 TR | discussion | Nokia, Nokia Shanghai Bell | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] | ||
S3-202434 | Reply LS to S2-2006589 on Security issues for 5G PRoSe |
LS out LS To: SA2 revised to S3-202689 |
Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] | |||
S3-202435 | Key Issue on Generic User consent | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.0.1 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
noted | [WTS] [JSN] |
S3-202436 | FS_eSBA_SEC |
SID new revision of S3-202107 |
Nokia | Rel-17 |
S3-100-bis-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-202437 | Discussion on editor notes in SQNms concealment solution | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202438 | Ed.note resolution on SQNms protection by concealment when 5G-GUTI is received | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202439 | Ed.note resolution on backward compatibility in solution SQNms protection by concealment | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202440 | Discussion_paper_on_editor_notes_SQN protection during re-synchronisation | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202441 | Ed.note resolution in solution summary of sol.4.4 |
pCR revised to S3-202788 |
Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
revised | [WTS] [JSN] |
S3-202442 | Ed.note resolution on backward compatibility in evaluation of sol.4.4 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202443 | KI update on SUCI replay | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202444 | Solution for avoiding linkability by SUCI replay and SUPI guessing attack | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202445 | Editorial updates of solution titles |
pCR revised to S3-202786 |
Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
revised | [WTS] [JSN] |
S3-202446 | Comparison of different solutions for Key issue#4.1 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202447 | Conclusion to key issue 4.1 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202448 | 5GFBS-RRCResumeRequest message protection | pCR | Apple, CableLabs | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202449 | 5GFBS-Add a NOTE in the key issue#7 on the MitM attack | pCR | Apple | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202450 | MEC-Reply LS to SA6 (S6-200947) on the protection of user’s consent |
LS out LS To: SA6 |
Apple | Rel-17 |
S3-100-bis-e AI: 2.8 |
merged | [WTS] [JSN] | ||
S3-202451 | ProSe- New solution on security of UE-to-UE relay |
pCR revised to S3-202780 |
Apple | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202452 | 5MBS-New key issue for PTP mode | pCR | Apple | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
noted | [WTS] [JSN] |
S3-202453 | KI on boundary 5GS TSN user plane interfaces | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202454 | Requirements for KI on boundary 5GS TSN user plane interfaces | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202455 | KI details update on time synchronization messages | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202456 | Requirements for KI on time synchronization messages | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202457 | KI details update on multiple working domains | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202458 | Requirements for KI on multiple working domains | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202459 | Solution - Authentication of TSN nodes sending time synchronization messages | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202460 | Solution - Authorization of incoming time synchronization messages based on policies | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202461 | Revised SID on IIoT Security - discussion paper | pCR | Nokia, Nokia Shanghai Bell | 33.851 17.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 3 |
noted | [WTS] [JSN] |
S3-202462 | Revised SID on Industrial IoT Security |
SID revised revision of SP-200355 |
Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 3 |
agreed | [WTS] [JSN] | |
S3-202463 | Key issue on the binding relationship for the UE IDs | pCR | CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
withdrawn | [WTS] [JSN] |
S3-202464 | Updates to solution #20 (6.20.2.1) |
pCR revised to S3-202718 |
CableLabs, Philips International B.V, Apple, Deutsche Telekom AG, InterDigital Communications, Charter Communications | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202465 | Key issue on the binding relationship for the UE IDs | pCR | CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
noted | [WTS] [JSN] |
S3-202466 | Updates to solution #20 (6.20.2.4) |
pCR revised to S3-202719 |
CableLabs, Philips International B.V, Apple, Deutsche Telekom AG, InterDigital Communications, Charter Communications | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202467 | Updates to solution #20 (6.20.2.5.1) | pCR | CableLabs, Philips International B.V, Apple, Deutsche Telekom AG, InterDigital Communications, Charter Communications | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202468 | Updates to solution #20 (adding Assessment using Annex A.3) |
pCR revised to S3-202720 |
CableLabs, Philips International B.V, Apple, Deutsche Telekom AG, InterDigital Communications, Charter Communications | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202469 | New solution on Key management in discovery procedure |
pCR revised to S3-202769 |
Huawei, HiSilicon | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202470 | New solution on discovery protection |
pCR revised to S3-202771 |
Huawei, HiSilicon | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202471 | Update key issue #1 | pCR | Huawei, HiSilicon | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202472 | Update key issue #2 | pCR | Huawei, HiSilicon | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202473 | Add content to clause 4 |
pCR revised to S3-202768 |
Huawei, HiSilicon | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
revised | [WTS] [JSN] |
S3-202474 | New key issue on security enhancement | pCR | Huawei, HiSilicon;China Telecom | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.13 |
noted | [WTS] [JSN] |
S3-202475 | Abbreviation | pCR | Huawei, HiSilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
approved | [WTS] [JSN] |
S3-202476 | Editorial change to key issue 2 | pCR | Huawei, HiSilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
approved | [WTS] [JSN] |
S3-202477 | New solution to protect MBS traffic in transport layer |
pCR revised to S3-202761 |
Huawei, HiSilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
revised | [WTS] [JSN] |
S3-202478 | New solution to protect MBS traffic in service layer |
pCR revised to S3-202762 |
Huawei, HiSilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
revised | [WTS] [JSN] |
S3-202479 | New solution to verify the location information |
pCR revised to S3-202772 |
Huawei, HiSilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
revised | [WTS] [JSN] |
S3-202480 | Key issue on the protection of multi-CU-UPs connectivity | pCR | CATT | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
withdrawn | [WTS] [JSN] |
S3-202481 | Key issue on the protection of multi-CU-UPs connectivity | pCR | CATT | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
noted | [WTS] [JSN] |
S3-202482 | New KI on service authorization between SNPNs | pCR | Huawei, Hisilicon | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202483 | EC: New solution on authentication and authorization between EEC and ECS |
pCR revised to S3-202742 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202484 | EC: New Key issue on authorization during Edge Data Network change |
pCR revised to S3-202743 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202485 | EC: New solution on transport security for EDGE-1-9 interfaces |
pCR revised to S3-202744 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202486 | 5G ProSe: New key issue on UE-to-UE Relay or UE-to-Network Relay selection | pCR | Huawei, Hisilicon | 33.847 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202487 | 5G ProSe: New solution on e2e authentication between two UE2 in the UE-to-UE relay scenario | pCR | Huawei, Hisilicon | 33.847 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202488 | Reply LS on Misalignments on HTTP message format over N32-f |
LS out LS To: CT4 |
Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-15 |
S3-100-bis-e AI: 4 |
noted | [WTS] [JSN] | |
S3-202489 | JSON object modification | draftCR | Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-15 |
S3-100-bis-e AI: 4 |
noted | [WTS] [JSN] | |
S3-202490 | JSON object modification | draftCR | Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-16 |
S3-100-bis-e AI: 4 |
noted | [WTS] [JSN] | |
S3-202491 | pCR: New solution to 5G MBS authentication and authorization | pCR | Huawei, Hisilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
approved | [WTS] [JSN] |
S3-202492 | pCR: Revocation of authorization of MBS communication service |
pCR revised to S3-202745 |
Huawei, Hisilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
revised | [WTS] [JSN] |
S3-202493 | pCR: New solution to MBS traffic protection |
pCR revised to S3-202746 |
Huawei, Hisilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
revised | [WTS] [JSN] |
S3-202494 | pCR: 33.846: Updates on key issue #2.1 |
pCR revised to S3-202747 |
Huawei, Hisilicon | 33.846 0.3.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
revised | [WTS] [JSN] |
S3-202495 | pCR: 33.846: Conclusion on key issue #3.1 | pCR | Huawei, Hisilicon | 33.846 0.3.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202496 | pCR: New key issue on solving registration failure in NAS reroute via RAN | pCR | Huawei, Hisilicon,China Mobile | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202497 | pCR: New solution for solving registration failure in AMF re-allocation | pCR | Huawei, Hisilicon | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202498 | pCR: Description of AMF re-allocation procedure | pCR | Huawei, Hisilicon | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202499 | New SID on Study on Security Enhancement of UPF deployed in the customer side | SID new | Huawei, Hisilicon | Rel-17 |
S3-100-bis-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-202500 | Solution on Authentication and Authorization between the Edge Enabler Client and the Edge Configuration Server |
pCR revised to S3-202776 |
CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202501 | Solution on Authentication and Authorization between the EEC and the EES when the ECS is deployed by the ECSP |
pCR revised to S3-202777 |
CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202502 | Solution on Authentication and Authorization between the EEC and the EES when the ECS is deployed by the MNO |
pCR revised to S3-202778 |
CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202503 | Solution on the service capability exposure to the EAS |
pCR revised to S3-202779 |
CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202504 | Draft LS: Misalignment on requirement for access token request between TS 29.510 and 33.501 |
LS out LS To: CT4 |
Mavenir | 5GS_Ph1-SEC | Rel-15 |
S3-100-bis-e AI: 4 |
withdrawn | [WTS] [JSN] | |
S3-202505 | SA3 and CT4 misalignment on token request for Discovery and NFManagement | discussion | Mavenir | 5GS_Ph1-SEC | Rel-15 |
S3-100-bis-e AI: 4 |
withdrawn | [WTS] [JSN] | |
S3-202506 | NRF authorization during NF service consumer Access Token Get Request | draftCR | Mavenir | 5GS_Ph1-SEC | Rel-15 |
S3-100-bis-e AI: 4 |
withdrawn | [WTS] [JSN] | |
S3-202507 | NRF authorization during NF service consumer Access Token Get Request | draftCR | Mavenir | 5G_eSBA | Rel-16 |
S3-100-bis-e AI: 4 |
withdrawn | [WTS] [JSN] | |
S3-202508 | New solution for Key Issue #1 |
pCR revised to S3-202721 |
CableLabs | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202509 | Discussion on SA2 LS and CR in S3-202366 | discussion | Futurewei |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] | |||
S3-202510 | Discussion on SA2 LS on EC Solution #22 | discussion | Futurewei |
S3-100-bis-e AI: 2.8 |
noted | [WTS] [JSN] | |||
S3-202511 | New key issue hosting third-party CU-UP | pCR | Futurewei | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
noted | [WTS] [JSN] |
S3-202512 | New key issue on UE accessing most preferred serving NPN | pCR | Futurewei | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202513 | Add Provisioning Server Term |
pCR revised to S3-202732 |
Intel Corporation (UK) Ltd | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202514 | Add terms related to Onboarding | pCR | Intel Corporation (UK) Ltd | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
merged | [WTS] [JSN] |
S3-202515 | Add Terms Default Credentials and DCS | pCR | Intel Corporation (UK) Ltd | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202516 | Onboarding and authentication/authorization framework for Edge Enabler Server with Edge Configuration Server |
pCR revised to S3-202731 |
Intel Corporation (UK) Ltd | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202517 | New Key Issue on NWDAF assisting in Detecting DoS Attack on Network Entities | pCR | Huawei, Hisilicon | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
merged | [WTS] [JSN] |
S3-202518 | Scope of eNA Security | pCR | Huawei, Hisilicon | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202519 | New Key Issue on Avoiding using Misleading or Untrusted Information for Data Analysis | pCR | Huawei, Hisilicon | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202520 | Reply LS on User consent requirements for analytics |
LS out LS To: SA2 |
Huawei, Hisilicon |
S3-100-bis-e AI: 2.16 |
merged | [WTS] [JSN] | |||
S3-202521 | Updates to Solution 3 | pCR | Intel Corporation (UK) Ltd | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202522 | Key issue for UE onboarding for provisioning | pCR | Intel Corporation (UK) Ltd | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
merged | [WTS] [JSN] |
S3-202523 | New SID on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) |
SID new revised to S3-202730 |
Intel Corporation (UK) Ltd |
S3-100-bis-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-202524 | Reply LS on checking Security issue for Solution 22 in TR 23.748 |
LS out LS To: SA2 |
Intel Corporation (UK) Ltd |
S3-100-bis-e AI: 2.8 |
merged | [WTS] [JSN] | |||
S3-202525 | Discussion on LS on checking security issue for Solution 22 in TR 23.748 | discussion | Intel Corporation (UK) Ltd |
S3-100-bis-e AI: 2.8 |
noted | [WTS] [JSN] | |||
S3-202526 | Solution to UE onboarding for non-public networks | pCR | Intel Corporation (UK) Ltd | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202527 | Updates to Key Issue 3 and 6 |
pCR revised to S3-202733 |
Intel Corporation (UK) Ltd | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202528 | New solution for key issue 1,2, 4,6 |
pCR revised to S3-202729 |
Intel Corporation (UK) Ltd | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202529 | Discussion on LS new SID Security Study on system enablers for devices having multiple USIMS | discussion | Intel Corporation (UK) Ltd |
S3-100-bis-e AI: 2.18 |
noted | [WTS] [JSN] | |||
S3-202530 | A new key issue on security of data collection from UE | pCR | Ericsson | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202531 | New solution for KI#3 | pCR | Philips International B.V., CableLabs | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202532 | Clarification Key Issue #7 | pCR | Philips International B.V., CableLabs | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
merged | [WTS] [JSN] |
S3-202533 | Scope for TR 33.862 | pCR | China Mobile | 33.862 0.0.0 | FS_SEC_5GMSG | Rel-17 |
S3-100-bis-e AI: 2.15 |
approved | [WTS] [JSN] |
S3-202534 | Key issue on cyber-attacks detection supported by NWDAF |
pCR revised to S3-202766 |
China Mobile | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
revised | [WTS] [JSN] |
S3-202535 | Key issue on remote provisioning of non-3GPP credentials for PNI-NPN | pCR | China Mobile | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202536 | Summary of editors notes and way forwards for UPIP - TR33.853 | discussion | VODAFONE Group Plc | FS_UP_IP_Sec | Rel-17 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] | |
S3-202537 | LS on Security Requirements for Sidelink/PC5 Relays | LS in | S2-2004750 |
S3-100-bis-e AI: 2.9 |
postponed | [WTS] [JSN] | |||
S3-202538 | New solution to KI#1: Primary authentication between an SNPN and third-party AAA server using EAP |
pCR revised to S3-202681 |
Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202539 | New solution to KI#1: Primary authentication between an SNPN and third-party AAA server using EAP-TTLS |
pCR revised to S3-202682 |
Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202540 | 5GFBS: Accuracy of Loaction Estimate for Solution#22 | pCR | Nokia, Nokia Shanghai Bell | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202541 | 5GFBS: FBS pretending to be in a different PLMN for Solution#22 |
pCR revised to S3-202699 |
Nokia, Nokia Shanghai Bell | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202542 | 5GFBS: FBS Detection in Network Sharing Scenario for Solution#22 | pCR | Nokia, Nokia Shanghai Bell | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202543 | 5GFBS: Support of Multiple FBS Detection for Solution#22 | pCR | Nokia, Nokia Shanghai Bell | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202544 | SCAS VNP: DoS Attack via Changing Virtualized Resource | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202545 | SCAS VNP: Secure Execution Environment | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202546 | SCAS VNP: Software Tampering |
pCR revised to S3-202696 |
Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
revised | [WTS] [JSN] |
S3-202547 | SCAS VNP: Threats on VNF-VNFM Interface | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202548 | SCAS VNP: VM Escape and Hypervisor Escape | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202549 | SCAS VNP: Security requirements on the interface between VNF and VNFM | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202550 | Update of key issue on provisioning of credentials | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
merged | [WTS] [JSN] |
S3-202551 | reply-LS on Misalignments on HTTP message format over N32-f |
LS out LS To: CT4 |
Ericsson | Rel-15 |
S3-100-bis-e AI: 4 |
noted | [WTS] [JSN] | ||
S3-202552 | Update of KI#3 (Security impacts from supporting IMS voice and IMS services in SNPNs) | pCR | Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202553 | New Solution to KI#3: Authentication to IMS Core using SNPN credentials | pCR | Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202554 | New Solution to KI#3: Authentication to IMS Core using credentials generated with AKMA | pCR | Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202555 | New Solution to KI#3: Authentication to IMS Core using credentials generated from the KAUSF | pCR | Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202556 | Clarification Solution #23 |
pCR revised to S3-202738 |
Philips International B.V. | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202557 | Updates to solution #20 (6.20.2.2.2) |
pCR revised to S3-202737 |
Philips International B.V., CableLabs, Apple | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202558 | Updates to solution #20 (6.20.2.5.1 (verification)) | pCR | Philips International B.V., CableLabs, Apple | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202559 | Clarifying summary of threats for GVNP | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
merged | [WTS] [JSN] |
S3-202560 | Security functional requirements derived from 3GPP specifications – general SBA/SBI aspects | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202561 | Adding hardening requirements for GVNP of type 1 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202562 | Adding hardening requirements for GVNP of type 2 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202563 | Adding hardening requirements for GVNP of type 3 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202564 | Adding basic vulnerability testing requirements for GVNP | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202565 | Adding vendor development and product lifecycle processes and test laboratory accreditation into Clause 6 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202566 | Adding evaluation and SCAS instantiation into clause 7 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202567 | Adding test case into clause 5.2.5.5.8.5.1 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202568 | Adding test case into clause 5.2.5.6.6.1 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202569 | Adding conclusion into clause 8 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
noted | [WTS] [JSN] |
S3-202570 | reply LS on security analysis for Solution 22 in TR 23.748 |
LS out LS is reply to S3-202364 LS To: SA2 revised to S3-202678 |
China Mobile | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] | |
S3-202571 | Complementary to key issue to mitigate the SUPI guessing attacks |
pCR revised to S3-202710 |
China Mobile | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
revised | [WTS] [JSN] |
S3-202572 | Discussion on a unified solution needs to the key issue #2.1 and key issue #4.1 | discussion | China Mobile | FS_AUTH_ENH | Rel-17 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] | |
S3-202573 | Propose a conclusion for the key issue #2.1 and key issue #4.1 | pCR | China Mobile | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202574 | New Key issue on reporting of base station involved in cyber attack |
discussion revised to S3-202584 |
NEC Europe Ltd | FS_eNA_SEC |
S3-100-bis-e AI: 2.16 |
revised | [WTS] [JSN] | ||
S3-202575 | IIOT: New key issue for protection of AF-NEF interface |
pCR revised to S3-202694 |
Ericsson | 33.851 0.1.0 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202576 | IIOT: New solution for protection of AF-NEF interface |
pCR revised to S3-202698 |
Ericsson | 33.851 0.1.0 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202577 | IIOT: Update to solution #2 | pCR | Ericsson | 33.851 0.1.0 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
withdrawn | [WTS] [JSN] |
S3-202578 | UPIP: Update to solution #11 |
pCR revised to S3-202727 |
Ericsson | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
revised | [WTS] [JSN] |
S3-202579 | UPIP: Conclusion on |
pCR | Ericsson | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] |
S3-202580 | UPIP: New solution to resolve KI#1 for Option (eUTRA with EPC) |
pCR revised to S3-202728 |
Ericsson | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
revised | [WTS] [JSN] |
S3-202581 | New solution for AMF reallocation procedure when 5G NAS security context is rerouted via RAN | pCR | Ericsson | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202582 | ProSe: Protection of the PC3 interface |
pCR revised to S3-202700 |
Ericsson | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202583 | ProSe: key management for UE-to-Network Relay and Remote UE |
pCR revised to S3-202701 |
Ericsson | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202584 | New Key issue on reporting of base station involved in cyber attack |
pCR revision of S3-202574 revised to S3-202668 |
NEC Europe Ltd | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
revised | [WTS] [JSN] |
S3-202585 | Securing initial access for UE onboarding between UE and SNPN |
pCR revised to S3-202715 |
Ericsson, Huawei, Hisilicon, Qualcomm Incorporated, Lenovo, Motorola Mobility, InterDigital | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202586 | Definition of Provisioning Server | pCR | Ericsson, Huawei, Hisilicon, InterDigital, Lenovo, Motorola Mobility, China Mobile | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202587 | Reply LS on propagation of user consent related information during Xn inter-PLMN handover |
LS out LS is reply to R3-204378 LS To: RAN3 |
Ericsson | Rel-16 |
S3-100-bis-e AI: 2.14 |
noted | [WTS] [JSN] | ||
S3-202588 | Discussion on provisioning server | discussion | Ericsson, Huawei, Hisilicon, InterDigital, Lenovo, Motorola Mobility, China Mobile |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] | |||
S3-202589 | Discussion on user consent study |
pCR revised to S3-202693 |
Ericsson | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
revised | [WTS] [JSN] |
S3-202590 | Not ruling out impact on UE/RAN/CN | pCR | Ericsson | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
noted | [WTS] [JSN] |
S3-202591 | Separate UP-keys per CU-UP instance | pCR | Ericsson | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
noted | [WTS] [JSN] |
S3-202592 | CU-UPs supported by DC | pCR | Ericsson | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
noted | [WTS] [JSN] |
S3-202593 | New key issue for the security of the AMF re-allocation procedures | pCR | Ericsson | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202594 | Introduction for the AMF re-allocation security study |
pCR revised to S3-202725 |
Ericsson | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
revised | [WTS] [JSN] |
S3-202595 | Scope for the AMF re-allocation security study |
pCR revised to S3-202726 |
Ericsson | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
revised | [WTS] [JSN] |
S3-202596 | Assumptions for the AMF re-allocation security study | pCR | Ericsson | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202597 | New solution for NAS re-route via RAN and the use of a well-connected network function | pCR | Ericsson | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202598 | update to KI#10 User's consent for exposure of information to Edge Applications |
pCR revised to S3-202758 |
Huawei, Hiliscon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202599 | pCR to TR33.853 - Conclusions for Option 1 and 3 | pCR | VODAFONE Group Plc | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] |
S3-202600 | Broadcast privacy | pCR | Lenovo, Motorola Mobility | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202601 | Key Issue on detection of MitM attacks | pCR | Lenovo, Motorola Mobility | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
merged | [WTS] [JSN] |
S3-202602 | pCR: Conclusion of Key issue#5 | pCR | Lenovo, Motorola Mobility, Huawei | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202603 | Update of Solution#15 |
pCR revised to S3-202782 |
Lenovo, Motorola Mobility | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202604 | Key Issue on Impact of Simultaneous CU-UP applying common UP security | pCR | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Samsung, Altiostar | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
noted | [WTS] [JSN] |
S3-202605 | Authentication and Authorization with the Edge Data Network |
pCR revised to S3-202781 |
Lenovo, Motorola Mobility | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202606 | Network access authentication with credentials owned by an entity separate from the SNPN |
pCR revised to S3-202783 |
Lenovo, Motorola Mobility | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202607 | Solution on UAS Authentication and Authorization |
pCR revised to S3-202722 |
Lenovo, Motorola Mobility | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
revised | [WTS] [JSN] |
S3-202608 | DRAFT LS to RAN3 on UPIP solutions for LE |
LS out LS To: RAN3 |
VODAFONE Group Plc | Rel-17 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] | ||
S3-202609 | Solution on UAS Security Aspects | pCR | Lenovo, Motorola Mobility | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202610 | [UAS] Update to KI#6 | pCR | Samsung | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202611 | [5G_ProSe] Updates to solution#1 |
pCR revised to S3-202683 |
Samsung | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202612 | [5G_ProSe] Updates to solution#2 |
pCR revised to S3-202684 |
Samsung | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202613 | New KI for security policy handling in ProSe relay communication | pCR | Samsung | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202614 | Solution for security policy handling in ProSe relay communication | pCR | Samsung | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202615 | Key issue: Transport security for the MSGin5G interfaces |
pCR revised to S3-202685 |
Samsung | 33.862 0.0.0 | FS_SEC_5GMSG | Rel-17 |
S3-100-bis-e AI: 2.15 |
revised | [WTS] [JSN] |
S3-202616 | Key issue: Authentication and authorization between 5GMSGS client and MSGin5G server |
pCR revised to S3-202686 |
Samsung | 33.862 0.0.0 | FS_SEC_5GMSG | Rel-17 |
S3-100-bis-e AI: 2.15 |
revised | [WTS] [JSN] |
S3-202617 | Key issue: Authentication and authorization between Application Server and MSGin5G server | pCR | Samsung | 33.862 0.0.0 | FS_SEC_5GMSG | Rel-17 |
S3-100-bis-e AI: 2.15 |
approved | [WTS] [JSN] |
S3-202618 | Corrections to Key issue #6 | pCR | Samsung | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
merged | [WTS] [JSN] |
S3-202619 | Moving Key issue #10 to FS_UC3S | pCR | Samsung | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
merged | [WTS] [JSN] |
S3-202620 | Resolving editor’s note on AKMA key derivation | pCR | Samsung | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202621 | Resolving editor’s note on MAC-I calculation |
pCR revised to S3-202697 |
Samsung | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
revised | [WTS] [JSN] |
S3-202622 | Transfer of Key issue #10 from FS_eEDGE_SEC | pCR | Samsung | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
approved | [WTS] [JSN] |
S3-202623 | Potential Requirement on user's consent for exposure of information to Edge Applications | pCR | Samsung | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
noted | [WTS] [JSN] |
S3-202624 | Evaluation for Solution#13 | pCR | Samsung | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202625 | Evaluation for Solution#17 | pCR | Samsung | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202626 | Solution for Resumecause protection | pCR | Samsung | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
noted | [WTS] [JSN] |
S3-202627 | Revised SID: Study on Security for NR Integrated Access and Backhaul |
SID revised revised to S3-202695 |
Samsung | FS_NR_IAB_Sec | Rel-17 |
S3-100-bis-e AI: 3 |
revised | [WTS] [JSN] | |
S3-202628 | Solution on UAV and UAV-C Pairing Authorization and Security Aspects | pCR | Lenovo, Motorola Mobility | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202629 | Key Issue on Security Context handling issues with AMF re-allocation | pCR | Lenovo, Motorola Mobility | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] |
S3-202630 | Certificate based solution for Protecting System Information Messages with Digital Signature in an NPN |
pCR revised to S3-202717 |
MITRE Corporation, AT&T, InterDigital, DoD, NTIA, CISA/ECD, Charter Communications | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202631 | [DRAFT] Reply-LS on AAA based solutions for credentials owned by an entity separate from the SNPN |
LS out LS To: SA2 |
Ericsson |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] | |||
S3-202632 | New Key Issue on privacy of PDU session parameters | pCR | Philips International B.V. | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202633 | [DRAFT] reply LS on security issues for on-boarding and remote provisioning |
LS out LS To: SA2 |
Ericsson |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] | |||
S3-202634 | pCR to TR33.853 - Updates to Solution#15 | pCR | VODAFONE Group Plc | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
noted | [WTS] [JSN] |
S3-202635 | A new solution for UAS authentication and authorization |
pCR revised to S3-202690 |
Ericsson | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
revised | [WTS] [JSN] |
S3-202636 | Conclusion for Key Issue #2.1 | pCR | THALES | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202637 | Conclusion for Key Issue #4.1 | pCR | THALES | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202638 | eNPN SID: discussion | discussion | THALES, Orange, Idemia | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 3 |
noted | [WTS] [JSN] | |
S3-202639 | Restricting handovers to RAN nodes that don’t support UP IP |
pCR revised to S3-202707 |
Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
revised | [WTS] [JSN] |
S3-202640 | pCR: Solution for UP IP for EPC connected RAN options |
pCR revised to S3-202723 |
Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
revised | [WTS] [JSN] |
S3-202641 | Authentication and authorisation of UAVs | pCR | Qualcomm Incorporated | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
noted | [WTS] [JSN] |
S3-202642 | Obtaining UAV location information from the PLMN |
pCR revised to S3-202709 |
Qualcomm Incorporated | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
revised | [WTS] [JSN] |
S3-202643 | Some evaluation of solution#2.1 in TR 33.846 |
pCR revision of S3-201930 |
Qualcomm Incorporated | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202644 | Some evaluation of solution #2.2 in TR 33.846 |
pCR revision of S3-201931 |
Qualcomm Incorporated | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202645 | Some evaluation of solution #2.3 in TR 33.846 |
pCR revision of S3-201932 revised to S3-202711 |
Qualcomm Incorporated | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
revised | [WTS] [JSN] |
S3-202646 | Some evaluation of solution #2.5 in TR 33.846 |
pCR revision of S3-201933 revised to S3-202712 |
Qualcomm Incorporated | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
revised | [WTS] [JSN] |
S3-202647 | Proposing a conclusion for key issue #4.1 |
pCR revision of S3-201935 |
Qualcomm Incorporated | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
noted | [WTS] [JSN] |
S3-202648 | Solution for secure PC5 link establishment for UE-to-network relay | pCR | Qualcomm Incorporated | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202649 | Solution to establish end-to-end security for the L3 UE-to-network relay | pCR | Qualcomm Incorporated | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202650 | Solution for secure PC5 link establishment for UE-to-UE relay | pCR | Qualcomm Incorporated | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202651 | AS security for MBS traffic protection | pCR | Qualcomm Incorporated | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
merged | [WTS] [JSN] |
S3-202652 | Reply LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN |
LS out LS is reply to S3-201529 LS To: SA2 |
Qualcomm Incorporated |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] | |||
S3-202653 | pCR: Solution for KI#1 in TR 33.857 |
pCR revised to S3-202724 |
Qualcomm Incorporated | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
revised | [WTS] [JSN] |
S3-202654 | eNPN scope | pCR | THALES, Orange, Idemia | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202655 | eNPN security assumptions | pCR | THALES, Orange, Idemia | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 3 |
noted | [WTS] [JSN] |
S3-202656 | pCR to TR33.853 - Updates to solution #14 | pCR | VODAFONE Group Plc | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
approved | [WTS] [JSN] |
S3-202657 | eNPN SID revision | SID revised | THALES, Orange, Idemia | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 3 |
noted | [WTS] [JSN] | |
S3-202658 | Proposed TR Assumptions on credentials | pCR | Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202659 | pCR to TR33.853 - Updates to solution #14 | pCR | VODAFONE Group Plc | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
withdrawn | [WTS] [JSN] |
S3-202660 | Scope for TR 33.840 |
pCR revision of S3-202330 revised to S3-202792 |
China Telecom, Huawei, HiSilicon, CATT, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
revised | [WTS] [JSN] |
S3-202661 | [DRAFT] Reply LS on securing data collection from UE |
LS out LS To: SA2 |
Ericsson |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] | |||
S3-202662 | pCR to 33.809 Enhanced Description of Key Issue #7 |
pCR revised to S3-202691 |
Nokia, Nokia Shanghai Bell | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
revised | [WTS] [JSN] |
S3-202663 | Scope of TR 33.857 | pCR | Philips International B.V. | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202664 | Solution for authorization and security with UE-to-Network relay using Remote | pCR | InterDigital Communications | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
withdrawn | [WTS] [JSN] |
S3-202665 | Solution for authorization and security with UE-to-Network relay using Remote UE network primary authentication |
pCR revised to S3-202714 |
InterDigital Communications | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
revised | [WTS] [JSN] |
S3-202666 | Architectural model corrections | pCR | Philips International B.V. | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202667 | LS to CT1 on Clarifications on NAS message processing |
LS out LS To: CT1 |
Nokia Germany |
S3-100-bis-e AI: 2.17 |
approved | [WTS] [JSN] | |||
S3-202668 | New Key issue on reporting of base station involved in cyber attack |
pCR revision of S3-202584 |
NEC Europe Ltd | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
noted | [WTS] [JSN] |
S3-202669 | Minutes of the meeting for the offline teleconference on the AMF re-allocation | report | Ericsson Hungary Ltd |
S3-100-bis-e AI: 2.17 |
noted | [WTS] [JSN] | |||
S3-202670 | Process and agenda for SA3#100bis-e | other | SA WG3 Chair |
S3-100-bis-e AI: 1 |
withdrawn | [WTS] [JSN] | |||
S3-202671 | New solution for KI4 - Encrypted storage of OPc in UDR |
pCR revision of S3-202404 |
KPN N.V. | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202672 | New solution for KI6 - Encrypted storage of OP in UDR |
pCR revision of S3-202406 |
KPN N.V. | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202673 | New KI - UE identity protection during ProSe discovery |
pCR revision of S3-202403 |
KPN N.V. | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202674 | Skeleton for TR 33.866 |
draft TR revision of S3-202309 |
China Mobile¸ Nokia, Nokia Shanghai Bell | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
approved | [WTS] [JSN] | |
S3-202675 | Evaluation of Solution 2 |
pCR revision of S3-202305 |
NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202676 | Evaluation of Solution 3 |
pCR revision of S3-202306 |
NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202677 | Evaluation of Solution 4 |
pCR revision of S3-202307 |
NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202678 | reply LS on security analysis for Solution 22 in TR 23.748 |
LS out LS is reply to S3-202364 LS To: SA2 revision of S3-202570 |
China Mobile | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] | |
S3-202679 | TR 33.818 v0.8.0 | draft TR | China Mobile Com. Corporation | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
approved | [WTS] [JSN] | |
S3-202680 | New solution for KI2: Storage of LTK in UDR |
pCR revision of S3-202308 |
NCSC | 33.845 0.4.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-bis-e AI: 2.6 |
approved | [WTS] [JSN] |
S3-202681 | New solution to KI#1: Primary authentication between an SNPN and third-party AAA server using EAP |
pCR revision of S3-202538 |
Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202682 | New solution to KI#1: Primary authentication between an SNPN and third-party AAA server using EAP-TTLS |
pCR revision of S3-202539 |
Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202683 | [5G_ProSe] Updates to solution#1 |
pCR revision of S3-202611 |
Samsung | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202684 | [5G_ProSe] Updates to solution#2 |
pCR revision of S3-202612 |
Samsung | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202685 | Key issue: Transport security for the MSGin5G interfaces |
pCR revision of S3-202615 |
Samsung | 33.862 0.0.0 | FS_SEC_5GMSG | Rel-17 |
S3-100-bis-e AI: 2.15 |
approved | [WTS] [JSN] |
S3-202686 | Key issue: Authentication and authorization between 5GMSGS client and MSGin5G server |
pCR revision of S3-202616 |
Samsung | 33.862 0.0.0 | FS_SEC_5GMSG | Rel-17 |
S3-100-bis-e AI: 2.15 |
approved | [WTS] [JSN] |
S3-202687 | Reply LS to S2-2006037 MUSIM busy indication |
LS out LS is reply to S3-202400 LS To: SA2, RAN2, RAN3 revision of S3-202429 |
Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.18 |
approved | [WTS] [JSN] | |||
S3-202688 | Reply LS to SA5 LS on study items for security management aspect |
LS out LS is reply to S3-202402 LS To: SA5 revision of S3-202432 |
Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.18 |
approved | [WTS] [JSN] | |||
S3-202689 | Reply LS to S2-2006589 on Security issues for 5G PRoSe |
LS out LS is reply to S3-202368 LS To: SA2 revision of S3-202434 |
Nokia, Nokia Shanghai Bell |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] | |||
S3-202690 | A new solution for UAS authentication and authorization |
pCR revision of S3-202635 |
Ericsson | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202691 | pCR to 33.809 Enhanced Description of Key Issue #7 |
pCR revision of S3-202662 |
Nokia, Nokia Shanghai Bell | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202692 | Addressing EN in Sol1 on UAS registration Accept |
pCR revision of S3-202392 |
Huawei, HiSilicon, Lenovo, Motorola Mobility | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202693 | Discussion on user consent study |
pCR revision of S3-202589 |
Ericsson, Nokia | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
approved | [WTS] [JSN] |
S3-202694 | IIOT: New key issue for protection of AF-NEF interface |
pCR revision of S3-202575 |
Ericsson¸ Nokia, Nokia Shanghai Bell | 33.851 0.1.0 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202695 | Revised SID: Study on Security for NR Integrated Access and Backhaul |
SID revised revision of S3-202627 |
Samsung | FS_NR_IAB_Sec | Rel-17 |
S3-100-bis-e AI: 3 |
agreed | [WTS] [JSN] | |
S3-202696 | SCAS VNP: Software Tampering |
pCR revision of S3-202546 |
Nokia, Nokia Shanghai Bell, China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-bis-e AI: 2.2 |
approved | [WTS] [JSN] |
S3-202697 | Resolving editor’s note on MAC-I calculation |
pCR revision of S3-202621 |
Samsung | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202698 | IIOT: New solution for protection of AF-NEF interface |
pCR revision of S3-202576 |
Ericsson¸ Nokia, Nokia Shanghai Bell | 33.851 0.1.0 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202699 | 5GFBS: FBS pretending to be in a different PLMN for Solution#22 |
pCR revision of S3-202541 |
Nokia, Nokia Shanghai Bell | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202700 | ProSe: Protection of the PC3 interface |
pCR revision of S3-202582 |
Ericsson | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202701 | ProSe: key management for UE-to-Network Relay and Remote UE |
pCR revision of S3-202583 |
Ericsson | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202702 | Solution for UAV A&A during registration |
pCR revision of S3-202415 |
InterDigital, Europe, Ltd. | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202703 | Solution for UAV A&A using EAP-based PDU Secondary authentication |
pCR revision of S3-202416 |
InterDigital, Europe, Ltd. | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202704 | Solution for UAV A&A using API-based PDU Secondary authentication |
pCR revision of S3-202417 |
InterDigital, Europe, Ltd. | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202705 | KI for TR 33.847 – adding security for UE2N path switch in KI#3 |
pCR revision of S3-202377 |
InterDigital Communications, CableLabs | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202706 | Modification of KI for TR 33.847 – security for UE2UE Relay path switch |
pCR revision of S3-202378 |
InterDigital Communications, CableLabs | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202707 | Restricting handovers to RAN nodes that don’t support UP IP |
pCR revision of S3-202639 |
Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
approved | [WTS] [JSN] |
S3-202708 | New KI for TR 33.847 – security for support of Non-IP traffic |
pCR revision of S3-202413 |
InterDigital Communications | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202709 | Obtaining UAV location information from the PLMN |
pCR revision of S3-202642 |
Qualcomm Incorporated, Interdigital | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202710 | Complementary to key issue to mitigate the SUPI guessing attacks |
pCR revision of S3-202571 |
China Mobile | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202711 | Some evaluation of solution #2.3 in TR 33.846 |
pCR revision of S3-202645 |
Qualcomm Incorporated | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202712 | Some evaluation of solution #2.5 in TR 33.846 |
pCR revision of S3-202646 |
Qualcomm Incorporated | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202713 | New KI for TR 33.847 – privacy of ProSe entities while supporting Non-IP traffic |
pCR revision of S3-202414 |
InterDigital Communications | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202714 | Solution for authorization and security with UE-to-Network relay using Remote UE network primary authentication |
pCR revision of S3-202665 |
InterDigital Communications | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202715 | Securing initial access for UE onboarding between UE and SNPN |
pCR revision of S3-202585 |
Ericsson, Huawei, Hisilicon, Qualcomm Incorporated, Lenovo, Motorola Mobility, InterDigital, ZTE Corporation, Intel, Nokia, Nokia Shanghai Bell | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202716 | Draft TR 33857 v020 Study on enhanced security support for Non-Public Networks (NPN) | draft TR | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] | |
S3-202717 | Certificate based solution for Protecting System Information Messages with Digital Signature in an NPN |
pCR revision of S3-202630 |
MITRE Corporation, AT&T, InterDigital, DoD, NTIA, CISA/ECD, Charter Communications, SoftHandover Consulting, Apple | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202718 | Updates to solution #20 (6.20.2.1) |
pCR revision of S3-202464 |
CableLabs, Philips International B.V, Apple, Deutsche Telekom AG, InterDigital Communications, Charter Communications | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202719 | Updates to solution #20 (6.20.2.4) |
pCR revision of S3-202466 |
CableLabs, Philips International B.V, Apple, Deutsche Telekom AG, InterDigital Communications, Charter Communications | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202720 | Updates to solution #20 (adding Assessment using Annex A.3) |
pCR revision of S3-202468 |
CableLabs, Philips International B.V, Apple, Deutsche Telekom AG, InterDigital Communications, Charter Communications | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202721 | New solution for Key Issue #1 |
pCR revision of S3-202508 |
CableLabs | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202722 | Solution on UAS Authentication and Authorization |
pCR revision of S3-202607 |
Lenovo, Motorola Mobility | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202723 | pCR: Solution for UP IP for EPC connected RAN options |
pCR revision of S3-202640 |
Qualcomm Incorporated | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
approved | [WTS] [JSN] |
S3-202724 | pCR: Solution for KI#1 in TR 33.857 |
pCR revision of S3-202653 |
Qualcomm Incorporated | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202725 | Introduction for the AMF re-allocation security study |
pCR revision of S3-202594 |
Ericsson | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
approved | [WTS] [JSN] |
S3-202726 | Scope for the AMF re-allocation security study |
pCR revision of S3-202595 |
Ericsson | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
approved | [WTS] [JSN] |
S3-202727 | UPIP: Update to solution #11 |
pCR revision of S3-202578 |
Ericsson | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
approved | [WTS] [JSN] |
S3-202728 | UPIP: New solution to resolve KI#1 for Option (eUTRA with EPC) |
pCR revision of S3-202580 |
Ericsson | 33.853 1.1.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-bis-e AI: 2.3 |
approved | [WTS] [JSN] |
S3-202729 | New solution for key issue 1,2, 4,6 |
pCR revision of S3-202528 |
Intel Corporation (UK) Ltd | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202730 | New SID on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) |
SID new revision of S3-202523 |
Intel Corporation (UK) Ltd |
S3-100-bis-e AI: 3 |
agreed | [WTS] [JSN] | |||
S3-202731 | Onboarding and authentication/authorization framework for Edge Enabler Server with Edge Configuration Server |
pCR revision of S3-202516 |
Intel Corporation (UK) Ltd | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202732 | Add Provisioning Server Term |
pCR revision of S3-202513 |
Intel Corporation (UK) Ltd | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202733 | Updates to Key Issue 3 and 6 |
pCR revision of S3-202527 |
Intel Corporation (UK) Ltd | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202734 | Draft TR 33.864 v0.1.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson Hungary Ltd | FS_AMFREAL_SEC | Rel-17 |
S3-100-bis-e AI: 2.17 |
approved | [WTS] [JSN] | |
S3-202735 | Draft TR 33.846 v0.8.0 Study on authentication enhancements in the 5G System (5GS) | draft TR | Ericsson Hungary Ltd | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] | |
S3-202736 | New Key issue on groupcast security | pCR | Huawei Device Co., Ltd | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
withdrawn | [WTS] [JSN] |
S3-202737 | Update_solution_20_sec_6.20.2.2.2 |
pCR revision of S3-202557 |
Philips International B.V., CableLabsCableLabs, Philips International B.V, Apple, Deutsche Telekom AG | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202738 | Clarification Solution #23 |
pCR revision of S3-202556 |
Philips International B.V. | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202739 | New solution for key issue #1 |
pCR revision of S3-202324 |
ZTE Corporation, Nokia,Nokia Shanghai Bell | 33.851 0.1.1 | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202740 | Draft TR 33.809-5GFBS | draft TR | Apple Computer Trading Co. Ltd | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] | |
S3-202741 | EC: New solution on authentication and authorization between EEC and ECS | pCR | Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
withdrawn | [WTS] [JSN] |
S3-202742 | EC: New solution on authentication and authorization between EEC and ECS |
pCR revision of S3-202483 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202743 | EC: New Key issue on authorization during Edge Data Network change |
pCR revision of S3-202484 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202744 | EC: New solution on transport security for EDGE-1-9 interfaces |
pCR revision of S3-202485 |
Huawei, Hisilicon, ZTE | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202745 | pCR: Revocation of authorization of MBS communication service |
pCR revision of S3-202492 |
Huawei, Hisilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
approved | [WTS] [JSN] |
S3-202746 | pCR: New solution to MBS traffic protection |
pCR revision of S3-202493 |
Huawei, Hisilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
approved | [WTS] [JSN] |
S3-202747 | pCR: 33.846: Updates on key issue #2.1 |
pCR revision of S3-202494 |
Huawei, Hisilicon | 33.846 0.3.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202748 | New Key Issue on Provisioning of PNI-NPN credentials |
pCR revision of S3-202332 |
Huawei, Hisilicon, Ericsson, China Mobile | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202749 | Clarification on Key Issue #2 |
pCR revision of S3-202333 |
Huawei, Hisilicon, Ericsson | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
noted | [WTS] [JSN] |
S3-202750 | New Solution for Network Access Authentication with Credentials owned by an AAA external to the SNPN |
pCR revision of S3-202334 |
Huawei, Hisilicon | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202751 | Reply LS on security issue for on-boarding and remote provisioning |
LS out LS is reply to S3-202363 LS To: SA2 revision of S3-202336 |
Huawei, Hisilicon |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] | |||
S3-202752 | Skeleton of User Consent for 3GPP services |
pCR revision of S3-202338 |
Huawei, Hisilicon | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
approved | [WTS] [JSN] |
S3-202753 | Reply LS for IP address to GPSI translation |
LS out LS is reply to S3-202370 LS To: SA6 revision of S3-202343 |
Huawei, Hisilicon |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] | |||
S3-202754 | New key issue on security of one-to-one communication over PC5 |
pCR revision of S3-202346 |
Huawei, Hisilicon | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202755 | New solution on security establishment of one-to-one PC5 communication |
pCR revision of S3-202347 |
Huawei, Hisilicon | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202756 | New solution on Authentication between EEC and EES |
pCR revision of S3-202348 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202757 | New solution on Authentication between EEC and ECS |
pCR revision of S3-202349 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202758 | update to KI#10 User's consent for exposure of information to Edge Applications |
pCR revision of S3-202598 |
Huawei, Hisilicon, Samsung | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202759 | New solution on Security of Network Information Provisioning to Local Applications |
pCR revision of S3-202351 |
Huawei, Hisilicon | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202760 | Draft TR 33.850 | draft TR | Huawei, Hisilicon | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
approved | [WTS] [JSN] | |
S3-202761 | New solution to protect MBS traffic in transport layer |
pCR revision of S3-202477 |
Huawei, Hisilicon, Qualcomm | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
approved | [WTS] [JSN] |
S3-202762 | New solution to protect MBS traffic in service layer |
pCR revision of S3-202478 |
Huawei, Hisilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-bis-e AI: 2.11 |
approved | [WTS] [JSN] |
S3-202763 | New key issue on groupcast security |
pCR revision of S3-202393 |
Huawei, HiSilicon, CATT, Lenovo, Motorola Mobility | 33.847 0.2.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202764 | Draft TR 33.839 - FS_eEDGE_SEC | draft TR | Huawei, Hisilicon | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] | |
S3-202765 | draftTR 33.862 | draft TR | China Mobile | FS_SEC_5GMSG | Rel-17 |
S3-100-bis-e AI: 2.15 |
approved | [WTS] [JSN] | |
S3-202766 | Key issue on cyber-attacks detection supported by NWDAF |
pCR revision of S3-202534 |
China Mobile, Lenovo, Motorola Mobility, Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.866 0.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
approved | [WTS] [JSN] |
S3-202767 | draftTR 33.866 | draft TR | China Mobile | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
approved | [WTS] [JSN] | |
S3-202768 | Add content to clause 4 |
pCR revision of S3-202473 |
Huawei, HiSilicon | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
approved | [WTS] [JSN] |
S3-202769 | New solution on Key management in discovery procedure |
pCR revision of S3-202469 |
Huawei, HiSilicon | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202770 | Update key issue #2 | pCR | Huawei, HiSilicon | 33.84 0.1.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
withdrawn | [WTS] [JSN] |
S3-202771 | New solution on discovery protection |
pCR revision of S3-202470 |
Huawei, HiSilicon | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
noted | [WTS] [JSN] |
S3-202772 | New solution to verify the location information |
pCR revision of S3-202479 |
Huawei, HiSilicon | 33.854 0.1.0 | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] |
S3-202773 | pCR to TR33.847- Reuse LTE security mechanism for 5G ProSe open discovery |
pCR revision of S3-202409 |
CATT | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202774 | pCR to TR33.847- Reuse LTE security mechanism for 5G ProSe restricted discovery |
pCR revision of S3-202410 |
CATT | 33.847 0.1.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202775 | Draft TR 33.847 v0.2.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] | |
S3-202776 | Solution on Authentication and Authorization between the Edge Enabler Client and the Edge Configuration Server |
pCR revision of S3-202500 |
CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202777 | Solution on Authentication and Authorization between the EEC and the EES when the ECS is deployed by the ECSP |
pCR revision of S3-202501 |
CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202778 | Solution on Authentication and Authorization between the EEC and the EES when the ECS is deployed by the MNO |
pCR revision of S3-202502 |
CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202779 | Solution on the service capability exposure to the EAS |
pCR revision of S3-202503 |
CATT | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202780 | ProSe- New solution on security of UE-to-UE relay |
pCR revision of S3-202451 |
Apple | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-bis-e AI: 2.9 |
approved | [WTS] [JSN] |
S3-202781 | Authentication and Authorization with the Edge Data Network |
pCR revision of S3-202605 |
Lenovo, Motorola Mobility, Samsung | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-bis-e AI: 2.8 |
approved | [WTS] [JSN] |
S3-202782 | Update of Solution#15 |
pCR revision of S3-202603 |
Lenovo, Motorola Mobility | 33.809 0.10.0 | FS_5GFBS | Rel-16 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] |
S3-202783 | Network access authentication with credentials owned by an entity separate from the SNPN |
pCR revision of S3-202606 |
Lenovo, Motorola Mobility | 33.857 0.1.0 | FS_eNPN_SEC | Rel-17 |
S3-100-bis-e AI: 2.12 |
approved | [WTS] [JSN] |
S3-202784 | draft TR 33.867 | pCR | Huawei, Hisilicon | 33.867 0.0.0 | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
withdrawn | [WTS] [JSN] |
S3-202785 | draft TR 33.867 | draft TR | Huawei Technologies Sweden AB | FS_UC3S | Rel-17 |
S3-100-bis-e AI: 2.14 |
approved | [WTS] [JSN] | |
S3-202786 | Editorial updates of solution titles |
pCR revision of S3-202445 |
Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202787 | TR 33.854 v0.2.0 | draft TR | Qualcomm Incorporated | FS_UAS_SEC | Rel-17 |
S3-100-bis-e AI: 2.7 |
approved | [WTS] [JSN] | |
S3-202788 | Ed.note resolution in solution summary of sol.4.4 |
pCR revision of S3-202441 |
Nokia, Nokia Shanghai Bell | 33.846 0.7.0 | FS_AUTH_ENH | Rel-16 |
S3-100-bis-e AI: 2.5 |
approved | [WTS] [JSN] |
S3-202789 | Reply LS on user consent requirements for analytics |
LS out LS is reply to S3-202361 source LS: S2-2004560 LS To: SA WG2 revision of S3-202396 |
Nokia | Rel-17 |
S3-100-bis-e AI: 2.16 |
approved | [WTS] [JSN] | ||
S3-202790 | KI on Privacy preservation for transmitted data between multiple NWDAF instances |
pCR revision of S3-202425 |
Nokia, Nokia Shanghai Bell | 33.866 17.0.0 | FS_eNA_SEC | Rel-17 |
S3-100-bis-e AI: 2.16 |
approved | [WTS] [JSN] |
S3-202791 | TR_33.851_IIoT_Sec | draft TR | Nokia Germany | FS_IIoT_SEC | Rel-17 |
S3-100-bis-e AI: 2.1 |
approved | [WTS] [JSN] | |
S3-202792 | Scope for TR 33.840 |
pCR revision of S3-202660 |
China Telecom, Huawei, HiSilicon, CATT, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Deutsche Telekom | 33.84 0.0.3 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
approved | [WTS] [JSN] |
S3-202793 | TR33.840 v0.1.0 | draft TR | China Telecommunications | FS_disagg_gNB_Sec | Rel-17 |
S3-100-bis-e AI: 2.13 |
approved | [WTS] [JSN] |
494 documents (0.45822310447693 seconds)