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-260177 | Solution evaluation for solution 1 |
pCR revised to S3-260889 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260178 | Solution evaluation for solution 11 |
pCR revised to S3-261006 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260179 | Solution evaluation for solution 7 |
pCR revised to S3-260895 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260180 | Solution enhancements for solution 1 |
pCR revised to S3-260888 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260181 | Introduction of user scenarios for 256-bit support |
pCR revised to S3-260874 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260182 | Explanations of the Term AEAD | pCR | Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260183 | Updates on the terms related to AEAD | pCR | Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-260193 | Pseudo-CR on assumption update |
pCR revised to S3-260876 |
KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260194 | Pseudo-CR on Definitions and abbreviations | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-260195 | Pseudo-CR on new Key Issue Interworking and co-existence | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260196 | Pseudo-CR on new solution for handling of input parameters for interworking | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260197 | Pseudo-CR on Solution #2 update | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260198 | Pseudo-CR on Solution #8 update | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260217 | Align terms for AEAD | pCR | vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-260218 | Solution#4 Update on AEAD Algorithm Negotiation |
pCR revised to S3-260890 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260219 | New solutiion on AEAD Algorithm Interface |
pCR revised to S3-260881 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260220 | Update on A.3 Order of Operations |
pCR revised to S3-260875 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260221 | New Solution on Interoperability Analysis between AEAD-only and non-AEAD systems | pCR | vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260269 | New solution on algorithm selection |
pCR revised to S3-260880 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260270 | New solution on using NCAx as pure cipher algorithm |
pCR revised to S3-260882 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260272 | New solution on using NCAx as pure integrity algorithm |
pCR revised to S3-260883 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260331 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260332 | Conclusion for KI#3 | pCR | ZTE Corporation | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260333 | resolve EN and add evaluation for solution #3 |
pCR revised to S3-260891 |
ZTE Corporation | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260379 | update to solution#5 |
pCR revised to S3-260892 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260380 | update to solution#9 |
pCR revised to S3-260896 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260381 | general conclusion on the candidate 256bit algorithms | pCR | Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260393 | EN addressing for solution #10 | pCR | Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260394 | New solution about on-demand Extra-IV value derivation |
pCR revised to S3-260884 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260494 | Address the ENs in solution #6 |
pCR revised to S3-260893 |
Beijing Xiaomi Mobile Software | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260495 | Add the evaluation of solution #6 |
pCR revised to S3-260894 |
Beijing Xiaomi Mobile Software | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260514 | AEAD - KI#1 revision |
pCR revised to S3-260878 |
Apple | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260590 | New sol on using NCAx as cipher and integrity algorithm |
pCR revised to S3-260885 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260594 | Pseudo-CR on defining terms for TR 33.771 |
pCR revised to S3-260872 |
Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260595 | Pseudo-CR on solution for supporting AEAD mode |
pCR revised to S3-260879 |
Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260680 | Way forward for the application of AEAD | discussion | China Mobile Com. Corporation | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] | |
| S3-260685 | Adding definitions | pCR | Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-260686 | New KI on authenticated encryption |
pCR revised to S3-260877 |
Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260687 | New Solution for KI#1 | pCR | Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260688 | Update of Annex A | pCR | Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260689 | New Solution for KI on authenticated encryption | pCR | Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260690 | New Solution for KI#2 |
pCR revised to S3-260886 |
Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260699 | Solution to KI#3 |
pCR revised to S3-260887 |
Lenovo, Motorola Mobility | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260872 | Pseudo-CR on defining terms for TR 33.771 |
pCR revision of S3-260594 |
Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260873 | Draft TR 33.771 | draft TR | Vivo | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] | |
| S3-260874 | Introduction of user scenarios for 256-bit support |
pCR revision of S3-260181 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260875 | Update on A.3 Order of Operations |
pCR revision of S3-260220 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260876 | Pseudo-CR on assumption update |
pCR revision of S3-260193 |
KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260877 | New KI on authenticated encryption |
pCR revision of S3-260686 |
Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260878 | AEAD - KI#1 revision |
pCR revision of S3-260514 |
Apple | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260879 | Pseudo-CR on solution for supporting AEAD mode |
pCR revision of S3-260595 |
Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260880 | New solution on algorithm selection |
pCR revision of S3-260269 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260881 | New solutiion on AEAD Algorithm Interface |
pCR revision of S3-260219 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260882 | New solution on using NCAx as pure cipher algorithm |
pCR revision of S3-260270 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260883 | New solution on using NCAx as pure integrity algorithm |
pCR revision of S3-260272 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260884 | New solution about on-demand Extra-IV value derivation |
pCR revision of S3-260394 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260885 | New sol on using NCAx as cipher and integrity algorithm |
pCR revision of S3-260590 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260886 | New Solution for KI#2 |
pCR revision of S3-260690 |
Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260887 | Solution to KI#3 |
pCR revision of S3-260699 |
Lenovo, Motorola Mobility | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260888 | Solution enhancements for solution 1 |
pCR revision of S3-260180 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260889 | Solution evaluation for solution 1 |
pCR revision of S3-260177 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260890 | Solution#4 Update on AEAD Algorithm Negotiation |
pCR revision of S3-260218 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260891 | resolve EN and add evaluation for solution #3 |
pCR revision of S3-260333 |
ZTE Corporation | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260892 | update to solution#5 |
pCR revision of S3-260379 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260893 | Address the ENs in solution #6 |
pCR revision of S3-260494 |
Beijing Xiaomi Mobile Software | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260894 | Add the evaluation of solution #6 |
pCR revision of S3-260495 |
Beijing Xiaomi Mobile Software | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260895 | Solution evaluation for solution 7 |
pCR revision of S3-260179 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260896 | update to solution#9 |
pCR revision of S3-260380 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-261006 | Solution evaluation for solution 11 |
pCR revision of S3-260178 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
69 documents (0.35819602012634 seconds)