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-242700 | Agenda | agenda | SA WG3 Chair |
S3-117 AI: 1 |
approved | [WTS] [JSN] | |||
| S3-242701 | Report from SA3#116 | report | MCC |
S3-117 AI: 2.1 |
approved | [WTS] [JSN] | |||
| S3-242702 | Process for SA3#117 | other | SA WG3 Chair |
S3-117 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-242703 | Detail agenda planning for SA3#117 |
other revised to S3-243406 |
SA WG3 Chair |
S3-117 AI: 1 |
revised | [WTS] [JSN] | |||
| S3-242704 | SA3 meeting calendar | other | SA WG3 Chair |
S3-117 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-242705 | Report to SA3 from SA | report | SA WG3 Chair |
S3-117 AI: 2.1 |
noted | [WTS] [JSN] | |||
| S3-242706 | Response to S3-240886 LS on the introduction of the domain ""ipxnetwork.org"" |
LS in LS reply in S3-243676, S3-242780, S3-242931, S3-243676, S3-243677 |
GSMA 5GMRR |
S3-117 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-242707 | Reply LS on LS reply on LCS user plane connection binding to the UE | LS in | C1-243934 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242708 | Reply to LS on differentiating security materials used for PC5 direct discovery for 5G ProSe UE-to-network relay | LS in | C1-243949 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242709 | Reply LS on CAPIF extensibility | LS in | C3-243204 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242710 | LS on Resource content filters |
LS in LS reply in S3-243678, S3-243040, S3-243217, S3-243678 |
C4-241339 |
S3-117 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-242711 | Reply LS on N32-f N32-c correlation | LS in | C4-242393 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242712 | LS on Registering JWT claims at IANA | LS in | CP-241308 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242713 | LS on RFC 9374, "DRIP Entity Tag (DET) for Unmanned Aircraft System Remote ID (UAS RID)" | LS in | IETF Drone Remote ID Protocol (DRIP) |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242714 | LS on RFC 9543, "A Framework for Network Slices in Networks Built from IETF Technologies" | LS in | IETF Traffic Engineering Architecture and Signaling Working Group (teas) |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242715 | LS on a Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies | LS in | IETF Traffic Engineering Architecture and Signaling Working Group (teas) |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242716 | Reply LS on security of IP transport over satellite transport links | LS in | R3-243955 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242717 | LS on Avoiding Cross-TSG TEI | LS in | RP-241686 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242718 | Reply LS on clarification on mobile metaverse services | LS in | S1-241351 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242719 | LS on the use of TLS with QUIC in ATSSS context | LS in | S2-2405459 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242720 | Reply LS on ECS Configuration Information | LS in | S2-2406888 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242721 | LS on security considerations for 5G ProSe multi-hop relays |
LS in LS reply in S3-243559, S3-243307, S3-243559 |
S2-2407207 |
S3-117 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-242722 | LS on Clarifications related to User Identities | LS in | S2-2407219 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242723 | LS on Clarification of requirements for Ambient IoT |
LS in LS reply in S3-243239 |
S2-2407231 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242724 | LS on User Identities and Authentication Architecture |
LS in LS reply in S3-242852, S3-242891, S3-242903, S3-243145, S3-243251, S3-243264, S3-243322, S3-243558 |
S2-2407236 |
S3-117 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-242725 | LS on FS_5GSAT_Ph3_ARCH conclusions |
LS in LS reply in S3-243533, S3-243533 |
S2-2407350 |
S3-117 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-242726 | LS Reply on Internal 5G Core information expose to trusted AF | LS in | S2-2407354 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242727 | LS on enhancement to the protocol stack of IMS Data Channel |
LS in LS reply in S3-243027, S3-243407 |
S4-241373 |
S3-117 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-242728 | Reply LS on GSMA OPG PRDs publication | LS in | S5-243436 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242729 | Reply LS on clarifications on consent management | LS in | S6-242504 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242730 | LS on Clarification related to Internal 5G Core information expose to trusted AF |
LS in LS reply in S3-242898, S3-243408 |
S6-242714 |
S3-117 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-242731 | Reply LS on ECS Configuration Information | LS in | S6-242733 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242732 | Reply LS on request clarification on mobile metaverse services | LS in | S6-242734 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242733 | Recent attack on polynomial based MACs with short tag | LS in | ETSI SAGE |
S3-117 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-242734 | Reply LS on GSMA OPG PRDs publication | LS in | SP-240946 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242735 | Reply LS on data plane control by roaming hubs | LS in | SP-241014 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242736 | LS on Security considerations for MPQUIC | LS in | SP-241015 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242737 | LS on Support for Ambient IoT Security | LS in | SP-241016 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242738 | Reply LS on enhancement to the protocol stack of IMS Data Channel | LS in | s3i240475 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242739 | Reply LS to SA2 on User Identities and Authentication Architecture | LS in | s3i240476 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242740 | Reply LS to SA2 on FS_5GSAT_Ph3_ARCH conclusions | LS in | s3i240477 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242741 | Reply LS to SA3 on LI considerations for TR 33.757 |
LS in LS reply in S3-243410, S3-242900, S3-243410 |
s3i240502 |
S3-117 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-242742 | UPU Header Security | CR | Lenovo | 33.501 18.6.0 CR#2046 catF | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-242743 | Discussion paper on UPU Security and related header protection | discussion | Lenovo | Rel-18 |
S3-117 AI: 4.1.15 |
noted | [WTS] [JSN] | ||
| S3-242744 | Security re-establishment for Trusted non-3GPP access | draftCR | Lenovo | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 4.13 |
merged | [WTS] [JSN] | |
| S3-242745 | Cleanup of TR | pCR | Lenovo | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-242746 | Initial Conclusion to KI#1 |
pCR revised to S3-243505 |
Lenovo, US National Security Agency, MITRE-FFRDC | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242747 | Solution to KI#2 |
pCR revised to S3-243611 |
Lenovo, US National Security Agency | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242748 | Updates to Solution #2 |
pCR revised to S3-243496 |
Lenovo, Johns Hopkins University APL, US National Security Agency | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242749 | Updates to Solution#1 |
pCR revised to S3-243497 |
Lenovo, Johns Hopkins University APL, US National Security Agency | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242750 | Updates to Solution#11 |
pCR revised to S3-243480 |
Lenovo | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-242751 | Updates to Solution #14 |
pCR revised to S3-243457 |
Lenovo | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242752 | Updates to Solution #1 |
pCR revised to S3-243466 |
Lenovo | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242753 | LS on RAN2 agreements and assumptions for Ambient IoT | LS in | R2-2406150 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242754 | TR 33.757 correction of Term for PNI-NPN Operational domain | pCR | Johns Hopkins University APL | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-242755 | Editorial correction to section 6.4 | pCR | CMDI | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
withdrawn | [WTS] [JSN] |
| S3-242756 | LS reply on LS on support of SSIM on eUICC | LS in | C6-240261 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242757 | Reply LS on Security Considerations for MPQUIC | LS in | IETF QUIC Working Group (QUIC) |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242758 | Newly published data channel GSMA PRD TS.66 |
LS in LS reply in S3-243411, S3-243299, S3-243411 |
GSMA |
S3-117 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-242759 | Add specific UDR SCAS test cases for TS 33.530 |
pCR revised to S3-243419 |
BSI (DE) | 33.530 0.1.0 | SCAS_5G_UDR | Rel-19 |
S3-117 AI: 4.2 |
revised | [WTS] [JSN] |
| S3-242760 | UE Security Testing | discussion | BSI (DE) | Rel-19 |
S3-117 AI: 4.1.1 |
noted | [WTS] [JSN] | ||
| S3-242761 | MPQUIC TLS Annex | CR | Intel Technology India Pvt Ltd | 33.501 18.6.0 CR#2030 catB | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-242762 | TCG progress - report from TCG rapporteur | other | InterDigital Communications |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242763 | [MCXSec4] 33180 R19 MC Recording Server Introduction |
CR revised to S3-243717 |
Airbus | 33.180 18.1.0 CR#212 catC | MCXSec4 | Rel-19 |
S3-117 AI: 4.6 |
revised | [WTS] [JSN] |
| S3-242764 | LS on reply to LS on FS_5GSAT_Ph3_ARCH conclusions |
LS out LS To: SA2 revised to S3-243533 |
Nokia | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] | ||
| S3-242765 | Editorial correction to section 6.4 | pCR | China Mobile Com. Corporation | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
withdrawn | [WTS] [JSN] |
| S3-242766 | Revision of two errors in TR 33.757 | pCR | China Mobile Com. Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
withdrawn | [WTS] [JSN] |
| S3-242767 | Discussion on polynomial based MACs with short Tag | discussion | Nokia, Nokia Shanghai Bell |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242768 | Reply LS on Polynomial based MACs with short Tag |
LS out LS is reply to S3-242733 LS To: ETSI SAGE |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242769 | Refinement of UDR security requirements | other | Nokia, Nokia Shanghai Bell |
S3-117 AI: 4.2 |
noted | [WTS] [JSN] | |||
| S3-242770 | Test Case on No Default Content |
other revised to S3-243435 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
revised | [WTS] [JSN] | |||
| S3-242771 | Test Case on No Directory Listings |
other revised to S3-243436 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
revised | [WTS] [JSN] | |||
| S3-242772 | Test Case on No Web Server Header Info |
other revised to S3-243687 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
revised | [WTS] [JSN] | |||
| S3-242773 | Test Case on No Web Server Error Pages Info |
other revised to S3-243437 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
revised | [WTS] [JSN] | |||
| S3-242774 | Test Case on No Web Server File Type Mappings |
other revised to S3-243688 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
revised | [WTS] [JSN] | |||
| S3-242775 | Adaptation of 256-bit algorithm for AS and NAS | other | Nokia, Nokia Shanghai Bell |
S3-117 AI: 6 |
noted | [WTS] [JSN] | |||
| S3-242776 | Editorial Modifications |
pCR revised to S3-243648 |
Nokia, Nokia Shanghai Bell | 33.700-41 0.2.0 | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
revised | [WTS] [JSN] |
| S3-242777 | Proposed changes to the Conclusions | pCR | Nokia, Nokia Shanghai Bell | 33.700-41 0.2.0 | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
approved | [WTS] [JSN] |
| S3-242778 | Trust anchoring for N32-f/PRINS |
CR revised to S3-242822 |
BSI (DE) | 33.501 18.6.0 CR#2031 catB | Roaming5G | Rel-18 |
S3-117 AI: 4.1.14 |
revised | [WTS] [JSN] |
| S3-242779 | Conclude LI impacts for PNI-NPN Solutions in TR 33.757 | pCR | Johns Hopkins University APL | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-242780 | LS on aggregation and other N32 topics in the context of mediated roaming |
LS out LS is reply to S3-242706 source LS: S3-242364 LS To: GSMA 5GMRR revised to S3-243676 |
BSI (DE) | Roaming5G | Rel-18 |
S3-117 AI: 3 |
revised | [WTS] [JSN] | |
| S3-242781 | Living document for CryptoSP: draftCR to TS 33.501, Updates to cryptographic profiles |
draftCR revised to S3-243428 |
Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
revised | [WTS] [JSN] | |
| S3-242782 | Living document for CryptoSP: draftCR to TS 33.210, Updates to cryprographic profiles |
draftCR revised to S3-243429 |
Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
revised | [WTS] [JSN] | |
| S3-242783 | Living document for CryptoSP: draftCR to TS 33.310, Updates to cryptographic profiles |
draftCR revised to S3-243430 |
Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
revised | [WTS] [JSN] | |
| S3-242784 | Living document for CryptoSP: draftCR to TS 33.203, Updates to cryptographic profiles |
draftCR revised to S3-243431 |
Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
revised | [WTS] [JSN] | |
| S3-242785 | Supplementary on Solution #6: Collection of security related log data of NFs via DCCF | CR | BSI (DE) | 33.738 18.1.0 CR#3 catB | FS_eNA_SEC_Ph3 | Rel-18 |
S3-117 AI: 4.1.15 |
withdrawn | [WTS] [JSN] |
| S3-242786 | Annexes on 256-bit security and backwards compatibility |
pCR revised to S3-243647 |
KDDI Corporation, Cablelabs, Ericsson | 33.700-41 0.2.0 | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
revised | [WTS] [JSN] |
| S3-242787 | pCR on Editorial cleanup | pCR | KDDI Corporation | 33.700-41 0.2.0 | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
approved | [WTS] [JSN] |
| S3-242788 | Presentation of Specification to TSG: TR 33.700-41 |
TS or TR cover revised to S3-243649 |
KDDI Corporation | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
revised | [WTS] [JSN] | |
| S3-242789 | New WID on supporting 256-bit ciphering and integrity protection algorithms | WID new | KDDI Corporation | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-242790 | Add notes to KI#4 in TR 33.745 | pCR | China Mobile Com. Corporation | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-242791 | Algorithm identifier values for 256-bit algorithms | draftCR | KDDI Corporation | FS_CAT256 | Rel-18 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | |
| S3-242792 | Add notes to section 6.7 in TR 33.784 |
pCR revised to S3-243713 |
China Mobile Com. Corporation | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-242793 | (Draft) LS on 256-bit algorithm identifiers |
LS out LS To: CT1 |
KDDI Corporation | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-242794 | New Solution to KI#7: Verify and authorise direct connections between 5G NR Femtos |
pCR revised to S3-243515 |
China Mobile Com. Corporation | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-242795 | New Solution to KI#4: Privacy preserving scheme for exchanging training data when AF acting as VFL server | pCR | China Mobile Com. Corporation | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-242796 | New KI on Requirements for traffic monitoring and anomaly behavior analysis of 5G Femto |
pCR revised to S3-243521 |
China Mobile Com. Corporation | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-242797 | Solution on Privacy Protection for AIoT device | pCR | Sony | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242798 | 1-Hop Forward Security Solution for LTM |
other revised to S3-243524 |
vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-242799 | Discussion on Conclusion to Address Attack in MiBiDA | discussion | vivo | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
noted | [WTS] [JSN] | |
| S3-242800 | Conclusion for key issue #1 | pCR | vivo | 33.701 0.3.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
merged | [WTS] [JSN] |
| S3-242801 | New Solution Mitigation of Roaming Attack |
pCR revised to S3-243509 |
vivo | 33.701 0.3.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
revised | [WTS] [JSN] |
| S3-242802 | New Key Issue on Exposure of Inventory Device Quantity | pCR | vivo | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242803 | New solution on Protection on Quantity of AIoT Devices during Inventory | pCR | vivo | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242804 | New solution on Authentication for AIoT Device | pCR | vivo | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242805 | New solution on Communication Security of intermediate UE interacting with AIoT device | pCR | vivo | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242806 | Update on Key Issue#4 |
pCR revised to S3-243575 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-242807 | Update on Key Issue#1 | pCR | vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-242808 | New solution on KI#1 Authorization for LCS Data Storage and Retrieval |
pCR revised to S3-243576 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-242809 | EN Address for Solution#4 Authorization of VLF member selection |
pCR revised to S3-243579 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-242810 | Evaluation for Solution#4 Authorization of VLF member selection |
pCR revised to S3-243591 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-242811 | Update for Solution#10 Privacy of Simple alignment |
pCR revised to S3-243585 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-242812 | Conclusion Skeleton for AIML_SEC | pCR | vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-242813 | Conclusion for KI4 | pCR | vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-242814 | New solution on Reusing SBA to Protect Communication Data in Training Process | pCR | vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-242815 | New Use case proposal for data exposure related to attacks on network slices |
pCR revised to S3-243493 |
IRT, Nokia, Nokia Shanghai Bell | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242816 | Discussion on Impact Analysis for Inter-CU LTM | discussion | Nokia, Nokia Shanghai Bell |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-242817 | Discussion on Potential Solution for Inter-CU LTM | discussion | Nokia, Nokia Shanghai Bell |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-242818 | Solution for Inter-CU LTM |
other revised to S3-243525 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |||
| S3-242819 | LS on Security Handling for inter-CU LTM in non-DC cases |
LS out LS To: 3GPP RAN WG2 revised to S3-243666 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |||
| S3-242820 | Discussion on 3GPP Cryptographic Inventory | discussion | Nokia, Nokia Shanghai Bell |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242821 | Living document of the Non3GPPMobEnh study |
draftCR revised to S3-243642 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 4.13 |
revised | [WTS] [JSN] | |
| S3-242822 | Trust anchoring for N32-f/PRINS |
CR revision of S3-242778 revised to S3-242823 |
Federal Office for Information Security (BSI), Nokia | 33.501 18.6.0 CR#20311 catB | Roaming5G | Rel-18 |
S3-117 AI: 4.1.14 |
revised | [WTS] [JSN] |
| S3-242823 | Trust anchoring for N32-f/PRINS |
CR revision of S3-242822 |
Federal Office for Information Security (BSI), Nokia | 33.501 18.6.0 CR#20312 catB | Roaming5G | Rel-18 |
S3-117 AI: 4.1.14 |
not pursued | [WTS] [JSN] |
| S3-242824 | SA3 input to Reply LS on clarifications on consent management |
LS out LS To: SA |
Nokia |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242825 | A solution for Key Issue #2.1: Secure retrieval of 5G system UE IDs | pCR | InterDigital New York | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
merged | [WTS] [JSN] |
| S3-242826 | A new solution for AIML Data Privacy Protection | pCR | InterDigital New York | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-242827 | A new solution of security protection for VFL entity communication | pCR | InterDigital New York | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-242828 | Solution for security retrieval of 5G UE Id and privacy related information |
pCR revised to S3-243628 |
Nokia, Nokia Shanghai Bell | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-242829 | Solution for secure retrieval of 5G UE privacy related information based on AKMA |
pCR revised to S3-243629 |
Nokia, Nokia Shanghai Bell | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-242830 | New KI on Security aspects related to enhancements of EAS and local UPF (re)selection |
pCR revised to S3-243665 |
Nokia, Nokia Shanghai Bell | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-242831 | Correction to validation of usage of X.509 certificate procedure | CR | Nokia, Nokia Shanghai Bell, Ericsson, Johns Hopkins University APL, Cisco, Huawei | 33.310 19.1.0 CR#202 catA | ACM_SBA | Rel-19 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-242832 | Updates to the SBA certificate profile | CR | Nokia, Johns Hopkins University APL, Cisco, Ericsson | 33.310 19.1.0 CR#203 catA | ACM_SBA | Rel-19 |
S3-117 AI: 4.1.15 |
merged | [WTS] [JSN] |
| S3-242833 | Solution for enhancement of SBA access control decision mechanisms |
pCR revised to S3-243613 |
Nokia | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242834 | Discussion of enhancements for SNPN cellular hotspots |
discussion revision of S3-242066 |
Cisco Systems, Intel |
S3-117 AI: 6 |
noted | [WTS] [JSN] | |||
| S3-242835 | pCR on KI for 5GS Core network topology hiding from 5G Femto deployments |
pCR revision of S3-241110 |
Charter Communications, Inc | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-242836 | Study on Security Aspects of Interconnect of SNPN |
SID new revision of S3-242061 |
Cisco Systems, Intel | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-242837 | Further conclusion for Key issue #1 |
pCR revised to S3-243697 |
Charter Communications, Inc | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
revised | [WTS] [JSN] |
| S3-242838 | KI#1, Solution #3 Updates: Data Collection |
pCR revised to S3-243365 |
OTD_US, MITRE | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242839 | SWG Discussion | discussion | SA3 Chair |
S3-117 AI: 2.1 |
noted | [WTS] [JSN] | |||
| S3-242840 | Editorial correction to section 6.4 | pCR | China Mobile Com. Corporation | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-242841 | Revision of two errors in TR 33.757 | pCR | China Mobile Com. Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-242842 | Supplementary on Solution #6: Collection of security related log data of NFs via DCCF | CR | BSI (DE) | 33.738 18.1.0 CR#4 catB | FS_eNA_SEC_Ph3 | Rel-18 |
S3-117 AI: 4.1.15 |
withdrawn | [WTS] [JSN] |
| S3-242843 | Supplementary on Solution #6: Collection of security related log data of NFs via DCCF | CR | China Mobile Com. Corporation | 33.738 18.1.0 CR#5 catB | FS_eNA_SEC_Ph3 | Rel-18 |
S3-117 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-242844 | Solution for Lightweight AIoT ID privacy | pCR | InterDigital Communications | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242845 | An update for Key Issue #2: Authorization for 5G Ambient IoT Services | pCR | InterDigital Communications | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242846 | An Update for Solution #21: Remediation of unauthenticated (D)DOS in S&F |
pCR revised to S3-243535 |
InterDigital Communications | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-242847 | An Update for the Evaluation of Solution #21 |
pCR revised to S3-243536 |
InterDigital Communications | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-242848 | TR 33.759 update solution #1 |
pCR revised to S3-243605 |
InterDigital Canada | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-242849 | TR 33.759 conclusion KI #1 | pCR | InterDigital Canada | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
noted | [WTS] [JSN] |
| S3-242850 | TR 33.700-32 update solution #2 |
pCR revised to S3-243440 |
InterDigital Canada | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242851 | TR 33.700-32 update solution #3 |
pCR revised to S3-243441 |
InterDigital Canada | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242852 | LS Replay on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 source LS: S2-2407236 LS To: SA2 revised to S3-243558 |
InterDigital Canada | FS_UIA_ARC | Rel-19 |
S3-117 AI: 3 |
revised | [WTS] [JSN] | |
| S3-242853 | TR 33.743 update solution #1 |
pCR revised to S3-243663 |
InterDigital Canada | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-242854 | Solution on certificate revocation |
pCR revised to S3-243487 |
Johns Hopkins University APL, Cisco Systems, MITRE-FFRDC, US National Security Agency | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-242855 | New WID on Security for MonStra |
WID new revised to S3-243671 |
Vodafone, Telefonica, Nokia, Nokia Shanghai Bell | Rel-19 |
S3-117 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-242856 | Conclusion for KI#3 in TR 33.700-32 |
pCR revised to S3-243465 |
CableLabs, Charter Communications | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242857 | Conclusion for KI#1 in TR 33.754 | pCR | CableLabs, Charter Communications | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
merged | [WTS] [JSN] |
| S3-242858 | Conclusion for KI#2 in TR 33.754 | pCR | CableLabs, Charter Communications | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
merged | [WTS] [JSN] |
| S3-242859 | pCR to TR 33.713 Add new security assumptions for Clause 4 | pCR | CATT | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-242860 | pCR to TR33.713 Update key issue#4 for adding threats and requirements | pCR | CATT | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242861 | pCR to TR33.713 New key issue on authentication of AIoT Devices | pCR | CATT | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242862 | New solution for KI#1: Analytics for Secure N4 interface with Security Gateway | pCR | MITRE-FFRDC, Defense Information Systems Agency EM | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-242863 | pCR to TR33.713 New solution for protecting Device IDs in inventory scenarios | pCR | CATT | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242864 | pCR to pCR to TR33.713 New solution for message protection in command scenarios | pCR | CATT | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242865 | pCR to TR33.700-29 New solution on anti DoS attacks and privacy protection for S&F operations |
pCR revised to S3-243551 |
CATT | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-242866 | Discussion on Ambient IoT Device Resource Limitation | discussion | Xidian University |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] | |||
| S3-242867 | New solution for KI#2: Dynamic Security Policy Enforcement Framework |
pCR revised to S3-243614 |
MITRE-FFRDC, Defense Information Systems Agency EM | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242868 | Conclusions for Data Collection | pCR | MITRE-FFRDC, US National Security Agency | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
noted | [WTS] [JSN] |
| S3-242869 | New solution for KI #1 Data Collection using DCCF |
pCR revised to S3-243502 |
MITRE-FFRDC | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242870 | Update sol9 on Secure IMS DC capability exposure |
pCR revised to S3-243623 |
Nokia, Nokia Shanghai Bell | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-242871 | Conclusion for KI#3 on IMS DC capability exposure | pCR | Nokia, Nokia Shanghai Bell | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-242872 | Update Sol3 on Support of Third Party specific User Identities in IMS |
pCR revised to S3-243616 |
Nokia, Nokia Shanghai Bell | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-242873 | Update Sol7 on Protect IMS DC based Avatar Communication |
pCR revised to S3-243622 |
Nokia, Nokia Shanghai Bell | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-242874 | Solution for KI#1 on Authorization supporting spatial localization service |
pCR revised to S3-243653 |
Nokia, Nokia Shanghai Bell | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-242875 | Solution for KI1 on Authorization of spatial anchor services with multiple VAL-S |
pCR revised to S3-243654 |
Nokia, Nokia Shanghai Bell | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-242876 | Add clarification on encryption operation for PC5 ProSe discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 17.8.0 CR#204 catF | 5G_ProSe | Rel-17 |
S3-117 AI: 4.1.3 |
agreed | [WTS] [JSN] |
| S3-242877 | Add clarification on encryption operation for PC5 ProSe discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 18.3.0 CR#205 catA | 5G_ProSe | Rel-18 |
S3-117 AI: 4.1.3 |
agreed | [WTS] [JSN] |
| S3-242878 | key issue for no transmit zones | pCR | Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
noted | [WTS] [JSN] |
| S3-242879 | Sol#2 update to address ENs |
pCR revised to S3-243672 |
Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-242880 | Sol#2 evaluation |
pCR revised to S3-243674 |
Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-242881 | Sol#3 update to address ENs |
pCR revised to S3-243673 |
Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-242882 | Sol#3 evaluation |
pCR revised to S3-243675 |
Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-242883 | Sol#4 evaluation | pCR | Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-242884 | Sol#5 update to address ENs |
pCR revised to S3-243442 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242885 | Sol#5 evaluation |
pCR revised to S3-243443 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242886 | Sol#19 update to address ENs |
pCR revised to S3-243454 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242887 | Sol#19 evaluation | pCR | Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-242888 | Sol#21 update to address ENs | pCR | Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-242889 | Sol#21 evaluation |
pCR revised to S3-243458 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242890 | Conclusions for KI#3 | pCR | Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
merged | [WTS] [JSN] |
| S3-242891 | Reply LS to SA2 on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 LS To: SA2 |
Huawei, HiSilicon | FS_UIA_Sec | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-242892 | update to Sol#1 |
pCR revised to S3-243488 |
Huawei, HiSilicon | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-242893 | update to Sol#3 |
pCR revised to S3-243489 |
Huawei, HiSilicon | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-242894 | overall evaluation for KI#1 |
pCR revised to S3-243490 |
Huawei, HiSilicon | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-242895 | overall evaluation for KI#3 |
pCR revised to S3-243491 |
Huawei, HiSilicon | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-242896 | key issue on CAPIF-8 security procedures | pCR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-242897 | key issue on authorization of fine granularity access control | pCR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-242898 | Reply LS to SA6 on Clarification related to Internal 5G Core information expose to trusted AF |
LS out LS is reply to S3-242730 LS To: SA6 revised to S3-243408 |
Huawei, HiSilicon | Rel-18 |
S3-117 AI: 3 |
revised | [WTS] [JSN] | ||
| S3-242899 | Addressing EN in Use Case 5 |
pCR revised to S3-243495 |
U.S. National Security Agency, Johns Hopkins University APL, OTD_US, MITRE-FFRDC | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-242900 | [Draft] Reply LS on LI considerations for TR 33.757 |
LS out LS is reply to S3-242741 LS To: SA3-LI |
ZTE Corporation | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-242901 | draft - Reply LS on clarification on home network triggered re-authentication |
LS out LS is reply to S3-243391 LS To: CT4 |
ZTE Corporation | HN_Auth | Rel-18 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-242902 | Clarifications for HONTRA procedure with respect to failure cases | CR | ZTE | 33.501 18.6.0 CR#2032 catF | HN_Auth | Rel-18 |
S3-117 AI: 3 |
merged | [WTS] [JSN] |
| S3-242903 | draft - Reply LS on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 LS To: SA2 |
ZTE Corporation | FS_UIA_ARC | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-242904 | CR to update AKMA service disable procedure | CR | ZTE Corporation | 33.535 18.4.0 CR#216 catF | AKMA_Ph2 | Rel-18 |
S3-117 AI: 4.1.5 |
merged | [WTS] [JSN] |
| S3-242905 | Message name correction to TS 33.501 | CR | ZTE Corporation | 33.501 18.6.0 CR#2033 catF | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-242906 | Discussion on security handling for inter-CU LTM in non-DC cases | discussion | ZTE Corporation | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | ||
| S3-242907 | MAC CE integrity protection solution for LTM | other | ZTE Corporation | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | ||
| S3-242908 | NCC synchronization solution for LTM |
other revised to S3-243526 |
ZTE Corporation | Rel-19 |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | ||
| S3-242909 | Conclusion to KI#3 |
pCR revised to S3-243484 |
ZTE Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-242910 | Remove the EN in KI#1 | pCR | ZTE Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-242911 | Update the Sol#15 |
pCR revised to S3-243481 |
ZTE Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-242912 | Update the Sol#16 |
pCR revised to S3-243482 |
ZTE Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-242913 | introduction of 256-bit encryption and integrity protection algorithms in TS 33.501 | draftCR | ZTE Corporation | TEI19 | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | |
| S3-242914 | LS on assigning algorithm identifier values for 256-bit algorithms |
LS out LS To: CT1 |
ZTE Corporation | Rel-19 |
S3-117 AI: 5.5 |
noted | [WTS] [JSN] | ||
| S3-242915 | conclusion for KI#1 | pCR | ZTE Corporation | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
merged | [WTS] [JSN] |
| S3-242916 | Overall summary update | pCR | ZTE Corporation | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
noted | [WTS] [JSN] |
| S3-242917 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
not treated | [WTS] [JSN] |
| S3-242918 | Update the Clause 4 | pCR | ZTE Corporation | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-242919 | Update the KI#1 |
pCR revised to S3-243534 |
ZTE Corporation | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-242920 | Evaluation for Solution #13 |
pCR revised to S3-243537 |
ZTE Corporation | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-242921 | Clean up for TR 33.713 | pCR | ZTE Corporation | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242922 | Update the KI#1 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242923 | Update the Sol#2 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242924 | New solution on KI#3 | pCR | ZTE Corporation | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242925 | address the ENs in Solution#4 clause 6.4.2.1 | pCR | ZTE Corporation | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-242926 | address the EN in Solution#4 clause 6.4.2.2 with user_ID activation | pCR | ZTE Corporation | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-242927 | address the EN in Solution#4 clause 6.4.2.3 | pCR | ZTE Corporation | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-242928 | add evaluation to Solution#4 |
pCR revised to S3-243444 |
ZTE Corporation | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242929 | update to Solution#2 LMF authorization | pCR | ZTE Corporation | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-242930 | Evaluation for Solution #1 |
pCR revised to S3-243652 |
ZTE Corporation | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-242931 | LS on Discrepancy between GSMA and 3GPP specifications on 5G Roaming over Roaming Intermediaries |
LS out LS is reply to S3-242706 LS To: TSG SA revised to S3-243677 |
CableLabs |
S3-117 AI: 3 |
revised | [WTS] [JSN] | |||
| S3-242932 | Agreed pCR of the last meeting Mobike | pCR | Nokia | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
approved | [WTS] [JSN] |
| S3-242933 | KI1 and KI3 conclusion update |
pCR revised to S3-243644 |
Nokia | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
revised | [WTS] [JSN] |
| S3-242934 | LS on clarification on trusted non 3GPP access technologies |
LS out LS To: SA3 |
Nokia | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
noted | [WTS] [JSN] | |
| S3-242935 | Discussion paper for Fast BSS details from 802.11 specs |
discussion revised to S3-243667 |
Nokia | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
revised | [WTS] [JSN] | |
| S3-242936 | Discussion paper for Fast BSS based NSWO solution | discussion | Nokia | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
noted | [WTS] [JSN] | |
| S3-242937 | KI2 and KI4conclusion update |
pCR revised to S3-243645 |
Nokia | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
revised | [WTS] [JSN] |
| S3-242938 | TR editorial correction | pCR | Nokia | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
approved | [WTS] [JSN] |
| S3-242939 | Reply LS on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 source LS: S2-2407236 LS To: SA2 |
Nokia | FS_UIA_Sec | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-242940 | Enhancing solution 15 |
pCR revised to S3-243446 |
Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242941 | Enhancing solution 18 | pCR | Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-242942 | evaluation of solution 18 | pCR | Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-242943 | Enhancing solution 17 |
pCR revised to S3-243455 |
Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-242944 | concluding KI3 | pCR | Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
merged | [WTS] [JSN] |
| S3-242945 | KI3 update | pCR | Nokia | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-242946 | Enhancing solution 3 |
pCR revised to S3-243578 |
Nokia | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-242947 | Solution 3 evaluation |
pCR revised to S3-243590 |
Nokia | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-242948 | KI2 conclusion | pCR | Nokia | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-242949 | Discussion paper reauthentication via untrusted non 3GPP access | discussion | Nokia | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
noted | [WTS] [JSN] | |
| S3-242950 | Discussion paper of UPU implementation gaps | discussion | Nokia | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
noted | [WTS] [JSN] | |
| S3-242951 | Enhancement in UPU procedure to protect UPU header | CR | Nokia | 33.501 18.6.0 CR#2034 catF | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-242952 | AKMA API Name correction along with other editorial corrections | CR | Nokia | 33.535 18.4.0 CR#217 catF | AKMA_Ph2 | Rel-18 |
S3-117 AI: 4.1.5 |
agreed | [WTS] [JSN] |
| S3-242953 | AAnF Providing VPLMN Id to AF | CR | Nokia, | 33.535 18.4.0 CR#218 catF | AKMA_Ph2 | Rel-18 |
S3-117 AI: 4.1.5 |
not pursued | [WTS] [JSN] |
| S3-242954 | Discussion Paper on Security Key Handling for Inter-CU LTM | discussion | Intel Technology India Pvt Ltd |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-242955 | Conclusion of Key Issue 1 | pCR | Intel Technology India Pvt Ltd | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
not treated | [WTS] [JSN] |
| S3-242956 | Discussion Paper FSAT Solutions | discussion | Intel Technology India Pvt Ltd |
S3-117 AI: 5.7 |
not treated | [WTS] [JSN] | |||
| S3-242957 | Cleanup TR 33.754 Introduction | pCR | Intel Technology India Pvt Ltd | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-242958 | Cleanup TR 33.754: Key issues |
pCR revised to S3-243602 |
Intel Technology India Pvt Ltd | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
revised | [WTS] [JSN] |
| S3-242959 | Reply LS on the use of TLS with QUIC in ATSSS context |
LS out LS is reply to LS LS To: SA2 |
Intel Technology India Pvt Ltd |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-242960 | Update to New SID on security aspects for Multi-Access (DualSteer + ATSSS Ph-4) |
SID revised revision of S3-241191 |
NEC Corporation | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
noted | [WTS] [JSN] | |
| S3-242961 | UICC support for Ambient IoT Service | discussion | THALES, ORANGE | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] | ||
| S3-242962 | Discussion on Dual steer device and AKMA procedure | discussion | NEC Corporation | Rel-19 |
S3-117 AI: 5.15 |
noted | [WTS] [JSN] | ||
| S3-242963 | New Key Issue | pCR | THALES, ORANGE | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242964 | MPQUIC TLS Annex |
CR revised to S3-243415 |
Intel, Nokia, Charter Communications, | 33.501 18.6.0 CR#2035 catF | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-242965 | Solution #14 |
pCR revised to S3-243508 |
THALES | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
revised | [WTS] [JSN] |
| S3-242966 | Conclusion for KI#1 | pCR | THALES | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
merged | [WTS] [JSN] |
| S3-242967 | Evaluation of solution #1 | pCR | THALES | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-242968 | Editorial Correction of TC_NO_SYSTEM_PRIVILEGES_WEB_SERVER | CR | BSI (DE) | 33.117 18.3.0 CR#191 catD | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-242969 | Evaluation of solution #2 | pCR | THALES | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-242970 | Clarification on TC_NO_CGI_OR_SCRIPTING_FOR_UPLOADS | CR | BSI (DE) | 33.117 18.3.0 CR#192 catF | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-242971 | Evaluation of solution #13 | pCR | THALES | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-242972 | Clarification on TC_ACCESS_RIGHTS_WEB_SERVER_FILES | CR | BSI (DE) | 33.117 18.3.0 CR#193 catF | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-242973 | Clarification on TC_NO_DIRECTORY_LISTINGS | CR | BSI (DE) | 33.117 18.3.0 CR#194 catF | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-242974 | Clarification on TC_NO_WEB_SERVER_ERROR_PAGES_INFORMATION | CR | BSI (DE) | 33.117 18.3.0 CR#195 catF | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-242975 | Revised WID on Milenage-256 algorithm | WID revised | THALES, IDEMIA | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
agreed | [WTS] [JSN] | |
| S3-242976 | Clarification on TC_BVT_PORT_SCANNING | CR | BSI (DE) | 33.117 18.3.0 CR#196 catF | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-242977 | Selection of the option | discussion | THALES |
S3-117 AI: 4.7 |
endorsed | [WTS] [JSN] | |||
| S3-242978 | Removal of boiler plate texts in format of evidence |
CR revised to S3-243661 |
BSI (DE) | 33.117 18.3.0 CR#197 catF | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
revised | [WTS] [JSN] |
| S3-242979 | Content of TR 35.234 |
pCR revised to S3-243422 |
THALES | 35.234 0.1.0 | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
revised | [WTS] [JSN] |
| S3-242980 | Content of TS 35.235 |
pCR revised to S3-243423 |
THALES | 35.235 0.1.0 | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
revised | [WTS] [JSN] |
| S3-242981 | Add UDM SCAS test case for checking the authentication verification of a synchronization failure message |
CR revised to S3-243029 |
BSI (DE) | 33.514 18.3.0 CR#31 catF | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
revised | [WTS] [JSN] |
| S3-242982 | Content of TS 35.236 |
pCR revised to S3-243424 |
THALES | 35.236 0.1.0 | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
revised | [WTS] [JSN] |
| S3-242983 | Update KI on protection of information during AIoT service communication | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242984 | Solution on disabling operation procedure for AIoT services | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242985 | Remove ENs and update evaluation in Solution #12 |
pCR revised to S3-243539 |
OPPO | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-242986 | Update of Solution #1: Solution reusing existing interfaces and security mechanisms for energy related information collection |
pCR revised to S3-243608 |
Ericsson | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-242987 | Evaluation to solution#2 in TR 33.745 |
pCR revised to S3-243512 |
China Telecomunication Corp. | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-242988 | New key issue for satellite switching with re-synchronization in regenerative architecture | pCR | Nokia | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
not treated | [WTS] [JSN] |
| S3-242989 | AIoT - Security solution on privacy | pCR | Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242990 | AIoT - New KI for Ambient IoT on Authentication | pCR | Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242991 | AIoT - New KI for Ambient IoT on communication security | pCR | Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-242992 | MiBiDA - Conclusions | pCR | Apple | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
merged | [WTS] [JSN] |
| S3-242993 | MiBiDA - Update overall summary | pCR | Apple | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
noted | [WTS] [JSN] |
| S3-242994 | MiBiDA - Update solution#10 |
pCR revised to S3-243507 |
Apple | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
revised | [WTS] [JSN] |
| S3-242995 | LTM - Discussion paper on LTM security | other | Apple |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-242996 | LTM - Reply LS to RAN2 on LTM progress | other | Apple |
S3-117 AI: 4.12 |
merged | [WTS] [JSN] | |||
| S3-242997 | LTM - content on living CR - Candidate solution#1 |
other revised to S3-243527 |
Apple |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |||
| S3-242998 | LTM - content on living CR - Candidate solution#2 |
other revised to S3-243528 |
Apple |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |||
| S3-242999 | MEC - Soltuion on EEC provided Information authentication |
pCR revised to S3-243630 |
Apple | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-243000 | Draft LS to SA6 on obtaining user consent for the exposure of User Sensitive Information |
LS out LS is reply to S3-243366 source LS: S6-240232 LS To: SA6 |
Apple |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243001 | New solution for data collection related to API security risks |
pCR revised to S3-243503 |
Nokia | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243002 | Solution 6 update with evaluation |
pCR revised to S3-243538 |
Nokia | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243003 | Solution 22 updates with EN removal | pCR | Nokia | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243004 | update to Solution#1 ownership security |
pCR revised to S3-243513 |
ZTE | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243005 | Solution 22 updates with evaluation |
pCR revised to S3-243540 |
Nokia | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243006 | add conclusions to KI#1 ownership security | pCR | ZTE | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-243007 | EN removal for solution #4 |
pCR revised to S3-243499 |
Nokia | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243008 | Evaluation for solution #4 |
pCR revised to S3-243500 |
Nokia | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243009 | New key issue for detection of malicious 5G NR Femto | pCR | Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-243010 | New key issue for privacy aspects of MRL | pCR | Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-243011 | New Solution for Security of 5G NR Femto Ownership |
pCR revised to S3-243516 |
Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243012 | New Solution for Femto Owner one time registration with operator network |
pCR revised to S3-243517 |
Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243013 | Evaluation to solution#6 |
pCR revised to S3-243473 |
China Telecomunication Corp. | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243014 | New Solution for Support of 5G Femto location security |
pCR revised to S3-243519 |
Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243015 | Update EN in solution#13 |
pCR revised to S3-243711 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243016 | Updates for solution #4 |
pCR revised to S3-243514 |
Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243017 | Evaluation to solution#7 |
pCR revised to S3-243474 |
China Telecomunication Corp. | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243018 | Conclusion to KI#1 |
pCR revised to S3-243471 |
China Telecomunication Corp.,ZTE, Huawei, HiSilicon, China Mobile | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243019 | Evaluation of solution#13 |
pCR revised to S3-243712 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243020 | Conclusion to KI#2 |
pCR revised to S3-243479 |
China Telecomunication Corp., ZTE, Huawei, HiSilicon, China Mobile | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243021 | Addressing the EN and evaluation of Solution#4 | pCR | Huawei, HiSilicon | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243022 | Addressing the ENs on dynamic name card details and exposure mechanisms of solution#4 | pCR | Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243023 | Addressing the ENs on token related details and alignment of SA2 for solution#5 |
pCR revised to S3-243618 |
Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-243024 | Addressing the EN on details of determining the received Avatar ID of solution 5 |
pCR revised to S3-243617 |
Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-243025 | Evaluation on Solution#5 |
pCR revised to S3-243619 |
Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-243026 | A new solution on the security of IMS DC capability exposure |
pCR revised to S3-243625 |
Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-243027 | Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-242727 LS To: SA4 |
Huawei, HiSilicon | Rel-18 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-243028 | A new solution on authorizing AF to retrieve UE ID |
pCR revised to S3-243627 |
Huawei, HiSilicon | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-243029 | Add UDM SCAS test case for checking the authentication verification of a synchronization failure message |
CR revision of S3-242981 |
BSI (DE) | 33.514 18.3.0 CR#311 catF | SCAS_5G_Ph3, SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-243030 | New WID on Security for PLMN hosting a NPN | WID new | China Telecomunication Corp., , ZTE | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-243031 | Addressing the EN on the authorization mechanism through NRF and NEF for AF outside the PLMN |
pCR revised to S3-243581 |
Huawei, HiSilicon | 33.784 0.2.0 | eNA | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243032 | Evaluation to the solution on an authorization mechanism through NRF and NEF for AF outside the PLMN |
pCR revised to S3-243593 |
Huawei, HiSilicon | 33.784 0.2.0 | eNA | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243033 | Security protection based on AKA procedure in S&F operation with a full CN onboard the satellite |
pCR revised to S3-243552 |
Huawei, HiSilicon | 33.700-29 0.3.0 | SAT | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243034 | Interim GUTI privacy protection based on pseudonym UE IDs |
pCR revised to S3-243554 |
Huawei, HiSilicon | 33.700-29 0.3.0 | SAT | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243035 | Evaluation update on solution 9 | pCR | Huawei, HiSilicon | 33.700-29 0.3.0 | SAT | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243036 | User ID privacy protection based on EAP-TLS protocol using pseudonym mechanism |
pCR revised to S3-243460 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243037 | Addressing the EN on Human User authentication of through NAS procedure | pCR | Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243038 | Evaluation to solution 6 to address KI#1 |
pCR revised to S3-243447 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243039 | Conclusion on the security releted with 5G System Enhancements for Edge Computing | pCR | Huawei, HiSilicon | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
noted | [WTS] [JSN] |
| S3-243040 | Reply LS to CT4 on Resource content filters |
LS out LS is reply to S3-242710 LS To: CT4 |
Huawei, HiSilicon | Rel-18 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-243041 | Conclusion of KI#1 | pCR | China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
withdrawn | [WTS] [JSN] |
| S3-243042 | Discussion about Rel-18 ATSSS | discussion | Ericsson | Rel-18 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-243043 | Conclusion of KI#2 |
pCR revised to S3-243573 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243044 | Update of Solution #5: UE authentication and traffic protection in ATSSS-Lite | pCR | Ericsson | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
noted | [WTS] [JSN] |
| S3-243045 | Conclusion of Key issue #1 in TR 33.700-29 | pCR | China Telecomunication Corp. | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
not treated | [WTS] [JSN] |
| S3-243046 | Update of Solution #5: Discussion on UPF exposure |
pCR revised to S3-243598 |
Ericsson | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
revised | [WTS] [JSN] |
| S3-243047 | Adding the requirement of media confidentiality protection for IMS data channel | CR | Huawei, HiSilicon | 33.328 18.1.0 CR#78 catF | NG_RTC_SEC | Rel-18 |
S3-117 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-243048 | Replacing DCMF with MF |
CR revised to S3-243417 |
Huawei, HiSilicon | 33.328 18.1.0 CR#79 catF | NG_RTC_SEC | Rel-18 |
S3-117 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-243049 | Discussion paper on privacy issue associated with user id | discussion | Nokia | Rel-19 |
S3-117 AI: 5. |
noted | [WTS] [JSN] | ||
| S3-243050 | KI2 update |
pCR revised to S3-243464 |
Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243051 | Update the security threats of Key Issue #2: Authorization mechanism of selection of VFL participants in the VFL group |
pCR revised to S3-243705 |
Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243052 | Resolve the EN and update Solution #11 |
pCR revised to S3-243586 |
Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243053 | update to AKMA service disabling |
CR revised to S3-243413 |
Huawei, HiSilicon | 33.535 18.4.0 CR#219 catF | AKMA_Ph2 | Rel-18 |
S3-117 AI: 4.1.5 |
revised | [WTS] [JSN] |
| S3-243054 | solution on protection for disabling device operation | pCR | Huawei, HiSilicon, China Unicom, CAICT | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243055 | solution on protection for inventory and command procedure | pCR | Huawei, HiSilicon | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243056 | update to the support of ESP encryption transforms in TS 33.210 |
other revised to S3-243719 |
Huawei, HiSilicon | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
revised | [WTS] [JSN] | |
| S3-243057 | Resolution of EN on solution 18 |
pCR revised to S3-243693 |
Huawei, HiSilicon | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243058 | Evaluation update on solution 18 |
pCR revised to S3-243541 |
Huawei, HiSilicon | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243059 | update to the key issue on the protection of information during AIoT service | pCR | Huawei, HiSilicon, China Unicom, Vivo, Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243060 | New Key Issue for Authentication in Ambient IoT service |
pCR revised to S3-243680 |
Huawei, HiSilicon, China Unicom, Vivo, Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243061 | discussion paper on LTM solutions | discussion | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243062 | Evaluation on solution 1 for KI#1 |
pCR revised to S3-243704 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243063 | Resolution of EN on solution 9 for KI#3 |
pCR revised to S3-243584 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243064 | Correct the Federal Learning procedure |
CR revised to S3-243414 |
Huawei, HiSilicon | 33.501 18.6.0 CR#2036 catF | eNA_Ph3_SEC | Rel-18 |
S3-117 AI: 4.1.13 |
revised | [WTS] [JSN] |
| S3-243065 | Resolution of EN on solution 1 for KI#1 |
pCR revised to S3-243703 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243066 | Evaluation on solution 9 for KI#3 |
pCR revised to S3-243596 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243067 | Update procedure Security for AI/ML model storage and sharing in TS 33.501 | CR | Huawei, HiSilicon | 33.501 18.6.0 CR#2037 catF | eNA_Ph3_SEC | Rel-18 |
S3-117 AI: 4.1.13 |
not pursued | [WTS] [JSN] |
| S3-243068 | Address EN for solution 1 | pCR | Huawei, HiSilicon | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-243069 | Add evaluation to solution 1 |
pCR revised to S3-243600 |
Huawei, HiSilicon | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
revised | [WTS] [JSN] |
| S3-243070 | Address EN for solution 6 |
pCR revised to S3-243601 |
Huawei, HiSilicon | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
revised | [WTS] [JSN] |
| S3-243071 | Add evaluation to solution 6 | pCR | Huawei, HiSilicon | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-243072 | Removing ENs and adding evaluation in Sol#19 of TR 33.700-29 |
pCR revised to S3-243695 |
Huawei, HiSilicon | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243073 | Evaluates to solution#22 of TR 33.700-29 | pCR | Huawei, HiSilicon | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-243074 | Update KI#4 : Security of communication data used in VFL training process | pCR | Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-243075 | Solution to KI#4 : Security of communication data used in VFL training process |
pCR revised to S3-243589 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243076 | Evaluation on the solution 10 for KI#3 |
pCR revised to S3-243597 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243077 | Evaluation on the solution 11 for KI#3 |
pCR revised to S3-243587 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243078 | Evaluation on the solution 12 for KI#3 | pCR | Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243079 | Evaluation on the solution 13 for KI1 | pCR | Huawei, HiSilicon | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243080 | Evaluation on the solution 14 for KI2 | pCR | Huawei, HiSilicon | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243081 | Evaluation on the solution 17 for KI3 | pCR | Huawei, HiSilicon | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243082 | Evaluation for KI#1 and KI#2 on N4/SBA Security for solution 3 |
pCR revised to S3-243469 |
Huawei, HiSilicon | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243083 | solution related to KI2 |
pCR revised to S3-243609 |
Huawei, HiSilicon | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-243084 | Evaluation for solution 3 | pCR | Huawei, HiSilicon | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243085 | Evaluation for solution 5 | pCR | Huawei, HiSilicon | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243086 | Conclusion on KI3 | pCR | Huawei, HiSilicon | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243087 | Evaluation to Use case 4 |
pCR revised to S3-243494 |
Huawei, HiSilicon | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243088 | Evaluation to Use case 5 | pCR | Huawei, HiSilicon | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-243089 | Resolve EN and evaluate to Sol#11 for multi-hop U2U security establishment |
pCR revised to S3-243669 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243090 | Resolve ENs in solution#5 of TR 33.743 |
pCR revised to S3-243560 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243091 | Update solution#5 to add security establishment with more than one intermediate relays | pCR | Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243092 | Evaluates to solution#5 of TR 33.743 |
pCR revised to S3-243561 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243093 | Evaluates to solution#4 of TR 33.743 |
pCR revised to S3-243568 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243094 | Evaluates to solution#6 of TR 33.743 |
pCR revised to S3-243670 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243095 | Evaluates to solution#1 of TR 33.743 | pCR | Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-243096 | Reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-242721 source LS: S2-2407207 LS To: SA2 |
Huawei, HiSilicon | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |
| S3-243097 | Resolution of EN concerning the content of AN-parameters. |
CR revised to S3-243405 |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, ZTE | 33.501 18.6.0 CR#2038 catF | eNPN_Ph2 | Rel-18 |
S3-117 AI: 4.1.9 |
revised | [WTS] [JSN] |
| S3-243098 | DraftCR for TNAP and TWIF case | draftCR | Huawei, HiSilicon | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 4.13 |
merged | [WTS] [JSN] | |
| S3-243099 | new conclusion to KI#4 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
merged | [WTS] [JSN] |
| S3-243100 | new conclusion to KI#2 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
merged | [WTS] [JSN] |
| S3-243101 | Remove ENs to KI#1 and KI#3 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
merged | [WTS] [JSN] |
| S3-243102 | Update evaluation to solution 9 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243103 | Update evaluation to solution 12 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243104 | Update evaluation to solution 13 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243105 | Update evaluation to solution 16 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243106 | Update evaluation to solution 18 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243107 | Update evaluation to solution 19 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243108 | Update evaluation to solution 20 | pCR | Huawei, HiSilicon | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243109 | hosting party authentication using EAP-AKA’ | pCR | Huawei, HiSilicon | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243110 | Security solution for backhaul link between 5G NR Femto and 5GC |
pCR revised to S3-243520 |
Huawei, HiSilicon | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-243111 | Security solution for link between 5G NR Femto and 5G NR Femto MS | pCR | Huawei, HiSilicon | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243112 | Expired certificate checking at gNB to TS 33.511 | draftCR | Huawei, HiSilicon,CAICT,CTCC, Nokia | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243113 | Peer certificate checking at gNB to TS 33.511 | draftCR | Huawei, HiSilicon,CAICT,CTCC, Nokia | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243114 | Add threat to expired certificate checking at gNB | draftCR | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243115 | Add threat to peer certificate checking at gNB | draftCR | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243116 | Add evaluation to solution 20 |
pCR revised to S3-243456 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243117 | New WID Proposal on Mitigations on Bidding Down Attack | WID new | Huawei, HiSilicon | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-243118 | Way forward | discussion | Huawei, HiSilicon | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
merged | [WTS] [JSN] | |
| S3-243119 | Conference call minutes | report | Huawei, HiSilicon | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
noted | [WTS] [JSN] | |
| S3-243120 | Updates to overall summary |
pCR revised to S3-243659 |
Huawei, HiSilicon | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
revised | [WTS] [JSN] |
| S3-243121 | Updates to the assumption clause |
pCR revised to S3-243492 |
Huawei, HiSilicon | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-243122 | Conclusion proposal |
pCR revised to S3-243511 |
Huawei, HiSilicon | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
revised | [WTS] [JSN] |
| S3-243123 | Resolution of ENs on solution 1 |
pCR revised to S3-243631 |
Huawei, HiSilicon | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-243124 | Evaluation on solution 1 |
pCR revised to S3-243632 |
Huawei, HiSilicon | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-243125 | Update KI2 about privacy of exposure energy related information | pCR | Huawei, HiSilicon | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
merged | [WTS] [JSN] |
| S3-243126 | New key issue on security aspect of digital asset container in 5G |
pCR revised to S3-243650 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-243127 | New solution for KI#1 using Attribute-Based Authorization for the consumers | pCR | Huawei, HiSilicon | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-243128 | New solution for user authentication with EAP-PSK | pCR | Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243129 | New Solution on user authentication with user certificate of KI1 |
pCR revised to S3-243461 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243130 | New WID on specification of alternative example f5* (f5**) function | WID new | Ericsson | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-243131 | Skeleton of specification of alternative example f5* (f5**) function | other | Ericsson | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-243132 | pCR to f5** specification TS | other | Ericsson | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-243133 | Presentation of specification of alternative example f5* (f5**) function | other | Ericsson | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-243134 | New key issue for CAPIF interconnection | pCR | Ericsson, Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-243135 | New solution for CAPIF interconnection | pCR | Ericsson | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-243136 | New key issue for nested API invocation | pCR | Ericsson | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-243137 | New key issue for accessing UE resources by an application on another UE | pCR | Ericsson, Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-243138 | Solution for accessing UE resources by an application on another UE | pCR | Ericsson | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-243139 | Key issue on security of resource owner permission management |
pCR revised to S3-243636 |
Ericsson, Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243140 | Solution for managing resource owner permission | pCR | Ericsson | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-243141 | Solution mapping |
pCR revised to S3-243610 |
Ericsson | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-243142 | Update of Solution #9: Clarification and removal of Editor's Notes |
pCR revised to S3-243448 |
Ericsson | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243143 | Update of Solution #9: Resolution of Editor's Note on protection of user ID |
pCR revised to S3-243449 |
Ericsson | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243144 | Observations on and issues with NAS based solutions to Key Issue #1 of TR 33.700-32 "Authentication and Authorization of Human User ID" | discussion | Ericsson, CableLabs, NTT DOCOMO |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243145 | Reply LS on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 LS To: SA2 |
Ericsson | FS_UIA_ARC | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-243146 | Update of Solution #11: Resolving Editor's Notes on further clarification | pCR | Ericsson | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243147 | Update of Solution #11: Resolve Editor's Note on mobility | pCR | Ericsson | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243148 | Conclusion for Key Issue #3 (authentication and authorization of non-3GPP device behind UE/5G-RG) | pCR | Ericsson | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
merged | [WTS] [JSN] |
| S3-243149 | New solution for EEC provided information verification: UE ID token |
pCR revised to S3-243633 |
Ericsson | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-243150 | Mapping of solutions to key issues | pCR | Ericsson | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-243151 | Solution for multiple USS case |
pCR revised to S3-243604 |
Ericsson | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-243152 | Conclusion for KI#1 | pCR | THALES | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
withdrawn | [WTS] [JSN] |
| S3-243153 | LS on Masking of cryptographic keys in UE trace file from 3GPP core network entities |
LS out LS To: SA5 revised to S3-243696 |
Ericsson |
S3-117 AI: 3 |
revised | [WTS] [JSN] | |||
| S3-243154 | New key issue about CAPIF interconnection in TR 33.700-22 |
pCR revised to S3-243638 |
China Telecom Corporation Ltd., Xiaomi | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243155 | New key issue about CAPIF-8 security in TR 33.700-22 | pCR | China Telecom Corporation Ltd. | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-243156 | New key issue about Service API invocation authorization with resource owner consent in TR 33.700-22 | pCR | China Telecom Corporation Ltd. | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-243157 | Reply LS on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 source LS: S2-2407236 LS To: SA2 |
LG Electronics | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-243158 | New solution for LTM security handling |
other revised to S3-243529 |
LG Electronics | Rel-19 |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | ||
| S3-243159 | Editorial correction for AKMA procedures | CR | LG Electronics | 33.535 18.4.0 CR#220 catF | AKMA_Ph2 | Rel-18 |
S3-117 AI: 4.1.5 |
agreed | [WTS] [JSN] |
| S3-243160 | Validation of the allowed slices in the access token request at NRF |
CR revised to S3-243682 |
Ericsson | 33.501 18.6.0 CR#2039 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-117 AI: 4.1.2 |
revised | [WTS] [JSN] |
| S3-243161 | Validation of the requested slices at NF service producer |
CR revised to S3-243683 |
Ericsson | 33.501 18.6.0 CR#2040 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-117 AI: 4.1.2 |
revised | [WTS] [JSN] |
| S3-243162 | Discussion on the NF consumer PLMN ID check | discussion | Ericsson | Rel-18 |
S3-117 AI: 4.1.2 |
noted | [WTS] [JSN] | ||
| S3-243163 | Support iat claim in the access token | CR | Ericsson | 33.501 18.6.0 CR#2041 catB | TEI19 | Rel-19 |
S3-117 AI: 4.11 |
not pursued | [WTS] [JSN] |
| S3-243164 | Public key distribution and Issuer claim verification of the Access Token | CR | Ericsson | 33.501 18.6.0 CR#2042 catB | TEI19 | Rel-19 |
S3-117 AI: 4.11 |
not pursued | [WTS] [JSN] |
| S3-243165 | AIoT: Security assumptions in the 5G system | pCR | Ericsson | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243166 | New key issue for connectivity authentication in Ambient IoT | pCR | Ericsson | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243167 | New key issue for application layer authentication in Ambient IoT | pCR | Ericsson | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243168 | New key issue for Authenticated and authorized access to devices in Ambient IoT via 3GPP core | pCR | Ericsson | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243169 | AIoT: Security threats for KI on protection of information during AIoT service communication | pCR | Ericsson | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243170 | Authorization of AIoT capable UE in topology 2 | pCR | Ericsson | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243171 | Conclusion for Key Issue #1 "Security for dedicated UPF interacting with PLMN through N4 interface" | pCR | Ericsson | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243172 | Conclusion for Key Issue #2 "Dedicated NFs interacting with PLMN through SBA interface" | pCR | Ericsson | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243173 | Updating baseline of living document to 33.203 with content of the latest version of TS 33.203 | other | Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243174 | Updating baseline of living document to 33.310 with content of the latest version of TS 33.310 | other | Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243175 | Updating baseline of living document to 33.501 with content of the latest version of TS 33.501 | other | Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243176 | Forbid insecure usage of aes-gcm and aes-gmac | other | Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
noted | [WTS] [JSN] | |
| S3-243177 | Incorrect statements about 33.310 | CR | Ericsson | 33.401 15.11.0 CR#719 catF | TEI15 | Rel-15 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243178 | Incorrect statements about 33.310 | CR | Ericsson | 33.401 16.3.0 CR#720 catA | TEI15 | Rel-16 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243179 | Incorrect statements about 33.310 | CR | Ericsson | 33.401 17.5.0 CR#721 catA | TEI15 | Rel-17 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243180 | Incorrect statements about 33.310 | CR | Ericsson | 33.401 18.1.0 CR#722 catA | TEI15 | Rel-18 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243181 | Editorials on updates to the SBA certificate profile | CR | Nokia, Ericsson | 33.310 18.4.0 CR#204 catF | ACM_SBA | Rel-18 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243182 | Resolve the EN in Key issue #1 | pCR | China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-243183 | update solution #6 in TR 33.743 |
pCR revised to S3-243562 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243184 | Conclusion of KI#1 | pCR | China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-243185 | SCPAC: Secondary Node key update for SCPAC |
CR revised to S3-243418 |
Ericsson | 33.501 18.6.0 CR#2043 catF | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-243186 | Remove ENs and add evaluation in solution #12 |
pCR revised to S3-243588 |
OPPO | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243187 | Update KI#4 of TR 33.784 | pCR | OPPO | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-243188 | Reusing the exsiting security mechanism for VFL communication data | pCR | OPPO | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-243189 | Resolve one EN for Solution#5 |
pCR revised to S3-243580 |
Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243190 | Evaluation of Solution#5 |
pCR revised to S3-243592 |
Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243191 | Resolve other EN for Solution#5 | pCR | Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243192 | Conclusion on KI#4 | pCR | OPPO | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-243193 | Living document on NR mobility enhancement |
draftCR revised to S3-243689 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-243194 | Discussion on LTM from security perspective | discussion | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243195 | Key issue for security aspects of inter-CU LTM |
other revised to S3-243522 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-243196 | Key issue for authenticity verification of Cell Switch Command |
other revised to S3-243523 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-243197 | Solution for security aspects of inter-CU LTM |
other revised to S3-243530 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-243198 | Solution for verifying authenticity of cell switch command | other | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243199 | Conclusion for inter-CU LTM | other | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243200 | Evaluation for solution#9 | pCR | Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243201 | Update to Solution#9 |
pCR revised to S3-243476 |
Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243202 | Update to solution#17 |
pCR revised to S3-243483 |
Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243203 | Solution to enforce additional policy checks for NF Consumer in PNI-NPN |
pCR revised to S3-243485 |
Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243204 | Solution for SUPI privacy |
pCR revised to S3-243690 |
Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243205 | Conclusion for KI#1 | pCR | Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243206 | Conclusion for KI#2 | pCR | Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243207 | Conclusion for KI#3 | pCR | Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243208 | Resolution of ENs on user initiated procedure in Solution#16 | pCR | Samsung | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243209 | Resolution of ENs on Network triggered procedure in Solution#16 | pCR | Samsung | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243210 | Evaluation for solution#16 |
pCR revised to S3-243450 |
Samsung | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243211 | Discussion paper on metaverse | discussion | Samsung | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
noted | [WTS] [JSN] | |
| S3-243212 | Key issue on authentication and authorization of digital representation | pCR | Samsung | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-243213 | Solution for digital asset request validation | pCR | Samsung | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
noted | [WTS] [JSN] |
| S3-243214 | Solution for security aspects of CAPIF interconnection | pCR | Samsung | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-243215 | Conclusion for KI#1 in TR 33.701 | pCR | Samsung, Ericsson, Nokia, Lenovo | 33.701 0.3.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
merged | [WTS] [JSN] |
| S3-243216 | Solution for IP address verification |
pCR revised to S3-243634 |
Samsung | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-243217 | Reply LS on Resource content filter |
LS out LS is reply to S3-242710 LS To: CT4 revised to S3-243678 |
Samsung | Rel-19 |
S3-117 AI: 3 |
revised | [WTS] [JSN] | ||
| S3-243218 | Evaluation of solution#7 |
pCR revised to S3-243542 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243219 | Resolving EN of solution#8 |
pCR revised to S3-243543 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243220 | Evaluation of solution#8 |
pCR revised to S3-243544 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243221 | Update to solution#24 |
pCR revised to S3-243549 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243222 | Resolving EN of solution#25 |
pCR revised to S3-243546 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243223 | Evaluation of solution#25 |
pCR revised to S3-243547 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243224 | Update to solution#26 |
pCR revised to S3-243550 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243225 | Resolving EN in sol#9 | pCR | Samsung | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243226 | Resolving EN in sol#12 | pCR | Samsung | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243227 | Resolving EN in sol#19 | pCR | Samsung | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
not treated | [WTS] [JSN] |
| S3-243228 | Resolving EN in sol#6 |
pCR revised to S3-243620 |
Samsung | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-243229 | Evaluation for sol#6 |
pCR revised to S3-243621 |
Samsung | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-243230 | New solution on avatar communication |
pCR revised to S3-243624 |
Samsung | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-243231 | pCR to TR33.743 Update clause 3.1 and clause 3.3 | pCR | CATT | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243232 | Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-242427 LS To: SA4 |
China Mobile | 5G_MEDIA_MTSI_ext | Rel-18 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-243233 | New solution of Authentication and authorization in S&F based on onboard EPC |
pCR revised to S3-243553 |
China Mobile, CAICT | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243234 | Update solution 5 |
pCR revised to S3-243545 |
China Mobile, CAICT | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243235 | Adding description of non-MSGin5G UE scenarios | draftCR | China Mobile | 5GMARCH_SEC_Ph3 | Rel-19 |
S3-117 AI: 4.9 |
approved | [WTS] [JSN] | |
| S3-243236 | Living document of security aspects of MSGin5G service Ph3 |
draftCR revised to S3-243432 |
China Mobile | 5GMARCH_SEC_Ph3 | Rel-19 |
S3-117 AI: 4.9 |
revised | [WTS] [JSN] | |
| S3-243237 | Discussion on security assumption | discussion | China Mobile, CAICT | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] | ||
| S3-243238 | Architecture and Security Assumptions  for AIoT services | pCR | China Mobile, CAICT | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243239 | Reply LS on Clarification of requirements for Ambient IoT |
LS out LS is reply to S3-242723 LS To: SA1, SA2 |
China Mobile | FS_AmbientIoT | Rel-19 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |
| S3-243240 | Draft reply LS on LI considerations for TR 33.757 |
LS out LS is reply to S3-242741 LS To: SA3-LI revised to S3-243410 |
China Mobile | LI19 | Rel-19 |
S3-117 AI: 3 |
revised | [WTS] [JSN] | |
| S3-243241 | Solve EN for Sol#1&5 of TR 33.757 |
pCR revised to S3-243467 |
China Mobile | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243242 | Solve EN for sol#1&12 of TR 33.757 regarding SA3-LI |
pCR revised to S3-243386 |
China Mobile | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243243 | Solve EN for solution#12 to align with SA2 | pCR | China Mobile, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-243244 | Solve EN for solution#9 to align with SA2 | pCR | China Mobile, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-243245 | Solve EN for solution#10 to align with SA2 | pCR | China Mobile, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-243246 | Terms alignment with SA2 | pCR | China Mobile, vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243247 | Add abbreviations on TR 33.784 | pCR | China Mobile, vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243248 | pCR to TR33.743 Update clause 4 to standardize the use of terminology | pCR | CATT | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243249 | Discussion on security handling for inter-CU LTM in non-DC cases | discussion | OPPO | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243250 | Draft LS on reply to LS on FS_5GSAT_Ph3_ARCH conclusions |
LS out LS is reply to S3-242725 source LS: S2-2407350 LS To: SA2 |
CATT | FS_5GSAT_Ph3_ARCH | Rel-19 |
S3-117 AI: 5.7 |
noted | [WTS] [JSN] | |
| S3-243251 | Reply LS on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 LS To: SA2 |
OPPO | FS_UIA_ARC | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-243252 | Key Issue on Authenticating multiple API invokers of the same Resource Owner |
pCR revised to S3-243700 |
Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243253 | Update to solution #15 in TR 33.700-29 | pCR | Beijing Xiaomi Mobile Software | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243254 | Update to solution #16 in TR 33.700-29 | pCR | Beijing Xiaomi Mobile Software | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243255 | Update to solution #17 in TR 33.700-29 |
pCR revised to S3-243548 |
Beijing Xiaomi Mobile Software | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243256 | Reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-242721 source LS: S2-2407207 LS To: SA2 |
Beijing Xiaomi Mobile Software | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-243257 | Update to solution #7 in TR 33.743 |
pCR revised to S3-243569 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243258 | Update to solution #8 in TR 33.743 |
pCR revised to S3-243563 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243259 | Add the evaluation of solution #7 in TR 33.743 |
pCR revised to S3-243710 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243260 | Add the evaluation of solution #8 in TR 33.743 |
pCR revised to S3-243564 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243261 | New solution on disabling operation procedure | pCR | Beijing Xiaomi Mobile Software | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243262 | New solution on security protection method for Ambient IoT services | pCR | Beijing Xiaomi Mobile Software | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243263 | New solution on authorization of intermediate node for Ambient IoT services | pCR | Beijing Xiaomi Mobile Software | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243264 | [Draft] Reply LS on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 source LS: S2-2407236 LS To: SA2 |
Xiaomi Technology | FS_UIA_ARC | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-243265 | Completing the Privacy Check of n UEs for Service Exposure to Client UE |
CR revised to S3-243684 |
Xiaomi, OPPO, Phillips | 33.533 18.3.0 CR#76 catF | Ranging_SL_Sec | Rel-18 |
S3-117 AI: 4.1.12 |
revised | [WTS] [JSN] |
| S3-243266 | LTM: New Solution for Protecting NCC in MAC CE using AS Security Context | other | Xiaomi Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243267 | LTM: New Solution for Protecting NCC in MAC CE using C-RNTI | other | Xiaomi Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243268 | LTM: Solution on Rekeying Sychronization at Handover Completion |
other revised to S3-243531 |
Xiaomi Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-243269 | 33.701: Addition to Overall Summary | pCR | Xiaomi Technology | 33.701 1.0.0 | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 5.6 |
noted | [WTS] [JSN] |
| S3-243270 | 33.700-32: Update to Solution 8 |
pCR revised to S3-243451 |
Xiaomi Technology | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243271 | 33.700-32: Update to Solution 22 |
pCR revised to S3-243452 |
Xiaomi Technology | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243272 | 33.700-32: New Solution on User Authentication with Credential Derived by UIMF |
pCR revised to S3-243462 |
Xiaomi Technology | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243273 | 33.700-32: New Solution on Privacy Protection for UIP Exposure |
pCR revised to S3-243463 |
Xiaomi Technology | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243274 | 33.721: Resolve Editor’s Notes in Key Issue 2 |
pCR revised to S3-243715 |
Xiaomi Technology | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-243275 | 33.721: New Solution for Key Issue 2 | pCR | Xiaomi Technology | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-243276 | 33.721: Key Issue on Authentication and Authorization of Avatar |
pCR revised to S3-243651 |
Xiaomi Technology | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-243277 | New WID on 5G Security Assurance Specification (SCAS) for the Container-based Products | WID new | Ericsson | Rel-19 |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-243278 | Update KI#4 for Command | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243279 | Reply-LS on LS on Resource content filters |
LS out LS is reply to S3-241733 LS To: CT4 |
Nokia |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |||
| S3-243280 | New KI on AIoT Authentication of Command Use Case | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243281 | Test Case for Intra-VNF Communication Interface | CR | Ericsson | 33.527 18.3.0 CR#7 catB | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-243282 | Solution for Intermediate UE Authorization | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243283 | Solution for AIoT Lightweight Authentication Based on 5G-AKA | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243284 | Assumption on AIoT Device | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243285 | Discussion on SS7/MAP interface at SMSF to define MAP filtering and protection requirements for Security Assurance Specifications for SMSF | discussion | IIT Bombay | Rel-19 |
S3-117 AI: 4.4 |
noted | [WTS] [JSN] | ||
| S3-243286 | KI on authentication related to inventory use case | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243287 | Solution on Disabling Enabling | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243288 | Solution on temporary ID based AIoT device privacy protection | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243289 | Protection requirements on Map interface for Security Assurance Specifications for SMSF |
pCR revised to S3-243420 |
IIT Bombay | 33.529 0.5.0 | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
revised | [WTS] [JSN] |
| S3-243290 | Solution on AIoT device ID privacy protection using anonymous key | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243291 | Proposed conclusion for KI 1 for user authentication | pCR | NTT DOCOMO INC., Ericsson | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
noted | [WTS] [JSN] |
| S3-243292 | Filtering requirements on Map interface for Security Assurance Specifications for SMSF |
pCR revised to S3-243685 |
IIT Bombay | 33.529 0.5.0 | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
revised | [WTS] [JSN] |
| S3-243293 | Discussion about the HONTRA related responses from the AMF | discussion | Ericsson | Rel-18 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-243294 | Reply LS on clarification on home network triggered re-authentication |
LS out LS is reply to S3-243391 LS To: CT4 revised to S3-243412 |
Ericsson | Rel-18 |
S3-117 AI: 3 |
revised | [WTS] [JSN] | ||
| S3-243295 | Clarifications for HONTRA procedure with respect to failure cases | CR | Ericsson | 33.501 18.6.0 CR#2044 catF | HN_Auth | Rel-18 |
S3-117 AI: 3 |
not pursued | [WTS] [JSN] |
| S3-243296 | Remove Editor's Note from KI#1: Third party specific user identities | pCR | Ericsson | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243297 | Conclusion for KI#1: Third party specific user identities | pCR | Ericsson | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-243298 | New solution for KI#3: IMS DC capability exposure security based on existing specification |
pCR revised to S3-243626 |
Ericsson | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-243299 | Reply LS on Newly published data channel GSMA PRD TS.66 |
LS out LS is reply to S3-242758 LS To: SA revised to S3-243411 |
Ericsson |
S3-117 AI: 3 |
revised | [WTS] [JSN] | |||
| S3-243300 | Resolve ENs in Solution #2: Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revised to S3-243706 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243301 | Resolve EN in Solution #3: Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revised to S3-243572 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243302 | Resolve EN in Solution#4: Security of multi-hop UE-to-Network Relay communication |
pCR revised to S3-243565 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243303 | Evaluation of Solution #2: Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revised to S3-243707 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243304 | Evaluation of Solution #3: Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revised to S3-243708 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243305 | Evaluation of Solution#4: Security of multi-hop UE-to-Network Relay communication |
pCR revised to S3-243566 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243306 | Resolve EN in KI#1: Security for multi-hop UE-to-Network Relay | pCR | Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-243307 | LS Reply to LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-242721 LS To: SA2 |
Ericsson | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |
| S3-243308 | Update and evaluation for Solution #5 "Security log events collection for evaluation and monitoring" |
pCR revised to S3-243501 |
Ericsson | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243309 | New Solution to Key Issue #1: Using security log events, counters and protocol signaling monitoring |
pCR revised to S3-243504 |
Ericsson | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243310 | New Solution to Key Issue #2: Policy enforcement using NRF configuration and short access token lifetime |
pCR revised to S3-243615 |
Ericsson | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243311 | Security Log Management specifications in O-RAN Alliance | discussion | Ericsson | Rel-19 |
S3-117 AI: 5.1 |
noted | [WTS] [JSN] | ||
| S3-243312 | New clause on protection of Map interface in annexure to Security Assurance Specification (SCAS) threats specific to SMSF | draftCR | IIT Bombay | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
approved | [WTS] [JSN] | |
| S3-243313 | Addressing ENs in solution #12 in TR 33.700-32 |
pCR revised to S3-243459 |
CableLabs | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243314 | New clause on Map-based SS7 interface filtering in annexure to Security Assurance Specification (SCAS) threats specific to SMSF | draftCR | IIT Bombay | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
approved | [WTS] [JSN] | |
| S3-243315 | Minor additions/modifications for draft TS 33.529 | pCR | IIT Bombay | 33.529 0.5.0 | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
approved | [WTS] [JSN] |
| S3-243316 | Discussion on protecting header information in UPU | discussion | Qualcomm Incorporated, Vivo, Oppo |
S3-117 AI: 4.1.15 |
noted | [WTS] [JSN] | |||
| S3-243317 | Protection of UPU header | draftCR | Qualcomm Incorporated, Vivo, Oppo | TEI19, 5GS_Ph1-SEC | Rel-19 |
S3-117 AI: 4.1.15 |
noted | [WTS] [JSN] | |
| S3-243318 | Addition to solution #3 |
pCR revised to S3-243694 |
Qualcomm Incorporated | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-243319 | Security of Satellite Store & Forward Solutions | discussion | Qualcomm Incorporated |
S3-117 AI: 5.7 |
noted | [WTS] [JSN] | |||
| S3-243320 | Reply LS on FS_5GSAT_Ph3_ARCH conclusions |
LS out LS is reply to S3-242725 LS To: SA2 |
Qualcomm Incorporated |
S3-117 AI: 5.7 |
merged | [WTS] [JSN] | |||
| S3-243321 | Discussion on the User Identities LS from SA2 | discussion | Qualcomm Incorporated |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243322 | Reply LS on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 LS To: SA2 |
Qualcomm Incorporated |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |||
| S3-243323 | Updating the conclusion to KI#1 and KI#3 | pCR | Qualcomm Incorporated | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
merged | [WTS] [JSN] |
| S3-243324 | Proposed conclusion for KI#4 |
pCR revised to S3-243646 |
Qualcomm Incorporated | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
revised | [WTS] [JSN] |
| S3-243325 | Update of WID on Security for mobility over non-3GPP access to avoid full primary authentication |
WID revised revision of SP-240653 |
Qualcomm Incorporated | Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 6 |
agreed | [WTS] [JSN] | |
| S3-243326 | Discussion on normative solutions for KI#1 and KI#3 | discussion | Qualcomm Incorporated |
S3-117 AI: 4.13 |
noted | [WTS] [JSN] | |||
| S3-243327 | Mobility under a TNGF |
other revised to S3-243641 |
Qualcomm Incorporated |
S3-117 AI: 4.13 |
revised | [WTS] [JSN] | |||
| S3-243328 | Mobility under a TWIF | other | Qualcomm Incorporated |
S3-117 AI: 4.13 |
noted | [WTS] [JSN] | |||
| S3-243329 | Informative text of using FT for NSWO |
other revised to S3-243643 |
Qualcomm Incorporated |
S3-117 AI: 4.13 |
revised | [WTS] [JSN] | |||
| S3-243330 | Fixing the RRC/PDCP anchor for inter-gNB LTM cell switches |
other revised to S3-243532 |
Qualcomm Incorporated |
S3-117 AI: 4.12 |
revised | [WTS] [JSN] | |||
| S3-243331 | reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-242721 LS To: SA2 |
Qualcomm Incorporated |
S3-117 AI: 3 |
merged | [WTS] [JSN] | |||
| S3-243332 | Updates on solution #9 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243333 | Addressing ENs in solution #9 |
pCR revised to S3-243570 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243334 | Adding an evaluation to solution #9 |
pCR revised to S3-243571 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243335 | Updates to solution #10 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243336 | Addressing ENs in solution #10 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243337 | Adding an evaluation to solution #10 |
pCR revised to S3-243709 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243338 | Updates on solution #14 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243339 | Add an evaluation to solution #15 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243340 | A new solution for privacy protection of AIoT device identifier | pCR | Qualcomm Incorporated | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243341 | A new solution for end-to-end security protection of command | pCR | Qualcomm Incorporated | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243342 | Threat update for KI1 for MiBida | pCR | NTT DOCOMO INC.. | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] |
| S3-243343 | Solution for IP address verification using access token |
pCR revised to S3-243635 |
Samsung | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-243344 | Solution#10 update - Addresing EN |
pCR revised to S3-243453 |
Philips International B.V. | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
revised | [WTS] [JSN] |
| S3-243345 | New solution - Ambient IoT ID privacy | pCR | Philips International B.V. | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243346 | Solution#1 update - Addressing ENs | pCR | Philips International B.V. | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243347 | Update to new SID on security aspects for Multi-Access (DualSteer + ATSSS Ph-4) | pCR | Philips International B.V. | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
noted | [WTS] [JSN] |
| S3-243348 | Evaluation of Solution#13 | pCR | Philips International B.V. | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-243349 | Evaluation of Solution#22 | pCR | Philips International B.V. | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-243350 | Emergency Service over UE-to-Network relay - PEI status check | CR | Philips International B.V. | 33.503 18.3.0 CR#206 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-117 AI: 4.1.3 |
withdrawn | [WTS] [JSN] |
| S3-243351 | New solution for protecting AIoT ID | pCR | Samsung | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243352 | Resolution of EN concerning privacy. |
pCR revised to S3-243607 |
Nokia | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-243353 | Update of mapping table | pCR | Nokia | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
merged | [WTS] [JSN] |
| S3-243354 | KI Authentication and identity of type 1 and 2 devices | pCR | Nokia | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-243355 | Update to KI#4 | pCR | Nokia | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243356 | Resolution of EN concerning message inspection, filtering and topology hiding – solution 13. | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243357 | Resolution of editors note concerning message inspection/filtering and topology hiding – solution 14. |
pCR revised to S3-243478 |
Nokia, Nokia Shanghai Bell | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243358 | Evaluation of solution 13 | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243359 | Evaluation of solution 14 | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243360 | Conclusion to KI#1 | pCR | Nokia, Nokia Shanghai Bell, Johns Hopkins University APL | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243361 | Conclusion to KI#2 | pCR | Nokia, Nokia Shanghai Bell, Johns Hopkins University APL | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243362 | Removal of ENs to solution 14 in MiBiDA | pCR | NTT DOCOMO INC.. | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
merged | [WTS] [JSN] |
| S3-243363 | Security for Map-based SS7 interface | CR | IIT Bombay | 33.501 18.6.0 CR#2045 catF | SCAS_5G_SMSF | Rel-18 |
S3-117 AI: 4.4 |
not pursued | [WTS] [JSN] |
| S3-243364 | New UE configuration based solution for MibidA |
pCR revised to S3-243510 |
NTT DOCOMO INC.. | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
revised | [WTS] [JSN] |
| S3-243365 | KI#1, Solution #3 Updates: Data Collection |
pCR revision of S3-242838 revised to S3-243498 |
OTD_US, MITRE | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-243366 | LS on obtaining user consent for the exposure of User Sensitive Information | LS in | S6a240323 | Rel-19 |
S3-117 AI: 3 |
postponed | [WTS] [JSN] | ||
| S3-243367 | Add evaluation for sol#2 |
pCR revised to S3-243577 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243368 | Add evaluation for sol#7 |
pCR revised to S3-243594 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243369 | Add evaluation for sol#8 |
pCR revised to S3-243595 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243370 | Resolve ENs for sol#7 |
pCR revised to S3-243582 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243371 | Resolve ENs for sol#8 |
pCR revised to S3-243583 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-243372 | Conclusions for KI#1 and KI#2 | pCR | Xiaomi Communications | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
merged | [WTS] [JSN] |
| S3-243373 | add high-level architectures for TR 33.700-22 |
pCR revised to S3-243716 |
Xiaomi Communications | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243374 | add scope for TR 33.700-22 | pCR | Xiaomi Communications | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-243375 | draft_TR 33.700-22 skeleton FS_CAPIF_Ph3-sec |
draft TR revised to S3-243637 |
Xiaomi Communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
revised | [WTS] [JSN] | |
| S3-243376 | New KI_Key issue on API invoker on one UE accessing resources owned by another UE |
pCR revised to S3-243640 |
Xiaomi Communications | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243377 | New KI_Key issue on security of resource owner consent management | pCR | Xiaomi Communications | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-243378 | Add conclusion to KI#2 | pCR | Xiaomi Communications | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-243379 | Update sol#8 for wrong NF type handling |
pCR revised to S3-243475 |
Xiaomi Communications | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243380 | Update sol#10 for message handling |
pCR revised to S3-243477 |
Xiaomi Communications | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-243381 | Update solution #13 in TR 33.700-32 | pCR | China Telecomunication Corp. | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
noted | [WTS] [JSN] |
| S3-243382 | Update the Key issue #3 in TR 33.700-32 | pCR | China Telecomunication Corp. | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
noted | [WTS] [JSN] |
| S3-243383 | Emergency Service over UE-to-Network relay - PEI status check | CR | Philips International B.V | 33.503 18.3.0 CR#207 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-117 AI: 4.1.3 |
not pursued | [WTS] [JSN] |
| S3-243384 | Additional requirements for Key issue on CAPIF interconnection security | pCR | Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-243385 | 33.701: Update to Solution 4 | pCR | Xiaomi EV Technology | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] |
| S3-243386 | Solve EN for sol#1&12 of TR 33.757 regarding SA3-LI |
pCR revision of S3-243242 |
China Mobile | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243387 | Solution for Authentication, Authorization of AIoT devices with USIM on AIoT AS Layer | pCR | Lenovo | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243388 | Solution for Authentication, Authorization of AIoT devices with USIM on AIoT Layer | pCR | Lenovo | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243389 | Solution for Authentication, Authorization and ID privacy of AIoT devices without USIM | pCR | Lenovo | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-243390 | LS reply to 3GPP Reply-LS on PQC Migration | LS in | GSMA |
S3-117 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-243391 | LS on clarification on home network triggered re-authentication |
LS in LS reply in S3-243412, S3-243412 |
C4-235577 |
S3-117 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-243392 | Draft TR 33.784 | draft TR | China Mobile | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] | |
| S3-243393 | Newly published data channel GSMA PRD TS.66 | LS in | GSMA |
S3-117 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-243394 | Version 2.0 of 256-bit AICI. | LS in | ETSI SAGE |
S3-117 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-243395 | Evaluation to Solution #1 |
pCR revised to S3-243657 |
33.701 0.3.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
revised | [WTS] [JSN] | |
| S3-243396 | Evaluation to Solution #4 | pCR | 33.701 0.3.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] | |
| S3-243397 | Proposed solution for certificate enrolment |
pCR revised to S3-243486 |
Google, JHU APL | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-243398 | Proposed solution for Secure Transport of Messages |
pCR revised to S3-243662 |
33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
revised | [WTS] [JSN] | |
| S3-243399 | Rejecting security mode by the UE | discussion |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||||
| S3-243400 | New mini WID on rejecting insecure security algorithms in NAS SMC procedure | WID new |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||||
| S3-243401 | Rejecting insecure security algorithms in NAS SMC procedure | discussion |
S3-117 AI: 6 |
noted | [WTS] [JSN] | ||||
| S3-243402 | LS on security visibility for user or application |
LS out LS To: GSMA Device Security Group (DSG), GSMA DG |
S3-117 AI: 3 |
noted | [WTS] [JSN] | ||||
| S3-243403 | Remove unnecessary complexity from UDM test case | draftCR | BSI | SCAS_5G_Maint | Rel-18 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243404 | Add an OAuth2.0 test case to check for the absence of an access token | draftCR | BSI | SCAS_5G_Maint | Rel-18 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243405 | CR resubmission - the content of AN-parameters |
CR revision of S3-243097 |
Huawei, HiSilicon | 33.501 18.6.0 CR#20381 catF | eNPN_Ph2 | Rel-18 |
S3-117 AI: 4.1.9 |
agreed | [WTS] [JSN] |
| S3-243406 | Detail agenda planning for SA3#117 |
other revision of S3-242703 |
SA WG3 Chair |
S3-117 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-243407 | Reply to: LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-242727 LS To: SA4 |
China Mobile |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243408 | Reply LS to SA6 on Clarification related to Internal 5G Core information expose to trusted AF |
LS out LS is reply to S3-242730 LS To: SA6 revision of S3-242898 |
Huawei, HiSilicon | Rel-18 |
S3-117 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-243409 | Discussion for LS S2-2407236 on User Identities | discussion | Interdigital |
S3-117 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-243410 | Reply LS on LI considerations for TR 33.757 |
LS out LS is reply to S3-242741 LS To: SA3-LI revision of S3-243240 |
China Mobile | LI19 | Rel-19 |
S3-117 AI: 3 |
approved | [WTS] [JSN] | |
| S3-243411 | Reply LS on Newly published data channel GSMA PRD TS.66 |
LS out LS is reply to S3-242758 LS To: SA revision of S3-243299 |
Ericsson |
S3-117 AI: 3 |
approved | [WTS] [JSN] | |||
| S3-243412 | Reply LS on clarification on home network triggered re-authentication |
LS out LS is reply to S3-243391 LS To: CT4 LS reply in C4-244141, C4-244465, C4-244466, C4-244496 revision of S3-243294 |
Ericsson | Rel-18 |
S3-117 AI: 3 |
approved | [WTS] [JSN] | ||
| S3-243413 | update to AKMA service disabling |
CR revision of S3-243053 |
Huawei, HiSilicon | 33.535 18.4.0 CR#2191 catF | AKMA_Ph2 | Rel-18 |
S3-117 AI: 4.1.5 |
agreed | [WTS] [JSN] |
| S3-243414 | Correct the Federal Learning procedure |
CR revision of S3-243064 |
Huawei, HiSilicon | 33.501 18.6.0 CR#20361 catF | eNA_Ph3_SEC | Rel-18 |
S3-117 AI: 4.1.13 |
agreed | [WTS] [JSN] |
| S3-243415 | MPQUIC TLS Annex |
CR revision of S3-242964 |
Intel, Nokia, Charter Communications, | 33.501 18.6.0 CR#20351 catB | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243416 | Editorials on updates to the SBA certificate profile | CR | Nokia, Ericsson | 33.310 19.1.0 CR#2041 catA | ACM_SBA | Rel-19 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243417 | Replacing DCMF with MF |
CR revision of S3-243048 |
Huawei, HiSilicon | 33.328 18.1.0 CR#791 catF | NG_RTC_SEC | Rel-18 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243418 | SCPAC: Secondary Node key update for SCPAC |
CR revision of S3-243185 |
Ericsson | 33.501 18.6.0 CR#20431 catF | TEI18 | Rel-18 |
S3-117 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-243419 | Add specific UDR SCAS test cases for TS 33.530 |
pCR revision of S3-242759 revised to S3-243869 |
BSI (DE) | 33.530 0.1.0 | SCAS_5G_UDR | Rel-19 |
S3-117 AI: 4.2 |
noted | [WTS] [JSN] |
| S3-243420 | Protection requirements on Map interface for Security Assurance Specifications for SMSF |
pCR revision of S3-243289 |
IIT Bombay | 33.529 0.5.0 | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
noted | [WTS] [JSN] |
| S3-243421 | Draft TS 33.529 | draft TS | IIT Bombay | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
approved | [WTS] [JSN] | |
| S3-243422 | Content of TS 35.234 |
pCR revision of S3-242979 |
THALES | 35.234 0.1.0 | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
approved | [WTS] [JSN] |
| S3-243423 | Content of TS 35.235 |
pCR revision of S3-242980 |
THALES | 35.235 0.1.0 | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
approved | [WTS] [JSN] |
| S3-243424 | Content of TS 35.236 |
pCR revision of S3-242982 |
THALES | 35.236 0.1.0 | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
approved | [WTS] [JSN] |
| S3-243425 | Draft TS 35.234 | draft TS | Thales | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-243426 | Draft TS 35.235 | draft TS | Thales | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-243427 | Draft TS 35.236 | draft TS | Thales | Milenage_256 | Rel-19 |
S3-117 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-243428 | Living document for CryptoSP: draftCR to TS 33.501, Updates to cryptographic profiles |
draftCR revision of S3-242781 |
Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243429 | Living document for CryptoSP: draftCR to TS 33.210, Updates to cryprographic profiles |
draftCR revision of S3-242782 |
Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243430 | Living document for CryptoSP: draftCR to TS 33.310, Updates to cryptographic profiles |
draftCR revision of S3-242783 |
Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243431 | Living document for CryptoSP: draftCR to TS 33.203, Updates to cryptographic profiles |
draftCR revision of S3-242784 |
Ericsson | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243432 | Living document of security aspects of MSGin5G service Ph3 |
draftCR revision of S3-243236 |
China Mobile | 5GMARCH_SEC_Ph3 | Rel-19 |
S3-117 AI: 4.9 |
approved | [WTS] [JSN] | |
| S3-243433 | CR for living document TITLE TO BE PROVIDED BY CMCC | CR | China Mobile | 33.501 18.6.0 CR#2047 catB | 5GMARCH_SEC_Ph3 | Rel-19 |
S3-117 AI: 4.9 |
agreed | [WTS] [JSN] |
| S3-243434 | Living document for Rel-19 SCAS TS 33.117 | draftCR | Huawei | SCAS_5G_Maint | Rel-18 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243435 | Test Case on No Default Content |
other revision of S3-242770 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |||
| S3-243436 | Test Case on No Directory Listings |
other revision of S3-242771 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |||
| S3-243437 | Test Case on No Web Server Error Pages Info |
other revision of S3-242773 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |||
| S3-243438 | Draft CR TR 33.926 SCAS_5G_Maint | draftCR | Huawei | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243439 | Draft CR TS 33.511 | draftCR | Huawei | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |
| S3-243440 | TR 33.700-32 update solution #2 |
pCR revision of S3-242850 |
InterDigital Canada | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243441 | TR 33.700-32 update solution #3 |
pCR revision of S3-242851 |
InterDigital Canada | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243442 | Sol#5 update to address ENs |
pCR revision of S3-242884 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243443 | Sol#5 evaluation |
pCR revision of S3-242885 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243444 | add evaluation to Solution#4 |
pCR revision of S3-242928 |
ZTE Corporation | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243445 | Draft TR 33.700-32 | draft TR | Interdigital | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] | |
| S3-243446 | Enhancing solution 15 |
pCR revision of S3-242940 |
Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243447 | Evaluation to solution 6 to address KI#1 |
pCR revision of S3-243038 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243448 | Update of Solution #9: Clarification and removal of Editor's Notes |
pCR revision of S3-243142 |
Ericsson | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243449 | Update of Solution #9: Resolution of Editor's Note on protection of user ID |
pCR revision of S3-243143 |
Ericsson | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243450 | Evaluation for solution#16 |
pCR revision of S3-243210 |
Samsung | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243451 | 33.700-32: Update to Solution 8 |
pCR revision of S3-243270 |
Xiaomi Technology | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243452 | 33.700-32: Update to Solution 22 |
pCR revision of S3-243271 |
Xiaomi Technology | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243453 | Solution#10 update - Addresing EN |
pCR revision of S3-243344 |
Philips International B.V. | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243454 | Sol#19 update to address ENs |
pCR revision of S3-242886 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243455 | Enhancing solution 17 |
pCR revision of S3-242943 |
Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243456 | Add evaluation to solution 20 |
pCR revision of S3-243116 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243457 | Updates to Solution #14 |
pCR revision of S3-242751 |
Lenovo | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243458 | Sol#21 evaluation |
pCR revision of S3-242889 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243459 | Addressing ENs in solution #12 in TR 33.700-32 |
pCR revision of S3-243313 |
CableLabs | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243460 | User ID privacy protection based on EAP-TLS protocol using pseudonym mechanism |
pCR revision of S3-243036 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243461 | New Solution on user authentication with user certificate of KI1 |
pCR revision of S3-243129 |
Huawei, HiSilicon | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243462 | 33.700-32: New Solution on User Authentication with Credential Derived by UIMF |
pCR revision of S3-243272 |
Xiaomi Technology | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243463 | 33.700-32: New Solution on Privacy Protection for UIP Exposure |
pCR revision of S3-243273 |
Xiaomi Technology | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243464 | KI2 update |
pCR revision of S3-243050 |
Nokia | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
noted | [WTS] [JSN] |
| S3-243465 | Conclusion for KI#3 in TR 33.700-32 |
pCR revision of S3-242856 |
CableLabs, Charter Communications | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243466 | Updates to Solution #1 |
pCR revision of S3-242752 |
Lenovo | 33.700-32 0.2.0 | FS_UIA_Sec | Rel-19 |
S3-117 AI: 5. |
approved | [WTS] [JSN] |
| S3-243467 | Solve EN for Sol#1&5 of TR 33.757 |
pCR revision of S3-243241 |
China Mobile | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243468 | Draft TR 33.757 | draft TR | China Telecom | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] | |
| S3-243469 | Evaluation for KI#1 and KI#2 on N4/SBA Security for solution 3 |
pCR revision of S3-243082 |
Huawei, HiSilicon | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243470 | Resolution of EN concerning message inspection, filtering and topology hiding – solution 13. | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
withdrawn | [WTS] [JSN] |
| S3-243471 | Conclusion to KI#1 |
pCR revision of S3-243018 |
China Telecomunication Corp.,ZTE, Huawei, HiSilicon, China Mobile | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243472 | Addressing the EN and evaluation of Solution#4 | pCR | Huawei, HiSilicon | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
withdrawn | [WTS] [JSN] |
| S3-243473 | Evaluation to solution#6 |
pCR revision of S3-243013 |
China Telecomunication Corp. | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243474 | Evaluation to solution#7 |
pCR revision of S3-243017 |
China Telecomunication Corp. | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243475 | Update sol#8 for wrong NF type handling |
pCR revision of S3-243379 |
Xiaomi Communications | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243476 | Update to Solution#9 |
pCR revision of S3-243201 |
Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243477 | Update sol#10 for message handling |
pCR revision of S3-243380 |
Xiaomi Communications | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243478 | Resolution of editors note concerning message inspection/filtering and topology hiding – solution 14. |
pCR revision of S3-243357 |
Nokia, Nokia Shanghai Bell | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243479 | Conclusion to KI#2 |
pCR revision of S3-243020 |
China Telecomunication Corp., ZTE, Huawei, HiSilicon, China Mobile | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243480 | Updates to Solution#11 |
pCR revision of S3-242750 |
Lenovo | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243481 | Update the Sol#15 |
pCR revision of S3-242911 |
ZTE Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243482 | Update the Sol#16 |
pCR revision of S3-242912 |
ZTE Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243483 | Update to solution#17 |
pCR revision of S3-243202 |
Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243484 | Conclusion to KI#3 |
pCR revision of S3-242909 |
ZTE Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243485 | Solution to enforce additional policy checks for NF Consumer in PNI-NPN |
pCR revision of S3-243203 |
Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-243486 | Proposed solution for certificate enrolment |
pCR revision of S3-243397 |
Google, JHU APL | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-243487 | Solution on certificate revocation |
pCR revision of S3-242854 |
Johns Hopkins University APL, Cisco Systems, MITRE-FFRDC, US National Security Agency | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-243488 | update to Sol#1 |
pCR revision of S3-242892 |
Huawei, HiSilicon | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-243489 | update to Sol#3 |
pCR revision of S3-242893 |
Huawei, HiSilicon | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
noted | [WTS] [JSN] |
| S3-243490 | overall evaluation for KI#1 |
pCR revision of S3-242894 |
Huawei, HiSilicon | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
noted | [WTS] [JSN] |
| S3-243491 | overall evaluation for KI#3 |
pCR revision of S3-242895 |
Huawei, HiSilicon | 33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
noted | [WTS] [JSN] |
| S3-243492 | Updates to the assumption clause |
pCR revision of S3-243121 |
Huawei, HiSilicon | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-243493 | New Use case proposal for data exposure related to attacks on network slices |
pCR revision of S3-242815 |
IRT, Nokia, Nokia Shanghai Bell | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243494 | Evaluation to Use case 4 |
pCR revision of S3-243087 |
Huawei, HiSilicon | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243495 | Addressing EN in Use Case 5 |
pCR revision of S3-242899 |
U.S. National Security Agency, Johns Hopkins University APL, OTD_US, MITRE-FFRDC | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243496 | Updates to Solution #2 |
pCR revision of S3-242748 |
Lenovo, Johns Hopkins University APL, US National Security Agency | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243497 | Updates to Solution#1 |
pCR revision of S3-242749 |
Lenovo, Johns Hopkins University APL, US National Security Agency | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243498 | KI#1, Solution #3 Updates: Data Collection |
pCR revision of S3-243365 |
OTD_US, MITRE | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243499 | EN removal for solution #4 |
pCR revision of S3-243007 |
Nokia | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243500 | Evaluation for solution #4 |
pCR revision of S3-243008 |
Nokia | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243501 | Update and evaluation for Solution #5 "Security log events collection for evaluation and monitoring" |
pCR revision of S3-243308 |
Ericsson | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243502 | New solution for KI #1 Data Collection using DCCF |
pCR revision of S3-242869 |
MITRE-FFRDC | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243503 | New solution for data collection related to API security risks |
pCR revision of S3-243001 |
Nokia | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243504 | New Solution to Key Issue #1: Using security log events, counters and protocol signaling monitoring |
pCR revision of S3-243309 |
Ericsson | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243505 | Initial Conclusion to KI#1 |
pCR revision of S3-242746 |
Lenovo, US National Security Agency, MITRE-FFRDC, Nokia, Nokia Shanghai Bell, Ericsson, NTIA, Deutsche Telekom, T-Mobile US, BT, Charter Communications, Cablelabs, Peraton Labs, Intel, IRT Saint Exupery, Johns Hopkins University APL, Samsung, CISA ECD | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243506 | Threat update for KI1 for MiBida | pCR | NTT DOCOMO INC.. | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
withdrawn | [WTS] [JSN] |
| S3-243507 | MiBiDA - Update solution#10 |
pCR revision of S3-242994 |
Apple | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] |
| S3-243508 | Solution #14 |
pCR revision of S3-242965 |
THALES | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] |
| S3-243509 | New Solution Mitigation of Roaming Attack |
pCR revision of S3-242801 |
vivo | 33.701 0.3.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] |
| S3-243510 | New UE configuration based solution for MibidA |
pCR revision of S3-243364 |
NTT DOCOMO INC.. | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] |
| S3-243511 | Conclusion proposal |
pCR revision of S3-243122 revised to S3-243691 |
Huawei, HiSilicon | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
revised | [WTS] [JSN] |
| S3-243512 | Evaluation to solution#2 in TR 33.745 |
pCR revision of S3-242987 |
China Telecomunication Corp. | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243513 | update to Solution#1 ownership security |
pCR revision of S3-243004 |
ZTE | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243514 | Updates for solution #4 |
pCR revision of S3-243016 |
Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243515 | New Solution to KI#7: Verify and authorise direct connections between 5G NR Femtos |
pCR revision of S3-242794 |
China Mobile Com. Corporation | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243516 | New Solution for Security of 5G NR Femto Ownership |
pCR revision of S3-243011 |
Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243517 | New Solution for Femto Owner one time registration with operator network |
pCR revision of S3-243012 |
Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243518 | Alignment of terminology of 5G femto |
LS out LS To: SA2 |
Nokia |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] | |||
| S3-243519 | New Solution for Support of 5G Femto location security |
pCR revision of S3-243014 |
Nokia | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243520 | Security solution for backhaul link between 5G NR Femto and 5GC |
pCR revision of S3-243110 |
Huawei, HiSilicon | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-243521 | New KI on Requirements for traffic monitoring and anomaly behavior analysis of 5G Femto |
pCR revision of S3-242796 |
China Mobile Com. Corporation | 33.745 0.2.0 | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
noted | [WTS] [JSN] |
| S3-243522 | Key issue for security aspects of inter-CU LTM |
other revision of S3-243195 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-243523 | Key issue for authenticity verification of Cell Switch Command |
other revision of S3-243196 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-243524 | 1-Hop Forward Security Solution for LTM |
other revision of S3-242798 |
vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-243525 | Solution for Inter-CU LTM |
other revision of S3-242818 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |||
| S3-243526 | NCC synchronization solution for LTM |
other revision of S3-242908 |
ZTE Corporation | Rel-19 |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-243527 | LTM - content on living CR - Candidate solution#1 |
other revision of S3-242997 |
Apple |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |||
| S3-243528 | LTM - content on living CR - Candidate solution#2 |
other revision of S3-242998 |
Apple |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |||
| S3-243529 | New solution for LTM security handling |
other revision of S3-243158 |
LG Electronics | Rel-19 |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-243530 | Solution for security aspects of inter-CU LTM |
other revision of S3-243197 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-243531 | LTM: Solution on Rekeying Sychronization at Handover Completion |
other revision of S3-243268 |
Xiaomi Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-243532 | Fixing the RRC/PDCP anchor for inter-gNB LTM cell switches |
other revision of S3-243330 |
Qualcomm Incorporated |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |||
| S3-243533 | LS on reply to LS on FS_5GSAT_Ph3_ARCH conclusions |
LS out LS is reply to S3-242725 LS To: SA2 LS reply in S2-2410084, S2-2410144 revision of S3-242764 |
Nokia | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] | ||
| S3-243534 | Update the KI#1 |
pCR revision of S3-242919 |
ZTE Corporation | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243535 | An Update for Solution #21: Remediation of unauthenticated (D)DOS in S&F |
pCR revision of S3-242846 |
InterDigital Communications | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243536 | An Update for the Evaluation of Solution #21 |
pCR revision of S3-242847 |
InterDigital Communications | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243537 | Evaluation for Solution #13 |
pCR revision of S3-242920 |
ZTE Corporation | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243538 | Solution 6 update with evaluation |
pCR revision of S3-243002 |
Nokia | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243539 | Remove ENs and update evaluation in Solution #12 |
pCR revision of S3-242985 |
OPPO | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243540 | Solution 22 updates with evaluation |
pCR revision of S3-243005 |
Nokia | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243541 | Evaluation update on solution 18 |
pCR revision of S3-243058 |
Huawei, HiSilicon | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243542 | Evaluation of solution#7 |
pCR revision of S3-243218 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243543 | Resolving EN of solution#8 |
pCR revision of S3-243219 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243544 | Evaluation of solution#8 |
pCR revision of S3-243220 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243545 | Update solution 5 |
pCR revision of S3-243234 |
China Mobile, CAICT | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243546 | Resolving EN of solution#25 |
pCR revision of S3-243222 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243547 | Evaluation of solution#25 |
pCR revision of S3-243223 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243548 | Update to solution #17 in TR 33.700-29 |
pCR revision of S3-243255 |
Beijing Xiaomi Mobile Software | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243549 | Update to solution#24 |
pCR revision of S3-243221 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243550 | Update to solution#26 |
pCR revision of S3-243224 |
Samsung | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243551 | pCR to TR33.700-29 New solution on anti DoS attacks and privacy protection for S&F operations |
pCR revision of S3-242865 |
CATT | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243552 | Security protection based on AKA procedure in S&F operation with a full CN onboard the satellite |
pCR revision of S3-243033 |
Huawei, HiSilicon | 33.700-29 0.3.0 | SAT | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243553 | New solution of Authentication and authorization in S&F based on onboard EPC |
pCR revision of S3-243233 |
China Mobile, CAICT | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243554 | Interim GUTI privacy protection based on pseudonym UE IDs |
pCR revision of S3-243034 |
Huawei, HiSilicon | 33.700-29 0.3.0 | SAT | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243555 | Draft TR 33.700-29 | draft TR | CATT | SAT | Rel-19 |
S3-117 AI: 5.7 |
reserved | [WTS] [JSN] | |
| S3-243556 | Draft TR 33.745 | draft TR | ZTE | FS_5G_Femto_Sec | Rel-19 |
S3-117 AI: 5.17 |
approved | [WTS] [JSN] | |
| S3-243557 | Draft TR 33.701 | draft TR | Huawei | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] | |
| S3-243558 | LS Replay on User Identities and Authentication Architecture |
LS out LS is reply to S3-242724 source LS: S2-2407236 LS To: SA2 revision of S3-242852 |
InterDigital Canada | FS_UIA_ARC | Rel-19 |
S3-117 AI: 3 |
approved | [WTS] [JSN] | |
| S3-243559 | Reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-242721 source LS: S2-2407207 LS To: SA2 |
Huawei, HiSilicon | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 3 |
withdrawn | [WTS] [JSN] | |
| S3-243560 | Resolve ENs in solution#5 of TR 33.743 |
pCR revision of S3-243090 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243561 | Evaluates to solution#5 of TR 33.743 |
pCR revision of S3-243092 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243562 | update solution #6 in TR 33.743 |
pCR revision of S3-243183 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243563 | Update to solution #8 in TR 33.743 |
pCR revision of S3-243258 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243564 | Add the evaluation of solution #8 in TR 33.743 |
pCR revision of S3-243260 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243565 | Resolve EN in Solution#4: Security of multi-hop UE-to-Network Relay communication |
pCR revision of S3-243302 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243566 | Evaluation of Solution#4: Security of multi-hop UE-to-Network Relay communication |
pCR revision of S3-243305 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243567 | Draft TR 33.743 | draft TR | Huawei | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-243568 | Evaluates to solution#4 of TR 33.743 |
pCR revision of S3-243093 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243569 | Update to solution #7 in TR 33.743 |
pCR revision of S3-243257 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243570 | Addressing ENs in solution #9 |
pCR revision of S3-243333 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243571 | Adding an evaluation to solution #9 |
pCR revision of S3-243334 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243572 | Resolve EN in Solution #3: Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revision of S3-243301 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243573 | Conclusion of KI#2 |
pCR revision of S3-243043 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-243574 | Update on Key Issue#1 | pCR | vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
withdrawn | [WTS] [JSN] |
| S3-243575 | Update on Key Issue#4 |
pCR revision of S3-242806 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243576 | New solution on KI#1 Authorization for LCS Data Storage and Retrieval |
pCR revision of S3-242808 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243577 | Add evaluation for sol#2 |
pCR revision of S3-243367 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243578 | Enhancing solution 3 |
pCR revision of S3-242946 |
Nokia | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243579 | EN Address for Solution#4 Authorization of VLF member selection |
pCR revision of S3-242809 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243580 | Resolve one EN for Solution#5 |
pCR revision of S3-243189 |
Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243581 | Addressing the EN on the authorization mechanism through NRF and NEF for AF outside the PLMN |
pCR revision of S3-243031 |
Huawei, HiSilicon | 33.784 0.2.0 | eNA | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243582 | Resolve ENs for sol#7 |
pCR revision of S3-243370 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243583 | Resolve ENs for sol#8 |
pCR revision of S3-243371 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243584 | Resolution of EN on solution 9 for KI#3 |
pCR revision of S3-243063 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243585 | Update for Solution#10 Privacy of Simple alignment |
pCR revision of S3-242811 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243586 | Resolve the EN and update Solution #11 |
pCR revision of S3-243052 |
Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243587 | Adding Enn on the solution 11 for KI#3 |
pCR revision of S3-243077 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243588 | Remove ENs and add evaluation in solution #12 |
pCR revision of S3-243186 |
OPPO | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243589 | Solution to KI#4 : Security of communication data used in VFL training process |
pCR revision of S3-243075 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243590 | Solution 3 evaluation |
pCR revision of S3-242947 |
Nokia | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243591 | Evaluation for Solution#4 Authorization of VLF member selection |
pCR revision of S3-242810 |
vivo, CAICT | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243592 | Evaluation of Solution#5 |
pCR revision of S3-243190 |
Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243593 | Evaluation to the solution on an authorization mechanism through NRF and NEF for AF outside the PLMN |
pCR revision of S3-243032 |
Huawei, HiSilicon | 33.784 0.2.0 | eNA | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243594 | Add evaluation for sol#7 |
pCR revision of S3-243368 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243595 | Add evaluation for sol#8 |
pCR revision of S3-243369 |
Xiaomi Communications | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243596 | Evaluation on solution 9 for KI#3 |
pCR revision of S3-243066 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243597 | Evaluation on the solution 10 for KI#3 |
pCR revision of S3-243076 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243598 | Update of Solution #5: UE authentication and traffic protection in ATSSS-Lite |
pCR revision of S3-243046 |
Ericsson | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-243599 | Draft TR 33.754 | draft TR | Intel | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] | |
| S3-243600 | Add evaluation to solution 1 |
pCR revision of S3-243069 |
Huawei, HiSilicon | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-243601 | Address EN for solution 6 |
pCR revision of S3-243070 |
Huawei, HiSilicon | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-243602 | Cleanup TR 33.754: Key issues |
pCR revision of S3-242958 |
Intel Technology India Pvt Ltd | 33.754 0.2.0 | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] |
| S3-243603 | Draft TR 33.759 | draft TR | Ericsson | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] | |
| S3-243604 | Solution for multiple USS case |
pCR revision of S3-243151 |
Ericsson | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-243605 | TR 33.759 update solution #1 |
pCR revision of S3-242848 |
InterDigital Canada | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-243606 | Drraft TR 33.766 | draft TR | Ericsson | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
approved | [WTS] [JSN] | |
| S3-243607 | Resolution of EN concerning privacy. |
pCR revision of S3-243352 |
Nokia | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-243608 | Update of Solution #1: Solution reusing existing interfaces and security mechanisms for energy related information collection |
pCR revision of S3-242986 |
Ericsson | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-243609 | solution related to KI2 |
pCR revision of S3-243083 |
Huawei, HiSilicon | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-243610 | Solution mapping |
pCR revision of S3-243141 |
Ericsson,Nokia | 33.766 0.2.0 | FS_Energy_Sec | Rel-19 |
S3-117 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-243611 | Solution to KI#2 |
pCR revision of S3-242747 |
Lenovo, US National Security Agency | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243612 | Draft TR 33.794 | draft TR | Motorola Mobility | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] | |
| S3-243613 | Solution for enhancement of SBA access control decision mechanisms |
pCR revision of S3-242833 |
Nokia | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243614 | New solution for KI#2: Dynamic Security Policy Enforcement Framework |
pCR revision of S3-242867 |
MITRE-FFRDC, Defense Information Systems Agency EM | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243615 | New Solution to Key Issue #2: Policy enforcement using NRF configuration and short access token lifetime |
pCR revision of S3-243310 |
Ericsson | 33.794 0.3.0 | FS_eZTS | Rel-19 |
S3-117 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-243616 | Update Sol3 on Support of Third Party specific User Identities in IMS |
pCR revision of S3-242872 |
Nokia, Nokia Shanghai Bell | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243617 | Addressing the EN on details of determining the received Avatar ID of solution 5 |
pCR revision of S3-243024 |
Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243618 | Addressing the ENs on token related details and alignment of SA2 for solution#5 |
pCR revision of S3-243023 |
Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243619 | Evaluation on Solution#5 |
pCR revision of S3-243025 |
Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243620 | Resolving EN in sol#6 |
pCR revision of S3-243228 |
Samsung | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243621 | Evaluation for sol#6 |
pCR revision of S3-243229 |
Samsung | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243622 | Update Sol7 on Protect IMS DC based Avatar Communication |
pCR revision of S3-242873 |
Nokia, Nokia Shanghai Bell | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243623 | Update sol9 on Secure IMS DC capability exposure |
pCR revision of S3-242870 |
Nokia, Nokia Shanghai Bell | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243624 | New solution on avatar communication |
pCR revision of S3-243230 |
Samsung | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243625 | A new solution on the security of IMS DC capability exposure |
pCR revision of S3-243026 |
Huawei, HiSilicon | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243626 | New solution for KI#3: IMS DC capability exposure security based on existing specification |
pCR revision of S3-243298 |
Ericsson | 33.790 0.3.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-243627 | A new solution on authorizing AF to retrieve UE ID |
pCR revision of S3-243028 |
Huawei, HiSilicon | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243628 | Solution for security retrieval of 5G UE Id and privacy related information |
pCR revision of S3-242828 |
Nokia, Nokia Shanghai Bell | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243629 | Solution for secure retrieval of 5G UE privacy related information based on AKMA |
pCR revision of S3-242829 |
Nokia, Nokia Shanghai Bell | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243630 | MEC - Soltuion on EEC provided Information authentication |
pCR revision of S3-242999 |
Apple | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243631 | Resolution of ENs on solution 1 |
pCR revision of S3-243123 |
Huawei, HiSilicon | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243632 | Evaluation on solution 1 |
pCR revision of S3-243124 |
Huawei, HiSilicon | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243633 | New solution for EEC provided information verification: UE ID token |
pCR revision of S3-243149 |
Ericsson | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243634 | Solution for IP address verification |
pCR revision of S3-243216 |
Samsung | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243635 | Solution for IP address verification using access token |
pCR revision of S3-243343 |
Samsung | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243636 | Key issue on security of resource owner authorization management |
pCR revision of S3-243139 |
Ericsson, Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-243637 | draft_TR 33.700-22 skeleton FS_CAPIF_Ph3-sec |
draft TR revision of S3-243375 |
Xiaomi Communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-243638 | New key issue about CAPIF interconnection in TR 33.700-22 |
pCR revision of S3-243154 |
China Telecom Corporation Ltd., Xiaomi,Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-243639 | New key issue for CAPIF interconnection | pCR | Ericsson, Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-243640 | New KI_Key issue on API invoker on one UE accessing resources owned by another UE |
pCR revision of S3-243376 |
Xiaomi Communications,Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-243641 | Mobility under a TNGF |
other revision of S3-243327 |
Qualcomm Incorporated |
S3-117 AI: 4.13 |
noted | [WTS] [JSN] | |||
| S3-243642 | Living document of the Non3GPPMobEnh study |
draftCR revision of S3-242821 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 4.13 |
reserved | [WTS] [JSN] | |
| S3-243643 | Informative text of using FT for NSWO |
other revision of S3-243329 |
Qualcomm Incorporated |
S3-117 AI: 4.13 |
approved | [WTS] [JSN] | |||
| S3-243644 | KI1 and KI3 conclusion update |
pCR revision of S3-242933 |
Nokia | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
approved | [WTS] [JSN] |
| S3-243645 | KI2 and KI4conclusion update |
pCR revision of S3-242937 |
Nokia | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
approved | [WTS] [JSN] |
| S3-243646 | Proposed conclusion for KI#4 |
pCR revision of S3-243324 |
Qualcomm Incorporated | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
approved | [WTS] [JSN] |
| S3-243647 | Annexes on 256-bit security and backwards compatibility |
pCR revision of S3-242786 |
KDDI Corporation, Cablelabs, Ericsson | 33.700-41 0.2.0 | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
approved | [WTS] [JSN] |
| S3-243648 | Editorial Modifications |
pCR revision of S3-242776 |
Nokia, Nokia Shanghai Bell | 33.700-41 0.2.0 | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
approved | [WTS] [JSN] |
| S3-243649 | Presentation of Specification to TSG: TR 33.700-41 |
TS or TR cover revision of S3-242788 |
KDDI Corporation | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
approved | [WTS] [JSN] | |
| S3-243650 | New key issue on security aspect of digital asset container in 5G |
pCR revision of S3-243126 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-243651 | 33.721: Key Issue on Authentication and Authorization of Avatar |
pCR revision of S3-243276 |
Xiaomi Technology | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-243652 | Evaluation for Solution #1 |
pCR revision of S3-242930 |
ZTE Corporation | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-243653 | Solution for KI#1 on Authorization supporting spatial localization service |
pCR revision of S3-242874 |
Nokia, Nokia Shanghai Bell | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-243654 | Solution for KI1 on Authorization of spatial anchor services with multiple VAL-S |
pCR revision of S3-242875 |
Nokia, Nokia Shanghai Bell | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-243655 | Draft TR 33.700-41 | draft TR | KDDI | FS_CAT256 | Rel-19 |
S3-117 AI: 5.5 |
approved | [WTS] [JSN] | |
| S3-243656 | Draft TR 33.790 | draft TR | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-117 AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-243657 | Evaluation to Solution #1 |
pCR revision of S3-243395 |
33.701 0.3.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] | |
| S3-243658 | Draft TR 33.700-22 | draft TR | Xiaomi | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
withdrawn | [WTS] [JSN] | |
| S3-243659 | Updates to overall summary |
pCR revision of S3-243120 |
Huawei, HiSilicon | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] |
| S3-243660 | Draft TR 33.702 | draft TR | Nokia | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
approved | [WTS] [JSN] | |
| S3-243661 | Removal of boiler plate texts in format of evidence |
CR revision of S3-242978 |
BSI (DE) | 33.117 18.3.0 CR#1971 catF | SCAS_5G_Maint | Rel-19 |
S3-117 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-243662 | Proposed solution for Secure Transport of Messages |
pCR revision of S3-243398 |
33.776 0.3.0 | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
approved | [WTS] [JSN] | |
| S3-243663 | TR 33.743 update solution #1 |
pCR revision of S3-242853 |
InterDigital Canada | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243664 | New solution for KI#1 using Attribute-Based Authorization for the consumers | pCR | Huawei, HiSilicon | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
noted | [WTS] [JSN] |
| S3-243665 | New KI on Security aspects related to enhancements of EAS and local UPF (re)selection |
pCR revision of S3-242830 |
Nokia, Nokia Shanghai Bell | 33.749 0.2.0 | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-243666 | LS on Security Handling for inter-CU LTM in non-DC cases |
LS out LS To: 3GPP RAN WG2 revision of S3-242819 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-243667 | Discussion paper for Fast BSS details from 802.11 specs |
discussion revision of S3-242935 |
Nokia | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
noted | [WTS] [JSN] | |
| S3-243668 | Solution for multiple USS case using token | pCR | Ericsson | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-243669 | Resolve EN and evaluate to Sol#11 for multi-hop U2U security establishment |
pCR revision of S3-243089 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243670 | Evaluates to solution#6 of TR 33.743 |
pCR revision of S3-243094 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243671 | New WID on Security for MonStra |
WID new revision of S3-242855 |
Vodafone, Telefonica, Nokia, Nokia Shanghai Bell | Rel-19 |
S3-117 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-243672 | Sol#2 update to address ENs |
pCR revision of S3-242879 |
Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-243673 | Sol#3 update to address ENs |
pCR revision of S3-242881 |
Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-243674 | Sol#2 evaluation |
pCR revision of S3-242880 |
Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-243675 | Sol#3 evaluation |
pCR revision of S3-242882 |
Huawei, HiSilicon | 33.759 0.2.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-117 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-243676 | LS on aggregation and other N32 topics in the context of mediated roaming |
LS out LS is reply to S3-242706 source LS: S3-242364 LS To: GSMA 5GMRR revision of S3-242780 |
BSI (DE) | Roaming5G | Rel-18 |
S3-117 AI: 3 |
approved | [WTS] [JSN] | |
| S3-243677 | LS on GSMA non compliance with 3GPP specifications on 5G Roaming over Roaming Intermediaries |
LS out LS is reply to S3-242706 LS To: TSG SA revision of S3-242931 |
CableLabs |
S3-117 AI: 3 |
approved | [WTS] [JSN] | |||
| S3-243678 | Reply LS on Resource content filter |
LS out LS is reply to S3-242710 LS To: CT4 revision of S3-243217 |
Samsung | Rel-19 |
S3-117 AI: 3 |
approved | [WTS] [JSN] | ||
| S3-243679 | Clarifications for HONTRA procedure with respect to failure cases | CR | Ericsson | 33.501 18.6.0 CR#20441 catF | HN_Auth | Rel-18 |
S3-117 AI: 3 |
withdrawn | [WTS] [JSN] |
| S3-243680 | New Key Issue for Authentication in Ambient IoT service |
pCR revision of S3-243060 |
Huawei, HiSilicon, China Unicom, Vivo, Apple | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-243681 | Solution on Disabling Enabling | pCR | OPPO | 33.713 0.2.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
withdrawn | [WTS] [JSN] |
| S3-243682 | Validation of the allowed slices in the access token request at NRF |
CR revision of S3-243160 |
Ericsson, Nokia, Huawei | 33.501 18.6.0 CR#20391 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-117 AI: 4.1.2 |
agreed | [WTS] [JSN] |
| S3-243683 | Validation of the requested slices at NF service producer |
CR revision of S3-243161 |
Ericsson, Nokia, Huawei | 33.501 18.6.0 CR#20401 catF | 5G_eSBA_Ph2 | Rel-18 |
S3-117 AI: 4.1.2 |
agreed | [WTS] [JSN] |
| S3-243684 | Completing the Privacy Check of n UEs for Service Exposure to Client UE |
CR revision of S3-243265 |
Xiaomi, OPPO, Phillips | 33.533 18.3.0 CR#761 catF | Ranging_SL_Sec | Rel-18 |
S3-117 AI: 4.1.12 |
agreed | [WTS] [JSN] |
| S3-243685 | Filtering requirements on Map interface for Security Assurance Specifications for SMSF |
pCR revision of S3-243292 |
IIT Bombay | 33.529 0.5.0 | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
approved | [WTS] [JSN] |
| S3-243686 | Cover page TS 33.529 | TS or TR cover | IIT Bombay | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
approved | [WTS] [JSN] | |
| S3-243687 | Test Case on No Web Server Header Info |
other revision of S3-242772 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |||
| S3-243688 | Test Case on No Web Server File Type Mappings |
other revision of S3-242774 |
Nokia, Nokia Shanghai Bell |
S3-117 AI: 4. |
approved | [WTS] [JSN] | |||
| S3-243689 | Living document on NR mobility enhancement |
draftCR revision of S3-243193 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-117 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-243690 | Solution for SUPI privacy |
pCR revision of S3-243204 |
Samsung | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-117 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-243691 | Conclusion proposal |
pCR revision of S3-243511 |
Huawei, HiSilicon | 33.701 1.0.0 | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] |
| S3-243692 | Cover sheet TR 33.701 | TS or TR cover | Huawei | FS_MiBiDA | Rel-19 |
S3-117 AI: 5.6 |
approved | [WTS] [JSN] | |
| S3-243693 | Resolution of EN on solution 18 |
pCR revision of S3-243057 |
Huawei, HiSilicon | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243694 | Addition to solution #3 |
pCR revision of S3-243318 |
Qualcomm Incorporated | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243695 | Removing ENs and adding evaluation in Sol#19 of TR 33.700-29 |
pCR revision of S3-243072 |
Huawei, HiSilicon | 33.700-29 0.3.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-117 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-243696 | LS on Masking of cryptographic keys in UE trace file from 3GPP core network entities |
LS out LS To: SA5 revision of S3-243153 |
Ericsson |
S3-117 AI: 3 |
approved | [WTS] [JSN] | |||
| S3-243697 | Further conclusion for Key issue #1 |
pCR revision of S3-242837 |
Charter Communications, Inc | 33.702 0.3.0 | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
approved | [WTS] [JSN] |
| S3-243698 | Cover sheet TR 33.702 | TS or TR cover | Nokia | FS_Non3GPPMob_Sec | Rel-19 |
S3-117 AI: 5.8 |
approved | [WTS] [JSN] | |
| S3-243699 | Draft TR 33.713 | draft TR | OPPO | FS_Ambient_IoT_Sec | Rel-19 |
S3-117 AI: 5.9 |
approved | [WTS] [JSN] | |
| S3-243700 | Key Issue on Authenticating multiple API invokers of the same Resource Owner |
pCR revision of S3-243252 |
Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-243701 | Living document for SMSF SCAS | draftCR | IIT Bombay | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
approved | [WTS] [JSN] | |
| S3-243702 | Security Assurance Specification (SCAS) threats specific to SMSF | CR | IIT Bombay | 33.926 19.1.0 CR#99 catB | SCAS_5G_SMSF | Rel-19 |
S3-117 AI: 4.4 |
agreed | [WTS] [JSN] |
| S3-243703 | Resolution of EN on solution 1 for KI#1 |
pCR revision of S3-243065 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-243704 | Evaluation on solution 1 for KI#1 |
pCR revision of S3-243062 |
Huawei, HiSilicon | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243705 | Update the security threats of Key Issue #2: Authorization mechanism of selection of VFL participants in the VFL group |
pCR revision of S3-243051 |
Ericsson | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243706 | Resolve ENs in Solution #2: Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revision of S3-243300 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243707 | Evaluation of Solution #2: Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revision of S3-243303 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243708 | Evaluation of Solution #3: Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revision of S3-243304 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243709 | Adding an evaluation to solution #10 |
pCR revision of S3-243337 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243710 | Add the evaluation of solution #7 in TR 33.743 |
pCR revision of S3-243259 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243711 | Update EN in solution#13 |
pCR revision of S3-243015 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243712 | Evaluation of solution#13 |
pCR revision of S3-243019 revised to S3-243723 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243713 | Add notes to section 6.7 in TR 33.784 |
pCR revision of S3-242792 |
China Mobile Com. Corporation | 33.784 0.2.0 | FS_AIML_CN_SEC | Rel-19 |
S3-117 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-243714 | Cover sheet TR 33.754 | TS or TR cover | Intel | FS_MASSS_Sec | Rel-19 |
S3-117 AI: 5.15 |
approved | [WTS] [JSN] | |
| S3-243715 | 33.721: Resolve Editor’s Notes in Key Issue 2 |
pCR revision of S3-243274 |
Xiaomi Technology | 33.721 0.2.0 | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-243716 | add high-level architectures for TR 33.700-22 |
pCR revision of S3-243373 |
Xiaomi Communications,Nokia | 33.700-22 0.0.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-243717 | [MCXSec4] 33180 R19 MC Recording Server Introduction |
CR revision of S3-242763 |
Airbus, Motorola Solutions | 33.180 18.1.0 CR#2121 catC | MCXSec4 | Rel-19 |
S3-117 AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-243718 | Draft TR 33.700-22 | draft TR | Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-117 AI: 5.19 |
reserved | [WTS] [JSN] | |
| S3-243719 | update to the support of ESP encryption transforms in TS 33.210 |
other revision of S3-243056 |
Huawei, HiSilicon | CryptoSP | Rel-19 |
S3-117 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-243720 | Draft TR 33.721 | draft TR | Samsung | FS_Metaverse_Sec | Rel-19 |
S3-117 AI: 5.18 |
approved | [WTS] [JSN] | |
| S3-243721 | Draft TR 33.749 | draft TR | Huawei | FS_EDGE_Ph3 | Rel-19 |
S3-117 AI: 5.14 |
approved | [WTS] [JSN] | |
| S3-243722 | Draft TR 33.776 | draft TR | Cisco | FS_ACME_SBA | Rel-19 |
S3-117 AI: 5.4 |
approved | [WTS] [JSN] | |
| S3-243723 | Evaluation of solution#13 |
pCR revision of S3-243712 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
1024 documents (1.2274971008301 seconds)