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-243800 | Agenda | agenda | SA WG3 Chair |
S3-118 AI: 1 |
approved | [WTS] [JSN] | |||
| S3-243801 | Report from last SA3 meeting | report | MCC |
S3-118 AI: 2.1 |
approved | [WTS] [JSN] | |||
| S3-243802 | Process for SA3#118 | other | SA WG3 Chair |
S3-118 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-243803 | Detailed agenda planning | other | SA WG3 Chair |
S3-118 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-243804 | SA3 meeting calendar | other | SA WG3 Chair |
S3-118 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-243805 | Report to SA3 from SA |
report revised to S3-244120 |
SA WG3 Vice Chair |
S3-118 AI: 2.1 |
revised | [WTS] [JSN] | |||
| S3-243806 | Recent attack on polynomial based MACs with short tag | LS in | ETSI SAGE |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243807 | LS on Establishment of new Focus Group on Artificial Intelligence Native for Telecommunication Networks (FG-AINN) |
LS in LS reply in S3-243973, S3-245128 |
ITU-T |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243808 | LS on UE behaviour in case of SUCI calculation failure |
LS in LS reply in S3-244181, S3-244183, S3-244306 |
C1-245039 |
S3-118 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-243809 | LS on obtaining user consent for the exposure of User Sensitive Information |
LS in LS reply in S3-244306 |
S6a240323 |
S3-118 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-243810 | Reply LS on recursively defined JSON structures and reply to LS C4-241343 | LS in | C4-243520 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243811 | Draft TR 33.794 | draft TR | Lenovo | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] | |
| S3-243812 | LS reply to 3GPP Reply-LS on PQC Migration |
LS in LS reply in S3-244307, S3-243868, S3-244156, S3-244201, S3-244307 |
GSMA |
S3-118 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-243813 | Reply LS on Clarification of requirements for Ambient IoT | LS in | R1-2407364 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243814 | LS on security key update of inter-CU SCG LTM |
LS in LS reply in S3-244317, S3-244244, S3-244317 |
R2-2407602 |
S3-118 AI: 4.12 |
replied to | [WTS] [JSN] | |||
| S3-243815 | Reply LS on the Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | LS in | R3-244785 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243816 | Response LS to SA3 on architecture of NR Femto | LS in | R3-244831 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243817 | Draft TR 33.790 | draft TR | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-243818 | LS on AIML data collection |
LS in LS reply in S3-244308, S3-243887, S3-244137, S3-244308, S3-245038 |
RP-242389 |
S3-118 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-243819 | Reply LS on Clarifications related to User Identities | LS in | S1-242347 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243820 | Reply LS on Clarification of requirements for Ambient IoT | LS in | S1-242527 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243821 | LS on security considerations for 5G ProSe multi-hop relays |
LS in LS reply in S3-244371, S3-244371 |
S2-2407207 |
S3-118 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-243822 | LS Reply on ""A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies"" | LS in | S2-2408691 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243823 | Draft TR 33.757 | draft TR | China Telecom | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
approved | [WTS] [JSN] | |
| S3-243824 | Reply LS on clarifications on consent management | LS in | S2-2409440 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243825 | Draft TR 33.776 | draft TR | Cisco | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
approved | [WTS] [JSN] | |
| S3-243826 | Reply LS on KI#3 UE-Satellite-UE Communication Architectures | LS in | S2-2409442 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243827 | Draft TR 33.700-29 | draft TR | CATT | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] | |
| S3-243828 | Draft TR 33.713 | draft TR | OPPO | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] | |
| S3-243829 | Draft TR 33.700-32 | draft TR | Interdigital | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] | |
| S3-243830 | Draft TR 33.759 | draft TR | Ericsson | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
approved | [WTS] [JSN] | |
| S3-243831 | Draft TR 33.743 | draft TR | Huawei | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-243832 | Draft TR 33.784 | draft TR | China Mobile | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] | |
| S3-243833 | Draft TR 33.749 | draft TR | China Unicom | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] | |
| S3-243834 | LS on CAPIF phase 3 security considerations |
LS in LS reply in S3-244340, S3-243866, S3-244037, S3-244182, S3-244340 |
S6-243764 |
S3-118 AI: 5.19 |
replied to | [WTS] [JSN] | |||
| S3-243835 | Version 2.0 of 256-bit AICI. | LS in | ETSI SAGE |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243836 | LS on SG17 new work item ITU-T X.5Gsec-FMSC: Security requirements and guidelines for fixed, mobile and satellite convergence of IMT-2020 networks and beyond | LS in | ITU-T |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243837 | LS on SG17 new work item ITU-T TR.IMT2030-sec-con: ""Security Consideration for IMT2030 Networks"" | LS in | ITU-T |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243838 | LS on SG17 new work item TR.sa_RAN - Technical Report on ""Security Attacks in Radio Access Networks"" |
LS in LS reply in S3-244309, S3-244309 |
ITU-T |
S3-118 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-243839 | LS on Way forward on working agreement #63 | LS in | SP-241387 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243840 | Draft TR 33.754 | draft TR | Ericsson | FS_MASSS_Sec | Rel-19 |
S3-118 AI: 5.15 |
approved | [WTS] [JSN] | |
| S3-243841 | LS on maintaining specification consistency between GSMA and 3GPP on 5G roaming over roaming intermediaries. | LS in | SP-241405 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243842 | LS on Further Clarification for Ambient IoT Security | LS in | SP-241419 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243843 | Reply LS on CEN's requirements for eCall over IMS | LS in | SP-241421 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243844 | KI#1 Conclusion Alignment to SA Plenary Agreements | pCR | Lenovo | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243845 | KI#1 Conclusion Update | pCR | Lenovo | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243846 | Solution#1 assumptions clarification | pCR | Lenovo | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243847 | Solution#9 Update |
pCR revised to S3-244332 |
Lenovo | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243848 | KI#2 Initial Conclusion | pCR | Lenovo | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243849 | Solution to KI#1 |
pCR revised to S3-244344 |
Lenovo | 33.700-22 0.1.0 | FS_eZTS, FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243850 | Updates to Solution#11 |
pCR revised to S3-244336 |
Lenovo | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243851 | [MCXSec4] 33180 R19 MC Recording Server Introduction | CR | Airbus, Motorola Solutions | 33.180 18.1.0 CR#213 catC | MCXSec4 | Rel-19 |
S3-118 AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-243852 | Security re-establishment for Trusted non-3GPP access | draftCR | Lenovo | Non3GPPMob_Sec | Rel-19 |
S3-118 AI: 4.13 |
merged | [WTS] [JSN] | |
| S3-243853 | Addition of UDR security requirements | CR | BSI (DE) | 33.501 19.0.0 CR#2048 catF | SCAS_5G_UDR | Rel-19 |
S3-118 AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-243854 | An update for Key Issue #2: Authorization for 5G Ambient IoT Services | pCR | InterDigital, Europe, Ltd. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243855 | Solution for Lightweight AIoT ID privacy |
pCR revised to S3-244470 |
InterDigital, Europe, Ltd. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243856 | TCG progress - report from TCG rapporteur | other | InterDigital, Europe, Ltd. |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243857 | new solution on UUAA for USS changeover |
pCR revised to S3-244426 |
Huawei, HiSilicon | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-243858 | conclusions for KI#1 | pCR | Huawei, HiSilicon | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
merged | [WTS] [JSN] |
| S3-243859 | Sol#5 update to address EN | pCR | Huawei, HiSilicon | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243860 | Additional conclusions for KI#3 |
pCR revised to S3-244407 |
Huawei, HiSilicon | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243861 | conclusions for KI#1 | pCR | Huawei, HiSilicon | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243862 | conclusions for KI#2 | pCR | Huawei, HiSilicon | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243863 | new solution for KI1.1 - CAPIF-8 security |
pCR revised to S3-244341 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243864 | new solution for KI1.2 - resource owner authorized revocation |
pCR revised to S3-244343 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243865 | new solution for KI1.3 - resource-level and api-level authorization and revocation |
pCR revised to S3-244349 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243866 | draft reply LS to SA6 on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 LS To: SA6 |
Huawei, HiSilicon | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] | |
| S3-243867 | draft reply LS to SA6 Internal 5G Core information expose to trusted AF |
LS out LS is reply to SA6 LS To: SA7 |
Huawei, HiSilicon |
S3-118 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-243868 | draft reply LS to GSMA on PQC migration |
LS out LS is reply to S3-243812 LS To: GSMA |
Huawei, HiSilicon |
S3-118 AI: 3 |
merged | [WTS] [JSN] | |||
| S3-243869 | Add specific UDR SCAS test cases for TS 33.530 |
pCR revision of S3-243419 revised to S3-244310 |
BSI (DE) | 33.530 0.1.0 | SCAS_5G_UDR | Rel-19 |
S3-118 AI: 4.2 |
revised | [WTS] [JSN] |
| S3-243870 | Add an appendix of threats to the UDR | CR | BSI (DE) | 33.926 19.2.0 CR#100 catF | SCAS_5G_UDR | Rel-19 |
S3-118 AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-243871 | Clarification on TC_BVT_PORT_SCANNING |
draftCR revised to S3-244313 |
BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
revised | [WTS] [JSN] | |
| S3-243872 | EN resolution in KI#1 Solution #3 "New Data Collection NFs" | pCR | OTD_US | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243873 | eZTS conclusion for security event data records | pCR | Johns Hopkins University APL | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243874 | Solution for AIoT ID ephemeral security context |
pCR revised to S3-244477 |
InterDigital, Europe, Ltd. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243875 | Address ENs in Solution 1 |
other revised to S3-244320 |
vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-243876 | Correction on Evaluation of Solution 7 | other | vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-243877 | Discussion on Way Forward for Key Issue 1 of LTM | discussion | vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243878 | LS on security handling for inter-CU LTM |
LS out LS To: RAN2 |
vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243879 | New Solution on Mitigation of Security Issues of Unprotected NAS Reject |
pCR revised to S3-244391 |
vivo | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243880 | Conclusion for Key Issue#1 | pCR | vivo | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-243881 | Discussion on Design Principles for AIoT Authentication | discussion | vivo | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] | |
| S3-243882 | KI#5, New Sol: AIoT device authentication |
pCR revised to S3-244449 |
vivo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243883 | New Key Issue on Exposure of Inventory Device Quantity |
pCR revised to S3-244489 |
vivo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243884 | New Sol: Protection on quantity of AIoT devices during Inventory | pCR | vivo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243885 | KI#4, New Sol: Communication Security of intermediate UE interacting with AIoT device | pCR | vivo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243886 | Discussion on AIML data collection | discussion | vivo | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |
| S3-243887 | LS on AIML data collection |
LS out LS is reply to S3-243818 LS To: RAN, SA, SA2, SA5 |
vivo | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |
| S3-243888 | Address ENs in solution #4 |
pCR revised to S3-244440 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243889 | Address ENs in Solution #10 |
pCR revised to S3-244443 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243890 | Address ENs in solution #14 |
pCR revised to S3-244438 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243891 | Address ENs in Solution #15 |
pCR revised to S3-244445 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243892 | Discussion on basic conclusion of key issue#2 | discussion | vivo, China Mobile | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
noted | [WTS] [JSN] | |
| S3-243893 | Basic Conclusion for key issue#2 |
pCR revised to S3-244446 |
vivo, China Mobile | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243894 | Conclusion for Key Issue#2 on NEF security requirement | pCR | vivo, China Mobile, China Unicom, China Telecom | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243895 | Discussion on Wayforward for Key Issue 3 of AIML | discussion | vivo | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
noted | [WTS] [JSN] | |
| S3-243896 | Conclusion for key Issue#3 |
pCR revised to S3-244514 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243897 | LS to SA2 on Security Requirement on Restricting Exposure of UE ID for Sample Alignment |
LS out LS To: SA2 |
vivo | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
noted | [WTS] [JSN] | |
| S3-243898 | Addition of UDR security requirements | CR | BSI (DE) | 33.501 19.0.0 CR#2049 catF | SCAS_5G_UDR | Rel-19 |
S3-118 AI: 4.11 |
withdrawn | [WTS] [JSN] |
| S3-243899 | Add an appendix of threats to the UDR | CR | BSI (DE) | 33.926 19.2.0 CR#101 catF | SCAS_5G_UDR | Rel-19 |
S3-118 AI: 4.11 |
withdrawn | [WTS] [JSN] |
| S3-243900 | Add LI impacts to Conclusion for KI#1 in TR 33.757 | pCR | Johns Hopkins University APL | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243901 | Add LI impacts to Conclusion for KI#3 in TR 33.757 |
pCR revised to S3-244339 |
Johns Hopkins University APL | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243902 | Addition of UDR security requirements | draftCR | BSI (DE) | SCAS_5G_UDR | Rel-19 |
S3-118 AI: 4.11 |
withdrawn | [WTS] [JSN] | |
| S3-243903 | AIoT authentication integrated with data transmission | discussion | KPN | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] | ||
| S3-243904 | Evaluation update for solution #5 (Using ACME protocol for certificate enrolment) | pCR | Google Ireland Limited | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-243905 | Evaluation update for solution #7 (Using ACME protocol for secure transport of messages) | pCR | Google Ireland Limited | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-243906 | Solution for certificate renewal for ACME in 5G SBA |
pCR revised to S3-244412 |
Google Ireland Limited | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-243907 | A server-initiated ACME certificate renewal for 5G SBA | pCR | Google Ireland Limited | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
noted | [WTS] [JSN] |
| S3-243908 | Living document for CryptoSP: draftCR to TS 33.501, Updates to cryptographic profiles | draftCR | Ericsson | CryptoSP | Rel-19 |
S3-118 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243909 | Living document for CryptoSP: draftCR to TS 33.210, Updates to cryprographic profiles | draftCR | Ericsson | CryptoSP | Rel-19 |
S3-118 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243910 | Living document for CryptoSP: draftCR to TS 33.310, Updates to cryptographic profiles | draftCR | Ericsson | CryptoSP | Rel-19 |
S3-118 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243911 | Living document for CryptoSP: draftCR to TS 33.203, Updates to cryptographic profiles |
draftCR revised to S3-244311 |
Ericsson | CryptoSP | Rel-19 |
S3-118 AI: 4.8 |
revised | [WTS] [JSN] | |
| S3-243912 | Solution proposal for key issue #7 |
pCR revised to S3-244413 |
Cisco Systems | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-243913 | ACME and CMPv2 for ACM in SBA | discussion | Cisco Systems, NCSC, Johns Hopkins University APL, Google | Rel-19 |
S3-118 AI: 5.4 |
noted | [WTS] [JSN] | ||
| S3-243914 | Conclusions for TR 33.776 |
pCR revised to S3-244511 |
Cisco Systems | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-243915 | Add an appendix of threats to the UDR | draftCR | BSI (DE) | SCAS_5G_UDR | Rel-19 |
S3-118 AI: 4.11 |
withdrawn | [WTS] [JSN] | |
| S3-243916 | Alternatives to Solution #21 |
pCR revised to S3-244392 |
InterDigital, Europe, Ltd. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243917 | Merger of Solutions #8 and #21 |
pCR revised to S3-244393 |
InterDigital, Europe, Ltd. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243918 | Merger of Solutions #9 and #21 |
pCR revised to S3-244394 |
InterDigital, Europe, Ltd. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243919 | Merger of Solutions #15 and #21 |
pCR revised to S3-244395 |
InterDigital, Europe, Ltd. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243920 | Solution of Privacy protection in VFL |
pCR revised to S3-244444 |
InterDigital Communications | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243921 | LS on 5G SA Roaming Anomaly Detection in the context of PRINS |
LS out LS is reply to S3-242364 LS To: GSMA DESS revised to S3-244482 |
BSI (DE) | Rel-18 |
S3-118 AI: 3 |
revised | [WTS] [JSN] | ||
| S3-243922 | Discussion paper on privacy protection in sample alignment | discussion | InterDigital Communications | Rel-19 |
S3-118 AI: 5.13 |
noted | [WTS] [JSN] | ||
| S3-243923 | Update of Solution #1: Solution reusing existing interfaces and security mechanisms for energy related information collection | pCR | IIT Bombay | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-243924 | Update on Key Issue 1 related to security aspects on user consent for energy information collection |
pCR revised to S3-244503 |
IIT Bombay | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-243925 | New solution for security aspects on user consent for policy update based on energy information | pCR | IIT Bombay | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-243926 | Update on Key Issue 2 related to security aspects on user consent for energy information exposure |
pCR revised to S3-244504 |
IIT Bombay | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-243927 | New solution for security aspects on user consent for energy information exposure/retrieval | pCR | IIT Bombay | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-243928 | Discussion on security overhead for collecting and exposing energy information | discussion | IIT Bombay | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] | ||
| S3-243929 | Solution #6 Update |
pCR revised to S3-244328 |
MITRE-FFRDC | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243930 | eZTS Sol 11 Evaluation |
pCR revised to S3-244333 |
MITRE-FFRDC | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243931 | eZTS KI 1 Conclusions |
pCR revised to S3-244327 |
MITRE-FFRDC | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243932 | eZTS KI 2 Conclusions | pCR | MITRE-FFRDC, OTD_US | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243933 | Living CR for Non3GPPMobility |
draftCR revised to S3-244326 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-118 AI: 4.13 |
revised | [WTS] [JSN] | |
| S3-243934 | Discussion paper for Fast BSS mobility domain and TNGF domain | discussion | Nokia, Charter | Non3GPPMob_Sec | Rel-19 |
S3-118 AI: 4.13 |
noted | [WTS] [JSN] | |
| S3-243935 | TNGF and TWIF solution | other | Nokia, Charter | Non3GPPMob_Sec | Rel-19 |
S3-118 AI: 4.13 |
merged | [WTS] [JSN] | |
| S3-243936 | NSWO text alignment |
other revised to S3-244507 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-118 AI: 4.13 |
revised | [WTS] [JSN] | |
| S3-243937 | KI2 conclusion | pCR | Nokia | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-243938 | KI4 conclusion | pCR | Nokia | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-243939 | solution 3 update |
pCR revised to S3-244499 |
Nokia | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243940 | Discussion paper for CT1 LS on SUCI calculation failure | discussion | Nokia | Rel-19 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-243941 | Security mechanism for the LTM case where CU is acting as SN and MN is unchanged | other | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-243942 | Security mechanism for the LTM case where CU is acting as MN and SN is unchanged | other | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243943 | overall summary to the solutions in the living CR | other | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-243944 | conclusion to key issue#1 regarding split MME architecture | pCR | Huawei, HiSilicon | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-243945 | conclusion to key issue#2 | pCR | Huawei, HiSilicon | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-243946 | update to key issue#5 on authentication |
pCR revised to S3-244453 |
Huawei, HiSilicon | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243947 | update to key issue#4 on information protection |
pCR revised to S3-244455 |
Huawei, HiSilicon | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243948 | solution on protection for inventory and command procedure |
pCR revised to S3-244366 |
Huawei, HiSilicon | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243949 | discussion paper on NAS security in Split MME architecture | discussion | Huawei, HiSilicon | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
noted | [WTS] [JSN] | |
| S3-243950 | Discussion paper on the selection of algorithm in LTM | discussion | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243951 | conclusion to key issue#1 |
pCR revised to S3-244500 |
Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243952 | withdrawn |
LS out LS To: SA3 |
Huawei, HiSilicon | Rel-19 |
S3-118 AI: 3 |
withdrawn | [WTS] [JSN] | ||
| S3-243953 | Resolve EN on solution 1 for kI#1 | pCR | Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-243954 | conclusion to key issue#3 | pCR | Huawei, HiSilicon | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243955 | Evaluation for Solution 11 to KI3 | pCR | Huawei, HiSilicon | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243956 | conclusion to key issue#3 |
pCR revised to S3-244447 |
Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243957 | conclusion to key issue#4 |
pCR revised to S3-244448 |
Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243958 | Update to sol#3 for KI#2 |
pCR revised to S3-244404 |
Huawei, HiSilicon | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-243959 | Resolution of EN on solution 15 | pCR | Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-243960 | update on solution 9 |
pCR revised to S3-244442 |
Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243961 | Resolution of EN on solution 9 | pCR | Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243962 | Resolve EN to Sol#3 |
pCR revised to S3-244405 |
Huawei, HiSilicon | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-243963 | Resolve EN to Sol#2 | pCR | Huawei, HiSilicon | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-243964 | Resolve EN to KI#2 | pCR | Huawei, HiSilicon | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-243965 | Terminology alignment of TR 33.743 | pCR | Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243966 | Discussion on multi-hop U2NW relay solutions and way forward for the conclusion | discussion | Huawei, HiSilicon | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
noted | [WTS] [JSN] | |
| S3-243967 | Update the evaluation of solution 5 in TR 33.743 |
pCR revised to S3-244481 |
Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243968 | Conclusion to KI#1 - multi-hop U2NW discovery |
pCR revised to S3-244375 |
Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243969 | Conclusion to KI#1 - multi-hop U2NW link setup | pCR | Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-243970 | Conclusion to KI#2 - multi-hop U2U discovery | pCR | Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-243971 | Conclusion to KI#2 - multi-hop U2U link setup | pCR | Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-243972 | Reply LS on security considerations for 5G ProSew multi-hop relays |
LS out LS is reply to S3-243821 source LS: S2-2407207 LS To: SA2 |
Huawei, HiSilicon | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] | |
| S3-243973 | Reply LS on including the HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS out LS is reply to S3-243807 source LS: C1-244647 LS To: CT1 |
Huawei, HiSilicon | Rel-18 |
S3-118 AI: 3 |
withdrawn | [WTS] [JSN] | ||
| S3-243974 | address EN to KI#4 |
pCR revised to S3-244414 |
Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243975 | address EN to KI#9 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-243976 | New solution to KI#3 and conclusion | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-243977 | conclusion to KI#2 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-243978 | New solution to KI#4 and conclusion |
pCR revised to S3-244418 |
Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243979 | conclusion to KI#5 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-243980 | conclusion to KI#6 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-243981 | New solution to KI#7 and conclusion |
pCR revised to S3-244419 |
Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243982 | conclusion to KI#8 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-243983 | conclusion to KI#9 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-243984 | add evaluation to solution#8 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243985 | add evaluation to solution#9 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243986 | add evaluation to solution#11 | pCR | Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243987 | Add new test case to 33.117 on recommended algorithms checking | other | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
noted | [WTS] [JSN] | |
| S3-243988 | Living document to Draft CR TS 33.511 |
draftCR revised to S3-244505 |
Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
revised | [WTS] [JSN] | |
| S3-243989 | Living document to Draft TS 33.117 | draftCR | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
approved | [WTS] [JSN] | |
| S3-243990 | Living document to Draft TR 33.926 | draftCR | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
approved | [WTS] [JSN] | |
| S3-243991 | Living document to Draft TS 33.514 | draftCR | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
approved | [WTS] [JSN] | |
| S3-243992 | Add new test case to 33.117 on default using algorithms to test 4.2.3.2.4 | other | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
noted | [WTS] [JSN] | |
| S3-243993 | Discussion paper on algorithm checking in TS 33.117 | other | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
noted | [WTS] [JSN] | |
| S3-243994 | Update to solution 23 |
pCR revised to S3-244386 |
Huawei, HiSilicon | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243995 | New solution for authentication on split MME architecture in S&F mode |
pCR revised to S3-244396 |
Huawei, HiSilicon | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243996 | Evaluation on sol#23 | pCR | Huawei, HiSilicon | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243997 | Evaluation on sol#25 | pCR | Huawei, HiSilicon | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243998 | Way forward for eZTS study | discussion | Huawei, HiSilicon | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
noted | [WTS] [JSN] | |
| S3-243999 | Conclusion updates | pCR | Huawei, HiSilicon | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-244000 | Solution #5 updates |
pCR revised to S3-244329 |
Huawei, HiSilicon | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244001 | LS on NR Femto GW for aggregating user plane traffic |
LS out LS To: RAN3 |
Charter Communications, Inc | Rel-19 |
S3-118 AI: 5.17 |
noted | [WTS] [JSN] | ||
| S3-244002 | Discussion paper: Observations on TR 38.799 Study on additional topological enhancements for NR | discussion | Charter Communications, Inc | Rel-19 |
S3-118 AI: 5.17 |
noted | [WTS] [JSN] | ||
| S3-244003 | Updates for solution #3 to address the needs for KI#9 |
pCR revised to S3-244416 |
Charter Communications, Inc | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244004 | Discussion paper on access to local services for Femto | discussion | Charter Communications, Inc | Rel-19 |
S3-118 AI: 5.17 |
noted | [WTS] [JSN] | ||
| S3-244005 | Editorial updates to KI#9 descriptions |
pCR revised to S3-244415 |
Charter Communications, Inc | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244006 | Conclusion on KI#4 VFL communication security | pCR | OPPO, vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244007 | Sol on AIoT device ID privacy protection using anonymous key |
pCR revised to S3-244478 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244008 | Sol on temporary ID based AIoT device privacy protection |
pCR revised to S3-244479 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244009 | Update KI#4 for Command | pCR | OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244010 | Solution for AIoT Authentication Based on 5G-AKA |
pCR revised to S3-244367 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244011 | Evaluation for AIoT Authentication Based on 5G-AKA | pCR | OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244012 | Resolving ENs for AIoT KI#5 | pCR | OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244013 | New solution for key issue 3 | pCR | China Mobile Com. Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-244014 | Discussion paper for ACME | discussion | Charter Communications, Inc | Rel-19 |
S3-118 AI: 5.4 |
noted | [WTS] [JSN] | ||
| S3-244015 | New solution for authentication in Ambient IoT service | pCR | China Mobile Com. Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244016 | Conclusion on KI#6 certificate revocation |
pCR revised to S3-244512 |
Johns Hopkins University APL, US National Security Agency | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-244017 | TR 33.700-32 Conclusion for Key Issue#1 and Key Issue#2 | pCR | InterDigital Communications | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-244018 | TR 33.700-32 Conclusion for Key Issue#3 |
pCR revised to S3-244408 |
InterDigital Communications | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244019 | TR 33.759 Conclusion for Key Issue#1 |
pCR revised to S3-244427 |
InterDigital Communications, Qualcomm Incorporated | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-244020 | TR 33.743 Conclusion for Key Issue#1 |
pCR revised to S3-244376 |
InterDigital Communications | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244021 | LS-out Reply to LS on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 source LS: S6-243764 LS To: SA6 |
Nokia |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] | |||
| S3-244022 | KI2 Solution on security method retrieval in CAPIF interconnect |
pCR revised to S3-244353 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244023 | KI2 Solution on authentication aspect in CAPIF interconnect requesting security information from another CCF |
pCR revised to S3-244354 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244024 | KI2 Solution on authentication aspect in CAPIF interconnect when API invoker has not included CCF information |
pCR revised to S3-244355 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244025 | KI2 Solution on authorization token request handling in CAPIF interconnect |
pCR revised to S3-244356 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244026 | KI2 Solution on mapping an API invoker authorization request to the correct CCF in CAPIF interconnect |
pCR revised to S3-244357 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244027 | KI1.3 Solution on scope enhancing |
pCR revised to S3-244350 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244028 | RO consent management |
pCR revised to S3-244346 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244029 | KI5 Solution on authenticating multiple API invokers of the same RO |
pCR revised to S3-244463 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244030 | KI on Onboarding security issue |
pCR revised to S3-244464 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244031 | Solution on validation of correct GPSI in API invoker information |
pCR revised to S3-244465 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244032 | Editorial - Streamlining interconnect KI details |
pCR revised to S3-244466 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244033 | Concluding KI1 and KI2 in UIA |
pCR revised to S3-244409 |
DOCOMO Communications Lab. | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244034 | Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out source LS: S3-242427 LS To: SA4 |
China Mobile |
S3-118 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-244035 | Conclusion to KI#1 | pCR | China Telecomunication Corp., ZTE, Huawei, HiSilicon, China Mobile | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244036 | Conclusion to KI#2 |
pCR revised to S3-244337 |
China Telecomunication Corp., ZTE, Huawei, HiSilicon, China Mobile | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-244037 | reply LS on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 LS To: SA6 |
ZTE Corporation | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] | |
| S3-244038 | add evaluation for Sol#3 |
other revised to S3-244506 |
ZTE Corporation | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244039 | Resolve the EN in Sol#3 |
other revised to S3-244319 |
ZTE Corporation | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244040 | Resolve another EN in Sol#3 | other | ZTE Corporation | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-244041 | Conclusion to KI#3 | pCR | ZTE Corporation | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-244042 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244043 | New solution on KI#3 |
pCR revised to S3-244480 |
ZTE Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244044 | Add the evaluation for the Sol#2 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244045 | Clean up for TR 33.713 | pCR | ZTE Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244046 | Resolve the EN in the Sol#2 in TR 33.713 |
pCR revised to S3-244467 |
ZTE Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244047 | New Sol for KI#5 |
pCR revised to S3-244368 |
ZTE Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244048 | add conclusion to KI1 | pCR | ZTE Corporation | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-244049 | add conclusion to KI2 | pCR | ZTE Corporation | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-244050 | Clean up for TR 33.749 | pCR | ZTE Corporation | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244051 | New solution for KI#1.1 |
pCR revised to S3-244435 |
ZTE Corporation | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244052 | Update the KI#1.1 |
pCR revised to S3-244434 |
ZTE Corporation | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244053 | Change the EN to a NOTE in KI#4 | pCR | ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-244054 | Update Sol#1 to address the EN | pCR | ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244055 | Add a solution to KI#3 |
pCR revised to S3-244417 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244056 | Add conclusions to KI#1 |
pCR revised to S3-244420 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244057 | Add conclusions to KI#2 |
pCR revised to S3-244421 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244058 | Add conclusions to KI#3 | pCR | ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244059 | Add conclusions to KI#4 |
pCR revised to S3-244422 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244060 | Add conclusions to KI#5 |
pCR revised to S3-244423 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244061 | Add conclusions to KI#6 |
pCR revised to S3-244424 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244062 | Add conclusions to KI#7 | pCR | ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244063 | Add conclusions to KI#8 |
pCR revised to S3-244425 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244064 | Draft WID on security aspects of 5G NR Femto | other | ZTE Corporation | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
noted | [WTS] [JSN] | |
| S3-244065 | Resolve the EN in the Sol#1 in TR 33.721 |
pCR revised to S3-244471 |
ZTE Corporation | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-244066 | Update evaluation for Sol#1 in TR 33.721 |
pCR revised to S3-244472 |
ZTE Corporation | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-244067 | Update KI #1 in TR 33.721 | pCR | ZTE Corporation | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-244068 | Solution for key issue 1.1 | pCR | ZTE Corporation | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244069 | Clean up for TR 33.700-22 | pCR | ZTE Corporation | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244070 | Solution for key issue 2 | pCR | ZTE Corporation | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244071 | Conclusion on KI#3 VFL privacy | pCR | OPPO | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244072 | Conclusion of KI#3 in TR 33.700-32 | pCR | China Telecom | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-244073 | Conclusion of Key issue #1 in TR 33.700-29 | pCR | ChinaTelecom | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
not treated | [WTS] [JSN] |
| S3-244074 | Overall Summary of solutions |
pCR revised to S3-244382 |
Nokia | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244075 | Evaluation of solution #10 |
pCR revised to S3-244334 |
Nokia | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244076 | New solution for KI#1.1 CAPIF-8 reference point |
pCR revised to S3-244342 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244077 | New solution for KI#2 CAPIF interconnection |
pCR revised to S3-244358 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244078 | New solution for KI#1.2 resource owner authorization management |
pCR revised to S3-244345 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244079 | Integrity protection of inter-CU LTM Cell Switch Command MAC CE | other | OPPO | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | ||
| S3-244080 | Solution 4 evaluation updates |
pCR revised to S3-244330 |
Nokia | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244081 | Solution 7 evaluation updates |
pCR revised to S3-244331 |
Nokia | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244082 | Updates for solution 5 | pCR | Nokia | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244083 | Solution 6 updates | pCR | Nokia | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244084 | Evaluation of solution 6 |
pCR revised to S3-244441 |
Huawei, HiSilicon | 33.784 0.3.0 | eNA | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244085 | Resolution of EN on solution 6 | pCR | Huawei, HiSilicon | 33.784 0.3.0 | eNA | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244086 | K#2 Conclusion | pCR | Huawei, HiSilicon | 33.784 0.3.0 | eNA | Rel-19 |
S3-118 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244087 | updates and evaluation to solution #30 |
pCR revised to S3-244388 |
Huawei, HiSilicon | 33.700-29 0.4.0 | SAT | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244088 | updates and evaluation to solution #28 |
pCR revised to S3-244389 |
Huawei, HiSilicon | 33.700-29 0.4.0 | SAT | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244089 | KI1 conclusion | pCR | Huawei, HiSilicon | 33.700-29 0.4.0 | SAT | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244090 | Update and evaluation on solution 24 | pCR | Huawei, HiSilicon | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244091 | New solution on NAS secuity in split MME architecture |
pCR revised to S3-244397 |
Huawei, HiSilicon | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244092 | Addressing the ENs on token and Avatar ID of Solution#5 |
pCR revised to S3-244399 |
Huawei, HiSilicon | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-244093 | Addressing the ENs on user interaction of Solution#10 |
pCR revised to S3-244403 |
Huawei, HiSilicon | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-244094 | conclusion to KI#3 | pCR | Huawei, HiSilicon | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-244095 | Addressing the ENs on brute force and synchronization of Solution#2 |
pCR revised to S3-244428 |
Huawei, HiSilicon | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244096 | conclusion to KI#2.1 |
pCR revised to S3-244433 |
Huawei, HiSilicon | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244097 | conclusion to KI#2 | pCR | Huawei, HiSilicon | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-244098 | New key issue for Security and privacy aspects of local access | pCR | Nokia | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-244099 | Discussion of new Features in Version2 of 256-bit Specifications | discussion | Nokia |
S3-118 AI: 4.5 |
noted | [WTS] [JSN] | |||
| S3-244100 | Reply LS on security key update of inter-CU SCG LTM |
LS out LS is reply to S3-243814 source LS: R2-2407602 LS To: RAN2 revised to S3-244317 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244101 | LTM: Update to Solution 8 | other | Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-244102 | LTM: Evaluation of Solution 8 | other | Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-244103 | LTM: New Solution for Protecting NCC in MAC CE using AS Security Context | other | Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-244104 | LTM: New Solution for Protecting NCC in MAC CE using C-RNTI | other | Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-244105 | 33.700-32: Evaluation of Solution 26 and Conclusion on KI#1 |
pCR revised to S3-244410 |
Xiaomi EV Technology | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244106 | 33.700-32: Evaluation of Solution 27 and Conclusion on KI#2 |
pCR revised to S3-244411 |
Xiaomi EV Technology | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244107 | 33.721: Evaluation of Solution 4 | pCR | Xiaomi EV Technology | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-244108 | 33.721: Update to Key Issue 4 | pCR | Xiaomi EV Technology | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-244109 | 33.721: New Solution for Key Issue 4 | pCR | Xiaomi EV Technology | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
noted | [WTS] [JSN] |
| S3-244110 | Discussion on the S&F operation under the split MME architecture | discussion | Beijing Xiaomi Mobile Software | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
noted | [WTS] [JSN] | |
| S3-244111 | Conclusion for KI#1 in TR 33.700-29 | pCR | Beijing Xiaomi Mobile Software | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244112 | Conclusion for KI#2 in TR 33.700-29 |
pCR revised to S3-244385 |
Beijing Xiaomi Mobile Software | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244113 | Update to KI#4 in TR 33.713 | pCR | Beijing Xiaomi Mobile Software | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244114 | New solution on authorization of intermediate node for Ambient IoT services |
pCR revised to S3-244468 |
Beijing Xiaomi Mobile Software | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244115 | New solution on disabling operation procedure |
pCR revised to S3-244458 |
Beijing Xiaomi Mobile Software | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244116 | Update to solution #7 in TR 33.743 |
pCR revised to S3-244513 |
Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244117 | Update to solution #8 in TR 33.743 |
pCR revised to S3-244372 |
Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244118 | Conclusion for KI#1 in TR 33.743 | pCR | Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244119 | Reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-243821 source LS: S2-2407207 LS To: SA2 |
Beijing Xiaomi Mobile Software | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] | |
| S3-244120 | Report to SA3 from SA |
report revision of S3-243805 |
SA WG3 Chair |
S3-118 AI: 2.1 |
noted | [WTS] [JSN] | |||
| S3-244121 | Solution for Authentication and ID Privacy of AIoT devices with USIM on AIoT AS Layer |
pCR revised to S3-244450 |
Lenovo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244122 | Solution for Authentication and ID Privacy of AIoT devices with USIM on AIoT Layer |
pCR revised to S3-244451 |
Lenovo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244123 | Solution for Authentication and ID privacy of AIoT devices without USIM |
pCR revised to S3-244452 |
Lenovo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244124 | Solution on Privacy Protection for AIoT device | pCR | Sony | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244125 | Solution on Protection of transmitted information |
pCR revised to S3-244456 |
Sony | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244126 | Clarifying the threat for checking expiry of its own certificate | other | Qualcomm Incorporated |
S3-118 AI: 4.1 |
noted | [WTS] [JSN] | |||
| S3-244127 | Clarification to the TS 33.551 living draft CR on own certificate expiry | other | Qualcomm Incorporated |
S3-118 AI: 4.1 |
approved | [WTS] [JSN] | |||
| S3-244128 | Adding expiry time checking for peer certificates |
other revised to S3-244315 |
Qualcomm Incorporated |
S3-118 AI: 4.1 |
revised | [WTS] [JSN] | |||
| S3-244129 | Discussion on open issues of using FT under a TNGF | discussion | Qualcomm Incorporated, Huawei, Hisilicon, Cablelabs |
S3-118 AI: 4.13 |
noted | [WTS] [JSN] | |||
| S3-244130 | Mobility under a TNGF |
other revised to S3-244325 |
Qualcomm Incorporated, Huawei, Hisilicon, Cablelabs |
S3-118 AI: 4.13 |
revised | [WTS] [JSN] | |||
| S3-244131 | Discussion on possible response to LTM LS | discussion | Qualcomm Incorporated |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-244132 | Progress update on security handling for inter-CU LTM in non-DC cases |
LS out LS To: RAN2, RAN3 |
Qualcomm Incorporated |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-244133 | Clarifications on the IOPS enhancements in solution #3 |
pCR revised to S3-244390 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244134 | Proposed conclusions for key issues #1 & 2 for HSS in satellite |
pCR revised to S3-244383 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244135 | Proposed conclusions for key issue #1 & 2 for split MME deployment | pCR | Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244136 | Discussion on RAN plenary LS on AIML | discussion | Qualcomm Incorporated |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-244137 | Reply LS on AIML data collection |
LS out LS is reply to S3-243818 LS To: RAN |
Qualcomm Incorporated |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-244138 | A new solution for privacy protection of AIoT device identifier |
pCR revised to S3-244483 |
Qualcomm Incorporated | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244139 | A new solution for end-to-end security protection of command |
pCR revised to S3-244457 |
Qualcomm Incorporated | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244140 | reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-243821 LS To: SA2 revised to S3-244371 |
Qualcomm Incorporated |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] | |||
| S3-244141 | A new solution for multi-hop U2N relay communication security |
pCR revised to S3-244498 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244142 | Conclusion of KI#1 | pCR | Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244143 | Conclusion of KI#2 |
pCR revised to S3-244377 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244144 | Updating evaluations to solution #9 |
pCR revised to S3-244374 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244145 | Updating evaluations to solution #7 | pCR | Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244146 | Correction of references | pCR | Nokia | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
merged | [WTS] [JSN] |
| S3-244147 | Regional legislation compliance in relation to collection user information. | pCR | Nokia | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-244148 | Update of SID schedule | SID revised | Nokia | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] | |
| S3-244149 | Resolution of editors note concerning mitigating denial of service and malfunction message inspection – solution 14. | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-244150 | Update to KI#4 | pCR | Nokia | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244151 | Resolution of EN concerning message inspection, filtering and topology hiding – solution 13. |
pCR revised to S3-244492 |
Nokia, Nokia Shanghai Bell | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-244152 | Evaluation of solution 13 | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-244153 | Evaluation of solution 14 | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-244154 | Conclusion to KI#1 | pCR | Nokia, Nokia Shanghai Bell, Samsung | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244155 | Conclusion to KI#2 | pCR | Nokia, Nokia Shanghai Bell, Ericsson, Samsung | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244156 | LS on 3GPP ReplyLS on PQC Migration |
LS out LS is reply to S3-243812 LS To: GSMA PQTN TF |
Nokia, Nokia Shanghai Bell |
S3-118 AI: 3 |
merged | [WTS] [JSN] | |||
| S3-244157 | LS reply on Issues related to Analytics context transfer between AnLF(s) |
LS out LS is reply to S2-2409441 LS To: SA2 |
Ericsson |
S3-118 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-244158 | New solution for CAPIF interconnection |
pCR revised to S3-244359 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244159 | Solution for accessing UE resources by an application on another UE | pCR | Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244160 | Solution for nested API invocation |
pCR revised to S3-244461 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244161 | Resolving ENs in solution #6 |
pCR revised to S3-244430 |
Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244162 | Evaluation of solution #6 |
pCR revised to S3-244431 |
Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244163 | Security requirements for KI#1.1 | pCR | Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
merged | [WTS] [JSN] |
| S3-244164 | A new solution for KI#1.1 |
pCR revised to S3-244436 |
Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244165 | Conclusion for KI#1.1 | pCR | Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
merged | [WTS] [JSN] |
| S3-244166 | Solution for key issue #1.2 |
pCR revised to S3-244352 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244167 | Update to KI#1.2 |
pCR revised to S3-244351 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244168 | Update to KI#1 for fixing the terminology |
pCR revised to S3-244515 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244169 | LS on terminology alignment between SA6 and SA3 |
LS out LS To: SA6 revised to S3-244516 |
Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] | |
| S3-244170 | A new solution for KI#2.1 |
pCR revised to S3-244502 |
Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244171 | Editorial updates |
pCR revised to S3-244406 |
Ericsson | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-244172 | Overview | pCR | Ericsson | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-244173 | Discussion and way forward for zero trust study | discussion | China Mobile Com. Corporation | Rel-19 |
S3-118 AI: 5.1 |
noted | [WTS] [JSN] | ||
| S3-244174 | Update for solution 5 |
pCR revised to S3-244378 |
Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-244175 | AIoT - Security solution on Authentication |
pCR revised to S3-244369 |
Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244176 | AIoT - KI update on communication security | pCR | Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244177 | AIoT - Security solution on Privacy protection |
pCR revised to S3-244484 |
Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244178 | LTM - Update solution#4 |
other revised to S3-244321 |
Apple |
S3-118 AI: 4.12 |
revised | [WTS] [JSN] | |||
| S3-244179 | LTM - Update solution#5 |
other revised to S3-244322 |
Apple |
S3-118 AI: 4.12 |
revised | [WTS] [JSN] | |||
| S3-244180 | LTM - WID revision | other | Apple |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-244181 | Reply LS to SA6 on Metaverse user consent |
LS out LS is reply to S3-243808 LS To: SA6 revised to S3-244306 |
Apple |
S3-118 AI: 3 |
revised | [WTS] [JSN] | |||
| S3-244182 | Reply LS to SA6 on CAPIF security consideration |
LS out LS is reply to S3-243834 LS To: SA6 |
Apple |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] | |||
| S3-244183 | Reply LS to CT1 on UE bahaviour in case of SUCI calculation failure |
LS out LS is reply to S3-243808 LS To: CT1 |
Apple |
S3-118 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-244184 | Editorial change on CryptoSP living document draft CR to TS 33203 |
other revised to S3-244312 |
Apple |
S3-118 AI: 4.8 |
revised | [WTS] [JSN] | |||
| S3-244185 | Conclusion for KI#1 in TR 33.700-29 | pCR | OPPO | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244186 | Update KI #4 for Inventory | pCR | OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244187 | Solution on disabling operation procedure for AIoT services |
pCR revised to S3-244459 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244188 | Update of Solution #5: UE authentication and traffic protection in ATSSS-Lite | pCR | Ericsson | 33.754 1.0.0 | FS_MASSS_Sec | Rel-19 |
S3-118 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-244189 | Update for solution 6 |
pCR revised to S3-244379 |
Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-244190 | Data collection for security monitoring | draftCR | Ericsson | DUMMY | Rel-19 |
S3-118 AI: 5.1 |
noted | [WTS] [JSN] | |
| S3-244191 | Updated conclusion for Key Issue #1 "Data exposure for security evaluation and monitoring" | pCR | Ericsson | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-244192 | Update Solution #12 "Policy enforcement using NRF configuration and short access token lifetime" | pCR | Ericsson | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244193 | Conclusion for Key Issue #2 "Security mechanisms for policy enforcement at the 5G SBA" |
pCR revised to S3-244335 |
Ericsson | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244194 | Conclusion for KI#1: Third party specific user identities | pCR | Ericsson | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-244195 | Update of Solution 11: IMS (DC) capability exposure security based on existing specification | pCR | Ericsson | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-244196 | New WID on security support for the Next Generation Real Time Communication services Phase 2 | WID new | Ericsson, China Mobile | Rel-19 |
S3-118 AI: 5.2 |
noted | [WTS] [JSN] | ||
| S3-244197 | Update Solution#2 |
pCR revised to S3-244496 |
Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244198 | Update Solution#3 |
pCR revised to S3-244497 |
Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244199 | Update Solution#4 | pCR | Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-244200 | Update of Solution #5: Discussion on UPF exposure | pCR | Ericsson | 33.754 1.0.0 | FS_MASSS_Sec | Rel-19 |
S3-118 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-244201 | Draft_Reply-LS on PQC Migration |
LS out LS is reply to S3-243812 LS To: GSMA PQTN revised to S3-244307 |
Ericsson |
S3-118 AI: 3 |
revised | [WTS] [JSN] | |||
| S3-244202 | Public key distribution and Issuer claim verification of the Access Token | CR | Ericsson, Deutsche Telekom, AT&T, Samsung, KDDI | 33.501 19.0.0 CR#2050 catB | TEI19 | Rel-19 |
S3-118 AI: 4.11 |
not pursued | [WTS] [JSN] |
| S3-244203 | Support iat claim in the access token |
CR revised to S3-244510 |
Ericsson, AT&T, Charter Communications, Samsung | 33.501 19.0.0 CR#2051 catB | TEI19 | Rel-19 |
S3-118 AI: 4.11 |
revised | [WTS] [JSN] |
| S3-244204 | New solution for KI#1: Re-use existing SMF/UPF functionality | pCR | Ericsson, Nokia, Nokia Shanghai Bell | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-244205 | Conclusion for KI#1 |
pCR revised to S3-244338 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-244206 | AIoT: Security assumptions in the 5G system | pCR | Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244207 | AIoT: Security threats for KI#4 on protection of information during AIoT service communication | pCR | Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244208 | Updating KI#5 Authentication in Ambient IoT service |
pCR revised to S3-244454 |
Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244209 | New key issue for Authenticated and authorized access to devices in Ambient IoT via 3GPP core | pCR | Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244210 | New key issue for application layer authentication in Ambient IoT | pCR | Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244211 | New key issue for secure storage in AIoT devices |
pCR revised to S3-244365 |
Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244212 | New Key Issue on Amplification of resource exhaustion by exploiting AIoT | pCR | Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244213 | New solution to KI#3 Privacy by protecting AIoT device identifiers |
pCR revised to S3-244485 |
Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244214 | New solution to key issue #2: Authorization for 5G Ambient IoT services |
pCR revised to S3-244469 |
Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244215 | Resolve EN in Solution#1 | pCR | Ericsson | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-244216 | Evaluation for solution 5 |
pCR revised to S3-244380 |
Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-244217 | Conclusion for KI#1 | pCR | Ericsson | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-244218 | Conclusion of KI#1 | pCR | China Telecom Corporation Ltd. | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244219 | Conclusion for KI#2 | pCR | Ericsson | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-244220 | Evaluation for solution 6 |
pCR revised to S3-244381 |
Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-244221 | Conclusion of KI#2 | pCR | China Telecom Corporation Ltd. | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244222 | Reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS To: SA2 |
China Telecom Corporation Ltd. | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] | ||
| S3-244223 | Conclusion for KI#1 | pCR | Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
merged | [WTS] [JSN] |
| S3-244224 | Reply LS on including the HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS out LS To: CT1 |
China Telecom Corporation Ltd. |
S3-118 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-244225 | New KI - security of backhaul communication over feeder link in generic regenerative mode | pCR | Ericsson | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-244226 | New WID on UAS security enhancements | WID new | Ericsson | Rel-19 |
S3-118 AI: 5.11 |
noted | [WTS] [JSN] | ||
| S3-244227 | Solution to secure backhaul of generic regenerative architecture | pCR | Ericsson | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244228 | Resolve EN on vertical/horizontal key derivation for solution #6 | other | LG Electronics | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-244229 | Resolve EN on methods to deliver updated NCC for solution #6 | other | LG Electronics | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-244230 | Resolve EN on the cases for change of security algorithm for solution #6 |
other revised to S3-244323 |
LG Electronics | Rel-19 |
S3-118 AI: 4.12 |
revised | [WTS] [JSN] | ||
| S3-244231 | Evaluation for solution #6 | other | LG Electronics | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-244232 | LMF authorization for AI/ML model retrieval from NWDAF |
pCR revised to S3-244439 |
Ericsson | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244233 | Resolve ENs for Solution#5 | pCR | Ericsson | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244234 | Update Solution #5 |
pCR revised to S3-244495 |
Ericsson | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244235 | pCR to TR33.713 New solution for device authentication and data |
pCR revised to S3-244370 |
CATT | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244236 | pCR to TR33.713 New solution for protecting Device IDs in inventory scenarios |
pCR revised to S3-244486 |
CATT | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244237 | pCR to TR33.713 Update key issue#4 for adding threats and requirements | pCR | CATT | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244238 | pCR to TR33.713 Update key issue#5 for updating threats and requirements | pCR | CATT | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-244239 | pCR to TR33.743 Conclusion of KI#1 | pCR | CATT | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244240 | Solution on Disabling Enabling |
pCR revised to S3-244460 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244241 | pCR to TR33.743 Conclusion of KI#2 | pCR | CATT | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244242 | Interim Conclusion on KI#2 | pCR | OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244243 | pCR to TR33.700-29 Conclusion of KI#1 | pCR | CATT | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244244 | Reply LS on security handling for inter-CU SCG LTM |
LS out LS is reply to S3-243814 LS To: RAN2 |
CATT |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-244245 | New solution - Ambient IoT ID privacy |
pCR revised to S3-244487 |
Philips International B.V. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244246 | Solution#1 update - Addressing ENs |
pCR revised to S3-244508 |
Philips International B.V. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244247 | Conclusions KI#1 |
pCR revised to S3-244384 |
Philips International B.V. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244248 | Conclusions K#2 | pCR | Philips International B.V. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244249 | Evaluation of Solution #30 |
pCR revised to S3-244387 |
Philips International B.V. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244250 | New solution for inter-CU SCG LTM | other | CATT | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-244251 | New WID on enablers for Zero Trust Security | discussion | Motorola Mobility | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
noted | [WTS] [JSN] | |
| S3-244252 | Key Issue and Solution Mapping | pCR | Lenovo | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244253 | Signaling Monitoring Requirements | CR | Vodafone, Nokia, Nokia Shanghai Bell, Ericsson, Telefonica | 33.501 19.0.0 CR#2052 catB | MonStra-Sec | Rel-19 |
S3-118 AI: 4.14 |
not pursued | [WTS] [JSN] |
| S3-244254 | Living document on NR mobility enhancement |
draftCR revised to S3-244324 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244255 | Way forward for inter-CU LTM in non-DC cases | discussion | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-244256 | Updates to Solution#7 | other | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-244257 | Conclusion for inter-CU LTM in non-DC cases | other | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-244258 | Conclusion for inter-CU SCG LTM | other | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-244259 | Solution for SUPI privacy |
pCR revised to S3-244493 |
Samsung | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-244260 | Conclusion for key issue#3 | pCR | Samsung, Lenovo, Johns Hopkins University APL | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-244261 | Conclusion update for KI#2 for DNS messages protection | pCR | Samsung | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244262 | Conclusion update for KI#2 in TR 33.757 | pCR | Samsung, US National Security Agency | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244263 | Solution for digital asset request validation |
pCR revised to S3-244475 |
Samsung | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-244264 | Solution for security aspects of CAPIF interconnection |
pCR revised to S3-244360 |
Samsung, Nokia, Nokia Shanghai Bell | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244265 | Authorization for Nested API invocation |
pCR revised to S3-244462 |
Samsung | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244266 | Update to solution#7 in TR 33.749 |
pCR revised to S3-244432 |
Samsung | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244267 | Update to solution#8 in TR 33.749 |
pCR revised to S3-244501 |
Samsung | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244268 | [draft] Reply LS on AIML data collection |
LS out LS is reply to S3-243818 source LS: RP-242389 LS To: RAN |
Samsung | Rel-19 |
S3-118 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-244269 | Conclusion on KI #1 | pCR | Samsung | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244270 | Updates to Solution #21 |
pCR revised to S3-244494 |
Samsung | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244271 | Resolving EN in solution #6 |
pCR revised to S3-244400 |
Samsung | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-244272 | Evaluation update on solution #6 |
pCR revised to S3-244401 |
Samsung | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-244273 | Updates to solution #7 | pCR | Samsung | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
merged | [WTS] [JSN] |
| S3-244274 | New solution on protecting AIoT ID |
pCR revised to S3-244488 |
Samsung | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244275 | Update to solution#4 | pCR | Lenovo | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244276 | Address ENs of Sol7 on Protect IMS DC based Avatar Communication |
pCR revised to S3-244402 |
Nokia, Nokia Shanghai Bell | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-244277 | update KI#4 on Authentication and authorization of digital representation |
pCR revised to S3-244476 |
Nokia, Nokia Shanghai Bell | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-244278 | Solution for KI#2 on Privacy of user sensitive information |
pCR revised to S3-244473 |
Nokia, Nokia Shanghai Bell | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-244279 | Solution for KI#3 on Security aspects of digital asset container in 5G | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
noted | [WTS] [JSN] |
| S3-244280 | discussion paper on Security for MonStra | discussion | Nokia, Nokia Shanghai Bell | Rel-19 |
S3-118 AI: 4.14 |
withdrawn | [WTS] [JSN] | ||
| S3-244281 | discussion paper for KI#1.1 | discussion | Nokia, Nokia Shanghai Bell | Rel-19 |
S3-118 AI: 5.14 |
noted | [WTS] [JSN] | ||
| S3-244282 | evaluation and conlcusion for KI#1.1 |
pCR revised to S3-244437 |
Nokia, Nokia Shanghai Bell | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244283 | evaluation summary of solutions for KI#2.1 | pCR | Nokia, Nokia Shanghai Bell | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
noted | [WTS] [JSN] |
| S3-244284 | conclusion for KI#2.1 | pCR | Nokia, Nokia Shanghai Bell | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
merged | [WTS] [JSN] |
| S3-244285 | enhancement in solution 3 for KI#2.1 |
pCR revised to S3-244429 |
Nokia, Nokia Shanghai Bell | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244286 | fixing ENs in solution 4 for KI#2.1 | pCR | Nokia, Nokia Shanghai Bell | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244287 | Evaluation of solution#1 |
pCR revised to S3-244509 |
Philips International B.V. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244288 | Conclusion for KI#1 in TR 33.700-29 | pCR | Lenovo | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-244289 | Conclusion for Key Issue#1 of TR 33.784 | pCR | Xiaomi communications | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-244290 | Conclusion for Key Issue#2 of TR 33.784 | pCR | Xiaomi communications | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244291 | Resource owner triggered revocation procedure |
pCR revised to S3-244347 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244292 | Resource owner authentication and authorization mechanism |
pCR revised to S3-244348 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244293 | API invoker authentication mechanism in CAPIF interconnection scenarios |
pCR revised to S3-244361 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244294 | API invoker authorization mechanism in CAPIF interconnection scenarios |
pCR revised to S3-244362 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244295 | Security method negotiation mechanism in CAPIF interconnection scenarios |
pCR revised to S3-244363 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244296 | Reply LS on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 source LS: S6-243764 LS To: SA6 revised to S3-244340 |
Xiaomi communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] | |
| S3-244297 | Shared information based authentication and authorization mechanism for multiple API invokers | pCR | Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244298 | Add scope for the TR 33.700-22 | pCR | Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244299 | Update conclusion to KI#2 | pCR | Xiaomi communications | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244300 | Solution to KI#2 |
pCR revised to S3-244364 |
Lenovo | 33.700-22 0.1.0 | FS_eZTS, FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244301 | MonSTra: Monitoring of Signaling Traffic Functionality in 3GPP | discussion | Ericsson, Nokia, Vodafone |
S3-118 AI: 4.14 |
noted | [WTS] [JSN] | |||
| S3-244302 | Draft TR 33.766 | draft TR | Ericsson,Nokia | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] | |
| S3-244303 | Draft TR 33.745 | draft TR | ZTE | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] | |
| S3-244304 | Draft TR 33.721 | draft TR | Samsung | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
approved | [WTS] [JSN] | |
| S3-244305 | Draft TR 33.700-22 | draft TR | Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-244306 | Reply LS to SA6 on Metaverse user consent |
LS out LS is reply to S3-243808 LS To: SA6 revision of S3-244181 |
Apple |
S3-118 AI: 3 |
approved | [WTS] [JSN] | |||
| S3-244307 | Reply-LS on PQC Migration |
LS out LS is reply to S3-243812 LS To: GSMA PQTN revision of S3-244201 |
Ericsson |
S3-118 AI: 3 |
approved | [WTS] [JSN] | |||
| S3-244308 | [draft] Reply LS on AIML data collection |
LS out LS is reply to S3-243818 source LS: RP-242389 LS To: RAN |
Samsung | Rel-19 |
S3-118 AI: 3 |
withdrawn | [WTS] [JSN] | ||
| S3-244309 | Reply to: LS on SG17 new work item TR.sa_RAN - Technical Report on ""Security Attacks in Radio Access Networks"" |
LS out LS is reply to S3-243838 LS To: ITU-T SG17, ITU-T SG13 |
Nokia |
S3-118 AI: 3 |
approved | [WTS] [JSN] | |||
| S3-244310 | Add specific UDR SCAS test cases for TS 33.530 |
pCR revision of S3-243869 revised to S3-244792 |
BSI (DE) | 33.530 0.1.0 | SCAS_5G_UDR | Rel-19 |
S3-118 AI: 4.2 |
noted | [WTS] [JSN] |
| S3-244311 | Living document for CryptoSP: draftCR to TS 33.203, Updates to cryptographic profiles |
draftCR revision of S3-243911 |
Ericsson | CryptoSP | Rel-19 |
S3-118 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-244312 | Editorial change on CryptoSP living document draft CR to TS 33203 |
other revision of S3-244184 |
Apple |
S3-118 AI: 4.8 |
approved | [WTS] [JSN] | |||
| S3-244313 | Clarification on TC_BVT_PORT_SCANNING |
draftCR revision of S3-243871 |
BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
noted | [WTS] [JSN] | |
| S3-244314 | Clarifying the threat for checking expiry of its own certificate | other | Qualcomm Incorporated |
S3-118 AI: 4.1 |
withdrawn | [WTS] [JSN] | |||
| S3-244315 | Adding expiry time checking for peer certificates |
other revision of S3-244128 |
Qualcomm Incorporated |
S3-118 AI: 4.1 |
approved | [WTS] [JSN] | |||
| S3-244316 | LS on security handling for inter-CU LTM |
LS out LS To: RAN2 |
Samsung |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |||
| S3-244317 | Reply LS on security key update of inter-CU SCG LTM |
LS out LS is reply to S3-243814 source LS: R2-2407602 LS To: RAN2 revision of S3-244100 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-244318 | overall summary to the solutions in the living CR | other | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
withdrawn | [WTS] [JSN] | |
| S3-244319 | Resolve the EN in Sol#3 |
other revision of S3-244039 |
ZTE Corporation | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-244320 | Address ENs in Solution 1 |
other revision of S3-243875 |
vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-244321 | LTM - Update solution#4 |
other revision of S3-244178 |
Apple |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |||
| S3-244322 | LTM - Update solution#5 |
other revision of S3-244179 |
Apple |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |||
| S3-244323 | Resolve EN on the cases for change of security algorithm for solution #6 |
other revision of S3-244230 |
LG Electronics | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-244324 | Living document on NR mobility enhancement |
draftCR revision of S3-244254 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-244325 | Mobility under a TNGF |
other revision of S3-244130 |
Qualcomm Incorporated, Huawei, Hisilicon, Cablelabs |
S3-118 AI: 4.13 |
approved | [WTS] [JSN] | |||
| S3-244326 | Living CR for Non3GPPMobility |
draftCR revision of S3-243933 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-118 AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-244327 | eZTS KI 1 Conclusions |
pCR revision of S3-243931 |
MITRE-FFRDC | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244328 | Solution #6 Update |
pCR revision of S3-243929 |
MITRE-FFRDC | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244329 | Solution #5 updates |
pCR revision of S3-244000 |
Huawei, HiSilicon | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244330 | Solution 4 evaluation updates |
pCR revision of S3-244080 |
Nokia | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244331 | Solution 7 evaluation updates |
pCR revision of S3-244081 |
Nokia | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244332 | Solution#9 Update |
pCR revision of S3-243847 |
Lenovo | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244333 | eZTS Sol 11 Evaluation |
pCR revision of S3-243930 |
MITRE-FFRDC | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244334 | Evaluation of solution #10 |
pCR revision of S3-244075 |
Nokia | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244335 | Conclusion for Key Issue #2 "Security mechanisms for policy enforcement at the 5G SBA" |
pCR revision of S3-244193 |
Ericsson, Lenovo, MITRE-FFRDC, OTD_US | 33.794 0.4.0 | FS_eZTS | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244336 | Updates to Solution#11 |
pCR revision of S3-243850 |
Lenovo | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-244337 | Conclusion to KI#2 |
pCR revision of S3-244036 |
China Telecomunication Corp., ZTE, Huawei, HiSilicon, China Mobile | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-244338 | Conclusion for KI#1 |
pCR revision of S3-244205 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-244339 | Add LI impacts to Conclusion for KI#3 in TR 33.757 |
pCR revision of S3-243901 |
Johns Hopkins University APL | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-244340 | Reply LS on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 source LS: S6-243764 LS To: SA6 revision of S3-244296 |
Xiaomi communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-244341 | new solution for KI1.1 - CAPIF-8 security |
pCR revision of S3-243863 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244342 | New solution for KI#1.1 CAPIF-8 reference point |
pCR revision of S3-244076 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244343 | new solution for KI1.2 - resource owner authorized revocation |
pCR revision of S3-243864 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244344 | Solution to KI#1 |
pCR revision of S3-243849 |
Lenovo | 33.700-22 0.1.0 | FS_eZTS, FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244345 | New solution for KI#1.2 resource owner authorization management |
pCR revision of S3-244078 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244346 | RO consent management |
pCR revision of S3-244028 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244347 | Resource owner triggered revocation procedure |
pCR revision of S3-244291 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244348 | Resource owner authentication and authorization mechanism |
pCR revision of S3-244292 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244349 | new solution for KI1.3 - resource-level and api-level authorization and revocation |
pCR revision of S3-243865 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244350 | KI1.3 Solution on scope enhancing |
pCR revision of S3-244027 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244351 | Update to KI#1.2 |
pCR revision of S3-244167 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244352 | Solution for key issue #1.2 |
pCR revision of S3-244166 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244353 | KI2 Solution on security method retrieval in CAPIF interconnect |
pCR revision of S3-244022 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244354 | KI2 Solution on authentication aspect in CAPIF interconnect requesting security information from another CCF |
pCR revision of S3-244023 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244355 | KI2 Solution on authentication aspect in CAPIF interconnect when API invoker has not included CCF information |
pCR revision of S3-244024 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244356 | KI2 Solution on authorization token request handling in CAPIF interconnect |
pCR revision of S3-244025 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244357 | KI2 Solution on mapping an API invoker authorization request to the correct CCF in CAPIF interconnect |
pCR revision of S3-244026 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244358 | New solution for KI#2 CAPIF interconnection |
pCR revision of S3-244077 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244359 | New solution for CAPIF interconnection |
pCR revision of S3-244158 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244360 | Solution for security aspects of CAPIF interconnection |
pCR revision of S3-244264 |
Samsung, Nokia, Nokia Shanghai Bell | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244361 | API invoker authentication mechanism in CAPIF interconnection scenarios |
pCR revision of S3-244293 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244362 | API invoker authorization mechanism in CAPIF interconnection scenarios |
pCR revision of S3-244294 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244363 | Security method negotiation mechanism in CAPIF interconnection scenarios |
pCR revision of S3-244295 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244364 | Solution to KI#2 |
pCR revision of S3-244300 |
Lenovo | 33.700-22 0.1.0 | FS_eZTS, FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244365 | New key issue for secure storage in AIoT devices |
pCR revision of S3-244211 |
Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244366 | solution on protection for inventory and command procedure |
pCR revision of S3-243948 |
Huawei, HiSilicon | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244367 | Solution for AIoT Authentication Based on 5G-AKA |
pCR revision of S3-244010 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244368 | New Sol for KI#5 |
pCR revision of S3-244047 |
ZTE Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244369 | AIoT - Security solution on Authentication |
pCR revision of S3-244175 |
Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244370 | pCR to TR33.713 New solution for device authentication and data |
pCR revision of S3-244235 |
CATT | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244371 | reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-243821 LS To: SA2 revision of S3-244140 |
Qualcomm Incorporated |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] | |||
| S3-244372 | Update to solution #8 in TR 33.743 |
pCR revision of S3-244117 |
Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244373 | Update Solution#4 | pCR | Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
withdrawn | [WTS] [JSN] |
| S3-244374 | Updating evaluations to solution #9 |
pCR revision of S3-244144 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244375 | Conclusion to KI#1 - multi-hop U2NW discovery |
pCR revision of S3-243968 |
Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-244376 | TR 33.743 Conclusion for Key Issue#1 |
pCR revision of S3-244020 |
InterDigital Communications | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-244377 | Conclusion of KI#2 |
pCR revision of S3-244143 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244378 | Update for solution 5 |
pCR revision of S3-244174 |
Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-244379 | Update for solution 6 |
pCR revision of S3-244189 |
Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-244380 | Evaluation for solution 5 |
pCR revision of S3-244216 |
Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-244381 | Evaluation for solution 6 |
pCR revision of S3-244220 |
Ericsson | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-244382 | Overall Summary of solutions |
pCR revision of S3-244074 |
Nokia | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244383 | Proposed conclusions for key issues #1 & 2 for HSS in satellite |
pCR revision of S3-244134 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244384 | Conclusions KI#1 |
pCR revision of S3-244247 |
Philips International B.V. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244385 | Conclusion for KI#2 in TR 33.700-29 |
pCR revision of S3-244112 |
Beijing Xiaomi Mobile Software | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244386 | Update to solution 23 |
pCR revision of S3-243994 |
Huawei, HiSilicon | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244387 | Evaluation of Solution #30 |
pCR revision of S3-244249 |
Philips International B.V. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244388 | updates and evaluation to solution #30 |
pCR revision of S3-244087 |
Huawei, HiSilicon | 33.700-29 0.4.0 | SAT | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244389 | updates and evaluation to solution #28 |
pCR revision of S3-244088 |
Huawei, HiSilicon | 33.700-29 0.4.0 | SAT | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244390 | Clarifications on the IOPS enhancements in solution #3 |
pCR revision of S3-244133 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244391 | New Solution on Mitigation of Security Issues of Unprotected NAS Reject |
pCR revision of S3-243879 |
vivo | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244392 | Alternatives to Solution #21 |
pCR revision of S3-243916 |
InterDigital, Europe, Ltd. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244393 | Merger of Solutions #8 and #21 |
pCR revision of S3-243917 |
InterDigital, Europe, Ltd. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244394 | Merger of Solutions #9 and #21 |
pCR revision of S3-243918 |
InterDigital, Europe, Ltd. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244395 | Merger of Solutions #15 and #21 |
pCR revision of S3-243919 |
InterDigital, Europe, Ltd. | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244396 | New solution for authentication on split MME architecture in S&F mode |
pCR revision of S3-243995 |
Huawei, HiSilicon | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244397 | New solution on NAS secuity in split MME architecture |
pCR revision of S3-244091 |
Huawei, HiSilicon | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244398 | New KI - security of backhaul communication over feeder link in generic regenerative mode | pCR | Ericsson | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
withdrawn | [WTS] [JSN] |
| S3-244399 | Addressing the ENs on token and Avatar ID of Solution#5 |
pCR revision of S3-244092 |
Huawei, HiSilicon | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-244400 | Resolving EN in solution #6 |
pCR revision of S3-244271 |
Samsung | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-244401 | Evaluation update on solution #6 |
pCR revision of S3-244272 |
Samsung | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-244402 | Address ENs of Sol7 on Protect IMS DC based Avatar Communication |
pCR revision of S3-244276 |
Nokia, Nokia Shanghai Bell | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-244403 | Addressing the ENs on user interaction of Solution#10 |
pCR revision of S3-244093 |
Huawei, HiSilicon | 33.790 0.4.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-118 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-244404 | Update to sol#3 for KI#2 |
pCR revision of S3-243958 |
Huawei, HiSilicon | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-244405 | Resolve EN to Sol#3 |
pCR revision of S3-243962 |
Huawei, HiSilicon | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-244406 | Editorial updates |
pCR revision of S3-244171 |
Ericsson | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-244407 | Additional conclusions for KI#3 |
pCR revision of S3-243860 |
Huawei, HiSilicon | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
noted | [WTS] [JSN] |
| S3-244408 | TR 33.700-32 Conclusion for Key Issue#3 |
pCR revision of S3-244018 |
InterDigital Communications | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
noted | [WTS] [JSN] |
| S3-244409 | Concluding KI1 and KI2 in UIA |
pCR revision of S3-244033 |
DOCOMO Communications Lab. | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244410 | 33.700-32: Evaluation of Solution 26 and Conclusion on KI#1 |
pCR revision of S3-244105 |
Xiaomi EV Technology | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244411 | 33.700-32: Evaluation of Solution 27 and Conclusion on KI#2 |
pCR revision of S3-244106 |
Xiaomi EV Technology | 33.700-32 0.3.0 | FS_UIA_Sec | Rel-19 |
S3-118 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244412 | Solution for certificate renewal for ACME in 5G SBA |
pCR revision of S3-243906 |
Google Ireland Limited | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-244413 | Solution proposal for key issue #7 |
pCR revision of S3-243912 |
Cisco Systems | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-244414 | address EN to KI#4 |
pCR revision of S3-243974 |
Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244415 | Editorial updates to KI#9 descriptions |
pCR revision of S3-244005 |
Charter Communications, Inc | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244416 | Updates for solution #3 to address the needs for KI#9 |
pCR revision of S3-244003 |
Charter Communications, Inc | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244417 | Add a solution to KI#3 |
pCR revision of S3-244055 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244418 | New solution to KI#4 and conclusion |
pCR revision of S3-243978 |
Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244419 | New solution to KI#7 and conclusion |
pCR revision of S3-243981 |
Huawei, HiSilicon | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244420 | Add conclusions to KI#1 |
pCR revision of S3-244056 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244421 | Add conclusions to KI#2 |
pCR revision of S3-244057 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244422 | Add conclusions to KI#4 |
pCR revision of S3-244059 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244423 | Add conclusions to KI#5 |
pCR revision of S3-244060 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244424 | Add conclusions to KI#6 |
pCR revision of S3-244061 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244425 | Add conclusions to KI#8 |
pCR revision of S3-244063 |
ZTE Corporation | 33.745 0.3.0 | FS_5G_Femto_Sec | Rel-19 |
S3-118 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244426 | new solution on UUAA for USS changeover |
pCR revision of S3-243857 |
Huawei, HiSilicon | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-244427 | TR 33.759 Conclusion for Key Issue#1 |
pCR revision of S3-244019 |
InterDigital Communications, Qualcomm Incorporated | 33.759 0.3.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-118 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-244428 | Addressing the ENs on brute force and synchronization of Solution#2 |
pCR revision of S3-244095 |
Huawei, HiSilicon | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244429 | enhancement in solution 3 for KI#2.1 |
pCR revision of S3-244285 |
Nokia, Nokia Shanghai Bell | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244430 | Resolving ENs in solution #6 |
pCR revision of S3-244161 |
Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244431 | Evaluation of solution #6 |
pCR revision of S3-244162 |
Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244432 | Update to solution#7 in TR 33.749 |
pCR revision of S3-244266 |
Samsung | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244433 | conclusion to KI#2.1 |
pCR revision of S3-244096 |
Huawei, HiSilicon | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
noted | [WTS] [JSN] |
| S3-244434 | Update the KI#1.1 |
pCR revision of S3-244052 |
ZTE Corporation | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244435 | New solution for KI#1.1 |
pCR revision of S3-244051 |
ZTE Corporation | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244436 | A new solution for KI#1.1 |
pCR revision of S3-244164 |
Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
noted | [WTS] [JSN] |
| S3-244437 | evaluation and conlcusion for KI#1.1 |
pCR revision of S3-244282 |
Nokia, Nokia Shanghai Bell | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244438 | Address ENs in solution #14 |
pCR revision of S3-243890 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244439 | LMF authorization for AI/ML model retrieval from NWDAF |
pCR revision of S3-244232 |
Ericsson | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244440 | Address ENs in solution #4 |
pCR revision of S3-243888 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244441 | Evaluation of solution 6 |
pCR revision of S3-244084 |
Huawei, HiSilicon | 33.784 0.3.0 | eNA | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244442 | update on solution 9 |
pCR revision of S3-243960 |
Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244443 | Address ENs in Solution #10 |
pCR revision of S3-243889 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244444 | Solution of Privacy protection in VFL |
pCR revision of S3-243920 |
InterDigital Communications | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244445 | Address ENs in Solution #15 |
pCR revision of S3-243891 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244446 | Basic Conclusion for key issue#2 |
pCR revision of S3-243893 |
vivo, China Mobile | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244447 | conclusion to key issue#3 |
pCR revision of S3-243956 |
Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244448 | conclusion to key issue#4 |
pCR revision of S3-243957 |
Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244449 | KI#5, New Sol: AIoT device authentication |
pCR revision of S3-243882 |
vivo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244450 | Solution for Authentication and ID Privacy of AIoT devices with USIM on AIoT AS Layer |
pCR revision of S3-244121 |
Lenovo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244451 | Solution for Authentication and ID Privacy of AIoT devices with USIM on AIoT Layer |
pCR revision of S3-244122 |
Lenovo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244452 | Solution for Authentication and ID privacy of AIoT devices without USIM |
pCR revision of S3-244123 |
Lenovo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244453 | update to key issue#5 on authentication |
pCR revision of S3-243946 |
Huawei, HiSilicon | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244454 | Updating KI#5 Authentication in Ambient IoT service |
pCR revision of S3-244208 |
Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244455 | update to key issue#4 on information protection |
pCR revision of S3-243947 |
Huawei, HiSilicon | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244456 | Solution on Protection of transmitted information |
pCR revision of S3-244125 |
Sony | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244457 | A new solution for end-to-end security protection of command |
pCR revision of S3-244139 |
Qualcomm Incorporated | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244458 | New solution on disabling operation procedure |
pCR revision of S3-244115 |
Beijing Xiaomi Mobile Software | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244459 | Solution on disabling operation procedure for AIoT services |
pCR revision of S3-244187 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244460 | Solution on Disabling Enabling |
pCR revision of S3-244240 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244461 | Solution for nested API invocation |
pCR revision of S3-244160 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244462 | Authorization for Nested API invocation |
pCR revision of S3-244265 |
Samsung | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244463 | KI5 Solution on authenticating multiple API invokers of the same RO |
pCR revision of S3-244029 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244464 | KI on Onboarding security issue |
pCR revision of S3-244030 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244465 | Solution on validation of correct GPSI in API invoker information |
pCR revision of S3-244031 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244466 | Editorial - Streamlining interconnect KI details |
pCR revision of S3-244032 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244467 | Resolve the EN in the Sol#2 in TR 33.713 |
pCR revision of S3-244046 |
ZTE Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244468 | New solution on authorization of intermediate node for Ambient IoT services |
pCR revision of S3-244114 |
Beijing Xiaomi Mobile Software | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244469 | New solution to key issue #2: Authorization for 5G Ambient IoT services |
pCR revision of S3-244214 |
Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244470 | Solution for Lightweight AIoT ID privacy |
pCR revision of S3-243855 |
InterDigital, Europe, Ltd. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244471 | Resolve the EN in the Sol#1 in TR 33.721 |
pCR revision of S3-244065 |
ZTE Corporation | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-244472 | Update evaluation for Sol#1 in TR 33.721 |
pCR revision of S3-244066 |
ZTE Corporation | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-244473 | Solution for KI#2 on Privacy of user sensitive information |
pCR revision of S3-244278 |
Nokia, Nokia Shanghai Bell | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-244474 | Solution for KI#3 on Security aspects of digital asset container in 5G | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
withdrawn | [WTS] [JSN] |
| S3-244475 | Solution for digital asset request validation |
pCR revision of S3-244263 revised to S3-244518 |
Samsung | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-244476 | update KI#4 on Authentication and authorization of digital representation |
pCR revision of S3-244277 |
Nokia, Nokia Shanghai Bell | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-244477 | Solution for AIoT ID ephemeral security context |
pCR revision of S3-243874 |
InterDigital, Europe, Ltd. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244478 | Sol on AIoT device ID privacy protection using anonymous key |
pCR revision of S3-244007 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244479 | Sol on temporary ID based AIoT device privacy protection |
pCR revision of S3-244008 |
OPPO | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244480 | New solution on KI#3 |
pCR revision of S3-244043 |
ZTE Corporation | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244481 | Update the evaluation of solution 5 in TR 33.743 |
pCR revision of S3-243967 |
Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244482 | LS on 5G SA Roaming Anomaly Detection in the context of PRINS |
LS out LS is reply to S3-242364 LS To: GSMA DESS, 5GMRR revision of S3-243921 |
BSI (DE) | Rel-18 |
S3-118 AI: 3 |
approved | [WTS] [JSN] | ||
| S3-244483 | A new solution for privacy protection of AIoT device identifier |
pCR revision of S3-244138 |
Qualcomm Incorporated | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244484 | AIoT - Security solution on Privacy protection |
pCR revision of S3-244177 |
Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244485 | New solution to KI#3 Privacy by protecting AIoT device identifiers |
pCR revision of S3-244213 |
Ericsson | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244486 | pCR to TR33.713 New solution for protecting Device IDs in inventory scenarios |
pCR revision of S3-244236 |
CATT | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244487 | New solution - Ambient IoT ID privacy |
pCR revision of S3-244245 |
Philips International B.V. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244488 | New solution on protecting AIoT ID |
pCR revision of S3-244274 |
Samsung | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244489 | New Key Issue on Exposure of Inventory Device Quantity |
pCR revision of S3-243883 |
vivo | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244490 | Signaling Monitoring Requirements | draftCR | Vodafone, Nokia, Nokia Shanghai Bell, Ericsson, Telefonica | MonStra-Sec | Rel-19 |
S3-118 AI: 4.14 |
approved | [WTS] [JSN] | |
| S3-244491 | Rel-20 Planning | other | SA3 WG Chair |
S3-118 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-244492 | Resolution of EN concerning message inspection, filtering and topology hiding – solution 13. |
pCR revision of S3-244151 |
Nokia, Nokia Shanghai Bell | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-244493 | Solution for SUPI privacy |
pCR revision of S3-244259 |
Samsung | 33.757 0.4.0 | PLMNNPN_SEC | Rel-19 |
S3-118 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-244494 | Updates to Solution #21 |
pCR revision of S3-244270 |
Samsung | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-118 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244495 | Update Solution #5 |
pCR revision of S3-244234 |
Ericsson | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244496 | Update Solution#2 |
pCR revision of S3-244197 |
Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244497 | Update Solution#3 |
pCR revision of S3-244198 |
Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244498 | A new solution for multi-hop U2N relay communication security |
pCR revision of S3-244141 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244499 | solution 3 update |
pCR revision of S3-243939 |
Nokia | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244500 | conclusion to key issue#1 |
pCR revision of S3-243951 |
Huawei, HiSilicon | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244501 | Update to solution#8 in TR 33.749 |
pCR revision of S3-244267 |
Samsung | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244502 | A new solution for KI#2.1 |
pCR revision of S3-244170 |
Ericsson | 33.749 0.3.0 | FS_EDGE_Ph3 | Rel-19 |
S3-118 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-244503 | Update on Key Issue 1 related to security aspects on user consent for energy information collection |
pCR revision of S3-243924 |
IIT Bombay | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-244504 | Update on Key Issue 2 related to security aspects on user consent for energy information exposure |
pCR revision of S3-243926 |
IIT Bombay | 33.766 0.3.0 | FS_Energy_Sec | Rel-19 |
S3-118 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-244505 | Living document to Draft CR TS 33.511 |
draftCR revision of S3-243988 |
Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-118 AI: 4.1 |
approved | [WTS] [JSN] | |
| S3-244506 | add evaluation for Sol#3 |
other revision of S3-244038 |
ZTE Corporation | NR_Mob_Ph4_Sec | Rel-19 |
S3-118 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-244507 | NSWO text alignment |
other revision of S3-243936 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-118 AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-244508 | Solution#1 update - Addressing ENs |
pCR revision of S3-244246 |
Philips International B.V. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244509 | Evaluation of solution#1 |
pCR revision of S3-244287 |
Philips International B.V. | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-118 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244510 | Support iat claim in the access token |
CR revision of S3-244203 |
Ericsson, AT&T, Charter Communications, Samsung | 33.501 19.0.0 CR#20511 catB | TEI19 | Rel-19 |
S3-118 AI: 4.11 |
agreed | [WTS] [JSN] |
| S3-244511 | Conclusions for TR 33.776 |
pCR revision of S3-243914 |
Cisco Systems | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-244512 | Conclusion on KI#6 certificate revocation |
pCR revision of S3-244016 |
Johns Hopkins University APL, US National Security Agency | 33.776 0.4.0 | FS_ACME_SBA | Rel-19 |
S3-118 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-244513 | Update to solution #7 in TR 33.743 |
pCR revision of S3-244116 |
Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244514 | Conclusion for key Issue#3 |
pCR revision of S3-243896 |
vivo | 33.784 0.3.0 | FS_AIML_CN_SEC | Rel-19 |
S3-118 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244515 | Update to KI#1 for fixing the terminology |
pCR revision of S3-244168 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244516 | LS on terminology alignment between SA6 and SA3 |
LS out LS To: SA6 revision of S3-244169 |
Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-244517 | Rel-19 meetings for SA3 | other | SA3 WG Chair |
S3-118 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-244518 | Solution for digital asset request validation |
pCR revision of S3-244475 |
Samsung | 33.721 0.3.0 | FS_Metaverse_Sec | Rel-19 |
S3-118 AI: 5.18 |
approved | [WTS] [JSN] |
719 documents (1.2577679157257 seconds)