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-2404211 | MU-MIMO demodulation requirement discussion | discussion | Qualcomm Incorporated |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | |||
R4-2404237 | Discussion on MIMO-IC on MU-MIMO | discussion | MediaTek inc. | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | |
R4-2404238 | Simulation results of MIMO-IC on MU-MIMO | discussion | MediaTek inc. | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | |
R4-2404239 | Draft CR to 38.101-4 TDD 4Rx PDSCH requirements of MU-MIMO |
draftCR revised to R4-2406115 |
MediaTek inc. | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
revised | [WTS] [JSN] | |
R4-2404293 | On demod for requirements for MU-MIMO with advanced receiver | discussion | Apple | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2404294 | Simulation results for MU-MIMO with advanced receiver | discussion | Apple | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2404295 | DraftCR on FDD 4Rx requirements for advanced receiver for MU-MIMO |
draftCR revised to R4-2406116 |
Apple | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
revised | [WTS] [JSN] | |
R4-2404296 | Simulation result summary for MU-MIMO with advanced receiver | discussion | Apple | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2404391 | Discussion on test parameters for the advanced receiver for MU-MIMO | discussion | China Telecom | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | |
R4-2404392 | Discussion on test parameters for the advanced receiver for MU-MIMO: Simulation results | discussion | China Telecom | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | |
R4-2404393 | Draft big CR for UE advanced receiver performance requirements for MU-MIMO | draftCR | China Telecom | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
endorsed | [WTS] [JSN] | |
R4-2404525 | On Advanced Receivers - Test parameters | discussion | Nokia | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2404526 | On Advanced Receivers - Test parameters - Simulations | discussion | Nokia | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2404527 | DraftCR for 38.101-4 on RMC for Advanced Receivers |
draftCR revised to R4-2406117 |
Nokia | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
revised | [WTS] [JSN] | |
R4-2404750 | discussion on advanced receiver test parameters for MU-MIMO | discussion | Samsung | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2404751 | Draft CR on applicability rule of advanced receiver for MU-MIMO |
draftCR revised to R4-2406118 |
Samsung | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
revised | [WTS] [JSN] | |
R4-2405156 | Discussions on remaining issues for MU-MIMO | discussion | Huawei,HiSilicon | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2405157 | Simulation results for advanced receiver for MU-MIMO | other | Huawei,HiSilicon | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2405203 | Discussion on advanced receiver test parameters for MU-MIMO | other | ZTE Corporation | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | |
R4-2405204 | Simulation results for MU-MIMO with R-ML receiver | other | ZTE Corporation | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | |
R4-2405216 | Draft CR on introduction of TDD 2Rx requirements for advanced receiver for MU-MIMO |
draftCR revised to R4-2406119 |
ZTE Corporation | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
revised | [WTS] [JSN] | |
R4-2405475 | Draft CR to 38.101-4 Introduction of FDD 2Rx PDSCH requirements for advanced receiver for MU-MIMO |
draftCR revised to R4-2406120 |
Ericsson | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
revised | [WTS] [JSN] | |
R4-2405476 | On test case selection and applicability | discussion | Ericsson | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2405477 | Updated simulation results for phase II | other | Ericsson | NR_demod_enh3-Perf |
R4-110-bis AI: 6.11.2.2 |
noted | [WTS] [JSN] | ||
R4-2406115 | Draft CR to 38.101-4 TDD 4Rx PDSCH requirements of MU-MIMO |
draftCR revision of R4-2404239 |
MediaTek inc. | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
endorsed | [WTS] [JSN] | |
R4-2406116 | DraftCR on FDD 4Rx requirements for advanced receiver for MU-MIMO |
draftCR revision of R4-2404295 |
Apple | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
endorsed | [WTS] [JSN] | |
R4-2406117 | DraftCR for 38.101-4 on RMC for Advanced Receivers |
draftCR revision of R4-2404527 |
Nokia | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
endorsed | [WTS] [JSN] | |
R4-2406118 | Draft CR on applicability rule of advanced receiver for MU-MIMO |
draftCR revision of R4-2404751 |
Samsung | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
endorsed | [WTS] [JSN] | |
R4-2406119 | Draft CR on introduction of TDD 2Rx requirements for advanced receiver for MU-MIMO |
draftCR revision of R4-2405216 |
ZTE Corporation | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
endorsed | [WTS] [JSN] | |
R4-2406120 | Draft CR to 38.101-4 Introduction of FDD 2Rx PDSCH requirements for advanced receiver for MU-MIMO |
draftCR revision of R4-2405475 |
Ericsson | NR_demod_enh3-Perf | Rel-18 |
R4-110-bis AI: 6.11.2.2 |
endorsed | [WTS] [JSN] |
30 documents (0.35629296302795 seconds)