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-241116 | New Key Issue on permanent secret key length (K) | pCR | KDDI Corporation, Samsung, Xiaomi | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241117 | New Key Issue on different cryptographic key lengths in dual connectivity scenarios | pCR | KDDI Corporation, CMCC | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241118 | New Key Issue on algorithm negotiation on re-establishing RRC connection | pCR | KDDI Corporation, CMCC | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241170 | New Key Issue on authentication parameters in AKA procedure | pCR | ZTE Corporation | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241171 | New Key Issue on different length of cryptographic key in EPS and 5GS interworking | pCR | ZTE Corporation | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241172 | New Solution on different length of cryptographic key in EPS and 5GS interworking | pCR | ZTE Corporation | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241181 | New key issue on algorithm negotiation for 256-bit algorithms | pCR | vivo | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241190 | new kew issue on backward compatibility | pCR | CableLabs, Charter Communications | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241275 | Adaptations to AS and NAS Procedures | pCR | Nokia, Nokia Shanghai Bell | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241276 | Architecture Assumptions | pCR | Nokia, Nokia Shanghai Bell | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241286 | UE States and Transitions | pCR | Nokia, Nokia Shanghai Bell | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241288 | Introduction of AEAD Algorithm for Air-link Data Protection | pCR | Nokia, Nokia Shanghai Bell | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241289 | Introduction of AEAD Algorithm and the Order of Data Protection | pCR | Nokia, Nokia Shanghai Bell | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241291 | Discussion on AEAD Properties | discussion | Nokia, Nokia Shanghai Bell |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] | |||
S3-241310 | key issues on introducing 256-bit algorithm in 5GS | pCR | Huawei, HiSilicon | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241316 | New Key Issue on different cryptographic key lengths in URLLC scenario | pCR | Huawei, HiSilicon | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241359 | Add KI on 256 bits algorithms selection in 5G system | pCR | OPPO | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241362 | Add sol on 256 bits algorithm selection in 5G system | pCR | OPPO | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241377 | Conclusion on 256 bits algorithms selection in 5G system KI | pCR | OPPO | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241390 | New key issue on specifying usage of new encryption and integrity protection algorithms in the 5G system | pCR | Ericsson | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241391 | New solution for specifying usage of new encryption and integrity protection algorithms in the 5G system | pCR | Ericsson | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241394 | CAT256 - New KI for CAT_256 on correctly indication | pCR | Apple | 33.701 0.0.2 | FS_MiBiDA | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241395 | CAT256 - New solution for CAT_256 on correctly indication | pCR | Apple | 33.701 0.0.2 | FS_MiBiDA | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241396 | CAT256 - New KI for CAT_256 on Flexibility to adjust the preference on security algorithms | pCR | Apple | 33.701 0.0.2 | FS_MiBiDA | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241397 | CAT256 - New solution for CAT_256 on Flexibility to adjust the preference on security algorithms | pCR | Apple | 33.701 0.0.2 | FS_MiBiDA | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241466 | New KI on AKA related 256-bit algorithm update | pCR | Xiaomi communications | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241467 | New KI on negotiation for NAS and AS related 256-bit algorithms | pCR | Xiaomi communications | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241480 | KI on key hiearchy | pCR | OPPO | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241481 | Solution on Key Hierarchy | pCR | OPPO | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241482 | Conclusion on Key Hierarchy KI | pCR | OPPO | 33.700-41 0.1.0 | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
noted | [WTS] [JSN] |
S3-241504 | Draft TR 33.700-41 | draft TR | KDDI Corporation | FS_CAT256 | Rel-19 |
S3-115-adhoc-e AI: 5.5 |
withdrawn | [WTS] [JSN] |
31 documents (0.40427803993225 seconds)