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-223290 | Sol#3 Resolution of EN on CAPIF support | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-223291 | Sol#3 Resolution of EN on visibility of application |
pCR revised to S3-224038 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223292 | Sol#3 Resolution of EN on prearranged policies |
pCR revised to S3-224039 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223293 | Sol#3 Resolution of EN on authorization of third party |
pCR revised to S3-224040 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223294 | Sol#3 Resolution of EN on AKMA Usage |
pCR revised to S3-224041 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223295 | Sol#3 Resolution of EN on Mutual Authentication | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223296 | Sol#3 Resolution of EN on Client Credential Grant | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223297 | Sol#3 Adding Evaluation |
pCR revised to S3-224042 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223488 | Address EN for solution 1 |
pCR revised to S3-224101 |
Huawei, HiSilicon | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
revised | [WTS] [JSN] |
S3-223489 | Conclusion for key issue #2 | pCR | Huawei, HiSilicon | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
noted | [WTS] [JSN] |
S3-223658 | A solution for authorization before allowing access to resources | pCR | Ericsson | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223738 | New Solution on User Authorization in API Invocation | pCR | Samsung | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223739 | New Solution on Resource owner Authorization in API Invocation using AKMA | pCR | Samsung | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223790 | KI#2, New Sol OAuth 2.0 based API invocation procedure | pCR | Xiaomi Communication | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223791 | KI#2, New Sol on User authorization revocation for API invocation procedure | pCR | Xiaomi Communication | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223792 | KI#2, New Sol UE credential based API invocation procedure | pCR | Xiaomi Communication | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223867 | New solution: PKCE flow based authorization | pCR | DOCOMO Communications Lab. | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223871 | new solution: Subscriber vs. user authorization | pCR | DOCOMO Communications Lab. | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223873 | Conclusion to use oAuth based authorization | pCR | DOCOMO Communications Lab. | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
noted | [WTS] [JSN] |
S3-223876 | Update to Solution #4 in SNAAPPY | pCR | Lenovo | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-223877 | Solution to address KI#2 in SNAAPPY | pCR | Lenovo | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
not treated | [WTS] [JSN] |
S3-224038 | Sol#3 Resolution of EN on visibility of application |
pCR revision of S3-223291 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224039 | Sol#3 Resolution of EN on prearranged policies |
pCR revision of S3-223292 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224040 | Sol#3 Resolution of EN on authorization of third party |
pCR revision of S3-223293 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224041 | Sol#3 Resolution of EN on AKMA Usage |
pCR revision of S3-223294 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224042 | Sol#3 Adding Evaluation |
pCR revision of S3-223297 |
Nokia, Nokia Shanghai Bell | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224101 | Address EN for solution 1 |
pCR revision of S3-223488 |
Huawei, HiSilicon | 33.884 0.2.0 | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] |
S3-224106 | Draft TR 33.884 | draft TR | NTT-Docomo | FS_SNAAPPY | Rel-18 |
S3-109 AI: 5.11 |
approved | [WTS] [JSN] | |
S3-224167 | LS reply on CAPIF authorization roles related to FS_SNAAPP | LS in | S6-223489 |
S3-109 AI: 5.11 |
postponed | [WTS] [JSN] | |||
S3-224168 | LS reply on SNAAPP requirements clarifications | LS in | S6-223488 |
S3-109 AI: 5.11 |
postponed | [WTS] [JSN] | |||
S3-230069 | Update to Solution #4 in SNAAPPY |
pCR revised to S3-230451 |
Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230070 | Solution to address KI#2 |
pCR revised to S3-230452 |
Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230071 | Conclusion to KI#1 in SNAAPPY | pCR | Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230072 | Conclusion to KI#2 in SNAAPPY | pCR | Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230074 | Sol#3 Resolution of EN on root certificate provisioning | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230075 | Sol#3 Resolution of EN on cross UE API access | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230076 | Sol#3 Resolution of EN on Uastar protocol | pCR | Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230077 | Sol#3 Resolution of EN on Mutual Authentication |
pCR revised to S3-230520 |
Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230078 | Sol#3 Resolution of EN on Client Credential Grant |
pCR revised to S3-230522 |
Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230172 | Address EN for solution 1: onboarding |
pCR revised to S3-230475 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230173 | Address EN for solution 1: detail for token | pCR | Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230174 | Address EN for solution 1: authorization decision |
pCR revised to S3-230476 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230175 | Evaluation Update on Solution 1 |
pCR revised to S3-230477 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230176 | New Solution on OAuth2.0 Token Revocation | pCR | Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230177 | Role mapping from TR 23.700-95 | pCR | Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230178 | Conclusion for key issue #2 | pCR | Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230230 | A solution for authorization before allowing access to resources |
pCR revised to S3-230486 |
Ericsson | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230337 | Update of Key Issue #2 |
pCR revised to S3-230543 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230338 | New Solution on Resource owner Authorization in API Invocation using OAuth 2.0 Authorization Code Grant |
pCR revised to S3-230544 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230339 | New Solution on Resource owner Authorization in API Invocation |
pCR revised to S3-230545 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230389 | KI#2, New Sol OAuth 2.0 based API invocation procedure |
pCR revised to S3-230534 |
Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230390 | KI#2, New Sol on User authorization revocation for API invocation procedure | pCR | Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
noted | [WTS] [JSN] |
S3-230391 | KI#2, New Sol UE credential based API invocation procedure |
pCR revised to S3-230535 |
Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230421 | pCR to 33.884 updating solution #2 |
pCR revised to S3-230515 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230422 | pCR to 33.884 adding new solution: PKCE flow |
pCR revised to S3-230517 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230423 | pCR to 33.884 adding new solution: token validation |
pCR revised to S3-230518 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
revised | [WTS] [JSN] |
S3-230451 | Update to Solution #4 in SNAAPPY |
pCR revision of S3-230069 |
Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230452 | Solution to address KI#2 |
pCR revision of S3-230070 |
Lenovo | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230475 | Address EN for solution 1: onboarding |
pCR revision of S3-230172 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230476 | Address EN for solution 1: authorization decision |
pCR revision of S3-230174 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230477 | Evaluation Update on Solution 1 |
pCR revision of S3-230175 |
Huawei, HiSilicon | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230486 | A solution for authorization before allowing access to resources |
pCR revision of S3-230230 |
Ericsson | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230515 | pCR to 33.884 updating solution #2 |
pCR revision of S3-230421 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230517 | pCR to 33.884 adding new solution: PKCE flow |
pCR revision of S3-230422 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230518 | pCR to 33.884 adding new solution: token validation |
pCR revision of S3-230423 |
NTT DOCOMO INC. | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230519 | draft TR 33.884 | draft TR | NTT DOCOMO INC. | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] | |
S3-230520 | Sol#3 Resolution of EN on Mutual Authentication |
pCR revision of S3-230077 |
Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230522 | Sol#3 Resolution of EN on Client Credential Grant |
pCR revision of S3-230078 |
Nokia, Nokia Shanghai Bell | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230534 | KI#2, New Sol OAuth 2.0 based API invocation procedure |
pCR revision of S3-230389 |
Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230535 | KI#2, New Sol UE credential based API invocation procedure |
pCR revision of S3-230391 |
Xiaomi communications | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230543 | Update of Key Issue #2 |
pCR revision of S3-230337 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230544 | New Solution on Resource owner Authorization in API Invocation using OAuth 2.0 Authorization Code Grant |
pCR revision of S3-230338 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
S3-230545 | New Solution on Resource owner Authorization in API Invocation |
pCR revision of S3-230339 |
Samsung | 33.884 0.3.0 | FS_SNAAPPY | Rel-18 |
S3-109-ad hoc-e AI: 5.11 |
approved | [WTS] [JSN] |
73 documents (0.32291698455811 seconds)