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-2300252 | On RRM requirements for NR MIMO evolution for downlink and uplink | discussion | Apple | NR_MIMO_evo_DL_UL-Core |
R4-106 AI: 9.28.3.2 |
noted | [WTS] [JSN] | ||
| R4-2300469 | Discussion on Rel-18 FeMIMO RRM impacts | discussion | Intel Corporation | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R4-106 AI: 9.28.3.2 |
noted | [WTS] [JSN] | |
| R4-2300530 | NR MIMO evolution for downlink and uplink - RRM Requirements impacts | discussion | Nokia, Nokia Shanghai Bell | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R4-106 AI: 9.28.3.2 |
noted | [WTS] [JSN] | |
| R4-2300909 | on the RRM requirement impact for MIMO-e | discussion | Xiaomi | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R4-106 AI: 9.28.3.2 |
noted | [WTS] [JSN] | |
| R4-2300918 | Discussion on R18 MIMO for RRM requirements impacts | discussion | MediaTek Inc. | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R4-106 AI: 9.28.3.2 |
noted | [WTS] [JSN] | |
| R4-2301006 | Discussion on RRM impact on Rel-18 MIMO evolution for downlink and uplink | discussion | Samsung | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R4-106 AI: 9.28.3.2 |
noted | [WTS] [JSN] | |
| R4-2302018 | Discussion on RRM impacts for R18 MIMO evolution | discussion | Huawei, HiSilicon |
R4-106 AI: 9.28.3.2 |
noted | [WTS] [JSN] | |||
| R4-2302664 | On RRM requirements for MIMO evolution | discussion | Ericsson | NR_MIMO_evo_DL_UL-Core | Rel-18 |
R4-106 AI: 9.28.3.2 |
noted | [WTS] [JSN] |
8 documents (0.31675481796265 seconds)