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-221830 | Proposed solution for key issue #1 using SHAKEN based third-party specific user identities |
pCR revised to S3-222320 |
Qualcomm Incorporated | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-221952 | New solution for 3rd party ID | pCR | Huawei, HiSilicon | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
merged | [WTS] [JSN] |
S3-221953 | New KI on security aspects of SBA in IMS | pCR | Huawei, HiSilicon | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-221954 | New KI on security aspects of IMS DC |
pCR revised to S3-222338 |
Huawei, HiSilicon | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-222022 | New solution: How the Originating IMS network signs the 3rd party IDs and terminating IMS network verifies the 3rd party IDs |
pCR revised to S3-222401 |
Ericsson | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
revised | [WTS] [JSN] |
S3-222220 | New solution on AAA Server based Authorization for Third Party Specific User Identities | pCR | Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
merged | [WTS] [JSN] |
S3-222221 | New solution on IMS HSS based Authorization for Third Party Specific User Identities | pCR | Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
merged | [WTS] [JSN] |
S3-222222 | New solution on Verification of Third Party Specific User Identities based on STIR/SHAKEN framework | pCR | Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
merged | [WTS] [JSN] |
S3-222320 | Proposed solution for key issue #1 using SHAKEN based third-party specific user identities |
pCR revision of S3-221830 |
Qualcomm Incorporated, Huawei, Hisilicon, Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-222338 | New KI on security aspects of IMS DC |
pCR revision of S3-221954 |
Huawei, HiSilicon | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
approved | [WTS] [JSN] |
S3-222340 | Draft TR 33.890 020 | draft TR | Huawei, HiSilicon | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
available | [WTS] [JSN] | |
S3-222401 | New solution: How the Originating IMS network signs the 3rd party IDs and terminating IMS network verifies the 3rd party IDs |
pCR revision of S3-222022 |
Ericsson, Beijing Xiaomi Mobile Software | 33.89 0.1.0 | FS_NG_RTC_SEC | Rel-18 |
S3-108-e AI: 5.15 |
approved | [WTS] [JSN] |
12 documents (0.34381699562073 seconds)