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 |
|---|---|---|---|---|---|---|---|---|---|
| R1-2500099 | Discussion on 3-antenna-port UL transmission | discussion | Huawei, HiSilicon | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500106 | 3-antenna-port UL transmissions | discussion | MediaTek Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500117 | Remaining Details on Rel-19 CB-based UL for 3TX UE | discussion | InterDigital, Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500119 | FL Summary Support for 3TX CB-based Uplink; First Round | discussion | Moderator (InterDigital, Inc.) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
noted | [WTS] [JSN] | |
| R1-2500120 | FL Summary Support for 3TX CB-based Uplink; Second Round | discussion | Moderator (InterDigital, Inc.) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
withdrawn | [WTS] [JSN] | |
| R1-2500121 | Summary of Discussion on 3TX CB-based Uplink in RAN1#120 | discussion | Moderator (InterDigital, Inc.) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
noted | [WTS] [JSN] | |
| R1-2500219 | Views on 3Tx uplink transmissions | discussion | CATT | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500243 | Discussion on 3-antenna-port codebook-based transmissions | discussion | ZTE Corporation, Sanechips | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500281 | Discussion on support for 3-antenna-port codebook-based transmissions | discussion | CMCC | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500344 | Remaining issues on 3-antenna-port codebook-based uplink transmissions | discussion | vivo | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500472 | Discussion on 3-antenna-port uplink transmissions | discussion | OPPO | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500539 | Remaining issues for 3 Tx UL transmissions | discussion | Ericsson | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500551 | Uplink 3 Port Codebook based Transmission | discussion | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | ||
| R1-2500701 | Support for 3-antenna-port codebook-based transmissions | discussion | Lenovo | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500727 | Discussion on the support of 3-antenna-port CB based transmissions | discussion | Xiaomi | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500773 | Remaining issues on R19 MIMO 3Tx transmission | discussion | Apple | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500842 | Views on Rel-19 3-antenna-port codebook-based transmissions | discussion | Samsung | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500879 | Discussions on 3-antenna-port codebook-based UL transmission | discussion | China Telecom Corporation Ltd. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500898 | On the support for 3-antenna-port codebook-based transmissions | discussion | Nokia | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2500932 | Discussion on uplink enhancement for UE with 3Tx | discussion | Fujitsu | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501129 | Support for 3-antenna-port transmission | discussion | Sharp | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501151 | Remaining issues for 3Tx CB based PUSCH | discussion | Qualcomm Incorporated | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501197 | Discussion on support for 3-antenna-port codebook-based transmissions | discussion | NTT DOCOMO, INC. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120 AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501744 | On Specifications of Rel-19 CB-based UL for 3TX UE | discussion | InterDigital, Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501746 | FL Summary Support for 3TX CB-based Uplink; First Round | discussion | Moderator (InterDigital, Inc.) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
noted | [WTS] [JSN] | |
| R1-2501747 | FL Summary Support for 3TX CB-based Uplink; Second Round | discussion | Moderator (InterDigital, Inc.) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
withdrawn | [WTS] [JSN] | |
| R1-2501748 | Summary of Discussion on 3TX CB-based Uplink in RAN1#120bis | discussion | Moderator (InterDigital, Inc.) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
noted | [WTS] [JSN] | |
| R1-2501782 | Discussion on 3-antenna-port codebook-based transmissions | discussion | ZTE Corporation, Sanechips | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501801 | Remaining issues on 3-antenna-port codebook-based uplink transmissions | discussion | vivo | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501852 | 3-antenna-port UL transmissions | discussion | MediaTek Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501941 | Remaining issues for 3 Tx UL transmissions | discussion | Ericsson Japan K.K. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2501951 | Uplink 3 Port Codebook based Transmission | discussion | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | ||
| R1-2501987 | Remaining issues on 3-antenna-port uplink transmission | discussion | CATT | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502109 | Support for 3-antenna-port codebook-based transmissions | discussion | Lenovo | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502155 | Discussion on support for 3-antenna-port codebook-based transmissions | discussion | CMCC | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502226 | Discussion on 3-antenna-port UL transmission | discussion | Huawei, HiSilicon | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502295 | Discussion on 3-antenna-port uplink transmissions | discussion | OPPO | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502359 | Views on Rel-19 3-antenna-port codebook-based transmissions | discussion | Samsung | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502436 | Discussion on the support of 3-antenna-port CB based transmissions | discussion | Xiaomi | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502526 | On the support for 3-antenna-port codebook-based transmissions | discussion | Nokia | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502600 | Remaining issues on R19 MIMO 3Tx transmission | discussion | Apple | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502667 | Support for 3-antenna-port transmission | discussion | Sharp | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] | |
| R1-2502761 | Discussion on support for 3-antenna-port codebook-based transmissions | discussion | NTT DOCOMO, INC. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.3 |
not treated | [WTS] [JSN] |
43 documents (0.37090182304382 seconds)