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-243834 | LS on CAPIF phase 3 security considerations |
LS in LS reply in S3-244340, S3-243866, S3-244037, S3-244182, S3-244340 |
S6-243764 |
S3-118 AI: 5.19 |
replied to | [WTS] [JSN] | |||
| S3-243849 | Solution to KI#1 |
pCR revised to S3-244344 |
Lenovo | 33.700-22 0.1.0 | FS_eZTS, FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243863 | new solution for KI1.1 - CAPIF-8 security |
pCR revised to S3-244341 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243864 | new solution for KI1.2 - resource owner authorized revocation |
pCR revised to S3-244343 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243865 | new solution for KI1.3 - resource-level and api-level authorization and revocation |
pCR revised to S3-244349 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-243866 | draft reply LS to SA6 on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 LS To: SA6 |
Huawei, HiSilicon | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] | |
| S3-244021 | LS-out Reply to LS on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 source LS: S6-243764 LS To: SA6 |
Nokia |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] | |||
| S3-244022 | KI2 Solution on security method retrieval in CAPIF interconnect |
pCR revised to S3-244353 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244023 | KI2 Solution on authentication aspect in CAPIF interconnect requesting security information from another CCF |
pCR revised to S3-244354 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244024 | KI2 Solution on authentication aspect in CAPIF interconnect when API invoker has not included CCF information |
pCR revised to S3-244355 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244025 | KI2 Solution on authorization token request handling in CAPIF interconnect |
pCR revised to S3-244356 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244026 | KI2 Solution on mapping an API invoker authorization request to the correct CCF in CAPIF interconnect |
pCR revised to S3-244357 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244027 | KI1.3 Solution on scope enhancing |
pCR revised to S3-244350 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244028 | RO consent management |
pCR revised to S3-244346 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244029 | KI5 Solution on authenticating multiple API invokers of the same RO |
pCR revised to S3-244463 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244030 | KI on Onboarding security issue |
pCR revised to S3-244464 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244031 | Solution on validation of correct GPSI in API invoker information |
pCR revised to S3-244465 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244032 | Editorial - Streamlining interconnect KI details |
pCR revised to S3-244466 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244037 | reply LS on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 LS To: SA6 |
ZTE Corporation | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] | |
| S3-244068 | Solution for key issue 1.1 | pCR | ZTE Corporation | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244069 | Clean up for TR 33.700-22 | pCR | ZTE Corporation | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244070 | Solution for key issue 2 | pCR | ZTE Corporation | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244076 | New solution for KI#1.1 CAPIF-8 reference point |
pCR revised to S3-244342 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244077 | New solution for KI#2 CAPIF interconnection |
pCR revised to S3-244358 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244078 | New solution for KI#1.2 resource owner authorization management |
pCR revised to S3-244345 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244158 | New solution for CAPIF interconnection |
pCR revised to S3-244359 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244159 | Solution for accessing UE resources by an application on another UE | pCR | Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244160 | Solution for nested API invocation |
pCR revised to S3-244461 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244166 | Solution for key issue #1.2 |
pCR revised to S3-244352 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244167 | Update to KI#1.2 |
pCR revised to S3-244351 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244168 | Update to KI#1 for fixing the terminology |
pCR revised to S3-244515 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244169 | LS on terminology alignment between SA6 and SA3 |
LS out LS To: SA6 revised to S3-244516 |
Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] | |
| S3-244182 | Reply LS to SA6 on CAPIF security consideration |
LS out LS is reply to S3-243834 LS To: SA6 |
Apple |
S3-118 AI: 5.19 |
merged | [WTS] [JSN] | |||
| S3-244264 | Solution for security aspects of CAPIF interconnection |
pCR revised to S3-244360 |
Samsung, Nokia, Nokia Shanghai Bell | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244265 | Authorization for Nested API invocation |
pCR revised to S3-244462 |
Samsung | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244291 | Resource owner triggered revocation procedure |
pCR revised to S3-244347 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244292 | Resource owner authentication and authorization mechanism |
pCR revised to S3-244348 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244293 | API invoker authentication mechanism in CAPIF interconnection scenarios |
pCR revised to S3-244361 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244294 | API invoker authorization mechanism in CAPIF interconnection scenarios |
pCR revised to S3-244362 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244295 | Security method negotiation mechanism in CAPIF interconnection scenarios |
pCR revised to S3-244363 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244296 | Reply LS on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 source LS: S6-243764 LS To: SA6 revised to S3-244340 |
Xiaomi communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] | |
| S3-244297 | Shared information based authentication and authorization mechanism for multiple API invokers | pCR | Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244298 | Add scope for the TR 33.700-22 | pCR | Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244300 | Solution to KI#2 |
pCR revised to S3-244364 |
Lenovo | 33.700-22 0.1.0 | FS_eZTS, FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244305 | Draft TR 33.700-22 | draft TR | Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-244340 | Reply LS on CAPIF phase 3 security considerations |
LS out LS is reply to S3-243834 source LS: S6-243764 LS To: SA6 revision of S3-244296 |
Xiaomi communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-244341 | new solution for KI1.1 - CAPIF-8 security |
pCR revision of S3-243863 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244342 | New solution for KI#1.1 CAPIF-8 reference point |
pCR revision of S3-244076 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244343 | new solution for KI1.2 - resource owner authorized revocation |
pCR revision of S3-243864 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244344 | Solution to KI#1 |
pCR revision of S3-243849 |
Lenovo | 33.700-22 0.1.0 | FS_eZTS, FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244345 | New solution for KI#1.2 resource owner authorization management |
pCR revision of S3-244078 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244346 | RO consent management |
pCR revision of S3-244028 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244347 | Resource owner triggered revocation procedure |
pCR revision of S3-244291 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244348 | Resource owner authentication and authorization mechanism |
pCR revision of S3-244292 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244349 | new solution for KI1.3 - resource-level and api-level authorization and revocation |
pCR revision of S3-243865 |
Huawei, HiSilicon | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244350 | KI1.3 Solution on scope enhancing |
pCR revision of S3-244027 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244351 | Update to KI#1.2 |
pCR revision of S3-244167 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244352 | Solution for key issue #1.2 |
pCR revision of S3-244166 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244353 | KI2 Solution on security method retrieval in CAPIF interconnect |
pCR revision of S3-244022 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244354 | KI2 Solution on authentication aspect in CAPIF interconnect requesting security information from another CCF |
pCR revision of S3-244023 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244355 | KI2 Solution on authentication aspect in CAPIF interconnect when API invoker has not included CCF information |
pCR revision of S3-244024 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244356 | KI2 Solution on authorization token request handling in CAPIF interconnect |
pCR revision of S3-244025 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244357 | KI2 Solution on mapping an API invoker authorization request to the correct CCF in CAPIF interconnect |
pCR revision of S3-244026 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244358 | New solution for KI#2 CAPIF interconnection |
pCR revision of S3-244077 |
China Telecom | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244359 | New solution for CAPIF interconnection |
pCR revision of S3-244158 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244360 | Solution for security aspects of CAPIF interconnection |
pCR revision of S3-244264 |
Samsung, Nokia, Nokia Shanghai Bell | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244361 | API invoker authentication mechanism in CAPIF interconnection scenarios |
pCR revision of S3-244293 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244362 | API invoker authorization mechanism in CAPIF interconnection scenarios |
pCR revision of S3-244294 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244363 | Security method negotiation mechanism in CAPIF interconnection scenarios |
pCR revision of S3-244295 |
Xiaomi communications | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244364 | Solution to KI#2 |
pCR revision of S3-244300 |
Lenovo | 33.700-22 0.1.0 | FS_eZTS, FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244461 | Solution for nested API invocation |
pCR revision of S3-244160 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244462 | Authorization for Nested API invocation |
pCR revision of S3-244265 |
Samsung | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244463 | KI5 Solution on authenticating multiple API invokers of the same RO |
pCR revision of S3-244029 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244464 | KI on Onboarding security issue |
pCR revision of S3-244030 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244465 | Solution on validation of correct GPSI in API invoker information |
pCR revision of S3-244031 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244466 | Editorial - Streamlining interconnect KI details |
pCR revision of S3-244032 |
Nokia | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244515 | Update to KI#1 for fixing the terminology |
pCR revision of S3-244168 |
Ericsson | 33.700-22 0.1.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244516 | LS on terminology alignment between SA6 and SA3 |
LS out LS To: SA6 revision of S3-244169 |
Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-118 AI: 5.19 |
approved | [WTS] [JSN] |
78 documents (0.39728593826294 seconds)