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-2310871 | Maintenance on UL precoding indication for multi-panel transmission | discussion | Huawei, HiSilicon | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2310924 | Maintenance on Rel-18 MPUE Uplink Transmission | discussion | InterDigital, Inc. | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2310952 | Maintenance on UL precoding indication for multi-panel transmission | discussion | ZTE | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311043 | Remaining issues on UL precoding indication for multi-panel transmission | discussion | Fujitsu | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311088 | Maintenance on UL precoding indication for multi-panel transmission | discussion | vivo | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311159 | Remaining issues on UL precoding indication for multi-panel transmission | discussion | Spreadtrum Communications | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311218 | Remaining issues of UL precoding indication for multi-panel transmission | discussion | OPPO | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311319 | Remaining issues on UL precoding indication for multi-panel transmission | discussion | CATT | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311366 | Maintenance on UL precoding indication for multi-panel transmission | discussion | Lenovo | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311384 | Maintenance on multi-panel uplink transmission | discussion | xiaomi | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311422 | Remaining issues on UL precoding indication for multi-panel transmission | discussion | NEC | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311479 | Remaining issues on UL precoding indication for multi-panel transmission | discussion | CMCC | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311523 | Remaining Issues on UL Precoding for Multi-panel Transmission | discussion | Panasonic | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311570 | On Simultaneous Multi-Panel Transmission | discussion | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | ||
R1-2311617 | Remaining issues on multi-panel transmission | discussion | NTT DOCOMO, INC. | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311657 | UL precoding indication for multi-panel transmission | discussion | Intel Corporation | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311677 | Remaining issues on multi-panel simultaneous transmissions | discussion | Apple | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311726 | Maintenance on UL multi-panel transmission | discussion | Sharp | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311734 | Remaining issues on UL precoding indication for multi-panel transmission | discussion | Langbo | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311744 | Maintenance of precoder Indication for Multi-Panel UL Transmission | discussion | Nokia, Nokia Shanghai Bell | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311794 | Remaining issues of UL precoding indication for multi-panel transmission | discussion | Transsion Holdings | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311835 | Remaining details on UL precoding indication for STxMP | discussion | Samsung | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311930 | Remaining issues on UL precoding indication for multi-panel transmission | discussion | Ruijie Network Co. Ltd | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2311973 | Remaining issues on simultaneous UL transmission across multi-panel | discussion | MediaTek Inc. | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2312006 | Remaining issues on UL precoding indication for multi-panel transmission | discussion | Hyundai Motor Company | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2312030 | Simultaneous multi-panel transmission | discussion | Qualcomm Incorporated | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2312194 | Maintenance on UL precoding indication for multi-panel transmission | discussion | Ericsson | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
not treated | [WTS] [JSN] | |
R1-2312255 | Summary #1 on Rel-18 STxMP | discussion | Moderator (OPPO) | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
noted | [WTS] [JSN] | |
R1-2312256 | Summary #2 on Rel-18 STxMP | discussion | Moderator (OPPO) | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
noted | [WTS] [JSN] | |
R1-2312257 | Summary #3 on Rel-18 STxMP | discussion | Moderator (OPPO) | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R1-115 AI: 8.1.4.1 |
withdrawn | [WTS] [JSN] |
30 documents (0.3430769443512 seconds)