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-2300130 | Discussion on multi-cell scheduling with a single DCI | discussion | Huawei, HiSilicon | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300233 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Spreadtrum Communications | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300289 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | OPPO | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300342 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ZTE | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300365 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | other | Nokia, Nokia Shanghai Bell | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300469 | Discussion on multi-cell scheduling | discussion | vivo | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300591 | Discussion on the remaining issues for the multi-cell scheduling with a single DCI | discussion | xiaomi | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300696 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CATT | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300725 | Remaining issues on multi-cell scheduling with a single DCI | discussion | China Telecom | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300731 | On multi-cell scheduling via a single DCI | discussion | Lenovo | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300756 | CSI request in case of multi-cell PUSCH scheduling | discussion | Fujitsu | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300830 | Discussion on Multi-cell PXSCH scheduling with a single DCI | discussion | NEC | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2300964 | Discussions on multi-cell scheduling with a single DCI | discussion | Intel Corporation | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301018 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CMCC | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301062 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CAICT | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301091 | Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2301092 | Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2301093 | Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2301094 | Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2301109 | Discussion on Multi-cell PUSCH/PDSCH scheduling | discussion | LG Electronics | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301280 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Samsung | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301315 | Remaining Issues on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Langbo | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301321 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ITRI | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301362 | On remaining issues for multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Apple | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301429 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Qualcomm Incorporated | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301509 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | NTT DOCOMO, INC. | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301556 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Ericsson | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301563 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Google Inc. | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2301601 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | MediaTek Inc. | NR_MC_enh-Core | Rel-18 |
R1-112 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302364 | Discussion on coverage enhancement for NR NTN | discussion | Huawei, HiSilicon | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302433 | Further considerations on coverage enhancements for NR over NTN | discussion | Nokia, Nokia Shanghai Bell | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302502 | Discussions on remaining issues of coverage enhancements in NR NTN | discussion | vivo | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302564 | Discussion on coverage enhancement for NR NTN | discussion | OPPO | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302616 | Discussion on coverage enhancements for NTN | discussion | Spreadtrum Communications | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302719 | Further discussion on UL coverage enhancement for NR NTN | discussion | CATT | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302738 | Discussion on coverage enhancement for NR NTN | discussion | Baicells | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302748 | Coverage enhancement for NR NTN | discussion | NEC | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302812 | On coverage enhancement for NR NTN | discussion | Intel Corporation | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302857 | On coverage enhancement for NR NTN | discussion | Sony | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2302998 | Discussion on coverage enhancement for NR-NTN | discussion | xiaomi | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303014 | On coverage enhancements for NR NTN | discussion | Ericsson | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303032 | Discussion on coverage enhancement for NR NTN | discussion | China Telecom | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303144 | On coverage enhancement for NR NTN | discussion | Samsung | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303204 | Discussion on coverage enhancement for NR NTN | discussion | ETRI | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303250 | Discussion on coverage enhancement for NR NTN | discussion | CMCC | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303294 | Discussion on coverage enhancement for NTN | discussion | ZTE | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303351 | UL coverage enhancements | discussion | MediaTek Inc. | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303499 | On Coverage Enhancement for NR NTN | discussion | Apple | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303534 | Coverage enhancements for NR NTN | discussion | Lenovo | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303606 | Coverage enhancements for NR NTN | discussion | Qualcomm Incorporated | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303625 | Discussion on coverage enhancement for NR-NTN | discussion | Panasonic | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303643 | Views on Coverage enhancement for NR NTN | discussion | Sharp | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303725 | Discussion on coverage enhancement for NR NTN | discussion | NTT DOCOMO, INC. | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303748 | Discussion on coverage enhancement for NR NTN | discussion | LG Electronics | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2303950 | Summary #1 on 9.9.1 Coverage enhancement for NR NTN | discussion | Moderator (NTT DOCOMO, INC.) | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2303951 | Summary #2 on 9.9.1 Coverage enhancement for NR NTN | discussion | Moderator (NTT DOCOMO, INC.) | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2303952 | Summary #3 on 9.9.1 Coverage enhancement for NR NTN |
discussion revised to R1-2303953 |
Moderator (NTT DOCOMO, INC.) | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
revised | [WTS] [JSN] | |
| R1-2303953 | Summary #4 on 9.9.1 Coverage enhancement for NR NTN |
discussion revision of R1-2303952 |
Moderator (NTT DOCOMO, INC.) | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2304093 | [Draft] LS on PUSCH DMRS bundling for NR NTN coverage enhancement |
LS out LS To: RAN4 revised to R1-2304094 |
Moderator (NTT DOCOMO, INC.) | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
revised | [WTS] [JSN] | |
| R1-2304094 | LS on PUSCH DMRS bundling for NR NTN coverage enhancement |
LS out LS To: RAN4 revision of R1-2304093 |
RAN1, NTT DOCOMO, INC. | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
approved | [WTS] [JSN] | |
| R1-2304244 | Summary EOM on 9.9.1 Coverage enhancement for NR NTN | discussion | Moderator (NTT DOCOMO, INC.) | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2304252 | [Draft] LS on higher layer signaling in Msg3 PUSCH for PUCCH repetition for Msg4 HARQ-ACK |
LS out LS To: RAN2 |
Moderator (NTT DOCOMO, INC.) | NR_NTN_enh-Core | Rel-18 |
R1-112-bis-e AI: 9.9.1 |
not pursued | [WTS] [JSN] |
62 documents (0.31806993484497 seconds)