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-201500 | Agenda |
agenda revised to S3-202152 |
SA WG3 Chair |
S3-100-e AI: 1 |
revised | [WTS] [JSN] | |||
S3-201501 | Report from SA3#99-e | report | MCC |
S3-100-e AI: 2 |
approved | [WTS] [JSN] | |||
S3-201502 | Process for SA3#100-e meeting |
other revised to S3-201550 |
SA WG3 Chair |
S3-100-e AI: 1 |
revised | [WTS] [JSN] | |||
S3-201503 | Report from last SA | report | SA WG3 Chair |
S3-100-e AI: 2 |
noted | [WTS] [JSN] | |||
S3-201504 | 5G capabilities exposure for factories of the future | LS in | 5GACIA |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201505 | Reply LS on IANA assigned values for mission critical | LS in | C1-203503 |
S3-100-e AI: 4.3 |
noted | [WTS] [JSN] | |||
S3-201506 | Reply LS on specification of NAS COUNT for 5G | LS in | C1-203971 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201507 | Reply LS on Updated User Plane Integrity Protection advice | LS in | C1-204194 |
S3-100-e AI: 5.4 |
noted | [WTS] [JSN] | |||
S3-201508 | LS on Key Management procedure in SEAL |
LS in LS reply in S3-202177, S3-201654, S3-202177 |
C3-203588 |
S3-100-e AI: 4.12 |
replied to | [WTS] [JSN] | |||
S3-201509 | Reply PAP/CHAP and other point-to-point protocols usage in 5GS |
LS in LS reply in S3-202190, S3-202190 |
S2-2004481 |
S3-100-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-201510 | Reply LS on PAP/CHAP and other point-to-point protocols usage in 5GS | LS in | C3-203609 |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201511 | LS on 5G SoR integrity protection mechanism |
LS in LS reply in S3-202251 |
C4-203367 |
S3-100-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-201512 | LS on Clarification on AAA-Server address |
LS in LS reply in S3-202048 |
C4-203452 |
S3-100-e AI: 4.1 |
postponed | [WTS] [JSN] | |||
S3-201513 | LS Reply on Multiple Kausf upon registering via multiple Serving Networks | LS in | C4-203568 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201514 | Reply LS on S1/NG DAPS handover | LS in | CP-201312 |
S3-100-e AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-201515 | LS on human-readable network name (HRNN) | LS in | CP-201361 |
S3-100-e AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-201516 | LS to ITU-T Study Group 17 | LS in | ETSI TC CYBER QSC |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201517 | Announcement of ISG ETI | LS in | ETSI ISG ETI |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201518 | Specification of NAS COUNT for 5G | LS in | GSMA FSAG |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201519 | Uniqueness of FN-RG PEI for Lawful Interception purposes | LS in | BBF |
S3-100-e AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-201520 | Reply LS to SA3 on FBS detection | LS in | R2-1914224 |
S3-100-e AI: 5.2 |
postponed | [WTS] [JSN] | |||
S3-201521 | LS on early UE capability retrieval for eMTC | LS in | R2-2003935 |
S3-100-e AI: 4.8 |
noted | [WTS] [JSN] | |||
S3-201522 | LS on the re-keying procedure for NR SL | LS in | R2-2005978 |
S3-100-e AI: 4.13 |
postponed | [WTS] [JSN] | |||
S3-201523 | LS on system support for WUS | LS in | R2-2005985 |
S3-100-e AI: 3 |
withdrawn | [WTS] [JSN] | |||
S3-201524 | LS on propagation of user consent related information during Xn inter-PLMN handover | LS in | R3-204378 |
S3-100-e AI: 4.21 |
postponed | [WTS] [JSN] | |||
S3-201525 | LS on Questions on onboarding requirements | LS in | S1-201087 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] | |||
S3-201526 | Reply LS on Questions on onboarding requirements | LS in | S1-202266 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] | |||
S3-201527 | Questions on onboarding requirements | LS in | S2-2001729 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] | |||
S3-201528 | LS on AMF Reallocation via RAN re-routing |
LS in LS reply in S3-201862, S3-201862 |
S2-2001730 |
S3-100-e AI: 4.21 |
replied to | [WTS] [JSN] | |||
S3-201529 | LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN |
LS in LS reply in S3-201953, S3-202652 |
S2-2004385 |
S3-100-e AI: 5.13 |
postponed | [WTS] [JSN] | |||
S3-201530 | Reply LS on Application Architecture for enabling Edge Applications | LS in | S2-2004386 |
S3-100-e AI: 5.9 |
noted | [WTS] [JSN] | |||
S3-201531 | Reply LS on early UE capability retrieval for eMTC | LS in | S2-2004446 |
S3-100-e AI: 4.8 |
noted | [WTS] [JSN] | |||
S3-201532 | Reply LS on manipulation of CAG Information element by a VPLMN | LS in | S2-2004453 |
S3-100-e AI: 4.21 |
noted | [WTS] [JSN] | |||
S3-201533 | Reply LS on protection of allowed CAG list against MITM Attack | LS in | S2-2004455 |
S3-100-e AI: 4.21 |
noted | [WTS] [JSN] | |||
S3-201534 | Reply LS on NSSAAF in slice specific authentication | LS in | S2-2004476 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201535 | LS on user consent requirements for analytics | LS in | S2-2004560 |
S3-100-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-201536 | LS on Security Requirements for Sidelink/PC5 Relays |
LS in LS reply in S3-201950 |
S2-2004750 |
S3-100-e AI: 5.1 |
postponed | [WTS] [JSN] | |||
S3-201537 | LS on uniqueness of PEI in certain FN-RG configurations | LS in | S3i200069 |
S3-100-e AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-201538 | LS on security procedures for Edge Applications |
LS in LS reply in S3-202087, S3-202087 |
S6-200945 |
S3-100-e AI: 5.9 |
replied to | [WTS] [JSN] | |||
S3-201539 | LS on IP address to GPSI translation | LS in | S6-200947 |
S3-100-e AI: 5.9 |
postponed | [WTS] [JSN] | |||
S3-201540 | 256 bit algorithm candidates |
LS in LS reply in S3-202191 |
ETSI SAGE |
S3-100-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-201541 | Observations on ZUC-256 |
LS in LS reply in S3-202192 |
ETSI SAGE |
S3-100-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-201542 | Observations and questions on 256-bit security goals | LS in | ETSI SAGE |
S3-100-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-201543 | Reply to LS on Resynchronisations | LS in | ETSI SAGE |
S3-100-e AI: 5.6 |
postponed | [WTS] [JSN] | |||
S3-201544 | Use of 256-bit block Rijndael in Milenage-256 | LS in | ETSI SAGE |
S3-100-e AI: 3 |
postponed | [WTS] [JSN] | |||
S3-201545 | Liaison statement from ETSI ISG SAI on Securing Artificial Intelligence | LS in | ETSI ISG SAI |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201546 | Reply LS to TC CYBER QSC request for collaboration on migration planning of HSMs to support Quantum Safe Cryptography | LS in | ETSI TC SCP |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201547 | NESAS Official Launch |
LS in LS reply in S3-202219, S3-202219 |
GSMA SECAG |
S3-100-e AI: 4.2 |
replied to | [WTS] [JSN] | |||
S3-201548 | LS on technical reports on use cases and requirements as well as architecture for vehicular multimedia | LS in | ITU-T Focus Group on Vehicular Multimedia (FG-VM) |
S3-100-e AI: 4.13 |
noted | [WTS] [JSN] | |||
S3-201549 | LS on mandatory support of full rate user plane integrity protection for 5G | LS in | SP-200617 |
S3-100-e AI: 5.4 |
noted | [WTS] [JSN] | |||
S3-201550 | Process for SA3#100-e meeting |
other revision of S3-201502 revised to S3-202058 |
SA WG3 Chair |
S3-100-e AI: 1 |
revised | [WTS] [JSN] | |||
S3-201551 | New Solution for KI2 - Encrypted storage of LTK in UDR |
pCR revised to S3-202060 |
KPN N.V. | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-201552 | New Solution for KI3 - Encrypted transfer of LTK out of UDR |
pCR revised to S3-202059 |
KPN N.V. | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-201553 | Discussion on adapting BEST for use in 5G networks supporting AKMA | discussion | KPN N.V. | Rel-17 |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-201554 | Study on adapting BEST for use in 5G networks supporting AKMA | SID new | KPN N.V. | Rel-17 |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-201555 | pCR: Updates to TR 33.809 | pCR | Deutsche Telekom AG | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-201556 | TCG progress - report from TCG rapporteur | other | InterDigital, Inc. |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201557 | Clarification on the definition of KNRP-sess | CR | InterDigital, Inc., LG Electronics, Qualcomm Incorporated | 33.536 16.0.0 CR#1 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-201558 | Resolution of editor's note in clause 6.3.2.1 | CR | NTT DOCOMO | 33.501 15.9.0 CR#857 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201559 | Resolution of editor's note in clause 6.3.2.1 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#858 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201560 | Discussion on treatment of editor's notes in 33.501 | discussion | NTT DOCOMO | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201561 | resolution of editor's notes in clause 6.8.1.2.0 | CR | NTT DOCOMO | 33.501 15.9.0 CR#859 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201562 | resolution of editor's notes in clause 6.8.1.2.0 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#860 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201563 | resolution of editor's note in clause 6.8.1.2.2 | CR | NTT DOCOMO | 33.501 15.9.0 CR#861 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201564 | resolution of editor's note in clause 6.8.1.2.2 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#862 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201565 | resolution of editor's note in clause 6.8.1.2.4 | CR | NTT DOCOMO, ZTE | 33.501 15.9.0 CR#863 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201566 | resolution of editor's note in clause 6.8.1.2.4 - R16 mirror | CR | NTT DOCOMO, ZTE | 33.501 16.3.0 CR#864 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201567 | resolution of editor's note in clause 6.9.1 | CR | NTT DOCOMO | 33.501 15.9.0 CR#865 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201568 | resolution of editor's note in clause 6.9.1 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#866 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201569 | resolution of editor's note in clause 6.9.4.1 | CR | NTT DOCOMO | 33.501 15.9.0 CR#867 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201570 | resolution of editor's note in clause 6.9.4.1 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#868 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201571 | resolution of editor's note in clause 6.9.4.2 | CR | NTT DOCOMO | 33.501 15.9.0 CR#869 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201572 | resolution of editor's note in clause 6.9.4.2 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#870 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201573 | resolution of editor's note in clause 6.9.4.3 | CR | NTT DOCOMO | 33.501 15.9.0 CR#871 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201574 | resolution of editor's note in clause 6.9.4.3 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#872 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201575 | resolution of editor's note in clause 10.2.2.2 |
CR revised to S3-202193 |
NTT DOCOMO | 33.501 15.9.0 CR#873 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201576 | resolution of editor's note in clause 10.2.2.2 - R16 mirror |
CR revised to S3-202196 |
NTT DOCOMO | 33.501 16.3.0 CR#874 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201577 | resolution of editor's note in clause 13.2.4.4.1 | CR | NTT DOCOMO | 33.501 15.9.0 CR#875 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201578 | resolution of editor's note in clause 13.2.4.4.1 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#876 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201579 | resolution of editor's note in clause 13.5 | CR | NTT DOCOMO | 33.501 15.9.0 CR#877 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201580 | resolution of editor's note in clause 13.5 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#878 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201581 | Editorial corrections to NDS/AF | CR | Juniper Networks | 33.31 16.4.0 CR#111 catF | TEI16 | Rel-16 |
S3-100-e AI: 4.21 |
withdrawn | [WTS] [JSN] |
S3-201582 | Skeleton TR 33.857 v000 | draft TR | Ericsson | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
approved | [WTS] [JSN] | |
S3-201583 | TR_33.851_IIoT_Sec skeleton |
draft TR revised to S3-202101 |
Nokia, Nokia Shanghai Bell | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
revised | [WTS] [JSN] | |
S3-201584 | Scope of study |
pCR revised to S3-202102 |
Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-201585 | References |
pCR revised to S3-202103 |
Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-201586 | Abbreviations |
pCR revised to S3-202104 |
Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-201587 | Architectural considerations |
pCR revised to S3-202105 |
Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-201588 | External 5GS TSN user plane interfaces | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-201589 | N60 interface security | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-201590 | Multiple TSN working domains |
pCR revised to S3-202106 |
Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-201591 | Updating 33.501 Annex L text for PTP support | pCR | Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-201592 | Add certificate based solution for NPN as a new Solution |
pCR revised to S3-202161 |
MITRE Corporation | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-201593 | New Key Issue for TR 33.854 – UAV and UAV-C Location Information veracity |
pCR revised to S3-202088 |
InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201594 | New Key Issue for TR 33.854 –UAV authentication and authorisation | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201595 | New Key Issue for TR 33.854 – C2 communications security | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201596 | New Key Issue for TR 33.854 – UAV and UAC-C pairing authorization | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201597 | New Key Issue for TR 33.854 – New_KI_UAS_TR_-_Revocation of UAV auhorisation | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201598 | Certificate-Based Encryption Solution |
pCR revised to S3-202076 |
MITRE Corporation | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-201599 | New Key Issue for TR 33.854 – Privacy protection of UAS identities |
pCR revised to S3-202090 |
InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201600 | New Key Issue for TR 33.854 – differentiated privacy for UAS-UTM connection | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-201601 | New Key Issue for TR 33.854 – differentiated security for UAS-UAV connection | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-201602 | New Key Issue for TR 33.854 – non-repudiation for UAS-UAV exchanges | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-201603 | New Key Issue for TR 33.854 – regulatory compliance | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-201604 | Withdrawn - New Key Issue for TR 33.854 – Detection and identification of problematic UAS | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-201605 | New Key Issue for TR 33.854 – Security protection of UAS-UTM information exchanges | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201606 | New Key Issue for TR 33.854 – Impersonation of UAS entities’ identities | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201607 | Withdrawn - New Key Issue for TR 33.xyz – Limiting the information exchange between UAS and UTM/USS to authorised types and granularity of information | other | InterDigital, Inc. | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
withdrawn | [WTS] [JSN] | |
S3-201608 | New Key Issue for TR 33.854 – Secure delivery of UAV and UAC-C identities and other info to UTM/USS | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201609 | Corrections on security establishment | CR | InterDigital, Inc. | 33.536 16.0.0 CR#2 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-201610 | Access Token Signature using MAC with symmetric key | CR | Mavenir, Deutsche Telekom | 33.501 16.3.0 CR#879 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-201611 | Static authorization details |
CR revised to S3-202174 |
Mavenir,Deutsche Telekom | 33.501 16.3.0 CR#880 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-201612 | Access token indication of NF service consumer authentication via NRF | CR | Mavenir | 33.501 16.3.0 CR#881 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-201613 | SQNms protection by concealment |
pCR revised to S3-202099 |
Nokia, Nokia Shanghai Bell | 33.846 17.0.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-201614 | SQN protection during re-synchronisation procedure in AKA |
pCR revised to S3-202098 |
Nokia, Nokia Shanghai Bell | 33.846 17.0.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-201615 | Key Issue on Linking of UEs by SUCI replay attack |
pCR revised to S3-202100 |
Nokia, Nokia Shanghai Bell | 33.846 17.0.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-201616 | New Key Issue for TR 33.847 – privacy of information over the UE-to-Network | pCR | InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-201617 | New Key Issue for TR 33.847 – integrity and confidentiality of information over the UE-to-Network Relay. | pCR | InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201618 | New Key Issue for TR 33.847 – privacy of information over the UE-to-UE Relay. | pCR | InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-201619 | New Key Issue for TR 33.847 – integrity and confidentiality of information over the UE-to-UE Relay. |
pCR revised to S3-202157, S3-202158 |
InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201620 | New Key Issue for TR 33.abc – security preservation for path change | pCR | InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-201621 | New Key Issue for TR 33.847 – privacy preservation for path change | pCR | InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-201622 | New Key Issue for TR 33.847 – Authorisation of UE to Network Relay | pCR | InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201623 | New Key Issue for TR 33.847 – Authorisation of UE to UE Relay | pCR | InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201624 | Removing rel-15 text relating to N9 roaming UP | CR | Juniper Networks | 33.501 16.3.0 CR#882 catF | UPGF | Rel-16 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-201625 | Key issue on user consent/authorization for network capability exposure to Edge Application Servers | pCR | China Telecommunications | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-201626 | Milenage AKA authenticaiton | pCR | China Telecommunications | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-201627 | TUAK AKA authenticaiton |
pCR revised to S3-202110 |
China Telecommunications | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-201628 | Counter related parameters | pCR | China Telecommunications | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-201629 | Skeleton for TR 33.840 |
draft TR revised to S3-201704 |
China Telecommunications | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
revised | [WTS] [JSN] | |
S3-201630 | Scope for TR 33.840 | pCR | China Telecommunications | 33.84 0.0.1 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-201631 | Key issue about the SUCI Replaying attacks in TR 33.846 | pCR | China Mobile | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
merged | [WTS] [JSN] |
S3-201632 | Solution to mitgate the SUPI guessing attack in TR 33.846 | pCR | China Mobile | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-201633 | Complementary to Key issue to mitigate the SUCI guessing attacks in TR 33.846 | pCR | China Mobile | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-201634 | Revise the Evaluation for Solution 5 in TR 33.853 | pCR | China Mobile | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-201635 | Updates to solution #20 - resolving EN in 6.20.2.2.1 |
pCR revised to S3-202223 |
CableLabs, Apple, Intel, Deutsche Telekom AG, InterDigital Communications, Rogers Communications, Charter Communications | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-201636 | Updates to solution #20 - resolving ENs in 6.20.2.3.1 |
pCR revised to S3-202225 |
CableLabs, Apple, Intel, Deutsche Telekom AG, InterDigital Communications, Rogers Communications, Charter Communications | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-201637 | Updates to solution #20 - resolving ENs in 6.20.2.4 |
pCR revised to S3-202226 |
CableLabs, Apple, Deutsche Telekom AG, InterDigital Communications, Rogers Communications, Charter Communications | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-201638 | Updates to solution #20 - resolving ENs in 6.20.2.5.1 |
pCR revised to S3-202227 |
CableLabs, Apple, Intel, Deutsche Telekom AG, InterDigital Communications, Rogers Communications, Charter Communications | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-201639 | Architectural assumptions and definitions | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
merged | [WTS] [JSN] |
S3-201640 | Key issue on requirements for storing non-3GPP credentials | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201641 | Key issue on device and DCS authenticity | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201642 | Key issue on trustworthiness of onboarding networks | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201643 | Key issue related to primary authentication during onboarding | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201644 | Key issue on invalid device provisioning | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201645 | Key issue on AUSF with AAA integration | pCR | Nokia, Nokia Shanghai Bell | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
merged | [WTS] [JSN] |
S3-201646 | Discussion paper on contradictory text on Kseaf deletion | discussion | Nokia, Nokia Shanghai Bell |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201647 | [33.180] R16 Group regroup and user regroup security | CR | Motorola Solutions Danmark A/S | 33.18 16.4.0 CR#149 catF | MCXSec | Rel-16 |
S3-100-e AI: 4.3 |
not pursued | [WTS] [JSN] |
S3-201648 | [33.180] MCData message store security |
CR revised to S3-202176 |
Motorola Solutions Danmark A/S | 33.18 16.4.0 CR#150 catF | MCXSec | Rel-16 |
S3-100-e AI: 4.3 |
revised | [WTS] [JSN] |
S3-201649 | CR on Kseaf text deletion |
CR revised to S3-202199 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 16.3.0 CR#883 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201650 | [33.434] KM Clarifications |
CR revised to S3-202178 |
Motorola Solutions Danmark A/S | 33.434 16.0.0 CR#1 catF | SEAL | Rel-16 |
S3-100-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-201651 | CR on Kseaf text deletion |
CR revised to S3-202200 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 15.9.0 CR#884 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201652 | New WID on mission critical security enhancements for release 17 |
WID new revised to S3-202179 |
Motorola Solutions Danmark A/S | Rel-17 |
S3-100-e AI: 4.22 |
revised | [WTS] [JSN] | ||
S3-201653 | Discussion paper on Profile B uncompressed mode misalignment with CT6 | discussion | Nokia, Nokia Shanghai Bell | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-201654 | Reply LS on Key Management procedure in SEAL |
LS out LS is reply to S3-201508 source LS: S3-201508 LS To: CT3 revised to S3-202177 |
Motorola Solutions Danmark A/S | SEAL | Rel-16 |
S3-100-e AI: 4.12 |
revised | [WTS] [JSN] | |
S3-201655 | CR to delete uncompressed mode text in profile B |
CR revised to S3-202201 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#885 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201656 | CR to delete uncompressed mode text in Profile B | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#886 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201657 | Draft LS to CT6 on Profile B uncompressed mode |
LS out LS To: CT6 |
Nokia, Nokia Shanghai Bell |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201658 | Draft LS to SA2 on Security requirements for Side link PC5 |
LS out LS To: SA2 |
Nokia, Nokia Shanghai Bell |
S3-100-e AI: 5.1 |
noted | [WTS] [JSN] | |||
S3-201659 | Draft reply LS to RAN3 LS on User consent during Xn inter PLMN handover |
LS out LS To: RAN3 |
Nokia, Nokia Shanghai Bell |
S3-100-e AI: 4.21 |
noted | [WTS] [JSN] | |||
S3-201660 | TR 33.836 - clean-up | CR | LG Electronics Inc. | 33.836 16.0.0 CR#1 catF | FS_eV2X_Sec | Rel-16 |
S3-100-e AI: 5.15 |
agreed | [WTS] [JSN] |
S3-201661 | ProSe TR 33.847 - new KI on E2E security for ProSe UE2UE relay | pCR | LG Electronics Inc. | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201662 | ProSe TR 33.847 - new KI on restricted discovery | pCR | LG Electronics Inc. | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201663 | TR 33.839 - New key issue on UE location spoofing attack in 5G EC environment | pCR | LG Electronics Inc. | 33.839 0.1.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-201664 | New Key Issue for TR 33.854– Detection and identification of problematic UAS | pCR | InterDigital, Inc. | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-201665 | Requirements for TR 33.840 | pCR | China Telecommunications | 33.84 0.0.1 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
withdrawn | [WTS] [JSN] |
S3-201666 | Discussion on the Scenario and Requirement for the Disaggregated gNB | discussion | China Telecommunications |
S3-100-e AI: 5.14 |
noted | [WTS] [JSN] | |||
S3-201667 | key issue on security policy differentiation in CU-UPs |
pCR revised to S3-201702 |
China Telecommunications | 33.84 0.0.1 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
revised | [WTS] [JSN] |
S3-201668 | Key Issue on Edge Data Network authentication and authorization | pCR | Futurewei | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-201669 | Key Issue on Edge UE ID and credential protection | pCR | Futurewei | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-201670 | UAS Key Issue on location | pCR | Futurewei | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201671 | UAS Key Issue on UAV | pCR | Futurewei | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201672 | Key issue on Authentication and Authorization | pCR | CATT | 33.839 0.0.1 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-201673 | Key issue on key isolation | pCR | CATT | 33.84 0.0.1 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-201674 | Key issue on security policy differentiation | pCR | CATT | 33.84 0.0.1 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-201675 | Discussion on new SID Security Study on system enablers for devices having multiple USIMS | discussion | Intel Deutschland GmbH |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | |||
S3-201676 | New SID on the security of the system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) | SID new | Intel Deutschland GmbH |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | |||
S3-201677 | reply LS on AMF Reallocation via RAN re-routing |
LS out LS is reply to S2-2001730/S3-201528 LS To: SA2 |
ZTE Corporation | 5GS_Ph1, TEI16 | Rel-16 |
S3-100-e AI: 4.21 |
noted | [WTS] [JSN] | |
S3-201678 | Edirorials on 13.4.1.2 Service access authorization in roaming scenarios-R15 | CR | ZTE Corporation | 33.501 15.9.0 CR#887 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201679 | Edirorials on 13.4.1.2 Service access authorization in roaming scenarios-R16 |
CR revised to S3-202243 |
ZTE Corporation | 33.501 16.3.0 CR#888 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201680 | Add three Abbreviations to clause 3.3 |
CR revised to S3-202233 |
ZTE Corporation | 33.535 16.0.0 CR#1 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-201681 | Delete routing ID in A-KID | CR | ZTE Corporation | 33.535 16.0.0 CR#2 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201682 | Discussion on KAF update | discussion | ZTE Corporation | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
noted | [WTS] [JSN] | |
S3-201683 | Kaf update in clause 5.2 and 6.4.3 | CR | ZTE Corporation | 33.535 16.0.0 CR#3 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201684 | AUSF needs not store KAUSF | CR | ZTE Corporation | 33.535 16.0.0 CR#4 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201685 | Resolution of editor's note on other parameter in clause 6.3 | CR | ZTE Corporation | 33.535 16.0.0 CR#5 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201686 | Services Provided by AAnF in clause 7.1 | CR | ZTE Corporation | 33.535 16.0.0 CR#6 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-201687 | Services Provided by AUSF in clause 7.2 | CR | ZTE Corporation | 33.535 16.0.0 CR#7 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-201688 | Clarification of when to derive Kaf in UE | CR | ZTE Corporation | 33.535 16.0.0 CR#8 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201689 | Clarification of handling of the user plane security policy in clause 5.3.3.1.4.2.3 | CR | ZTE Corporation | 33.536 16.0.0 CR#3 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-201690 | Clean up for eV2X | CR | ZTE Corporation | 33.536 16.0.0 CR#4 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
merged | [WTS] [JSN] |
S3-201691 | Update the clause 5.3.3.1.4.3 | CR | ZTE Corporation | 33.536 16.0.0 CR#5 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-201692 | Update the clause 5.3.3.2.2 |
CR revised to S3-202232 |
ZTE Corporation | 33.536 16.0.0 CR#6 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-201693 | Updating IPUPS of UPF to Annex L of TR 33.926 | CR | ZTE Corporation | 33.926 16.3.0 CR#36 catB | SCAS_5G_IPUPS | Rel-17 |
S3-100-e AI: 4.2 |
not pursued | [WTS] [JSN] |
S3-201694 | New key issue on security for uplink time synchronization |
pCR revised to S3-202118 |
ZTE Corporation | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-201695 | New solution for key issue on security for uplink time synchronization | pCR | ZTE Corporation | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-201696 | New key issue on authorization for multicast communication services | pCR | ZTE Corporation | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
merged | [WTS] [JSN] |
S3-201697 | Key Issue: UE onboarding and provisioning for non-public networks | pCR | Intel Deutschland GmbH | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
merged | [WTS] [JSN] |
S3-201698 | Key Issue: Authentication using credentials owned by an entity separate from the SNPN UE onboarding and provisioning for non-public networks | pCR | Intel Deutschland GmbH | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
merged | [WTS] [JSN] |
S3-201699 | Solution to UE onboarding and provisioning for non-public networks | pCR | Intel Deutschland GmbH | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201700 | AKMA Anchor Key derivation in the UE | draftCR | CATT | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
withdrawn | [WTS] [JSN] | |
S3-201701 | Key Issue: Security Requirements for EDGE-1 Interface |
pCR revised to S3-202115 |
Intel Deutschland GmbH | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-201702 | key issue on security policy differentiation in CU-UPs |
pCR revision of S3-201667 |
China Telecommunications | 33.84 0.0.1 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-201703 | Key Issue: Security Requirements for EDGE-4 Interface |
pCR revised to S3-202116 |
Intel Deutschland GmbH | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-201704 | Skeleton for TR 33.840 |
draft TR revision of S3-201629 revised to S3-201705 |
China Telecommunications | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
revised | [WTS] [JSN] | |
S3-201705 | Skeleton for TR 33.840 |
draft TR revision of S3-201704 revised to S3-202229 |
China Telecommunications | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
approved | [WTS] [JSN] | |
S3-201706 | Key Issue: Security Requirements for EDGE-6 Interface |
pCR revised to S3-202117 |
Intel Deutschland GmbH | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-201707 | Reply LS to RAN2 on FBS detection |
LS out LS is reply to RAN2 LS To: RAN2 |
Huawei, HiSilicon | FS_5GFBS | Rel-17 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] | |
S3-201708 | Clarification for solution 4 | pCR | Huawei, HiSilicon | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201709 | Detection of MiTM False Base Station | pCR | Huawei, HiSilicon | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201710 | Editorial changes about subscript corrections |
CR revised to S3-202212 |
Huawei, Hisilicon | 33.536 16.0.0 CR#7 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-201711 | Propose to add descriptions about Knrp ID confliction | CR | Huawei, Hisilicon | 33.536 16.0.0 CR#8 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-201712 | Clarification on policy handling |
CR revised to S3-202213 |
Huawei, Hisilicon | 33.536 16.0.0 CR#9 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-201713 | Clarification on algorithm selection and key derivation |
CR revised to S3-202214 |
Huawei, Hisilicon | 33.536 16.0.0 CR#10 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-201714 | Clarification on processing null-algorithms |
CR revised to S3-202215 |
Huawei, Hisilicon | 33.536 16.0.0 CR#11 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-201715 | Propose to mitigate the bidding down attack | CR | Huawei, Hisilicon | 33.536 16.0.0 CR#12 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-201716 | Propose to complete security lagorithm selection for UP |
CR revised to S3-202216 |
Huawei, Hisilicon | 33.536 16.0.0 CR#13 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-201717 | Clarifications on error case in AKMA process |
CR revised to S3-202217 |
Huawei, Hisilicon | 33.535 16.0.0 CR#9 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-201718 | NAS security based MIB SIBs integrity protection | pCR | Huawei, Hisilicon | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201719 | New Key Issue on Security of the MBS service authentication and authorization |
pCR revised to S3-202120 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-201720 | New Key Issue on security protection of MBS traffic |
pCR revised to S3-202121 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-201721 | Scope for TR on MBS security |
pCR revised to S3-202122, S3-202123 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-201722 | Proposed Skeleton for MBS SID |
draft TR revised to S3-202124 |
Huawei, Hisilicon | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
approved | [WTS] [JSN] | |
S3-201723 | New Key Issue on key distribution |
pCR revised to S3-202125 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
revised | [WTS] [JSN] |
S3-201724 | New Key Issue on protection of UE-UE communication |
pCR revised to S3-202126 |
Huawei, Hisilicon | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-201725 | Conclusion on mitigation against the linkability attack | pCR | Huawei, Hisilicon | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-201726 | New Key Issue on protection of flight information in remote identification |
pCR revised to S3-202127 |
Huawei, Hisilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201727 | New key issue on authentication with credentials owned by an entity separate from the SNPN | pCR | Huawei, Hisilicon | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
merged | [WTS] [JSN] |
S3-201728 | New key issue on authentication and authorization for UE onboarding between UE and PNI-NPN | pCR | Huawei, Hisilicon | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201729 | New key issue on authentication and authorization for UE onboarding between UE and SNPN |
pCR revised to S3-202128 |
Huawei, Hisilicon | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-201730 | Reply LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN |
LS out LS To: SA2 |
Huawei, Hisilicon |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] | |||
S3-201731 | Alignment with RAN3 specification in R16 | CR | Huawei, Hisilicon | 33.501 16.3.0 CR#889 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201732 | Alignment with RAN3 specification in R15 | CR | Huawei, Hisilicon | 33.501 15.9.0 CR#890 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201733 | SUPI Type Clarification in R16 |
CR revised to S3-202236 |
Huawei, Hisilicon | 33.501 16.3.0 CR#891 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201734 | SUPI Type Clarification in R15 |
CR revised to S3-202237 |
Huawei, Hisilicon | 33.501 15.9.0 CR#892 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201735 | System Information Protection using On-boarding Credential in NPN | pCR | Huawei, Hisilicon | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201736 | New Study on Enhancement of Authorization of API Invocation |
SID new revised to S3-202235 |
Huawei, Hisilicon, China Unicom, CAICT, CATT |
S3-100-e AI: 5.16 |
revised | [WTS] [JSN] | |||
S3-201737 | Discussion on Enhancement of Authorization of API Invocation | discussion | Huawei, Hisilicon |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | |||
S3-201738 | Reply LS on User consent requirements for analytics |
LS out LS To: SA2 |
Huawei, Hisilicon |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201739 | Reply LS for IP address to GPSI translation |
LS out LS To: SA6 |
Huawei, Hisilicon |
S3-100-e AI: 5.9 |
postponed | [WTS] [JSN] | |||
S3-201740 | Scope of Study on security aspects of the disaggregated gNB Architecture | pCR | Huawei, Hisilicon | 33.84 0.0.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-201741 | New WID on Security Assurance Specification for NSSAAF |
WID new revised to S3-202221, S3-202255 |
Huawei, Hisilicon | Rel-17 |
S3-100-e AI: 4.22 |
revised | [WTS] [JSN] | ||
S3-201742 | Aware of AF‘s AKMA service capability in the UE | CR | Huawei, Hisilicon | 33.535 16.0.0 CR#10 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201743 | AMF selection in NSSAA related procedure in case of dual registration in different PLMNs | discussion | Huawei, Hisilicon | eNS | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201744 | AMF selection in NSSAA related procedure in case of dual registration in different PLMNs | CR | Huawei, Hisilicon | 33.501 16.3.0 CR#893 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201745 | Slice privacy protection in NSSAA related procedure | CR | Huawei, Hisilicon | 33.501 16.3.0 CR#894 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201746 | Correction to Nnssaaf_NSSAA services service |
CR revised to S3-202239, S3-202240 |
Huawei, Hisilicon | 33.501 16.3.0 CR#895 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201747 | Secondary authentication revocation |
CR revised to S3-202241 |
Huawei, Hisilicon | 33.501 15.9.0 CR#896 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201748 | Secondary authentication revocation |
CR revised to S3-202242 |
Huawei, Hisilicon | 33.501 16.3.0 CR#897 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201749 | New KI for EAS discovery |
pCR revised to S3-202119 |
Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-201750 | New KI for on Network Information Provisioning to Local Applications with low latency | pCR | Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-201751 | Adding HSS and BSF SBI services | draftCR | Huawei, Hisilicon | GBA_5G | Rel-17 |
S3-100-e AI: 4.14 |
merged | [WTS] [JSN] | |
S3-201752 | Architecture support complement | draftCR | Huawei, Hisilicon | GBA_5G | Rel-17 |
S3-100-e AI: 4.14 |
merged | [WTS] [JSN] | |
S3-201753 | The deployment of AAnF | CR | Huawei, Hisilicon | 33.535 16.0.0 CR#11 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201754 | Use routing ID to find AAnF | CR | Huawei, Hisilicon | 33.535 16.0.0 CR#12 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201755 | Reauthenticaiton in AKMA |
CR revised to S3-202218 |
Huawei, Hisilicon | 33.535 16.0.0 CR#13 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-201756 | Architecture Introduction in 5G Prose | pCR | Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-201757 | New key issue on key distribution in prose discovery scenario | pCR | Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-201758 | New key issue on discovery message protection |
pCR revised to S3-202129 |
Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201759 | New key issue on security of UE-to-Network Relay |
pCR revised to S3-202130 |
Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201760 | New key issue on security of one-to-one communication | pCR | Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-201761 | Threat analysis on NAS based redirection from 5GS to EPS |
draftCR revised to S3-202131 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-201762 | SCAS-NAS based redirection from 5GS to EPS |
draftCR revised to S3-202132 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-201763 | threat analysis on state transation |
draftCR revised to S3-202133 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-201764 | Add state transation to gNB SCAS |
draftCR revised to S3-202134 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-201765 | Threat analysis on the RLF scenario in Control Plane CIoT 5GS Optimization | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
noted | [WTS] [JSN] | |
S3-201766 | RRCReestablishment in Control Plane CIoT 5GS Optimization | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
noted | [WTS] [JSN] | |
S3-201767 | living doc to 33.117 |
draftCR revised to S3-202135 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-201768 | Adding AMF functionality in clause 4.2 | CR | CATT | 33.535 16.0.0 CR#14 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201769 | Adding details of AKMA key generation in the UE | CR | CATT | 33.535 16.0.0 CR#15 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201770 | Clarifying summary of threats for GVNP | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201771 | Adding security functional requirements derived from 3GPP specifications – general SBA SBI aspects | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201772 | Adding hardening requirements for GVNP of type 1 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201773 | Adding hardening requirements for GVNP of type 2 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201774 | Adding hardening requirements for GVNP of type 3 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201775 | Adding basic vulnerability testing requirements for GVNP | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201776 | Adding vendor development and product lifecycle processes and test laboratory accreditation into clause 6 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201777 | Adding evaluation and SCAS instantiation into clause 7 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201778 | Adding test case into clause 5.2.5.5.8.5.1 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201779 | Adding test case into clause 5.2.5.6.6.1 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201780 | Adding conclusion into clause 8 | pCR | China Mobile | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-201781 | Addressing editor note on transformation of S-NSSAI during NSSAA | CR | China Mobile | 33.501 16.3.0 CR#898 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201782 | new SID on security aspects of 5G MSG | SID new | China Mobile, China Unicom, Huawei, ZTE, CATT | Rel-16 |
S3-100-e AI: 5.16 |
agreed | [WTS] [JSN] | ||
S3-201783 | Discussion on new SID for security aspects of enablers for Network Automation (eNA) for the 5G System (5GS) Phase 2 | discussion | China Mobile | Rel-16 |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-201784 | new SID on security aspects of eNA phase2 |
SID new revised to S3-202256 |
China Mobile, Nokia, Nokia Shanghai Bell, Huawei, China Unicom, CATT, ZTE | Rel-16 |
S3-100-e AI: 5.16 |
revised | [WTS] [JSN] | ||
S3-201785 | Add abbreviations to TS 33.535 | CR | China Mobile | 33.535 16.0.0 CR#16 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-201786 | FC values allocation | CR | China Mobile | 33.535 16.0.0 CR#17 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-201787 | CR to TS 33.220-FC values allocation for AKMA | CR | China Mobile | 33.535 16.0.0 CR#18 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
withdrawn | [WTS] [JSN] |
S3-201788 | Correction of AKMA services in section 7 | CR | China Mobile | 33.535 16.0.0 CR#19 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-201789 | Adding AKMA context description | CR | China Mobile | 33.535 16.0.0 CR#20 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-201790 | Adding details on UE AKMA capability handling | CR | CATT | 33.535 16.0.0 CR#21 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201791 | Clarification on AKMA Application Key derivation in the UE | CR | CATT | 33.535 16.0.0 CR#22 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201792 | KI on UAV authentication and authorization | pCR | Nokia, Nokia Shanghai Bell | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201793 | SID on eSBA sec cont |
SID new revised to S3-202185 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-100-e AI: 5.16 |
revised | [WTS] [JSN] | ||
S3-201794 | Missing abbreviations | CR | Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#899 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-201795 | Alignment and clarifications to SBA network or transport layer protocol |
CR revised to S3-202181 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#900 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-201796 | N32 interface |
CR revised to S3-202046 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#901 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-201797 | Resolving ed note in 13.2.2.6 | CR | Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#902 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-201798 | Authentication and static authorization |
CR revised to S3-202183 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#903 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-201799 | Overview clause on communication models and related security |
CR revised to S3-202182 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#904 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-201800 | Authorization of NF service access |
CR revised to S3-202189 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#905 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-201801 | Integrity protection of service request |
CR revised to S3-202186 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#906 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-201802 | Re-using of access token in indirect communication with delegated discovery |
CR revised to S3-202883 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#907 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-201803 | Making NF instance id in SBA certificate profile mandatory to support |
CR revised to S3-202184 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#908 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-201804 | Draft skeleton of TR 33.847 | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-201805 | Modification on AAA Server triggered Slice-Specific Authorization Revocation procedure |
CR revised to S3-202245 |
CATT | 33.501 16.3.0 CR#909 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201806 | pCR to TR33.847-Scope |
pCR revised to S3-202144 |
CATT | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201807 | pCR to TR33.847-Key issue on ProSe UE-to-UE relay discovery | pCR | CATT | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201808 | pCR to TR33.847-Key issue on ProSe relays | pCR | CATT | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201809 | New SID on introducing penetration test |
SID new revised to S3-202234 |
Huawei, Hisilicon | Rel-17 |
S3-100-e AI: 5.16 |
revised | [WTS] [JSN] | ||
S3-201810 | Discussion paper for Rel17 SID on network slicing security | discussion | Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT | Rel-17 |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-201811 | Rel17 SID on network slice security | SID new | Huawei, HiSilicon, Lenovo, Motorola Mobility, CableLab, CATT, CAICT | Rel-17 |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-201812 | Discussion on validity period | discussion | Huawei, HiSilicon | FS_eNS_SEC | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201813 | validity peirod of NSSAA results | CR | Huawei, HiSilicon | 33.501 16.3.0 CR#910 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201814 | Discussion on SN-ID in NSSAA | discussion | Huawei, HiSilicon | eNS | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201815 | Serving network name in NSSAA | CR | Huawei, HiSilicon | 33.501 16.3.0 CR#911 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201816 | Clarification on binding of NSSAI and UE ID at AAA-S | CR | Huawei, HiSilicon | 33.501 16.3.0 CR#912 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201817 | Editorial changes to clause 16 |
CR revised to S3-202231 |
Huawei, HiSilicon | 33.501 16.3.0 CR#913 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201818 | New KI: UAV/UAV-C authentication and authorization |
pCR revised to S3-202111 |
Huawei, HiSilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201819 | New KI: UAV and UAV-C pairing security |
pCR revised to S3-202112 |
Huawei, HiSilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201820 | New KI: privacy in remote Identification | pCR | Huawei, HiSilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201821 | New KI: TPAE security |
pCR revised to S3-202113 |
Huawei, HiSilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201822 | Introduction: Overview of Unmanned Aerial Systems | pCR | Huawei, HiSilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201823 | A solution to UAV/UAV-C authentication and authorization |
pCR revised to S3-202114 |
Huawei, HiSilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201824 | A solution to UAV/UAV-C pairing authorization | pCR | Huawei, HiSilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-201825 | New KI: Authentication and authorization checkpoint for PNI-NPN | pCR | Huawei, HiSilicon | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201826 | Definitions and abbreviations | pCR | Huawei, HiSilicon | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-201827 | Scope of Prose Security | pCR | Huawei, HiSilicon | 33.847 0.1.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201828 | New Key Issue on user ID privacy | pCR | Huawei, Hisilicon | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201829 | New Key Issue on secure provisioning between provisioning server and UE | pCR | Huawei, Hisilicon | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
merged | [WTS] [JSN] |
S3-201830 | New Key Issue on service provisioning | pCR | Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-201831 | New Key Issue on service consuming | pCR | Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-201832 | New Key Issue on EES capability exposure to EAS | pCR | Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-201833 | EC: Scope for edge computing SID | pCR | Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-201834 | Skeleton for edge computing SID |
draft TR revised to S3-202073 |
Huawei, Hisilicon | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] | |
S3-201835 | EC: New Key issue on the transport security for the EDGE-1-9 |
pCR revised to S3-202074 |
Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-201836 | 5G ProSe: New Key issue on authorization in the UE-to-UE relay scenario |
pCR revised to S3-202146 |
Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201837 | 5G ProSe: New Key issue on authorization in the UE-to-Network relay scenario |
pCR revised to S3-202147 |
Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201838 | Clarification on the UP security configuration checking |
CR revised to S3-202210 |
Huawei, Hisilicon | 33.536 16.0.0 CR#14 catB | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
S3-201839 | Clarification on the UP security policy activation | CR | Huawei, Hisilicon | 33.536 16.0.0 CR#15 catB | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-201840 | Clarification on the test cases if the UDM and AUSF are collocated |
CR revised to S3-202228 |
Huawei, Hisilicon | 33.514 16.2.0 CR#3 catF | SCAS_5G | Rel-16 |
S3-100-e AI: 4.2 |
revised | [WTS] [JSN] |
S3-201841 | Change the long-lived TLS connection of N32-C to the short-lived |
CR revised to S3-202208 |
Huawei, Hisilicon | 33.501 15.9.0 CR#914 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201842 | Mirror: change the long-lived TLS connection of N32-C to the short-lived |
CR revised to S3-202209 |
Huawei, Hisilicon | 33.501 16.3.0 CR#915 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201843 | Update the N32-f context ID negotiation procedure |
CR revised to S3-202211 |
Huawei, Hisilicon | 33.501 15.9.0 CR#916 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201844 | Mirror: update the N32-f context ID negotiation procedure |
CR revised to S3-202222 |
Huawei, Hisilicon | 33.501 16.3.0 CR#917 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201845 | Enhancement on the client credentials assertion verification | CR | Huawei, Hisilicon | 33.501 16.3.0 CR#918 catF | 5GS_Ph1-SEC, TEI16 | Rel-16 |
S3-100-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-201846 | Threats related to security enforcement configuration for vertical LAN | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
noted | [WTS] [JSN] | |
S3-201847 | New test case on security enforcement configuration for vertical LAN | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
noted | [WTS] [JSN] | |
S3-201848 | Discussion on the N32-f Protection Policy IE Data-Type Mapping issue | discussion | Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201849 | Reply LS on N32-f Protection Policy IE Data-Type Mapping |
LS out LS To: 5GIS, CT4 revised to S3-202224 |
Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-201850 | Clarification on the Data-type encryption policy | CR | Huawei, Hisilicon | 33.501 16.3.0 CR#919 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-201851 | IMS SCAS: adding the Introduction part |
pCR revised to S3-202075 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-201852 | IMS SCAS: Assets and threats of the IMS product classes |
draftCR revised to S3-202149 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] | |
S3-201853 | IMS SCAS: adding threats related to de-registration during the authentication | draftCR | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-201854 | IMS SCAS: new test case on de-registration |
pCR revised to S3-202077 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-201855 | Threats specific of high-priority algorithm selection in the P-CSCF |
draftCR revised to S3-202078 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] | |
S3-201856 | IMS SCAS: new test case on high-priority algorithm selection in the P-CSCF |
pCR revised to S3-202079, S3-202080 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-201857 | Threats specific of bidding down on security association set-up |
draftCR revised to S3-202081, S3-202153 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] | |
S3-201858 | IMS SCAS: new test case on bidding down on security association set-up |
pCR revised to S3-202082 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-201859 | Threats specific of unprotected register message | draftCR | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-201860 | IMS SCAS: new test case on unprotected register message |
pCR revised to S3-202083 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-201861 | Resolving the EN of solution#5 in the TR 33.809 | pCR | Huawei, Hisilicon, Lenovo | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201862 | LS out on AMF reallocation via RAN |
LS out LS is reply to S3-201528 LS To: SA2 |
Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-17 |
S3-100-e AI: 4.21 |
approved | [WTS] [JSN] | |
S3-201863 | Discussion on UE privacy in GBA | discussion | Huawei, Hisilicon | GBA_5G | Rel-17 |
S3-100-e AI: 4.14 |
noted | [WTS] [JSN] | |
S3-201864 | Adding security requirement on UE privacy | draftCR | Huawei, Hisilicon | GBA_5G | Rel-17 |
S3-100-e AI: 4.14 |
noted | [WTS] [JSN] | |
S3-201865 | Revocation of 5G multicast service authorization | pCR | Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
noted | [WTS] [JSN] |
S3-201866 | SHA-1 deprecation in GBA | CR | Huawei, Hisilicon | 33.22 16.1.0 CR#201 catF | TEI17 | Rel-17 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-201867 | Clarification of direct NAS reroute |
CR revised to S3-202206 |
Huawei, Hisilicon | 33.501 15.9.0 CR#920 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201868 | Mirror:Clarification of direct NAS reroute |
CR revised to S3-202207 |
Huawei, Hisilicon | 33.501 16.3.0 CR#921 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201869 | FC values for TS 33.535 | CR | China Mobile Com. Corporation | 33.22 16.1.0 CR#202 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-201870 | Selecting the authentication method for devices that do not support 5GC NAS over WLAN access | CR | Lenovo, Motorola Mobility | 33.501 16.3.0 CR#922 catF | 5WWC | Rel-16 |
S3-100-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-201871 | pCR: Conclusion of Key issue#5 | pCR | Lenovo, Motorola Mobility, Huawei | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201872 | pCR: Removal of Editor’s Note in solution #15 | pCR | Lenovo, Motorola Mobility, Huawei | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201873 | Clarification to SEAF |
CR revision of S3-201493 revised to S3-202813 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#8352 catF | 5GS_Ph1-SEC, TEI16 | Rel-16 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-201874 | Status of RFC 5448bis update |
discussion revision of S3-201147 |
Ericsson |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] | |||
S3-201875 | Key Issue to support SNPN along with credentials owned by an entity separate from the SNPN | pCR | Lenovo, Motorola Mobility | 33.857 0.0.0 | FS_UAS_SEC, FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
merged | [WTS] [JSN] |
S3-201876 | Key Issue on privacy protection for broadcast messages | pCR | Lenovo, Motorola Mobility | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-201877 | Discussion Anonymous IDs | discussion | Ericsson LM | Rel-16 |
S3-100-e AI: 4.9 |
noted | [WTS] [JSN] | ||
S3-201878 | Clarification to 5G AV |
CR revision of S3-201492 revised to S3-202253 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#8342 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.21 |
revised | [WTS] [JSN] |
S3-201879 | gNB-specific adaptation to account protection by authentication attribute | CR | Nokia, Nokia Shanghai Bell | 33.511 16.4.0 CR#15 catF | SCAS_5G | Rel-16 |
S3-100-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-201880 | gNB-specific adaptation to minimum number of individual accounts | CR | Nokia, Nokia Shanghai Bell | 33.511 16.4.0 CR#16 catF | SCAS_5G | Rel-16 |
S3-100-e AI: 4.2 |
not pursued | [WTS] [JSN] |
S3-201881 | Anonymous SUCI for N5GC | CR | Ericsson LM | 33.501 16.3.0 CR#923 catF | 5WWC | Rel-16 |
S3-100-e AI: 4.9 |
not pursued | [WTS] [JSN] |
S3-201882 | gNB-specific adaptation to enforcement of password change after initial login | CR | Nokia, Nokia Shanghai Bell | 33.511 16.4.0 CR#17 catF | SCAS_5G | Rel-16 |
S3-100-e AI: 4.2 |
not pursued | [WTS] [JSN] |
S3-201883 | eNB-specific adaptation to account protection by authentication attribute R15 | CR | Nokia, Nokia Shanghai Bell | 33.216 15.2.0 CR#16 catF | SCAS_eNB | Rel-15 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-201884 | eNB-specific adaptation to account protection by authentication attribute R16 | CR | Nokia, Nokia Shanghai Bell | 33.216 16.4.0 CR#17 catA | SCAS_eNB | Rel-16 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-201885 | eNB-specific adaptation to minimum number of individual accounts R15 | CR | Nokia, Nokia Shanghai Bell | 33.216 15.2.0 CR#18 catF | SCAS_eNB | Rel-15 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-201886 | eNB-specific adaptation to minimum number of individual accounts R16 | CR | Nokia, Nokia Shanghai Bell | 33.216 16.4.0 CR#19 catA | SCAS_eNB | Rel-16 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-201887 | eNB-specific adaptation to enforcement of password change after initial login R15 | CR | Nokia, Nokia Shanghai Bell | 33.216 15.2.0 CR#20 catF | SCAS_eNB | Rel-15 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-201888 | eNB-specific adaptation to enforcement of password change after initial login R16 | CR | Nokia, Nokia Shanghai Bell | 33.216 16.4.0 CR#21 catA | SCAS_eNB | Rel-16 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-201889 | Correction to SN Addition or modification |
CR revised to S3-202175 |
Lenovo, Motorola Mobility | 33.501 16.3.0 CR#924 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201890 | Key Issue on User Plane Security Compromise | pCR | Lenovo, Motorola Mobility | 33.84 0.0.2 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-201891 | Threat analysis of incorrect validation of client credentials assertion |
draftCR revised to S3-202140 |
Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-201892 | Test case for correct handling of client credentials assertion validation failure |
draftCR revised to S3-202141 |
Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
revised | [WTS] [JSN] | |
S3-201893 | Key Issue on Security of Command and Control Communication |
pCR revised to S3-202155 |
Lenovo, Motorola Mobility | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201894 | 5GFBS-RRCResumeRequest message protection | pCR | Apple, CableLabs | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201895 | 5GFBS-Way forward on DoS attack caused by modifying the signature | pCR | Apple | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201896 | 5GFBS-Way forward on bidding down attack | pCR | Apple | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201897 | 5GFBS-Way forward on replay attack | pCR | Apple | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201898 | 5GFBS-Add a NOTE in the key issue#7 on the MitM attack | pCR | Apple | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201899 | 5GFBS-Addressing EN on how to prevent UE camping on the FBS for solution#11 | pCR | Apple | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201900 | 5GFBS-Addressing EN on MitM attack for solution #11 | pCR | Apple | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201901 | 5GFBS-Draft reply LS to RAN2 on reply LS to SA3 on FBS detection(R2-1914224/S3-200944) |
LS out LS is reply to RAN2 LS To: RAN2 |
Apple | Rel-17 |
S3-100-e AI: 5.2 |
withdrawn | [WTS] [JSN] | ||
S3-201902 | MEC-New key issue on DNS address modification | pCR | Apple | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-201903 | MEC-New Solution on mitigating DNS request modification attack | pCR | Apple | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-201904 | MEC-New key issue on user consent on sharing sensitive information | pCR | Apple | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-201905 | MEC-Reply LS to SA6 (S6-200947) on the protection of user’s consent |
LS out LS To: SA6 |
Apple | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
noted | [WTS] [JSN] | |
S3-201906 | MEC-New key issue on authentication based on 3GPP credentials | pCR | Apple | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-201907 | MEC-New solution on authentication based on 3GPP credentials |
pCR revised to S3-202151 |
Apple | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-201908 | ProSe- New key issue on privacy protection in authentication procedure via UE-to-network relay | pCR | Apple | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201909 | ProSe- New key issue on PC5 security against UE-to-UE relay | pCR | Apple | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-201910 | ProSe- New solution on security of UE-to-UE relay | pCR | Apple | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-201911 | UP IP-New solution to address key issue#5 | pCR | Apple | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-201912 | Discussion paper on the NAS COUNTs storage | discussion | Apple | Rel-15 |
S3-100-e AI: 4.21 |
noted | [WTS] [JSN] | ||
S3-201913 | Draft LS to CT6 on the NAS COUNTs storage |
LS out LS To: CT6 |
Apple | Rel-15 |
S3-100-e AI: 4.21 |
noted | [WTS] [JSN] | ||
S3-201914 | Correction of the full form of the abbreviation NRF | CR | Ericsson | 33.501 15.9.0 CR#925 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201915 | Correction of the full form of the abbreviation NRF | CR | Ericsson | 33.501 16.3.0 CR#926 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201916 | Verification of Serving Network Name in AUSF | discussion | Ericsson |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201917 | Verification of Serving Network Name in AUSF | CR | Ericsson | 33.501 15.9.0 CR#927 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201918 | Verification of Serving Network Name in AUSF | CR | Ericsson | 33.501 16.3.0 CR#928 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201919 | Aligning steering of roaming security mechanism with TS 29.509, TS 29.503 and TS 24.501 | CR | Ericsson | 33.501 15.9.0 CR#929 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201920 | Aligning steering of roaming security mechanism with TS 29.509, TS 29.503 and TS 24.501 | CR | Ericsson | 33.501 16.3.0 CR#930 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201921 | Draft LS on Misalignment between TS 33.501 and TS 29.573 (N32-f, references to the encrypted values) |
LS out LS To: CT4 |
Ericsson, NCSC | Rel-15 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-201922 | Aligning TS 33.501 with TS 29.573 regarding N32-f context ID | CR | Ericsson | 33.501 15.9.0 CR#931 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201923 | Aligning TS 33.501 with TS 29.573 regarding N32-f context ID | CR | Ericsson | 33.501 16.3.0 CR#932 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201924 | Token request parameters in Scenario D | CR | Ericsson | 33.501 16.3.0 CR#933 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-201925 | New KI: Support of IMS voice and emergency services for SNPN | pCR | Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-201926 | Clean-up, including removal of Editor's Notes | CR | Ericsson | 33.855 16.0.0 CR#1 catF | FS_SBA_Sec | Rel-16 |
S3-100-e AI: 5.15 |
agreed | [WTS] [JSN] |
S3-201927 | pCR to TR 33.845: Location of ARPF functionality |
pCR revised to S3-202061 |
Ericsson | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
revised | [WTS] [JSN] |
S3-201928 | Location of ARPF functionality | CR | Ericsson | 33.501 16.3.0 CR#934 catF | TEI16 | Rel-16 |
S3-100-e AI: 5.7 |
not pursued | [WTS] [JSN] |
S3-201929 | Proposed removal of a redundant Editor’s Note from key issue #4.1 | pCR | Qualcomm Incorporated | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-201930 | Some evaluation of solution#2.1 in TR 33.846 |
pCR revised to S3-202643 |
Qualcomm Incorporated | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-201931 | Some evaluation of solution #2.2 in TR 33.846 |
pCR revised to S3-202094, S3-202644 |
Qualcomm Incorporated | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-201932 | Some evaluation of solution #2.3 in TR 33.846 |
pCR revised to S3-202645 |
Qualcomm Incorporated | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-201933 | Some evaluation of solution #2.5 in TR 33.846 |
pCR revised to S3-202646 |
Qualcomm Incorporated | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-201934 | Resolving the editor’s notes in the solution #4.1 | pCR | Qualcomm Incorporated | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-201935 | Proposing a conclusion for key issue #4.1 |
pCR revised to S3-202647 |
Qualcomm Incorporated | 33.846 0.6.1 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-201936 | Adding MACS as an input parameter to the calculation of AK* to provide freshness |
CR revision of S3-191529 |
Qualcomm Incorporated | 33.102 16.0.0 CR#2772 catF | TEI17 | Rel-17 |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] |
S3-201937 | Proposed scope for TR 33.854 on UAS security |
other revised to S3-202095 |
Qualcomm Incorporated |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] | |||
S3-201938 | Adding a reference to the UAS architecture from TS 23.754 |
pCR revised to S3-202096 |
Qualcomm Incorporated | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-201939 | Proposal to add a key issue on authorising UAV to use the 3GPP network | other | Qualcomm Incorporated |
S3-100-e AI: 5.8 |
merged | [WTS] [JSN] | |||
S3-201940 | Solving key issue #7 on moving bearer that require UP IP to EPS using the existing methods |
pCR revised to S3-202097 |
Qualcomm Incorporated | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-201941 | Enhancements to UPIP Support in 5GS |
WID new revised to S3-202202 |
Qualcomm Incorporated |
S3-100-e AI: 4.22 |
revised | [WTS] [JSN] | |||
S3-201942 | Clarification on the unicast privacy procedures | CR | Qualcomm Incorporated | 33.536 16.0.0 CR#16 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
S3-201943 | Updates to Abbreviations and Corrections and clarifications to clause 4 |
CR revised to S3-202203 |
Qualcomm Incorporated | 33.535 16.0.0 CR#23 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-201944 | Corrections to AKMA key lifetimes |
CR revised to S3-202204 |
Qualcomm Incorporated | 33.535 16.0.0 CR#24 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-201945 | Corrections and clarifications to AKMA procedures |
CR revised to S3-202205 |
Qualcomm Incorporated | 33.535 16.0.0 CR#25 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-201946 | Assignment of FC values for key derivations |
CR revised to S3-202168 |
Qualcomm Incorporated | 33.535 16.0.0 CR#26 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-201947 | Assigning FC values for AKMA TS |
CR revised to S3-202169 |
Qualcomm Incorporated | 33.22 16.1.0 CR#203 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-201948 | Specification of value of SUPI for key derivations | CR | Qualcomm Incorporated | 33.535 16.0.0 CR#27 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-201949 | Key Issue on PC5 link establishment for UE-to-network relay | other | Qualcomm Incorporated |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] | |||
S3-201950 | Reply LS on Security Requirements for Sidelink/PC5 Relays |
LS out LS is reply to S3-201536 LS To: SA2, RAN2, RAN3 |
Qualcomm Incorporated |
S3-100-e AI: 5.1 |
noted | [WTS] [JSN] | |||
S3-201951 | Key Issue on transport security for MBS flows | other | Qualcomm Incorporated |
S3-100-e AI: 5.12 |
merged | [WTS] [JSN] | |||
S3-201952 | Conclusion of Key Issue #3 | pCR | Qualcomm Incorporated | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-201953 | Reply LS on architectures for access to SNPNs using credentials owned by an entity separate from the SNPN |
LS out LS is reply to S3-201529 LS To: SA2 |
Qualcomm Incorporated |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] | |||
S3-201954 | Reply LS on 5G SoR integrity protection mechanism |
LS out LS is reply to S3-201511 LS To: CT4 |
Qualcomm Incorporated |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201955 | Reply LS on 256 bit algorithm candidates |
LS out LS is reply to S3-201540 LS To: ETSI SAGE |
Qualcomm Incorporated |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201956 | UPIP: Update to solution #11 (UP IP over eUTRA connected to EPS) |
pCR revised to S3-202086 |
Ericsson | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-201957 | UPIP: Update to solution #12, resolving editor note | pCR | Ericsson | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-201958 | [Draft] Reply LS on key management procedure in SEAL |
LS out source LS: C3-203588 LS To: CT3 |
Samsung | SEAL | Rel-16 |
S3-100-e AI: 4.12 |
merged | [WTS] [JSN] | |
S3-201959 | [SEAL] CR for TS 33.434 cleanup |
CR revised to S3-202170 |
Samsung | 33.434 16.0.0 CR#2 catF | SEAL | Rel-16 |
S3-100-e AI: 4.12 |
revised | [WTS] [JSN] |
S3-201960 | Key issue on key management in 5G ProSe |
pCR revised to S3-202064 |
Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201961 | Key management in 5G ProSe |
pCR revised to S3-202065 |
Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201962 | Key issue on handling security policies in ProSe relay communication | pCR | Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-201963 | Handling security policies in ProSe relay communication | pCR | Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
noted | [WTS] [JSN] |
S3-201964 | Key issue on secure data transfer between UE and 5GDDNMF in ProSe |
pCR revised to S3-202066 |
Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201965 | Secure data transfer between UE and 5GDDNMF in ProSe |
pCR revised to S3-202067 |
Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
revised | [WTS] [JSN] |
S3-201966 | [AKMA] Service Update to clause 6.1, 6.2 and 7.1 | CR | Samsung | 33.535 16.0.0 CR#28 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-201967 | [AKMA] Deletion of service provided by AUSF in clause 7.2 | CR | Samsung | 33.535 16.0.0 CR#29 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
merged | [WTS] [JSN] |
S3-201968 | Support for context deregistration option in AKMA | CR | Samsung | 33.535 16.0.0 CR#30 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-201969 | Key issue on authentication/authorization of Edge Enabler Client | pCR | Samsung | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-201970 | Authentication/authorization framework for Edge Enabler Client and server |
pCR revised to S3-202062 |
Samsung | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-201971 | Key issue on user's consent for exposure of information to Edge Application |
pCR revised to S3-202063 |
Samsung | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-201972 | User's consent for exposure of information to Edge Application | pCR | Samsung | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-201973 | Key issue on UP keys for Disaggregated gNB architecture | pCR | Samsung | 33.84 0.0.0 | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
noted | [WTS] [JSN] |
S3-201974 | Reply LS on 5G-GUTI reallocation after paging of a UE in 5GMM-IDLE mode with suspend indication |
LS out source LS: C1-200967 LS To: CT1 |
Samsung, Qualcomm Incorporated, Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.8 |
noted | [WTS] [JSN] | |
S3-201975 | Alignment of SoR procedures to Stage-3 | CR | Samsung | 33.501 15.9.0 CR#935 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201976 | Alignment of SoR procedures to Stage-3 | CR | Samsung | 33.501 16.3.0 CR#936 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201977 | Allocation of FC values for KIAB derivation function |
CR revised to S3-202172 |
Samsung | 33.501 16.3.0 CR#937 catF | NR_IAB | Rel-16 |
S3-100-e AI: 4.11 |
revised | [WTS] [JSN] |
S3-201978 | Allocation of FC values for IAB key derivation function | CR | Samsung | 33.22 16.1.0 CR#204 catF | NR_IAB | Rel-16 |
S3-100-e AI: 4.11 |
merged | [WTS] [JSN] |
S3-201979 | [5GFBS] Resume Cause protection |
pCR revised to S3-202018 |
Samsung | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-201980 | Removal of response from gNB to the AMF after inter-gNB-CU HO | CR | Samsung | 33.501 16.3.0 CR#938 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-201981 | Updates on Rel-16 IAB Conclusions | pCR | Samsung | 33.824 0.6.0 | FS_NR_IAB_Sec | Rel-16 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-201982 | Clean-up of IAB TR 33.824 | pCR | Samsung | 33.824 0.6.0 | FS_NR_IAB_Sec | Rel-16 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-201983 | Roaming case for indirect communication | CR | Ericsson | 33.501 16.3.0 CR#939 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
withdrawn | [WTS] [JSN] |
S3-201984 | [DRAFT] Reply-LS on 256-bit algorithm candidates |
LS out LS To: ETSI SAGE |
Ericsson |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-201985 | Reply-LS on user consent requirements for analytics |
LS out LS To: SA WG2 |
Nokia Germany | Rel-17 |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | ||
S3-201986 | eNPN Proposed TR Assumptions |
pCR revised to S3-202091 |
Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-201987 | eNPN New KI: Credentials owned by an external entity |
pCR revised to S3-202092 |
Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-201988 | eNPN New KI: Initial Access | pCR | Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201989 | eNPN New KI: Provisioning |
pCR revised to S3-202093 |
Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-201990 | eNPN [DRAFT] LS on AAA based solutions for credentials owned by an entity separate from the SNPN |
LS out LS is reply to S2-200438 LS To: SA2 |
Ericsson |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] | |||
S3-201991 | CIoT: Converting remaining ENs into Notes | CR | Ericsson | 33.861 16.0.0 CR#1 catF | FS_CIoT_sec_5G | Rel-16 |
S3-100-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-201992 | CIoT: Converting TBDs to notes | CR | Ericsson | 33.861 16.0.0 CR#2 catF | FS_CIoT_sec_5G | Rel-16 |
S3-100-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-201993 | CIoT: Adding missing references | CR | Ericsson | 33.861 16.0.0 CR#3 catF | FS_CIoT_sec_5G | Rel-16 |
S3-100-e AI: 4.8 |
agreed | [WTS] [JSN] |
S3-201994 | eNPN TR scope | pCR | Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201995 | eNPN TR Definitions | pCR | Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-201996 | SCAS SCP: Requirements and test cases of SBA/SBI aspects |
pCR revised to S3-202138 |
Nokia, Nokia Shanghai Bell | 33.522 0.1.0 | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
revised | [WTS] [JSN] |
S3-201997 | Critical Assets of SCP |
draftCR revised to S3-202139 |
Nokia, Nokia Shanghai Bell | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
revised | [WTS] [JSN] | |
S3-201998 | Analysis of threats over SCP internal network interfaces | draftCR | Nokia, Nokia Shanghai Bell | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
noted | [WTS] [JSN] | |
S3-201999 | SCAS SCP: Requirement and Test Case for Protection over Internal Interfaces | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.1.0 | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
noted | [WTS] [JSN] |
S3-202000 | Threat analysis of tokens forwarded by the SCP | draftCR | Nokia, Nokia Shanghai Bell | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
noted | [WTS] [JSN] | |
S3-202001 | pCR to TR33.853 - Updates to solution 14 |
pCR revised to S3-202258 |
VODAFONE Group Plc | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-202002 | Update of the OAuth Proof-of-Possession security architecture reference | CR | Ericsson | 33.203 13.3.0 CR#253 catF | eWebRTCi | Rel-13 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-202003 | Update of the OAuth Proof-of-Possession security architecture reference | CR | Ericsson | 33.203 14.2.0 CR#254 catA | eWebRTCi | Rel-14 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-202004 | Update of the OAuth Proof-of-Possession security architecture reference | CR | Ericsson | 33.203 15.2.0 CR#255 catA | eWebRTCi | Rel-15 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-202005 | Update of the OAuth Proof-of-Possession security architecture reference | CR | Ericsson | 33.203 16.0.0 CR#256 catA | eWebRTCi | Rel-16 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-202006 | SCAS SCP: Token forwarded to the current pNF | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.1.0 | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
noted | [WTS] [JSN] |
S3-202007 | SCAS SCP: Correct Token forwarded to the pNF | pCR | Nokia, Nokia Shanghai Bell | 33.522 0.1.0 | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
noted | [WTS] [JSN] |
S3-202008 | pCR to TR33.853 - Addition of solution addressing KI#8 |
pCR revised to S3-202257 |
VODAFONE Group Plc | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
revised | [WTS] [JSN] |
S3-202009 | DSnF improvements in time synchronization |
pCR revised to S3-202108 |
Philips International B.V. | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-202010 | SCAS VNP: Threats on VNF-VNFM Interface | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-202011 | SCAS VNP: Security requirements on the interface between VNF and VNFM | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-202012 | SCAS VNP: Software Tampering | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-202013 | SCAS VNP: VM Escape and Hypervisor Escape | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-202014 | SCAS VNP: Secure Execution Environment | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-202015 | SCAS VNP: DoS Attack via Changing Virtualized Resource | pCR | Nokia, Nokia Shanghai Bell | 33.818 0.7.0 | FS_VNP_SECAM_SCAS | Rel-16 |
S3-100-e AI: 5.3 |
noted | [WTS] [JSN] |
S3-202016 | 5GFBS: Detecting FBS based on UE Positioning Measurements |
pCR revised to S3-202142 |
Nokia, Nokia Shanghai Bell | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-202017 | eNPN Proposed TR Introduction |
pCR revised to S3-202089 |
Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
revised | [WTS] [JSN] |
S3-202018 | [5GFBS] Resume Cause protection |
pCR revision of S3-201979 |
Samsung | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
noted | [WTS] [JSN] |
S3-202019 | pCR to TR 33.846: editorial corrections for solution #2.4 |
pCR revised to S3-202070 |
THALES | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
revised | [WTS] [JSN] |
S3-202020 | pCR to TR 33.846: evaluation of solution #2.4 | pCR | THALES | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-202021 | ProSe: KI for Provisioning of ProSe parameters | pCR | Ericsson | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-202022 | ProSe: KI for Open Discovery | pCR | Ericsson | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-202023 | ProSe: KI for Restricted discovery | pCR | Ericsson | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-202024 | ProSe: KI for UE-to-network Relay | pCR | Ericsson | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-202025 | ProSe: KI for UE-to-UE Relay | pCR | Ericsson | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
merged | [WTS] [JSN] |
S3-202026 | Cryptographic CRC in MAC to avoid MitM relay nodes |
pCR revised to S3-202109 |
Philips International B.V. | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
revised | [WTS] [JSN] |
S3-202027 | Living document of Service Based Interfaces for GBA | draftCR | Ericsson | GBA_5G | Rel-16 |
S3-100-e AI: 4.14 |
noted | [WTS] [JSN] | |
S3-202028 | Living document of Service Based Interfaces for GBA Push | draftCR | Ericsson | GBA_5G | Rel-16 |
S3-100-e AI: 4.14 |
noted | [WTS] [JSN] | |
S3-202029 | pCR to living document for TS 33.220: SBA support for Zh and Zn interfaces |
draftCR revised to S3-202069 |
Ericsson | GBA_5G | Rel-16 |
S3-100-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-202030 | pCR to living document for TS 33.223: SBA support for Zpn interface |
draftCR revised to S3-202071 |
Ericsson | GBA_5G | Rel-16 |
S3-100-e AI: 4.14 |
revised | [WTS] [JSN] | |
S3-202031 | Discussion of HSS role in supporting SBA for GBA | discussion | Ericsson | GBA_5G |
S3-100-e AI: 4.14 |
noted | [WTS] [JSN] | ||
S3-202032 | Proposal for a new study on AMF re-allocation security | discussion | Ericsson |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | |||
S3-202033 | New study on the security of AMF re-allocation |
SID new revised to S3-202252 |
Ericsson |
S3-100-e AI: 5.16 |
revised | [WTS] [JSN] | |||
S3-202034 | Handling of counter wrap around in UDM | CR | Ericsson | 33.501 16.3.0 CR#940 catF | TEI16 | Rel-16 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-202035 | Storage of KAUSF in the UE and AUSF | CR | Ericsson | 33.501 16.3.0 CR#941 catF | TEI16 | Rel-16 |
S3-100-e AI: 4.21 |
not pursued | [WTS] [JSN] |
S3-202036 | AKMA Anchor Function selection clause | CR | Ericsson | 33.535 16.0.0 CR#31 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202037 | AKMA SBA interface clarifications |
CR revised to S3-202246 |
Ericsson | 33.535 16.0.0 CR#32 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-202038 | AKMA reference point architecture specification | CR | Ericsson | 33.535 16.0.0 CR#33 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
not pursued | [WTS] [JSN] |
S3-202039 | Several clarifications and editorials |
CR revised to S3-202247 |
Ericsson | 33.535 16.0.0 CR#34 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] |
S3-202040 | Discussion of the AKMA reference point interface names | discussion | Ericsson | AKMA |
S3-100-e AI: 4.7 |
noted | [WTS] [JSN] | ||
S3-202041 | LS on Reference point interface names for AKMA |
LS out LS To: SA2 revised to S3-202250 |
Ericsson | AKMA |
S3-100-e AI: 4.7 |
revised | [WTS] [JSN] | ||
S3-202042 | Discussion paper on removal of invalid authentication result in UDM | discussion | Ericsson | FS_AUTH_ENH |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] | ||
S3-202043 | LS on Removal of invalid authentication result in UDM |
LS out LS To: CT4 |
Ericsson | FS_AUTH_ENH |
S3-100-e AI: 5.6 |
noted | [WTS] [JSN] | ||
S3-202044 | Authentication Result Confirmation | CR | Ericsson | 33.501 16.3.0 CR#942 catF | TEI16 | Rel-16 |
S3-100-e AI: 5.6 |
not pursued | [WTS] [JSN] |
S3-202045 | pCR to TR33.853 - Update to section 4 | pCR | VODAFONE Group Plc | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-202046 | N32 interface |
CR revision of S3-201796 revised to S3-202180 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9011 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-202047 | pCR to 55.853 - Addition of conclusions | pCR | VODAFONE Group Plc | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
noted | [WTS] [JSN] |
S3-202048 | Draft LS Response on Clarification on AAA-Server address |
LS out LS is reply to S3-201512 source LS: C4-203452 LS To: CT4, SA2 |
Ericsson | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-202049 | Clarifications to SoR integrity protection mechanism |
CR revised to S3-202248 |
Orange | 33.501 15.9.0 CR#943 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-202050 | Clarifications to SoR integrity protection mechanism |
CR revised to S3-202249 |
Orange | 33.501 16.3.0 CR#944 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-202051 | Completion of WT-456 and WT-470 | LS in | BBF |
S3-100-e AI: 4.9 |
noted | [WTS] [JSN] | |||
S3-202052 | LS from RIFS to SA on 4G authentication improvement |
LS in LS reply in S3-202173 |
GSMA |
S3-100-e AI: 3 |
replied to | [WTS] [JSN] | |||
S3-202053 | LS on initiation of new work item Q.Pro-Trust “Signalling procedures and protocols for enabling interconnection between trustable network entities in support of existing and emerging networks” | LS in | ITU-T SG11 |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202054 | LS on initiation of new work item TR-USSD “Low resource requirement, quantum resistant, encryption of USSD messages for use in Financial services” | LS in | ITU-T SG11 |
S3-100-e AI: 3 |
noted | [WTS] [JSN] | |||
S3-202055 | N32-f Protection Policy IE Data-Type Mapping |
LS in LS reply in S3-202224 |
GSMA |
S3-100-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-202056 | N32-f Error Responses - Mapping | LS in | GSMA |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-202057 | LS on 5G-GUTI reallocation after paging of a UE in 5GMM-IDLE mode with suspend indication | LS in | C1-200967 |
S3-100-e AI: 4.8 |
postponed | [WTS] [JSN] | |||
S3-202058 | Process for SA3#100-e meeting |
other revision of S3-201550 revised to S3-202163 |
SA WG3 Chair |
S3-100-e AI: 1 |
revised | [WTS] [JSN] | |||
S3-202059 | New Solution for KI3 - Encrypted transfer of LTK out of UDR |
pCR revision of S3-201552 |
KPN N.V. | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-202060 | New Solution for KI2 - Encrypted storage of LTK in UDR |
pCR revision of S3-201551 |
KPN N.V. | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-202061 | pCR to TR 33.845: Location of ARPF functionality |
pCR revision of S3-201927 |
Ericsson | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-202062 | Authentication/authorization framework for Edge Enabler Client and server |
pCR revision of S3-201970 |
Samsung | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202063 | Key issue on user's consent for exposure of information to Edge Application |
pCR revision of S3-201971 |
Samsung, China Telecommunications, Apple | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202064 | Key issue on key management in 5G ProSe |
pCR revision of S3-201960 |
Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202065 | Key management in 5G ProSe |
pCR revision of S3-201961 |
Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202066 | Key issue on secure data transfer between UE and 5GDDNMF in ProSe |
pCR revision of S3-201964 |
Samsung, Ericsson | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202067 | Secure data transfer between UE and 5GDDNMF in ProSe |
pCR revision of S3-201965 |
Samsung | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202068 | Draft TR 33857 v010 Study on enhanced security support for Non-Public Networks (NPN) | draft TR | Ericsson Telecomunicazioni SpA | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
approved | [WTS] [JSN] | |
S3-202069 | Living document for TS 33.220: SBA support for Zh and Zn interfaces |
draftCR revision of S3-202029 |
Ericsson, Huawei, Hisilicon | GBA_5G | Rel-16 |
S3-100-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-202070 | pCR to TR 33.846: editorial corrections for solution #2.4 |
pCR revision of S3-202019 |
THALES | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-202071 | Living document for TS 33.223: SBA support for Zpn interface |
draftCR revision of S3-202030 |
Ericsson, Huawei, HiSilicon | GBA_5G | Rel-16 |
S3-100-e AI: 4.14 |
approved | [WTS] [JSN] | |
S3-202072 | Draft TR 33.846 v0.7.0 Study on authentication enhancements in the 5G System (5GS) | draft TR | Ericsson Japan K.K. | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] | |
S3-202073 | Skeleton for edge computing SID |
pCR revision of S3-201834 |
Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202074 | EC: New Key issue on the transport security for the EDGE-1-9 |
pCR revision of S3-201835 |
Huawei, Hisilicon | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202075 | IMS SCAS: adding the Introduction part |
pCR revision of S3-201851 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-202076 | Certificate-Based Encryption Solution |
pCR revision of S3-201598 |
MITRE Corporation, AT&T, InterDigital, DoD, Apple, CISA/ECD, III, CableLabs | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-202077 | IMS SCAS: new test case on de-registration |
pCR revision of S3-201854 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-202078 | Threats specific of high-priority algorithm selection in the P-CSCF |
draftCR revision of S3-201855 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-202079 | IMS SCAS: new test case on high-priority algorithm selection in the P-CSCF |
pCR revision of S3-201856 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
withdrawn | [WTS] [JSN] |
S3-202080 | IMS SCAS: new test case on high-priority algorithm selection in the P-CSCF |
pCR revision of S3-201856 revised to S3-202156 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] |
S3-202081 | Threats specific of bidding down on security association set-up |
draftCR revision of S3-201857 revised to S3-202154 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
revised | [WTS] [JSN] | |
S3-202082 | IMS SCAS: new test case on bidding down on security association set-up |
pCR revision of S3-201858 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-202083 | IMS SCAS: new test case on unprotected register message |
pCR revision of S3-201860 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-202084 | Draft TS 33.226 v0.2.0 Security assurance for IP Multimedia Subsystem (IMS) | draft TS | Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-202085 | Draft TR 33.839 Study on security aspects of enhancement of support for edge computing in 5G Core (5GC) | draft TR | Huawei, Hisilicon | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-202086 | UPIP: Update to solution #11 (UP IP over eUTRA connected to EPS) |
pCR revision of S3-201956 |
Ericsson | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-202087 | Reply LS on security procedures for Edge Applications |
LS out LS is reply to S3-201538 LS To: SA6 |
Huawei, Hisilicon | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] | ||
S3-202088 | New Key Issue for TR 33.854 – UAV and UAV-C Location Information veracity |
pCR revision of S3-201593 |
InterDigital, Europe, Ltd., Futurewei Technologies | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202089 | eNPN Proposed TR Introduction |
pCR revision of S3-202017 |
Ericsson | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-202090 | New Key Issue for TR 33.854 – Privacy protection of UAS identities |
pCR revision of S3-201599 |
InterDigital, Europe, Ltd., Huawei, HiSilicon, Lenovo, Motorola Mobility | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202091 | eNPN Proposed TR Assumptions |
pCR revision of S3-201986 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-202092 | eNPN New KI: Credentials owned by an external entity |
pCR revision of S3-201987 |
Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Huawei, Hisilicon, Intel, Qualcomm Incorporated | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-202093 | eNPN New KI: Provisioning |
pCR revision of S3-201989 |
Ericsson, Huawei, Hisilicon | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
approved | [WTS] [JSN] |
S3-202094 | Some evaluation of solution #2.2 in TR 33.846 |
pCR revision of S3-201931 |
Qualcomm Incorporated | 33.846 0.6.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-202095 | Proposed scope for TR 33.854 on UAS security |
other revision of S3-201937 |
Qualcomm Incorporated |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] | |||
S3-202096 | Adding a reference to the UAS architecture from TS 23.754 |
pCR revision of S3-201938 |
Qualcomm Incorporated, Huawei, Hsilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202097 | Solving key issue #7 on moving bearer that require UP IP to EPS using the existing methods |
pCR revision of S3-201940 |
Qualcomm Incorporated | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-202098 | SQN protection during re-synchronisation procedure in AKA |
pCR revision of S3-201614 |
Nokia, Nokia Shanghai Bell | 33.846 17.0.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-202099 | SQNms protection by concealment |
pCR revision of S3-201613 |
Nokia, Nokia Shanghai Bell | 33.846 17.0.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-202100 | Key Issue on Linking of UEs by SUCI replay attack |
pCR revision of S3-201615 |
Nokia, Nokia Shanghai Bell | 33.846 17.0.0 | FS_AUTH_ENH | Rel-16 |
S3-100-e AI: 5.6 |
approved | [WTS] [JSN] |
S3-202101 | TR_33.851_IIoT_Sec skeleton |
pCR revision of S3-201583 |
Nokia, Nokia Shanghai Bell | 33.851 17.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-202102 | Scope of study |
pCR revision of S3-201584 |
Nokia, Nokia Shanghai Bell | 33.851 17.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-202103 | References |
pCR revision of S3-201585 |
Nokia, Nokia Shanghai Bell | 33.851 17.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-202104 | Abbreviations |
pCR revision of S3-201586 |
Nokia, Nokia Shanghai Bell | 33.851 17.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
withdrawn | [WTS] [JSN] |
S3-202105 | Architectural considerations |
pCR revision of S3-201587 |
Nokia, Nokia Shanghai Bell | 33.851 17.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-202106 | Multiple TSN working domains |
pCR revision of S3-201590 |
Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-202107 | TR_33.851_IIoT_Sec |
draft TR revised to S3-202436 |
Nokia | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] | |
S3-202108 | DSnF improvements in time synchronization |
pCR revision of S3-202009 |
Philips International B.V. | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-202109 | Cryptographic CRC in MAC to avoid MitM relay nodes |
pCR revision of S3-202026 |
Philips International B.V. | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-202110 | TUAK AKA authenticaiton |
pCR revision of S3-201627 |
China Telecommunications | 33.845 0.3.0 | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
approved | [WTS] [JSN] |
S3-202111 | New KI: UAV/UAV-C authentication and authorization |
pCR revision of S3-201818 |
Huawei, HiSilicon, InterDigital, Qualcomm, Nokia, Nokia Shanghai Bell | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202112 | A new key issue on pairing authorization for UAV and UAVC |
pCR revision of S3-201819 |
Huawei, HiSilicon, InterDigital | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202113 | A new key issue on TPAE security |
pCR revision of S3-201821 |
Huawei, HiSilicon | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202114 | A new solution to UAS authentication and authorization |
pCR revision of S3-201823 |
Huawei, HiSilicon, InterDigital | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202115 | Key Issue: Security Requirements for EDGE-1 Interface |
pCR revision of S3-201701 |
Intel Deutschland GmbH | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202116 | Key Issue: Security Requirements for EDGE-4 Interface |
pCR revision of S3-201703 |
Intel Deutschland GmbH | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202117 | Key Issue: Security Requirements for EDGE-6 Interface |
pCR revision of S3-201706 |
Intel Deutschland GmbH | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202118 | New key issue on security for uplink time synchronization |
pCR revision of S3-201694 |
ZTE Corporation,Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-202119 | New KI for EAS discovery |
pCR revision of S3-201749 |
Huawei, Hisilicon, Apple | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202120 | New Key Issue on Security of authentication and authorization for Multicast communication services |
pCR revision of S3-201719 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-202121 | New Key Issue on security protection of MBS traffic |
pCR revision of S3-201720 |
HuaWei Technologies Co., Ltd | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-202122 | Scope for TR on MBS security |
pCR revision of S3-201721 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-202123 | Scope for TR on MBS security |
pCR revision of S3-201721 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-202124 | Proposed Skeleton for MBS SID |
pCR revision of S3-201722 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
withdrawn | [WTS] [JSN] |
S3-202125 | New Key Issue on key distribution |
pCR revision of S3-201723 |
Huawei, Hisilicon | 33.85 0.0.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-202126 | New Key Issue on protection of UE-UE communication |
pCR revision of S3-201724 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.851 0.0.0 | FS_IIoT_SEC | Rel-17 |
S3-100-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-202127 | New Key Issue on protection of information in remote identification and between UAV/UAVC and UTM/USS |
pCR revision of S3-201726 |
Huawei, Hisilicon, Interdigital, Futurewei | 33.854 0.0.0 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202128 | New key issue on authentication and authorization for UE onboarding between UE and SNPN |
pCR revision of S3-201729 |
Huawei, Hisilicon,Ericsson, Nokia, Nokia Shanghai Bell, Intel, Qualcomm Incorporated | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-202129 | New key issue on discovery message protection |
pCR revision of S3-201758 |
Huawei, Hisilicon, LG Electronics, Ericsson, CATT, Interdigital | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202130 | New key issue on security of UE-to-Network Relay |
pCR revision of S3-201759 |
Huawei, Hisilicon, Interdigital, Qualcomm Incorporated,CATT, Ericsson,Apple | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202131 | Threat analysis on NAS based redirection from 5GS to EPS |
draftCR revision of S3-201761 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202132 | SCAS-NAS based redirection from 5GS to EPS |
draftCR revision of S3-201762 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202133 | threat analysis on state transation |
draftCR revision of S3-201763 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202134 | Add state transation to gNB SCAS |
draftCR revision of S3-201764 |
Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202135 | living doc to 33.117 |
draftCR revision of S3-201767 |
Huawei, Hisilicon, Interdigital, Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202136 | Updating IPUPS of UPF to Annex L of TR 33.926 | draftCR | ZTE Corporation | SCAS_5G_IPUPS | Rel-17 |
S3-100-e AI: 4.2 |
approved | [WTS] [JSN] | |
S3-202137 | Draft TR 33.850 | pCR | Huawei, Hisilicon | 33.85 0.1.0 | FS_5MBS_SEC | Rel-17 |
S3-100-e AI: 5.12 |
approved | [WTS] [JSN] |
S3-202138 | SCAS SCP: Requirements and test cases of SBA/SBI aspects |
pCR revision of S3-201996 |
Nokia, Nokia Shanghai Bell | 33.522 0.1.0 | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
approved | [WTS] [JSN] |
S3-202139 | Critical Assets of SCP |
draftCR revision of S3-201997 |
Nokia, Nokia Shanghai Bell | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
approved | [WTS] [JSN] | |
S3-202140 | Threat analysis of incorrect validation of client credentials assertion |
draftCR revision of S3-201891 |
Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202141 | Test case for correct handling of client credentials assertion validation failure |
draftCR revision of S3-201892 |
Nokia, Nokia Shanghai Bell | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202142 | 5GFBS: Detecting FBS based on UE Positioning Measurements |
pCR revision of S3-202016 |
Nokia, Nokia Shanghai Bell | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-202143 | Draft TS 33.522 v0.2.0 5G SCAS for SCP | draft TS | Nokia, Nokia Shanghai Bell | SCAS_5G_SECOP | Rel-17 |
S3-100-e AI: 4.17 |
approved | [WTS] [JSN] | |
S3-202144 | pCR to TR33.847-Scope |
pCR revision of S3-201806 |
CATT, Huawei, HiSilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202145 | Draft TR 33.847 | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] | |
S3-202146 | 5G ProSe: New Key issue on authorization in the UE-to-UE relay scenario |
pCR revision of S3-201836 |
Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202147 | 5G ProSe: New Key issue on authorization in the UE-to-Network relay scenario |
pCR revision of S3-201837 |
Huawei, Hisilicon | 33.847 0.0.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202148 | Living CR to TR 33.926 | draftCR | Huawei, Hisilicon | eSCAS_5G | Rel-17 |
S3-100-e AI: 4.16 |
approved | [WTS] [JSN] | |
S3-202149 | IMS SCAS: living document for assets and threats of the IMS product classes |
draftCR revision of S3-201852 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-202150 | draft TR for 5GFBS | draft TR | Apple Computer Trading Co. Ltd | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] | |
S3-202151 | MEC-New solution on authentication based on 3GPP credentials |
pCR revision of S3-201907 |
Apple | 33.839 0.0.0 | FS_eEDGE_Sec | Rel-17 |
S3-100-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-202152 | Agenda |
agenda revision of S3-201500 |
SA WG3 Chair |
S3-100-e AI: 1 |
approved | [WTS] [JSN] | |||
S3-202153 | Threats specific of bidding down on security association set-up |
draftCR revision of S3-201857 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
withdrawn | [WTS] [JSN] | |
S3-202154 | Threats specific of bidding down on security association set-up |
draftCR revision of S3-202081 |
Huawei, Hisilicon | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] | |
S3-202155 | Key Issue on Security of Command and Control Communication |
pCR revision of S3-201893 |
Lenovo, Motorola Mobility, Huawei, HiSilicon, Interdigital | 33.854 0.0.1 | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-202156 | IMS SCAS: new test case on high-priority algorithm selection in the P-CSCF |
pCR revision of S3-202080 |
Huawei, Hisilicon | 33.226 0.1.0 | SCAS_IMS | Rel-17 |
S3-100-e AI: 4.15 |
approved | [WTS] [JSN] |
S3-202157 | New Key Issue for TR 33.847 – submission of draft_S3-201619-r5 that is a merger of S3-201619, S3-201661, and S3-201909 |
pCR revision of S3-201619 |
InterDigital, Inc. | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
withdrawn | [WTS] [JSN] |
S3-202158 | New Key Issue for TR 33.847 – submission of draft_S3-201619-r5 that is a merger of S3-201619, S3-201661, and S3-201909 |
pCR revision of S3-201619 |
InterDigital, Inc., LG Electronics, Apple | 33.847 0.0.1 | FS_5G_ProSe_Sec | Rel-17 |
S3-100-e AI: 5.1 |
approved | [WTS] [JSN] |
S3-202159 | Draft TR 33.854 | draft TR | Qualcomm | FS_UAS_SEC | Rel-17 |
S3-100-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-202160 | LS on Misalignments on HTTP message format over N32-f | LS in | C4-204409 |
S3-100-e AI: 4.1 |
postponed | [WTS] [JSN] | |||
S3-202161 | Add certificate based solution for NPN as a new Solution |
pCR revision of S3-201592 |
MITRE Corporation | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-202162 | Access Token Signature using MAC with symmetric key | CR | Mavenir, Deutsche Telekom | 33.501 15.9.0 CR#945 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202163 | Process for SA3#100-e meeting |
other revision of S3-202058 |
SA WG3 Chair |
S3-100-e AI: 1 |
noted | [WTS] [JSN] | |||
S3-202164 | Error handling by the receiving NF | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#946 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202165 | Error handling by the receiving NF | CR | Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#947 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202166 | Static authorization details | CR | Mavenir,Deutsche Telekom,Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#948 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202167 | N32 interface | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#949 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202168 | Assignment of FC values for key derivations |
CR revision of S3-201946 |
Qualcomm Incorporated, China Mobile | 33.535 16.0.0 CR#261 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202169 | Assigning FC values for AKMA TS |
CR revision of S3-201947 |
Qualcomm Incorporated, China Mobile, Samsung | 33.22 16.1.0 CR#2031 catF | TEI16 | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202170 | [SEAL] CR for TS 33.434 cleanup |
CR revision of S3-201959 |
Samsung | 33.434 16.0.0 CR#21 catF | SEAL | Rel-16 |
S3-100-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-202171 | FS_eSBA_SEC | SID new | Nokia, Nokia Shanghai Bell, Deutsche Telecom, Verizon, Mavenir, CableLabs, Mavenir, Docomo, China Mobile, Huawei, HiSilicon |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | |||
S3-202172 | Allocation of FC values for KIAB derivation function |
CR revision of S3-201977 |
Samsung | 33.501 16.3.0 CR#9371 catF | NR_IAB | Rel-16 |
S3-100-e AI: 4.11 |
agreed | [WTS] [JSN] |
S3-202173 | Reply LS to GSMA RIFS on 4G authentication improvement |
LS out LS is reply to S3-202052 source LS: RIFS90_04 LS To: GSMA FASG RIFS |
Nokia, Nokia Shanghai Bell |
S3-100-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-202174 | Static authorization details |
CR revision of S3-201611 |
Mavenir,Deutsche Telekom,Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#8801 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202175 | Correction to SN Addition or modification |
CR revision of S3-201889 |
Lenovo, Motorola Mobility | 33.501 16.3.0 CR#9241 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202176 | [33.180] MCData message store security |
CR revision of S3-201648 |
Motorola Solutions Danmark A/S | 33.18 16.4.0 CR#1501 catB | MCXSec2 | Rel-17 |
S3-100-e AI: 4.3 |
agreed | [WTS] [JSN] |
S3-202177 | Reply LS on Key Management procedure in SEAL |
LS out LS is reply to S3-201508 source LS: S3-201508 LS To: CT3 revision of S3-201654 |
Motorola Solutions Danmark A/S | SEAL | Rel-16 |
S3-100-e AI: 4.12 |
approved | [WTS] [JSN] | |
S3-202178 | [33.434] KM Clarifications |
CR revision of S3-201650 |
Motorola Solutions Danmark A/S | 33.434 16.0.0 CR#11 catF | SEAL | Rel-16 |
S3-100-e AI: 4.12 |
agreed | [WTS] [JSN] |
S3-202179 | New WID on mission critical security enhancements phase 2 |
WID new revision of S3-201652 |
Motorola Solutions Danmark A/S | Rel-17 |
S3-100-e AI: 4.22 |
agreed | [WTS] [JSN] | ||
S3-202180 | N32 interface |
CR revision of S3-202046 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9012 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202181 | Alignment and clarifications to SBA network or transport layer protocol |
CR revision of S3-201795 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9001 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202182 | Overview clause on communication models and related security |
CR revision of S3-201799 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9041 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202183 | Authentication and static authorization |
CR revision of S3-201798 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9031 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202184 | Making NF instance id in SBA certificate profile mandatory to support |
CR revision of S3-201803 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9081 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202185 | SID on eSBA sec cont |
SID new revision of S3-201793 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-202186 | Integrity protection of service request |
CR revision of S3-201801 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9061 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
not pursued | [WTS] [JSN] |
S3-202187 | SA3 meeting calendar | other | Ericsson LM |
S3-100-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-202188 | Draft agenda for SA3#100bis-e meeting | agenda | Ericsson LM |
S3-100-e AI: 6 |
noted | [WTS] [JSN] | |||
S3-202189 | Authorization of NF service access |
CR revision of S3-201800 revised to S3-202259 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9051 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
revised | [WTS] [JSN] |
S3-202190 | Reply to Reply PAP/CHAP and other point-to-point protocols usage in 5GS |
LS out LS is reply to S3-201509 LS To: SA2, CT1, CT3 |
NTT DOCOMO INC. |
S3-100-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-202191 | Reply LS on 256 bit algorithm candidates |
LS out LS is reply to S3- 201540 LS To: ETSI SAGE |
NTT DOCOMO INC. |
S3-100-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-202192 | Reply LS on Observations on ZUC-256 |
LS out LS is reply to S3-201541 LS To: ETSI SAGE |
NTT DOCOMO INC. |
S3-100-e AI: 3 |
approved | [WTS] [JSN] | |||
S3-202193 | resolution of editor's note in clause 10.2.2.2 |
CR revision of S3-201575 |
NTT DOCOMO | 33.501 15.9.0 CR#8731 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202194 | NF Service Producer authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#950 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202195 | NF Service Producer authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#951 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202196 | resolution of editor's note in clause 10.2.2.2 - R16 mirror |
CR revision of S3-201576 |
NTT DOCOMO | 33.501 16.3.0 CR#8741 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202197 | OAuth 2.0 based authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#952 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202198 | OAuth 2.0 based authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#953 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202199 | CR on Kseaf text deletion |
CR revision of S3-201649 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 16.3.0 CR#8831 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202200 | CR on Kseaf text deletion |
CR revision of S3-201651 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 15.9.0 CR#8841 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202201 | CR to delete uncompressed mode text in profile B |
CR revision of S3-201655 |
Nokia, Nokia Shanghai Bell, Verizon | 33.501 16.3.0 CR#8851 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202202 | Enhancements to UPIP Support in 5GS |
WID new revision of S3-201941 |
Qualcomm Incorporated |
S3-100-e AI: 4.22 |
agreed | [WTS] [JSN] | |||
S3-202203 | Updates to Abbreviations and Corrections and clarifications to clause 4 |
CR revision of S3-201943 |
Qualcomm Incorporated | 33.535 16.0.0 CR#231 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202204 | Corrections to AKMA key lifetimes |
CR revision of S3-201944 |
Qualcomm Incorporated | 33.535 16.0.0 CR#241 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202205 | Corrections and clarifications to AKMA procedures |
CR revision of S3-201945 |
Qualcomm Incorporated | 33.535 16.0.0 CR#251 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202206 | Clarification of direct NAS reroute |
CR revision of S3-201867 |
Huawei, Hisilicon | 33.501 15.9.0 CR#9201 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202207 | Mirror:Clarification of direct NAS reroute |
CR revision of S3-201868 |
Huawei, Hisilicon | 33.501 16.3.0 CR#9211 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202208 | Change the long-lived TLS connection of N32-C to the short-lived |
CR revision of S3-201841 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#9141 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202209 | Mirror: change the long-lived TLS connection of N32-C to the short-lived |
CR revision of S3-201842 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9151 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202210 | Clarification on the UP security configuration checking |
CR revision of S3-201838 |
Huawei, Hisilicon | 33.536 16.0.0 CR#141 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-202211 | Update the N32-f context ID negotiation procedure |
CR revision of S3-201843 |
Huawei, Hisilicon, Ericsson | 33.501 15.9.0 CR#9161 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202212 | Editorial changes about eV2X |
CR revision of S3-201710 |
Huawei, Hisilicon, ZTE Corporation | 33.536 16.0.0 CR#71 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-202213 | Clarification on policy handling |
CR revision of S3-201712 |
Huawei, Hisilicon | 33.536 16.0.0 CR#91 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-202214 | Clarification on algorithm selection and key derivation |
CR revision of S3-201713 |
Huawei, Hisilicon | 33.536 16.0.0 CR#101 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-202215 | Clarification on processing null-algorithms |
CR revision of S3-201714 |
Huawei, Hisilicon | 33.536 16.0.0 CR#111 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-202216 | Propose to complete security lagorithm selection for UP |
CR revision of S3-201716 |
Huawei, Hisilicon | 33.536 16.0.0 CR#131 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-202217 | Clarifications on error case in AKMA process |
CR revision of S3-201717 |
Huawei, Hisilicon | 33.535 16.0.0 CR#91 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202218 | Reauthenticaiton in AKMA |
CR revision of S3-201755 |
Huawei, Hisilicon | 33.535 16.0.0 CR#131 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202219 | Relay LS to NESAS Official Launch |
LS out LS is reply to S3-201547 LS To: GSMA SECAG |
Huawei, Hisilicon |
S3-100-e AI: 4.2 |
approved | [WTS] [JSN] | |||
S3-202220 | LS for penetration test inclusion of SCAS |
LS out LS To: GSMA SECAG revised to S3-202244 |
Huawei, Hisilicon |
S3-100-e AI: 5.16 |
revised | [WTS] [JSN] | |||
S3-202221 | New WID on Security Assurance Specification for NSSAAF |
WID new revision of S3-201741 |
Huawei, Hisilicon | Rel-17 |
S3-100-e AI: 4.22 |
agreed | [WTS] [JSN] | ||
S3-202222 | Mirror: update the N32-f context ID negotiation procedure |
CR revision of S3-201844 |
Huawei, Hisilicon, Ericsson | 33.501 16.3.0 CR#9171 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202223 | Updates to solution #20 - resolving EN in 6.20.2.2.1 |
pCR revision of S3-201635 |
CableLabs, Apple, Intel, Deutsche Telekom AG, InterDigital Communications, Rogers Communications, Charter Communications | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-202224 | Reply LS on N32-f Protection Policy IE Data-Type Mapping |
LS out LS To: GSMA FASG 5GIS, CT4 revision of S3-201849 |
Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-202225 | Updates to solution #20 - resolving ENs in 6.20.2.3.1 |
pCR revision of S3-201636 |
CableLabs, Apple, Intel, Deutsche Telekom AG, InterDigital Communications, Rogers Communications, Charter Communications | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-202226 | Updates to solution #20 - resolving ENs in 6.20.2.4 |
pCR revision of S3-201637 |
CableLabs, Apple, Deutsche Telekom AG, InterDigital Communications, Rogers Communications, Charter Communications | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-202227 | Updates to solution #20 - resolving ENs in 6.20.2.5.1 |
pCR revision of S3-201638 |
CableLabs, Apple, Intel, Deutsche Telekom AG, InterDigital Communications, Rogers Communications, Charter Communications | 33.809 0.9.0 | FS_5GFBS | Rel-16 |
S3-100-e AI: 5.2 |
approved | [WTS] [JSN] |
S3-202228 | Clarification on the test cases if the UDM and AUSF are collocated |
CR revision of S3-201840 |
Huawei, Hisilicon | 33.514 16.2.0 CR#31 catF | SCAS_5G | Rel-16 |
S3-100-e AI: 4.2 |
agreed | [WTS] [JSN] |
S3-202229 | Skeleton for TR 33.840 |
draft TR revision of S3-201705 revised to S3-202230 |
China Telecommunications | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
revised | [WTS] [JSN] | |
S3-202230 | Skeleton for TR 33.840 |
draft TR revision of S3-202229 |
China Telecommunications | FS_disagg_gNB_Sec | Rel-17 |
S3-100-e AI: 5.14 |
approved | [WTS] [JSN] | |
S3-202231 | Corrections to clause 16 |
CR revision of S3-201817 |
Huawei, HiSilicon | 33.501 16.3.0 CR#9131 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202232 | Update the clause 5.3.3.2.2 |
CR revision of S3-201692 |
ZTE Corporation | 33.536 16.0.0 CR#61 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
S3-202233 | Add three Abbreviations to clause 3.3 |
CR revision of S3-201680 |
ZTE Corporation | 33.535 16.0.0 CR#11 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202234 | New SID on introducing penetration test |
SID new revision of S3-201809 |
Huawei, Hisilicon | Rel-17 |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-202235 | New Study on Enhancement of Authorization of API Invocation |
SID new revision of S3-201736 |
Huawei, Hisilicon, China Unicom, CAICT, CATT |
S3-100-e AI: 5.16 |
noted | [WTS] [JSN] | |||
S3-202236 | SUPI Type Clarification in R16 |
CR revision of S3-201733 |
Huawei, Hisilicon | 33.501 16.3.0 CR#8911 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202237 | SUPI Type Clarification in R15 |
CR revision of S3-201734 |
Huawei, Hisilicon | 33.501 15.9.0 CR#8921 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202238 | New key issue on authentication and authorization for UE onboarding between UE and SNPN | pCR | Huawei, Hisilicon | 33.857 0.0.0 | FS_eNPN_SEC | Rel-17 |
S3-100-e AI: 5.13 |
noted | [WTS] [JSN] |
S3-202239 | Correction to Nnssaaf_NSSAA services service |
CR revision of S3-201746 |
Huawei, Hisilicon | 33.501 16.3.0 CR#8951 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202240 | Correction to Nnssaaf_NSSAA services service |
CR revision of S3-201746 |
Huawei, Hisilicon | 33.501 16.3.0 CR#8952 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-202241 | Secondary authentication revocation |
CR revision of S3-201747 |
Huawei, Hisilicon | 33.501 15.9.0 CR#8961 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202242 | Secondary authentication revocation |
CR revision of S3-201748 |
Huawei, Hisilicon | 33.501 16.3.0 CR#8971 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202243 | Edirorials on 13.4.1.2 Service access authorization in roaming scenarios-R16 |
CR revision of S3-201679 |
ZTE Corporation | 33.501 16.3.0 CR#8881 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202244 | LS for penetration test inclusion of SCAS |
LS out LS To: GSMA SECAG revision of S3-202220 |
Huawei, Hisilicon |
S3-100-e AI: 5.16 |
approved | [WTS] [JSN] | |||
S3-202245 | Modification on AAA Server triggered Slice-Specific Authorization Revocation procedure |
CR revision of S3-201805 |
CATT | 33.501 16.3.0 CR#9091 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202246 | AKMA SBA interface clarifications |
CR revision of S3-202037 |
Ericsson, ZTE, China Mobile, Samsung | 33.535 16.0.0 CR#321 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202247 | Several clarifications and editorials |
CR revision of S3-202039 |
Ericsson | 33.535 16.0.0 CR#341 catF | AKMA | Rel-16 |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] |
S3-202248 | Clarifications to SoR integrity protection mechanism |
CR revision of S3-202049 |
Orange, Ericsson, Samsung | 33.501 15.9.0 CR#9431 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202249 | Clarifications to SoR integrity protection mechanism |
CR revision of S3-202050 |
Orange, Ericsson, Samsung | 33.501 16.3.0 CR#9441 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202250 | LS on Reference point interface names for AKMA |
LS out LS To: SA2 revision of S3-202041 |
Ericsson | AKMA |
S3-100-e AI: 4.7 |
agreed | [WTS] [JSN] | ||
S3-202251 | Reply LS on LS on 5G SoR integrity protection mechanism |
LS out LS is reply to S3-201511 LS To: CT4 |
Orange | Rel-16 |
S3-100-e AI: 4.1 |
approved | [WTS] [JSN] | ||
S3-202252 | New study on the security of AMF re-allocation |
SID new revision of S3-202033 |
Ericsson | Rel-17 |
S3-100-e AI: 5.16 |
agreed | [WTS] [JSN] | ||
S3-202253 | Clarification to 5G AV |
CR revision of S3-201878 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#8343 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-202254 | Clarification to 5G AV | CR | Nokia,Nokia Shanghai Bell | 33.501 15.9.0 CR#954 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.21 |
agreed | [WTS] [JSN] |
S3-202255 | New WID on Security Assurance Specification for NSSAAF |
WID new revision of S3-201741 |
Huawei, Hisilicon | Rel-17 |
S3-100-e AI: 4.22 |
withdrawn | [WTS] [JSN] | ||
S3-202256 | new SID on security aspects of eNA phase2 |
SID new revision of S3-201784 |
China Mobile, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, China Unicom, CATT, ZTE, Ericsson, Lenovo, Motorola Mobility, LG Elecronics, CableLabs, Interdigital | Rel-17 |
S3-100-e AI: 5.16 |
agreed | [WTS] [JSN] | ||
S3-202257 | pCR to TR33.853 - Addition of solution addressing KI#8 |
pCR revision of S3-202008 |
VODAFONE Group Plc | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-202258 | pCR to TR33.853 - Updates to solution 14 |
pCR revision of S3-202001 |
VODAFONE Group Plc | 33.853 1.0.0 | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
approved | [WTS] [JSN] |
S3-202259 | Authorization of NF service access |
CR revision of S3-202189 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9052 catF | 5G_eSBA | Rel-16 |
S3-100-e AI: 4.6 |
agreed | [WTS] [JSN] |
S3-202260 | TR 33.853 v1.1.0 | draft TR | VODAFONE Group Plc | FS_UP_IP_Sec | Rel-16 |
S3-100-e AI: 5.4 |
approved | [WTS] [JSN] | |
S3-202261 | TR33.845 v0.4.0 | draft TR | VODAFONE Group Plc | FS_5GC_SEC_ARPF | Rel-16 |
S3-100-e AI: 5.7 |
approved | [WTS] [JSN] |
762 documents (1.0718719959259 seconds)