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 |
|---|---|---|---|---|---|---|---|---|---|
| S6-170267 | Revised SID on Common API Framework | other | Samsung Electronics Co., Ltd | Rel-15 |
S6-16 AI: 9.4 |
withdrawn | [WTS] [JSN] | ||
| S6-170281 | Revised SID on Common API Framework |
SID revised revised to S6-170397 |
Samsung Electronics Co., Ltd | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] | |
| S6-170287 | Analysis of API framework of ETSI MEC | discussion | Huawei, Hisilicon | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
noted | [WTS] [JSN] | |
| S6-170288 | Key Issue on obtaining service API information |
pCR revised to S6-170402 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170290 | Key Issue on hiding the real location of the service |
pCR revised to S6-170403 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170291 | Key Issue on secure access to service APIs |
pCR revised to S6-170404 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170292 | General concept of northbound API framework |
pCR revised to S6-170409 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170293 | Architecture consideration for north bound API framework |
pCR revised to S6-170410 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170302 | 23.722-CAPIF-skeleton |
other revised to S6-170398 |
Samsung | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] | |
| S6-170303 | 23.722-CAPIF-introduction |
pCR revised to S6-170400 |
Samsung | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170311 | 23.722-CAPIF-scope |
pCR revised to S6-170399 |
Samsung | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170312 | OMA API framework analysis | discussion | Samsung | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
noted | [WTS] [JSN] | |
| S6-170313 | OMA API analysis for CAPIF study |
pCR revised to S6-170401 |
Samsung | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170331 | Key Issue on charging on invocation of service APIs |
pCR revised to S6-170405 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170332 | Key Issue on lifecycle management of service APIs |
pCR revised to S6-170406 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170333 | Key issue on logging and auditing service API invocations |
pCR revised to S6-170407 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170334 | Key issue on monitoring service API invocations |
pCR revised to S6-170408 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170397 | Revised SID on Common API Framework |
SID revised revision of S6-170281 revised to S6-170452 |
Samsung Electronics Co., Ltd | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] | |
| S6-170398 | 23.722-CAPIF-skeleton |
other revision of S6-170302 |
Samsung | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] | |
| S6-170399 | 23.722-CAPIF-scope |
pCR revision of S6-170311 revised to S6-170439 |
Samsung | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170400 | 23.722-CAPIF-introduction |
pCR revision of S6-170303 |
Samsung | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170401 | OMA API analysis for CAPIF study |
pCR revision of S6-170313 revised to S6-170440 |
Samsung | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170402 | Key Issue on obtaining service API information |
pCR revision of S6-170288 revised to S6-170453 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170403 | Key Issue on hiding the real location of the service |
pCR revision of S6-170290 revised to S6-170454 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170404 | Key Issue on secure access to service APIs |
pCR revision of S6-170291 revised to S6-170455 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170405 | Key Issue on charging on invocation of service APIs |
pCR revision of S6-170331 revised to S6-170458 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170406 | Key Issue on lifecycle management of service APIs |
pCR revision of S6-170332 revised to S6-170460 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170407 | Key issue on logging and auditing service API invocations |
pCR revision of S6-170333 revised to S6-170461 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170408 | Key issues and architectural requirements on monitoring API invocations |
pCR revision of S6-170334 revised to S6-170462 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170409 | General concept of northbound API framework |
pCR revision of S6-170292 revised to S6-170457 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170410 | Architecture consideration for north bound API framework |
pCR revision of S6-170293 revised to S6-170456 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170439 | 23.722-CAPIF-scope |
pCR revision of S6-170399 |
Samsung | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170440 | OMA API analysis for CAPIF study |
pCR revision of S6-170401 |
Samsung | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170452 | Revised SID on Common API Framework |
SID revised revision of S6-170397 |
Samsung Electronics Co., Ltd | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
agreed | [WTS] [JSN] | |
| S6-170453 | Key Issue on obtaining service API information |
pCR revision of S6-170402 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170454 | Key Issue on hiding the real location of the service |
pCR revision of S6-170403 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170455 | Key Issue on secure access to service APIs |
pCR revision of S6-170404 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170456 | Architecture consideration for north bound API framework |
pCR revision of S6-170410 revised to S6-170481 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170457 | General concept of northbound API framework |
pCR revision of S6-170409 revised to S6-170482 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170458 | Key Issue on charging on invocation of service APIs |
pCR revision of S6-170405 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170460 | Key Issue on lifecycle management of service APIs |
pCR revision of S6-170406 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170461 | Key issue on logging and auditing service API invocations |
pCR revision of S6-170407 revised to S6-170483 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
revised | [WTS] [JSN] |
| S6-170462 | Key issues and architectural requirements on monitoring API invocations |
pCR revision of S6-170408 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170481 | Architecture consideration for north bound API framework |
pCR revision of S6-170456 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170482 | General concept of northbound API framework |
pCR revision of S6-170457 |
Huawei, Hisilicon | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
| S6-170483 | Key issue on logging and auditing service API invocations |
pCR revision of S6-170461 |
China Mobile | 23.722 0.0.0 | FS_CAPIF | Rel-15 |
S6-16 AI: 9.4 |
approved | [WTS] [JSN] |
46 documents (0.31784200668335 seconds)