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-202829 | LS on Clarification on processing of messages after NAS security establishment | LS in | C1-206582 |
S3-101-e AI: 5.17 |
noted | [WTS] [JSN] | |||
S3-202925 | Architecture and security assumptions of AMF re-allocation | pCR | ZTE Corporation | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-202926 | LS on Clarification of requirements and architecture impacts by network slice isolation |
LS out LS To: SA1, SA2 |
ZTE Corporation | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
noted | [WTS] [JSN] | |
S3-203040 | AMFREAL: Description of AMF reallocation procedure |
pCR revised to S3-203445 |
Huawei, Hisilicon | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203041 | AMFREAL: New key issue on registration failure with AMF reallocation | pCR | Huawei, Hisilicon | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-203042 | AMFREAL: New solution to registration failure with AMF reallocation |
pCR revised to S3-203446 |
Huawei, Hisilicon | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203180 | AMF re-allocation via RAN using existing security states |
pCR revised to S3-203395 |
Qualcomm Incorporated | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203214 | Assumptions for the AMF re-allocation security study |
pCR revised to S3-203419 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203215 | New key issue for the security of the AMF re-allocation procedures |
pCR revised to S3-203420 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203216 | New solution for AMF re-allocation procedure when 5G NAS security context is rerouted via RAN |
pCR revised to S3-203421 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203217 | New solution for NAS re-route via RAN and the use of a well-connected network function | pCR | Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
noted | [WTS] [JSN] |
S3-203293 | Key Issue on Security Context handling issues with AMF re-allocation | pCR | Lenovo, Motorola Mobility | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
merged | [WTS] [JSN] |
S3-203295 | Solution to enable NAS Security for AMF reallocation and reroute via RAN Scenario |
pCR revised to S3-203465 |
Lenovo, Motorola Mobility | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
revised | [WTS] [JSN] |
S3-203392 | Draft TR 33.864 v0.2.0 Study on the security of Access and Mobility Management Function (AMF) re-allocation | draft TR | Ericsson EspaƱa S.A. | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] | |
S3-203395 | AMF re-allocation via RAN using existing security states |
pCR revision of S3-203180 |
Qualcomm Incorporated | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203419 | Assumptions for the AMF re-allocation security study |
pCR revision of S3-203214 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203420 | New key issue for the security of the AMF re-allocation procedures |
pCR revision of S3-203215 |
Ericsson, Huawei, Hisilicon, China Mobile, Lenovo, Motorola Mobility | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203421 | New solution for AMF re-allocation procedure when 5G NAS security context is rerouted via RAN |
pCR revision of S3-203216 |
Ericsson | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203445 | AMFREAL: Description of AMF reallocation procedure |
pCR revision of S3-203040 |
Huawei, Hisilicon | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203446 | AMFREAL: New solution to registration failure with AMF reallocation |
pCR revision of S3-203042 |
Huawei, Hisilicon | 33.864 0.0.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
S3-203465 | Solution to enable NAS Security for AMF reallocation and reroute via RAN Scenario |
pCR revision of S3-203295 |
Lenovo, Motorola Mobility | 33.864 0.1.0 | FS_AMFREAL_SEC | Rel-17 |
S3-101-e AI: 5.17 |
approved | [WTS] [JSN] |
21 documents (0.33576703071594 seconds)