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-241700 | Agenda | agenda | SA WG3 Chair |
S3-116 AI: 1 |
approved | [WTS] [JSN] | |||
S3-241701 | Report from SA3#115AdHoc-e | report | MCC |
S3-116 AI: 2 |
approved | [WTS] [JSN] | |||
S3-241702 | Report from SA3#115 | report | MCC |
S3-116 AI: 2 |
approved | [WTS] [JSN] | |||
S3-241703 | Process for SA3#116 | other | SA WG3 Chair |
S3-116 AI: 1 |
noted | [WTS] [JSN] | |||
S3-241704 | Detail agenda planning for SA3#116 |
other revised to S3-242365 |
SA WG3 Chair |
S3-116 AI: 1 |
revised | [WTS] [JSN] | |||
S3-241705 | SA3 meeting calendar | other | SA WG3 Chair |
S3-116 AI: 8 |
noted | [WTS] [JSN] | |||
S3-241706 | Report to SA3 from SA | report | SA WG3 Chair |
S3-116 AI: 2 |
noted | [WTS] [JSN] | |||
S3-241707 | Modernization of the Integrity & Encryption Algorithms between UE and P-CSFC | CR | Deutsche Telekom AG | 33.203 18.0.0 CR#280 catF | TEI19 | Rel-19 |
S3-116 AI: 4.8 |
withdrawn | [WTS] [JSN] |
S3-241708 | Solution to prevent bidding down to GERAN/UTRAN by restricting inter RAT handover |
pCR revised to S3-242485 |
Ericsson | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-241709 | Solution to prevent bidding down by restricting UE access to GERAN/UTRAN in its location |
pCR revised to S3-242487 |
Ericsson | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-241710 | Solution to authenticate and secure backhaul of 5G NR Femto |
pCR revised to S3-242580 |
Ericsson | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
revised | [WTS] [JSN] |
S3-241711 | Architecture and security assumptions of TR 33.700-29 |
pCR revised to S3-242542 |
Ericsson | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241712 | Prevent acquiring the list of SUPI stored in the database of 5GC UDM | discussion | ISSDU, III, NYCU | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] | ||
S3-241713 | Resolve EN in Use case 1 |
pCR revised to S3-242418 |
Lenovo, Motorola Mobility, Johns Hopkins University APL | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241714 | Resolve EN in Use case 2 | pCR | Lenovo, Motorola Mobility, Johns Hopkins University APL | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
merged | [WTS] [JSN] |
S3-241715 | Solution to KI#1 Network assisted data collection |
pCR revised to S3-242424 |
Lenovo, Motorola Mobility | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241716 | Solution to KI#1_Direct data collection |
pCR revised to S3-242425 |
Lenovo, Motorola Mobility | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241717 | Update to KI#2 | pCR | Lenovo, Motorola Mobility | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
merged | [WTS] [JSN] |
S3-241718 | Initial Conclusion to KI#1 | pCR | Lenovo, Motorola Mobility | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
noted | [WTS] [JSN] |
S3-241719 | Threat scenarios to be addressed for KI#3 | discussion | Lenovo | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] | |
S3-241720 | Updates to Solution 11 |
pCR revised to S3-242635 |
Lenovo | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241721 | Updates to Solution #10 |
pCR revised to S3-242598 |
Lenovo | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-241722 | User authentication and authorization of human user |
pCR revised to S3-242495 |
Lenovo | 33.700-32 0.1.0 | FS_Non3GPPMob_Sec, FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241723 | UPU Header Security | CR | Lenovo | 33.501 18.5.0 CR#1978 catF | 5GS_Ph1-SEC | Rel-18 |
S3-116 AI: 4.1.15 |
merged | [WTS] [JSN] |
S3-241724 | LS on identifiers of 5G ProSe end UEs for 5G ProSe UE-to-UE relay discovery |
LS in LS reply in S3-242404, S3-242404 |
C1-241787 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241725 | Reply LS on lack of GPRS IOV randomisation | LS in | C1-241807 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241726 | Reply LS on Mitigation of Downgrade attacks |
LS in LS reply in S3-242367, S3-242367 |
C1-241848 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241727 | LS on differentiating security materials used for PC5 direct discovery for 5G ProSe UE-to-network relay |
LS in LS reply in S3-242366, S3-242366 |
C1-242665 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241728 | LS on ECS Configuration Information |
LS in LS reply in S3-242620, S3-242173, S3-242620 |
C1-242674 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241729 | LS on the condition for provisioning of the ePDG identity to the UE |
LS in LS reply in S3-242369, S3-242369 |
C1-242936 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241730 | Reply LS on Authorization of NF service consumer for data collection via DCCF | LS in | C4-240623 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241731 | Reply LS on PRINS security profiles | LS in | C4-240796 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241732 | Reply LS on in-path and in-query parameters | LS in | C4-240910 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241733 | LS on Resource content filters |
LS in LS reply in S3-242370 |
C4-241339 |
S3-116 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-241734 | Reply LS on nested JSON structures | LS in | C4-241343 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241735 | Reply LS on the Modified PRINS solution | LS in | C4-241522 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241736 | LS on clarification on home network triggered re-authentication |
LS in LS reply in S3-241895, S3-242371 |
C4-235577 |
S3-116 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-241737 | LS on support of SSIM on eUICC |
LS in LS reply in S3-242373, S3-242373 |
Trusted Connectivity Alliance |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241738 | ETSI ISG MEC publication of MEC Phase 3 deliverables | LS in | ETSI MEC |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241739 | ETSI ISG MEC publication of report on MEC security^^^^ | LS in | ETSI MEC |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241740 | LS on GSMA OPG PRDs publication | LS in | GSMA |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241741 | LS on clarifications on consent management |
LS in LS reply in S3-242374, S3-242374 |
GSMA |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241742 | Reply LS on user consent for trace reporting | LS in | R3-241115 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241743 | Reply-LS on Prohibition of GEA1 & GEA2 Support in all releases | LS in | R5-240020 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241744 | Reply LS to GSMA on Monitoring of Encrypted 5GS Signalling Traffic | LS in | S2-2403027 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241745 | LS Reply on Clarification related to the information exposed by the 5GC to NSCE server. | LS in | S2-2403703 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241746 | LS on the use of TLS with QUIC in ATSSS context |
LS in LS reply in S3-241988, S3-242048 |
S2-2405459 |
S3-116 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-241747 | Reply LS on data plane control by roaming hubs | LS in | S2-2405815 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241748 | LS on limited MSISDN exposure |
LS in LS reply in S3-242375, S3-241844, S3-242204, S3-242315, S3-242375 |
S2-2405824 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241749 | Reply LS on security of IP transport over satellite transport links (S3-240950 / S2-240390) | LS in | S2-2405836 |
S3-116 AI: 5.7 |
noted | [WTS] [JSN] | |||
S3-241750 | Clarification related to reliable location |
LS in LS reply in S3-242379, S3-242379 |
S2-2309698 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241751 | LI considerations for TR 33.757 (""Study on security for PLMN hosting a NPN"") |
LS in LS reply in S3-242376, S3-241778, S3-241899, S3-242192, S3-242254, S3-242376 |
s3i240294 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241752 | LI considerations for UE-Satellite-UE communications | LS in | s3i240295 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241753 | LS on LI considerations for Store and Forward NT operation | LS in | s3i240296 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241754 | LS Reply to SA4 on 3GPP work on energy efficiency | LS in | S5-241924 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241755 | Reply LS on the user consent for trace reporting | LS in | S5-242221 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241756 | Reply LS on service authorization for/to partner MC system | LS in | S6-240404 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241757 | Reply LS on evaluating security aspects for MC services over MC gateway UE | LS in | S6-241369 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241758 | LS on the proposal for a new work item: Security considerations for interconnection of computing power centers^^^^ | LS in | ITU-T |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241759 | LS/r on the proposal for new work item: Guidelines for increasing security of the AKA protocols in IMT-2020 and beyond (reply to 3GPP TSG SA3 S3-235006) | LS in | ITU-T |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241760 | Reply to LS on potential collaboration between 3GPP SA5 and ETSI TC SAI | LS in | SP-240485 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241761 | LS on removing Ranging/SL Positioning service exposure to Client UE through 5GC | LS in | SP-240497 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241762 | LS on the Modified PRINS solution | LS in | SP-240503 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241763 | Quantum Safe Cryptographic Protocol Inventory |
LS in LS To: S3-242377 LS reply in S3-241946, S3-242221, S3-242377 |
ETSI TC CYBER |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241764 | CVD-2023-0069 - 5G Core Network Attacks |
LS in LS reply in S3-242453, S3-242453 |
GSMA |
S3-116 AI: 7 |
replied to | [WTS] [JSN] | |||
S3-241765 | LS regarding the publication of the Post Quantum Cryptography – Guidelines for Telecom Use Cases document in Feb 24 | LS in | GSMA |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241766 | LS on 3GPP studies for PQC Migration |
LS in LS reply in S3-242378, S3-242378 |
GSMA |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241767 | TCG progress - report from TCG rapporteur | other | InterDigital Belgium. LLC |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241768 | Living document for CryptoSP: draftCR to TS 33.210, Updates to cryprographic profiles |
draftCR revised to S3-242664 |
Ericsson | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
revised | [WTS] [JSN] | |
S3-241769 | Living document for CryptoSP: draftCR to TS 33.501, Updates to cryptographic profiles |
draftCR revised to S3-242665 |
Ericsson | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
revised | [WTS] [JSN] | |
S3-241770 | Living document for CryptoSP: draftCR to TS 33.310, Updates to cryptographic profiles | draftCR | Ericsson | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | |
S3-241771 | New SID on Security Aspects of Roaming Traffic Offload via Home-Session Breakout | SID new | OTD_US | Rel-19 |
S3-116 AI: 6 |
noted | [WTS] [JSN] | ||
S3-241772 | Modernization of the Integrity Algorithms between UE and P-CSCF | CR | Deutsche Telekom AG | 33.203 18.0.0 CR#281 catF | TEI19 | Rel-19 |
S3-116 AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-241773 | LS on security handling for inter-CU LTM in non-DC cases |
LS in LS reply in S3-242400, S3-241886, S3-241898, S3-242044, S3-242080, S3-242101, S3-242105, S3-242400 |
R2-2404037 |
S3-116 AI: 3 |
replied to | [WTS] [JSN] | |||
S3-241774 | New Solution to KI#2 Authorization of VFL participant involving NWDAF and AF | pCR | Ericsson GmbH, Eurolab | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
withdrawn | [WTS] [JSN] |
S3-241775 | Addition of security threat to KI#1 | pCR | L.M. Ericsson Limited | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
withdrawn | [WTS] [JSN] |
S3-241776 | Solution reusing existing interfaces and security mechanisms for energy-related information | pCR | L.M. Ericsson Limited | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
withdrawn | [WTS] [JSN] |
S3-241777 | Added threat in testcase | CR | Keysight Technologies UK Ltd | 33.520 18.0.0 CR#1 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 4.3 |
merged | [WTS] [JSN] |
S3-241778 | draft Reply LS on LI considerations for Study on security for PLMN hosting a NPN |
LS out LS is reply to S3-241751 source LS: s3i240294 LS To: SA3-LI |
Johns Hopkins University APL | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |
S3-241779 | Pseudo-CR on TR 33.776 Solution #2 to remove Editor's Notes |
pCR revised to S3-242446 |
Cisco Systems, US National Security Agency | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
revised | [WTS] [JSN] |
S3-241780 | Updates to ESP-TTLS type | other | Nokia, Nokia Shanghai Bell | CryptoSP |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | ||
S3-241781 | Editorial Updates on TS 33.501 |
other revised to S3-242634 |
Nokia, Nokia Shanghai Bell | CryptoSP |
S3-116 AI: 4.8 |
revised | [WTS] [JSN] | ||
S3-241782 | Updates to TLS profiles on TS33210 |
other revised to S3-242413 |
Nokia, Nokia Shanghai Bell | CryptoSP |
S3-116 AI: 4.8 |
revised | [WTS] [JSN] | ||
S3-241783 | Add specific UDR SCAS test cases for TS 33.530 | pCR | BSI (DE) | 33.530 0.1.0 | SCAS_5G_UDR | Rel-19 |
S3-116 AI: 4.2 |
noted | [WTS] [JSN] |
S3-241784 | Addition of UDR security requirements | CR | BSI (DE) | 33.501 18.5.0 CR#1979 catB | SCAS_5G_UDR | Rel-19 |
S3-116 AI: 4.2 |
not pursued | [WTS] [JSN] |
S3-241785 | Eliminate the possibility of implementing unverified security protocols for the UDR-UDM interface. | CR | BSI (DE) | 33.501 18.5.0 CR#1980 catF | SCAS_5G_UDR | Rel-19 |
S3-116 AI: 4.2 |
not pursued | [WTS] [JSN] |
S3-241786 | Add an appendix of threats to the UDR | CR | BSI (DE) | 33.926 19.0.0 CR#94 catB | SCAS_5G_UDR | Rel-19 |
S3-116 AI: 4.2 |
not pursued | [WTS] [JSN] |
S3-241787 | Conclusion for KI#1 in TR 33.701 | pCR | Ericsson | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] |
S3-241788 | Added threat in testcase | CR | Keysight Technologies UK Ltd | 33.512 18.1.0 CR#43 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 4.3 |
not pursued | [WTS] [JSN] |
S3-241789 | Conclusion for TR 33.700-41 |
pCR revised to S3-242450 |
KDDI Corporation | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
revised | [WTS] [JSN] |
S3-241790 | Discussion paper on AEAD | discussion | KDDI Corporation |
S3-116 AI: 6 |
noted | [WTS] [JSN] | |||
S3-241791 | New WID on Security for mobility over non-3GPP access to avoid full primary authentication |
WID new revised to S3-242659 |
Nokia | Rel-19 |
S3-116 AI: 6 |
revised | [WTS] [JSN] | ||
S3-241792 | New use case for security evaluation and monitoring: Common Vulnerabilities and Exposures (CVE) attacks | pCR | ISSDU, NYCU, III | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
noted | [WTS] [JSN] |
S3-241793 | Add the N1 interface to the scope of fuzz testing for the AMF | CR | BSI (DE) | 33.512 18.1.0 CR#44 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-241794 | Add an OAuth2.0 test case to check for the absence of an access token | CR | BSI (DE) | 33.117 18.3.0 CR#190 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
S3-241795 | Remove unnecessary complexity from UDM test case TC_AUTH_STATUS_STORE_UDM | CR | BSI (DE) | 33.514 18.2.0 CR#14 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
S3-241796 | Add UDM SCAS test case for checking the authentication verification of a synchronization failure message | CR | BSI (DE) | 33.514 18.2.0 CR#15 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 4.1.1 |
withdrawn | [WTS] [JSN] |
S3-241797 | Add parameters to NRF discovery authorization | CR | BSI (DE) | 33.518 18.0.0 CR#7 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 7 |
not pursued | [WTS] [JSN] |
S3-241798 | Clarification of security requirement on NF Discovery response | CR | BSI (DE) | 33.501 18.5.0 CR#1981 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 7 |
merged | [WTS] [JSN] |
S3-241799 | Solution on certificate revocation |
pCR revised to S3-242441 |
Johns Hopkins University APL | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
revised | [WTS] [JSN] |
S3-241800 | A new solution for AIML Data Privacy Protection | pCR | InterDigital Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
noted | [WTS] [JSN] |
S3-241801 | LS on vulnerability due to null ciphering request by network |
LS out LS To: CT1, RAN2 revised to S3-242512 |
Google Inc., Deutsche Telekom | Rel-18 |
S3-116 AI: 3 |
revised | [WTS] [JSN] | ||
S3-241802 | generic conclusion for KI1 and KI3 | pCR | Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
merged | [WTS] [JSN] |
S3-241803 | conclusion for KI1 and KI3 with only Fast BSS |
pCR revised to S3-242560 |
Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-241804 | solution for AUN3 device | pCR | Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-241805 | conclusion for KI2 | pCR | Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
noted | [WTS] [JSN] |
S3-241806 | solution 8 correction | pCR | Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-241807 | Editorial cleanup of the TR | pCR | Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-241808 | user profile exposure privacy issue |
pCR revised to S3-242507 |
Nokia | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241809 | User privacy during the connection with 5GC |
pCR revised to S3-242508 |
Nokia | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241810 | User authentication |
pCR revised to S3-242496 |
Nokia | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241811 | Solutionf for VLF member authorization |
pCR revised to S3-242586 |
Nokia | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-241812 | Reply LS on clarification on home network triggered re-authentication |
LS out LS is reply to S3-241736 source LS: C4-235577 LS To: CT4 |
Nokia | TEI18 | Rel-18 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |
S3-241813 | Reply LS on Clarification related to reliable location |
LS out LS is reply to S3-241750 source LS: S2-2309698 LS To: SA2 |
Nokia | TEI17 | Rel-17 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |
S3-241814 | LS reply on the condition for provisioning of the ePDG identity to the UE |
LS out LS is reply to S3-241729 source LS: C1-242936 LS To: CT1 |
Nokia | TEI18 | Rel-18 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |
S3-241815 | ePDG procedure clarification | CR | Nokia, Nokia Shanghai Bell | 33.402 18.0.0 CR#149 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241816 | Clarification in TNGF and N3IWF procedures |
CR revised to S3-242381 |
Nokia | 33.501 17.13.0 CR#1982 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241817 | Clarification in TNGF and N3IWF procedures |
CR revised to S3-242382 |
Nokia | 33.501 18.5.0 CR#1983 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241818 | TWIF procedure correction | CR | Nokia | 33.501 17.13.0 CR#1984 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-241819 | TWIF procedure correction | CR | Nokia | 33.501 18.5.0 CR#1985 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-241820 | UDR control flag for NSWO |
CR revised to S3-242628 |
Nokia, Verizon | 33.501 17.13.0 CR#1986 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241821 | UDR control flag for NSWO |
CR revised to S3-242629 |
Nokia, Verizon | 33.501 18.5.0 CR#1987 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241822 | Discussion paper of UPU implementation gaps | discussion | Nokia | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
noted | [WTS] [JSN] | |
S3-241823 | Enhancement in UPU procedure to protect UPU header |
CR revised to S3-242380 |
Nokia | 33.501 18.5.0 CR#1988 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241824 | AF disabling the encryption when roaming |
CR revised to S3-242656 |
Nokia, Verizon | 33.535 18.3.0 CR#210 catF | AKMA_Disable | Rel-18 |
S3-116 AI: 4.1.5 |
revised | [WTS] [JSN] |
S3-241825 | Updates to the SBA certificate profile |
CR revision of S3-240580 revised to S3-242383 |
Nokia, Johns Hopkins University APL, Cisco | 33.310 18.3.0 CR#1971 catF | ACM_SBA | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241826 | Correction to validation of usage of X.509 certificate procedure |
CR revision of S3-240993 revised to S3-242384 |
Nokia, Nokia Shanghai Bell, Ericsson, Johns Hopkins University APL, Cisco | 33.310 18.3.0 CR#1992 catF | ACM_SBA | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241827 | Secure retrieval of 5G system UE Ids and privacy related information in EDGE | discussion | Nokia, Nokia Shanghai Bell | Rel-19 |
S3-116 AI: 5.14 |
noted | [WTS] [JSN] | ||
S3-241828 | Secure retrieval of 5G system UE Ids and privacy related information in the EDGE |
pCR revised to S3-242567 |
Nokia, Nokia Shanghai Bell | 33.749 0.1.0 | FS_EDGE_Ph3 | Rel-19 |
S3-116 AI: 5.14 |
revised | [WTS] [JSN] |
S3-241829 | Proposal to remove Editor’s Note and update solution in TR 33.701 | pCR | Google Inc. | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
merged | [WTS] [JSN] |
S3-241830 | Proposal to update a solution in TR 33.701 |
pCR revised to S3-242488 |
Google Inc. | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-241831 | Propose to update a new solution text in TR 33.701 |
pCR revised to S3-242513 |
Google Inc. | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-241832 | Retrieval of the EASDF security information from EASDF |
CR revised to S3-242433 |
Nokia, Nokia Shanghai Bell | 33.501 18.5.0 CR#1989 catF | EDGE_Ph2 | Rel-18 |
S3-116 AI: 4.1. |
revised | [WTS] [JSN] |
S3-241833 | Solution for authentication, confidentiality, and integrity protection of UE in ATSSS while selecting MPQUIC |
pCR revised to S3-242572 |
Nokia | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-241834 | Solution #1: resolution of ENs in evaluation part |
pCR revised to S3-242627 |
THALES | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241835 | Solution #5: evaluation |
pCR revised to S3-242552 |
THALES | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241836 | Solution #13: evaluation |
pCR revised to S3-242553 |
THALES | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241837 | Key Issue #1: new solution |
pCR revised to S3-242486 |
THALES | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-241838 | Key Issue #1: conclusion | pCR | THALES | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] |
S3-241839 | Solution for KI#4 UE authentication while connecting to a new WLAN AP through the same NSWOF |
pCR revision of S3-241653 |
Charter Communications, Inc | 33.702 0.1.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-241840 | UE IPSec connection optimization while connecting to a new WLAN AP through the same TNGF | pCR | Charter Communications, Inc | 33.702 0.1.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-241841 | Correcting CR implementation S3-240895 | CR | Nokia | 33.501 18.5.0 CR#1990 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
merged | [WTS] [JSN] |
S3-241842 | Clarifications on NRF and NFp checks |
CR revision of S3-240648 revised to S3-242461 |
Nokia, Nokia Shanghai Bell | 33.501 18.5.0 CR#19401 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
revised | [WTS] [JSN] |
S3-241843 | Clarification needed on NF type handling in alignment with stage 3 |
CR revised to S3-242462 |
Nokia | 33.501 18.5.0 CR#1991 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
revised | [WTS] [JSN] |
S3-241844 | Reply LS on MSISDN exposure |
LS out LS is reply to S3-241748 source LS: SA6, CT3 LS To: SA2, SA |
AT&T Services, Inc. |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |||
S3-241845 | KI#2, New Sol: Authorization of intermediate UE interacting with AIoT device | pCR | vivo | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-241846 | New Sol: AIoT device authentication and authorization | pCR | vivo | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-241847 | KI#3, New Sol: Privacy protection on number of AIoT devices | pCR | vivo | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-241848 | New key issue for AIoT device authentication and authorization | pCR | vivo | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-241849 | Update Key issue #3 | pCR | vivo | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-241850 | New solution for KI#1: New Data Collection NFs |
pCR revised to S3-242426 |
MITRE Corporation, Johns Hopkins University APL, OTD_US, US National Security Agency | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241851 | New use case for security evaluation and monitoring: API security risks |
pCR revised to S3-242422 |
MITRE Corporation, Dell Technologies, Defense Information Systems Agency EM, US National Security Agency, Nokia, Nokia Shanghai Bell, Johns Hopkins University APL, AT&T | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241852 | Updates to eZTS Key Issue 2 |
pCR revised to S3-242423 |
MITRE Corporation, Johns Hopkins University APL, OTD_US, US National Security Agency, Nokia, Nokia Shanghai Bell | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241853 | New solution for KI#2: Security Policy Enforcement via NRF and SCP/NF |
pCR revised to S3-242429 |
MITRE Corporation, Johns Hopkins University APL, US National Security Agency | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241854 | New Solution for User Authentication and Authorization via AMF |
pCR revised to S3-242497 |
InterDigital France R&D, SAS | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241855 | New Solution for User Authentication and Authorization via SMF |
pCR revised to S3-242498 |
InterDigital France R&D, SAS | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241856 | New solution UAV Authentication and Authorization for Multiple USS |
pCR revised to S3-242516 |
InterDigital France R&D, SAS | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
revised | [WTS] [JSN] |
S3-241857 | New Solution for Security for multi-hop UE-to-Network Relay |
pCR revised to S3-242650 |
InterDigital France R&D, SAS | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-241858 | Resource owner function | CR | Nokia | 33.122 18.3.0 CR#72 catF | SNAAPPY | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-241859 | Addressing EN on claim versus scope | CR | Nokia | 33.122 18.3.0 CR#73 catF | SNAAPPY | Rel-18 |
S3-116 AI: 4.1.15 |
merged | [WTS] [JSN] |
S3-241860 | Split between authentication and authorization |
CR revised to S3-242630 |
Nokia | 33.501 18.5.0 CR#1992 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
revised | [WTS] [JSN] |
S3-241861 | Reference for IPX provider | CR | Nokia | 33.501 18.5.0 CR#1993 catF | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
merged | [WTS] [JSN] |
S3-241862 | Modified PRINS alignment with 29.573 on security profile |
CR revised to S3-242458 |
Nokia | 33.501 18.5.0 CR#1994 catF | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
revised | [WTS] [JSN] |
S3-241863 | RAN2 assumptions for 5GSAT_SEC study | discussion | InterDigital Belgium. LLC, Nokia | Rel-19 |
S3-116 AI: 5.7 |
noted | [WTS] [JSN] | ||
S3-241864 | Solution for unauthenticated DOS protection |
pCR revised to S3-242638 |
InterDigital Belgium. LLC | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241865 | RAN2 assumptions for AIOT study | discussion | InterDigital Belgium. LLC | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] | ||
S3-241866 | Solution for Lightweight AIoT ID privacy | pCR | InterDigital Belgium. LLC | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-241867 | Addressing ENs in Use Case 5 |
pCR revised to S3-242421 |
US National Security Agency, MITRE Corporation, Johns Hopkins University APL | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241868 | Reference on requirements for multiple NRFs | CR | Nokia | 33.501 18.5.0 CR#1995 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
S3-241869 | Discussion on ZTS Assumptions | discussion | Johns Hopkins University APL, MITRE Corporation, National Security Agency | Rel-19 |
S3-116 AI: 5.1 |
noted | [WTS] [JSN] | ||
S3-241870 | PRINS version 2 | CR | CableLabs | 33.501 18.5.0 CR#1996 catB | TEI19 | Rel-19 |
S3-116 AI: 4.11 |
not pursued | [WTS] [JSN] |
S3-241871 | Reply LS on the use of TLS with QUIC in ATSSS context |
LS out LS is reply to SA2 source LS: S3-241746 LS To: SA2 |
CableLabs | Rel-18 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] | ||
S3-241872 | Revised SID on security aspects for Multi-Access (DualSteer + ATSSS Ph-4) | SID revised | CableLabs | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] | |
S3-241873 | new kew issue on backward compatibility | pCR | CableLabs, Charter Communications | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
merged | [WTS] [JSN] |
S3-241874 | Solution for authentication and authorization of non-3GPP devices behind 5G-RG |
pCR revised to S3-242612 |
CableLabs | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241875 | LS to CT on IANA reservation on Security vulnerability fix for use of AES-GCM and AES-GMAC in 33.203 |
LS out LS To: CT |
Apple |
S3-116 AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-241876 | CAT256 - New KI for CAT_256 on correctly indication | pCR | Apple | 33.701 0.0.2 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.5 |
withdrawn | [WTS] [JSN] |
S3-241877 | CAT256 - New solution for CAT_256 on correctly indication | pCR | Apple | 33.701 0.0.2 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.5 |
withdrawn | [WTS] [JSN] |
S3-241878 | CAT256 - New KI for CAT_256 on Flexibility to adjust the preference on security algorithms | pCR | Apple | 33.701 0.0.2 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.5 |
withdrawn | [WTS] [JSN] |
S3-241879 | CAT256 - New solution for CAT_256 on Flexibility to adjust the preference on security algorithms | pCR | Apple | 33.701 0.0.2 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.5 |
withdrawn | [WTS] [JSN] |
S3-241880 | MiBiDA - New solution for mitigating bidding down attack | pCR | Apple | 33.700-41 0.0.2 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.6 |
withdrawn | [WTS] [JSN] |
S3-241881 | AIoT - New KI for Ambient IoT on Authentication | pCR | Apple | 33.713 0.0.1 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-241882 | AIoT - New KI for Ambient IoT on communication security | pCR | Apple | 33.713 0.0.1 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-241883 | AIoT - Security assumption for Ambient IoT | pCR | Apple | 33.713 0.0.1 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-241884 | LS to CT on IANA reservation on Security vulnerability fix for use of AES-GCM and AES-GMAC in 33.203 |
LS out LS To: CT |
Apple |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-241885 | Reply LS to S3-241726 on Mitigation of Downgrade attacks |
LS out source LS: S3-241726 LS To: CT1 revised to S3-242367 |
Apple |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |||
S3-241886 | LTM-reply LS to RAN2 on LTM |
LS out LS is reply to S3-241773 source LS: R2-2404037 LS To: RAN2 revised to S3-242400 |
Apple |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |||
S3-241887 | AIoT-Security assumption for Ambient IoT | pCR | Apple | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-241888 | AIoT-LS to RAN2 on AIoT assumptions |
LS out LS To: RAN2, SA2, SA1 revised to S3-242533 |
Apple |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] | |||
S3-241889 | AIoT - New KI for Ambient IoT on Authentication | pCR | Apple | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-241890 | AIoT - New KI for Ambient IoT on communication security | pCR | Apple | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
merged | [WTS] [JSN] |
S3-241891 | MiBiDA- Conclusions | pCR | Apple | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] |
S3-241892 | MiBiDA- Evaluation for solution#5 |
pCR revised to S3-242491 |
Apple | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-241893 | CAT256-New KI for CAT_256 on correctly indication | pCR | Apple | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
noted | [WTS] [JSN] |
S3-241894 | CAT256-New solution for CAT_256 on correctly indication | pCR | Apple | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
noted | [WTS] [JSN] |
S3-241895 | draft Reply LS on home network triggered re-authentication |
LS out LS is reply to S3-241736 LS To: CT4 |
ZTE Corporation | Rel-18 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-241896 | CR on the failure cases in home network triggered re-authentication | CR | ZTE Corporation | 33.501 18.5.0 CR#1997 catF | HN_Auth | Rel-18 |
S3-116 AI: 3 |
merged | [WTS] [JSN] |
S3-241897 | Discussion on security handling for inter-CU LTM in non-DC cases | discussion | ZTE Corporation | Rel-19 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | ||
S3-241898 | Draft reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-241773 LS To: RAN WG2 |
ZTE Corporation | Rel-19 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-241899 | [Draft]Reply LS on Issues related to LI considerations for TR 33.757 |
LS out LS is reply to S3-241751 LS To: SA3-LI |
ZTE Corporation | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |
S3-241900 | Discussion on the condition for provisioning of the ePDG identity to the UE | discussion | ZTE Corporation | Rel-18 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | ||
S3-241901 | LS reply on the condition for provisioning of the ePDG identity to the UE |
LS out LS To: CT1 revised to S3-242369 |
ZTE Corporation | Rel-18 |
S3-116 AI: 3 |
revised | [WTS] [JSN] | ||
S3-241902 | Clarification on the condition for provisioning of the ePDG identity to the UE |
CR revised to S3-242368 |
ZTE Corporation | 33.402 18.0.0 CR#150 catF | TEI18 | Rel-18 |
S3-116 AI: 3 |
revised | [WTS] [JSN] |
S3-241903 | CR on editorial clear up | CR | ZTE Corporation | 33.535 18.3.0 CR#211 catF | AKMA_Ph2 | Rel-18 |
S3-116 AI: 4.1.5 |
agreed | [WTS] [JSN] |
S3-241904 | CR to update AKMA related UDM services | CR | ZTE Corporation | 33.535 18.3.0 CR#212 catF | AKMA_Ph2 | Rel-18 |
S3-116 AI: 4.1.5 |
agreed | [WTS] [JSN] |
S3-241905 | CR to update the AKMA service disabling procedure | CR | ZTE Corporation | 33.535 18.3.0 CR#213 catF | AKMA_Ph2 | Rel-18 |
S3-116 AI: 4.1.5 |
not pursued | [WTS] [JSN] |
S3-241906 | CR to update the procedure for AAnF requesting UE roaming status reports | CR | ZTE Corporation | 33.535 18.3.0 CR#214 catF | AKMA_Ph2 | Rel-18 |
S3-116 AI: 4.1.5 |
not pursued | [WTS] [JSN] |
S3-241907 | Update registration procedure for handover from EPS to 5GS over N26 | CR | ZTE Corporation | 33.501 18.5.0 CR#1998 catF | TEI19 | Rel-19 |
S3-116 AI: 4.11 |
not pursued | [WTS] [JSN] |
S3-241908 | Update the role of UE in 5GMSG | CR | ZTE Corporation | 33.501 18.5.0 CR#1999 catF | TEI18 | Rel-18 |
S3-116 AI: 4.9 |
merged | [WTS] [JSN] |
S3-241909 | Update Transport security protection between the two MSGin5G Servers |
CR revised to S3-242463 |
ZTE Corporation | 33.501 18.5.0 CR#2000 catF | TEI18 | Rel-18 |
S3-116 AI: 4.9 |
revised | [WTS] [JSN] |
S3-241910 | Non MSGin5G UE Authentication and Authorization in bulk registration scenarios | other | ZTE Corporation | 5GMARCH_SEC_Ph3 | Rel-19 |
S3-116 AI: 4.9 |
approved | [WTS] [JSN] | |
S3-241911 | Add an EN to Solution#11 | pCR | ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-241912 | New solution for SUPI privacy issue based on AMF register with UDM |
pCR revised to S3-242556 |
ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241913 | New solution for SUPI privacy issue |
pCR revised to S3-242557 |
ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241914 | Conclusion proposal | pCR | ZTE Corporation | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
merged | [WTS] [JSN] |
S3-241915 | Conclusion proposal | pCR | ZTE Corporation | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] |
S3-241916 | Evaluation proposal on summarizing impact of solutions | pCR | ZTE Corporation | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
merged | [WTS] [JSN] |
S3-241917 | Update to Solution#6 |
pCR revised to S3-242492 |
ZTE Corporation | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-241918 | Update to the Solution#13 | pCR | ZTE Corporation | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-241919 | Clean up for TR 33.713 | pCR | ZTE Corporation | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-241920 | New solution for KI#2 |
pCR revised to S3-242540 |
ZTE Corporation | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] |
S3-241921 | Solution to KI#1 and KI#2 |
pCR revised to S3-242499 |
ZTE Corporation | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241922 | EN removal for Solution#3 |
pCR revised to S3-242489 |
Nokia | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-241923 | LS on Reply LS on Mitigation of Downgrade attacks |
LS out LS To: CT1 |
Nokia | Rel-18 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-241924 | pCR on Solution for NRF reporting | pCR | Nokia | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
noted | [WTS] [JSN] |
S3-241925 | Solution 6 EN removal | pCR | Nokia | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-241926 | Solution 6 Evaluation |
pCR revised to S3-242551 |
Nokia | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241927 | New solution for AS security context establishment in satellite access with store-and-forward operations |
pCR revised to S3-242639 |
Nokia | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241928 | New Solution for UE access control using CAG verification |
pCR revised to S3-242581 |
Nokia | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
revised | [WTS] [JSN] |
S3-241929 | New Key Issue on data exposure relevant for network level attacks | pCR | Nokia | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
noted | [WTS] [JSN] |
S3-241930 | New Solution for Key Issue 1 |
pCR revised to S3-242427 |
Nokia | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-241931 | New solution on KI3 Privacy by protecting AIoT device identifiers | pCR | CALTTA | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-241932 | New solution for UE authorization |
pCR revised to S3-242583 |
China Unicom, ZTE | 33.721 0.1.0 | FS_Metaverse_Sec | Rel-19 |
S3-116 AI: 5.18 |
revised | [WTS] [JSN] |
S3-241933 | Update to security architecture and assumptions | pCR | ZTE Corporation | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-241934 | Solution to KI#1 Ownership Security | pCR | ZTE Corporation | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-241935 | Editorial update to gap analysis table | pCR | ZTE Corporation | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
merged | [WTS] [JSN] |
S3-241936 | Addition of security threat to KI#1 |
pCR revised to S3-242576 |
Ericsson | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
revised | [WTS] [JSN] |
S3-241937 | Solution reusing existing interfaces and security mechanisms for energy-related information collection |
pCR revised to S3-242578 |
Ericsson | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
revised | [WTS] [JSN] |
S3-241938 | Solution on authorization of Intermediate UE for AIoT services |
pCR revised to S3-242541 |
OPPO Beijing | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] |
S3-241939 | Updates to Solution #12 |
pCR revised to S3-242646 |
OPPO Beijing | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241940 | Add evaluation to Solution #12 |
pCR revised to S3-242647 |
OPPO Beijing | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241941 | Implementing CR to TS 33.533 agreed in SA plenary in SP-240498 | CR | Ericsson, Huawei, HiSilicon, Xiaomi | 33.533 18.2.0 CR#68 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
agreed | [WTS] [JSN] |
S3-241942 | New Solution on Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revised to S3-242651 |
Ericsson | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-241943 | New Solution on Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revised to S3-242652 |
Ericsson | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-241944 | New Solution on Security of multi-hop UE-to-Network Relay communication |
pCR revised to S3-242522 |
Ericsson | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-241945 | LS reply to GSMA on PQC |
LS out LS is reply to GSMA PQTN LS To: GSMA PQTN revised to S3-242378 |
Huawei, HiSilicon |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |||
S3-241946 | LS reply to ETSI on PQC |
LS out LS is reply to S3-241763 LS To: ETSI TC Cyber |
Huawei, HiSilicon |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |||
S3-241947 | LS reply on GSMA CVD-2023-0069 5G Core Network Attacks |
LS out LS is reply to GSMA CVD LS To: GSMA CVD revised to S3-242453 |
Huawei, HiSilicon |
S3-116 AI: 7 |
revised | [WTS] [JSN] | |||
S3-241948 | Clarification on SBI token | CR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 18.5.0 CR#2001 catF | TEI18 | Rel-18 |
S3-116 AI: 7 |
agreed | [WTS] [JSN] |
S3-241949 | Clarification on NFDiscovery Authorization |
CR revised to S3-242451 |
Huawei, HiSilicon | 33.501 18.5.0 CR#2002 catF | TEI18 | Rel-18 |
S3-116 AI: 7 |
revised | [WTS] [JSN] |
S3-241950 | updates to Sol#1 | pCR | Huawei, HiSilicon | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
approved | [WTS] [JSN] |
S3-241951 | updates to security assumption | pCR | Huawei, HiSilicon | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
noted | [WTS] [JSN] |
S3-241952 | addressing EN in Sol#3 |
pCR revised to S3-242445 |
Huawei, HiSilicon | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
revised | [WTS] [JSN] |
S3-241953 | solution for NFs sharing a ACME client | pCR | Huawei, HiSilicon | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
noted | [WTS] [JSN] |
S3-241954 | new key issue for no transmit zones (NTZ) | pCR | Huawei, HiSilicon | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
noted | [WTS] [JSN] |
S3-241955 | UUAA supporting multiple USS |
pCR revised to S3-242518 |
Huawei, HiSilicon | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
revised | [WTS] [JSN] |
S3-241956 | Authorization supporting multiple USS |
pCR revised to S3-242519 |
Huawei, HiSilicon | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
revised | [WTS] [JSN] |
S3-241957 | Revocation supporting multiple USS |
pCR revised to S3-242520 |
Huawei, HiSilicon | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
revised | [WTS] [JSN] |
S3-241958 | Discussions on DoS attacks to UAVs | discussion | Huawei, HiSilicon | Rel-18 |
S3-116 AI: 4.1.11 |
noted | [WTS] [JSN] | ||
S3-241959 | CR to address DoS attacks to UAV | CR | Huawei, HiSilicon | 33.256 18.2.0 CR#49 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.11 |
not pursued | [WTS] [JSN] |
S3-241960 | new solution for User A&A |
pCR revised to S3-242500 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241961 | new solution for User privacy protection |
pCR revised to S3-242509 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241962 | new solution for non-3gpp device A&A |
pCR revised to S3-242613 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-241963 | Home control for Network Slice Admission Control procedures | CR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, LGE, Xiaomi, ZTE | 33.501 18.5.0 CR#2003 catB | DUMMY | Rel-19 |
S3-116 AI: 6 |
not pursued | [WTS] [JSN] |
S3-241964 | Dummy WID for home control for NSAC procedures | WID new | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, LGE, Xiaomi, ZTE | Rel-19 |
S3-116 AI: 6 |
noted | [WTS] [JSN] | ||
S3-241965 | Corrections and removing token claim related EN |
CR revised to S3-242385 |
Huawei, HiSilicon | 33.122 18.3.0 CR#74 catF | SNAAPPY | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-241966 | Update and evaluation to solution#2 |
pCR revised to S3-242472 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241967 | Update and evaluation to solution#6 |
pCR revised to S3-242477 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241968 | Reply-LS on clarifications on consent management |
LS out LS is reply to S3-241741 LS To: GSMA OPG revised to S3-242374 |
Nokia |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |||
S3-241969 | Update and evaluation to solution#7 |
pCR revised to S3-242478 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241970 | Correction to terms |
CR revised to S3-242442 |
Ericsson | 33.514 16.4.0 CR#16 catF | SCAS_5G | Rel-16 |
S3-116 AI: 4.1.1 |
revised | [WTS] [JSN] |
S3-241971 | update to AKMA service disabling | CR | Huawei, HiSilicon | 33.535 18.3.0 CR#215 catF | AKMA_Disable | Rel-18 |
S3-116 AI: 4.1.5 |
not pursued | [WTS] [JSN] |
S3-241972 | Addressing the editor's note on the security assumption |
pCR revised to S3-242637 |
Huawei, HiSilicon, Interdigital, Ericsson, Nokia, Nokia Shanghai Bell, Intel, CATT, Xiaomi, China Telecom | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241973 | Addressing the editor's note and adding evaluation in solution 18 |
pCR revised to S3-242545 |
Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241974 | Withdrawn | pCR | Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
withdrawn | [WTS] [JSN] |
S3-241975 | key issue on protection of information transfer for AIoT services | pCR | Huawei, HiSilicon | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
merged | [WTS] [JSN] |
S3-241976 | solution on protection for disabling device operation |
pCR revised to S3-242537 |
Huawei, HiSilicon, China Unicom, CAICT | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] |
S3-241977 | Assumption on security aspects of network exposure | pCR | Huawei, HiSilicon, CAICT | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-241978 | solution on protection of information transfer for AIoT services | pCR | Huawei, HiSilicon | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-241979 | Correct procedure for Authorization of selection of participant NWDAF instances in the Federated Learning group |
CR revised to S3-242456 |
Huawei, HiSilicon | 33.501 18.5.0 CR#2004 catF | eNA_Ph3_SEC | Rel-18 |
S3-116 AI: 4.1.13 |
revised | [WTS] [JSN] |
S3-241980 | New solution on KI#3 Privacy of VFL between VFL members |
pCR revised to S3-242592 |
Huawei, HiSilicon | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-241981 | New solution on KI#1 Security aspects on enhancements to LCS to support AIML |
pCR revised to S3-242596 |
Huawei, HiSilicon | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-241982 | IPsec solution between UE and UPF |
pCR revised to S3-242575 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-241983 | Using 3GPP security context to derive authentication pre-shared key for NIN3A |
pCR revised to S3-242570 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-241984 | New key issue about UPF exposing new IP communication endpoint |
pCR revised to S3-242622 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-241985 | Reuse solution about policy based certificate renewal |
pCR revised to S3-242439 |
Huawei, HiSilicon | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
revised | [WTS] [JSN] |
S3-241986 | Reuse solution for certificate revocation | pCR | Huawei, HiSilicon | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
noted | [WTS] [JSN] |
S3-241987 | New solution about doing access control for UPF | pCR | Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] |
S3-241988 | Reply LS for the use of TLS with QUIC in ATSSS context |
LS out LS is reply to S3-241746 source LS: S2-2405459 LS To: SA2 |
Huawei, HiSilicon | ATSSS_Ph3 | Rel-18 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |
S3-241989 | New solution for mitigating UE privacy risks using temporary UE ID |
pCR revised to S3-242543 |
Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-241990 | Evaluation for KI#2 on SBA security for solution 7 |
pCR revised to S3-242479 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241991 | SID on security aspects of NEF | SID new | Huawei, HiSilicon, CAICT | Rel-19 |
S3-116 AI: 6 |
noted | [WTS] [JSN] | ||
S3-241992 | Solution on mutual authentication and NEF-AF interface protection for exposing energy related information |
pCR revised to S3-242579 |
Huawei, HiSilicon | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
revised | [WTS] [JSN] |
S3-241993 | Discussion paper on security aspects of NEF | discussion | Huawei, HiSilicon | Rel-19 |
S3-116 AI: 6 |
noted | [WTS] [JSN] | ||
S3-241994 | Evaluation for KI#2 on SBA security for solution 8 |
pCR revised to S3-242481 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241995 | Alignment with CT1 and editorial changes to U2U discovery | CR | Huawei, HiSilicon | 33.503 18.2.0 CR#171 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] |
S3-241996 | Reply LS on identifications of 5G ProSe End UEs for 5G ProSe UE-to-UE relay discovery |
LS out LS is reply to S3-241724 source LS: C1-241787 LS To: CT1, SA2 revised to S3-242404 |
Huawei, HiSilicon | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] | |
S3-241997 | Add the usage of the PLMN IDs from Remote UE – R17 | CR | Huawei, HiSilicon | 33.503 17.7.0 CR#172 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
not pursued | [WTS] [JSN] |
S3-241998 | Adding the usage of the PLMN IDs from Remote UE – R18 mirror | CR | Huawei, HiSilicon | 33.503 18.2.0 CR#173 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
not pursued | [WTS] [JSN] |
S3-241999 | Editorial and clarificaiton of SCPAC |
CR revised to S3-242386 |
Huawei, HiSilicon | 33.501 18.5.0 CR#2005 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-242000 | New Solution for Multi-hop UE-to-Network Relay security establishment |
pCR revised to S3-242523 |
Huawei, HiSilicon | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242001 | New Solution for Multi-hop UE-to-UE Relay security |
pCR revised to S3-242528 |
Huawei, HiSilicon | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242002 | Reply LS on differentiating security materials used for PC5 direct discovery for 5G ProSe UE-to-network relay |
LS out LS is reply to S3-241727 source LS: C1-242665 LS To: CT1 |
Huawei, HiSilicon | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] | |
S3-242003 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R17 | CR | Huawei, HiSilicon | 33.503 17.7.0 CR#174 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
not pursued | [WTS] [JSN] |
S3-242004 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R18 mirror | CR | Huawei, HiSilicon | 33.503 18.2.0 CR#175 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242005 | Addressing the editor's note in solution 10 | pCR | Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242006 | Addressing the editor's note in solution 8 | pCR | Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242007 | Addressing the editor's note in solution 7 | pCR | Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242008 | Update to Annex A |
pCR revised to S3-242582 |
Huawei, HiSilicon | 33.702 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
revised | [WTS] [JSN] |
S3-242009 | Update Key issue #5 | pCR | Huawei, HiSilicon | 33.702 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-242010 | New soluiton to address KI#1 |
pCR revised to S3-242501 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242011 | New KI on privacy to non-3GPP device case |
pCR revised to S3-242610 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242012 | New soluiton to address KI#2 | pCR | Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
noted | [WTS] [JSN] |
S3-242013 | update key issue #1 on privacy aspect |
pCR revised to S3-242568 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242014 | Address EN of key issue #2 |
pCR revised to S3-242569 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242015 | propose new solution to KI#2 |
pCR revised to S3-242563 |
Huawei, HiSilicon | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-242016 | propose conclusion to KI#1 and KI#3 | pCR | Huawei, HiSilicon | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
merged | [WTS] [JSN] |
S3-242017 | propose conclusion to KI#4 |
pCR revised to S3-242565 |
Huawei, HiSilicon | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-242018 | Peer certificate checking at gNB to TS 33.511 | CR | Huawei, HiSilicon, CAICT | 33.511 18.3.0 CR#66 catB | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
withdrawn | [WTS] [JSN] |
S3-242019 | Add threat to peer certificate checking at gNB | CR | Huawei, HiSilicon, CAICT | 33.511 18.3.0 CR#67 catB | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
withdrawn | [WTS] [JSN] |
S3-242020 | Local certificate checking at gNB to TS 33.511 | CR | Huawei, HiSilicon, CAICT | 33.511 18.3.0 CR#68 catB | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
withdrawn | [WTS] [JSN] |
S3-242021 | Add threat to local certificate checking at gNB | CR | Huawei, HiSilicon, CAICT | 33.511 18.3.0 CR#69 catB | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
withdrawn | [WTS] [JSN] |
S3-242022 | Expired certificate checking at gNB to TS 33.511 | CR | Huawei, HiSilicon, CAICT | 33.511 18.3.0 CR#70 catB | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
withdrawn | [WTS] [JSN] |
S3-242023 | Add threat to expired certificate checking at gNB | CR | Huawei, HiSilicon, CAICT | 33.511 18.3.0 CR#71 catB | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
withdrawn | [WTS] [JSN] |
S3-242024 | Corrections and additions for the N3IWF network product class |
CR revised to S3-242395 |
Huawei, HiSilicon, CAICT, China Unicom | 33.926 18.3.0 CR#95 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.1 |
revised | [WTS] [JSN] |
S3-242025 | Reversal of changes related to deprecated HTTP RFCs for 33.501 |
other revised to S3-242416 |
Huawei, HiSilicon | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
revised | [WTS] [JSN] | |
S3-242026 | HTTP RFC obsoleted by IETF RFC 9110 |
CR revised to S3-242387 |
Huawei, HiSilicon | 33.501 18.5.0 CR#2006 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-242027 | Reversal of changes related to deprecated HTTP RFCs for 33.210 |
other revised to S3-242417 |
Huawei, HiSilicon | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
revised | [WTS] [JSN] | |
S3-242028 | HTTP RFC obsoleted by IETF RFC 9110 |
CR revised to S3-242388 |
Huawei, HiSilicon | 33.210 18.0.0 CR#83 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-242029 | Clarifications of the proposals for reversal of changes related to deprecated RFCs | discussion | Huawei, HiSilicon | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
noted | [WTS] [JSN] | |
S3-242030 | Editorial corrections | pCR | Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242031 | Evaluation proposal |
pCR revised to S3-242493 |
Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-242032 | Conclusion proposal | pCR | Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] |
S3-242033 | New approach for increasing user awareness |
pCR revised to S3-242636 |
Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] |
S3-242034 | Updates to evaluation on malformed messages use case | pCR | Huawei, HiSilicon | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
merged | [WTS] [JSN] |
S3-242035 | Updates to evaluation on massive number of calls use case |
pCR revised to S3-242420 |
Huawei, HiSilicon | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-242036 | Proposal for a way forward | discussion | Huawei, HiSilicon | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
noted | [WTS] [JSN] | |
S3-242037 | Agenda and minutes from conf call | other | Huawei, HiSilicon | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] | |
S3-242038 | Coversheet for TR 33.701 |
TS or TR cover revised to S3-242494 |
Huawei, HiSilicon | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
revised | [WTS] [JSN] | |
S3-242039 | Corrections to the N3IWF annex (mirror) |
CR revised to S3-242396 |
Huawei, HiSilicon, CAICT, China Unicom | 33.926 19.0.0 CR#96 catA | TEI18 | Rel-19 |
S3-116 AI: 4.1.1 |
revised | [WTS] [JSN] |
S3-242040 | Corrections to the N3IWF scas |
CR revised to S3-242397 |
Huawei, HiSilicon, CAICT, China Unicom | 33.520 18.0.0 CR#2 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.1 |
revised | [WTS] [JSN] |
S3-242041 | Solution for EEC provided IP address verification |
pCR revised to S3-242661 |
Huawei, HiSilicon | 33.749 0.1.0 | FS_EDGE_Ph3 | Rel-19 |
S3-116 AI: 5.14 |
revised | [WTS] [JSN] |
S3-242042 | New solution on secuirty protection in store and forward Satellite Operation with RAN on board |
pCR revised to S3-242642 |
Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242043 | Correction to terms |
CR revised to S3-242443 |
Ericsson | 33.514 17.0.0 CR#17 catA | SCAS_5G | Rel-17 |
S3-116 AI: 4.1.1 |
revised | [WTS] [JSN] |
S3-242044 | draft-Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-241773 LS To: RAN2 |
Intel | Rel-19 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-242045 | Correction to terms |
CR revised to S3-242444 |
Ericsson | 33.514 18.2.0 CR#18 catA | SCAS_5G | Rel-18 |
S3-116 AI: 4.1.1 |
revised | [WTS] [JSN] |
S3-242046 | Conclusion to KI#1 | pCR | China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242047 | Conclusion to KI#2 | pCR | China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242048 | draft_Reply LS on the use of TLS with QUIC in ATSSS context |
LS out LS is reply to S3-241746 LS To: SA2 |
Intel | Rel-18 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | ||
S3-242049 | Conclusion to KI#3 | pCR | China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242050 | Add Abbreviations | pCR | Intel | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242051 | Mapping solutions to key issues | pCR | China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242052 | Discussion paper on TLS with QUIC in ATSSS context | discussion | Intel | Rel-18 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | ||
S3-242053 | New KI on direct link between 5G NR Femtos | pCR | China Telecomunication Corp. | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-242054 | New KI on 5G NR Femto management system accessible on the public internet | pCR | China Telecomunication Corp. | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-242055 | Discussion Paper on Security Key Handling for Inter-CU LTM | discussion | Intel |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-242056 | Architecture and Security Assumptions in TR 33.713 | pCR | China Telecom Corporation Ltd. | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
merged | [WTS] [JSN] |
S3-242057 | Solution to KI#2 in TR33.745 | pCR | China Telecomunication Corp. | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-242058 | Secure Authentication and Connectivity for UE in ATSSS over NIN3A |
pCR revised to S3-242573 |
Intel | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242059 | Updates to Secure Initial Registration for S&F Satellite Operation |
pCR revised to S3-242549 |
Intel | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242060 | Clarification of direct discovery in r18 | CR | China Telecom Corporation Ltd. | 33.503 18.2.0 CR#176 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242061 | Study on Security Aspects of Interconnect of SNPN | SID new | Cisco, Intel |
S3-116 AI: 6 |
noted | [WTS] [JSN] | |||
S3-242062 | Clarification of direct discovery in r17(mirror) | CR | China Telecom Corporation Ltd. | 33.503 17.7.0 CR#177 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242063 | Correction to abbreviations | CR | Ericsson | 33.514 16.4.0 CR#19 catF | SCAS_5G | Rel-16 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242064 | Discussion on publication of the Post Quantum Cryptography – Guidelines for Telecom Use Cases document | discussion | Intel |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-242065 | solution for AUN3 device |
pCR revised to S3-242600 |
Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-242066 | Discussion of enhancements for SNPN cellular hotspots | discussion | Cisco, Intel |
S3-116 AI: 6 |
noted | [WTS] [JSN] | |||
S3-242067 | Clarification related to U2U discovery model B |
CR revised to S3-242409 |
China Telecom Corporation Ltd., Xiaomi | 33.503 18.2.0 CR#178 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] |
S3-242068 | New solution for multi-hop U2U discovery |
pCR revised to S3-242530 |
China Telecom Corporation Ltd. | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242069 | Correction to abbreviations | CR | Ericsson | 33.514 17.0.0 CR#20 catA | SCAS_5G | Rel-17 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242070 | New Solution on Security for multi-hop UE-to-Network Relay Communication |
pCR revised to S3-242524 |
China Telecom Corporation Ltd. | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242071 | New Solution on Security of multi-hop UE-to-UE Relay Communication |
pCR revised to S3-242529 |
China Telecom Corporation Ltd. | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242072 | Update the clause 4 of TR 33.743 | pCR | China Telecom Corporation Ltd. | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242073 | Correction to abbreviations | CR | Ericsson | 33.514 18.2.0 CR#21 catA | SCAS_5G | Rel-18 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242074 | New Solution for KI #1 of TR 33.700-32 |
pCR revised to S3-242502 |
China Telecom Corporation Ltd. | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242075 | New Solution for KI #3 of TR 33.700-32 |
pCR revised to S3-242614 |
China Telecom Corporation Ltd. | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242076 | Correction to test names | CR | Ericsson | 33.514 16.4.0 CR#22 catF | SCAS_5G | Rel-16 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242077 | Correction to test names | CR | Ericsson | 33.514 17.0.0 CR#23 catA | SCAS_5G | Rel-17 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242078 | Correction to test names | CR | Ericsson | 33.514 18.2.0 CR#24 catA | SCAS_5G | Rel-18 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242079 | Reply LS on Mitigation of Downgrade attacks |
LS out LS is reply to C1-241848 LS To: CT1 |
vivo |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |||
S3-242080 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-241773 LS To: RAN2 |
vivo |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |||
S3-242081 | Correction on unauthenticated IMS emergency sessions |
CR revised to S3-242617 |
vivo, China Telecom | 33.501 15.18.0 CR#2007 catF | TEI15 | Rel-15 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-242082 | Conclusion for key issue#1 | pCR | vivo | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] |
S3-242083 | LS on Providing RAT information to UE of MiBiDA |
LS out LS To: CT1, SA2 |
vivo |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] | |||
S3-242084 | New solution on mitigation of privacy issues of interim GUTI |
pCR revised to S3-242619 |
vivo | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242085 | Address topology EN in Key Issue#2 |
pCR revised to S3-242584 |
vivo | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242086 | New key issue on Security of communication data used in VFL training process |
pCR revised to S3-242585 |
vivo, InterDigital, China Mobile | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242087 | New solution on KI2 Authorization of VFL member selection |
pCR revised to S3-242587 |
vivo | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242088 | New solution to KI3 privacy of data and sample alignment |
pCR revised to S3-242593 |
vivo | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242089 | Editorial correction of TEST CASE | CR | Ericsson | 33.514 16.4.0 CR#25 catF | SCAS_5G | Rel-16 |
S3-116 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
S3-242090 | Editorial correction of TEST CASE | CR | Ericsson | 33.514 17.0.0 CR#26 catA | SCAS_5G | Rel-17 |
S3-116 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
S3-242091 | Editorial correction of TEST CASE | CR | Ericsson | 33.514 18.2.0 CR#27 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242092 | Solution for KI#1 & #2 |
pCR revised to S3-242574 |
Ericsson | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242093 | Add KI on Privacy of processing VFL intermediate data | pCR | Huawei, HiSilicon | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
merged | [WTS] [JSN] |
S3-242094 | Discussion paper on processing VFL training data using privacy computation | discussion | Huawei, HiSilicon | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
noted | [WTS] [JSN] | |
S3-242095 | New sol for KI 2 about using homomorphic technology processing user sensitive data | pCR | Huawei, HiSilicon | 33.721 0.1.0 | FS_Metaverse_Sec | Rel-19 |
S3-116 AI: 5.18 |
noted | [WTS] [JSN] |
S3-242096 | New key issue on security aspect of digital asset container in 5GC | pCR | Huawei, HiSilicon | 33.721 0.1.0 | FS_Metaverse_Sec | Rel-19 |
S3-116 AI: 5.18 |
noted | [WTS] [JSN] |
S3-242097 | Update procedure of UE privacy verification for Ranging/SL positioning service exposure through PC5 link | CR | OPPO | 33.533 18.2.0 CR#69 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
merged | [WTS] [JSN] |
S3-242098 | Correction to headings | CR | Ericsson | 33.514 17.0.0 CR#28 catF | eSCAS_5G | Rel-17 |
S3-116 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
S3-242099 | Correction to headings | CR | Ericsson | 33.514 18.2.0 CR#29 catA | eSCAS_5G | Rel-18 |
S3-116 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
S3-242100 | Discussion on security handling for inter-CU LTM in non-DC cases | discussion | OPPO |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-242101 | draft reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-241773 LS To: RAN2 |
OPPO | Rel-19 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-242102 | Solution to KI#1 Reusing existing security mechanism for LCS | pCR | China Unicom | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
withdrawn | [WTS] [JSN] |
S3-242103 | Fuzz TLS | CR | Ericsson | 33.514 18.2.0 CR#30 catF | SCAS_5G_Ph3 | Rel-18 |
S3-116 AI: 4.3 |
agreed | [WTS] [JSN] |
S3-242104 | CR to TS33.503 Update U2U Relay Discovery procedures for aligning with CT1 |
CR revised to S3-242403 |
CATT | 33.503 18.2.0 CR#179 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] |
S3-242105 | LS Reply on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-241773 LS To: RAN2 |
Ericsson | Rel-19 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-242106 | AIoT: Security assumptions for existing services in the 5G system | pCR | Ericsson | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242107 | LS on Ambient IoT |
LS out LS To: SA1 |
Ericsson | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] | |
S3-242108 | AIoT: New key issue for integrity protection of communication messages sent between AIoT device and 5G network | pCR | Ericsson | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
merged | [WTS] [JSN] |
S3-242109 | AIoT: New key issue for encryption of communication messages sent between AIoT device and 5G network | pCR | Ericsson | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
merged | [WTS] [JSN] |
S3-242110 | Solution_Authorization of AIoT capable UE in topology 2 | pCR | Ericsson | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242111 | AIoT: Security assumptions for Ambient IoT services in 5G system | pCR | Ericsson | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242112 | Regulations with digital elements in EU CRA and security requirements in NIST ZTA | pCR | Ericsson | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242113 | Solution to KI#1 Reusing existing security mechanism for LCS | pCR | China Unicom, ZTE | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
merged | [WTS] [JSN] |
S3-242114 | pCR to TR33.700-29 Update Solution#10 | pCR | CATT | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242115 | pCR to TR33.700-29 Update Solution#11 | pCR | CATT | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242116 | Remove the Editor’s note in solution 16 of TR 33.700-29 |
pCR revised to S3-242546 |
Beijing Xiaomi Mobile Software | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242117 | New solution on multi-hop U2N relay discovery security procedure |
pCR revised to S3-242525 |
Beijing Xiaomi Mobile Software | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242118 | New solution on multi-hop U2N relay security establishment procedure |
pCR revised to S3-242526 |
Beijing Xiaomi Mobile Software | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242119 | Security assumption of 5G Ambient IoT services |
pCR revised to S3-242649 |
Beijing Xiaomi Mobile Software | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] |
S3-242120 | Update KI#1 in TR 33.713 |
pCR revised to S3-242534 |
Beijing Xiaomi Mobile Software | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] |
S3-242121 | New solution on disabling operation procedure |
pCR revised to S3-242538 |
Beijing Xiaomi Mobile Software | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] |
S3-242122 | New solution on authorization of intermediate node for Ambient IoT services | pCR | Beijing Xiaomi Mobile Software | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242123 | Reply LS on clarification on home network triggered re-authentication |
LS out LS is reply to S3-241736 source LS: C4-235577 LS To: CT4 |
Beijing Xiaomi Mobile Software | Rel-18 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-242124 | Reply LS on differentiating security materials used for PC5 direct discovery for 5G ProSe UE-to-network relay |
LS out LS is reply to S3-241727 source LS: C1-242665 LS To: CT1 |
Beijing Xiaomi Mobile Software | Rel-17 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] | ||
S3-242125 | Correction on the protection mechanism for U2N relay discovery (R17) | CR | Beijing Xiaomi Mobile Software | 33.503 17.7.0 CR#180 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] |
S3-242126 | Correction on the protection mechanism for U2N relay discovery (R18) | CR | Beijing Xiaomi Mobile Software | 33.503 18.2.0 CR#181 catA | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] |
S3-242127 | Correction on the scrambing mechanism for U2U relay discovery |
CR revised to S3-242412 |
Beijing Xiaomi Mobile Software | 33.503 18.2.0 CR#182 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] |
S3-242128 | Completing the Privacy Check of n UEs for Service Exposure to Client UE |
CR revised to S3-242466 |
Xiaomi | 33.533 18.2.0 CR#70 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
revised | [WTS] [JSN] |
S3-242129 | Update to UE Privacy Verification for UE-only Operation |
CR revised to S3-242467 |
Xiaomi | 33.533 18.2.0 CR#71 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
revised | [WTS] [JSN] |
S3-242130 | PC5-U integrity protection policy for Ranging/SL positioning service |
CR revised to S3-242657 |
Xiaomi | 33.533 18.2.0 CR#72 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
revised | [WTS] [JSN] |
S3-242131 | Updating RSPP broadcast/groupcast to SLPP broadcast/groupcast |
CR revised to S3-242468 |
Xiaomi | 33.533 18.2.0 CR#73 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
revised | [WTS] [JSN] |
S3-242132 | 33.700-32: Update to Assumption | pCR | Xiaomi Technology | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
noted | [WTS] [JSN] |
S3-242133 | 33.700-32: Update to Key Issue #3 | pCR | Xiaomi Technology | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
noted | [WTS] [JSN] |
S3-242134 | 33.700-32: New Solution on User Authentication with Preconfigured Credential |
pCR revised to S3-242503 |
Xiaomi Technology | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242135 | 33.700-32: New Solution on User Authentication with Derived Credential |
pCR revised to S3-242668 |
Xiaomi Technology | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242136 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-241773 source LS: R2-2404037 LS To: RAN2 |
Xiaomi Technology | Rel-19 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-242137 | pCR to TR33.700-29 New solution dynamically generate UE subscription data for S&F operations | pCR | CATT | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
noted | [WTS] [JSN] |
S3-242138 | pCR to TR 33.713 Clause 4 Security Architecture and Assumptions | pCR | CATT | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
merged | [WTS] [JSN] |
S3-242139 | Sol on AIoT device ID protection during the AIoT device initial registration | pCR | OPPO | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-242140 | New Solution to KI#3: Privacy of VFL between VFL members |
pCR revised to S3-242594 |
Ericsson | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242141 | Correcting the selections rules for "aes-gcm-us" |
CR revised to S3-242390 |
Qualcomm Incorporated | 33.203 18.0.0 CR#282 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-242142 | Proposing some evaluation for solution #15 | pCR | Qualcomm Incorporated | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242143 | Proposed conclusion for key issue #1 | pCR | Qualcomm Incorporated | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
merged | [WTS] [JSN] |
S3-242144 | Proposed conclusion for key issue #3 | pCR | Qualcomm Incorporated | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
merged | [WTS] [JSN] |
S3-242145 | Proposed conclusion for key issue #4 | pCR | Qualcomm Incorporated | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
merged | [WTS] [JSN] |
S3-242146 | Proposed update to solution #3 | pCR | Qualcomm Incorporated | 33.700-29 0.1.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242147 | Rel17 ProSe – Update on U2N relay discovery procedure | CR | Qualcomm Incorporated | 33.503 17.7.0 CR#183 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] |
S3-242148 | Rel18 ProSe – Update on U2N relay discovery procedure | CR | Qualcomm Incorporated | 33.503 18.2.0 CR#184 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] |
S3-242149 | Update on UE role authorization during discovery |
CR revised to S3-242465 |
Qualcomm Incorporated | 33.533 18.2.0 CR#74 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
revised | [WTS] [JSN] |
S3-242150 | New Key Issue on the protection of information during AIoT service communication |
pCR revised to S3-242535 |
Qualcomm Incorporated | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] |
S3-242151 | A new solution for privacy protection of AIoT device identifier | pCR | Qualcomm Incorporated | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-242152 | A new solution for end-to-end security protection of command | pCR | Qualcomm Incorporated | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-242153 | A new solution for multihop U2N relay discovery security |
pCR revised to S3-242527 |
Qualcomm Incorporated | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242154 | A new solution for multi-hop U2N relay communication security |
pCR revised to S3-242653 |
Qualcomm Incorporated | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242155 | A new solution for multihop U2U relay discovery security |
pCR revised to S3-242532 |
Qualcomm Incorporated | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
revised | [WTS] [JSN] |
S3-242156 | A new solution for multihop U2U relay communication security | pCR | Qualcomm Incorporated | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242157 | pCR to TR33.713 New key issue on authentication of AIoT Devices | pCR | CATT | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242158 | pCR to TR33.713 New key issue on communication security of AIoT system | pCR | CATT | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
merged | [WTS] [JSN] |
S3-242159 | Sol on temporary ID based AIoT device privacy protection | pCR | OPPO | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-242160 | New Solution to KI#2: Authorization of VFL participant involving NWDAF and AF |
pCR revised to S3-242588 |
Ericsson | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242161 | Solution #1: resolution of EN in procedure | pCR | THALES | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242162 | KI on protection of training data exchange in VFL | pCR | OPPO | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
merged | [WTS] [JSN] |
S3-242163 | A new solution on authorizing the usage of base Avatar model |
pCR revised to S3-242434 |
Huawei, HiSilicon | 33.790 0.2.0 | FS_NG_RTC | Rel-19 |
S3-116 AI: 5.2 |
revised | [WTS] [JSN] |
S3-242164 | A new solution on third-party specific user identities |
pCR revised to S3-242432 |
Huawei, HiSilicon | 33.790 0.2.0 | FS_NG_RTC | Rel-19 |
S3-116 AI: 5.2 |
revised | [WTS] [JSN] |
S3-242165 | EEC provided information verification | pCR | Huawei, HiSilicon, Ericsson, Samsung, China Unicom | 33.749 0.1.0 | FS_EDGE_Ph3 | Rel-19 |
S3-116 AI: 5.14 |
merged | [WTS] [JSN] |
S3-242166 | New KI on authorization of AF outside the operator domain | pCR | Huawei, HiSilicon | 33.749 0.1.0 | FS_EDGE_Ph3 | Rel-19 |
S3-116 AI: 5.14 |
merged | [WTS] [JSN] |
S3-242167 | Removing ENs in Sol#3 of TS 33.757 | pCR | Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242168 | Addressing the EN on the impacts due to HNSPP |
pCR revised to S3-242473 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242169 | Addressing the EN on the difference btw. HNSPP and SEG |
pCR revised to S3-242474 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242170 | Discussion on unifying the name of IPX, roaming intermediary, Roaming Hub, etc. | discussion | Huawei, HiSilicon | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
noted | [WTS] [JSN] | |
S3-242171 | VFL sample alignment initialled by NWDAF |
pCR revised to S3-242595 |
OPPO | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242172 | Modification on the name of IPX, roaming intermediary, Roaming Hub, etc. |
CR revised to S3-242457 |
Huawei, HiSilicon | 33.501 18.5.0 CR#2008 catD | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
revised | [WTS] [JSN] |
S3-242173 | Reply LS on ECS Configuration Information |
LS out LS is reply to S3-241728 LS To: CT1 revised to S3-242620 |
Huawei, HiSilicon | Rel-18 |
S3-116 AI: 3 |
revised | [WTS] [JSN] | ||
S3-242174 | Removing the requirement of Roaming Hub to support session termination | CR | Huawei, HiSilicon | 33.501 18.5.0 CR#2009 catF | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
not pursued | [WTS] [JSN] |
S3-242175 | Modification on the definition of PNI-NPN Operational domain |
pCR revised to S3-242558 |
Huawei, HiSilicon, CMCC | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242176 | Update KI#2 on Authorization for exposing Energy related information |
pCR revised to S3-242577 |
Huawei, HiSilicon | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
revised | [WTS] [JSN] |
S3-242177 | Removing ENs in Sol#14 of TR 33.700-29 |
pCR revised to S3-242547 |
Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242178 | Removing EN in Sol#4 of TR 33.757 | pCR | Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242179 | Add evaluation to Sol#4 of TR 33.757 |
pCR revised to S3-242475 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242180 | Discussion on SMC based solution for an NB-IoT UE in NTN to report its location to the network | discussion | Huawei, HiSilicon | Rel-18 |
S3-116 AI: 4.1.15 |
noted | [WTS] [JSN] | ||
S3-242181 | LS on SMC based solution for an NB-IoT UE in NTN to report its location to the network |
LS out LS To: SA2,CT1 |
Huawei, HiSilicon | Rel-18 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | ||
S3-242182 | Update to the Store and forward KI: Selective forwarding scenario | pCR | Huawei, HiSilicon | 33.700-29 0.2.0 | SAT | Rel-19 |
S3-116 AI: 5.7 |
noted | [WTS] [JSN] |
S3-242183 | Update to solution on preventing DoS attacks in S&F operation | pCR | Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
merged | [WTS] [JSN] |
S3-242184 | Authorization mechanism through NRF and NEF for AF outside the PLMN |
pCR revised to S3-242589 |
Huawei, HiSilicon | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242185 | Reply LS on on Resource content filters |
LS out LS To: CT4 |
Huawei, HiSilicon | Rel-18 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | ||
S3-242186 | Clarification on the usage of N32-f message ID |
CR revised to S3-242459 |
Huawei, HiSilicon | 33.501 18.5.0 CR#2010 catF | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
revised | [WTS] [JSN] |
S3-242187 | Clarification on PLMN ID verification(R17) |
CR revised to S3-242391 |
Huawei, HiSilicon | 33.501 17.13.0 CR#2011 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-242188 | Clarification on token verification by NFp | CR | Huawei, HiSilicon | 33.501 18.5.0 CR#2012 catF | TEI18 | Rel-18 |
S3-116 AI: 4.11 |
not pursued | [WTS] [JSN] |
S3-242189 | Revision on the TS 33.526 according to the scope | CR | Huawei, HiSilicon | 33.526 18.1.0 CR#2 catF | VNP_SECAM_SCAS | Rel-18 |
S3-116 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
S3-242190 | Serving Network Name check at AUSF |
CR revised to S3-242392 |
Huawei, HiSilicon | 33.501 18.5.0 CR#2013 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-242191 | LS reply on LS on support of SSIM on eUICC |
LS out source LS: S3-241737 LS To: TCA eUICC WG revised to S3-242373 |
Nokia. Nokia Shanghai Bell |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |||
S3-242192 | LS reply to LS on LI considerations for TR 33.757 |
LS out LS is reply to S3-241751 source LS: S3-241751 LS To: SA3-LI |
Nokia. Nokia Shanghai Bell |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |||
S3-242193 | KI Authentication and identity of type 1 and 2 devices | pCR | Nokia | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242194 | Resolution to EN concerning DoS attack | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
merged | [WTS] [JSN] |
S3-242195 | Update of KI’s based on comments provided by SA3-LI |
pCR revised to S3-242469 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242196 | Solution to KI1 - Reuse SEG to protect N4 |
pCR revised to S3-242554 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242197 | Solution to KI2 – Extension of SCP |
pCR revised to S3-242555 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242198 | New WID on 5G Security Assurance Specification (SCAS) for the Container-based Products | WID new | Ericsson | Rel-19 |
S3-116 AI: 6 |
noted | [WTS] [JSN] | ||
S3-242199 | Solution on AIoT capable UE Authorization | pCR | OPPO | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242200 | AIoT security assumption of device constrains | pCR | OPPO, ZTE, Apple | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242201 | New WID on specification of new f5 function | WID new | Ericsson | Rel-19 |
S3-116 AI: 6 |
noted | [WTS] [JSN] | ||
S3-242202 | Analysis of backwards compatibility |
pCR revised to S3-242449 |
Ericsson | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
revised | [WTS] [JSN] |
S3-242203 | Conclusion | pCR | Ericsson | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
merged | [WTS] [JSN] |
S3-242204 | Reply LS on limited MSISDN exposure |
LS out LS is reply to S3-241748 LS To: SA2 |
Ericsson | eEDGE_5GC | Rel-18 |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |
S3-242205 | New key issue on EEC provided IP address verification | pCR | Ericsson | 33.749 0.1.0 | FS_EDGE_Ph3 | Rel-19 |
S3-116 AI: 5.14 |
merged | [WTS] [JSN] |
S3-242206 | Alignment on resource definition | CR | Ericsson | 33.122 18.3.0 CR#75 catF | SNAAPPY | Rel-18 |
S3-116 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
S3-242207 | Terminology alignment for 5GMSG |
CR revised to S3-242389 |
China Mobile Group Device Co. | 33.501 18.5.0 CR#2014 catF | 5GMARCH_Ph2_SEC | Rel-18 |
S3-116 AI: 4.1.15 |
revised | [WTS] [JSN] |
S3-242208 | Test Case for Intra-VNF Communication Interface | CR | Ericsson | 33.527 18.2.0 CR#5 catB | SCAS_5G_Maint | Rel-19 |
S3-116 AI: 4. |
not pursued | [WTS] [JSN] |
S3-242209 | New KI on protection of network topology information in VFL | pCR | China Mobile Group Device Co. | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
noted | [WTS] [JSN] |
S3-242210 | Topology information exposure EN resolving of KI #2 | pCR | China Mobile Group Device Co. | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
merged | [WTS] [JSN] |
S3-242211 | Add terms to TR 33.745 | pCR | China Mobile Group Device Co. | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-242212 | Evaluation for solution#1 of TR 33.757 | pCR | China Mobile Group Device Co. | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
withdrawn | [WTS] [JSN] |
S3-242213 | Evaluation for solution#5 of TR 33.757 | pCR | China Mobile Group Device Co. | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
withdrawn | [WTS] [JSN] |
S3-242214 | Resolving EN on roaming and interconnect |
draftCR revised to S3-242460 |
Nokia | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
revised | [WTS] [JSN] | |
S3-242215 | Evaluation for solution#12 of TR 33.757 | pCR | China Mobile Group Device Co. | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
withdrawn | [WTS] [JSN] |
S3-242216 | Corrections to NSWO with CH AAA |
CR revised to S3-242455 |
Ericsson | 33.501 18.5.0 CR#2015 catF | eNPN_Ph2 | Rel-18 |
S3-116 AI: 4.1.9 |
revised | [WTS] [JSN] |
S3-242217 | Evaluation for solution #1 |
pCR revised to S3-242471 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242218 | Evaluation for solution #5 |
pCR revised to S3-242476 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242219 | Evaluation for solution #12 |
pCR revised to S3-242484 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242220 | Solve EN for Key issue#1&2 |
pCR revised to S3-242470 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242221 | LS on Quantum Safe Cryptographic Protocol Inventory |
LS out LS is reply to S3-241763 LS To: ETSI TC CYBER QSC WG (ETSI QSC) revised to S3-242377 |
Ericsson |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |||
S3-242222 | LS on 3GPP studies for PQC Migration |
LS out LS To: GSMA |
Ericsson |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |||
S3-242223 | Public key distribution and Issuer claim verification of the Access Token | CR | Ericsson | 33.501 18.5.0 CR#2016 catB | TEI19 | Rel-19 |
S3-116 AI: 4.11 |
withdrawn | [WTS] [JSN] |
S3-242224 | Consistency Between NF Profile and Certificate | CR | Ericsson | 33.501 18.5.0 CR#2017 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
merged | [WTS] [JSN] |
S3-242225 | Clarification of input parameter verification for token-based authorization | CR | Erricsson | 33.501 18.5.0 CR#2018 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
merged | [WTS] [JSN] |
S3-242226 | Correcting typo in algorithm names | CR | Ericsson | 33.203 18.0.0 CR#283 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242227 | Updates of obsoleted RFCs | CR | Ericsson | 33.310 18.3.0 CR#200 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242228 | Updates of obsoleted RFCs | CR | Ericsson | 33.310 19.0.0 CR#201 catA | TEI18 | Rel-19 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242229 | Correcting incorrect reference in Section 33.501 Annex S.3.2 | CR | Ericsson | 33.501 18.5.0 CR#2019 catA | NSWO_5G | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242230 | Correcting incorrect reference in Section 33.501 Annex S.3.2 | CR | Ericsson | 33.501 17.13.0 CR#2020 catF | NSWO_5G | Rel-17 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242231 | Remove insecure usage of “aes-gcm” and “aes-gmac” and introduce HMAC-SHA-256 |
draftCR revised to S3-242414 |
Ericsson | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
revised | [WTS] [JSN] | |
S3-242232 | A user plane based solution for key issue #1 |
pCR revised to S3-242504 |
Ericsson | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242233 | New solution for key issue #2 |
pCR revised to S3-242611 |
Ericsson | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242234 | New solution for key issue #3 | pCR | Ericsson | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
withdrawn | [WTS] [JSN] |
S3-242235 | Validation of the allowed slices in the access token request at NRF | CR | Ericsson | 33.501 18.5.0 CR#2021 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 7 |
not pursued | [WTS] [JSN] |
S3-242236 | Validation of the requested slices at NF service producer | CR | Ericsson | 33.501 18.5.0 CR#2022 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 7 |
not pursued | [WTS] [JSN] |
S3-242237 | Support iat claim in the access token | CR | Ericsson | 33.501 18.5.0 CR#2023 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 7 |
not pursued | [WTS] [JSN] |
S3-242238 | Clarification of security requirement on NF Discovery response | CR | Ericsson | 33.501 18.5.0 CR#2024 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 7 |
merged | [WTS] [JSN] |
S3-242239 | Correcting wrong implementation of agreed CR |
CR revised to S3-242452 |
Erricsson | 33.501 18.5.0 CR#2025 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 7 |
revised | [WTS] [JSN] |
S3-242240 | LS on GSMA CVD-2023-0069 - 5G Core Network Attacks |
LS out LS To: GSMA CVD PoE, 3GPP CT4 |
Ericsson |
S3-116 AI: 7 |
merged | [WTS] [JSN] | |||
S3-242241 | General Authentication Requirement | pCR | OPPO | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242242 | Solve EN for solution #5 | pCR | China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242243 | discussion on UICC support for AIoT Service | discussion | OPPO |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] | |||
S3-242244 | Direct Discovery Set scrambling protection - correction | CR | Philips International B.V. | 33.503 18.2.0 CR#185 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] |
S3-242245 | A.7 in TS 33.503 - correction | CR | Philips International B.V. | 33.503 18.2.0 CR#186 catC | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242246 | Clause 6.3.6 in TS 33.503 - correction |
CR revised to S3-242641 |
Philips International B.V. | 33.503 18.2.0 CR#187 catC | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] |
S3-242247 | Security of 5G ProSe PC5 communication without network assistance - correction |
CR revised to S3-242616 |
Philips International B.V. | 33.503 18.2.0 CR#188 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] |
S3-242248 | Update of local privacy check in clause 6.3.7 for server UE request | CR | Philips International B.V. | 33.533 18.2.0 CR#75 catB | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
not pursued | [WTS] [JSN] |
S3-242249 | New solution - Human User ID authentication and authorization |
pCR revised to S3-242505 |
Philips International B.V. | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242250 | New solution - Ambient IoT ID privacy | pCR | Philips International B.V. | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-242251 | New solution - Ambient IoT device disabling mechanism |
pCR revised to S3-242539 |
Philips International B.V. | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
revised | [WTS] [JSN] |
S3-242252 | Update to new SID on security aspects for Multi-Access (DualSteer + ATSSS Ph-4) | pCR | Philips International B.V. | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] |
S3-242253 | LS on UICC in AIoT service |
LS out LS To: SA, SA1, SA2, RAN |
OPPO |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] | |||
S3-242254 | Reply LS on LI considerations for TR 33.757 |
LS out LS is reply to S3-241751 LS To: SA3-LI revised to S3-242376 |
China Mobile Group Device Co. | Rel-19 |
S3-116 AI: 3 |
revised | [WTS] [JSN] | ||
S3-242255 | Partially fill the gap analysis table of TR 33.745 | pCR | China Mobile Group Device Co. | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
merged | [WTS] [JSN] |
S3-242256 | Add onboard capabilitu to solution mappling | pCR | OPPO | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
noted | [WTS] [JSN] |
S3-242257 | New SID on security management service | SID new | China Mobile, ZTE, Nokia, Nokia Shanghai Bell, CATT, CableLabs, China Telecom |
S3-116 AI: 6 |
noted | [WTS] [JSN] | |||
S3-242258 | Reply LS on Clarification related to reliable location |
LS out LS is reply to S3-241750 source LS: S2-2309698 LS To: SA2 revised to S3-242379 |
Ericsson | ID_UAS | Rel-17 |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |
S3-242259 | Correction on negotiation of security algorithms for EN-DC (R17) | CR | CMCC | 33.401 17.4.0 CR#716 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242260 | Solution on NF Authorization in PLMN hosting NPN Scenario | pCR | Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242261 | Update to solution#9 on DNS Security in PLMN hosting NPN Scenario |
pCR revised to S3-242482 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242262 | Solution for remote attestation of dedicated NFs |
pCR revised to S3-242640 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242263 | Solution for SUPI privacy protection in PLMN hosted NPN scenario | pCR | Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242264 | New solution for SUPI privacy protection |
pCR revised to S3-242667 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242265 | Discussion paper to Revise the SID on security for PLMN hosting a NPN | discussion | Samsung | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] | |
S3-242266 | [TR 33.701] Update to security requirement of KI#1 | pCR | Samsung | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242267 | Conclusion for KI#1 in TR 33.701 | pCR | Samsung | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] |
S3-242268 | Update to Sol#4 on store and forward Satellite Operation |
pCR revised to S3-242550 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242269 | New Solution on Expedited Authentication in 5G S&F Mode |
pCR revised to S3-242643 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242270 | Resolving EN in Sol#8 |
pCR revised to S3-242548 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242271 | Evaluation on Solution #8 |
pCR revised to S3-242648 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242272 | New solution on preventing DoS attack before security context is established |
pCR revised to S3-242644 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242273 | [TR 33.700-29] Update to solution#7 | pCR | Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242274 | Evaluation to solution#7 | pCR | Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242275 | New solution on Protecting registration or attach procedure |
pCR revised to S3-242645 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
revised | [WTS] [JSN] |
S3-242276 | Key issue on broadcasting manipulated CAG IDs by the malicious Femto devices | pCR | Samsung | 33.745 0.0.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
noted | [WTS] [JSN] |
S3-242277 | New solution to handle Security Requirements of KI #1 |
pCR revised to S3-242506 |
Samsung | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242278 | Evaluation on Sol#9 |
pCR revised to S3-242599 |
Samsung | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-242279 | Evaluation on Sol#12 |
pCR revised to S3-242561 |
Samsung | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-242280 | New solution on KI#2 without AMF impact |
pCR revised to S3-242601 |
Samsung | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-242281 | New solution on KI#3 without AMF impact | pCR | Samsung | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242282 | New solution on secure IMS based avatar communication |
pCR revised to S3-242435 |
Samsung | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
revised | [WTS] [JSN] |
S3-242283 | Clarification on the authentication method(s) between EEC and ECS |
CR revised to S3-242621 |
Samsung | 33.558 18.1.0 CR#18 catF | EDGE_Ph2 | Rel-18 |
S3-116 AI: 3 |
revised | [WTS] [JSN] |
S3-242284 | [draft] Reply LS on ECS Configuration Information |
LS out LS is reply to S3-241728 source LS: C1-242674 LS To: CT1 |
Samsung |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |||
S3-242285 | Discussion on CT4 LS on Resource Content Filters | discussion | Samsung |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-242286 | [draft] Reply LS on Resource content filters |
LS out LS is reply to S3-241733 source LS: C4-241339 LS To: CT4 |
Samsung |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |||
S3-242287 | Study on security aspects of CAPIF Phase 3 |
SID new revised to S3-242660 |
Samsung | Rel-19 |
S3-116 AI: 6 |
revised | [WTS] [JSN] | ||
S3-242288 | New SID on security aspects NR mobility enhancement |
SID new revised to S3-242401 |
Samsung, OPPO | Rel-19 |
S3-116 AI: 6 |
revised | [WTS] [JSN] | ||
S3-242289 | Correction on negotiation of security algorithms for EN-DC (R18) | CR | CMCC | 33.401 18.0.0 CR#717 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242290 | Solution for Authentication, Authorization of AIoT devices with USIM on AIoT AS Layer | pCR | Lenovo | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-242291 | Evaluation of Solution#4 on store and forward Satellite Operation | pCR | Lenovo | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242292 | Public key distribution and Issuer claim verification of the Access Token | CR | Ericsson | 33.501 18.5.0 CR#2026 catB | TEI19 | Rel-19 |
S3-116 AI: 4.11 |
not pursued | [WTS] [JSN] |
S3-242293 | Update to Solution#4 on store and forward Satellite Operation | pCR | Lenovo | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
merged | [WTS] [JSN] |
S3-242294 | Reply LS on clarification on home network triggered re-authentication |
LS out LS To: CT4 revised to S3-242371 |
Ericsson | Rel-18 |
S3-116 AI: 3 |
revised | [WTS] [JSN] | ||
S3-242295 | Clarifications for HONTRA procedure with respect to failure cases |
CR revised to S3-242372 |
Ericsson | 33.501 18.5.0 CR#2027 catF | HN_Auth | Rel-18 |
S3-116 AI: 3 |
revised | [WTS] [JSN] |
S3-242296 | Adding requirements to KI#2 "Security mechanisms for policy enforcement at the 5G SBA" | pCR | Ericsson | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
merged | [WTS] [JSN] |
S3-242297 | Adding solution to KI#1 "Data exposure for security evaluation and monitoring" |
pCR revised to S3-242428 |
Ericsson | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-242298 | Resolve EN in Solution #2: Security of 3rd party specific identities | pCR | Ericsson | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
approved | [WTS] [JSN] |
S3-242299 | New solution for IMS based Avatar Communication |
pCR revised to S3-242438 |
Ericsson | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
revised | [WTS] [JSN] |
S3-242300 | Solution on UE-satellite-UE communication security | pCR | Lenovo | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
noted | [WTS] [JSN] |
S3-242301 | Solution on omitting IPsec for QUIC traffic over non-3GPP access |
pCR revised to S3-242654 |
Lenovo | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242302 | Reply-LS on LS on Resource content filters |
LS out LS is reply to S3-241733 LS To: CT4 revised to S3-242370 |
Nokia |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |||
S3-242303 | Key Issue #1: new solution | pCR | THALES | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
noted | [WTS] [JSN] |
S3-242304 | New solution for KI#3 |
pCR revised to S3-242559 |
LG Electronics | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-242305 | New solution for KI#2 |
pCR revised to S3-242562 |
LG Electronics | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
revised | [WTS] [JSN] |
S3-242306 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-241773 source LS: R2-2404037 LS To: RAN2 |
LG Electronics |
S3-116 AI: 3 |
merged | [WTS] [JSN] | |||
S3-242307 | Discussion on SGd interface at SMSF to define Diameter filtering requirements for Security Assurance Specifications for SMSF | discussion | IIT Bombay | Rel-19 |
S3-116 AI: 4.4 |
noted | [WTS] [JSN] | ||
S3-242308 | Update assumption for 256-bit algorithm indication |
pCR revised to S3-242447 |
Xiaomi Communications | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
revised | [WTS] [JSN] |
S3-242309 | New sol for KI#2_Authorization for selection of participant NWDAF instances for the 3rd party AF-initiated federated Learning |
pCR revised to S3-242590 |
Xiaomi Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242310 | New solution for KI#1 LMF authorization mechanism in the AIML model retrieving scenarios |
pCR revised to S3-242597 |
Xiaomi Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242311 | New sol for KI#2_Authorization for selection of participant AF for the NWDAF-initiated federated Learning |
pCR revised to S3-242591 |
Xiaomi Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242312 | New solution for KI#3 Privacy protect mechanism for sample alignment |
pCR revised to S3-242669 |
Xiaomi Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
revised | [WTS] [JSN] |
S3-242313 | conclusion for KI#1 | pCR | Xiaomi Communications | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
noted | [WTS] [JSN] |
S3-242314 | evaluation for solutions related to KI#1 | pCR | Xiaomi Communications | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
merged | [WTS] [JSN] |
S3-242315 | Reply LS on limited MSISDN exposure |
LS out LS is reply to S3-241748 LS To: SA2 revised to S3-242375 |
Xiaomi Communications | eEDGE_5GC | Rel-18 |
S3-116 AI: 3 |
revised | [WTS] [JSN] | |
S3-242316 | New solution for KI#2 protection for network energy related information exposure | pCR | Xiaomi Communications | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
merged | [WTS] [JSN] |
S3-242317 | New sol for KI#1_AUSF based authenticatation mechanism for UE and UPF |
pCR revised to S3-242571 |
Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242318 | New sol for KI#1_A random number based authenticatation mechanism for UE and UPF | pCR | Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] |
S3-242319 | New sol for KI#2_User plane data protection mechanism between UE and UPF |
pCR revised to S3-242655 |
Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242320 | Add evaluation for solution #8 |
pCR revised to S3-242480 |
Xiaomi Communications | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242321 | Add evaluation for solution #10 |
pCR revised to S3-242483 |
Xiaomi Communications | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242322 | Proposed solution for Certificate enrolment, Challenge validation and Certificate renewal |
pCR revised to S3-242514 |
Google Inc., John Hopkins University APL | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
revised | [WTS] [JSN] |
S3-242323 | Add a clause in annexure to Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes specific to SMSF | CR | IIT Bombay | 33.926 19.0.0 CR#97 catB | SCAS_5G_SMSF | Rel-19 |
S3-116 AI: 4.4 |
not pursued | [WTS] [JSN] |
S3-242324 | Diameter Session security requirements on SGd interface for Security Assurance Specifications for SMSF |
pCR revised to S3-242631 |
IIT Bombay | 33.529 0.4.0 | SCAS_5G_SMSF | Rel-19 |
S3-116 AI: 4.4 |
revised | [WTS] [JSN] |
S3-242325 | Add threat to local certificate checking at gNB | draftCR | Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
not pursued | [WTS] [JSN] | |
S3-242326 | Expired certificate checking at gNB to TS 33.511 |
draftCR revised to S3-242623 |
Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
revised | [WTS] [JSN] | |
S3-242327 | Add threat to expired certificate checking at gNB | draftCR | Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
noted | [WTS] [JSN] | |
S3-242328 | Peer certificate checking at gNB to TS 33.511 |
draftCR revised to S3-242624 |
Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
revised | [WTS] [JSN] | |
S3-242329 | Add threat to peer certificate checking at gNB | draftCR | Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
noted | [WTS] [JSN] | |
S3-242330 | Local certificate checking at gNB to TS 33.511 |
draftCR revised to S3-242625 |
Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
revised | [WTS] [JSN] | |
S3-242331 | new sol for KI#2 Security of IMS based Avatar Communication | pCR | Nokia, Nokia Shanghai Bell | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
withdrawn | [WTS] [JSN] |
S3-242332 | new sol for KI#X IMS DC capability exposure | pCR | Nokia, Nokia Shanghai Bell | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
withdrawn | [WTS] [JSN] |
S3-242333 | Discussion on HPLMN ID in the PC5 U2N relay discovery messages | discussion | Nokia, Nokia Shanghai Bell | Rel-17 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] | ||
S3-242334 | support cleartext HPLMN ID in PC5 U2N relay discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 17.7.0 CR#189 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242335 | support cleartext HPLMN ID in PC5 U2N relay discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 18.2.0 CR#190 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242336 | LS replay on ProSe_diffSecParam_U2N |
LS out LS is reply to S3-241727 source LS: C1-242665 LS To: CT1 |
Nokia, Nokia Shanghai Bell |
S3-116 AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-242337 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R18 | CR | Huawei, HiSilicon | 33.503 18.2.0 CR#191 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
not pursued | [WTS] [JSN] |
S3-242338 | New clause on SGd interface filtering in annexure to Security Assurance Specification (SCAS) threats specific to SMSF | CR | IIT Bombay | 33.926 19.0.0 CR#98 catB | SCAS_5G_SMSF | Rel-19 |
S3-116 AI: 4.4 |
not pursued | [WTS] [JSN] |
S3-242339 | Filtering requirements on Diameter interface for Security Assurance Specifications for SMSF |
pCR revised to S3-242632 |
IIT Bombay | 33.529 0.4.0 | SCAS_5G_SMSF | Rel-19 |
S3-116 AI: 4.4 |
revised | [WTS] [JSN] |
S3-242340 | Solution for Authentication, Authorization of AIoT devices with USIM on AIoT Layer | pCR | Lenovo | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
not treated | [WTS] [JSN] |
S3-242341 | Fix issue of scrambling operation for PC5 ProSe discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 17.7.0 CR#192 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242342 | Fix issue of scrambling operation for PC5 ProSe discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 18.2.0 CR#193 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242343 | Add clarification on scrambling operation for PC5 ProSe discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 17.7.0 CR#194 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242344 | Add clarification on scrambling operation for PC5 ProSe discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 18.2.0 CR#195 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242345 | Add clarification on encryption operation for PC5 ProSe discovery |
CR revised to S3-242410 |
Nokia, Nokia Shanghai Bell | 33.503 17.7.0 CR#196 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] |
S3-242346 | new sol for KI#2 Security of IMS based Avatar Communication |
pCR revised to S3-242436 |
Nokia, Nokia Shanghai Bell | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
revised | [WTS] [JSN] |
S3-242347 | new sol for KI#X IMS DC capability exposure |
pCR revised to S3-242437 |
Nokia, Nokia Shanghai Bell | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
revised | [WTS] [JSN] |
S3-242348 | Discussion on HPLMN ID in the PC5 U2N relay discovery messages | discussion | Nokia, Nokia Shanghai Bell | Rel-17 |
S3-116 AI: 4.1.3 |
noted | [WTS] [JSN] | ||
S3-242349 | Support cleartext HPLMN ID in PC5 U2N relay discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 17.7.0 CR#197 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] |
S3-242350 | Support cleartext HPLMN ID in PC5 U2N relay discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 18.2.0 CR#198 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
merged | [WTS] [JSN] |
S3-242351 | LS replay on ProSe_diffSecParam_U2N |
LS out LS is reply to S3-241727 source LS: C1-242665 LS To: CT1 revised to S3-242366 |
Nokia, Nokia Shanghai Bell |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] | |||
S3-242352 | Fix issue of scrambling operation for PC5 ProSe discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 17.7.0 CR#199 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
not pursued | [WTS] [JSN] |
S3-242353 | Fix issue of scrambling operation for PC5 ProSe discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 18.2.0 CR#200 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
not pursued | [WTS] [JSN] |
S3-242354 | Add clarification on encryption operation for PC5 ProSe discovery |
CR revised to S3-242411 |
Nokia, Nokia Shanghai Bell | 33.503 18.2.0 CR#201 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
revised | [WTS] [JSN] |
S3-242355 | Correcting incorrect statements about TLS profile | CR | Ericsson | 33.401 18.0.0 CR#718 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
S3-242356 | New solution for key issue #3 | pCR | Ericsson India Private Limited | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
noted | [WTS] [JSN] |
S3-242357 | TR 33.794 Cleanup |
pCR revised to S3-242430 |
Lenovo, Motorola Mobility, Johns Hopkins University APL | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
revised | [WTS] [JSN] |
S3-242358 | PLMN hosting a NPN SID Update | SID revised | Lenovo | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 6 |
noted | [WTS] [JSN] | |
S3-242359 | Authentication and authorization of non-3GPP devices |
pCR revised to S3-242615 |
Lenovo | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
revised | [WTS] [JSN] |
S3-242360 | draft reply LS on limited MSISDN exposure |
LS out LS is reply to S3-241748 LS To: SA2 |
NTT DOCOMO INC. | EDGEAPP_Ph2 | Rel-18 |
S3-116 AI: 3 |
withdrawn | [WTS] [JSN] | |
S3-242361 | Security levels vs device capabilities of Ambient IoT devices | discussion | KPN N.V. |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] | |||
S3-242362 | Disabling Peer Discovery on Diameter interface for Security Assurance Specifications for SMSF |
pCR revised to S3-242633 |
IIT Bombay | 33.529 0.4.0 | SCAS_5G_SMSF | Rel-19 |
S3-116 AI: 4.4 |
revised | [WTS] [JSN] |
S3-242363 | Recent attack on polynomial based MACs with short tag | LS in | ETSI SAGE |
S3-116 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-242364 | Response to S3-240886 LS on the introduction of the domain "ipxnetwork.org" | LS in | GSMA |
S3-116 AI: 3 |
postponed | [WTS] [JSN] | |||
S3-242365 | Detail agenda planning for SA3#116 |
other revision of S3-241704 |
SA WG3 Chair |
S3-116 AI: 1 |
noted | [WTS] [JSN] | |||
S3-242366 | LS replay on ProSe_diffSecParam_U2N |
LS out LS is reply to S3-241727 source LS: C1-242665 LS To: CT1 revision of S3-242351 |
Nokia, Nokia Shanghai Bell |
S3-116 AI: 4.1.3 |
approved | [WTS] [JSN] | |||
S3-242367 | Reply LS to S3-241726 on Mitigation of Downgrade attacks |
LS out LS is reply to S3-241726 source LS: S3-241726 LS To: CT1 revision of S3-241885 |
Apple |
S3-116 AI: 3 |
approved | [WTS] [JSN] | |||
S3-242368 | Clarification on the condition for provisioning of the ePDG identity to the UE |
CR revision of S3-241902 |
ZTE Corporation, Nokia | 33.402 18.0.0 CR#1501 catF | TEI18 | Rel-18 |
S3-116 AI: 3 |
agreed | [WTS] [JSN] |
S3-242369 | LS reply on the condition for provisioning of the ePDG identity to the UE |
LS out LS is reply to S3-241729 LS To: CT1 revision of S3-241901 |
ZTE Corporation | Rel-18 |
S3-116 AI: 3 |
approved | [WTS] [JSN] | ||
S3-242370 | Reply-LS on Resource content filters |
LS out LS is reply to S3-241733 LS To: CT4 revision of S3-242302 |
Nokia |
S3-116 AI: 3 |
noted | [WTS] [JSN] | |||
S3-242371 | Reply LS on clarification on home network triggered re-authentication |
LS out LS is reply to S3-241736 LS To: CT4 revision of S3-242294 |
Ericsson | Rel-18 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | ||
S3-242372 | Clarifications for HONTRA procedure with respect to failure cases |
CR revision of S3-242295 |
Ericsson, ZTE | 33.501 18.5.0 CR#20271 catF | HN_Auth | Rel-18 |
S3-116 AI: 3 |
not pursued | [WTS] [JSN] |
S3-242373 | LS reply on LS on support of SSIM on eUICC |
LS out LS is reply to S3-241737 source LS: S3-241737 LS To: TCA eUICC WG revision of S3-242191 |
Nokia. Nokia Shanghai Bell |
S3-116 AI: 3 |
approved | [WTS] [JSN] | |||
S3-242374 | Reply-LS on clarifications on consent management |
LS out LS is reply to S3-241741 LS To: SA revision of S3-241968 |
Nokia |
S3-116 AI: 3 |
approved | [WTS] [JSN] | |||
S3-242375 | Reply LS on limited MSISDN exposure |
LS out LS is reply to S3-241748 LS To: SA2 revision of S3-242315 |
Xiaomi Communications | eEDGE_5GC | Rel-18 |
S3-116 AI: 3 |
approved | [WTS] [JSN] | |
S3-242376 | Reply LS on LI considerations for TR 33.757 |
LS out LS is reply to S3-241751 LS To: SA3-LI revision of S3-242254 |
China Mobile Group Device Co. | Rel-19 |
S3-116 AI: 3 |
approved | [WTS] [JSN] | ||
S3-242377 | LS on Quantum Safe Cryptographic Protocol Inventory |
LS out LS is reply to S3-241763 LS To: ETSI TC CYBER QSC WG (ETSI QSC) revision of S3-242221 |
Ericsson |
S3-116 AI: 3 |
approved | [WTS] [JSN] | |||
S3-242378 | LS reply to GSMA on PQC |
LS out LS is reply to S3-241766 LS To: GSMA PQTN revision of S3-241945 |
Huawei, HiSilicon |
S3-116 AI: 3 |
approved | [WTS] [JSN] | |||
S3-242379 | Reply LS on Clarification related to reliable location |
LS out LS is reply to S3-241750 source LS: S2-2309698 LS To: SA2 revision of S3-242258 |
Ericsson | ID_UAS | Rel-17 |
S3-116 AI: 3 |
approved | [WTS] [JSN] | |
S3-242380 | Enhancement in UPU procedure to protect UPU header |
CR revision of S3-241823 |
Nokia | 33.501 18.5.0 CR#19881 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
S3-242381 | Clarification in TNGF and N3IWF procedures |
CR revision of S3-241816 |
Nokia | 33.501 17.13.0 CR#19821 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242382 | Clarification in TNGF and N3IWF procedures |
CR revision of S3-241817 |
Nokia | 33.501 18.5.0 CR#19831 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242383 | Updates to the SBA certificate profile |
CR revision of S3-241825 |
Nokia, Johns Hopkins University APL, Cisco, Ericsson | 33.310 18.3.0 CR#1972 catF | ACM_SBA | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242384 | Correction to validation of usage of X.509 certificate procedure |
CR revision of S3-241826 |
Nokia, Nokia Shanghai Bell, Ericsson, Johns Hopkins University APL, Cisco, Huawei | 33.310 18.3.0 CR#1993 catF | ACM_SBA | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242385 | Corrections and removing token claim related EN |
CR revision of S3-241965 |
Huawei, HiSilicon, Nokia | 33.122 18.3.0 CR#741 catF | SNAAPPY | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242386 | Editorial and clarificaiton of SCPAC |
CR revision of S3-241999 |
Huawei, HiSilicon | 33.501 18.5.0 CR#20051 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242387 | HTTP RFC obsoleted by IETF RFC 9110 |
CR revision of S3-242026 |
Huawei, HiSilicon, Ericsson | 33.501 18.5.0 CR#20061 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242388 | HTTP RFC obsoleted by IETF RFC 9110 |
CR revision of S3-242028 |
Huawei, HiSilicon, Ericsson | 33.210 18.0.0 CR#831 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242389 | Terminology alignment for 5GMSG |
CR revision of S3-242207 |
China Mobile, ZTE | 33.501 18.5.0 CR#20141 catF | 5GMARCH_Ph2_SEC | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242390 | Correcting the selections rules for "aes-gcm-us" |
CR revision of S3-242141 |
Qualcomm Incorporated | 33.203 18.0.0 CR#2821 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242391 | Serving Network Name check at AUSF |
CR revision of S3-242187 |
Huawei, HiSilicon | 33.501 17.13.0 CR#20111 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242392 | Serving Network Name check at AUSF |
CR revision of S3-242190 |
Huawei, HiSilicon | 33.501 18.5.0 CR#20131 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242393 | Add an OAuth2.0 test case to check for the absence of an access token | draftCR | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-116 AI: 4. |
approved | [WTS] [JSN] | |
S3-242394 | Remove unnecessary complexity from UDM test case TC_AUTH_STATUS_STORE_UDM | draftCR | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-116 AI: 4. |
approved | [WTS] [JSN] | |
S3-242395 | Corrections and additions for the N3IWF network product class |
CR revision of S3-242024 |
Huawei, HiSilicon, CAICT, China Unicom | 33.926 18.3.0 CR#951 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242396 | Corrections and additions for the N3IWF network product class |
CR revision of S3-242039 |
Huawei, HiSilicon, CAICT, China Unicom | 33.926 19.0.0 CR#961 catA | TEI18 | Rel-19 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242397 | Corrections to N3IWF SCAS |
CR revision of S3-242040 |
Huawei, HiSilicon, CAICT, China Unicom, Keysight Technologies UK Ltd | 33.520 18.0.0 CR#21 catF | TEI18 | Rel-18 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242398 | Revision on the TS 33.527 according to the scope | CR | Huawei, HiSilicon | 33.527 18.2.0 CR#6 catF | VNP_SECAM_SCAS | Rel-18 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242399 | Summary on the contributions submitted for security handling of inter-CU LTM in non-DC cases | discussion | Samsung |
S3-116 AI: 6 |
noted | [WTS] [JSN] | |||
S3-242400 | LTM-reply LS to RAN2 on LTM |
LS out LS is reply to S3-241773 source LS: R2-2404037 LS To: RAN2 revision of S3-241886 |
Apple |
S3-116 AI: 3 |
approved | [WTS] [JSN] | |||
S3-242401 | New WID on security aspects NR mobility enhancement |
WID new revision of S3-242288 |
Samsung, OPPO | Rel-19 |
S3-116 AI: 6 |
agreed | [WTS] [JSN] | ||
S3-242402 | Security Assurance Specification (SCAS) threats specific to SMSF | draftCR | IIT Bombay | SCAS_5G_SMSF | Rel-18 |
S3-116 AI: 4.4 |
approved | [WTS] [JSN] | |
S3-242403 | CR to TS33.503 Update U2U Relay Discovery procedures for aligning with CT1 |
CR revision of S3-242104 |
CATT | 33.503 18.2.0 CR#1791 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242404 | Reply LS on identifications of 5G ProSe End UEs for 5G ProSe UE-to-UE relay discovery |
LS out LS is reply to S3-241724 source LS: C1-241787 LS To: CT1, SA2 revision of S3-241996 |
Huawei, HiSilicon | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
approved | [WTS] [JSN] | |
S3-242405 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R17 | CR | Huawei, HiSilicon | 33.503 17.7.0 CR#1741 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242406 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R18 | CR | Huawei, HiSilicon | 33.503 18.2.0 CR#1911 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242407 | Add the usage of the PLMN IDs from Remote UE – R17 | CR | Huawei, HiSilicon | 33.503 17.7.0 CR#1721 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242408 | Adding the usage of the PLMN IDs from Remote UE – R18 mirror | CR | Huawei, HiSilicon | 33.503 18.2.0 CR#1731 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
S3-242409 | Clarification related to U2U discovery model B |
CR revision of S3-242067 |
China Telecom, Xiaomi | 33.503 18.2.0 CR#1781 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242410 | Add clarification on encryption operation for PC5 ProSe discovery |
CR revision of S3-242345 |
Nokia, Nokia Shanghai Bell | 33.503 17.7.0 CR#1961 catF | 5G_ProSe | Rel-17 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242411 | Add clarification on encryption operation for PC5 ProSe discovery |
CR revision of S3-242354 |
Nokia, Nokia Shanghai Bell | 33.503 18.2.0 CR#2011 catA | 5G_ProSe | Rel-18 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242412 | Correction on the scrambing mechanism for U2U relay discovery |
CR revision of S3-242127 |
Xiaomi, Philips International B.V. | 33.503 18.2.0 CR#1821 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242413 | Updates to TLS profiles on TS33210 |
other revision of S3-241782 |
Nokia, Nokia Shanghai Bell | CryptoSP |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | ||
S3-242414 | Remove insecure usage of “aes-gcm” and “aes-gmac” and introduce HMAC-SHA-256 |
draftCR revision of S3-242231 |
Ericsson | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
noted | [WTS] [JSN] | |
S3-242415 | Modernization of the Integrity Algorithms between UE and P-CSCF | draftCR | Deutsche Telekom AG | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | |
S3-242416 | Reversal of changes related to deprecated HTTP RFCs for 33.501 |
other revision of S3-242025 |
Huawei, HiSilicon | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | |
S3-242417 | Reversal of changes related to deprecated HTTP RFCs for 33.210 |
other revision of S3-242027 |
Huawei, HiSilicon | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | |
S3-242418 | Resolve EN in Use case 1 |
pCR revision of S3-241713 |
Lenovo, Motorola Mobility, Johns Hopkins University APL | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242419 | Draft TR 33.794 | draft TR | Lenovo | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] | |
S3-242420 | Updates to evaluation on massive number of calls use case |
pCR revision of S3-242035 |
Huawei, HiSilicon | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242421 | Addressing ENs in Use Case 5 |
pCR revision of S3-241867 |
US National Security Agency, MITRE Corporation, Johns Hopkins University APL | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242422 | New use case for security evaluation and monitoring: API security risks |
pCR revision of S3-241851 |
MITRE Corporation, Dell Technologies, Defense Information Systems Agency EM, US National Security Agency, Nokia, Nokia Shanghai Bell, Johns Hopkins University APL, AT&T | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242423 | Updates to eZTS Key Issue 2 |
pCR revision of S3-241852 |
MITRE Corporation, Johns Hopkins University APL, OTD_US, US National Security Agency, Nokia, Nokia Shanghai Bell,Lenovo, Motorola Mobility,Ericsson | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242424 | Solution to KI#1 Network assisted data collection |
pCR revision of S3-241715 |
Lenovo, Motorola Mobility | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242425 | Solution to KI#1_Direct data collection |
pCR revision of S3-241716 |
Lenovo, Motorola Mobility | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242426 | New solution for KI#1: New Data Collection NFs |
pCR revision of S3-241850 |
MITRE Corporation, Johns Hopkins University APL, OTD_US, US National Security Agency | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242427 | New Solution for Key Issue 1 |
pCR revision of S3-241930 |
Nokia | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242428 | Adding solution to KI#1 "Data exposure for security evaluation and monitoring" |
pCR revision of S3-242297 |
Ericsson | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242429 | New solution for KI#2: Security Policy Enforcement via NRF and SCP/NF |
pCR revision of S3-241853 |
MITRE Corporation, Johns Hopkins University APL, US National Security Agency | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
noted | [WTS] [JSN] |
S3-242430 | TR 33.794 Cleanup |
pCR revision of S3-242357 |
Lenovo, Motorola Mobility, Johns Hopkins University APL | 33.794 0.2.0 | FS_eZTS | Rel-19 |
S3-116 AI: 5.1 |
approved | [WTS] [JSN] |
S3-242431 | Draft TR 33.790 | draft TR | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
approved | [WTS] [JSN] | |
S3-242432 | A new solution on third-party specific user identities |
pCR revision of S3-242164 |
Huawei, HiSilicon | 33.790 0.2.0 | FS_NG_RTC | Rel-19 |
S3-116 AI: 5.2 |
approved | [WTS] [JSN] |
S3-242433 | Retrieval of the EASDF security information from EASDF |
CR revision of S3-241832 |
Nokia, Nokia Shanghai Bell | 33.501 18.5.0 CR#19891 catF | EDGE_Ph2 | Rel-18 |
S3-116 AI: 4.1. |
agreed | [WTS] [JSN] |
S3-242434 | A new solution on authorizing the usage of base Avatar model |
pCR revision of S3-242163 |
Huawei, HiSilicon | 33.790 0.2.0 | FS_NG_RTC | Rel-19 |
S3-116 AI: 5.2 |
approved | [WTS] [JSN] |
S3-242435 | New solution on secure IMS based avatar communication |
pCR revision of S3-242282 |
Samsung | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
approved | [WTS] [JSN] |
S3-242436 | new sol for KI#2 Security of IMS based Avatar Communication |
pCR revision of S3-242346 |
Nokia, Nokia Shanghai Bell | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
approved | [WTS] [JSN] |
S3-242437 | new sol for KI#X IMS DC capability exposure |
pCR revision of S3-242347 |
Nokia, Nokia Shanghai Bell | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
approved | [WTS] [JSN] |
S3-242438 | New solution for IMS based Avatar Communication |
pCR revision of S3-242299 |
Ericsson | 33.790 0.2.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-116 AI: 5.2 |
approved | [WTS] [JSN] |
S3-242439 | Reuse solution about policy based certificate renewal |
pCR revision of S3-241985 |
Huawei, HiSilicon | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
approved | [WTS] [JSN] |
S3-242440 | Draft TR 33.776 | draft TR | Cisco Systems | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
approved | [WTS] [JSN] | |
S3-242441 | Solution on certificate revocation |
pCR revision of S3-241799 |
Johns Hopkins University APL | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
noted | [WTS] [JSN] |
S3-242442 | Correction to terms |
CR revision of S3-241970 |
Ericsson | 33.514 16.4.0 CR#161 catF | SCAS_5G | Rel-16 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242443 | Correction to terms |
CR revision of S3-242043 |
Ericsson | 33.514 17.0.0 CR#171 catA | SCAS_5G | Rel-17 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242444 | Correction to terms |
CR revision of S3-242045 |
Ericsson | 33.514 18.2.0 CR#181 catA | SCAS_5G | Rel-18 |
S3-116 AI: 4.1.1 |
agreed | [WTS] [JSN] |
S3-242445 | addressing EN in Sol#3 |
pCR revision of S3-241952 |
Huawei, HiSilicon | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
approved | [WTS] [JSN] |
S3-242446 | Pseudo-CR on TR 33.776 Solution #2 to remove Editor's Notes |
pCR revision of S3-241779 |
Cisco Systems, US National Security Agency | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
approved | [WTS] [JSN] |
S3-242447 | Update assumption for 256-bit algorithm indication |
pCR revision of S3-242308 |
Xiaomi Communications | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
approved | [WTS] [JSN] |
S3-242448 | Draft TR 33.700-41 | draft TR | KDDI | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
approved | [WTS] [JSN] | |
S3-242449 | Analysis of backwards compatibility |
pCR revision of S3-242202 |
Ericsson | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
noted | [WTS] [JSN] |
S3-242450 | Conclusion for TR 33.700-41 |
pCR revision of S3-241789 |
KDDI Corporation | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-116 AI: 5.5 |
approved | [WTS] [JSN] |
S3-242451 | Clarification on NFDiscovery Authorization |
CR revision of S3-241949 |
Huawei, HiSilicon,Nokia,Nokia Shanghai Bell | 33.501 18.5.0 CR#20021 catF | TEI18 | Rel-18 |
S3-116 AI: 7 |
agreed | [WTS] [JSN] |
S3-242452 | Correcting wrong implementation of agreed CR |
CR revision of S3-242239 |
Erricsson, Nokia | 33.501 18.5.0 CR#20251 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 7 |
agreed | [WTS] [JSN] |
S3-242453 | LS reply on GSMA CVD-2023-0069 5G Core Network Attacks |
LS out LS is reply to S3-241764 LS To: GSMA CVD revision of S3-241947 |
Huawei, HiSilicon |
S3-116 AI: 7 |
approved | [WTS] [JSN] | |||
S3-242454 | Living document Add parameters to NRF discovery authorization | draftCR | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-116 AI: 7 |
approved | [WTS] [JSN] | |
S3-242455 | Corrections to NSWO with CH AAA |
CR revision of S3-242216 |
Ericsson | 33.501 18.5.0 CR#20151 catF | eNPN_Ph2 | Rel-18 |
S3-116 AI: 4.1.9 |
agreed | [WTS] [JSN] |
S3-242456 | Correct procedure for Authorization of selection of participant NWDAF instances in the Federated Learning group |
CR revision of S3-241979 |
Huawei, HiSilicon | 33.501 18.5.0 CR#20041 catF | eNA_Ph3_SEC | Rel-18 |
S3-116 AI: 4.1.13 |
agreed | [WTS] [JSN] |
S3-242457 | Modification on the name of IPX, roaming intermediary, Roaming Hub, etc. |
CR revision of S3-242172 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 18.5.0 CR#20081 catF | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
agreed | [WTS] [JSN] |
S3-242458 | Modified PRINS alignment with 29.573 on security profile |
CR revision of S3-241862 |
Nokia | 33.501 18.5.0 CR#19941 catF | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
agreed | [WTS] [JSN] |
S3-242459 | Clarification on the usage of N32-f message ID |
CR revision of S3-242186 |
Huawei, HiSilicon | 33.501 18.5.0 CR#20101 catF | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
not pursued | [WTS] [JSN] |
S3-242460 | Resolving EN on roaming and interconnect |
draftCR revision of S3-242214 |
Nokia | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
approved | [WTS] [JSN] | |
S3-242461 | Clarifications on NRF and NFp checks |
CR revision of S3-241842 |
Nokia, Nokia Shanghai Bell, Ericsson | 33.501 18.5.0 CR#19402 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
agreed | [WTS] [JSN] |
S3-242462 | Clarification needed on NF type handling in alignment with stage 3 |
CR revision of S3-241843 |
Nokia | 33.501 18.5.0 CR#19911 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
agreed | [WTS] [JSN] |
S3-242463 | Update Transport security protection between the two MSGin5G Servers |
CR revision of S3-241909 |
ZTE Corporation | 33.501 18.5.0 CR#20001 catF | 5GMARCH_Ph2_SEC | Rel-18 |
S3-116 AI: 4.9 |
agreed | [WTS] [JSN] |
S3-242464 | Living document of security aspects of MSGin5G service Ph3 | draftCR | China Mobile | 5GMARCH_SEC_Ph3 | Rel-19 |
S3-116 AI: 4.9 |
approved | [WTS] [JSN] | |
S3-242465 | Update on UE role authorization during discovery |
CR revision of S3-242149 |
Qualcomm Incorporated | 33.533 18.2.0 CR#741 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
agreed | [WTS] [JSN] |
S3-242466 | Completing the Privacy Check of n UEs for Service Exposure to Client UE |
CR revision of S3-242128 |
Xiaomi | 33.533 18.2.0 CR#701 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
not pursued | [WTS] [JSN] |
S3-242467 | Update to UE Privacy Verification for UE-only Operation |
CR revision of S3-242129 |
Xiaomi | 33.533 18.2.0 CR#711 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
agreed | [WTS] [JSN] |
S3-242468 | Updating RSPP broadcast/groupcast to SLPP broadcast/groupcast |
CR revision of S3-242131 |
Xiaomi | 33.533 18.2.0 CR#731 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
agreed | [WTS] [JSN] |
S3-242469 | Update of KI’s based on comments provided by SA3-LI |
pCR revision of S3-242195 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242470 | Solve EN for Key issue#1&2 |
pCR revision of S3-242220 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242471 | Evaluation for solution #1 |
pCR revision of S3-242217 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242472 | Update and evaluation to solution#2 |
pCR revision of S3-241966 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242473 | Addressing the EN on the impacts due to HNSPP |
pCR revision of S3-242168 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242474 | Addressing the EN on the difference btw. HNSPP and SEG |
pCR revision of S3-242169 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242475 | Add evaluation to Sol#4 of TR 33.757 |
pCR revision of S3-242179 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242476 | Evaluation for solution #5 |
pCR revision of S3-242218 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242477 | Update and evaluation to solution#6 |
pCR revision of S3-241967 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242478 | Update and evaluation to solution#7 |
pCR revision of S3-241969 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242479 | Evaluation for KI#2 on SBA security for solution 7 |
pCR revision of S3-241990 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242480 | Add evaluation for solution #8 |
pCR revision of S3-242320 |
Xiaomi Communications | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242481 | Evaluation for KI#2 on SBA security for solution 8 |
pCR revision of S3-241994 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242482 | Update to solution#9 on DNS Security in PLMN hosting NPN Scenario |
pCR revision of S3-242261 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242483 | Add evaluation for solution #10 |
pCR revision of S3-242321 |
Xiaomi Communications | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242484 | Evaluation for solution #12 |
pCR revision of S3-242219 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242485 | Solution to prevent bidding down to GERAN/UTRAN by restricting inter RAT handover |
pCR revision of S3-241708 |
Ericsson | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242486 | Key Issue #1: new solution |
pCR revision of S3-241837 |
THALES | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242487 | Solution to prevent bidding down by restricting UE access to GERAN/UTRAN in its location |
pCR revision of S3-241709 |
Ericsson | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242488 | Proposal to update a solution in TR 33.701 |
pCR revision of S3-241830 |
Google Inc. | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242489 | EN removal for Solution#3 |
pCR revision of S3-241922 |
Nokia | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242490 | Proposal to remove Editor’s Note and update solution in TR 33.701 | pCR | Google Inc. | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
withdrawn | [WTS] [JSN] |
S3-242491 | MiBiDA- Evaluation for solution#5 |
pCR revision of S3-241892 |
Apple | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242492 | Update to Solution#6 |
pCR revision of S3-241917 |
ZTE Corporation | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242493 | Evaluation proposal |
pCR revision of S3-242031 |
Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242494 | Coversheet for TR 33.701 |
TS or TR cover revision of S3-242038 |
Huawei, HiSilicon | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] | |
S3-242495 | User authentication and authorization of human user |
pCR revision of S3-241722 |
Lenovo | 33.700-32 0.1.0 | FS_Non3GPPMob_Sec, FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242496 | User authentication |
pCR revision of S3-241810 |
Nokia | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242497 | New Solution for User Authentication and Authorization via AMF |
pCR revision of S3-241854 |
InterDigital France R&D, SAS | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242498 | New Solution for User Authentication and Authorization via SMF |
pCR revision of S3-241855 |
InterDigital France R&D, SAS | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242499 | Solution to KI#1 and KI#2 |
pCR revision of S3-241921 |
ZTE Corporation | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242500 | new solution for User A&A |
pCR revision of S3-241960 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242501 | New soluiton to address KI#1 |
pCR revision of S3-242010 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242502 | New Solution for KI #1 of TR 33.700-32 |
pCR revision of S3-242074 |
China Telecom Corporation Ltd. | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242503 | 33.700-32: New Solution on User Authentication with Preconfigured Credential |
pCR revision of S3-242134 |
Xiaomi Technology | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242504 | A user plane based solution for key issue #1 |
pCR revision of S3-242232 |
Ericsson | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242505 | New solution - Human User ID authentication and authorization |
pCR revision of S3-242249 |
Philips International B.V. | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242506 | New solution to handle Security Requirements of KI #1 |
pCR revision of S3-242277 |
Samsung | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242507 | user profile exposure privacy issue |
pCR revision of S3-241808 |
Nokia | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242508 | User privacy during the connection with 5GC |
pCR revision of S3-241809 |
Nokia | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242509 | new solution for User privacy protection |
pCR revision of S3-241961 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242510 | Draft TR 33.757 | draft TR | China Telecom | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] | |
S3-242511 | Draft TR 33.701 | draft TR | Huawei | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] | |
S3-242512 | LS on vulnerability due to null ciphering request by network |
LS out LS To: CT1, RAN2 revision of S3-241801 |
Google Inc., Deutsche Telekom | Rel-18 |
S3-116 AI: 3 |
noted | [WTS] [JSN] | ||
S3-242513 | Propose to update a new solution text in TR 33.701 |
pCR revision of S3-241831 |
Google Inc. | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242514 | Proposed solution for Certificate enrolment, Challenge validation and Certificate renewal |
pCR revision of S3-242322 |
Google Inc., John Hopkins University APL | 33.776 0.2.0 | FS_ACME_SBA | Rel-19 |
S3-116 AI: 5.4 |
noted | [WTS] [JSN] |
S3-242515 | Draft TR 33.700-32 | draft TR | Interdigital | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] | |
S3-242516 | New solution UAV Authentication and Authorization for Multiple USS |
pCR revision of S3-241856 |
InterDigital France R&D, SAS | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
approved | [WTS] [JSN] |
S3-242517 | Draft TR 33.759 | draft TR | Ericsson | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
approved | [WTS] [JSN] | |
S3-242518 | UUAA supporting multiple USS |
pCR revision of S3-241955 |
Huawei, HiSilicon | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
approved | [WTS] [JSN] |
S3-242519 | Authorization supporting multiple USS |
pCR revision of S3-241956 |
Huawei, HiSilicon | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
approved | [WTS] [JSN] |
S3-242520 | Revocation supporting multiple USS |
pCR revision of S3-241957 |
Huawei, HiSilicon | 33.759 0.1.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-116 AI: 5.11 |
approved | [WTS] [JSN] |
S3-242521 | Draft TR 33.743 | draft TR | Huawei | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] | |
S3-242522 | New Solution on Security of multi-hop UE-to-Network Relay communication |
pCR revision of S3-241944 |
Ericsson | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242523 | New Solution for Multi-hop UE-to-Network Relay security establishment |
pCR revision of S3-242000 |
Huawei, HiSilicon | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242524 | New Solution on Security for multi-hop UE-to-Network Relay Communication |
pCR revision of S3-242070 |
China Telecom Corporation Ltd. | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242525 | New solution on multi-hop U2N relay discovery security procedure |
pCR revision of S3-242117 |
Beijing Xiaomi Mobile Software | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242526 | New solution on multi-hop U2N relay security establishment procedure |
pCR revision of S3-242118 |
Beijing Xiaomi Mobile Software | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242527 | A new solution for multihop U2N relay discovery security |
pCR revision of S3-242153 |
Qualcomm Incorporated | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242528 | New Solution for Multi-hop UE-to-UE Relay security |
pCR revision of S3-242001 |
Huawei, HiSilicon | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242529 | New Solution on Security of multi-hop UE-to-UE Relay Communication |
pCR revision of S3-242071 |
China Telecom Corporation Ltd. | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242530 | New solution for multi-hop U2U discovery |
pCR revision of S3-242068 |
China Telecom Corporation Ltd. | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242531 | Living document for CryptoSP: draftCR to TS 33.203, Updates to cryptographic profiles | draftCR | Ericsson | CryptoSP | Rel-18 |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | |
S3-242532 | A new solution for multihop U2U relay discovery security |
pCR revision of S3-242155 |
Qualcomm Incorporated | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242533 | AIoT-LS to RAN2 on AIoT assumptions |
LS out LS To: RAN2, SA2, SA1 revision of S3-241888 |
Apple |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] | |||
S3-242534 | Update KI#1 in TR 33.713 |
pCR revision of S3-242120 |
Beijing Xiaomi Mobile Software | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
approved | [WTS] [JSN] |
S3-242535 | New Key Issue on the protection of information during AIoT service communication |
pCR revision of S3-242150 |
Qualcomm Incorporated | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
approved | [WTS] [JSN] |
S3-242536 | Draft TR 33.713 | draft TR | OPPO | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
approved | [WTS] [JSN] | |
S3-242537 | solution on protection for disabling device operation |
pCR revision of S3-241976 |
Huawei, HiSilicon, China Unicom, CAICT | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242538 | New solution on disabling operation procedure |
pCR revision of S3-242121 |
Beijing Xiaomi Mobile Software | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
noted | [WTS] [JSN] |
S3-242539 | New solution - Ambient IoT device disabling mechanism |
pCR revision of S3-242251 |
Philips International B.V. | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
approved | [WTS] [JSN] |
S3-242540 | New solution for KI#2 |
pCR revision of S3-241920 |
ZTE Corporation | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
approved | [WTS] [JSN] |
S3-242541 | Solution on authorization of Intermediate UE for AIoT services |
pCR revision of S3-241938 |
OPPO Beijing | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
approved | [WTS] [JSN] |
S3-242542 | Architecture and security assumptions of TR 33.700-29 |
pCR revision of S3-241711 |
Ericsson | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242543 | New solution for mitigating UE privacy risks using temporary UE ID |
pCR revision of S3-241989 |
Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242544 | Draft TR 33.700-29 | draft TR | CATT | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] | |
S3-242545 | Addressing the editor's note and adding evaluation in solution 18 |
pCR revision of S3-241973 |
Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242546 | Remove the Editor’s note in solution 16 of TR 33.700-29 |
pCR revision of S3-242116 |
Beijing Xiaomi Mobile Software | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242547 | Removing ENs in Sol#14 of TR 33.700-29 |
pCR revision of S3-242177 |
Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242548 | Resolving EN in Sol#8 |
pCR revision of S3-242270 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242549 | Updates to Secure Initial Registration for S&F Satellite Operation |
pCR revision of S3-242059 |
Intel | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242550 | Update to Sol#4 on store and forward Satellite Operation |
pCR revision of S3-242268 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242551 | Solution 6 Evaluation |
pCR revision of S3-241926 |
Nokia | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242552 | Solution #5: evaluation |
pCR revision of S3-241835 |
THALES | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242553 | Solution #13: evaluation |
pCR revision of S3-241836 |
THALES | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242554 | Solution to KI1 - Reuse SEG to protect N4 |
pCR revision of S3-242196 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242555 | Solution to KI2 – Extension of SCP |
pCR revision of S3-242197 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242556 | New solution for SUPI privacy issue based on AMF register with UDM |
pCR revision of S3-241912 |
ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242557 | New solution for SUPI privacy issue |
pCR revision of S3-241913 |
ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242558 | Modification on the definition of PNI-NPN Operational domain |
pCR revision of S3-242175 |
Huawei, HiSilicon, CMCC | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242559 | New solution for KI#3 |
pCR revision of S3-242304 |
LG Electronics | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242560 | conclusion for KI1 and KI3 with only Fast BSS |
pCR revision of S3-241803 |
Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242561 | Evaluation on Sol#12 |
pCR revision of S3-242279 |
Samsung | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242562 | New solution for KI#2 |
pCR revision of S3-242305 |
LG Electronics | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
noted | [WTS] [JSN] |
S3-242563 | propose new solution to KI#2 |
pCR revision of S3-242015 |
Huawei, HiSilicon | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242564 | conclusion for KI2 | pCR | Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-242565 | propose conclusion to KI#4 |
pCR revision of S3-242017 |
Huawei, HiSilicon | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
noted | [WTS] [JSN] |
S3-242566 | Proposing some evaluation for solution #15 | pCR | Qualcomm Incorporated | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-242567 | Secure retrieval of 5G system UE Ids and privacy related information in the EDGE |
pCR revision of S3-241828 |
Nokia, Nokia Shanghai Bell | 33.749 0.1.0 | FS_EDGE_Ph3 | Rel-19 |
S3-116 AI: 5.14 |
approved | [WTS] [JSN] |
S3-242568 | update key issue #1 on privacy aspect |
pCR revision of S3-242013 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242569 | Address EN of key issue #2 |
pCR revision of S3-242014 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242570 | Using 3GPP security context to derive authentication pre-shared key for NIN3A |
pCR revision of S3-241983 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242571 | New sol for KI#1_AUSF based authenticatation mechanism for UE and UPF |
pCR revision of S3-242317 |
Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242572 | Solution for authentication, confidentiality, and integrity protection of UE in ATSSS while selecting MPQUIC |
pCR revision of S3-241833 |
Nokia | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242573 | Secure Authentication and Connectivity for UE in ATSSS over NIN3A |
pCR revision of S3-242058 |
Intel | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242574 | Solution for KI#1 & #2 |
pCR revision of S3-242092 |
Ericsson | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242575 | IPsec solution between UE and UPF |
pCR revision of S3-241982 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242576 | Addition of security threat to KI#1 |
pCR revision of S3-241936 |
Ericsson | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
approved | [WTS] [JSN] |
S3-242577 | Update KI#2 on Authorization for exposing Energy related information |
pCR revision of S3-242176 |
Huawei, HiSilicon | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
approved | [WTS] [JSN] |
S3-242578 | Solution reusing existing interfaces and security mechanisms for energy-related information collection |
pCR revision of S3-241937 |
Ericsson | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
approved | [WTS] [JSN] |
S3-242579 | Solution on mutual authentication and NEF-AF interface protection for exposing energy related information |
pCR revision of S3-241992 |
Huawei, HiSilicon | 33.766 0.1.0 | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
approved | [WTS] [JSN] |
S3-242580 | Solution to authenticate and secure backhaul of 5G NR Femto |
pCR revision of S3-241710 |
Ericsson | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-242581 | New Solution for UE access control using CAG verification |
pCR revision of S3-241928 |
Nokia | 33.745 0.1.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-242582 | Update to Annex A |
pCR revision of S3-242008 |
Huawei, HiSilicon | 33.702 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] |
S3-242583 | New solution for UE authorization |
pCR revision of S3-241932 |
China Unicom, ZTE | 33.721 0.1.0 | FS_Metaverse_Sec | Rel-19 |
S3-116 AI: 5.18 |
approved | [WTS] [JSN] |
S3-242584 | Address topology EN in Key Issue#2 |
pCR revision of S3-242085 |
vivo | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242585 | New key issue on Security of communication data used in VFL training process |
pCR revision of S3-242086 |
vivo, InterDigital, China Mobile | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242586 | Solutionf for VLF member authorization |
pCR revision of S3-241811 |
Nokia | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242587 | New solution on KI2 Authorization of VFL member selection |
pCR revision of S3-242087 |
vivo | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242588 | New Solution to KI#2: Authorization of VFL participant involving NWDAF and AF |
pCR revision of S3-242160 |
Ericsson,Huawei | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242589 | Authorization mechanism through NRF and NEF for AF outside the PLMN |
pCR revision of S3-242184 |
Huawei, HiSilicon | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242590 | New sol for KI#2_Authorization for selection of participant NWDAF instances for the 3rd party AF-initiated federated Learning |
pCR revision of S3-242309 |
Xiaomi Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242591 | New sol for KI#2_Authorization for selection of participant AF for the NWDAF-initiated federated Learning |
pCR revision of S3-242311 |
Xiaomi Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242592 | New solution on KI#3 Privacy of VFL between VFL members |
pCR revision of S3-241980 |
Huawei, HiSilicon | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242593 | New solution to KI3 privacy of data and sample alignment |
pCR revision of S3-242088 |
vivo | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242594 | New Solution to KI#3: Privacy of VFL between VFL members |
pCR revision of S3-242140 |
Ericsson | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242595 | VFL sample alignment initialled by NWDAF |
pCR revision of S3-242171 |
OPPO | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242596 | New solution on KI#1 Security aspects on enhancements to LCS to support AIML |
pCR revision of S3-241981 |
Huawei, HiSilicon | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242597 | New solution for KI#1 LMF authorization mechanism in the AIML model retrieving scenarios |
pCR revision of S3-242310 |
Xiaomi Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242598 | Updates to Solution #10 |
pCR revision of S3-241721 |
Lenovo | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242599 | Evaluation on Sol#9 |
pCR revision of S3-242278 |
Samsung | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242600 | solution for AUN3 device |
pCR revision of S3-242065 |
Nokia | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242601 | New solution on KI#2 without AMF impact |
pCR revision of S3-242280 |
Samsung | 33.702 0.2.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] |
S3-242602 | Draft TR 33.702 | draft TR | Nokia | FS_Non3GPPMob_Sec | Rel-19 |
S3-116 AI: 5.8 |
approved | [WTS] [JSN] | |
S3-242603 | LS on clarification on non 3GPP access mobility |
LS out LS To: SA2 |
Nokia |
S3-116 AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-242604 | Draft TR 33.749 | draft TR | China Unicom | FS_EDGE_Ph3 | Rel-19 |
S3-116 AI: 5.14 |
approved | [WTS] [JSN] | |
S3-242605 | Draft TR 33.754 | draft TR | Intel | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] | |
S3-242606 | Draft TR 33.766 | draft TR | Nokia | FS_Energy_Sec | Rel-19 |
S3-116 AI: 5.16 |
approved | [WTS] [JSN] | |
S3-242607 | Draft TR 33.745 | draft TR | ZTE | FS_5G_Femto_Sec | Rel-19 |
S3-116 AI: 5.17 |
approved | [WTS] [JSN] | |
S3-242608 | Draft TR 33.721 | draft TR | Samsung | FS_Metaverse_Sec | Rel-19 |
S3-116 AI: 5.18 |
approved | [WTS] [JSN] | |
S3-242609 | Draft TR 33.784 | draft TR | China /Mobile | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] | |
S3-242610 | New KI on privacy to non-3GPP device case |
pCR revision of S3-242011 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242611 | New solution for key issue #2 |
pCR revision of S3-242233 |
Ericsson | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242612 | Solution for authentication and authorization of non-3GPP devices behind 5G-RG |
pCR revision of S3-241874 |
CableLabs | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242613 | new solution for non-3gpp device A&A |
pCR revision of S3-241962 |
Huawei, HiSilicon | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242614 | New Solution for KI #3 of TR 33.700-32 |
pCR revision of S3-242075 |
China Telecom Corporation Ltd. | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242615 | Authentication and authorization of non-3GPP devices |
pCR revision of S3-242359 |
Lenovo | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242616 | Security of 5G ProSe PC5 communication without network assistance - correction |
CR revision of S3-242247 |
Philips International B.V. | 33.503 18.2.0 CR#1881 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242617 | Correction on unauthenticated IMS emergency sessions – R17 |
CR revision of S3-242081 |
vivo, China Telecom | 33.501 17.13.0 CR#20071 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242618 | Correction on unauthenticated IMS emergency sessions | CR | vivo, China Telecom | 33.501 18.5.0 CR#2028 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242619 | New solution on mitigation of privacy issues of interim GUTI |
pCR revision of S3-242084 |
vivo | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242620 | Reply LS on ECS Configuration Information |
LS out LS is reply to S3-241728 LS To: CT1 revision of S3-242173 |
Huawei, HiSilicon | Rel-18 |
S3-116 AI: 3 |
approved | [WTS] [JSN] | ||
S3-242621 | Clarification on the authentication method(s) between EEC and ECS |
CR revision of S3-242283 |
Samsung, Nokia | 33.558 18.1.0 CR#181 catF | EDGE_Ph2 | Rel-18 |
S3-116 AI: 3 |
agreed | [WTS] [JSN] |
S3-242622 | New key issue about UPF exposing new IP communication endpoint |
pCR revision of S3-241984 |
Huawei, HiSilicon,Deutsche Telekom | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] |
S3-242623 | Expired certificate checking at gNB to TS 33.511 |
draftCR revision of S3-242326 |
Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
noted | [WTS] [JSN] | |
S3-242624 | Peer certificate checking at gNB to TS 33.511 |
draftCR revision of S3-242328 |
Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
noted | [WTS] [JSN] | |
S3-242625 | Local certificate checking at gNB to TS 33.511 |
draftCR revision of S3-242330 |
Huawei, HiSilicon, CAICT | SCAS_5G_Maint | Rel-18 |
S3-116 AI: 4. |
noted | [WTS] [JSN] | |
S3-242626 | MPQUIC TLS Annex | draftCR | Intel | TEI18 | Rel-18 |
S3-116 AI: 3 |
withdrawn | [WTS] [JSN] | |
S3-242627 | Solution #1: resolution of ENs in evaluation part |
pCR revision of S3-241834 |
THALES | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242628 | UDR control flag for NSWO |
CR revision of S3-241820 |
Nokia, Verizon | 33.501 17.13.0 CR#19861 catF | TEI17 | Rel-17 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242629 | UDR control flag for NSWO |
CR revision of S3-241821 |
Nokia, Verizon, AT&T | 33.501 18.5.0 CR#19871 catA | TEI17 | Rel-18 |
S3-116 AI: 4.1.15 |
agreed | [WTS] [JSN] |
S3-242630 | Split between authentication and authorization |
CR revision of S3-241860 |
Nokia | 33.501 18.5.0 CR#19921 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-116 AI: 4.1.2 |
agreed | [WTS] [JSN] |
S3-242631 | Diameter Session security requirements on SGd interface for Security Assurance Specifications for SMSF |
pCR revision of S3-242324 |
IIT Bombay | 33.529 0.4.0 | SCAS_5G_SMSF | Rel-19 |
S3-116 AI: 4.4 |
approved | [WTS] [JSN] |
S3-242632 | Filtering requirements on Diameter interface for Security Assurance Specifications for SMSF |
pCR revision of S3-242339 |
IIT Bombay | 33.529 0.4.0 | SCAS_5G_SMSF | Rel-19 |
S3-116 AI: 4.4 |
approved | [WTS] [JSN] |
S3-242633 | Disabling Peer Discovery on Diameter interface for Security Assurance Specifications for SMSF |
pCR revision of S3-242362 |
IIT Bombay | 33.529 0.4.0 | SCAS_5G_SMSF | Rel-19 |
S3-116 AI: 4.4 |
approved | [WTS] [JSN] |
S3-242634 | Editorial Updates on TS 33.501 |
other revision of S3-241781 |
Nokia, Nokia Shanghai Bell | CryptoSP |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | ||
S3-242635 | Updates to Solution 11 |
pCR revision of S3-241720 |
Lenovo | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242636 | New approach for increasing user awareness |
pCR revision of S3-242033 |
Huawei, HiSilicon | 33.701 0.2.0 | FS_MiBiDA | Rel-19 |
S3-116 AI: 5.6 |
approved | [WTS] [JSN] |
S3-242637 | Addressing the editor's note on the security assumption |
pCR revision of S3-241972 |
Huawei, HiSilicon, Interdigital, Ericsson, Nokia, Nokia Shanghai Bell, Intel, CATT, Xiaomi, China Telecom | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242638 | Solution for unauthenticated DOS protection |
pCR revision of S3-241864 |
InterDigital Belgium. LLC | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242639 | New solution for AS security context establishment in satellite access with store-and-forward operations |
pCR revision of S3-241927 |
Nokia | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242640 | Solution for remote attestation of dedicated NFs |
pCR revision of S3-242262 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242641 | Clause 6.3.6 in TS 33.503 - correction |
CR revision of S3-242246 |
Philips International B.V. | 33.503 18.2.0 CR#1871 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-116 AI: 4.1.3 |
agreed | [WTS] [JSN] |
S3-242642 | New solution on secuirty protection in store and forward Satellite Operation with RAN on board |
pCR revision of S3-242042 |
Huawei, HiSilicon | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242643 | New Solution on Expedited Authentication in 5G S&F Mode |
pCR revision of S3-242269 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242644 | New solution on preventing DoS attack before security context is established |
pCR revision of S3-242272 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242645 | New solution on Protecting registration or attach procedure |
pCR revision of S3-242275 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242646 | Updates to Solution #12 |
pCR revision of S3-241939 |
OPPO Beijing | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242647 | Add evaluation to Solution #12 |
pCR revision of S3-241940 |
OPPO Beijing | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242648 | Evaluation on Solution #8 |
pCR revision of S3-242271 |
Samsung | 33.700-29 0.2.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-116 AI: 5.7 |
approved | [WTS] [JSN] |
S3-242649 | Security assumption of 5G Ambient IoT services |
pCR revision of S3-242119 |
Beijing Xiaomi Mobile Software | 33.713 0.1.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-116 AI: 5.9 |
approved | [WTS] [JSN] |
S3-242650 | New Solution for Security for multi-hop UE-to-Network Relay |
pCR revision of S3-241857 |
InterDigital France R&D, SAS | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242651 | New Solution on Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revision of S3-241942 |
Ericsson | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242652 | New Solution on Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revision of S3-241943 |
Ericsson | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242653 | A new solution for multi-hop U2N relay communication security |
pCR revision of S3-242154 |
Qualcomm Incorporated | 33.743 0.1.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-116 AI: 5.12 |
approved | [WTS] [JSN] |
S3-242654 | Solution on omitting IPsec for QUIC traffic over non-3GPP access |
pCR revision of S3-242301 |
Lenovo | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242655 | New sol for KI#2_User plane data protection mechanism between UE and UPF |
pCR revision of S3-242319 |
Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242656 | AF disabling the encryption when roaming |
CR revision of S3-241824 |
Nokia, Verizon | 33.535 18.3.0 CR#2101 catF | AKMA_Disable | Rel-18 |
S3-116 AI: 4.1.5 |
agreed | [WTS] [JSN] |
S3-242657 | PC5-U integrity protection policy for Ranging/SL positioning service |
CR revision of S3-242130 |
Xiaomi | 33.533 18.2.0 CR#721 catF | Ranging_SL_Sec | Rel-18 |
S3-116 AI: 4.1.12 |
agreed | [WTS] [JSN] |
S3-242658 | Living document on NR mobility enhancement | other | Samsung |
S3-116 AI: 6 |
approved | [WTS] [JSN] | |||
S3-242659 | New WID on Security for mobility over non-3GPP access to avoid full primary authentication |
WID new revision of S3-241791 |
Nokia | Rel-19 |
S3-116 AI: 6 |
agreed | [WTS] [JSN] | ||
S3-242660 | Study on security aspects of CAPIF Phase 3 |
SID new revision of S3-242287 |
Samsung | Rel-19 |
S3-116 AI: 6 |
agreed | [WTS] [JSN] | ||
S3-242661 | Solution for EEC provided IP address verification |
pCR revision of S3-242041 |
Huawei, HiSilicon | 33.749 0.1.0 | FS_EDGE_Ph3 | Rel-19 |
S3-116 AI: 5.14 |
approved | [WTS] [JSN] |
S3-242662 | Addition of UDR security requirements | draftCR | BSI (DE) | SCAS_5G_UDR | Rel-19 |
S3-116 AI: 4.2 |
approved | [WTS] [JSN] | |
S3-242663 | Drraft CR Add an appendix of threats to the UDR | draftCR | BSI (DE) | SCAS_5G_UDR | Rel-19 |
S3-116 AI: 4.2 |
approved | [WTS] [JSN] | |
S3-242664 | Living document for CryptoSP: draftCR to TS 33.210, Updates to cryprographic profiles |
draftCR revision of S3-241768 |
Ericsson | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | |
S3-242665 | Living document for CryptoSP: draftCR to TS 33.501, Updates to cryptographic profiles |
draftCR revision of S3-241769 |
Ericsson | CryptoSP | Rel-19 |
S3-116 AI: 4.8 |
approved | [WTS] [JSN] | |
S3-242666 | Resolving EN on roaming and interconnect | CR | Nokia | 33.501 18.5.0 CR#2029 catF | Roaming5G | Rel-18 |
S3-116 AI: 4.1.14 |
agreed | [WTS] [JSN] |
S3-242667 | New solution for SUPI privacy protection |
pCR revision of S3-242264 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242668 | 33.700-32: New Solution on User Authentication with Derived Credential |
pCR revision of S3-242135 |
Xiaomi Technology | 33.700-32 0.1.0 | FS_UIA_Sec | Rel-19 |
S3-116 AI: 5. |
approved | [WTS] [JSN] |
S3-242669 | New solution for KI#3 Privacy protect mechanism for sample alignment |
pCR revision of S3-242312 |
Xiaomi Communications | 33.784 0.1.0 | FS_AIML_CN_SEC | Rel-19 |
S3-116 AI: 5.13 |
approved | [WTS] [JSN] |
S3-242670 | Living document on SCAS for SMS | other | IIT Bombay |
S3-116 AI: 4.4 |
approved | [WTS] [JSN] |
971 documents (1.0697779655457 seconds)