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-250017 | KI#1.1-Further conclusions on ROF authentication |
pCR revised to S3-250182 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250018 | KI#1.2-Further conclusions on authorization information | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250019 | KI#1.3-Further conclusions on granularity | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250020 | remove EN for KI#1.1 | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250021 | remove EN for KI#1.2 | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250022 | remove EN in clause 6.4 |
pCR revised to S3-250212 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250023 | editorial corrections in clauses 6.2 and 6.10 |
pCR revised to S3-250216 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250035 | Update to the conclusion for KI#1.2 | pCR | ZTE Corporation | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250036 | Update to the conclusion for KI#2 | pCR | ZTE Corporation | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250037 | Updates to Solution#21 |
pCR revised to S3-250187 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250038 | Solution to address KI#6 |
pCR revised to S3-250191 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250039 | Conclusion for KI#2 | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250040 | Update sol#17 to resolve EN | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250053 | Conclusion on key issue #1.2 in TR 33.700-22 | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250086 | Update to solution#27 |
pCR revised to S3-250188 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250087 | Updates to conclusion for key issue#2 |
pCR revised to S3-250189 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250096 | New solution for Authorization of API invoker on one UE accessing resources related to another UE |
pCR revised to S3-250198 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250097 | Resolving EN in key issue #1.2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250098 | Resolving ENs and evaluation of solution #11 |
pCR revised to S3-250199 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250099 | Resolving ENs and evaluation of solution #22 |
pCR revised to S3-250200 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250100 | Resolving ENs and evaluation of solution #26 |
pCR revised to S3-250201 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250101 | Conclusion reformulation for key issue #1.2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250102 | Further conclusion for key issue #1.1 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250103 | Further conclusion for key issue #1.2 |
pCR revised to S3-250196 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250104 | Further conclusion for key issue #1.3 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-250105 | Further conclusion for key issue #2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250106 | Conclusion for key issue #3 |
pCR revised to S3-250197 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250107 | Conclusion for key issue #4 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250108 | Conclusion for key issue #5 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250109 | Conclusion for key issue #6 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250115 | Draft CR on TS 33.122 | draftCR | Xiaomi communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] | |
| S3-250116 | TR 33.700-22KI#1.1 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250117 | TR 33.700-22KI#1.2 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250118 | TR 33.700-22KI#1.3 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250119 | TR 33.700-22KI#2 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250160 | KI1.1 ROF authentication conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250161 | KI1.1 ROF authentication | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250162 | KI1.1 Solution 3 update | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250163 | KI1.2 EN resolution in solution 7 | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250164 | KI1.3 conclusion |
pCR revised to S3-250222 |
Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250165 | KI2 interconnect conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250166 | KI3 conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250167 | KI4 Nested API invocation conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250168 | KI5 muliple API infovoker same RO conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250169 | TR correction | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250182 | KI#1.1-Further conclusions on ROF authentication |
pCR revision of S3-250017 |
Huawei, HiSilicon, Ericsson, Xiaomi, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250187 | Updates to Solution#21 |
pCR revision of S3-250037 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250188 | Update to solution#27 |
pCR revision of S3-250086 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250189 | Updates to conclusion for key issue#2 |
pCR revision of S3-250087 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250191 | Solution to address KI#6 |
pCR revision of S3-250038 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250196 | Further conclusion for key issue #1.2 |
pCR revision of S3-250103 |
Ericsson, Huawei, HiSilicon, ZTE Corporation, China Telecom, Xiaomi communications, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250197 | Conclusion for key issue #3 |
pCR revision of S3-250106 |
Ericsson, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250198 | New solution for Authorization of API invoker on one UE accessing resources related to another UE |
pCR revision of S3-250096 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250199 | Resolving ENs and evaluation of solution #11 |
pCR revision of S3-250098 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250200 | Resolving ENs and evaluation of solution #22 |
pCR revision of S3-250099 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250201 | Resolving ENs and evaluation of solution #26 |
pCR revision of S3-250100 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250212 | remove EN in clause 6.4 |
pCR revision of S3-250022 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250216 | editorial corrections in clauses 6.2 and 6.10 |
pCR revision of S3-250023 |
Huawei, HiSilicon, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250222 | KI1.3 conclusion |
pCR revision of S3-250164 |
Nokia, Huawei, HiSilicon, Xiaomi | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250235 | Study on security aspects of CAPIF Phase3 |
draft TR revised to S3-250236 |
Ericsson LM | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] | |
| S3-250236 | Study on security aspects of CAPIF Phase3 |
draft TR revision of S3-250235 |
Ericsson LM | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
61 documents (0.38637685775757 seconds)