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-241833 | Solution for authentication, confidentiality, and integrity protection of UE in ATSSS while selecting MPQUIC |
pCR revised to S3-242572 |
Nokia | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-241871 | Reply LS on the use of TLS with QUIC in ATSSS context |
LS out LS is reply to SA2 source LS: S3-241746 LS To: SA2 |
CableLabs | Rel-18 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] | ||
S3-241872 | Revised SID on security aspects for Multi-Access (DualSteer + ATSSS Ph-4) | SID revised | CableLabs | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] | |
S3-241982 | IPsec solution between UE and UPF |
pCR revised to S3-242575 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-241983 | Using 3GPP security context to derive authentication pre-shared key for NIN3A |
pCR revised to S3-242570 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-241984 | New key issue about UPF exposing new IP communication endpoint |
pCR revised to S3-242622 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-241987 | New solution about doing access control for UPF | pCR | Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] |
S3-242013 | update key issue #1 on privacy aspect |
pCR revised to S3-242568 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242014 | Address EN of key issue #2 |
pCR revised to S3-242569 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242050 | Add Abbreviations | pCR | Intel | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242058 | Secure Authentication and Connectivity for UE in ATSSS over NIN3A |
pCR revised to S3-242573 |
Intel | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242092 | Solution for KI#1 & #2 |
pCR revised to S3-242574 |
Ericsson | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242252 | Update to new SID on security aspects for Multi-Access (DualSteer + ATSSS Ph-4) | pCR | Philips International B.V. | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] |
S3-242301 | Solution on omitting IPsec for QUIC traffic over non-3GPP access |
pCR revised to S3-242654 |
Lenovo | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242317 | New sol for KI#1_AUSF based authenticatation mechanism for UE and UPF |
pCR revised to S3-242571 |
Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242318 | New sol for KI#1_A random number based authenticatation mechanism for UE and UPF | pCR | Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] |
S3-242319 | New sol for KI#2_User plane data protection mechanism between UE and UPF |
pCR revised to S3-242655 |
Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
revised | [WTS] [JSN] |
S3-242568 | update key issue #1 on privacy aspect |
pCR revision of S3-242013 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242569 | Address EN of key issue #2 |
pCR revision of S3-242014 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242570 | Using 3GPP security context to derive authentication pre-shared key for NIN3A |
pCR revision of S3-241983 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242571 | New sol for KI#1_AUSF based authenticatation mechanism for UE and UPF |
pCR revision of S3-242317 |
Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242572 | Solution for authentication, confidentiality, and integrity protection of UE in ATSSS while selecting MPQUIC |
pCR revision of S3-241833 |
Nokia | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242573 | Secure Authentication and Connectivity for UE in ATSSS over NIN3A |
pCR revision of S3-242058 |
Intel | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242574 | Solution for KI#1 & #2 |
pCR revision of S3-242092 |
Ericsson | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242575 | IPsec solution between UE and UPF |
pCR revision of S3-241982 |
Huawei, HiSilicon | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242605 | Draft TR 33.754 | draft TR | Intel | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] | |
S3-242622 | New key issue about UPF exposing new IP communication endpoint |
pCR revision of S3-241984 |
Huawei, HiSilicon,Deutsche Telekom | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
noted | [WTS] [JSN] |
S3-242654 | Solution on omitting IPsec for QUIC traffic over non-3GPP access |
pCR revision of S3-242301 |
Lenovo | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
S3-242655 | New sol for KI#2_User plane data protection mechanism between UE and UPF |
pCR revision of S3-242319 |
Xiaomi Communications | 33.754 0.1.0 | FS_MASSS_Sec | Rel-19 |
S3-116 AI: 5.15 |
approved | [WTS] [JSN] |
29 documents (0.34889483451843 seconds)