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