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-170831 | Miscellaneous corrections (editorials, drafting rules related, alignment, terminology…) |
pCR revised to S6-170983 |
LG Electronics, Samsung, NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170834 | Pseudo-CR on service API discovery requirement |
pCR revised to S6-170988 |
NEC Corporation | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170835 | Pseudo-CR on terminology alignment |
pCR revised to S6-170985 |
NEC Corporation | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170836 | Pseudo-CR on API terminology definition |
pCR revised to S6-170986 |
NEC Corporation | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170837 | Pseudo-CR on API invoker terminology definition | pCR | NEC Corporation | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
noted | [WTS] [JSN] |
| S6-170929 | Solution for API invoker onboarding | pCR | Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
merged | [WTS] [JSN] |
| S6-170930 | Update on solution for service API publish and discovery |
pCR revised to S6-170991 |
Huawei, Hisilicon | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170931 | Solution for API invoker authorization for service API access |
pCR revised to S6-170993 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170932 | Common requirements for CAPIF-2 |
pCR revised to S6-170989 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170933 | CAPIF architecture enhancement |
pCR revised to S6-170990 |
Huawei, Hisilicon | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170934 | Key issue on CAPIF support for service APIs from multiple providers |
pCR revised to S6-171001 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170937 | Pseudo-CR on Editorials to TR 23.722 |
pCR revised to S6-170984 |
Samsung, LG Electronics, NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170939 | Pseudo-CR on Onboarding API invoker |
pCR revised to S6-170992 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170940 | Pseudo-CR on Onboarding definition |
pCR revised to S6-170987 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170941 | Pseudo-CR on Publishing and Discovery of service APIs | pCR | Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
merged | [WTS] [JSN] |
| S6-170942 | Pseudo-CR on Authorization and secure communication |
pCR revised to S6-170994 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170944 | Pseudo-CR on Authentication between API invoker and CAPIF core functions |
pCR revised to S6-170995 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170945 | Pseudo-CR on Authentication between API invoker and AEF |
pCR revised to S6-170996 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170947 | Pseudo-CR on API management - Logging |
pCR revised to S6-170997 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170948 | Pseudo-CR on API management - Charging |
pCR revised to S6-170998 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170950 | Pseudo-CR on API management - Auditing |
pCR revised to S6-170999 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170951 | Pseudo-CR on API management - Monitoring |
pCR revised to S6-171000 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170952 | Pseudo-CR on Multiple API provider |
pCR revised to S6-171002 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170983 | Miscellaneous corrections (editorials, drafting rules related, alignment, terminology…) |
pCR revision of S6-170831 |
LG Electronics, Samsung, NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-170984 | Pseudo-CR on Editorials to TR 23.722 |
pCR revision of S6-170937 |
Samsung, LG Electronics, NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-170985 | Pseudo-CR on terminology alignment |
pCR revision of S6-170835 revised to S6-171079 |
NEC Corporation | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170986 | Pseudo-CR on API terminology definition |
pCR revision of S6-170836 |
NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-170987 | Pseudo-CR on Onboarding definition |
pCR revision of S6-170940 revised to S6-171096 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170988 | Pseudo-CR on service API discovery requirement |
pCR revision of S6-170834 revised to S6-171080 |
NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170989 | Common requirements for CAPIF-2 |
pCR revision of S6-170932 revised to S6-171097 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170990 | CAPIF architecture enhancement |
pCR revision of S6-170933 revised to S6-171098 |
Huawei, Hisilicon | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170991 | Update on solution for service API publish and discovery |
pCR revision of S6-170930 |
Huawei, Hisilicon, Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-170992 | Pseudo-CR on Onboarding API invoker |
pCR revision of S6-170939 revised to S6-171101 |
Samsung, Huawei, Hisilicon, CMCC, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170993 | Solution for API invoker authorization for service API access |
pCR revision of S6-170931 revised to S6-171109 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170994 | Pseudo-CR on Authorization and secure communication |
pCR revision of S6-170942 revised to S6-171102 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170995 | Pseudo-CR on Authentication between API invoker and CAPIF core functions |
pCR revision of S6-170944 revised to S6-171111 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170996 | Pseudo-CR on Authentication between API invoker and AEF |
pCR revision of S6-170945 revised to S6-171103 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170997 | Pseudo-CR on API management - Logging |
pCR revision of S6-170947 revised to S6-171104 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170998 | Pseudo-CR on API management - Charging |
pCR revision of S6-170948 revised to S6-171114 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-170999 | Pseudo-CR on API management - Auditing |
pCR revision of S6-170950 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171000 | Pseudo-CR on API management - Monitoring |
pCR revision of S6-170951 revised to S6-171115 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171001 | Key issue on CAPIF support for service APIs from multiple providers |
pCR revision of S6-170934 revised to S6-171116 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171002 | Pseudo-CR on Multiple API provider |
pCR revision of S6-170952 revised to S6-171117 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171003 | Pseudo-CR on onboarding logging requirement |
pCR revised to S6-171118 |
NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171004 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171005 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171006 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171007 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171008 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171009 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171010 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171011 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171012 | Reserved for FS CAPIF session | other | FS CAPIF session |
S6-18 AI: 9.3 |
withdrawn | [WTS] [JSN] | |||
| S6-171079 | Pseudo-CR on terminology alignment |
pCR revision of S6-170985 |
NEC Corporation | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171080 | Pseudo-CR on service API discovery requirement |
pCR revision of S6-170988 |
NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171096 | Pseudo-CR on Onboarding definition |
pCR revision of S6-170987 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171097 | Common requirements for CAPIF-2 |
pCR revision of S6-170989 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171098 | CAPIF architecture enhancement |
pCR revision of S6-170990 revised to S6-171108 |
Huawei, Hisilicon | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171101 | Pseudo-CR on Onboarding API invoker |
pCR revision of S6-170992 |
Samsung, Huawei, Hisilicon, CMCC, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171102 | Pseudo-CR on Authorization and secure communication |
pCR revision of S6-170994 revised to S6-171110 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171103 | Pseudo-CR on Authentication between API invoker and AEF |
pCR revision of S6-170996 revised to S6-171112 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171104 | Pseudo-CR on API management - Logging |
pCR revision of S6-170997 revised to S6-171113 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171108 | CAPIF architecture enhancement |
pCR revision of S6-171098 |
Huawei, Hisilicon | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171109 | Solution for API invoker authorization for service API access |
pCR revision of S6-170993 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171110 | Pseudo-CR on Authorization and secure communication |
pCR revision of S6-171102 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171111 | Pseudo-CR on Authentication between API invoker and CAPIF core functions |
pCR revision of S6-170995 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171112 | Pseudo-CR on Authentication between API invoker and AEF |
pCR revision of S6-171103 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171113 | Pseudo-CR on API management - Logging |
pCR revision of S6-171104 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171114 | Pseudo-CR on API management - Charging |
pCR revision of S6-170998 revised to S6-171130 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171115 | Pseudo-CR on API management - Monitoring |
pCR revision of S6-171000 revised to S6-171131 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
revised | [WTS] [JSN] |
| S6-171116 | Key issue on CAPIF support for service APIs from multiple providers |
pCR revision of S6-171001 |
Huawei, Hisilicon, CMCC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171117 | Pseudo-CR on Multiple API provider |
pCR revision of S6-171002 |
Samsung | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171118 | Pseudo-CR on onboarding logging requirement |
pCR revision of S6-171003 |
NEC | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171130 | Pseudo-CR on API management - Charging |
pCR revision of S6-171114 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
| S6-171131 | Pseudo-CR on API management - Monitoring |
pCR revision of S6-171115 |
Samsung, SyncTechno Inc. | 23.722 0.2.0 | FS_CAPIF | Rel-15 |
S6-18 AI: 9.3 |
approved | [WTS] [JSN] |
75 documents (0.31960797309875 seconds)