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-250300 | Agenda | agenda | SA WG3 Chair |
S3-120 AI: 1 |
approved | [WTS] [JSN] | |||
| S3-250301 | Report from SA3#119 | report | MCC |
S3-120 AI: 2.1 |
approved | [WTS] [JSN] | |||
| S3-250302 | Report from SA3#119 AdHoc-e | report | MCC |
S3-120 AI: 2.1 |
approved | [WTS] [JSN] | |||
| S3-250303 | Process for SA3#120 | other | SA WG3 Chair |
S3-120 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-250304 | Detailed agenda planning | other | SA WG3 Chair |
S3-120 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-250305 | SA3 meeting calendar | other | SA WG3 Chair |
S3-120 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-250306 | UPU Header Security |
CR revised to S3-251120 |
Lenovo | 33.501 19.1.0 CR#2114 catF | 5GS_Ph1-SEC, TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-250307 | FS_eZTS next steps Offline Call Minutes | discussion | Motorola Mobility | Rel-19 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250308 | SUPI Privacy Issue in PLMN hosted NPN | draftCR | Lenovo | PLMNNPN | Rel-19 |
S3-120 AI: 4.25 |
merged | [WTS] [JSN] | |
| S3-250309 | Conclusion to KI#6 | pCR | Lenovo | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250310 | Updates to Solution #33 |
pCR revised to S3-251003 |
Lenovo | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250311 | KI#6 update to add Clarifications | pCR | Lenovo | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250312 | AIoT TR clean up | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250313 | Reply to LS on CEN's requirements for eCall over IMS | LS in | C1-246950 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250314 | LS on ProSe Message Content Type extensions for Release 19 |
LS in LS reply in S3-250955 |
C1-247001 |
S3-120 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-250315 | LS on Clarifications related to the parameter to support 5G ProSe in SNPN |
LS in LS reply in S3-251172, S3-251172 |
C1-247074 |
S3-120 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-250316 | LS on security questions related to NAS layer overhead reduction for data transfer using control plane CIoT |
LS in LS reply in S3-251143 |
C1-247156 |
S3-120 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-250317 | LS on including the HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS in LS reply in S3-251122 |
C1-244647 |
S3-120 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-250318 | Reply LS on clarification on home network triggered re-authentication | LS in | C4-244496 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250319 | LS on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case | LS in | C4-244497 |
S3-120 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-250320 | Reply LS on N32-f Lifetime and Reconnection | LS in | C4-245540 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250321 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS in LS reply in S3-251123 |
C6-240721 |
S3-120 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-250322 | Update on ETSI TC Cyber middlebox work | LS in | ETSI TC CYBER |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250323 | LS on signalling feasibility of dataset and parameter sharing | LS in | R1-2410922 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250324 | Reply LS to SA5 on AIML data collection | LS in | R2-2411114 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250325 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS in LS reply in S3-251124 |
R2-2411136 |
S3-120 AI: 4.12 |
replied to | [WTS] [JSN] | |||
| S3-250326 | Reply LS to SA2 on AIML data collection | LS in | R2-2411152 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250327 | Reply LS on AIML data collection | LS in | R3-247801 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250328 | LS on AI/ML UE sided data collection | LS in | RP-243316 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250329 | Reply LS on CEN requirements for eCall over IMS | LS in | S1-244755 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250330 | LS Reply to Issues related to Analytics context transfer between AnLF(s) | LS in | S2-2409441 |
S3-120 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-250331 | Reply LS to SA WG3-LI: Reply LS on UE-Satellite-UE Communication Architectures | LS in | S2-2412670 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250332 | Reply LS on request for IMS Data Channel related clarifications | LS in | S2-2412697 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250333 | Reply LS on AIML data collection | LS in | S2-2412726 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250334 | Reply LS on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case | LS in | S2-2412738 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250335 | Reply LS to request clarification on the potential baseline system architecture of 5G NR Femto | LS in | S2-2412752 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250336 | LS on User Privacy Aspects of LMF-based AI/ML positioning | LS in | S2-2412940 |
S3-120 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-250337 | Reply to Reply LS on FS_5GSAT_Ph3_ARCH conclusions | LS in | S2-2501085 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250338 | LS on Device Subscription Data | LS in | S2-2501242 |
S3-120 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-250339 | Reply LS on Multi-hop U2N Relay Architecture Aspects | LS in | S2-2501335 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250340 | LS on security aspects of Ambient IoT |
LS in LS reply in S3-251055 |
S2-2411049 |
S3-120 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-250341 | Reply LS on request for IMS Data Channel related clarifications | LS in | S4-242073 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250342 | Reply LS on AIML Data Collection | LS in | S5-247219 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250343 | Reply LS on Masking of cryptographic keys in UE trace file from 3GPP core network entities | LS in | S5-247312 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250344 | Reply LS on AIML Data Collection | LS in | S5-247336 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250345 | Reply LS on clarifications on consent management | LS in | S6-245716 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250346 | TS.43 Service Entitlement Configuration, v11.0 ^^^^TS.43 CR1098 - App Token |
LS in LS reply in S3-250453 |
GSMA |
S3-120 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-250347 | LS Response to SA3-LI on RCS lawful intercept requirements | LS in | GSMA |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250348 | New WID on mission critical security enhancements for release 20 | WID new | Motorola Solutions Germany | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250349 | Initial Trust in the NF for ACME account creation | other | NCSC | ACME_SBA |
S3-120 AI: 4.18 |
merged | [WTS] [JSN] | ||
| S3-250350 | LS Response to GSMA RCSG on RCS lawful interception requirements | LS in | s3i250083 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250351 | Authorization of a service request when the discovery is delegated to the target PLMN |
CR revision of S3-244918 |
Nokia | 33.501 19.1.0 CR#20771 catB | TEI19, TEI19_NFsel_by_tPLMN | Rel-19 |
S3-120 AI: 4.1.2 |
merged | [WTS] [JSN] |
| S3-250352 | IdMS - OIDC Client Registration |
CR revised to S3-251096 |
Leonardo SpA | 33.180 19.0.0 CR#216 catF | MCXSec3 | Rel-19 |
S3-120 AI: 4.6 |
revised | [WTS] [JSN] |
| S3-250353 | IdMS - PKCE Downgrade Attack |
CR revised to S3-251097 |
Leonardo SpA | 33.180 19.0.0 CR#217 catF | MCXSec3 | Rel-19 |
S3-120 AI: 4.6 |
revised | [WTS] [JSN] |
| S3-250354 | Discussion on SCAS test cases for containerized network products | discussion | BSI (DE) |
S3-120 AI: 4.1.1 |
noted | [WTS] [JSN] | |||
| S3-250355 | Discussion paper for clustering of all solutions | discussion | Nokia, Nokia Shanghai Bell |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-250356 | Proposed Changes to Conclusions | other | Nokia, Nokia Shanghai Bell |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-250357 | Proposed Text for Normative Clause | other | Nokia, Nokia Shanghai Bell |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-250358 | Proposed Changes to Solution 2 | other | Nokia, Nokia Shanghai Bell |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-250359 | Removing Editors Note in Solution 2 | other | Nokia, Nokia Shanghai Bell |
S3-120 AI: 4.12 |
withdrawn | [WTS] [JSN] | |||
| S3-250360 | Proposed new KI on the MAC CE security | other | Nokia, Nokia Shanghai Bell |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-250361 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-250325 LS To: RAN2 |
Nokia, Nokia Shanghai Bell |
S3-120 AI: 4.12 |
merged | [WTS] [JSN] | |||
| S3-250362 | TCG progress - report from TCG rapporteur | other | InterDigital, Inc. |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250363 | Mitigation of GNSS spoofing | discussion | MediaTek Inc., Ericsson | Rel-19 |
S3-120 AI: 4.1.15 |
noted | [WTS] [JSN] | ||
| S3-250364 | Study on UE Security Assurance | SID new | Keysight Technologies UK Ltd | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250365 | LS informing about the latest PQTN TF publications |
LS in LS reply in S3-250956 |
GSMA |
S3-120 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-250366 | N32 consistency checks |
CR revised to S3-251064 |
BSI (DE), Nokia | 33.501 19.1.0 CR#2090 catF | Roaming5G, TEI19 | Rel-19 |
S3-120 AI: 4.1.14 |
revised | [WTS] [JSN] |
| S3-250367 | Report from SA#106 | report | WG Chair |
S3-120 AI: 2.1 |
noted | [WTS] [JSN] | |||
| S3-250368 | New SID on use of AEAD |
SID new revised to S3-250961 |
KDDI Corporation | Rel-20 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-250369 | Use of AEAD in Next-Generation 3GPP system | discussion | KDDI Corporation |
S3-120 AI: 6 |
noted | [WTS] [JSN] | |||
| S3-250370 | Technical Content for 3GPP Cryptographic Inventory | pCR | KDDI Corporation | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
merged | [WTS] [JSN] |
| S3-250371 | New WID on supporting 256-bit ciphering and integrity protection algorithms | WID new | KDDI Corporation | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250372 | Algorithm identifier values for 256-bit algorithms | draftCR | KDDI Corporation | FS_CAT256 | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | |
| S3-250373 | Guidelines on WID names and acronyms | other | MCC |
S3-120 AI: 8 |
noted | [WTS] [JSN] | |||
| S3-250374 | Reply LS on security questions related to NAS layer overhead reduction for data transfer using control plane CIoT |
LS out LS is reply to S3-250316 LS To: CT1 revised to S3-251143 |
vivo | Rel-19 |
S3-120 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-250375 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS To: CT1, CT6 |
vivo | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250376 | DP on UE behaviour in case of SUCI calculation failure | discussion | vivo | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250377 | Conclusion on security handling for LTM | other | vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250378 | Procedure for security handling for LTM | other | vivo | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250379 | Reply LS on Device Subscription Data |
LS out LS To: SA2 |
vivo | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250380 | Align conclusion with SA2 LS and conclusion for KI#5 | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250381 | Conclusion for communication protection in AIoT | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250382 | Conclusion for privacy in AIoT | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250383 | Update conclusion for authentication in AIoT | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250384 | Update generic conclusion for AIoT | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250385 | Remove EN for Sol#10 |
pCR revised to S3-251111 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250386 | Remove EN for Sol#40 | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250387 | Remove EN for Sol#41 | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250388 | Reply LS on User Privacy Aspects of LMF-based AI/ML positioning |
LS out LS is reply to S3-250336 LS To: SA2 |
vivo | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250389 | Abbreviations for AIML_CN_SEC | other | vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-250390 | General description for security for UE positioning based on a ML model at the LMF |
other revised to S3-251057 |
vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
revised | [WTS] [JSN] | |
| S3-250391 | Security for data collection for the LMF-based AI/ML positioning | other | vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250392 | General description for security for vertical federated Learning among NWDAFs and AFs |
other revised to S3-251059 |
vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
revised | [WTS] [JSN] | |
| S3-250393 | Authorization of candidate VFL participants for vertical federated learning when NWDAF or internal AF is acting as the VFL server | other | vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250394 | Authorization of candidate VFL participants for vertical federated learning when external AF is acting as the VFL server | other | vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250395 | NEF security requirements | other | vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
noted | [WTS] [JSN] | |
| S3-250396 | Protection of communication data used in VFL process | other | vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250397 | Scope of the TR on 3GPP crypto inventory | pCR | Nokia, Nokia Shanghai Bell | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
noted | [WTS] [JSN] |
| S3-250398 | Technical Content | pCR | Nokia, Nokia Shanghai Bell | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
noted | [WTS] [JSN] |
| S3-250399 | Framework |
pCR revised to S3-251073 |
Nokia, Nokia Shanghai Bell | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
revised | [WTS] [JSN] |
| S3-250400 | LS reply to GSMA on App token |
LS out LS is reply to GSMA source LS: S3-250346 LS To: GSMA |
Huawei, HiSilicon |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250401 | TR 33.938 skeleton_FS_CryptoInv | draft TR | Huawei, HiSilicon, Nokia | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
approved | [WTS] [JSN] | |
| S3-250402 | scope of TR 33.938 | pCR | Huawei, HiSilicon | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
approved | [WTS] [JSN] |
| S3-250403 | general clause |
pCR revised to S3-251074 |
Huawei, HiSilicon | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
revised | [WTS] [JSN] |
| S3-250404 | inventory of 5G security protocols | pCR | Huawei, HiSilicon | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
merged | [WTS] [JSN] |
| S3-250405 | inventory of 5G protocols by organizations | pCR | Huawei, HiSilicon | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
merged | [WTS] [JSN] |
| S3-250406 | KI#1.1 conclusions on ROF authentication | pCR | Huawei, HiSilicon | 33.700-22 0.4.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250407 | KI#1.2 conclusions on RO authorization | pCR | Huawei, HiSilicon | 33.700-22 0.4.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250408 | KI#1.3 conclusions on granularity of authorization and revocation |
pCR revised to S3-251000 |
Huawei, HiSilicon | 33.700-22 0.4.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250409 | RO authentication and authorization information for CAPIF-8 reference point | CR | Huawei, HiSilicon | 33.122 18.4.0 CR#76 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
not pursued | [WTS] [JSN] |
| S3-250410 | Authorization revocation through CAPIF-8 reference point | CR | Huawei, HiSilicon | 33.122 18.4.0 CR#77 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
not pursued | [WTS] [JSN] |
| S3-250411 | Security requirements and procedures for CAPIF-8 reference point |
CR revised to S3-251032 |
Huawei, HiSilicon | 33.122 18.4.0 CR#78 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
revised | [WTS] [JSN] |
| S3-250412 | Finer granularity support for security procedures | CR | Huawei, HiSilicon | 33.122 18.4.0 CR#79 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
merged | [WTS] [JSN] |
| S3-250413 | Informative Annex general clause | draftCR | Huawei, HiSilicon | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
merged | [WTS] [JSN] | |
| S3-250414 | challenge validation | draftCR | Huawei, HiSilicon | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
noted | [WTS] [JSN] | |
| S3-250415 | certificate renew | draftCR | Huawei, HiSilicon | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
merged | [WTS] [JSN] | |
| S3-250416 | authorized USS list |
draftCR revised to S3-251007 |
Huawei, HiSilicon | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] | |
| S3-250417 | USS initiated UUAA | draftCR | Huawei, HiSilicon | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
merged | [WTS] [JSN] | |
| S3-250418 | security aspects of USS changeover procedure | draftCR | Huawei, HiSilicon | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
merged | [WTS] [JSN] | |
| S3-250419 | Access token scope clarification for recording authorization | CR | Airbus, Motorola Solutions | 33.180 19.0.0 CR#218 catF | MCXSec3 | Rel-19 |
S3-120 AI: 4.6 |
not pursued | [WTS] [JSN] |
| S3-250420 | Finalising the certificate test for split gNBs |
CR revised to S3-250465 |
Qualcomm Incorporated | 33.523 19.0.0 CR#10 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250421 | Discussion on incoming SUCI LS from CT6 | discussion | Qualcomm Incorporated |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250422 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to C6-240721 LS To: CT1 revised to S3-251123 |
Qualcomm Incorporated | 5GProtoc19 | Rel-19 |
S3-120 AI: 3.1 |
revised | [WTS] [JSN] | |
| S3-250423 | ME behaviour when the USIM does not contain the parameter needed for SUCI calculation | CR | Qualcomm Inorporated | 33.501 19.1.0 CR#2091 catF | 5GProtoc19, TEI19 | Rel-19 |
S3-120 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-250424 | Discussion on the response to C1-247126 on NAS overhead | discussion | Qualcomm Incorporated |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250425 | Reply LS on security questions related to NAS layer overhead reduction for data transfer using control plane CIoT |
LS out LS is reply to S3-250316 LS To: CT1 |
Qualcomm Incorporated | NORDAT_CP | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-250426 | Pseudo-CR on proposed privacy conclusion for split MME case | pCR | Qualcomm Incorporated | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-250427 | Proposed text for general clause of satellite store & forward | other | Qualcomm Incorporated |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |||
| S3-250428 | Proposed text for split MME clause of satellite store & forward | other | Qualcomm Incorporated |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |||
| S3-250429 | Proposed text for full EPC clause of satellite store & forward |
other revised to S3-251034 |
Qualcomm Incorporated |
S3-120 AI: 4.19 |
revised | [WTS] [JSN] | |||
| S3-250430 | Adding in-band key deprecation to the informative annex on IOPS | other | Qualcomm Incorporated |
S3-120 AI: 4.19 |
noted | [WTS] [JSN] | |||
| S3-250431 | Adding support for multiple USSs |
CR revised to S3-250466 |
Qualcomm Incorporated | 33.256 18.2.0 CR#50 catB | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250432 | Reply LS on ProSe Message Content Type extensions for Release 19 |
LS out LS is reply to C1-247001 LS To: CT1 |
Qualcomm Incorporated | 5G_ProSe_Ph3 | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-250433 | Reply LS on clarifications related to the parameter to support 5G ProSe in SNPN |
LS out LS is reply to S3-250315 LS To: CT1 |
Qualcomm Incorporated | TEI19_ProSe_NPN |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250434 | Updates on KI#1 conclusions | pCR | Qualcomm Incorporated | 33.743 1.0.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-120 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-250435 | U2N relay discovery security |
other revised to S3-251042 |
Qualcomm Incorporated |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |||
| S3-250436 | U2N relay communication security | other | Qualcomm Incorporated |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |||
| S3-250437 | U2U relay discovery security |
other revised to S3-251045 |
Qualcomm Incorporated |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |||
| S3-250438 | U2U relay communication security | other | Qualcomm Incorporated |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |||
| S3-250439 | 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-250317 LS To: CT1 revised to S3-251122 |
Qualcomm Incorporated | 5G_ProSe_Ph2 |
S3-120 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-250440 | Pseudo-CR on Template Proposal for 3GPP Cryptographic Inventory | other | Qualcomm Incorporated |
S3-120 AI: 5. |
noted | [WTS] [JSN] | |||
| S3-250441 | Pseudo-CR on 3GPP Cryptographic Inventory for DTLS and TLS |
pCR revised to S3-251072 |
Qualcomm Incorporated | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
revised | [WTS] [JSN] |
| S3-250442 | UUAA update for multi-USS support | draftCR | InterDigital, Europe, Ltd. | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
merged | [WTS] [JSN] | |
| S3-250443 | Adding USS changeover with multi-USS support | draftCR | InterDigital, Europe, Ltd. | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
merged | [WTS] [JSN] | |
| S3-250444 | Location tracking update for multi-USS support |
draftCR revised to S3-251010 |
InterDigital, Europe, Ltd. | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] | |
| S3-250445 | Adding Abbreviations to TR 33.700-32 | CR | InterDigital, Europe, Ltd. | 33.700-32 19.0.0 CR#1 catD | FS_UIA_Sec | Rel-19 |
S3-120 AI: 4.1.15 |
withdrawn | [WTS] [JSN] |
| S3-250446 | Security_Aspects_for_User_Identities_Ph2 | SID new | InterDigital, Europe, Ltd. | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250447 | Update KI#1 Conclusion | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250448 | New WID on Ambient IoT security |
WID new revised to S3-251150 |
OPPO, Huawei, HiSilicon, Intel, Lenovo, Inter Digital, China Unicom, Sony, Vivo, Xiaomi, China Mobile, Philips, Cable Labs, CATT, ZTE | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-250449 | Living document for Automatic Certificate Management Environment (ACME) for the Service Based Architecture (SBA) |
draftCR revised to S3-251089 |
Cisco Systems | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
revised | [WTS] [JSN] | |
| S3-250450 | Cover for draft TR 33.713 | TS or TR cover | Guangdong OPPO Mobile Telecom. | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] | |
| S3-250451 | ACME as optional protocol for ACM for SBA |
other revised to S3-251093 |
Cisco Systems | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
revised | [WTS] [JSN] | |
| S3-250452 | ACME challenge validation for 5G SBA NFs |
other revised to S3-251139 |
Cisco Systems, U.S. National Security Agency | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
revised | [WTS] [JSN] | |
| S3-250453 | Reply LS on OSAppID usage by App Token use case |
LS out LS is reply to S3-250346 LS To: GSMA TSGNS |
Verizon Sweden | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250454 | PKI Modifications for Clause 10 TS 33.310 | discussion | NCSC |
S3-120 AI: 4.1.15 |
noted | [WTS] [JSN] | |||
| S3-250455 | Updates on general conclusion for AIoT | pCR | Qualcomm Incorporated | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250456 | Updates on KI#5 conclusion | pCR | Qualcomm Incorporated | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250457 | KI#4 conclusion | pCR | Qualcomm Incorporated | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250458 | KI#3 conclusion for AIoT | pCR | Qualcomm Incorporated | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250459 | Updates on solution 15 | pCR | Qualcomm Incorporated | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250460 | A new solution for network layer security based on the key provided by AF |
pCR revised to S3-251171 |
Qualcomm Incorporated | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250461 | New WID on Key Derivation for QUIC/TLS in ATSSS | WID new | CableLabs, Charter Communications, Lenovo, Nokia, Nokia Shanghai Bell | Rel-19 |
S3-120 AI: 6 |
merged | [WTS] [JSN] | ||
| S3-250462 | Addition of the new content specifying security aspects of Store and Forward Satellite operation in Split MME architecture |
draftCR revised to S3-251035 |
InterDigital, Inc. | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
revised | [WTS] [JSN] | |
| S3-250463 | New KI: Reader Authorization for 5G Ambient IoT Services | pCR | InterDigital, Inc. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250464 | Conclusion for New KI: Reader Authorization for 5G Ambient IoT Services |
pCR revised to S3-251145 |
InterDigital, Inc. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250465 | Finalising the certificate test for split gNBs |
CR revision of S3-250420 |
Qualcomm Incorporated | 33.523 19.0.0 CR#101 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-250466 | Adding support for multiple USSs |
CR revision of S3-250431 revised to S3-251008 |
Qualcomm Incorporated | 33.256 18.2.0 CR#501 catB | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250467 | Updates to Annex I.2 |
other revised to S3-251094 |
Johns Hopkins University APL, Cisco Systems | Rel-19 |
S3-120 AI: 4.18 |
revised | [WTS] [JSN] | ||
| S3-250468 | certificate revocation |
other revised to S3-251092 |
Johns Hopkins University APL, Cisco Systems, U.S. National Security Agency | Rel-19 |
S3-120 AI: 4.18 |
revised | [WTS] [JSN] | ||
| S3-250469 | Update Conclusion of KI#2.1 |
pCR revised to S3-251081 |
Nokia, Nokia Shanghai Bell | 33.749 0.5.0 | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-250470 | Security of N6 delay measurements |
CR revised to S3-251088 |
Nokia, Nokia Shanghai Bell | 33.501 19.1.0 CR#2092 catB | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
revised | [WTS] [JSN] |
| S3-250471 | Solutions for secure retrieval of 5G system UE Ids and privacy related information |
draftCR revised to S3-251083 |
Nokia, Nokia Shanghai Bell | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
revised | [WTS] [JSN] | |
| S3-250472 | Requirements for secure retrieval of 5G system UE lds and privacy related information | CR | Nokia, Nokia Shanghai Bell | 33.558 18.2.0 CR#19 catB | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
not pursued | [WTS] [JSN] |
| S3-250473 | RNAA and Interconnect aspects in function security model |
CR revised to S3-251115 |
Nokia | 33.122 18.4.0 CR#80 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
revised | [WTS] [JSN] |
| S3-250474 | Security requirements on CAPIF-6 and -6e reference points |
CR revised to S3-251030 |
Nokia | 33.122 18.4.0 CR#81 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
revised | [WTS] [JSN] |
| S3-250475 | Security requirements on CAPIF-8 reference points | CR | Nokia | 33.122 18.4.0 CR#82 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
merged | [WTS] [JSN] |
| S3-250476 | Security solution for interconnect | CR | Nokia | 33.122 18.4.0 CR#83 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
not pursued | [WTS] [JSN] |
| S3-250477 | CAPIF-8 - Security aspects of RO authorization | CR | Nokia | 33.122 18.4.0 CR#84 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
merged | [WTS] [JSN] |
| S3-250478 | CAPIF-8 - Authorization for finer level service API access | CR | Nokia | 33.122 18.4.0 CR#85 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
not pursued | [WTS] [JSN] |
| S3-250479 | Security solution for revocation at CAPIF-8 | CR | Nokia | 33.122 18.4.0 CR#86 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
not pursued | [WTS] [JSN] |
| S3-250480 | RNAA authentication and authorization - mapping of API Invoker ID and GPSI |
CR revised to S3-251117 |
Nokia | 33.122 18.4.0 CR#87 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
revised | [WTS] [JSN] |
| S3-250481 | Requirements for secure retrieval of 5G system UE Ids and privacy related information |
CR revised to S3-251137 |
Nokia, Nokia Shanghai Bell | 33.501 19.1.0 CR#2093 catB | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
revised | [WTS] [JSN] |
| S3-250482 | Protecting XRM Media related information in connect-UDP | other | Nokia | Rel-19 |
S3-120 AI: 6 |
merged | [WTS] [JSN] | ||
| S3-250483 | LS reply on Issues related to Analytics context transfer between AnLF(s) |
LS out LS To: SA2 |
Nokia | Rel-18 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250484 | Correction of existing text in section 6.10 |
CR revised to S3-251118 |
Nokia | 33.122 18.4.0 CR#88 catF | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
revised | [WTS] [JSN] |
| S3-250485 | NRF verification of parameters | CR | Nokia, Huawei | 33.501 19.1.0 CR#2094 catF | 5G_eSBA_Ph2, TEI19 | Rel-19 |
S3-120 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
| S3-250486 | Adding missing abbreviations | CR | InterDigital | 33.700-32 19.0.0 CR#2 catF | FS_UIA_Sec | Rel-19 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-250487 | Clean Up for TR 33.757 |
pCR revised to S3-251067 |
China Telecommunications Corp.,ZTE | 33.757 0.6.0 | PLMNNPN_SEC | Rel-19 |
S3-120 AI: 5.3 |
revised | [WTS] [JSN] |
| S3-250488 | Presentation of Specification/Report to TSG: TR 33.757, Version 0.7.0 | TS or TR cover | China Telecommunications Corp.,ZTE | PLMNNPN_SEC | Rel-19 |
S3-120 AI: 5.3 |
approved | [WTS] [JSN] | |
| S3-250489 | Living CR for security for PLMN hosting a NPN |
draftCR revised to S3-251168 |
China Telecommunications Corp.,ZTE | PLMNNPN | Rel-19 |
S3-120 AI: 4.25 |
revised | [WTS] [JSN] | |
| S3-250490 | General |
other revised to S3-251068 |
China Telecommunications Corp.,ZTE | Rel-19 |
S3-120 AI: 4.25 |
revised | [WTS] [JSN] | ||
| S3-250491 | Update the conclusion for KI#2 | pCR | China Telecom | 33.700-22 0.4.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250492 | Update the conclusion of key issue #1.1 in TR 33.700-22 | pCR | China Telecom | 33.700-22 0.4.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250493 | Update the conclusion of key issue #1.2 in TR 33.700-22 | pCR | China Telecom | 33.700-22 0.4.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250494 | CR on Authentication and authorization for CAPIF interconnection | CR | China Telecom | 33.122 18.4.0 CR#89 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] |
| S3-250495 | CR of Resource owner authorization management | CR | China Telecom | 33.122 18.4.0 CR#90 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] |
| S3-250496 | Architecture |
other revised to S3-251069 |
China Telecommunications Corp.,ZTE | Rel-19 |
S3-120 AI: 4.25 |
revised | [WTS] [JSN] | ||
| S3-250497 | Proxy entity at the border | other | China Telecommunications Corp.,ZTE | Rel-19 |
S3-120 AI: 4.25 |
approved | [WTS] [JSN] | ||
| S3-250498 | AIoT - Concusion on KI#3 | pCR | Apple | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250499 | AIoT - Concusion on KI#4 | pCR | Apple | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250500 | Proposal for changing the description of SN counter in SCPAC |
CR revised to S3-250991 |
Apple | 33.501 19.1.0 CR#2095 catF | TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-250501 | Editorial change on Security handling in Control Plane CIoT 5GS Optimization |
CR revised to S3-251161 |
Apple, NTT DOCOMO | 33.501 19.1.0 CR#2096 catF | TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-250502 | Discussion paper on AIML positioning | discussion | Apple |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250503 | Reply LS on AIML positioning |
LS out LS is reply to S3-250336 LS To: SA2 |
Apple |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250504 | LTM - Conclusions | other | Apple |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-250505 | LTM - Update to solution#4 | other | Apple |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-250506 | LTM - Update to solution#5 | other | Apple |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |||
| S3-250507 | LTM - Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-250325 LS To: RAN2 |
Apple |
S3-120 AI: 4.12 |
merged | [WTS] [JSN] | |||
| S3-250508 | Reply CT1 LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-250321 LS To: CT1 |
Apple |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-250509 | draft CR on Authentication and authorization for CAPIF interconnection | draftCR | China Telecom | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
merged | [WTS] [JSN] | |
| S3-250510 | draft CR of Resource owner authorization management |
draftCR revised to S3-251113 |
China Telecom | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
revised | [WTS] [JSN] | |
| S3-250511 | Reply to LS on security questions related to NAS layer overhead reduction for data transfer using control plane CIoT |
LS out LS is reply to S3-250316 LS To: S3-250316 |
Intel Sweden AB |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250512 | Discussion paper of NAS Overhead Reduction | discussion | Intel Sweden AB |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250513 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250514 | Conclusion for KI#3 | pCR | ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250515 | Conclusion for KI#4 | pCR | ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250516 | Conclusion for KI#6 |
pCR revised to S3-251103 |
ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250517 | Update Conclusion to Key issue 3 and 4 | pCR | Intel Sweden AB | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250518 | Discussion on Temp ID based AIOT device ID protection | discussion | OPPO | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] | ||
| S3-250519 | Clean up for TR 33.713 | pCR | ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250520 | Update Conclusion to Key issue 5 | pCR | Intel Sweden AB | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250521 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-250340 LS To: SA2 revised to S3-251055 |
OPPO | Rel-19 |
S3-120 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-250522 | Update AIOT KI#3 | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250523 | Update AIOT sol#24 | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250524 | Conclusion on AIOT KI#3 | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250525 | Security Considerations for Store and Forward (S&F) Satellite Operation | CR | Intel Sweden AB | 33.401 18.2.0 CR#723 catB | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
not pursued | [WTS] [JSN] |
| S3-250526 | Reply LS on User Privacy Aspects of LMF-based AIML positioning |
LS out LS is reply to S3-250336 LS To: SA2 |
OPPO | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250527 | Update AIOT sol#7 |
pCR revised to S3-251110 |
OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250528 | Update AIOT sol#37 | pCR | Xidian University, OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250529 | Correction of TC UP integrity check failure | CR | Nokia, Nokia Shanghai Bell | 33.511 19.0.0 CR#72 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
merged | [WTS] [JSN] |
| S3-250530 | [draft] reply LS to CT1 on UE behaviour in case of SUCI calculation failure |
LS out LS To: CT1 |
ZTE Corporation | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250531 | Update conclusion on AIOT KI#5 | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250532 | [draft] reply LS to CT4 on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS To: CT4 |
ZTE Corporation | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250533 | draft - Reply LS on clarification on home network triggered re-authentication |
LS out LS To: CT4 |
ZTE Corporation | HN_Auth | Rel-18 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-250534 | Security aspects for Indirect Network Sharing | CR | ZTE Corporation | 33.501 19.1.0 CR#2097 catF | TEI19 | Rel-19 |
S3-120 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-250535 | Correct the procedure of notification about AKMA service disabling | CR | ZTE Corporation | 33.535 18.6.0 CR#223 catF | AKMA_Ph2 | Rel-18 |
S3-120 AI: 4.1.5 |
agreed | [WTS] [JSN] |
| S3-250536 | Clarifications for HONTRA procedure with respect to failure cases | CR | ZTE | 33.501 18.8.0 CR#2098 catF | HN_Auth | Rel-18 |
S3-120 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-250537 | Correction of parameters stored in AAnF | CR | ZTE Corporation | 33.535 18.6.0 CR#224 catF | AKMA_Ph2 | Rel-18 |
S3-120 AI: 4.1.5 |
agreed | [WTS] [JSN] |
| S3-250538 | Clarifications for HONTRA procedure with respect to failure cases | CR | ZTE | 33.501 19.1.0 CR#2099 catA | HN_Auth | Rel-19 |
S3-120 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-250539 | reply LS to RAN2 on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-250325 LS To: RAN2 |
ZTE Corporation | Rel-19 |
S3-120 AI: 4.12 |
merged | [WTS] [JSN] | ||
| S3-250540 | Draft skeleton for TS 33.545 Femto security | draft TS | ZTE Corporation | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] | |
| S3-250541 | Scope of TS 33.545 |
pCR revised to S3-250980 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250542 | Overview of Security Architecture and Requirements of TS 33.545 | pCR | ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250543 | Device Authentication clause 5.1 | pCR | ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250544 | Hosting Party Authentication clause 5.2 |
pCR revised to S3-250984 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250545 | Update conclusion for KI#1 | other | ZTE Corporation | NR_Mob_Ph4_Sec |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | ||
| S3-250546 | Location Security clause 5.3 |
pCR revised to S3-250985 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250547 | Backhaul Link Protection clause 5.4 |
pCR revised to S3-250986 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250548 | Update Security mechanism and procedures for inter-CU LTM | other | ZTE Corporation | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250549 | Access Control Mechanisms clause 5.5 | pCR | ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250550 | Topology Hiding clause 5.6 |
pCR revised to S3-250988 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250551 | security mechanism for S&F operation in full EPC onboard architecture | other | ZTE Corporation | 5GSAT_Ph3_SEC |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | ||
| S3-250552 | security mechanism for S&F operation in split-MME architecture | other | ZTE Corporation |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |||
| S3-250553 | resolving ENs in sol#6 in TR 33.713 |
pCR revised to S3-251109 |
ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250554 | Authentication and authorization for digital asset services | other | ZTE Corporation |
S3-120 AI: 4.21 |
noted | [WTS] [JSN] | |||
| S3-250555 | Evaluation for solution 6 |
pCR revised to S3-251108 |
ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250556 | Authentication and authorization for spatial localization services |
other revised to S3-251052 |
ZTE Corporation |
S3-120 AI: 4.21 |
revised | [WTS] [JSN] | |||
| S3-250557 | resolving ENs in sol#25 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250558 | Privacy protection for user information exposure | other | ZTE Corporation |
S3-120 AI: 4.21 |
noted | [WTS] [JSN] | |||
| S3-250559 | Security procedures for CAPIF-8 reference points | other | ZTE Corporation |
S3-120 AI: 4.22 |
noted | [WTS] [JSN] | |||
| S3-250560 | Security requirements on the CAPIF-6/6e reference points | other | ZTE Corporation |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] | |||
| S3-250561 | Security requirements on the CAPIF-6/6e reference points | other | ZTE Corporation |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] | |||
| S3-250562 | Security requirements on the CAPIF-6/6e reference points | other | ZTE Corporation |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] | |||
| S3-250563 | Security requirements on the CAPIF-6/6e reference points | other | ZTE Corporation |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] | |||
| S3-250564 | Security requirements on the CAPIF-6/6e reference points | other | ZTE Corporation |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] | |||
| S3-250565 | Security requirements on the CAPIF-6/6e reference points | other | ZTE Corporation |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] | |||
| S3-250566 | Clean up for TR 33.745 | CR | ZTE Corporation | 33.745 19.0.0 CR#1 catF | FS_5G_Femto_Sec | Rel-19 |
S3-120 AI: 5.17 |
agreed | [WTS] [JSN] |
| S3-250567 | Security requirements on the CAPIF-6/6e reference points | other | ZTE Corporation |
S3-120 AI: 4.22 |
merged | [WTS] [JSN] | |||
| S3-250568 | NWDAF VFL server authorization | draftCR | Nokia | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250569 | Reply LS on User Privacy Aspects of LMF-based AI/ML positioning |
LS out LS is reply to S3-250336 LS To: SA2 |
Nokia | AIML_CN_SEC | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-250570 | Reply LS on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-250319 LS To: SA2 |
Nokia | TEI19 | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-250571 | Security related to Indirect Network Sharing | CR | Nokia | 33.501 19.1.0 CR#2100 catF | TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-250572 | eNA related API Name correction |
CR revised to S3-250989 |
Nokia | 33.501 18.8.0 CR#2101 catF | TEI18 | Rel-18 |
S3-120 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-250573 | eNA related API Name correction |
CR revised to S3-250990 |
Nokia | 33.501 19.1.0 CR#2102 catA | TEI18 | Rel-19 |
S3-120 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-250574 | WWC related alignment | CR | Nokia | 33.501 19.1.0 CR#2103 catD | TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-250575 | SUCI error handling | CR | Nokia | 33.501 19.1.0 CR#2104 catF | TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-250576 | Reply LS on Clarifications related to the parameter to support 5G ProSe in SNPN |
LS out LS is reply to S3-250315 LS To: CT1 revised to S3-251121 |
China Telecom Corporation Ltd. | Rel-19 |
S3-120 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-250577 | Adding conclusion for KI#2 | pCR | ZTE Corporation | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-250578 | Update overall summary | pCR | ZTE Corporation | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-250579 | Adding conclusion to KI#3 | pCR | ZTE Corporation | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250580 | Address the Note in U2N conclusion |
pCR revised to S3-251038 |
China Telecom Corporation Ltd. | 33.743 1.0.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-120 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-250581 | Reply LS to CT4 on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-250319 LS To: CT4 |
China Unicom |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250582 | Correct the CCF associated with the registered AEF in KI#2 | pCR | ZTE Corporation | 33.700-22 0.4.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250583 | LS reply on Issues related to Analytics context transfer between AnLF(s) |
LS out LS To: SA2 |
Ericsson | Rel-18 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250584 | New WID on specification of alternative example f5* (f5**) function |
WID new revised to S3-251154 |
Ericsson, Thales, Qualcomm Incorporated | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-250585 | Skeleton of specification of alternative example f5* (f5**) function |
other revised to S3-251155 |
Ericsson, Thales | DUMMY | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | |
| S3-250586 | pCR to f5** specification TS | other | Ericsson, Thales | DUMMY | Rel-19 |
S3-120 AI: 6 |
approved | [WTS] [JSN] | |
| S3-250587 | Presentation of specification of alternative example f5* (f5**) function |
other revised to S3-251156 |
Ericsson, Thales | DUMMY | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | |
| S3-250588 | Clarifying the naming for the new alternative example f5* (f5**) function |
CR revised to S3-251157 |
Ericsson, Thales | 33.102 18.0.0 CR#285 catD | DUMMY | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] |
| S3-250589 | Adding a reference for the new alternative example f5* (f5**) function |
CR revised to S3-251158 |
Ericsson, Thales | 35.205 18.0.0 CR#1 catB | DUMMY | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] |
| S3-250590 | Adding a reference for the new alternative example f5* function |
CR revised to S3-251159 |
Ericsson, Thales | 35.231 18.0.0 CR#8 catB | DUMMY | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] |
| S3-250591 | UE ID Token based mechanism | CR | Ericsson | 33.558 18.2.0 CR#20 catB | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
not pursued | [WTS] [JSN] |
| S3-250592 | UE ID Token based mechanism for 33501 | CR | Ericsson | 33.501 19.1.0 CR#2105 catB | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
not pursued | [WTS] [JSN] |
| S3-250593 | Fixing API invoker onboarding – Rel15 | CR | Ericsson | 33.122 15.4.0 CR#91 catF | CAPIF-Sec | Rel-15 |
S3-120 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-250594 | Fixing API invoker onboarding – Rel16 | CR | Ericsson | 33.122 16.4.0 CR#92 catA | CAPIF-Sec | Rel-16 |
S3-120 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-250595 | Fixing API invoker onboarding – Rel17 | CR | Ericsson | 33.122 17.1.0 CR#93 catA | CAPIF-Sec | Rel-17 |
S3-120 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-250596 | Fixing API invoker onboarding – Rel18 |
CR revised to S3-251132 |
Ericsson | 33.122 18.4.0 CR#94 catA | CAPIF-Sec | Rel-18 |
S3-120 AI: 4.1.15 |
revised | [WTS] [JSN] |
| S3-250597 | New solution for onboarding of UE hosted API invoker |
pCR revised to S3-251019 |
Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250598 | Resolving ENs and evaluation of solution #26 |
pCR revised to S3-251004 |
Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250599 | Moving CIBA discussion from KI#1.2 to KI#3 |
pCR revised to S3-251026 |
Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250600 | Further conclusion for key issue #1.1 | pCR | Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250601 | Further conclusion for key issue #1.2 | pCR | Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250602 | Further conclusion for key issue #1.3 | pCR | Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250603 | Further conclusion for key issue #2 |
pCR revised to S3-251001 |
Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250604 | Further conclusion for key issue #3 | pCR | Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250605 | Conclusion for key issue #4 | pCR | Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250606 | Conclusion for key issue #5 | pCR | Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250607 | Conclusion for key issue #6 | pCR | Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250608 | Updates for CAPIF interconnection | CR | Ericsson | 33.122 18.4.0 CR#95 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
not pursued | [WTS] [JSN] |
| S3-250609 | Add scope and definition in TS 33.503 |
other revised to S3-251040 |
China Telecom Corporation Ltd. | Rel-19 |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | ||
| S3-250610 | Add multi-hop description in PKMF and AUSF |
other revised to S3-251041 |
China Telecom Corporation Ltd. |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |||
| S3-250611 | Add multi-hop description in PKMF and AUSF | other | China Telecom Corporation Ltd. |
S3-120 AI: 4.15 |
withdrawn | [WTS] [JSN] | |||
| S3-250612 | KI#3, Conclusions | pCR | Sony | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250613 | Security enhancement for indirect network sharing | CR | China Unicom | 33.501 19.1.0 CR#2106 catB | TEI19 | Rel-19 |
S3-120 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-250614 | Add description for protection of communication data used in VFL process |
other revised to S3-251062 |
China Mobile | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
revised | [WTS] [JSN] | |
| S3-250615 | Add NEF requirements of X.12 | other | China Mobile | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-250616 | Add user consent description of X.11 |
other revised to S3-251058 |
China Mobile | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
revised | [WTS] [JSN] | |
| S3-250617 | Draft skeleton for AIML_CN_SEC |
draftCR revised to S3-251056 |
China Mobile, Vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
revised | [WTS] [JSN] | |
| S3-250618 | General description of X.11 | other | China Mobile | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
noted | [WTS] [JSN] | |
| S3-250619 | General description of X.12 | other | China Mobile | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250620 | Add description to the General Clause | draftCR | China Mobile | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250621 | Security aspects on full EPC in each satellite | draftCR | China Mobile | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250622 | Pseudo-CR on Lightweight authentication and privacy protection for inventory and command procedure |
pCR revised to S3-251104 |
China Mobile | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250623 | Pseudo-CR-New solution on AIoT privacy for TR 33.713 |
pCR revised to S3-251105 |
China Mobile | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250624 | Pseudo-CR-Add the scope for Femto in TS 33.545 | pCR | China Mobile | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250625 | Pseudo-CR- Add terms and abbriviations for Femto in TS 33.545 | pCR | China Mobile | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250626 | Pseudo-CR-System architecture and security assumption for Femto in TS 33.545 |
pCR revised to S3-250982 |
China Mobile | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250627 | Pseudo-CR-Void solution#36 in TR 33.713 |
pCR revised to S3-250641 |
China Mobile | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250628 | Pseudo-CR-The support of location security in TS 33.545 | pCR | China Mobile | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250629 | Security requirement for ProSe Multi-hop U2N Discovery | other | China Telecom Corporation Ltd. |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |||
| S3-250630 | New mini WID on Security Aspects of Indirect Network Sharing | WID new | China Unicom |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250631 | Updates to Overall Summary of solutions |
pCR revised to S3-250995 |
Nokia | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-250632 | Security procedure for ProSe Multi-hop U2N Discovery | other | China Telecom Corporation Ltd. |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |||
| S3-250633 | Clean Up for TR 33.749 |
pCR revised to S3-251082 |
China Unicom | 33.749 0.5.0 | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 5.14 |
revised | [WTS] [JSN] |
| S3-250634 | Security procedure for ProSe Multi-hop U2N Communication | other | China Telecom Corporation Ltd. |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |||
| S3-250635 | Security requirement for ProSe Multi-hop U2U Discovery | other | China Telecom Corporation Ltd. |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |||
| S3-250636 | Update clause 5.3 for femto location security | pCR | Nokia | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250637 | Update clause 3.1 to add relevant terms and its definitions. |
pCR revised to S3-250981 |
Nokia | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250638 | Presentation of Report to TSG: TR 33.749, Version 1.0.0 | TS or TR cover | China Unicom | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 5.14 |
approved | [WTS] [JSN] | |
| S3-250639 | Update clause 5.2 for femto hosting party authentication | pCR | Nokia | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250640 | Correction of TC UP replay protection | CR | Nokia, Nokia Shanghai Bell | 33.511 19.0.0 CR#73 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-250641 | Pseudo-CR-Void solution#36 in TR 33.713 |
pCR revision of S3-250627 |
China Mobile | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250642 | KI#4, Conclusions | pCR | Sony | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250643 | Correction of TC RRC replay protection | CR | Nokia, Nokia Shanghai Bell | 33.511 19.0.0 CR#74 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-250644 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-250325 source LS: R2-2411136 LS To: RAN2 |
Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
merged | [WTS] [JSN] | |
| S3-250645 | conclusion on NCC handling for inter-CU LTM in non-DC cases | other | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250646 | Update on the mismatched UE security context handling in non-DC cases | other | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250647 | discussion paper on the security issue where CU is acting as MN and SN is unchanged | discussion | Huawei, HiSilicon | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250648 | Editorial change to AKMA procedure | CR | Huawei, HiSilicon | 33.535 18.6.0 CR#225 catF | AKMA_Ph2 | Rel-18 |
S3-120 AI: 4.1.5 |
agreed | [WTS] [JSN] |
| S3-250649 | Proposed baseline for conclusion on KI#4 |
pCR revised to S3-250975 |
Huawei, HiSilicon, OPPO, China Unicom, Lenovo, ZTE, CATT, Xiaomi, Philips International B.V. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250650 | Additional update to the proposed baseline for conclusion on key issue#4 | pCR | Huawei, HiSilicon | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250651 | Update to generic conclusion |
pCR revised to S3-250963 |
Huawei, HiSilicon | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250652 | Update to key issue#5 | pCR | Huawei, HiSilicon | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250653 | reply LS on Device Subscription Data |
LS out LS is reply to S3-250338 source LS: S2-2501242 LS To: SA2 revised to S3-251102 |
Huawei, HiSilicon | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] | ||
| S3-250654 | Update conclusion on key issue#1 | CR | Huawei, HiSilicon | 33.784 19.0.0 CR#1 catB | FS_AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.1.13 |
not pursued | [WTS] [JSN] |
| S3-250655 | Update conclusion on key issue#2 | CR | Huawei, HiSilicon | 33.784 19.0.0 CR#2 catB | FS_AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.1.13 |
not pursued | [WTS] [JSN] |
| S3-250656 | Authorization of LMF retrieval of a trained AI/ML model for positioning |
other revised to S3-251140 |
Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
revised | [WTS] [JSN] | |
| S3-250657 | Update conclusion on key issue#3 | CR | Huawei, HiSilicon | 33.784 19.0.0 CR#3 catB | FS_AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.1.13 |
not pursued | [WTS] [JSN] |
| S3-250658 | Update NEF security requirements for VFL | other | Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
noted | [WTS] [JSN] | |
| S3-250659 | Reply LS on Issues related Analytics context transfer between AnLFs |
LS out LS is reply to S3-250330 source LS: S2-2409441 LS To: SA2 |
Huawei, HiSilicon | Rel-18 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250660 | Discussion paper on the security establishment of QUIC protocol used in 3GPP | discussion | Huawei, HiSilicon | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250661 | New SID on security aspects for MPQUIC |
SID new revised to S3-251153 |
Huawei, HiSilicon | Rel-20 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-250662 | Security aspects on store and forward operation with split MME architecture | other | Huawei, HiSilicon | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250663 | Reply to LS on User Privacy Aspects of LMF-based AI/ML positioning |
LS out LS is reply to S3-250336 source LS: S2-2412940 LS To: SA2 |
Huawei, HiSilicon | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250664 | Resolve EN for KI2 Conclusion |
pCR revised to S3-251013 |
Huawei, HiSilicon | 33.766 0.6.0 | FS_Energy_Sec | Rel-19 |
S3-120 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-250665 | Authorization of VFL members (External AF as a Server) |
other revised to S3-251061 |
Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
revised | [WTS] [JSN] | |
| S3-250666 | Protection of communication data used in VFL process | other | Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250667 | Privacy of VFL during sample Alignment ( NWDAF as a server) | other | Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
noted | [WTS] [JSN] | |
| S3-250668 | General Clause for 12.x | other | Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250669 | Authorization for selection of VFL participants in VFL Group NWDAF As VFL Server |
other revised to S3-251060 |
Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
revised | [WTS] [JSN] | |
| S3-250670 | pCR to update the draft skeleton X.12.3 | other | Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
noted | [WTS] [JSN] | |
| S3-250671 | Clearn up TR 33.743 |
pCR revised to S3-251037 |
Huawei, HiSilicon | 33.743 1.0.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-120 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-250672 | Cover sheet Draft TR 33.743 | TS or TR cover | Huawei, HiSilicon | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-120 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-250673 | Reply LS on on Clarifications related to the parameter to support 5G ProSe in SNPN |
LS out LS is reply to S3-250315 source LS: C1-247074 LS To: CT1 |
Huawei, HiSilicon | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250674 | Reply LS on ProSe Message Content Type extensions for Release 19 |
LS out LS is reply to S3-250314 source LS: C1-247001 LS To: CT1 |
Huawei, HiSilicon | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250675 | Update to the scope and terminology of ProSe draftCR | other | Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |
| S3-250676 | Adapts the reference point details and security requirements to multi-hop use cases | other | Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |
| S3-250677 | Update functional entities and services to support multi-hop services | other | Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |
| S3-250678 | Adding general introduction and security requirements of multi-hop UE-to-Network Relay to ProSe draftCR |
other revised to S3-251080 |
Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |
| S3-250679 | Adding Security flow of Multi-hop UE-to-Network Relay discovery procedure to ProSe draftCR | other | Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |
| S3-250680 | Adding Security flow of Multi-hop UE-to-Network Relay security establishment procedure to ProSe draftCR |
other revised to S3-251043 |
Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |
| S3-250681 | Adding general introduction and security requirements of multi-hop UE-to-UE Relay to ProSe draftCR |
other revised to S3-251044 |
Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |
| S3-250682 | Adding Security flow of L3 Multi-hop UE-to-UE Relay discovery procedure to ProSe draftCR | other | Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |
| S3-250683 | Adding Security flow of L3 Multi-hop UE-to-UE Relay security establishment procedure to ProSe draftCR |
other revised to S3-251046 |
Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |
| S3-250684 | Update metaverse draftCR to support Authentication and authorisation for digital asset services | other | Huawei, HiSilicon | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
noted | [WTS] [JSN] | |
| S3-250685 | Update metaverse draftCR to support Authentication and authorisation for spatial localisation services | other | Huawei, HiSilicon | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
merged | [WTS] [JSN] | |
| S3-250686 | Discussion paper on the security aspects of Integrated Sensing and Communication | discussion | Huawei, HiSilicon | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250687 | Living document for 5G_ProSe_Sec_Ph3 skeleton |
draftCR revised to S3-251039 |
Huawei, HiSilicon, China Telecom | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |
| S3-250688 | Error correction and clarfication in clause 4.2.2.1.19 to TS 33.216 |
CR revised to S3-251098 |
Huawei, HiSilicon | 33.216 18.1.0 CR#28 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250689 | Update test case to clause 4.2.2.1.20 | CR | Huawei, HiSilicon | 33.216 18.1.0 CR#29 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-250690 | Reformulation to avoid normative language in test description | CR | Huawei, HiSilicon | 33.216 18.1.0 CR#30 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-250691 | Added missing references | CR | Huawei, HiSilicon | 33.116 18.0.0 CR#5 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-250692 | Adding missing references | CR | Huawei, HiSilicon | 33.250 18.0.0 CR#6 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-250693 | Skeleton update to clause 4 | other | Huawei, HiSilicon | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] | |
| S3-250694 | Content to clause 4.X Security Architecture of NR Femto | other | Huawei, HiSilicon | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] | |
| S3-250695 | Content to 4.Y.1 Functional entities | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250696 | Content to 4.Y.1.1 NR Femto | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250697 | Content to 4.Y.1.2 Security Gateway (SeGW) | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250698 | Content to 4.Y.1.3 NR Femto Mgmt System | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250699 | Content to 4. Y.1.4 AAA Server/AUSF and UDM |
pCR revised to S3-251135 |
Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250700 | Content to 4.Y.2 Reference points | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250701 | Content to clause 5 Security Feature Enhancements | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250702 | Content to clause 5.1 Device Authentication |
pCR revised to S3-250983 |
Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250703 | Content to clause 5.2 Hosting party Authentication | other | Huawei, HiSilicon | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] | |
| S3-250704 | Content to clause 5.3 Location security | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250705 | clarification in UP IP activation-R17 | CR | Huawei, HiSilicon | 33.401 17.6.0 CR#724 catF | TEI17 | Rel-17 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-250706 | clarification in UP IP activation-R18 | CR | Huawei, HiSilicon | 33.401 18.2.0 CR#725 catA | TEI17 | Rel-18 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-250707 | clarification in UP IP activation-R19 | CR | Huawei, HiSilicon | 33.401 18.2.0 CR#726 catA | TEI17 | Rel-19 |
S3-120 AI: 4.1.15 |
withdrawn | [WTS] [JSN] |
| S3-250708 | Content to clause 5.4 Backhaul Link Protection | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250709 | Content to clause 5.5 Access Control Mechanisms For Femto |
pCR revised to S3-250987 |
Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
revised | [WTS] [JSN] |
| S3-250710 | Contentt to clause 5.6 Topology Hiding | pCR | Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
merged | [WTS] [JSN] |
| S3-250711 | other | Huawei, HiSilicon | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
withdrawn | [WTS] [JSN] | ||
| S3-250712 | Way forward for key issue #3 on privacy | discussion | Huawei, HiSilicon | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] | |
| S3-250713 | Way forward for key issue #4 on communication security | discussion | Huawei, HiSilicon | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] | |
| S3-250714 | Way forward for key issue #5 on the authentication framework | discussion | Huawei, HiSilicon | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] | |
| S3-250715 | On the Rel-20 planning | discussion | Huawei, HiSilicon | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250716 | Notification about AKMA service disabling via NEF |
CR revised to S3-251063 |
Huawei, HiSilicon | 33.535 18.6.0 CR#226 catF | AKMA_Ph2 | Rel-18 |
S3-120 AI: 4.1.5 |
revised | [WTS] [JSN] |
| S3-250717 | KI#5, Updated Conclusions | pCR | Sony | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250718 | Content to X.11.2 Security for data collection for the LMF-based AIML positioning | other | OPPO | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | ||
| S3-250719 | Adding Note to TC_BVT_PORT_SCANNING on external interfaces |
CR revised to S3-251099 |
BSI | 33.117 19.0.2 CR#199 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250720 | Adding Note to TC_RESTRICTED_REACHABILITY_OF_SERVICES |
CR revised to S3-251100 |
BSI | 33.117 19.0.2 CR#200 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250721 | Correction of Expected Results in AS algorithm selection in Handover scenario |
CR revised to S3-251138 |
BSI | 33.511 19.0.0 CR#75 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250722 | Clarification of gNB SCAS test cases where an “or” could lead to missing test coverage. |
CR revised to S3-251133 |
BSI | 33.511 19.0.0 CR#76 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250723 | Clarification of gNB SCAS wording |
CR revised to S3-251101 |
BSI | 33.511 19.0.0 CR#77 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250724 | Correction and clarification of TC_AMF_NAS_INTEGRITY_FAILURE | draftCR | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
approved | [WTS] [JSN] | |
| S3-250725 | pCR to TR33.700-22 Conclusion for KI#3 | pCR | CATT | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250726 | Motivation for RES* verification SCAS test for AUSF in roaming scenarios | discussion | BSI (DE) | SCAS_5G_Maint |
S3-120 AI: 4. |
noted | [WTS] [JSN] | ||
| S3-250727 | Add threat description about the implications of the AUSF not validating RES* correctly | CR | BSI, Montsecure | 33.926 19.3.0 CR#102 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-250728 | Add test case that verifies if the AUSF processes RES* failures correctly | draftCR | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
noted | [WTS] [JSN] | |
| S3-250729 | Add threat description about the implications of the AUSF confirming an authentication with the SUPI whi e the authentication was started with the SUCI | CR | BSI, Montsecure | 33.926 19.3.0 CR#103 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-250730 | Add test case TC_AUSF_CONFIRMATION_WITH_SUPI that check whether the AUSF is vulnerable to a confirmation attack | draftCR | BSI (DE) | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
noted | [WTS] [JSN] | |
| S3-250731 | Updates to Terms, Abbreviations and Overview |
CR revised to S3-251011 |
Ericsson | 33.256 18.2.0 CR#51 catB | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
revised | [WTS] [JSN] |
| S3-250732 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-250325 LS To: RAN2,RAN3 revised to S3-251124 |
CATT | Rel-19 |
S3-120 AI: 4.12 |
revised | [WTS] [JSN] | ||
| S3-250733 | UUAA in 5GS updates | CR | Ericsson | 33.256 18.2.0 CR#52 catB | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
noted | [WTS] [JSN] |
| S3-250734 | New WID on Protection of XRM Media related information | WID new | Ericsson | Rel-19 |
S3-120 AI: 6 |
withdrawn | [WTS] [JSN] | ||
| S3-250735 | Reply LS on Issues related to Analytics context transfer between AnLF(s) |
LS out LS is reply to S3-250330/S2-2409441 LS To: SA2 |
CATT | Rel-18 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250736 | pCR to TR33.700-29 Update conclusion#2 |
pCR revised to S3-250994 |
CATT | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
revised | [WTS] [JSN] |
| S3-250737 | Protecting XRM Media related information in QUIC aware forwarding |
CR revised to S3-251127 |
Ericsson | 33.501 19.1.0 CR#2107 catB | DUMMY | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] |
| S3-250738 | Skeleton for security aspects of 5G satellite access phase 3 |
draftCR revised to S3-250997 |
CATT | 5GSAT_Ph3_SEC | Rel-18 |
S3-120 AI: 4.19 |
revised | [WTS] [JSN] | |
| S3-250739 | Reply LS on User Privacy Aspects of LMF-based AI/ML positioning |
LS out LS is reply to S3-250336 LS To: SA2 |
Ericsson | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250740 | General description for security aspects of 5G satellite access phase 3 |
draftCR revised to S3-251119 |
CATT | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
revised | [WTS] [JSN] | |
| S3-250741 | Content to X.12.4 Protection of communication data used in VFL process | other | OPPO | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | ||
| S3-250742 | Security aspects of Split MME architecture | draftCR | CATT | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250743 | Security aspects of Full EPC in each satellite | draftCR | CATT | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250744 | pCR to TR33.713 Generic conclusion | pCR | CATT | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250745 | New solution for KI#2: Security of IMS based Avatar Communication |
pCR revised to S3-251142 |
Ericsson | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250746 | Conclusion update for KI#2: Security of IMS based Avatar Communication | pCR | Ericsson | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-250747 | Conclusion update for KI#3: Security and privacy aspects of IMS DC capability exposure |
pCR revised to S3-251075 |
Ericsson | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250748 | TR 33.790 cleanup |
pCR revised to S3-251076 |
Ericsson | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250749 | Presentation of Report to TSG: TR 33.790 Study on the security support for the next generation real time communication services phase 2, Version 1.2.0 | TS or TR cover | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
noted | [WTS] [JSN] | |
| S3-250750 | Proposal for a living document for NG_RTC_SEC_Ph2: draftCR to TS 33.203, Signing and verification of third party user identity information in IMS | draftCR | Ericsson | NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 4.23 |
approved | [WTS] [JSN] | |
| S3-250751 | Revised WID on security support for the Next Generation Real Time Communication services Phase 2 |
WID revised revised to S3-251151 |
Ericsson | NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | |
| S3-250752 | Rel-19 Work Item Exception for the Security support for the Next Generation Real Time Communication services Phase 2 (NG_RTC_SEC_Ph2) |
WI exception request revised to S3-251077 |
Ericsson | NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 4.23 |
revised | [WTS] [JSN] | |
| S3-250753 | pCR to TR33.713 Conclusion#3 | pCR | CATT | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250754 | VFL Authorization when the External AF acts as a VFL Server | CR | Ericsson | 33.501 19.1.0 CR#2108 catB | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
not pursued | [WTS] [JSN] |
| S3-250755 | pCR to TR33.713 Conclusion#4 | pCR | CATT | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250756 | pCR to TR33.713 Conclusion#5 | pCR | CATT | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250757 | pCR to TR33.713 New solution AIoT command message security protection procedure |
pCR revised to S3-251106 |
CATT | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250758 | Solution#1 update - Addressing Ens |
pCR revised to S3-251107 |
Philips International B.V. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250759 | KI#1 conclusion |
pCR revised to S3-250967 |
Philips International B.V. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250760 | KI#2 conclusion | pCR | Philips International B.V. | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-250761 | Security for S&F satellite operation - General | draftCR | Philips International B.V. | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250762 | Security for S&F satellite operation - Split MME architecture |
draftCR revised to S3-251036 |
Philips International B.V. | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
revised | [WTS] [JSN] | |
| S3-250763 | Security for S&F satellite operation - Full EPC onboard | draftCR | Philips International B.V. | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250764 | New SID on enhanced security management service about security policy provisioni | SID new | China Mobile Com. Corporation |
S3-120 AI: 6 |
noted | [WTS] [JSN] | |||
| S3-250765 | Living document on NR mobility enhancement | draftCR | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
approved | [WTS] [JSN] | |
| S3-250766 | Solution for inter-CU LTM and conclusion | other | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250767 | Security procedure for inter-CU LTM | other | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250768 | Rel-19 Work item exception for NR_Mob_Ph4_Sec |
WI exception request revised to S3-251162 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
revised | [WTS] [JSN] | |
| S3-250769 | [Draft] Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-250325 source LS: R2-2411136 LS To: RAN2 |
Samsung |
S3-120 AI: 4.12 |
merged | [WTS] [JSN] | |||
| S3-250770 | Updates to conclusion for key issue#2 | pCR | Samsung | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250771 | Conclusion for key issue#4 (Nested API invocation) |
pCR revised to S3-251023 |
Samsung | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250772 | Security procedures for CAPIF interconnection |
other revised to S3-251116 |
Samsung | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
revised | [WTS] [JSN] | |
| S3-250773 | Security procedures for nested API invocation | other | Samsung | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
noted | [WTS] [JSN] | |
| S3-250774 | Access policy enforcement | other | Samsung, Nokia | PLMNNPN | Rel-19 |
S3-120 AI: 4.25 |
noted | [WTS] [JSN] | |
| S3-250775 | DNS Message Security | other | Samsung | PLMNNPN | Rel-19 |
S3-120 AI: 4.25 |
approved | [WTS] [JSN] | |
| S3-250776 | SUPI privacy for PLMN hosted NPN |
other revised to S3-251070 |
Samsung | PLMNNPN | Rel-19 |
S3-120 AI: 4.25 |
revised | [WTS] [JSN] | |
| S3-250777 | Update to conclusion for Key Issue#3 | pCR | Samsung | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250778 | Presentation of Report to TSG SA: TR 33.721, Version 0.7.0 |
TS or TR cover revised to S3-251051 |
Samsung | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
revised | [WTS] [JSN] | |
| S3-250779 | Skeleton for security aspects of 5G mobile metaverse services | draftCR | Samsung | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
approved | [WTS] [JSN] | |
| S3-250780 | Authentication and authorization for spatial localization services | other | Samsung | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
merged | [WTS] [JSN] | |
| S3-250781 | Authentication and authorization for digital asset services | other | Samsung | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
noted | [WTS] [JSN] | |
| S3-250782 | Privacy protection for user information exposure | other | Samsung | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
noted | [WTS] [JSN] | |
| S3-250783 | Rel-19 Work item exception for Metaverse_Sec |
WI exception request revised to S3-251054 |
Samsung | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
revised | [WTS] [JSN] | |
| S3-250784 | Revise WID on security aspects of 5G Mobile Metaverse services |
WID revised revised to S3-251129 |
Samsung | Metaverse_Sec | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | |
| S3-250785 | Discussion paper on SUCI calculation failure | discussion | Samsung |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250786 | [draft] Reply LS on UE behaviour in case of SUCI calculation failure |
LS out source LS: C6-240721 LS To: CT1, CT6 |
Samsung |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-250787 | pCR on General part on S&F operation | other | Samsung | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250788 | pCR on Security for S&F operation on split MME architecture | other | Samsung | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250789 | pCR on Security for S&F operation on Full EPC architecture | other | Samsung | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250790 | Update to conclusion for key issue#2 | pCR | Samsung | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-250791 | Discussion on S&F operation for a split MME architecture | discussion | Samsung | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
noted | [WTS] [JSN] | |
| S3-250792 | Conclusion for KI#2 | pCR | Samsung | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-250793 | Update to solution #12 | pCR | Samsung | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250794 | Resolving EN on solution #22 | pCR | Samsung | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250795 | Evaluation update on solution #22 | pCR | Samsung | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250796 | Resolving EN on solution #38 | pCR | Samsung | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250797 | Evaluation update on solution #38 | pCR | Samsung | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250798 | Conclusion on KI#4 | pCR | Samsung | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250799 | DRAFT CR SBA Rel-19 public key or cert retrieval for access token verification |
draftCR revised to S3-251134 |
Ericsson | TEI19 | Rel-19 |
S3-120 AI: 4.11 |
revised | [WTS] [JSN] | |
| S3-250800 | Resolve ENs on authorized NRF in draft CR on Public key distribution and Issuer claim verification of the Access Token |
other revised to S3-250992 |
Ericsson | TEI19 |
S3-120 AI: 4.11 |
revised | [WTS] [JSN] | ||
| S3-250801 | Resolve EN on several NRFs in draft CR on Public key distribution and Issuer claim verification of the Access Token | other | Ericsson | TEI19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | ||
| S3-250802 | Resolve ENs on check failure in draft CR on Public key distribution and Issuer claim verification of the Access Token | other | Ericsson | TEI19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | ||
| S3-250803 | Resolve EN on access token service in draft CR on Public key distribution and Issuer claim verification of the Access Token | other | Ericsson | TEI19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | ||
| S3-250804 | Resolve ENs in draft CR on Public key distribution and Issuer claim verification of the Access Token | other | Ericsson | TEI19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | ||
| S3-250805 | Resolve EN on causes for validation failure in draft CR on Public key distribution and Issuer claim verification of the Access Token | other | Ericsson | TEI19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | ||
| S3-250806 | LS on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-250319 LS To: CT4 |
Ericsson | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250807 | Discussion on the NF consumer PLMN ID check | discussion | Ericsson |
S3-120 AI: 4.1.2 |
noted | [WTS] [JSN] | |||
| S3-250808 | Checking PLMNID of NF Service Consumer in interconnect scenario | CR | Ericsson | 33.501 17.14.0 CR#2109 catF | TEI17 | Rel-17 |
S3-120 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
| S3-250809 | Checking PLMNID of NF Service Consumer in interconnect scenario | CR | Ericsson | 33.501 18.8.0 CR#2110 catA | TEI17 | Rel-18 |
S3-120 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
| S3-250810 | Checking PLMNID of NF Service Consumer in interconnect scenario | CR | Ericsson | 33.501 19.1.0 CR#2111 catA | TEI17 | Rel-19 |
S3-120 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
| S3-250811 | Draft_LS on Checking PLMNID of NFc in interconnect scenario |
LS out LS To: CT4 |
Ericsson | Rel-16 |
S3-120 AI: 4.1.2 |
noted | [WTS] [JSN] | ||
| S3-250812 | Reply LS on User Privacy Aspects of LMF-based AI/ML positioning |
LS out LS To: SA2 |
Ericsson | AIML_CN | Rel-19 |
S3-120 AI: 3.1 |
withdrawn | [WTS] [JSN] | |
| S3-250813 | Token-based authorization for indirect communication scenarios when NF is selected at target PLMN | CR | Ericsson | 33.501 19.1.0 CR#2112 catB | TEI19_NFsel_by_tPLMN | Rel-19 |
S3-120 AI: 4.1.2 |
not pursued | [WTS] [JSN] |
| S3-250814 | Token-based authorization for indirect communication scenarios when NF is selected at source PLMN | CR | Ericsson | 33.501 19.1.0 CR#2113 catB | TEI19_NFsel_by_tPLMN | Rel-19 |
S3-120 AI: 4.1.2 |
merged | [WTS] [JSN] |
| S3-250815 | New key issue for secure storage in AIoT devices | pCR | Ericsson, Thales | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250816 | Updating General Conclusion | pCR | Ericsson | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250817 | Conclusion on KI#3 |
pCR revised to S3-251048 |
Ericsson | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250818 | Conclusion on Key Issue #4 | pCR | Ericsson | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250819 | New Key Issue on Amplification of resource exhaustion by exploiting AIoT paging messages |
pCR revised to S3-250959 |
Ericsson | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250820 | Update Solution #17 in TR 33.713 | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250821 | Editorial Correction to TR 33.794 |
CR revised to S3-251071 |
Motorola Mobility | 33.794 19.0.0 CR#1 catD | FS_eZTS | Rel-19 |
S3-120 AI: 5.1 |
revised | [WTS] [JSN] |
| S3-250822 | Resolution of EN in KI#1 conclusion |
pCR revised to S3-251012 |
Nokia | 33.766 0.6.0 | FS_Energy_Sec | Rel-19 |
S3-120 AI: 5.16 |
revised | [WTS] [JSN] |
| S3-250823 | Resolution of EN in KI#2 conclusion | pCR | Nokia | 33.766 0.6.0 | FS_Energy_Sec | Rel-19 |
S3-120 AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250824 | Presentation of Report to TSG: TR 33.766, Version 1.0.0 | TS or TR cover | Nokia | FS_Energy_Sec | Rel-19 |
S3-120 AI: 5.16 |
approved | [WTS] [JSN] | |
| S3-250825 | Proposal for a conclusion on KI#3 | pCR | Nokia | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250826 | Proposal for a conclusion on KI#4 | pCR | Nokia | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250827 | Proposal for a conclusion on KI#6 | pCR | Nokia | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250828 | Resolution of EN in solution 35 concerning device constrains | pCR | Nokia | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250829 | Refinement of EN in KI#5 | pCR | Nokia | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250830 | LS reply on Device Subscription Data |
LS out source LS: S2-2409441 LS To: SA2 |
Nokia | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-250831 | LS reply to LS on security aspects of Ambient IoT |
LS out LS is reply to S3-250340 source LS: S3-244641 LS To: SA2 |
Nokia | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-250832 | Security Monitoring |
WID new revised to S3-250944 |
AT&T, Charter Communications, Deutsche Telekom, KDDI, NTT DOCOMO, Telecom Italia, Vodafone | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-250833 | Security aspects on Split MME architecture | other | Xiaomi Technology Spain S.L | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
noted | [WTS] [JSN] | |
| S3-250834 | Reply LS on Device Subscription Data |
LS out LS is reply to S3-250338 source LS: S2-2501242 LS To: SA2 |
Xiaomi Technology Spain S.L | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250835 | Conclusion for KI#4 in TR 33.713 | pCR | Xiaomi Technology Spain S.L | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250836 | Updates to conclusion for KI#5 in TR 33.713 | pCR | Xiaomi Technology Spain S.L | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250837 | Updates to conclusion for KI#1 in TR 33.743 | pCR | Xiaomi Technology Spain S.L | 33.743 1.0.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-120 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-250838 | Reply LS on security questions related to NAS layer overhead reduction for data transfer using control plane CIoT |
LS out LS is reply to S3-250316 source LS: C1-247156 LS To: CT1 |
Xiaomi Technology Spain S.L | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250839 | Reply LS on ProSe Message Content Type extensions for Release 19 |
LS out LS is reply to S3-250314 source LS: C1-247001 LS To: CT1 |
Xiaomi Technology Spain S.L | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250840 | Protection mechanism for PC5 discovery messages with ProSe Message Content Type extensions |
other revised to S3-251047 |
Xiaomi Technology Spain S.L | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
revised | [WTS] [JSN] | |
| S3-250841 | Security flows for 5G ProSe Multi-hop UE-to-Network Relay Discovery | other | Xiaomi Technology Spain S.L | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |
| S3-250842 | Security procedure for 5G ProSe Multi-hop UE-to-Network Relay communication | other | Xiaomi Technology Spain S.L | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
merged | [WTS] [JSN] | |
| S3-250843 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-250321 source LS: C6-240721 LS To: CT1, CT6 |
Xiaomi Technology UK Limited | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250844 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-250325 source LS: R2-2411136 LS To: RAN2 |
Xiaomi Technology UK Limited | Rel-19 |
S3-120 AI: 4.12 |
merged | [WTS] [JSN] | ||
| S3-250845 | LTM: New Solution for NCC Encoding using C-RNTI | other | Xiaomi Technology UK Limited | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250846 | LTM: Update to Overall Summary | other | Xiaomi Technology UK Limited | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250847 | LTM: More Conclusion on Key Issue #1 | other | Xiaomi Technology UK Limited | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | |
| S3-250848 | Pseudo-CR on 33.721: Resolution of the Editor’s Notes in Solution #10 |
pCR revised to S3-251147 |
Xiaomi Technology UK Limited | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250849 | Pseudo-CR on 33.721: CAPIF-based Solution for Key Issue #4 |
pCR revised to S3-251050 |
Xiaomi Technology UK Limited | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250850 | Pseudo-CR on 33.721: Update to Conclusion on Key Issue #3 | pCR | Xiaomi Technology UK Limited | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250851 | Pseudo-CR on 33.721: Update to Conclusion on Key Issue #4 |
pCR revised to S3-251148 |
Xiaomi Technology UK Limited | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250852 | Revised WID on security aspects of CAPIF Phase3 |
WID revised revised to S3-251130 |
Xiaomi Technology Netherlands | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | |
| S3-250853 | Draft skeleton for CAPIF_Ph3_Sec | draftCR | Xiaomi Technology Netherlands | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
noted | [WTS] [JSN] | |
| S3-250854 | Rel-19 exception sheet for CAPIF_Ph3_sec |
WI exception request revised to S3-251031 |
Xiaomi Technology Netherlands | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
revised | [WTS] [JSN] | |
| S3-250855 | Conclusion for KI#4 of TR 33.700-22 | pCR | Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250856 | Conclusion for KI#6 of TR 33.700-22 |
pCR revised to S3-251025 |
Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250857 | TR 33.700-22 KI#1.1 conclusion update |
pCR revised to S3-250998 |
Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250858 | TR 33.700-22 KI#1.2 conclusion update | pCR | Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250859 | TR 33.700-22 KI#1.3 conclusion update | pCR | Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250860 | TR 33.700-22 KI#2 conclusion update | pCR | Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250861 | TR 33.700-22 KI#3 conclusion update | pCR | Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250862 | Resolve ENs in TR 33.700-22 KI#6 |
pCR revised to S3-251028 |
Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250863 | Resolve ENs in TR 33.700-22 solution #19 |
pCR revised to S3-251005 |
Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250864 | Resolve ENs in TR 33.700-22 solutions #8, #9, #20, and #31 |
pCR revised to S3-251006 |
Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250865 | TR 33.700-22 Reusing existing mechanism to enable cross-UE authorization |
pCR revised to S3-251022 |
Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250866 | Resource owner authorization management update | other | Xiaomi Technology Netherlands | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
merged | [WTS] [JSN] | |
| S3-250867 | LS reply on User Privacy Aspects of LMF-based AI ML positioning |
LS out LS is reply to S3-250336 source LS: S2-2412940 LS To: SA2 |
Xiaomi Technology Netherlands | AIML_CN_SEC | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-250868 | Authorization of candidate VFL participants for vertical federated learning | other | Xiaomi Technology Netherlands | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
merged | [WTS] [JSN] | |
| S3-250869 | Update for Solution #6 | other | LG Electronics | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | ||
| S3-250870 | Evaluation update for Solution #6 | other | LG Electronics | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | ||
| S3-250871 | Conclusion for Key issue #1 | other | LG Electronics | Rel-19 |
S3-120 AI: 4.12 |
noted | [WTS] [JSN] | ||
| S3-250872 | Update Conclusion for KI #2 | pCR | OPPO | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-250873 | Updating conclusion of KI#2 | pCR | Huawei, HiSilicon | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
noted | [WTS] [JSN] |
| S3-250874 | Solving ENs in Solution#5 | pCR | Huawei, HiSilicon | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250875 | Generic security aspects to support store and Forward operation | draftCR | Huawei, HiSilicon | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250876 | Security aspects on store and forward operation with full EPC in each satellite | draftCR | Huawei, HiSilicon | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | |
| S3-250877 | Reply LS on security questions related to NAS layer overhead reduction for data transfer using control plane CIoT |
LS out LS is reply to S3-250316 LS To: CT1 |
Huawei, HiSilicon | Rel-19 |
S3-120 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250878 | Update of conclusions KI#2 | pCR | Huawei, HiSilicon | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
merged | [WTS] [JSN] |
| S3-250879 | DraftCR for TS 33.558 on ID verification |
draftCR revised to S3-251126 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
revised | [WTS] [JSN] | |
| S3-250880 | DraftCR for TS 33.501 on the requirement of N6 deplay management protection. | draftCR | Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
merged | [WTS] [JSN] | |
| S3-250881 | Adding priciple on ID verification to draftCR of MEC ph3 |
draftCR revised to S3-251084 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
revised | [WTS] [JSN] | |
| S3-250882 | Adding token based mechanism to draftCR of MEC ph3 |
draftCR revised to S3-251085 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
revised | [WTS] [JSN] | |
| S3-250883 | Adding hash based mechanism draftCR of MEC ph3 |
draftCR revised to S3-251086 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
revised | [WTS] [JSN] | |
| S3-250884 | Adding Temporeary ID based mechanism draftCR of MEC ph3 |
draftCR revised to S3-251087 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
revised | [WTS] [JSN] | |
| S3-250885 | Remove ENs in Solution #32 and #33 | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250886 | Resolving ENs in Solution #42 of TR 33.713 | pCR | KPN | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250887 | Update to the clause 4.2.3.4.3.1 - Password Structure | CR | Huawei, HiSilicon | 33.117 19.0.2 CR#201 catF | SCAS_5G_Ph3 | Rel-19 |
S3-120 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-250888 | update conclusion for KI2 Privacy of user sensitive information |
pCR revised to S3-251065 |
Nokia, Nokia Shanghai Bell | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250889 | update conclusion for KI3 Security aspects of digital asset container in 5G |
pCR revised to S3-251049 |
Nokia, Nokia Shanghai Bell | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250890 | update conclusion for KI4 Authentication and authorization of digital representation | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250891 | input to metaverse sec draftCR for solution on KI1 | other | Nokia, Nokia Shanghai Bell | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
revised | [WTS] [JSN] | |
| S3-250892 | update conclusion for KI3 Security and privacy aspects of IMS DC capability exposure | pCR | Nokia, Nokia Shanghai Bell | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
merged | [WTS] [JSN] |
| S3-250893 | LS on Privacy and security aspects regarding DC management by the network |
LS out LS To: SA2 revised to S3-251144 |
Nokia, Nokia Shanghai Bell | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 3.1 |
revised | [WTS] [JSN] | |
| S3-250894 | Updates to Solution#11 | pCR | Lenovo | 33.757 0.6.0 | PLMNNPN_SEC | Rel-19 |
S3-120 AI: 5.3 |
noted | [WTS] [JSN] |
| S3-250895 | draft Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS To: CT1 |
THALES | Rel-19 |
S3-120 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-250896 | Update to solution 32 | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250897 | Enabling mTLS between ROF and CCF by CAPIF-specific key derivation |
pCR revised to S3-251014 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250898 | Solution on ROF and CCF to enable mTLS using AKMA |
pCR revised to S3-251016 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250899 | Onboarding solution |
pCR revised to S3-251017 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250900 | Solution on ROF certificate |
pCR revised to S3-251029 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250901 | Additional aspects for KI6 onboarding |
pCR revised to S3-251027 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250902 | Solution 3 Security procedures for CAPIF-8 reference points - EN resolution |
pCR revised to S3-251020 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250903 | Solution 7 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250904 | Solution 8 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250905 | Solution 9 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250906 | Solution 12 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250907 | Solution 13 evaluation and EN resolution | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250908 | Solution 14 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250909 | Solution 15 update | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250910 | Solution 16 update | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250911 | Solution 17 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250912 | Solution 18 evaluation |
pCR revised to S3-251021 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250913 | Solution 19 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250914 | Solution 20 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250915 | Solution 24 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250916 | Solution 26 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250917 | Solution 28 update and evaluation |
pCR revised to S3-251015 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250918 | Solution 29 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250919 | Solution 31 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250920 | Solution 32 evaluation |
pCR revised to S3-251018 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250921 | Solution 33 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250922 | Solution 34 evaluation | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250923 | Conclusion KI1.1 CAPIF-8 reference point | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250924 | Conclusion KI1.2 Recource owner authorization management |
pCR revised to S3-250999 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250925 | Conclusion KI1.3 Finer granular authorization | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250926 | Conclusion KI2 CAPIF interconnect security | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250927 | Conclusion KI3 Authorizing API invoker on UE accessing other UE |
pCR revised to S3-251002 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250928 | Conclusion KI4 Nested API | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250929 | Conclusion KI5 multiple API invoker |
pCR revised to S3-251024 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250930 | Conclusion KI6 Onboarding | pCR | Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250931 | draftCR: security aspects on Full EPC in each satellite | other | THALES | Rel-19 |
S3-120 AI: 4.19 |
merged | [WTS] [JSN] | ||
| S3-250932 | DP on handling NAS counters in S&F Mode when the UE registration is valid in multiple satellites | discussion | Sateliot, Novamint |
S3-120 AI: 4.19 |
noted | [WTS] [JSN] | |||
| S3-250933 | Update test case on access token verification | CR | MITRE-FFRDC, US National Security Agency | 33.117 19.0.2 CR#202 catB | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-250934 | Resolution of ENs in solution #39 | pCR | THALES | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
not treated | [WTS] [JSN] |
| S3-250935 | Add a threat on access token subject verification | CR | MITRE-FFRDC, US National Security Agency | 33.926 19.3.0 CR#104 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-250936 | Discussion on protecting header information in UPU | discussion | Qualcomm Incorporated |
S3-120 AI: 4.1.15 |
noted | [WTS] [JSN] | |||
| S3-250937 | Protection of UPU header | CR | Qualcomm Incorporated | 33.501 19.1.0 CR#2115 catC | DUMMY | Rel-19 |
S3-120 AI: 4.1.15 |
merged | [WTS] [JSN] |
| S3-250938 | Discussion on update of SCAS access token verification | discussion | MITRE-FFRDC |
S3-120 AI: 4.1.1 |
noted | [WTS] [JSN] | |||
| S3-250939 | pCR to the living document on: secure message transport using ACME to ACME-SBA | other | Google Ireland Limited, AT&T, TELUS |
S3-120 AI: 4.18 |
withdrawn | [WTS] [JSN] | |||
| S3-250940 | pCR to ACME-SBA living document on: certificate enrollment and renewal in 5G SBA using ACME |
other revised to S3-251091 |
Google Ireland Limited, AT&T, TELUS |
S3-120 AI: 4.18 |
revised | [WTS] [JSN] | |||
| S3-250941 | Key Derivation for QUIC/TLS in ATSSS | draftCR | Lenovo | DUMMY | Rel-19 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | |
| S3-250942 | Protecting XRM Media related information in UDP Option | draftCR | Lenovo | DUMMY | Rel-19 |
S3-120 AI: 6 |
merged | [WTS] [JSN] | |
| S3-250943 | pCR to the living document on: secure message transport using ACME to ACME-SBA |
other revised to S3-251090 |
Google, Cisco Systems, AT&T, TELUS |
S3-120 AI: 4.18 |
revised | [WTS] [JSN] | |||
| S3-250944 | New WID on Security Monitoring |
WID new revision of S3-250832 revised to S3-251131 |
AT&T, Charter Communications, Deutsche Telekom, KDDI, NTT DOCOMO, Telecom Italia, Verizon, Vodafone | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-250945 | KI on attacking via external carrier wave |
pCR revision of S3-250145 revised to S3-250960 |
NTT DOCOMO INC. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250946 | SA3 Rel-20 Planning | discussion | WG Chair |
S3-120 AI: 6 |
noted | [WTS] [JSN] | |||
| S3-250947 | New WID on Protection of XRM Media related information |
WID new revised to S3-251128 |
Ericsson, Lenovo, Nokia, Nokia Shanghai Bell | Rel-19 |
S3-120 AI: 6 |
revised | [WTS] [JSN] | ||
| S3-250948 | Determining NRFs allowed to act as authorization servers | other | Nokia | TEI19 | Rel-19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | |
| S3-250949 | NRF Set issue | other | Nokia | TEI19 | Rel-19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | |
| S3-250950 | NRF Cert retrieval operation | other | Nokia | TEI19 | Rel-19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | |
| S3-250951 | NRF Cert update notification and logging | other | Nokia | TEI19 | Rel-19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | |
| S3-250952 | NRF error handling | other | Nokia | TEI19 | Rel-19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | |
| S3-250953 | NF producer behavior | other | Nokia | TEI19 | Rel-19 |
S3-120 AI: 4.11 |
merged | [WTS] [JSN] | |
| S3-250954 | O-RAN ALLIANCE ZTA Standardization Workshop |
LS in LS reply in S3-250957 |
O-RAN |
S3-120 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-250955 | Reply to: LS on ProSe Message Content Type extensions for Release 19 |
LS out LS is reply to S3-250314 LS To: CT1 |
Xiaomi |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] | |||
| S3-250956 | Reply to: LS informing about the latest PQTN TF publications |
LS out LS is reply to S3-250365 LS To: GSMA PQTN |
Huawei |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] | |||
| S3-250957 | Reply to: O-RAN ALLIANCE ZTA Standardization Workshop |
LS out LS is reply to S3-250954 LS To: O-RAN WG11 |
Ericsson |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] | |||
| S3-250958 | Draft TR 33.713 | draft TR | OPPO | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] | |
| S3-250959 | New Key Issue on Amplification of resource exhaustion by exploiting AIoT paging messages |
pCR revision of S3-250819 |
Ericsson | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250960 | KI on attacking via external carrier wave |
pCR revision of S3-250945 |
NTT DOCOMO INC. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250961 | New SID on use of AEAD |
SID new revision of S3-250368 |
KDDI Corporation | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-250962 | Updates on general conclusion for AIoT | pCR | Qualcomm Incorporated | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
withdrawn | [WTS] [JSN] |
| S3-250963 | Update to generic conclusion |
pCR revision of S3-250651 |
Huawei, HiSilicon | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250964 | Draft TR 33.790 | draft TR | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-250965 | Updating General Conclusion | pCR | Ericsson | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
withdrawn | [WTS] [JSN] |
| S3-250966 | LS on secure storage and processing of credentials for AIoT |
LS out LS To: ETSI TC SET |
ORANGE |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] | |||
| S3-250967 | KI#1 conclusion |
pCR revision of S3-250759 |
Philips International B.V. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250968 | Conclusion on AIOT KI#3 | pCR | OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
withdrawn | [WTS] [JSN] |
| S3-250969 | Draft TR 33.757 | draft TR | China Telecom | PLMNNPN_SEC | Rel-19 |
S3-120 AI: 5.3 |
approved | [WTS] [JSN] | |
| S3-250970 | Draft TR 33.700-29 | draft TR | CATT | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
approved | [WTS] [JSN] | |
| S3-250971 | Draft TR 33.743 | draft TR | Huawei | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-120 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-250972 | Draft TR 33.749 | draft TR | China Unicom | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 5.14 |
approved | [WTS] [JSN] | |
| S3-250973 | Draft TR 33.766 | draft TR | Ericsson | FS_Energy_Sec | Rel-19 |
S3-120 AI: 5.16 |
approved | [WTS] [JSN] | |
| S3-250974 | Draft TR 33.721 | draft TR | Samsung | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
approved | [WTS] [JSN] | |
| S3-250975 | Proposed baseline for conclusion on KI#4 |
pCR revision of S3-250649 |
Huawei, HiSilicon, OPPO, China Unicom, Lenovo, ZTE, CATT, Xiaomi, Philips International B.V. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250976 | Draft TR 33.700-22 | draft TR | Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-250977 | Draft TR 33.938 | draft TR | Huawei | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
approved | [WTS] [JSN] | |
| S3-250978 | Way forward discussion | discussion | Huawei |
S3-120 AI: 5.9 |
noted | [WTS] [JSN] | |||
| S3-250979 | Draft TS 33.545 | draft TS | ZTE | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] | |
| S3-250980 | Scope of TS 33.545 |
pCR revision of S3-250541 |
China Mobile | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250981 | Update clause 3.1 to add relevant terms and its definitions. |
pCR revision of S3-250637 |
China Mobile | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250982 | Pseudo-CR-System architecture and security assumption for Femto in TS 33.545 |
pCR revision of S3-250626 |
China Mobile | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250983 | Content to clause 5.1 Device Authentication |
pCR revision of S3-250702 |
Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250984 | Hosting Party Authentication clause 5.2 |
pCR revision of S3-250544 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250985 | Location Security clause 5.3 |
pCR revision of S3-250546 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250986 | Backhaul Link Protection clause 5.4 |
pCR revision of S3-250547 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250987 | Content to clause 5.5 Access Control Mechanisms For Femto |
pCR revision of S3-250709 |
Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250988 | Topology Hiding clause 5.6 |
pCR revision of S3-250550 |
ZTE Corporation | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-250989 | eNA related API Name correction |
CR revision of S3-250572 |
Nokia | 33.501 18.8.0 CR#21011 catF | TEI18 | Rel-18 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-250990 | eNA related API Name correction |
CR revision of S3-250573 |
Nokia | 33.501 19.1.0 CR#21021 catA | TEI18 | Rel-19 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-250991 | Proposal for changing the description of SN counter in SCPAC |
CR revision of S3-250500 |
Apple | 33.501 19.1.0 CR#20951 catF | TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-250992 | Resolve ENs on authorized NRF in draft CR on Public key distribution and Issuer claim verification of the Access Token |
other revision of S3-250800 |
Ericsson | TEI19 |
S3-120 AI: 4.11 |
approved | [WTS] [JSN] | ||
| S3-250993 | Token-based authorization for indirect communication scenarios when NF is selected at target PLMN |
draftCR revision of - |
Ericsson,Nokia | TEI19 | Rel-19 |
S3-120 AI: 4.1.2 |
approved | [WTS] [JSN] | |
| S3-250994 | pCR to TR33.700-29 Update conclusion#2 |
pCR revision of S3-250736 |
CATT | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-250995 | Updates to Overall Summary of solutions |
pCR revision of S3-250631 |
Nokia | 33.700-29 0.6.0 | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
approved | [WTS] [JSN] |
| S3-250996 | Cover sheet TR 33.700-29 | TS or TR cover | CATT | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.7 |
approved | [WTS] [JSN] | |
| S3-250997 | Skeleton for security aspects of 5G satellite access phase 3 |
draftCR revision of S3-250738 |
CATT | 5GSAT_Ph3_SEC | Rel-18 |
S3-120 AI: 4.19 |
noted | [WTS] [JSN] | |
| S3-250998 | TR 33.700-22 KI#1.1 conclusion update |
pCR revision of S3-250857 |
Xiaomi, Huawei, HiSilicon, China Telecom, Ericsson, Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250999 | Conclusion KI1.2 Recource owner authorization management |
pCR revision of S3-250924 |
Nokia, Huawei, HiSilicon, China Telecom, Ericsson, Xiaomi | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251000 | KI#1.3 conclusions on granularity of authorization and revocation |
pCR revision of S3-250408 |
Huawei, HiSilicon, Ericsson, Nokia, Xiaomi | 33.700-22 0.4.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251001 | Further conclusion for key issue #2 |
pCR revision of S3-250603 |
Ericsson, China Telecom, Samsung, Xiaomi, Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251002 | Conclusion KI3 Authorizing API invoker on UE accessing other UE |
pCR revision of S3-250927 |
Nokia, Ericsson, CATT, Xiaomi | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251003 | Updates to Solution #33 |
pCR revision of S3-250310 |
Lenovo | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251004 | Resolving ENs and evaluation of solution #26 |
pCR revision of S3-250598 |
Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251005 | Resolve ENs in TR 33.700-22 solution #19 |
pCR revision of S3-250863 |
Xiaomi, Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251006 | Resolve ENs in TR 33.700-22 solutions #8, #9, #20, and #31 |
pCR revision of S3-250864 |
Xiaomi, Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251007 | authorized USS list |
draftCR revision of S3-250416 |
Huawei, HiSilicon | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
noted | [WTS] [JSN] | |
| S3-251008 | Adding support for multiple USSs |
CR revision of S3-250466 |
Qualcomm Incorporated | 33.256 18.2.0 CR#502 catB | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
not pursued | [WTS] [JSN] |
| S3-251009 | UUAA in 5GS updates | CR | Ericsson | 33.256 18.2.0 CR#521 catB | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
withdrawn | [WTS] [JSN] |
| S3-251010 | Location tracking update for multi-USS support |
draftCR revision of S3-250444 |
InterDigital, Europe, Ltd. | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
noted | [WTS] [JSN] | |
| S3-251011 | Updates to Terms, Abbreviations and Overview |
CR revision of S3-250731 |
Ericsson | 33.256 18.2.0 CR#511 catF | UAS_Ph3_Sec | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-251012 | Resolution of EN in KI#1 conclusion |
pCR revision of S3-250822 |
Nokia | 33.766 0.6.0 | FS_Energy_Sec | Rel-19 |
S3-120 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-251013 | Resolve EN for KI2 Conclusion |
pCR revision of S3-250664 |
Huawei, HiSilicon | 33.766 0.6.0 | FS_Energy_Sec | Rel-19 |
S3-120 AI: 5.16 |
approved | [WTS] [JSN] |
| S3-251014 | Enabling mTLS between ROF and CCF by CAPIF-specific key derivation |
pCR revision of S3-250897 |
Nokia, Lenovo | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251015 | Solution 28 update and evaluation |
pCR revision of S3-250917 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251016 | Solution on ROF and CCF to enable mTLS using AKMA |
pCR revision of S3-250898 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251017 | Onboarding solution |
pCR revision of S3-250899 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251018 | Solution 32 evaluation |
pCR revision of S3-250920 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251019 | New solution for onboarding of UE hosted API invoker |
pCR revision of S3-250597 |
Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251020 | Solution 3 Security procedures for CAPIF-8 reference points - EN resolution |
pCR revision of S3-250902 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251021 | Solution 18 evaluation |
pCR revision of S3-250912 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251022 | TR 33.700-22 Reusing existing mechanism to enable cross-UE authorization |
pCR revision of S3-250865 |
Xiaomi Technology Netherlands | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251023 | Conclusion for key issue#4 (Nested API invocation) |
pCR revision of S3-250771 |
Samsung, Ericsson, Xiaomi, Nokia, Nokia Shanghai Bell | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251024 | Conclusion KI5 multiple API invoker |
pCR revision of S3-250929 |
Nokia, Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251025 | Conclusion for KI#6 of TR 33.700-22 |
pCR revision of S3-250856 |
Xiaomi, Nokia, Ericsson, Lenovo | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251026 | Moving CIBA discussion from KI#1.2 to KI#3 |
pCR revision of S3-250599 |
Ericsson | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251027 | Additional aspects for KI6 onboarding |
pCR revision of S3-250901 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251028 | Resolve ENs in TR 33.700-22 KI#6 |
pCR revision of S3-250862 |
Xiaomi, Lenovo | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251029 | Solution on ROF certificate |
pCR revision of S3-250900 |
Nokia | 33.700-22 0.5.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-251030 | Security requirements on CAPIF-6 and -6e reference points |
CR revision of S3-250474 |
Nokia, ZTE, Xiaomi | 33.122 18.4.0 CR#811 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
agreed | [WTS] [JSN] |
| S3-251031 | Rel-19 exception sheet for CAPIF_Ph3_sec |
WI exception request revision of S3-250854 |
Xiaomi Technology Netherlands | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
agreed | [WTS] [JSN] | |
| S3-251032 | Security requirements and procedures for CAPIF-8 reference point |
CR revision of S3-250411 |
Huawei, HiSilicon | 33.122 18.4.0 CR#781 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
agreed | [WTS] [JSN] |
| S3-251033 | Security procedures for CAPIF-8 reference points | CR | ZTE Corporation | 33.122 18.4.0 CR#96 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
withdrawn | [WTS] [JSN] |
| S3-251034 | Proposed text for full EPC clause of satellite store & forward |
other revision of S3-250429 |
Qualcomm Incorporated |
S3-120 AI: 4.19 |
noted | [WTS] [JSN] | |||
| S3-251035 | Addition of the new content specifying security aspects of Store and Forward Satellite operation in Split MME architecture |
draftCR revision of S3-250462 |
InterDigital, Inc. | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
noted | [WTS] [JSN] | |
| S3-251036 | Security for S&F satellite operation - Split MME architecture |
draftCR revision of S3-250762 |
Philips International B.V. | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
noted | [WTS] [JSN] | |
| S3-251037 | Clearn up TR 33.743 |
pCR revision of S3-250671 |
Huawei, HiSilicon | 33.743 1.0.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-120 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-251038 | Address the Note in U2N conclusion |
pCR revision of S3-250580 |
China Telecom Corporation Ltd. | 33.743 1.0.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-120 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-251039 | Living document for 5G_ProSe_Sec_Ph3 skeleton |
draftCR revision of S3-250687 |
Huawei, HiSilicon, China Telecom | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-251040 | Add scope and definition in TS 33.503 |
other revision of S3-250609 |
China Telecom Corporation Ltd. | Rel-19 |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | ||
| S3-251041 | Add multi-hop description in PKMF and AUSF |
other revision of S3-250610 |
China Telecom Corporation Ltd. |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |||
| S3-251042 | U2N relay discovery security |
other revision of S3-250435 |
Qualcomm Incorporated |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |||
| S3-251043 | Adding Security flow of Multi-hop UE-to-Network Relay security establishment procedure to ProSe draftCR |
other revision of S3-250680 |
Huawei, HiSilicon, Interdigital | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-251044 | Adding general introduction and security requirements of multi-hop UE-to-UE Relay to ProSe draftCR |
other revision of S3-250681 |
Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-251045 | U2U relay discovery security |
other revision of S3-250437 |
Qualcomm Incorporated |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |||
| S3-251046 | Adding Security flow of L3 Multi-hop UE-to-UE Relay security establishment procedure to ProSe draftCR |
other revision of S3-250683 |
Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-251047 | Protection mechanism for PC5 discovery messages with ProSe Message Content Type extensions |
other revision of S3-250840 |
Xiaomi Technology Spain S.L | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-251048 | Conclusion on KI#3 |
pCR revision of S3-250817 |
Ericsson | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251049 | update conclusion for KI3 Security aspects of digital asset container in 5G |
pCR revision of S3-250889 |
Nokia, Nokia Shanghai Bell | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-251050 | Pseudo-CR on 33.721: CAPIF-based Solution for Key Issue #4 |
pCR revision of S3-250849 |
Xiaomi Technology UK Limited | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-251051 | Presentation of Report to TSG SA: TR 33.721, Version 0.7.0 |
TS or TR cover revision of S3-250778 |
Samsung | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
approved | [WTS] [JSN] | |
| S3-251052 | Authentication and authorization for spatial localization services |
other revision of S3-250556 |
Nokia |
S3-120 AI: 4.21 |
approved | [WTS] [JSN] | |||
| S3-251053 | Authentication and authorization for spatial localization services when CAPIF is not used | other | ZTE Corporation |
S3-120 AI: 4.21 |
approved | [WTS] [JSN] | |||
| S3-251054 | Rel-19 Work item exception for Metaverse_Sec |
WI exception request revision of S3-250783 |
Samsung | Metaverse_Sec | Rel-19 |
S3-120 AI: 4.21 |
agreed | [WTS] [JSN] | |
| S3-251055 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-250340 LS To: SA2 revision of S3-250521 |
OPPO | Rel-19 |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-251056 | Draft skeleton for AIML_CN_SEC |
draftCR revision of S3-250617 |
China Mobile, Vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251057 | General description for security for UE positioning based on a ML model at the LMF |
other revision of S3-250390 |
vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251058 | Add user consent description of X.11 |
other revision of S3-250616 |
China Mobile | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251059 | General description for security for vertical federated Learning among NWDAFs and AFs |
other revision of S3-250392 |
vivo | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251060 | Authorization for selection of VFL participants in VFL Group NWDAF As VFL Server |
other revision of S3-250669 |
Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251061 | Authorization of VFL members (External AF as a Server) |
other revision of S3-250665 |
Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251062 | Add description for protection of communication data used in VFL process |
other revision of S3-250614 |
China Mobile | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251063 | Notification about AKMA service disabling via NEF |
CR revision of S3-250716 |
Huawei, HiSilicon | 33.535 18.6.0 CR#2261 catF | AKMA_Ph2 | Rel-18 |
S3-120 AI: 4.1.5 |
agreed | [WTS] [JSN] |
| S3-251064 | N32 consistency checks |
CR revision of S3-250366 |
BSI (DE), Nokia | 33.501 19.1.0 CR#20901 catF | Roaming5G, TEI19 | Rel-19 |
S3-120 AI: 4.1.14 |
agreed | [WTS] [JSN] |
| S3-251065 | update conclusion for KI2 Privacy of user sensitive information |
pCR revision of S3-250888 |
Nokia, Nokia Shanghai Bell | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-251066 | Updates to Solution#11 | pCR | Lenovo | 33.757 0.6.0 | PLMNNPN_SEC | Rel-19 |
S3-120 AI: 5.3 |
withdrawn | [WTS] [JSN] |
| S3-251067 | Clean Up for TR 33.757 |
pCR revision of S3-250487 |
China Telecommunications Corp.,ZTE | 33.757 0.6.0 | PLMNNPN_SEC | Rel-19 |
S3-120 AI: 5.3 |
approved | [WTS] [JSN] |
| S3-251068 | General |
other revision of S3-250490 |
China Telecommunications Corp.,ZTE | Rel-19 |
S3-120 AI: 4.25 |
approved | [WTS] [JSN] | ||
| S3-251069 | Architecture |
other revision of S3-250496 |
China Telecommunications Corp.,ZTE | Rel-19 |
S3-120 AI: 4.25 |
approved | [WTS] [JSN] | ||
| S3-251070 | SUPI privacy for PLMN hosted NPN |
other revision of S3-250776 |
Samsung | PLMNNPN | Rel-19 |
S3-120 AI: 4.25 |
approved | [WTS] [JSN] | |
| S3-251071 | Editorial Correction to TR 33.794 |
CR revision of S3-250821 |
Motorola Mobility | 33.794 19.0.0 CR#11 catF | FS_eZTS | Rel-19 |
S3-120 AI: 5.1 |
agreed | [WTS] [JSN] |
| S3-251072 | Pseudo-CR on 3GPP Cryptographic Inventory for DTLS and TLS |
pCR revision of S3-250441 |
Qualcomm Incorporated | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
approved | [WTS] [JSN] |
| S3-251073 | Framework |
pCR revision of S3-250399 |
Nokia, Nokia Shanghai Bell | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
approved | [WTS] [JSN] |
| S3-251074 | general clause |
pCR revision of S3-250403 |
Huawei, HiSilicon | 33.938 0.0.0 | FS_CryptoInv | Rel-19 |
S3-120 AI: 5. |
approved | [WTS] [JSN] |
| S3-251075 | Conclusion update for KI#3: Security and privacy aspects of IMS DC capability exposure |
pCR revision of S3-250747 |
Ericsson | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-251076 | TR 33.790 cleanup |
pCR revision of S3-250748 |
Ericsson | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-251077 | Rel-19 Work Item Exception for the Security support for the Next Generation Real Time Communication services Phase 2 (NG_RTC_SEC_Ph2) |
WI exception request revision of S3-250752 |
Ericsson | NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 4.23 |
agreed | [WTS] [JSN] | |
| S3-251078 | Security procedure for inter-CU LTM | other | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
withdrawn | [WTS] [JSN] | |
| S3-251079 | Living document on NR mobility enhancement | draftCR | Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
withdrawn | [WTS] [JSN] | |
| S3-251080 | Adding general introduction and security requirements of multi-hop UE-to-Network Relay to ProSe draftCR |
other revision of S3-250678 |
Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
approved | [WTS] [JSN] | |
| S3-251081 | Update Conclusion of KI#2.1 |
pCR revision of S3-250469 |
Nokia, Nokia Shanghai Bell | 33.749 0.5.0 | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-251082 | Clean Up for TR 33.749 |
pCR revision of S3-250633 |
China Unicom | 33.749 0.5.0 | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 5.14 |
approved | [WTS] [JSN] |
| S3-251083 | Solutions for secure retrieval of 5G system UE Ids and privacy related information |
draftCR revision of S3-250471 |
Nokia, Nokia Shanghai Bell | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
approved | [WTS] [JSN] | |
| S3-251084 | Adding priciple on ID verification to draftCR of MEC ph3 |
draftCR revision of S3-250881 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
approved | [WTS] [JSN] | |
| S3-251085 | Adding token based mechanism to draftCR of MEC ph3 |
draftCR revision of S3-250882 |
Huawei, HiSilicon,Ericsson | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
approved | [WTS] [JSN] | |
| S3-251086 | Adding hash based mechanism draftCR of MEC ph3 |
draftCR revision of S3-250883 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
approved | [WTS] [JSN] | |
| S3-251087 | Adding Temporeary ID based mechanism draftCR of MEC ph3 |
draftCR revision of S3-250884 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
approved | [WTS] [JSN] | |
| S3-251088 | Security of N6 delay measurements |
CR revision of S3-250470 |
Nokia, Nokia Shanghai Bell | 33.501 19.1.0 CR#20921 catB | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
agreed | [WTS] [JSN] |
| S3-251089 | Living document for Automatic Certificate Management Environment (ACME) for the Service Based Architecture (SBA) |
draftCR revision of S3-250449 |
Cisco Systems | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
approved | [WTS] [JSN] | |
| S3-251090 | pCR to the living document on: secure message transport using ACME to ACME-SBA |
other revision of S3-250943 |
Google, Cisco Systems, AT&T, TELUS |
S3-120 AI: 4.18 |
approved | [WTS] [JSN] | |||
| S3-251091 | pCR to ACME-SBA living document on: certificate enrollment and renewal in 5G SBA using ACME |
other revision of S3-250940 |
Google Ireland Limited, AT&T, TELUS |
S3-120 AI: 4.18 |
approved | [WTS] [JSN] | |||
| S3-251092 | certificate revocation |
other revision of S3-250468 |
Johns Hopkins University APL, Cisco Systems, U.S. National Security Agency | Rel-19 |
S3-120 AI: 4.18 |
approved | [WTS] [JSN] | ||
| S3-251093 | ACME as optional protocol for ACM for SBA |
other revision of S3-250451 |
Cisco Systems | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
approved | [WTS] [JSN] | |
| S3-251094 | Updates to Annex I.2 |
other revision of S3-250467 |
Johns Hopkins University APL, Cisco Systems | Rel-19 |
S3-120 AI: 4.18 |
approved | [WTS] [JSN] | ||
| S3-251095 | Reply LS on AIML positioning |
LS out LS is reply to S3-250336 LS To: SA2 revision of - |
Apple |
S3-120 AI: 3.1 |
withdrawn | [WTS] [JSN] | |||
| S3-251096 | IdMS - OIDC Client Registration |
CR revision of S3-250352 |
Leonardo SpA | 33.180 19.0.0 CR#2161 catF | MCXSec3 | Rel-19 |
S3-120 AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-251097 | IdMS - PKCE Downgrade Attack |
CR revision of S3-250353 |
Leonardo SpA | 33.180 19.0.0 CR#2171 catF | MCXSec3 | Rel-19 |
S3-120 AI: 4.6 |
agreed | [WTS] [JSN] |
| S3-251098 | Error correction and clarfication in clause 4.2.2.1.19 to TS 33.216 |
CR revision of S3-250688 |
Huawei, HiSilicon | 33.216 18.1.0 CR#281 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-251099 | Adding Note to TC_BVT_PORT_SCANNING on external interfaces |
CR revision of S3-250719 |
BSI | 33.117 19.0.2 CR#1991 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-251100 | Adding Note to TC_RESTRICTED_REACHABILITY_OF_SERVICES |
CR revision of S3-250720 |
BSI | 33.117 19.0.2 CR#2001 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-251101 | Clarification of gNB SCAS wording |
CR revision of S3-250723 |
BSI | 33.511 19.0.0 CR#771 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-251102 | LS on Device Subscription Data |
LS out source LS: S2-2501242 LS To: SA2 revision of S3-250653 |
Huawei, HiSilicon | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] | ||
| S3-251103 | Conclusion for KI#6 |
pCR revision of S3-250516 |
ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251104 | Pseudo-CR on Lightweight authentication and privacy protection for inventory and command procedure |
pCR revision of S3-250622 |
China Mobile | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251105 | Pseudo-CR-New solution on AIoT privacy for TR 33.713 |
pCR revision of S3-250623 |
China Mobile | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251106 | pCR to TR33.713 New solution AIoT command message security protection procedure |
pCR revision of S3-250757 |
CATT | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251107 | Solution#1 update - Addressing Ens |
pCR revision of S3-250758 |
Philips International B.V. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251108 | Evaluation for solution 6 |
pCR revision of S3-250555 |
ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251109 | resolving ENs in sol#6 in TR 33.713 |
pCR revision of S3-250553 |
ZTE Corporation | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251110 | Update AIOT sol#7 |
pCR revision of S3-250527 |
OPPO | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251111 | Remove EN for Sol#10 |
pCR revision of S3-250385 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251112 | RO authentication and authorization information for CAPIF-8 reference point | draftCR | Huawei, HiSilicon | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
approved | [WTS] [JSN] | |
| S3-251113 | draft CR of Resource owner authorization management |
draftCR revision of S3-250510 |
China Telecom | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
approved | [WTS] [JSN] | |
| S3-251114 | CAPIF-8 - Authorization for finer level service API access | draftCR | Huawei, Nokia | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
approved | [WTS] [JSN] | |
| S3-251115 | RNAA and Interconnect aspects in function security model |
CR revision of S3-250473 |
Samsung, Nokia | 33.122 18.4.0 CR#801 catB | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
agreed | [WTS] [JSN] |
| S3-251116 | Security procedures for CAPIF interconnection |
other revision of S3-250772 |
Samsung | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
approved | [WTS] [JSN] | |
| S3-251117 | RNAA authentication and authorization - mapping of API Invoker ID and GPSI |
CR revision of S3-250480 |
Nokia | 33.122 18.4.0 CR#871 catF | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 4.22 |
agreed | [WTS] [JSN] |
| S3-251118 | Correction of existing text in section 6.10 |
CR revision of S3-250484 |
Nokia | 33.122 18.4.0 CR#881 catF | TEI19 | Rel-19 |
S3-120 AI: 4.22 |
agreed | [WTS] [JSN] |
| S3-251119 | Living document on General description for security aspects of 5G satellite access phase 3 |
draftCR revision of S3-250740 |
CATT | 5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 4.19 |
approved | [WTS] [JSN] | |
| S3-251120 | UPU Header Security |
CR revision of S3-250306 |
Lenovo | 33.501 19.1.0 CR#21141 catF | TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-251121 | Reply LS on Clarifications related to the parameter to support 5G ProSe in SNPN |
LS out LS is reply to S3-250315 LS To: CT1 revision of S3-250576 revised to S3-251172 |
China Telecom Corporation Ltd. | Rel-19 |
S3-120 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-251122 | 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-250317 LS To: CT1 revision of S3-250439 |
Qualcomm Incorporated | 5G_ProSe_Ph2 |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-251123 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-250321 LS To: CT1,CT6 revision of S3-250422 |
Qualcomm Incorporated | 5GProtoc19 | Rel-19 |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] | |
| S3-251124 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-250325 LS To: RAN2,RAN3 revision of S3-250732 |
CATT | Rel-19 |
S3-120 AI: 4.12 |
approved | [WTS] [JSN] | ||
| S3-251125 | Reply LS on Issues related Analytics context transfer between AnLFs |
LS out LS is reply to S3-250330 source LS: S2-2409441 LS To: SA2 |
Huawei, HiSilicon | Rel-18 |
S3-120 AI: 3.1 |
withdrawn | [WTS] [JSN] | ||
| S3-251126 | DraftCR for TS 33.558 on ID verification |
draftCR revision of S3-250879 |
Huawei, HiSilicon | FS_EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
approved | [WTS] [JSN] | |
| S3-251127 | Protecting XRM Media related information in QUIC aware forwarding |
CR revision of S3-250737 |
Ericsson | 33.501 19.1.0 CR#21071 catB | XRM_Ph2-SEC | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] |
| S3-251128 | New WID on Protection of XRM Media related information |
WID new revision of S3-250947 |
Ericsson, Lenovo, Nokia, Nokia Shanghai Bell | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-251129 | Revise WID on security aspects of 5G Mobile Metaverse services |
WID revised revision of S3-250784 |
Samsung | Metaverse_Sec | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] | |
| S3-251130 | Revised WID on security aspects of CAPIF Phase3 |
WID revised revision of S3-250852 |
Xiaomi Technology Netherlands | CAPIF_Ph3_sec | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] | |
| S3-251131 | New WID on Security Monitoring |
WID new revision of S3-250944 |
AT&T, Charter Communications, Deutsche Telekom, KDDI, NTT DOCOMO, Telecom Italia, Verizon, Vodafone | Rel-19 |
S3-120 AI: 6 |
endorsed | [WTS] [JSN] | ||
| S3-251132 | Fixing API invoker onboarding – Rel18 |
CR revision of S3-250596 |
Ericsson | 33.122 18.4.0 CR#941 catF | CAPIF-Sec, TEI18 | Rel-18 |
S3-120 AI: 4.1.15 |
not pursued | [WTS] [JSN] |
| S3-251133 | Clarification of gNB SCAS test cases where an “or” could lead to missing test coverage. |
CR revision of S3-250722 |
BSI | 33.511 19.0.0 CR#761 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-251134 | DRAFT CR SBA Rel-19 public key or cert retrieval for access token verification |
draftCR revision of S3-250799 |
Ericsson | TEI19 | Rel-19 |
S3-120 AI: 4.11 |
approved | [WTS] [JSN] | |
| S3-251135 | Content to 4. Y.1.4 AAA Server/AUSF and UDM |
pCR revision of S3-250699 |
Huawei, HiSilicon | 33.545 0.0.0 | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] |
| S3-251136 | CR for TS 33.558 on ID verification | CR | Huawei, HiSilicon | 33.558 18.2.0 CR#21 catB | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
agreed | [WTS] [JSN] |
| S3-251137 | Requirements for secure retrieval of 5G system UE Ids and privacy related information |
CR revision of S3-250481 |
Nokia, Nokia Shanghai Bell | 33.501 19.1.0 CR#20931 catB | EDGE_Ph3 | Rel-19 |
S3-120 AI: 4.17 |
agreed | [WTS] [JSN] |
| S3-251138 | Correction of Expected Results in AS algorithm selection in Handover scenario |
CR revision of S3-250721 |
BSI | 33.511 19.0.0 CR#751 catF | SCAS_5G_Maint | Rel-19 |
S3-120 AI: 4. |
agreed | [WTS] [JSN] |
| S3-251139 | ACME challenge validation for 5G SBA NFs |
other revision of S3-250452 |
Cisco Systems, U.S. National Security Agency | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
approved | [WTS] [JSN] | |
| S3-251140 | Authorization of LMF retrieval of a trained AI/ML model for positioning |
other revision of S3-250656 |
Huawei, HiSilicon | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251141 | Living document for AIML_CN_SEC | draftCR | China Mobile | AIML_CN_SEC | Rel-19 |
S3-120 AI: 4.24 |
approved | [WTS] [JSN] | |
| S3-251142 | New solution for KI#2: Security of IMS based Avatar Communication |
pCR revision of S3-250745 |
Ericsson | 33.790 1.1.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 5.2 |
approved | [WTS] [JSN] |
| S3-251143 | Reply LS on security questions related to NAS layer overhead reduction for data transfer using control plane CIoT |
LS out LS is reply to S3-250316 LS To: CT1 revision of S3-250374 |
vivo | Rel-19 |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-251144 | LS on Privacy and security aspects regarding DC management by the network |
LS out LS To: SA2 revision of S3-250893 |
Nokia, Nokia Shanghai Bell | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] | |
| S3-251145 | Conclusion for New KI: Reader Authorization for 5G Ambient IoT Services |
pCR revision of S3-250464 |
InterDigital, Inc. | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251146 | Cover sheet TR 33.700-22 | TS or TR cover | Xiaomi | FS_5GSAT_Ph3_SEC | Rel-19 |
S3-120 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-251147 | Pseudo-CR on 33.721: Resolution of the Editor’s Notes in Solution #10 |
pCR revision of S3-250848 |
Xiaomi Technology UK Limited | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-251148 | Pseudo-CR on 33.721: Update to Conclusion on Key Issue #4 |
pCR revision of S3-250851 |
Xiaomi Technology UK Limited | 33.721 0.6.0 | FS_Metaverse_Sec | Rel-19 |
S3-120 AI: 5.18 |
approved | [WTS] [JSN] |
| S3-251149 | Exception sheet 5GSAT_Ph3_SEC | WI exception request | CATT | 5GSAT_Ph3_SEC |
S3-120 AI: 4.19 |
agreed | [WTS] [JSN] | ||
| S3-251150 | New WID on Ambient IoT security |
WID new revision of S3-250448 |
OPPO, Huawei, HiSilicon, Intel, Lenovo, Inter Digital, China Unicom, Sony, Vivo, Xiaomi, China Mobile, Philips, Cable Labs, CATT, ZTE | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-251151 | Revised WID on security support for the Next Generation Real Time Communication services Phase 2 |
WID revised revision of S3-250751 |
Ericsson | NG_RTC_SEC_Ph2 | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] | |
| S3-251152 | Living document for Automatic Certificate Management Environment (ACME) for the Service Based Architecture (SBA) | draftCR | Cisco | ACME_SBA | Rel-19 |
S3-120 AI: 4.18 |
approved | [WTS] [JSN] | |
| S3-251153 | New SID on security aspects for MPQUIC |
SID new revision of S3-250661 |
Huawei, HiSilicon | Rel-20 |
S3-120 AI: 6 |
noted | [WTS] [JSN] | ||
| S3-251154 | New WID on specification of examplea algorithm for alternative f5* (f5**) function |
WID new revision of S3-250584 |
Ericsson, Thales, Qualcomm Incorporated | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] | ||
| S3-251155 | Skeleton of specification of alternative example f5* (f5**) function |
other revision of S3-250585 |
Ericsson, Thales | DUMMY | Rel-19 |
S3-120 AI: 6 |
approved | [WTS] [JSN] | |
| S3-251156 | Presentation of specification of alternative example f5* (f5**) function |
other revision of S3-250587 |
Ericsson, Thales | DUMMY | Rel-19 |
S3-120 AI: 6 |
approved | [WTS] [JSN] | |
| S3-251157 | Clarifying the naming for the new alternative example f5* (f5**) function |
CR revision of S3-250588 |
Ericsson, Thales | 33.102 18.0.0 CR#2851 catF | Crypto_f5** | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] |
| S3-251158 | Adding a reference for the new alternative example f5* (f5**) function |
CR revision of S3-250589 |
Ericsson, Thales | 35.205 18.0.0 CR#11 catB | Crypto_f5** | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] |
| S3-251159 | Adding a reference for the new alternative example f5* function |
CR revision of S3-250590 |
Ericsson, Thales | 35.231 18.0.0 CR#81 catB | Crypto_f5** | Rel-19 |
S3-120 AI: 6 |
agreed | [WTS] [JSN] |
| S3-251160 | Draft TS 35.XXX | other | Ericsson |
S3-120 AI: 6 |
approved | [WTS] [JSN] | |||
| S3-251161 | Editorial change on Security handling in Control Plane CIoT 5GS Optimization |
CR revision of S3-250501 |
Apple, NTT DOCOMO | 33.501 19.1.0 CR#20961 catF | TEI19 | Rel-19 |
S3-120 AI: 4.1.15 |
agreed | [WTS] [JSN] |
| S3-251162 | Rel-19 Work item exception for NR_Mob_Ph4_Sec |
WI exception request revision of S3-250768 |
Samsung | NR_Mob_Ph4_Sec | Rel-19 |
S3-120 AI: 4.12 |
agreed | [WTS] [JSN] | |
| S3-251163 | Cover sheet TS 33.545 | TS or TR cover | ZTE | 5G_Femto_Sec | Rel-19 |
S3-120 AI: 4.16 |
approved | [WTS] [JSN] | |
| S3-251164 | WID exception ACME_SBA | WI exception request | Cisco | ACME_SBA |
S3-120 AI: 4.18 |
agreed | [WTS] [JSN] | ||
| S3-251165 | WI exception UAS_Ph3_Sec | WI exception request | Ericsson | UAS_Ph3_Sec |
S3-120 AI: 4. |
agreed | [WTS] [JSN] | ||
| S3-251166 | Living document on Metaverse_Sec | draftCR | Samsung | Metaverse_Sec | Rel-18 |
S3-120 AI: 4.21 |
approved | [WTS] [JSN] | |
| S3-251167 | WI exception sheet AIML_CN_SEC | WI exception request | China Mobile | AIML_CN_SEC |
S3-120 AI: 4.24 |
agreed | [WTS] [JSN] | ||
| S3-251168 | Living CR for security for PLMN hosting a NPN |
draftCR revision of S3-250489 |
China Telecommunications Corp.,ZTE | PLMNNPN | Rel-19 |
S3-120 AI: 4.25 |
approved | [WTS] [JSN] | |
| S3-251169 | Security for PLMN hosting a NPN | CR | China Telecom | 33.501 19.1.0 CR#2116 catB | PLMNNPN | Rel-19 |
S3-120 AI: 4.25 |
not pursued | [WTS] [JSN] |
| S3-251170 | Adding multi-hop security features of 5G_ProSe_Sec_Ph3 | CR | Huawei | 33.503 18.5.0 CR#211 catB | 5G_ProSe_Sec_Ph3 | Rel-19 |
S3-120 AI: 4.15 |
agreed | [WTS] [JSN] |
| S3-251171 | A new solution for network layer security based on the key provided by AF |
pCR revision of S3-250460 |
Qualcomm Incorporated | 33.713 0.6.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-120 AI: 5.9 |
approved | [WTS] [JSN] |
| S3-251172 | Reply LS on Clarifications related to the parameter to support 5G ProSe in SNPN |
LS out LS is reply to S3-250315 LS To: CT1 revision of S3-251121 |
China Telecom Corporation Ltd. | Rel-19 |
S3-120 AI: 3.1 |
approved | [WTS] [JSN] |
873 documents (1.2196929454803 seconds)