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-2503278 | Enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | Huawei, HiSilicon | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503304 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | MediaTek Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503354 | Remaining issues on asymmetric DL sTRP/UL mTRP scenarios | discussion | vivo | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503436 | Remaining Details of Rel-19 Asymmetric mTRP Operation | discussion | InterDigital, Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503511 | Enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | Spreadtrum, UNISOC | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503558 | Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios | discussion | Samsung | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503671 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | ZTE Corporation, Sanechips, China Telecom | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503712 | Enhancement for asymmetric DL sTRP UL mTRP | discussion | Tejas Network Limited | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503730 | Enhancements on asymmetric DL STRP/UL MTRP scenarios | discussion | Ofinno | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503789 | Remaining issues on asymmetric DL sTRP and UL mTRP scenarios | discussion | CATT | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503817 | Enhancement for Asymmetric DL sTRP/UL mTRP Scenarios | discussion | Panasonic | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503826 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | CMCC | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503878 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Xiaomi | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503915 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Lenovo | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503929 | Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios | discussion | NEC | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503978 | Remaining issues on asymmetric DL sTRP UL mTRP scenarios | discussion | Ericsson | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2503986 | Discussions on asymmetric DL sTRP/UL mTRP scenarios | discussion | LG Electronics | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504063 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Sony | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504079 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Nokia | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504135 | Remaining issues in asymmetric UL MIMO operation | discussion | ETRI | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504173 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | Transsion Holdings | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504231 | Enhancements on asymmetric DL sTRP/UL mTRP scenarios | discussion | OPPO | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504298 | Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios | discussion | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | ||
| R1-2504314 | Enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | Apple | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504390 | Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios | discussion | Qualcomm Incorporated | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504458 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Sharp | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504462 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | discussion | TCL | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
withdrawn | [WTS] [JSN] | |
| R1-2504463 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | discussion | TCL | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504497 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | NTT DOCOMO, INC. | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
not treated | [WTS] [JSN] | |
| R1-2504655 | Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP | discussion | Moderator (OPPO) | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
noted | [WTS] [JSN] | |
| R1-2504656 | Summary #2 on Rel-19 asymmetric DL sTRP/UL mTRP | discussion | Moderator (OPPO) | NR_MIMO_Ph5-Core | Rel-19 |
R1-121 AI: 9.2.4 |
noted | [WTS] [JSN] |
31 documents (0.36172103881836 seconds)