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-220600 | Reserved | CR | -- | 33.203 17.1.0 CR#264 catF | TEI17 | Rel-17 |
S3-107-e AI: 7 |
withdrawn | [WTS] [JSN] |
S3-220601 | Agenda | agenda | WG Chair |
S3-107-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-220602 | Report from SA3#106e | report | MCC |
S3-107-e AI: 2 |
approved | [WTS] [JSN] | |||
S3-220603 | Process for SA3#107e meeting | other | WG Chair |
S3-107-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-220604 | Report from last SA | report | WG Chair |
S3-107-e AI: 2 |
noted | [WTS] [JSN] | |||
S3-220605 | Meeting notes from SA3 leadership | report | WG Chair |
S3-107-e AI: 2 |
reserved | [WTS] [JSN] | |||
S3-220606 | Process and agenda for SA3#107e |
other revised to S3-221142 |
WG Chair |
S3-107-e AI: 1 |
revised | [WTS] [JSN] | |||
S3-220607 | Meeting calendar |
other revised to S3-220684 |
WG Chair |
S3-107-e AI: 8 |
revised | [WTS] [JSN] | |||
S3-220608 | LS to 3GPP CT4 on Identification of source PLMN-ID in SBA | LS in | GSMA |
S3-107-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-220609 | LS on new parameters for SOR |
LS in revised to S3-220648 |
C1-214118 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220610 | Reply LS on User Controlled PLMN Selector with Access Technology in Control plane solution for steering of roaming in 5GS |
LS in revised to S3-220649 |
S1-220187 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220611 | LS on the impact of MSK update on MBS multicast session update procedure |
LS in revised to S3-220650 |
C1-221747 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |||
S3-220612 | Reply LS on UE capabilities indication in UPU |
LS in revised to S3-220651 |
C1-223177 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220613 | LS on AF specific UE ID retrieval |
LS in revised to S3-220652 |
C3-221735 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] | |||
S3-220614 | Reply LS on AF specific UE ID retrieval |
LS in revised to S3-220653 |
S6-220976 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] | |||
S3-220615 | Reply LS on AF specific UE ID retrieval |
LS in revised to S3-220654 |
S2-2203426 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] | |||
S3-220616 | LS on 5G NSWO roaming aspects |
LS in LS reply in S3-220697, S3-221220 revised to S3-220655 |
S2-2203253 |
S3-107-e AI: 4.12 |
revised | [WTS] [JSN] | |||
S3-220617 | Reply LS on 5G NSWO roaming aspects |
LS in revised to S3-220656 |
C3-222487 |
S3-107-e AI: 4.12 |
revised | [WTS] [JSN] | |||
S3-220618 | Reply LS on 5G NSWO roaming aspects |
LS in revised to S3-220657 |
C4-222436 |
S3-107-e AI: 4.12 |
revised | [WTS] [JSN] | |||
S3-220619 | LS on Clarification on MBS Security Context (MSK/MTK) Definitions |
LS in LS reply in S3-220958, S3-221155 revised to S3-220658 |
C4-222303 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |||
S3-220620 | LS on Indication of Network Assisted Positioning method |
LS in LS reply in S3-220699, S3-220985 revised to S3-220659 |
C4-222306 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] | |||
S3-220621 | LS on 3GPP TS 29.244 |
LS in revised to S3-220660 |
BBF |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220622 | Reply LS on NTN specific User Consent |
LS in revised to S3-220661 |
R2-2201754 |
S3-107-e AI: 4.13 |
revised | [WTS] [JSN] | |||
S3-220623 | LS on UE location during initial access in NTN |
LS in revised to S3-220662 |
R2-2201881 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220624 | LS on UE location during initial access in NTN |
LS in revised to S3-220663 |
R2-2202057 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220625 | Reply LS on UE location during initial access in NTN |
LS in revised to S3-220664 |
R3-222861 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220626 | LS on UE location in connected mode in NTN |
LS in revised to S3-220665 |
R2-2204257 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220627 | Reply LS on LTE User Plane Integrity Protection |
LS in revised to S3-220666 |
R2-2203663 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220628 | LS on EPS fallback enhancements |
LS in revised to S3-220667 |
R2-2204236 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220629 | Reply LS on EPS fallback enhancements |
LS in revised to S3-220668 |
S2-2203590 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220630 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS in revised to S3-220669 |
R3-222610 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220631 | Reply LS on UE providing Location Information for NB-IoT |
LS in revised to S3-220670 |
C1-222100 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220632 | Reply LS on UE providing Location Information for NB-IoT |
LS in revised to S3-220671 |
R3-222858 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220633 | LS Response to LS on UE providing Location Information for NB-IoT |
LS in revised to S3-220672 |
S2-2201333 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220634 | LS on V2X PC5 link for unicast communication with null security algorithm |
LS in revised to S3-220673 |
R5-222035 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220635 | Reply LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT |
LS in revised to S3-220674 |
S1-220185 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220636 | Reply LS on secondary authentication for multicast PDU session |
LS in revised to S3-220675 |
S2-2201311 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |||
S3-220637 | Reply LS to GSMA OPG on Further Operator Platform Group questions following SDO Workshop |
LS in revised to S3-220676 |
SP-220346 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] | |||
S3-220638 | Reply LS on Further GSMA OPAG questions following SDO Workshop |
LS in revised to S3-220677 |
S2-2201721 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] | |||
S3-220639 | LS reply on RAN2 agreements for paging with service indication |
LS in revised to S3-220678 |
S2-2201838 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220640 | Reply to LS on new reference point name for the interface between PKMF and UDM in 5G ProSe |
LS in revised to S3-220679 |
S2-2203018 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] | |||
S3-220641 | LS on MINT functionality for Disaster Roaming |
LS in revised to S3-220680 |
S5-222575 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-220642 | Reply LS to ETSI MEC on MEC Federation and interest to collaborate |
LS in revised to S3-220681 |
S6-220931 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] | |||
S3-220643 | CR on Modernization of the Integrity & Encryption Algorithms between UE and P-CSFC | CR | Deutsche Telekom AG | 33.203 17.1.0 CR#265 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220644 | New KI on Post-Quantum Secure Subscription Concealed Identifier | pCR | Deutsche Telekom AG | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-220645 | DP on Post-Quantum Secure Subscription Concealed Identifier | discussion | Deutsche Telekom AG | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
noted | [WTS] [JSN] | |
S3-220646 | DP on Modernization of the Integrity & Encryption Algorithms between UE and P-CSFC (for SIP Sessions). | discussion | Deutsche Telekom AG | TEI17 | Rel-17 |
S3-107-e AI: 4.16 |
withdrawn | [WTS] [JSN] | |
S3-220647 | LS on ETSI Plugtest #6 Observation 10.1.11 |
LS out LS To: TSG CT WG1 |
Motorola Solutions Danmark A/S | MCXSec | Rel-16 |
S3-107-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-220648 | LS on new parameters for SOR |
LS in revision of S3-220609 |
C1-214118 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220649 | Reply LS on User Controlled PLMN Selector with Access Technology in Control plane solution for steering of roaming in 5GS |
LS in revision of S3-220610 |
S1-220187 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220650 | LS on the impact of MSK update on MBS multicast session update procedure |
LS in revision of S3-220611 |
C1-221747 |
S3-107-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-220651 | Reply LS on UE capabilities indication in UPU |
LS in revision of S3-220612 |
C1-223177 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220652 | LS on AF specific UE ID retrieval |
LS in LS reply in S3-221161, S3-221161 revision of S3-220613 |
C3-221735 |
S3-107-e AI: 4.11 |
replied to | [WTS] [JSN] | |||
S3-220653 | Reply LS on AF specific UE ID retrieval |
LS in revision of S3-220614 |
S6-220976 |
S3-107-e AI: 4.11 |
noted | [WTS] [JSN] | |||
S3-220654 | Reply LS on AF specific UE ID retrieval |
LS in revision of S3-220615 |
S2-2203426 |
S3-107-e AI: 4.11 |
noted | [WTS] [JSN] | |||
S3-220655 | LS on 5G NSWO roaming aspects |
LS in LS reply in S3-221220, S3-221220 revision of S3-220616 |
S2-2203253 |
S3-107-e AI: 4.12 |
replied to | [WTS] [JSN] | |||
S3-220656 | Reply LS on 5G NSWO roaming aspects |
LS in revision of S3-220617 |
C3-222487 |
S3-107-e AI: 4.12 |
noted | [WTS] [JSN] | |||
S3-220657 | Reply LS on 5G NSWO roaming aspects |
LS in revision of S3-220618 |
C4-222436 |
S3-107-e AI: 4.12 |
noted | [WTS] [JSN] | |||
S3-220658 | LS on Clarification on MBS Security Context (MSK/MTK) Definitions |
LS in LS reply in S3-221155, S3-221155 revision of S3-220619 |
C4-222303 |
S3-107-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-220659 | LS on Indication of Network Assisted Positioning method |
LS in LS reply in S3-221254 revision of S3-220620 |
C4-222306 |
S3-107-e AI: 4.16 |
replied to | [WTS] [JSN] | |||
S3-220660 | LS on 3GPP TS 29.244 |
LS in revision of S3-220621 |
BBF |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220661 | Reply LS on NTN specific User Consent |
LS in revision of S3-220622 |
R2-2201754 |
S3-107-e AI: 4.13 |
noted | [WTS] [JSN] | |||
S3-220662 | LS on UE location during initial access in NTN |
LS in revision of S3-220623 |
R2-2201881 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220663 | LS on UE location during initial access in NTN |
LS in revision of S3-220624 |
R2-2202057 |
S3-107-e AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-220664 | Reply LS on UE location during initial access in NTN |
LS in revision of S3-220625 |
R3-222861 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220665 | LS on UE location in connected mode in NTN |
LS in LS reply in S3-221268, S3-221268 revision of S3-220626 |
R2-2204257 |
S3-107-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-220666 | Reply LS on LTE User Plane Integrity Protection |
LS in revision of S3-220627 |
R2-2203663 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220667 | LS on EPS fallback enhancements |
LS in LS reply in S3-221162, S3-220880 revision of S3-220628 |
R2-2204236 |
S3-107-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-220668 | Reply LS on EPS fallback enhancements |
LS in revision of S3-220629 |
S2-2203590 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220669 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS in revision of S3-220630 |
R3-222610 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220670 | Reply LS on UE providing Location Information for NB-IoT |
LS in revision of S3-220631 |
C1-222100 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220671 | Reply LS on UE providing Location Information for NB-IoT |
LS in revision of S3-220632 |
R3-222858 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220672 | LS Response to LS on UE providing Location Information for NB-IoT |
LS in revision of S3-220633 |
S2-2201333 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220673 | LS on V2X PC5 link for unicast communication with null security algorithm |
LS in revision of S3-220634 |
R5-222035 |
S3-107-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-220674 | Reply LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT |
LS in revision of S3-220635 |
S1-220185 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220675 | Reply LS on secondary authentication for multicast PDU session |
LS in revision of S3-220636 revised to S3-221148 |
S2-2201311 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |||
S3-220676 | Reply LS to GSMA OPG on Further Operator Platform Group questions following SDO Workshop |
LS in revision of S3-220637 |
SP-220346 |
S3-107-e AI: 4.11 |
noted | [WTS] [JSN] | |||
S3-220677 | Reply LS on Further GSMA OPAG questions following SDO Workshop |
LS in revision of S3-220638 |
S2-2201721 |
S3-107-e AI: 4.11 |
noted | [WTS] [JSN] | |||
S3-220678 | LS reply on RAN2 agreements for paging with service indication |
LS in revision of S3-220639 |
S2-2201838 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220679 | Reply to LS on new reference point name for the interface between PKMF and UDM in 5G ProSe |
LS in revision of S3-220640 |
S2-2203018 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-220680 | LS on MINT functionality for Disaster Roaming |
LS in revision of S3-220641 |
S5-222575 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220681 | Reply LS to ETSI MEC on MEC Federation and interest to collaborate |
LS in revision of S3-220642 |
S6-220931 |
S3-107-e AI: 4.11 |
noted | [WTS] [JSN] | |||
S3-220682 | LS on Inter-PLMN Handover of VoLTE calls and idle mode mobility of IMS sessions | LS in | S3i220244 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220683 | TCG progress - report from TCG rapporteur | other | InterDigital, Inc. |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-220684 | Meeting calendar |
other revision of S3-220607 |
WG Chair |
S3-107-e AI: 8 |
noted | [WTS] [JSN] | |||
S3-220685 | Clarifications to secondary authentication PDU Session Container |
CR revised to S3-221291 |
Intel Corporation (UK) Ltd | 33.501 15.15.0 CR#1357 catF | 5GS_Ph1-SEC | Rel-15 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220686 | Clarifications to secondary authentication PDU Session Container |
CR revised to S3-221292 |
Intel Corporation (UK) Ltd | 33.501 16.10.0 CR#1358 catA | 5GS_Ph1-SEC | Rel-16 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220687 | Clarifications to secondary authentication PDU Session Container |
CR revised to S3-221293 |
Intel Corporation (UK) Ltd | 33.501 17.5.0 CR#1359 catA | 5GS_Ph1-SEC | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220688 | Clarifications to secondary authentication for UE onboarding | CR | Intel Corporation (UK) Ltd | 33.501 17.5.0 CR#1360 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
merged | [WTS] [JSN] |
S3-220689 | New test case for confidentiality, integrity and replay protection between AAnF and AUSF |
pCR revised to S3-221156 |
Keysight Technologies UK Ltd | 33.537 0.0.0 | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
revised | [WTS] [JSN] |
S3-220690 | New threat for confidentiality, integrity and replay between AAnF and AUSF | CR | Keysight Technologies UK Ltd | 33.926 17.3.0 CR#53 catB | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
not pursued | [WTS] [JSN] |
S3-220691 | New test case for confidentiality, integrity and replay protection between AF/NEF and AAnF |
pCR revised to S3-221159 |
Keysight Technologies UK Ltd | 33.537 0.0.0 | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
revised | [WTS] [JSN] |
S3-220692 | New threat for confidentiality, integrity and replay between AAnF and AF/NEF | CR | Keysight Technologies UK Ltd | 33.926 17.3.0 CR#54 catB | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
not pursued | [WTS] [JSN] |
S3-220693 | Aligning text for AKMA procedure | CR | Nokia, Nokia Shanghai Bell | 33.535 17.5.0 CR#125 catF | AKMA | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220694 | Clarification on anonymization api |
CR revised to S3-221215 |
Nokia, Nokia Shanghai Bell | 33.535 17.5.0 CR#126 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220695 | UPU procedure alignment | CR | Nokia, Nokia Shanghai Bell | 33.501 16.10.0 CR#1361 catF | TEI16 | Rel-16 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220696 | UPU procedure alignment | CR | Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#1362 catA | TEI16 | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220697 | LS reply on 5G NSWO roaming aspects |
LS out LS is reply to S3-220616 LS To: SA2 revised to S3-221220 |
Nokia, Nokia Shanghai Bell | TEI17 | Rel-17 |
S3-107-e AI: 4.12 |
revised | [WTS] [JSN] | |
S3-220698 | NSWO alignment with SA2 specs |
CR revised to S3-221216 |
Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#1363 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-220699 | LS reply on High-reliability requirement of UAV |
LS out LS is reply to S3-220620 LS To: CT4, SA2 |
Nokia, Nokia Shanghai Bell | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
merged | [WTS] [JSN] | |
S3-220700 | High-reliability requirement of UAV | CR | Nokia, Nokia Shanghai Bell | 33.256 17.0.0 CR#1 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220701 | New content for Terms clause on key properties of privacy | pCR | InterDigital, Inc. | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-220702 | TR 33.870 – Informative Annex A | pCR | InterDigital, Inc. | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-220703 | New key issue on TMGI Privacy | pCR | InterDigital, Inc., Convida | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-220704 | New key issue on PIN ID Privacy | pCR | InterDigital, Inc. | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-220705 | Evaluation of Solution #5 | pCR | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | 33.848 0.11.0 | FS_SIV | Rel-16 |
S3-107-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-220706 | Clarify relationship between KAUSF, KAUSF_P and 5G PRUK | pCR | China Telecomunication Corp. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220707 | Clarify the necessity of refreshing 5G PRUK during CP-based Security Procedure | pCR | China Telecomunication Corp. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220708 | New KI on Home network triggered primary authentication | pCR | China Telecomunication Corp. | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220709 | New SID on Personal IoT Networks Security Aspects |
SID new revision of S3-220133 revised to S3-221265 |
vivo, Apple, ZTE, Xiaomi, CATT, OPPO, China Unicom, China Telecom, CableLabs, InterDigital, LGE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola mobility, Philips | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-220710 | Addressing the editor’s note in 6.27.2.1.1 of Sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-220711 | Addressing the editor’s note in 6.27.2.1.7 of sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-220712 | Addressing the editor’s note in 6.27.2.2.1of Sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-220713 | Addressing the editor’s note #1 in 6.27.2.2.4 of Sol#27 | pCR | CableLabs, Deutsche Telekom | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-220714 | Addressing the editor’s note #2 in 6.27.2.2.4 of Sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-220715 | Removing incorrect texts in 6.27.2.2.4 of Sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-220716 | Removing redundant texts in 6.27.2.2.4 of Sol# | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-220717 | Removing unrelated texts in 6.27.2.2.4 of Sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-220718 | LS out on authenticity and replay protection of system information |
LS out LS To: RAN2 |
CableLabs, Deutsche Telekom, Philips International B.V. | FS_5GFBS | Rel-18 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] | |
S3-220719 | New SID: Study on SNAAPP securitY |
SID new revised to S3-221179 |
NTT DOCOMO INC. |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | |||
S3-220720 | Key issue on Security for data and analytics exchange in roaming | pCR | Nokia, Nokia Shanghai Bell | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-220721 | Key issue on Security for AIML model storage | pCR | Nokia, Nokia Shanghai Bell | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-220722 | Key issue on Security for AIML model sharing |
pCR revised to S3-221221 |
Nokia, Nokia Shanghai Bell | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-220723 | Key issue on Anomalous NF behaviour detection by NWDAF |
pCR revised to S3-221222 |
Nokia, Nokia Shanghai Bell | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-220724 | Clarification on separate handling of N32-c and N32-f |
CR revision of S3-220589 |
Nokia, Nokia Shanghai Bell, Ericsson, Mavenir, Lenovo, Deutsche Telekom, NCSC, Xiaomi, BT, AT&T, Interdigital | 33.501 15.15.0 CR#13322 catF | TEI15 | Rel-15 |
S3-107-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-220725 | Clarification on separate handling of N32-c and N32-f |
CR revision of S3-220590 |
Nokia, Nokia Shanghai Bell, Ericsson, Mavenir, Lenovo, Deutsche Telekom, NCSC, Xiaomi, BT, AT&T, Interdigital | 33.501 16.10.0 CR#13332 catA | TEI15 | Rel-16 |
S3-107-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-220726 | Clarification on separate handling of N32-c and N32-f |
CR revision of S3-220591 |
Nokia, Nokia Shanghai Bell, Ericsson, Mavenir, Lenovo, Deutsche Telekom, NCSC, Xiaomi, BT, AT&T, Interdigital | 33.501 17.5.0 CR#13342 catA | TEI15 | Rel-17 |
S3-107-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-220727 | Security improvements of N32 connection | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.1.0 | 5G_eSBA | Rel-18 |
S3-107-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-220728 | Authorization of N32-f connection establishment with TLS |
CR revised to S3-221283 |
Nokia, Nokia Shanghai Bell | 33.501 16.10.0 CR#1364 catF | TEI16 | Rel-16 |
S3-107-e AI: 4.14 |
revised | [WTS] [JSN] |
S3-220729 | Authorization of N32-f connection establishment with TLS |
CR revised to S3-221285 |
Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#1365 catA | TEI16 | Rel-17 |
S3-107-e AI: 4.14 |
revised | [WTS] [JSN] |
S3-220730 | Resolution EN authorization method negotiation per KI7-Sol9 | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.1.0 | 5G_eSBA | Rel-18 |
S3-107-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-220731 | Resolving EN on authorization between SCPs | CR | Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#1366 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.14 |
merged | [WTS] [JSN] |
S3-220732 | New sol. for KI7 on authorization mechanism negotiation | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.1.0 | 5G_eSBA | Rel-18 |
S3-107-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-220733 | Conclusion on authorization method negotiation | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.1.0 | 5G_eSBA | Rel-18 |
S3-107-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-220734 | Update Security procedure over CP with using PRUK ID in DCR | pCR | InterDigital, Europe, Ltd.,, Samsung, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson, Verizon Wireless, MITRE, Convida Wireless LLC, Philips International B.V. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220735 | 5GPRUK/5GPRUK ID Storage Options and Way Forward | discussion | InterDigital, Europe, Ltd., Ericsson | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | ||
S3-220736 | PAnF supported services discussion | discussion | InterDigital, Europe, Ltd. | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | ||
S3-220737 | Update Security procedure over CP with using PRUK ID in DCR (alt#2) | pCR | InterDigital, Europe, Ltd. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220738 | New KI on Topology Hiding in Data and Analytics Exchange | pCR | China Telecommunications | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-220739 | Adding a test case for gNB in TS 33.511 clause 4.2.2.1.4 | CR | ZTE Corporation | 33.511 17.1.0 CR#27 catB | SCAS_5G_Ph2 | Rel-18 |
S3-107-e AI: 4.4 |
not pursued | [WTS] [JSN] |
S3-220740 | New KI on authorization of selection of participant NWDAF instances in the Federated Learning group |
pCR revised to S3-221176 |
China Telecommunications | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-220741 | Adding AAnF critical assets and threats to TS 33.926 | CR | ZTE Corporation | 33.926 17.3.0 CR#55 catB | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
withdrawn | [WTS] [JSN] |
S3-220742 | Adding Network product class description for the AAnF to TS 33.926. | CR | ZTE Corporation | 33.926 17.3.0 CR#56 catB | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
withdrawn | [WTS] [JSN] |
S3-220743 | AKMA subscription asynchronization_Test_Case | pCR | ZTE Corporation | 33.537 0.0.0 | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
noted | [WTS] [JSN] |
S3-220744 | Add some context about 5G PRUK ID reject cases in the clause 6.3.3.3.2 | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220745 | Clarification on AUSF instance store in UDM | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220746 | Remove the EN in the clause 6.3.3.2.2 | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220747 | Update the clause 6.3.3.3.3 | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220748 | Update the clause 7.4.2 | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220749 | Correction on clause F.2.1 in TS 33.926-R16 | CR | ZTE Corporation | 33.926 16.4.0 CR#57 catF | SCAS_5G | Rel-16 |
S3-107-e AI: 4.15 |
agreed | [WTS] [JSN] |
S3-220750 | Correction on clause F.2.1 in TS 33.926-R17 mirror | CR | ZTE Corporation | 33.926 17.3.0 CR#58 catA | SCAS_5G | Rel-17 |
S3-107-e AI: 4.15 |
agreed | [WTS] [JSN] |
S3-220751 | Update the test case in TS 33.216 clause 4.2.2.1.10 | CR | ZTE Corporation | 33.216 16.7.0 CR#24 catF | SCAS_eNB | Rel-16 |
S3-107-e AI: 4.15 |
not pursued | [WTS] [JSN] |
S3-220752 | Correct AAnF service in clause 6.3 |
CR revised to S3-221227 |
ZTE Corporation | 33.535 17.5.0 CR#127 catF | AKMA | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220753 | NF selects AAnF in clause 6.7 |
CR revised to S3-221228 |
ZTE Corporation | 33.535 17.5.0 CR#128 catF | AKMA | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220754 | Key issue on authorization in multi-path transmission for UE-to-Network Relay scenario | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Sec | Rel-18 |
S3-107-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-220755 | Key issue on authorization in the UE-to-UE relay scenario | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Sec | Rel-18 |
S3-107-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-220756 | Key issue on Integrity and confidentiality of information over the UE-to-UE Relay | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Sec | Rel-18 |
S3-107-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-220757 | Key issue on Privacy of information over the UE-to-UE Relay | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Sec | Rel-18 |
S3-107-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-220758 | Key issue on Support direct communication path switching between PC5 and Uu | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Sec | Rel-18 |
S3-107-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-220759 | New solution on key issue SUPI length disclosed by SUCI. | pCR | China Southern Power Grid Co., Ltd, ZTE | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-220760 | Discussion paper on AKMA application context removal. | pCR | ZTE Corporation | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-220761 | Discussion paper on AKMA interworking | pCR | ZTE Corporation | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-220762 | New KI on AKMA interworking | pCR | ZTE Corporation | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-220763 | Key issue on security of EAS Discovery Procedure with EASDF | pCR | ZTE Corporation | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-220764 | Revised SID on AKMA phase2 | SID revised | ZTE Corporation | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | |
S3-220765 | Adding authorization for delegated discovery | CR | China Telecommunications | 33.501 16.10.0 CR#1367 catF | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-220766 | Adding authorization for delegated discovery(mirror) | CR | China Telecommunications | 33.501 17.5.0 CR#1368 catA | 5G_eSBA | Rel-17 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-220767 | Adding AAnF critical assets and threats to TS 33.926 | draftCR | ZTE Corporation | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
noted | [WTS] [JSN] | |
S3-220768 | Adding Network product class description for the AAnF to TS 33.926 | draftCR | ZTE Corporation | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-220769 | Supplement to generic virtualised network product model | pCR | China Telecom Corporation Ltd. | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220770 | Clarification on the description about AAnF |
CR revised to S3-221203 |
China Telecom Corporation Ltd. | 33.535 17.5.0 CR#129 catF | AKMA | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220771 | draft_TR_33.738- skeleton for eNA security ph3 | draft TR | China Mobile | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-220772 | Scope of TR 33.738 | pCR | China Mobile | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-220773 | Overview of TR 33.738 | pCR | China Mobile | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-220774 | KI on Protection of data and analytics exchange in roaming case |
pCR revised to S3-221269 |
China Mobile | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-220775 | Proposal to add overview in clause 4 Generic Virtulizated Network Product(GVNP) class | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220776 | Proposal to add clause 4.2 Minimum set of functions defining the GVNP class | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220777 | Proposal to add introduction in clause 4.3 Generic virtualized network product model | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220778 | Proposal to add GVNP model of type 1 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220779 | Proposal to add GVNP model of type 2 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220780 | Proposal to add GVNP model of type 3 | pCR | China Mobile | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220781 | adding overview and Scope of a SECAM SCAS for 3GPP virtualized network products | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220782 | adding Scope of SECAM evaluation and accreditation for 3GPP virtualized network products | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220783 | adding the contents of chapters 4.5 to 4.7 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220784 | adding the contents of chapters 4.8 to 4.10 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220785 | adding content to clause 5.1 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220786 | Adding description about general content of SCAS document and ToE to clause 5.2 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220787 | adding description about SPD to clause 5.2 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220788 | adding description about methodology of security requirements to clause 5.2 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220789 | adding description about improvement of SCAS and new potential security requirements to clause 5.3 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220790 | adding description about basic vulnerability testing requirements for GVNP to clause 5.4 | pCR | China Mobile | 33.936 0.2.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220791 | New SID on Study on XR Security | SID new | China Mobile | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-220792 | Update to solution #25 | pCR | Huawei, HiSilicon | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-220793 | Evaluation of solution #4 | pCR | Huawei, HiSilicon | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-220794 | Conclusion for KI#3 | pCR | Huawei, HiSilicon | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-220795 | KI#2 update - threats and requirements |
pCR revised to S3-221181 |
Huawei, HiSilicon | 33.874 0.6.0 | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-220796 | New solution for part 1 of KI#2 | pCR | Huawei, HiSilicon | 33.874 0.6.0 | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-220797 | New solution for part 2 of KI#2 | pCR | Huawei, HiSilicon | 33.874 0.6.0 | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-220798 | Conclusion for part 2 of KI#2 |
pCR revised to S3-221184 |
Huawei, HiSilicon | 33.874 0.6.0 | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-220799 | Address EN on alignment to SA2 | CR | Huawei, HiSilicon | 33.501 17.5.0 CR#1369 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-220800 | Address EN on AF Authorization | CR | Huawei, HiSilicon | 33.501 17.5.0 CR#1370 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-220801 | Discussion on Rel-18 study for network slicing security | discussion | Huawei, HiSilicon, Lenovo, CATT, CAICT, China Mobile, China Unicom, InterDigital, NEC, Nokia | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-220802 | New SID: Rel-18 study for network slicing security |
SID new revised to S3-221178 |
Huawei, HiSilicon, Lenovo, CATT, CAICT, China Mobile, China Unicom, InterDigital, NEC, Nokia | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-220803 | Address EN on UAV ID | CR | Huawei, HiSilicon | 33.256 17.0.0 CR#2 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220804 | Address EN on UAV re-auth | CR | Huawei, HiSilicon | 33.256 17.0.0 CR#3 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
merged | [WTS] [JSN] |
S3-220805 | Issue of NSSAA in multiple registration | discussion | Huawei, HiSilicon | Rel-16 |
S3-107-e AI: 4.16 |
noted | [WTS] [JSN] | ||
S3-220806 | Include SN ID in NSSAA procedure | CR | Huawei, HiSilicon | 33.501 16.10.0 CR#1371 catF | eNS | Rel-16 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220807 | AAnF sending GPSI to internal AKMA AF | CR | China Mobile | 33.535 17.5.0 CR#130 catF | AKMA | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220808 | Skeleton for TS33.537(SCAS for AAnF) | draft TS | China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-220809 | Scope of TS 33.537 | pCR | China Mobile | 33.537 0.0.0 | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-220810 | Skeleton for TR 33.737(AKMA ph2) | draft TR | China Mobile | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-220811 | Scope of TR 33.737 |
pCR revised to S3-221288 |
China Mobile | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-220812 | Architectural Asumptions in TR 33.737 | pCR | China Mobile | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-220813 | Key issue of AKMA roaming | pCR | China Mobile | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-220814 | Key issue of introducing application proxy into AKMA |
pCR revised to S3-221289 |
China Mobile | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-220815 | EN resolution for Secondary Authentication for Remote UE with L3 U2N relay without N3IWF(Alt1) | pCR | LG Electronics Inc. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220816 | EN resolution for Secondary Authentication for Remote UE with L3 U2N relay without N3IWF(Alt2) |
pCR revised to S3-221174 |
LG Electronics Inc. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220817 | Revocation_ReAuth for Secondary Authentication for Remote UE |
pCR revised to S3-221175 |
LG Electronics Inc. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220818 | Summary for Non-Seamless WLAN offload authentication in 5GS | WI summary | Nokia Solutions & Networks (I) | NSWO_5G | Rel-17 |
S3-107-e AI: 4.12 |
noted | [WTS] [JSN] | |
S3-220819 | A use case of HONTRA in SoR protection service suspension | pCR | LG Electronics France | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220820 | A Key issue in SoR protection service suspension | pCR | LG Electronics France | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220821 | A use case of HONTRA in UPU protection service suspension | pCR | LG Electronics France | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220822 | A Key issue in UPU protection service suspension | pCR | LG Electronics France | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220823 | New KI for security of certificate update |
pCR revised to S3-221236 |
Huawei, HiSilicon | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-220824 | New KI for Security protection of certificate enrolment |
pCR revised to S3-221237 |
Huawei, HiSilicon | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-220825 | Integrity protection of DCR message | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220826 | Clarification on the privacy protection of DCR | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220827 | Delete of CP based solution | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220828 | Delete of Secondary authentication | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220829 | Address EN of secondary authentication | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220830 | Add a new clause for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support |
pCR revised to S3-221238 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220831 | Skeleton of HNTRA | pCR | Huawei, HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-220832 | Scope of HNTRA | pCR | Huawei, HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-220833 | Adding a usecase of interworking from EPS to 5G | pCR | Huawei, HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220834 | KI on Scalability of the home triggered primary authentication |
pCR revised to S3-221239 |
Huawei, HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-220835 | Adding a usecase of Kakma refresh |
pCR revised to S3-221240 |
Huawei, HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-220836 | KI on Signalling overhead | pCR | Huawei, HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220837 | Format of anonymous SUCI | CR | Huawei, HiSilicon | 33.501 17.5.0 CR#1372 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-220838 | LS on anonymous SUCI |
LS out LS To: CT4 |
Huawei, HiSilicon | Rel-17 |
S3-107-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-220839 | Modfiy Scope of TS 33.527 | pCR | Huawei, HiSilicon | 33.527 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220840 | Modfiy Scope of TR 33.936 | pCR | Huawei, HiSilicon | 33.936 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220841 | Modfiy Scope of TS 33.927 | pCR | Huawei, HiSilicon | 33.927 0.1.0 | VNP_SECAM_SCAS | Rel-18 |
S3-107-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-220842 | Adding UDM Services for SUCI deconceal and authorization information retrieval |
pCR revised to S3-221241 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220843 | Remote UE Identity provisioning in UE-to-Network Relay communication security procedure over user plane | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220844 | Remote UE authorization check in UE-to-Network Relay communication security procedure over control plane | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-220845 | Resolving the EN on the needs and usage of 5GPRUK ID |
pCR revised to S3-221242 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220846 | Format of 5GPRUK ID |
pCR revised to S3-221243 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220847 | Clarification on restricted discovery procedures | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220848 | Clarification on the security of L2 U2NW |
pCR revised to S3-221244 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220849 | Rel-16 Add clarifications to unicast procedures | CR | Huawei, HiSilicon | 33.536 16.4.0 CR#27 catF | eV2XARC | Rel-16 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220850 | Key derivation related clarification in CP-based UE-to-Network relay procedures |
pCR revised to S3-221245 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220851 | Add subclause about the restricted discovery for UE-to-Network relay | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220852 | Terminology alignment for 5G ProSe Remote UE specific authentication | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-220853 | New WID on Security aspects of 5G Isolated operation for public safety (IOPS) | WID new | Huawei, HiSilicon | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-220854 | Discussion paper on 5G IOPS | discussion | Huawei, HiSilicon | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-220855 | Clarification | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
withdrawn | [WTS] [JSN] |
S3-220856 | New SID on security enhancements for 5G multicast-broadcast services Phase 2 |
SID new revised to S3-221246 |
Huawei, HiSilicon | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-220857 | New SID on security enhancements for 5GC LoCation Services Phase 3 | SID new | Huawei, HiSilicon | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-220858 | Removing the Editor’s Note and add clarifications in the security mechanisms for MBS |
CR revised to S3-221247 |
Huawei, HiSilicon | 33.501 17.5.0 CR#1373 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-220859 | Clarifications on the control-plane and user-plane procedures |
CR revised to S3-221248 |
Huawei, HiSilicon | 33.501 17.5.0 CR#1374 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-220860 | Enhancement for service announcement |
CR revised to S3-221249 |
Huawei, HiSilicon | 33.501 17.5.0 CR#1375 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-220861 | Alignment with RAN2 for LTE UP IP | CR | Huawei, HiSilicon | 33.401 17.1.0 CR#705 catF | UPIP_SEC_LTE | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220862 | Address EN for LTE UP IP | CR | Huawei, HiSilicon | 33.401 17.1.0 CR#706 catF | UPIP_SEC_LTE | Rel-17 |
S3-107-e AI: 4.16 |
merged | [WTS] [JSN] |
S3-220863 | Address Ens for NPN | CR | Huawei, HiSilicon | 33.501 17.5.0 CR#1376 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-220864 | Address EN for UC3S | CR | Huawei, HiSilicon | 33.501 17.5.0 CR#1377 catF | UC3S_SEC | Rel-17 |
S3-107-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-220865 | Clarification on Enforcement Point for User Consent | CR | Huawei, HiSilicon | 33.501 17.5.0 CR#1378 catF | UC3S_SEC | Rel-17 |
S3-107-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-220866 | Update for solution 5 |
pCR revised to S3-221250 |
Huawei, HiSilicon | 33.848 0.11.0 | FS_SIV | Rel-16 |
S3-107-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-220867 | New SID on Enhancement of User Consent for 3GPP Services |
SID new revised to S3-221251 |
Huawei, HiSilicon | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-220868 | Clarification on KAUSF_P | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220869 | Clarification on PRUK ID |
pCR revised to S3-221252 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220870 | Clarifications on the multicast security context handling in session creation procedure |
CR revised to S3-221253 |
Huawei, HiSilicon | 33.501 17.5.0 CR#1379 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-220871 | Reply LS on security architecture for 5G multicast-broadcast services |
LS out source LS: S4-220531 LS To: SA4 revised to S3-221158 |
Huawei, HiSilicon | Rel-17 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | ||
S3-220872 | Reply LS on the Indication of Network Assisted Positioning method |
LS out LS is reply to S3-220659 source LS: C4-222306 LS To: CT4, SA2 revised to S3-221254 |
Huawei, HiSilicon | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] | ||
S3-220873 | Rel-17 Add clarifications to unicast procedures | CR | Huawei, HiSilicon | 33.536 17.0.0 CR#28 catA | eV2XARC | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220874 | Security capability negotiation during unicast establishment after restricted discovery | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220875 | Delete Use Case on Finding the right NF instance are serving the UE | CR | Huawei, HiSilicon | 33.521 17.1.0 CR#3 catF | SCAS_5G_NWDAF | Rel-17 |
S3-107-e AI: 4.15 |
agreed | [WTS] [JSN] |
S3-220876 | Delete Threat Analysis on Finding the right NF instance are serving the UE | CR | Huawei, HiSilicon | 33.926 17.3.0 CR#59 catF | SCAS_5G_NWDAF | Rel-17 |
S3-107-e AI: 4.15 |
agreed | [WTS] [JSN] |
S3-220877 | new KI on Authentication and Authorization when EHE in a VPLMN | pCR | Huawei, HiSilicon | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-220878 | New KI on Security for DNS server IP address | pCR | Huawei, HiSilicon | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
merged | [WTS] [JSN] |
S3-220879 | Disucssion on security aspect of EPS fallback enhancements in Rel-17 | discussion | Huawei, HiSilicon | Rel-17 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-220880 | LS to RAN2 on EPS fallback enhancements |
LS out LS is reply to S3-220667 LS To: RAN2, SA2, CT1 |
Huawei, HiSilicon | Rel-17 |
S3-107-e AI: 3 |
merged | [WTS] [JSN] | ||
S3-220881 | Clarification on the description of PRUK |
pCR revised to S3-221255 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220882 | Clarification on the secondary authentication procedure |
pCR revised to S3-221256 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220883 | Update general clause for secondary authentication |
pCR revised to S3-221257 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220884 | Discussion paper on security enhancements for 5GC LoCation Services Phase 3 | discussion | Huawei, HiSilicon | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-220885 | 33.926-Clarifications of the scope of OAM functions in the GNP model | draftCR | Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-220886 | 33.926-Rewrite the 5G MnF GNP model |
draftCR revised to S3-221258 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-220887 | 33.926-Add new assets to the OAM functions |
draftCR revised to S3-221259 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-220888 | 33.926-Add a new threat |
draftCR revised to S3-221260 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-220889 | 33.526 - update clause 4.2.3 | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] |
S3-220890 | 33.526 - update clause 4.2.4 | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] |
S3-220891 | 33.526 - update clause 4.2.5 | pCR | Huawei, HiSilicon | 33.526 0.2.0 | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] |
S3-220892 | Adding a usecase of SoR Counter Wrap around |
pCR revised to S3-221261 |
Huawei, HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-220893 | Living document for MnF SCAS: draftCR to TR 33.926 |
draftCR revised to S3-221301 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-220894 | Discussion for key storage and derivation in UE-to-Network security procedure over Control Plane | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220895 | New SID on Security aspects for 5WWC Phase 2 |
SID new revised to S3-221217 |
Nokia Solutions & Networks (I) | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-220896 | Discussion on Security aspects for 5WWC Phase 2 | discussion | Nokia Solutions & Networks (I) | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-220897 | New KI AKMA Kaf refresh | pCR | OPPO | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-220898 | Adding evaluation for Sol#6 | pCR | Nokia, Nokia Shanghai Bell | 33.848 0.11.0 | FS_SIV | Rel-16 |
S3-107-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-220899 | New solution Security procedure of KAF refresh-MAC | pCR | OPPO | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-220900 | New solution Security procedure of KAF refresh-Counter | pCR | OPPO | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-220901 | Key issue on AKMA Roaming Scenario |
pCR revised to S3-221218 |
Nokia, Nokia Shanghai Bell | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-220902 | KI on AP function introduction | pCR | Nokia, Nokia Shanghai Bell | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-220903 | Key issue on KAF refresh without primary reauthentication |
pCR revised to S3-221219 |
Nokia, Nokia Shanghai Bell | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-220904 | Key issue on HN triggering primary reauthentication | pCR | Nokia, Nokia Shanghai Bell | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220905 | Reauthentication during the handover | pCR | Intel Corporation (UK) Ltd | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-220906 | New solution Security procedure of KAF-Nonce | pCR | OPPO | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-220907 | New KI Edge algorithm selection |
pCR revised to S3-221186 |
OPPO | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-220908 | New solution Authentication algorithm selection in EDGE | pCR | OPPO | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-220909 | New solution Authentication algorithm selection among EEC, ECS, and EES | pCR | OPPO | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-220910 | Rapporteur update to TR 33.875 | pCR | Nokia | 33.875 1.1.0 | FS_eSBA_SEC | Rel-18 |
S3-107-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-220911 | New key issue on SUPI length disclosed by SUCI |
pCR revised to S3-221180 |
Ericsson, Apple, AT&T, Cable Labs, China Southern Power Grid Co, Convida Wireless LLC, Intel, Interdigital, Johns Hopkins University APL, Lenovo, LGE, Mavenir, MITRE, NCSC, Oppo, Phillips, Samsung, Telefonica, US NIST, US NSA, Verizon Wireless, Xiaomi, ZT | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-220912 | Definition of Anonymous SUCI |
CR revised to S3-221170 |
Ericsson, Qualcomm | 33.501 17.5.0 CR#1380 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-220913 | UDM interaction for Anonymous SUCI |
CR revised to S3-221267 |
Ericsson | 33.501 17.5.0 CR#1381 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-220914 | Removing Editor’s note on using only null-scheme SUCI | CR | Ericsson | 33.501 17.5.0 CR#1382 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-220915 | Anonymous SUCI for onboarding | CR | Ericsson | 33.501 17.5.0 CR#1383 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-220916 | Clarification SUPI privacy for NPN | CR | Ericsson | 33.501 17.5.0 CR#1384 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-220917 | Updates to 33.434 for CoAP usage | CR | Ericsson | 33.434 17.1.1 CR#13 catF | eSEAL | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220918 | [DRAFT] Reply LS on AF specific UE ID retrieval |
LS out LS is reply to C3-221735 LS To: CT3 revised to S3-221161 |
Ericsson | eEDGE_5GC | Rel-17 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] | |
S3-220919 | A new key issue for single automated certificate management protocol and procedures |
pCR revised to S3-221277 |
Ericsson | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-220920 | A new key issue for the relation between NF lifecycle and certificate lifecycle |
pCR revised to S3-221278 |
Ericsson | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-220921 | Editorial corrections and technical clarifications |
CR revised to S3-221130 |
Ericsson | 33.558 17.0.0 CR#1 catF | eEDGE_5GC | Rel-17 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] |
S3-220922 | Clarification of access token usage in EC |
CR revised to S3-221274 |
Ericsson | 33.558 17.0.0 CR#2 catF | eEDGE_5GC | Rel-17 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] |
S3-220923 | Removing EN on secondary authentication | CR | Ericsson | 33.501 17.5.0 CR#1385 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-220924 | Update of the introduction and scope of TR 33.876 skeleton | pCR | Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-220925 | Key issue on Relation between NF and Certificate lifecycle management | pCR | Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-220926 | Key issue on Network Function instances identifiers |
pCR revised to S3-221224 |
Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-220927 | Key issue on Multiple certificates to be associated with a Network Function |
pCR revised to S3-221223 |
Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-220928 | Key issue on CMPv2 adoption and initial NF trust during certificate enrolment | pCR | Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-220929 | Key issue on Certificates revocation procedures |
pCR revised to S3-221225 |
Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-220930 | Key issue on Automated certificate management for Network Slicing |
pCR revised to S3-221226 |
Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-220931 | Trust in SEPP deployment scenarios | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.1.0 | 5G_eSBA | Rel-18 |
S3-107-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-220932 | Update to KI on roaming hub | pCR | Nokia, Nokia Shanghai Bell | 33.875 1.1.0 | 5G_eSBA | Rel-18 |
S3-107-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-220933 | Requirement to KI on roaming hub |
pCR revised to S3-221287 |
Nokia, Nokia Shanghai Bell | 33.875 1.1.0 | 5G_eSBA | Rel-18 |
S3-107-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-220934 | Security protocol over CP with 5G AKA to establishPC5 keys | pCR | THALES | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220935 | Editorial correction and clarification to 33.501 | CR | Ericsson | 33.501 17.5.0 CR#1386 catF | eNA_Ph2 | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220936 | Security protocol over CP with 5G ProSe security context in the USIM | pCR | THALES | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220937 | Terminology correction for security of UE onboarding | CR | Ericsson | 33.501 17.5.0 CR#1387 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-220938 | PWS for Non-Public Networks | CR | Ericsson | 33.969 17.0.0 CR#1 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-220939 | Corrections and clarifications to secondary authentication during UE onboarding |
CR revised to S3-221210 |
Ericsson | 33.501 17.5.0 CR#1388 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-220940 | Derivation of SUPI from default UE credentials |
CR revised to S3-221111 |
Ericsson, CableLabs, Intel, Qualcomm | 33.501 17.5.0 CR#1389 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-220941 | Removing EN on UE being uniquely identifiable and verifiably secure |
CR revised to S3-221112 |
Ericsson, CableLabs, Intel, Qualcomm, Xiaomi | 33.501 17.5.0 CR#1390 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-220942 | Implementation correction of CR1309 | CR | Ericsson | 33.501 17.5.0 CR#1391 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-220943 | Clarification on the certificate profile for SCP and SEPP | draftCR | Ericsson, Nokia, Nokia Shanghai Bell | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-220944 | SEPP interconnect certificate profile | other | Ericsson | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
noted | [WTS] [JSN] | |
S3-220945 | Clarification on CN-ID when it is presented in the certificate |
CR revised to S3-221211 |
Ericsson | 33.31 16.9.0 CR#127 catF | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
revised | [WTS] [JSN] |
S3-220946 | Clarification on CN-ID when it is presented in the certificate |
CR revised to S3-221212 |
Ericsson | 33.31 17.2.0 CR#128 catA | 5G_eSBA | Rel-17 |
S3-107-e AI: 4.14 |
revised | [WTS] [JSN] |
S3-220947 | Clarification on the format of callback URI in the NF certificate profile | CR | Ericsson | 33.31 16.9.0 CR#129 catF | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-220948 | Clarification on the format of callback URI in the NF certificate profile | CR | Ericsson | 33.31 17.2.0 CR#130 catA | 5G_eSBA | Rel-17 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-220949 | Clarification on access token requests for NF Producers of a specific NF type and token-based authorization for indirect communication with delegated discovery | CR | Ericsson | 33.501 16.10.0 CR#1392 catF | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-220950 | Clarification on access token requests for NF Producers of a specific NF type and token-based authorization for indirect communication with delegated discovery | CR | Ericsson | 33.501 17.5.0 CR#1393 catA | 5G_eSBA | Rel-17 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-220951 | SEPP to include and verify the source PLMN-ID |
draftCR revised to S3-221213 |
Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | TEI17 | Rel-17 |
S3-107-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-220952 | LS on PLMN ID used in Roaming Scenarios |
LS out LS To: CT4 revised to S3-221214 |
Ericsson |
S3-107-e AI: 4.14 |
revised | [WTS] [JSN] | |||
S3-220953 | SEPP handling of PLMN-ID in Roaming scenarios for PLMNs supporting more than on PLMN-ID | other | Ericsson | TEI17 | Rel-17 |
S3-107-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-220954 | Clarification of SNI usage for NF clients and servers | CR | Ericsson | 33.501 17.5.0 CR#1394 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-220955 | New KI, NRF validation of NFc for access token requests | pCR | Ericsson | 33.875 1.1.0 | FS_eSBA_SEC | Rel-18 |
S3-107-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-220956 | New SID on security aspects of enhanced support of Non-Public Networks phase 2 | SID new | Ericsson, CableLabs, InterDigital, Intel, Xiaomi, Nokia, Nokia Shanghai Bell, ZTE, China Mobile, LGE, Philips, Lenovo, Samsung | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-220957 | Skeleton for proposed FS_eNPN_Ph2_SEC | other | Ericsson | Rel-18 |
S3-107-e AI: 6 |
approved | [WTS] [JSN] | ||
S3-220958 | Reply LS on Clarification on MBS Security Context (MSK/MTK) Definitions |
LS out LS is reply to S3-220619 source LS: C4-222303 LS To: CT4 revised to S3-221155 |
Ericsson | 5MBS |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | ||
S3-220959 | UP IP: mapping of EPS integrity algorithm to NR integrity algorithm |
CR revised to S3-221177 |
Ericsson | 33.401 17.1.0 CR#707 catF | eUPIP_SEC | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220960 | Correction to Clause 5.2.1.5 UUAA Revocation |
CR revised to S3-221193 |
Lenovo | 33.256 17.0.0 CR#4 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220961 | Correction to Clause 5.2.2.4 UUAA Revocation |
CR revised to S3-221194 |
Lenovo | 33.256 17.0.0 CR#5 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220962 | Clarification to multiple registrations in different PLMNs | CR | Ericsson | 33.501 17.5.0 CR#1395 catA | TEI16 | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220963 | Clarification to multiple registrations in different PLMNs | CR | Ericsson | 33.501 16.10.0 CR#1396 catF | TEI16 | Rel-16 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220964 | Resolving of EN in Clause 5.2.1.4 UUAA re-authentication procedure |
CR revised to S3-221173 |
Lenovo | 33.256 17.0.0 CR#6 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220965 | Corrections to CP based solution | pCR | Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-220966 | Reference point name |
pCR revised to S3-221182 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220967 | Remote UE Report in UP based solution |
pCR revised to S3-221271 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220968 | Rephrasing Clause 6.2.1 to emphasize that security parameters for PC5 Direct Communication are determined during Direct Discovery |
pCR revised to S3-221272 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220969 | Restructure of security requirements for 5G ProSe UE-to-network relay | pCR | Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220970 | Remote UE Report in CP based solution | pCR | Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220971 | Discussion on UE ID privacy for Remote UE Report | discussion | Ericsson | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |
S3-220972 | PLMN ID in Direct Security Mode Failure |
pCR revised to S3-221183 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220973 | KNRP key derivation | pCR | Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-220974 | CR for Prose changes to TS 33.220 in Rel-17 | CR | Ericsson | 33.22 17.2.0 CR#216 catF | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-220975 | Discussion for Study on Zero Trust Security | discussion | Lenovo |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-220976 | Adding conclusions and recommendations related to KI#13 | pCR | Nokia, Nokia Shanghai Bell | 33.848 0.11.0 | FS_SIV | Rel-16 |
S3-107-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-220977 | Adding terms and abbreviations | CR | Qualcomm Incorporated | 33.256 17.0.0 CR#7 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220978 | Adding text for the Overview clause |
CR revised to S3-221197 |
Qualcomm Incorporated | 33.256 17.0.0 CR#8 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220979 | Resolving the EN on CAA level ID during UUAA procedures | CR | Qualcomm Incorporated | 33.256 17.0.0 CR#9 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220980 | Resolving the ENs related to re-authentication | CR | Qualcomm Incorporated | 33.256 17.0.0 CR#10 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
merged | [WTS] [JSN] |
S3-220981 | Resolving the ENs on CAA level ID during revocation | CR | Qualcomm Incorporated | 33.256 17.0.0 CR#11 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-220982 | Removing EN on USS authorisation | CR | Qualcomm Incorporated | 33.256 17.0.0 CR#12 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220983 | Removing EN on TPAE | CR | Qualcomm Incorporated | 33.256 17.0.0 CR#13 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220984 | Clarification on ‘high reliability’ location information |
CR revised to S3-221192 |
Qualcomm Incorporated | 33.256 17.0.0 CR#14 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220985 | Reply LS on Indication of Network Assisted Positioning method |
LS out LS is reply to S3-220620 LS To: CT4 |
Qualcomm Incorporated |
S3-107-e AI: 4.16 |
merged | [WTS] [JSN] | |||
S3-220986 | Resolving the ENs on protection of UAS data |
CR revised to S3-221198 |
Qualcomm Incorporated | 33.256 17.0.0 CR#15 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220987 | New Study on security of architecture enhancement for UAV and UAM |
SID new revised to S3-221200 |
Qualcomm Incorporated |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | |||
S3-220988 | Proposed skeleton for TS 33.742 |
other revised to S3-221196 |
Qualcomm Incorporated |
S3-107-e AI: 4.6 |
revised | [WTS] [JSN] | |||
S3-220989 | Proposed scope for TS 33.742 | other | Qualcomm Incorporated |
S3-107-e AI: 4.6 |
approved | [WTS] [JSN] | |||
S3-220990 | Discussion on how to document test cases in TS 33.742 | discussion | Qualcomm Incorporated |
S3-107-e AI: 4.6 |
noted | [WTS] [JSN] | |||
S3-220991 | Discussion on Ua security protocol identifier for PSK TLS 1.3 |
discussion revision of S3-220317 |
Qualcomm Incorporated |
S3-107-e AI: 4.16 |
noted | [WTS] [JSN] | |||
S3-220992 | Adding a Note about the new Ua security protocol identifier for TLS 1.3 |
CR revision of S3-220318 revised to S3-221199 |
Qualcomm Incorporated | 33.222 17.1.0 CR#571 catF | eCryptPr | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-220993 | Adding a new Ua security protocol identifier for TLS 1.3 |
CR revision of S3-220319 |
Qualcomm Incorporated | 33.22 17.2.0 CR#2151 catF | eCryptPr | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-220994 | PC5 security policy provisioning for user-plane L3 U2N relay solution |
pCR revised to S3-221294 |
Qualcomm Incorporated, Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220995 | Clarification on the PC5 link establishment for user-plane L3 U2N relay solution | pCR | Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-220996 | CR to ProSe TS - Address the Editor’s Notes in clause 6.3.5 |
pCR revised to S3-221295 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-220997 | CR to ProSe TS – An update on MIC calculation for discovery message | pCR | Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-220998 | CR to ProSe TS – Clarification on discovery message protection | pCR | Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-220999 | CR to ProSe TS – Removing an Editor’s Note in user plane based U2N procedure |
pCR revised to S3-221296 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221000 | Update on 5G ProSe restricted discovery procedure for U2N relay |
pCR revised to S3-221302 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221001 | CR to ProSe TS - Clarification on Knrp derivation for U2N relay over user plane |
pCR revised to S3-221297 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221002 | Resolving Editor’s note on using only null-scheme SUCI |
CR revised to S3-221202 |
Qualcomm Incorporated | 33.501 17.5.0 CR#1397 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221003 | pCR to TS33.503 Abbreviations update |
pCR revised to S3-221281 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221004 | Study on Zero Trust Security |
SID new revised to S3-221172 |
Lenovo, Motorola Mobility, Interdigital, Verizon, Cablelabs, Mavenir, Johns Hopkins University APL, LG Electronics, Telefonica, NEC, Telia Company, AT&T, Samsung, PCCW Global B.V, China Mobile, Motorola Solutions, Inc, Nokia, Nokia Shanghai Bell, Intel, N | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-221005 | pCR to TS33.503 Clause 4.2 Update reference point name between 5G PKMF and UDM | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-221006 | pCR to TS33.503 Wording update | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221007 | pCR to TS33.503 Clause 6.3 Update security requirements of UE-to-Network Relay | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221008 | Resolution of editor's note relating to anonymizing SUPI or skipping default credential identifier. | CR | Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#1398 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221009 | Resolution of editor's note relating to usage of SUPI as a verifiable identifier | CR | Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#1399 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221010 | Resolution of editor’s note relating to exclusive use of anonymized SUCI. | CR | Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#1400 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221011 | Resolution of inconsistency in SUCI usage during UE onboarding. |
CR revised to S3-221273 |
Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#1401 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221012 | pCR to TS33.503 Clause 6.3 Update security requirements of Layer-3 UE-to-Network Relay | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221013 | pCR to TS33.503 Clause 6.3 Remove unnecessary description from UP-based and CP-based procedures | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221014 | pCR to TS33.503 Clause 6.3 Clarification text for Kausf_p |
pCR revised to S3-221282 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221015 | pCR to TS33.503 Clause 6.3 Solution for co-existence of UP and CP security options |
pCR revised to S3-221284 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221016 | pCR to TS33.503 Clause 6.3 Update security procedure over Control Plane | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-221017 | Discussion on usage of identifier during UE onboarding in SNPNs | discussion | Lenovo | eNPN |
S3-107-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-221018 | NSWO security revisited | discussion | Ericsson, Deutsche Telekom, Vodafone | Rel-17 |
S3-107-e AI: 4.12 |
noted | [WTS] [JSN] | ||
S3-221019 | Draft LS on NSWO security |
LS out LS To: CT4 |
Ericsson | Rel-17 |
S3-107-e AI: 4.12 |
noted | [WTS] [JSN] | ||
S3-221020 | Resolving Editor’s Note related to UE onboarding |
CR revised to S3-221195 |
Lenovo | 33.501 17.5.0 CR#1402 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
revised | [WTS] [JSN] |
S3-221021 | Draft skeleton of TR 33.740 | draft TR | CATT | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e AI: 6 |
approved | [WTS] [JSN] | |
S3-221022 | Update to clause I.2.2.2.2 for Onboarding clarifications | CR | Lenovo | 33.501 17.5.0 CR#1403 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
merged | [WTS] [JSN] |
S3-221023 | New SID on Security Aspects of Ranging Based Services and Sidelink Positioning |
SID new revised to S3-221209 |
Xiaomi, Apple, China Mobile, CATT, Huawei, Hisilicon, InterDigital, LGE, Philips, vivo, ZTE, Lenovo, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-221024 | New SID on Security Aspects of Satellite Access | SID new | Xiaomi, China Mobile, China Telecom | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221025 | 33.503: Updates in Clause 4.2 | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221026 | 33.503: Updates in Clause 5.2.5 | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221027 | 33.503: Updates in Clause 6.1.3.2 |
pCR revised to S3-221189 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221028 | 33.503: Clarifiacation on MIC Check in Open Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221029 | 33.503: General Description for ProSe U2N Relay Discovery Security | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221030 | 33.503: Add Security Requirement for ProSe U2N Relay Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221031 | 33.503: Control Plane based Security Procedure for ProSe U2N Relay Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221032 | 33.503: User Plane based Security Procedure for ProSe U2N Relay Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221033 | 33.503: Derivation of Discovery Keys for ProSe U2N Relay Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221034 | 33.503: Updates to General Security Requirements for U2N Relay Communication |
pCR revised to S3-221206 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221035 | 33.503: Updates to Security Requirements for U2N Relay Communication via L3 Relay UE |
pCR revised to S3-221207 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221036 | Discussion on PC5 Key Hierarchy for ProSe U2N Relay Communication | discussion | Xiaomi Technology | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |
S3-221037 | Discussion on Security for ProSe U2N Relay Communication over User Plane | discussion | Xiaomi Technology | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |
S3-221038 | 33.503: Update to Security Procedure over User Plane | pCR | Xiaomi Technology, China Telecom | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221039 | 33.503: PRUK Derivation for ProSe U2N Relay Security over User Plane | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221040 | 33.503: Updates in Clause 6.3.4 |
pCR revised to S3-221208 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-221041 | Key Issue on Refresh of Long Lived Key KAUSF | pCR | Beijing Xiaomi Mobile Software | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-221042 | Key Issue on Security of Interworking | pCR | Beijing Xiaomi Mobile Software | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-221043 | New Use Case for Continuity of Steering of Roaming Service Delivery | pCR | Beijing Xiaomi Mobile Software | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-221044 | New Use Case for Continuity of UE Parameters Update Service Delivery | pCR | Beijing Xiaomi Mobile Software | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-221045 | New Use Case for Security of Interworking |
pCR revised to S3-221205 |
Beijing Xiaomi Mobile Software | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-221046 | Key Issue on Trust Chain of Certificate Authority Hierarchy |
pCR revised to S3-221204 |
Beijing Xiaomi Mobile Software | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-221047 | Resolving the alignment related EN for NSACF Subscription/unsubscription procedure | CR | Xiaomi Communication | 33.501 17.5.0 CR#1404 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-221048 | Update Figure: I.2.2.2.2-1 for consistent service operation names | CR | Xiaomi Communication | 33.501 17.5.0 CR#1405 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
merged | [WTS] [JSN] |
S3-221049 | Resolving the Editor’s Notes for UE onboarding in SNPNs | CR | Xiaomi Communication, Ericsson | 33.501 17.5.0 CR#1406 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
merged | [WTS] [JSN] |
S3-221050 | Update Subscription and unsubscription procedure of NSACF notification service | CR | Xiaomi Communication | 33.501 17.5.0 CR#1407 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-221051 | eNS2_Sec: Solution #1 update | pCR | Xiaomi Communication | 33.874 0.6.0 | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-221052 | New key issue on authentication proxy architecture for AKMA | pCR | Xiaomi Communication | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-221053 | New key issue on protecting application servers with different security requirements | pCR | Xiaomi Communication | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-221054 | New key issue on secure AKMA application key request in AKMA supporting authentication proxy | pCR | Xiaomi Communication | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-221055 | New key issue on secure authorization for AKMA supporting authentication proxy | pCR | Xiaomi Communication | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-221056 | New key issue on secure identification of authentication proxy and application server in AKMA scenarios | pCR | Xiaomi Communication | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-221057 | New key issue on AKMA application key request in home routed and local-breakout scenarios | pCR | Xiaomi Communication | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-221058 | New key issue on Secure AAnF service request in roaming scenarios of AKMA | pCR | Xiaomi Communication | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-221059 | New key issue on secure architecture for roaming scenarios in AKMA | pCR | Xiaomi Communication | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-221060 | New key issue on authentication and authorization problem for the EEC hosted in the roaming UE |
pCR revised to S3-221191 |
Xiaomi Communication | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-221061 | Clarification on AF authorization for the NSACF notification procedure | CR | Ericsson | 33.501 17.5.0 CR#1408 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.8 |
not pursued | [WTS] [JSN] |
S3-221062 | New SID on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the NR Air Interface and NG-RAN |
SID new revised to S3-221276 |
Ericsson | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-221063 | LS reply on UE location in connected mode in NTN |
LS out LS To: RAN2 revised to S3-221268 |
Ericsson | Rel-17 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-221064 | Reply LS on EPS fallback enhancements |
LS out LS To: RAN2 revised to S3-221162 |
Ericsson | Rel-17 |
S3-107-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-221065 | New WID on IETF OSCORE Ua* protocol profile for AKMA | WID new | Ericsson | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221066 | IETF OSCORE as AKMA Ua* protocol | CR | Ericsson, DT | 33.535 17.5.0 CR#131 catB | DUMMY | Rel-18 |
S3-107-e AI: 6 |
not pursued | [WTS] [JSN] |
S3-221067 | Extending the Ua security protocol namespace to include the AKMA OSCORE Ua* protocol | CR | Ericsson, DT | 33.22 17.2.0 CR#217 catB | DUMMY | Rel-18 |
S3-107-e AI: 6 |
not pursued | [WTS] [JSN] |
S3-221068 | 5G registration via trusted non-3GPP access after NSWO authentication | discussion | Lenovo | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221069 | New Study to enable 5G registration via trusted non-3GPP access after NSWO Authentication (FS_5GRTN3) | SID new | Lenovo | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221070 | Study to enable URSP rules to securely identify applications | discussion | Lenovo | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221071 | New Study to enable URSP rules to securely identify Applications (FS_USIA) | SID new | Lenovo, AT&T, Broadcom, CableLabs, CATT, China Mobile, China Telecom, Deutsche Telekom, Intel, LG Electronics, Motorola Solutions MSI, NEC, PCCW Global B.V., Verizon, Xiaomi | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221072 | 5GFBS - Conclusion for solution#17 | pCR | Apple. Ericsson, Intel, Nokia, Deutsche Telekom, CableLabs, LGE, OPPO, Xiaomi, Huawei, NIST, Telecom Italia, AT&T | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-221073 | 5GFBS - Draft LS to RAN plenary on the conlcusion of solution#17 |
LS out LS To: RAN Plenary |
Apple | Rel-18 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] | ||
S3-221074 | 5GFBS - new WID on 5GFBS |
WID new revised to S3-221185 |
Apple, US National Security Agency, AT&T, Deutsche Telekom, Ericsson, Huawei, Hisilicon, CableLabs, Intel, InterDigital, Johns Hopkins University APL, NIST, Xiaomi, OPPO | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-221075 | 5GFBS - Security risk in lower layers | pCR | Apple | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221076 | CR - 33501 - Clarification on Fast re-authentication | CR | Apple | 33.501 17.5.0 CR#1409 catF | TEI17 | Rel-18 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-221077 | CR - 33501 - Clarification on the NAS COUNT for KeNB derivation | CR | Apple | 33.501 17.5.0 CR#1410 catF | TEI17 | Rel-18 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-221078 | IDPrvc - Security issue on C-RNTI | pCR | Apple | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-221079 | AKMA - New key issue of introducing AP to AKMA architecture | pCR | Apple | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-221080 | MEC - Reply LS on AF specific UE ID retrieval (C3-221735) |
LS out LS To: CT3 |
Apple | Rel-17 |
S3-107-e AI: 4.11 |
merged | [WTS] [JSN] | ||
S3-221081 | NTN - Reply LS on UE location in connected mode in NTN(R2-2204257) |
LS out LS To: RAN2 |
Apple | Rel-17 |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-221082 | NTN - Reply LS on NTN specific user consent (R2-2201754) |
LS out LS To: RAN2 |
Apple | Rel-17 |
S3-107-e AI: 3 |
merged | [WTS] [JSN] | ||
S3-221083 | HN-auth-NAS based HN triggered authentication | pCR | Apple | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-221084 | Detection of MitM attacks with secret paging | pCR | Lenovo | 33.809 0.18.0 | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-221085 | Discussion on security aspects of NGRTC | discussion | Huawei,HiSilicon, Deutsche Telekom | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221086 | New SID on NGRTC |
SID new revised to S3-221229 |
Huawei,HiSilicon | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-221087 | corrections on measurements flow of solution#5 | pCR | Huawei,HiSilicon | 33.848 0.11.0 | FS_SIV | Rel-16 |
S3-107-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-221088 | editorial changes of ENSI | CR | Huawei,HiSilicon | 33.501 16.10.0 CR#1411 catF | TEI16 | Rel-16 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221089 | mirror-editorial changes of ENSI | CR | Huawei,HiSilicon | 33.501 17.5.0 CR#1412 catA | TEI16 | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221090 | New threat on Kausf handing | draftCR | Huawei,HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-107-e AI: 4.4 |
noted | [WTS] [JSN] | |
S3-221091 | threat modifications for token verification |
draftCR revised to S3-221230 |
Huawei,HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-107-e AI: 4.4 |
revised | [WTS] [JSN] | |
S3-221092 | threat modifications for SEPP |
draftCR revised to S3-221231 |
Huawei,HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-107-e AI: 4.4 |
revised | [WTS] [JSN] | |
S3-221093 | Adding a key issue of Multiple registrations | pCR | Huawei,HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-221094 | The Scope of the FS_EDGE_Ph2 | pCR | Huawei, HiSilicon | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-221095 | The Skeleton of the FS_EDGE_Ph2 | draft TR | Huawei, HiSilicon | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
approved | [WTS] [JSN] | |
S3-221096 | Update of Solution #12 |
pCR revised to S3-221232 |
Huawei, HiSilicon | 33.875 1.1.0 | FS_eSBA_SEC | Rel-18 |
S3-107-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-221097 | Update of Solution #9 | pCR | Huawei, HiSilicon | 33.875 1.1.0 | FS_eSBA_SEC | Rel-18 |
S3-107-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-221098 | Clarification on the NSWO in the UE side |
CR revised to S3-221233 |
Huawei, HiSilicon | 33.501 17.5.0 CR#1413 catF | NSWO_5G | Rel-17 |
S3-107-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-221099 | Removing the Ens on the SCP authorization |
CR revised to S3-221234 |
Huawei, HiSilicon | 33.501 17.5.0 CR#1414 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.14 |
revised | [WTS] [JSN] |
S3-221100 | Clarification on IV usage on N32-f protection-R15 | CR | Huawei, HiSilicon | 33.501 15.15.0 CR#1415 catF | 5GS_Ph1-SEC | Rel-15 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-221101 | Clarification on IV usage on N32-f protection-R16 | CR | Huawei, HiSilicon | 33.501 16.10.0 CR#1416 catA | 5GS_Ph1-SEC | Rel-16 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-221102 | Clarification on IV usage on N32-f protection-R17 | CR | Huawei, HiSilicon | 33.501 17.5.0 CR#1417 catA | 5GS_Ph1-SEC | Rel-17 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-221103 | Clarification on handling of the incoming N32-f message in the pSEPP side – R15 | CR | Huawei, HiSilicon | 33.501 15.15.0 CR#1418 catF | 5GS_Ph1-SEC | Rel-15 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-221104 | Clarification on handling of the incoming N32-f message in the pSEPP side – R16 | CR | Huawei, HiSilicon | 33.501 16.10.0 CR#1419 catA | 5GS_Ph1-SEC | Rel-16 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-221105 | Clarification on handling of the incoming N32-f message in the pSEPP side – R17 | CR | Huawei, HiSilicon | 33.501 17.5.0 CR#1420 catA | 5GS_Ph1-SEC | Rel-17 |
S3-107-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-221106 | Reply LS on UE location in connected mode in NTN |
LS out source LS: R2-2204257 LS To: RAN2 |
Nokia Corporation |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221107 | Reply LS on Reply LS on NTN specific User Consent |
LS out source LS: R2-2200148 / S3-214349 LS To: RAN2 |
Nokia Corporation |
S3-107-e AI: 3 |
merged | [WTS] [JSN] | |||
S3-221108 | CableLabs, Ericsson, Nokia, Nokia Shanghai Bell | draftCR | CableLabs | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
withdrawn | [WTS] [JSN] | |
S3-221109 | Reply LS on EPS fallback enhancements |
LS out LS To: RAN2 |
Nokia Corporation |
S3-107-e AI: 3 |
merged | [WTS] [JSN] | |||
S3-221110 | Discussion on LS on EPS fallback enhancements | discussion | Nokia Corporation |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221111 | Derivation of SUPI from default UE credentials |
CR revision of S3-220940 |
Ericsson, CableLabs, Intel, Qualcomm, Philips | 33.501 17.5.0 CR#13891 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221112 | Removing EN on UE being uniquely identifiable and verifiably secure |
CR revision of S3-220941 |
Ericsson, CableLabs, Intel, Qualcomm, Xiaomi, Philips | 33.501 17.5.0 CR#13901 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-221113 | New SID on Security and Privacy of AI/ML-based services and applications in 5G |
SID new revised to S3-221188 |
OPPO, Apple, vivo, Inter Digital, China Mobile, Samsung, Nokia, Nokia Shanghai Bell | Rel-18 |
S3-107-e AI: 6 |
revised | [WTS] [JSN] | ||
S3-221114 | New Key Issue on UE-to-UE Relay Trust Model | pCR | OPPO | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221115 | KI#27 update - requirements |
pCR revised to S3-221190 |
MITRE Corporation | 33.848 0.11.0 | FS_SIV | Rel-16 |
S3-107-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-221116 | New KI: Remote UE Security Establishment via UE-to-UE Relay | pCR | OPPO | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-221117 | Need for Rel-18 study on UP security enhancement | discussion | Samsung, CableLabs, Interdigital | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221118 | New SID on 5G User plane security enhancements | SID new | Samsung | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221119 | [SBA] CR to update NF profile for inter-slice access | CR | Samsung | 33.501 17.5.0 CR#1421 catF | 5G_eSBA | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-221120 | Clarification on selected EDGE authentication method indication | CR | Samsung | 33.558 17.0.0 CR#3 catF | eEDGE_5GC | Rel-17 |
S3-107-e AI: 4.11 |
not pursued | [WTS] [JSN] |
S3-221121 | New SID on security aspects of control plane based remote provisioning in Non-Public Networks | SID new | Samsung | Rel-18 |
S3-107-e AI: 6 |
noted | [WTS] [JSN] | ||
S3-221122 | New Key Issue on AKMA Roaming | pCR | Samsung | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-221123 | New solution on AKMA Roaming | pCR | Samsung | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-221124 | New solution on pushing AKMA context to visited PLMN | pCR | Samsung | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-221125 | New Key issue on HN initiated Re-authentication | pCR | Samsung | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-221126 | New Solution on UDM initiated re-authentication based on AUSF request | pCR | Samsung | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-221127 | New solution on HN initiated re-authentication via AUSF | pCR | Samsung | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-221128 | New solution on UDM triggered key update procecdure based on AAnF request | pCR | Samsung | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-221129 | New solution on UPU based re-authentication procedure | pCR | Samsung | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-221130 | Editorial corrections and technical clarifications |
CR revision of S3-220921 revised to S3-221275 |
Ericsson | 33.558 17.0.0 CR#11 catF | eEDGE_5GC | Rel-17 |
S3-107-e AI: 4.11 |
revised | [WTS] [JSN] |
S3-221131 | Verification of NSSAIs for preventing slice attack |
draftCR revision of S3-220468 |
CableLabs, Ericsson,Nokia, Nokia Shanghai Bell | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-221132 | Discussion on security procedure during registration procedure over two different PLMN | discussion | NEC Corporation | TEI17 | Rel-17 |
S3-107-e AI: 4.16 |
noted | [WTS] [JSN] | |
S3-221133 | Checking S-NSSAI against authoritative information source | other | CableLabs,Nokia, Nokia Shanghai Bell | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
noted | [WTS] [JSN] | |
S3-221134 | Update to NAS security context procedure when UE is registering over two different PLMNs | CR | NEC Corporation | 33.501 17.5.0 CR#1422 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-221135 | MBS capability exchange and delivery method | CR | Samsung | 33.501 17.5.0 CR#1423 catB | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-221136 | New KI for Authentication of PLMNs over IPX | pCR | CableLabs | 33.875 1.1.0 | FS_eSBA_SEC | Rel-18 |
S3-107-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-221137 | CP based security selection | pCR | Nokia, Nokia Shanghai Bell, Interdigital, LGE, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221138 | derive 5GPRUK based on Kausf_p | pCR | Nokia, Nokia Shanghai Bell, Interdigital, LGE, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-221139 | authorization of remote UE | pCR | Nokia, Nokia Shanghai Bell, Interdigital, LGE, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221140 | UP based security selection | pCR | Nokia, Nokia Shanghai Bell, Interdigital, LGE, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221141 | Relay Discovery clarifications | pCR | Philips International B.V. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
S3-221142 | Process and agenda for SA3#107e |
other revision of S3-220606 |
WG Chair |
S3-107-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-221143 | Avoid linkage between security functions and UE Radio Access Capabilities |
CR revised to S3-221298 |
VODAFONE | 33.401 17.1.0 CR#708 catF | UPIP_SEC_LTE | Rel-17 |
S3-107-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-221144 | E1 interface security requirements | CR | VODAFONE | 33.401 17.1.0 CR#709 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221145 | LS on Security architecture for 5G multicast/broadcast services |
LS in LS reply in S3-221158, S3-221158 |
S4-220531 |
S3-107-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-221146 | Response LS on Clarifications on Nmbstf_MBCDistributionSession service | LS in | S4-220575 |
S3-107-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-221147 | LS on 3GPP TS 29.244 | LS in | BBF |
S3-107-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-221148 | Reply LS on secondary authentication for multicast PDU session |
LS in revision of S3-220675 |
S2-2201311 |
S3-107-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-221149 | 5G Prose questions on CP for show-of-hands | other | Interdigital,CATT |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-221150 | Questions of show hand on ProSe CP-based solution | discussion | CATT |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |||
S3-221151 | LS on authentication type and related information of MSGin5G service |
LS in LS reply in S3-221152 |
C1-223957 |
S3-107-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221152 | Reply to: LS on authentication type and related information of MSGin5G service |
LS out LS is reply to S3-221151 LS To: CT1 |
China Mobile |
S3-107-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-221153 | LS on Clarification on MBS Security Keys |
LS in LS reply in S3-221262 |
C4-223302 |
S3-107-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-221154 | Reply to: LS on Clarification on MBS Security Keys |
LS out LS is reply to S3-221153 LS To: CT4 revised to S3-221262 |
Huawei |
S3-107-e AI: 4.1 |
revised | [WTS] [JSN] | |||
S3-221155 | Reply LS on Clarification on MBS Security Context (MSK/MTK) Definitions |
LS out LS is reply to S3-220658 source LS: C4-222303 LS To: CT4 revision of S3-220958 |
Ericsson | 5MBS |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | ||
S3-221156 | New test case for confidentiality, integrity and replay protection between AAnF and AUSF |
pCR revision of S3-220689 |
Keysight Technologies UK Ltd | 33.537 0.0.0 | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-221157 | New threat for confidentiality, integrity and replay between AAnF and AUSF | draftCR | Keysight Technologies UK Ltd | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-221158 | Reply LS on security architecture for 5G multicast-broadcast services |
LS out LS is reply to S3-221145 source LS: S4-220531 LS To: SA4 revision of S3-220871 |
Huawei, HiSilicon | Rel-17 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | ||
S3-221159 | New test case for confidentiality, integrity and replay protection between AF/NEF and AAnF |
pCR revision of S3-220691 |
Keysight Technologies UK Ltd | 33.537 0.0.0 | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-221160 | New threat for confidentiality, integrity and replay between AAnF and AF/NEF | draftCR | Keysight Technologies UK Ltd | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-221161 | Reply LS on AF specific UE ID retrieval |
LS out LS is reply to S3-220652 LS To: CT3 revision of S3-220918 |
Ericsson | eEDGE_5GC | Rel-17 |
S3-107-e AI: 4.11 |
approved | [WTS] [JSN] | |
S3-221162 | Reply LS on EPS fallback enhancements |
LS out LS To: RAN2 revision of S3-221064 |
Ericsson | Rel-17 |
S3-107-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-221163 | LS on handling of the modification policy in the IPX and receiving SEPP |
LS out LS To: CT4 |
Huawei, HiSilicon | Rel-15 |
S3-107-e AI: 4.14 |
approved | [WTS] [JSN] | ||
S3-221164 | LS to SA2 on NSAC |
LS out LS To: SA2 |
Huawei Technologies R&D UK | Rel-17 |
S3-107-e AI: 5.5 |
approved | [WTS] [JSN] | ||
S3-221165 | LS on TNAP mobility security aspect |
LS out LS To: SA2 |
Nokia Solutions & Networks (I) | FS_5WWC_Ph2 | Rel-18 |
S3-107-e AI: 6 |
approved | [WTS] [JSN] | |
S3-221166 | new draft TS 33.526 MnF SCAS | draft TS | Huawei Technologies Sweden AB | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-221167 | Living document for AAnF SCAS: draftCR to TR 33.926 | draftCR | China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-221168 | draft TS 33.537 | draft TS | China Mobile | SCAS_5G_AAnF | Rel-18 |
S3-107-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-221169 | draft TR 33.737 | draft TR | China Mobile | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-221170 | Configuration of Anonymous SUCI |
CR revision of S3-220912 |
Ericsson, Qualcomm | 33.501 17.5.0 CR#13801 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221171 | 33.926-Add a new threat | draftCR | Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
withdrawn | [WTS] [JSN] | |
S3-221172 | Study on Zero Trust Security |
SID new revision of S3-221004 |
Lenovo, Motorola Mobility, Interdigital, Verizon, Cablelabs, Mavenir, Johns Hopkins University APL, LG Electronics, Telefonica, NEC, Telia Company, AT&T, Samsung, PCCW Global B.V, China Mobile, Motorola Solutions, Inc, Nokia, Nokia Shanghai Bell, Intel,.. | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221173 | Resolving of EN in Clause 5.2.1.4 UUAA re-authentication procedure |
CR revision of S3-220964 |
Lenovo, Huawei HiSilicon, Qualcomm Incorporated | 33.256 17.0.0 CR#61 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221174 | EN resolution for Secondary Authentication for Remote UE with L3 U2N relay without N3IWF(Alt2) |
pCR revision of S3-220816 |
LG Electronics Inc., Interdigital | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221175 | Revocation_ReAuth for Secondary Authentication for Remote UE |
pCR revision of S3-220817 |
LG Electronics Inc., Interdigital | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221176 | New KI on authorization of selection of participant NWDAF instances in the Federated Learning group |
pCR revision of S3-220740 |
China Telecommunications | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-221177 | UP IP: mapping of EPS integrity algorithm to NR integrity algorithm |
CR revision of S3-220959 |
Ericsson | 33.401 17.1.0 CR#7071 catF | eUPIP_SEC | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221178 | Rel-18 study for network slicing security |
SID new revision of S3-220802 |
Huawei, HiSilicon, Lenovo, CATT, CAICT, China Mobile, China Unicom, InterDigital, NEC, Nokia, Deutsche Telekom, ZTE | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221179 | New SID: Study on SNAAPP securitY |
SID new revision of S3-220719 |
NTT DOCOMO INC. |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | |||
S3-221180 | New key issue on SUPI length disclosed by SUCI |
pCR revision of S3-220911 |
Ericsson, Apple, AT&T, Cable Labs, China Southern Power Grid Co, Convida Wireless LLC, Intel, Interdigital, Johns Hopkins University APL, Lenovo, LGE, Mavenir, MITRE, NCSC, Oppo, Phillips, Samsung, Telefonica, US NIST, US NSA, Verizon Wireless, Xiaomi, ZT | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-221181 | KI#2 update - threats and requirements |
pCR revision of S3-220795 |
Huawei, HiSilicon | 33.874 0.6.0 | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-221182 | Reference point name |
pCR revision of S3-220966 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221183 | PLMN ID in Direct Security Mode Failure |
pCR revision of S3-220972 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221184 | Conclusion for part 2 of KI#2 |
pCR revision of S3-220798 |
Huawei, HiSilicon | 33.874 0.6.0 | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-221185 | 5GFBS - new WID on 5GFBS |
WID new revision of S3-221074 |
Apple, US National Security Agency, AT&T, Deutsche Telekom, Ericsson, Huawei, Hisilicon, CableLabs, Intel, InterDigital, Johns Hopkins University APL, NIST, Xiaomi, OPPO, ZTE | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221186 | New KI Edge algorithm selection |
pCR revision of S3-220907 |
OPPO, CMCC, vivo | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-221187 | draft TR 33.874 | draft TR | Huawei Technologies R&D UK | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
approved | [WTS] [JSN] | |
S3-221188 | New SID on Security and Privacy of AI/ML-based services and applications in 5G |
SID new revision of S3-221113 |
OPPO, Apple, vivo, Inter Digital, China Mobile, Samsung, Nokia, Nokia Shanghai Bell | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221189 | 33.503: Updates in Clause 6.1.3.2 |
pCR revision of S3-221027 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221190 | KI#27 update - requirements |
pCR revision of S3-221115 |
MITRE Corporation | 33.848 0.11.0 | FS_SIV | Rel-16 |
S3-107-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-221191 | New key issue on authentication and authorization problem for the EEC hosted in the roaming UE |
pCR revision of S3-221060 |
Xiaomi Communication | 33.739 0.0.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-221192 | Clarification on ‘high reliability’ location information |
CR revision of S3-220984 |
Qualcomm Incorporated | 33.256 17.0.0 CR#141 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221193 | Correction to Clause 5.2.1.5 UUAA Revocation |
CR revision of S3-220960 |
Lenovo | 33.256 17.0.0 CR#41 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221194 | Correction to Clause 5.2.2.4 UUAA Revocation |
CR revision of S3-220961 |
Lenovo | 33.256 17.0.0 CR#51 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221195 | Resolving Editor’s Note related to UE onboarding |
CR revision of S3-221020 |
Lenovo, Xiaomi Communication | 33.501 17.5.0 CR#14021 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221196 | Proposed skeleton for TR 33.742 |
draft TR revision of S3-220988 |
Qualcomm Incorporated | SCAS_5G_split_gNB | Rel-18 |
S3-107-e AI: 4.6 |
approved | [WTS] [JSN] | |
S3-221197 | Adding text for the Overview clause |
CR revision of S3-220978 |
Qualcomm Incorporated, Lenovo | 33.256 17.0.0 CR#81 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221198 | Resolving the ENs on protection of UAS data |
CR revision of S3-220986 |
Qualcomm Incorporated | 33.256 17.0.0 CR#151 catF | ID_UAS | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221199 | Adding a Note about the new Ua security protocol identifier for TLS 1.3 |
CR revision of S3-220992 |
Qualcomm Incorporated | 33.222 17.1.0 CR#572 catF | eCryptPr | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221200 | New Study on on Security for Phase 2 for UAS, UAV and UAM |
SID new revision of S3-220987 |
Qualcomm Incorporated |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | |||
S3-221201 | TS 33.742 v1.0.0 | draft TR | Qualcomm Austria RFFE GmbH | SCAS_5G_split_gNB | Rel-18 |
S3-107-e AI: 4.6 |
approved | [WTS] [JSN] | |
S3-221202 | Resolving Editor’s note on using only null-scheme SUCI |
CR revision of S3-221002 |
Qualcomm Incorporated | 33.501 17.5.0 CR#13971 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221203 | Clarification on the description about AAnF |
CR revision of S3-220770 |
China Telecom Corporation Ltd. | 33.535 17.5.0 CR#1291 catF | AKMA | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221204 | Key Issue on Trust Chain of Certificate Authority Hierarchy |
pCR revision of S3-221046 |
Beijing Xiaomi Mobile Software | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221205 | New Use Case for Security of Interworking |
pCR revision of S3-221045 |
Beijing Xiaomi Mobile Software | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-221206 | 33.503: Updates to General Security Requirements for U2N Relay Communication |
pCR revision of S3-221034 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221207 | 33.503: Updates to Security Requirements for U2N Relay Communication via L3 Relay UE |
pCR revision of S3-221035 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221208 | 33.503: Updates in Clause 6.3.4 |
pCR revision of S3-221040 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221209 | New SID on Security Aspects of Ranging Based Services and Sidelink Positioning |
SID new revision of S3-221023 |
Xiaomi, Apple, China Mobile, CATT, Huawei, Hisilicon, InterDigital, LGE, Philips, vivo, ZTE, Lenovo, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221210 | Corrections and clarifications to secondary authentication during UE onboarding |
CR revision of S3-220939 |
Ericsson, Intel | 33.501 17.5.0 CR#13881 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221211 | Clarification on CN-ID when it is presented in the certificate |
CR revision of S3-220945 |
Ericsson | 33.31 16.9.0 CR#1271 catF | 5G_eSBA | Rel-16 |
S3-107-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-221212 | Clarification on CN-ID when it is presented in the certificate |
CR revision of S3-220946 |
Ericsson | 33.31 17.2.0 CR#1281 catA | 5G_eSBA | Rel-17 |
S3-107-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-221213 | SEPP to include and verify the source PLMN-ID |
draftCR revision of S3-220951 |
Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | TEI17 | Rel-17 |
S3-107-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-221214 | LS on PLMN ID used in Roaming Scenarios |
LS out LS To: CT4, SA2 revision of S3-220952 |
Ericsson |
S3-107-e AI: 4.14 |
approved | [WTS] [JSN] | |||
S3-221215 | Clarification on anonymization api |
CR revision of S3-220694 |
Nokia, Nokia Shanghai Bell | 33.535 17.5.0 CR#1261 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221216 | NSWO alignment with SA2 specs |
CR revision of S3-220698 |
Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#13631 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-221217 | New SID on Security aspects for 5WWC Phase 2 |
SID new revision of S3-220895 |
Nokia Solutions & Networks (I) | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221218 | Key issue on AKMA Roaming Scenario |
pCR revision of S3-220901 |
Nokia, Nokia Shanghai Bell, CMCC, Lenovo, Xiaomi, Samsung | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-221219 | Key issue on KAF refresh without primary reauthentication |
pCR revision of S3-220903 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, OPPO | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-221220 | LS reply on 5G NSWO roaming aspects |
LS out LS is reply to S3-220655 LS To: SA2 revision of S3-220697 |
Nokia, Nokia Shanghai Bell | TEI17 | Rel-17 |
S3-107-e AI: 4.12 |
approved | [WTS] [JSN] | |
S3-221221 | Key issue on Security for AIML model sharing |
pCR revision of S3-220722 |
Nokia, Nokia Shanghai Bell | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-221222 | Key issue on Anomalous NF behaviour detection by NWDAF |
pCR revision of S3-220723 |
Nokia, Nokia Shanghai Bell | 33.738 0.0.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-221223 | Key issue on Multiple certificates to be associated with a Network Function |
pCR revision of S3-220927 |
Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221224 | Key issue on Network Function instances identifiers |
pCR revision of S3-220926 |
Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221225 | Key issue on Certificates revocation procedures |
pCR revision of S3-220929 |
Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221226 | Key issue on Automated certificate management for Network Slicing |
pCR revision of S3-220930 |
Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221227 | Correct AAnF service in clause 6.3 |
CR revision of S3-220752 |
ZTE Corporation | 33.535 17.5.0 CR#1271 catF | AKMA | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221228 | NF selects AAnF in clause 6.7 |
CR revision of S3-220753 |
ZTE Corporation | 33.535 17.5.0 CR#1281 catF | AKMA | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221229 | New SID on NGRTC |
SID new revision of S3-221086 |
Huawei,HiSilicon | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221230 | threat modifications for token verification |
draftCR revision of S3-221091 |
Huawei,HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-107-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-221231 | threat modifications for SEPP |
draftCR revision of S3-221092 |
Huawei,HiSilicon | SCAS_5G_Ph2 | Rel-18 |
S3-107-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-221232 | Update of Solution #12 |
pCR revision of S3-221096 |
Huawei, HiSilicon | 33.875 1.1.0 | FS_eSBA_SEC | Rel-18 |
S3-107-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-221233 | Clarification on the NSWO in the UE side |
CR revision of S3-221098 |
Huawei, HiSilicon | 33.501 17.5.0 CR#14131 catF | NSWO_5G | Rel-17 |
S3-107-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-221234 | Removing the Ens on the SCP authorization |
CR revision of S3-221099 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#14141 catF | TEI17 | Rel-17 |
S3-107-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-221235 | Draft TR 33.739 0.1.0 | draft TR | Huawei, HiSilicon | FS_EDGE_Ph2 | Rel-18 |
S3-107-e AI: 4.11 |
approved | [WTS] [JSN] | |
S3-221236 | New KI for security of certificate update |
pCR revision of S3-220823 |
Huawei, HiSilicon, Ericsson | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221237 | New KI for Security protection of NF certificate enrolment |
pCR revision of S3-220824 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221238 | Add a new clause for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support |
pCR revision of S3-220830 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221239 | KI on Scalability of the home triggered primary authentication |
pCR revision of S3-220834 |
Huawei, HiSilicon, China telecom, LG Electronics, Nokia, Nokia Shanghai Bell, Beijing Xiaomi Mobile Software, Samsung | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-221240 | Adding a usecase of Kakma refresh |
pCR revision of S3-220835 |
Huawei, HiSilicon | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-221241 | Adding UDM Services for SUCI deconceal and authorization information retrieval |
pCR revision of S3-220842 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221242 | Resolving the EN on the needs and usage of 5GPRUK ID |
pCR revision of S3-220845 |
Huawei, HiSilicon, Interdigital, LG Electronics, ChinaTelecom,Xiaomi, CATT, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221243 | Format of 5GPRUK ID |
pCR revision of S3-220846 |
Huawei, HiSilicon, ZTE | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221244 | Clarification on the security of L2 U2NW |
pCR revision of S3-220848 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221245 | Key derivation related clarification in CP-based UE-to-Network relay procedures |
pCR revision of S3-220850 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221246 | New SID on security enhancements for 5G multicast-broadcast services Phase 2 |
SID new revision of S3-220856 |
Huawei, HiSilicon | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221247 | Removing the Editor’s Note and add clarifications in the security mechanisms for MBS |
CR revision of S3-220858 |
Huawei, HiSilicon | 33.501 17.5.0 CR#13731 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-221248 | Clarifications on the control-plane and user-plane procedures |
CR revision of S3-220859 |
Huawei, HiSilicon | 33.501 17.5.0 CR#13741 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-221249 | Enhancement for service announcement |
CR revision of S3-220860 |
Huawei, HiSilicon | 33.501 17.5.0 CR#13751 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-221250 | Update for solution 5 |
pCR revision of S3-220866 |
Huawei, HiSilicon | 33.848 0.11.0 | FS_SIV | Rel-16 |
S3-107-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-221251 | New SID on Enhancement of User Consent for 3GPP Services |
SID new revision of S3-220867 |
Huawei, HiSilicon | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221252 | Clarification on PRUK ID |
pCR revision of S3-220869 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221253 | Clarifications on the multicast security context handling in session creation procedure |
CR revision of S3-220870 |
Huawei, HiSilicon | 33.501 17.5.0 CR#13791 catF | 5MBS | Rel-17 |
S3-107-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-221254 | Reply LS on the Indication of Network Assisted Positioning method |
LS out LS is reply to S3-220659 source LS: C4-222306 LS To: CT4, SA2 revision of S3-220872 |
Huawei, HiSilicon | Rel-17 |
S3-107-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-221255 | Clarification on the description of PRUK |
pCR revision of S3-220881 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221256 | Clarification on the secondary authentication procedure |
pCR revision of S3-220882 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221257 | Update general clause for secondary authentication |
pCR revision of S3-220883 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221258 | 33.926-Rewrite the 5G MnF GNP model |
draftCR revision of S3-220886 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-221259 | 33.926-Add new assets to the OAM functions |
draftCR revision of S3-220887 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-221260 | 33.926-Add a new threat |
draftCR revision of S3-220888 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-221261 | Adding a usecase of SoR Counter Wrap around |
pCR revision of S3-220892 |
Huawei, HiSilicon, LG Electronics France, Beijing Xiaomi Mobile Software | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-221262 | Reply LS on Clarification on MBS Security Keys |
LS out LS To: CT4 revision of S3-221154 |
Huawei, HiSilicon | Rel-17 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | ||
S3-221263 | draftCR to TR 33.926 for SCAS 5G Ph2 | draftCR | Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-221264 | TR 33.741 | draft TR | Huawei, HiSilicon | FS_HN_Auth | Rel-18 |
S3-107-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-221265 | New SID on Personal IoT Networks Security Aspects |
SID new revision of S3-220709 |
vivo, Apple, ZTE, Xiaomi, CATT, OPPO, China Unicom, China Telecom, CableLabs, InterDigital, LGE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola mobility, Philips, China Mobile, Qualcomm | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221266 | TR 33.809 | draft TR | Apple Computer Trading Co. Ltd | FS_5GFBS | Rel-17 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-221267 | UDM interaction for Anonymous SUCI |
CR revision of S3-220913 |
Ericsson, Lenovo, Xiaomi | 33.501 17.5.0 CR#13811 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221268 | LS reply on Reply LS on NTN specific User Consent and UE location in connected mode in NTN |
LS out LS is reply to S3-220665 LS To: RAN2 revision of S3-221063 |
Ericsson | Rel-17 |
S3-107-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-221269 | KI on Protection of data and analytics exchange in roaming case |
pCR revision of S3-220774 |
China Mobile | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-221270 | Draft TR 33.876 Study on Standardising Automated Certificate Management in SBA | draft TR | Nokia Poland | FS_ACM_SBA | Rel-17 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] | |
S3-221271 | Remote UE Report in UP based solution |
pCR revision of S3-220967 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221272 | Rephrasing Clause 6.2.1 to emphasize that security parameters for PC5 Direct Communication are determined during Direct Discovery |
pCR revision of S3-220968 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221273 | Resolution of inconsistency in SUCI usage during UE onboarding. |
CR revision of S3-221011 |
Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#14011 catF | eNPN | Rel-17 |
S3-107-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-221274 | Clarification of access token usage in EC |
CR revision of S3-220922 |
Ericsson | 33.558 17.0.0 CR#21 catF | eEDGE_5GC | Rel-17 |
S3-107-e AI: 4.11 |
agreed | [WTS] [JSN] |
S3-221275 | Editorial corrections and technical clarifications |
CR revision of S3-221130 |
Ericsson | 33.558 17.0.0 CR#12 catF | eEDGE_5GC | Rel-17 |
S3-107-e AI: 4.11 |
agreed | [WTS] [JSN] |
S3-221276 | New SID on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the NR Air Interface and NG-RAN |
SID new revision of S3-221062 |
Ericsson | Rel-18 |
S3-107-e AI: 6 |
agreed | [WTS] [JSN] | ||
S3-221277 | A new key issue for single automated certificate management protocol and procedures |
pCR revision of S3-220919 |
Ericsson | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221278 | A new key issue for the relation between NF lifecycle and certificate lifecycle |
pCR revision of S3-220920 |
Ericsson | 33.876 0.1.0 | FS_ACM_SBA | Rel-18 |
S3-107-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-221279 | Draft TR 33.738 | draft TR | CMCC | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-221280 | TR 33.875-120 | draft TR | Nokia UK | FS_eSBA_SEC | Rel-17 |
S3-107-e AI: 5.4 |
approved | [WTS] [JSN] | |
S3-221281 | pCR to TS33.503 Abbreviations update |
pCR revision of S3-221003 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221282 | pCR to TS33.503 Clause 6.3 Clarification text for Kausf_p |
pCR revision of S3-221014 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221283 | Clarification on N32-f connection establishment with TLS |
CR revision of S3-220728 |
Nokia, Nokia Shanghai Bell | 33.501 16.10.0 CR#13641 catF | TEI16 | Rel-16 |
S3-107-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-221284 | pCR to TS33.503 Clause 6.3 Solution for co-existence of UP and CP security options |
pCR revision of S3-221015 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221285 | Clarification on N32-f connection establishment with TLS |
CR revision of S3-220729 |
Nokia, Nokia Shanghai Bell | 33.501 17.5.0 CR#13651 catA | TEI16 | Rel-17 |
S3-107-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-221286 | Draft TS 33.503 v0.4.0 Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) | draft TS | CATT | 5GS_Ph1-SEC, 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-221287 | Requirement to KI on roaming hub |
pCR revision of S3-220933 |
Nokia, Nokia Shanghai Bell | 33.875 1.1.0 | 5G_eSBA | Rel-18 |
S3-107-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-221288 | Scope of TR 33.737 |
pCR revision of S3-220811 |
China Mobile | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-221289 | Key issue of introducing application proxy into AKMA |
pCR revision of S3-220814 |
China Mobile | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-221290 | TR 33.870-020 | draft TR | Interdigital | FS_Id_Prvc | Rel-18 |
S3-107-e AI: 5.6 |
approved | [WTS] [JSN] | |
S3-221291 | Clarifications to secondary authentication PDU Session Container |
CR revision of S3-220685 |
Intel Corporation (UK) Ltd | 33.501 15.15.0 CR#13571 catF | 5GS_Ph1-SEC | Rel-15 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221292 | Clarifications to secondary authentication PDU Session Container |
CR revision of S3-220686 |
Intel Corporation (UK) Ltd | 33.501 16.10.0 CR#13581 catA | 5GS_Ph1-SEC | Rel-16 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221293 | Clarifications to secondary authentication PDU Session Container |
CR revision of S3-220687 |
Intel Corporation (UK) Ltd | 33.501 17.5.0 CR#13591 catA | 5GS_Ph1-SEC | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221294 | PC5 security policy provisioning for user-plane L3 U2N relay solution |
pCR revision of S3-220994 |
Qualcomm Incorporated, Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221295 | CR to ProSe TS - Address the Editor’s Notes in clause 6.3.5 |
pCR revision of S3-220996 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221296 | CR to ProSe TS – Removing an Editor’s Note in user plane based U2N procedure |
pCR revision of S3-220999 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221297 | CR to ProSe TS - Clarification on Knrp derivation for U2N relay over user plane |
pCR revision of S3-221001 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221298 | Avoid linkage between security functions and UE Radio Access Capabilities |
CR revision of S3-221143 |
VODAFONE | 33.401 17.1.0 CR#7081 catF | UPIP_SEC_LTE | Rel-17 |
S3-107-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-221299 | Cover page TS 33.503 | TS or TR cover | CATT | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-221300 | Coversheet TR 33.874 | TS or TR cover | Huawei | FS_eNS2_SEC | Rel-18 |
S3-107-e AI: 5.5 |
approved | [WTS] [JSN] | |
S3-221301 | Living document for MnF SCAS: draftCR to TR 33.926 |
draftCR revision of S3-220893 |
Huawei, HiSilicon | SCAS_5G_MF | Rel-18 |
S3-107-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-221302 | Update on 5G ProSe restricted discovery procedure for U2N relay |
pCR revision of S3-221000 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
S3-221310 | Agenda | agenda | SA WG3 Chair |
S3-107-e-Ad Hoc AI: 1 |
approved | [WTS] [JSN] | |||
S3-221311 | Process for SA3#107e meeting | other | SA WG3 Chair |
S3-107-e-Ad Hoc AI: 1 |
noted | [WTS] [JSN] | |||
S3-221312 | Process and agenda for SA3#107e | other | SA WG3 Chair |
S3-107-e-Ad Hoc AI: 1 |
noted | [WTS] [JSN] | |||
S3-221313 | LS on 5GC information exposure to UE |
LS in LS reply in S3-221621 |
S2-2205286 |
S3-107-e-Ad Hoc AI: 5.2 |
replied to | [WTS] [JSN] | |||
S3-221314 | skeleton for draft TR 33.884 SNAAPP security(FS_SNAAPPY) | draft TR | NTT DOCOMO | FS_SNAAPPY | Rel-18 |
S3-107-e-Ad Hoc AI: 5.11 |
approved | [WTS] [JSN] | |
S3-221315 | LS on user’s consent for EDGEAPP | LS in | C3-223780 |
S3-107-e-Ad Hoc AI: 3 |
postponed | [WTS] [JSN] | |||
S3-221316 | LS to 3GPP CT4 on Identification of source PLMN-ID in SBA | LS in | GSMA |
S3-107-e-Ad Hoc AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-221317 | LS on V2X PC5 link for unicast communication with null security algorithm |
LS in LS reply in S3-221590, S3-221590 |
R5-222035 |
S3-107-e-Ad Hoc AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221318 | Solution 5 EN on Certificates and Tokens |
pCR revised to S3-221648 |
U.S. National Security Agency | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
revised | [WTS] [JSN] |
S3-221319 | New key issue on Protecting Identification of PIN and PIN Privacy | pCR | InterDigital, Inc. | 33.882 0.0.1 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221320 | New key issue on UE privacy protection and authorization in NW exposure of UE traffic related information to AF | pCR | InterDigital Communications | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
noted | [WTS] [JSN] |
S3-221321 | New key issue on Secure Communication of between PINEs | pCR | InterDigital, Inc. | 33.882 0.0.1 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221322 | New key issue on Authorization for ACR | pCR | InterDigital Communications | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
noted | [WTS] [JSN] |
S3-221323 | New key issue on ACR security | pCR | InterDigital Communications | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
noted | [WTS] [JSN] |
S3-221324 | New key issue on Federated Learning AIML model protection | pCR | InterDigital Communications | 33.898 0.0.1 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221325 | New key issue on Secure policy and parameters provisioning for PIN | pCR | InterDigital, Inc. | 33.882 0.0.1 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221326 | New key issue on Federated Learning AIML model privacy protection | pCR | InterDigital Communications | 33.898 0.0.1 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221327 | New key issue on Authorization of PINE | pCR | InterDigital, Inc. | 33.882 0.0.1 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221328 | New key issue on PIN and PINE discovery authorization | pCR | InterDigital, Inc. | 33.882 0.0.1 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221329 | New solution for Key issue #1 | pCR | InterDigital, Inc. | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221330 | Key issue on Privacy protection over the UE-to-UE Relay | pCR | InterDigital, Europe, Ltd. | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221331 | Key Issue on Authorization in the UE-to-UE Relay Scenario |
pCR revised to S3-221608 |
InterDigital, Europe, Ltd. | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
revised | [WTS] [JSN] |
S3-221332 | Key Issue on Security of UE-to-UE Relay |
pCR revised to S3-221609 |
InterDigital, Europe, Ltd. | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
revised | [WTS] [JSN] |
S3-221333 | Key Issue on Direct C2 Security |
pCR revised to S3-221610 |
InterDigital, Europe, Ltd. | 33.891 0.0.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
revised | [WTS] [JSN] |
S3-221334 | Key Issue on Direct C2 Authorization | pCR | InterDigital, Europe, Ltd. | 33.891 0.0.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
noted | [WTS] [JSN] |
S3-221335 | New Key Issue on controlling access of PIN elements to 5G network | pCR | Nokia, Nokia Shanghai Bell | 33.882 0.0.1 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
merged | [WTS] [JSN] |
S3-221336 | New Key Issue on Securing API invocation from UE applications | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.0.0 | FS_SNAAPPY | Rel-18 |
S3-107-e-Ad Hoc AI: 5.11 |
merged | [WTS] [JSN] |
S3-221337 | Updates to Solution #5 |
pCR revised to S3-221701 |
Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
revised | [WTS] [JSN] |
S3-221338 | Address EN on Run-time Attestation |
pCR revised to S3-221702 |
Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
revised | [WTS] [JSN] |
S3-221339 | Remove EN in clause 6.6.3.4 | pCR | Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221340 | New key issue on users identified by Priority Access |
pCR revised to S3-221642 |
Johns Hopkins University APL, US National Security Agency, CISA ECD, Peraton Labs, Interdigital, Apple | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
revised | [WTS] [JSN] |
S3-221341 | Skeleton for 5WWC Ph2 study | pCR | Nokia, Nokia Shanghai Bell | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
approved | [WTS] [JSN] |
S3-221342 | Scope of 5WWC study |
pCR revised to S3-221636 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
revised | [WTS] [JSN] |
S3-221343 | Key issue on authentication of AUN3 device not supporting EAP | pCR | Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
noted | [WTS] [JSN] |
S3-221344 | Key issue on authentication of AUN3 device supporting EAP |
pCR revised to S3-221637 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
revised | [WTS] [JSN] |
S3-221345 | Key issue on Authentication of UE behind RG and connected via NSWO | pCR | Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
noted | [WTS] [JSN] |
S3-221346 | Key issue on Security aspect of slice information exposure of N3IWF/TNGF |
pCR revised to S3-221638 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
revised | [WTS] [JSN] |
S3-221347 | Key issue on authorization of AIML operations | pCR | Nokia, Nokia Shanghai Bell | 33.898 0.0.0 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221348 | Key issue on authorization of UE accessing the 5G analytics | pCR | Nokia, Nokia Shanghai Bell | 33.898 0.0.0 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221349 | Key issue on securing AIML operation | pCR | Nokia, Nokia Shanghai Bell | 33.898 0.0.0 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221350 | Key issue on Security criteria of UE selection for AIML | pCR | Nokia, Nokia Shanghai Bell | 33.898 0.0.0 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221351 | Update in KI1 for encryption keys |
pCR revised to S3-221635 |
Nokia, Nokia Shanghai Bell | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
revised | [WTS] [JSN] |
S3-221352 | Solution on AKMA roaming |
pCR revised to S3-221634 |
Nokia, Nokia Shanghai Bell | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
revised | [WTS] [JSN] |
S3-221353 | Solution on HN triggering primary authentication for various scenarios |
pCR revised to S3-221633 |
Nokia, Nokia Shanghai Bell | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221354 | Solution on Kaf refresh without primary authentication -UA* | pCR | Nokia, Nokia Shanghai Bell | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221355 | Solution on Kaf refresh without primary authentication- AAnF | pCR | Nokia, Nokia Shanghai Bell | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221356 | Key Issue for AKMA roaming scenario | pCR | THALES | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
merged | [WTS] [JSN] |
S3-221357 | Solution for Key Issue #2.2 |
pCR revised to S3-221704 |
THALES | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221358 | draft-LS reply on 5GC information exposure to UE |
LS out LS is reply to S3-221313 LS To: SA2 revised to S3-221621 |
NTT DOCOMO | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
revised | [WTS] [JSN] | ||
S3-221359 | pCR to 33.884, scope | pCR | NTT DOCOMO | 33.884 0.0.0 | FS_SNAAPPY | Rel-18 |
S3-107-e-Ad Hoc AI: 5.11 |
approved | [WTS] [JSN] |
S3-221360 | Key issue on application impersonation | pCR | Nokia, Nokia Shanghai Bell | 33.892 0.0.1 | FS_USIA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
noted | [WTS] [JSN] |
S3-221361 | Key issue on connected and idle mode mobility | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.0.1 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
noted | [WTS] [JSN] |
S3-221362 | Key issue on non-3GPP access in SNPN’s | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.0.1 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
merged | [WTS] [JSN] |
S3-221363 | Key issue on providing access to localised services | pCR | Nokia, Nokia Shanghai Bell | 33.858 0.0.1 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
noted | [WTS] [JSN] |
S3-221364 | Addressing the editor’s note in 6.27.2.1.1 of Sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.18.0 | FS_5GFBS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221365 | New solution on authorization of AI/ML model retrieving |
pCR revised to S3-221595 |
China Telecommunications | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
revised | [WTS] [JSN] |
S3-221366 | Addressing EN on NR Repeater in 6.27.2.2.4 of Sol#27 | pCR | CableLabs | 33.809 0.19.0 | FS_5GFBS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221367 | New solution on Using Federated-Learning-related Analytics Id for authorization of selection of participant NWDAF instances in the Federated Learning group | pCR | China Telecommunications | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
noted | [WTS] [JSN] |
S3-221368 | Addressing the editor’s note in 6.27.2.2.1of Sol#27 | pCR | CableLabs, Deutsche Telekom, Philips International B.V. | 33.809 0.19.0 | FS_5GFBS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221369 | New solution on topology hiding in data and analytics exchange in roaming case | pCR | China Telecommunications | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
noted | [WTS] [JSN] |
S3-221370 | LS out on authenticity and replay protection of system information |
LS out LS To: RAN2 revised to S3-221612 |
CableLabs, Deutsche Telekom, Philips International B.V., Ericsson, InterDigital, Apple, Johns Hopkins University APL, NIST | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
revised | [WTS] [JSN] | ||
S3-221371 | Evaluation of solution #4 | pCR | Huawei, HiSilicon, Ericsson, Apple, Philips | 33.809 0.19.0 | FS_5GFBS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221372 | Skeleton of TR33.886 | pCR | Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
approved | [WTS] [JSN] |
S3-221373 | Scope of TR33.886 |
pCR revised to S3-221628 |
Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
revised | [WTS] [JSN] |
S3-221374 | New KI-providing VPLMN slice information to roaming UE |
pCR revised to S3-221629 |
Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
revised | [WTS] [JSN] |
S3-221375 | New KI-temprory slices and slice authorization |
pCR revised to S3-221630 |
Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
revised | [WTS] [JSN] |
S3-221376 | New KI on NSAC |
pCR revised to S3-221631 |
Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
revised | [WTS] [JSN] |
S3-221377 | New solution Authentication mechanism selection in EDGE |
pCR revised to S3-221694 |
OPPO | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221378 | Solution for Privacy aspects of variable length user identifiers | pCR | Nokia Japan | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221379 | New solution Authentication mechanism selection among EEC, ECS, and EES |
pCR revised to S3-221695 |
OPPO | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221380 | Key Issue for Management of Automated Bulk Certificate updates for SBA leading to temporary service unavailability |
pCR revised to S3-221585 |
Nokia Japan | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221381 | Update KI #6 for a new security threat |
pCR revised to S3-221661 |
Huawei, HiSilicon | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221382 | New solution for KI #6 Relation between certificate management lifecycle and NF management lifecycle | pCR | Huawei, HiSilicon | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
noted | [WTS] [JSN] |
S3-221383 | Integrity and confidentiality of information over the UE-to-UE Relay | pCR | Huawei, HiSilicon | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221384 | new solution for AKMA roaming when both UE and AF are in VPLMN |
pCR revised to S3-221662 |
Huawei, HiSilicon | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
revised | [WTS] [JSN] |
S3-221385 | new solution for AKMA roaming when UE is in visited network but the AF in Home network. | pCR | Huawei, HiSilicon | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] |
S3-221386 | Skeleton update |
pCR revised to S3-221663 |
Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221387 | new KI in interworking | pCR | Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221388 | new KI in SoR/UPU counter wraparound | pCR | Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221389 | new KI in Kakma refresh |
pCR revised to S3-221664 |
Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221390 | AUSF triggered the primary authentication | pCR | Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221391 | New KI on race condition | pCR | Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221392 | Update of KI #3 to contribute an EN |
pCR revised to S3-221689 |
Huawei, HiSilicon | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
revised | [WTS] [JSN] |
S3-221393 | Reply LS on Clarification on MBS Security Keys |
LS out LS is reply to S3-221153 LS To: CT4 revised to S3-221665 |
Huawei, HiSilicon | Rel-18 |
S3-107-e-Ad Hoc AI: 3 |
revised | [WTS] [JSN] | ||
S3-221394 | Skeleton of MBS phase2 | draft TR | Huawei, HiSilicon | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
approved | [WTS] [JSN] | |
S3-221395 | Scope of MBS phase2 | pCR | Huawei, HiSilicon | 33.883 0.0.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
approved | [WTS] [JSN] |
S3-221396 | New key issue on TMGI protection |
pCR revised to S3-221666 |
Huawei, HiSilicon | 33.883 0.0.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
revised | [WTS] [JSN] |
S3-221397 | New key issue on security handling in MOCN network sharing scenario |
pCR revised to S3-221667 |
Huawei, HiSilicon | 33.883 0.0.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
revised | [WTS] [JSN] |
S3-221398 | New key issue on privacy protection for Ranging/Sidelink positioning with the assistance of assistant UE | pCR | Huawei, HiSilicon | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
merged | [WTS] [JSN] |
S3-221399 | Authentication mechanism selection between the EEC and ECS/EES | pCR | Huawei, HiSilicon | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
noted | [WTS] [JSN] |
S3-221400 | Skeleton of UC3S_Ph2 | draft TR | Huawei, HiSilicon | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
approved | [WTS] [JSN] | |
S3-221401 | Scope of UC3S_Ph2 | pCR | Huawei, HiSilicon | 33.896 0.0.0 | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
approved | [WTS] [JSN] |
S3-221402 | New key issue on Roaming of eNA |
pCR revised to S3-221668 |
Huawei, HiSilicon | 33.896 0.0.0 | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
revised | [WTS] [JSN] |
S3-221403 | New Key Issue on NTN |
pCR revised to S3-221669 |
Huawei, HiSilicon | 33.896 0.0.0 | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
revised | [WTS] [JSN] |
S3-221404 | evaluation on solution 5 |
pCR revised to S3-221670 |
Huawei, HiSilicon | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
revised | [WTS] [JSN] |
S3-221405 | Reply LS about V2X PC5 unicast link with null security algorithm |
LS out LS is reply to S3-221317 source LS: R5-222035 LS To: RAN5 |
Huawei, HiSilicon | Rel-18 |
S3-107-e-Ad Hoc AI: 3 |
merged | [WTS] [JSN] | ||
S3-221406 | New Key Issue on security of ProSe groupcast communications | pCR | Huawei, HiSilicon | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
noted | [WTS] [JSN] |
S3-221407 | New Key Issue on security enhancement of C2 communication | pCR | Huawei, HiSilicon | 33.891 0.0.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
merged | [WTS] [JSN] |
S3-221408 | New solution for key issue 1 |
pCR revised to S3-221671 |
Huawei, HiSilicon | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221409 | New solution for key issue 3 and 4 based on OCSP |
pCR revised to S3-221672 |
Huawei, HiSilicon | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221410 | New solution for key issue 1 | pCR | Huawei, HiSilicon | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221411 | New KI on Authentication and Authorization between V-ECS and H-ECS |
pCR revised to S3-221673 |
Huawei, HiSilicon | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221412 | New KI on Transport security for the EDGE10 interface | pCR | Huawei, HiSilicon | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221413 | New KI on Authentication and Authorization between AC and EEC | pCR | Huawei, HiSilicon | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
noted | [WTS] [JSN] |
S3-221414 | New key issue on security protection for Ues in RRC inactive state |
pCR revised to S3-221674 |
Huawei, HiSilicon | 33.883 0.0.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
revised | [WTS] [JSN] |
S3-221415 | New solution UDM triggered primary authentication |
pCR revised to S3-221675 |
Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221416 | authentication and authorization to N3GPP device behind 5G-RG | pCR | Huawei, HiSilicon | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
noted | [WTS] [JSN] |
S3-221417 | Authentication and authorization to PINE behind PEGC and PEMC |
pCR revised to S3-221676 |
Huawei, HiSilicon | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
revised | [WTS] [JSN] |
S3-221418 | Authorization in the UE-to-UE relay scenario | pCR | Huawei, HiSilicon | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221419 | Privacy of information over the UE-to-UE Relay |
pCR revised to S3-221677 |
Huawei, HiSilicon | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
revised | [WTS] [JSN] |
S3-221420 | Reply LS on User Consent for EDGEAPP |
LS out LS To: CT3 |
Huawei, HiSilicon | Rel-18 |
S3-107-e-Ad Hoc AI: 3 |
noted | [WTS] [JSN] | ||
S3-221421 | Key issue on Authorization in the UE-to-UE relay scenario | pCR | China Telecomunication Corp. | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221422 | Key issue on Integrity and confidentiality of information over the UE-to-UE | pCR | China Telecomunication Corp. | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221423 | Key issue on Secondary authentication of Remote UE via L3 UE-to-Network relay without N3IWF | pCR | China Telecomunication Corp. | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
noted | [WTS] [JSN] |
S3-221424 | Key Issue for NTN specific user consent for UE location sharing | pCR | Nokia Japan | 33.896 0.0.1 | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
merged | [WTS] [JSN] |
S3-221425 | Add context to the architecture clause | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221426 | Key issue on authorization in multi-path transmission for UE-to-Network Relay scenario | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
noted | [WTS] [JSN] |
S3-221427 | Key issue on authorization in the UE-to-UE relay scenario | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221428 | Key issue on Integrity and confidentiality of information over the UE-to-UE Relay | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221429 | Key issue on Privacy of information over the UE-to-UE Relay | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221430 | Key issue on Support direct communication path switching between PC5 and Uu | pCR | ZTE Corporation | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
noted | [WTS] [JSN] |
S3-221431 | SUPI padding solution on Key issue #1 | pCR | ZTE Corporation | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221432 | Discussion on the regulatory control point in AKMA roaming | pCR | ZTE Corporation | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] |
S3-221433 | New solution about the roaming AKMA architecture of the AF inside and outside the HPLMN |
pCR revised to S3-221651 |
ZTE Corporation | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
revised | [WTS] [JSN] |
S3-221434 | New solution about the roaming AKMA architecture of the AF inside and outside the VPLMN |
pCR revised to S3-221652 |
ZTE Corporation | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
revised | [WTS] [JSN] |
S3-221435 | Update the Key issue of AKMA roaming | pCR | ZTE Corporation | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
merged | [WTS] [JSN] |
S3-221436 | Home network triggered authentication solution for 4G to 5G interworking on Key issue #1 |
pCR revised to S3-221653 |
ZTE Corporation | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221437 | Kaf update solution without triggering primary authentication on Key issue #2 | pCR | ZTE Corporation | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221438 | ECS EES authentication method information provisioning solution on Key issue #2.2 |
pCR revised to S3-221654 |
ZTE Corporation | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221439 | new key issue Exposure of Network Capabilities | pCR | ZTE Corporation | 33.894 0.0.0 | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
noted | [WTS] [JSN] |
S3-221440 | Key issue on secure data transfer between PEGC PEMC and PIN NF | pCR | ZTE Corporation | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221441 | Add context to the architecture assumption | pCR | ZTE Corporation | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
merged | [WTS] [JSN] |
S3-221442 | Key issue on discovery message protection between reference UEs and target UEs | pCR | ZTE Corporation | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
merged | [WTS] [JSN] |
S3-221443 | Key issue on security of network based sidelink positioning | pCR | ZTE Corporation | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
noted | [WTS] [JSN] |
S3-221444 | Key issue on security of service exposure to a UE | pCR | ZTE Corporation | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
noted | [WTS] [JSN] |
S3-221445 | Key issue on security of UE based sidelink positioning | pCR | ZTE Corporation | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
noted | [WTS] [JSN] |
S3-221446 | Key issue on UE Identity protection during UE-to-UE relay discovery | pCR | China Telecomunication Corp. | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221447 | Key issue on Privacy protection over the UE-to-UE Relay | pCR | China Telecomunication Corp. | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221448 | Key Issue on secure storage and limited access to NF credentials | other | Intel | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
noted | [WTS] [JSN] | |
S3-221449 | Key Issue on Secure Trust Evaluation | other | Intel |
S3-107-e-Ad Hoc AI: 5.21 |
noted | [WTS] [JSN] | |||
S3-221450 | Authentication and Authorization for Localized Services | other | Intel | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
noted | [WTS] [JSN] | |
S3-221451 | Anomaly in Multivendor NWDAF Framework | pCR | Intel | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
noted | [WTS] [JSN] |
S3-221452 | Authorization and Authentication of ML model transfer |
pCR revised to S3-221639 |
Intel | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
revised | [WTS] [JSN] |
S3-221453 | Revision on KI#2 | pCR | China Mobile Com. Corporation | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221454 | KI on Security for NWDAF-assisted application detection | pCR | China Mobile Com. Corporation | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221455 | Key issue on Privacy protection for Network assisted Sidelink Positioning | pCR | China Telecomunication Corp. | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
merged | [WTS] [JSN] |
S3-221456 | Discussion paper of AKMA roaming | discussion | China Mobile | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] | ||
S3-221457 | New key issue of multiple AAnF sets in AKMA roaming scenario | pCR | LG Electronics France | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] |
S3-221458 | Solution of introducing AP into AKMA |
pCR revised to S3-221688 |
China Mobile | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
revised | [WTS] [JSN] |
S3-221459 | New solution of AKMA anchor key registration to the AAnF in VPLMN after primary authentication |
pCR revised to S3-221596 |
LG Electronics France | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
revised | [WTS] [JSN] |
S3-221460 | Padding-based solution to the leakage of the length of SUPI through SUCI. | pCR | Ericsson LM | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221461 | Discussion paper about the security enhancements enabling UE’s receiving Multicast MBS Session data in RRC_INACTIVE state | discussion | Ericsson | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
noted | [WTS] [JSN] | |
S3-221462 | Hash-based solution to the leakage of the length of SUPI through SUCI | pCR | Ericsson LM | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221463 | Map-based solution to the leakage of the length of SUPI through SUCI | pCR | Ericsson LM | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221464 | 5GFBS - Security risk in lower layers | pCR | Apple | 33.809 0.18.0 | FS_5GFBS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221465 | IDPrvc - Security issue on C-RNTI | pCR | Apple | 33.87 0.1.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221466 | AKMA - New solution on AP | pCR | Apple | 33.737 0.0.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
merged | [WTS] [JSN] |
S3-221467 | MEC - Negotiation procedure for the authentication and authorization |
LS out LS To: CT3 revised to S3-221678 |
Apple | Rel-17 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] | ||
S3-221468 | HN-auth-NAS based HN triggered authentication | pCR | Apple | 33.741 0.0.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
noted | [WTS] [JSN] |
S3-221469 | Solution for anomalous NF behaviour detection by NWDAF |
pCR revised to S3-221617 |
Nokia, Nokia Shanghai Bell | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
revised | [WTS] [JSN] |
S3-221470 | Solution for AI-ML model authorization and retrieval |
pCR revised to S3-221615 |
Nokia, Nokia Shanghai Bell | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
revised | [WTS] [JSN] |
S3-221471 | Solution for access control and anonymization for data and analytics exchange in roaming |
pCR revised to S3-221616 |
Nokia, Nokia Shanghai Bell | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
revised | [WTS] [JSN] |
S3-221472 | New solution Security procedure of KAF refresh-MAC | pCR | OPPO | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221473 | A solution for certificate and NF lifecycle management relation |
pCR revised to S3-221658 |
Ericsson | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221474 | A new solution for using attestation to build initial trust for certificate management | pCR | Ericsson | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
noted | [WTS] [JSN] |
S3-221475 | A new solution of using CMP for certificate enrolment and renewal |
pCR revised to S3-221659 |
Ericsson | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221476 | [DRAFT] Reply LS on user’s consent for EDGEAPP |
LS out LS is reply to C3-223780 LS To: CT3 |
Ericsson | eEDGE_5GC | Rel-17 |
S3-107-e-Ad Hoc AI: 3 |
noted | [WTS] [JSN] | |
S3-221477 | Updates to authentication and authorization key issue | pCR | Ericsson | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221478 | A new key issue on authentication and authorization of UE in UE originated API invocation |
pCR revised to S3-221660 |
Ericsson | 33.884 0.0.0 | FS_SNAAPPY | Rel-18 |
S3-107-e-Ad Hoc AI: 5.11 |
revised | [WTS] [JSN] |
S3-221479 | A new key issue on user consent in API invocations | pCR | Ericsson | 33.884 0.0.0 | FS_SNAAPPY | Rel-18 |
S3-107-e-Ad Hoc AI: 5.11 |
noted | [WTS] [JSN] |
S3-221480 | New solution Security procedure of KAF refresh-Counter | pCR | OPPO | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221481 | New solution Security procedure of KAF-Nonce | pCR | OPPO | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221482 | skeleton for NGRTC | draft TR | Huawei, HiSilicon | FS_NG_RTC_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.15 |
approved | [WTS] [JSN] | |
S3-221483 | Scope of TR 33.890 | pCR | Huawei, HiSilicon | 33.89 0.0.0 | FS_NG_RTC_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.15 |
approved | [WTS] [JSN] |
S3-221484 | New KI on 3rd party ID |
pCR revised to S3-221682 |
Huawei, HiSilicon | 33.89 0.0.0 | FS_NG_RTC_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.15 |
revised | [WTS] [JSN] |
S3-221485 | New solution on boot time attestation at 3GPP function level | pCR | Huawei, HiSilicon | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221486 | New solution on trust domain and slice Isolation | pCR | Huawei, HiSilicon | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] |
S3-221487 | New KI on data protection for the fast and efficient network exposure | pCR | Huawei, HiSilicon | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
noted | [WTS] [JSN] |
S3-221488 | New KI on how to authorize PDU session to support local traffic routing to access an EHE in the VPLMN |
pCR revised to S3-221683 |
Huawei, HiSilicon | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221489 | pCR to TR33.740 Clause Introduction and Scope | pCR | CATT | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
approved | [WTS] [JSN] |
S3-221490 | pCR to TR 33.740 Clause 4 Security Aspects of 5G ProSe |
pCR revised to S3-221640 |
CATT | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
revised | [WTS] [JSN] |
S3-221491 | pCR to TR33.740 Key Issue on Integrity and confidentiality of information over the UE-to-UE Relay | pCR | CATT | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221492 | Scope for Study on security aspects of enhanced support of Non-Public Networks phase 2 | pCR | Ericsson | 33.858 0.0.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
approved | [WTS] [JSN] |
S3-221493 | New Key Issue "Security of non-3GPP access for SNPN" |
pCR revised to S3-221681 |
Ericsson | 33.858 0.0.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
revised | [WTS] [JSN] |
S3-221494 | New Key Issue "Hosting network and UE mutual authentication" | pCR | Ericsson | 33.858 0.0.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
noted | [WTS] [JSN] |
S3-221495 | pCR to TR33.740 Key Issue on Authorization in the UE-to-UE relay scenario | pCR | CATT | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221496 | pCR to TR33.740 Key Issue on Privacy of information over the UE-to-UE Relay | pCR | CATT | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221497 | New solution on KI#1 UE based solution | pCR | NEC Corporation | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221498 | New solution on KI#1 AMF based solution |
pCR revised to S3-221697 |
NEC Corporation | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221499 | Key issue on misuse of OAuth 2.0 access token by anomalous Network functions | pCR | Nokia, Nokia Shanghai Bell | 33.894 0.0.0 | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
noted | [WTS] [JSN] |
S3-221500 | Key issue on determining and maintaining trust indication in 5G Core | pCR | Nokia, Nokia Shanghai Bell | 33.894 0.0.0 | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
noted | [WTS] [JSN] |
S3-221501 | Solution for secure initial enrolment of NF certificates |
pCR revised to S3-221620 |
Nokia, Nokia Shanghai Bell | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221502 | Proposed skeleton for TR 33.882 | pCR | vivo Mobile Communication (S) | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
approved | [WTS] [JSN] |
S3-221503 | Remote UE Security Establishment via U2U Relay | pCR | OPPO | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221504 | Scope of TR 33.882 | pCR | vivo Mobile Communication (S) | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
approved | [WTS] [JSN] |
S3-221505 | U2U Relay Trust Model |
pCR revised to S3-221699 |
OPPO | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
revised | [WTS] [JSN] |
S3-221506 | New KI for authentication of PINE | pCR | vivo Mobile Communication (S) | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
merged | [WTS] [JSN] |
S3-221507 | New Key Issue for controlling of remote provisioning | pCR | vivo Mobile Communication (S) | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221508 | TR 33.898 Skeleton |
pCR revised to S3-221583 |
OPPO | 33.898 0.0.0 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
revised | [WTS] [JSN] |
S3-221509 | Scope of TR 33.898 | pCR | OPPO | 33.898 0.0.0 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] |
S3-221510 | References in TR 33.898 | pCR | OPPO | 33.898 0.0.0 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] |
S3-221511 | Draft LS on 5GC Information Exposure to UE |
LS out LS is reply to S3-221313 LS To: SA2, SA1 |
OPPO |
S3-107-e-Ad Hoc AI: 5.2 |
merged | [WTS] [JSN] | |||
S3-221512 | Proposed skeleton for TR 33.891 | draft TR | Qualcomm Incorporated | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
approved | [WTS] [JSN] | |
S3-221513 | Proposed scope for TR 33.891 |
pCR revised to S3-221604 |
Qualcomm Incorporated | 33.891 0.0.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
revised | [WTS] [JSN] |
S3-221514 | Key issue for security of unicast connection |
other revised to S3-221605 |
Qualcomm Incorporated |
S3-107-e-Ad Hoc AI: 5.17 |
revised | [WTS] [JSN] | |||
S3-221515 | Solution using UDM to trigger authentication |
pCR revised to S3-221606 |
Qualcomm Incorporated | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221516 | AKMA Application Proxy solution based on GBA procedures | pCR | Qualcomm Incorporated | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
merged | [WTS] [JSN] |
S3-221517 | Scope of SUPI Type IMSI in KI#1 | pCR | Qualcomm Incorporated | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221518 | Addition of threats due to EAP in KI#1 | pCR | Qualcomm Incorporated | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
noted | [WTS] [JSN] |
S3-221519 | New Key Issue: Security for UE-to-UE Relay discovery |
pCR revised to S3-221693 |
Qualcomm Incorporated | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
revised | [WTS] [JSN] |
S3-221520 | Proposal for TR 33.894 Skeleton | draft TR | Lenovo | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
approved | [WTS] [JSN] | |
S3-221521 | Key Issue#1 on Need for continuous Trust evaluation | pCR | Lenovo, Nokia, Nokia Shanghai Bell, Rakuten Mobile Inc., Interdigital, US NSA, Motorola Solutions, Johns Hopkins University APL, Intel, Center for Internet Security | 33.894 0.0.1 | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
noted | [WTS] [JSN] |
S3-221522 | Security Assumptions | pCR | Lenovo, Rakuten Mobile Inc., Interdigital, US NSA, Motorola Solutions, Johns Hopkins University APL, Intel, Center for Internet Security | 33.894 0.0.1 | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
noted | [WTS] [JSN] |
S3-221523 | Update of Scope |
pCR revised to S3-221588 |
Lenovo, Rakuten Mobile Inc, Interdigital, US NSA, Motorola Solutions, Johns Hopkins University APL, Intel, Center for Internet Security | 33.894 0.0.1 | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
revised | [WTS] [JSN] |
S3-221524 | Corrections to TR 33.741 | pCR | Lenovo | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221525 | Solution to enable HN triggered Primary Authentication with AUSF | pCR | Lenovo | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221526 | Solution to enable HN triggered Primary Authentication with UDM |
pCR revised to S3-221589 |
Lenovo | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221527 | Authentication mechanism selection between EEC and ECS |
pCR revised to S3-221599 |
Samsung | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221528 | Authentication mechanism selection between EEC and EES |
pCR revised to S3-221600 |
Samsung | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221529 | Adding security threat and requirements to KI#1 | pCR | Samsung | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
merged | [WTS] [JSN] |
S3-221530 | New solution on HN initiated re-authentcation via AUSF |
pCR revised to S3-221601 |
Samsung | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221531 | New solution on UDM initiated re-authentcation based on AUSF request |
pCR revised to S3-221602 |
Samsung | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221532 | New solution for Kaf refresh | pCR | Samsung | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221533 | Key issue on Cyber-attack detection supported by NWDAF |
pCR revised to S3-221603 |
Samsung | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
revised | [WTS] [JSN] |
S3-221534 | Key issue on Privacy and security aspects of broadcasting Remote ID | pCR | Samsung | 33.891 0.0.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
noted | [WTS] [JSN] |
S3-221535 | DRAFT Reply LS on V2X PC5 link for unicast communication with null security algorithm |
LS out LS is reply to S3-220673 source LS: R5-222035 LS To: RAN WG5 revised to S3-221590 |
Lenovo | eV2XARC | Rel-17 |
S3-107-e-Ad Hoc AI: 3 |
revised | [WTS] [JSN] | |
S3-221536 | Null algorithm is not security deactivation | CR | Lenovo | 33.536 17.1.0 | eV2XARC | Rel-17 |
S3-107-e-Ad Hoc AI: 3 |
withdrawn | [WTS] [JSN] |
S3-221537 | 33.893: Draft Skeleton | draft TR | Xiaomi Technology | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
approved | [WTS] [JSN] | |
S3-221538 | 33.893: Scope | pCR | Xiaomi Technology | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
approved | [WTS] [JSN] |
S3-221539 | 33.893: Architecure Assumptions |
pCR revised to S3-221622 |
Xiaomi Technology | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
revised | [WTS] [JSN] |
S3-221540 | 33.893: New Key Issue on Privacy |
pCR revised to S3-221623 |
Xiaomi Technology | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
revised | [WTS] [JSN] |
S3-221541 | 33.893: New Key Issue on Authorization for Ranging/SL Positioning Service |
pCR revised to S3-221647 |
Beijing Xiaomi Mobile Software | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
revised | [WTS] [JSN] |
S3-221542 | 33.893: New Key Issue on Discovery Security |
pCR revised to S3-221624 |
Xiaomi Technology | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
revised | [WTS] [JSN] |
S3-221543 | 33.893: New Key Issue on Direct Communication Security | pCR | Xiaomi Technology | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
noted | [WTS] [JSN] |
S3-221544 | 33.896: New Key Issue on NTN Specific User Consent | pCR | Xiaomi Technology | 33.896 0.0.0 | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
merged | [WTS] [JSN] |
S3-221545 | 33.896: New Solution for NTN Specific User Consent | pCR | Xiaomi Technology | 33.896 0.0.0 | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
noted | [WTS] [JSN] |
S3-221546 | Key Issue on Authorization for Third Party Specific User ID Usage | pCR | Beijing Xiaomi Mobile Software | 33.89 0.0.0 | FS_NG_RTC_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.15 |
merged | [WTS] [JSN] |
S3-221547 | Key Issue on Verification of the Third Party User Specific ID | pCR | Beijing Xiaomi Mobile Software | 33.89 0.0.0 | FS_NG_RTC_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.15 |
merged | [WTS] [JSN] |
S3-221548 | Key Issue on Security for UE-to-UE Relay Discovery | pCR | Beijing Xiaomi Mobile Software | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221549 | Key Issue on Security of UE-to-UE Relay Communication | pCR | Beijing Xiaomi Mobile Software | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
merged | [WTS] [JSN] |
S3-221550 | New solution on UDM initiated Primary Authentication |
pCR revised to S3-221646 |
Beijing Xiaomi Mobile Software | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
revised | [WTS] [JSN] |
S3-221551 | New solution on AUSF initiated Primary Authentication | pCR | Beijing Xiaomi Mobile Software | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221552 | New solution on Cross-Certification Based Trust Chain in the SBA Architecture |
pCR revised to S3-221644 |
Beijing Xiaomi Mobile Software | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221553 | New solution on Interconnection CA Based Trust Chain in the SBA Architecture |
pCR revised to S3-221645 |
Beijing Xiaomi Mobile Software | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
revised | [WTS] [JSN] |
S3-221554 | KI#1, New Sol AKMA Application key request via proxy and NEF in roaming scenarios | pCR | Xiaomi Communication | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] |
S3-221555 | KI#1, New Sol Proxy-based AKMA Application key request in roaming scenarios | pCR | Xiaomi Communication | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] |
S3-221556 | KI#2, New Sol Authentication via proxy AKMA scenarios. | pCR | Xiaomi Communication | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] |
S3-221557 | KI#2, New Sol Authentication via proxy and NEF in AKMA scenarios | pCR | Xiaomi Communication | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] |
S3-221558 | New KI Multiple registrations in AKMA scenarios | pCR | Xiaomi Communication | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
noted | [WTS] [JSN] |
S3-221559 | KI#2.1, New Sol Authentication and authorization between EEC hosted in the roaming UE and ECS |
pCR revised to S3-221611 |
Xiaomi Communication | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221560 | KI#2.1, New Sol Authentication and authorization between EEC hosted in the roaming UE and EES |
pCR revised to S3-221613 |
Xiaomi Communication | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221561 | KI#2.2, New Sol 5GC-based authentication mechanism selection between EEC and ECS or EES |
pCR revised to S3-221614 |
Xiaomi Communication | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
revised | [WTS] [JSN] |
S3-221562 | New KI: Home control enhancement for eNPN | pCR | Xiaomi Communication | 33.858 0.0.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
noted | [WTS] [JSN] |
S3-221563 | New KI: Support for secure non-3GPP access for NPN | pCR | Xiaomi Communication | 33.858 0.0.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
merged | [WTS] [JSN] |
S3-221564 | New KI: Secure authentication of PINE | pCR | Xiaomi Communication | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
merged | [WTS] [JSN] |
S3-221565 | New KI: Secure provisioning of credentials for non-3GPP device via PEGC | pCR | Xiaomi Communication | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221566 | New KI: Privacy-preserving federated learning | pCR | Xiaomi Communication | 33.898 0.0.0 | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
noted | [WTS] [JSN] |
S3-221567 | Skeleton for TR 33.892 FS_USIA |
draft TR revised to S3-221593 |
Lenovo | FS_USIA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.18 |
revised | [WTS] [JSN] | |
S3-221568 | Scope for TR 33.892 | pCR | Lenovo | 33.892 0.0.0 | FS_USIA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.18 |
noted | [WTS] [JSN] |
S3-221569 | KI on determination of additional information for application identification |
pCR revised to S3-221594 |
Lenovo | 33.892 0.0.0 | FS_USIA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.18 |
revised | [WTS] [JSN] |
S3-221570 | AI/ML model storage and sharing security |
pCR revised to S3-221591 |
Lenovo | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
revised | [WTS] [JSN] |
S3-221571 | AKMA roaming and LI |
pCR revised to S3-221592 |
Lenovo | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
revised | [WTS] [JSN] |
S3-221572 | Detection of MitM attacks with secret paging | pCR | Lenovo | 33.809 0.19.0 | FS_5GFBS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
noted | [WTS] [JSN] |
S3-221573 | TR skeleton | draft TR | Ericsson | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.14 |
approved | [WTS] [JSN] | |
S3-221574 | Content for the scope clause of the technical report | pCR | Ericsson | 33.877 0.0.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.14 |
approved | [WTS] [JSN] |
S3-221575 | Initial content for the background clause of the technical report |
pCR revised to S3-221649 |
Ericsson | 33.877 0.0.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.14 |
revised | [WTS] [JSN] |
S3-221576 | Discussion about the home triggered primary authentication for interworking | discussion | Ericsson | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] | |
S3-221577 | Conclusion for the primary authentication upon interworking from EPS to 5GS | pCR | Ericsson | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221578 | Discussion about the need for initiating home triggered primary authentication for the SoR/UPU use case. | discussion | Ericsson | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] | |
S3-221579 | Conclusion for the primary authentication upon SoR and UPU counter wrap around. | pCR | Ericsson | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221580 | KI#2 update to remove the signalling overhead for KAF | pCR | Ericsson | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
noted | [WTS] [JSN] |
S3-221581 | Discussion about the roaming architecture | discussion | Ericsson | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
endorsed | [WTS] [JSN] | |
S3-221582 | pCR to 33.884, key issues from scope objective 1 | pCR | NTT DOCOMO | 33.884 0.0.0 | FS_SNAAPPY | Rel-18 |
S3-107-e-Ad Hoc AI: 5.11 |
withdrawn | [WTS] [JSN] |
S3-221583 | TR 33.898 Skeleton |
draft TR revision of S3-221508 |
OPPO | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] | |
S3-221584 | Null algorithm is not security deactivation | draftCR | Lenovo | eV2XARC | Rel-17 |
S3-107-e-Ad Hoc AI: 3 |
noted | [WTS] [JSN] | |
S3-221585 | Key Issue for Management of Automated Bulk Certificate updates for SBA leading to temporary service unavailability |
pCR revision of S3-221380 |
Nokia Japan | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
noted | [WTS] [JSN] |
S3-221586 | LS on CAPIF authorization roles related to FS_SNAAPP | LS in | S6-221771 |
S3-107-e-Ad Hoc AI: 5.11 |
postponed | [WTS] [JSN] | |||
S3-221587 | Reply LS on V2X PC5 link for unicast communication with null security algorithm |
LS in LS reply in S3-221590 |
C1-223972 |
S3-107-e-Ad Hoc AI: 3 |
replied to | [WTS] [JSN] | |||
S3-221588 | Update of Scope |
pCR revision of S3-221523 |
Lenovo, Rakuten Mobile Inc, Interdigital, US NSA, Motorola Solutions, Johns Hopkins University APL, Intel, Center for Internet Security | 33.894 0.0.1 | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
approved | [WTS] [JSN] |
S3-221589 | Solution to enable HN triggered Primary Authentication with UDM |
pCR revision of S3-221526 |
Lenovo | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221590 | Reply LS on V2X PC5 link for unicast communication with null security algorithm |
LS out LS is reply to S3-221317 source LS: R5-222035 LS To: RAN WG5 revision of S3-221535 |
Lenovo | eV2XARC | Rel-17 |
S3-107-e-Ad Hoc AI: 3 |
approved | [WTS] [JSN] | |
S3-221591 | AI/ML model storage and sharing security |
pCR revision of S3-221570 |
Lenovo | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221592 | AKMA roaming and LI |
pCR revision of S3-221571 |
Lenovo | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] |
S3-221593 | Skeleton for TR 33.892 FS_USIA |
draft TR revision of S3-221567 |
Lenovo | FS_USIA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.18 |
approved | [WTS] [JSN] | |
S3-221594 | KI on determination of additional information for application identification |
pCR revision of S3-221569 |
Lenovo | 33.892 0.0.0 | FS_USIA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.18 |
approved | [WTS] [JSN] |
S3-221595 | New solution on authorization of AI/ML model retrieving |
pCR revision of S3-221365 |
China Telecommunications | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221596 | New solution of AKMA anchor key registration to the AAnF in VPLMN after primary authentication |
pCR revision of S3-221459 |
LG Electronics France | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] |
S3-221597 | draft TR 33.884 | draft TR | DOCOMO Communications Lab. | FS_SNAAPPY | Rel-18 |
S3-107-e-Ad Hoc AI: 5.11 |
approved | [WTS] [JSN] | |
S3-221598 | draft-LS reply on 5GC information exposure to UE |
LS out LS is reply to S3-221313 LS To: SA2, SA1 |
NTT DOCOMO | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
withdrawn | [WTS] [JSN] | ||
S3-221599 | Authentication mechanism selection between EEC and ECS |
pCR revision of S3-221527 |
Samsung | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221600 | Authentication mechanism selection between EEC and EES |
pCR revision of S3-221528 |
Samsung | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221601 | New solution on HN initiated re-authentcation via AUSF |
pCR revision of S3-221530 |
Samsung | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221602 | New solution on UDM initiated re-authentcation based on AUSF request |
pCR revision of S3-221531 |
Samsung | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221603 | Key issue on Cyber-attack detection |
pCR revision of S3-221533 |
Samsung | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221604 | Proposed scope for TR 33.891 |
pCR revision of S3-221513 |
Qualcomm Incorporated | 33.891 0.0.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
approved | [WTS] [JSN] |
S3-221605 | Key issue for security of unicast connection |
other revision of S3-221514 |
Qualcomm Incorporated |
S3-107-e-Ad Hoc AI: 5.17 |
approved | [WTS] [JSN] | |||
S3-221606 | Solution using UDM to trigger authentication |
pCR revision of S3-221515 |
Qualcomm Incorporated | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221607 | Draft TR 33.891 v0.1.0 | draft TR | Qualcomm Incorporated | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
approved | [WTS] [JSN] | |
S3-221608 | Key Issue on Authorization in the UE-to-UE Relay Scenario |
pCR revision of S3-221331 |
InterDigital, Europe, Ltd., Huawei, HiSilicon, China Telecomunication, ZTE, CATT | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
approved | [WTS] [JSN] |
S3-221609 | Key Issue on Security of UE-to-UE Relay |
pCR revision of S3-221332 |
InterDigital, Europe, Ltd., Huawei, HiSilicon, China Telecomunication, ZTE, CATT, Xiaomi, OPPO | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
approved | [WTS] [JSN] |
S3-221610 | Key Issue on Direct C2 Security |
pCR revision of S3-221333 |
InterDigital, Europe, Ltd., Huawei, HiSilicon | 33.891 0.0.0 | FS_UAS_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.17 |
approved | [WTS] [JSN] |
S3-221611 | KI#2.1, New Sol Authentication and authorization between EEC hosted in the roaming UE and ECS |
pCR revision of S3-221559 |
Xiaomi Communication | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221612 | LS out on authenticity and replay protection of system information |
LS out LS To: RAN2 revision of S3-221370 revised to S3-221700 |
CableLabs, Deutsche Telekom, Philips International B.V., Ericsson, InterDigital, Apple, Johns Hopkins University APL, NIST, Huawei, Nokia, Samsung, Intel | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
revised | [WTS] [JSN] | ||
S3-221613 | KI#2.1, New Sol Authentication and authorization between EEC hosted in the roaming UE and EES |
pCR revision of S3-221560 |
Xiaomi Communication | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221614 | KI#2.2, New Sol 5GC-based authentication mechanism selection between EEC and ECS or EES |
pCR revision of S3-221561 |
Xiaomi Communication | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221615 | Solution for AI-ML model authorization and retrieval |
pCR revision of S3-221470 |
Nokia, Nokia Shanghai Bell | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221616 | Solution for access control and anonymization for data and analytics exchange in roaming |
pCR revision of S3-221471 |
Nokia, Nokia Shanghai Bell | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221617 | Solution for anomalous NF behaviour detection by NWDAF |
pCR revision of S3-221469 |
Nokia, Nokia Shanghai Bell | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221618 | Solution for secure initial enrolment of NF certificates | pCR | Nokia, Nokia Shanghai Bell | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
withdrawn | [WTS] [JSN] |
S3-221619 | Draft TR 33.876 Study on Standardising Automated Certificate Management in SBA | draft TR | Nokia, Nokia Shanghai Bell | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] | |
S3-221620 | Solution for secure initial enrolment of NF certificates |
pCR revision of S3-221501 |
Nokia, Nokia Shanghai Bell | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] |
S3-221621 | LS reply on 5GC information exposure to UE |
LS out LS is reply to S3-221313 LS To: SA2, SA1 revision of S3-221358 |
NTT DOCOMO | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] | ||
S3-221622 | 33.893: Architecure Assumptions |
pCR revision of S3-221539 |
Xiaomi Technology | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
approved | [WTS] [JSN] |
S3-221623 | 33.893: New Key Issue on Privacy |
pCR revision of S3-221540 |
Xiaomi Technology | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
approved | [WTS] [JSN] |
S3-221624 | 33.893: New Key Issue on Discovery Security |
pCR revision of S3-221542 |
Xiaomi Technology | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
approved | [WTS] [JSN] |
S3-221625 | 33.893: New Key Issue on Authorization for Ranging/SL Positioning Service | pCR | Beijing Xiaomi Mobile Software | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
withdrawn | [WTS] [JSN] |
S3-221626 | draft - LS reply on CAPIF authorization roles related to FS_SNAAPP – documenting state of discussion after SA3#107e-AdHoc - to be noted |
LS out LS To: SA6 |
DOCOMO Communications Lab. |
S3-107-e-Ad Hoc AI: 5.11 |
noted | [WTS] [JSN] | |||
S3-221627 | Draft TR 33.893 | draft TR | Xiaomi Technology | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
approved | [WTS] [JSN] | |
S3-221628 | Scope of TR33.886 |
pCR revision of S3-221373 |
Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
approved | [WTS] [JSN] |
S3-221629 | New KI-providing VPLMN slice information to roaming UE |
pCR revision of S3-221374 |
Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
approved | [WTS] [JSN] |
S3-221630 | New KI-temprory slices and slice authorization |
pCR revision of S3-221375 |
Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
approved | [WTS] [JSN] |
S3-221631 | New KI on NSAC |
pCR revision of S3-221376 |
Huawei, HiSilicon | 33.886 0.0.0 | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
approved | [WTS] [JSN] |
S3-221632 | Draft TR 33.886 for eNS3 | draft TR | Huawei | FS_eNS_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.12 |
approved | [WTS] [JSN] | |
S3-221633 | Solution on HN triggering primary authentication for various scenarios |
pCR revision of S3-221353 |
Nokia, Nokia Shanghai Bell | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221634 | Solution on AKMA roaming |
pCR revision of S3-221352 |
Nokia, Nokia Shanghai Bell | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] |
S3-221635 | Update in KI1 for encryption keys |
pCR revision of S3-221351 |
Nokia, Nokia Shanghai Bell, Samsung | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] |
S3-221636 | Scope of 5WWC study |
pCR revision of S3-221342 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
approved | [WTS] [JSN] |
S3-221637 | Key issue on authentication of AUN3 device supporting EAP |
pCR revision of S3-221344 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
approved | [WTS] [JSN] |
S3-221638 | Key issues on Security aspect of slice information exposure of N3IWF/TNGF |
pCR revision of S3-221346 |
Nokia, Nokia Shanghai Bell, CableLabs | 33.887 0.0.0 | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
approved | [WTS] [JSN] |
S3-221639 | Authorization and Authentication of ML model transfer |
pCR revision of S3-221452 |
Intel | 33.738 0.1.0 | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] |
S3-221640 | pCR to TR 33.740 Clause 4 Security Aspects of 5G ProSe |
pCR revision of S3-221490 |
CATT, ZTE | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
approved | [WTS] [JSN] |
S3-221641 | New key issue on users identified by Priority Access | pCR | InterDigital, Inc. | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
withdrawn | [WTS] [JSN] |
S3-221642 | New key issue on users identified by Priority Access |
pCR revision of S3-221340 |
Johns Hopkins University APL, US National Security Agency, CISA ECD, Peraton Labs, Interdigital, Apple, CableLabs | 33.87 0.2.0 | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
approved | [WTS] [JSN] |
S3-221643 | TR 33.740 v0.1.0 Study on security aspects of Proximity Based Services (ProSe) in 5G System (5GS) phase 2 | draft TR | CATT | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
approved | [WTS] [JSN] | |
S3-221644 | New solution on Cross-Certification Based Trust Chain in the SBA Architecture |
pCR revision of S3-221552 |
Beijing Xiaomi Mobile Software | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] |
S3-221645 | New solution on Interconnection CA Based Trust Chain in the SBA Architecture |
pCR revision of S3-221553 |
Beijing Xiaomi Mobile Software | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] |
S3-221646 | New solution on UDM initiated Primary Authentication |
pCR revision of S3-221550 |
Beijing Xiaomi Mobile Software | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221647 | 33.893: New Key Issue on Authorization for Ranging/SL Positioning Service |
pCR revision of S3-221541 |
Beijing Xiaomi Mobile Software | 33.893 0.0.0 | FS_Ranging_SL_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.19 |
approved | [WTS] [JSN] |
S3-221648 | Solution 5 EN on Certificates and Tokens |
pCR revision of S3-221318 |
U.S. National Security Agency | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] |
S3-221649 | Initial content for the background clause of the technical report |
pCR revision of S3-221575 |
Ericsson | 33.877 0.0.0 | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.14 |
approved | [WTS] [JSN] |
S3-221650 | Draft TR 33.877 v0.1.0 Study on the security aspects of Artificial Intelligence (AI)/Machine Learning (ML) for the NG-RAN | draft TR | Ericsson España S.A. | FS_NR_AIML_NGRAN_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.14 |
approved | [WTS] [JSN] | |
S3-221651 | New solution about the roaming AKMA architecture of the AF inside and outside the HPLMN |
pCR revision of S3-221433 |
ZTE Corporation | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] |
S3-221652 | New solution about the roaming AKMA architecture of the AF inside and outside the VPLMN |
pCR revision of S3-221434 |
ZTE Corporation | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] |
S3-221653 | Home network triggered authentication solution for 4G to 5G interworking on Key issue #1 |
pCR revision of S3-221436 |
ZTE Corporation | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221654 | ECS EES authentication method information provisioning solution on Key issue #2.2 |
pCR revision of S3-221438 |
ZTE Corporation | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221655 | TR 33.883 | draft TR | Huawei, HiSilicon | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
approved | [WTS] [JSN] | |
S3-221656 | TR 33.882 v0.1.0 | draft TR | vivo | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
approved | [WTS] [JSN] | |
S3-221657 | draft TR 33.738 0.2.0 | draft TR | China Mobile Group Device Co. | FS_eNA_SEC_Ph3 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.8 |
approved | [WTS] [JSN] | |
S3-221658 | A solution for certificate and NF lifecycle management relation |
pCR revision of S3-221473 |
Ericsson | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] |
S3-221659 | A new solution of using CMP for certificate enrolment and renewal |
pCR revision of S3-221475 |
Ericsson, Intel, Verizon, Nokia, Nokia Shanghai Bell | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] |
S3-221660 | A new key issue on authentication and authorization of UE in UE originated API invocation |
pCR revision of S3-221478 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.884 0.0.0 | FS_SNAAPPY | Rel-18 |
S3-107-e-Ad Hoc AI: 5.11 |
approved | [WTS] [JSN] |
S3-221661 | Update KI #6 for a new security threat |
pCR revision of S3-221381 |
Huawei, HiSilicon | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] |
S3-221662 | new solution for AKMA roaming when both UE and AF are in VPLMN |
pCR revision of S3-221384 |
Huawei, HiSilicon | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] |
S3-221663 | Skeleton update |
pCR revision of S3-221386 |
Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221664 | new KI in Kakma refresh |
pCR revision of S3-221389 |
Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221665 | Reply LS on Clarification on MBS Security Keys |
LS out LS is reply to S3-221153 LS To: CT4 revision of S3-221393 |
Huawei, HiSilicon | Rel-18 |
S3-107-e-Ad Hoc AI: 3 |
approved | [WTS] [JSN] | ||
S3-221666 | New key issue on TMGI protection |
pCR revision of S3-221396 |
Huawei, HiSilicon | 33.883 0.0.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
approved | [WTS] [JSN] |
S3-221667 | New key issue on security handling in MOCN network sharing scenario |
pCR revision of S3-221397 |
Huawei, HiSilicon | 33.883 0.0.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
approved | [WTS] [JSN] |
S3-221668 | New key issue on Roaming of eNA |
pCR revision of S3-221402 |
Huawei, HiSilicon | 33.896 0.0.0 | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
approved | [WTS] [JSN] |
S3-221669 | New Key Issue on NTN |
pCR revision of S3-221403 |
Huawei, HiSilicon, Xiaomi, Nokia, Nokia Shanghai Bell | 33.896 0.0.0 | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
approved | [WTS] [JSN] |
S3-221670 | evaluation on solution 5 |
pCR revision of S3-221404 |
Huawei, HiSilicon | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] |
S3-221671 | New solution for key issue 1 |
pCR revision of S3-221408 |
Huawei, HiSilicon | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] |
S3-221672 | New OCSP based solution for key issue 3 |
pCR revision of S3-221409 |
Huawei, HiSilicon | 33.876 0.2.0 | FS_ACM_SBA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.5 |
approved | [WTS] [JSN] |
S3-221673 | New KI on Authentication and Authorization between V-ECS and H-ECS |
pCR revision of S3-221411 |
Huawei, HiSilicon | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221674 | New key issue on security protection for Ues in RRC inactive state |
pCR revision of S3-221414 |
Huawei, HiSilicon | 33.883 0.0.0 | FS_5MBS_SEC_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.23 |
approved | [WTS] [JSN] |
S3-221675 | New solution UDM triggered primary authentication |
pCR revision of S3-221415 |
Huawei, HiSilicon | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221676 | Authentication and authorization to PINE behind PEGC and PEMC |
pCR revision of S3-221417 |
Huawei, HiSilicon | 33.882 0.0.0 | FS_PIN_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
approved | [WTS] [JSN] |
S3-221677 | Privacy of information over the UE-to-UE Relay |
pCR revision of S3-221419 |
Huawei, HiSilicon, Interdigital, ZTE, ChinaTelecom, CATT | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
approved | [WTS] [JSN] |
S3-221678 | MEC - Negotiation procedure for the authentication and authorization |
pCR revision of S3-221467 |
Apple | 33.739 0.1.0 | FS_LISE, FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221679 | TR 33.741 | draft TR | Huawei, HiSilicon | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] | |
S3-221680 | TR 33.896 | draft TR | HUAWEI TECH. GmbH | FS_UC3S_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.22 |
approved | [WTS] [JSN] | |
S3-221681 | New Key Issue "Security of non-3GPP access for SNPN" |
pCR revision of S3-221493 |
Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi, CableLabs | 33.858 0.0.0 | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
approved | [WTS] [JSN] |
S3-221682 | New KI on 3rd party ID |
pCR revision of S3-221484 |
Huawei, HiSilicon, Xiaomi, Ericsson | 33.89 0.0.0 | FS_NG_RTC_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.15 |
approved | [WTS] [JSN] |
S3-221683 | New KI on how to authorize PDU session to support local traffic routing to access an EHE in the VPLMN |
pCR revision of S3-221488 |
Huawei, HiSilicon | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221684 | draft TR 33.858 v0.1.0 | draft TR | Ericsson | FS_eNPN_Ph2_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.16 |
approved | [WTS] [JSN] | |
S3-221685 | Draft TR 33.739 | draft TR | Huawei, HiSilicon | FS_NG_RTC_SEC, FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] | |
S3-221686 | DraftTR_33.890 | draft TR | Huawei, HiSilicon | FS_NG_RTC_SEC | Rel-18 |
S3-107-e-Ad Hoc AI: 5.15 |
approved | [WTS] [JSN] | |
S3-221687 | draft TR 33.737 | draft TR | China Mobile | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] | |
S3-221688 | Solution of introducing AP into AKMA |
pCR revision of S3-221458 |
China Mobile, Apple, Qualcomm | 33.737 0.1.0 | FS_AKMA_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.6 |
approved | [WTS] [JSN] |
S3-221689 | Update of KI #3 to contribute an EN |
pCR revision of S3-221392 |
Huawei, HiSilicon | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] |
S3-221690 | Draft TR 33.892 | draft TR | Lenovo | FS_USIA | Rel-18 |
S3-107-e-Ad Hoc AI: 5.18 |
approved | [WTS] [JSN] | |
S3-221691 | Draft TR 33.894 for ZTS | draft TR | Lenovo | FS_ZTS | Rel-18 |
S3-107-e-Ad Hoc AI: 5.21 |
approved | [WTS] [JSN] | |
S3-221692 | TR 33 848 v0_13_0 | draft TR | BT plc | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] | |
S3-221693 | New Key Issue: Security for UE-to-UE Relay discovery |
pCR revision of S3-221519 |
Qualcomm Incorporated | 33.74 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
approved | [WTS] [JSN] |
S3-221694 | New solution Authentication mechanism selection in EDGE |
pCR revision of S3-221377 |
OPPO | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221695 | New solution Authentication mechanism selection among EEC, ECS, and EES |
pCR revision of S3-221379 |
OPPO | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
S3-221696 | TR 33.870 | draft TR | InterDigital, Inc. | FS_Id_Prvc | Rel-18 |
S3-107-e-Ad Hoc AI: 5.4 |
approved | [WTS] [JSN] | |
S3-221697 | New solution on KI#1 AMF based solution |
pCR revision of S3-221498 |
NEC Corporation | 33.741 0.1.0 | FS_HN_Auth | Rel-18 |
S3-107-e-Ad Hoc AI: 5.7 |
approved | [WTS] [JSN] |
S3-221698 | TR 33.898 | draft TR | OPPO | FS_AIML | Rel-18 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] | |
S3-221699 | U2U Relay Trust Model |
pCR revision of S3-221505 |
OPPO | 33.74 0.0.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.3 |
noted | [WTS] [JSN] |
S3-221700 | LS out on authenticity and replay protection of system information |
LS out LS To: RAN2 revision of S3-221612 |
CableLabs, Deutsche Telekom, Philips International B.V., Ericsson, InterDigital, Apple, Johns Hopkins University APL, NIST, Huawei, Nokia, Samsung, Intel | Rel-18 |
S3-107-e-Ad Hoc AI: 5.1 |
approved | [WTS] [JSN] | ||
S3-221701 | Updates to Solution #5 |
pCR revision of S3-221337 |
Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] |
S3-221702 | Address EN on Run-time Attestation |
pCR revision of S3-221338 |
Johns Hopkins University APL, US National Security Agency, CableLabs, InterDigital, AT&T, CISA ECD | 33.848 0.12.0 | FS_SIV | Rel-16 |
S3-107-e-Ad Hoc AI: 5.2 |
approved | [WTS] [JSN] |
S3-221703 | draft 33.887 v0.1.0 Study on Security aspects for 5WWC Phase 2 | draft TR | Nokia | FS_5WWC_Ph2_Sec | Rel-18 |
S3-107-e-Ad Hoc AI: 5.13 |
approved | [WTS] [JSN] | |
S3-221704 | Solution for Key Issue #2.2 |
pCR revision of S3-221357 |
THALES | 33.739 0.1.0 | FS_EDGE_Ph2 | Rel-18 |
S3-107-e-Ad Hoc AI: 5.9 |
approved | [WTS] [JSN] |
1098 documents (1.1267609596252 seconds)