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-2402020 | Discussion on power control enhancements for DL sTRP and UL mTRP deployment | discussion | Huawei, HiSilicon | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402066 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | ZTE, China Telecom | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402070 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Ericsson | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402082 | Rel-19 Asymmetric mTRP Operation | discussion | InterDigital, Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402101 | Enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | Spreadtrum Communications | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402141 | Enhancements for asymmetric DL/UL scenarios | discussion | Intel Corporation | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402158 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | MediaTek Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402238 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | discussion | vivo | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402288 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | discussion | TCL | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402324 | Enhancements on asymmetric DL sTRP/UL mTRP scenarios | discussion | OPPO | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402379 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | discussion | CATT | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402462 | Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios | discussion | Samsung | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402499 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Lenovo | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402507 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | China Telecom, ZTE | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402531 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Langbo | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402561 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | CMCC | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402635 | Discussions on asymmetric DL sTRP/UL mTRP scenarios | discussion | LG Electronics | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402662 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Xiaomi | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402686 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | Transsion Holdings | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402719 | Discussion on asymmetric DL sTRP and UL mTRP | discussion | ASUSTeK | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402724 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | discussion | Honor | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402759 | Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios | discussion | NEC | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402794 | Discussion on UL-only mTRP operation | discussion | Fujitsu | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402841 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Nokia | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402877 | Views on R19 enhancement for asymmetric DL sTRP/UL mTRP | discussion | Apple | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2402963 | Considerations on enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Sony | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2403016 | Discussion on asymmetric DL_UL mTRP operation | discussion | ETRI | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2403089 | Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios | discussion | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | ||
R1-2403111 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Sharp | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2403132 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | Panasonic | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2403190 | Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios | discussion | Qualcomm Incorporated | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2403240 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | discussion | NTT DOCOMO, INC. | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
not treated | [WTS] [JSN] | |
R1-2403414 | Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP | discussion | Moderator (OPPO) | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
noted | [WTS] [JSN] | |
R1-2403415 | Summary #2 on Rel-19 asymmetric DL sTRP/UL mTRP | discussion | Moderator (OPPO) | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
noted | [WTS] [JSN] | |
R1-2403416 | Summary #3 on Rel-19 asymmetric DL sTRP/UL mTRP | discussion | Moderator (OPPO) | NR_MIMO_Ph5-Core | Rel-19 |
R1-116-bis AI: 9.2.4 |
noted | [WTS] [JSN] |
35 documents (0.31268882751465 seconds)