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-221710 | Agenda | agenda | SA WG3 Chair |
S3-108-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-221711 | Report from SA3#107e | report | MCC |
S3-108-e AI: 2 |
approved | [WTS] [JSN] | |||
S3-221712 | Report from SA3#107e ad-Hoc | other | SA WG3 Chair |
S3-108-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-221713 | Process for SA3#108e | other | SA WG3 Chair |
S3-108-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-221714 | Report from last SA | report | SA WG3 Chair |
S3-108-e AI: 2 |
noted | [WTS] [JSN] | |||
S3-221715 | Meeting notes from SA3 leadership | report | MCC |
S3-108-e AI: 2 |
available | [WTS] [JSN] | |||
S3-221716 | Process and agenda planning for SA3#108e | other | SA WG3 Chair |
S3-108-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-221717 | SA3 meeting calendar | other | SA WG3 Chair |
S3-108-e AI: 8 |
noted | [WTS] [JSN] | |||
S3-221718 | Reply LS on EPS fallback enhancements | LS in | C1-223535 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221719 | LS on user’s consent for EDGEAPP | LS in | C3-223780 |
S3-108-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-221720 | LS on CT specification on Control Plane based security procedures for 5G ProSe UE-to-Network Relay | LS in | CP-221322 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221721 | LS to 3GPP on user plane security |
LS in LS reply in S3-222426 |
GSMA |
S3-108-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221722 | LS on 3GPP TS 29.244 | LS in | BBF |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221723 | East/West Bound Interface for Telco Edge consideration |
LS in LS reply in S3-222360 |
GSMA |
S3-108-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221724 | LS on UE’s LTE UPIP capability for EN-DC |
LS in LS reply in S3-222432 |
R3-223915 |
S3-108-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221725 | Reply LS on User Consent Updating | LS in | R3-224076 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221726 | Reply LS on UE capabilities indication in UPU | LS in | S2-2204722 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221727 | LS on Joint CC for support of LI at HO for S8 Home routing | LS in | S2-2204731 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221728 | Reply LS on the impact of MSK update on MBS multicast session update procedure |
LS in LS reply in S3-222391 |
S2-2204741 |
S3-108-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221729 | Reply LS on Clarifications on Nmbstf_MBSDistributionSession service | LS in | S2-2204742 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221730 | LS OUT on Indication of Network Assisted Positioning method | LS in | S2-2204744 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221731 | LS OUT on alignment of non-seamless NSW handling |
LS in LS reply in S3-221778, S3-222397 |
S2-2204752 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221732 | LS on 5G ProSe security open items |
LS in LS reply in S3-222363 |
S2-2204904 |
S3-108-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221733 | LS on CAPIF authorization roles related to FS_SNAAPP |
LS in LS reply in S3-222256 |
S6-221771 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] | |||
S3-221734 | LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network |
LS in LS reply in S3-222038 |
S6-221953 |
S3-108-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-221735 | Reply LS on 5G ProSe security open items |
LS in LS reply in S3-222363 |
SP-220716 |
S3-108-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221736 | LS on X.5Gsec-vs (X.1813): Security requirements for the operation of vertical services supporting ultra- reliable and low latency communication (URLLC) in the IMT-2020 private networks | LS in | ITU-T Study Group 17 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221737 | LS to 3GPP Hosted SEPP |
LS in LS reply in S3-222304 |
GSMA |
S3-108-e AI: 5.24 |
replied to | [WTS] [JSN] | |||
S3-221738 | LS on authentication type and related information of MSGin5G service | LS in | C1-223957 |
S3-108-e AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-221739 | LS on consent of ITU-T Q.3062 (ex Q.Pro-Trust) and ITU-T Q.3063 (ex Q.CIDA) | LS in | ITU-T SG11 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221740 | Facilitating roaming adoption across 3GPP NPN deployments |
LS in LS reply in S3-222040 |
WBA OpenRoaming Technical Standards Task Group |
S3-108-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-221741 | [33.180] R14 Incorrect Reference |
CR revised to S3-222271 |
Motorola Solutions Danmark A/S | 33.18 14.10.0 CR#190 catF | MCSec | Rel-14 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221742 | [33.180] R15 Incorrect Reference (mirror) |
CR revised to S3-222272 |
Motorola Solutions Danmark A/S | 33.18 15.11.0 CR#191 catA | MCSec | Rel-15 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221743 | [33.180] R16 Incorrect Reference (mirror) |
CR revised to S3-222273 |
Motorola Solutions Danmark A/S | 33.18 16.9.0 CR#192 catA | MCSec | Rel-16 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221744 | [33.180] R17 Incorrect Reference (mirror) |
CR revised to S3-222274 |
Motorola Solutions Danmark A/S | 33.18 17.6.0 CR#193 catA | MCSec | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221745 | TCG progress - report from TCG rapporteur | other | InterDigital, Inc. |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221746 | Clarification on NAI format for PRUK ID | CR | ZTE Corporation | 33.503 17.0.1 CR#1 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-221747 | Address ENs related to sending UAV ID to UAV | CR | Huawei, HiSilicon | 33.256 17.1.0 CR#16 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221748 | HPLMN ID of Remote UE in Remote UE Report message | CR | Ericsson | 33.503 17.0.1 CR#2 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-221749 | Implementation correction of S3-221294 |
CR revised to S3-222356 |
Ericsson | 33.503 17.0.1 CR#3 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-221750 | [33.180] R18 MC client clarification | CR | Motorola Solutions Danmark A/S | 33.18 17.6.0 CR#194 catF | MCXSec3 | Rel-18 |
S3-108-e AI: 4.3 |
not pursued | [WTS] [JSN] |
S3-221751 | Discussion paper on open questions regarding 256-bit algorithms | discussion | KDDI Corporation | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221752 | New group of test cases deriving from TS 33.117 for SCAS AAnF |
pCR revised to S3-222260 |
Keysight Technologies UK Ltd | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
revised | [WTS] [JSN] |
S3-221753 | New test case to cover the AAnF provisioning | CR | Keysight Technologies UK Ltd | 33.516 17.0.0 CR#3 catB | eSCAS_5G | Rel-17 |
S3-108-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-221754 | New test case to cover the AAnF provisioning | CR | Keysight Technologies UK Ltd | 33.516 17.0.0 CR#4 catB | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221755 | Key Issue on Direct C2 Authorization | pCR | InterDigital, Europe, Ltd. | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-221756 | Key Issue: UAV Privacy over PC5 link |
pCR revised to S3-222361 |
InterDigital, Europe, Ltd. | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-221757 | Solution on Direct C2 Security |
pCR revised to S3-222362 |
InterDigital, Europe, Ltd. | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-221758 | LS Reply on Reply LS on 5G ProSe security open items |
LS out LS is reply to S3-221735 LS To: SA, SA2 revised to S3-222363 |
InterDigital, Europe, Ltd. | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] | ||
S3-221759 | Support for Prose Secondary Authentication excluded from Rel-17 | CR | InterDigital, Europe, Ltd., LG Electronics, Samsung | 33.503 17.0.1 CR#4 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-221760 | CP-UP Security Procedure selection | CR | InterDigital, Europe, Ltd. | 33.503 17.0.1 CR#5 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
merged | [WTS] [JSN] |
S3-221761 | Discussion on Work for Prose Secondary Authentication in Rel-18 | discussion | InterDigital, Europe, Ltd. | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221762 | New WID: 5G ProSe Secondary Authentication |
WID new revised to S3-222366 |
InterDigital, Europe, Ltd., LG Electronics, Samsung, China Telecom | Rel-18 |
S3-108-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-221763 | New Solution for Security of Layer-2 based UE-to-UE Relay | pCR | InterDigital, Europe, Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221764 | New solution: Restricted Peer UE IP Discovery with Layer-3 UE-to-UE Relay |
pCR revised to S3-222364 |
InterDigital, Europe, Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-221765 | New solution: Privacy for Layer-3 UE-to-UE Relay based on IP routing |
pCR revised to S3-222365 |
InterDigital, Europe, Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-221766 | KI1 Update | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.1.1 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-108-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-221767 | KI2 Update | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.1.1 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-108-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-221768 | EAP_AKA prime based authentication for AUN3 devices |
pCR revised to S3-222395 |
Nokia, Nokia Shanghai Bell | 33.887 0.1.1 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-108-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-221769 | EAP_TLS based authentication for AUN3 devices | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.1.1 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-108-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-221770 | Solution for UE privacy | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.1.1 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-108-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-221771 | Discussion on authorization issue in inter NF mobility | discussion | Nokia, Nokia Shanghai Bell | TEI17 | Rel-17 |
S3-108-e AI: 4.7 |
noted | [WTS] [JSN] | |
S3-221772 | Clarification on authorization for inter NF mobility | CR | Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1424 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221773 | Discussion on privacy issue in AKMA | discussion | Nokia, Nokia Shanghai Bell | AKMA | Rel-17 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | |
S3-221774 | Correction in UPU procedure to align with stage 3 | CR | Nokia, Nokia Shanghai Bell | 33.501 16.11.0 CR#1425 catF | TEI16 | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221775 | Correction in UPU procedure to align with stage 3 | CR | Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1426 catA | TEI16 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221776 | NSWO alignment for MSK and PMK | CR | Nokia, Nokia Shanghai Bell, CableLabs | 33.501 17.6.0 CR#1427 catF | NSWO_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221777 | Correction in AUSF api related to NSWO |
CR revised to S3-222396 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.501 17.6.0 CR#1428 catF | NSWO_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221778 | LS reply on 5G NSWO roaming aspects |
LS out LS is reply to S3-221731 LS To: SA2 revised to S3-222397 |
Nokia, Nokia Shanghai Bell | NSWO_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] | |
S3-221779 | New key issue on Protecting Identification of PIN and PIN Privacy | pCR | InterDigital, Inc. | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221780 | New key issue on Security of Discovery of PINE and PIN | pCR | InterDigital, Inc. | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221781 | Adding threats and requirements to KI#1 | pCR | InterDigital, Inc. | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-221782 | New subclause - Assumptions for PIN | pCR | InterDigital, Inc. | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221783 | New key issue on Secure Communication between PINEs | pCR | InterDigital, Inc. | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221784 | New key issue on Secure policy and parameters provisioning for PIN | pCR | InterDigital, Inc. | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221785 | Discussion on authenticating carrier applications via IMS | discussion | Google, Apple | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221786 | Verification of NSSAIs for preventing slice attack |
CR revision of S3-221131 |
CableLabs, Ericsson,Nokia, Nokia Shanghai Bell | 33.501 16.11.0 CR#1429 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221787 | Key issue on misuse of OAuth 2.0 access token by anomalous Network functions | pCR | Nokia, Nokia Shanghai Bell | 33.894 0.1.0 | FS_ZTS | Rel-18 |
S3-108-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-221788 | LS reply on user plane security |
LS out LS To: GSMA |
Nokia, Nokia Shanghai Bell |
S3-108-e AI: 3 |
merged | [WTS] [JSN] | |||
S3-221789 | User plane security for Non-SBA based interfaces | CR | Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1430 catF | TEI17 | Rel-17 |
S3-108-e AI: 3 |
not pursued | [WTS] [JSN] |
S3-221790 | LS reply on East/West Bound Interface for Telco Edge consideration |
LS out LS To: GSMA revised to S3-222360 |
Nokia, Nokia Shanghai Bell |
S3-108-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-221791 | Update Key Issue for authentication of PINE | pCR | vivo | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-221792 | New Key Issue for security protection on parameters requested from PEMC that will be provisioned to PEGC | pCR | vivo | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221793 | New Key Issue for controlling credential downloading to PINE | pCR | vivo | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221794 | Solution on Key Issue #3 | pCR | BUPT | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-221795 | Include SN ID in NSSAA procedure in support of multiple registration | CR | Huawei, Hisilicon | 33.501 16.11.0 CR#1431 catF | TEI16 | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221796 | Clean up to TR33874 |
CR revised to S3-222305 |
Huawei, Hisilicon | 33.874 18.0.0 CR#1 catF | FS_eNS2_SEC | Rel-18 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221797 | Address EN on alignment to SA2 | CR | Huawei, Hisilicon | 33.501 17.6.0 CR#1432 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221798 | LS to SA2 to align NSACF procedure |
LS out LS To: SA2 |
Huawei, Hisilicon | Rel-17 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-221799 | Address EN on AF Authorization | CR | Huawei, Hisilicon | 33.501 17.6.0 CR#1433 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221800 | update to KI#1 | pCR | Huawei, Hisilicon | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-221801 | update to KI#2 | pCR | Huawei, Hisilicon | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-221802 | update to KI#3 | pCR | Huawei, Hisilicon | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-221803 | Solution on temporay slice authorization | pCR | Huawei, Hisilicon | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-221804 | New solution for network triggered authentication of PINE | pCR | vivo | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221805 | New Ki related to authorization of exposed PIN capabilites |
pCR revised to S3-222343 |
Nokia, Nokia Shanghai Bell | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-221806 | Discussion Paper on Structure of KIs | discussion | Nokia, Nokia Shanghai Bell |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] | |||
S3-221807 | New KI on securing resource owner access to own resources | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-221808 | New KI on securing API access from AF acting on own behalf | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-221809 | New Ki on securing API access from subscriber to resources of other subscriber | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-221810 | Solution for NTN User consent | pCR | Nokia, Nokia Shanghai Bell | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-221811 | A solution for KI#1 - Provide additional authentication information to enhance URSP policy enforcement | pCR | Nokia, Nokia Shanghai Bell, Lenovo | 33.892 0.1.0 | FS_USIA | Rel-18 |
S3-108-e AI: 5.18 |
approved | [WTS] [JSN] |
S3-221812 | MOCN security handling for MBS | pCR | Nokia, Nokia Shanghai Bell | 33.883 0.1.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-221813 | Discussion paper on draft CR to TR 33.926 for split gNB | discussion | Qualcomm Incorporated |
S3-108-e AI: 4.6 |
noted | [WTS] [JSN] | |||
S3-221814 | Introducing split gNBs into TR 33.926 | draftCR | Qualcomm Incorporated | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
noted | [WTS] [JSN] | |
S3-221815 | Proposed text for gNB-CU part of draft CR to TR 33.926 | other | Qualcomm Incorporated |
S3-108-e AI: 4.6 |
noted | [WTS] [JSN] | |||
S3-221816 | Proposed text for gNB-CU-CP part of draft CR to TR 33.926 | other | Qualcomm Incorporated |
S3-108-e AI: 4.6 |
noted | [WTS] [JSN] | |||
S3-221817 | Proposed text for gNB-CU-UP part of draft CR to TR 33.926 |
other revised to S3-222307 |
Qualcomm Incorporated |
S3-108-e AI: 4.6 |
revised | [WTS] [JSN] | |||
S3-221818 | Proposed text for gNB-DU part of draft CR to TR 33.926 |
other revised to S3-222308 |
Qualcomm Incorporated |
S3-108-e AI: 4.6 |
revised | [WTS] [JSN] | |||
S3-221819 | Discussion paper on 33.501 test cases for TS 33.742 SCAS for split gNB | discussion | Qualcomm Incorporated |
S3-108-e AI: 4.6 |
noted | [WTS] [JSN] | |||
S3-221820 | Proposed text for gNB-CU test cases from TS 33.501 for TS 33.742 |
pCR revised to S3-222309 |
Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-221821 | Proposed text for gNB-CU-CP test cases from TS 33.501 for TS 33.742 |
pCR revised to S3-222310 |
Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-221822 | Proposed text for gNB-CU-UP test cases from TS 33.501 for TS 33.742 |
pCR revised to S3-222312 |
Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-221823 | Proposed text for gNB-DU test cases from TS 33.501 for TS 33.742 |
pCR revised to S3-222313 |
Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-221824 | Proposed corrections for TS 33.742 | pCR | Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] |
S3-221825 | Proposed correction to Annex D on gNB network product class |
CR revised to S3-222315 |
Qualcomm Incorporated | 33.926 17.4.0 CR#60 catF | eSCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221826 | Corrections for gNB test cases |
CR revised to S3-222317 |
Qualcomm Incorporated | 33.511 17.1.0 CR#28 catF | eSCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221827 | Resolving the EN on CAA level ID during UUAA procedures |
CR revision of S3-220979 |
Qualcomm Incorporated | 33.256 17.1.0 CR#91 catF | ID_UAS | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221828 | Resolving the ENs on CAA level ID during revocation |
CR revision of S3-220981 |
Qualcomm Incorporated | 33.256 17.1.0 CR#111 catF | ID_UAS | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221829 | Re-using V2X unicast security for UAS |
pCR revised to S3-222319 |
Qualcomm Incorporated | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-221830 | Proposed solution for key issue #1 using SHAKEN based third-party specific user identities |
pCR revised to S3-222320 |
Qualcomm Incorporated | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-221831 | A new solution for security mechanism for UE-to-UE Relay discovery | pCR | Qualcomm Incorporated | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221832 | A new solution for security mechanism for UE-to-UE Relay discovery in case of multiple ProSe services for an RSC | pCR | Qualcomm Incorporated | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221833 | A new solution for secure PC5 link establishment for UE-to-UE relay | pCR | Qualcomm Incorporated | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221834 | Updates on Open 5G ProSe Direct Discovery | CR | Qualcomm Incorporated | 33.503 17.0.1 CR#6 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-221835 | Updates on Restricted 5G ProSe Direct Discovery | CR | Qualcomm Incorporated | 33.503 17.0.1 CR#7 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-221836 | TMGI protection during group Paging | pCR | Nokia, Nokia Shanghai Bell | 33.883 0.1.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-221837 | Detecting sources of potential data poisoning attacks towards RAN AI-ML based network optimizations | pCR | Nokia Japan | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
withdrawn | [WTS] [JSN] |
S3-221838 | Key issue on Privacy and security aspects of broadcasting remote ID | pCR | Samsung | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-221839 | Key issue for secure ProSe multi-path transmission for UE-to-Network relay | pCR | Samsung | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221840 | TargetNFServiceSetId to be part of access token claims | CR | Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1434 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221841 | Clarification on N32-f connection establishment with TLS | CR | Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1435 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221842 | pSEPP authorization fo PLMN ID in access token for TLS |
CR revised to S3-222275 |
Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1436 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221843 | Editiorial updates to 33875-120 |
pCR revised to S3-222278 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221844 | Scope update |
pCR revised to S3-222279 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221845 | Clause 3 clean up of subsections | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-221846 | Scope general remark |
pCR revised to S3-222280 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221847 | Trust clause editorial update |
pCR revised to S3-222281 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221848 | KI1 EN resolution in KI1 - threat clarification |
pCR revised to S3-222282 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221849 | KI1 solution 1 update | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-221850 | KI1 EN resolution in solution 6 - evaluation part | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
merged | [WTS] [JSN] |
S3-221851 | KI1 conclusion on NFp authentication in indirect comm | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-221852 | KI2 update with solution and conclusion on trust domain |
pCR revised to S3-222283 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221853 | KI3 EN resolution on requirements for subscribe notify | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-221854 | KI3 EN resolution in solution 12 | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-221855 | KI4 EN resolution of solution 3 |
pCR revised to S3-222284 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221856 | KI4 conclusion on authorization of SCP to act on behalf of another SCP |
pCR revised to S3-222285 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221857 | KI5 Sol4 ENs resolution |
pCR revised to S3-222286 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221858 | KI5 Sol5 ENs resolution | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-221859 | KI5 Sol8 ENs resolution | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-221860 | KI5 conclusion on e2e integrity prot of HTTP msg |
pCR revised to S3-222287 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221861 | KI6 EN resolution in KI threat |
pCR revised to S3-222288 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221862 | KI6 related Sol7 update and conclusion on access token usage by NFs of an NF Set |
pCR revised to S3-222289 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221863 | KI7 evaluation of solution 9 on authorization method negotiation |
pCR revised to S3-222290 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221864 | KI7 Adding a solution on how to handle static auth in roaming with existing methods |
pCR revised to S3-222291 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221865 | KI7 conclusion on authorization mechanism determination | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-221866 | DraftCR NRF deployments | draftCR | Nokia, Nokia Shanghai Bell, Ericsson, Mavenir, Huawei, HiSilicon | DUMMY | Rel-18 |
S3-108-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-221867 | CR NRF deployments | CR | Nokia, Nokia Shanghai Bell, Ericsson, Mavenir, Huawei, HiSilicon | 33.501 17.6.0 CR#1437 catB | DUMMY | Rel-18 |
S3-108-e AI: 4.7 |
endorsed | [WTS] [JSN] |
S3-221868 | KI8 update of solution 10 and evaluation |
pCR revised to S3-222292 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221869 | KI8 conclusion on deploying multiple NRFs |
pCR revised to S3-222293 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221870 | KI9 sol11 EN resolution on authorization for inter-slicing access | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
merged | [WTS] [JSN] |
S3-221871 | LS reply to GSMA on Hosted SEPP |
LS out LS is reply to S3-221737 source LS: S3-221737 LS To: GSMA 5GMRR revised to S3-222304 |
Nokia, Nokia Shanghai Bell | 5G_eSBA |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] | ||
S3-221872 | KI10 conclusion on N32 roaming | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-221873 | KI11 conclusion on NFc registration at NRF | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-221874 | Secondary PDU re-authentication when UE is not reachable | CR | Samsung | 33.501 17.6.0 CR#1438 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221875 | Add a test case in TS 33.216 | draftCR | ZTE Corporation | SCAS_5G | Rel-18 |
S3-108-e AI: 4.4 |
noted | [WTS] [JSN] | |
S3-221876 | Adding AAnF critical assets to TS 33.926 |
other revised to S3-222369 |
ZTE Corporation | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
revised | [WTS] [JSN] | |
S3-221877 | Adding AKMA subscription asynchronization threats to TS 33.926 | draftCR | ZTE Corporation | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] | |
S3-221878 | Security Assurance Requirement and Test for AKMA subscription synchronization in the AAnF | pCR | ZTE Corporation | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] |
S3-221879 | 5GPRUK refresh in clause 6.3.3.3.2 | CR | ZTE Corporation | 33.503 17.0.1 CR#8 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-221880 | Clarification on subscription update in clause 6.3.3.3.2 | CR | ZTE Corporation | 33.503 17.0.1 CR#9 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-221881 | Verification of NSSAIs for preventing slice attack | draftCR | ZTE Corporation | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
noted | [WTS] [JSN] | |
S3-221882 | Add ApplicationKey_ AnonUser_Get into table 7.1.1-1 |
CR revised to S3-222368 |
ZTE Corporation | 33.535 17.6.0 CR#132 catF | AKMA | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221883 | Add Context_Remove into table 7.1.1-1. | CR | ZTE Corporation | 33.535 17.6.0 CR#133 catF | AKMA | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221884 | Add UDM or OAM in clause 6.6.1and 6.7 | CR | ZTE Corporation | 33.535 17.6.0 CR#134 catF | AKMA | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221885 | AKMA application context removal | CR | ZTE Corporation | 33.535 17.6.0 CR#135 catF | AKMA | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221886 | Adding a test case for gNB in TS 33.511 clause 4.2.2.1.4-R16 | CR | ZTE Corporation | 33.511 16.7.0 CR#29 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221887 | Adding a test case for gNB in TS 33.511 clause 4.2.2.1.4-R17 | CR | ZTE Corporation | 33.511 17.1.0 CR#30 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221888 | Adding a test case for gNB in TS 33.511 clause 4.2.2.1.4-R18 | CR | ZTE Corporation | 33.511 17.1.0 CR#31 catA | SCAS_5G | Rel-18 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221889 | Clarification on ResumeMAC-IshortResumeMAC-I check failed in clause 6.8.2.1.3-R15 | CR | ZTE Corporation | 33.501 15.16.0 CR#1439 catF | 5GS_Ph1-SEC | Rel-15 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221890 | Clarification on ResumeMAC-IshortResumeMAC-I check failed in clause 6.8.2.1.3-R16 | CR | ZTE Corporation | 33.501 16.11.0 CR#1440 catA | 5GS_Ph1-SEC | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221891 | Clarification on ResumeMAC-IshortResumeMAC-I check failed in clause 6.8.2.1.3-R17 | CR | ZTE Corporation | 33.501 17.6.0 CR#1441 catA | 5GS_Ph1-SEC | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221892 | Add terms and abbreviations to TR 33.882 |
pCR revised to S3-222367 |
ZTE Corporation | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-221893 | New KI on the Security of Network Slice Service continuity | pCR | ZTE Corporation | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-221894 | New KI-protecting information transfer in UE initiated slice-based SoR | pCR | ZTE Corporation | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-221895 | New KI on the security of providing access to local services | pCR | ZTE Corporation | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-221896 | DTLS for AKMA WID | WID new | ZTE Corporation | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221897 | Resolve EN for solution#11 |
pCR revised to S3-222311 |
Samsung | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221898 | Conclusion for KI#9 |
pCR revised to S3-222314 |
Samsung | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221899 | Updated work plan for SID eSBA security |
WI status report revised to S3-222277 |
Nokia, Nokia Shanghai Bell | FS_eSBA_SEC |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] | ||
S3-221900 | Solution to secure direct C2 and DAA connection |
pCR revised to S3-222268 |
Lenovo | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-221901 | Solution on enhancing the URSP rule with certificate fingerprint |
pCR revised to S3-222425 |
Lenovo | 33.892 0.1.0 | FS_USIA | Rel-18 |
S3-108-e AI: 5.18 |
revised | [WTS] [JSN] |
S3-221902 | Scope for TR 33.892 | pCR | Lenovo, Nokia, Nokia Shanghai Bell | 33.892 0.1.0 | FS_USIA | Rel-18 |
S3-108-e AI: 5.18 |
approved | [WTS] [JSN] |
S3-221903 | Update of KI#1 | pCR | Lenovo, Nokia, Nokia Shanghai Bell | 33.892 0.1.0 | FS_USIA | Rel-18 |
S3-108-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-221904 | Authentication of NF Producer in Indirect Communication |
pCR revised to S3-222326 |
CableLabs, Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221905 | Assumption on actors and attacker model | pCR | Lenovo | 33.892 0.1.0 | FS_USIA | Rel-18 |
S3-108-e AI: 5.18 |
noted | [WTS] [JSN] |
S3-221906 | EAP base authentication for AUN3 devices behind RG | pCR | CableLabs | 33.887 0.1.1 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-108-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-221907 | Clarification to multiple registrations in different PLMNs |
CR revised to S3-222255 |
Ericsson | 33.501 17.6.0 CR#1442 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221908 | Discussion paper on multiple registrations in different PLMN’s and different access types |
discussion revised to S3-222257 |
Ericsson | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] | ||
S3-221909 | Correction to authorization based on RSC |
CR revised to S3-222357 |
Ericsson | 33.503 17.0.1 CR#10 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-221910 | Clarifications of general description to Restricted 5G ProSe Direct Discovery |
CR revised to S3-222358 |
Ericsson | 33.503 17.0.1 CR#11 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-221911 | Rename 5GPRUK ID and 5GPRUK in CP based solution |
CR revised to S3-222359 |
Ericsson | 33.503 17.0.1 CR#12 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-221912 | New solution for PC5 link security when UE-to-UE relay is in coverage |
pCR revised to S3-222354 |
Ericsson | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-221913 | New solution for PC5 link security when UE-to-UE relay is out of coverage |
pCR revised to S3-222355 |
Ericsson | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-221914 | Reply LS on UE’s LTE UPIP capability for EN-DC |
LS out LS is reply to R3-223915 LS To: RAN3 |
Ericsson | UPIP_SEC | Rel-17 |
S3-108-e AI: 4.9 |
merged | [WTS] [JSN] | |
S3-221915 | Activation of UP IP in SgNB | CR | Ericsson | 33.401 17.2.0 CR#710 catF | UPIP_SEC | Rel-17 |
S3-108-e AI: 4.9 |
merged | [WTS] [JSN] |
S3-221916 | Key issue on Direct Communication Security | pCR | China Telecom Corporation Ltd. | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
merged | [WTS] [JSN] |
S3-221917 | Update to KI#1 Providing VPLMN slice information to roaming UE | pCR | Lenovo | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-221918 | Alignment of NAS transport protocol for 5G-RG over Wireline |
CR revised to S3-222263 |
Ericsson | 33.501 16.11.0 CR#1443 catF | 5WWC | Rel-16 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221919 | Alignment of NAS transport protocol for 5G-RG over Wireline |
CR revised to S3-222264 |
Ericsson | 33.501 17.6.0 CR#1444 catA | 5WWC | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221920 | Update key issue on Authentication and authorization for PINE | pCR | Philips International B.V. | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-221921 | Solution for PC5 link security establishment for U2U Relay |
pCR revised to S3-222402 |
China Telecom Corporation Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-221922 | Recent research papers on LTE security | discussion | CableLabs |
S3-108-e AI: 7 |
noted | [WTS] [JSN] | |||
S3-221923 | Key Issue on Authentication for access to localized services | pCR | Lenovo | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-221924 | New Solution UE-to-UE security |
pCR revised to S3-222296 |
Philips International B.V. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-221925 | Authentication and Authorization for UE originated API Invocation | pCR | Lenovo | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-221926 | Solution for U2U Relay (model A) discovery security | pCR | China Telecom Corporation Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221927 | Architectural assumption on out-of-coverage operation of UE-to-UE relay | pCR | Philips International B.V. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-221928 | Conclusion on KI9 authorization for inter-slicing access |
pCR revised to S3-222294 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221929 | New Key Issue on path switching between different N3IWFs | pCR | KPN N.V. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221930 | Solution for U2U Relay (model B) discovery security | pCR | China Telecom Corporation Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221931 | KI "Need for trust evidence collection for dynamic trust monitoring" | pCR | Ericsson India Private Limited | 33.894 0.1.0 | FS_ZTS | Rel-18 |
S3-108-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-221932 | Clarification on the authorzation of NF Service Consumers for data access via DCCF for R17 | CR | Huawei, Hisilicon | 33.501 17.6.0 CR#1445 catF | eNA_Ph2 | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221933 | Resolving EN in solution #6 |
pCR revised to S3-222327 |
Huawei, Hisilicon | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221934 | New solution for the authorization of the delegated subscribe |
pCR revised to S3-222328 |
Huawei, Hisilicon | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221935 | Resolving EN in solution #9 | pCR | Huawei, Hisilicon | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-221936 | Resolving EN in KI#3 | pCR | Huawei, Hisilicon | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
noted | [WTS] [JSN] |
S3-221937 | TS33.526 MnF threats |
pCR revised to S3-222329 |
Huawei, Hisilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-221938 | TS33.526 Mnf_test cases | pCR | Huawei, Hisilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
noted | [WTS] [JSN] |
S3-221939 | new threat for KAUSF handling | draftCR | Huawei,HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
noted | [WTS] [JSN] | |
S3-221940 | token verification modification to include SNPN snenario | draftCR | Huawei,HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
noted | [WTS] [JSN] | |
S3-221941 | PLMNID verification modification to include SNPN scenario | draftCR | Huawei,HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
noted | [WTS] [JSN] | |
S3-221942 | clarification on IP_FWD_DISABLING-R16 |
CR revised to S3-222330 |
Huawei,HiSilicon | 33.117 16.7.0 CR#73 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221943 | clarification on IP_FWD_DISABLING-R17 |
CR revised to S3-222331 |
Huawei,HiSilicon | 33.117 17.0.0 CR#74 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221944 | modification on EXCLUSIVE_EXECUTE_RIGHTS-R16 |
CR revised to S3-222332 |
Huawei,HiSilicon | 33.117 16.7.0 CR#75 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221945 | modification on EXCLUSIVE_EXECUTE_RIGHTS-R17 |
CR revised to S3-222333 |
Huawei,HiSilicon | 33.117 17.0.0 CR#76 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221946 | modification on Handling of ICMP-R16 |
CR revised to S3-222334 |
Huawei,HiSilicon | 33.117 16.7.0 CR#77 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221947 | modification on Handling of ICMP-R17 |
CR revised to S3-222335 |
Huawei,HiSilicon | 33.117 17.0.0 CR#78 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221948 | modification on IP_MULTICAST_HANDLING-R16 |
CR revised to S3-222336 |
Huawei,HiSilicon | 33.117 16.7.0 CR#79 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221949 | modification on IP_MULTICAST_HANDLING-R17 |
CR revised to S3-222337 |
Huawei,HiSilicon | 33.117 17.0.0 CR#80 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221950 | DP on loss of control of preferred SNPN list in eNPN | discussion | Huawei,HiSilicon | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] | |
S3-221951 | New KI on loss of control of preferred SNPN list in eNPN | pCR | Huawei,HiSilicon | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-221952 | New solution for 3rd party ID | pCR | Huawei, HiSilicon | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
merged | [WTS] [JSN] |
S3-221953 | New KI on security aspects of SBA in IMS | pCR | Huawei, HiSilicon | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-221954 | New KI on security aspects of IMS DC |
pCR revised to S3-222338 |
Huawei, HiSilicon | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-221955 | New Key Issue: Robustness of NG-RAN AI/ML against attacks | pCR | Philips International B.V. | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-221956 | Key Issue#1 on Need for continuous Trust evaluation | pCR | Lenovo, Nokia, Nokia Shanghai Bell, Rakuten Mobile Inc., Interdigital, US NSA, Motorola Solutions, Johns Hopkins University APL, Intel, Center for Internet Security, China Mobile, ZTE, CableLabs | 33.894 0.1.0 | FS_ZTS | Rel-18 |
S3-108-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-221957 | Editorial correction | pCR | Philips International B.V. | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-221958 | New Key Issue on Usage of Evaluated Trust Information | pCR | Lenovo | 33.894 0.1.0 | FS_ZTS | Rel-18 |
S3-108-e AI: 5.21 |
withdrawn | [WTS] [JSN] |
S3-221959 | Rel-15 Correcting the OAuth 2.0 roles in CAPIF | CR | Ericsson | 33.122 15.3.0 CR#28 catF | CAPIF-Sec | Rel-15 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221960 | Rel-16 Correcting the OAuth 2.0 roles in CAPIF | CR | Ericsson | 33.122 16.3.0 CR#29 catA | CAPIF-Sec | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221961 | Rel-17 Correcting the OAuth 2.0 roles in CAPIF | CR | Ericsson | 33.122 17.0.0 CR#30 catA | CAPIF-Sec | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221962 | Correction and clarification in user consent requirements | CR | Ericsson | 33.558 17.1.0 CR#4 catF | eEDGE_5GC | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221963 | Addressing authorization for EDGE-9 | CR | Ericsson | 33.558 17.1.0 CR#5 catF | eEDGE_5GC | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221964 | [DRAFT] Reply LS on user’s consent for EDGEAPP |
LS out LS is reply to C3-223780 LS To: CT3 |
Ericsson | eEDGE_5GC | Rel-17 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |
S3-221965 | Corrections and clarifications on the usage of HTTPS and X.509 certificates | CR | Ericsson | 33.558 17.1.0 CR#6 catF | eEDGE_5GC | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221966 | Correction on the implementation of CR 0013 (S3-220917) | CR | Ericsson | 33.434 17.2.0 CR#14 catF | eSEAL | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221967 | Update to key issue #1 | pCR | Ericsson | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-221968 | A new key issue on authorization by resource owner | pCR | Ericsson | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-221969 | New solution on authentication procedure of UE-to-UE relay | pCR | OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221970 | Update Key Issue #1: privacy risks of exposing positioning reference signals | pCR | Philips International B.V. | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-221971 | New solution on end-to-end security establishmet for UE-to-UE relay | pCR | OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
withdrawn | [WTS] [JSN] |
S3-221972 | Clarification for ProSe UE-to-Network Relay security procedure over Control Plane in TS33.503 | CR | China Telecom Corporation Ltd. | 33.503 17.0.1 CR#13 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-221973 | Update Key Issue #3: source authenticity verification | pCR | Philips International B.V. | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-221974 | Update Key Issue #2: User consent for NTN | pCR | Philips International B.V. | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-221975 | Correction figure in 5G ProSe Discoervery in TS33.503 | CR | China Telecom Corporation Ltd. | 33.503 17.0.1 CR#14 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-221976 | LS reply to 3GPP on Alignment of EDGEAPP and ETSI MEC | LS in | ETSI ISG MEC |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221977 | Confidentiality protection of SMS content over N32 | CR | NTT DOCOMO INC. | 33.501 17.6.0 CR#1446 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221978 | Update to and split of KI#10 to clarify the scenarios |
pCR revised to S3-222436 |
BSI (DE),Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221979 | new KI on Identity verification for UE-to-UE relay scenarios | pCR | OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
withdrawn | [WTS] [JSN] |
S3-221980 | Solution for KI#10 (hosted SEPP) |
pCR revised to S3-222437 |
BSI (DE),Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-221981 | Correction figure in ProSe UE-to-Network Relay security procedure over Control Plane in TS33.503 |
CR revised to S3-222403 |
China Telecom Corporation Ltd. | 33.503 17.0.1 CR#15 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-221982 | New Key Issue "Authentication for UE access to hosting network" | pCR | Ericsson, Intel, Nokia, Nokia Shanghai Bell | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-221983 | Discussion on the SAN and SBA certificate profiles | discussion | Ericsson |
S3-108-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-221984 | Clarification on the format of callback URI in the NF certificate profile | CR | Ericsson | 33.31 16.10.0 CR#131 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-221985 | Clarification on the format of callback URI in the NF certificate profile | CR | Ericsson | 33.31 17.3.0 CR#132 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-221986 | Clarification on the certificate profile for SCP |
CR revised to S3-222297 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.31 16.10.0 CR#133 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221987 | Clarification on the certificate profile for SCP |
CR revised to S3-222298 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.31 17.3.0 CR#134 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221988 | Clarification on the certificate profile for SEPP | CR | Ericsson | 33.31 16.10.0 CR#135 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221989 | Clarification on the certificate profile for SEPP | CR | Ericsson | 33.31 17.3.0 CR#136 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221990 | Review request of an IETF draft on X.509 Certificate Extension for 5G Network Function Types | discussion | Ericsson |
S3-108-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-221991 | Clarification of SNI usage for NF clients and servers |
CR revised to S3-222299 |
Ericsson | 33.501 17.6.0 CR#1447 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221992 | Clarification on OAuth 2.0 in interconnect and roaming scenarios | discussion | Ericsson |
S3-108-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-221993 | Clarification on OAuth2.0 in interconnect and roaming scenarios, alternative 1 |
CR revised to S3-222300 |
Ericsson | 33.501 16.11.0 CR#1448 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221994 | Clarification on OAuth2.0 in interconnect and roaming scenarios, alternative 2 | CR | Ericsson | 33.501 16.11.0 CR#1449 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221995 | Authorization between SCPs: Alignment with CR 1414 | CR | Ericsson | 33.501 16.11.0 CR#1450 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-221996 | Clarification on access token requests for NF Producers of a specific NF type and token-based authorization for indirect communication with delegated discovery | CR | Ericsson | 33.501 16.11.0 CR#1451 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221997 | Clarification on access token requests for NF Producers of a specific NF type and token-based authorization for indirect communication with delegated discovery | CR | Ericsson | 33.501 17.6.0 CR#1452 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-221998 | SEPP to include and verify the source PLMN-ID | draftCR | Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-221999 | Discussion regarding issues for NRF validation of NFc for access token | discussion | Ericsson |
S3-108-e AI: 5.24 |
noted | [WTS] [JSN] | |||
S3-222000 | Certificate solution for NRF validation of NFc for access token requests |
pCR revised to S3-222302 |
Ericsson | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-222001 | Combined certificate and profile solution for NRF validation of NFc for access token requests |
pCR revised to S3-222303 |
Ericsson | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-222002 | Correction figure in ProSe Discovery in TS33.303(R15) | CR | China Telecom Corporation Ltd. | 33.303 15.0.0 CR#136 catF | 5GS_Ph1-SEC | Rel-15 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222003 | Correction figure in ProSe Discovery in TS33.303(R16) - mirror | CR | China Telecom Corporation Ltd. | 33.303 16.0.0 CR#137 catA | 5GS_Ph1-SEC | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222004 | Correction figure in ProSe Discovery in TS33.303 | CR | China Telecom Corporation Ltd. | 33.303 17.0.0 CR#138 catF | 5GS_Ph1-SEC, TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222005 | clarify Remote UE ID of Remote UE report for CP based security | CR | Nokia, Nokia Shanghai Bell | 33.503 17.0.1 CR#16 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.8 |
merged | [WTS] [JSN] |
S3-222006 | Add restriction for multi registrations in two PLMNs | CR | Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1453 catA | TEI16 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222007 | control on NSSAA procedures for multi registrations in two PLMNs | CR | Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1454 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222008 | Add restriction for multi registrations in two PLMNs | CR | Nokia, Nokia Shanghai Bell | 33.501 16.11.0 CR#1455 catF | TEI16 | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222009 | control on NSSAA procedures for multi registrations in two PLMNs | CR | Nokia, Nokia Shanghai Bell | 33.501 16.11.0 CR#1456 catA | TEI17 | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222010 | LS for multi-registration impact on UE authentication |
LS out LS To: SA2, CT1 |
Nokia, Nokia Shanghai Bell |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-222011 | New Key issue on the security of the information transfer of the RAN AI/ML framework | pCR | Ericsson | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-222012 | New Key issue on the privacy of information handled by the RAN AI/ML framework |
pCR revised to S3-222404 |
Ericsson | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-222013 | New WID on IETF OSCORE Ua* protocol profile for AKMA | WID new | Ericsson | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-222014 | IETF OSCORE as AKMA Ua* protocol | CR | Ericsson, Deutsche Telekom | 33.535 17.6.0 CR#136 catB | DUMMY | Rel-18 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222015 | Extending the Ua security protocol namespace to include the AKMA OSCORE Ua* protocol | CR | Ericsson, Deutsche Telekom | 33.22 17.3.0 CR#218 catB | DUMMY | Rel-18 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222016 | Discussion on the authentication result removal operation | discussion | Ericsson |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-222017 | LS on AUSF and UDM authentication result service operation |
LS out LS To: CT4 |
Ericsson |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-222018 | Discussion on the authorization of Application Functions for NSACF services via the NEF | discussion | Ericsson | Rel-17 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-222019 | Clarification on AF authorization for the NSACF notification procedure | CR | Ericsson | 33.501 17.6.0 CR#1457 catF | eNS2_SEC | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222020 | Alignment of NSACF notification procedure with existing procedures | CR | Ericsson | 33.501 17.6.0 CR#1458 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222021 | Living document for SERP: draftCR to TS 33.501 on the Protection of the RRC Resume Request message | draftCR | Ericsson | SERP | Rel-18 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | |
S3-222022 | New solution: How the Originating IMS network signs the 3rd party IDs and terminating IMS network verifies the 3rd party IDs |
pCR revised to S3-222401 |
Ericsson | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-222023 | CR to TS33.503 Clean up clause 6.1.3.2.2 | CR | CATT | 33.503 17.0.1 CR#17 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222024 | Discussion paper on improvements of TS33.117 | discussion | BSI (DE) | Rel-18 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-222025 | Clarification on Authentication for UE behind 5G-RG and FN-RG |
CR revised to S3-222324 |
CableLabs | 33.501 17.6.0 CR#1459 catF | NSWO_5G | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-222026 | CR to TS33.503 Correct error in clause 6.3.3.2.2 | CR | CATT | 33.503 17.0.1 CR#18 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
merged | [WTS] [JSN] |
S3-222027 | CR to TS33.503 Define reference point for PAnF | CR | CATT | 33.503 17.0.1 CR#19 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222028 | Adding optional use of CCA for delegated discovery | CR | China Telecommunications, Nokia, Nokia Shanghai Bell | 33.501 16.11.0 CR#1460 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-222029 | CR to TS33.503 Remove secondary authentication related content |
CR revised to S3-222400 |
CATT | 33.503 17.0.1 CR#20 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-222030 | CR to TS33.503 Update Abbreviations | CR | CATT | 33.503 17.0.1 CR#21 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222031 | Adding optional use of CCA for delegated discovery(mirror) | CR | China Telecommunications, Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1461 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-222032 | CR to TS33.503 Update Figure 6.3.3.3.2-1 | CR | CATT | 33.503 17.0.1 CR#22 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
merged | [WTS] [JSN] |
S3-222033 | Revise the pre-requisite of access token request | CR | China Telecommunications | 33.501 16.11.0 CR#1462 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-222034 | Revise the pre-requisite of access token request(mirror) | CR | China Telecommunications | 33.501 17.6.0 CR#1463 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-222035 | Revise the subject that performs verificaiton of access token | CR | China Telecommunications | 33.501 16.11.0 CR#1464 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-222036 | Revise the subject that performs verificaiton of access token(mirror) | CR | China Telecommunications | 33.501 17.6.0 CR#1465 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-222037 | EDGE-9 and Interface Between EASs Security | CR | InterDigital Communications | 33.558 17.1.0 CR#7 catB | eEDGE_5GC | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222038 | draft-Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network |
LS out LS is reply to S3-221734 LS To: SA6 |
Intel |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-222039 | Study on enhancements to facilitate N32 adoption by Standalone Non-Public Networks | SID new | Intel |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-222040 | draft-Reply LS on Facilitating roaming adoption across 3GPP NPN deployments |
LS out LS is reply to S3-221740 LS To: WBA OpenRoaming Technical Standards Task Group |
Intel |
S3-108-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-222041 | Discussion about the enhancement to N32 Reference Point | discussion | Intel |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-222042 | Updates to non-3gpp access key issue | pCR | Intel | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-222043 | Detection of MiTM attacks. | pCR | Intel | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-222044 | Anomalous Behaviour Detection | pCR | Intel | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-222045 | Privacy-Preserving Machine Learning | pCR | Intel | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
withdrawn | [WTS] [JSN] |
S3-222046 | Privacy-Preserving Machine Learning | pCR | Intel | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
merged | [WTS] [JSN] |
S3-222047 | Update IPSec reference from obsolete RFC 7296 to RFC 8247 |
CR revised to S3-222346 |
Intel | 33.21 17.0.0 CR#73 catF | eCryptPr | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-222048 | Update IPSec reference from obsolete RFC 7296 to RFC 8247 |
CR revised to S3-222347 |
Intel | 33.21 17.0.0 CR#74 catF | eCryptPr | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-222049 | Discussion Paper on Revised WID(s) on AKMA Kaf Refresh | discussion | OPPO, ZTE, Nokia, Nokia Shanghai Bell, Samsung |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-222050 | Revised SID on enhancement of AKMA | other | OPPO, ZTE, Nokia, Nokia Shanghai Bell, Samsung, Apple, VIVO | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-222051 | Revised SID on Study of Security aspect of home network triggered primary authentication | other | OPPO, ZTE, Nokia, Nokia Shanghai Bell, Samsung |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-222052 | Update of KI#2 |
pCR revised to S3-222306 |
OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-222053 | New KI on U2U relay protection of remote UE traffic | pCR | OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-222054 | New Solution on security negotiation of U2U relay protection of remote UE traffic | pCR | OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-222055 | clarification on the internal authentication and an external authentication | CR | Huawei, HiSilicon | 33.501 17.6.0 CR#1466 catF | eNPN | Rel-18 |
S3-108-e AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-222056 | Discussion on ZTA study approach | discussion | Huawei, HiSilicon | FS_ZTS | Rel-18 |
S3-108-e AI: 5.21 |
noted | [WTS] [JSN] | |
S3-222057 | Addition of tenant evaluation clause | pCR | Huawei, HiSilicon | 33.894 0.1.0 | FS_ZTS | Rel-18 |
S3-108-e AI: 5.21 |
approved | [WTS] [JSN] |
S3-222058 | Clarifications to TS 33.535 | CR | Huawei, HiSilicon | 33.535 17.6.0 CR#137 catF | AKMA | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222059 | Discussion on Kiab handling in IAB migiration | discussion | Huawei, HiSilicon | Rel-17 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-222060 | CR on Kiab handling in IAB migiration | CR | Huawei, HiSilicon | 33.501 17.6.0 CR#1467 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222061 | LS on Kiab handling in IAB migiration |
LS out LS To: RAN3 |
Huawei, HiSilicon | Rel-17 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-222062 | Alignment with RAN3 LS for EN-DC for UPIP |
CR revised to S3-222431 |
Huawei, HiSilicon | 33.401 17.2.0 CR#711 catF | UPIP_SEC_LTE | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-222063 | Reply LS on UE’s LTE UPIP capability for EN-DC |
LS out LS To: RAN3 revised to S3-222432 |
Huawei, HiSilicon | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] | ||
S3-222064 | Add threat and requirement to PINE authentication |
pCR revised to S3-222374 |
Huawei, HiSilicon | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-222065 | Solution on PINE authentication | pCR | Huawei, HiSilicon | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-222066 | Add threat and requirement to key issue on TMGI protection | pCR | Huawei, HiSilicon | 33.883 0.1.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-222067 | Add threat and requirement to key issue on MOCN | pCR | Huawei, HiSilicon | 33.883 0.1.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-222068 | New key issue on security protection for Ues in RRC inactive state | pCR | Huawei, HiSilicon | 33.883 0.1.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-222069 | Solution on security protection in MOCN network sharing scenario | pCR | Huawei, HiSilicon | 33.883 0.1.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
noted | [WTS] [JSN] |
S3-222070 | MBS_Abbreviations update | pCR | Huawei, HiSilicon | 33.883 0.1.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
approved | [WTS] [JSN] |
S3-222071 | Addressing the editor's note in key issue#1 | pCR | Huawei, HiSilicon | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-222072 | New SID on eLCS security | WID new | Huawei, HiSilicon | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-222073 | Discussion paper on eLCS security | discussion | Huawei, HiSilicon | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-222074 | Resolution of the issue of authentication mechanism selection |
CR revised to S3-222375 |
Huawei, HiSilicon | 33.503 17.0.1 CR#23 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-222075 | Delete of secondary authentication | CR | Huawei, HiSilicon | 33.503 17.0.1 CR#24 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
merged | [WTS] [JSN] |
S3-222076 | Clarification on 5G ProSe Remote UE specific authentication mechanism |
CR revised to S3-222376 |
Huawei, HiSilicon | 33.503 17.0.1 CR#25 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-222077 | Remote UE Report when security procedure over Control Plane is performed |
CR revised to S3-222377 |
Huawei, HiSilicon | 33.503 17.0.1 CR#26 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-222078 | clarification on SUPI in Nudm_UEAuthentication_GetProseAv service | CR | Huawei, HiSilicon | 33.503 17.0.1 CR#27 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-222079 | Add clause of broadcast communication | CR | Huawei, HiSilicon | 33.503 17.0.1 CR#28 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222080 | Add clause of groupcast communication | CR | Huawei, HiSilicon | 33.503 17.0.1 CR#29 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222081 | New Key Issue on Security and privacy of path switching between two indirect network communication paths for UE-to-Network Relaying |
pCR revised to S3-222378 |
Huawei, HiSilicon | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-222082 | New Key Issue on Security and privacy of path switch between L2 U2NW and direct connections |
pCR revised to S3-222379 |
Huawei, HiSilicon | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-222083 | New Key Issue on Security and privacy of multi-path transmission for UE-to-Network Relay |
pCR revised to S3-222380 |
Huawei, HiSilicon | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-222084 | New Key Issue on the Security of Ranging/SL Positioning PC5 direct | pCR | Huawei, HiSilicon | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
merged | [WTS] [JSN] |
S3-222085 | R18 WID on security for Isolated Operation for Public Safety in 5G system | WID new | Huawei, HiSilicon | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-222086 | Discussion on the security of Isolated Operation for Public Safety in 5GS | discussion | Huawei, HiSilicon | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-222087 | New solution about Security establishment and link security protection of unicast PC5 communication | pCR | Huawei, HiSilicon | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-222088 | Address EN for UC3S |
CR revised to S3-222433 |
Huawei, HiSilicon,Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1468 catF | UC3S_SEC | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-222089 | Reply LS on User Consent for EDGEAPP |
LS out LS To: CT3, SA6 |
Huawei, HiSilicon | Rel-17 |
S3-108-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-222090 | Protection of RRC Resume Request mesasge | draftCR | Huawei, HiSilicon | SERP | Rel-18 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | |
S3-222091 | New key issue on User Consent for AI/ML for RAN | pCR | Huawei, HiSilicon | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222092 | Key Issue Update on User Consent for NTN | pCR | Huawei, HiSilicon | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222093 | New solution on User Consent for Roaming of eNA | pCR | Huawei, HiSilicon | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222094 | New solution on User Consent Architecture for RAN as enforcement point | pCR | Huawei, HiSilicon | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222095 | New solution on User authorization for network exposure | pCR | Huawei, HiSilicon | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222096 | Correction to Nausf_UEAuthentication_Authenticate service | CR | Huawei, HiSilicon | 33.503 17.0.1 CR#30 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222097 | Address UPIP forward compability issue | CR | Huawei, HiSilicon | 33.401 17.2.0 CR#712 catF | UPIP_SEC_LTE | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222098 | supporting UP IP at eNB |
draftCR revised to S3-222381 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
revised | [WTS] [JSN] | |
S3-222099 | UP IP policy selection-R18 |
draftCR revised to S3-222382 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
revised | [WTS] [JSN] | |
S3-222100 | locally UP IP supporting at eNB |
draftCR revised to S3-222383 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
revised | [WTS] [JSN] | |
S3-222101 | Revised WID for 5G SCAS work for Rel-17 features on existing functions | WID revised | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 6 |
agreed | [WTS] [JSN] | |
S3-222102 | draft CR to 33.926 on locally UP IP supporting at eNB |
draftCR revised to S3-222384 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
revised | [WTS] [JSN] | |
S3-222103 | draft CR to 33.926 on UP IP policy selection at eNB |
draftCR revised to S3-222385 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
revised | [WTS] [JSN] | |
S3-222104 | Living document to TR 33.926 for SCAS 5G Ph2 |
draftCR revised to S3-222386 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
revised | [WTS] [JSN] | |
S3-222105 | update testcase in clause 4.2.3.2.4 | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-222106 | Update requirement and add new test case to clause 4.2.3.4.3.1 | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
noted | [WTS] [JSN] | |
S3-222107 | Update requirement and add new test case to clause 4.2.3.4.3.2 | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
noted | [WTS] [JSN] | |
S3-222108 | AAnF authorized the AF | pCR | Huawei, HiSilicon | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] |
S3-222109 | NEF authorized the AF | pCR | Huawei, HiSilicon | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] |
S3-222110 | AAnF replies error response | pCR | Huawei, HiSilicon | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] |
S3-222111 | draft CR to 33.926 on AAnF authorizes the AF | draftCR | Huawei, HiSilicon | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] | |
S3-222112 | draft CR to 33.926 on NEF authorizes the AF | draftCR | Huawei, HiSilicon | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] | |
S3-222113 | draft CR to 33.926 on error response | draftCR | Huawei, HiSilicon | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] | |
S3-222114 | Update clause 4.2.3 | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
approved | [WTS] [JSN] |
S3-222115 | Update clause 4.2.4 | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
noted | [WTS] [JSN] |
S3-222116 | Update clause 4.2.5, and 4.2.6 |
pCR revised to S3-222267 |
Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-222117 | Add new content for clause 4.3 | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
noted | [WTS] [JSN] |
S3-222118 | Add new content for clause 4.4 | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
approved | [WTS] [JSN] |
S3-222119 | Living document for MnF SCAS |
draftCR revised to S3-222265 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-222120 | Security assurance specification drafting | discussion | Huawei, HiSilicon | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-222121 | Clarification on ID handling at AMF and 5G PKMF | CR | Huawei, HiSilicon | 33.503 17.0.1 CR#31 catF | 5G_ProSe | Rel-18 |
S3-108-e AI: 4.8 |
withdrawn | [WTS] [JSN] |
S3-222122 | add a new requirement and test case | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
noted | [WTS] [JSN] |
S3-222123 | clarification on the internal authentication and an external authentication |
CR revised to S3-222388 |
Huawei, HiSilicon | 33.501 17.6.0 CR#1469 catF | eNPN | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-222124 | Clarification on ID handling at AMF and 5G PKMF | CR | Huawei, HiSilicon | 33.503 17.0.1 CR#32 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-222125 | Detecting sources of potential data poisoning attacks towards RAN AI-ML based network optimizations | pCR | Nokia, Nokia Shanghai Bell | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-222126 | Discussion of Distributed Intelligent Enabled 6G Networks | discussion | Xidian University |
S3-108-e AI: 5.14 |
noted | [WTS] [JSN] | |||
S3-222127 | New Key Issue on User Consent for Roaming of Edge Application | pCR | China Mobile, Huawei, HiSilicon, OPPO | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222128 | New Solution on User Consent for Edge Application | pCR | China Mobile, Huawei, HiSilicon, OPPO | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222129 | Key issue for privacy protection for unicast messages over PC5 |
pCR revised to S3-222427 |
China Mobile | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-222130 | Address EN in Overview and editorial modification |
pCR revised to S3-222428 |
China Mobile | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-222131 | LS reply on User plane security |
LS out LS To: GSMA revised to S3-222426 |
China Mobile | Rel-17 |
S3-108-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-222132 | UP IP security | CR | China Mobile | 33.501 17.6.0 CR#1470 catF | 5GS_Ph1-SEC | Rel-17 |
S3-108-e AI: 3 |
not pursued | [WTS] [JSN] |
S3-222133 | Correction of Transport security protection for MSGin5G interfaces |
CR revised to S3-222398 |
China Mobile | 33.501 17.6.0 CR#1471 catF | 5GMSG | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-222134 | Introduction of AAnF-specific security requirements and related test cases | pCR | China Mobile | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-222135 | General description of clause 4.2.2 | pCR | China Mobile | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-222136 | Adding AAnF critical assets and threats to TS 33.926 | draftCR | China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] | |
S3-222137 | Adding a test case of AKMA key strorage and update | pCR | China Mobile | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
noted | [WTS] [JSN] |
S3-222138 | Adding technical baseline text | pCR | China Mobile | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-222139 | Adding text to clause 4.2.4 | pCR | China Mobile | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-222140 | Adding text to clause 4.2.5 | pCR | China Mobile | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-222141 | Adding text to clause 4.2.6 | pCR | China Mobile | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-222142 | Living document for AAnF SCAS – draftCR to TR 33.926 |
draftCR revised to S3-222270 |
China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
revised | [WTS] [JSN] | |
S3-222143 | AAnF sending GPSI to internal AKMA AF | CR | China Mobile | 33.535 17.6.0 CR#138 catF | AKMA | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222144 | Adding overview of SECAM for 3GPP virtualized networ products into clause 4 in TR 33.936 |
pCR revised to S3-222407 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222145 | Adding Scope of SECAM for 3GPP virtualized network products of type 1 into clause 4 in TR 33.936 |
pCR revised to S3-222408 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222146 | Adding Scope of SECAM for 3GPP virtualized network products of type 2 into clause 4 in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222147 | Adding Scope of SECAM for 3GPP virtualized network products of type 3 into clause 4 in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222148 | Adding Scope of SECAM evaluation for type 1 of 3GPP virtualized network products into clause 4 in TR 33.936 |
pCR revised to S3-222409 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222149 | Adding Scope of SECAM evaluation for type 2 of 3GPP virtualized network products into clause 4 in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222150 | Adding Scope of SECAM evaluation for type 3 of 3GPP virtualized network products into clause 4 in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222151 | Adding Scope of SECAM accreditation for type 1 of 3GPP virtualized network products into clause 4 in TR 33.936 |
pCR revised to S3-222410 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222152 | Adding Scope of SECAM accreditation for type 2 of 3GPP virtualized network products into clause 4 in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222153 | Adding Scope of SECAM accreditation for type 3 of 3GPP virtualized network products into clause 4 in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222154 | Adding contents of chapters 4.5 about type 1 of 3GPP virtualized network product in TR 33.936 |
pCR revised to S3-222411 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222155 | Adding contents of chapters 4.5 about type 2 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222156 | Adding contents of chapters 4.5 about type 3 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222157 | Adding contents of chapters 4.6 for type 1 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222158 | Adding contents of chapters 4.6 for type 2 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222159 | Adding contents of chapters 4.6 for type 3 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222160 | Adding contents of chapters 4.7 for type 1 of 3GPP virtualized network product in TR 33.936 |
pCR revised to S3-222412 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222161 | Adding contents of chapters 4.7 for type 2 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222162 | Adding contents of chapters 4.7 for type 3 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222163 | Adding contents of chapters 4.8 for type 1 of 3GPP virtualized network product in TR 33.936 |
pCR revised to S3-222413 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222164 | Adding contents of chapters 4.8 for type 2 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222165 | Adding contents of chapters 4.8 for type 3 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222166 | Adding contents of chapters 4.9 for type 1 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222167 | Adding contents of chapters 4.9 for type 2 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222168 | Adding contents of chapters 4.9 for type 3 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222169 | Adding contents of chapters 4.10 for type 1 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222170 | Adding contents of chapters 4.10 for type 2 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222171 | Adding contents of chapters 4.10 for type 3 of 3GPP virtualized network product in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222172 | Adding content to clause 5.1 in TR 33.936 |
pCR revised to S3-222414 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222173 | Adding description about general content of SCAS document and ToE to clause 5.2 in TR 33.936 |
pCR revised to S3-222415 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222174 | Adding description about SPD to clause 5.2 in TR33.936 |
pCR revised to S3-222416 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222175 | Adding description about methodology of security requirements to clause 5.2 in TR 33.936 |
pCR revised to S3-222417 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222176 | Adding description about improvement of SCAS and new potential security requirements to clause 5.3 in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222177 | Adding description about basic vulnerability testing requirements for GVNP to clause 5.4 in TR 33.936 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222178 | Proposal to add overview in clause 4 Generic Virtulizated Network Product (GVNP) class for type 1 in TR 33.927 |
pCR revised to S3-222418 |
China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222179 | Proposal to add overview in clause 4 Generic Virtulizated Network Product (GVNP) class for type 2 in TR 33.927 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222180 | Proposal to add overview in clause 4 Generic Virtulizated Network Product (GVNP) class for type 3 in TR 33.927 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222181 | Proposal to add clause 4.2 Minimum set of functions defining the GVNP class in TR 33.927 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222182 | Proposal to add introduction in clause 4.3 Generic virtualized network product model for type 1 in TR33.927 |
pCR revised to S3-222419 |
China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222183 | Proposal to add introduction in clause 4.3 Generic virtualized network product model for type 2 in TR33.927 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222184 | Proposal to add introduction in clause 4.3 Generic virtualized network product model for type 3 in TR33.927 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222185 | Proposal to add GVNP model of type 1 in TR 33.927 |
pCR revised to S3-222420 |
China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-222186 | Proposal to add GVNP model of type 2 in TR 33.927 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222187 | Proposal to add GVNP model of type 3 in TR 33.927 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-222188 | New key issue on Identity verification for UE-to-UE relay scenarios | pCR | OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-222189 | New solution on end-to-end security establishmet for UE-to-UE relay |
pCR revised to S3-222341 |
OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-222190 | SERP-CR to 33501 | CR | Apple | 33.501 17.6.0 CR#1472 catB | SERP | Rel-18 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222191 | SERP-Draft LS on SERP |
LS out LS To: RAN, RAN2, RAN3 |
Apple | Rel-18 |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-222192 | 33401CR - Clarification on NAS COUNT usage in KeNB derivation | CR | Apple | 33.501 17.6.0 CR#1473 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222193 | 33501CR - Clarification on NAS COUNT usage in KeNB derivation | CR | Apple | 33.501 17.6.0 CR#1474 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222194 | 33501_s1n1_idlemode_mapped_ctxt | CR | Apple | 33.501 17.6.0 CR#1475 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222195 | 33501CR on fast reauthentication | CR | Apple | 33.501 17.6.0 CR#1476 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222196 | CR to TS33.503 Modify clause and figure titles for U2N relay clauses | CR | CATT | 33.503 17.0.1 CR#33 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222197 | New SID on Security Aspects of Satellite Access |
SID new revised to S3-222439 |
Xiaomi, China Mobile, China Telecom, Qualcomm, InterDitigal, ZTE, Nokia, Nokia Shanghai Bell, Thales | Rel-18 |
S3-108-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-222198 | Updates to U2N Relay Discovery Security Procedure |
CR revised to S3-222352 |
Xiaomi Technology | 33.503 17.0.1 CR#34 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-222199 | DDNMF Selection during U2N Relay Discovery Security Procedure | CR | Xiaomi Technology | 33.503 17.0.1 CR#35 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-222200 | Match Report in U2N Relay Discovery Security Procedure | CR | Xiaomi Technology | 33.503 17.0.1 CR#36 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-222201 | Updates to Key Definitions | CR | Xiaomi Technology | 33.503 17.0.1 CR#37 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-222202 | Security Method Check during U2N Relay Discovery Procedure | CR | Xiaomi Technology | 33.503 17.0.1 CR#38 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-222203 | Security Method Check during CP-based U2N Relay Communication Establishment | CR | Xiaomi Technology | 33.503 17.0.1 CR#39 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-222204 | Security Method Check during UP-based U2N Relay Communication Establishment | CR | Xiaomi Technology | 33.503 17.0.1 CR#40 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-222205 | Corrections in TS 33.503 |
CR revised to S3-222353 |
Xiaomi Technology | 33.503 17.0.1 CR#41 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] |
S3-222206 | 33.893: Terminology Alignment | pCR | Xiaomi Technology | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-222207 | 33.893: New Key Issue on Security for PC5 Communication |
pCR revised to S3-222349 |
Xiaomi Technology | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-222208 | 33.893: New Key Issue on Security for SR5 Communication | pCR | Xiaomi Technology | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
merged | [WTS] [JSN] |
S3-222209 | 33.893: Add Third Party UE in KI#2 |
pCR revised to S3-222348 |
Xiaomi Technology | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-222210 | 33.893: Solution on Assistant UE Authorization during Discovery for KI#2 | pCR | Xiaomi Technology | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-222211 | 33.893: Solution on Application Server Authorization for KI#2 | pCR | Xiaomi Technology | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-222212 | 33.893: Solution on 5GC NF Authorization for KI#2 | pCR | Xiaomi Technology | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-222213 | 33.896: Requirements for Key Issue #2 | pCR | Xiaomi Technology | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222214 | 33.896: Solution on Obtaining User Consent in Non-mobility Case for KI#2 |
pCR revised to S3-222350 |
Xiaomi Technology | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-222215 | 33.896: Solution on Obtaining User Consent Revocation for KI#2 |
pCR revised to S3-222351 |
Xiaomi Technology | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-222216 | New solution on Network-assisted Security Establishment Procedure for 5G ProSe Layer-3 UE-to-UE Relay | pCR | Beijing Xiaomi Mobile Software | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-222217 | New solution on Non-network-assisted Security Establishment Procedure for 5G ProSe Layer-3 UE-to-UE Relay |
pCR revised to S3-222371 |
Beijing Xiaomi Mobile Software | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-222218 | New solution on Restricted 5G ProSe UE-to-UE Relay Discovery Model A |
pCR revised to S3-222372 |
Beijing Xiaomi Mobile Software | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-222219 | New solution on Restricted 5G ProSe UE-to-UE Relay Discovery Model B |
pCR revised to S3-222373 |
Beijing Xiaomi Mobile Software | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-222220 | New solution on AAA Server based Authorization for Third Party Specific User Identities | pCR | Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
merged | [WTS] [JSN] |
S3-222221 | New solution on IMS HSS based Authorization for Third Party Specific User Identities | pCR | Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
merged | [WTS] [JSN] |
S3-222222 | New solution on Verification of Third Party Specific User Identities based on STIR/SHAKEN framework | pCR | Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
merged | [WTS] [JSN] |
S3-222223 | New solution on User Consent for UE Data Exposure to HPLMN in the Roaming case | pCR | Beijing Xiaomi Mobile Software | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222224 | New solution on User Consent for UE Data Exposure to VPLMN in the Roaming case | pCR | Beijing Xiaomi Mobile Software | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222225 | New solution on Modification or Revocation of User Consent for eNA in the Roaming case | pCR | Beijing Xiaomi Mobile Software | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-222226 | New solution on GMLC based authorization for Ranging/SL Positioning services | pCR | Beijing Xiaomi Mobile Software | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-222227 | New solution on NEF based authorization for Ranging/SL Positioning services | pCR | Beijing Xiaomi Mobile Software | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-222228 | 33.501: R15 Update EAP based secondary authentication by an external DN-AAA server | CR | Xiaomi Communication | 33.501 15.16.0 CR#1477 catF | 5GS_Ph1-SEC | Rel-15 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222229 | 33.501: R16 Update EAP based secondary authentication by an external DN-AAA server (mirror) | CR | Xiaomi Communication | 33.501 16.11.0 CR#1478 catA | 5GS_Ph1-SEC | Rel-16 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222230 | 33.501: R17 Update EAP based secondary authentication by an external DN-AAA server (mirror) | CR | Xiaomi Communication | 33.501 17.6.0 CR#1479 catA | 5GS_Ph1-SEC | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222231 | New KI: Home control enhancement for eNPN | pCR | Xiaomi Communication | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-222232 | KI1,New Sol Authentication mechanism for untrusted non-3GPP Access in NPN scenarios | pCR | Xiaomi Communication | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-222233 | KI1,New Sol Authentication mechanism for trusted non-3GPP Access in NPN scenarios. | pCR | Xiaomi Communication | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-222234 | KI1,New Sol Authentication for devices that do not support 5GC NAS over WLAN access in NPN scenarios | pCR | Xiaomi Communication | 33.858 0.1.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-222235 | Resolving the alignment related EN for NSACF Subscription and unsubscription procedure | CR | Xiaomi Communication | 33.501 17.6.0 CR#1480 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222236 | Update Subscription and unsubscription procedure of NSACF notification service | CR | Xiaomi Communication | 33.501 17.6.0 CR#1481 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222237 | Update KI1 providing VPLMN slice information to roaming UE | pCR | Xiaomi Communication | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-222238 | KI1, New Sol Secure mechanism for UE initiated capability indication procedure | pCR | Xiaomi Communication | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-222239 | KI1, New Sol Secure mechanism for network triggered UE capability indication procedure | pCR | Xiaomi Communication | 33.886 0.1.0 | FS_eNS_Ph3 | Rel-18 |
S3-108-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-222240 | KI1, New Sol AKMA based UE authentication for API invoker on-boarding procedure in SNA scenarios | pCR | Xiaomi Communication | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222241 | KI1,New Sol GBA based UE authentication in SNA scenarios | pCR | Xiaomi Communication | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222242 | KI1, New Sol User authorization based API invocation procedure | pCR | Xiaomi Communication | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222243 | KI1,New Sol UE credential based API invocation procedure | pCR | Xiaomi Communication | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222244 | KI1,New Sol User authorization revocation for API invocation procedure | pCR | Xiaomi Communication | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222245 | KI1,New Sol User resource authorization profile based API invocation procedure | pCR | Xiaomi Communication | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222246 | pCR to TR33.875 new solution on PRINS for roaming hubs |
pCR revised to S3-222438 |
NTT DOCOMO INC., Nokia, NokiaShanghai Bell, BSI (DE), Deutsche Telekom | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-222247 | Selective End of End Protection of HTTP Request and Response in Indirect |
pCR revised to S3-222339 |
CableLabs | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
revised | [WTS] [JSN] |
S3-222248 | pCR to TR 33.884 on new KI on authorization revocation | pCR | NTT DOCOMO | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222249 | pCR to TR 33.884 on new KI on AF originated API invocation | pCR | NTT DOCOMO | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222250 | pCR to TR 33.884 on new KI on placement of authorization function | pCR | NTT DOCOMO | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222251 | pCR to TR 33.884 new solution on UE authentication | pCR | NTT DOCOMO | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222252 | pCR to TR 33.884 new solution on non resource owner UE authorization | pCR | NTT DOCOMO | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222253 | pCR to TR 33.884 new solution on authenticating the triggering UE | pCR | NTT DOCOMO | 33.884 0.1.0 | FS_SNAAPPY | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-222254 | WID on SBA security | WID new | Nokia, Nokia Shanghai Bell | Rel-18 |
S3-108-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-222255 | Clarification to multiple registrations in different PLMNs |
CR revision of S3-221907 |
Ericsson | 33.501 17.6.0 CR#14421 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-222256 | draft LS reply on CAPIF authorization roles related to FS_SNAAPP |
LS out LS is reply to S3-221733 source LS: S6-221771 LS To: SA6 |
NTT DOCOMO INC. | Rel-18 |
S3-108-e AI: 5.11 |
noted | [WTS] [JSN] | ||
S3-222257 | Discussion paper on multiple registrations in different PLMN’s and different access types |
discussion revision of S3-221908 |
Ericsson | Rel-17 |
S3-108-e AI: 4.9 |
not pursued | [WTS] [JSN] | ||
S3-222258 | LS on Source user info in Direct Communication Request in UE-to-Network Relay |
LS out LS To: SA2,CT1 |
Qualcomm |
S3-108-e AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-222259 | Reply LS on PLMN ID used in Roaming Scenarios | LS in | C4-224444 |
S3-108-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-222260 | New group of test cases deriving from TS 33.117 for SCAS AAnF |
pCR revision of S3-221752 |
Keysight Technologies UK Ltd | 33.537 0.1.0 | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-222261 | New test case to cover the AAnF provisioning | draftCR | Keysight Technologies UK Ltd | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
noted | [WTS] [JSN] | |
S3-222262 | Support for Prose Secondary Authentication | draftCR | InterDigital, Europe, Ltd., LG Electronics, Samsung | DUMMY | Rel-18 |
S3-108-e AI: 4.8 |
approved | [WTS] [JSN] | |
S3-222263 | Alignment of NAS transport protocol for 5G-RG over Wireline |
CR revision of S3-221918 |
Ericsson | 33.501 16.11.0 CR#14431 catF | 5WWC | Rel-16 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222264 | Alignment of NAS transport protocol for 5G-RG over Wireline |
CR revision of S3-221919 |
Ericsson | 33.501 17.6.0 CR#14441 catA | 5WWC | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222265 | Living document for MnF SCAS |
draftCR revision of S3-222119 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-222266 | TS33.526 MnF threats | pCR | Huawei, Hisilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-222267 | Update clause 4.2.5, and 4.2.6 |
pCR revision of S3-222116 |
Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
approved | [WTS] [JSN] |
S3-222268 | Solution to secure direct C2 and DAA connection |
pCR revision of S3-221900 |
Lenovo | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-222269 | new draft TS 33.526 MnF SCAS | draft TS | Huawei Technologies Sweden AB | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-222270 | Living document for AAnF SCAS – draftCR to TR 33.926 |
draftCR revision of S3-222142 |
China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
available | [WTS] [JSN] | |
S3-222271 | [33.180] R14 Incorrect Reference |
CR revision of S3-221741 |
Motorola Solutions Danmark A/S | 33.18 14.10.0 CR#1901 catF | MCSec | Rel-14 |
S3-108-e AI: 4.9 |
available | [WTS] [JSN] |
S3-222272 | [33.180] R15 Incorrect Reference (mirror) |
CR revision of S3-221742 |
Motorola Solutions Danmark A/S | 33.18 15.11.0 CR#1911 catA | MCSec | Rel-15 |
S3-108-e AI: 4.9 |
available | [WTS] [JSN] |
S3-222273 | [33.180] R16 Incorrect Reference (mirror) |
CR revision of S3-221743 |
Motorola Solutions Danmark A/S | 33.18 16.9.0 CR#1921 catA | MCSec | Rel-16 |
S3-108-e AI: 4.9 |
available | [WTS] [JSN] |
S3-222274 | [33.180] R17 Incorrect Reference (mirror) |
CR revision of S3-221744 |
Motorola Solutions Danmark A/S | 33.18 17.6.0 CR#1931 catA | MCSec | Rel-17 |
S3-108-e AI: 4.9 |
available | [WTS] [JSN] |
S3-222275 | pSEPP authorization fo PLMN ID in access token for TLS |
CR revision of S3-221842 |
Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#14361 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-222276 | draft TS 33.537 | draft TS | China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
available | [WTS] [JSN] | |
S3-222277 | Updated work plan for SID eSBA security |
WI status report revision of S3-221899 |
Nokia, Nokia Shanghai Bell | FS_eSBA_SEC |
S3-108-e AI: 5.24 |
endorsed | [WTS] [JSN] | ||
S3-222278 | Editiorial updates to 33875-120 |
pCR revision of S3-221843 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222279 | Scope update |
pCR revision of S3-221844 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222280 | Scope general remark |
pCR revision of S3-221846 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222281 | Trust clause editorial update |
pCR revision of S3-221847 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222282 | KI1 EN resolution in KI1 - threat clarification |
pCR revision of S3-221848 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222283 | KI2 update with solution and conclusion on trust domain |
pCR revision of S3-221852 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222284 | KI4 EN resolution of solution 3 |
pCR revision of S3-221855 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222285 | KI4 conclusion on authorization of SCP to act on behalf of another SCP |
pCR revision of S3-221856 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222286 | KI5 Sol4 ENs resolution |
pCR revision of S3-221857 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222287 | KI5 conclusion on e2e integrity prot of HTTP msg |
pCR revision of S3-221860 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222288 | KI6 EN resolution in KI threat |
pCR revision of S3-221861 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222289 | KI6 related Sol7 update and conclusion on access token usage by NFs of an NF Set |
pCR revision of S3-221862 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222290 | KI7 evaluation of solution 9 on authorization method negotiation |
pCR revision of S3-221863 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222291 | KI7 Adding a solution on how to handle static auth in roaming with existing methods |
pCR revision of S3-221864 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222292 | KI8 update of solution 10 and evaluation |
pCR revision of S3-221868 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222293 | KI8 conclusion on deploying multiple NRFs |
pCR revision of S3-221869 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | 5G_eSBA | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222294 | Conclusion on KI9 authorization for inter-slicing access |
pCR revision of S3-221928 |
Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222295 | TR 33.875-130 eSBA Security | draft TR | Nokia | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
available | [WTS] [JSN] | |
S3-222296 | New Solution UE-to-UE security |
pCR revision of S3-221924 |
Philips International B.V. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222297 | Clarification on the certificate profile for SCP |
CR revision of S3-221986 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.31 16.10.0 CR#1331 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-222298 | Clarification on the certificate profile for SCP |
CR revision of S3-221987 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.31 17.3.0 CR#1341 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-222299 | Clarification of SNI usage for NF clients and servers |
CR revision of S3-221991 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#14471 catF | TEI17 | Rel-17 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-222300 | Clarification on OAuth2.0 in interconnect and roaming scenarios |
CR revision of S3-221993 |
Ericsson | 33.501 16.11.0 CR#14481 catF | 5G_eSBA | Rel-16 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-222301 | Clarification on OAuth2.0 in interconnect and roaming scenarios | CR | Ericsson | 33.501 17.6.0 CR#1482 catA | 5G_eSBA | Rel-17 |
S3-108-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-222302 | Certificate solution for NRF validation of NFc for access token requests |
pCR revision of S3-222000 |
Ericsson | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222303 | Combined certificate and profile solution for NRF validation of NFc for access token requests |
pCR revision of S3-222001 |
Ericsson | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222304 | LS reply to GSMA on Hosted SEPP |
LS out LS is reply to S3-221737 source LS: S3-221737 LS To: GSMA 5GMRR revision of S3-221871 |
Nokia, Nokia Shanghai Bell | 5G_eSBA |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] | ||
S3-222305 | Clean up to TR33874 |
CR revision of S3-221796 |
Huawei, Hisilicon | 33.874 18.0.0 CR#11 catF | FS_eNS2_SEC | Rel-18 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222306 | Update of KI#2 |
pCR revision of S3-222052 |
OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222307 | Proposed text for gNB-CU-UP part of draft CR to TR 33.926 |
other revision of S3-221817 |
Qualcomm Incorporated |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] | |||
S3-222308 | Proposed text for gNB-DU part of draft CR to TR 33.926 |
other revision of S3-221818 |
Qualcomm Incorporated |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] | |||
S3-222309 | Proposed text for gNB-CU test cases from TS 33.501 for TS 33.742 |
pCR revision of S3-221820 |
Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] |
S3-222310 | Proposed text for gNB-CU-CP test cases from TS 33.501 for TS 33.742 |
pCR revision of S3-221821 |
Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] |
S3-222311 | Resolve EN for solution#11 |
pCR revision of S3-221897 |
Samsung, Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222312 | Proposed text for gNB-CU-UP test cases from TS 33.501 for TS 33.742 |
pCR revision of S3-221822 |
Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] |
S3-222313 | Proposed text for gNB-DU test cases from TS 33.501 for TS 33.742 |
pCR revision of S3-221823 |
Qualcomm Incorporated | 33.742 0.1.0 | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] |
S3-222314 | Conclusion for KI#9 |
pCR revision of S3-221898 |
Samsung | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222315 | Proposed correction to Annex D on gNB network product class |
CR revision of S3-221825 |
Qualcomm Incorporated | 33.926 16.5.0 CR#601 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222316 | Proposed correction to Annex D on gNB network product class | CR | Qualcomm Incorporated | 33.926 17.4.0 CR#61 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222317 | Corrections for gNB test cases |
CR revision of S3-221826 |
Qualcomm Incorporated | 33.511 16.7.0 CR#281 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222318 | Corrections for gNB test cases | CR | Qualcomm Incorporated | 33.511 17.1.0 CR#32 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222319 | Re-using V2X unicast security for UAS |
pCR revision of S3-221829 |
Qualcomm Incorporated | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-222320 | Proposed solution for key issue #1 using SHAKEN based third-party specific user identities |
pCR revision of S3-221830 |
Qualcomm Incorporated, Huawei, Hisilicon, Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-222321 | TS 33.742 |
draft TR revision of S3-221201 |
Qualcomm Austria RFFE GmbH | SCAS_5G_split_gNB | Rel-18 |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] | |
S3-222322 | Draft CR: Introducing split gNBs into TR 33.926 | draftCR | Qualcomm Incorporated | SCAS_5G_split_gNB | Rel-17 |
S3-108-e AI: 4.6 |
approved | [WTS] [JSN] | |
S3-222323 | Draft TR 33.891 |
draft TR revision of S3-221607 revised to S3-223129 |
Qualcomm Incorporated | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
available | [WTS] [JSN] | |
S3-222324 | Clarification on Authentication for UE behind 5G-RG and FN-RG |
CR revision of S3-222025 |
CableLabs | 33.501 17.6.0 CR#14591 catF | NSWO_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222325 | TR 33.883 for 5MBS security | draft TR | Huawei, HiSilicon | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
approved | [WTS] [JSN] | |
S3-222326 | Authentication of NF Producer in Indirect Communication |
pCR revision of S3-221904 |
CableLabs, Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222327 | Resolving EN in solution #6 |
pCR revision of S3-221933 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222328 | New solution for the authorization of the delegated subscribe |
pCR revision of S3-221934 |
Huawei, Hisilicon | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222329 | TS33.526 MnF threats |
pCR revision of S3-221937 |
Huawei, Hisilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
approved | [WTS] [JSN] |
S3-222330 | clarification on IP_FWD_DISABLING-R16 |
CR revision of S3-221942 |
Huawei,HiSilicon | 33.117 16.7.0 CR#731 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222331 | clarification on IP_FWD_DISABLING-R17 |
CR revision of S3-221943 |
Huawei,HiSilicon | 33.117 17.0.0 CR#741 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222332 | modification on EXCLUSIVE_EXECUTE_RIGHTS-R16 |
CR revision of S3-221944 |
Huawei,HiSilicon | 33.117 16.7.0 CR#751 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222333 | modification on EXCLUSIVE_EXECUTE_RIGHTS-R17 |
CR revision of S3-221945 |
Huawei,HiSilicon | 33.117 17.0.0 CR#761 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222334 | modification on Handling of ICMP-R16 |
CR revision of S3-221946 |
Huawei,HiSilicon | 33.117 16.7.0 CR#771 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222335 | modification on Handling of ICMP-R17 |
CR revision of S3-221947 |
Huawei,HiSilicon | 33.117 17.0.0 CR#781 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222336 | modification on IP_MULTICAST_HANDLING-R16 |
CR revision of S3-221948 |
Huawei,HiSilicon | 33.117 16.7.0 CR#791 catF | SCAS_5G | Rel-16 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222337 | modification on IP_MULTICAST_HANDLING-R17 |
CR revision of S3-221949 |
Huawei,HiSilicon | 33.117 17.0.0 CR#801 catA | SCAS_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222338 | New KI on security aspects of IMS DC |
pCR revision of S3-221954 |
Huawei, HiSilicon | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-222339 | Selective End of End Protection of HTTP Request and Response in Indirect |
pCR revision of S3-222247 |
CableLabs | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222340 | Draft TR 33.890 020 | draft TR | Huawei, HiSilicon | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
available | [WTS] [JSN] | |
S3-222341 | New solution: End-to-end security establishment for Layer-2 UE-to-UE relay |
pCR revision of S3-222189 |
OPPO | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222342 | TR 33.896v020 | draft TR | Huawei, HiSilicon | FS_UC3S, FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.23 |
available | [WTS] [JSN] | |
S3-222343 | New Ki related to authorization of exposed PIN capabilites |
pCR revision of S3-221805 |
Nokia, Nokia Shanghai Bell | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-222344 | TR 33.740 v0.2.0 Study on security aspects of Proximity Based Services (ProSe) in 5G System (5GS) phase 2 | draft TR | CATT | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
available | [WTS] [JSN] | |
S3-222345 | CR to TS33.503 Update Figure 6.3.3.3.2-1 | CR | CATT | 33.503 17.0.1 CR#221 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
withdrawn | [WTS] [JSN] |
S3-222346 | Update IPSec reference from obsolete RFC 7296 to RFC 8247 |
CR revision of S3-222047 |
Intel | 33.21 17.0.0 CR#731 catF | eCryptPr | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222347 | Update IPSec reference from obsolete RFC 7296 to RFC 8247 |
CR revision of S3-222048 |
Intel | 33.21 17.0.0 CR#741 catF | eCryptPr | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222348 | 33.893: Add Third Party UE in KI#2 |
pCR revision of S3-222209 |
Xiaomi Technology | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-222349 | 33.893: New Key Issue on Security for PC5 Communication |
pCR revision of S3-222207 |
Xiaomi, Huawei, Hisilicon, ChinaTelecom, Interdigital | 33.893 0.1.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-222350 | 33.896: Solution on Obtaining User Consent in Non-mobility Case for KI#2 |
pCR revision of S3-222214 |
Xiaomi Technology | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-222351 | 33.896: Solution on Obtaining User Consent Revocation for KI#2 |
pCR revision of S3-222215 |
Xiaomi Technology | 33.896 0.1.0 | FS_UC3S_Ph2 | Rel-18 |
S3-108-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-222352 | Updates to U2N Relay Discovery Security Procedure |
CR revision of S3-222198 |
Xiaomi Technology | 33.503 17.0.1 CR#341 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222353 | Corrections in TS 33.503 |
CR revision of S3-222205 |
Xiaomi Technology | 33.503 17.0.1 CR#411 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222354 | New solution for PC5 link security when UE-to-UE relay is in coverage |
pCR revision of S3-221912 |
Ericsson | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222355 | New solution for PC5 link security when UE-to-UE relay is out of coverage |
pCR revision of S3-221913 |
Ericsson | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222356 | Implementation correction of S3-221294 |
CR revision of S3-221749 |
Ericsson | 33.503 17.0.1 CR#31 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222357 | Correction to authorization based on RSC |
CR revision of S3-221909 |
Ericsson | 33.503 17.0.1 CR#101 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222358 | Clarifications of general description to Restricted 5G ProSe Direct Discovery |
CR revision of S3-221910 |
Ericsson | 33.503 17.0.1 CR#111 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222359 | Rename 5GPRUK ID and 5GPRUK in CP based solution |
CR revision of S3-221911 |
Ericsson | 33.503 17.0.1 CR#121 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222360 | LS reply on East/West Bound Interface for Telco Edge consideration |
LS out LS is reply to S3-221723 LS To: GSMA revision of S3-221790 |
Nokia, Nokia Shanghai Bell |
S3-108-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-222361 | Key Issue: UAV Privacy over PC5 link |
pCR revision of S3-221756 |
InterDigital, Europe, Ltd. | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-222362 | Solution on Direct C2 Security |
pCR revision of S3-221757 |
InterDigital, Europe, Ltd. | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-222363 | LS Reply on Reply LS on 5G ProSe security open items |
LS out LS is reply to S3-221732,S3-221735 LS To: SA, SA2 revision of S3-221758 revised to S3-222434 |
InterDigital, Europe, Ltd. | Rel-17 |
S3-108-e AI: 4.8 |
revised | [WTS] [JSN] | ||
S3-222364 | New solution: Restricted Peer UE IP Discovery with Layer-3 UE-to-UE Relay |
pCR revision of S3-221764 |
InterDigital, Europe, Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222365 | New solution: Privacy for Layer-3 UE-to-UE Relay based on IP routing |
pCR revision of S3-221765 |
InterDigital, Europe, Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222366 | New WID: 5G ProSe Secondary Authentication |
WID new revision of S3-221762 |
InterDigital, Europe, Ltd., LG Electronics, Samsung, China Telecom, Philips | Rel-18 |
S3-108-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-222367 | Add terms and abbreviations to TR 33.882 |
pCR revision of S3-221892 |
ZTE Corporation | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-222368 | Add ApplicationKey_ AnonUser_Get into table 7.1.1-1 |
CR revision of S3-221882 |
ZTE Corporation | 33.535 17.6.0 CR#1321 catF | AKMA | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222369 | Adding AAnF critical assets to TS 33.926 |
other revision of S3-221876 |
ZTE Corporation | SCAS_5G_AAnF | Rel-18 |
S3-108-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-222370 | New solution on Network-assisted Security Establishment Procedure for 5G ProSe Layer-3 UE-to-UE Relay | pCR | Beijing Xiaomi Mobile Software | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
withdrawn | [WTS] [JSN] |
S3-222371 | New solution on Non-network-assisted Security Establishment Procedure for 5G ProSe Layer-3 UE-to-UE Relay |
pCR revision of S3-222217 |
Beijing Xiaomi Mobile Software | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222372 | New solution on Restricted 5G ProSe UE-to-UE Relay Discovery Model A |
pCR revision of S3-222218 |
Beijing Xiaomi Mobile Software | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222373 | New solution on Restricted 5G ProSe UE-to-UE Relay Discovery Model B |
pCR revision of S3-222219 |
Beijing Xiaomi Mobile Software | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222374 | Add threat and requirement to key issue #1 |
pCR revision of S3-222064 |
Huawei, HiSilicon, Philips, Interdigital | 33.882 0.1.0 | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-222375 | Resolution of the issue of authentication mechanism selection |
CR revision of S3-222074 |
Huawei, HiSilicon, Interdigital, Nokia, Nokia Shanghai Bell | 33.503 17.0.1 CR#231 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222376 | Clarification on 5G ProSe Remote UE specific authentication mechanism |
CR revision of S3-222076 |
Huawei, HiSilicon | 33.503 17.0.1 CR#251 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222377 | Remote UE Report when security procedure over Control Plane is performed |
CR revision of S3-222077 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.503 17.0.1 CR#261 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222378 | New Key Issue on Security and privacy of path switching between two indirect network communication paths for UE-to-Network Relaying |
pCR revision of S3-222081 |
Huawei, HiSilicon | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-222379 | New Key Issue on Security and privacy of path switch between L2 U2NW and direct connections |
pCR revision of S3-222082 |
Huawei, HiSilicon | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-222380 | New Key Issue on Security and privacy of multi-path transmission for UE-to-Network Relay |
pCR revision of S3-222083 |
Huawei, HiSilicon | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-222381 | supporting UP IP at eNB |
draftCR revision of S3-222098 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-222382 | UP IP policy selection-R18 |
draftCR revision of S3-222099 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-222383 | locally UP IP supporting at eNB |
draftCR revision of S3-222100 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-222384 | draft CR to 33.926 on locally UP IP supporting at eNB |
draftCR revision of S3-222102 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-222385 | draft CR to 33.926 on UP IP policy selection at eNB |
draftCR revision of S3-222103 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-222386 | Living document to TR 33.926 for SCAS 5G Ph2 |
draftCR revision of S3-222104 |
Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-108-e AI: 4.4 |
available | [WTS] [JSN] | |
S3-222387 | Update clause 4.2.5, and 4.2.6 | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-108-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-222388 | clarification on the internal authentication and an external authentication |
CR revision of S3-222123 |
Huawei, HiSilicon | 33.501 17.6.0 CR#14691 catF | eNPN | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222389 | Living document to TS 33.216 | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-16 |
S3-108-e AI: 4.4 |
available | [WTS] [JSN] | |
S3-222390 | Living document to TS 33.117 | draftCR | Huawei, HiSilicon | SCAS_5G_Ph2 | Rel-17 |
S3-108-e AI: 4.4 |
available | [WTS] [JSN] | |
S3-222391 | Reply LS on the impact of MSK update on MBS multicast session update procedure |
LS out LS is reply to S3-221728 LS To: SA2, CT1, SA4 |
Huawei, HiSilicon | Rel-17 |
S3-108-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-222392 | Alignment with RAN3 LS for EN-DC for UPIP | CR | Huawei, HiSilicon, Ericsson | 33.401 17.2.0 CR#713 catF | UPIP_SEC_LTE | Rel-17 |
S3-108-e AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-222393 | Reply LS on UEs LTE UPIP capability for EN-DC |
LS out LS To: RAN3 |
Huawei, HiSilicon, Ericsson | Rel-17 |
S3-108-e AI: 3 |
withdrawn | [WTS] [JSN] | ||
S3-222394 | Address EN for UC3S | CR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#1483 catF | UC3S_SEC | Rel-17 |
S3-108-e AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-222395 | EAP_AKA prime based authentication for AUN3 devices |
pCR revision of S3-221768 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.1.1 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-108-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-222396 | Correction in AUSF api related to NSWO |
CR revision of S3-221777 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.501 17.6.0 CR#14281 catF | NSWO_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222397 | LS reply on 5G NSWO roaming aspects |
LS out LS is reply to S3-221731 LS To: SA2 revision of S3-221778 |
Nokia, Nokia Shanghai Bell | NSWO_5G | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] | |
S3-222398 | Correction of Transport security protection for MSGin5G interfaces |
CR revision of S3-222133 |
China Mobile | 33.501 17.6.0 CR#14711 catF | 5GMSG | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222399 | Draft 33.887 Study on Security aspects for 5WWC Phase 2 | draft TR | Nokia Solutions & Networks (I) | FS_5WWC_Ph2_Sec | Rel-18 |
S3-108-e AI: 5.13 |
available | [WTS] [JSN] | |
S3-222400 | CR to TS33.503 Remove secondary authentication related content |
CR revision of S3-222029 |
CATT | 33.503 17.0.1 CR#201 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222401 | New solution: How the Originating IMS network signs the 3rd party IDs and terminating IMS network verifies the 3rd party IDs |
pCR revision of S3-222022 |
Ericsson, Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-222402 | Solution for PC5 link security establishment for U2U Relay |
pCR revision of S3-221921 |
China Telecom Corporation Ltd. | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-108-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-222403 | Correction figure in ProSe UE-to-Network Relay security procedure over Control Plane in TS33.503 |
CR revision of S3-221981 |
China Telecom Corporation Ltd. | 33.503 17.0.1 CR#151 catF | 5G_ProSe | Rel-17 |
S3-108-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-222404 | New Key issue on the privacy of information handled by the RAN AI/ML framework |
pCR revision of S3-222012 |
Ericsson, Intel | 33.877 0.1.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-222405 | Draft TR 33.877 v0.2.0 Study on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the NG-RAN | draft TR | Ericsson España S.A. | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-108-e AI: 5.14 |
available | [WTS] [JSN] | |
S3-222406 | Draft TR 33.893 v0.2.0 Study on Security Aspects of Ranging Based Services and Sidelink Positioning | draft TR | Xiaomi Technology | FS_Ranging_SL_Sec | Rel-18 |
S3-108-e AI: 5.19 |
available | [WTS] [JSN] | |
S3-222407 | Adding overview of SECAM for 3GPP virtualized networ products into clause 4 in TR 33.936 |
pCR revision of S3-222144 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222408 | Adding Scope of SECAM for 3GPP virtualized network products of type 1 into clause 4 in TR 33.936 |
pCR revision of S3-222145 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222409 | Adding Scope of SECAM evaluation for type 1 of 3GPP virtualized network products into clause 4 in TR 33.936 |
pCR revision of S3-222148 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222410 | Adding Scope of SECAM accreditation for type 1 of 3GPP virtualized network products into clause 4 in TR 33.936 |
pCR revision of S3-222151 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222411 | Adding contents of chapters 4.5 about type 1 of 3GPP virtualized network product in TR 33.936 |
pCR revision of S3-222154 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222412 | Adding contents of chapters 4.7 for type 1 of 3GPP virtualized network product in TR 33.936 |
pCR revision of S3-222160 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222413 | Adding contents of chapters 4.8 for type 1 of 3GPP virtualized network product in TR 33.936 |
pCR revision of S3-222163 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222414 | Adding content to clause 5.1 in TR 33.936 |
pCR revision of S3-222172 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222415 | Adding description about general content of SCAS document and ToE to clause 5.2 in TR 33.936 |
pCR revision of S3-222173 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222416 | Adding description about SPD to clause 5.2 in TR33.936 |
pCR revision of S3-222174 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222417 | Adding description about methodology of security requirements to clause 5.2 in TR 33.936 |
pCR revision of S3-222175 |
China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222418 | Proposal to add overview in clause 4 Generic Virtulizated Network Product (GVNP) class for type 1 in TR 33.927 |
pCR revision of S3-222178 |
China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222419 | Proposal to add introduction in clause 4.3 Generic virtualized network product model for type 1 in TR33.927 |
pCR revision of S3-222182 |
China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222420 | Proposal to add GVNP model of type 1 in TR 33.927 |
pCR revision of S3-222185 |
China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-222421 | TR 33.936 | draft TR | China Mobile | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
available | [WTS] [JSN] | |
S3-222422 | TR 33.927 | draft TR | China Mobile | VNP_SECAM_SCAS | Rel-18 |
S3-108-e AI: 4.2 |
available | [WTS] [JSN] | |
S3-222423 | TR 33.894 for FS_ZTS | draft TR | Lenovo | FS_ZTS | Rel-18 |
S3-108-e AI: 5.19 |
available | [WTS] [JSN] | |
S3-222424 | Draft TR 33.892 v0.2.0 | draft TR | Lenovo | FS_USIA | Rel-18 |
S3-108-e AI: 5.18 |
available | [WTS] [JSN] | |
S3-222425 | Solution on enhancing the URSP rule with certificate fingerprint |
pCR revision of S3-221901 |
Lenovo | 33.892 0.1.0 | FS_USIA | Rel-18 |
S3-108-e AI: 5.18 |
approved | [WTS] [JSN] |
S3-222426 | LS reply on User plane security |
LS out LS is reply to S3-222721 LS To: GSMA revision of S3-222131 |
China Mobile | Rel-17 |
S3-108-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-222427 | Key issue for privacy protection for unicast messages over PC5 |
pCR revision of S3-222129 |
China Mobile | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-222428 | Address EN in Overview and editorial modification |
pCR revision of S3-222130 |
China Mobile | 33.891 0.1.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-108-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-222429 | TR 33.882 v0.2.0 Study on personal IoT networks security aspects | draft TR | vivo Mobile Communication (S) | FS_PIN_Sec | Rel-18 |
S3-108-e AI: 5.1 |
available | [WTS] [JSN] | |
S3-222430 | withdrawn | CR | Huawei, HiSilicon | 33.501 17.6.0 CR#14681 catF | UC3S_SEC | Rel-17 |
S3-108-e AI: 4.9 |
withdrawn | [WTS] [JSN] |
S3-222431 | Alignment with RAN3 LS for EN-DC for UPIP |
CR revision of S3-222062 |
Huawei, HiSilicon, Ericsson | 33.401 17.2.0 CR#7111 catF | UPIP_SEC_LTE | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222432 | Reply LS on UE’s LTE UPIP capability for EN-DC |
LS out LS is reply to S3 221724 LS To: RAN3 revision of S3-222063 revised to S3-222435 |
Huawei, HiSilicon, Ericsson | Rel-17 |
S3-108-e AI: 4.9 |
revised | [WTS] [JSN] | ||
S3-222433 | Address EN for UC3S |
CR revision of S3-222088 |
Huawei, HiSilicon,Nokia, Nokia Shanghai Bell | 33.501 17.6.0 CR#14681 catF | UC3S_SEC | Rel-17 |
S3-108-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-222434 | LS Reply on Reply LS on 5G ProSe security open items |
LS out LS is reply to S3-221732,S3-221735 LS To: SA, SA2 revision of S3-222363 |
InterDigital, Europe, Ltd. | Rel-17 |
S3-108-e AI: 4.8 |
approved | [WTS] [JSN] | ||
S3-222435 | Reply LS on UE’s LTE UPIP capability for EN-DC |
LS out LS is reply to S3 221724 LS To: RAN3 revision of S3-222432 |
Huawei, HiSilicon, Ericsson | Rel-17 |
S3-108-e AI: 4.9 |
approved | [WTS] [JSN] | ||
S3-222436 | Update to and split of KI#10 to clarify the scenarios |
pCR revision of S3-221978 |
BSI (DE),Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222437 | Solution for KI#10 (hosted SEPP) |
pCR revision of S3-221980 |
BSI (DE),Nokia, Nokia Shanghai Bell | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222438 | pCR to TR33.875 new solution on PRINS for roaming hubs |
pCR revision of S3-222246 |
NTT DOCOMO INC., Nokia, NokiaShanghai Bell, BSI (DE), Deutsche Telekom | 33.875 1.2.0 | FS_eSBA_SEC | Rel-18 |
S3-108-e AI: 5.24 |
approved | [WTS] [JSN] |
S3-222439 | New SID on Security Aspects of Satellite Access |
SID new revision of S3-222197 |
Xiaomi, China Mobile, China Telecom, Qualcomm, InterDitigal, ZTE, Nokia, Nokia Shanghai Bell, Thales | Rel-18 |
S3-108-e AI: 6 |
agreed | [WTS] [JSN] |
730 documents (1.1082401275635 seconds)