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 |
---|---|---|---|---|---|---|---|---|---|
R4-2211872 | On PDCCH demod requirements for multi-TRP | discussion | Apple | NR_feMIMO-Perf |
R4-104-e AI: 9.17.4.1.2 |
noted | [WTS] [JSN] | ||
R4-2212112 | On Enhancement on Multi-TRP for feMIMO | discussion | Nokia, Nokia Shanghai Bell | NR_feMIMO-Perf | Rel-17 |
R4-104-e AI: 9.17.4.1.2 |
noted | [WTS] [JSN] | |
R4-2212448 | Discussion on demodulation performance requirements definition for Rel17 multi-TRP | discussion | MediaTek inc. | NR_feMIMO-Perf | Rel-17 |
R4-104-e AI: 9.17.4.1.2 |
noted | [WTS] [JSN] | |
R4-2212551 | Discussion on the PDCCH enhancement for Multi-TRP | discussion | Ericsson | NR_feMIMO-Perf | Rel-17 |
R4-104-e AI: 9.17.4.1.2 |
noted | [WTS] [JSN] | |
R4-2212559 | Views on Performance Requirements for Multi-TRP PDCCH Tests | discussion | Qualcomm Incorporated |
R4-104-e AI: 9.17.4.1.2 |
noted | [WTS] [JSN] | |||
R4-2212560 | Simulation Results on m-TRP PDCCH Tests |
discussion revised to R4-2214212 |
Qualcomm Incorporated |
R4-104-e AI: 9.17.4.1.2 |
revised | [WTS] [JSN] | |||
R4-2213840 | Discussion on UE FeMIMO demod mTRP | discussion | Huawei,HiSilicon | NR_feMIMO-Perf |
R4-104-e AI: 9.17.4.1.2 |
noted | [WTS] [JSN] | ||
R4-2213842 | Simulation results on UE FeMIMO demod mTRP | other | Huawei,HiSilicon | NR_feMIMO-Perf |
R4-104-e AI: 9.17.4.1.2 |
noted | [WTS] [JSN] | ||
R4-2214212 | Simulation Results on m-TRP PDCCH Tests |
discussion revision of R4-2212560 |
Qualcomm Incorporated |
R4-104-e AI: 9.17.4.1.2 |
noted | [WTS] [JSN] |
9 documents (0.31538486480713 seconds)