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-233736 | API invoker obtaining authorization from resource owner | other | Huawei, HiSilicon | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | ||
| S3-233737 | Revocation procedures invoked by API invoker | other | Huawei, HiSilicon | Rel-18 |
S3-112 AI: 4.28 |
noted | [WTS] [JSN] | ||
| S3-233738 | Revocation procedure invoked by resource owner client | other | Huawei, HiSilicon | Rel-18 |
S3-112 AI: 4.28 |
not treated | [WTS] [JSN] | ||
| S3-233789 | pCR to DraftCR SNAAPPY Security requirements on CAPIF-8 |
draftCR revised to S3-234299 |
Nokia, Nokia Shanghai Bell | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
revised | [WTS] [JSN] | |
| S3-233790 | pCR to DraftCR SNAAPPY Functional security models for CAPIF supporting RNAA | draftCR | Nokia, Nokia Shanghai Bell | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
noted | [WTS] [JSN] | |
| S3-233791 | pCR to DraftCR SNAAPPY API invoker is part of UE | draftCR | Nokia, Nokia Shanghai Bell | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-233972 | pCR to DraftCR SNAAPPY: Definition of device | draftCR | Nokia, Nokia Shanghai Bell | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
noted | [WTS] [JSN] | |
| S3-233976 | pCR to SNAAPPY CR baseline living document | other | Ericsson | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234046 | pCR to living document of RNAA: updates to clause 5 | other | Samsung | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234049 | Authentication and authorization using OAuth including redirection | other | Samsung | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234051 | Add a new annex on token for RNAA | other | Samsung | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234053 | pCR to living document RNAA: revocation | other | Samsung | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
not treated | [WTS] [JSN] | |
| S3-234118 | Update token and token request for the RNAA scenarios | other | Xiaomi Communications | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234119 | API invoker authorization revocation for RNAA scenarios | other | Xiaomi Communications | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
not treated | [WTS] [JSN] | |
| S3-234120 | Update the general procedure to address the redundant authorization issue | other | Xiaomi Communications | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234121 | Authorization code grant with PKCE for the RNAA scenarios | other | Xiaomi Communications | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234122 | API invoker onboarding mechainsm for RNAA scenarios | other | Xiaomi Communications | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
noted | [WTS] [JSN] | |
| S3-234123 | Client credentials grant type for the RNAA scenarios | other | Xiaomi Communications | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234124 | Update onboarding and authorization mechanism selection procedure to support RNAA scenarios | other | Xiaomi Communications | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234125 | Authorization code flow for the RNAA scenarios | other | Xiaomi Communications | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234126 | Update to Clause 6.5 for clarification on claims | draftCR | Lenovo | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
merged | [WTS] [JSN] | |
| S3-234128 | baseline SNAAPPY draft CR to 33.122 |
draftCR revised to S3-234300 |
NTT DOCOMO INC. | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
revised | [WTS] [JSN] | |
| S3-234129 | pCR to draft CR on SNAAPPY - editorials |
other revised to S3-234297 |
NTT DOCOMO INC. | SNAAPPY |
S3-112 AI: 4.28 |
revised | [WTS] [JSN] | ||
| S3-234130 | pCR to draft CR on SNAAPPY - adding oauth flows |
other revised to S3-234298 |
NTT DOCOMO INC. | SNAAPPY |
S3-112 AI: 4.28 |
revised | [WTS] [JSN] | ||
| S3-234297 | pCR to draft CR on SNAAPPY - editorials |
other revision of S3-234129 |
NTT DOCOMO INC. | SNAAPPY |
S3-112 AI: 4.28 |
approved | [WTS] [JSN] | ||
| S3-234298 | pCR to draft CR on SNAAPPY - adding oauth flows |
other revision of S3-234130 |
NTT DOCOMO INC. | SNAAPPY |
S3-112 AI: 4.28 |
approved | [WTS] [JSN] | ||
| S3-234299 | pCR to DraftCR SNAAPPY Security requirements on CAPIF-8 |
draftCR revision of S3-233789 |
Nokia, Nokia Shanghai Bell | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
approved | [WTS] [JSN] | |
| S3-234300 | baseline SNAAPPY draft CR to 33.122 |
draftCR revision of S3-234128 |
NTT DOCOMO INC. | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
revised | [WTS] [JSN] | |
| S3-234360 | CR on security for resource owner aware northbound access to APIs | CR | NTT DOCOMO INC. | 33.122 18.0.0 CR#36 catB | SNAAPPY | Rel-18 |
S3-112 AI: 4.28 |
agreed | [WTS] [JSN] |
29 documents (0.30194306373596 seconds)