Please enter the search related information in the fields below. Partial information works, e.g. "SP-21" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP" gives the same results as "3gpp".
Download results in JSON format
| tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
|---|---|---|---|---|---|---|---|---|---|
| S3-210000 | Agenda | agenda | SA WG3 Chair |
S3-102-e AI: 1 |
approved | [WTS] [JSN] | |||
| S3-210001 | Report from SA3#101e meeting | report | MCC |
S3-102-e AI: 2 |
approved | [WTS] [JSN] | |||
| S3-210002 | Process for SA3#102e meeting | other | SA WG3 Chair |
S3-102-e AI: 1 |
noted | [WTS] [JSN] | |||
| S3-210003 | Report from last SA | report | SA WG3 Chair |
S3-102-e AI: 2 |
noted | [WTS] [JSN] | |||
| S3-210004 | AMF transparency for SOR | LS in | C1-207736 |
S3-102-e AI: 4.23 |
postponed | [WTS] [JSN] | |||
| S3-210005 | LS on Storage of KAUSF |
LS in LS reply in S3-210706 |
C1-207764 |
S3-102-e AI: 4.23 |
replied to | [WTS] [JSN] | |||
| S3-210006 | User location identification from Carrier Aggregation secondary cell activation messages |
LS in LS reply in S3-210302, S3-210302 |
GSMA FSAG |
S3-102-e AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-210007 | LS on broadcasting gNB ID length in system information block | LS in | R3-207226 |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210008 | Reply LS on MuDe functionality | LS in | S1-204380 |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210009 | Reply LS on security issue for on-boarding and remote provisioning from SA3 |
LS in LS reply in S3-210800, S3-210800 |
S2-2009132 |
S3-102-e AI: 5.12 |
replied to | [WTS] [JSN] | |||
| S3-210010 | LS Response on Support of L2TP in PFCP | LS in | S2-2009331 |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210011 | Reply LS on IP address to GPSI translation | LS in | S2-2009339 |
S3-102-e AI: 5.8 |
postponed | [WTS] [JSN] | |||
| S3-210012 | Reply-LS on user consent requirements for analytics |
LS in LS reply in S3-210689 |
S2-2009383 |
S3-102-e AI: 5.16 |
replied to | [WTS] [JSN] | |||
| S3-210013 | Independent evaluation of SNOW V | LS in | ETSI SAGE |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210014 | 256-bit algorithms based on SNOW 3G or SNOW V | LS in | ETSI SAGE |
S3-102-e AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-210015 | LS on SG17 new work item 'Security Methodology for Zero-Touch Massive IoT Deployment' | LS in | ITU-T SG17 |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210016 | LS on Use of Inclusive Language in 3GPP | LS in | SP-201143 |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210017 | LS on 5G-GUTI reallocation after paging of a UE in 5GMM-IDLE mode with suspend indication | LS in | C1-200967 |
S3-102-e AI: 4.6 |
noted | [WTS] [JSN] | |||
| S3-210018 | Reply LS to SA3 on FBS detection |
LS in LS reply in S3-210756, S3-210756 |
R2-1914224 |
S3-102-e AI: 5.1 |
replied to | [WTS] [JSN] | |||
| S3-210019 | LS on propagation of user consent related information during Xn inter-PLMN handover | LS in | R3-204378 |
S3-102-e AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-210020 | LS on Security Requirements for Sidelink/PC5 Relays | LS in | S2-2004750 |
S3-102-e AI: 5.9 |
postponed | [WTS] [JSN] | |||
| S3-210021 | LS on method for collection of data from the UE |
LS in LS reply in S3-210611, S3-210611 |
S2-2006292 |
S3-102-e AI: 5.16 |
replied to | [WTS] [JSN] | |||
| S3-210022 | Reply to LS on Resynchronisations | LS in | ETSI SAGE |
S3-102-e AI: 5.5 |
postponed | [WTS] [JSN] | |||
| S3-210023 | Reply LS on AUSF/UDM discovery based on SUCI information | LS in | S2-2009207 |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210024 | LS on Support of L2TP on SGi/N6 with Control and User Plane Separation |
LS in LS reply in S3-210791, S3-210791 |
C4-205478 |
S3-102-e AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-210025 | LS on Changes to SoR Delivery Mechanism | LS in | C4-205696 |
S3-102-e AI: 4.23 |
postponed | [WTS] [JSN] | |||
| S3-210026 | Reply LS on the user consent for trace reporting | LS in | R2-2010894 |
S3-102-e AI: 5.14 |
postponed | [WTS] [JSN] | |||
| S3-210027 | Reply LS on the re-keying procedure for NR SL |
LS in LS reply in S3-210738, S3-210738 |
R2-2010963 |
S3-102-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
| S3-210028 | LS on propagation of user consent related information during Xn inter-PLMN handover |
LS in LS reply in S3-211011, S3-211330 |
R3-204378 |
S3-102-e AI: 5.14 |
postponed | [WTS] [JSN] | |||
| S3-210029 | Reply LS on System support for Multi-USIM devices | LS in | R3-207207 |
S3-102-e AI: 5.19 |
noted | [WTS] [JSN] | |||
| S3-210030 | LS on integrity and confidentiality protection of xcap-diff and pidf documents in MCPTT (TS 24.379) | LS in | R5- 206273 |
S3-102-e AI: 4.23 |
noted | [WTS] [JSN] | |||
| S3-210031 | LS on Security Requirements for Sidelink/PC5 Relays | LS in | S2-2004750 |
S3-102-e AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-210032 | Reply on method for collection of data from the UE | LS in | S4-201584 |
S3-102-e AI: 5.16 |
noted | [WTS] [JSN] | |||
| S3-210033 | TC CYBER Activities | LS in | ETSI TC CYBER |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210034 | New Key Issue: MBS Location Privacy |
pCR revised to S3-210036 |
MITRE | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210035 | New Key Issue: MBS Location Privacy | pCR | MITRE | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
withdrawn | [WTS] [JSN] |
| S3-210036 | New Key Issue: MBS Location Privacy |
pCR revision of S3-210034 |
MITRE | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
noted | [WTS] [JSN] |
| S3-210037 | Update of clause 4.2 | pCR | KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210038 | New KI: Protection of TUAK TOPc value during storage in UDR | pCR | KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210039 | New KI: Protection of TUAK TOPc value during transfer out of UDR | pCR | KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210040 | New Solution: Protection of SQN during storage in UDR |
pCR revised to S3-210709 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210041 | New Solution: Protection of SQN during transfer out of UDR | pCR | KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
merged | [WTS] [JSN] |
| S3-210042 | New Solution: Protection of TUAK TOPc value during storage in UDR |
pCR revised to S3-210712 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210043 | New Solution: Protection of TUAK TOPc value during transfer out of UDR |
pCR revised to S3-210713 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210044 | Updated Solution #8: Encrypted transfer of OPc between UDR and UDM/ARPF |
pCR revised to S3-210714 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210045 | Updated Solution #9: Encrypted transfer of OP between UDR and UDM/ARPF |
pCR revised to S3-210716 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210046 | Updated Solution #10: Encrypted strorage of OPc in UDR |
pCR revised to S3-210717 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210047 | Updated Solution #11: Encrypted storage of OP in UDR |
pCR revised to S3-210718 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210048 | TCG progress - report from TCG rapporteur | report | InterDigital, Inc. |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210049 | Limited service state for missioncritical services | CR | BDBOS | 33.18 17.1.0 CR#153 catC | MCXSec2 | Rel-17 |
S3-102-e AI: 4.19 |
not pursued | [WTS] [JSN] |
| S3-210050 | Update to solution #17 (6.17.2) of TR 33.809 | pCR | Deutsche Telekom AG | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210051 | Discussion – R17 Group regroup and user regroup security | discussion | Motorola Solutions Danmark A/S | MCXSec2 | Rel-17 |
S3-102-e AI: 4.19 |
noted | [WTS] [JSN] | |
| S3-210052 | [33.180] R17 Group regroup and user regroup security | CR | Motorola Solutions Danmark A/S | 33.18 17.1.0 CR#154 catB | MCXSec2 | Rel-17 |
S3-102-e AI: 4.19 |
not pursued | [WTS] [JSN] |
| S3-210053 | [33.180] R14 RFC3830 reference correction | CR | Motorola Solutions Danmark A/S | 33.18 14.8.0 CR#155 catF | MCSec | Rel-14 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210054 | [33.180] R15 RFC3830 reference correction (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 15.8.0 CR#156 catA | MCSec | Rel-15 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210055 | [33.180] R16 RFC3830 reference correction (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 16.5.0 CR#157 catA | MCSec | Rel-16 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210056 | [33.180] R17 RFC3830 reference correction (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 17.1.0 CR#158 catA | MCSec | Rel-17 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210057 | [33.180] R14 XML encryption correction | CR | Motorola Solutions Danmark A/S | 33.18 14.8.0 CR#159 catF | MCSec | Rel-14 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210058 | [33.180] R15 XML encryption correction (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 15.8.0 CR#160 catA | MCSec | Rel-15 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210059 | [33.180] R16 XML encryption correction (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 16.5.0 CR#161 catA | MCSec | Rel-16 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210060 | [33.180] R17 XML encryption correction (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 17.1.0 CR#162 catA | MCSec | Rel-17 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210061 | Discussion on Conclusion to TR 33.840 | discussion | Futurewei |
S3-102-e AI: 5.13 |
endorsed | [WTS] [JSN] | |||
| S3-210062 | Conclusion to TR 33.840 |
pCR revised to S3-210595 |
Futurewei | 33.84 0.2.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-102-e AI: 5.13 |
revised | [WTS] [JSN] |
| S3-210063 | LS on conclusion of security study of disaggregated gNB architecture |
LS out LS To: RAN3 revised to S3-210596 |
Futurewei | FS_disagg_gNB_Sec | Rel-17 |
S3-102-e AI: 5.13 |
revised | [WTS] [JSN] | |
| S3-210064 | 5G architecture enhancements for BEST | draftCR | KPN N.V. | BEST_5G | Rel-17 |
S3-102-e AI: 4.21 |
approved | [WTS] [JSN] | |
| S3-210065 | Error code details - Resolving ed note in 13.2.2.6 |
CR revision of S3-201797 |
Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#9021 catF | 5G_eSBA | Rel-15 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
| S3-210066 | TS 33.536 - overall clean-up |
CR revised to S3-210705 |
LG Electronics Inc. | 33.536 16.2.0 CR#22 catD | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210067 | TR 33.847 - Remove ENs in KI1 | pCR | LG Electronics Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210068 | TR 33.847 - Resolve ENs in Sol13 |
pCR revised to S3-210636 |
LG Electronics Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210069 | TR 33.847 - Evaluation of Sol13 |
pCR revised to S3-210637 |
LG Electronics Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210070 | TR 33.847 - New KI on security protection misalignment in L3 UE2NW relay | pCR | LG Electronics Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210071 | Updated Solution #22: Representation of identities during broadcast |
pCR revised to S3-210555 |
KPN N.V. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210072 | Updated Solution #23: Initial key with validity time |
pCR revised to S3-210557 |
KPN N.V. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210073 | Correct NAS uplink COUNT for KgNB/KeNB derivation |
CR revision of S3-202947 |
MediaTek Inc. | 33.501 16.5.0 CR#9621 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210074 | Error code details - Resolving ed note in 13.2.2.6 |
CR revision of S3-201797 revised to S3-210723 |
Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#9022 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210075 | Error code details - Resolving ed note in 13.2.2.6 |
CR revised to S3-210724 |
Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#1019 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210076 | Evaluation of solution 6 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210077 | Evaluation of solution 7 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210078 | Evaluation of solution 8 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
noted | [WTS] [JSN] |
| S3-210079 | Evaluation of solution 9 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
noted | [WTS] [JSN] |
| S3-210080 | Evaluation of solution 10 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
noted | [WTS] [JSN] |
| S3-210081 | Evaluation of solution 11 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
noted | [WTS] [JSN] |
| S3-210082 | New solution for KI#8 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
merged | [WTS] [JSN] |
| S3-210083 | New solution for KI#9 |
pCR revised to S3-210715 |
NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210084 | Some conclusions for TR 33.845 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
merged | [WTS] [JSN] |
| S3-210085 | Editorial corrections | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210086 | TR 33.847 Update for KI #4 |
pCR revised to S3-210149 |
InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210087 | TR 33.848 Jan 2021 Refresh | pCR | BT plc | 33.848 0.5.0 | FS_SIV | Rel-16 |
S3-102-e AI: 5.4 |
approved | [WTS] [JSN] |
| S3-210088 | Discussion on user versus subscriber in relation to the U3C study | discussion | Futurewei | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] | ||
| S3-210089 | KI on U3C User Identification | pCR | Futurewei | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210090 | gNB Cipher Security Policy Verification |
CR revised to S3-210795 |
Futurewei | 33.511 16.5.0 CR#19 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
revised | [WTS] [JSN] |
| S3-210091 | gNB Integrity Security Policy Verification |
CR revised to S3-210796 |
Futurewei | 33.511 16.5.0 CR#20 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
revised | [WTS] [JSN] |
| S3-210092 | pCR Signing solutions and cell selection in TR 33.809 | pCR | VODAFONE Group Plc | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210093 | TR 33.854 Update for solution#5 |
pCR revised to S3-210593 |
InterDigital, Europe, Ltd. | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210094 | Solution for UAV location privacy |
pCR revised to S3-210594 |
InterDigital, Europe, Ltd. | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210095 | Choice of cryptographic algorithm in 256-bit Milenage | LS in | ETSI SAGE |
S3-102-e AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-210096 | NF Service Consumer and Producer in Service Request Process |
CR revised to S3-210725 |
Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#1020 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210097 | Access Token Misuse Prevention |
CR revised to S3-210727 |
Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#1021 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210098 | NF Service Consumer and Producer in Service Request Process |
CR revised to S3-210726 |
Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#1022 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210099 | Access Token Misuse Prevention |
CR revised to S3-210728 |
Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#1023 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210100 | SCAS Protection Policies - TBD updated |
CR revised to S3-210729 |
Nokia, Nokia Shanghai Bell | 33.517 16.1.0 CR#5 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
revised | [WTS] [JSN] |
| S3-210101 | Protection policies test case |
CR revised to S3-210730 |
Nokia, Nokia Shanghai Bell, NTT Docomo, Huawei, HiSilicon | 33.517 16.1.0 CR#6 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
revised | [WTS] [JSN] |
| S3-210102 | Optional registration of NF Service Consumer to NRF | CR | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 15.11.0 CR#1024 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
| S3-210103 | Optional registration of NF Service Consumer to NRF | CR | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 16.5.0 CR#1025 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
| S3-210104 | Optional registration of NF Service Consumer to NRF | CR | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 17.0.0 CR#1026 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
| S3-210105 | TR 33866-020_update on formats and typos |
pCR revised to S3-210569 |
Nokia, Nokia Shanghai Bell, China Mobile | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-210106 | Abbreviations.doc |
pCR revised to S3-210570 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-210107 | KI on protection of data in transfer |
pCR revised to S3-210573 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-210108 | Usage of current SBA mechanisms to protect data in transfer |
pCR revised to S3-210574 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-210109 | KI details on Anomalous NF behaviour detection by NWDAF | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210110 | Threats on KI Anomalous NF behavior detection by NWDAF | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210111 | Requirements on KI Anomalous NF behavior detection by NWDAF |
pCR revised to S3-210572 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-210112 | KI on UE data collection protection | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
noted | [WTS] [JSN] |
| S3-210113 | Threats and requirements to KI on UE data collection protection | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
noted | [WTS] [JSN] |
| S3-210114 | Solution on UE data collection protection.docx |
pCR revised to S3-210581 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-210115 | Requirements to KI on Processing of tampered data | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210116 | KI on Authorization of consumers for data access via DCCF.doc |
pCR revised to S3-210571 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-210117 | TR 33.867 – New KI – Confidentiality Protection | pCR | InterDigital, Inc. | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210118 | TR 33.867 – New KI – User Authentication | pCR | InterDigital, Inc. | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210119 | TR 33.867 – New KI – Replay Protection | pCR | InterDigital, Inc. | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210120 | TR 33.867 – New KI – Integrity Protection | pCR | InterDigital, Inc. | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210121 | TR 33.867 – New KI – Non-Repudiation | pCR | InterDigital, Inc. | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210122 | TR 33.847 Update for solution #10 |
pCR revised to S3-210598 |
InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210123 | Solution for NSSAA procedure for Remote UE with L3 UE-to-Network relay |
pCR revised to S3-210601 |
InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210124 | Solution for secondary authentication Remote UE with L3 UE-to-Network relay |
pCR revised to S3-210600 |
InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210125 | TR 33.847 Update for solution #12 | pCR | InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210126 | TR 33.857: scope | pCR | THALES | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210127 | Living document for TS 33.220: addition of UDM | draftCR | THALES | GBA_5G | Rel-17 |
S3-102-e AI: 4.11 |
noted | [WTS] [JSN] | |
| S3-210128 | Living document for TS 33.223: addition of UDM | draftCR | THALES | GBA_5G | Rel-17 |
S3-102-e AI: 4.11 |
noted | [WTS] [JSN] | |
| S3-210129 | TR 33.846: conclusion for key issue #2.1 | pCR | THALES | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210130 | TR 33.846: conclusion for key issue #4.1 | pCR | THALES | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210131 | Additions to FBS Solution #23 |
pCR revised to S3-210783 |
Philips International B.V. | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
revised | [WTS] [JSN] |
| S3-210132 | Additions to FBS Solution #24 |
pCR revised to S3-210784 |
Philips International B.V., CableLabs, Nokia, Nokia Shanghai Bell | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
revised | [WTS] [JSN] |
| S3-210133 | New solution FBS KI#2 | pCR | Philips International B.V. | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210134 | Additions to MBS Solution #2 | pCR | Philips International B.V. | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210135 | Clarifications regarding Authentication procedure for V2X PC5 unicast link |
CR revised to S3-210804 |
Nokia, Nokia Shanghai Bell | 33.536 16.2.0 CR#23 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210136 | Solution for protecting the privacy of the UE identity. |
pCR revised to S3-210801 |
Nokia, Nokia Shanghai Bell | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210137 | [DRAFT] Reply-LS on security issue for on-boarding and remote provisioning. |
LS out LS is reply to LS (S2-209132) on Reply LS on security issue for on-boarding and remote provisioning source LS: S2-209132 LS To: SA2 revised to S3-210800 |
Nokia, Nokia Shanghai Bell | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] | |
| S3-210138 | Discussion on NSSAA Editor note for sending S-NSSAI to the AAA-S. | discussion | Nokia | Rel-16 |
S3-102-e AI: 4.9 |
noted | [WTS] [JSN] | ||
| S3-210139 | CR to delete the EN (rel-16) in NSSAA clause | CR | Nokia | 33.501 16.5.0 CR#1027 catF | eNS | Rel-16 |
S3-102-e AI: 4.9 |
not pursued | [WTS] [JSN] |
| S3-210140 | CR to dete the NSSAA Editor Note (Rel-17) | CR | Nokia | 33.501 17.0.0 CR#1028 catA | eNS | Rel-17 |
S3-102-e AI: 4.9 |
not pursued | [WTS] [JSN] |
| S3-210141 | Authentication procedure during Xn handover procedure | CR | NEC | 33.501 16.5.0 CR#1029 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
not pursued | [WTS] [JSN] |
| S3-210142 | New WID for supporting NSWO in 5G | WID new | ATT, Nokia, Nokia Shanghai Bell | Rel-17 |
S3-102-e AI: 4.22 |
noted | [WTS] [JSN] | ||
| S3-210143 | Enhanced description for KI#7 | pCR | Nokia, Nokia Shanghai Bell, Philips | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210144 | DISC Handling of latest Kasuf | discussion | NEC | Rel-16 |
S3-102-e AI: 4.23 |
noted | [WTS] [JSN] | ||
| S3-210145 | Key Issue on privacy issues relating to Paging Cause exposure | other | Nokia, Nokia Shangahi Bell, Samsung | Rel-17 |
S3-102-e AI: 5.19 |
noted | [WTS] [JSN] | ||
| S3-210146 | Maintaining latest Kausf | CR | NEC | 33.501 16.5.0 CR#1030 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
not pursued | [WTS] [JSN] |
| S3-210147 | Secure Busy indication | other | Nokia, Nokia Shanghai Bell |
S3-102-e AI: 5.19 |
noted | [WTS] [JSN] | |||
| S3-210148 | SUCI Linkability attack | pCR | NEC | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210149 | TR 33.847 Update for KI #4 |
pCR revision of S3-210086 |
InterDigital, Inc., LG Electronics | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210150 | AMF re-allocation Solution#4 | pCR | Nokia, Nokia Shanghai Bell | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
merged | [WTS] [JSN] |
| S3-210151 | AAnF checks AKMA service for UE and AF in clause 6.3 |
CR revised to S3-210760 |
ZTE Corporation | 33.535 17.0.0 CR#55 catB | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
revised | [WTS] [JSN] |
| S3-210152 | AAnF selection in AF |
CR revised to S3-210761 |
ZTE Corporation | 33.535 17.0.0 CR#56 catB | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
revised | [WTS] [JSN] |
| S3-210153 | Add Application Key Get service in clause 7.1 |
CR revised to S3-210762 |
ZTE Corporation | 33.535 17.0.0 CR#57 catB | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
revised | [WTS] [JSN] |
| S3-210154 | Kakma invalid and Kausf invalid in clause 6.2 | CR | ZTE Corporation | 33.535 17.0.0 CR#58 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
not pursued | [WTS] [JSN] |
| S3-210155 | Resolution of EN on other parameter in clause 6.3 | CR | ZTE Corporation | 33.535 17.0.0 CR#59 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
not pursued | [WTS] [JSN] |
| S3-210156 | the KAF lifetime expiration in clause 5.2 |
CR revised to S3-210763 |
ZTE Corporation | 33.535 17.0.0 CR#60 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
revised | [WTS] [JSN] |
| S3-210157 | Discussion paper on KAUSF invalid and KAKMA invalid | discussion | ZTE Corporation | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
noted | [WTS] [JSN] | |
| S3-210158 | UDM notifies AAnF AKMA context removal | CR | ZTE Corporation | 33.535 17.0.0 CR#61 catB | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
not pursued | [WTS] [JSN] |
| S3-210159 | New security functional requirement and related test case on validating of user data transported | draftCR | ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-102-e AI: 4.17 |
merged | [WTS] [JSN] | |
| S3-210160 | Update the clause 5.2.5.5.7 |
pCR revised to S3-210764 |
ZTE Corporation, China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210161 | Conclusion for Key Issue #4.1 | pCR | ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210162 | New solution for key issue# 4.1 in TR 33.846 |
pCR revised to S3-210766 |
ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
revised | [WTS] [JSN] |
| S3-210163 | Solution of Mitigation against the SUPI replay attack |
pCR revised to S3-210769 |
ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
revised | [WTS] [JSN] |
| S3-210164 | Update solution#2.1 in TR 33.846 |
pCR revised to S3-210767 |
ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
revised | [WTS] [JSN] |
| S3-210165 | Update the evaluation for solution# 4.1 | pCR | ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210166 | Update the evaluation for solution# 4.2 | pCR | ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210167 | Update the evaluation for solution# 4.3 | pCR | ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210168 | Update the evaluation for solution# 4.4 | pCR | ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210169 | Update the key issue 4.1 | pCR | ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210170 | AMF selection in multiple NAS connections in solution#6.7 in TR 33.839 | pCR | ZTE Corporation | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210171 | LBO roaming scenario should be supported in solution#6.7 in TR 33.839 |
pCR revised to S3-210633 |
ZTE Corporation | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210172 | Update the key issue#7 in TR 33.839 |
pCR revised to S3-210634 |
ZTE Corporation | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210173 | Update the solution#14 in TR 33.839 |
pCR revised to S3-210635 |
ZTE Corporation | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210174 | Update to Solution #3 | pCR | ZTE Corporation | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210175 | Update to Solution #4 | pCR | ZTE Corporation | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210176 | Evaluation of Solution #8 |
pCR revised to S3-210638 |
ZTE Corporation | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210177 | Evaluation of Solution #9 |
pCR revised to S3-210639 |
ZTE Corporation | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210178 | New solution on security of AMF re-allocation using Registration Reject message | pCR | ZTE Corporation | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
noted | [WTS] [JSN] |
| S3-210179 | New solution on security of AMF re-allocation using RRC Release message | pCR | ZTE Corporation | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
noted | [WTS] [JSN] |
| S3-210180 | Updates to solution 18: Removal EN related to EEC ID |
pCR revised to S3-210623 |
Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210181 | Add new solution in TR 33.839 | pCR | CATT | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
noted | [WTS] [JSN] |
| S3-210182 | Updates to solution 18: Removal EN related to identification of serving AMF |
pCR revised to S3-210624 |
Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210183 | Remove the EN in solution #5 |
pCR revised to S3-210677 |
CATT | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210184 | Key issue on authorization revocation in TR 33.839 | pCR | CATT | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
noted | [WTS] [JSN] |
| S3-210185 | Remove EN in Solution #6 in TR 33.839 |
pCR revised to S3-210678 |
CATT | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210186 | Updates to solution 18: Removal EN related to roaming | pCR | Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
noted | [WTS] [JSN] |
| S3-210187 | Add new key issue for user consent | pCR | CATT | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210188 | Add references in TR 33.866 | pCR | CATT | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-210189 | Add new key issue in TR 33.866 | pCR | CATT | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-210190 | Updates to solution 4: evaluation | pCR | Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
noted | [WTS] [JSN] |
| S3-210191 | Updates to solution 4 | pCR | Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
noted | [WTS] [JSN] |
| S3-210192 | Updates to solution 12: Removing EN |
pCR revised to S3-210625 |
Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210193 | Detection of MitM FBS | pCR | Huawei, HiSilicon | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210194 | Reply LS on FBS detection |
LS out LS is reply to RAN2 LS To: RAN2 revised to S3-210756 |
Huawei, HiSilicon | Rel-17 |
S3-102-e AI: 5.1 |
revised | [WTS] [JSN] | ||
| S3-210195 | Discussion paper for Rel17 SID on network slicing security | discussion | Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT, China Unicom, China Mobile, InterDigital, NEC | Rel-17 |
S3-102-e AI: 5.21 |
noted | [WTS] [JSN] | ||
| S3-210196 | Rel17 SID on network slice security | SID new | Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT, China Unicom, China Mobile, InterDigital, NEC | Rel-17 |
S3-102-e AI: 5.21 |
withdrawn | [WTS] [JSN] | ||
| S3-210197 | Discussion on SN-ID in NSSAA | discussion | Huawei, HiSilicon | eNS | Rel-16 |
S3-102-e AI: 4.9 |
noted | [WTS] [JSN] | |
| S3-210198 | Serving network ID in NSSAA | CR | Huawei, HiSilicon | 33.501 16.5.0 CR#1031 catF | eNS | Rel-16 |
S3-102-e AI: 4.9 |
not pursued | [WTS] [JSN] |
| S3-210199 | validity peirod of NSSAA result | CR | Huawei, HiSilicon | 33.501 16.5.0 CR#1032 catF | eNS | Rel-16 |
S3-102-e AI: 4.9 |
not pursued | [WTS] [JSN] |
| S3-210200 | Addressing EN in KI#7: scope of C2 Security | pCR | Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
noted | [WTS] [JSN] |
| S3-210201 | Remove EN1-align SA2 procedure | pCR | Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210202 | Remove EN2-align AF defined by SA2 | pCR | Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210203 | Remove EN3-revocation |
pCR revised to S3-210615 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210204 | Remove EN1-exchange ID with USS |
pCR revised to S3-210616 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210205 | Remove EN2- revocation |
pCR revised to S3-210617 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210206 | Remove EN1:security of group management |
pCR revised to S3-210618 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210207 | Remove EN2: Time synchronization |
pCR revised to S3-210619 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210208 | Adding Evalaution | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210209 | Security Solution for Busy Indication using NAS signaling |
other revised to S3-210626 |
Intel Corporation (UK) Ltd |
S3-102-e AI: 5.19 |
revised | [WTS] [JSN] | |||
| S3-210210 | Updates to key issue 2 | other | Intel Corporation (UK) Ltd |
S3-102-e AI: 5.19 |
noted | [WTS] [JSN] | |||
| S3-210211 | New WID on 5GFBS | WID new | Apple, AT&T, Deutsche Telekom, Charter Communication, China Unicom, NIST, CableLabs, Interdigital, Ericsson, Samsung, CAICT, CATT, Intel, vivo, MITRE, Philips | Rel-17 |
S3-102-e AI: 4.22 |
noted | [WTS] [JSN] | ||
| S3-210212 | 5GFBS-Edotorial change After EditHelp | pCR | Apple | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210213 | MUSIM-key issue on BUSY indication |
pCR revised to S3-210694 |
Apple | 33.873 0.0.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-210214 | MUSIM-Solution to protect BUSY indication | pCR | Apple | 33.873 0.0.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-210215 | MBS-Modification on solution#1 |
pCR revised to S3-210693 |
Apple | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210216 | MEC-Evaluation on solution#1 | pCR | Apple | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210217 | MEC-Modification on solution#22 |
pCR revised to S3-210692 |
Apple | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210218 | New Key Issue on UE preferred SNPN information update | pCR | Alibaba Group | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210219 | New solution on preferred SNPN information update | pCR | Alibaba Group | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210220 | New solution on UE onboarding for SNPN with the interaction between PS and DCS |
pCR revised to S3-210602 |
Alibaba Group | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210221 | Threat to send EAP-Identity Request by N3IWF |
CR revised to S3-210805 |
China Unicom | 33.926 16.3.0 CR#37 catB | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
revised | [WTS] [JSN] |
| S3-210222 | Check whether the N3IWF sends the EAP-Identity Request message |
pCR revised to S3-210802 |
China Unicom | 33.52 0.1.0 | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
revised | [WTS] [JSN] |
| S3-210223 | Draft CR on Clarification for UP integrity Mechanisms between the UE and the ng-eNB | draftCR | Huawei, HiSilicon | eUPIP_SEC | Rel-17 |
S3-102-e AI: 4.2 |
merged | [WTS] [JSN] | |
| S3-210224 | Draft CR on Clarification for Handling for indication of UE supports UPIP | draftCR | Huawei, HiSilicon | eUPIP_SEC | Rel-17 |
S3-102-e AI: 4.2 |
approved | [WTS] [JSN] | |
| S3-210225 | New Solution for UPIP for EPS |
pCR revised to S3-210655 |
Huawei, HiSilicon | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210226 | New Use Case for MEC | pCR | Huawei, HiSilicon, Samsung | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210227 | Add Terms for UC3S | pCR | Huawei, HiSilicon | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
approved | [WTS] [JSN] |
| S3-210228 | Analysis for UC3S |
pCR revised to S3-210656 |
Huawei, HiSilicon | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
revised | [WTS] [JSN] |
| S3-210229 | New Solution for Network Framework for DDoS Attack | pCR | Huawei, HiSilicon | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210230 | Reply LS on Security issue for On-boarding and Remote Provisioning |
LS out LS To: SA2 |
Huawei, HiSilicon |
S3-102-e AI: 5.12 |
merged | [WTS] [JSN] | |||
| S3-210231 | New Solution on Authentication for UE onboarding for SNPN |
pCR revised to S3-210657 |
Huawei, HiSilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210232 | Solution Update for Solution #5 |
pCR revised to S3-210658 |
Huawei, HiSilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210233 | System Impact and Evaluation for solution #5 | pCR | Huawei, HiSilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210234 | Threat analysis related to RRCConnectionReestablsihment in CP CIoT 5GS Optimization | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210235 | Draft CR on New Test Case on RRCConnectionReestablsihment in CP CIoT 5GS Optimization | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210236 | Critical Assets for NWDAF | draftCR | Huawei, HiSilicon, China Mobile | SCAS_5G_NWDAF | Rel-17 |
S3-102-e AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-210237 | Network Product Class Description for NWDAF | draftCR | Huawei, HiSilicon, China Mobile | SCAS_5G_NWDAF | Rel-17 |
S3-102-e AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-210238 | Correction to the access token storage in NF service consumer | CR | Huawei, HiSilicon | 33.501 15.11.0 CR#1033 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
| S3-210239 | Correction to the access token storage in NF service consumer |
CR revised to S3-210735 |
Huawei, HiSilicon | 33.501 16.5.0 CR#1034 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210240 | Correction to the access token storage in NF service consumer |
CR revised to S3-210736 |
Huawei, HiSilicon | 33.501 17.0.0 CR#1035 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210241 | Correction to service request process in OAuth 2.0 based authorization rel16 |
CR revised to S3-210793 |
Huawei, HiSilicon | 33.501 16.5.0 CR#1036 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210242 | Correction to service request process in OAuth 2.0 based authorization rel17 |
CR revised to S3-210794 |
Huawei, HiSilicon | 33.501 17.0.0 CR#1037 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210243 | Slice privacy protection in NSSAA related procedure | CR | Huawei, HiSilicon | 33.501 16.5.0 CR#1038 catF | eNS | Rel-16 |
S3-102-e AI: 4.9 |
not pursued | [WTS] [JSN] |
| S3-210244 | Address Editor's Note in solution 15 |
pCR revised to S3-210659 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210245 | A solution to protect PDU session related parameters for L2 relay |
pCR revised to S3-210660 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210246 | Propose to resolve EN in KI#16 | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210247 | Propose to resolve ENs in the clause of KI detail of KI#12 | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210248 | Propose to mitigate policy confliction using match report |
pCR revised to S3-210662 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210249 | Propose to mitigate policy conflication using restricted discovery |
pCR revised to S3-210663 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210250 | Clarification on key derivation |
CR revised to S3-210737 |
Huawei, HiSilicon | 33.536 16.2.0 CR#24 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210251 | Reply LS about the layer to provide security |
LS out LS To: RAN2, CT1 revised to S3-210738 |
Huawei, HiSilicon | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] | ||
| S3-210252 | Update evaluation to Solution#7 | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210253 | Clarification on A-KID generation |
CR revised to S3-210739 |
Huawei, HiSilicon | 33.535 17.0.0 CR#62 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
revised | [WTS] [JSN] |
| S3-210254 | Clarification on AAnF Selection | CR | Huawei, HiSilicon | 33.535 17.0.0 CR#63 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
not pursued | [WTS] [JSN] |
| S3-210255 | Update Key issue #11 | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210256 | Evaluation on Solution#3 |
pCR revised to S3-210664 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210257 | Evaluation on Solution#4 |
pCR revised to S3-210665 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210258 | Evaluation on Solution#5 | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210259 | Evaluation on solution #11 | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210260 | Conclusion on PC3 protection | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210261 | Address Editor's Note in solution 14 |
pCR revised to S3-210680 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210262 | Threat to trigger condition on NSSAA procedure | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
noted | [WTS] [JSN] | |
| S3-210263 | Living document for TS 33.511 | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210264 | Living document for TS 33.512 |
draftCR revised to S3-210740 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
revised | [WTS] [JSN] | |
| S3-210265 | Living document for TS 33.514 | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210266 | Living document for TS 33.517 | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210267 | Living document for TS 33.117 | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210268 | Living document for TR 33.926 |
draftCR revised to S3-210741 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
revised | [WTS] [JSN] | |
| S3-210269 | Threat analysis on the ability to create different child Sas | pCR | Huawei, HiSilicon, China Unicom | 33.52 0.1.0 | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
noted | [WTS] [JSN] |
| S3-210270 | Check whether the N3IWF has the ability to create different child Sas | pCR | Huawei, HiSilicon, China Unicom | 33.52 0.1.0 | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
noted | [WTS] [JSN] |
| S3-210271 | Threat analysis on mixing CP and UP into main SA | pCR | Huawei, HiSilicon | 33.52 0.1.0 | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
noted | [WTS] [JSN] |
| S3-210272 | Check whether the N3IWF creats a child SA for PDU session | pCR | Huawei, HiSilicon | 33.52 0.1.0 | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
noted | [WTS] [JSN] |
| S3-210273 | Threat analysis on select AAA-P and AAA-S | pCR | Huawei, HiSilicon | 33.326 0.1.0 | SCAS_5G_NSSAAF | Rel-17 |
S3-102-e AI: 4.18 |
approved | [WTS] [JSN] |
| S3-210274 | NSSAAF route the S-NSSAI to the right place | pCR | Huawei, HiSilicon | 33.326 0.1.0 | SCAS_5G_NSSAAF | Rel-17 |
S3-102-e AI: 4.18 |
approved | [WTS] [JSN] |
| S3-210275 | New skeleton to TR 33867 | pCR | Huawei, HiSilicon | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
approved | [WTS] [JSN] |
| S3-210276 | Threat analysis on finding the right NF insances are serving this UE | draftCR | Huawei, HiSilicon, China Mobile | SCAS_5G_NWDAF | Rel-17 |
S3-102-e AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-210277 | Solution to UE onboarding for non-public networks |
pCR revised to S3-210621 |
Intel Corporation (UK) Ltd | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210278 | Conclusions to TR33.840 | pCR | China Telecommunications | 33.84 0.2.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-102-e AI: 5.13 |
merged | [WTS] [JSN] |
| S3-210279 | Authentication procedure during Xn handover procedure | CR | NEC | 33.501 17.0.0 CR#1039 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.23 |
not pursued | [WTS] [JSN] |
| S3-210280 | Solution to UE onboarding for non-public networks using PA and SA |
pCR revised to S3-210622 |
Intel Corporation (UK) Ltd | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210281 | pCR to TR33.847- New solution on L3 UE-to-Network Relay |
pCR revised to S3-210674 |
CATT | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210282 | new solution to mitigate supi guessing and suci replay attack |
pCR revised to S3-210742 |
Huawei, HiSilicon | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
revised | [WTS] [JSN] |
| S3-210283 | F1 interface security for IAB in NR-DC mode | pCR | Huawei, HiSilicon | 33.824 0.7.0 | FS_NR_IAB_Sec | Rel-17 |
S3-102-e AI: 5.18 |
noted | [WTS] [JSN] |
| S3-210284 | updating the scope in TR33.824 |
pCR revised to S3-210666 |
Huawei, HiSilicon | 33.824 0.7.0 | FS_NR_IAB_Sec | Rel-17 |
S3-102-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-210285 | Conclusion on key issue 4 | pCR | Huawei, HiSilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
noted | [WTS] [JSN] |
| S3-210286 | Addressing the EN on solution1 | pCR | Huawei, HiSilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210287 | Addressing the EN on solution2 |
pCR revised to S3-210672 |
Huawei, HiSilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210288 | New solution for traffic protection in service layer |
pCR revised to S3-210667 |
Huawei, HiSilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210289 | New solution to support the UE mobility in MBS | pCR | Huawei, HiSilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
merged | [WTS] [JSN] |
| S3-210290 | Update the terms in TR 33.850 | pCR | Huawei, HiSilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210291 | Add evaluation to solution 1 |
pCR revised to S3-210668 |
Huawei, HiSilicon | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
revised | [WTS] [JSN] |
| S3-210292 | Add evaluation to solution 3 |
pCR revised to S3-210669 |
Huawei, HiSilicon | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
revised | [WTS] [JSN] |
| S3-210293 | Reply LS on User location identification from Carrier Aggregation secondary cell activation messages |
LS out LS To: GSMA FSAG |
HUAWEI TECHNOLOGIES Co. Ltd. |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210294 | Clarification on security protection in AMF reallocation(direct NAS reroute) |
CR revised to S3-210743 |
Huawei, HiSilicon | 33.501 16.5.0 CR#1040 catF | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.23 |
revised | [WTS] [JSN] |
| S3-210295 | UC3S_SID_revision | SID revised | Huawei, HiSilicon | FS_UC3S | Rel-17 |
S3-102-e AI: 5.21 |
noted | [WTS] [JSN] | |
| S3-210296 | pCR to TR33.847- New solution on UE-to-Network Relay based on primary authentication |
pCR revised to S3-210675 |
CATT | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210297 | Adding a new threat related with biding down attack in the threats | CR | China Telecom, Huawei, HiSilicon | 33.926 16.3.0 CR#38 catB | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
not pursued | [WTS] [JSN] |
| S3-210298 | New SID on security aspects on PAP/CHAP protocols in 5GS | SID new | China Telecom, Huawei, HiSilicon | Rel-17 |
S3-102-e AI: 5.21 |
noted | [WTS] [JSN] | ||
| S3-210299 | Evaluation on solution #14 | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210300 | Resolving the ENs related with abort operation in the test case | pCR | China Telecom, Huawei, HiSilicon | 33.226 0.3.0 | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] |
| S3-210301 | Reply LS on propagation of user consent related information during Xn inter-PLMN handover |
LS out LS is reply to S3-210028 LS To: RAN3 |
Ericsson Limited |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] | |||
| S3-210302 | Reply LS on SLIC |
LS out LS is reply to S3-210006 LS To: RAN2 |
Ericsson Limited |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210303 | Clarifying the scope |
pCR revised to S3-210770 |
China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210304 | Clarifying for types of virtualised network product class |
pCR revised to S3-210771 |
China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210305 | Clarifying for Generic virtualised network product model class description | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210306 | Clarifying for Generic assets and threats for GVNP of type 1 |
pCR revised to S3-210772 |
China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210307 | Clarifying for Generic assets and threats for GVNP of type 2 and type 3 | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210308 | Adding comparison | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210309 | Modifying test case in clause 5.2.5.5.7.2 | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
noted | [WTS] [JSN] |
| S3-210310 | clarifying the content in clause 5.2.5.6.6.1 and clause 5.2.5.6.7 |
pCR revised to S3-210773 |
China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210311 | Clarifying for the security requirements and test cases in clause 5.2.5.7.7.1 and 5.2.5.7.7.2 | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
noted | [WTS] [JSN] |
| S3-210312 | Adding hardening requirements for GVNP of type 3 | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210313 | Adding vendor development and product lifecycle processes and test laboratory accreditation into Clause 6 | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
noted | [WTS] [JSN] |
| S3-210314 | Adding evaluation and SCAS instantiation into clause 7 | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210315 | new proposal for way forward v2 | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
noted | [WTS] [JSN] |
| S3-210316 | editorial correction on TR33818-coversheet | pCR | China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210317 | Solution to botnet terminal detection | pCR | China Mobile | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
noted | [WTS] [JSN] |
| S3-210318 | Solution to provisioning of PNI-NPN credentials | pCR | China Mobile | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210319 | Authentication and Authorization between 5GMSGS Client and MSGin5G server based on AKMA | pCR | China Mobile | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
approved | [WTS] [JSN] |
| S3-210320 | Overview of MSGin5G Service | pCR | China Mobile | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
approved | [WTS] [JSN] |
| S3-210321 | Solution to address the Key issue #2.2 in TR 33.846 | pCR | China Mobile | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210322 | Discussion on enlarging the length of truncated MACs for 5G systems | pCR | China Mobile | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210323 | Find the right NF instance are serving the UE | pCR | China Mobile, Huawei, HiSilicon | 33.521 0.2.0 | SCAS_5G_NWDAF | Rel-17 |
S3-102-e AI: 4.15 |
approved | [WTS] [JSN] |
| S3-210324 | New Use Case for eNA |
pCR revised to S3-210603 |
China Mobile | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
revised | [WTS] [JSN] |
| S3-210325 | Adding test case on the confidentiality configuration in P-CSCF | pCR | China Telecom, Huawei, HiSilicon | 33.226 0.3.0 | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] |
| S3-210326 | Correct current uplink EPS NAS COUNT used at derivation of a mapped 5G security context |
CR revised to S3-210787 |
MediaTek Inc. | 33.501 16.5.0 CR#1041 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
revised | [WTS] [JSN] |
| S3-210327 | Linkability by distinguishing MAC failure and synchronization failure | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210328 | Update KI on SUPI guessing | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210329 | KI on linkability by SUCI |
pCR revised to S3-210731 |
Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
revised | [WTS] [JSN] |
| S3-210330 | Assuring SUCI generation by legitimiate SUPI owner | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210331 | EN resolution on SQNms protection | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210332 | Evaluation of solution 2.3 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210333 | EN related note to solution 4.4 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210334 | Evaluation criterias | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
merged | [WTS] [JSN] |
| S3-210335 | Editorial changes to TR |
pCR revised to S3-210732 |
Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
revised | [WTS] [JSN] |
| S3-210336 | SQNms protection by concealment in ME |
pCR revision of S3-203330 revised to S3-210733 |
Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
revised | [WTS] [JSN] |
| S3-210337 | AUTS SQNMS solution for EPS | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210338 | AUTS SQNMS solution for 5GS | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210339 | Typo correction in clause 6.9.9.4 | CR | Xidian University | 33.501 17.0.0 CR#1042 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
| S3-210340 | High-level conclusions for KI#1 (Credentials owned by an external entity) | discussion | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] | |
| S3-210341 | Resolving EN in KI#1 | pCR | Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210342 | Authentication method selection for N5CW | CR | Ericsson,Lenovo, Motorola Mobility, Cablelabs | 33.501 16.5.0 CR#1043 catF | 5WWC | Rel-16 |
S3-102-e AI: 4.7 |
agreed | [WTS] [JSN] |
| S3-210343 | draft LS on Feedback on function supporting primary authentication and authorization of SNPN UEs that use credentials from the AAA Server |
LS out LS To: SA2 revised to S3-210560 |
Ericsson |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] | |||
| S3-210344 | Resolving EN on SUPI privacy in solution #1 |
pCR revised to S3-210561 |
Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210345 | Authentication method selection for N5CW | CR | Ericsson,Lenovo, Motorola Mobility, Cablelabs | 33.501 17.0.0 CR#1044 catA | 5WWC | Rel-17 |
S3-102-e AI: 4.7 |
agreed | [WTS] [JSN] |
| S3-210346 | High-level conclusions for KI#1 (Credentials owned by an external entity) | pCR | Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210347 | Clarification on the format of NF type in the NF certification | CR | Huawei, Hisilicon | 33.31 16.6.0 CR#117 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210348 | Threats related to session establishment procedure | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
noted | [WTS] [JSN] | |
| S3-210349 | New test case on validation of S-NSSAIs in PDU session establishment request | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
noted | [WTS] [JSN] | |
| S3-210350 | DP on loop registration in CAG | discussion | Huawei, Hisilicon | Rel-16 |
S3-102-e AI: 4.23 |
noted | [WTS] [JSN] | ||
| S3-210351 | LS on loop registration in CAG |
LS out LS To: SA2, CT1 |
Huawei, Hisilicon | Rel-16 |
S3-102-e AI: 4.23 |
noted | [WTS] [JSN] | ||
| S3-210352 | New KI on service authorization for SNPNs |
pCR revised to S3-210644 |
Huawei, Hisilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210353 | New solution on service authorization for SNPNs |
pCR revised to S3-210645 |
Huawei, Hisilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210354 | New requirement on key issue #2 of TR 33.851 | pCR | Huawei, HiSilicon | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210355 | Assets and threats specific of encryption in network hiding in the I-CSCF | draftCR | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210356 | New test case on encryption in network hiding in the I-CSCF | pCR | Huawei, HiSilicon | 33.226 16.3.0 | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] |
| S3-210357 | Assets and threats specific of network hiding in the IBCF | draftCR | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210358 | New test case on network hiding in the IBCF | pCR | Huawei, HiSilicon | 33.226 16.3.0 | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] |
| S3-210359 | eSCAS:Add a new test case for GUTI allocation | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210360 | SCAS IPUPS: Add a new test |
draftCR revised to S3-210755 |
Huawei, Hisilicon | SCAS_5G_IPUPS | Rel-17 |
S3-102-e AI: 4.17 |
revised | [WTS] [JSN] | |
| S3-210361 | eSCAS:Add a new test case for NSSAA | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
noted | [WTS] [JSN] | |
| S3-210362 | eSCAS: Updating the security threat to user privacy | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210363 | eSCAS: Add a new threat on unauthorized slice access | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
noted | [WTS] [JSN] | |
| S3-210364 | SCAS: Correction of incomplete test cases | CR | Huawei, Hisilicon | 33.512 16.4.0 CR#9 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-210365 | EC: New key issue on N4 protection for UPF in customer network | pCR | Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
noted | [WTS] [JSN] |
| S3-210366 | EC: New solution to th ekey issue on N4 security | pCR | Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
noted | [WTS] [JSN] |
| S3-210367 | LS reply on changes to SoR delivery mechanims |
LS out LS To: CT4 |
Huawei, Hisilicon | Rel-16 |
S3-102-e AI: 4.23 |
noted | [WTS] [JSN] | ||
| S3-210368 | 5MBS: Updats to solution #3 |
pCR revised to S3-210641 |
Huawei, Hisilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210369 | 5MBS: Adding overview | pCR | Huawei, Hisilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210370 | 5MBS: Updates to solution #4 |
pCR revised to S3-210642 |
Huawei, Hisilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210371 | 5MBS: Updates to solution #5 |
pCR revised to S3-210643 |
Huawei, Hisilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210372 | NPN: New solution to key issue #1 | pCR | Huawei, Hisilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210373 | AMFReal: Updates to solution #3 |
pCR revised to S3-210646 |
Huawei, Hisilicon | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
revised | [WTS] [JSN] |
| S3-210374 | AMFReal: Updates to TR 33.864 |
pCR revised to S3-210647 |
Huawei, Hisilicon | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
revised | [WTS] [JSN] |
| S3-210375 | IMS SCAS: living doc for the threats | draftCR | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210376 | Resolving the ENs related with biding down attacker in the test case | draftCR | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210377 | Resolving the Ens related with biding down attack in the threats | draftCR | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210378 | Clarification on confidential IEs replacement handling in original N32-f message |
CR revised to S3-210745 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.517 16.1.0 CR#7 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
revised | [WTS] [JSN] |
| S3-210379 | Clarification on exposure of confidential IEs in N32-f message in TR 33.926 |
CR revised to S3-210746 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.926 16.3.0 CR#39 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
revised | [WTS] [JSN] |
| S3-210380 | Clarification on a figure and the key activation | CR | Huawei, HiSilicon | 33.535 16.2.0 CR#64 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210381 | Resolving the EN on the authorization between SCPs |
CR revised to S3-210747 |
Huawei, HiSilicon | 33.501 16.5.0 CR#1045 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210382 | Align the JSON format on encryption IE with CT4 in Rel15 |
CR revised to S3-210748 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#1046 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210383 | Mirror: align the JSON format on encryption IE with CT4 in Rel16 |
CR revised to S3-210749 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#1047 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210384 | Mirror: align the JSON format on encryption IE with CT4 in Rel17 |
CR revised to S3-210750 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#1048 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210385 | Adding the security requirement with encBlockIndex in Rel15 | CR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#1049 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
| S3-210386 | Mirror Adding the security requirement with encBlockIndex in Rel16 |
CR revised to S3-210751 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#1050 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210387 | Mirror Adding the security requirement with encBlockIndex in Rel17 |
CR revised to S3-210752 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#1051 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210388 | EC: Editorial changes and Resolving the ENs of solution #13 | pCR | Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210389 | EC: Resolving the En and adding evalution of solution #16 |
pCR revised to S3-210648 |
Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210390 | EC: Evaluation of solution #20 and conclusion of KI #8 |
pCR revised to S3-210649 |
Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210391 | EC: Evaluation of solution #21 | pCR | Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210392 | EC: Resolving the Editor’s notes and evaluation of solution #22 |
pCR revised to S3-210650 |
Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210393 | EC: skeleton of clause 7 and conclusion of KI #4 |
pCR revised to S3-210651 |
Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210394 | ProSe: Resolving the ENs of solution #16 |
pCR revised to S3-210652 |
Huawei, Hisilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210395 | Clarification on PLMN ID verification in Rel15 | CR | Huawei, HiSilicon | 33.501 15.11.0 CR#1052 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
| S3-210396 | Clarification on PLMN ID verification in Rel16 | CR | Huawei, HiSilicon | 33.501 16.5.0 CR#1053 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
| S3-210397 | Discussion paper on TAU reject issue during MME handover | discussion | Huawei, HiSilicon | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
noted | [WTS] [JSN] | |
| S3-210398 | LS on TAU reject issue during MME handover |
LS out LS To: CT4 |
Huawei, HiSilicon | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
noted | [WTS] [JSN] | |
| S3-210399 | IMS SCAS: Adding the assets and threats of the AS | draftCR | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210400 | Adding test cases on the authorization and privacy in AS | pCR | Huawei, HiSilicon | 33.226 0.3.0 | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] |
| S3-210401 | IMS SCAS: Adding the assets and threats of the MRFC | draftCR | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210402 | Adding details to provisioning key issue |
pCR revised to S3-210704 |
Ericsson, China Mobile, Huawei, InterDigital, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Philips, Samsung, ZTE | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210403 | Use case for KI#3 (Supporting IMS in SNPNs) not yet covered by existing specifications | discussion | Ericsson | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] | ||
| S3-210404 | New Solution to KI#3: Authentication to IMS Core using credentials generated with AKMA | pCR | Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210405 | New Solution to KI#3: Authentication to IMS Core using credentials generated from the KAUSF | pCR | Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210406 | LS on Feedback on Key Issue #4 "UE onboarding and remote provisioning" |
LS out LS To: SA2 |
Ericsson |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] | |||
| S3-210407 | Resolving SUPI privacy EN in solution #10 |
pCR revised to S3-210583 |
Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210408 | Resolving prerequisite EN in solution #10 |
pCR revised to S3-210584 |
Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210409 | Resolving indication EN in solution #10 | pCR | Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210410 | Resolving CP provisioning EN in solution #10 | pCR | Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
noted | [WTS] [JSN] |
| S3-210411 | Corrections for the NRF token request service | CR | Ericsson | 33.501 16.5.0 CR#1054 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210412 | Corrections for the NRF token request service | CR | Ericsson | 33.501 17.0.0 CR#1055 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210413 | OAuth 2.0 client registration and NF Service registration | discussion | Ericsson |
S3-102-e AI: 4.1 |
noted | [WTS] [JSN] | |||
| S3-210414 | New KI: Roaming case for token-based authorization in indirect communication | pCR | Ericsson | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
noted | [WTS] [JSN] |
| S3-210415 | Correcting notation used for inter-AMF mobility key derivation |
CR revision of S3-202948 revised to S3-210782 |
MediaTek Inc. | 33.501 16.5.0 CR#9631 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
revised | [WTS] [JSN] |
| S3-210416 | KI on Verification of UE in subscription and notification in the delegated "Subscribe-Notify" scenarios |
pCR revised to S3-210653 |
Huawei, Hisilicon | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210417 | KI on Verification of UE in subscription and notification in the non-delegated "Subscribe-Notify" scenarios | pCR | Huawei, Hisilicon | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
merged | [WTS] [JSN] |
| S3-210418 | New key issue for Paging Cause protection | pCR | Huawei, HiSilicon | 33.873 0.0.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-210419 | Analytics for MitM Attack Detection | pCR | Lenovo, Motorola Mobility | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
noted | [WTS] [JSN] |
| S3-210420 | Skeleton of TR eSBA SEC | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210421 | Introduction |
pCR revised to S3-210562 |
Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210422 | Scope | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210423 | Authentication of NRF and NFp in indirect communication |
pCR revised to S3-210564 |
Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210424 | End-to-end authentication in roaming case | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
noted | [WTS] [JSN] |
| S3-210425 | SCP deployment models |
pCR revised to S3-210565 |
Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210426 | Verification of URI in subscription and notification | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
merged | [WTS] [JSN] |
| S3-210427 | Dynamic authorization between SCPs or between NF and SCP |
pCR revised to S3-210566 |
Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210428 | End-to-End Critical HTTP headers and body parts integrity protection |
pCR revised to S3-210567 |
Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-210429 | NRF service management | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
noted | [WTS] [JSN] |
| S3-210430 | Update of Solution #7 | pCR | Lenovo, Motorola Mobility | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
noted | [WTS] [JSN] |
| S3-210431 | Update of solution #6 | pCR | Lenovo, Motorola Mobility | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210432 | Evaluation of solution #6 | pCR | Lenovo, Motorola Mobility | 33.857 0.3.0 | FS_UP_IP_Sec, FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210433 | Update to Solution #24: Interworking handover from 5GS to EPS |
pCR revised to S3-210588 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210434 | Update to Solution #21: Interworking handover from EPS to 5GS |
pCR revised to S3-210589 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210435 | Update to Solution #22: S1 handover |
pCR revised to S3-210590 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210436 | Update to Solution #23: X2 handover |
pCR revised to S3-210591 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210437 | Discussion paper on UP IP policy in EPS | pCR | Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
noted | [WTS] [JSN] |
| S3-210438 | Conclusion on UE connects to EPC via eUTRA |
pCR revised to S3-210592 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210439 | ProSe: Update to solution #21 |
pCR revised to S3-210585 |
Ericsson | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210440 | ProSe: New solution for the use of authorization token in UE-to-UE relay |
pCR revised to S3-210586 |
Ericsson | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210441 | ProSe: Update to solution #6 |
pCR revised to S3-210587 |
Ericsson | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210442 | Mapping table | pCR | Nokia, Nokia Shanghai Bell | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210443 | Evaluation update of solution 7 | pCR | Nokia, Nokia Shanghai Bell | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210444 | DHIES encryption to avoid UAV spoofing | pCR | Nokia, Nokia Shanghai Bell | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
noted | [WTS] [JSN] |
| S3-210445 | Correction to FC values in range for future use in 3GPP specifications | CR | Samsung | 33.501 17.0.0 CR#1056 catF | TEI17 | Rel-17 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210446 | [eNA]Updates to KI #1.1 | pCR | Samsung | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210447 | Network provides authorization to AF/UE for KAF key refresh | CR | Samsung | 33.535 17.0.0 CR#65 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
not pursued | [WTS] [JSN] |
| S3-210448 | [ProSe] pCR for resolving ENs in solution#1 |
pCR revised to S3-210577 |
Samsung | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210449 | Discussion on MitM attack | discussion | Samsung | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
noted | [WTS] [JSN] | |
| S3-210450 | CR for identification of MitM attack | CR | Samsung | 33.501 16.5.0 CR#1057 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
not pursued | [WTS] [JSN] |
| S3-210451 | CR for correction in SEAL |
CR revised to S3-210707 |
Samsung | 33.434 16.1.0 CR#3 catF | SEAL | Rel-16 |
S3-102-e AI: 4.23 |
revised | [WTS] [JSN] |
| S3-210452 | CR to correct figure 7A.2.4-1 | CR | Samsung | 33.501 17.0.0 CR#1058 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.7 |
not pursued | [WTS] [JSN] |
| S3-210453 | CR to correct figure 7A.2.4-1 | CR | Samsung | 33.501 16.5.0 CR#1059 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.7 |
not pursued | [WTS] [JSN] |
| S3-210454 | Update to KI#4 in TR 33.862 |
pCR revised to S3-210578 |
Samsung | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
revised | [WTS] [JSN] |
| S3-210455 | Authentication and authorization for MSGin5G UE |
pCR revised to S3-210579 |
Samsung | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
revised | [WTS] [JSN] |
| S3-210456 | Authentication and authorization for legacy UE |
pCR revised to S3-210580 |
Samsung | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
revised | [WTS] [JSN] |
| S3-210457 | Authentication and authorization for Non-3GPP UE |
pCR revised to S3-210582 |
Samsung | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
revised | [WTS] [JSN] |
| S3-210458 | Updates to solution#7 to identify the appropriate AMF by the NEF |
pCR revised to S3-210575 |
Samsung | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210459 | LS on Reply LS on Storage of KAUSF from CT1 |
LS out LS is reply to S3-210005 source LS: C1-207764 LS To: CT1 revised to S3-210706 |
Samsung | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
revised | [WTS] [JSN] | |
| S3-210460 | Handling of KAUSF upon successful primary authentication | CR | Samsung, Nokia, Nokia Shanghai Bell, Intel | 33.501 16.5.0 CR#1060 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
not pursued | [WTS] [JSN] |
| S3-210461 | pCR: AMF re-allocation by re-directing UE to new AMF |
pCR revised to S3-210576 |
Samsung | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
revised | [WTS] [JSN] |
| S3-210462 | Key Issue on Authorization for MUSIM optimizations | pCR | Samsung | 33.873 0.0.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-210463 | Addition to support key update in Solution 1 |
pCR revised to S3-210690 |
Philips International B.V. | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210464 | Conclusions for TR 33.845 |
pCR revised to S3-210708 |
Ericsson | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
revised | [WTS] [JSN] |
| S3-210465 | Update to solution #17 |
pCR revised to S3-210604 |
Ericsson | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210466 | Update to solution #2 |
pCR revised to S3-210605 |
Ericsson | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210467 | Typo correction in clause 6.9.9.4 | CR | Xidian University | 33.501 16.5.0 CR#1061 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
| S3-210468 | removal of Editor’s Notes | pCR | Ericsson | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210469 | Some clarifications to solution #10 |
pCR revised to S3-210628 |
Qualcomm Incorporated | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210470 | Proposed solution for pairing authorisation in 5G |
pCR revised to S3-210629 |
Qualcomm Incorporated | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210471 | Proposed solution for UAV authorisation when connected to 4G |
pCR revised to S3-210630 |
Qualcomm Incorporated | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210472 | Discussion on K_AUSF handling | discussion | Qualcomm Incorporated |
S3-102-e AI: 4.23 |
noted | [WTS] [JSN] | |||
| S3-210473 | Update of solution #1 in TR 33.864 |
pCR revised to S3-210631 |
Qualcomm Incorporated | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
revised | [WTS] [JSN] |
| S3-210474 | Addressing the EN in solution #18 |
pCR revised to S3-210632 |
Qualcomm Incorporated | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210475 | Addressing some ENs in solution #20 | pCR | Qualcomm Incorporated | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210476 | Proposed partial conclusion to key issues #1 and #2 | pCR | Qualcomm Incorporated | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
merged | [WTS] [JSN] |
| S3-210477 | Profiling the GBA TLS protocols for use with AKMA |
CR revised to S3-211785 |
Qualcomm Incorporated | 33.535 17.0.0 CR#66 catB | AKMA_TLS | Rel-17 |
S3-102-e AI: 4.23 |
not pursued | [WTS] [JSN] |
| S3-210478 | Adding references to AKMA profiles of Ua protocols | CR | Qualcomm Incorporated | 33.222 16.1.0 CR#53 catB | DUMMY | Rel-17 |
S3-102-e AI: 4.23 |
not pursued | [WTS] [JSN] |
| S3-210479 | New WID on AKMA Ua protocol profiles |
WID new revised to S3-211784 |
Qualcomm Incorporated |
S3-102-e AI: 4.22 |
noted | [WTS] [JSN] | |||
| S3-210480 | 5G GUTI re-allocation |
CR revised to S3-210759 |
Qualcomm Incorporated, Huawei, Hisilicon | 33.501 16.5.0 CR#1062 catF | 5G_CIoT | Rel-16 |
S3-102-e AI: 4.6 |
revised | [WTS] [JSN] |
| S3-210481 | 5G CIoT K_NG-RAN derivation | CR | Qualcomm Incorporated | 33.501 16.5.0 CR#1063 catF | 5G_CIoT | Rel-16 |
S3-102-e AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-210482 | New Key Issue on security policy handling for 5G Prose services |
pCR revised to S3-211064 |
Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-210483 | Solution 18 EN resolution |
pCR revised to S3-210608 |
Qualcomm Incorporated | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210484 | Solution 19 EN resolution | pCR | Qualcomm Incorporated | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210485 | Solution 20 EN resolution |
pCR revised to S3-210609 |
Qualcomm Incorporated | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210486 | Update of solution #18 to add authorization for the UE-to-Network relay |
pCR revised to S3-210607 |
Qualcomm Incorporated | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210487 | Security for MBS traffic during handover |
pCR revised to S3-210610 |
Qualcomm Incorporated | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210488 | Reply LS on False Base Station Detection |
LS out LS is reply to R2-1914224 LS To: RAN2 |
Qualcomm Incorporated |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] | |||
| S3-210489 | Sending UE identifier to the AKMA AF |
CR revision of S3-203191 |
Qualcomm Incorporated, China Mobile | 33.535 17.0.0 CR#521 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
not pursued | [WTS] [JSN] |
| S3-210490 | Extend UPIP support in 5GS for all 5GC connected RAN architecture (NG-RAN) options |
draftCR revision of S3-203511 revised to S3-210701 |
Qualcomm Incorporated | eUPIP_SEC | Rel-17 |
S3-102-e AI: 4.2 |
revised | [WTS] [JSN] | |
| S3-210491 | pCR to UP IP draft CR to TS 33.501 |
other revised to S3-210700 |
Qualcomm Incorporated |
S3-102-e AI: 4.2 |
revised | [WTS] [JSN] | |||
| S3-210492 | Reply LS method for collection of data from the UE |
LS out LS is reply to S2-2006292 LS To: SA2 revised to S3-210611 |
Qualcomm Incorporated |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] | |||
| S3-210493 | Addressing the EN in solution #4 |
pCR revised to S3-210613 |
Qualcomm Incorporated | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210494 | pCR: Security architecture conclusion for KI #1 |
pCR revised to S3-210614 |
Qualcomm Incorporated | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210495 | Addressing some ENs in solution #11 |
pCR revised to S3-210612 |
Qualcomm Incorporated | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
revised | [WTS] [JSN] |
| S3-210496 | UE Sending GPSI (if available) to the AF | CR | Samsung | 33.535 17.0.0 CR#67 catB | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
not pursued | [WTS] [JSN] |
| S3-210497 | pCR to TR 33.853 – New Best Effort solution for EPS using UE Radio Access capabilities |
pCR revised to S3-210556 |
VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210498 | Key issue on security of data via Messaging Framework |
pCR revised to S3-210679 |
Ericsson | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-210499 | New WID on 3GPP profiles for cryptographic algorithms and security protocols |
WID new revised to S3-210781 |
Ericsson | Rel-17 |
S3-102-e AI: 4.22 |
revised | [WTS] [JSN] | ||
| S3-210500 | pCR to TR 33.853 - Updates to Solution#13 - MME and IoDT test impacts |
pCR revised to S3-210558 |
VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210501 | Home network triggered reauthentication | pCR | NTT DOCOMO INC. | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
noted | [WTS] [JSN] |
| S3-210502 | pCR to TR 33.853 - Updates to Solution#14 – optional use of security mode command | pCR | VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210503 | pCR to TR 33.853 - Updates to Solution#15 – 5GC control concept | pCR | VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210504 | pCR to TR 33.853 - Updates to Solution#18 – small corrections | pCR | VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
merged | [WTS] [JSN] |
| S3-210505 | Evaluation of Solution #7 |
pCR revised to S3-210682 |
Lenovo, Motorola Mobility | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
revised | [WTS] [JSN] |
| S3-210506 | TR editorials | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210507 | Mapping table | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210508 | Annex on Security considerations for integration with TSN | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210509 | KI details Attacks based on asymmetric channel delay | pCR | Nokia, Nokia Shanghai Bell, Deutsche Telekom | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210510 | Authorization of incoming time synchronization messages based on policies | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210511 | Evaluation to solution 1 | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
merged | [WTS] [JSN] |
| S3-210512 | Evaluation to solution 3 | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
merged | [WTS] [JSN] |
| S3-210513 | pCR to TR 33.853 - Updates to Solution #20 – small corrections |
pCR revised to S3-210559 |
VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] |
| S3-210514 | pCR to TR 33.853 - Updates to Solution #21 EPS to 5GS handover– evaluation | pCR | VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210515 | Updated proposal to introduce draft-ietf-emu-rfc5448bis to TS 33.501 |
discussion revision of S3-203322 |
Ericsson |
S3-102-e AI: 4.1 |
noted | [WTS] [JSN] | |||
| S3-210516 | pCR to TR 33.853 – New Solution #AC Handover from EPS to 5GS using unmodified R15/16 messages and procedures | pCR | VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210517 | TR 33.846: comparison of candidate solutions |
pCR revised to S3-210779 |
THALES | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
revised | [WTS] [JSN] |
| S3-210518 | pCR to 33.809 - addition of evaluation for solution 8 | pCR | VODAFONE Group Plc | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210519 | Living document for TS 33.220: SBA support for Zh and Zn interfaces | draftCR | Ericsson | GBA_5G | Rel-17 |
S3-102-e AI: 4.11 |
approved | [WTS] [JSN] | |
| S3-210520 | Living document for TS 33.223: SBA support for Zpn | draftCR | Ericsson | GBA_5G | Rel-16 |
S3-102-e AI: 4.11 |
approved | [WTS] [JSN] | |
| S3-210521 | pCR to living document for TS 33.220: Support GBA in UDM | draftCR | Ericsson | GBA_5G | Rel-17 |
S3-102-e AI: 4.11 |
noted | [WTS] [JSN] | |
| S3-210522 | pCR to living document for TS 33.223: Support GBA in UDM | draftCR | Ericsson | GBA_5G | Rel-16 |
S3-102-e AI: 4.11 |
noted | [WTS] [JSN] | |
| S3-210523 | [DRAFT] LS on the SBA for GBA |
LS out LS To: SA2 |
Ericsson | GBA_5G | Rel-17 |
S3-102-e AI: 4.11 |
noted | [WTS] [JSN] | |
| S3-210524 | AMF reallocation: Update to solution #2 | pCR | Ericsson | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
noted | [WTS] [JSN] |
| S3-210525 | Discussion paper on the shared network entity assumptions for the AMF re-allocation security study | discussion | Ericsson | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
noted | [WTS] [JSN] | |
| S3-210526 | Shared network entity assumptions for the purpose of AMF re-allocation | pCR | Ericsson | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
noted | [WTS] [JSN] |
| S3-210527 | New solution for NAS re-route via RAN and the use of a well-connected network function | pCR | Ericsson | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
noted | [WTS] [JSN] |
| S3-210528 | New solution for AMF re-allocation using a well-connected network function | pCR | Ericsson | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
noted | [WTS] [JSN] |
| S3-210529 | Draft CR on algorithm selection | draftCR | Ericsson | eUPIP_SEC | Rel-17 |
S3-102-e AI: 4.2 |
approved | [WTS] [JSN] | |
| S3-210530 | Notes: SAGE/SA3 2nd joint conference call on the 256-bit topics | report | NTT DOCOMO INC. |
S3-102-e AI: 3 |
noted | [WTS] [JSN] | |||
| S3-210531 | Resolving EN in Clause 4.3 Architecture and Security Assumptions |
pCR revised to S3-210683 |
Lenovo, Motorola Mobility | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
revised | [WTS] [JSN] |
| S3-210532 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 15.11.0 CR#1064 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210533 | Update to Solution#4 on enabling security during AMF reallocation via RAN |
pCR revised to S3-210684 |
Lenovo, Motorola Mobility | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
revised | [WTS] [JSN] |
| S3-210534 | Solution to ensure system availability for indirect AMF reallocation |
pCR revised to S3-210685 |
Lenovo, Motorola Mobility | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
revised | [WTS] [JSN] |
| S3-210535 | Updates to Key Issue #7 |
pCR revised to S3-210686 |
Lenovo, Motorola Mobility | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210536 | Presentation of Specification/Report to TSG: TR33.853, Version <2.0.0> | TS or TR cover | VODAFONE Group Plc | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
noted | [WTS] [JSN] | |
| S3-210537 | Update to Solution #7 |
pCR revised to S3-210687 |
Lenovo, Motorola Mobility | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210538 | Solution on UAV and UAV-C Pairing Authorization |
pCR revised to S3-210688 |
Lenovo, Motorola Mobility | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
revised | [WTS] [JSN] |
| S3-210539 | Rel17 SID on network slice security |
SID new revised to S3-210757 |
Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT, China Unicom, China Mobile, InterDigital, NEC | Rel-17 |
S3-102-e AI: 5.21 |
revised | [WTS] [JSN] | ||
| S3-210540 | pCR to TR 33.853 – Conclusion on UE connects to EPC via eUTRA | pCR | VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
merged | [WTS] [JSN] |
| S3-210541 | New annex of TR 33.809 – analysis of KI#2 and recommendations | pCR | CableLabs, Deutsche Telekom AG, InterDigital | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
noted | [WTS] [JSN] |
| S3-210542 | [DRAFT] LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS out LS To: RAN2, RAN3, CT1, SA2 revised to S3-210563 |
VODAFONE Group Plc | Rel-17 |
S3-102-e AI: 5.3 |
revised | [WTS] [JSN] | ||
| S3-210543 | Solution to mitigate privacy issues of relay service codes and PDU parameters for L3 UE-to-NW relays |
pCR revised to S3-210597 |
Philips International B.V. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-210544 | New WID on normative changes for User Plane Integrity Protection for LTE options |
WID new revised to S3-210722 |
VODAFONE Group Plc | Rel-17 |
S3-102-e AI: 4.22 |
revised | [WTS] [JSN] | ||
| S3-210545 | resolving ed note on protection policy mismatch |
CR revised to S3-210792 |
NTT DOCOMO INC. | 33.501 15.11.0 CR#1065 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
| S3-210546 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1066 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
| S3-210547 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1067 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
| S3-210548 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1068 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
| S3-210549 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1069 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
| S3-210550 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1070 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210551 | resolving ed note on protection policy mismatch | CR | NTT DOCOMO INC. | 33.501 16.5.0 CR#1071 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
merged | [WTS] [JSN] |
| S3-210552 | resolving ed note on protection policy mismatch | CR | NTT DOCOMO INC. | 33.501 17.0.0 CR#1072 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
merged | [WTS] [JSN] |
| S3-210553 | SA3 meeting calendar | other | WG Chair |
S3-102-e AI: 7 |
noted | [WTS] [JSN] | |||
| S3-210554 | Draft agenda for SA3 102bis-e | agenda | WG Chair |
S3-102-e AI: 7 |
noted | [WTS] [JSN] | |||
| S3-210555 | Updated Solution #22: Representation of identities during broadcast |
pCR revision of S3-210071 |
KPN N.V. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210556 | pCR to TR 33.853 – New Best Effort solution for EPS using UE Radio Access capabilities |
pCR revision of S3-210497 |
VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210557 | Updated Solution #23: Initial key with validity time |
pCR revision of S3-210072 |
KPN N.V. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210558 | pCR to TR 33.853 - Updates to Solution#13 - MME and IoDT test impacts |
pCR revision of S3-210500 |
VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210559 | pCR to TR 33.853 - Updates to Solution #20 – small corrections |
pCR revision of S3-210513 |
VODAFONE Group Plc | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210560 | draft LS on Feedback on function supporting primary authentication and authorization of SNPN UEs that use credentials from the AAA Server |
LS out LS To: SA2 revision of S3-210343 |
Ericsson |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] | |||
| S3-210561 | Resolving EN on SUPI privacy in solution #1 |
pCR revision of S3-210344 |
Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210562 | Introduction |
pCR revision of S3-210421 |
Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210563 | LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS out LS To: RAN2, RAN3, CT4, SA2 LS reply in C1-211161, C1-211339, C1-211461 revision of S3-210542 |
VODAFONE Group Plc | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] | ||
| S3-210564 | Authentication of NRF and NFp in indirect communication |
pCR revision of S3-210423 |
Nokia, Nokia Shanghai Bell, CableLabs, Mavenir | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210565 | SCP deployment models |
pCR revision of S3-210425 |
Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210566 | Dynamic authorization between SCPs or between NF and SCP |
pCR revision of S3-210427 |
Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210567 | End-to-End Critical HTTP headers and body parts integrity protection |
pCR revision of S3-210428 |
Nokia, Nokia Shanghai Bell, Mavenir, CablLabs | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210568 | TR33.853 1.4.0 | draft TR | VODAFONE Group Plc | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] | |
| S3-210569 | TR 33866-020_update on formats and typos |
pCR revision of S3-210105 |
Nokia, Nokia Shanghai Bell, China Mobile | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210570 | Abbreviations.doc |
pCR revision of S3-210106 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210571 | KI on Authorization of consumers for data access via DCCF.doc |
pCR revision of S3-210116 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210572 | Requirements on KI Anomalous NF behavior detection by NWDAF |
pCR revision of S3-210111 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210573 | KI on protection of data in transfer |
pCR revision of S3-210107 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210574 | Usage of current SBA mechanisms to protect data in transfer |
pCR revision of S3-210108 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210575 | Updates to solution#7 to identify the appropriate AMF by the NEF |
pCR revision of S3-210458 |
Samsung, Lenovo and Motorola Mobility | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210576 | pCR: AMF re-allocation by re-directing UE to new AMF |
pCR revision of S3-210461 |
Samsung | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
approved | [WTS] [JSN] |
| S3-210577 | [ProSe] pCR for resolving ENs in solution#1 |
pCR revision of S3-210448 |
Samsung | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210578 | Update to KI#4 in TR 33.862 |
pCR revision of S3-210454 |
Samsung | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
approved | [WTS] [JSN] |
| S3-210579 | Authentication and authorization for MSGin5G UE |
pCR revision of S3-210455 |
Samsung | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
approved | [WTS] [JSN] |
| S3-210580 | Authentication and authorization for legacy UE |
pCR revision of S3-210456 |
Samsung | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
approved | [WTS] [JSN] |
| S3-210581 | Solution on UE data collection protection.docx |
pCR revision of S3-210114 |
Nokia, Nokia Shanghai Bell | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210582 | Authentication and authorization for Non-3GPP UE |
pCR revision of S3-210457 |
Samsung | 33.862 0.2.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
approved | [WTS] [JSN] |
| S3-210583 | Resolving SUPI privacy EN in solution #10 |
pCR revision of S3-210407 |
Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210584 | Resolving prerequisite EN in solution #10 |
pCR revision of S3-210408 |
Ericsson | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210585 | ProSe: Update to solution #21 |
pCR revision of S3-210439 |
Ericsson | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210586 | ProSe: New solution for the use of authorization token in UE-to-UE relay |
pCR revision of S3-210440 |
Ericsson | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210587 | ProSe: Update to solution #6 |
pCR revision of S3-210441 |
Ericsson | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210588 | Update to Solution #24: Interworking handover from 5GS to EPS |
pCR revision of S3-210433 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210589 | Update to Solution #21: Interworking handover from EPS to 5GS |
pCR revision of S3-210434 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210590 | Update to Solution #22: S1 handover |
pCR revision of S3-210435 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210591 | Update to Solution #23: X2 handover |
pCR revision of S3-210436 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210592 | Conclusion on UE connects to EPC via eUTRA |
pCR revision of S3-210438 |
Ericsson | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210593 | TR 33.854 Update for solution#5 |
pCR revision of S3-210093 |
InterDigital, Europe, Ltd. | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210594 | Solution for UAV location privacy |
pCR revision of S3-210094 |
InterDigital, Europe, Ltd. | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210595 | Conclusion to TR 33.840 |
pCR revision of S3-210062 |
Futurewei | 33.84 0.2.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-102-e AI: 5.13 |
approved | [WTS] [JSN] |
| S3-210596 | LS on conclusion of security study of disaggregated gNB architecture |
LS out LS To: RAN3 revision of S3-210063 |
Futurewei | FS_disagg_gNB_Sec | Rel-17 |
S3-102-e AI: 5.13 |
approved | [WTS] [JSN] | |
| S3-210597 | Solution to mitigate privacy issues of relay service codes and PDU parameters for L3 UE-to-NW relays |
pCR revision of S3-210543 |
Philips International B.V. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210598 | TR 33.847 Update for solution #10 |
pCR revision of S3-210122 |
InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210599 | Solution for NSSAA procedure for Remote UE with L3 UE-to-Network relay | pCR | InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
| S3-210600 | Solution for secondary authentication Remote UE with L3 UE-to-Network relay |
pCR revision of S3-210124 |
InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210601 | Solution for NSSAA procedure for Remote UE with L3 UE-to-Network relay |
pCR revision of S3-210123 |
InterDigital, Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210602 | New solution on UE onboarding for SNPN with the interaction between PS and DCS |
pCR revision of S3-210220 |
Alibaba Group | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210603 | New Use Case for eNA |
pCR revision of S3-210324 |
China Mobile | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
approved | [WTS] [JSN] |
| S3-210604 | Update to solution #17 |
pCR revision of S3-210465 |
Ericsson | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210605 | Update to solution #2 |
pCR revision of S3-210466 |
Ericsson | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210606 | TR 33.840 v1.0.0 | pCR | China Telecomunication Corp. | 33.84 0.2.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-102-e AI: 5.13 |
approved | [WTS] [JSN] |
| S3-210607 | Update of solution #18 to add authorization for the UE-to-Network relay |
pCR revision of S3-210486 |
Qualcomm Incorporated | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210608 | Solution 18 EN resolution |
pCR revision of S3-210483 |
Qualcomm Incorporated | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210609 | Solution 20 EN resolution |
pCR revision of S3-210485 |
Qualcomm Incorporated | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210610 | Security for MBS traffic during handover |
pCR revision of S3-210487 |
Qualcomm Incorporated | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210611 | Reply LS method for collection of data from the UE |
LS out LS is reply to S3-210021 LS To: SA2 revision of S3-210492 |
Qualcomm Incorporated | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] | ||
| S3-210612 | Addressing some ENs in solution #11 |
pCR revision of S3-210495 |
Qualcomm Incorporated | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210613 | Addressing the EN in solution #4 |
pCR revision of S3-210493 |
Qualcomm Incorporated | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210614 | pCR: Security architecture conclusion for KI #1 |
pCR revision of S3-210494 |
Qualcomm Incorporated | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210615 | Remove EN3-revocation |
pCR revision of S3-210203 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210616 | Remove EN1-exchange ID with USS |
pCR revision of S3-210204 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210617 | Remove EN2- revocation |
pCR revision of S3-210205 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210618 | Remove EN1:security of group management |
pCR revision of S3-210206 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210619 | Remove EN2: Time synchronization |
pCR revision of S3-210207 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210620 | Draft TR 33.864 v0.3.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson Japan K.K. | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
approved | [WTS] [JSN] | |
| S3-210621 | Solution to UE onboarding for non-public networks |
pCR revision of S3-210277 |
Intel Corporation (UK) Ltd | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210622 | Solution to UE onboarding for non-public networks using PA and SA |
pCR revision of S3-210280 |
Intel Corporation (UK) Ltd | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210623 | Updates to solution 18: Removal EN related to EEC ID |
pCR revision of S3-210180 |
Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210624 | Updates to solution 18: Removal EN related to identification of serving AMF |
pCR revision of S3-210182 |
Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210625 | Updates to solution 12: Removing EN |
pCR revision of S3-210192 |
Intel Corporation (UK) Ltd | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210626 | Security Solution for Busy Indication using NAS signaling |
other revision of S3-210209 |
Intel Corporation (UK) Ltd |
S3-102-e AI: 5.19 |
approved | [WTS] [JSN] | |||
| S3-210627 | draft TR 33.873 Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules 0.2 | draft TR | Intel China Ltd. | FS_MUSIM_SEC | Rel-17 |
S3-102-e AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-210628 | Some clarifications to solution #10 |
pCR revision of S3-210469 |
Qualcomm Incorporated | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210629 | Proposed solution for pairing authorisation in 5G |
pCR revision of S3-210470 |
Qualcomm Incorporated | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210630 | Proposed solution for UAV authorisation when connected to 4G |
pCR revision of S3-210471 |
Qualcomm Incorporated | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210631 | Update of solution #1 in TR 33.864 |
pCR revision of S3-210473 |
Qualcomm Incorporated | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
approved | [WTS] [JSN] |
| S3-210632 | Addressing the EN in solution #18 |
pCR revision of S3-210474 |
Qualcomm Incorporated, Vodafone | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210633 | LBO roaming scenario should be supported in solution#6.7 in TR 33.839 |
pCR revision of S3-210171 |
ZTE Corporation | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210634 | Update the key issue#7 in TR 33.839 |
pCR revision of S3-210172 |
ZTE Corporation | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210635 | Update the solution#14 in TR 33.839 |
pCR revision of S3-210173 |
ZTE Corporation | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210636 | TR 33.847 - Resolve ENs in Sol13 |
pCR revision of S3-210068 |
LG Electronics Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210637 | TR 33.847 - Evaluation of Sol13 |
pCR revision of S3-210069 |
LG Electronics Inc. | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210638 | Evaluation of Solution #8 |
pCR revision of S3-210176 |
ZTE Corporation | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210639 | Evaluation of Solution #9 |
pCR revision of S3-210177 |
ZTE Corporation | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210640 | Draft TR 33.850 |
pCR revised to S3-210670 |
Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
revised | [WTS] [JSN] |
| S3-210641 | 5MBS: Updats to solution #3 |
pCR revision of S3-210368 |
Huawei, Hisilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210642 | 5MBS: Updates to solution #4 |
pCR revision of S3-210370 |
Huawei, Hisilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210643 | 5MBS: Updates to solution #5 |
pCR revision of S3-210371 |
Huawei, Hisilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210644 | New KI on service authorization for SNPNs |
pCR revision of S3-210352 |
Huawei, Hisilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210645 | New solution on service authorization for SNPNs |
pCR revision of S3-210353 |
Huawei, Hisilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210646 | AMFReal: Updates to solution #3 |
pCR revision of S3-210373 |
Huawei, Hisilicon | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
approved | [WTS] [JSN] |
| S3-210647 | AMFReal: Updates to TR 33.864 |
pCR revision of S3-210374 |
Huawei, Hisilicon | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
withdrawn | [WTS] [JSN] |
| S3-210648 | EC: Resolving the En and adding evalution of solution #16 |
pCR revision of S3-210389 |
Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210649 | EC: Evaluation of solution #20 and conclusion of KI #8 |
pCR revision of S3-210390 |
Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210650 | EC: Resolving the Editor’s notes and evaluation of solution #22 |
pCR revision of S3-210392 |
Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210651 | EC: skeleton of clause 7 and conclusion of KI #4 |
pCR revision of S3-210393 |
Huawei, Hisilicon | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210652 | ProSe: Resolving the ENs of solution #16 |
pCR revision of S3-210394 |
Huawei, Hisilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210653 | KI on Verification of UE in subscription and notification in the delegated "Subscribe-Notify" scenarios |
pCR revision of S3-210416 |
Huawei, Hisilicon,Nokia, Nokia Shanghai Bell | 33.875 0.0.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210654 | Draft TR33.839 0.4.0 | draft TR | Huawei, Hisilicon | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] | |
| S3-210655 | New Solution for UPIP for EPS |
pCR revision of S3-210225 |
Huawei, HiSilicon | 33.853 1.3.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e AI: 5.3 |
approved | [WTS] [JSN] |
| S3-210656 | Analysis for UC3S |
pCR revision of S3-210228 |
Huawei, HiSilicon | 33.867 0.2.0 | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
noted | [WTS] [JSN] |
| S3-210657 | New Solution on Authentication for UE onboarding for SNPN |
pCR revision of S3-210231 |
Huawei, HiSilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210658 | Solution Update for Solution #5 |
pCR revision of S3-210232 |
Huawei, HiSilicon | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210659 | Address Editor's Note in solution 15 |
pCR revision of S3-210244 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210660 | A solution to protect PDU session related parameters for L2 relay |
pCR revision of S3-210245 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210661 | Propose to resolve ENs in the clause of KI detail of KI#12 | pCR | Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
| S3-210662 | Mitigate the conflict between policies using match report |
pCR revision of S3-210248 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210663 | Mitigate the conflict between policies using restricted discovery |
pCR revision of S3-210249 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210664 | Evaluation on Solution#3 |
pCR revision of S3-210256 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210665 | Evaluation on Solution#4 |
pCR revision of S3-210257 |
Huawei, HiSilicon | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210666 | updating the scope in TR33.824 |
pCR revision of S3-210284 |
Huawei, HiSilicon | 33.824 0.7.0 | FS_NR_IAB_Sec | Rel-17 |
S3-102-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-210667 | New solution for traffic protection in service layer |
pCR revision of S3-210288 |
Huawei, HiSilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210668 | Add evaluation to solution 1 |
pCR revision of S3-210291 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210669 | Add evaluation to solution 3 |
pCR revision of S3-210292 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.851 0.3.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210670 | Draft TR 33.850 |
draft TR revision of S3-210640 |
Huawei, Hisilicon | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] | |
| S3-210671 | Draft TR 33.867 | draft TR | Huawei,Hisilicon | FS_UC3S | Rel-17 |
S3-102-e AI: 5.14 |
approved | [WTS] [JSN] | |
| S3-210672 | Addressing the EN on solution2 |
pCR revision of S3-210287 |
Huawei, HiSilicon | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210673 | draft TR 33.862 0.3.0 | draft TR | china mobile | FS_SEC_5GMSG | Rel-17 |
S3-102-e AI: 5.15 |
approved | [WTS] [JSN] | |
| S3-210674 | pCR to TR33.847- New solution on L3 UE-to-Network Relay |
pCR revision of S3-210281 |
CATT | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210675 | pCR to TR33.847- New solution on UE-to-Network Relay based on primary authentication |
pCR revision of S3-210296 |
CATT | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210676 | Draft TR 33.847 v0.4.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] | |
| S3-210677 | Remove the EN in solution #5 |
pCR revision of S3-210183 |
CATT | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210678 | Remove EN in Solution #6 in TR 33.839 |
pCR revision of S3-210185 |
CATT | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210679 | Key issue on security of data via Messaging Framework |
pCR revision of S3-210498 |
Ericsson, CATT | 33.866 0.2.0 | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-210680 | Address Editor's Note in solution 14 |
pCR revision of S3-210261 |
Huawei Technologies (Korea) | 33.847 0.3.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-210681 | draft TR 33.866 0.3.0 | draft TR | china mobile | FS_eNA_SEC | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] | |
| S3-210682 | Evaluation of Solution #7 |
pCR revision of S3-210505 |
Lenovo, Motorola Mobility | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210683 | Resolving EN in Clause 4.3 Architecture and Security Assumptions |
pCR revision of S3-210531 |
Lenovo, Motorola Mobility | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
approved | [WTS] [JSN] |
| S3-210684 | Update to Solution#4 on enabling security during AMF reallocation via RAN |
pCR revision of S3-210533 |
Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
approved | [WTS] [JSN] |
| S3-210685 | Solution to ensure system availability for indirect AMF reallocation |
pCR revision of S3-210534 |
Lenovo, Motorola Mobility | 33.864 0.2.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e AI: 5.17 |
approved | [WTS] [JSN] |
| S3-210686 | Updates to Key Issue #7 |
pCR revision of S3-210535 |
Lenovo, Motorola Mobility, Interdigital, Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210687 | Update to Solution #7 |
pCR revision of S3-210537 |
Lenovo, Motorola Mobility | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210688 | Solution on UAV and UAV-C Pairing Authorization |
pCR revision of S3-210538 |
Lenovo, Motorola Mobility | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] |
| S3-210689 | Reply-LS on user consent requirements for analytics |
LS out LS is reply to S3-210012 source LS: S2-2009383 LS To: SA2 |
NTT DOCOMO INC. | Rel-17 |
S3-102-e AI: 5.16 |
approved | [WTS] [JSN] | ||
| S3-210690 | Addition to support key update in Solution 1 |
pCR revision of S3-210463 |
Philips International B.V. | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210691 | MEC-Evaluation on solution#1 | pCR | Apple | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
| S3-210692 | MEC-Modification on solution#22 |
pCR revision of S3-210217 |
Apple | 33.839 0.3.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e AI: 5.8 |
approved | [WTS] [JSN] |
| S3-210693 | MBS-Modification on solution#1 |
pCR revision of S3-210215 |
Apple | 33.85 0.3.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e AI: 5.11 |
approved | [WTS] [JSN] |
| S3-210694 | MUSIM-key issue on BUSY indication |
pCR revision of S3-210213 |
Apple | 33.873 0.0.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-210695 | TR 33.854 v0.4.0 |
draft TR revision of S3-203467 |
Qualcomm Incoporated | FS_UAS_SEC | Rel-17 |
S3-102-e AI: 5.7 |
approved | [WTS] [JSN] | |
| S3-210696 | IAB draft TR 33.824 v 0.8.0 | draft TR | Samsung | FS_NR_IAB_Sec | Rel-17 |
S3-102-e AI: 5.18 |
approved | [WTS] [JSN] | |
| S3-210697 | TR 33875-010 FS_eSBA_SEC | draft TR | Nokia, Nokia Shanghai Bell | FS_eSBA_SEC | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-210698 | TR_33.851-040_IIoT_Sec | draft TR | Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] | |
| S3-210699 | LS on authorization for Indirect Communication and Delegated Discovery |
LS out LS To: SA2 |
Huawei, HiSilicon | Rel-16 |
S3-102-e AI: 4.4 |
noted | [WTS] [JSN] | ||
| S3-210700 | pCR to UP IP draft CR to TS 33.501 |
other revision of S3-210491 |
Qualcomm Incorporated, Huawei, HiSilicon |
S3-102-e AI: 4.2 |
approved | [WTS] [JSN] | |||
| S3-210701 | Extend UPIP support in 5GS for all 5GC connected RAN architecture (NG-RAN) options |
draftCR revision of S3-210490 |
Qualcomm Incorporated | eUPIP_SEC | Rel-17 |
S3-102-e AI: 4.2 |
approved | [WTS] [JSN] | |
| S3-210702 | Extend UPIP support in 5GS for all 5GC connected RAN architecture (NG-RAN) options | CR | Qualcomm Incorporated | 33.501 17.0.0 | eUPIP_SEC | Rel-17 |
S3-102-e AI: 4.2 |
withdrawn | [WTS] [JSN] |
| S3-210703 | Extend UPIP support in 5GS for all 5GC connected RAN architecture (NG-RAN) options | CR | Qualcomm Incorporated | 33.501 17.0.0 CR#1073 catB | eUPIP_SEC | Rel-17 |
S3-102-e AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-210704 | Adding details to provisioning key issue |
pCR revision of S3-210402 |
Ericsson, China Mobile, Huawei, InterDigital, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Philips, Samsung, ZTE | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210705 | TS 33.536 - overall clean-up |
CR revision of S3-210066 |
LG Electronics Inc. | 33.536 16.2.0 CR#221 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210706 | LS on Reply LS on Storage of KAUSF from CT1 |
LS out LS is reply to S3-210005 source LS: C1-207764 LS To: CT1, CT4 LS reply in C1-210737, C1-211338, C1-211516, C1-211518 revision of S3-210459 |
Samsung | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
approved | [WTS] [JSN] | |
| S3-210707 | CR for correction in SEAL |
CR revision of S3-210451 |
Samsung | 33.434 16.1.0 CR#31 catF | SEAL | Rel-16 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210708 | Conclusions for TR 33.845 |
pCR revision of S3-210464 |
Ericsson | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210709 | New Solution: Protection of SQN during storage in UDR |
pCR revision of S3-210040 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210710 | New solution for KI#9 | pCR | NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
withdrawn | [WTS] [JSN] |
| S3-210711 | New Solution: Protection of TUAK TOPc value during storage in UDR | pCR | KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
withdrawn | [WTS] [JSN] |
| S3-210712 | New Solution: Protection of TUAK TOPc value during storage in UDR |
pCR revision of S3-210042 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210713 | New Solution: Protection of TUAK TOPc value during transfer out of UDR |
pCR revision of S3-210043 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210714 | Updated Solution #8: Encrypted transfer of OPc between UDR and UDM/ARPF |
pCR revision of S3-210044 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210715 | New solution for KI#9 |
pCR revision of S3-210083 |
NCSC | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210716 | Updated Solution #9: Encrypted transfer of OP between UDR and UDM/ARPF |
pCR revision of S3-210045 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210717 | Updated Solution #10: Encrypted strorage of OPc in UDR |
pCR revision of S3-210046 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210718 | Updated Solution #11: Encrypted storage of OP in UDR |
pCR revision of S3-210047 |
KPN N.V. | 33.845 0.6.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] |
| S3-210719 | Process and agenda presentation for SA3#102e | other | WG chair |
S3-102-e AI: 1 |
noted | [WTS] [JSN] | |||
| S3-210720 | Cover sheet for TR 33.845 - presentation for information | TS or TR cover | VODAFONE Group Plc | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] | |
| S3-210721 | TR 33.845 v0.7.0 | draft TR | VODAFONE Group Plc | FS_5GC_SEC_ARPF | Rel-17 |
S3-102-e AI: 5.6 |
approved | [WTS] [JSN] | |
| S3-210722 | New WID on normative changes for User Plane Integrity Protection for LTE options |
WID new revision of S3-210544 |
VODAFONE Group Plc | Rel-17 |
S3-102-e AI: 4.22 |
agreed | [WTS] [JSN] | ||
| S3-210723 | Resolving editor's note on encryption policy mismatch between SEPPs |
CR revision of S3-210074 |
NTT Docomo, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#9023 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210724 | Resolving editor's note on encryption policy mismatch between SEPPs |
CR revision of S3-210075 |
NTT Docomo, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#10191 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210725 | NF Service Consumer and Producer in Service Request Process |
CR revision of S3-210096 |
Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#10201 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210726 | NF Service Consumer and Producer in Service Request Process |
CR revision of S3-210098 |
Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#10221 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210727 | Access Token Misuse Prevention |
CR revision of S3-210097 |
Nokia, Nokia Shanghai Bell, CableLabs, Mavenir | 33.501 16.5.0 CR#10211 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210728 | Access Token Misuse Prevention |
CR revision of S3-210099 |
Nokia, Nokia Shanghai Bell, CableLabs, Mavenir | 33.501 17.0.0 CR#10231 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210729 | SCAS Protection Policies - TBD updated |
CR revision of S3-210100 |
Nokia, Nokia Shanghai Bell | 33.517 16.1.0 CR#51 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-210730 | Protection policies test case |
CR revision of S3-210101 |
Nokia, Nokia Shanghai Bell, NTT Docomo, Huawei, HiSilicon | 33.517 16.1.0 CR#61 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-210731 | KI on linkability by SUCI |
pCR revision of S3-210329 |
Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210732 | Editorial changes to TR |
pCR revision of S3-210335 |
Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210733 | SQNms protection by concealment in ME |
pCR revision of S3-210336 |
Nokia, Nokia Shanghai Bell | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210734 | TR 33.848 v0.6.0 | draft TR | BT plc | FS_SIV | Rel-16 |
S3-102-e AI: 5.4 |
approved | [WTS] [JSN] | |
| S3-210735 | Correction to the access token storage in NF service consumer |
CR revision of S3-210239 |
Huawei, HiSilicon | 33.501 16.5.0 CR#10341 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210736 | Correction to the access token storage in NF service consumer |
CR revision of S3-210240 |
Huawei, HiSilicon | 33.501 17.0.0 CR#10351 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210737 | Clarification on key derivation |
CR revision of S3-210250 |
Huawei, HiSilicon | 33.536 16.2.0 CR#241 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210738 | Reply LS about the layer to provide security |
LS out LS is reply to S3-210027 LS To: RAN2, CT1 revision of S3-210251 |
Huawei, HiSilicon | Rel-16 |
S3-102-e AI: 4.1 |
approved | [WTS] [JSN] | ||
| S3-210739 | Clarification on A-KID generation |
CR revision of S3-210253 |
Huawei, HiSilicon | 33.535 17.0.0 CR#621 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
agreed | [WTS] [JSN] |
| S3-210740 | Living document for TS 33.512 |
draftCR revision of S3-210264 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210741 | Living document for TR 33.926 |
draftCR revision of S3-210268 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-102-e AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-210742 | new solution to mitigate supi guessing and suci replay attack |
pCR revision of S3-210282 |
Huawei, HiSilicon | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210743 | Clarification on security protection in AMF reallocation(direct NAS reroute) |
CR revision of S3-210294 |
Huawei, HiSilicon | 33.501 16.5.0 CR#10401 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210744 | Draft 33.326 | draft TS | Huawei, HiSilicon | SCAS_5G_NSSAAF | Rel-17 |
S3-102-e AI: 4.18 |
approved | [WTS] [JSN] | |
| S3-210745 | Clarification on confidential IEs replacement handling in original N32-f message |
CR revision of S3-210378 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.517 16.1.0 CR#71 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-210746 | Clarification on exposure of confidential IEs in N32-f message in TR 33.926 |
CR revision of S3-210379 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.926 16.3.0 CR#391 catF | SCAS_5G | Rel-17 |
S3-102-e AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-210747 | Resolving the EN on the authorization between SCPs |
CR revision of S3-210381 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#10451 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210748 | Align the JSON format on encryption IE with CT4 in Rel15 |
CR revision of S3-210382 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#10461 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210749 | Mirror: align the JSON format on encryption IE with CT4 in Rel16 |
CR revision of S3-210383 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#10471 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210750 | Mirror: align the JSON format on encryption IE with CT4 in Rel17 |
CR revision of S3-210384 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#10481 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210751 | Mirror Adding the security requirement with encBlockIndex in Rel16 |
CR revision of S3-210386 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#10501 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210752 | Mirror Adding the security requirement with encBlockIndex in Rel17 |
CR revision of S3-210387 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#10511 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210753 | IMS SCAS: living doc for the threats | draftCR | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
withdrawn | [WTS] [JSN] | |
| S3-210754 | Draft TS 33.226 0.4.0 | draft TS | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210755 | SCAS IPUPS: Add a new test |
draftCR revision of S3-210360 |
Huawei, Hisilicon,ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-102-e AI: 4.17 |
approved | [WTS] [JSN] | |
| S3-210756 | Reply LS on FBS detection |
LS out LS is reply to S3-210018 source LS: S3-210018 LS To: RAN2 revision of S3-210194 |
Huawei, HiSilicon | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] | ||
| S3-210757 | R17 SID on enhanced security for Phase 2 network slicing |
SID new revision of S3-210539 |
Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT, China Unicom, China Mobile, InterDigital, NEC, Telecom Italia | Rel-17 |
S3-102-e AI: 5.21 |
agreed | [WTS] [JSN] | ||
| S3-210758 | Draft TR 33.846 v0.10.0 Study on authentication enhancements in the 5G System (5GS) | draft TR | Ericsson Japan K.K. | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] | |
| S3-210759 | 5G GUTI re-allocation |
CR revision of S3-210480 |
Qualcomm Incorporated, Huawei, Hisilicon | 33.501 16.5.0 CR#10621 catF | 5G_CIoT | Rel-16 |
S3-102-e AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-210760 | AAnF checks AKMA service for UE and AF in clause 6.3 |
CR revision of S3-210151 |
ZTE Corporation | 33.535 17.0.0 CR#551 catB | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
agreed | [WTS] [JSN] |
| S3-210761 | AAnF selection in AF |
CR revision of S3-210152 |
ZTE Corporation | 33.535 17.0.0 CR#561 catB | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
agreed | [WTS] [JSN] |
| S3-210762 | Add Application Key Get service in clause 7.1 |
CR revision of S3-210153 |
ZTE Corporation | 33.535 17.0.0 CR#571 catB | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
agreed | [WTS] [JSN] |
| S3-210763 | the KAF lifetime expiration in clause 5.2 |
CR revision of S3-210156 |
ZTE Corporation | 33.535 17.0.0 CR#601 catF | AKMA | Rel-17 |
S3-102-e AI: 4.5 |
agreed | [WTS] [JSN] |
| S3-210764 | Update the clause 5.2.5.5.7 |
pCR revision of S3-210160 |
ZTE Corporation, China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210765 | Adding a new threat related with biding down attack in the threats | draftCR | China Telecom, Huawei, HiSilicon | SCAS_IMS | Rel-16 |
S3-102-e AI: 4.12 |
withdrawn | [WTS] [JSN] | |
| S3-210766 | New solution for key issue# 4.1 in TR 33.846 |
pCR revision of S3-210162 |
ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210767 | Update solution#2.1 in TR 33.846 |
pCR revision of S3-210164 |
ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210768 | Adding a new threat related with biding down attack in the threats | draftCR | China Telecom, Huawei, HiSilicon | SCAS_IMS | Rel-16 |
S3-102-e AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-210769 | Solution of Mitigation against the SUPI replay attack |
pCR revision of S3-210163 |
ZTE Corporation | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210770 | Clarifying the scope |
pCR revision of S3-210303 |
China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210771 | Clarifying for types of virtualised network product class |
pCR revision of S3-210304 |
China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210772 | Clarifying for Generic assets and threats for GVNP of type 1 |
pCR revision of S3-210306 |
China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210773 | clarifying the content in clause 5.2.5.6.6.1 and clause 5.2.5.6.7 |
pCR revision of S3-210310 |
China Mobile | 33.818 0.9.2 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-210774 | TR 33.818 v0.a.0 | draft TR | China Mobile Com. Corporation | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-210775 | living document to TR 33.926 for NWDAF SCAS |
draftCR revised to S3-211842 |
China Mobile Com. Corporation | SCAS_5G_NWDAF | Rel-17 |
S3-102-e AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-210776 | TS 33.521 v0.3.0 | draft TS | China Mobile Com. Corporation | SCAS_5G_NWDAF | Rel-17 |
S3-102-e AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-210777 | TS 33.520 Security Assurance Specification for Non-3GPP InterWorking Function | draft TS | China Unicom | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
approved | [WTS] [JSN] | |
| S3-210778 | draft TR of TR 33.809-5GFBS | draft TR | Apple | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] | |
| S3-210779 | TR 33.846: comparison of candidate solutions |
pCR revision of S3-210517 |
THALES | 33.846 0.9.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e AI: 5.5 |
approved | [WTS] [JSN] |
| S3-210780 | draft TR 33.857 v0.4.0 | draft TR | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-210781 | New WID on 3GPP profiles for cryptographic algorithms and security protocols |
WID new revision of S3-210499 |
Ericsson | Rel-17 |
S3-102-e AI: 4.22 |
agreed | [WTS] [JSN] | ||
| S3-210782 | Correcting notation used for inter-AMF mobility key derivation |
CR revision of S3-210415 |
MediaTek Inc. | 33.501 16.5.0 CR#9632 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210783 | Clarifications on Cryptographic CRC in MAC to avoid MitM relay nodes |
pCR revision of S3-210131 |
Philips International B.V. | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210784 | Clarifications in Solution #24 |
pCR revision of S3-210132 |
Philips International B.V., CableLabs, Nokia, Nokia Shanghai Bell | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e AI: 5.1 |
approved | [WTS] [JSN] |
| S3-210785 | Correcting notation used for inter-AMF mobility key derivation | CR | MediaTek Inc. / Marko | 33.501 17.0.0 CR#1074 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210786 | Correct NAS uplink COUNT for KgNB/KeNB derivation | CR | MediaTek Inc. / Marko | 33.501 17.0.0 CR#1075 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210787 | Correct current uplink EPS NAS COUNT used at derivation of a mapped 5G security context |
CR revision of S3-210326 |
MediaTek Inc. / Marko | 33.501 16.5.0 CR#10411 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210788 | Correct current uplink EPS NAS COUNT used at derivation of a mapped 5G security context | CR | MediaTek Inc. / Marko | 33.501 17.0.0 CR#1076 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210789 | 5G GUTI re-allocation | CR | Qualcomm Incorporated | 33.501 17.0.0 CR#1077 catA | 5G_CIoT | Rel-17 |
S3-102-e AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-210790 | 5G CIoT K_NG-RAN derivation | CR | Qualcomm Incorporated | 33.501 17.0.0 CR#1078 catA | 5G_CIoT | Rel-17 |
S3-102-e AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-210791 | Reply-LS on Support of L2TP on SGi/N6 with Control and User Plane Separation |
LS out LS is reply to S3-210024 LS To: CT4 |
Ericsson | BEPoP | Rel-17 |
S3-102-e AI: 3 |
approved | [WTS] [JSN] | |
| S3-210792 | Resolving editor's note on encryption policy mismatch between SEPPs |
CR revision of S3-210545 |
NTT DOCOMO INC., Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#10651 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210793 | Correction to service request process in OAuth 2.0 based authorization rel16 |
CR revision of S3-210241 revised to S3-210798 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#10361 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210794 | Correction to service request process in OAuth 2.0 based authorization rel17 |
CR revision of S3-210242 revised to S3-210797 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#10371 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.4 |
revised | [WTS] [JSN] |
| S3-210795 | gNB Cipher Security Policy Verification |
CR revision of S3-210090 |
Futurewei | 33.511 16.5.0 CR#191 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-210796 | gNB Integrity Security Policy Verification |
CR revision of S3-210091 |
Futurewei | 33.511 16.5.0 CR#201 catF | SCAS_5G | Rel-16 |
S3-102-e AI: 4.2 |
agreed | [WTS] [JSN] |
| S3-210797 | Correction to service request process in OAuth 2.0 based authorization rel17 |
CR revision of S3-210794 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#10372 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210798 | Correction to service request process in OAuth 2.0 based authorization rel16 |
CR revision of S3-210793 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#10362 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-210799 | Mirror_Clarification on security protection in AMF reallocation | CR | Huawei, HiSilicon | 33.501 17.0.0 CR#1079 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.23 |
agreed | [WTS] [JSN] |
| S3-210800 | Reply-LS on security issue for on-boarding and remote provisioning. |
LS out LS is reply to S3-210009 LS To: SA2 revision of S3-210137 |
Nokia, Nokia Shanghai Bell | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-210801 | Solution for protecting the privacy of the UE identity. |
pCR revision of S3-210136 |
Nokia, Nokia Shanghai Bell | 33.857 0.3.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e AI: 5.12 |
approved | [WTS] [JSN] |
| S3-210802 | Check whether the N3IWF sends the EAP-Identity Request message |
pCR revision of S3-210222 |
China Unicom | 33.52 0.1.0 | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
approved | [WTS] [JSN] |
| S3-210803 | Threat to send EAP-Identity Request by N3IWF | CR | China Unicom | 33.926 16.3.0 CR#40 catB | SCAS-SA3 | Rel-17 |
S3-102-e AI: 4.16 |
withdrawn | [WTS] [JSN] |
| S3-210804 | Clarifications regarding Authentication procedure for V2X PC5 unicast link |
CR revision of S3-210135 |
Nokia, Nokia Shanghai Bell | 33.536 16.2.0 CR#231 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
| S3-210805 | Threat to send EAP-Identity Request by N3IWF |
CR revision of S3-210221 |
China Unicom | 33.926 16.3.0 CR#371 catB | SCAS_5G_N3IWF | Rel-17 |
S3-102-e AI: 4.16 |
agreed | [WTS] [JSN] |
| S3-210810 | Agenda | agenda | WG Chair |
S3-102-e-Bis AI: 1 |
approved | [WTS] [JSN] | |||
| S3-210811 | E-meeting procedures | other | WG Chair |
S3-102-e-Bis AI: 1 |
noted | [WTS] [JSN] | |||
| S3-210812 | LS on Identification of source PLMN-ID in SBA |
LS in LS reply in S3-211204, S3-210822, S3-211204 |
C4-210249 |
S3-102-e-Bis AI: 2.2 |
replied to | [WTS] [JSN] | |||
| S3-210813 | Reply LS on the user consent for trace reporting |
LS in LS reply in S3-211338, S3-211338 |
R2-2010894 |
S3-102-e-Bis AI: 2.14 |
replied to | [WTS] [JSN] | |||
| S3-210814 | Reply LS on 5MBS progress and issues to address |
LS in LS reply in S3-211313, S3-211313 |
R2-2102480 |
S3-102-e-Bis AI: 2.11 |
replied to | [WTS] [JSN] | |||
| S3-210815 | LS on using MOBIKE in Integrated Access and Backhaul system | LS in | R3-211297 |
S3-102-e-Bis AI: 2.18 |
postponed | [WTS] [JSN] | |||
| S3-210816 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-211059 |
S2-2009339 |
S3-102-e-Bis AI: 2.8 |
postponed | [WTS] [JSN] | |||
| S3-210817 | LS on propagation of user consent related information during Xn inter-PLMN handover |
LS in LS reply in S3-211330, S3-211330 |
R3-204378 |
S3-102-e-Bis AI: 2.14 |
replied to | [WTS] [JSN] | |||
| S3-210818 | Reply to LS on Resynchronisations | LS in | ETSI SAGE |
S3-102-e-Bis AI: 2.5 |
postponed | [WTS] [JSN] | |||
| S3-210819 | LS on Security Requirements for Sidelink/PC5 Relays | LS in | S2-2004750 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |||
| S3-210820 | New Solution for privacy with Layer-2 based UE-to-UE Relay and Adaptation Layer | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-210821 | Privacy considerations for Adaptation Layer and Layer-2 based UE-to-UE Relay | discussion | InterDigital, Inc. |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |||
| S3-210822 | Reply-LS on Identification of source PLMN-ID in SBA |
LS out LS is reply to S3-210812 LS To: CT4 revised to S3-211204 |
Ericsson |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] | |||
| S3-210823 | DRAFT LS on Layer-2 based UE-to-UE Relay utilizing Adaptation Layer |
LS out LS To: RAN2, SA2 |
InterDigital, Inc. | FS_5G_ProSe | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |
| S3-210824 | Solution for privacy handling with Layer-3 based UE-to-UE Relay | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-210825 | TR 33.847 Update for solution #10 |
pCR revised to S3-211240 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210826 | TR 33.847 Update for solution #24 |
pCR revised to S3-211242 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210827 | TR 33.847 Update for solution #25 | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-210828 | Updated Solution #22: Representation of identities during broadcast |
pCR revised to S3-211179 |
KPN N.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210829 | Administration of the virtualisation fabric |
pCR revised to S3-211340 |
NCSC | 33.848 0.6.0 | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
revised | [WTS] [JSN] |
| S3-210830 | Updated Solution #23: Initial key with validity time |
pCR revised to S3-211185 |
KPN N.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210831 | TR 33.854 Solution#3 evaluation |
pCR revised to S3-211251 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-210832 | TR 33.854 Solution#5 evaluation |
pCR revised to S3-211252 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-210833 | TR 33.854 Solution#12 evaluation |
pCR revised to S3-211254 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-210834 | TR 33.854 Update for KI#4 |
pCR revised to S3-211255 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-210835 | TR 33.854 Update for KI#6 |
pCR revised to S3-211256 |
InterDigital, Europe, Ltd., Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-210836 | TR 33.854 Conclusion for KI#4 | pCR | InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
noted | [WTS] [JSN] |
| S3-210837 | TR 33.854 Conclusion for KI#1 | pCR | InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
noted | [WTS] [JSN] |
| S3-210838 | TR 33.854 Conclusion for KI#2 | pCR | InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
noted | [WTS] [JSN] |
| S3-210839 | Update on Ki#27 Image Snapshot and VNF Mobility. |
pCR revised to S3-211341 |
Nokia, Nokia Shanghai Bell | 33.848 0.6.0 | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
revised | [WTS] [JSN] |
| S3-210840 | Resolving UE ID privacy and format EN in solution 16 |
pCR revised to S3-211187 |
Alibaba Group | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-210841 | Editor note removal on SQNms protection by concealment with SUPI with f5 |
pCR revised to S3-211181 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210842 | Update to mapping table | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-210843 | Assuring SUCI generation by legitimiate SUPI owner using KSUCI |
pCR revised to S3-211182 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210844 | Update to Solution 4.5 AUTS SQNMS solution for 5GS to add a note | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-210845 | Evaluation of solution 2.3 Unified authentication response message by UE |
pCR revised to S3-211177 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210846 | Evaluation of solution 2.2 Encryption of authentication failure message types by UE with new keys derived from K_AUSF | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
noted | [WTS] [JSN] |
| S3-210847 | Evaluation of solution 2.4 MAC-S based solution |
pCR revised to S3-211178 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210848 | MAC, SYNCH failure cause concealment solution |
pCR revised to S3-211183 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210849 | Key issue risk assessment | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
noted | [WTS] [JSN] |
| S3-210850 | TR 33.847: Solution #18 | pCR | THALES | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-210851 | TR 33.846: update of solution #4.7 | pCR | THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
merged | [WTS] [JSN] |
| S3-210852 | TR 33.846: evaluation of solution #3.1 |
pCR revised to S3-211210 |
THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210853 | TR 33.846: impacts of solutions |
pCR revised to S3-211211 |
THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210854 | TR 33.846: conclusion for KI #4.1 | pCR | THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
noted | [WTS] [JSN] |
| S3-210855 | Discussion paper on GPSI translation to Temperary UE id | discussion | Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |||
| S3-210856 | Reply LS on GPSI translation for Edge AS |
LS out LS is reply to S2-2005923,S6-202008 LS To: SA6, SA2 |
Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.8 |
merged | [WTS] [JSN] | |||
| S3-210857 | Secure framewrok for MBS key distribution |
pCR revised to S3-211278 |
Nokia, Nokia Shanghai Bell | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-210858 | Direct UE connection to Slice AMF |
pCR revised to S3-211279 |
Nokia, Nokia Shanghai Bell | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-210859 | Discussion paper on LS on MOBIKE in IAB | discussion | Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.18 |
noted | [WTS] [JSN] | |||
| S3-210860 | draft reply LS on MOBIKE in IAB |
LS out LS is reply to R3-211297 LS To: RAN3 |
Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.18 |
noted | [WTS] [JSN] | |||
| S3-210861 | Key issue on Paging cause security | pCR | Nokia, Nokia Shanghai Bell, Samsung | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-210862 | Solution for secure BUSY indication | pCR | Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-210863 | Solution for secure paging cause | pCR | Nokia, Nokia Shanghai Bell | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-210864 | key issue on secure connection to RAN slice | other | Nokia, Nokia Shanghai Bell |
S3-102-e-Bis AI: 2.21 |
merged | [WTS] [JSN] | |||
| S3-210865 | EN resolution for KI#1 | pCR | LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-210866 | Update for Sol#13 |
pCR revised to S3-211174 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210867 | Evaluation for Sol#13 |
pCR revised to S3-211175 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210868 | Add evaluation to solution#5 |
pCR revised to S3-211268 |
CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210869 | Add evaluation to solution#6 |
pCR revised to S3-211269 |
CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210870 | Modification on solution #6 | pCR | CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-210871 | Remove EN in solution#5 | pCR | CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-210872 | Add new key issue for user consent in TR 33.867 |
pCR revised to S3-211267 |
CATT | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] |
| S3-210873 | Add use case mapping part for Key Issue #1 in TR 33.867 | pCR | CATT | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-210874 | ProSE Direct Discovery Clarification in Out-of-Coverage Scenarios | pCR | MITRE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-210875 | Update comparison table for solution 2.7 and 6.4 | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
merged | [WTS] [JSN] |
| S3-210876 | EN resolution on null scheme for solution 2.7 |
pCR revised to S3-211213 |
ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210877 | Text editing update on solution 2.7 | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
merged | [WTS] [JSN] |
| S3-210878 | Solution of mitigating the SUPI guessing attacks | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-210879 | Resolve the EN in Sol#4.6 | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-210880 | Update mapping table in clause 6.0 | pCR | ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-210881 | Resolving the EN of solution #7 | pCR | ZTE Corporation | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
| S3-210882 | Resolving the EN of solution #17 | pCR | ZTE Corporation | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
| S3-210883 | Conclusion for key issue 9 | pCR | ZTE Corporation | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
merged | [WTS] [JSN] |
| S3-210884 | Removing ENs of Solution #3 |
pCR revised to S3-211202 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210885 | Removing ENs of Solution #4 |
pCR revised to S3-211203 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210886 | Update Solution#8 |
pCR revised to S3-211188 |
ZTE Corporation | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-210887 | New solution on control plane based provisioning - PS to AUSF | pCR | ZTE Corporation | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210888 | New solution on control plane based provisioning - PS to UDM | pCR | ZTE Corporation | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210889 | Definition of Network Slicing Isolation | pCR | ZTE Corporation | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
| S3-210890 | New key issue on Network Slicing Isolation | pCR | ZTE Corporation | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
| S3-210891 | Update and add evaluation to Solution #7 in TR 33.847 |
pCR revised to S3-211295 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210892 | Address Editor's Note in Solution #27 |
pCR revised to S3-211296 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210893 | Address Editor's Note in Solution #28 |
pCR revised to S3-211297 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210894 | Update details and add evaluation to Solution #26 in TR 33.847 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-210895 | Propose to resolve EN in KI#16 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-210896 | New solution to prevent malicious revocation | pCR | Huawei, HiSilicon | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-210897 | new solution for PC5 one-to-one rekeying |
pCR revised to S3-211298 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210898 | New solution to provide consisitent PDU session security for C2 | pCR | Huawei, HiSilicon | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
noted | [WTS] [JSN] |
| S3-210899 | New Solution for Interworking from 5GS to EPS |
pCR revised to S3-211299 |
Huawei, HiSilicon | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
| S3-210900 | Conclusion for Key Issue #7 | pCR | Huawei, HiSilicon | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
noted | [WTS] [JSN] |
| S3-210901 | Discussion Paper on Source of User Consent | discussion | Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.14 |
noted | [WTS] [JSN] | ||
| S3-210902 | Add Text for Source of User Consent for eNA | pCR | Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-210903 | New Use Case for MEC | pCR | Huawei, HiSilicon, Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-210904 | Analysis for UC3S | pCR | Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-210905 | New Solution for UE Related Analytics of NWDAF |
pCR revised to S3-211300 |
Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] |
| S3-210906 | New Solution for Security for Provisioning of SNPN Credentials without Initial Credential | pCR | Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210907 | New Solution for Security for Provisioning of SNPN Credentials with initial credential | pCR | Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210908 | New Solution for Security for Provisioning of PNI-NPN Credentials with initial credential | pCR | Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210909 | Solution Update for Solution #5 |
pCR revised to S3-211301 |
Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-210910 | Solution Update for Solution #12 |
pCR revised to S3-211302 |
Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-210911 | Conclusion for Key Issue #1 | pCR | Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210912 | Solution Update for Solution #2 |
pCR revised to S3-211303 |
Huawei, HiSilicon | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-210913 | F1 interface security for IAB in NR-DC mode | pCR | Huawei, HiSilicon | 33.824 0.8.0 | FS_NR_IAB_Sec | Rel-17 |
S3-102-e-Bis AI: 2.18 |
noted | [WTS] [JSN] |
| S3-210914 | New solution to mitigate the SUPI guessing attack |
pCR revised to S3-211304 |
Huawei, HiSilicon | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210915 | Update for solution #3.1 |
pCR revised to S3-211305 |
Huawei, HiSilicon | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210916 | Conclusion on key issue 1 |
pCR revised to S3-211306 |
Huawei, HiSilicon | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-210917 | Conclusion on key issue 4 | pCR | Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-210918 | New solution to update the MBS keys |
pCR revised to S3-211307 |
Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-210919 | Resolving the Editor's Notes in solution 2 |
pCR revised to S3-211308 |
Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-210920 | Updating and resolving the Editor's Notes in solution 8 | pCR | Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-210921 | Update solution#11 to meet privacy requirement | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-210922 | Add evaluation to solution#11 |
pCR revised to S3-211309 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210923 | Address Editors Note in evaluation of solution #5 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
merged | [WTS] [JSN] |
| S3-210924 | Add conclusion to KI#10 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-210925 | Add evaluaition to solution#29 |
pCR revised to S3-211310 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210926 | Add evaluaition to solution#30 |
pCR revised to S3-211311 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210927 | A new solution to protect busy indication | pCR | Huawei, HiSilicon | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-210928 | A new Key issue on paging cause | pCR | Huawei, HiSilicon | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-210929 | Address the remaining ENs in solution 15 |
pCR revised to S3-211312 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210930 | Address Editor's Note in solution 11 | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-210931 | Address Editor's Note in solution 8 | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-210932 | Evaluation of solution #14 | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-210933 | Add evaluation to solution 1 |
pCR revised to S3-211270 |
CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-210934 | Add evaluation to solution 2 |
pCR revised to S3-211271 |
CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-210935 | Add evaluation to solution 8 | pCR | CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-210936 | Scope of SECAM SCAS | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210937 | Scope of VNP evaluation | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210938 | SECAM Assurance Level | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210939 | SECAM Vendor Role | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210940 | VNP SCAS Instantiation |
pCR revised to S3-211257 |
Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-210941 | GVNP Type 2 hardening unnecessary service or protocol | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210942 | GVNP Type 2 hardening unsupported component | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210943 | GVNP Tyype 2 hardening unused function | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210944 | GVNP Type 2 hardening unused software | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210945 | Operational Environmental Security Assumptions | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-210946 | Monitoring | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210947 | Dispute Resolution | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210948 | Operator Acceptance Aspect | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210949 | Discussion on GVNP Type 1 assets protection | discussion | Futurewei Technologies | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] | ||
| S3-210950 | GVNP Type 1 assets protection | pCR | Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210951 | More clarification on scope | pCR | Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
noted | [WTS] [JSN] |
| S3-210952 | New Solution for Authentication and Authorization between EEC and ECS/EES |
pCR revised to S3-211326 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210953 | Editor notes removal |
pCR revised to S3-211314 |
Huawei, Hisilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-210954 | Conclusions on KI#5 Roaming-related security mechanisms for SNPNs | pCR | Huawei, Hisilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210955 | Evaluation of solution#9 |
pCR revised to S3-211327 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210956 | NPN: New solution to key issue #1 | pCR | Huawei, Hisilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210957 | AMFReal: Evaluation to solution #1 |
pCR revised to S3-211315 |
Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-210958 | AMFReal: Evaluation to solution #2 | pCR | Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
merged | [WTS] [JSN] |
| S3-210959 | AMFReal: Updates to solution #3 |
pCR revised to S3-211316 |
Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-210960 | AMFReal: Evaluation to solution #4 | pCR | Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
merged | [WTS] [JSN] |
| S3-210961 | AMFReal: Evaluation to solution #5 | pCR | Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-210962 | AMFReal: Evaluation to solution #6 | pCR | Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
merged | [WTS] [JSN] |
| S3-210963 | MBS: Updates to solution #4 | pCR | Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-210964 | MBS: Evaluation to solution #4 |
pCR revised to S3-211317 |
Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-210965 | MBS: Conclusion to key issue #1 | pCR | Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
noted | [WTS] [JSN] |
| S3-210966 | Requirement of subscribe-notification key issue | pCR | Huawei, Hisilicon | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210967 | Solution for non-delegated subscribe-notification key issue | pCR | Huawei, Hisilicon | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210968 | Update on Key issue #1 | pCR | Huawei, Hisilicon | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-210969 | EC: Conclusion for KI #9 |
pCR revised to S3-211318 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210970 | EC: Update Solution #13 to include CP option | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-210971 | EC: Discussion for the authorization during EDN relocation | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
| S3-210972 | EC: Update of solution #22 |
pCR revised to S3-211319 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210973 | EC: New solution for the authorization during EDN relocation |
pCR revised to S3-211320 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210974 | EC: Conclusion for Key issue #5 | pCR | Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
| S3-210975 | MitM FBS Detection |
pCR revised to S3-211261 |
Huawei, HiSilicon, Philips | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-210976 | add evaluation to solution 1 |
pCR revised to S3-211262 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-210977 | add evaluation to solution 11 |
pCR revised to S3-211263 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-210978 | Proposal for conclusion for Key Issue 1,2,4,6 | pCR | Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
| S3-210979 | Updates to solution 4 |
pCR revised to S3-211281 |
Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210980 | Updates to solution 12 |
pCR revised to S3-211282 |
Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-210981 | Key issue on security aspects of Paging Cause | pCR | Intel Deutschland GmbH | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-210982 | Conclusion to Key issue 1 | pCR | Intel Deutschland GmbH | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-210983 | Updates to solution 1 |
pCR revised to S3-211280 |
Intel Deutschland GmbH | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
revised | [WTS] [JSN] |
| S3-210984 | Updates to solution 14: Add detailed steps |
pCR revised to S3-211283 |
Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-210985 | Updates to solution 14: Removal of Editor’s notes and Evaluation | pCR | Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210986 | skeleton for eNS2 TR |
other revised to S3-211266 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
revised | [WTS] [JSN] | ||
| S3-210987 | Introduction for eNS2 TR | other | Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
noted | [WTS] [JSN] | ||
| S3-210988 | Scope of eNS2 study |
other revised to S3-211264 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
revised | [WTS] [JSN] | ||
| S3-210989 | New KI - slice authorization under UE quota constraint | other | Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
noted | [WTS] [JSN] | ||
| S3-210990 | New KI - privacy issue on broadcasting slice information |
other revised to S3-211265 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
revised | [WTS] [JSN] | ||
| S3-210991 | Proposal for conclusion for Key Issue 4 | pCR | Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
withdrawn | [WTS] [JSN] |
| S3-210992 | SUCI Linkability attack |
pCR revised to S3-211236 |
NEC | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-210993 | New Solution for User Consent for Exposure of information to Edge Applications in Real Time |
pCR revised to S3-211342 |
China Unicom | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] |
| S3-210994 | pCR to TR33.847- Update Solution#29 |
pCR revised to S3-211272 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210995 | pCR to TR33.847- Update Solution#30 |
pCR revised to S3-211273 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-210996 | Proposal for conclusion for Key Issue 4 | pCR | Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
withdrawn | [WTS] [JSN] |
| S3-210997 | Proposal for conclusion for Key Issue 4 -rev | pCR | Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-210998 | Draft CR 33.501 updates to TSC Annex L | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
withdrawn | [WTS] [JSN] |
| S3-210999 | Requirement and solution on multiple working domains |
pCR revised to S3-211226 |
Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211000 | KI4 update on NEF-AF |
pCR revised to S3-211228 |
Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211001 | Solution update on NEF-AF | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211002 | Annex on asmmetric delay attacks |
pCR revised to S3-211227 |
Nokia, Nokia Shanghai Bell, Deutsche Telekom | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211003 | Annex on Security considerations for integration with TSN | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211004 | Solution to KI#2 (Provisioning of credentials) using AKMA | pCR | Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211005 | Resolving CP provisioning EN in solution #10 | pCR | Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211006 | Add evaluation to Solution #10 "Secure initial access to an SNPN onboarding network" | pCR | Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211007 | Updates to solution#10 on PS address |
pCR revised to S3-211206 |
Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-211008 | Solution for privacy protection during initial access | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211009 | Solution for providing secure onboarding without client authentication |
pCR revised to S3-211244 |
Nokia, Nokia Shanghai Bell | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-211010 | Solution for KI#1.3 |
pCR revised to S3-211234 |
Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-211011 | Reply LS on propagation of user consent related information during Xn inter-PLMN handover |
LS out LS is reply to S3-210028 LS To: RAN3 revised to S3-211330 |
Ericsson France S.A.S | Rel-16 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] | ||
| S3-211012 | Solution for KI#1.4 | pCR | Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
merged | [WTS] [JSN] |
| S3-211013 | Clarifying the GVNP lifecycle in clause 5.2.5.5.7.1 | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211014 | Modifying test case in clause 5.2.5.5.7.2 | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211015 | Clarifying for the security requirements and test cases in clause 5.2.5.7.7.2 and 5.2.5.7.7.3 | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211016 | Adding vendor development and product lifecycle processes and test laboratory accreditation into Clause 6 | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211017 | proposal for way forward | pCR | China Mobile | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211018 | Update key issue #2.2 in TR 33.846 |
pCR revised to S3-211049 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-211019 | Solution to Key issue #2.2 in TR 33.846 |
pCR revised to S3-211050 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-211020 | Update key issue #3.2 in TR 33.846 |
pCR revised to S3-211026 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-211021 | Removal of solution without any KI | pCR | China Mobile | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
| S3-211022 | Update for KI#1.3 | pCR | Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
| S3-211023 | Resolution of Editor’s Notes in Solution#7 |
pCR revised to S3-211232 |
Lenovo, Motorola Mobility | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-211024 | A new onboarding solution addressing KI#2 | pCR | Lenovo, Motorola Mobility | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211025 | Update of Solution#6 |
pCR revised to S3-211233 |
Lenovo, Motorola Mobility | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-211026 | Update key issue #3.2 in TR 33.846 |
pCR revision of S3-211020 |
China Mobile, ZTE, Huawei | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211027 | 5GFBS-Adding evaluation for solution#4 | pCR | Apple | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
| S3-211028 | 5GFBS-Adding evaluation for solution#17 | pCR | Apple | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211029 | 5GFBS-Adding evaluation for solution#19 | pCR | Apple | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
| S3-211030 | 5GFBS-Conclusion for key issue#2 | pCR | Apple | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
| S3-211031 | MUSIM-Addressing the EN in solution#1 | pCR | Apple | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
| S3-211032 | ProSe-enhancement on discovery procedure | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211033 | ProSe-Security solution during reselection via UE-to-UE relay | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211034 | ProSe-Editorial in key issue#11 | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211035 | MEC-New key issue on EEC ID privacy protection | pCR | Apple | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
| S3-211036 | MEC-New solution for key issue#10 |
pCR revised to S3-211176 |
Apple | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-211037 | MEC-Modification on key issue#4 | pCR | Apple | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] |
| S3-211038 | Update of scope of TR | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211039 | KI on Ensuring restrictive transfer of ML models between authorized NWDAFs |
pCR revised to S3-211237 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-211040 | KI on UE data collection protection | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211041 | Solution on Privacy preservation of data |
pCR revised to S3-211238 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-211042 | Solution on Abnormal NF behaviour detection |
pCR revised to S3-211239 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-211043 | Update of KI on Security protection of data via Message Framework |
pCR revised to S3-211241 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-211044 | High-level conclusions to KI#4 "Securing initial access for UE onboarding between UE and SNPN" | pCR | Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211045 | New Key Issue: Roaming case for token-based authorization in indirect communication | pCR | Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211046 | New Solution to KI#4: Using existing procedures for authorization of SCP to act on behalf of an NF Consumer | pCR | Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211047 | New Solution to KI#5: End-to-end integrity protection of HTTP body and method |
pCR revised to S3-211205 |
Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211048 | Security policy consistency during UE-to-UE relay path switch | pCR | Apple Computer Trading Co. Ltd | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211049 | Update key issue #2.2 in TR 33.846 |
pCR revision of S3-211018 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211050 | Solution to Key issue #2.2 in TR 33.846 |
pCR revision of S3-211019 revised to S3-211324 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-211051 | Solution on Providing the Security protection of data via Messaging |
pCR revised to S3-211207 |
Ericsson | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-211052 | Update on KI on Authorization of consumers for data access via DCCF |
pCR revised to S3-211209 |
Ericsson | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-211053 | Adding the revocation functionality to solution #14 |
pCR revised to S3-211331 |
Qualcomm Incorporated | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-211054 | Adding the revocation functionality to solution #13 |
pCR revised to S3-211333 |
Qualcomm Incorporated | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-211055 | Addressing the ENs on ngKSI in solution #1 |
pCR revised to S3-211334 |
Qualcomm Incorporated | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211056 | Addressing the EN on determining whether there is an AMF re-allocation in solution #1 |
pCR revised to S3-211335 |
Qualcomm Incorporated | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211057 | Some proposed text for the assessment of attack risk table |
pCR revised to S3-211336 |
Qualcomm Incorporated | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-211058 | Discussion on the LS on providing UE identity based on IP address | discussion | Qualcomm Incorporated |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |||
| S3-211059 | Reply LS on IP address to GPSI translation |
LS out LS is reply to S3-210816 LS To: SA2 |
Qualcomm Incorporated |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |||
| S3-211060 | Using TLS with AKMA to protect EDGE-1 and EDGE-4 |
pCR revised to S3-211337 |
Qualcomm Incorporated | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-211061 | Discussion on the LS on the user consent for trace reporting | discussion | Qualcomm Incorporated |
S3-102-e-Bis AI: 2.14 |
noted | [WTS] [JSN] | |||
| S3-211062 | Reply LS on the user consent for trace reporting |
LS out LS is reply to R2-2010894 LS To: RAN2, SA5 revised to S3-211338 |
Qualcomm Incorporated |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] | |||
| S3-211063 | Authorization of remote UE in L3 U2N relay |
pCR revised to S3-211291 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211064 | New Key Issue on security policy handling for 5G Prose services |
pCR revision of S3-210482 |
Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211065 | EN resolution for solution #18 | pCR | Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211066 | EN resolution and evaluation for solution #20 |
pCR revised to S3-211292 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211067 | Update the evaluation for solution #3 |
pCR revised to S3-211289 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211068 | Update the evaluation for solution #4 |
pCR revised to S3-211290 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211069 | EN resolution of Solution #1 | pCR | Qualcomm Incorporated | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211070 | 5G MBS traffic protection at service-layer |
pCR revised to S3-211294 |
Qualcomm Incorporated | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-211071 | Conclusions for KI #2 | pCR | Qualcomm Incorporated | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
| S3-211072 | Evaluation on UE behavior on detection of false signature | pCR | Qualcomm Incorporated | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
| S3-211073 | Evaluation on signing key management | pCR | Qualcomm Incorporated | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
| S3-211074 | pCR: Further conclusions for KI #1 | pCR | Qualcomm Incorporated, CableLabs, Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211075 | pCR: Conclusions for KI #4 | pCR | Qualcomm Incorporated, CableLabs | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211076 | pCR: Addressing the EN in solution #4 |
pCR revised to S3-211259 |
Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-211077 | pCR: Addressing the SUPI privacy EN in solution #11 | pCR | Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211078 | pCR: Addressing the PS discovery EN in solution #11 |
pCR revised to S3-211260 |
Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
revised | [WTS] [JSN] |
| S3-211079 | IIOT: Resolve EN in solution #2 | pCR | Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211080 | IIOT: Update to KI#3 |
pCR revised to S3-211243 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211081 | IIOT: Conclusion on KI#4 |
pCR revised to S3-211246 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211082 | IIOT: Conclusion on KI#1 | pCR | Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
merged | [WTS] [JSN] |
| S3-211083 | KI on Processing user consent depending on the regulatory and regional demands | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
merged | [WTS] [JSN] |
| S3-211084 | KI on Modification or revocation of user consent | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
noted | [WTS] [JSN] |
| S3-211085 | KI on User consent for data collection | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
merged | [WTS] [JSN] |
| S3-211086 | Editorial updates to 33846-0100 |
pCR revised to S3-211184 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-211087 | ProSe: Update to solution #5 |
pCR revised to S3-211328 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211088 | ProSe: Retrieve Discovery keys for UE-to-network relays |
pCR revised to S3-211229 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211089 | ProSe: Update to solution #21 |
pCR revised to S3-211230 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211090 | ProSe: Update to solution #6 | pCR | Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
withdrawn | [WTS] [JSN] |
| S3-211091 | AMF reallocation: Update to solution #2 |
pCR revised to S3-211285 |
Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211092 | AMF re-allocation: Definition of isolation | pCR | Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
| S3-211093 | AMF re-allocation: New solution with reroute of Registration Request and protected security context via RAN |
pCR revised to S3-211286 |
Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211094 | AMF re-allocation: Notes from offline teleconference | discussion | Ericsson | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] | |
| S3-211095 | AMF re-allocation: Update of the assumptions | pCR | Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
| S3-211096 | MUSIM: Resolving the EN regarding SA2’s decision on Busy Indication |
pCR revised to S3-211275 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
revised | [WTS] [JSN] |
| S3-211097 | MUSIM: Updating the threat analysis in Key Issue #1 |
pCR revised to S3-211276 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
revised | [WTS] [JSN] |
| S3-211098 | MUSIM: Updating Key Issue #2 with Threats and Requirements | pCR | Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-211099 | MUSIM: Adding a New Key Issue on User Privacy | pCR | Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-211100 | MUSIM: Updating Solution #1 |
pCR revised to S3-211277 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
revised | [WTS] [JSN] |
| S3-211101 | ProSe: Updating Key Issue #1 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211102 | ProSe: Updating Key Issue #9 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211103 | ProSe: Updating Key Issue #12 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211104 | ProSe: Updating Key Issue #16 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211105 | ProSe: Adding a New Key Issue on Security Policies for PC5 Direct Link | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211106 | ProSe: Adding a New Key Issue on Security Policy with UE-to-Network Relay | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211107 | ProSe: Adding a New Key Issue on Security Policy with UE-to-UE Relay | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
| S3-211108 | Reply LS to LS on Security Requirements for Sidelink/PC5 Relays |
LS out LS To: SA2 |
Xiaomi Technology | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |
| S3-211109 | Solution for KI#2 using PKC without requiring tight time sync |
pCR revised to S3-211329 |
Philips International B.V. | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211110 | Secondary authentication for Session Breakout | discussion | Ericsson |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |||
| S3-211111 | [Draft] LS on Secondary authentication for Session Breakout |
LS out LS To: SA2 |
Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
noted | [WTS] [JSN] | |
| S3-211112 | IIoT: Update to solution #3 |
pCR revised to S3-211215 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211113 | IIoT: Update to and conclusion on KI #2 |
pCR revised to S3-211216 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211114 | EC: Update to solution #17 |
pCR revised to S3-211222 |
Ericsson | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
revised | [WTS] [JSN] |
| S3-211115 | UAS: Update to solution #2 |
pCR revised to S3-211212 |
Ericsson | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-211116 | Editorials Solution #24 | pCR | Philips International B.V. | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211117 | Update to Solution#4 |
pCR revised to S3-211245 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211118 | LS on end-to-end protection of HTTP message for Indirect communication |
LS out LS To: CT4 revised to S3-211231 |
CableLabs, Mavenir, Nokia, Nokia Bell Labs | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] | ||
| S3-211119 | Update to Solution#6 |
pCR revised to S3-211247 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211120 | Modification to address FFS about key update after re-authentication in Solution 2 | pCR | Philips International B.V. | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
merged | [WTS] [JSN] |
| S3-211121 | Solution to enable Reallocated AMF to serve the UE |
pCR revised to S3-211248 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211122 | Update to Solution#7 |
pCR revised to S3-211249 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-211123 | pCR: Conclusion for KI #1 on receiving KAUSF from AAA | pCR | CableLabs | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211124 | Resolving EN on UAVC Change |
pCR revised to S3-211250 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-211125 | Update to Solution#15 |
pCR revised to S3-211253 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
revised | [WTS] [JSN] |
| S3-211126 | pCR: Conclusion for KI #1 on addressing security threat against KAUSF | pCR | CableLabs | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
noted | [WTS] [JSN] |
| S3-211127 | Improve description of key update in Solution 2 by refering to Solution 9 | pCR | Philips International B.V. | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211128 | New annex of TR 33.809 – attack taxonomy for 5G UE over radio interfaces |
pCR revised to S3-211235 |
CableLabs, NTT Docomo, Philips, Deutsche Telekom AG | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
revised | [WTS] [JSN] |
| S3-211129 | [ProSe] Evaluation for solution#1 |
pCR revised to S3-211198 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211130 | [ProSe] Resolving ENs in solution#1 |
pCR revised to S3-211199 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211131 | Discussion for MitM attack | discussion | Samsung | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] | |
| S3-211132 | [5GFBS] Identifying MitM attack | pCR | Samsung | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
| S3-211133 | New key issue for Restricted Access in AMF re-allocation | pCR | Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
noted | [WTS] [JSN] |
| S3-211134 | Resolving ENs in Solution#1 |
pCR revised to S3-211200 |
Samsung | 33.862 0.3.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e-Bis AI: 2.15 |
revised | [WTS] [JSN] |
| S3-211135 | Solution on integrity protection of data transferred between AF and NWDAF |
pCR revised to S3-211201 |
Samsung | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
revised | [WTS] [JSN] |
| S3-211136 | Correction to clause 5A.1.1 in TR 33.867 | pCR | Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-211137 | Key Issue on user consent for UE data analytics using NWDAF | pCR | Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
merged | [WTS] [JSN] |
| S3-211138 | Update on scope of User Consent |
pCR revised to S3-211193 |
Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
revised | [WTS] [JSN] |
| S3-211139 | Solution on analytics for DoS attack detection | pCR | Samsung | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
| S3-211140 | Solution on analytics for MitM attack detection | pCR | Samsung | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
| S3-211141 | Removal of Editor’s Note (1 and 5) in Solution #5 |
pCR revised to S3-211194 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211142 | Resolution of Editor’s Notes and clarification on handling of Legacy UEs in Solution #5 |
pCR revised to S3-211195 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211143 | Removal of Editor’s Note (#4) in Solution #5 |
pCR revised to S3-211196 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
revised | [WTS] [JSN] |
| S3-211144 | [Solution] Key generation and distribution mechanism for MBS |
pCR revised to S3-211197 |
Samsung | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
revised | [WTS] [JSN] |
| S3-211145 | Key issue on User authorization for MUSIM optimizations | pCR | Samsung | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-211146 | Key Issue on home network authorization for MUSIM optimizations | pCR | Samsung | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
noted | [WTS] [JSN] |
| S3-211147 | TR 33.846: evaluation of solution #2.2 |
pCR revised to S3-211208 |
THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
revised | [WTS] [JSN] |
| S3-211148 | TR 33.846: conclusion for KI #2.1 | pCR | THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
noted | [WTS] [JSN] |
| S3-211149 | Resolving editor’s note in solution #32 |
pCR revised to S3-211258 |
Philips International B.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
| S3-211150 | Update on Solution #21: Interworking handover from EPS to 5GS |
pCR revised to S3-211189 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
| S3-211151 | Update on Solution #22: S1 handover |
pCR revised to S3-211190 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
| S3-211152 | Update on Solution #23: X2 handover | pCR | Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
| S3-211153 | Update on Solution #24: Interworking handover from 5GS to EPS |
pCR revised to S3-211191 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
| S3-211154 | pCR to 33.809 - addition of new key issue on false detections | pCR | VODAFONE Group Plc | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
noted | [WTS] [JSN] |
| S3-211155 | pCR to 33.809 - addition of solution to False positive detections | pCR | VODAFONE Group Plc | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
withdrawn | [WTS] [JSN] |
| S3-211156 | Rapporteurs update to 33.875 |
pCR revised to S3-211224 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211157 | Mapping of solutions to key issues |
pCR revised to S3-211225 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211158 | KI details added to NRF NF authentication in indirect communication |
pCR revised to S3-211170 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211159 | Service request authenticity verification in indirect communication |
pCR revised to S3-211223 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211160 | NF-SCP authorization |
pCR revised to S3-211220 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211161 | Service response verification in indirect communication |
pCR revised to S3-211217 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211162 | Authorization of multiple consumers within a NF set | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211163 | KI on Roaming with token based authorization in indirect communication | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211164 | Trust model | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211165 | NRF service management | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
noted | [WTS] [JSN] |
| S3-211166 | More details on SCP deployment models |
pCR revised to S3-211218 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211167 | Update of key issue #7 with X2 handover and S1 handover | pCR | Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
noted | [WTS] [JSN] |
| S3-211168 | New solution for source eNB pre-configured with neighbour target eNB’s support of UP IP |
pCR revised to S3-211192 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
revised | [WTS] [JSN] |
| S3-211169 | Use of criticality information | pCR | Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
| S3-211170 | KI details added to End-to-end integrity protection of HTTP messages |
pCR revision of S3-211158 revised to S3-211221 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
revised | [WTS] [JSN] |
| S3-211171 | Study item management and planning | other | WG Chair |
S3-102-e-Bis AI: 1 |
noted | [WTS] [JSN] | |||
| S3-211172 | Reply LS on IP address to GPSI translation | LS in | S2-2101307 |
S3-102-e-Bis AI: 2.8 |
postponed | [WTS] [JSN] | |||
| S3-211173 | Process and agenda presentation for SA3#102Bis-e | other | SA WG3 chair |
S3-102-e-Bis AI: 1 |
noted | [WTS] [JSN] | |||
| S3-211174 | Update for Sol#13 |
pCR revision of S3-210866 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211175 | Evaluation for Sol#13 |
pCR revision of S3-210867 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211176 | MEC-New solution for key issue#10 |
pCR revision of S3-211036 |
Apple | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211177 | Evaluation of solution 2.3 Unified authentication response message by UE |
pCR revision of S3-210845 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211178 | Evaluation of solution 2.4 MAC-S based solution |
pCR revision of S3-210847 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211179 | Updated Solution #22: Representation of identities during broadcast |
pCR revision of S3-210828 |
KPN N.V., MITRE | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211180 | TR 33.846: evaluation of solution #2.2 | pCR | THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
withdrawn | [WTS] [JSN] |
| S3-211181 | Editor note removal on SQNms protection by concealment with SUPI with f5 |
pCR revision of S3-210841 |
Nokia, Nokia Shanghai Bell, Thales | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211182 | Assuring SUCI generation by legitimiate SUPI owner using KSUCI |
pCR revision of S3-210843 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211183 | MAC, SYNCH failure cause concealment solution |
pCR revision of S3-210848 |
Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211184 | Editorial updates to 33846-0100 |
pCR revision of S3-211086 |
Nokia, Nokia Shanghai Bell,ZTE | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211185 | Updated Solution #23: Initial key with validity time |
pCR revision of S3-210830 |
TNO | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211186 | TR 33.853 v1.5.0 | draft TR | VODAFONE Group Plc | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] | |
| S3-211187 | Resolving UE ID privacy and format EN in solution 16 |
pCR revision of S3-210840 |
Alibaba Group | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211188 | Update Solution#8 |
pCR revision of S3-210886 |
ZTE Corporation | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211189 | Update on Solution #21: Interworking handover from EPS to 5GS |
pCR revision of S3-211150 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
| S3-211190 | Update on Solution #22: S1 handover |
pCR revision of S3-211151 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
| S3-211191 | Update on Solution #24: Interworking handover from 5GS to EPS |
pCR revision of S3-211153 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
| S3-211192 | New solution for source eNB pre-configured with neighbour target eNB’s support of UP IP |
pCR revision of S3-211168 |
Ericsson | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
| S3-211193 | Update on scope of User Consent |
pCR revision of S3-211138 |
Samsung | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-211194 | Removal of Editor’s Note (1 and 5) in Solution #5 |
pCR revision of S3-211141 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211195 | Resolution of Editor’s Notes and clarification on handling of Legacy UEs in Solution #5 |
pCR revision of S3-211142 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211196 | Removal of Editor’s Note (#4) in Solution #5 |
pCR revision of S3-211143 |
Samsung | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211197 | [Solution] Key generation and distribution mechanism for MBS |
pCR revision of S3-211144 |
Samsung | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211198 | [ProSe] Evaluation for solution#1 |
pCR revision of S3-211129 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211199 | [ProSe] Resolving ENs in solution#1 |
pCR revision of S3-211130 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211200 | Resolving ENs in Solution#1 |
pCR revision of S3-211134 |
Samsung | 33.862 0.3.0 | FS_SEC_5GMSG | Rel-17 |
S3-102-e-Bis AI: 2.15 |
approved | [WTS] [JSN] |
| S3-211201 | Solution on integrity protection of data transferred between AF and NWDAF |
pCR revision of S3-211135 |
Samsung | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211202 | Removing ENs of Solution #3 |
pCR revision of S3-210884 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211203 | Removing ENs of Solution #4 |
pCR revision of S3-210885 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211204 | Reply-LS on Identification of source PLMN-ID in SBA |
LS out LS is reply to S3-210812 LS To: CT4 revision of S3-210822 |
Ericsson |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] | |||
| S3-211205 | New Solution to KI#5: End-to-end integrity protection of HTTP body and method |
pCR revision of S3-211047 |
Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211206 | Updates to solution#10 on PS address |
pCR revision of S3-211007 |
Ericsson | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211207 | Solution on Providing the Security protection of data via Messaging |
pCR revision of S3-211051 |
Ericsson, Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211208 | TR 33.846: evaluation of solution #2.2 |
pCR revision of S3-211147 |
THALES, Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211209 | Update on KI on Authorization of consumers for data access via DCCF |
pCR revision of S3-211052 |
Ericsson, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211210 | TR 33.846: evaluation of solution #3.1 |
pCR revision of S3-210852 |
THALES | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211211 | TR 33.846: impacts of solutions |
pCR revision of S3-210853 |
THALES, ZTE | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211212 | UAS: Update to solution #2 |
pCR revision of S3-211115 |
Ericsson | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211213 | EN resolution on null scheme for solution 2.7 |
pCR revision of S3-210876 |
ZTE Corporation | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211214 | KI on Modification or revocation of user consent | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
withdrawn | [WTS] [JSN] |
| S3-211215 | IIoT: Update to solution #3 |
pCR revision of S3-211112 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211216 | IIoT: Update to and conclusion on KI #2 |
pCR revision of S3-211113 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211217 | Service response verification in indirect communication |
pCR revision of S3-211161 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211218 | More details on SCP deployment models |
pCR revision of S3-211166 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211219 | New Solution to KI#4: Using existing procedures for authorization of SCP to act on behalf of an NF Consumer | pCR | Ericsson | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
withdrawn | [WTS] [JSN] |
| S3-211220 | NF-SCP authorization |
pCR revision of S3-211160 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211221 | KI details added to End-to-end integrity protection of HTTP messages |
pCR revision of S3-211170 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211222 | EC: Update to solution #17 |
pCR revision of S3-211114 |
Ericsson | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211223 | Service request authenticity verification in indirect communication |
pCR revision of S3-211159 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211224 | Rapporteurs update to 33.875 |
pCR revision of S3-211156 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211225 | Mapping of solutions to key issues |
pCR revision of S3-211157 |
Nokia, Nokia Shanghai Bell | 33.875 0.1.0 | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211226 | Requirement and solution on multiple working domains |
pCR revision of S3-210999 |
Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211227 | Annex on asmmetric delay attacks |
pCR revision of S3-211002 |
Nokia, Nokia Shanghai Bell, Deutsche Telekom | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211228 | KI4 update on NEF-AF |
pCR revision of S3-211000 |
Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211229 | ProSe: Retrieve Discovery keys for UE-to-network relays |
pCR revision of S3-211088 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211230 | ProSe: Update to solution #21 |
pCR revision of S3-211089 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211231 | LS on end-to-end protection of HTTP message for Indirect communication |
LS out LS To: CT4 revision of S3-211118 |
CableLabs, Mavenir, Nokia, Nokia Bell Labs | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] | ||
| S3-211232 | Resolution of Editor’s Notes in Solution#7 |
pCR revision of S3-211023 |
Lenovo, Motorola Mobility | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211233 | Update of Solution#6 |
pCR revision of S3-211025 |
Lenovo, Motorola Mobility | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211234 | Solution for KI#1.3 |
pCR revision of S3-211010 |
Lenovo, Motorola Mobility | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211235 | New annex of TR 33.809 – attack taxonomy for 5G UE over radio interfaces |
pCR revision of S3-211128 |
CableLabs, NTT Docomo, Philips, Deutsche Telekom AG | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211236 | SUCI Linkability attack |
pCR revision of S3-210992 |
NEC | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211237 | KI on Ensuring restrictive transfer of ML models between authorized NWDAFs |
pCR revision of S3-211039 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211238 | Solution on Privacy preservation of data |
pCR revision of S3-211041 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
noted | [WTS] [JSN] |
| S3-211239 | Solution on Abnormal NF behaviour detection |
pCR revision of S3-211042 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211240 | TR 33.847 Update for solution #10 |
pCR revision of S3-210825 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211241 | Update of KI on Security protection of data via Message Framework |
pCR revision of S3-211043 |
Nokia, Nokia Shanghai Bell | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211242 | TR 33.847 Update for solution #24 |
pCR revision of S3-210826 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211243 | IIOT: Update to KI#3 |
pCR revision of S3-211080 |
Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211244 | Solution for providing secure onboarding without client authentication |
pCR revision of S3-211009 |
Nokia, Nokia Shanghai Bell | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211245 | Update to Solution#4 |
pCR revision of S3-211117 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211246 | IIOT: Conclusion on KI#4 |
pCR revision of S3-211081 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211247 | Update to Solution#6 |
pCR revision of S3-211119 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211248 | Solution to enable Reallocated AMF to serve the UE |
pCR revision of S3-211121 |
Lenovo, Motorola Mobility | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211249 | Update to Solution#7 |
pCR revision of S3-211122 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211250 | Resolving EN on UAVC Change |
pCR revision of S3-211124 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211251 | TR 33.854 Solution#3 evaluation |
pCR revision of S3-210831 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211252 | TR 33.854 Solution#5 evaluation |
pCR revision of S3-210832 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211253 | Update to Solution#15 |
pCR revision of S3-211125 |
Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211254 | TR 33.854 Solution#12 evaluation |
pCR revision of S3-210833 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211255 | TR 33.854 Update for KI#4 |
pCR revision of S3-210834 |
InterDigital, Europe, Ltd. | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211256 | TR 33.854 Update for KI#6 |
pCR revision of S3-210835 |
InterDigital, Europe, Ltd., Lenovo, Motorola Mobility | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211257 | VNP SCAS Instantiation |
pCR revision of S3-210940 |
Futurewei Technologies | 33.818 0.10.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] |
| S3-211258 | Resolving editor’s note in solution #32 |
pCR revision of S3-211149 |
Philips International B.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211259 | pCR: Addressing the EN in solution #4 |
pCR revision of S3-211076 |
Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211260 | pCR: Addressing the PS discovery EN in solution #11 |
pCR revision of S3-211078 |
Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211261 | MitM FBS Detection |
pCR revision of S3-210975 |
Huawei, HiSilicon, Philips | 33.809 0.12.1 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211262 | add evaluation to solution 1 |
pCR revision of S3-210976 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211263 | add evaluation to solution 11 |
pCR revision of S3-210977 |
Huawei, HiSilicon | 33.854 0.3.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211264 | Scope of eNS2 study |
other revision of S3-210988 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
approved | [WTS] [JSN] | ||
| S3-211265 | New KI - privacy issue on broadcasting slice information |
other revision of S3-210990 |
Huawei, HiSilicon, Nokia | Rel-17 |
S3-102-e-Bis AI: 2.21 |
approved | [WTS] [JSN] | ||
| S3-211266 | Draft TR for eNS2 Study |
other revision of S3-210986 |
Huawei, HiSilicon | Rel-17 |
S3-102-e-Bis AI: 2.21 |
approved | [WTS] [JSN] | ||
| S3-211267 | Add new key issue for user consent in TR 33.867 |
pCR revision of S3-210872 |
CATT | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-211268 | Add evaluation to solution#5 |
pCR revision of S3-210868 |
CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211269 | Add evaluation to solution#6 |
pCR revision of S3-210869 |
CATT | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211270 | Add evaluation to solution 1 |
pCR revision of S3-210933 |
CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211271 | Add evaluation to solution 2 |
pCR revision of S3-210934 |
CATT | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211272 | pCR to TR33.847- Update Solution#29 |
pCR revision of S3-210994 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211273 | pCR to TR33.847- Update Solution#30 |
pCR revision of S3-210995 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211274 | Draft TR 33.847 v0.5.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] | |
| S3-211275 | MUSIM: Resolving the EN regarding SA2’s decision on Busy Indication |
pCR revision of S3-211096 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
| S3-211276 | MUSIM: Updating the threat analysis in Key Issue #1 |
pCR revision of S3-211097 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
| S3-211277 | MUSIM: Updating Solution #1 |
pCR revision of S3-211100 |
Xiaomi Technology | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
| S3-211278 | Secure framewrok for MBS key distribution |
pCR revision of S3-210857 |
Nokia, Nokia Shanghai Bell | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211279 | Direct UE connection to Slice AMF |
pCR revision of S3-210858 |
Nokia, Nokia Shanghai Bell | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211280 | Updates to solution 1 |
pCR revision of S3-210983 |
Intel Deutschland GmbH | 33.873 0.2.0 | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] |
| S3-211281 | Updates to solution 4 |
pCR revision of S3-210979 |
Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211282 | Updates to solution 12 |
pCR revision of S3-210980 |
Intel Deutschland GmbH | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211283 | Updates to solution 14: Add detailed steps |
pCR revision of S3-210984 |
Intel Deutschland GmbH | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211284 | draft TR Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules | draft TR | Intel Deutschland GmbH | FS_MUSIM_SEC | Rel-17 |
S3-102-e-Bis AI: 2.19 |
approved | [WTS] [JSN] | |
| S3-211285 | AMF reallocation: Update to solution #2 |
pCR revision of S3-211091 |
Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211286 | AMF re-allocation: New solution with reroute of Registration Request and protected security context via RAN |
pCR revision of S3-211093 |
Ericsson | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211287 | Draft TR 33.846 v0.11.0 Study on authentication enhancements in the 5G System (5GS) | draft TR | Ericsson Hungary Ltd | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] | |
| S3-211288 | Draft TR 33.864 v0.4.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson Hungary Ltd | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] | |
| S3-211289 | Update the evaluation for solution #3 |
pCR revision of S3-211067 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211290 | Update the evaluation for solution #4 |
pCR revision of S3-211068 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211291 | Authorization of remote UE in L3 U2N relay |
pCR revision of S3-211063 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211292 | EN resolution and evaluation for solution #20 |
pCR revision of S3-211066 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211293 | Draft TR 33.850 | draft TR | Huawei, HiSilicon | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] | |
| S3-211294 | 5G MBS traffic protection at service-layer |
pCR revision of S3-211070 |
Qualcomm Incorporated | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211295 | Update and add evaluation to Solution #7 in TR 33.847 |
pCR revision of S3-210891 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211296 | Address Editor's Note in Solution #27 |
pCR revision of S3-210892 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211297 | Address Editor's Note in Solution #28 |
pCR revision of S3-210893 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211298 | new solution for PC5 one-to-one rekeying |
pCR revision of S3-210897 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211299 | New Solution for Interworking from 5GS to EPS |
pCR revision of S3-210899 |
Huawei, HiSilicon | 33.853 1.4.0 | FS_UP_IP_Sec | Rel-17 |
S3-102-e-Bis AI: 2.3 |
approved | [WTS] [JSN] |
| S3-211300 | New Solution for UE Related Analytics of NWDAF |
pCR revision of S3-210905 |
Huawei, HiSilicon | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-211301 | Solution Update for Solution #5 |
pCR revision of S3-210909 |
Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211302 | Solution Update for Solution #12 |
pCR revision of S3-210910 |
Huawei, HiSilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211303 | Solution Update for Solution #2 |
pCR revision of S3-210912 |
Huawei, HiSilicon | 33.866 0.3.0 | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] |
| S3-211304 | New solution to mitigate the SUPI guessing attack |
pCR revision of S3-210914 |
Huawei, HiSilicon | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211305 | Update for solution #3.1 |
pCR revision of S3-210915 |
Huawei, HiSilicon | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211306 | Conclusion on key issue 1 |
pCR revision of S3-210916 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell, Ericsson | 33.851 0.4.0 | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211307 | New solution to update the MBS keys |
pCR revision of S3-210918 |
Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211308 | Resolving the Editor's Notes in solution 2 |
pCR revision of S3-210919 |
Huawei, HiSilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211309 | Add evaluation to solution#11 |
pCR revision of S3-210922 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211310 | Add evaluaition to solution#29 |
pCR revision of S3-210925 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211311 | Add evaluaition to solution#30 |
pCR revision of S3-210926 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211312 | Address the remaining ENs in solution 15 |
pCR revision of S3-210929 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211313 | Reply LS on 5MBS progress and issues to address |
LS out LS is reply to S3-210814 LS To: RAN2 |
Huawei, HiSilicon |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] | |||
| S3-211314 | Editor notes removal |
pCR revision of S3-210953 |
Huawei, Hisilicon | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
| S3-211315 | AMFReal: Evaluation to solution #1 |
pCR revision of S3-210957 |
Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211316 | AMFReal: Updates to solution #3 |
pCR revision of S3-210959 |
Huawei, Hisilicon | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211317 | MBS: Evaluation to solution #4 |
pCR revision of S3-210964 |
Huawei, Hisilicon | 33.85 0.4.0 | FS_5MBS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.11 |
approved | [WTS] [JSN] |
| S3-211318 | EC: Conclusion for KI #9 |
pCR revision of S3-210969 |
Huawei, Hisilicon, ZTE | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211319 | EC: Update of solution #22 |
pCR revision of S3-210972 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211320 | EC: New solution for the authorization during EDN relocation |
pCR revision of S3-210973 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211321 | TR 33.839 v0.5.0 | draft TR | Huawei, Hisilicon | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] | |
| S3-211322 | draft TR 33.866 0.4.0 | draft TR | China Mobile | FS_eNA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.16 |
approved | [WTS] [JSN] | |
| S3-211323 | draft TR 33.862 0.4.0 | draft TR | China Mobile | FS_SEC_5GMSG | Rel-17 |
S3-102-e-Bis AI: 2.15 |
approved | [WTS] [JSN] | |
| S3-211324 | Solution to Key issue #2.2 in TR 33.846 |
pCR revision of S3-211050 |
China Mobile | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211325 | TR 33.818 v0.11.0 | draft TR | China Mobile Com. Corporation | FS_VNP_SECAM_SCAS | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] | |
| S3-211326 | New Solution for Authentication and Authorization between EEC and ECS/EES |
pCR revision of S3-210952 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211327 | Evaluation of solution#9 |
pCR revision of S3-210955 |
Huawei, Hisilicon | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211328 | ProSe: Update to solution #5 |
pCR revision of S3-211087 |
Ericsson, Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
| S3-211329 | Solution for KI#2 using PKC without requiring tight time sync |
pCR revision of S3-211109 |
Philips International B.V. | 33.809 0.13.0 | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] |
| S3-211330 | Reply LS on propagation of user consent related information during Xn inter-PLMN handover |
LS out LS is reply to S3-210817 LS To: RAN3 revision of S3-211011 |
Ericsson France S.A.S | Rel-16 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] | ||
| S3-211331 | Adding the revocation functionality to solution #14 |
pCR revision of S3-211053 |
Qualcomm Incorporated | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211332 | TR 33.867 | draft TR | Huawei;HiSilicon | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] | |
| S3-211333 | Adding the revocation functionality to solution #13 |
pCR revision of S3-211054 |
Qualcomm Incorporated | 33.854 0.4.0 | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] |
| S3-211334 | Addressing the ENs on ngKSI in solution #1 |
pCR revision of S3-211055 |
Qualcomm Incorporated | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211335 | Addressing the EN on determining whether there is an AMF re-allocation in solution #1 |
pCR revision of S3-211056 |
Qualcomm Incorporated | 33.864 0.3.0 | FS_AMFREAL_SEC | Rel-17 |
S3-102-e-Bis AI: 2.17 |
approved | [WTS] [JSN] |
| S3-211336 | Some proposed text for the assessment of attack risk table |
pCR revision of S3-211057 |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | 33.846 0.10.0 | FS_AUTH_ENH | Rel-17 |
S3-102-e-Bis AI: 2.5 |
approved | [WTS] [JSN] |
| S3-211337 | Using TLS with AKMA to protect EDGE-1 and EDGE-4 |
pCR revision of S3-211060 |
Qualcomm Incorporated | 33.839 0.4.0 | FS_eEDGE_Sec | Rel-17 |
S3-102-e-Bis AI: 2.8 |
approved | [WTS] [JSN] |
| S3-211338 | Reply LS on the user consent for trace reporting |
LS out LS is reply to S3-210813 LS To: RAN2, SA5 revision of S3-211062 |
Qualcomm Incorporated |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] | |||
| S3-211339 | TR 33.848 v0.7.0 | draft TR | BT plc | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
approved | [WTS] [JSN] | |
| S3-211340 | Administration of the virtualisation fabric |
pCR revision of S3-210829 |
NCSC | 33.848 0.6.0 | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
approved | [WTS] [JSN] |
| S3-211341 | Update on Ki#27 Image Snapshot and VNF Mobility. |
pCR revision of S3-210839 |
Nokia, Nokia Shanghai Bell | 33.848 0.6.0 | FS_SIV | Rel-16 |
S3-102-e-Bis AI: 2.4 |
approved | [WTS] [JSN] |
| S3-211342 | New Solution for User Consent for Exposure of information to Edge Applications in Real Time |
pCR revision of S3-210993 |
China Unicom | 33.867 0.3.0 | FS_UC3S | Rel-17 |
S3-102-e-Bis AI: 2.14 |
approved | [WTS] [JSN] |
| S3-211343 | Draft TR 33.851 | draft TR | Nokia | FS_IIoT_SEC | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] | |
| S3-211344 | Draft TR 33.875 | draft TR | Nokia | FS_eSBA_SEC | Rel-17 |
S3-102-e-Bis AI: 2.2 |
approved | [WTS] [JSN] | |
| S3-211345 | Draft TR 33.809 | draft TR | Apple | FS_5GFBS | Rel-17 |
S3-102-e-Bis AI: 2.1 |
approved | [WTS] [JSN] | |
| S3-211346 | Draft TR 33.854 | draft TR | Qualcomm | FS_UAS_SEC | Rel-17 |
S3-102-e-Bis AI: 2.7 |
approved | [WTS] [JSN] | |
| S3-211347 | Draft TR TR 33.857 | draft TR | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-102-e-Bis AI: 2.12 |
approved | [WTS] [JSN] |
1344 documents (1.1062200069427 seconds)