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-2205864 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | discussion | Huawei, HiSilicon | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2205964 | Discussion on NR PDCCH reception for DSS | discussion | ZTE | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2206003 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | discussion | Spreadtrum Communications | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2206057 | Discussion on PDCCH reception on CRS symbol | discussion | vivo | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2206324 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | discussion | OPPO | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2206432 | NR PDCCH overlapping with LTE CRS | discussion | Nokia, Nokia Shanghai Bell | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2206658 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | discussion | Xiaomi | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
withdrawn | [WTS] [JSN] | |
| R1-2206842 | On PDCCH receptions in symbols with LTE CRS | discussion | Samsung | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207011 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | discussion | MediaTek Inc. | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207039 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | discussion | LG Electronics | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207130 | Evaluation of NR PDCCH overlapping with LTE CRS | discussion | InterDigital, Inc. | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207249 | NR PDCCH reception in symbols with LTE CRS REs | discussion | Qualcomm Incorporated | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207347 | Discussion on NR PDCCH reception in symbols with LTE CRS REs | discussion | Apple | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207422 | Discussion on NR PDCCH reception in symbols with LTE CRS Res | discussion | NTT DOCOMO, INC. | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207439 | NR PDCCH reception in symbols with LTE CRS REs | discussion | Ericsson | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207591 | Considerations on NR PDCCH for DSS | discussion | KT Corp. | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2207801 | Summary#1 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | discussion | Moderator (Intel Corporation) | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2207802 | Summary#2 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | discussion | Moderator (Intel Corporation) | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2207803 | Summary#3 of AI: 9.9.1 NR PDCCH reception in symbols with LTE CRS REs | discussion | Moderator (Intel Corporation) | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2207865 | Joint Proposal on enabling LTE CRS puncturing of NR PDCCH for Rel18 DSS Enhancements WI | discussion | Ericsson, Nokia, Nokia Shanghai Bell, NTT DOCOMO, Softbank | Rel-18 |
R1-110 AI: 9.9.1 |
not treated | [WTS] [JSN] | ||
| R1-2208426 | Discussion on multi-cell scheduling with a single DCI | discussion | Huawei, HiSilicon | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2208486 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ZTE | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2208564 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Spreadtrum Communications | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2208658 | Discussion on multi-cell scheduling | discussion | vivo | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2208779 | Discussion on multi-cell scheduling with a single DCI | discussion | China Telecom | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2208860 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | OPPO | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2208991 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CATT | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2208997 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Langbo | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209020 | Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Fujitsu | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209067 | Discussions on multi-cell scheduling with a single DCI | discussion | Intel Corporation | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209239 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CAICT | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209299 | Discussion on the design of multi-cell scheduling with a single DCI | discussion | xiaomi | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209305 | On multi-cell scheduling via a single DCI | discussion | Lenovo | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209352 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CMCC | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209416 | Discussion on Multicarrier scheduling with a single DCI | discussion | FGI | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209426 | Discussion on Multi-cell PXSCH scheduling with a single DCI | discussion | NEC | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209454 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | LG Electronics | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209516 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | MediaTek Inc. | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209595 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Apple | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209746 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Samsung | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209860 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Ericsson | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2209917 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | NTT DOCOMO, INC. | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2210000 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Qualcomm Incorporated | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2210032 | Discussion on multi-cell scheduling with a single DCI | discussion | ITRI | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2210034 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Google Inc. | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2210151 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Nokia, Nokia Shanghai Bell | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
not treated | [WTS] [JSN] | |
| R1-2210350 | Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2210351 | Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2210352 | Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
noted | [WTS] [JSN] | |
| R1-2210662 | Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.1 |
noted | [WTS] [JSN] |
50 documents (0.32681393623352 seconds)