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-244600 | Agenda |
agenda revised to S3-245134 |
SA WG3 Chair |
S3-119 AI: 1 |
revised | [WTS] [JSN] | |||
| S3-244601 | Report from last SA3 meeting | report | MCC |
S3-119 AI: 2.1 |
approved | [WTS] [JSN] | |||
| S3-244602 | Process for SA3#119 | other | SA WG3 Chair |
S3-119 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-244603 | Detailed agenda planning |
other revised to S3-245135 |
SA WG3 Chair |
S3-119 AI: 1 |
revised | [WTS] [JSN] | |||
| S3-244604 | SA3 meeting calendar | other | SA WG3 Chair |
S3-119 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-244605 | Discussion paper for CT1 LS on expected UE behavior on potential SUCI computation failure | discussion | Deutsche Telekom AG | TEI19 | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-244606 | Discussion paper on user consent for energy information collection and energy information exposure | discussion | Deutsche Telekom AG | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
noted | [WTS] [JSN] | |
| S3-244607 | TCG progress - report from TCG rapporteur | report | InterDigital Belgium. LLC |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244608 | Additional conclusions for KI#1 |
pCR revised to S3-245212 |
InterDigital Belgium. LLC | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244609 | Updates and Clean-up of KI#1 Conclusion |
pCR revised to S3-245182 |
Motorola Mobility [Rapporteur] | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244610 | Updates and Clean-up of KI#2 Conclusion | pCR | Motorola Mobility [Rapporteur] | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-244611 | Cleanup of TR 33.794 |
pCR revised to S3-245185 |
Motorola Mobility [Rapporteur] | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244612 | Presentation of Specification/Report to TSG for TR 33.794 |
pCR revised to S3-245365 |
Motorola Mobility [Rapporteur] | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244613 | Updates to Solution#11 |
pCR revised to S3-245201 |
Lenovo | 33.757 0.5.0 | FS_eZTS, PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-244614 | Discussion Paper on eZTS SBA WID Proposal | discussion | Motorola Mobility [Rapporteur] | FS_eZTS | Rel-19 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | |
| S3-244615 | New WID on enablers for Zero Trust Security in SBA |
WID new revised to S3-245319 |
Motorola Mobility [Rapporteur] | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-244616 | Updates to Solution #21 |
pCR revised to S3-245236 |
Lenovo | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244617 | Updates to Solution #5 |
pCR revised to S3-245221 |
Lenovo | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244618 | New Study on 3GPP Cryptographic Inventory |
SID new revised to S3-245142 |
Nokia, Nokia Shanghai Bell |
S3-119 AI: 6 |
revised | [WTS] [JSN] | |||
| S3-244619 | Coverpage for TR Skeleton for 3GPP Cryprographic Inventory | other | Nokia, Nokia Shanghai Bell |
S3-119 AI: 3.2 |
noted | [WTS] [JSN] | |||
| S3-244620 | Scope of TR on 3GPP cryptographic inventory | other | Nokia, Nokia Shanghai Bell |
S3-119 AI: 3.2 |
noted | [WTS] [JSN] | |||
| S3-244621 | Technical Content for 3GPP Cryptographic Inventory |
other revised to S3-245362 |
Nokia, Nokia Shanghai Bell |
S3-119 AI: 3.2 |
revised | [WTS] [JSN] | |||
| S3-244622 | New SID on 5G Security Assurance Specification (SCAS) for the Container-based Products | SID new | Ericsson, Nokia, Nokia Shanghai Bell | Rel-19 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-244623 | Discussion on SCAS for Containerized applications | discussion | Nokia, Nokia Shanghai Bell |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |||
| S3-244624 | Analysis on Solution 2 | other | Nokia, Nokia Shanghai Bell |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | |||
| S3-244625 | Correction of terms in Overview of TR 33.757 | pCR | Johns Hopkins University APL | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-244626 | New annex for security event data records |
pCR revised to S3-245183 |
Johns Hopkins University APL | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244627 | LS to 3GPP CT4 on recursively defined JSON structures and reply to LS C4-241343 | LS in | GSMA |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244628 | LS on including the HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS in LS reply in S3-244961, S3-245128, S3-245136 |
C1-244647 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244629 | LS on UE behaviour in case of SUCI calculation failure |
LS in LS reply in S3-245137, S3-244729, S3-245137 |
C1-245039 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244630 | Reply LS on Mitigation of Downgrade attacks | LS in | C1-245048 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244631 | Reply-LS on GSMA CVD-2023-0069 5G Core Network Attacks |
LS in LS reply in S3-244845, S3-244845 |
C4-243671 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244632 | Reply LS on clarification on home network triggered re-authentication |
LS in LS reply in S3-244973 |
C4-244496 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244633 | LS on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS in LS reply in S3-244727, S3-244751 |
C4-244497 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244634 | LS on PWS support for NB-IoT NTN | LS in | R2-2409243 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244635 | Response LS on Newly published data channel GSMA PRD TS.66 | LS in | R5-245464 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244636 | LS on AIML data collection |
LS in LS reply in S3-245138, S3-244713, S3-244728, S3-244948, S3-245038, S3-245138 |
RP-242389 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244637 | LS on Completion of 5WWC_Ph2 (R18) work | LS in | S2-2409022 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244638 | LS Reply to Issues related to Analytics context transfer between AnLF(s) |
LS in LS reply in S3-244875, S3-244990, S3-245055 |
S2-2409441 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244639 | Reply LS on LCS user plane connection binding to the UE | LS in | S2-2409544 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244640 | Further LS Reply on Internal 5G Core information expose to trusted AF | LS in | S2-2410813 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244641 | LS on security aspects of Ambient IoT |
LS in LS reply in S3-244800, S3-244863, S3-244925, S3-244944, S3-244958, S3-245012, S3-245139 |
S2-2411049 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244642 | Reply LS on AIML data collection | LS in | S2-2411191 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244643 | Reply LS on Clarification regarding definition of 5G NR femto ownership | LS in | S2-2411241 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244644 | Reply to Reply LS on CEN's requirements for eCall over IMS | LS in | S2-2411246 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244645 | Reply LS on FS_5GSAT_Ph3_ARCH conclusions |
LS in LS reply in S3-245340, S3-244794, S3-244998, S3-245340 |
S2-2411250 |
S3-119 AI: 5.7 |
replied to | [WTS] [JSN] | |||
| S3-244646 | LS on enhancement to the protocol stack of IMS Data Channel |
LS in LS reply in S3-245140, S3-245074, S3-245140 |
S4-241373 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244647 | LS Reply on Newly Published data channel GSMA PRD TS.66 | LS in | S4-241684 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244648 | LS reply to IETF Traffic Engineering Architecture and Signaling Working Group on ""A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies"" | LS in | S5-244662 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244649 | LS Reply on Internal 5G Core information expose to trusted AF | LS in | S5-245162 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244650 | LS on SA5 MonStra work progress | LS in | S5-246296 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244651 | LS on Clarification related to Internal 5G Core information expose to trusted AF |
LS in LS reply in S3-245141, S3-244844, S3-245141 |
S6-242714 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244652 | LS on SA6 Answer to GSMA LS on Newly published data channel GSMA PRD TS.66 | LS in | S6-243763 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244653 | Reply LS on Newly published data channel GSMA PRD TS.66 | LS in | SP-241404 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244654 | Reply LS on AIML Data Collection | LS in | S5-246299 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244655 | [33.180] Additions to access token for recording authorization |
CR revised to S3-245148 |
Motorola Solutions, Airbus | 33.180 18.1.0 CR#214 catB | MCXSec4 | Rel-19 |
S3-119 AI: 4.6 |
revised | [WTS] [JSN] |
| S3-244656 | Evaluation update for solution #9 (Using ACME protocol for certificate renewal) |
pCR revised to S3-245367 |
Google Ireland Limited | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-244657 | Conclusion for KI#4 (Certificate enrolment) |
pCR revised to S3-245211 |
Google Ireland Limited | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-244658 | Conclusion for KI#5 (Certificate Renewal) |
pCR revised to S3-245368 |
Google Ireland Limited | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-244659 | Conclusion for KI#2 (Secure Transport of Messages) |
pCR revised to S3-245210 |
Google Ireland Limited | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-244660 | Clarification on TC_BVT_PORT_SCANNING | draftCR | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-244661 | Add UDM SCAS test case for checking the authentication verification of a synchronization failure message | other | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-244662 | Living Document to TS 33.518 NRF SCAS |
draftCR revised to S3-245364 |
BSI (DE) | SCAS_5G_Maint | Rel-18 |
S3-119 AI: 4.1.1 |
revised | [WTS] [JSN] | |
| S3-244663 | Add threat description about the implications of the AUSF confirming an authentication with the SUPI while the authentication was started with the SUCI | other | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-244664 | Add test case TC_AUSF_CONFIRMATION_WITH_SUPI that check whether the AUSF is vulnerable to a confirmation attack | draftCR | BSI (DE), Radix Security | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-244665 | Add threat description about the implications of the AUSF not validating RES* correctly | other | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-244666 | Add test case that verifies if the AUSF processes RES* failures correctly | draftCR | BSI (DE), Radix Security | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-244667 | Correction and clarification of TC_AMF_NAS_INTEGRITY_FAILURE |
draftCR revised to S3-245328 |
BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
revised | [WTS] [JSN] | |
| S3-244668 | Trust anchoring for N32-f/PRINS |
CR revised to S3-245147 |
BSI (DE), Nokia, Nokia Shanghai Bell | 33.501 19.0.0 CR#2053 catF | TEI19, Roaming5G | Rel-19 |
S3-119 AI: 4.1.14 |
revised | [WTS] [JSN] |
| S3-244669 | New solution on combined authentication and data protection for Ambient IoT services |
pCR revised to S3-245344 |
KPN N.V. | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244670 | New KI: Reader Authorization for 5G Ambient IoT Services | pCR | InterDigital Belgium. LLC | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244671 | Resolution of ENs in Solution #21 |
pCR revised to S3-245304 |
InterDigital Belgium. LLC | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244672 | Resolution of ENs in Solution #20 |
pCR revised to S3-245305 |
InterDigital Belgium. LLC | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244673 | Pre-authorization solution for ACME |
pCR revised to S3-245366 |
NCSC | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-244674 | LS on Multi-hop U2N Relay Architecture Aspects |
LS out LS To: SA2 revised to S3-245259 |
InterDigital France R&D, SAS | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
revised | [WTS] [JSN] | |
| S3-244675 | Living document for MonStra: draftCR to TS 33.501, Signalling Monitoring |
draftCR revised to S3-245168 |
Vodafone | MonStra-Sec | Rel-19 |
S3-119 AI: 4.14 |
revised | [WTS] [JSN] | |
| S3-244676 | Cover Sheet TR 33.700-32 |
TS or TR cover revised to S3-245369 |
InterDigital France R&D, SAS | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5. |
revised | [WTS] [JSN] | |
| S3-244677 | TR 33.700-32 Conclusion for Key Issue#3, Cablelabs, Lenovo |
pCR revised to S3-245268 |
InterDigital France R&D, SAS | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5. |
revised | [WTS] [JSN] |
| S3-244678 | KI 1 Conclusion Clarification on Replay Use Case |
pCR revised to S3-245180 |
MITRE-FFRDC, US National Security Agency, Johns Hopkins University APL | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244679 | Address ENs in Solution #8: Supporting all 5G SBA certificate types | pCR | Cisco Systems | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-244680 | Conclusion for KI#1: ACME initial trust framework |
pCR revised to S3-245209 |
Cisco Systems | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-244681 | Conclusion for KI#7: Supporting all 5G SBA certificate types |
pCR revised to S3-245317 |
Cisco Systems | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
revised | [WTS] [JSN] |
| S3-244682 | Presentation of Specification/Report to TSG: TR 33.776, Version 1.0.0 |
TS or TR cover revised to S3-245318 |
Cisco Systems | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
revised | [WTS] [JSN] | |
| S3-244683 | New WID on Automatic Certificate Management Environment (ACME) for the Service Based Architecture (SBA) |
WID new revised to S3-245372 |
Cisco Systems | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-244684 | Use of AEAD in Next-Generation 3GPP System | discussion | KDDI Corporation | Rel-20 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-244685 | MnF User session timeout | draftCR | Keysight Technologies UK Ltd | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-244686 | Living document of the Non3GPPMobEnh study |
draftCR revised to S3-245166 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-119 AI: 4.13 |
revised | [WTS] [JSN] | |
| S3-244687 | TNGF solution alignment | other | Nokia, CableLabs | Non3GPPMob_Sec | Rel-19 |
S3-119 AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-244688 | TWIF solution |
other revised to S3-245165 |
Nokia, Lenovo, Charter Communications | Non3GPPMob_Sec | Rel-19 |
S3-119 AI: 4.13 |
revised | [WTS] [JSN] | |
| S3-244689 | LS on Non3GPPMob_Sec update |
LS out LS To: SA2 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-119 AI: 4.13 |
noted | [WTS] [JSN] | |
| S3-244690 | concluding KI3 | pCR | Nokia | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5. |
merged | [WTS] [JSN] |
| S3-244691 | KI3 conclusion | pCR | Nokia | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244692 | Discussion paper reauthentication via untrusted non 3GPP access | discussion | Nokia | TEI18 | Rel-18 |
S3-119 AI: 4.1.15 |
noted | [WTS] [JSN] | |
| S3-244693 | Reauthentication aspect for IPSec in non 3GPP access | CR | Nokia | 33.501 18.7.0 CR#2054 catF | TEI18 | Rel-18 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244694 | Reauthentication aspect for IPSec in non 3GPP access |
CR revised to S3-245143 |
Nokia | 33.501 19.0.0 CR#2055 catF | TEI19 | Rel-19 |
S3-119 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-244695 | Discussion paper of UPU implementation gaps | discussion | Nokia | TEI18 | Rel-18 |
S3-119 AI: 4.1.15 |
noted | [WTS] [JSN] | |
| S3-244696 | Enhancement in UPU procedure to protect UPU header | CR | Nokia | 33.501 18.7.0 CR#2056 catF | TEI18 | Rel-18 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244697 | Discussion paper on SUCI calculation | discussion | Nokia | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244698 | NSWO AN and SNN related update | CR | Nokia | 33.501 18.7.0 CR#2057 catF | TEI18 | Rel-18 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244699 | NSWO AN and SNN related update | CR | Nokia | 33.501 19.0.0 CR#2058 catA | TEI18 | Rel-19 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244700 | Kamf definition alignment for NAS count | CR | Nokia | 33.501 16.18.0 CR#2059 catF | TEI16 | Rel-16 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244701 | Kamf definition alignment for NAS count | CR | Nokia | 33.501 17.14.0 CR#2060 catA | TEI16 | Rel-17 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244702 | Kamf definition alignment for NAS count | CR | Nokia | 33.501 18.7.0 CR#2061 catA | TEI16 | Rel-18 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244703 | Kamf definition alignment for NAS count | CR | Nokia | 33.501 19.0.0 CR#2062 catA | TEI16 | Rel-19 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244704 | Home control for NSWO | CR | Nokia | 33.501 18.7.0 CR#2063 catF | TEI18 | Rel-18 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244705 | Home control for NSWO | CR | Nokia | 33.501 19.0.0 CR#2064 catA | TEI18 | Rel-19 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244706 | AUSF requirement for the case of Indirect Network Sharing: | CR | Nokia | 33.501 19.0.0 CR#2065 catF | TEI19 | Rel-19 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244707 | Reply LS to CT4 on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-244633 source LS: C4-244497 LS To: CT4 |
Nokia | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244708 | New (mini) WID on SUCI calculation failure alignment | WID new | Nokia | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244709 | Ambient IoT solution on privacy revision |
pCR revised to S3-245306 |
Apple | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244710 | Ambient IoT solution on mutual authentication revision |
pCR revised to S3-245315 |
Apple | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244711 | Discussion paper on SUCI calculation failure | discussion | Apple |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244712 | Reply LS to CT1 on UE bahaviour in case of SUCI calculation failure |
LS out LS To: CT1 |
Apple |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-244713 | Reply LS on AIML data collection |
LS out LS is reply to S3-244636 LS To: RAN |
Apple |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-244714 | LTM - way forward discussion - leave the final decision to RAN | other | Apple |
S3-119 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-244715 | LTM - WID revision | WID new | Apple |
S3-119 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-244716 | SERP - Discussion paper | discussion | Apple |
S3-119 AI: 4.1.15 |
noted | [WTS] [JSN] | |||
| S3-244717 | SERP - revised WID | WID new | Apple | Rel-18 |
S3-119 AI: 4.1.15 |
noted | [WTS] [JSN] | ||
| S3-244718 | SERP - CR on security protection on RRCResumeRequest message | draftCR | Ericsson, Apple | SERP | Rel-19 |
S3-119 AI: 4.1.15 |
noted | [WTS] [JSN] | |
| S3-244719 | SERP - LS to RAN on SERP |
LS out LS To: RAN 2, RAN 3 |
Apple |
S3-119 AI: 4.1.15 |
noted | [WTS] [JSN] | |||
| S3-244720 | Using mTLS with ACME | pCR | NCSC | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
noted | [WTS] [JSN] |
| S3-244721 | Clarifications to Conclusion 1 |
pCR revised to S3-245181 |
U.S. National Security Agency, OTD_US, MITRE-FFRDC, Johns Hopkins University APL, Deutsche Telekom AG | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244722 | Confidentiality and Integrity for KI 1 Conclusion | pCR | U.S. National Security Agency, MITRE-FFRDC, Johns Hopkins University APL, OTD_US, Deutsche Telekom AG | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-244723 | General Recommendations for Conclusion 2 Policy Enforcement |
pCR revised to S3-245184 |
U.S. National Security Agency,OTD_US, Johns Hopkins University APL, MITRE-FFRDC | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-244724 | Update solution mapping to incorporate KI#9 | pCR | Charter Communications, Inc | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244725 | Add evaluation to solution#3 | pCR | Charter Communications, Inc | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244726 | Discussion on PLMN ID setting in the 3gpp-Sbi-Originating-Network-Id header in the Indirect Network Sharing case during UE authentication | discussion | China Unicom, ZTE Corporation |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244727 | Reply LS to CT4 on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-244633 LS To: CT4 |
China Unicom |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244728 | Reply LS on AIML data collection |
LS out LS is reply to S3-244636 LS To: RAN, RAN2, SA2 |
vivo | NR_AIML_air | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244729 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-244629 LS To: CT1 |
vivo | 5GProtoc19 | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244730 | UE behaviour in case of SUCI calculation failure | CR | vivo | 33.501 19.0.0 CR#2066 catF | TEI19 | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244731 | New solution on Mismatch of UE security context |
other revised to S3-245163 |
vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244732 | Conclusion on mismatch of UE security context | other | vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
merged | [WTS] [JSN] | |
| S3-244733 | Address EN in solution 31 |
pCR revised to S3-245216 |
vivo | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244734 | Update on Key Issue#6 | pCR | vivo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244735 | KI#5, Solution update on AIoT device authentication |
pCR revised to S3-245316 |
vivo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244736 | KI#4, New Sol Communication Security of intermediate UE interacting with AIoT device |
pCR revised to S3-245296 |
vivo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244737 | KI#1, New Sol Disable AIoT device |
pCR revised to S3-245299 |
vivo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244738 | KI#3, New Sol Privacy protection based on anonymous AIoT device ID | pCR | vivo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244739 | Address EN in solution 4 | pCR | vivo | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244740 | KI1 update | pCR | vivo | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244741 | New sol: User consent for LCS | pCR | vivo | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-244742 | Additional Conclusion for key issue#1 | pCR | vivo | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-244743 | Additional Conclusion for key issue#2 |
pCR revised to S3-245269 |
vivo, Nokia, Nokia Shanghai Bell, China Mobile, China Telecom, China Unicom, Xiaomi | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244744 | Additional Conclusion for key Issue#3 |
pCR revised to S3-245270 |
vivo, China Mobile, China Telecom, China Unicom | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244745 | TR clean up |
pCR revised to S3-245347 |
vivo | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244746 | R20 Security Planning - vivo's views | discussion | vivo |
S3-119 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-244747 | Evaluation to solution #4 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244748 | draft - Reply LS on clarification on home network triggered re-authentication |
LS out LS To: CT4 |
ZTE Corporation | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244749 | Clarifications for HONTRA procedure with respect to failure cases | CR | ZTE | 33.501 18.7.0 CR#2067 catF | HN_Auth | Rel-18 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244750 | Clarifications for HONTRA procedure with respect to failure cases | CR | ZTE | 33.501 19.0.0 CR#2068 catA | HN_Auth | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244751 | reply LS to CT4 on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-244633 LS To: CT4 |
ZTE Corporation |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244752 | Security aspects for Indirect Network Sharing | CR | ZTE Corporation | 33.501 19.0.0 CR#2069 catF | TEI19 | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244753 | Resolve the EN in Sol#3 |
other revised to S3-245161 |
ZTE Corporation | Rel-19 |
S3-119 AI: 4.12 |
revised | [WTS] [JSN] | ||
| S3-244754 | Conclusion to KI#3 | pCR | ZTE Corporation | 33.757 0.3.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244755 | Adding solution to KI#2 |
pCR revised to S3-245217 |
ZTE Corporation | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244756 | Conclusion on KI#2 for split MME architecture | pCR | ZTE Corporation | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-244757 | Add the evaluation for the Sol#2 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244758 | New key issue on secure data transfer between UE and AIOTF | pCR | ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244759 | Resolving ENs in sol#6 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244760 | Evaluation for solution 6 | pCR | ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244761 | Resolving ENs in sol#25 in TR 33.713 |
pCR revised to S3-245307 |
ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244762 | Adding evaluation to sol#25 in TR 33.713 |
pCR revised to S3-245308 |
ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244763 | Update the KI#1 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244764 | Update the KI#3 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244765 | Update to KI#9 | pCR | ZTE Corporation | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-244766 | Address the EN in Sol#3 | pCR | ZTE Corporation | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244767 | Add conclusions to KI#9 | pCR | ZTE Corporation | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-244768 | Update conclusions to KI#1 | pCR | ZTE Corporation | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-244769 | Remove the EN in stable conclusions |
pCR revised to S3-245353 |
ZTE Corporation | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244770 | Conclusion on KI#1 | pCR | ZTE Corporation | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-244771 | Conclusion on KI#2 | pCR | ZTE Corporation | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-244772 | Evaluation for the Solution 23 |
pCR revised to S3-245237 |
ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244773 | Add evaluation to Sol#1 | pCR | ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244774 | Conclusion on KI#1.1 | pCR | ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244775 | Conclusion on KI#1.2 | pCR | ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244776 | Conclusion on KI#2 |
pCR revised to S3-245248 |
ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244777 | WID on security aspects of 5G NR Femto |
WID new revised to S3-245325 |
ZTE Corporation | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-244778 | Evaluation to solution #5 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-244779 | Update and evaluate solution #6 in TR 33.700-22 |
pCR revised to S3-245223 |
China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244780 | Conclusion on key issue #1.2 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244781 | Evaluation to solution #4 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244782 | New WID on Security Aspects of Enhancement of Support for Edge Computing in 5GC — phase 3 |
WID new revised to S3-245342 |
China Unicom, Huawei, HiSilicon |
S3-119 AI: 6 |
revised | [WTS] [JSN] | |||
| S3-244783 | Evaluation to solution #8 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244784 | Evaluation to solution #9 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244785 | New WID on Security Aspects of Enhancement for Proximity Based Services in 5GS Phase 3 | WID new | China Telecom Corporation Ltd. |
S3-119 AI: 6 |
merged | [WTS] [JSN] | |||
| S3-244786 | New WID on Security Aspects of Enhancement for Proximity Based Services in 5GS Phase 3 | WID new | China Telecom Corporation Ltd. |
S3-119 AI: 6 |
withdrawn | [WTS] [JSN] | |||
| S3-244787 | Cover Sheet for TR 33.754 |
TS or TR cover revised to S3-245277 |
Intel Corporation (UK) Ltd | FS_MASSS_Sec | Rel-19 |
S3-119 AI: 5.15 |
revised | [WTS] [JSN] | |
| S3-244788 | Resolving EN from Sol#5 |
pCR revised to S3-245300 |
OPPO, Xidian | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244789 | General Principle for Conclusion | discussion | OPPO |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] | |||
| S3-244790 | Updates to Overall Summary of solutions |
pCR revised to S3-245219 |
Nokia | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244791 | Updates to conclusions for split MME architecture | pCR | Nokia | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-244792 | Add specific UDR SCAS test cases for TS 33.530 |
pCR revision of S3-244310 revised to S3-245275 |
BSI (DE) | 33.530 0.1.0 | SCAS_5G_UDR | Rel-19 |
S3-119 AI: 4.2 |
revised | [WTS] [JSN] |
| S3-244793 | Cover Sheet for TS 33.530 SCAS_5G_UDR | TS or TR cover | BSI (DE) | SCAS_5G_UDR | Rel-19 |
S3-119 AI: 4.2 |
approved | [WTS] [JSN] | |
| S3-244794 | Reply LS to Reply LS on FS_5GSAT_Ph3_ARCH conclusions |
LS out LS is reply to S3-244645 LS To: SA2 |
Nokia | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
merged | [WTS] [JSN] | |
| S3-244795 | Resolve ENs in sol#23 | pCR | OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244796 | Conclusion to KI#2 |
pCR revised to S3-245206 |
China Telecomunication Corp., ZTE, China Unicom, CATT | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-244797 | Removing EN in Sol#2 |
pCR revised to S3-245200 |
China Telecomunication Corp. | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-244798 | Updates to conclusions for Key Issue #1 |
pCR revised to S3-245282 |
Nokia | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244799 | EN Removal for solution #5 | pCR | Nokia | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244800 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 revised to S3-245139 |
OPPO | Rel-19 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-244801 | EN Removal for solution #6 | pCR | Nokia | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244802 | Updates and EN Removal for solution #7 | pCR | Nokia | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-244803 | KI#3 Discussion related to SA2 LS S2-2411049 | discussion | Sony | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-244804 | Proposal for changing the description of SN counter in SCPAC | CR | Apple Computer Trading Co. Ltd | 33.501 19.0.0 CR#2070 catF | TEI19 | Rel-19 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244805 | [draft] Reply LS to SA2 on on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 source LS: S2-2411049 LS To: SA2 |
Sony | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244806 | Solution 26 Update and Evaluation |
pCR revised to S3-245309 |
Sony | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244807 | Removing MRF from IMS data channel architecture | CR | Huawei, HiSilicon | 33.328 18.2.0 CR#80 catF | NG_RTC_SEC | Rel-18 |
S3-119 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-244808 | Addressing the ENs on Avatar ID determination and token details of Solution#5 |
pCR revised to S3-245190 |
Huawei, HiSilicon | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-244809 | Addressing the ENs on user interaction of Solution#10 | pCR | Huawei, HiSilicon | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-244810 | Conclusion to KI#2 of NG_RTC | pCR | Huawei, HiSilicon | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-244811 | Conclusion to KI#3 of NG_RTC | pCR | Huawei, HiSilicon | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
merged | [WTS] [JSN] |
| S3-244812 | conclusion to KI#2.1 of eEDGE | pCR | Huawei, HiSilicon | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
merged | [WTS] [JSN] |
| S3-244813 | Solving the problem of generating and forwarding the salt to the BSF |
pCR revised to S3-245348 |
Huawei, HiSilicon | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244814 | Update of conclusions KI#1 |
pCR revised to S3-245341 |
Huawei, HiSilicon | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244815 | Update of Conclusions KI#2 | pCR | Huawei, HiSilicon | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244816 | Update on solution 28 | pCR | Huawei, HiSilicon | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-244817 | Retrieval of public key used for token verification | CR | Huawei, HiSilicon | 33.501 19.0.0 CR#2071 catF | TEI19 | Rel-19 |
S3-119 AI: 4.11 |
not pursued | [WTS] [JSN] |
| S3-244818 | Updates to conclusions for Key Issue #3 |
pCR revised to S3-245352 |
Nokia | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244819 | Solution 14 Update and Evaluation |
pCR revised to S3-245312 |
Sony | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244820 | Conclusion for KI#2 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244821 | Evaluation for sol#13 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244822 | Evaluation for sol#14 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244823 | Evaluation for sol#15 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244824 | Evaluation for sol#18 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244825 | Evaluation for sol#19 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244826 | Evaluation for sol#21 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244827 | Evaluation for sol#22 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244828 | Evaluation for sol#24 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244829 | Update sol#17 |
pCR revised to S3-245245 |
China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244830 | KI#3 Conclusion | pCR | Sony | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244831 | Updating Solution #7 | pCR | OPPO, Xidian | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244832 | Solution 2 updates to address ENs | pCR | Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244833 | Adding evaluation to Solution 2 |
pCR revised to S3-245220 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244834 | Solution 4 updates to address ENs | pCR | Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244835 | Adding evaluation to Solution 4 |
pCR revised to S3-245228 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244836 | Adding evaluation to Solution 10 |
pCR revised to S3-245233 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244837 | Conclusion to KI#1.1 |
pCR revised to S3-245222 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244838 | Conclusion to KI#1.2 |
pCR revised to S3-245231 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244839 | Conclusion to KI#1.3 |
pCR revised to S3-245235 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244840 | New solution for UAV triggered UUAA |
pCR revised to S3-245256 |
Huawei, HiSilicon | 33.759 0.4.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-244841 | New solution for USS triggered UUAA |
pCR revised to S3-245257 |
Huawei, HiSilicon | 33.759 0.4.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-244842 | Solution 7 updates to address ENs | pCR | Huawei, HiSilicon | 33.759 0.4.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-244843 | Additional conclusions for KI#3 | pCR | Huawei, HiSilicon, China Telecomunication Corp. | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5. |
merged | [WTS] [JSN] |
| S3-244844 | draft reply LS to SA6 Internal 5G Core information expose to trusted AF |
LS out LS is reply to S3-244651 LS To: SA6 revised to S3-245141 |
Huawei, HiSilicon | Rel-18 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-244845 | Reply LS to CT4 on GSMA CVD-2023-0069 5G Core Network Attacks |
LS out LS is reply to S3-244631 LS To: CT4 |
Huawei, HiSilicon | Rel-18 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-244846 | Inventory of protocols and algorithms for PQC migration | discussion | Huawei, HiSilicon |
S3-119 AI: 3.2 |
noted | [WTS] [JSN] | |||
| S3-244847 | Analysis of GSMA PQC guidelines related to SA3 specifications | discussion | Huawei, HiSilicon |
S3-119 AI: 3.2 |
noted | [WTS] [JSN] | |||
| S3-244848 | New WID on UAS security enhancements |
WID new revised to S3-245321 |
Ericsson | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-244849 | Update KI #1 of TR 33.784 |
pCR revised to S3-245271 |
OPPO | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244850 | RCS lawful intercept requirements | LS in | s3i240708 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244851 | Reply LS on UE-Satellite-UE Communication Architectures | LS in | s3i240752 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244852 | Reply LS on FS_5GSAT_Ph3_ARCH conclusions | LS in | s3i240703 |
S3-119 AI: 5.7 |
noted | [WTS] [JSN] | |||
| S3-244853 | Updating living Draft CR for MonSTra | other | Vodafone, Nokia, Nokia Shanghai Bell | MonStra-Sec | Rel-19 |
S3-119 AI: 4.14 |
approved | [WTS] [JSN] | |
| S3-244854 | LS on request for IMS Data Channel related clarifications | LS in | s3i240707 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244855 | Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-244646 LS To: SA4 revised to S3-245140 |
China Mobile | Rel-18 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-244856 | New WID on Security aspects of Core Network Enhanced Support for AIML |
WID new revised to S3-245322 |
China Mobile, vivo | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-244857 | Presentation of Report to TSG: | other | China Mobile | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] | |
| S3-244858 | Discussion about way forward for zero trust study and beyond | discussion | China Mobile | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
noted | [WTS] [JSN] | |
| S3-244859 | Resolution of ENs concerning compliance to regional legislation when collecting and exposing user energy consumption information. |
pCR revised to S3-245278 |
Nokia, Deutsche Telekom | 33.766 0.4.0 | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-244860 | Regional legislation compliance in relation to collection of user information. |
pCR revised to S3-245350 |
Nokia, Deutsche Telekom | 33.766 0.4.0 | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-244861 | Discission paper concerning RAN agreements | discussion | Nokia |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244862 | Solution to KI#3, KI#4 and KI#5 |
pCR revised to S3-245172 |
Nokia | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244863 | LS reply to LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 source LS: S3-244641 LS To: SA2 |
Nokia |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-244864 | LS reply to LS on RAN2 agreements and assumptions for Ambient IoT |
LS out source LS: S3-242753 LS To: RAN2 |
Nokia |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244865 | Conclusion to KI#2 | pCR | Nokia, Nokia Shanghai Bell, Ericsson, Samsung | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244866 | Conclusion to KI#3 | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244867 | Redundant text in Annex I. | CR | Nokia | 33.501 18.7.0 CR#2072 catF | eNPN_Ph2 | Rel-18 |
S3-119 AI: 4.1.9 |
not pursued | [WTS] [JSN] |
| S3-244868 | Redundant text in Annex I. |
CR revised to S3-245146 |
Nokia | 33.501 19.0.0 CR#2073 catF | eNPN_Ph2 | Rel-19 |
S3-119 AI: 4.1.9 |
revised | [WTS] [JSN] |
| S3-244869 | Updates to Terms, Abbreviations and Overview | draftCR | Ericsson | DUMMY | Rel-19 |
S3-119 AI: 5.11 |
noted | [WTS] [JSN] | |
| S3-244870 | Conclusion for KI#3 | pCR | China Telecomunication Corp. | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-244871 | Update of Conclusion on Key issue #1 |
pCR revised to S3-245346 |
Huawei, HiSilicon | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244872 | Update of Conclusion on Key issue #3 | pCR | Huawei, HiSilicon | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244873 | Solution 1 update to address ENs | pCR | Huawei, HiSilicon | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244874 | Solution 9 update to address ENs | pCR | Huawei, HiSilicon | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244875 | Reply LS on Issues related to Analytics context transfer between AnLF(s) |
LS out LS is reply to S3-244638 source LS: S2-2409441 LS To: SA2 |
Huawei, HiSilicon | eNA_Ph3_SEC | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-244876 | Discussion Paper for using MPQUIC in ATSSS scenario | discussion | Huawei, HiSilicon | Rel-18 |
S3-119 AI: 4.1.15 |
noted | [WTS] [JSN] | ||
| S3-244877 | Update to MPQUIC TLS Annex | CR | Huawei, HiSilicon | 33.501 18.7.0 CR#2074 catF | TEI18 | Rel-18 |
S3-119 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-244878 | Discussion about mitigating the Security risk of Unprotected NAS Reject | discussion | Huawei, HiSilicon | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
noted | [WTS] [JSN] | |
| S3-244879 | Update to TS 33.503 to fix the referred clause and table of services | CR | Huawei, HiSilicon | 33.503 17.9.0 CR#208 catF | 5G_ProSe | Rel-17 |
S3-119 AI: 4.1.3 |
agreed | [WTS] [JSN] |
| S3-244880 | Update to TS 33.503 to fix the referred clause and table of services - Mirror | CR | Huawei, HiSilicon | 33.503 18.4.0 CR#209 catA | 5G_ProSe | Rel-18 |
S3-119 AI: 4.1.3 |
agreed | [WTS] [JSN] |
| S3-244881 | Update to Conclusion on Key issue #2 | pCR | Huawei, HiSilicon | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244882 | conclusion on key issue#3 |
pCR revised to S3-245208 |
Huawei, HiSilicon | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-244883 | Evaluation to solution 20 | pCR | Huawei, HiSilicon | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-244884 | Evaluation to solution 11 | pCR | Huawei, HiSilicon | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-244885 | resolve EN for K1 and KI2 | pCR | Huawei, HiSilicon | 33.766 0.4.0 | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
merged | [WTS] [JSN] |
| S3-244886 | Update to KI#2 conclusion of TR 33.743 |
pCR revised to S3-245265 |
Huawei, HiSilicon | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244887 | Conclude to KI#1 of TR 33.743 - U2NW discovery security | pCR | Huawei, HiSilicon, Interdigital | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244888 | Conclude to KI#1 of TR 33.743 - U2NW security setup |
pCR revised to S3-245264 |
Huawei, HiSilicon, Interdigital, China Telecom, Xiaomi | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244889 | New WID on ProSe Ph3 security |
WID new revised to S3-245320 |
Huawei, HiSilicon | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-244890 | Conclude KI#1 in TR 33.721 | pCR | Huawei, HiSilicon | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-244891 | Conclude KI#2 in TR 33.721 |
pCR revised to S3-245288 |
Huawei, HiSilicon | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-244892 | New solution about Multi-hop U2U Model A discovery in non-IP scenario |
pCR revised to S3-245266 |
Huawei, HiSilicon | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244893 | Draft CR TS 33.511 | draftCR | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
approved | [WTS] [JSN] | |
| S3-244894 | Draft CR TS 33.117 |
draftCR revised to S3-245332 |
Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
revised | [WTS] [JSN] | |
| S3-244895 | Draft CR TR33.926 |
draftCR revised to S3-245333 |
Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
revised | [WTS] [JSN] | |
| S3-244896 | Draft CR TS 33.514 | draftCR | Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
approved | [WTS] [JSN] | |
| S3-244897 | Discussion paper on SUCI error handling | discussion | Huawei, HiSilicon | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244898 | Addressing EN in KI#9 |
pCR revised to S3-245281 |
Huawei, HiSilicon | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244899 | Adding conclusion to KI#9 |
pCR revised to S3-245285 |
Huawei, HiSilicon | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244900 | Updating conclusion#5 |
pCR revised to S3-245283 |
Huawei, HiSilicon | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244901 | Updating conclusion#6 |
pCR revised to S3-245284 |
Huawei, HiSilicon | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244902 | General conclusion proposal | pCR | Huawei, HiSilicon | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244903 | Way forward | discussion | Huawei, HiSilicon | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
noted | [WTS] [JSN] | |
| S3-244904 | Notification about AKMA service disabling via NEF | CR | Huawei, HiSilicon | 33.535 18.5.0 CR#221 catF | AKMA_Ph2 | Rel-18 |
S3-119 AI: 4.1.5 |
not pursued | [WTS] [JSN] |
| S3-244905 | Correction to AAnF response without UE Identity | CR | Huawei, HiSilicon | 33.535 18.5.0 CR#222 catF | AKMA_Ph2 | Rel-18 |
S3-119 AI: 4.1.5 |
agreed | [WTS] [JSN] |
| S3-244906 | [33.180] MCRec ID Introduction |
CR revised to S3-245149 |
Airbus | 33.180 18.1.0 CR#215 catB | MCXSec4 | Rel-19 |
S3-119 AI: 4.6 |
revised | [WTS] [JSN] |
| S3-244907 | Authorization of direct AI/ML based Positioning UE data collection | pCR | OPPO | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-244908 | Solution on PHY key based protecting AIoT device identifiers |
pCR revised to S3-245298 |
OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244909 | Security Key Generation Using L1 Parameter |
pCR revised to S3-245297 |
OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244910 | New WID on Security for PLMN hosting a NPN |
WID new revised to S3-245373 |
China Telecomunication Corp., ZTE | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-244911 | Conclusion of Device Power Constrain Consideration | pCR | OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244912 | Authentication Using L1 Parameter |
pCR revised to S3-245173 |
OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244913 | Remove ENs and add evaluation in Solution #17 |
pCR revised to S3-245313 |
OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244914 | Discussion on security of LTM cell switch command MAC CE | discussion | OPPO | Rel-19 |
S3-119 AI: 4.12 |
noted | [WTS] [JSN] | ||
| S3-244915 | Corrections to Nudm_UEAuthentication_ResultConfirmation | CR | Ericsson | 33.501 18.7.0 CR#2075 catF | eNPN_Ph2 | Rel-18 |
S3-119 AI: 4.1.9 |
agreed | [WTS] [JSN] |
| S3-244916 | Security analysis of LTM cell switch command MAC CE |
other revised to S3-245336 |
OPPO | Rel-19 |
S3-119 AI: 4.12 |
revised | [WTS] [JSN] | ||
| S3-244917 | Corrections to Nudm_UEAuthentication_ResultConfirmation | CR | Ericsson | 33.501 19.0.0 CR#2076 catA | eNPN_Ph2 | Rel-19 |
S3-119 AI: 4.1.9 |
agreed | [WTS] [JSN] |
| S3-244918 | Authorization of a service request when the discovery is delegated to the target PLMN |
CR revised to S3-250351 |
Nokia | 33.501 19.0.0 CR#2077 catB | TEI19 | Rel-19 |
S3-119 AI: 4.11 |
not pursued | [WTS] [JSN] |
| S3-244919 | DP SBA Rel-19 public key retrieval for access token verification | discussion | Nokia | Rel-19 |
S3-119 AI: 4.11 |
noted | [WTS] [JSN] | ||
| S3-244920 | addressing the editor's note in solution#4 | pCR | Huawei, HiSilicon | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-244921 | conclusion on key issue#5 | pCR | Huawei, HiSilicon | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244922 | conclusion on key issue#1 | pCR | Huawei, HiSilicon | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-244923 | New WID on Ambient IoT security | WID new | Huawei, HiSilicon | Rel-19 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-244924 | conclusion assuming the PDCP anchor changing | other | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
merged | [WTS] [JSN] | |
| S3-244925 | reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 source LS: S2-2411049 LS To: SA2 |
Huawei, HiSilicon | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244926 | DRAFT CR SBA Rel-19 public key or cert retrieval for access token verification |
draftCR revised to S3-245334 |
Nokia | 5G_eSBA_Ph2 | Rel-19 |
S3-119 AI: 4.11 |
revised | [WTS] [JSN] | |
| S3-244927 | Input to SA for Reply LS on clarifications on consent management |
LS out LS To: SA revised to S3-245363 |
Nokia |
S3-119 AI: 3.2 |
revised | [WTS] [JSN] | |||
| S3-244928 | Addressing ENs on KI1.2 RO permission management in solution 7 |
pCR revised to S3-245226 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244929 | Update to KI1.3 Solution 29 on scope enhancing |
pCR revised to S3-245234 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244930 | Update to KI2 Solution 12 on security method retrieval in CAPIF interconnect |
pCR revised to S3-245246 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244931 | Update to KI2 Solution 13 on authentication aspect in CAPIF interconnect requesting security information from another CCF |
pCR revised to S3-245238 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244932 | Update to KI2 Solution 14 on authentication aspect in CAPIF interconnect when API invoker has not included CCF information |
pCR revised to S3-245239 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244933 | Update to KI2 Solution 15 on authorization token request handling in CAPIF interconnect |
pCR revised to S3-245240 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244934 | Update to KI2 Solution 16 on mapping an API invoker authorization request to the correct CCF in CAPIF interconnect |
pCR revised to S3-245247 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244935 | Update to KI5 Solution on authenticating multiple API invokers of the same RO |
pCR revised to S3-245254 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244936 | Informative annex for N6 delay measurement protocols | pCR | Nokia, Nokia Shanghai Bell | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
noted | [WTS] [JSN] |
| S3-244937 | KI4 Sol on Authentication of the origin API invoker in nested API invocation |
pCR revised to S3-245250 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244938 | New KI on Onboarding security issue |
pCR revised to S3-245255 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244939 | Solution on validation of correct GPSI in API invoker information |
pCR revised to S3-245371 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244940 | Correction of implementation mistake | pCR | Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244941 | Update of mapping table | pCR | Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244942 | Conclusion for KI#2.1 |
pCR revised to S3-245274 |
Nokia, Nokia Shanghai Bell | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244943 | Conclusion for KI#1.1 |
pCR revised to S3-245349 |
Nokia, Nokia Shanghai Bell | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-244944 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 |
China Mobile | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244945 | New solution for authentication in Ambient IoT service |
pCR revised to S3-245174 |
China Mobile | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244946 | New solution for key issue 3 |
pCR revised to S3-245351 |
China Mobile | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
revised | [WTS] [JSN] |
| S3-244947 | Discussion on RAN plenary LS on AIML | discussion | Qualcomm Incorporated |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244948 | Reply LS on AIML data collection |
LS out LS is reply to S3-244636 LS To: RAN |
Qualcomm Incorporated |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-244949 | Discussion on incoming SUCI LS | discussion | Qualcomm Incorporated |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244950 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to C1-245039 LS To: CT1 revised to S3-245137 |
Qualcomm Incorporated | 5GProtoc19 | Rel-19 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | |
| S3-244951 | Adding TWIF related text to the non-3GPP living document | other | Qualcomm Incorporated |
S3-119 AI: 4.13 |
merged | [WTS] [JSN] | |||
| S3-244952 | Certificate threats for split gNB |
other revised to S3-245158 |
Qualcomm Incorporated |
S3-119 AI: 4. |
revised | [WTS] [JSN] | |||
| S3-244953 | Adding certificate handling tests to SCAS for split gNB |
CR revised to S3-245093 |
Qualcomm Incorporated | 33.523 18.2.0 CR#9 catB | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
revised | [WTS] [JSN] |
| S3-244954 | Proposed privacy conclusion for split MME case |
pCR revised to S3-245215 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244955 | Proposed addition to the split MME conclusion for key issue #1 |
pCR revised to S3-245213 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244956 | Further additions to the enhancement of IOPs in solution #3 |
pCR revised to S3-245343 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244957 | Enhancing the conclusion of KI#1 |
pCR revised to S3-245258 |
Qualcomm Incorporated | 33.759 0.4.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
revised | [WTS] [JSN] |
| S3-244958 | reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 |
Qualcomm Incorporated | FS_AmbientIoT | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244959 | Addressing the EN in solution #15 |
pCR revised to S3-245314 |
Qualcomm Incorporated | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244960 | Addressing the EN in solution #27 | pCR | Qualcomm Incorporated | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244961 | reply LS on including the HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS out LS is reply to S3-244628 LS To: CT1 |
Qualcomm Incorporated | 5G_ProSe_Ph2 | Rel-18 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244962 | Addressing Ens in solution #16 |
pCR revised to S3-245261 |
Qualcomm Incorporated | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244963 | Conclusion of multi-hop U2N relay discovery security in KI#1 |
pCR revised to S3-245263 |
Qualcomm Incorporated | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244964 | Conclusion of multi-hop U2N relay communication security in KI#1 | pCR | Qualcomm Incorporated | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244965 | LS on security aspects related to protocols used in N6 delay measurements |
LS out LS To: SA2 revised to S3-245276 |
Nokia, Nokia Shanghai Bell |
S3-119 AI: 5.14 |
revised | [WTS] [JSN] | |||
| S3-244966 | UUAA in 5GS updates | draftCR | Ericsson | DUMMY | Rel-19 |
S3-119 AI: 5.11 |
noted | [WTS] [JSN] | |
| S3-244967 | [Draft] Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 source LS: S2-2411049 LS To: SA2 |
Beijing Xiaomi Mobile Software | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-244968 | Update to solution #16 in TR 33.713 |
pCR revised to S3-245301 |
Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244969 | Add evaluation for solution #16 in TR 33.713 |
pCR revised to S3-245302 |
Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244970 | Update to solution #18 in TR 33.713 | pCR | Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-244971 | Add evaluation for solution #18 in TR 33.713 |
pCR revised to S3-245303 |
Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244972 | Conclusion for KI#2 in TR 33.713 |
pCR revised to S3-245170 |
Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-244973 | [Draft] Reply LS on clarification on home network triggered re-authentication |
LS out LS is reply to S3-244632 source LS: C4-244496 LS To: CT4 |
Beijing Xiaomi Mobile Software | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244974 | Clarification for re-authentication notification response in HONTRA procedure | CR | Xiaomi | 33.501 18.7.0 CR#2078 catF | HN_Auth | Rel-18 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244975 | Clarification for re-authentication notification response in HONTRA procedure | CR | Xiaomi | 33.501 19.0.0 CR#2079 catA | HN_Auth | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244976 | Update to the conclusion for KI#1 in TR 33.700.29 |
pCR revised to S3-245214 |
Beijing Xiaomi Mobile Software | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-244977 | Update to the conclusion for KI#2 in TR 33.700.29 | pCR | Beijing Xiaomi Mobile Software | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244978 | Conclusion for KI#1 in TR 33.743 | pCR | Beijing Xiaomi Mobile Software | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244979 | Terminology Alignment and Consistency for Target UE | CR | Xiaomi | 33.533 18.4.0 CR#77 catF | Ranging_SL_Sec | Rel-18 |
S3-119 AI: 4.1.12 |
agreed | [WTS] [JSN] |
| S3-244980 | LTM: Requirement on AS Security Context Synchronization |
other revised to S3-245160 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244981 | LTM: Further Update to Solution 8 |
other revised to S3-245162 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244982 | LTM: Partial Conclusion on Key Issue 1 |
other revised to S3-245335 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244983 | LTM: Further Evaluation to Solution 7 | other | Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-244984 | LTM: Update to Overall Summary |
other revised to S3-245337 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-244985 | 33.721: New Solution for Key Issue 4 |
pCR revised to S3-245354 |
Xiaomi EV Technology | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-244986 | 33.721: Conclusion for Key Issue 2 | pCR | Xiaomi EV Technology | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-244987 | New conclusion for KI#1 | pCR | Ericsson | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244988 | Resolution of ENs and updates in Solution#16 | pCR | Ericsson | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244989 | Adding initial trust in CMPv2 initialization request |
CR revised to S3-245144 |
Nokia | 33.310 18.5.0 CR#205 catF | ACM_SBA | Rel-18 |
S3-119 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-244990 | Reply LS on Issues related to Analytics context transfer between AnLF(s) |
LS out LS is reply to S3-244638 LS To: SA2 |
CATT | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244991 | Conclusion update for KI#1 |
pCR revised to S3-245345 |
Ericsson | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
revised | [WTS] [JSN] |
| S3-244992 | Adding initial trust in CMPv2 initialization request |
CR revised to S3-245145 |
Nokia | 33.310 19.2.0 CR#206 catA | ACM_SBA | Rel-19 |
S3-119 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-244993 | Proposal way forward for eZTS | discussion | CATT, China Unicom, China Telecom | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
noted | [WTS] [JSN] | |
| S3-244994 | Resolution of Editor's Note in Solution#5 (Authorization of VFL participants involving NWDAF and AF) | pCR | Ericsson | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-244995 | Conclusion for KI#2 for the case that the NWDAF is the VFL Server | pCR | Ericsson | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
merged | [WTS] [JSN] |
| S3-244996 | pCR to TR33.700-29 Update conclusion#1 | pCR | CATT | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244997 | pCR to TR33.700-29 Update conclusion#2 | pCR | CATT | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-244998 | Reply LS on FS_5GSAT_Ph3_ARCH conclusions |
LS out LS is reply to S3-244645 LS To: SA2 revised to S3-245340 |
CATT | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] | |
| S3-244999 | pCR to TR33.713 Update solution#9 to remove EN | pCR | CATT | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-245000 | pCR to TR33.713 Update solution#30 to remove EN |
pCR revised to S3-245310 |
CATT | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-245001 | pCR to TR33.713 New solution general AIoT Device operation message protection procedure | pCR | CATT | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-245002 | Mutual Authentication Using AEAD for Inventory and Command case |
pCR revised to S3-245175 |
Xidian, OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-245003 | Presentation of Report to TSG: TR 33.754 Study on security aspects for multi-access (DualSteer + Access Traffic Steering, Switch and Splitting support in the 5G system architecture phase 4 (ATSSS Ph-4), Version 1.1.0 | TS or TR cover | Ericsson | FS_MASSS_Sec | Rel-19 |
S3-119 AI: 5.15 |
noted | [WTS] [JSN] | |
| S3-245004 | pCR to TR33.713 Conclusion#3 | pCR | CATT | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-245005 | pCR to TR33.713 Conclusion#4 | pCR | CATT | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-245006 | Discussion on the NF consumer PLMN ID check | discussion | Ericsson |
S3-119 AI: 4.1.2 |
noted | [WTS] [JSN] | |||
| S3-245007 | Checking PLMNID of NF Service Consumer in interconnect scenario | CR | Ericsson | 33.501 17.14.0 CR#2080 catF | TEI17 | Rel-17 |
S3-119 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
| S3-245008 | Checking PLMNID of NF Service Consumer in interconnect scenario | CR | Ericsson | 33.501 18.7.0 CR#2081 catA | TEI17 | Rel-18 |
S3-119 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
| S3-245009 | Checking PLMNID of NF Service Consumer in interconnect scenario | CR | Ericsson | 33.501 19.0.0 CR#2082 catA | TEI17 | Rel-19 |
S3-119 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
| S3-245010 | Draft_LS on Checking PLMNID of NFc in interconnect scenario |
LS out LS To: CT4 |
Ericsson | Rel-16 |
S3-119 AI: 4.1.2 |
noted | [WTS] [JSN] | ||
| S3-245011 | Public key distribution and Issuer claim verification of the Access Token | CR | Ericsson, Deutsche Telekom, AT&T, Samsung, BT PLC | 33.501 19.0.0 CR#2083 catB | TEI19 | Rel-19 |
S3-119 AI: 4.11 |
not pursued | [WTS] [JSN] |
| S3-245012 | Draft_LS reply to LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 |
Ericsson | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-245013 | New key issue for secure storage in AIoT devices | pCR | Ericsson | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-245014 | New Key Issue on Amplification of resource exhaustion by exploiting AIoT paging messages | pCR | Ericsson | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-245015 | New key issue for Authenticated and authorized access to devices in Ambient IoT via 3GPP core | pCR | Ericsson | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-245016 | New Solution to KI#5 | pCR | Ericsson | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-245017 | Addressing ENs in Solution#29 to KI#3 |
pCR revised to S3-245311 |
Ericsson | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-245018 | Evaluation of Solution#29 to KI#3 | pCR | Ericsson | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245019 | Living document for CryptoSP: draftCR to TS 33.501, Updates to cryptographic profiles | draftCR | Ericsson | CryptoSP | Rel-19 |
S3-119 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-245020 | Living document for CryptoSP: draftCR to TS 33.210, Updates to cryprographic profiles | draftCR | Ericsson | CryptoSP | Rel-19 |
S3-119 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-245021 | Living document for CryptoSP: draftCR to TS 33.310, Updates to cryptographic profiles | draftCR | Ericsson | CryptoSP | Rel-19 |
S3-119 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-245022 | Living document for CryptoSP: draftCR to TS 33.203, Updates to cryptographic profiles | draftCR | Ericsson | CryptoSP | Rel-19 |
S3-119 AI: 4.8 |
approved | [WTS] [JSN] | |
| S3-245023 | pCR to TR33.713 Conclusion#5 | pCR | CATT | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.11 |
withdrawn | [WTS] [JSN] |
| S3-245024 | pCR to TR33.743 Conclusion#1 | pCR | CATT | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-245025 | Living document on NR mobility enhancement |
draftCR revised to S3-245164 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-245026 | Conclusion for key issue#3 | pCR | Samsung, Lenovo | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-245027 | Conclusion update for KI#2 for DNS messages protection |
pCR revised to S3-245207 |
Samsung | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-245028 | Conclusion update for KI#2 in TR 33.757 | pCR | Samsung | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-245029 | [TR 33.757] Update to solution#20 | pCR | Samsung | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-245030 | [TR 33.700-22] Update to solution#24 |
pCR revised to S3-245244 |
Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245031 | [TR 33.700-22] Update to solution#27 |
pCR revised to S3-245251 |
Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245032 | [TR 33.700-22] Conclusion for Key issue#4 | pCR | Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-245033 | [TR 33.721] Update to solution#6 |
pCR revised to S3-245289 |
Samsung | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-245034 | [TR 33.721] Conclusion for Key issue#1 |
pCR revised to S3-245287 |
Samsung | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-245035 | [TR 33.721] Conclusion for Key issue#2 | pCR | Samsung | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-245036 | [TR 33.721] Conclusion for Key issue#3 | pCR | Samsung | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
noted | [WTS] [JSN] |
| S3-245037 | New WID on security aspects of 5G Mobile Metaverse services |
WID new revised to S3-245323 |
Samsung | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-245038 | [draft] Reply LS on AIML data collection |
LS out LS is reply to S3-244636 source LS: RP-242389 LS To: RAN revised to S3-245138 |
Samsung | Rel-19 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-245039 | Discussion on security procedure on S&F operation for a split MME architecture | pCR | Samsung | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-245040 | Update on KI#1 |
pCR revised to S3-245218 |
Samsung | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-245041 | Update on overall summary | pCR | Samsung | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-245042 | Resolving EN in solution #6 |
pCR revised to S3-245191 |
Samsung | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-245043 | Resolving EN in solution #22 | pCR | Samsung | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245044 | New solution on authentication and privacy of AIoT device |
pCR revised to S3-245177 |
Samsung | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-245045 | Discussion paper on SUCI calculation failure | discussion | Samsung | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-245046 | [draft] Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-244629 source LS: C1-245039 LS To: CT1 |
Samsung | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-245047 | New WID on Security Aspects of 5G Satellite Access Phase 3 |
WID new revised to S3-245356 |
CATT | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-245048 | Presentation of Report to TSG: TR 33.759 'Study on security enhancements of Uncrewed Aerial Systems (UAS) Phase 3', Version 1.0.0 |
TS or TR cover revised to S3-245370 |
Ericsson | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
revised | [WTS] [JSN] | |
| S3-245049 | pCR to TR33.713 Conclusion#5 | pCR | CATT | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-245050 | New solution for security aspects on user consent for policy update based on energy information | pCR | IIT Bombay | 33.766 0.4.0 | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-245051 | New solution for security aspects on user consent for energy information exposure/retrieval | pCR | IIT Bombay | 33.766 0.4.0 | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
noted | [WTS] [JSN] |
| S3-245052 | Resolving ENs in Solution #6 |
pCR revised to S3-245272 |
Ericsson | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-245053 | Resolving ENs in Solution #9 |
pCR revised to S3-245273 |
Ericsson | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-245054 | Conclusion for KI#2.1 | pCR | Ericsson | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
merged | [WTS] [JSN] |
| S3-245055 | LS reply on Issues related to Analytics context transfer between AnLF(s) |
LS out LS is reply to S3-244638 LS To: SA2 |
Ericsson | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-245056 | Conclusion on authorization of non-3GPP devices behind gateway UE or 5G-RG (KI#3) | pCR | Ericsson | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5. |
merged | [WTS] [JSN] |
| S3-245057 | Update to KI#1.2 |
pCR revised to S3-245232 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245058 | Resolving ENs and evaluation of Solution #11 |
pCR revised to S3-245227 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245059 | Resolving ENs and evaluation of Solution #22 |
pCR revised to S3-245243 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245060 | Update to Solution #25 and evaluation |
pCR revised to S3-245249 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245061 | Resolving EN and evaluation of Solution #26 |
pCR revised to S3-245252 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245062 | Remove normative language from test cases | draftCR | Keysight Technologies UK Ltd | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
approved | [WTS] [JSN] | |
| S3-245063 | Resolution of ENs on Authentication Result, Encryption and Command Protection | pCR | Lenovo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245064 | Resolution of EN on Temporary ID synchronization | pCR | Lenovo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245065 | Resolution of EN on group of devices | pCR | Lenovo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245066 | Update of solution#13 for key mismatch handling | pCR | Lenovo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245067 | Evaluation of Solution#13 | pCR | Lenovo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245068 | Solution#31 update - Addressing EN | pCR | Philips International B.V. | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245069 | Solution#31 update | pCR | Philips International B.V. | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245070 | Solution#1 update - Addressing EN | pCR | Philips International B.V. | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245071 | Solution#1 evaluation update | pCR | Philips International B.V. | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245072 | K#2 conclusion | pCR | Philips International B.V. | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-245073 | IMS Data Channel and LI | discussion | Ericsson | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-245074 | [Draft] Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-244646 LS To: SA4 |
Ericsson | Rel-18 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-245075 | HONTRA Error Handling | CR | Ericsson | 33.501 18.7.0 CR#2084 catF | HN_Auth | Rel-18 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-245076 | HONTRA Error Handling | CR | Ericsson | 33.501 19.0.0 CR#2085 catA | HN_Auth | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-245077 | [Draft] Reply LS on clarification on home network triggered re-authentication |
LS out LS To: CT4 |
Ericsson | HN_Auth | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-245078 | Resolution of EN in Solution #8 (Using security log events, counters and protocol signaling monitoring) | pCR | Ericsson | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-245079 | Resolution of EN in conclusions for KI#1 (Data exposure for security evaluation and monitoring) | pCR | Ericsson | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-245080 | Data collection for security monitoring | draftCR | Ericsson | DUMMY | Rel-19 |
S3-119 AI: 5.1 |
noted | [WTS] [JSN] | |
| S3-245081 | Resolution of EN in conclusions for KI#2 (Security mechanisms for policy enforcement at the 5G SBA) | pCR | Ericsson | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-245082 | Editorial update of conclusions for KI#1 (Data exposure for security evaluation and monitoring) | pCR | Ericsson | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
merged | [WTS] [JSN] |
| S3-245083 | Conclusion for KI#1: Third party specific user identities | pCR | Ericsson | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
merged | [WTS] [JSN] |
| S3-245084 | Discussion about the KI#2: Security of IMS based Avatar Communication | discussion | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
noted | [WTS] [JSN] | |
| S3-245085 | LS on IMS avatar communication |
LS out LS To: SA2 |
Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
noted | [WTS] [JSN] | |
| S3-245086 | Conclusion for KI#3: Security and privacy aspects of IMS DC capability exposure |
pCR revised to S3-245196 |
Ericsson | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-245087 | Presentation of Report to TSG: TR 33.790, Study on the security support for the next generation real time communication services phase 2, Version 0.6.0 |
TS or TR cover revised to S3-245357 |
Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
revised | [WTS] [JSN] | |
| S3-245088 | New WID on security support for the Next Generation Real Time Communication services Phase 2 |
WID new revised to S3-245326 |
Ericsson |
S3-119 AI: 6 |
revised | [WTS] [JSN] | |||
| S3-245089 | Conclusion for Key Issue#1 - Communication setup | pCR | Ericsson | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-245090 | Conclusion to KI#1 – multi-hop U2NW discovery | pCR | Ericsson | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-245091 | Update Solution #2 |
pCR revised to S3-245260 |
Ericsson | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-245092 | Update Solution#4 |
pCR revised to S3-245262 |
Ericsson | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-245093 | Adding certificate handling tests to SCAS for split gNB |
CR revision of S3-244953 revised to S3-245159 |
Qualcomm Incorporated | 33.523 18.2.0 CR#91 catB | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
revised | [WTS] [JSN] |
| S3-245094 | Protection of XRM metadata | discussion | Ericsson | Rel-19 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-245095 | New WID on MOBIKE for NTN 3GPP backhaul over the feeder link | WID new | Ericsson | Rel-19 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-245096 | New WID on Protection of XRM Metadata | WID new | Ericsson, Nokia, Nokia Shanghai Bell | Rel-19 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-245097 | MOBIKE for NTN 3GPP backhaul over feeder link | CR | Ericsson | 33.501 19.0.0 CR#2086 catB | DUMMY | Rel-19 |
S3-119 AI: 6 |
not pursued | [WTS] [JSN] |
| S3-245098 | Protecting XRM Metadata in QUIC aware forwarding | draftCR | Ericsson | DUMMY | Rel-19 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | |
| S3-245099 | Editorial updates for solution #6 | other | LG Electronics | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-245100 | Teminology updates regarding NR Femto Hosting Party | pCR | LG Electronics | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
merged | [WTS] [JSN] |
| S3-245101 | TR 35.937 skeleton | draft TR | THALES | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245102 | Changes to TS 35.234 | pCR | THALES | 35.234 0.2.0 | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] |
| S3-245103 | Changes to TS 35.235 | pCR | THALES | 35.235 0.2.0 | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] |
| S3-245104 | Content for TS 35.236 | pCR | THALES | 35.236 0.2.0 | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] |
| S3-245105 | Content for TR 35.937 | pCR | THALES | 35.937 1.0.0 | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] |
| S3-245106 | Discussion on Impact Analysis for Inter-CU LTM | discussion | Nokia, Nokia Shanghai Bell |
S3-119 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-245107 | New solution |
pCR revised to S3-245178 |
THALES | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-245108 | A user consent mechanism for data collection related to AIML-based positioning | pCR | Xiaomi communications | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
noted | [WTS] [JSN] |
| S3-245109 | Add evaluation for solution #8 of TR 33.700-22 |
pCR revised to S3-245229 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245110 | Add evaluation for solution #9 of TR 33.700-22 |
pCR revised to S3-245224 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245111 | Add evaluation for solution #18 of TR 33.700-22 |
pCR revised to S3-245241 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245112 | Add evaluation for solution #19 of TR 33.700-22 |
pCR revised to S3-245242 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245113 | Add evaluation for solution #20 of TR 33.700-22 | pCR | Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245114 | Authorization mechanism for nested API invocation |
pCR revised to S3-245253 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245115 | Resolve ENs for solution #8 of TR 33.700-22 |
pCR revised to S3-245230 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245116 | Resolve ENs for solution #9 of TR 33.700-22 |
pCR revised to S3-245225 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245117 | Conclusion for CAPIF 6 and CAPIF 6e security | pCR | Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-245118 | New WID on security aspects of CAPIF Phase3 | pCR | Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-245119 | Update conclusion for KI#2 | pCR | Xiaomi communications | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
merged | [WTS] [JSN] |
| S3-245120 | Remove ENs of solution#3 for KI#1 | pCR | Nokia, Nokia Shanghai Bell | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-245121 | Remove ENs of solution#9 for KI#3 |
pCR revised to S3-245355 |
Nokia, Nokia Shanghai Bell | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-245122 | Conclusion of KI#1 |
pCR revised to S3-245188 |
Nokia, Nokia Shanghai Bell | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-245123 | Conclusion of KI#3 | pCR | Nokia, Nokia Shanghai Bell | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
merged | [WTS] [JSN] |
| S3-245124 | Solution for KI#3 to authorize DA client to create digital asset |
pCR revised to S3-245290 |
Nokia, Nokia Shanghai Bell | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-245125 | olution for KI#3 to authorize VAL-S or VAL_C to access digital asset |
pCR revised to S3-245291 |
Nokia, Nokia Shanghai Bell | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-245126 | Solution for KI#4 to authorize avatar by metaverse service provider |
pCR revised to S3-245292 |
Nokia, Nokia Shanghai Bell | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-245127 | Support cleartext HPLMN ID in PC5 U2U relay discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 18.4.0 CR#210 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-245128 | Reply LS on including HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS out LS is reply to S3-244628 source LS: C1-244647 LS To: CT1 revised to S3-245136 |
Nokia, Nokia Shanghai Bell | 5G_ProSe_Ph2 | Rel-18 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | |
| S3-245129 | MonSTra Security Solution |
other revised to S3-245167 |
Ericsson, Vodafone, Nokia, Nokia Shanghai Bell, NSA, BT, Verizon |
S3-119 AI: 4.14 |
revised | [WTS] [JSN] | |||
| S3-245130 | New WID on security aspects of CAPIF Phase3 |
WID new revised to S3-245324 |
Xiaomi commnications | Rel-19 |
S3-119 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-245131 | Conclusion for Key Issue #5 | pCR | THALES | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-245132 | Authorization of external AF for Inventory |
pCR revised to S3-250144 |
NTT DOCOMO INC. | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-245133 | LS on draft-ietf-raw-technologies, "Reliable and Available Wireless Technologies | LS in | IETF |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-245134 | Agenda |
agenda revision of S3-244600 |
SA WG3 Chair |
S3-119 AI: 1 |
approved | [WTS] [JSN] | |||
| S3-245135 | Detailed agenda planning |
other revision of S3-244603 |
SA WG3 Chair |
S3-119 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-245136 | Reply LS on including HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS out LS is reply to S3-244628 source LS: C1-244647 LS To: CT1 revision of S3-245128 |
Nokia, Nokia Shanghai Bell | 5G_ProSe_Ph2 | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-245137 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-244629 LS To: CT1,Ct6 LS reply in C6-240721 revision of S3-244950 |
Qualcomm Incorporated | 5GProtoc19 | Rel-19 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | |
| S3-245138 | Reply LS on AIML data collection |
LS out LS is reply to S3-244636 source LS: RP-242389 LS To: RAN revision of S3-245038 |
Samsung | Rel-19 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-245139 | LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 revision of S3-244800 |
OPPO | Rel-19 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-245140 | Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-244646 LS To: SA4 revision of S3-244855 |
China Mobile | Rel-18 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-245141 | Reply LS to SA6 Internal 5G Core information expose to trusted AF |
LS out LS is reply to S3-244651 LS To: SA6 revision of S3-244844 |
Huawei, HiSilicon | Rel-18 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-245142 | New Study on 3GPP Cryptographic Inventory |
SID new revision of S3-244618 |
Nokia, Nokia Shanghai Bell |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | |||
| S3-245143 | Reauthentication aspect for IPSec in non 3GPP access |
CR revision of S3-244694 |
Nokia | 33.501 19.0.0 CR#20551 catF | TEI19 | Rel-19 |
S3-119 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-245144 | Adding initial trust in CMPv2 initialization request |
CR revision of S3-244989 |
Nokia | 33.310 18.5.0 CR#2051 catF | ACM_SBA | Rel-18 |
S3-119 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-245145 | Adding initial trust in CMPv2 initialization request |
CR revision of S3-244992 |
Nokia | 33.310 19.2.0 CR#2061 catA | ACM_SBA | Rel-19 |
S3-119 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-245146 | Redundant text in Annex I. |
CR revision of S3-244868 |
Nokia | 33.501 19.0.0 CR#20731 catD | eNPN_Ph2 | Rel-19 |
S3-119 AI: 4.1.9 |
agreed | [WTS] [JSN] |
| S3-245147 | Trust anchoring for N32-f/PRINS |
CR revision of S3-244668 |
BSI (DE), Nokia, Nokia Shanghai Bell | 33.501 19.0.0 CR#20531 catF | TEI19, Roaming5G | Rel-19 |
S3-119 AI: 4.1.14 |
agreed | [WTS] [JSN] |
| S3-245148 | [33.180] Additions to access token for recording authorization |
CR revision of S3-244655 |
Motorola Solutions, Airbus | 33.180 18.1.0 CR#2141 catB | MCXSec4 | Rel-19 |
S3-119 AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-245149 | [33.180] MCRec ID Introduction |
CR revision of S3-244906 |
Airbus | 33.180 18.1.0 CR#2151 catB | MCXSec4 | Rel-19 |
S3-119 AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-245150 | Updates to cryptographic profiles | CR | Ericsson, Nokia, Nokia Shanghai Bell | 33.501 19.0.0 CR#2087 catB | CryptoSP | Rel-19 |
S3-119 AI: 4.8 |
agreed | [WTS] [JSN] |
| S3-245151 | Updates to cryprographic profiles | CR | Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.210 18.1.0 CR#84 catB | CryptoSP | Rel-19 |
S3-119 AI: 4.8 |
agreed | [WTS] [JSN] |
| S3-245152 | Updates to cryptographic profiles | CR | Huawei, HiSilicon, Ericsson | 33.310 19.2.0 CR#207 catB | CryptoSP | Rel-19 |
S3-119 AI: 4.8 |
agreed | [WTS] [JSN] |
| S3-245153 | Updates to cryptographic profiles | CR | Deutsche Telekom AG, Huawei, HiSilicon, Ericsson | 33.203 18.1.0 CR#284 catB | CryptoSP | Rel-19 |
S3-119 AI: 4.8 |
agreed | [WTS] [JSN] |
| S3-245154 | Draft TS 35.234 | draft TS | Thales | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245155 | Draft TS 35.235 | draft TS | Thales | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245156 | Draft TS 35.236 | draft TS | Thales | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245157 | Draft TR 35.937 | draft TR | Thales | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245158 | Certificate threats for split gNB |
other revision of S3-244952 |
Qualcomm Incorporated |
S3-119 AI: 4. |
approved | [WTS] [JSN] | |||
| S3-245159 | Adding certificate handling tests to SCAS for split gNB |
CR revision of S3-245093 |
Qualcomm Incorporated | 33.523 18.2.0 CR#92 catB | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
agreed | [WTS] [JSN] |
| S3-245160 | LTM: Requirement on AS Security Context Synchronization |
other revision of S3-244980 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-245161 | Resolve the EN in Sol#3 |
other revision of S3-244753 |
ZTE Corporation | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-245162 | LTM: Further Update to Solution 8 |
other revision of S3-244981 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-245163 | New solution on Mismatch of UE security context |
other revision of S3-244731 |
vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-245164 | Living document on NR mobility enhancement |
draftCR revision of S3-245025 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-245165 | TWIF solution |
other revision of S3-244688 |
Nokia, Lenovo, Charter Communications | Non3GPPMob_Sec | Rel-19 |
S3-119 AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-245166 | Living document of the Non3GPPMobEnh study |
draftCR revision of S3-244686 |
Nokia | Non3GPPMob_Sec | Rel-19 |
S3-119 AI: 4.13 |
approved | [WTS] [JSN] | |
| S3-245167 | MonSTra Security Solution |
other revision of S3-245129 |
Ericsson, Vodafone, Nokia, Nokia Shanghai Bell, NSA, BT, Verizon |
S3-119 AI: 4.14 |
approved | [WTS] [JSN] | |||
| S3-245168 | Living document for MonStra: draftCR to TS 33.501, Signalling Monitoring |
draftCR revision of S3-244675 |
Vodafone | MonStra-Sec | Rel-19 |
S3-119 AI: 4.14 |
approved | [WTS] [JSN] | |
| S3-245169 | Draft TR 33.713 | draft TR | OPPO | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] | |
| S3-245170 | Conclusion for KI#2 in TR 33.713 |
pCR revision of S3-244972 |
Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-245171 | conclusion on key issue#5 | pCR | Huawei, HiSilicon | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
withdrawn | [WTS] [JSN] |
| S3-245172 | Solution to KI#3, KI#4 and KI#5 |
pCR revision of S3-244862 |
Nokia | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245173 | Authentication Using L1 Parameter |
pCR revision of S3-244912 |
OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245174 | New solution for authentication in Ambient IoT service |
pCR revision of S3-244945 |
China Mobile | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245175 | Mutual Authentication Using AEAD for Inventory and Command case |
pCR revision of S3-245002 |
Xidian, OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245176 | New Solution to KI#5 | pCR | Ericsson | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
withdrawn | [WTS] [JSN] |
| S3-245177 | New solution on authentication and privacy of AIoT device |
pCR revision of S3-245044 |
Samsung | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245178 | New solution |
pCR revision of S3-245107 |
THALES | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245179 | Draft TR 33.794 | draft TR | Motorola Mobility | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] | |
| S3-245180 | KI 1 Conclusion Clarification on Replay Use Case |
pCR revision of S3-244678 |
MITRE-FFRDC, US National Security Agency, Johns Hopkins University APL | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-245181 | Clarifications to Conclusion 1 |
pCR revision of S3-244721 |
U.S. National Security Agency, OTD_US, MITRE-FFRDC, Johns Hopkins University APL, Deutsche Telekom AG | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-245182 | Updates and Clean-up of KI#1 Conclusion |
pCR revision of S3-244609 |
Motorola Mobility [Rapporteur],Ericsson | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-245183 | New annex for security event data records |
pCR revision of S3-244626 |
Johns Hopkins University APL | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-245184 | General Recommendations for Conclusion 2 Policy Enforcement |
pCR revision of S3-244723 |
U.S. National Security Agency,OTD_US, Johns Hopkins University APL, MITRE-FFRDC | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-245185 | Cleanup of TR 33.794 |
pCR revision of S3-244611 |
Motorola Mobility [Rapporteur] | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-245186 | Draft TR 33.790 | draft TR | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-245187 | Draft TR 33.757 | draft TR | China Telecom | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
approved | [WTS] [JSN] | |
| S3-245188 | Conclusion of KI#1 |
pCR revision of S3-245122 |
Nokia, Nokia Shanghai Bell | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-245189 | Draft TR 33.776 | draft TR | Cisco | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] | |
| S3-245190 | Addressing the ENs on Avatar ID determination and token details of Solution#5 |
pCR revision of S3-244808 |
Huawei, HiSilicon | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-245191 | Resolving EN in solution #6 |
pCR revision of S3-245042 |
Samsung | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-245192 | Draft TR 33.700-29 | draft TR | CATT | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] | |
| S3-245193 | Draft TR 33.700-32 | draft TR | Interdigital | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5. |
approved | [WTS] [JSN] | |
| S3-245194 | Draft TR 33.759 | draft TR | Ericsson | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
approved | [WTS] [JSN] | |
| S3-245195 | Draft TR 33.743 | draft TR | Huawei | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-245196 | Conclusion for KI#3: Security and privacy aspects of IMS DC capability exposure |
pCR revision of S3-245086 |
Ericsson | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-245197 | Draft TR 33.784 | draft TR | China Mobile | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] | |
| S3-245198 | Draft TR 33.749 | draft TR | China Unicom | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
approved | [WTS] [JSN] | |
| S3-245199 | Draft TR 33.766 | draft TR | Ericsson | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
approved | [WTS] [JSN] | |
| S3-245200 | Removing EN in Sol#2 |
pCR revision of S3-244797 |
China Telecomunication Corp. | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-245201 | Updates to Solution#11 |
pCR revision of S3-244613 |
Lenovo | 33.757 0.5.0 | FS_eZTS, PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-245202 | [TR 33.757] Update to solution#20 | pCR | Samsung | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
withdrawn | [WTS] [JSN] |
| S3-245203 | Draft TR 33.745 | draft TR | ZTE | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] | |
| S3-245204 | Draft TR 33.721 | draft TR | Samsung | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
approved | [WTS] [JSN] | |
| S3-245205 | Draft TR 33.700-22 | draft TR | Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-245206 | Conclusion to KI#2 |
pCR revision of S3-244796 |
China Telecomunication Corp., ZTE, China Unicom, CATT | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-245207 | Conclusion update for KI#2 for DNS messages protection |
pCR revision of S3-245027 |
Samsung | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-245208 | conclusion on key issue#3 |
pCR revision of S3-244882 |
Huawei, HiSilicon | 33.757 0.5.0 | PLMNNPN_SEC | Rel-19 |
S3-119 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-245209 | Conclusion for KI#1: ACME initial trust framework |
pCR revision of S3-244680 |
Cisco Systems | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-245210 | Conclusion for KI#2 (Secure Transport of Messages) |
pCR revision of S3-244659 |
Google Ireland Limited | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-245211 | Conclusion for KI#4 (Certificate enrolment) |
pCR revision of S3-244657 |
Google Ireland Limited | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-245212 | Additional conclusions for KI#1 |
pCR revision of S3-244608 |
InterDigital Belgium. LLC | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245213 | Proposed addition to the split MME conclusion for key issue #1 |
pCR revision of S3-244955 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245214 | Update to the conclusion for KI#1 in TR 33.700.29 |
pCR revision of S3-244976 |
Beijing Xiaomi Mobile Software | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245215 | Proposed privacy conclusion for split MME case |
pCR revision of S3-244954 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
noted | [WTS] [JSN] |
| S3-245216 | Address EN in solution 31 |
pCR revision of S3-244733 |
vivo | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245217 | Adding solution to KI#2 |
pCR revision of S3-244755 |
ZTE Corporation | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245218 | Update on KI#1 |
pCR revision of S3-245040 |
Samsung | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245219 | Updates to Overall Summary of solutions |
pCR revision of S3-244790 |
Nokia | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245220 | Adding evaluation to Solution 2 |
pCR revision of S3-244833 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245221 | Updates to Solution #5 |
pCR revision of S3-244617 |
Lenovo | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245222 | Conclusion to KI#1.1 |
pCR revision of S3-244837 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245223 | Update and evaluate solution #6 in TR 33.700-22 |
pCR revision of S3-244779 |
China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245224 | Add evaluation for solution #9 of TR 33.700-22 |
pCR revision of S3-245110 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245225 | Resolve ENs for solution #9 of TR 33.700-22 |
pCR revision of S3-245116 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245226 | Addressing ENs on KI1.2 RO permission management in solution 7 |
pCR revision of S3-244928 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245227 | Resolving ENs and evaluation of Solution #11 |
pCR revision of S3-245058 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245228 | Adding evaluation to Solution 4 |
pCR revision of S3-244835 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245229 | Add evaluation for solution #8 of TR 33.700-22 |
pCR revision of S3-245109 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245230 | Resolve ENs for solution #8 of TR 33.700-22 |
pCR revision of S3-245115 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245231 | Conclusion to KI#1.2 |
pCR revision of S3-244838 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245232 | Update to KI#1.2 |
pCR revision of S3-245057 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-245233 | Adding evaluation to Solution 10 |
pCR revision of S3-244836 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245234 | Update to KI1.3 Solution 29 on scope enhancing |
pCR revision of S3-244929 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245235 | Conclusion to KI#1.3 |
pCR revision of S3-244839 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245236 | Updates to Solution #21 |
pCR revision of S3-244616 |
Lenovo | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245237 | Evaluation for the Solution 23 |
pCR revision of S3-244772 |
ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245238 | Update to KI2 Solution 13 on authentication aspect in CAPIF interconnect requesting security information from another CCF |
pCR revision of S3-244931 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245239 | Update to KI2 Solution 14 on authentication aspect in CAPIF interconnect when API invoker has not included CCF information |
pCR revision of S3-244932 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245240 | Update to KI2 Solution 15 on authorization token request handling in CAPIF interconnect |
pCR revision of S3-244933 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245241 | Add evaluation for solution #18 of TR 33.700-22 |
pCR revision of S3-245111 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245242 | Add evaluation for solution #19 of TR 33.700-22 |
pCR revision of S3-245112 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245243 | Resolving ENs and evaluation of Solution #22 |
pCR revision of S3-245059 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245244 | [TR 33.700-22] Update to solution#24 |
pCR revision of S3-245030 |
Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245245 | Update sol#17 |
pCR revision of S3-244829 |
China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245246 | Update to KI2 Solution 12 on security method retrieval in CAPIF interconnect |
pCR revision of S3-244930 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245247 | Update to KI2 Solution 16 on mapping an API invoker authorization request to the correct CCF in CAPIF interconnect |
pCR revision of S3-244934 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245248 | Conclusion on KI#2 |
pCR revision of S3-244776 |
ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245249 | Update to Solution #25 and evaluation |
pCR revision of S3-245060 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245250 | KI4 Sol on Authentication of the origin API invoker in nested API invocation |
pCR revision of S3-244937 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245251 | [TR 33.700-22] Update to solution#27 |
pCR revision of S3-245031 |
Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245252 | Resolving EN and evaluation of Solution #26 |
pCR revision of S3-245061 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245253 | Authorization mechanism for nested API invocation |
pCR revision of S3-245114 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245254 | Update to KI5 Solution on authenticating multiple API invokers of the same RO |
pCR revision of S3-244935 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245255 | New KI on Onboarding security issue |
pCR revision of S3-244938 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245256 | New solution for UAV triggered UUAA |
pCR revision of S3-244840 |
Huawei, HiSilicon | 33.759 0.4.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-245257 | New solution for USS triggered UUAA |
pCR revision of S3-244841 |
Huawei, HiSilicon | 33.759 0.4.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
approved | [WTS] [JSN] |
| S3-245258 | Enhancing the conclusion of KI#1 |
pCR revision of S3-244957 |
Qualcomm Incorporated | 33.759 0.4.0 | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
noted | [WTS] [JSN] |
| S3-245259 | LS on Multi-hop U2N Relay Architecture Aspects |
LS out LS To: SA2 revision of S3-244674 |
InterDigital France R&D, SAS | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-245260 | Update Solution #2 |
pCR revision of S3-245091 |
Ericsson | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-245261 | Addressing Ens in solution #16 |
pCR revision of S3-244962 |
Qualcomm Incorporated | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-245262 | Update Solution#4 |
pCR revision of S3-245092 |
Ericsson | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-245263 | Conclusion of multi-hop U2N relay discovery security in KI#1 |
pCR revision of S3-244963 |
Qualcomm Incorporated | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-245264 | Conclude to KI#1 of TR 33.743 - U2NW security setup |
pCR revision of S3-244888 |
Huawei, HiSilicon, Interdigital, China Telecom, Xiaomi | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-245265 | Update to KI#2 conclusion of TR 33.743 |
pCR revision of S3-244886 |
Huawei, HiSilicon | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-245266 | New solution about Multi-hop U2U Model A discovery in non-IP scenario |
pCR revision of S3-244892 |
Huawei, HiSilicon | 33.743 0.4.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-245267 | Cover sheet Draft TR 33.743 | TS or TR cover | Huawei | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-119 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-245268 | TR 33.700-32 Conclusion for Key Issue#3, Cablelabs, Lenovo |
pCR revision of S3-244677 |
InterDigital France R&D, SAS | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5. |
approved | [WTS] [JSN] |
| S3-245269 | Additional Conclusion for key issue#2 |
pCR revision of S3-244743 |
vivo, Nokia, Nokia Shanghai Bell, China Mobile, China Telecom, China Unicom, Xiaomi | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-245270 | Additional Conclusion for key Issue#3 |
pCR revision of S3-244744 |
vivo, China Mobile, China Telecom, China Unicom | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-245271 | Update KI #1 of TR 33.784 |
pCR revision of S3-244849 |
OPPO | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-245272 | Resolving ENs in Solution #6 |
pCR revision of S3-245052 |
Ericsson | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-245273 | Resolving ENs in Solution #9 |
pCR revision of S3-245053 |
Ericsson | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-245274 | Conclusion for KI#2.1 |
pCR revision of S3-244942 |
Nokia, Nokia Shanghai Bell | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-245275 | Add specific UDR SCAS test cases for TS 33.530 |
pCR revision of S3-244792 |
BSI (DE) | 33.530 0.1.0 | SCAS_5G_UDR | Rel-19 |
S3-119 AI: 4.2 |
approved | [WTS] [JSN] |
| S3-245276 | LS on security aspects related to protocols used in N6 delay measurements |
LS out LS To: SA2 revision of S3-244965 |
Nokia, Nokia Shanghai Bell |
S3-119 AI: 5.14 |
approved | [WTS] [JSN] | |||
| S3-245277 | Cover Sheet for TR 33.754 |
TS or TR cover revision of S3-244787 |
Intel Corporation (UK) Ltd | FS_MASSS_Sec | Rel-19 |
S3-119 AI: 5.15 |
approved | [WTS] [JSN] | |
| S3-245278 | Resolution of ENs concerning compliance to regional legislation when collecting and exposing user energy consumption information. |
pCR revision of S3-244859 |
Nokia, Deutsche Telekom | 33.766 0.4.0 | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-245279 | Notification about AKMA service disabling via NEF | CR | Huawei, HiSilicon | 33.535 18.5.0 CR#2211 catF | AKMA_Ph2 | Rel-18 |
S3-119 AI: 4.1.5 |
withdrawn | [WTS] [JSN] |
| S3-245280 | Add standardized format for security event logs into conclusion of KI#1 | pCR | Johnn Hopkina | 33.794 0.5.0 | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] |
| S3-245281 | Addressing EN in KI#9 |
pCR revision of S3-244898 |
Huawei, HiSilicon | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-245282 | Updates to conclusions for Key Issue #1 |
pCR revision of S3-244798 |
Nokia | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-245283 | Updating conclusion#5 |
pCR revision of S3-244900 |
Huawei, HiSilicon | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-245284 | Updating conclusion#6 |
pCR revision of S3-244901 |
Huawei, HiSilicon | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-245285 | Adding conclusion to KI#9 |
pCR revision of S3-244899 |
Huawei, HiSilicon | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-245286 | Cover sheet draft TR 33.745 for approval | TS or TR cover | ZTE | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] | |
| S3-245287 | [TR 33.721] Conclusion for Key issue#1 |
pCR revision of S3-245034 |
Samsung | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-245288 | Conclude KI#2 in TR 33.721 |
pCR revision of S3-244891 |
Huawei, HiSilicon | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-245289 | [TR 33.721] Update to solution#6 |
pCR revision of S3-245033 |
Samsung | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-245290 | Solution for KI#3 to authorize DA client to create digital asset |
pCR revision of S3-245124 |
Nokia, Nokia Shanghai Bell | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-245291 | olution for KI#3 to authorize VAL-S or VAL_C to access digital asset |
pCR revision of S3-245125 |
Nokia, Nokia Shanghai Bell | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-245292 | Solution for KI#4 to authorize avatar by metaverse service provider |
pCR revision of S3-245126 |
Nokia, Nokia Shanghai Bell | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-245293 | Cover sheet draft TR 35.234 | TS or TR cover | Thales | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245294 | Cover sheet draft TR 35.235 | TS or TR cover | Thales | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245295 | Cover sheet draft TR 35.236 | TS or TR cover | Thales | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245296 | KI#4, New Sol Communication Security of intermediate UE interacting with AIoT device |
pCR revision of S3-244736 |
vivo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245297 | Security Key Generation Using L1 Parameter |
pCR revision of S3-244909 |
OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245298 | Solution on PHY key based protecting AIoT device identifiers |
pCR revision of S3-244908 |
OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245299 | KI#1, New Sol Disable AIoT device |
pCR revision of S3-244737 |
vivo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245300 | Resolving EN from Sol#5 |
pCR revision of S3-244788 |
OPPO, Xidian | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245301 | Update to solution #16 in TR 33.713 |
pCR revision of S3-244968 |
Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245302 | Add evaluation for solution #16 in TR 33.713 |
pCR revision of S3-244969 |
Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245303 | Add evaluation for solution #18 in TR 33.713 |
pCR revision of S3-244971 |
Beijing Xiaomi Mobile Software | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245304 | Resolution of ENs in Solution #21 |
pCR revision of S3-244671 |
InterDigital Belgium. LLC | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245305 | Resolution of ENs in Solution #20 |
pCR revision of S3-244672 |
InterDigital Belgium. LLC | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245306 | Ambient IoT solution on privacy revision |
pCR revision of S3-244709 |
Apple | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245307 | Resolving ENs in sol#25 in TR 33.713 |
pCR revision of S3-244761 |
ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245308 | Adding evaluation to sol#25 in TR 33.713 |
pCR revision of S3-244762 |
ZTE Corporation | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245309 | Solution 26 Update and Evaluation |
pCR revision of S3-244806 |
Sony | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245310 | pCR to TR33.713 Update solution#30 to remove EN |
pCR revision of S3-245000 |
CATT | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245311 | Addressing ENs in Solution#29 to KI#3 |
pCR revision of S3-245017 |
Ericsson | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245312 | Solution 14 Update and Evaluation |
pCR revision of S3-244819 |
Sony | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245313 | Remove ENs and add evaluation in Solution #17 |
pCR revision of S3-244913 |
OPPO | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245314 | Addressing the EN in solution #15 |
pCR revision of S3-244959 |
Qualcomm Incorporated | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245315 | Ambient IoT solution on mutual authentication revision |
pCR revision of S3-244710 |
Apple | 33.713 0.3.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245316 | KI#5, Solution update on AIoT device authentication |
pCR revision of S3-244735 |
vivo | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245317 | Conclusion for KI#7: Supporting all 5G SBA certificate types |
pCR revision of S3-244681 |
Cisco Systems | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-245318 | Presentation of Specification/Report to TSG: TR 33.776, Version 1.0.0 |
TS or TR cover revision of S3-244682 |
Cisco Systems | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] | |
| S3-245319 | New WID on enablers for Zero Trust Security in SBA |
WID new revision of S3-244615 |
Motorola Mobility [Rapporteur] | Rel-19 |
S3-119 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-245320 | New WID on ProSe Ph3 security |
WID new revision of S3-244889 |
Huawei, HiSilicon | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-245321 | New WID on UAS security enhancements |
WID new revision of S3-244848 |
Ericsson | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-245322 | New WID on Security aspects of Core Network Enhanced Support for AIML |
WID new revision of S3-244856 |
China Mobile, vivo | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-245323 | New WID on security aspects of 5G Mobile Metaverse services |
WID new revision of S3-245037 |
Samsung | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-245324 | New WID on security aspects of CAPIF Phase3 |
WID new revision of S3-245130 |
Xiaomi communications | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-245325 | WID on security aspects of 5G NR Femto |
WID new revision of S3-244777 |
ZTE Corporation | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-245326 | New WID on security support for the Next Generation Real Time Communication services Phase 2 |
WID new revision of S3-245088 |
Ericsson,China Mobile |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | |||
| S3-245327 | Release 20 Planning | other | WG Chair |
S3-119 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-245328 | Correction and clarification of TC_AMF_NAS_INTEGRITY_FAILURE |
draftCR revision of S3-244667 |
BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-245329 | MnF User session timeout | draftCR | Keysight Technologies UK Ltd | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4.1.1 |
withdrawn | [WTS] [JSN] | |
| S3-245330 | Draft TS 33.530 | draft TS | BSI | SCAS_5G_UDR | Rel-19 |
S3-119 AI: 4.2 |
approved | [WTS] [JSN] | |
| S3-245331 | Cover sheet TR 35.937 | TS or TR cover | Thales | Milenage_256 | Rel-19 |
S3-119 AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-245332 | Draft CR TS 33.117 |
draftCR revision of S3-244894 |
Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
approved | [WTS] [JSN] | |
| S3-245333 | Draft CR TR33.926 |
draftCR revision of S3-244895 |
Huawei, HiSilicon | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
approved | [WTS] [JSN] | |
| S3-245334 | DRAFT CR SBA Rel-19 public key or cert retrieval for access token verification |
draftCR revision of S3-244926 |
Ericsson, Deutsche Telekom, AT&T, Samsung, BT PLC, KDDI, Huawei, NCSC, Nokia | 5G_eSBA_Ph2 | Rel-19 |
S3-119 AI: 4.11 |
approved | [WTS] [JSN] | |
| S3-245335 | LTM: Partial Conclusion on Key Issue 1 |
other revision of S3-244982 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-245336 | Security analysis of LTM cell switch command MAC CE |
other revision of S3-244916 |
OPPO | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-245337 | LTM: Update to Overall Summary |
other revision of S3-244984 |
Xiaomi EV Technology | NR_Mob_Ph4_Sec | Rel-19 |
S3-119 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-245338 | Non3GPPMobEnh enhancement | CR | Nokia | 33.501 19.0.0 CR#2088 catB | Non3GPPMob_Sec | Rel-19 |
S3-119 AI: 4.13 |
agreed | [WTS] [JSN] |
| S3-245339 | Security of Signalling Traffic Monitoring |
CR revised to SP-241769, SP-241971 |
Vodafone, Nokia, Nokia Shanghai Bell, Ericsson, Telefonica, Telecom Italia | 33.501 19.0.0 CR#2089 catB | MonStra-Sec | Rel-19 |
S3-119 AI: 4.14 |
agreed | [WTS] [JSN] |
| S3-245340 | Reply LS on FS_5GSAT_Ph3_ARCH conclusions |
LS out LS is reply to S3-244645 LS To: SA2 revision of S3-244998 |
CATT | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] | |
| S3-245341 | Update of conclusions KI#1 |
pCR revision of S3-244814 |
Huawei, HiSilicon | 33.700-29 0.5.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245342 | New WID on Security Aspects of Enhancement of Support for Edge Computing in 5GC — phase 3 |
WID new revision of S3-244782 |
China Unicom, Huawei, HiSilicon |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | |||
| S3-245343 | Further additions to the enhancement of IOPs in solution #3 |
pCR revision of S3-244956 |
Qualcomm Incorporated | 33.700-29 0.4.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-119 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-245344 | New solution on combined authentication and data protection for Ambient IoT services |
pCR revision of S3-244669 |
KPN N.V. | 33.713 0.4.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-245345 | Conclusion update for KI#1 |
pCR revision of S3-244991 |
Ericsson | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-245346 | Update of Conclusion on Key issue #1 |
pCR revision of S3-244871 |
Huawei, HiSilicon | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-245347 | TR clean up |
pCR revision of S3-244745 |
vivo | 33.784 0.4.0 | FS_AIML_CN_SEC | Rel-19 |
S3-119 AI: 5.13 |
approved | [WTS] [JSN] |
| S3-245348 | Solving the problem of generating and forwarding the salt to the BSF |
pCR revision of S3-244813 |
Huawei, HiSilicon | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-245349 | Conclusion for KI#1.1 |
pCR revision of S3-244943 |
Nokia, Nokia Shanghai Bell | 33.749 0.4.0 | FS_EDGE_Ph3 | Rel-19 |
S3-119 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-245350 | Regional legislation compliance in relation to collection of user information. |
pCR revision of S3-244860 |
Nokia, Deutsche Telekom | 33.766 0.4.0 | FS_Energy_Sec | Rel-19 |
S3-119 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-245351 | New solution for key issue 3 |
pCR revision of S3-244946 |
China Mobile | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-245352 | Updates to conclusions for Key Issue #3 |
pCR revision of S3-244818 |
Nokia | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-245353 | Remove the EN in stable conclusions |
pCR revision of S3-244769 |
ZTE Corporation | 33.745 0.4.0 | FS_5G_Femto_Sec | Rel-19 |
S3-119 AI: 5.17 |
approved | [WTS] [JSN] |
| S3-245354 | 33.721: New Solution for Key Issue 4 |
pCR revision of S3-244985 |
Xiaomi EV Technology | 33.721 0.4.0 | FS_Metaverse_Sec | Rel-19 |
S3-119 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-245355 | Remove ENs of solution#9 for KI#3 |
pCR revision of S3-245121 |
Nokia, Nokia Shanghai Bell | 33.790 0.5.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-245356 | New WID on Security Aspects of 5G Satellite Access Phase 3 |
WID new revision of S3-245047 |
CATT | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-245357 | Presentation of Report to TSG: TR 33.790, Study on the security support for the next generation real time communication services phase 2, Version 0.6.0 |
TS or TR cover revision of S3-245087 |
Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119 AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-245358 | Adding certificate test cases to TS 33.511 | CR | Huawei; HiSilicon, CAICT, CTCC, Nokia, | 33.511 18.3.0 CR#13 catB | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
agreed | [WTS] [JSN] |
| S3-245359 | Adding threat about certificate verification to TR 33.926 | CR | Huawei; HiSilicon, CAICT, CTCC, Nokia | 33.926 19.2.0 CR#34 catB | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
agreed | [WTS] [JSN] |
| S3-245360 | Corrections and test case updating to TS 33.117 | CR | Huawei; HiSilicon, BSI (DE), Nokia, Nokia Shanghai Bell | 33.117 18.3.0 CR#198 catB | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
agreed | [WTS] [JSN] |
| S3-245361 | Updating test case about authentication status of UE by UDM | CR | Huawei; HiSilicon, CAICT, CTCC, Nokia | 33.514 18.3.0 CR#32 catF | SCAS_5G_Maint | Rel-19 |
S3-119 AI: 4. |
agreed | [WTS] [JSN] |
| S3-245362 | Technical Content for 3GPP Cryptographic Inventory |
other revision of S3-244621 |
Nokia, Nokia Shanghai Bell |
S3-119 AI: 3.2 |
noted | [WTS] [JSN] | |||
| S3-245363 | Input to SA for Reply LS on clarifications on consent management |
LS out LS To: SA revision of S3-244927 |
Nokia |
S3-119 AI: 3.2 |
approved | [WTS] [JSN] | |||
| S3-245364 | Living Document to TS 33.518 NRF SCAS |
draftCR revision of S3-244662 |
BSI (DE) | SCAS_5G_Maint | Rel-18 |
S3-119 AI: 4.1.1 |
approved | [WTS] [JSN] | |
| S3-245365 | Presentation of Specification/Report to TSG for TR 33.794 |
TS or TR cover revision of S3-244612 |
Motorola Mobility [Rapporteur] | FS_eZTS | Rel-19 |
S3-119 AI: 5.1 |
approved | [WTS] [JSN] | |
| S3-245366 | Pre-authorization solution for ACME |
pCR revision of S3-244673 |
NCSC | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-245367 | Evaluation update for solution #9 (Using ACME protocol for certificate renewal) |
pCR revision of S3-244656 |
Google Ireland Limited | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-245368 | Conclusion for KI#5 (Certificate Renewal) |
pCR revision of S3-244658 |
Google Ireland Limited | 33.776 0.5.0 | FS_ACME_SBA | Rel-19 |
S3-119 AI: 5.4 |
approved | [WTS] [JSN] |
| S3-245369 | Cover Sheet TR 33.700-32 |
TS or TR cover revision of S3-244676 |
InterDigital France R&D, SAS | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5. |
approved | [WTS] [JSN] | |
| S3-245370 | Presentation of Report to TSG: TR 33.759 'Study on security enhancements of Uncrewed Aerial Systems (UAS) Phase 3', Version 1.0.0 |
TS or TR cover revision of S3-245048 |
Ericsson | FS_UAS_Ph3_Sec | Rel-19 |
S3-119 AI: 5.11 |
approved | [WTS] [JSN] | |
| S3-245371 | Solution on validation of correct GPSI in API invoker information |
pCR revision of S3-244939 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245372 | New WID on Automatic Certificate Management Environment (ACME) for the Service Based Architecture (SBA) |
WID new revision of S3-244683 |
Cisco Systems | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-245373 | New WID on Security for PLMN hosting a NPN |
WID new revision of S3-244910 |
China Telecomunication Corp., ZTE | Rel-19 |
S3-119 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-250001 | Agenda | agenda | SA WG3 Chair |
S3-119-e AI: 1 |
approved | [WTS] [JSN] | |||
| S3-250002 | Process for SA3#119AdHoc-e | other | SA WG3 Chair |
S3-119-e AI: 1 |
noted | [WTS] [JSN] | |||
| S3-250003 | Detailed agenda planning | other | SA WG3 Chair |
S3-119-e AI: 1 |
noted | [WTS] [JSN] | |||
| S3-250004 | LS on security aspects of Ambient IoT | LS in | S2-2411049 |
S3-119-e AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-250005 | LS on RAN2 outcome of Ambient IoT study | LS in | R2-2411263 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250006 | Reply to LS on Further Clarification for Ambient IoT Security | LS in | S1-244920 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250007 | LS on A-IoT Conclusions in SA WG2 | LS in | S2-2413035 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250008 | Reply LS on terminology alignment between SA6 and SA3 | LS in | S6-245644 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250009 | Reply LS on clarifications on consent management | LS in | SP-241934 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250010 | New KI: Reader Authorization for 5G Ambient IoT Services | pCR | InterDigital, Inc. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250011 | KI#3, Conclusions | pCR | Sony | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250012 | KI#5, Conclusions | pCR | Sony | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250013 | Conclusion to key issue#1 |
pCR revised to S3-250195 |
Lenovo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250014 | Conclusion to key issue#3 | pCR | Lenovo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250015 | Conclusion to key issue#4 | pCR | Lenovo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250016 | Conclusion to key issue#5 | pCR | Lenovo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250017 | KI#1.1-Further conclusions on ROF authentication |
pCR revised to S3-250182 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250018 | KI#1.2-Further conclusions on authorization information | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250019 | KI#1.3-Further conclusions on granularity | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250020 | remove EN for KI#1.1 | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250021 | remove EN for KI#1.2 | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250022 | remove EN in clause 6.4 |
pCR revised to S3-250212 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250023 | editorial corrections in clauses 6.2 and 6.10 |
pCR revised to S3-250216 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250024 | Resolving ENs in sol#6 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250025 | Evaluation for solution 6 |
pCR revised to S3-250208 |
ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250026 | Update the KI#2 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250027 | Update the KI#3 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250028 | Update the scope in TR 33.713 |
pCR revised to S3-250209 |
ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250029 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250030 | Conclusion for KI#2 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250031 | Conclusion for KI#3 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250032 | Conclusion for KI#4 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250033 | Conclusion for KI#5 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250034 | Conclusion for KI#3 |
pCR revised to S3-250211 |
ZTE Corporation | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250035 | Update to the conclusion for KI#1.2 | pCR | ZTE Corporation | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250036 | Update to the conclusion for KI#2 | pCR | ZTE Corporation | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250037 | Updates to Solution#21 |
pCR revised to S3-250187 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250038 | Solution to address KI#6 |
pCR revised to S3-250191 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250039 | Conclusion for KI#2 | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250040 | Update sol#17 to resolve EN | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250041 | Conclusion on AIOT KI#3 |
pCR revised to S3-250224 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250042 | Update AIOT KI#3 | pCR | OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250043 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-250004/S2-2411049 LS To: SA2 |
OPPO | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250044 | addressing the editor's note in solution#4 |
pCR revised to S3-250203 |
Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250045 | Discussion paper on the conclusion on key issue#5 | pCR | Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250046 | conclusion on key issue#4 |
pCR revised to S3-250206 |
Huawei, HiSilicon, OPPO, China Unicom | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250047 | Generic conclusion on AIoT |
pCR revised to S3-250204 |
Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250048 | Resolve various EN's for KI#1 | pCR | Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250049 | Conclusion for KI#1 | pCR | Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250050 | conclusion to KI#2 | pCR | Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250051 | Update on Solution #6-Digital asset request validation | pCR | Huawei, HiSilicon | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
noted | [WTS] [JSN] |
| S3-250052 | Conclusion to KI#3 in TR 33.721 | pCR | Huawei, HiSilicon | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250053 | Conclusion on key issue #1.2 in TR 33.700-22 | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250054 | Adding evaluation for solution#3 | pCR | Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250055 | Update solution#8 |
pCR revised to S3-250175 |
Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250056 | Update solution#28 |
pCR revised to S3-250176 |
Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250057 | Update solution#31 | pCR | Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250058 | Conclusion on KI#5 AIoT Authentication |
pCR revised to S3-250226 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250059 | pCR to TR33.713 Update solution#9 to remove EN |
pCR revised to S3-250231 |
CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250060 | pCR to TR33.713 New solution AIoT command message security protection procedure | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250061 | pCR to TR33.713 Generic conclusion | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250062 | Proposal for a conclusion to KI#1 |
pCR revised to S3-250171 |
Nokia, Deutsche Telekom, BMWK, IIT Bombay | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-250063 | Proposal for a conclusion to KI#2 |
pCR revised to S3-250172 |
Nokia, Deutsche Telekom, IIT Bombay | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-250064 | TR cleanup |
pCR revised to S3-250173 |
Nokia | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-250065 | Presentation of Report to TSG: TR 33.766, Version 1.0.0 | TS or TR cover | Nokia | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
endorsed | [WTS] [JSN] | |
| S3-250066 | Proposal for a conclusion | pCR | Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250067 | Proposal for a resolution to an EN concerning counter synchronisation | pCR | Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250068 | Proposal for a resolution of an EN concerning alignment with RAN specifications | pCR | Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250069 | Proposal for a resolution to an EN concerning device constrains |
pCR revised to S3-250174 |
Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250070 | Proposal for a resolution to an EN concerning key identification | pCR | Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250071 | LS reply to LS on security aspects of Ambient IoT |
LS out source LS: S3-244641 LS To: SA2 |
Nokia | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-250072 | pCR to TR33.713 Conclusion#3 | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250073 | pCR to TR33.713 Conclusion#4 | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250074 | pCR to TR33.713 Conclusion#5 | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250075 | Conclusion for KI#2 in TR 33.713 |
pCR revised to S3-250223 |
OPPO, Xiaomi | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250076 | pCR to TR33.713 Update solution#30 to remove EN | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250077 | Resolving ENs for AIoT Security Sol#37 |
pCR revised to S3-250225 |
Xidian, OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250078 | Resolving ENs in Solution #42 of TR 33.713 |
pCR revised to S3-250183 |
KPN N.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250079 | New Solution to KI#5 |
pCR revised to S3-250177 |
Ericsson | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250080 | New key issue for secure storage in AIoT devices | pCR | Ericsson, Thales | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250081 | New Key Issue on Amplification of resource exhaustion by exploiting AIoT paging messages | pCR | Ericsson | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250082 | New key issue for Authenticated and authorized access to devices in Ambient IoT via 3GPP core | pCR | Ericsson | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250083 | Pseudo-CR-General conclusion for the architecture of AIoT |
pCR revised to S3-250232 |
China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250084 | Pseudo-CR-System architecture and security assumptions for AIoT services |
pCR revised to S3-250233 |
China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250085 | Pseudo-CR on New solution on AIoT privacy | pCR | China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250086 | Update to solution#27 |
pCR revised to S3-250188 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250087 | Updates to conclusion for key issue#2 |
pCR revised to S3-250189 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250088 | [TR 33.721] Update to solution#6 |
pCR revised to S3-250190 |
Samsung | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250089 | Updates to solution#6 |
other revised to S3-250184 |
Samsung | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] | |
| S3-250090 | Evaluation updates for solution#6 |
other revised to S3-250185 |
Samsung | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] | |
| S3-250091 | Conclusion for Key issue#2 | other | Samsung | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
merged | [WTS] [JSN] | |
| S3-250092 | Resolving EN in solution #22 |
pCR revised to S3-250186 |
Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250093 | Evaluation update for solution#22 | pCR | Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250094 | Resolving EN in solution #38 | pCR | Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250095 | Evaluation to solution #38 | pCR | Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250096 | New solution for Authorization of API invoker on one UE accessing resources related to another UE |
pCR revised to S3-250198 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250097 | Resolving EN in key issue #1.2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250098 | Resolving ENs and evaluation of solution #11 |
pCR revised to S3-250199 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250099 | Resolving ENs and evaluation of solution #22 |
pCR revised to S3-250200 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250100 | Resolving ENs and evaluation of solution #26 |
pCR revised to S3-250201 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250101 | Conclusion reformulation for key issue #1.2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250102 | Further conclusion for key issue #1.1 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250103 | Further conclusion for key issue #1.2 |
pCR revised to S3-250196 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250104 | Further conclusion for key issue #1.3 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-250105 | Further conclusion for key issue #2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250106 | Conclusion for key issue #3 |
pCR revised to S3-250197 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250107 | Conclusion for key issue #4 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250108 | Conclusion for key issue #5 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250109 | Conclusion for key issue #6 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250110 | Conclusion for KI#4 in TR 33.713 | pCR | Beijing Xiaomi Mobile Software | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250111 | Conclusion for KI#5 in TR 33.713 | pCR | Beijing Xiaomi Mobile Software | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250112 | 33.721: Evaluation of Solution 10 |
pCR revised to S3-250213 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250113 | 33.721: Update to Conclusion on Key Issue #2 |
pCR revised to S3-250214 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250114 | 33.721: Conclusion on Key Issue #4 |
pCR revised to S3-250215 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250115 | Draft CR on TS 33.122 | draftCR | Xiaomi communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] | |
| S3-250116 | TR 33.700-22KI#1.1 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250117 | TR 33.700-22KI#1.2 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250118 | TR 33.700-22KI#1.3 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250119 | TR 33.700-22KI#2 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250120 | Solution#1 update: Addressing ENs |
pCR revised to S3-250230 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250121 | Solution#1 evaluation update |
pCR revised to S3-250229 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250122 | KI#1 update: Addressing EN | pCR | Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250123 | KI#3 update: Addressing ENs |
pCR revised to S3-250228 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250124 | KI#4 update: Addressing ENs |
pCR revised to S3-250227 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250125 | KI#3 conclusions | pCR | Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250126 | KI#4 conclusions | pCR | Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250127 | KI#5 conclusions | pCR | Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250128 | Conclusion for KI#1 | pCR | Ericsson | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250129 | Conclusion for KI#2 | pCR | Ericsson | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250130 | LS on User Consent aspects for Energy Saving |
LS out LS To: SA WG2 |
Ericsson | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250131 | Solution#5 update for alignment with SA2 and addressing EN |
pCR revised to S3-250207 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250132 | Conclusion to KI#2 of NG_RTC |
pCR revised to S3-250192 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250133 | Conclusion to KI#3 of NG_RTC |
pCR revised to S3-250210 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250134 | Update on Key Issue#6 |
pCR revised to S3-250217 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250135 | Sol#10 update |
pCR revised to S3-250218 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250136 | Sol#40 update |
pCR revised to S3-250219 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250137 | Sol#41 update |
pCR revised to S3-250220 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250138 | Conclusion for Key Issue#4 Information Protection | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250139 | Conclusion for Key Issue#5 AIoT Authentication | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250140 | Conclusion to KI#1 |
pCR revised to S3-250193 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250141 | Solution#3 update | pCR | OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250142 | Solution#18 update | pCR | OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250143 | Solution#19 update | pCR | OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250144 | Authorization of external AF for Inventory |
pCR revision of S3-245132 revised to S3-250194 |
NTT DOCOMO INC. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250145 | KI on attacking via external carrier wave |
pCR revised to S3-250945 |
NTT DOCOMO INC. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250146 | Evaluation for Sol2 Authorization supporting spatial localization service with CCF | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250147 | Update Sol3 Authorization supporting spatial localization service with CCF |
pCR revised to S3-250178 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250148 | Update Sol5 Privacy protection during metaverse service discovery |
pCR revised to S3-250179 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250149 | Update Sol7 authorize avatar by metaverse service provider | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250150 | Update Sol8 authenticate and authorize DA client to create a digital asset |
pCR revised to S3-250180 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250151 | Update Sol9 authenticate and authorize DA client to access a digital asset |
pCR revised to S3-250181 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250152 | Conclusion for KI3 Security aspects of digital asset container in 5G | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250153 | Conclusion for KI4 Authentication and authorization of digital representation | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250154 | Conclusion for KI2 IMS based Avatar Communication | other | Nokia, Nokia Shanghai Bell | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
merged | [WTS] [JSN] | |
| S3-250155 | Update KI#1: Third party specific user identities to include NEF-AF interface security | other | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
noted | [WTS] [JSN] | |
| S3-250156 | LS on IMS support for AF authorization |
LS out LS To: SA2 revised to S3-250170 |
Ericsson | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] | ||
| S3-250157 | Conclusion for KI3 IMS DC capability exposure | other | Nokia, Nokia Shanghai Bell | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
merged | [WTS] [JSN] | |
| S3-250158 | Comments on S3-250145, “KI on attacking via external carrier wave” | pCR | InterDigital, Inc. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250159 | Generic conclusion for AIoT | pCR | Qualcomm Incorporated | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250160 | KI1.1 ROF authentication conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250161 | KI1.1 ROF authentication | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250162 | KI1.1 Solution 3 update | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250163 | KI1.2 EN resolution in solution 7 | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250164 | KI1.3 conclusion |
pCR revised to S3-250222 |
Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250165 | KI2 interconnect conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250166 | KI3 conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250167 | KI4 Nested API invocation conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250168 | KI5 muliple API infovoker same RO conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250169 | TR correction | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250170 | LS on IMS support for AF authorization and IMS avatar communication |
LS out LS To: SA2 revision of S3-250156 |
Ericsson | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] | ||
| S3-250171 | Proposal for a conclusion to KI#1 |
pCR revision of S3-250062 |
Nokia, Deutsche Telekom, BMWK, IIT Bombay, Ericsson, Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-250172 | Proposal for a conclusion to KI#2 |
pCR revision of S3-250063 |
Nokia, Deutsche Telekom, IIT Bombay, Ericsson, Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-250173 | TR cleanup |
pCR revision of S3-250064 |
Nokia, Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-250174 | Proposal for a resolution to an EN concerning device constrains |
pCR revision of S3-250069 |
Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250175 | Update solution#8 |
pCR revision of S3-250055 |
Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250176 | Update solution#28 |
pCR revision of S3-250056 |
Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250177 | New Solution to KI#5 |
pCR revision of S3-250079 |
Ericsson | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250178 | Update Sol3 Authorization supporting spatial localization service with CCF |
pCR revision of S3-250147 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250179 | Update Sol5 Privacy protection during metaverse service discovery |
pCR revision of S3-250148 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250180 | Update Sol8 authenticate and authorize DA client to create a digital asset |
pCR revision of S3-250150 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250181 | Update Sol9 authenticate and authorize DA client to access a digital asset |
pCR revision of S3-250151 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250182 | KI#1.1-Further conclusions on ROF authentication |
pCR revision of S3-250017 |
Huawei, HiSilicon, Ericsson, Xiaomi, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250183 | Resolving ENs in Solution #42 of TR 33.713 |
pCR revision of S3-250078 |
KPN N.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250184 | Updates to solution#6 |
pCR revision of S3-250089 |
Samsung | 33.790 1.0.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250185 | Evaluation updates for solution#6 |
pCR revision of S3-250090 |
Samsung | 33.790 1.0.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250186 | Resolving EN in solution #22 |
pCR revision of S3-250092 |
Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250187 | Updates to Solution#21 |
pCR revision of S3-250037 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250188 | Update to solution#27 |
pCR revision of S3-250086 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250189 | Updates to conclusion for key issue#2 |
pCR revision of S3-250087 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250190 | [TR 33.721] Update to solution#6 |
pCR revision of S3-250088 |
Samsung | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250191 | Solution to address KI#6 |
pCR revision of S3-250038 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250192 | Conclusion to KI#2 of NG_RTC |
pCR revision of S3-250132 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250193 | Conclusion to KI#1 |
pCR revision of S3-250140 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250194 | Authorization of external AF for Inventory |
pCR revision of S3-250144 |
NTT DOCOMO INC. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250195 | Conclusion to key issue#1 |
pCR revision of S3-250013 |
Lenovo, ZTE, OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250196 | Further conclusion for key issue #1.2 |
pCR revision of S3-250103 |
Ericsson, Huawei, HiSilicon, ZTE Corporation, China Telecom, Xiaomi communications, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250197 | Conclusion for key issue #3 |
pCR revision of S3-250106 |
Ericsson, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250198 | New solution for Authorization of API invoker on one UE accessing resources related to another UE |
pCR revision of S3-250096 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250199 | Resolving ENs and evaluation of solution #11 |
pCR revision of S3-250098 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250200 | Resolving ENs and evaluation of solution #22 |
pCR revision of S3-250099 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250201 | Resolving ENs and evaluation of solution #26 |
pCR revision of S3-250100 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250202 | draft TR 33.713 v0.6.0 | draft TR | OPPO | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] | |
| S3-250203 | addressing the editor's note in solution#4 |
pCR revision of S3-250044 |
Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250204 | Generic conclusion on AIoT |
pCR revision of S3-250047 |
Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250205 | Draft TR 33.790 v1.1.0 Study on the security support for the next generation real time communication services phase 2 | draft TR | Ericsson Hungary Ltd | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-250206 | conclusion on key issue#4 |
pCR revision of S3-250046 |
Huawei, HiSilicon, OPPO, China Unicom, Lenovo, ZTE, CATT, Xiaomi, Philips | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250207 | Solution#5 update for alignment with SA2 and addressing EN |
pCR revision of S3-250131 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250208 | Evaluation for solution 6 |
pCR revision of S3-250025 |
ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250209 | Update the scope in TR 33.713 |
pCR revision of S3-250028 |
ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250210 | Conclusion to KI#3 of NG_RTC |
pCR revision of S3-250133 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250211 | Conclusion for KI#3 |
pCR revision of S3-250034 |
ZTE Corporation | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250212 | remove EN in clause 6.4 |
pCR revision of S3-250022 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250213 | 33.721: Evaluation of Solution 10 |
pCR revision of S3-250112 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250214 | 33.721: Update to Conclusion on Key Issue #2 |
pCR revision of S3-250113 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250215 | 33.721: Conclusion on Key Issue #4 |
pCR revision of S3-250114 |
Xiaomi EV Technology, Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250216 | editorial corrections in clauses 6.2 and 6.10 |
pCR revision of S3-250023 |
Huawei, HiSilicon, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250217 | Update on Key Issue#6 |
pCR revision of S3-250134 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250218 | Sol#10 update |
pCR revision of S3-250135 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250219 | Sol#40 update |
pCR revision of S3-250136 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250220 | Sol#41 update |
pCR revision of S3-250137 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250221 | Draft TR 33.766 v0.6.0 | draft TR | Ericsson | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
approved | [WTS] [JSN] | |
| S3-250222 | KI1.3 conclusion |
pCR revision of S3-250164 |
Nokia, Huawei, HiSilicon, Xiaomi | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250223 | Conclusion for KI#2 in TR 33.713 |
pCR revision of S3-250075 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250224 | Conclusion on AIOT KI#3 |
pCR revision of S3-250041 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250225 | Resolving ENs for AIoT Security Sol#37 |
pCR revision of S3-250077 |
Xidian, OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250226 | Conclusion on KI#5 AIoT Authentication |
pCR revision of S3-250058 |
OPPO, Huawei, HiSilicon, Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250227 | KI#4 update: Addressing ENs |
pCR revision of S3-250124 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250228 | KI#3 update: Addressing ENs |
pCR revision of S3-250123 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250229 | Solution#1 evaluation update |
pCR revision of S3-250121 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250230 | Solution#1 update: Addressing ENs |
pCR revision of S3-250120 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250231 | pCR to TR33.713 Update solution#9 to remove EN |
pCR revision of S3-250059 |
CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250232 | Pseudo-CR-General conclusion for the architecture of AIoT |
pCR revision of S3-250083 |
China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250233 | Pseudo-CR-System architecture and security assumptions for AIoT services |
pCR revision of S3-250084 |
China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250234 | Draft TR 33.721 v0.6.0 | draft TR | Samsung | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] | |
| S3-250235 | Study on security aspects of CAPIF Phase3 |
draft TR revised to S3-250236 |
Ericsson LM | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] | |
| S3-250236 | Study on security aspects of CAPIF Phase3 |
draft TR revision of S3-250235 |
Ericsson LM | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-250237 | SA3 Leadership meeting notes | report | MCC |
S3-119-e AI: 3.1 |
available | [WTS] [JSN] |
1011 documents (1.2765018939972 seconds)