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-211350 | Agenda | agenda | SA WG3 Chair |
S3-103-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-211351 | Report from SA3#102Bis-e meeting | report | MCC |
S3-103-e AI: 2 |
approved | [WTS] [JSN] | |||
S3-211352 | Process for SA3#103e meeting |
other revised to S3-211989 |
SA WG3 Chair |
S3-103-e AI: 1 |
revised | [WTS] [JSN] | |||
S3-211353 | Report from last SA | report | SA WG3 Chair |
S3-103-e AI: 2 |
noted | [WTS] [JSN] | |||
S3-211354 | Process and agenda presentation for SA3#103-e | other | SA3 VC |
S3-103-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-211355 | Agenda and notes from the SA3/IETF joint call | other | SA WG3 Chair |
S3-103-e AI: 4.22 |
noted | [WTS] [JSN] | |||
S3-211356 | Living document for TS 33.220: UDM services for GBA | draftCR | THALES | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-211357 | Living document for TS 33.223: UDM services for GBA | draftCR | THALES | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-211358 | New KI: Secure Direct Discovery codes and filters renewal for the out-of-coverage scenario | pCR | MITRE Corporation | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211359 | SA3 meeting calendar |
other revised to S3-211433 |
SA WG3 Chair |
S3-103-e AI: 7 |
revised | [WTS] [JSN] | |||
S3-211360 | Draft agenda for SA3 104-e | agenda | SA WG3 Chair |
S3-103-e AI: 7 |
withdrawn | [WTS] [JSN] | |||
S3-211361 | Report from SA3#102e | report | MCC |
S3-103-e AI: 2 |
approved | [WTS] [JSN] | |||
S3-211362 | LS on using MOBIKE in Integrated Access and Backhaul system |
LS in LS reply in S3-212164, S3-212164 |
R3-211297 |
S3-103-e AI: 5.18 |
replied to | [WTS] [JSN] | |||
S3-211363 | Reply LS on IP address to GPSI translation | LS in | S2-2009339 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] | |||
S3-211364 | Reply to LS on Resynchronisations |
LS in LS reply in S3-211496 |
ETSI SAGE |
S3-103-e AI: 5.5 |
postponed | [WTS] [JSN] | |||
S3-211365 | Reply LS on IP address to GPSI translation | LS in | S2-2101307 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] | |||
S3-211366 | 5G capabilities exposure for factories of the future - revised | LS in | 5G Alliance for Connected Industries and Automation (5G-ACIA) |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211367 | Misalignment on usage of OAuth within 3GPP 29.510 |
LS in LS reply in S3-212876, S3-213192 |
GSMA |
S3-103-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-211368 | AMF transparency for SOR | LS in | C1-207736 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211369 | Reply LS on AMF transparency for SOR | LS in | C4- 211701 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211370 | LS on extraterritorial use of MCC for satellite access | LS in | C1-210439 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211371 | Reply LS on extraterritorial use of MCC for satellite access | LS in | S1-210358 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211372 | LS on broadcasting from other PLMN in case of Disaster Condition |
LS in LS reply in S3-212258 |
C1-211189 |
S3-103-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-211373 | Reply LS on the re-keying procedure and security indication for NR SL | LS in | C1-211228 |
S3-103-e AI: 4.2 |
noted | [WTS] [JSN] | |||
S3-211374 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | LS in | C1-211461 |
S3-103-e AI: 4.13 |
noted | [WTS] [JSN] | |||
S3-211375 | Reply LS on storage of KAUSF |
LS in LS reply in S3-212291, S3-212291 |
C1-211518 |
S3-103-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-211376 | LS on Secondary AUTH for 5GS interworking with EPS |
LS in LS reply in S3-212366 |
C3-210377 |
S3-103-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-211377 | LS on Changes to SoR Delivery Mechanism | LS in | C4-205696 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211378 | LS on the Security consideration to support L2TP with CUPS |
LS in LS reply in S3-212365, S3-211746, S3-212365 |
C4-210171 |
S3-103-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-211379 | LS on the support of L2TP with CUPS | LS in | C4-211624 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211380 | LS on Header Enrichment for HTTPS in PFCP |
LS in LS reply in S3-212344, S3-212344 |
C4-211662 |
S3-103-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-211381 | Reply LS on port allocation for the W1 interface | LS in | C4-211700 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211382 | User location identification from Carrier Aggregation secondary cell activation messages |
LS in LS reply in S3-212305, S3-212305 |
GSMA |
S3-103-e AI: 6 |
replied to | [WTS] [JSN] | |||
S3-211383 | Prevention of attacks on sliced core network | LS in | GSMA |
S3-103-e AI: 4.19 |
postponed | [WTS] [JSN] | |||
S3-211384 | Attack preventing NAS procedures to succeed | LS in | GSMA |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211385 | Support of UAVs authentication/authorization in 3GPP systems and interfacing with USS/UTM |
LS in LS reply in S3-213372 |
GSMA |
S3-103-e AI: 5.7 |
postponed | [WTS] [JSN] | |||
S3-211386 | 3GPP SA1 clarifications on problematic UAV | LS in | GSMA |
S3-103-e AI: 5.7 |
noted | [WTS] [JSN] | |||
S3-211387 | LS on UE location aspects in NTN |
LS in LS reply in S3-212306, S3-212306 |
R2-2102055 |
S3-103-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-211388 | Reply LS on broadcasting gNB ID length in system information block | LS in | R2-2102449 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211389 | Remove the user message size limitation for DTLS over SCTP | LS in | R3-211274 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211390 | LS on support of PWS over SNPN | LS in | S1-210368 |
S3-103-e AI: 5.12 |
postponed | [WTS] [JSN] | |||
S3-211391 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-212048 |
S2-2009339 |
S3-103-e AI: 5.8 |
replied to | [WTS] [JSN] | |||
S3-211392 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-212048 |
S2-2101307 |
S3-103-e AI: 5.8 |
replied to | [WTS] [JSN] | |||
S3-211393 | Reply LS on NSSAA at inter-PLMN mobility | LS in | S2-2101052 |
S3-103-e AI: 4.19 |
noted | [WTS] [JSN] | |||
S3-211394 | LS on UE capabilities indication in UPU | LS in | S2-2101072 |
S3-103-e AI: 5.12 |
postponed | [WTS] [JSN] | |||
S3-211395 | LS on updating the Credentials Holder controlled lists for SNPN selection |
LS in LS reply in S3-212208 |
S2-2101077 |
S3-103-e AI: 5.12 |
replied to | [WTS] [JSN] | |||
S3-211396 | Reply LS on AKMA Anchor Function selection | LS in | S2-2101304 |
S3-103-e AI: 4.12 |
noted | [WTS] [JSN] | |||
S3-211397 | Reply LS on Secondary AUTH for 5GS interworking with EPS |
LS in LS reply in S3-212366 |
S2-2101305 |
S3-103-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-211398 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | LS in | S2-2101306 |
S3-103-e AI: 4.13 |
noted | [WTS] [JSN] | |||
S3-211399 | LS on PAP/CHAP and other point-to-point protocols usage in 5GS | LS in | S2-2101309 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211400 | LS Response on Network Slice PA Charging per maximum utilized bandwidth | LS in | S2-21001347 |
S3-103-e AI: 5.16 |
withdrawn | [WTS] [JSN] | |||
S3-211401 | LS on Layer-3 UE-to-Network Relay authentication and authorization | LS in | S2-2101623 |
S3-103-e AI: 5.9 |
postponed | [WTS] [JSN] | |||
S3-211402 | LS on System support for Multi-USIM devices | LS in | S2-2102039 |
S3-103-e AI: 5.19 |
noted | [WTS] [JSN] | |||
S3-211403 | Reply LS on 5MBS progress and issues to address | LS in | S2-2102077 |
S3-103-e AI: 5.11 |
withdrawn | [WTS] [JSN] | |||
S3-211404 | LS on Plugtest issues | LS in | S6-210203 |
S3-103-e AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-211405 | LS on EDGEAPP | LS in | S6-210630 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211406 | Reply LS on clarification regarding EEC ID | LS in | S6-210707 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211407 | 256-bit algorithms based on SNOW 3G or SNOW V |
LS in LS reply in S3-211497 |
ETSI SAGE |
S3-103-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-211408 | Choice of cryptographic algorithm in 256-bit Milenage |
LS in LS reply in S3-212329 |
ETSI SAGE |
S3-103-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-211409 | LS re Penetration Testing of SCAS | LS in | GSMA |
S3-103-e AI: 4.3 |
postponed | [WTS] [JSN] | |||
S3-211410 | LS on progress of ongoing work item ITU-T TR-USSD | LS in | ITU-T SG11 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211411 | Reply LS on UE location aspects in NTN | LS in | S3i210282 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211412 | Living document for TS 33.163 |
draftCR revised to S3-212271 |
KPN N.V. | BEST_5G | Rel-17 |
S3-103-e AI: 4.11 |
revised | [WTS] [JSN] | |
S3-211413 | LS on the latest results on the Vehicular Multimedia deliverables from ITU FG-VM | LS in | ITU-T Focus Group on Vehicular Multimedia (FG-VM) |
S3-103-e AI: 4.2 |
noted | [WTS] [JSN] | |||
S3-211414 | Reply LS on support of PWS over SNPN | LS in | S2-2102963 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-211415 | Reply LS on Prevention of attacks on sliced core network | LS in | S2-2103213 |
S3-103-e AI: 4.19 |
noted | [WTS] [JSN] | |||
S3-211416 | Reply LS on the support of L2TP with CUPS | LS in | S2-2103232 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211417 | Reply LS on RAT type for network monitoring |
LS in LS reply in S3-212158, S3-212158 |
S2-2103237 |
S3-103-e AI: 5.16 |
replied to | [WTS] [JSN] | |||
S3-211418 | LS on security aspects for the method of collection of data from the UE | LS in | S2-213263 |
S3-103-e AI: 5.16 |
postponed | [WTS] [JSN] | |||
S3-211419 | Reply to LS on UE location aspects in NTN | LS in | S2-2103550 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211420 | Reply LS to SA2 on UE Data Collection | LS in | S4-210644 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211421 | LS on Media-Related Services and Requirements | LS in | S4-210680 |
S3-103-e AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-211422 | LS on Transaction Information - Dispersion Analytics |
LS in LS reply in S3-212159 |
S2-2103268 |
S3-103-e AI: 5.16 |
replied to | [WTS] [JSN] | |||
S3-211423 | 3GPP Edge Computing coordination | LS in | S6-210978 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211424 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-212048 |
S6-211082 |
S3-103-e AI: 5.8 |
replied to | [WTS] [JSN] | |||
S3-211425 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | LS in | R2-2104349 |
S3-103-e AI: 5.3 |
noted | [WTS] [JSN] | |||
S3-211426 | LS to SA3 on Small data transmissions |
LS in LS reply in S3-211545 |
R2-2104401 |
S3-103-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-211427 | Reply LS to SA3 on FBS detection | LS in | R2-2104626 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] | |||
S3-211428 | Reply LS on support of PWS over SNPN | LS in | R2-2104640 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-211429 | Discussion paper BEST key hierarchy based on AKMA | discussion | Deutsche Telekom AG | Rel-17 |
S3-103-e AI: 4.11 |
noted | [WTS] [JSN] | ||
S3-211430 | Reply LS on the support of L2TP with CUPS | LS in | C3-212569 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211431 | LS on NAS-based busy indication | LS in | R2-2104354 |
S3-103-e AI: 5.19 |
noted | [WTS] [JSN] | |||
S3-211432 | LS on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism |
LS in LS reply in S3-212204, S3-212204 |
R2-2104654 |
S3-103-e AI: 5.9 |
replied to | [WTS] [JSN] | |||
S3-211433 | SA3 meeting calendar |
other revision of S3-211359 |
SA WG3 Chair |
S3-103-e AI: 7 |
noted | [WTS] [JSN] | |||
S3-211434 | pCR to TR 33.846: Clarification on Key Issue #2.2 | pCR | THALES | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-211435 | pCR to TR 33.846: Clarification on Key Issue #3.2 | pCR | THALES | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-211436 | pCR to TR 33.846: update of assessment of attack risk | pCR | THALES, Nokia, Nokia Shanghai Bell | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-211437 | pCR to 33.846: update of impact of solutions | pCR | THALES | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-211438 | Reply LS on choice of cryptographic algorithm in 256-bit Milenage |
LS out source LS: LS SAGE (21) 01 / S3-211408 LS To: ETSI SAGE |
THALES, Idemia |
S3-103-e AI: 3 |
merged | [WTS] [JSN] | |||
S3-211439 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection | LS in | C1-212419 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-211440 | LS on integrity protection between the UE and the HPLMN of additional fields in SOR transparent container carrying SOR acknowledgement | LS in | C1-212523 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211441 | Reply LS on UE capabilities indication in UPU | LS in | C1-212599 |
S3-103-e AI: 5.12 |
postponed | [WTS] [JSN] | |||
S3-211442 | pCR to 33.846: update to solution #2.4 | pCR | THALES | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-211443 | pCR to 33.847: editorial correction to solution #11 | pCR | THALES | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211444 | pCR to 33.839: GBA-based solution for EEC authentication and authorization framework with ECS and EES |
pCR revised to S3-212223 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211445 | pCR to 33.839: Using TLS with GBA to protect edge interfaces |
pCR revised to S3-212224 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211446 | LS to 3GPP SA3 N32 and multiple PLMN IDs |
LS in LS reply in S3-212392 |
GSMA |
S3-103-e AI: 4.16 |
replied to | [WTS] [JSN] | |||
S3-211447 | Presentation of Report TR 33.851 | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.5.0 | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-211448 | Conclusion on UE-UE |
pCR revised to S3-212125 |
Nokia, Nokia Shanghai Bell | 33.851 0.5.0 | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-211449 | Update of solution applicability to KI | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.5.0 | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-211450 | Update of mapping table related to documented solution in Annex | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.5.0 | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-211451 | Update to asymmetric delay attacks annex | pCR | Nokia, Nokia Shanghai Bell, | 33.851 0.5.0 | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-211452 | WID on IIoT |
WID new revised to S3-212318 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-103-e AI: 4.21 |
revised | [WTS] [JSN] | ||
S3-211453 | WID IIoT Draft CR PTP aspects |
draftCR revised to S3-212316 |
Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] | |
S3-211454 | WID IIoT Draft CR NEF-AF aspects |
draftCR revised to S3-212317 |
Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] | |
S3-211455 | WID IIoT Draft CR Security considerations - informative | draftCR | Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 4.22 |
noted | [WTS] [JSN] | |
S3-211456 | TCG progress - report from TCG rapporteur | other | InterDigital, Inc. |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211457 | Discussion on SEPP to SEPP communication on 5GSA networks | discussion | VODAFONE Group Plc | Rel-16 |
S3-103-e AI: 4.16 |
noted | [WTS] [JSN] | ||
S3-211458 | draft response LS to GSMA on 3GPP SA3 N32 and multiple PLMN IDs |
LS out LS is reply to S3-211446 LS To: GSMA revised to S3-212392 |
VODAFONE Group Plc | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-211459 | CR to 33.501 R16 - Clarification on the number of PLMN IDuse by SEPP over N32 |
CR revised to S3-212287 |
VODAFONE Group Plc | 33.501 16.6.0 CR#1080 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211460 | CR to 33.501 R17 - Clarification on the number of PLMN IDuse by SEPP over N32 |
CR revised to S3-212288 |
VODAFONE Group Plc | 33.501 17.1.0 CR#1081 catA | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211461 | pCR to Living document for TS 33.163: update for 3G, 4G, and 5G key agreement |
other revised to S3-212270 |
KPN N.V. | Rel-17 |
S3-103-e AI: 4.11 |
revised | [WTS] [JSN] | ||
S3-211462 | Draft CR to TS 33.501 to resolve security hole when IPX SEPP is used | draftCR | VODAFONE Group Plc | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.16 |
noted | [WTS] [JSN] | |
S3-211463 | Updated Solution #22: Representation of identities during broadcast |
pCR revised to S3-212132 |
KPN N.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211464 | Solution on Remote Attestation for 5GS | pCR | Johns Hopkins University APL, US National Security Agency, CISA ECD, InterDigital, Fraunhofer SIT, CableLabs, AT&T, Verizon Wireless, NIST | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-211465 | Discussion on Remote Attestation for 5GS | discussion | Johns Hopkins University APL, US National Security Agency, CISA ECD, InterDigital, Fraunhofer SIT, CableLabs, AT&T, Verizon Wireless, NIST | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-211466 | Changes to TR 33.866 | pCR | InterDigital, Inc. | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-211467 | Changes to TR 33.857 | pCR | InterDigital, Inc. | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211468 | pCR to 33.853 - update to 7.2 following liaisons | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
withdrawn | [WTS] [JSN] |
S3-211469 | pCR to 33.853 - Removal of template sections ready for specification approval | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
withdrawn | [WTS] [JSN] |
S3-211470 | pCR to 33.853: editorial updates | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
withdrawn | [WTS] [JSN] |
S3-211471 | pCR to TR 33.853 - resolution of editors notes | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.5 |
withdrawn | [WTS] [JSN] |
S3-211472 | CR to TS 33.401 - addition of UPIP to LTE | CR | VODAFONE Group Plc | 33.401 16.3.0 CR#698 catB | UPIP_SEC_LTE | Rel-16 |
S3-103-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-211473 | CR to TS 43.020 - R16 - Removal of support for GEA2 |
CR revised to S3-212361 |
VODAFONE Group Plc | 43.02 16.0.0 CR#58 catF | TEI16 | Rel-16 |
S3-103-e AI: 6 |
revised | [WTS] [JSN] |
S3-211474 | [33.180] R14 UID encoding | CR | Motorola Solutions Danmark A/S | 33.18 14.9.0 CR#163 catF | MCSec | Rel-14 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211475 | [33.180] R15 UID encoding (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 15.9.0 CR#164 catA | MCSec | Rel-15 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211476 | [33.180] R16 UID encoding (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 16.6.0 CR#165 catA | MCSec | Rel-16 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211477 | Standardising Automated TLS Certificate Management in SBA |
SID new revised to S3-212390 |
BT plc | Rel-18 |
S3-103-e AI: 5.23 |
revised | [WTS] [JSN] | ||
S3-211478 | [33.180] R17 UID encoding (mirror) | CR | Motorola Solutions Danmark A/S | 33.18 17.2.0 CR#166 catA | MCSec | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211479 | [33.180] R17 Group subscription | CR | Motorola Solutions Danmark A/S | 33.18 17.2.0 CR#167 catF | MCXSec2 | Rel-17 |
S3-103-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-211480 | [33.180] R17 Limited Service | CR | Motorola Solutions Danmark A/S | 33.18 17.2.0 CR#168 catB | MCXSec2 | Rel-17 |
S3-103-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-211481 | [33.180] R17 Preconfigured group clarification | CR | Motorola Solutions Danmark A/S | 33.18 17.2.0 CR#169 catF | MCXSec2 | Rel-17 |
S3-103-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-211482 | New KI: DoS on Network Slice Quota | pCR | US National Security Agency, Johns Hopkins University APL, CISA ECD, NIST | 33.874 0.0.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
withdrawn | [WTS] [JSN] |
S3-211483 | Changes to TR 33.847 | pCR | InterDigital, Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211484 | TR 33.847 sol#10 update |
pCR revised to S3-212129 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211485 | TR 33.847 sol#24 evaluation |
pCR revised to S3-212130 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211486 | TR 33.847 sol#25 evaluation |
pCR revised to S3-212131 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211487 | TR 33.854 KI#1 conclusion | pCR | InterDigital, Europe, Ltd. | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-211488 | TR 33.854 KI#2 conclusion | pCR | InterDigital, Europe, Ltd. | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
merged | [WTS] [JSN] |
S3-211489 | TR 33.854 KI#4 conclusion |
pCR revised to S3-212128 |
InterDigital, Europe, Ltd. | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211490 | Discussion document on the use of GEA1 and GEA2 | discussion | VODAFONE Group Plc |
S3-103-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-211491 | CR to TS 43.020 - R11 - Removal of GEA1 and GEA2 due to security concerns |
CR revised to S3-212362 |
VODAFONE Group Plc | 43.02 11.2.0 CR#59 catF | TEI11 | Rel-11 |
S3-103-e AI: 6 |
revised | [WTS] [JSN] |
S3-211492 | CR to TS 43.020 - R12 - Depreciation of GEA2 due to security concerns |
CR revised to S3-212363 |
VODAFONE Group Plc | 43.02 12.1.0 CR#60 catF | TEI12 | Rel-12 |
S3-103-e AI: 6 |
revised | [WTS] [JSN] |
S3-211493 | CR to TS 43.020 - R13 - Removal of GEA1 and GEA2 due to security concerns - mirror |
CR revised to S3-212364 |
VODAFONE Group Plc | 43.02 13.6.0 CR#61 catA | TEI12 | Rel-13 |
S3-103-e AI: 6 |
revised | [WTS] [JSN] |
S3-211494 | CR to TS 43.020 - R14 - Removal of GEA1 and GEA2 due to security concerns - mirror |
CR revised to S3-212370 |
VODAFONE Group Plc | 43.02 14.3.0 CR#62 catA | TEI12 | Rel-14 |
S3-103-e AI: 6 |
revised | [WTS] [JSN] |
S3-211495 | CR to TS 43.020 - R15 - Removal of GEA1 and GEA2 due to security concerns - mirror |
CR revised to S3-212373 |
VODAFONE Group Plc | 43.02 15.0.0 CR#63 catA | TEI12 | Rel-15 |
S3-103-e AI: 6 |
revised | [WTS] [JSN] |
S3-211496 | Draft reply to ETSI SAGE on Resynchronisations |
LS out LS is reply to S3-211364 source LS: S3-211364 LS To: ETSI SAGE |
VODAFONE Group Plc | FS_256_Algo |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] | ||
S3-211497 | DRAFT Response LS on 256-bit algorithms based on SNOW 3G or SNOW V |
LS out LS is reply to S3-211407 source LS: S3-211407 LS To: ETSI SAGE |
VODAFONE Group Plc |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211498 | Alternative 1 DRAFT Response LS on 256-bit Milenage |
LS out LS is reply to S3-211408 source LS: S3-211408 LS To: ETSI SAGE |
VODAFONE Group Plc |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211499 | Alternative 2 DRAFT Response LS on 256-bit Milenage |
LS out LS is reply to S3-211408 source LS: S3-211408 LS To: ETSI SAGE |
VODAFONE Group Plc |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211500 | Alternative 3 DRAFT Response LS on 256-bit Milenage |
LS out LS is reply to S3-211408 source LS: S3-211408 LS To: ETSI SAGE revised to S3-212329 |
VODAFONE Group Plc |
S3-103-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-211501 | Changes to TR 33.839 | pCR | InterDigital, Inc. | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211502 | Solution#8 Clarifications | pCR | Nokia, Nokia Shanghai Bell | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-211503 | Discussion on the solution#4.1 in TR 33.846 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211504 | Evaluation of sol#4.1 using MACS as freshness in calculation of AK | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211505 | Editor note removal on solution #2.9 MAC, SYNCH failure cause concealment |
pCR revised to S3-212267 |
Nokia, Nokia Shanghai Bell | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211506 | Conclusion on Key issue #2.1 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211507 | Conclusion on Key issue #3.2 SUPI guessing attack | pCR | Nokia, Nokia Shanghai Bell,THALES | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211508 | Conclusion on Key issue #4.1 | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211509 | EN removal on SUCI generation by legitimate SUPI owner using KSUCI | pCR | Nokia, Nokia Shanghai Bell | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211510 | LS on Security risk evaluation of using long term key for another key derivation than AKA |
LS out LS To: ETSI SAGE revised to S3-212268 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] | ||
S3-211511 | Discussion paper on ENs in Network Slicing clause 16.3 | discussion | Nokia, Nokia Shanghai-Bell |
S3-103-e AI: 4.19 |
noted | [WTS] [JSN] | |||
S3-211512 | CR to Delete NSSAA Editor Notes (Rel-16) | CR | Nokia, Nokia Shangahai-Bell | 33.501 16.6.0 CR#1082 catF | eNS | Rel-16 |
S3-103-e AI: 4.19 |
merged | [WTS] [JSN] |
S3-211513 | CR to Delete NSSAA Editor Notes (Rel-17) | CR | Nokia, Nokia Shanghai-Bell | 33.501 17.1.0 CR#1083 catF | eNS | Rel-17 |
S3-103-e AI: 4.19 |
merged | [WTS] [JSN] |
S3-211514 | Discussion on UE IP address to GPSI translation | discussion | Nokia, Nokia Shanghai-Bell |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211515 | Skeleton for 5G NSWO TR | draft TR | Nokia, Nokia Shanghai-Bell | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
approved | [WTS] [JSN] | |
S3-211516 | Scope for 5G NSWO TR |
pCR revised to S3-212148 |
Nokia, Nokia Shanghai-Bell | 33.881 0.0.0 | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-211517 | Introduction for 5G NSWO TR |
pCR revised to S3-212149 |
Nokia, Nokia Shanghai-Bell | 33.881 0.0.0 | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-211518 | KI: Support of EAP Authentication for 5G NSWO |
pCR revised to S3-212150 |
Nokia, Nokia Shanghai-Bell | 33.881 0.0.0 | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
revised | [WTS] [JSN] |
S3-211519 | Discussion on R3 LS on MOBIKE | discussion | Nokia, Nokia Shanghai-Bell | Rel-17 |
S3-103-e AI: 5.18 |
endorsed | [WTS] [JSN] | ||
S3-211520 | REly LS on MOBIKE usage in IAB |
LS out LS is reply to R3-211297 LS To: RAN3 revised to S3-212164 |
Nokia, Nokia Shanghai-Bell | Rel-17 |
S3-103-e AI: 5.18 |
revised | [WTS] [JSN] | ||
S3-211521 | Further conclusions for KI #1 |
pCR revised to S3-212521 |
CableLabs | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211522 | Updating annex B in TR 33.809 | pCR | CableLabs | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211523 | Reply LS to LS on broadcasting from other PLMN in case of Disaster Condition |
LS out LS is reply to S3-211372 source LS: C1-211189 LS To: CT1 revised to S3-212258 |
LG Electronics Inc. | FS_MINT-CT | Rel-17 |
S3-103-e AI: 3 |
revised | [WTS] [JSN] | |
S3-211524 | Updates in Solution 4 |
pCR revised to S3-212176 |
LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211525 | Evaluation of Solution 13 |
pCR revised to S3-212175 |
LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211526 | Remove editor's notes in key issue 1 | pCR | LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211527 | Reply LS to GSMA on prevention of attacks on sliced core network |
LS out LS is reply to GSMA source LS: S3-211383 LS To: GSMA revised to S3-212463 |
CableLabs | Rel-16 |
S3-103-e AI: 4.19 |
noted | [WTS] [JSN] | ||
S3-211528 | Resolving ENs of solution 6.2.10 |
pCR revised to S3-212296 |
NEC Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211529 | Evaluation of key issue 2.2 SUCI replay attack. | pCR | NEC Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-211530 | Discussion document on replies to ETSI SAGE | discussion | VODAFONE Group Plc |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211531 | pCR to TR 33.845 - editorial corrections |
pCR revised to S3-212347 |
VODAFONE Group Plc | 33.845 1.0.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-103-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-211532 | Cover Sheet for approval of TR 33.845 | TS or TR cover | VODAFONE Group Plc | FS_5GC_SEC_ARPF | Rel-17 |
S3-103-e AI: 5.6 |
approved | [WTS] [JSN] | |
S3-211533 | pCR to TR 33.845 - removal of template sections | pCR | VODAFONE Group Plc | 33.845 1.0.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-103-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-211534 | Adding test case on the confidentiality configuration in P-CSCF | pCR | China Telecommunications | 33.226 0.4.0 | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-211535 | Evaluation of solution #2.10 | pCR | NEC Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211536 | Adding a new threat related to SPI allocation in the P-CSCF | draftCR | China Telecommunications | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
withdrawn | [WTS] [JSN] | |
S3-211537 | LS on PAP/CHAP and other point-to-point protocols usage in 5GS |
LS out source LS: S2-2101309 LS To: SA2, CT1, CT3 |
China Telecommunications |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211538 | Adding a new threat related to SPI allocation in the P-CSCF | draftCR | China Telecommunications | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
approved | [WTS] [JSN] | |
S3-211539 | Discussion on security of Small data transmissions | discussion | ZTE Corporation | Rel-17 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-211540 | Reply LS on Header Enrichment for HTTPS in PFCP |
LS out LS is reply to C4-211662/S3-211380 source LS: C4-211662/S3-211380 LS To: CT4 |
ZTE Corporation | BEPoP | Rel-17 |
S3-103-e AI: 3 |
merged | [WTS] [JSN] | |
S3-211541 | Reply LS on Small data transmissions |
LS out LS is reply to R2-2104401/S3-211426 source LS: R2-2104401/S3-211426 LS To: RAN2 |
ZTE Corporation | Rel-17 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-211542 | Add a new test case in clause 4.2.2.1.18 | draftCR | ZTE Corporation | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211543 | Living document for SCAS_5G_IPUPS draftCR to TR 33.926 |
other revised to S3-212385 |
ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-103-e AI: 4.7 |
revised | [WTS] [JSN] | |
S3-211544 | Living document for SCAS_5G_IPUPS draftCR to TS 33.513 |
other revised to S3-212386 |
ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-103-e AI: 4.7 |
revised | [WTS] [JSN] | |
S3-211545 | Reply LS on Small data transmission |
LS out LS is reply to S3-211426 LS To: RAN2 |
Intel K.K. | Rel-17 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-211546 | Clarification on how AF select AAnF | CR | ZTE Corporation | 33.535 17.1.0 CR#68 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
merged | [WTS] [JSN] |
S3-211547 | Clarification on how AUSF select AAnF | CR | ZTE Corporation | 33.535 17.1.0 CR#69 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
merged | [WTS] [JSN] |
S3-211548 | Clarification on how the AUSF get RID | CR | ZTE Corporation | 33.535 17.1.0 CR#70 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-211549 | Discussion on Security Issues with SDT | discussion | Intel K.K. | Rel-17 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-211550 | Resolution of EN on other parameter in clause 6.3 | CR | ZTE Corporation | 33.535 17.1.0 CR#71 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-211551 | UDM notifies AAnF AKMA context removal |
CR revised to S3-212319 |
ZTE Corporation | 33.535 17.1.0 CR#72 catB | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-211552 | Update clause 6.1 refer to Kausf stored in AUSF | CR | ZTE Corporation | 33.535 17.1.0 CR#73 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-211553 | Add Routing indicator in Authentication response | CR | ZTE Corporation | 33.501 17.1.0 CR#1084 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-211554 | Clarification on external file system mount restrictions R16 | CR | ZTE Corporation | 33.117 16.6.0 CR#69 catF | SCAS_5G | Rel-16 |
S3-103-e AI: 4.15 |
agreed | [WTS] [JSN] |
S3-211555 | Clarification on external file system mount restrictions R17 | CR | ZTE Corporation | 33.117 16.6.0 CR#70 catA | SCAS_5G | Rel-17 |
S3-103-e AI: 4.15 |
not pursued | [WTS] [JSN] |
S3-211556 | Editorial correction in clause 4.2.2.1.5 R16 | CR | ZTE Corporation | 33.511 16.6.0 CR#21 catF | SCAS_5G | Rel-16 |
S3-103-e AI: 4.15 |
agreed | [WTS] [JSN] |
S3-211557 | Editorial correction in clause 4.2.2.1.5 R17 | CR | ZTE Corporation | 33.511 16.6.0 CR#22 catA | SCAS_5G | Rel-17 |
S3-103-e AI: 4.15 |
not pursued | [WTS] [JSN] |
S3-211558 | Add evaluation and update comparison table for solution 3.2 |
pCR revised to S3-212276 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211559 | Add evaluation for solution 4.5 |
pCR revised to S3-212277 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211560 | EN resolution on null scheme for solution 2.7 |
pCR revised to S3-212274 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211561 | Update to mapping table |
pCR revised to S3-212273 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211562 | Update to solution 2.7 and evaluation table |
pCR revised to S3-212275 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211563 | Update to solution 4.5 for the scenario of UE triggered service request |
pCR revised to S3-212278 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211564 | Conclusion for the key issue#4.1 | pCR | ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211565 | S3-21XXXX Authentication and Authorization with ECS EES EAS | pCR | ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211566 | Conclusion for the key issue#6 |
pCR revised to S3-212180 |
ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211567 | Editorial correction in the references clause | pCR | ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211568 | Evaluation of solution #13 | pCR | ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211569 | New solution for Key issue#4 |
pCR revised to S3-212177 |
ZTE Corporation | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211570 | New solution on control plane based provisioning PS to AUSF | pCR | ZTE Corporation | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211571 | New solution on control plane based provisioning PS to UDM | pCR | ZTE Corporation | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211572 | New solution for AMF re-allocation |
pCR revised to S3-212179 |
ZTE Corporation | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-211573 | Updates to solution 14: Removal of Editor's notes: Certificate Handling |
pCR revised to S3-212166 |
Intel K.K. | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-211574 | Updates to solution 14: Removal of Editor’s notes: One-Way | pCR | Intel K.K. | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211575 | Handle the failure cause by UE | CR | ZTE Corporation | 33.535 17.1.0 CR#74 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-211576 | Additions in Solution #25 | pCR | Philips International B.V. | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211577 | Proposal for conclusion for Key Issue 4 | pCR | Intel K.K. | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-211578 | Proposal for conclusion for Key Issue 4 | pCR | Intel K.K. | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211579 | Updates to solution 14: Removal of Editor’s notes: Three Authentication | pCR | Intel K.K. | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211580 | Updates to solution 4 | pCR | Intel K.K. | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211581 | pCR to TR33.845 - removal of editors notes |
pCR revised to S3-212350 |
VODAFONE Group Plc | 33.845 1.0.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-103-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-211582 | Updates in Solution #23 |
pCR revised to S3-212358 |
Philips International B.V. | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-211583 | Proposal for conclusion for Key Issue 1,2,4,6 | pCR | Intel K.K. | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211584 | Updates in Appendix B | pCR | Philips International B.V. | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211585 | Add an abbreviation to AKMA |
CR revised to S3-212320 |
ZTE Corporation | 33.535 17.1.0 CR#75 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-211586 | Remarks_in_Solution_14 |
pCR revised to S3-212356 |
Philips International B.V. | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-211587 | pCR to TR33.853 - editorial corrections | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211588 | Update_in_solution_26 |
pCR revised to S3-212357 |
Philips International B.V. | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-211589 | Updates to solution 12 |
pCR revised to S3-212167 |
Intel K.K. | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211590 | Update_in_solution_9 |
pCR revised to S3-212232 |
Philips International B.V. | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-211591 | Remark_in_solution_4 |
pCR revised to S3-212231 |
Philips International B.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211592 | Updated Solution #23: Initial key with validity time |
pCR revision of S3-211185 |
TNO | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-211593 | Cover sheet for approval of TR33.853 | TS or TR cover | VODAFONE Group Plc | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] | |
S3-211594 | Updates to solution 1 | pCR | Intel K.K. | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-211595 | Conclusion to Key issue 1,2 |
pCR revised to S3-212165 |
Intel K.K. | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-211596 | Key issue on security aspects of Paging Cause | pCR | Intel K.K. | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-211597 | Updated Solution #23: Initial key with validity time |
pCR revised to S3-212127 |
KPN N.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211598 | Update to solution #25 |
pCR revised to S3-212283 |
Huawei, HiSilicon | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-211599 | Evaluation of solution #4 | pCR | Huawei, HiSilicon | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211600 | Conclusion for KI#3 | pCR | Huawei, HiSilicon | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211601 | Discussion on SN-ID in NSSAA | discussion | Huawei, HiSilicon | eNS |
S3-103-e AI: 4.19 |
noted | [WTS] [JSN] | ||
S3-211602 | Serving network ID in NSSAA | CR | Huawei, HiSilicon | 33.501 16.6.0 CR#1085 catF | eNS | Rel-16 |
S3-103-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-211603 | validity peirod of NSSAA result | CR | Huawei, HiSilicon | 33.501 16.6.0 CR#1086 catF | eNS | Rel-16 |
S3-103-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-211604 | update to KI#1 | pCR | Huawei, HiSilicon | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
merged | [WTS] [JSN] |
S3-211605 | new key issue proposal | pCR | Huawei, HiSilicon | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-211606 | Evaluation of solution #3 |
pCR revised to S3-212181 |
Huawei, HiSilicon | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211607 | Evaluation of solution #5 |
pCR revised to S3-212211 |
Huawei, HiSilicon | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211608 | Conclusion for KI#1 (AA) |
pCR revised to S3-212183 |
Huawei, HiSilicon | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211609 | Conclusion for KI#2 (pairing) |
pCR revised to S3-212184 |
Huawei, HiSilicon | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211610 | Conclusion for KI#7 (C2) |
pCR revised to S3-212185 |
Huawei, HiSilicon | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211611 | Discussion on slice issues in core networks |
discussion revised to S3-212187 |
Huawei, HiSilicon |
S3-103-e AI: 4.19 |
revised | [WTS] [JSN] | |||
S3-211612 | pCR to TR33.845 - Resolution of editors notes for solution#2 | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211613 | pCR to TR33.845 - Resolution of editors notes for solution#3 | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211614 | pCR to TR33.845 - Resolution of editors notes for solutions 5 and 6 | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211615 | Reply LS on SLIC |
LS out LS is reply to S3-211382 LS To: GSMA FSAG, RAN2 |
Nanjing Ericsson Panda Com Ltd |
S3-103-e AI: 6 |
merged | [WTS] [JSN] | |||
S3-211616 | pCR to TR33.845 - Resolution of editors notes for solutions 9 and 10 | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211617 | propose evaluation to Solution #16 | pCR | Huawei, HiSilicon | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-211618 | New solution for one-to-one communication | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211619 | Resolve EN and add evaluation to Solution #27 | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211620 | Resolve EN and add evaluation to Solution #28 | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211621 | Propose evaluation to Solution #32 |
pCR revised to S3-212188 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211622 | Address Ens in Solution #33 | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211623 | Add conclusions about UE-to-Network relay | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211624 | Slice privacy protection in NSSAA related procedures |
CR revised to S3-212280 |
Huawei, HiSilicon | 33.501 16.6.0 CR#1087 catF | eNS | Rel-16 |
S3-103-e AI: 4.19 |
revised | [WTS] [JSN] |
S3-211625 | Security solution for temporary group – broadcast group call procedure | CR | Huawei, HiSilicon | 33.18 17.2.0 CR#170 catB | MCXSec2 | Rel-17 |
S3-103-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-211626 | Correction to Authorization for indirect communication with delegated discovery procedure | CR | Huawei, HiSilicon | 33.501 16.6.0 CR#1088 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
not pursued | [WTS] [JSN] |
S3-211627 | Solution Evaluation for solution 15 |
pCR revised to S3-212189 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211628 | Solution Evaluation for solution 8 |
pCR revised to S3-212190 |
Huawei, HiSilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211629 | Solution Evaluation for solution 11 |
pCR revised to S3-212191 |
Huawei, HiSilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211630 | New WID on Security enhancements for 5G multicast-broadcast services (5MBS) |
WID new revised to S3-212304 |
Huawei, Hisilicon,China Broadcasting Network | Rel-17 |
S3-103-e AI: 4.21 |
revised | [WTS] [JSN] | ||
S3-211631 | Discussion paper on MBS traffic protection | discussion | Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 5.11 |
noted | [WTS] [JSN] | ||
S3-211632 | Update to the solution 11 |
pCR revised to S3-212192 |
Huawei, Hisilicon,China Broadcasting Network | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-211633 | Conclusion for key issue 2 | pCR | Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-211634 | Conclusion for key issue 3 |
pCR revised to S3-212193 |
Huawei, Hisilicon,China Broadcasting Network | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-211635 | Update to the overview | pCR | Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-211636 | Update to the solution 3.3 |
pCR revised to S3-212327 |
Huawei, Hisilicon | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
revised | [WTS] [JSN] |
S3-211637 | Clarification to protect F1 interface security for IAB in NR-DC mode | draftCR | Huawei, Hisilicon | FS_NR_IAB_Sec | Rel-17 |
S3-103-e AI: 5.18 |
noted | [WTS] [JSN] | |
S3-211638 | Reply LS on User location identification from Carrier Aggregation secondary cell activation messages |
LS out LS To: GSMA FSAG revised to S3-212305 |
Huawei, Hisilicon |
S3-103-e AI: 6 |
revised | [WTS] [JSN] | |||
S3-211639 | Reply LS on UE location aspects in NTN |
LS out LS To: RAN2, SA2, SA3-LI, RAN3 revised to S3-212306 |
Huawei, Hisilicon |
S3-103-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-211640 | Corrections on TS 33.521 | pCR | Huawei, HiSilicon, China Mobile | 33.521 0.3.0 | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-211641 | Execution Step for Finding the right NF instance serving the UE |
pCR revised to S3-212307 |
Huawei, HiSilicon, China Mobile | 33.521 0.3.0 | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
revised | [WTS] [JSN] |
S3-211642 | User Plane Integrity Protection Policy Handling in LTE |
draftCR revised to S3-212308 |
Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-103-e AI: 4.13 |
revised | [WTS] [JSN] | |
S3-211643 | UP Integrity protection Handling for Option 3 | draftCR | Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-103-e AI: 4.13 |
withdrawn | [WTS] [JSN] | |
S3-211644 | Assign FC Value for KTIPSec and KTNAP Derivation in R16 |
CR revised to S3-212309 |
Huawei, HiSilicon | 33.501 16.6.0 CR#1089 catF | 5WWC | Rel-16 |
S3-103-e AI: 4.18 |
revised | [WTS] [JSN] |
S3-211645 | Assign FC Value for KTIPSec and KTNAP Derivation in R17 |
CR revised to S3-212310 |
Huawei, HiSilicon | 33.501 17.1.0 CR#1090 catA | 5WWC | Rel-17 |
S3-103-e AI: 4.18 |
revised | [WTS] [JSN] |
S3-211646 | FC Value Change because of KTIPSec and KTNAP Derivation in R16 | CR | Huawei, HiSilicon | 33.22 16.3.0 CR#208 catF | 5WWC | Rel-16 |
S3-103-e AI: 4.18 |
agreed | [WTS] [JSN] |
S3-211647 | FC Value Change because of KTIPSec and KTNAP Derivation in R17 |
CR revised to S3-212311 |
Huawei, HiSilicon | 33.22 17.0.0 CR#209 catA | 5WWC | Rel-17 |
S3-103-e AI: 4.18 |
revised | [WTS] [JSN] |
S3-211648 | Address ENs in TS 33.216 | CR | Huawei, HiSilicon | 33.216 16.5.0 CR#22 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211649 | Solution Update for Solution #28 |
pCR revised to S3-212194 |
Huawei, HiSilicon | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-211650 | Conclusion for Key Issue #7 |
pCR revised to S3-212195 |
Huawei, HiSilicon | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-211651 | LS on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS |
LS out LS To: SA2 revised to S3-212196 |
Huawei, HiSilicon |
S3-103-e AI: 5.3 |
revised | [WTS] [JSN] | |||
S3-211652 | Solution Update for Solution #5 |
pCR revised to S3-212197 |
Huawei, HiSilicon | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-211653 | Evaluation for Solution #12 |
pCR revised to S3-212198 |
Huawei, HiSilicon | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-211654 | Solution Update for Solution #2 |
pCR revised to S3-212199 |
Huawei, HiSilicon | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-211655 | Update on Observations related to Regulations |
pCR revised to S3-212200 |
Huawei, HiSilicon | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-211656 | Add Security Requirement for Key Issue #3 |
pCR revised to S3-212201 |
Huawei, HiSilicon | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-211657 | Conclusion for Key Issue #3.1 | pCR | Huawei, HiSilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-211658 | Conclusion for Key Issue #3.2 | pCR | Huawei, HiSilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-211659 | Conclusion for Key Issue #1.1 | pCR | Huawei, HiSilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-211660 | Reply LS on Security of Small Data Transmissions |
LS out LS To: RAN2 |
Huawei, HiSilicon |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211661 | Delete EN of Solution#2 |
pCR revised to S3-212202 |
Huawei, HiSilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-211662 | Change the procedure of network slice re-authentication and revocation by AAA-S |
CR revised to S3-212312 |
Huawei, HiSilicon | 33.501 17.1.0 CR#1091 catF | eNS | Rel-17 |
S3-103-e AI: 4.19 |
revised | [WTS] [JSN] |
S3-211663 | Add conclusion to KI#10 |
pCR revised to S3-212203 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211664 | Discussion on security of 5G-TMSI-RNTI used for paging and UE ID in adaptation layer in 5G Prose | discussion | Huawei, HiSilicon |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] | |||
S3-211665 | Draft rely LS on R17 Layer-2 SL Relay |
LS out LS To: RAN2 revised to S3-212204 |
Huawei, HiSilicon | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] | ||
S3-211666 | A new Key issue on paging cause | pCR | Huawei, HiSilicon | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-211667 | A new solution to paging cause | pCR | Huawei, HiSilicon | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-211668 | Discussion on penetration testing | discussion | Huawei, HiSilicon | Rel-17 |
S3-103-e AI: 5.23 |
noted | [WTS] [JSN] | ||
S3-211669 | A new SID - penetration testing | SID new | Huawei, HiSilicon | Rel-17 |
S3-103-e AI: 5.23 |
noted | [WTS] [JSN] | ||
S3-211670 | Draft rely LS to GSMA on penetration testing |
LS out LS To: GSMA |
Huawei, HiSilicon | Rel-17 |
S3-103-e AI: 5.23 |
noted | [WTS] [JSN] | ||
S3-211671 | Clarification on AAnF Selection |
CR revised to S3-212313 |
Huawei, HiSilicon | 33.535 17.1.0 CR#76 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-211672 | Editoral change in clause 6.1 | CR | Huawei, HiSilicon | 33.535 17.1.0 CR#77 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-211673 | liviing CR to 33.511 |
draftCR revised to S3-212375 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
revised | [WTS] [JSN] | |
S3-211674 | liviing CR to 33.512 |
draftCR revised to S3-212376 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
revised | [WTS] [JSN] | |
S3-211675 | liviing CR to 33.514 | draftCR | Huawei, HiSilicon,Nokia,Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211676 | liviing CR to 33.517 | draftCR | Huawei, HiSilicon,Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211677 | liviing CR to 33.117 | draftCR | Huawei, HiSilicon,Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211678 | liviing CR to 33.926 |
draftCR revised to S3-212377 |
Huawei, HiSilicon,Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
revised | [WTS] [JSN] | |
S3-211679 | Add textcase of NAS based redirection | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211680 | Add testcase to UP security activation in Inactive scenario | draftCR | Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211681 | Update testcases in gNB SCAS |
CR revised to S3-212314 |
Huawei, HiSilicon | 33.511 16.6.0 CR#23 catF | SCAS_5G | Rel-16 |
S3-103-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-211682 | pCR to TR33.845 - Resolution of editors notes for solutions 11 13 14 and 15 | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211683 | EAP ID Request in NSSAA procedure | discussion | Ericsson |
S3-103-e AI: 4.22 |
withdrawn | [WTS] [JSN] | |||
S3-211684 | Clarify on ngKSI used in NAS SMC in Kausf storage | CR | Huawei, HiSilicon | 33.501 16.6.0 CR#1092 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211685 | Addressing impersonate attack from AAA-S | CR | Huawei, HiSilicon | 33.501 16.6.0 CR#1093 catF | eNS | Rel-16 |
S3-103-e AI: 4.19 |
agreed | [WTS] [JSN] |
S3-211686 | Mirror- Addressing impersonate attack from AAA-S | CR | Huawei, HiSilicon | 33.501 17.1.0 CR#1094 catA | eNS | Rel-17 |
S3-103-e AI: 4.19 |
agreed | [WTS] [JSN] |
S3-211687 | EAP ID Request in NSSAA procedure | discussion | Ericsson |
S3-103-e AI: 4.22 |
noted | [WTS] [JSN] | |||
S3-211688 | pCR to TR33.845 - Resolution of editors notes for solutions 18 19 20 and 21 | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211689 | EAP ID Request in NSSAA Procedure | CR | Ericsson | 33.501 16.6.0 CR#1095 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-211690 | pCR to TR33.845 - Resolution of editors notes for solutions 22 23 24 26 | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211691 | EN Resolution Anomolous NF Behaviour |
pCR revised to S3-212163 |
Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-211692 | Output analytics from NWDAF to detect Anomalous NF Behaviour | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-211693 | Solution on Processing of tampered data |
pCR revised to S3-212160 |
Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-211694 | EN on solution relation with user consent study | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-211695 | EN resolution on solution privacy preservation of transmitted data | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-211696 | Solution on Authorization of NF Service Consumers for data access via DCCF |
pCR revised to S3-212161 |
Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-211697 | Solution on Authorization of NF Service Consumers to access data from ADRF via DCCF |
pCR revised to S3-212162 |
Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-211698 | Reply LS on Transaction Information - Dispersion Analytics |
LS out LS is reply to S3-211422 LS To: SA2 revised to S3-212159 |
Nokia, Nokia Shanghai Bell | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] | |
S3-211699 | KI update Dispersion Analytics against DDoS | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-211700 | EAP ID Request in NSSAA Procedure (Rel-17) | CR | Ericsson | 33.501 17.1.0 CR#1096 catA | TEI16 | Rel-17 |
S3-103-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-211701 | 5GFBS-WID for 5GFBS | WID new | Apple | Rel-17 |
S3-103-e AI: 4.21 |
noted | [WTS] [JSN] | ||
S3-211702 | 5GFBS-Adding evaluation for solution#4 | pCR | Apple | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211703 | 5GFBS-Adding a new clause on Evaluations for key issues | pCR | Apple | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211704 | 5GFBS-Conclusion for key issue#2 | pCR | Apple | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211705 | 5GFBS-Conclusion for key issue#3 | pCR | Apple | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-211706 | 5GFBS-Draft LS to RAN2 on Solution#17 |
LS out LS To: RAN2 revised to S3-212349 |
Apple | Rel-17 |
S3-103-e AI: 5.1 |
revised | [WTS] [JSN] | ||
S3-211707 | MEC-New key issue on EEC ID privacy protection | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211708 | MEC-Adding evaluation on Solution#8 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211709 | MEC-Adding evaluation on Solution#9 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211710 | MEC-Adding evaluation on Solution#11 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211711 | MEC-Adding evaluation on Solution#17 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211712 | MEC-New solution on authentication between EEC and ECS |
pCR revised to S3-212253 |
Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211713 | MEC-Kedge ID generation method |
pCR revised to S3-212254 |
Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211714 | MBS-New solution on Key distribution |
pCR revised to S3-212255 |
Apple | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-211715 | UC3S-Requirement on revoking user consent |
pCR revised to S3-212256 |
Apple | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-211716 | MINT-Discussion paper on MINT | discussion | Apple | Rel-17 |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-211717 | MINT-draft Reply LS to CT1 on MINT. |
LS out LS is reply to CT1 source LS: C1-211189 LS To: CT1 |
Apple | Rel-17 |
S3-103-e AI: 3 |
merged | [WTS] [JSN] | ||
S3-211718 | pCR to TR33.845 - Resolution of editors notes for solutions 28 29 30 |
pCR revised to S3-212217 |
VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-211719 | DRAFT LS on EAP ID Request in NSSAA Procedure |
LS out LS To: SA2 |
Ericsson |
S3-103-e AI: 4.22 |
noted | [WTS] [JSN] | |||
S3-211720 | UE procedures at TAU reject in idle mode mobility from 5GS to EPS over N26 | CR | MediaTek Inc. / Marko | 33.501 16.6.0 CR#1097 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211721 | pCR to TR33.853 - removal of template sections | pCR | VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-211722 | UE procedures at TAU reject in idle mode mobility from 5GS to EPS over N26 | CR | MediaTek Inc. / Marko | 33.501 17.1.0 CR#1098 catA | TEI16 | Rel-17 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211723 | MBS conclusions | pCR | Ericsson | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-211724 | Solution for privacy protection during initial access | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211725 | Analysis of security properties of architectural options | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211726 | Proposal for a conclusion on KI#4 | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211727 | Resolution of editor’s note in solution 19 related to bidding down attacks. | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-211728 | Resolution of Editor's Note in Solution 19 related to provisioning of server certificate the the onboarding UE. |
pCR revised to S3-212241 |
Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-211729 | Resolution of an Editor's Note in Solution 19 related to security implications of the solution | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.5.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-211730 | Resolution of Editor's Note in Solution 19 related to construction of SUCI. | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-211731 | Resolution of Editor's Note in Solution 19 related to UDM involvementUpdate | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-211732 | Evalution and system impact for soluiton 19 |
pCR revised to S3-212248 |
Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-211733 | Update to Solution | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-211734 | LS on Feedback on Key Issue #1 "Enhancements to Support SNPN along with credentials owned by an entity separate from the SNPN" |
LS out LS is reply to SA2 LS To: SA2 |
Nokia, Nokia Shanghai Bell | FS_eNPN |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | ||
S3-211735 | LS on architectural clarifications related to onboarding without client authentication |
LS out LS is reply to SA2 LS To: SA2 |
Nokia, Nokia Shanghai Bell | FS_eNPN |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | ||
S3-211736 | pCR to TR33.853 - Resolution of editors notes in Conclusions and Recommendations |
pCR revised to S3-212218 |
VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-211737 | Update to Solution #4 |
pCR revised to S3-212228 |
Lenovo, Motorola Mobility | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-211738 | Update to Solution #6 |
pCR revised to S3-212229 |
Lenovo, Motorola Mobility | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-211739 | Update to Solution #7 |
pCR revised to S3-212230 |
Lenovo, Motorola Mobility | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-211740 | Mapping of Key Issues | pCR | Lenovo, Motorola Mobility | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-211741 | Discussion capability negotiation for the parameters contained in UPU | discussion | Ericsson Japan K.K. | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | ||
S3-211742 | Conclusion on Key Issue #1 | pCR | Lenovo, Motorola Mobility | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-211743 | LS reply on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism |
LS out LS To: RAN2 |
OPPO | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] | ||
S3-211744 | draft LS reply: UE capabilities indication in UPU |
LS out LS is reply to S2-2101072, C1-212599 LS To: SA2, CT1 |
Ericsson Japan K.K. | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | ||
S3-211745 | Discussion on Security consideration to support L2TP with CUPS | discussion | Ericsson |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211746 | [DRAFT] Reply-LS on the Security consideration to support L2TP with CUPS |
LS out LS is reply to S3-211378 LS To: CT4 revised to S3-212365 |
Ericsson | Rel-17 |
S3-103-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-211747 | [DRAFT] Reply-LS on Secondary AUTH for 5GS interworking with EPS |
LS out LS is reply to S3-211376/C3-210377 LS To: CT3, SA2 revised to S3-212366 |
Ericsson | Rel-17 |
S3-103-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-211748 | Discussion on "LS to 3GPP SA3 N32 and multiple PLMN IDs" | discussion | Ericsson |
S3-103-e AI: 4.16 |
noted | [WTS] [JSN] | |||
S3-211749 | [DRAFT] Reply-LS on N32 and multiple PLMN IDs |
LS out LS To: GSMA 5GJA |
Ericsson |
S3-103-e AI: 4.16 |
noted | [WTS] [JSN] | |||
S3-211750 | Discussion on integrity protection between the UE and the HPLMN of additional fields in SOR transparent container carrying SOR acknowledgement | discussion | Ericsson |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211751 | [Draft] Reply-LS on integrity protection between the UE and the HPLMN of additional fields in SOR transparent container carrying SOR acknowledgement |
LS out LS is reply to S3-211440/C1-212523 LS To: CT1 revised to S3-212272 |
Ericsson |
S3-103-e AI: 3 |
revised | [WTS] [JSN] | |||
S3-211752 | NRF services authorization and OAuth 2.0 client registration from Rel-15 onwards | discussion | Ericsson, Nokia, Nokia Shanghai Bell |
S3-103-e AI: 4.22 |
noted | [WTS] [JSN] | |||
S3-211753 | Clarification on the NRF services authorization | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.501 15.12.0 CR#1099 catF | 5GS_Ph1-SEC | Rel-15 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211754 | Clarification on the NRF services authorization | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.501 16.6.0 CR#1100 catF | 5GS_Ph1-SEC | Rel-16 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211755 | Clarification on the NRF services authorization | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#1101 catA | 5GS_Ph1-SEC | Rel-17 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211756 | Clarification on the OAuth 2.0 client registration | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.501 15.12.0 CR#1102 catF | 5GS_Ph1-SEC | Rel-15 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211757 | Clarification on the OAuth 2.0 client registration | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.501 16.6.0 CR#1103 catA | 5GS_Ph1-SEC | Rel-16 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211758 | Clarification on the OAuth 2.0 client registration | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#1104 catA | 5GS_Ph1-SEC | Rel-17 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211759 | Clarify the usage of TLS and PRINS between SEPPs |
CR revised to S3-212367 |
Ericsson | 33.501 15.12.0 CR#1105 catF | 5GS_Ph1-SEC | Rel-15 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211760 | Clarify the usage of TLS and PRINS between SEPPs |
CR revised to S3-212368 |
Ericsson | 33.501 16.6.0 CR#1106 catA | 5GS_Ph1-SEC | Rel-16 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211761 | Clarify the usage of TLS and PRINS between SEPPs |
CR revised to S3-212369 |
Ericsson | 33.501 17.1.0 CR#1107 catA | 5GS_Ph1-SEC | Rel-17 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211762 | Correction to NF Certificate profile: Format of the apiRoot | CR | Ericsson | 33.31 16.7.0 CR#118 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-211763 | Correction to JOSE profile Reference | CR | Ericsson | 33.501 16.6.0 CR#1108 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-211764 | Correction to JOSE profile Reference | CR | Ericsson | 33.501 17.1.0 CR#1109 catA | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-211765 | Update Solution #5: End-to-end integrity protection of HTTP body and method | pCR | Ericsson | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-211766 | Evaluation of Solution #3 "Using existing procedures for authorization of SCP to act on behalf of an NF Consumer" |
pCR revised to S3-212372 |
Ericsson | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-211767 | Conclusions for KI#1 (external entity) on SUPI privacy and usage of MSK | pCR | Ericsson, Huawei, Interdigital, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211768 | Conclusions for KI#1 (external entity) on AAA interworking | pCR | Ericsson, China Mobile, Huawei, InterDigital, Qualcomm Incorporated | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211769 | Conclusions for KI#4 (initial access) | pCR | Ericsson, Huawei, InterDigital, Lenovo, Motorola Mobility, Qualcomm Incorporated | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211770 | Conclusions for KI#2 on secure provisioning of PNI-NPN credentials | pCR | Ericsson | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211771 | Security aspects of eNPN: draft skeleton for draft CR | discussion | Ericsson, Huawei, InterDigital |
S3-103-e AI: 4.21 |
noted | [WTS] [JSN] | |||
S3-211772 | New WID on Security Aspects of eNPN |
WID new revised to S3-212371 |
Ericsson, Alibaba, China Mobile, InterDigital, ZTE | Rel-17 |
S3-103-e AI: 4.21 |
revised | [WTS] [JSN] | ||
S3-211773 | New WID on certificate profiles for SBA | WID new | Ericsson | Rel-17 |
S3-103-e AI: 4.21 |
noted | [WTS] [JSN] | ||
S3-211774 | New WID on Security aspects of Uncrewed Aerial Systems |
WID new revised to S3-212354 |
Qualcomm Incorporated, Interdigital, Huawei, HiSilicon |
S3-103-e AI: 4.21 |
revised | [WTS] [JSN] | |||
S3-211775 | Update to solution #6 on obtaining UAV location information from the PLMN |
pCR revised to S3-212244 |
Qualcomm Incorporated | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211776 | Update to solution #10 on authentication and authorisation of UAVs | pCR | Qualcomm Incorporated | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-211777 | Update to solution #13 on authorisation of UAV/UAVC when connected to EPS |
pCR revised to S3-212245 |
Qualcomm Incorporated | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211778 | Update to solution #14 on authorisation of UAV/UAVC pairing when connected to 5GS |
pCR revised to S3-212246 |
Qualcomm Incorporated | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-211779 | Discussion on an SA2 LS on IP address to GPSI translation | discussion | Qualcomm Incorporated |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211780 | Proposed reply LS on IP address to GPSI translation |
LS out LS is reply to S2-2101307 LS To: SA2 |
Qualcomm Incorporated |
S3-103-e AI: 5.8 |
merged | [WTS] [JSN] | |||
S3-211781 | Proposed evaluation text for solution #23 | pCR | Qualcomm Incorporated | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-211782 | Proposed evaluation for solution #24 and partial conclusion for key issue #6 |
pCR revised to S3-212243 |
Qualcomm Incorporated | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211783 | Information on the updates to the proposed WID on TLS protocol profiles for AKMA | discussion | Qualcomm Incorporated |
S3-103-e AI: 4.21 |
noted | [WTS] [JSN] | |||
S3-211784 | New WID on TLS protocols profiles for AKMA |
WID new revision of S3-210479 revised to S3-212352 |
Qualcomm Incorporated |
S3-103-e AI: 4.21 |
revised | [WTS] [JSN] | |||
S3-211785 | Profiling the GBA TLS protocols for use with AKMA |
CR revision of S3-210477 revised to S3-212353 |
Qualcomm Incorporated | 33.535 17.1.0 CR#661 catB | AKMA_TLS | Rel-17 |
S3-103-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-211786 | Some proposed text for the assessment of attack risk table |
pCR revision of S3-211057 |
Qualcomm Incorporated, Vodafone | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211787 | Proposed conclusion for key issue #4.1 | pCR | Qualcomm Incorporated, Vodafone | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211788 | Proposed conclusion for the linkability parts of key issues #2.1 and 2.2 | pCR | Qualcomm Incorporated, Vodafone, DoCoMo | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211789 | Addressing the Editors’ Note in solution #1 |
pCR revised to S3-212242 |
Qualcomm Incorporated | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-211790 | Missing details on handling of possible unprotected messages in solution #3 | pCR | Qualcomm Incorporated | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-211791 | ABBA parameter handling in solutions #6 and #7 | pCR | Qualcomm Incorporated | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-211792 | Discussion on adding SCAS for the various split gNB cases |
discussion revised to S3-212838 |
Qualcomm Incorporated |
S3-103-e AI: 4.3 |
noted | [WTS] [JSN] | |||
S3-211793 | Adding SCAS for the various split gNB cases | other | Qualcomm Incorporated |
S3-103-e AI: 4.3 |
noted | [WTS] [JSN] | |||
S3-211794 | Some analysis for key issue #1 | other | Qualcomm Incorporated |
S3-103-e AI: 5.21 |
noted | [WTS] [JSN] | |||
S3-211795 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover | CR | Qualcomm Incorporated, Huawei, HiSilicon, CATT, ZTE | 33.501 15.12.0 CR#1110 catF | 5GS_Ph1-SEC | Rel-15 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211796 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover | CR | Qualcomm Incorporated, Huawei, HiSilicon, CATT, ZTE | 33.501 16.6.0 CR#1111 catA | 5GS_Ph1-SEC | Rel-16 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211797 | Downlink NAS COUNT handling after creating NAS container in EPS to 5GS Handover | CR | Qualcomm Incorporated, Huawei, HiSilicon, CATT, ZTE | 33.501 17.1.0 CR#1112 catA | 5GS_Ph1-SEC | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211798 | Evaluation of Solution #18 |
pCR revised to S3-212169 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211799 | Evaluation of Solution #19 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211800 | Conclusion of KI #1 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211801 | Evaluation of Solution #13 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211802 | EN resolution of Solution #19 |
pCR revised to S3-212170 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211803 | New Key Issue on security policy handling for 5G Prose services |
pCR revised to S3-212171 |
Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211804 | EN resolution of Solution #34 |
pCR revised to S3-212172 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211805 | Conclusion of PC5 security setup for the Layer-3 UE-to-Network relay scenario | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211806 | Evaluation of Solution #24 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211807 | Add an evaluation for solution #10 |
pCR revised to S3-212213 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211808 | Add an evaluation for solution #15 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-211809 | Update an evaluation for solution #30 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211810 | Update of solution #18 to support privacy protection | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211811 | Add an evaluation for solution #32 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211812 | EN resolution of Solution #12 |
pCR revised to S3-212173 |
Qualcomm Incorporated | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-211813 | Evaluation of Solution #2 |
pCR revised to S3-212174 |
Qualcomm Incorporated | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-211814 | Evaluation of Solution #11 | pCR | Qualcomm Incorporated | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
merged | [WTS] [JSN] |
S3-211815 | Discussion on SA2 LS on UE capabilities indication in UPU | discussion | Qualcomm Incorporated |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | |||
S3-211816 | pCR: Additional conclusions for KI #1 | pCR | Qualcomm Incorporated | 33.857 0.4.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-211817 | Sending UE identifier to the AKMA AF |
CR revised to S3-212869 |
Qualcomm Incorporated | 33.535 17.1.0 CR#78 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-211818 | Clarifying the support for authentication methods in an SNPN | CR | Qualcomm Incorporated | 33.501 16.6.0 CR#1113 catF | Vertical_LAN_SEC | Rel-16 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211819 | Clarifying the support for authentication methods in an SNPN | CR | Qualcomm Incorporated | 33.501 17.1.0 CR#1114 catA | Vertical_LAN_SEC | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211820 | UP integrity protection in options 4,5 and 7 | CR | Ericsson | 33.501 17.1.0 CR#1115 catF | eUPIP_SEC | Rel-17 |
S3-103-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-211821 | Correction of Annex A.13 | CR | Ericsson | 33.501 16.6.0 CR#1116 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
withdrawn | [WTS] [JSN] |
S3-211822 | Correction of Annex A.13 | CR | Ericsson | 33.501 17.1.0 CR#1117 catA | TEI16 | Rel-17 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211823 | Reply-LS on security aspects for the method of collection of data from the UE |
LS out LS is reply to LS S2-2103263 on security aspects for the method of collection of data from the UE source LS: S2-2103263 LS To: SA WG2 |
OPPO | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] | |
S3-211824 | pCR to TR33.847- Update Solution#3 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211825 | Clarification on GVNP and 3GPP functinoality in 4.1.1 | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211826 | resolving EN about the GVNP lifecycle in clause 5.2.5.5.7.1 | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211827 | editorial modification in clause 5.2.5.6.8.5.3 and 5.2.5.7.6 | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211828 | Adding threat reference in clause 5.2.5.7.7.2 and 5.2.5.7.7.3 | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211829 | Modifying contents about decoupling scenarios | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211830 | Resolving EN about Figure 5.2.5.1-1 | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211831 | Adding vendor development and product lifecycle processes and test laboratory accreditation into Clause 6 | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211832 | proposal for way forward | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211833 | Clean up to existing editor's note | pCR | China Mobile | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211834 | Presentation of TR33.818 to SA plenary |
TS or TR cover revised to S3-212326 |
China Mobile | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] | |
S3-211835 | Assessment of attack risk | pCR | China Mobile | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211836 | Solution to mitgate the SUPI guessing attack without changing the format of SUCI | pCR | China Mobile | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211837 | Solution to mitigate the SUPI guessing attack and SUCI replay attack by adding new MAC tag in SUCI | pCR | China Mobile | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211838 | Add evaluation to solution #4 |
pCR revised to S3-212216 |
China Mobile | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-211839 | Add evaluation to solution #1 | pCR | China Mobile | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-211840 | Add deatails to solution #6 | pCR | China Mobile | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-211841 | Add evaluation to solution #6 | pCR | China Mobile | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-211842 | Adding asset, description and threats to TR 33.926 for NWDAF SCAS |
CR revision of S3-210775 revised to S3-212321 |
China Mobile | 33.926 17.0.0 CR#41 catB | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
revised | [WTS] [JSN] |
S3-211843 | Execution Step for Data Masking on Integration Analysis |
pCR revised to S3-212322 |
China Mobile | 33.521 0.3.0 | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
revised | [WTS] [JSN] |
S3-211844 | Address ENs in TS 33.521 | pCR | China Mobile, Huawei, HiSilicon | 33.521 0.3.0 | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-211845 | Presentation of TR33.521 to SA plenary |
TS or TR cover revised to S3-212387 |
China Mobile | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
revised | [WTS] [JSN] | |
S3-211846 | pCR to TR33.847- Update Solution#4 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211847 | pCR to TR33.847- Update Solution#29 |
pCR revised to S3-212152 |
CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211848 | pCR to TR33.847- Update Solution#30 |
pCR revised to S3-212153 |
CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211849 | pCR to TR33.847- Conclusion of KI#1 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211850 | pCR to TR33.847- Conclusion of KI#3 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211851 | pCR to TR33.847- Conclusion of KI#10 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-211852 | Address ENs for User Consent for Exposure of information to Edge Applications in Real Time | pCR | China Unicom | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-211853 | add evaluation to solution #23 |
pCR revised to S3-212234 |
Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211854 | add ENs to solution#5 | pCR | Huawei, Hisilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-211855 | recommendation of SHA256 in SIP digest | CR | Huawei, Hisilicon | 33.203 16.1.0 CR#257 catB | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-211856 | reply LS on UE capabilities indication in UPU |
LS out LS To: SA2, CT1 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | ||
S3-211857 | Threats related to session establishment procedure | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211858 | New test case on validation of S-NSSAIs in PDU session establishment |
draftCR revised to S3-212332 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
revised | [WTS] [JSN] | |
S3-211859 | EN removal of solution #9 |
pCR revised to S3-212235 |
Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211860 | Discussion on UE capabilities indication in UPU | discussion | Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] | ||
S3-211861 | Conclusion on KI#5 | pCR | Huawei, Hisilicon | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
merged | [WTS] [JSN] |
S3-211862 | Discussion on NF Domain granularity authorization | discussion | Huawei, Hisilicon | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] | |
S3-211863 | Update to the SID of eSBA for NF Domain granularity authorization | SID revised | Huawei, Hisilicon | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] | |
S3-211864 | New KI on NF Domain granularity authorization | pCR | Huawei, Hisilicon | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-211865 | New solution to key issue #3.3 |
pCR revised to S3-212237 |
Huawei, Hisilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-211866 | New solution to key issue #2.1 | pCR | Huawei, Hisilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-211867 | New solution to key issue #1.5 |
pCR revised to S3-212238 |
Huawei, Hisilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-211868 | New test case on malformatted message for IPUPS |
draftCR revised to S3-212334 |
Huawei, Hisilicon | SCAS_5G_IPUPS | Rel-17 |
S3-103-e AI: 4.7 |
revised | [WTS] [JSN] | |
S3-211869 | New security threats on IPUPS malformatted message |
draftCR revised to S3-212335 |
Huawei, Hisilicon | SCAS_5G_IPUPS | Rel-17 |
S3-103-e AI: 4.7 |
revised | [WTS] [JSN] | |
S3-211870 | New test case on de-registering UE after NSSAA revocation | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211871 | New security threats on unauthorized slice access | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-211872 | Reply LS on changes to SoR |
LS out LS To: CT1, CT4 revised to S3-212336 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] | ||
S3-211873 | Clarifications to 5G CIoT K_NG-RAN derivation | CR | Huawei, Hisilicon | 33.501 16.6.0 CR#1118 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211874 | Claifications on mapped security |
CR revised to S3-212337 |
Huawei, Hisilicon | 33.501 16.6.0 CR#1119 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-211875 | Discussion paper on GBA authentication vector service | discussion | Huawei, Hisilicon | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-211876 | UDM support of GBA service | draftCR | Huawei, Hisilicon | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-211877 | Updates to solutoin #3 |
pCR revised to S3-212239 |
Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-211878 | Updates to solutoin #4 | pCR | Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-211879 | Updates to solutoin #5 | pCR | Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-211880 | Add conclusion for key issue #1 | pCR | Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-211881 | Clarification to SoR transparent container |
CR revised to S3-212339 |
Huawei, Hisilicon | 33.501 17.1.0 CR#1120 catF | TEI17 | Rel-17 |
S3-103-e AI: 3 |
revised | [WTS] [JSN] |
S3-211882 | Clarification on a figure and the key activation |
CR revised to S3-212341 |
Huawei, Hisilicon | 33.536 16.3.0 CR#25 catF | eV2XARC | Rel-16 |
S3-103-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-211883 | Resolving EN on the error handling | CR | Huawei, Hisilicon | 33.517 16.2.0 CR#8 catF | SCAS_5G | Rel-16 |
S3-103-e AI: 4.15 |
agreed | [WTS] [JSN] |
S3-211884 | Draft Reply LS on Security consideration to support L2TP with CUPS |
LS out LS To: CT4 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 3 |
merged | [WTS] [JSN] | ||
S3-211885 | UP Security policy requirement on the IMS data network | CR | Huawei, Hisilicon | 33.501 17.1.0 CR#1121 catF | TEI17 | Rel-17 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211886 | Editor's note of the security of 5GLAN services removal in R16 | CR | Huawei, Hisilicon | 33.501 16.6.0 CR#1122 catF | Vertical_LAN_SEC | Rel-16 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211887 | Editor's note of the security of 5GLAN services removal in R17 | CR | Huawei, Hisilicon | 33.501 17.1.0 CR#1123 catA | Vertical_LAN_SEC | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-211888 | Clarification on the Oauth client registration | CR | Huawei, Hisilicon | 33.501 15.12.0 CR#1124 catF | 5GS_Ph1-SEC | Rel-15 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211889 | Clarification on the Oauth client registration and authorization | CR | Huawei, Hisilicon | 33.501 16.6.0 CR#1125 catA | 5GS_Ph1-SEC | Rel-16 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211890 | Discussion on the Authentication, Authorization and Data Protection between EEC and EES/ECS | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211891 | Clarification on the static authorization | CR | Huawei, Hisilicon | 33.501 17.1.0 CR#1126 catF | TEI17 | Rel-17 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-211892 | New WID on Study on Security Aspects of Enhancement of Support for Edge Computing in 5GC |
WID new revised to S3-212342 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 4.21 |
revised | [WTS] [JSN] | ||
S3-211893 | EC: Conclusion for Key issue #1 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211894 | EC: Conclusion for Key issue #2 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211895 | EC: Conclusion for Key issue #3 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-211896 | EC: Conclusion for Key issue #4 and Key issue #5 |
pCR revised to S3-212236 |
Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211897 | EC: Conclusion for Key issue #7 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211898 | EC: Conclusion for Key issue #10 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211899 | Draft LS on TAU reject issue during MME handover |
LS out LS To: CT4 revised to S3-212343 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-211900 | Draft Reply LS on Header Enrichment for HTTPS in PFCP |
LS out LS To: CT4 revised to S3-212344 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 3 |
revised | [WTS] [JSN] | ||
S3-211901 | Requirement of subscribe-notification key issue | pCR | Huawei, Hisilicon | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-211902 | IMS SCAS: living doc for the threats | draftCR | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
approved | [WTS] [JSN] | |
S3-211903 | IMS SCAS: Adding the assets and threats of the new NFs and update existing threats | draftCR | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
approved | [WTS] [JSN] | |
S3-211904 | IMS SCAS: living doc for the threats | draftCR | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
withdrawn | [WTS] [JSN] | |
S3-211905 | Update the test case on bidding down and add reqirements on new NFs | pCR | Huawei, Hisilicon | 33.226 0.4.0 | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-211906 | Editorial change on TS 33.516 | pCR | Huawei, Hisilicon | 33.226 0.4.0 | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
approved | [WTS] [JSN] |
S3-211907 | Presentation of Specification to TSG: TS 33.226, Version 0.5.0 | pCR | Huawei, Hisilicon | 33.226 0.4.0 | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
noted | [WTS] [JSN] |
S3-211908 | AKMA Anchor Function selection clause |
CR revised to S3-212359 |
Ericsson | 33.535 17.1.0 CR#79 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-211909 | New WID on IoT Ua* protocol profiles for AKMA | WID new | Ericsson, China Mobile | Rel-17 |
S3-103-e AI: 4.21 |
noted | [WTS] [JSN] | ||
S3-211910 | IETF OSCORE as AKMA Ua* protocol | CR | Ericsson, DT | 33.535 17.1.0 CR#80 catB | DUMMY | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-211911 | Extending the Ua security protocol namespace to include AKMA Ua* protocols | CR | Ericsson | 33.22 17.0.0 CR#210 catB | DUMMY | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-211912 | Handling of AKMA keys in the UE | discussion | Ericsson | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
noted | [WTS] [JSN] | |
S3-211913 | AKMA UE aspects |
CR revised to S3-212328 |
Ericsson | 33.535 17.1.0 CR#81 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-211914 | Update to solution #2 |
pCR revised to S3-212156 |
Ericsson | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-211915 | AMF reallocation via direct NAS reroute: handling of UL NAS COUNT corresponding to RR message derivation | discussion | Ericsson | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] | ||
S3-211916 | AMF re-allocation: Analysis of solutions | discussion | Ericsson | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-211917 | AMF re-allocation: Conclusion | pCR | Ericsson | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-211918 | AMF re-allocation: Solution #9 updates |
pCR revised to S3-212157 |
Ericsson | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-211919 | New WID on the security of AMF re-allocation | WID new | Ericsson | Rel-17 |
S3-103-e AI: 4.21 |
noted | [WTS] [JSN] | ||
S3-211920 | AMF re-allocation: Discussion about the WID | discussion | Ericsson | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-211921 | Authentication enhancements: TR editorials | pCR | Ericsson | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-211922 | Authentication enhancements: Clause 4 | pCR | Ericsson | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-211923 | New WID on Authentication enhancements in 5GS | WID new | Ericsson | Rel-17 |
S3-103-e AI: 4.21 |
noted | [WTS] [JSN] | ||
S3-211924 | Authentication enhancements: Discussion about the WID | discussion | Ericsson | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] | |
S3-211925 | Living document for GBA_5G: draftCR to TS 33.220: SBA support for Zh and Zn interfaces | draftCR | Ericsson | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-211926 | Living document for GBA_5G: draftCR to TS 33.223: SBA support for Zpn | draftCR | Ericsson | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-211927 | Discussion on GBA support in UDM | discussion | Ericsson | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-211928 | pCR to living document for TS 33.220: Support for GBA in UDM | other | Ericsson | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-211929 | pCR to living document for TS 33.223: Support for GBA in UDM | other | Ericsson | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-211930 | DRAFT LS on SBA for GBA |
LS out LS To: SA2 |
Ericsson | GBA_5G | Rel-17 |
S3-103-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-211931 | pCR to TR33.847- Conclusion of KI#12 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211932 | Editor Note removal for Solution#10 |
pCR revised to S3-212250 |
Nokia, Nokia Shanghai-Bell | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-211933 | Evaluation for Solution#10 | pCR | Nokia, Nokia Shanghai-Bell | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-211934 | Work Item Exception sheet for BEST_5G Rel 17 | WI exception request | VODAFONE Group Plc | BEST_5G | Rel-17 |
S3-103-e AI: 4.11 |
agreed | [WTS] [JSN] | |
S3-211935 | Alignment of requirements with specification updates |
CR revised to S3-212395, S3-212871 |
Nokia, Nokia Shanghai Bell | 33.117 16.6.0 CR#71 catF | SCAS_5G | Rel-16 |
S3-103-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-211936 | SCP-specific adaptations - technical baseline | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211937 | SCP-specific adaptations - Operating systems | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211938 | SCP-specific adaptations - Web servers | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211939 | SCP-specific adaptations - Network devices | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211940 | SCP-specific adaptations - NFs in SBA | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211941 | SCP test cases | pCR | Nokia, Nokia Shanghai Bell, NTT Docomo | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211942 | Assets and Threats specific to SCP | CR | Nokia, Nokia Shanghai Bell | 33.926 17.0.0 CR#42 catB | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211943 | SCP Test on Token forwarded to the correct NFp | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211944 | SCP Test on Correct token forwarded to NFp | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
withdrawn | [WTS] [JSN] |
S3-211945 | SCP-specific adaptations - technical baseline | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
approved | [WTS] [JSN] |
S3-211946 | SCP-specific adaptations - Operating systems | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
approved | [WTS] [JSN] |
S3-211947 | SCP-specific adaptations - Web servers | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
approved | [WTS] [JSN] |
S3-211948 | SCP-specific adaptations - Network devices | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
approved | [WTS] [JSN] |
S3-211949 | SCP-specific adaptations - NFs in SBA | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
approved | [WTS] [JSN] |
S3-211950 | SCP test cases |
pCR revised to S3-212121 |
Nokia, Nokia Shanghai Bell, NTT Docomo | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
revised | [WTS] [JSN] |
S3-211951 | Assets and Threats specific to SCP | CR | Nokia, Nokia Shanghai Bell | 33.926 17.0.0 CR#43 catB | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
not pursued | [WTS] [JSN] |
S3-211952 | SCP Test on Token forwarded to the correct NFp | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
noted | [WTS] [JSN] |
S3-211953 | SCP Test on Correct token forwarded to NFp | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
noted | [WTS] [JSN] |
S3-211954 | New KI: DoS on Network Slice Quota | pCR | US National Security Agency, Johns Hopkins University APL, CISA ECD, NIST | 33.874 0.0.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-211955 | SCP Requirement and test case for protection over internal interfaces | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
noted | [WTS] [JSN] |
S3-211956 | Update to solution #6 |
pCR revised to S3-212143 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211957 | Update to solution #21 |
pCR revised to S3-212144 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211958 | Update to solution #35 |
pCR revised to S3-212145 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211959 | Conclusion on key issue #3 and key issue #4 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211960 | Update to evaluation to solution #1 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211961 | Update to evaluation to solution #15 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-211962 | Update to evaluation to solution #10 |
pCR revised to S3-212146 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211963 | Update to evaluation to solution #13 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211964 | Conclusion on key issue #2 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211965 | Way forward for draft-ietf-emu-rfc5448bis | discussion | Ericsson | Rel-15 |
S3-103-e AI: 4.22 |
noted | [WTS] [JSN] | ||
S3-211966 | pCR to 33.846: conclusion for KI #2.1 | pCR | THALES | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211967 | pCR to 33.846: conclusion for KI#4.1 | pCR | THALES | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-211968 | KI1 Security requirements for authentication of NRF and NFp in indirect commuication | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-211969 | Sol1 deployment scenarios |
pCR revised to S3-212298 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-211970 | ENs on Sol1 Service response verification in model C |
pCR revised to S3-212299 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-211971 | Threats and requirements to KI3 on Service access authorization in Subscribe-Notify | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-211972 | Solution on URI verification and notification acceptance | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-211973 | KI on Access token usage by all NFs of an NF Set | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-211974 | Solution on Access token request for NF Set |
pCR revised to S3-212302 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-211975 | EN resolution on sol 2 - NFc authorizing SCP to act on its behalf |
pCR revised to S3-212300 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-211976 | Evaluation on sol 2 - NFc authorizing SCP to act on its behalf |
pCR revised to S3-212301 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-211977 | Evaluation to sol 3 - proof of possession of CCA NFc authorizes the SCP to act on behalf of an NFc | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
merged | [WTS] [JSN] |
S3-211978 | KI on Roaming case for token-based authorization | pCR | Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-211979 | Trust model |
pCR revised to S3-212303 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-211980 | N32-c and N32-f clarification R16 |
CR revised to S3-212282 |
Nokia, Nokia Shanghai Bell | 33.501 16.6.0 CR#1127 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211981 | N32-c and N32-f clarification R17 |
CR revised to S3-212284 |
Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#1128 catA | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211982 | Deployment models R16 |
CR revised to S3-212285 |
Nokia, Nokia Shanghai Bell | 33.501 16.6.0 CR#1129 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211983 | Deployment models R17 |
CR revised to S3-212286 |
Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#1130 catA | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.16 |
revised | [WTS] [JSN] |
S3-211984 | Discussion of GSMA LS S3-211383 Prevention of attacks on sliced core | discussion | Nokia, Nokia Shanghai Bell | Rel-17 |
S3-103-e AI: 4.19 |
noted | [WTS] [JSN] | ||
S3-211985 | Prevention of attacks on slice core by CCA modifications - Rel-16 |
CR revised to S3-212823 |
Nokia, Nokia Shanghai Bell | 33.501 16.6.0 CR#1131 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-211986 | Prevention of attacks on slice core by CCA modifications - Rel-17 |
CR revised to S3-212824 |
Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#1132 catA | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.19 |
not pursued | [WTS] [JSN] |
S3-211987 | pCR to TR 33.839: Using TLS with Edge Security Service to protect edge interfaces |
pCR revised to S3-212225 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211988 | Removal of ENs for draft-ietf-emu-rfc5448bis - Rel-15 |
CR revised to S3-212330 |
Ericsson | 33.501 15.12.0 CR#1133 catF | 5GS_Ph1-SEC | Rel-15 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-211989 | Process for SA3#103e meeting |
other revision of S3-211352 |
SA WG3 Vice Chairs |
S3-103-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-211990 | Removal of ENs for draft-ietf-emu-rfc5448bis -Rel-16 |
CR revised to S3-212331 |
Ericsson | 33.501 16.6.0 CR#1134 catA | 5GS_Ph1-SEC | Rel-16 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-211991 | Removal of ENs for draft-ietf-emu-rfc5448bis- Rel-17 |
CR revised to S3-212346 |
Ericsson | 33.501 17.1.0 CR#1135 catA | 5GS_Ph1-SEC | Rel-17 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-211992 | Discussion on 256-bit algorithms based on SNOW 3G or SNOW V | discussion | Ericsson, AT&T, BT plc, Deutsche Telekom AG |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-211993 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #5 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211994 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211995 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 |
pCR revised to S3-212206 |
Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211996 | eEDGE: Conclusion for Key Issue #4 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-211997 | ProSe: Resolving an Editor’s Note in KI #1 | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211998 | ProSe: New Key Issue on Security Policies for PC5 Connection | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-211999 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212000 | eNPN: Conclusion on KI#8 with Solution#18 Updating |
pCR revised to S3-212207 |
Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-212001 | eNPN: Solution of Security Mechansim for UP Provisioning of Credentials | pCR | Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212002 | eNPN: New KI of Security Protection for the Update of Preferred SNPN List | pCR | Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212003 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection |
LS out LS To: SG2 revised to S3-212208 |
Xiaomi Technology | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
revised | [WTS] [JSN] | |
S3-212004 | MUSIM: New Solution for Key Issue #1 for RRC_Idle UE | pCR | Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-212005 | MUSIM: New Solution for Key Issue #1 for RRC_Inactive UE | pCR | Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
noted | [WTS] [JSN] |
S3-212006 | MUSIM: Conclusion for Key Issue #2 |
pCR revised to S3-212209 |
Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
revised | [WTS] [JSN] |
S3-212007 | eNS2: Add Threat Analysis to KI #1 |
pCR revised to S3-212210 |
Xiaomi Technology | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
revised | [WTS] [JSN] |
S3-212008 | eNS2: New Key Issue on Primary Authentication with NSAC | pCR | Xiaomi Technology | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
noted | [WTS] [JSN] |
S3-212009 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #5 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212010 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212011 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212012 | eEDGE: Conclusion for Key Issue #4 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212013 | ProSe: Resolving an Editor’s Note in KI #1 | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212014 | ProSe: New Key Issue on Security Policies for PC5 Connection | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212015 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212016 | eNPN: Conclusion on KI#8 with Solution#18 Updating | pCR | Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-212017 | eNPN: Solution of Security Mechansim for UP Provisioning of Credentials | pCR | Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-212018 | eNPN: New KI of Security Protection for the Update of Preferred SNPN List | pCR | Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-212019 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection |
LS out LS To: SG2 |
Xiaomi Technology | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] | |
S3-212020 | MUSIM: New Solution for Key Issue #1 for RRC_Idle UE | pCR | Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
S3-212021 | MUSIM: New Solution for Key Issue #1 for RRC_Inactive UE | pCR | Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
S3-212022 | MUSIM: Conclusion for Key Issue #2 | pCR | Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
S3-212023 | eNS2: Add Threat Analysis to KI #1 | pCR | Xiaomi Technology | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
withdrawn | [WTS] [JSN] |
S3-212024 | eNS2: New Key Issue on Primary Authentication with NSAC | pCR | Xiaomi Technology | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
withdrawn | [WTS] [JSN] |
S3-212025 | Reply LS on 256-bit algorithms based on SNOW 3G or SNOW V |
LS out LS is reply to S3-211407 / SAGE (20) 14 LS To: ETSI SAGE |
Ericsson, AT&T, BT plc, Deutsche Telekom AG |
S3-103-e AI: 3 |
merged | [WTS] [JSN] | |||
S3-212026 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212027 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212028 | eEDGE: Conclusion for Key Issue #4 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212029 | ProSe: Resolving an Editor’s Note in KI #1 | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212030 | ProSe: New Key Issue on Security Policies for PC5 Connection | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212031 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212032 | eNPN: Conclusion on KI#8 with Solution#18 Updating | pCR | Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-212033 | eNPN: Solution of Security Mechansim for UP Provisioning of Credentials | pCR | Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-212034 | eNPN: New KI of Security Protection for the Update of Preferred SNPN List | pCR | Xiaomi Technology | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-212035 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection |
LS out LS To: SG2 |
Xiaomi Technology | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] | |
S3-212036 | MUSIM: New Solution for Key Issue #1 for RRC_Idle UE | pCR | Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
S3-212037 | MUSIM: New Solution for Key Issue #1 for RRC_Inactive UE | pCR | Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
S3-212038 | MUSIM: Conclusion for Key Issue #2 | pCR | Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
S3-212039 | eNS2: Add Threat Analysis to KI #1 | pCR | Xiaomi Technology | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
withdrawn | [WTS] [JSN] |
S3-212040 | eNS2: New Key Issue on Primary Authentication with NSAC | pCR | Xiaomi Technology | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
withdrawn | [WTS] [JSN] |
S3-212041 | Conclusions for KI#10 "Authorization during Edge Data Network change" | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212042 | Conclusions for KI#7 "Security of Network Information Provisioning to Local Applications with low latency procedure" | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212043 | Update Solution #17: Resolving EN on TLS ID | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212044 | Update to Solution #17: Resolving EN on Token Usage | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212045 | Update to Solution #17: Resolving EN on Multiple GPSI |
pCR revised to S3-212226 |
Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212046 | Evaluation of Solution #17 |
pCR revised to S3-212227 |
Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212047 | Discussion on IP address to GPSI translation | discussion | Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |
S3-212048 | Reply LS on IP address to GPSI translation |
LS out LS is reply to S3-211392/S2-2101307 LS To: SA2, SA6 revised to S3-212355 |
Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] | |
S3-212049 | LS on EAS and ECS identifiers |
LS out LS To: SA6 |
Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |
S3-212050 | Update to solution #2 |
pCR revised to S3-212222 |
Ericsson | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-212051 | Update to Solution #17: Handling multiple GPSI in IP address to GPSI translation | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212052 | Intro update | pCR | Nokia, Nokia Shanghai Bell | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-212053 | Security for user regroup | CR | CATT | 33.18 17.2.0 CR#171 catB | MCXSec2 | Rel-17 |
S3-103-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-212054 | pCR: Conclusion for KI #1 on addressing security threat against KAUSF | pCR | CableLabs | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-212055 | Removal of Editor’s Note of Solution#5 | pCR | Lenovo, Motorola Mobility | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212056 | pCR: Conclusion for KI #1 on addressing security threat against KAUSF | pCR | CableLabs | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212057 | Solution on Authorization of Data Consumers for data access via DCCF |
pCR revised to S3-212221 |
Ericsson | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212058 | Solution on Authorization of Data Consumers for data access via DCCF through Messaging Framework | pCR | Ericsson | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212059 | New KI Untrusted DCCF for secure data collection | pCR | Ericsson | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212060 | Solution for Untrusted DCCF for secure data collection | pCR | Ericsson | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212061 | Security updates for algorithms and protocols in 33.220 | CR | Ericsson | 33.22 17.0.0 CR#211 catB | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-212062 | Security updates for algorithms and protocols in 33.222 | CR | Ericsson | 33.222 16.1.0 CR#54 catB | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-212063 | Security updates for algorithms and protocols in 33.223 | CR | Ericsson | 33.223 16.0.0 CR#30 catB | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
agreed | [WTS] [JSN] |
S3-212064 | Security updates for algorithms and protocols in 33.210 | CR | Ericsson | 33.21 16.4.0 CR#71 catB | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-212065 | Security updates for algorithms and protocols in 33.203 | CR | Ericsson | 33.203 16.1.0 CR#258 catB | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-212066 | Security updates for algorithms and protocols in 33.310 | CR | Ericsson | 33.31 16.7.0 CR#119 catB | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-212067 | Security updates for algorithms and protocols in 33.501 | CR | Ericsson | 33.501 17.1.0 CR#1136 catB | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
not pursued | [WTS] [JSN] |
S3-212068 | Removal of Editor’s Notes | pCR | Lenovo, Motorola Mobility | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212069 | Type 1 threat | pCR | Futurewei Technologies | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212070 | Typye 2 Threats | pCR | Futurewei Technologies | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212071 | Type 3 Threats | pCR | Futurewei Technologies | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212072 | A new onboarding solution addressing KI#2 | pCR | Lenovo, Motorola Mobility | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-212073 | Discussion on refresh of Kaf and Kakma | discussion | Samsung | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
noted | [WTS] [JSN] | |
S3-212074 | Refresh of Kaf and Kakma | CR | Samsung | 33.535 17.1.0 CR#82 catB | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212075 | Discussion on authorization of Kaf refresh | discussion | Samsung | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
noted | [WTS] [JSN] | |
S3-212076 | Network provides authorization to AF for Kaf key refresh | CR | Samsung | 33.535 17.1.0 CR#83 catB | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
not pursued | [WTS] [JSN] |
S3-212077 | Discussion on detection of MitM attack using NWDAF | discussion | Samsung | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] | |
S3-212078 | Solution on analytics for MitM attack detection | pCR | Samsung | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212079 | Solution on analytics for DoS attack detection | pCR | Samsung | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212080 | Solution on user's consent for exposure of information to Edge Applications | pCR | Samsung | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-212081 | Solution on user consent for UE data collection | pCR | Samsung | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-212082 | [EDGE] Resolving EN1 in Solution#3 | pCR | Samsung | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212083 | [EDGE] Resolving EN3 in Solution#3 | pCR | Samsung | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212084 | [EDGE] Evaluation for solution#3 | pCR | Samsung | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212085 | Update for solution#1: Optimized Authorization |
pCR revised to S3-212135 |
Samsung | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212086 | [5gmsg] Transport security protection for MSGin5G-3 interface | pCR | Samsung | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212087 | [5gmsg] Resolving ENs in solution#1 | pCR | Samsung | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212088 | [5gmsg] Resolving ENs in solution#5 | pCR | Samsung | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212089 | [5gmsg] Resolving ENs in solution#6 |
pCR revised to S3-212136 |
Samsung | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-212090 | [5gmsg] Resolving ENs in solution#7 |
pCR revised to S3-212137 |
Samsung | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-212091 | CR on signalling Algorithm Selection | CR | Samsung | 33.18 17.2.0 CR#172 catF | MCXSec2 | Rel-17 |
S3-103-e AI: 4.9 |
agreed | [WTS] [JSN] |
S3-212092 | Correction to FC values in range for future use in 3GPP specifications | CR | Samsung | 33.22 17.0.0 CR#212 catF | TEI17 | Rel-17 |
S3-103-e AI: 4.22 |
merged | [WTS] [JSN] |
S3-212093 | Update to solution#9 |
pCR revised to S3-212138 |
Samsung | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-212094 | New solution for key issue#1: Authentication of NF service producer in indirect communication |
pCR revised to S3-212292 |
Samsung | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212095 | New solution for key issue#3: Authorization of notification request | pCR | Samsung | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-212096 | Updates to solution#13 on Key refresh mechanism | pCR | Samsung | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212097 | Updates to solution#13 on support for multiple MB-SMF |
pCR revised to S3-212139 |
Samsung | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212098 | Updates to solution#13 on MBS security algorithm selection |
pCR revised to S3-212140 |
Samsung | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-212099 | Comparison of solutions and propose way forward | discussion | Samsung | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-212100 | Updates to solution#5 | pCR | Samsung | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212101 | Removal of Editor's Note in Solution#5 | pCR | Samsung | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212102 | Updates to evaluation in solution#5 | pCR | Samsung | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-212103 | Rel16-Handling of Kausf upon successful primary authentication |
CR revised to S3-212289 |
Samsung, NEC, Nokia, Nokia Shanghai Bell, Intel | 33.501 16.6.0 CR#1137 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-212104 | Rel17-Handling of Kausf upon successful primary authentication |
CR revised to S3-212290 |
Samsung, NEC, Nokia, Nokia Shanghai Bell, Intel | 33.501 17.1.0 CR#1138 catA | TEI16 | Rel-17 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] |
S3-212105 | Updates to KI#1 & KI#7 | pCR | Samsung | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-212106 | [Draft] LS on feasibility of addressing the attacks against 5G UE over radio interfaces |
LS out LS To: RAN2 |
Samsung | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
noted | [WTS] [JSN] | |
S3-212107 | [IAB] Unprotected BAP Control PDU exchange |
pCR revised to S3-212141 |
Samsung | 33.824 0.8.0 | FS_NR_IAB_Sec | Rel-17 |
S3-103-e AI: 5.18 |
revised | [WTS] [JSN] |
S3-212108 | [UC3S] Update to Conclusion |
pCR revised to S3-212142 |
Samsung | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-212109 | [EDGE] Conclusion for KI#1, KI#2 and KI#6 | pCR | Samsung | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212110 | Clause 6.1 | pCR | Futurewei Technologies | 33.818 0.11.0 | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212111 | Key Issue on subscription identifier privacy | pCR | Lenovo, Motorola Mobility | 33.881 0.0.0 | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
merged | [WTS] [JSN] |
S3-212112 | eEDGE: Additional Threat and Requirement for KI #10 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212113 | Solution on NSWO authentication | pCR | Lenovo, Motorola Mobility | 33.881 0.0.0 | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
noted | [WTS] [JSN] |
S3-212114 | Update to solution #32 |
pCR revised to S3-212147 |
Philips International B.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212115 | UP IP: Update to solution #21 (Interworking handover from EPS to 5GS) |
pCR revised to S3-212133 |
Ericsson | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-212116 | UP IP: Update to solution #24 Interworking handover from 5GS to EPS |
pCR revised to S3-212134 |
Ericsson | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
revised | [WTS] [JSN] |
S3-212117 | UP IP: Update to solution #30 | pCR | Ericsson | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-212118 | Removal of Editor’s Note of Solution#4 | pCR | Lenovo, Motorola Mobility | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212119 | Correction of Annex A.13 | CR | Ericsson | 33.501 16.6.0 CR#1139 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212120 | Addition of Key Issue 26 Text |
pCR revised to S3-212388 |
BT plc | 33.848 0.7.0 | FS_SIV | Rel-16 |
S3-103-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-212121 | SCP test cases |
pCR revision of S3-211950 revised to S3-212295 |
Nokia, Nokia Shanghai Bell, NTT Docomo | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
revised | [WTS] [JSN] |
S3-212122 | Addition of Key Issue 25 Text |
pCR revised to S3-212389 |
BT plc | 33.848 0.7.0 | FS_SIV | Rel-16 |
S3-103-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-212123 | S on user consent revocation to SA2 |
LS out LS To: SA2 |
Nokia |
S3-103-e AI: 5.14 |
approved | [WTS] [JSN] | |||
S3-212124 | LS on Clarification of AMF Reallocation and network slice selection |
LS out LS To: SA2 |
Lenovo |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] | |||
S3-212125 | Conclusion on UE-UE |
pCR revision of S3-211448 |
Nokia, Nokia Shanghai Bell | 33.851 0.5.0 | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-212126 | TR_33.851_IIoT_Sec | draft TR | Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-212127 | Updated Solution #23: Initial key with validity time |
pCR revision of S3-211597 |
KPN N.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212128 | TR 33.854 KI#4 conclusion |
pCR revision of S3-211489 |
InterDigital, Europe, Ltd., Huawei, HiSilicon | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212129 | TR 33.847 sol#10 update |
pCR revision of S3-211484 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212130 | TR 33.847 sol#24 evaluation |
pCR revision of S3-211485 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212131 | TR 33.847 sol#25 evaluation |
pCR revision of S3-211486 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212132 | Updated Solution #22: Representation of identities during broadcast |
pCR revision of S3-211463 |
KPN N.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212133 | UP IP: Update to solution #21 (Interworking handover from EPS to 5GS) |
pCR revision of S3-212115 |
Ericsson | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-212134 | UP IP: Update to solution #24 Interworking handover from 5GS to EPS |
pCR revision of S3-212116 |
Ericsson | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-212135 | Update for solution#1: Optimized Authorization |
pCR revision of S3-212085 |
Samsung | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212136 | [5gmsg] Resolving ENs in solution#6 |
pCR revision of S3-212089 |
Samsung | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212137 | [5gmsg] Resolving ENs in solution#7 |
pCR revision of S3-212090 |
Samsung | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212138 | Solution to reroute 5G NAS security context via RAN |
pCR revision of S3-212093 |
Samsung | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212139 | Updates to solution#13 on support for multiple MB-SMF |
pCR revision of S3-212097 |
Samsung | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212140 | Updates to solution#13 on MBS security algorithm selection |
pCR revision of S3-212098 |
Samsung | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212141 | [IAB] Unprotected BAP Control PDU exchange |
pCR revision of S3-212107 |
Samsung | 33.824 0.8.0 | FS_NR_IAB_Sec | Rel-17 |
S3-103-e AI: 5.18 |
approved | [WTS] [JSN] |
S3-212142 | [UC3S] Update to Conclusion |
pCR revision of S3-212108 |
Samsung | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-212143 | Update to solution #6 |
pCR revision of S3-211956 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212144 | Update to solution #21 |
pCR revision of S3-211957 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212145 | Update to solution #35 |
pCR revision of S3-211958 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212146 | Update to evaluation to solution #10 |
pCR revision of S3-211962 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212147 | Update to solution #32 |
pCR revision of S3-212114 |
Philips International B.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212148 | Scope for 5G NSWO TR |
pCR revision of S3-211516 |
Nokia, Nokia Shanghai-Bell | 33.881 0.0.0 | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-212149 | Introduction for 5G NSWO TR |
pCR revision of S3-211517 |
Nokia, Nokia Shanghai-Bell | 33.881 0.0.0 | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-212150 | KI: Support of EAP Authentication for 5G NSWO |
pCR revision of S3-211518 |
Nokia, Nokia Shanghai-Bell | 33.881 0.0.0 | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
approved | [WTS] [JSN] |
S3-212151 | New TR33.811 for 5G NSWO | draft TR | Nokia, Nokia Shanghai Bell | FS_NSWO_5G | Rel-17 |
S3-103-e AI: 5.22 |
approved | [WTS] [JSN] | |
S3-212152 | pCR to TR33.847- Update Solution#29 |
pCR revision of S3-211847 |
CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212153 | pCR to TR33.847- Update Solution#30 |
pCR revision of S3-211848 |
CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212154 | Draft TR 33.847 v0.6.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-212155 | Draft TR 33.864 v0.5.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson España S.A. | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] | |
S3-212156 | Update to solution #2 |
pCR revision of S3-211914 |
Ericsson | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212157 | AMF re-allocation: Solution #9 updates |
pCR revision of S3-211918 |
Ericsson | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212158 | Reply LS on RAT type for network monitoring |
LS out LS is reply to S3-211417 LS To: SA WG2; SA WG6 |
S2-2103237 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] | |||
S3-212159 | Reply LS on Transaction Information - Dispersion Analytics |
LS out LS is reply to S3-211422 LS To: SA WG2 revision of S3-211698 |
Nokia, Nokia Shanghai Bell | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] | |
S3-212160 | Solution on Processing of tampered data |
pCR revision of S3-211693 |
Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212161 | Solution on Authorization of NF Service Consumers for data access via DCCF |
pCR revision of S3-211696 |
Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212162 | Solution on Authorization of NF Service Consumers to access data from ADRF via DCCF |
pCR revision of S3-211697 |
Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212163 | EN Resolution Anomolous NF Behaviour |
pCR revision of S3-211691 |
Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212164 | Reply LS on MOBIKE usage in IAB |
LS out LS is reply to S3-211362 LS To: RAN3 revision of S3-211520 |
Nokia, Nokia Shanghai-Bell | Rel-17 |
S3-103-e AI: 5.18 |
approved | [WTS] [JSN] | ||
S3-212165 | Conclusion to Key issue 1,2 |
pCR revision of S3-211595 |
Intel K.K. | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-212166 | Updates to solution 14: Removal of Editor's notes: Certificate Handling |
pCR revision of S3-211573 |
Intel K.K. | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212167 | Updates to solution 12 |
pCR revision of S3-211589 |
Intel K.K.,Huawei | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212168 | draft TR Study on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules | draft TR | Intel K.K. | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
approved | [WTS] [JSN] | |
S3-212169 | Evaluation of Solution #18 |
pCR revision of S3-211798 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212170 | EN resolution of Solution #19 |
pCR revision of S3-211802 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212171 | New Key Issue on security policy handling for 5G Prose services |
pCR revision of S3-211803 |
Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212172 | EN resolution of Solution #34 |
pCR revision of S3-211804 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212173 | EN resolution of Solution #12 |
pCR revision of S3-211812 |
Qualcomm Incorporated | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212174 | Evaluation of Solution #2 |
pCR revision of S3-211813 |
Qualcomm Incorporated | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212175 | Evaluation of Solution 13 |
pCR revision of S3-211525 |
LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212176 | Updates in Solution 4 |
pCR revision of S3-211524 |
LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212177 | New solution for Key issue#4 |
pCR revision of S3-211569 |
ZTE Corporation | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212178 | TR 33.850 for MBS security | draft TR | Huawei, Hisilicon | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] | |
S3-212179 | New solution for AMF re-allocation |
pCR revision of S3-211572 |
ZTE Corporation | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212180 | Conclusion for the key issue#6 |
pCR revision of S3-211566 |
ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212181 | Evaluation of solution #3 |
pCR revision of S3-211606 |
Huawei, HiSilicon, InterDigital | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212182 | Evaluation of solution #5 | pCR | Huawei, HiSilicon, InterDigital | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
withdrawn | [WTS] [JSN] |
S3-212183 | Conclusion for KI#1 (AA) |
pCR revision of S3-211608 |
Huawei, HiSilicon, InterDigital, Lenovo, Motorola Mobility | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212184 | Conclusion for KI#2 (pairing) |
pCR revision of S3-211609 |
Huawei, HiSilicon, InterDigital, Lenovo, Motorola Mobility | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212185 | Conclusion for KI#7 (C2) |
pCR revision of S3-211610 |
Huawei, HiSilicon, InterDigital, Lenovo, Motorola Mobility | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212186 | Draft TR33.874 eNS2_SEC |
draft TR revised to S3-212279 |
Huawei, HiSilicon | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
revised | [WTS] [JSN] | |
S3-212187 | Discussion on slice issues in core networks |
discussion revision of S3-211611 |
Huawei, HiSilicon |
S3-103-e AI: 4.19 |
noted | [WTS] [JSN] | |||
S3-212188 | Propose evaluation to Solution #32 |
pCR revision of S3-211621 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212189 | Solution Evaluation for solution 15 |
pCR revision of S3-211627 |
Huawei, HiSilicon, Ericsson, Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212190 | Solution Evaluation for solution 8 |
pCR revision of S3-211628 |
Huawei, HiSilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212191 | Solution Evaluation for solution 11 |
pCR revision of S3-211629 |
Huawei, HiSilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212192 | Update to the solution 11 |
pCR revision of S3-211632 |
Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212193 | Conclusion for key issue 3 |
pCR revision of S3-211634 |
Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-212194 | Solution Update for Solution #28 |
pCR revision of S3-211649 |
Huawei, HiSilicon | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-212195 | Conclusion for Key Issue #7 |
pCR revision of S3-211650 |
Huawei, HiSilicon | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-212196 | LS on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS |
LS out LS To: SA2 LS reply in S2-2105697 revision of S3-211651 |
Huawei, HiSilicon |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] | |||
S3-212197 | Solution Update for Solution #5 |
pCR revision of S3-211652 |
Huawei, HiSilicon | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212198 | Evaluation for Solution #12 |
pCR revision of S3-211653 |
Huawei, HiSilicon | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212199 | Solution Update for Solution #2 |
pCR revision of S3-211654 |
Huawei, HiSilicon | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-212200 | Update on Observations related to Regulations |
pCR revision of S3-211655 |
Huawei, HiSilicon | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-212201 | Add Security Requirement for Key Issue #3 |
pCR revision of S3-211656 |
Huawei, HiSilicon, Apple, Nokia, Nokia Shanghai Bell | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-212202 | Delete EN of Solution#2 |
pCR revision of S3-211661 |
Huawei, HiSilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212203 | Add conclusion to KI#10 |
pCR revision of S3-211663 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212204 | Reply LS on R17 Layer-2 SL Relay |
LS out LS is reply to S3-211432 LS To: RAN2 revision of S3-211665 |
Huawei, HiSilicon | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] | ||
S3-212205 | Draft TR 33.867 | draft TR | Huawei, HiSilicon | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
approved | [WTS] [JSN] | |
S3-212206 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 |
pCR revision of S3-211995 |
Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212207 | eNPN: Conclusion on KI#8 with Solution#18 Updating |
pCR revision of S3-212000 |
Xiaomi Technology,Huawei | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212208 | Reply LS on updating the Credentials Holder controlled lists for SNPN selection |
LS out LS is reply to S3-211395,S3-211439 LS To: SA2 revision of S3-212003 |
Xiaomi Technology | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] | |
S3-212209 | MUSIM: Conclusion for Key Issue #2 |
pCR revision of S3-212006 |
Xiaomi Technology | 33.873 0.3.0 | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
approved | [WTS] [JSN] |
S3-212210 | eNS2: Add Threat Analysis to KI #1 |
pCR revision of S3-212007 revised to S3-212212 |
Xiaomi Technology | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
revised | [WTS] [JSN] |
S3-212211 | Evaluation of solution #5 |
pCR revision of S3-211607 |
Huawei, HiSilicon, InterDigital | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212212 | eNS2: Add Threat Analysis to KI #1 |
pCR revision of S3-212210 |
Xiaomi Technology | 33.874 0.1.0 | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
approved | [WTS] [JSN] |
S3-212213 | Add an evaluation for solution #10 |
pCR revision of S3-211807 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212214 | draft TR 33.866 0.5.0 | draft TR | China Mobile E-Commerce Co. | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] | |
S3-212215 | draft TR 33.862 0.5.0 | draft TR | China Mobile E-Commerce Co. | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
approved | [WTS] [JSN] | |
S3-212216 | Add evaluation to solution #4 |
pCR revision of S3-211838 |
China Mobile | 33.862 0.4.0 | FS_SEC_5GMSG | Rel-17 |
S3-103-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-212217 | pCR to TR33.845 - Resolution of editors notes for solutions 28 29 30 |
pCR revision of S3-211718 |
VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-212218 | pCR to TR33.853 - Resolution of editors notes in Conclusions and Recommendations |
pCR revision of S3-211736 |
VODAFONE Group Plc | 33.853 1.5.0 | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] |
S3-212219 | new draft TR33.853 v1.6.0 | draft TR | VODAFONE Group Plc | FS_UP_IP_Sec | Rel-17 |
S3-103-e AI: 5.3 |
approved | [WTS] [JSN] | |
S3-212220 | draft TR 33.857 v0.6.0 | draft TR | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] | |
S3-212221 | Solution on Authorization of Data Consumers for data access via DCCF |
pCR revision of S3-212057 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212222 | Update to solution #2 |
pCR revision of S3-212050 |
Ericsson | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212223 | pCR to 33.839: GBA-based solution for EEC authentication and authorization framework with ECS and EES |
pCR revision of S3-211444 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212224 | pCR to 33.839: Using TLS with GBA to protect edge interfaces |
pCR revision of S3-211445 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212225 | pCR to TR 33.839: Using TLS with Edge Security Service to protect edge interfaces |
pCR revision of S3-211987 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212226 | Update to Solution #17: Resolving EN on Multiple GPSI |
pCR revision of S3-212045 |
Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212227 | Evaluation of Solution #17 |
pCR revision of S3-212046 |
Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212228 | Update to Solution #4 |
pCR revision of S3-211737 |
Lenovo, Motorola Mobility | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212229 | Update to Solution #6 |
pCR revision of S3-211738 |
Lenovo, Motorola Mobility | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212230 | Update to Solution #7 |
pCR revision of S3-211739 |
Lenovo, Motorola Mobility | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212231 | Remark to address a potential security issue in Solution #4 (LTE security-based mechanism for 5G ProSe restricted discovery) |
pCR revision of S3-211591 |
Philips International B.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212232 | Additions in Solution #9 |
pCR revision of S3-211590 |
Philips International B.V. | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212233 | Draft 33.824 v0.9.0 | draft TR | Samsung | FS_NR_IAB_Sec | Rel-17 |
S3-103-e AI: 5.18 |
approved | [WTS] [JSN] | |
S3-212234 | add evaluation to solution #23 |
pCR revision of S3-211853 |
Huawei, Hisilicon, Qualcomm | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212235 | EN removal of solution #9 |
pCR revision of S3-211859 |
Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212236 | EC: Conclusion for Key issue #4 and Key issue #5 |
pCR revision of S3-211896 |
Huawei, Hisilicon,Xiaomi | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212237 | New solution to key issue #3.3 |
pCR revision of S3-211865 |
Huawei, Hisilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212238 | New solution to key issue #1.5 |
pCR revision of S3-211867 |
Huawei, Hisilicon | 33.866 0.4.0 | FS_eNA_SEC | Rel-17 |
S3-103-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212239 | Updates to solutoin #3 |
pCR revision of S3-211877 |
Huawei, Hisilicon | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212240 | Draft TR 33.839 v0.6.0 | draft TR | Huawei, HiSilicon | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-212241 | Resolution of Editor's Note in Solution 19 related to provisioning of server certificate the the onboarding UE. |
pCR revision of S3-211728 |
Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212242 | Addressing the Editors’ Note in solution #1 |
pCR revision of S3-211789 |
Qualcomm Incorporated | 33.864 0.4.0 | FS_AMFREAL_SEC | Rel-17 |
S3-103-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-212243 | Proposed evaluation for solution #24 and partial conclusion for key issue #6 |
pCR revision of S3-211782 |
Qualcomm Incorporated | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212244 | Update to solution #6 on obtaining UAV location information from the PLMN |
pCR revision of S3-211775 |
Qualcomm Incorporated | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212245 | Update to solution #13 on authorisation of UAV/UAVC when connected to EPS |
pCR revision of S3-211777 |
Qualcomm Incorporated | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212246 | Update to solution #14 on authorisation of UAV/UAVC pairing when connected to 5GS |
pCR revision of S3-211778 |
Qualcomm Incorporated | 33.854 0.5.0 | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-212247 | Draft TR 33.854 |
draft TR revision of S3-211346 revised to S3-213148 |
Qualcomm | FS_UAS_SEC | Rel-17 |
S3-103-e AI: 5.7 |
approved | [WTS] [JSN] | |
S3-212248 | Evalution and system impact for soluiton 19 |
pCR revision of S3-211732 |
Nokia, Nokia Shanghai Bell | 33.857 0.5.0 | FS_eNPN_SEC | Rel-17 |
S3-103-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-212249 | Summary of discussion: NRF services authorization and OAuth 2.0 client registration from Rel-15 onwards | discussion | Nokia, Nokia Shanghai Bell |
S3-103-e AI: 4.22 |
not treated | [WTS] [JSN] | |||
S3-212250 | Editor Note removal for Solution#10 |
pCR revision of S3-211932 |
Nokia, Nokia Shanghai-Bell | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212251 | MEC-Adding evaluation on Solution#9 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212252 | MEC-Adding evaluation on Solution#9 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212253 | MEC-New solution on authentication between EEC and ECS |
pCR revision of S3-211712 |
Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212254 | MEC-Kedge ID generation method |
pCR revision of S3-211713 |
Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212255 | MBS-New solution on Key distribution |
pCR revision of S3-211714 |
Apple | 33.85 0.5.0 | FS_5MBS_SEC | Rel-17 |
S3-103-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-212256 | UC3S-Requirement on revoking user consent |
pCR revision of S3-211715 |
Apple | 33.867 0.4.0 | FS_UC3S | Rel-17 |
S3-103-e AI: 5.14 |
approved | [WTS] [JSN] |
S3-212257 | LS reply on Small data transmissions |
LS out LS To: RAN2 |
InterDigital, Inc. |
S3-103-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-212258 | Reply LS to LS on broadcasting from other PLMN in case of Disaster Condition |
LS out LS is reply to S3-211372 source LS: C1-211189 LS To: CT1 revision of S3-211523 |
LG Electronics Inc. | FS_MINT-CT | Rel-17 |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | |
S3-212259 | Cover sheet TR 33.873 |
TS or TR cover revised to S3-212374 |
Intel K.K. | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
revised | [WTS] [JSN] | |
S3-212260 | WID IIoT CR NEF-AF aspects | draftCR | Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 4.22 |
withdrawn | [WTS] [JSN] | |
S3-212261 | recommendation of SHA256 in SIP digest |
draftCR revised to S3-212333 |
Huawei, HiSilicon | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-212262 | IMS SCAS: Adding the assets and threats | CR | Huawei, HiSilicon | 33.926 17.0.0 CR#44 catB | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-212263 | Presentation of Specification to TSG: TS 33.226 for approval | TS or TR cover | Huawei, HiSilicon | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
approved | [WTS] [JSN] | |
S3-212264 | Security updates for algorithms and protocols in 33.310 | draftCR | Ericsson | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-212265 | PTP aspects | CR | Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#1140 catB | DUMMY | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212266 | NEF-AF aspects | CR | Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#1141 catB | DUMMY | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212267 | Editor note removal on solution #2.9 MAC, SYNCH failure cause concealment |
pCR revision of S3-211505 |
Nokia, Nokia Shanghai Bell | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212268 | LS on Security risk evaluation of using long term key for another key derivation than AKA |
LS out LS To: ETSI SAGE revision of S3-211510 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] | ||
S3-212269 | Security updates for algorithms and protocols in 33.210 | draftCR | Ericsson | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-212270 | pCR to Living document for TS 33.163: update for 3G, 4G, and 5G key agreement |
other revision of S3-211461 |
KPN N.V. | Rel-17 |
S3-103-e AI: 4.11 |
approved | [WTS] [JSN] | ||
S3-212271 | Living document for TS 33.163 |
draftCR revision of S3-211412 |
KPN N.V. | BEST_5G | Rel-17 |
S3-103-e AI: 4.11 |
approved | [WTS] [JSN] | |
S3-212272 | Reply-LS on integrity protection between the UE and the HPLMN of additional fields in SOR transparent container carrying SOR acknowledgement |
LS out LS is reply to S3-211440/C1-212523 LS To: CT1 revision of S3-211751 |
Ericsson |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-212273 | Update to mapping table |
pCR revision of S3-211561 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212274 | EN resolution on null scheme for solution 2.7 |
pCR revision of S3-211560 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212275 | Update to solution 2.7 and evaluation table |
pCR revision of S3-211562 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212276 | Add evaluation and update comparison table for solution 3.2 |
pCR revision of S3-211558 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212277 | Add evaluation for solution 4.5 |
pCR revision of S3-211559 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212278 | Update to solution 4.5 for the scenario of UE triggered service request |
pCR revision of S3-211563 |
ZTE Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212279 | draft TR 33.874 |
draft TR revision of S3-212186 |
Huawei, HiSilicon | FS_eNS2_SEC | Rel-17 |
S3-103-e AI: 5.21 |
approved | [WTS] [JSN] | |
S3-212280 | Slice privacy protection in NSSAA related procedures |
CR revision of S3-211624 |
Huawei, HiSilicon, Nokia, Nokia Shangahai-Bell | 33.501 16.6.0 CR#10871 catF | eNS | Rel-16 |
S3-103-e AI: 4.19 |
agreed | [WTS] [JSN] |
S3-212281 | Slice privacy protection in NSSAA related procedures (Rel-17) | CR | Huawei, HiSilicon, Nokia, Nokia Shangahai-Bell | 33.501 17.1.0 CR#1142 catA | eNS | Rel-17 |
S3-103-e AI: 4.19 |
agreed | [WTS] [JSN] |
S3-212282 | N32-c and N32-f clarification R16 |
CR revision of S3-211980 |
Nokia, Nokia Shanghai Bell | 33.501 16.6.0 CR#11271 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212283 | Update to solution #25 |
pCR revision of S3-211598 |
Huawei, HiSilicon | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-212284 | N32-c and N32-f clarification R17 |
CR revision of S3-211981 |
Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#11281 catA | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212285 | Deployment models R16 |
CR revision of S3-211982 |
Nokia, Nokia Shanghai Bell | 33.501 16.6.0 CR#11291 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212286 | Deployment models R17 |
CR revision of S3-211983 |
Nokia, Nokia Shanghai Bell | 33.501 17.1.0 CR#11301 catA | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212287 | CR to 33.501 R16 - Clarification on the number of PLMN IDuse by SEPP over N32 |
CR revision of S3-211459 |
VODAFONE Group Plc, Nokia, Nokia Shanghai Bell, Mavenir | 33.501 16.6.0 CR#10801 catF | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212288 | CR to 33.501 R17 - Clarification on the number of PLMN IDuse by SEPP over N32 |
CR revision of S3-211460 |
VODAFONE Group Plc, Nokia, Nokia Shanghai Bell, Mavenir | 33.501 17.1.0 CR#10811 catA | 5G_eSBA | Rel-17 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212289 | Rel16-Handling of Kausf upon successful primary authentication |
CR revision of S3-212103 |
Samsung, NEC, Nokia, Nokia Shanghai Bell, Intel, Ericsson | 33.501 16.6.0 CR#11371 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212290 | Rel17-Handling of Kausf upon successful primary authentication |
CR revision of S3-212104 |
Samsung, NEC, Nokia, Nokia Shanghai Bell, Intel, Ericsson | 33.501 17.1.0 CR#11381 catA | TEI16 | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212291 | Reply LS on Storage of KAUSF |
LS out LS is reply to S3-211375 source LS: S3-211375 LS To: CT1 |
Samsung | Rel-17 |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-212292 | New solution for key issue#1: Authentication of NF service producer in indirect communication |
pCR revision of S3-212094 |
Samsung | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212293 | Living CR on SCP to 33.926 |
draftCR revised to S3-214078 |
Nokia, Nokia Shanghai Bell | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-212294 | TS 33.522 SCAS SCP | draft TS | Nokia, Nokia Shanghai Bell | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
approved | [WTS] [JSN] | |
S3-212295 | SCP test cases |
pCR revision of S3-212121 |
Nokia, Nokia Shanghai Bell, NTT Docomo | 33.522 0.2.0 | SCAS_5G_SECOP | Rel-17 |
S3-103-e AI: 4.4 |
approved | [WTS] [JSN] |
S3-212296 | Resolving ENs of solution 6.2.10 |
pCR revision of S3-211528 |
NEC Corporation | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212297 | TR 33.875-030 | draft TR | Nokia Germany | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] | |
S3-212298 | Sol1 deployment scenarios |
pCR revision of S3-211969 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212299 | ENs on Sol1 Service response verification in model C |
pCR revision of S3-211970 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212300 | EN resolution on sol 2 - NFc authorizing SCP to act on its behalf |
pCR revision of S3-211975 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212301 | Evaluation on sol 2 - NFc authorizing SCP to act on its behalf |
pCR revision of S3-211976 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212302 | Solution on Access token request for NF Set |
pCR revision of S3-211974 revised to S3-212394 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-212303 | Trust model |
pCR revision of S3-211979 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212304 | New WID on Security enhancements for 5G multicast-broadcast services (5MBS) |
WID new revision of S3-211630 |
Huawei, Hisilicon,China Broadcasting Network | Rel-17 |
S3-103-e AI: 4.21 |
agreed | [WTS] [JSN] | ||
S3-212305 | Reply LS on User location identification from Carrier Aggregation secondary cell activation messages |
LS out LS is reply to S3-211382 LS To: GSMA FSAG revision of S3-211638 |
Huawei, Hisilicon |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-212306 | Reply LS on UE location aspects in NTN |
LS out LS is reply to S3-211387 LS To: RAN2, SA2, SA3-LI, RAN3 revision of S3-211639 |
Huawei, Hisilicon |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-212307 | Execution Step for Finding the right NF instance serving the UE |
draftCR revision of S3-211641 |
Huawei, HiSilicon, China Mobile, Nokia, Nokia Shanghai Bell | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-212308 | User Plane Integrity Protection Policy Handling in LTE |
draftCR revision of S3-211642 |
Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
S3-103-e AI: 4.13 |
approved | [WTS] [JSN] | |
S3-212309 | Assign FC Value for KTIPSec and KTNAP Derivation in R16 |
CR revision of S3-211644 |
Huawei, HiSilicon | 33.501 16.6.0 CR#10891 catF | 5WWC | Rel-16 |
S3-103-e AI: 4.18 |
agreed | [WTS] [JSN] |
S3-212310 | Assign FC Value for KTIPSec and KTNAP Derivation in R17 |
CR revision of S3-211645 |
Huawei, HiSilicon | 33.501 17.1.0 CR#10901 catA | 5WWC | Rel-17 |
S3-103-e AI: 4.18 |
agreed | [WTS] [JSN] |
S3-212311 | FC Value Change because of KTIPSec and KTNAP Derivation in R17 |
CR revision of S3-211647 |
Huawei, HiSilicon, Samsung | 33.22 17.0.0 CR#2091 catA | 5WWC | Rel-17 |
S3-103-e AI: 4.18 |
agreed | [WTS] [JSN] |
S3-212312 | Change the procedure of network slice re-authentication and revocation by AAA-S |
CR revision of S3-211662 |
Huawei, HiSilicon, Ericsson | 33.501 17.1.0 CR#10911 catF | eNS | Rel-17 |
S3-103-e AI: 4.19 |
agreed | [WTS] [JSN] |
S3-212313 | Clarification on AAnF Selection |
CR revision of S3-211671 |
Huawei, HiSilicon | 33.535 17.1.0 CR#761 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-212314 | Update testcases in gNB SCAS |
CR revision of S3-211681 |
Huawei, HiSilicon | 33.511 16.6.0 CR#231 catF | SCAS_5G | Rel-16 |
S3-103-e AI: 4.15 |
agreed | [WTS] [JSN] |
S3-212315 | Draft TR 33.846 v0.12.0 Study on authentication enhancements in the 5G System (5GS) | draft TR | Ericsson España S.A. | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] | |
S3-212316 | WID IIoT Draft CR PTP aspects |
draftCR revision of S3-211453 |
Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 4.22 |
approved | [WTS] [JSN] | |
S3-212317 | WID IIoT Draft CR NEF-AF aspects |
draftCR revision of S3-211454 |
Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-103-e AI: 4.22 |
approved | [WTS] [JSN] | |
S3-212318 | WID on IIoT |
WID new revision of S3-211452 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-103-e AI: 4.21 |
agreed | [WTS] [JSN] | ||
S3-212319 | UDM notifies AAnF AKMA context removal |
CR revision of S3-211551 |
ZTE Corporation | 33.535 17.1.0 CR#721 catB | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-212320 | Add an abbreviation to AKMA |
CR revision of S3-211585 |
ZTE Corporation | 33.535 17.1.0 CR#751 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-212321 | Adding asset, description and threats to TR 33.926 for NWDAF SCAS |
CR revision of S3-211842 |
China Mobile | 33.926 17.0.0 CR#411 catB | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
agreed | [WTS] [JSN] |
S3-212322 | Execution Step for Data Masking on Integration Analysis |
pCR revision of S3-211843 |
China Mobile | 33.521 0.3.0 | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
approved | [WTS] [JSN] |
S3-212323 | TS 33.521 v0.4.0 | draft TS | China Mobile Com. Corporation | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-212324 | Presentation of TR33.818 to SA plenary | TS or TR cover | China Mobile | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
withdrawn | [WTS] [JSN] | |
S3-212325 | TR 33.818 v0.12.0 | draft TR | China Mobile Com. Corporation | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] | |
S3-212326 | Presentation of TR33.818 to SA plenary |
TS or TR cover revision of S3-211834 |
China Mobile | FS_VNP_SECAM_SCAS | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] | |
S3-212327 | Update to the solution 3.3 |
pCR revision of S3-211636 |
Huawei, Hisilicon | 33.846 0.11.0 | FS_AUTH_ENH | Rel-17 |
S3-103-e AI: 5.5 |
approved | [WTS] [JSN] |
S3-212328 | AKMA UE aspects |
CR revision of S3-211913 |
Ericsson | 33.535 17.1.0 CR#811 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-212329 | Response LS on 256-bit Milenage |
LS out LS is reply to S3-211408 source LS: S3-211408 LS To: ETSI SAGE revision of S3-211500 |
VODAFONE Group Plc |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-212330 | Removal of ENs for draft-ietf-emu-rfc5448bis - Rel-15 |
CR revision of S3-211988 |
Ericsson | 33.501 15.12.0 CR#11331 catF | 5GS_Ph1-SEC | Rel-15 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212331 | Removal of ENs for draft-ietf-emu-rfc5448bis -Rel-16 |
CR revision of S3-211990 |
Ericsson | 33.501 16.6.0 CR#11341 catA | 5GS_Ph1-SEC | Rel-16 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212332 | New test case on validation of S-NSSAIs in PDU session establishment |
draftCR revision of S3-211858 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-212333 | recommendation of SHA256 in SIP digest |
draftCR revision of S3-212261 |
Huawei, Hisilicon | eCryptPr | Rel-17 |
S3-103-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-212334 | New test case on malformatted message for IPUPS |
draftCR revision of S3-211868 |
Huawei, Hisilicon | SCAS_5G_IPUPS | Rel-17 |
S3-103-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-212335 | New security threats on IPUPS malformatted message |
draftCR revision of S3-211869 |
Huawei, Hisilicon | SCAS_5G_IPUPS | Rel-17 |
S3-103-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-212336 | Reply LS on changes to SoR |
LS out LS To: CT1, CT4 revision of S3-211872 revised to S3-212378 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 4.22 |
revised | [WTS] [JSN] | ||
S3-212337 | Claifications on mapped security |
CR revision of S3-211874 |
Huawei, Hisilicon | 33.501 16.6.0 CR#11191 catF | TEI16 | Rel-16 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212338 | Claifications on mapped security | CR | Huawei, Hisilicon | 33.501 17.1.0 CR#1143 catA | TEI16 | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212339 | Clarification to SoR transparent container |
CR revision of S3-211881 |
Huawei, Hisilicon | 33.501 17.1.0 CR#11201 catF | TEI17 | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212340 | Clarifications to 5G CIoT K_NG-RAN derivation | CR | Huawei, Hisilicon | 33.501 17.1.0 CR#1144 catA | TEI16 | Rel-17 |
S3-103-e AI: 4.22 |
not pursued | [WTS] [JSN] |
S3-212341 | Clarification on a figure and the key activation |
CR revision of S3-211882 revised to S3-212348 |
Huawei, Hisilicon | 33.536 16.3.0 CR#251 catF | eV2XARC | Rel-16 |
S3-103-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-212342 | New WID on Security Aspects of Enhancement of Support for Edge Computing in 5GC |
WID new revision of S3-211892 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 4.21 |
agreed | [WTS] [JSN] | ||
S3-212343 | LS on TAU reject issue during MME handover |
LS out LS To: CT4 revision of S3-211899 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-212344 | Reply LS on Header Enrichment for HTTPS in PFCP |
LS out LS is reply to S3-211380 LS To: CT4 LS reply in C4-214214 revision of S3-211900 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-212345 | Draft TS 33.226 | draft TS | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-103-e AI: 4.2 |
approved | [WTS] [JSN] | |
S3-212346 | Removal of ENs for draft-ietf-emu-rfc5448bis- Rel-17 |
CR revision of S3-211991 |
Ericsson | 33.501 17.1.0 CR#11351 catA | 5GS_Ph1-SEC | Rel-17 |
S3-103-e AI: 4.22 |
agreed | [WTS] [JSN] |
S3-212347 | pCR to TR 33.845 - editorial corrections |
pCR revision of S3-211531 |
VODAFONE Group Plc | 33.845 1.0.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-103-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-212348 | Clarification on a figure and the key activation |
CR revision of S3-212341 |
Huawei, Hisilicon, Interdigtal | 33.536 16.3.0 CR#252 catF | eV2XARC | Rel-16 |
S3-103-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-212349 | 5GFBS-LS to RAN2 on Solution#17 |
LS out LS To: RAN2 LS reply in R2-2107572, R2-2109060, R2-2109121 revision of S3-211706 |
Apple | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] | ||
S3-212350 | pCR to TR33.845 - removal of editors notes |
pCR revision of S3-211581 |
VODAFONE Group Plc | 33.845 1.0.0 | FS_5GC_SEC_ARPF | Rel-17 |
S3-103-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-212351 | draft TR 33.809 | draft TR | Apple (UK) Limited | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-212352 | New WID on TLS protocols profiles for AKMA |
WID new revision of S3-211784 |
Qualcomm Incorporated, Ericsson, CMCC, ZTE, Nokia |
S3-103-e AI: 4.21 |
agreed | [WTS] [JSN] | |||
S3-212353 | Profiling the GBA TLS protocols for use with AKMA |
CR revision of S3-211785 |
Qualcomm Incorporated | 33.535 17.1.0 CR#662 catB | AKMA_TLS | Rel-17 |
S3-103-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-212354 | New WID on Security aspects of Uncrewed Aerial Systems |
WID new revision of S3-211774 |
Qualcomm Incorporated, Interdigital, Huawei, HiSilicon, Ericsson, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
S3-103-e AI: 4.21 |
agreed | [WTS] [JSN] | |||
S3-212355 | Reply LS on IP address to GPSI translation |
LS out LS is reply to S3-211391,S3-211392,S3-211424 LS To: SA2, SA6 revision of S3-212048 |
Ericsson, Qualcomm Incorporated | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-212356 | Remarks_in_Solution_14 |
pCR revision of S3-211586 |
Philips International B.V. | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-212357 | Update_in_solution_26 |
pCR revision of S3-211588 |
Philips International B.V. | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-212358 | Updates in Solution #23 |
pCR revision of S3-211582 |
Philips International B.V. | 33.809 0.14.0 | FS_5GFBS | Rel-17 |
S3-103-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-212359 | AKMA Anchor Function selection clause |
CR revision of S3-211908 |
Ericsson | 33.535 17.1.0 CR#791 catF | AKMA | Rel-17 |
S3-103-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-212360 | TR33.845 v1.1.0 | draft TR | VODAFONE Group Plc | FS_5GC_SEC_ARPF | Rel-17 |
S3-103-e AI: 5.6 |
approved | [WTS] [JSN] | |
S3-212361 | CR to TS 43.020 - R16 - Removal of support for GEA2 |
CR revision of S3-211473 |
VODAFONE Group Plc | 43.02 16.0.0 CR#581 catA | TEI11 | Rel-16 |
S3-103-e AI: 6 |
agreed | [WTS] [JSN] |
S3-212362 | CR to TS 43.020 - R11 - Removal of GEA1 and GEA2 due to security concerns |
CR revision of S3-211491 |
VODAFONE Group Plc | 43.02 11.2.0 CR#591 catF | TEI11 | Rel-11 |
S3-103-e AI: 6 |
agreed | [WTS] [JSN] |
S3-212363 | CR to TS 43.020 - R12 - Depreciation of GEA2 due to security concerns |
CR revision of S3-211492 |
VODAFONE Group Plc | 43.02 12.1.0 CR#601 catF | TEI11 | Rel-12 |
S3-103-e AI: 6 |
agreed | [WTS] [JSN] |
S3-212364 | CR to TS 43.020 - R13 - Removal of GEA1 and GEA2 due to security concerns - mirror |
CR revision of S3-211493 |
VODAFONE Group Plc | 43.02 13.6.0 CR#611 catA | TEI11 | Rel-13 |
S3-103-e AI: 6 |
agreed | [WTS] [JSN] |
S3-212365 | Reply-LS on the Security consideration to support L2TP with CUPS |
LS out LS is reply to S3-211378 LS To: CT4 revision of S3-211746 |
Ericsson | Rel-17 |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-212366 | Reply-LS on Secondary AUTH for 5GS interworking with EPS |
LS out LS is reply to S3-211376,S3-211397 LS To: CT3, SA2 revision of S3-211747 |
Ericsson | Rel-17 |
S3-103-e AI: 3 |
approved | [WTS] [JSN] | ||
S3-212367 | Clarify the usage of TLS and PRINS between SEPPs |
CR revision of S3-211759 |
Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | 33.501 15.12.0 CR#11051 catF | 5GS_Ph1-SEC | Rel-15 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212368 | Clarify the usage of TLS and PRINS between SEPPs |
CR revision of S3-211760 |
Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | 33.501 16.6.0 CR#11061 catA | 5GS_Ph1-SEC | Rel-16 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212369 | Clarify the usage of TLS and PRINS between SEPPs |
CR revision of S3-211761 |
Ericsson, Nokia, Nokia Shanghai Bell, Mavenir | 33.501 17.1.0 CR#11071 catA | 5GS_Ph1-SEC | Rel-17 |
S3-103-e AI: 4.16 |
agreed | [WTS] [JSN] |
S3-212370 | CR to TS 43.020 - R14 - Removal of GEA1 and GEA2 due to security concerns - mirror |
CR revision of S3-211494 |
VODAFONE Group Plc | 43.02 14.3.0 CR#621 catA | TEI11 | Rel-14 |
S3-103-e AI: 6 |
agreed | [WTS] [JSN] |
S3-212371 | New WID on Security Aspects of eNPN |
WID new revision of S3-211772 |
Ericsson, Alibaba, China Mobile, InterDigital, ZTE | Rel-17 |
S3-103-e AI: 4.21 |
agreed | [WTS] [JSN] | ||
S3-212372 | Evaluation of Solution #3 "Using existing procedures for authorization of SCP to act on behalf of an NF Consumer" |
pCR revision of S3-211766 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212373 | CR to TS 43.020 - R15 - Removal of GEA1 and GEA2 due to security concerns - mirror |
CR revision of S3-211495 |
VODAFONE Group Plc | 43.02 15.0.0 CR#631 catA | TEI11 | Rel-15 |
S3-103-e AI: 6 |
agreed | [WTS] [JSN] |
S3-212374 | Cover sheet TR 33.873 |
TS or TR cover revision of S3-212259 |
Intel K.K. | FS_MUSIM_SEC | Rel-17 |
S3-103-e AI: 5.19 |
approved | [WTS] [JSN] | |
S3-212375 | living CR to 33.511 |
draftCR revision of S3-211673 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-212376 | living CR to 33.512 |
draftCR revision of S3-211674 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-212377 | living CR to 33.926 |
draftCR revision of S3-211678 |
Huawei, HiSilicon | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
approved | [WTS] [JSN] | |
S3-212378 | Reply LS on changes to SoR |
LS out LS To: CT1, CT4 revision of S3-212336 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 4.22 |
approved | [WTS] [JSN] | ||
S3-212379 | CR to include R-16 feature of gNB to 33.511 | CR | Huawei, HiSilicon | 33.511 16.6.0 CR#24 catB | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-212380 | CR to include R-16 feature of AMF to 33.512 | CR | Huawei, HiSilicon | 33.512 16.5.0 CR#10 catB | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-212381 | CR to include R-16 feature of UDM to 33.514 | CR | Huawei, HiSilicon | 33.514 16.4.0 CR#5 catB | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-212382 | CR to include R-16 feature of SEPP to 33.517 | CR | Huawei, HiSilicon | 33.517 16.2.0 CR#9 catB | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-212383 | CR to include new test cases and fix editorial in33.117 | CR | Huawei, HiSilicon | 33.117 16.6.0 CR#72 catB | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-212384 | CR to add threat related to R-16 features of network products to 33.926 | CR | Huawei, HiSilicon | 33.926 17.0.0 CR#45 catB | eSCAS_5G | Rel-17 |
S3-103-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-212385 | Living document for SCAS_5G_IPUPS draftCR to TR 33.926 |
draftCR revision of S3-211543 |
ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-103-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-212386 | Living document for SCAS_5G_IPUPS draftCR to TS 33.513 |
draftCR revision of S3-211544 |
ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-103-e AI: 4.7 |
approved | [WTS] [JSN] | |
S3-212387 | Presentation of TR33.521 to SA plenary |
TS or TR cover revision of S3-211845 |
China Mobile | SCAS_5G_NWDAF | Rel-17 |
S3-103-e AI: 4.5 |
approved | [WTS] [JSN] | |
S3-212388 | Addition of Key Issue 26 Text |
pCR revision of S3-212120 |
BT plc | 33.848 0.7.0 | FS_SIV | Rel-16 |
S3-103-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-212389 | Addition of Key Issue 25 Text |
pCR revision of S3-212122 |
BT plc | 33.848 0.7.0 | FS_SIV | Rel-16 |
S3-103-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-212390 | Standardising Automated TLS Certificate Management in SBA |
SID new revision of S3-211477 |
BT plc | Rel-18 |
S3-103-e AI: 5.23 |
agreed | [WTS] [JSN] | ||
S3-212391 | TR 33.848 v080 | draft TR | BT plc | FS_SIV | Rel-16 |
S3-103-e AI: 5.4 |
approved | [WTS] [JSN] | |
S3-212392 | Response LS to GSMA on 3GPP SA3 N32 and multiple PLMN IDs |
LS out LS is reply to S3-211446 LS To: GSMA revision of S3-211458 |
VODAFONE Group Plc | 5G_eSBA | Rel-16 |
S3-103-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-212393 | Reply LS on changes to SoR |
LS out LS To: CT1, CT4 |
Huawei, Hisilicon | Rel-17 |
S3-103-e AI: 4.22 |
withdrawn | [WTS] [JSN] | ||
S3-212394 | Solution on Access token request for NF Set |
pCR revision of S3-212302 |
Nokia, Nokia Shanghai Bell | 33.875 0.2.0 | FS_eSBA_SEC | Rel-17 |
S3-103-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-212395 | Alignment of requirements with specification updates |
CR revision of S3-211935 revised to S3-212872 |
Nokia, Nokia Shanghai Bell | 33.117 16.6.0 CR#711 catF | SCAS_5G | Rel-16 |
S3-103-e AI: 4.15 |
not pursued | [WTS] [JSN] |
S3-212396 | Chair notes of the e-meeting | report | WG Chair |
S3-103-e AI: 2 |
available | [WTS] [JSN] | |||
S3-212397 | Response LS on 256-bit algorithms based on SNOW 3G or SNOW V |
LS out LS is reply to S3-211407 source LS: S3-211407 LS To: ETSI SAGE |
VODAFONE Group Plc |
S3-103-e AI: 3 |
withdrawn | [WTS] [JSN] |
1048 documents (1.1221449375153 seconds)