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-190613 | New Solution: Battery efficient AKMA |
pCR revised to S3-190926 |
KPN N.V. | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190632 | Solution to KI#9 Key separation for AKMA AFs |
pCR revised to S3-190927 |
NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190639 | Solution for Established Key Synchronization |
pCR revised to S3-190929 |
NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190640 | Discussion on use of established keys for AKMA root key | discussion | NEC Europe Ltd | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] | |
S3-190641 | Discussion on using KSEAF and/or KAUSF for AKMA in view of regulatory compliance | discussion | NEC Europe Ltd | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] | |
S3-190642 | Resolving Editor’s Notes in Solution #16 | pCR | NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190643 | Solution for Roaming Architecture | pCR | NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190644 | Updating solution #16 to include home network option |
pCR revised to S3-190930 |
NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190645 | Creating a combined solution for usage of KSEAF and KAUSF |
pCR revised to S3-190996 |
NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190646 | New KI on Synchronization of Keys when using established keys | pCR | NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190688 | improvement for AKMA architecture | pCR | Huawei, HiSilicon | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190701 | Evaluation of solution 4 | pCR | Huawei, Hisilicon | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190702 | Key issue on Key freshness in AKMA |
pCR revised to S3-190924 |
Huawei, Hisilicon | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190703 | Solution for Key freshness in AKMA |
pCR revised to S3-191005 |
Huawei, Hisilicon | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190750 | New KI: Interworking between AKMA and GBA | pCR | Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190767 | AKMA Architecture and procedures with the anchor function as NEF | pCR | China Mobile Com. Corporation | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190774 | Resolving Editor's notes in solution 6 |
pCR revised to S3-190931 |
China Mobile Com. Corporation | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190801 | pCR: Reusing KAUSF for AKMA |
pCR revision of S3-190385 revised to S3-190928 |
Qualcomm Incorporated | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190806 | Evaluation of solution 2 | pCR | Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190807 | Protocol details for solution 3 | pCR | Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190808 | Evaluation of solution 3 | pCR | Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190821 | Updates to Solution #14 | pCR | Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190822 | Conclusion to Solution #14 | pCR | Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190823 | New Solution Key Lifetime | pCR | Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190824 | Updates to KI #14 |
pCR revised to S3-190925 |
Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190836 | Modification of user identity in solution 2 and solution 3 | pCR | ZTE Corporation, Nubia | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
noted | [WTS] [JSN] |
S3-190842 | Solution 15 editorials |
pCR revised to S3-190932 |
Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190843 | Solution 15 comment on the application keys |
pCR revised to S3-190933 |
Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190844 | Solution 15 evaluation |
pCR revised to S3-190935 |
Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
revised | [WTS] [JSN] |
S3-190922 | New KI: Interworking between AKMA and GBA | pCR | Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
withdrawn | [WTS] [JSN] |
S3-190923 | draft TR 33.835 | draft TR | China Mobile | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] | |
S3-190924 | Key issue on Key freshness in AKMA |
pCR revision of S3-190702 |
Huawei, Hisilicon | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190925 | Updates to KI #14 |
pCR revision of S3-190824 |
Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190926 | New Solution: Battery efficient AKMA |
pCR revision of S3-190613 |
KPN N.V. | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190927 | Solution to KI#9 Key separation for AKMA AFs |
pCR revision of S3-190632 |
NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190928 | pCR: Reusing KAUSF for AKMA |
pCR revision of S3-190801 |
Qualcomm Incorporated | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190929 | Solution for Established Key Synchronization |
pCR revision of S3-190639 |
NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190930 | Updating solution #16 to include home network option |
pCR revision of S3-190644 |
NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190931 | Resolving Editor's notes in solution 6 |
pCR revision of S3-190774 |
China Mobile Com. Corporation | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190932 | Solution 15 editorials |
pCR revision of S3-190842 |
Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190933 | Solution 15 comment on the application keys |
pCR revision of S3-190843 |
Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190934 | Way forward on evaluations for FS_AKMA | discussion | ORANGE |
S3-ah-35591 AI: 5.5 |
endorsed | [WTS] [JSN] | |||
S3-190935 | Solution 15 evaluation |
pCR revision of S3-190844 |
Ericsson | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-190996 | Creating a combined solution for usage of KSEAF and KAUSF |
pCR revision of S3-190645 |
NEC Europe Ltd | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
S3-191005 | Solution for Key freshness in AKMA |
pCR revision of S3-190703 |
Huawei, Hisilicon | 33.835 0.3.0 | FS_AKMA | Rel-16 |
S3-ah-35591 AI: 5.5 |
approved | [WTS] [JSN] |
45 documents (0.34013199806213 seconds)