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-2205862 | Discussion on multi-cell scheduling with a single DCI | discussion | Huawei, HiSilicon | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2205962 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | ZTE | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206005 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
discussion revised to R1-2207695 |
Spreadtrum Communications | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
revised | [WTS] [JSN] | |
| R1-2206059 | Discussion on multi-cell scheduling | discussion | vivo | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206103 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Langbo | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206155 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Nokia, Nokia Shanghai Bell | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206176 | Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Fujitsu | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206243 | Discussion on Multi-cell PXSCH scheduling with a single DCI | discussion | NEC | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
withdrawn | [WTS] [JSN] | |
| R1-2206326 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | OPPO | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206382 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CATT | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206451 | Discussion on multi-cell scheduling via a single DCI | discussion | Lenovo | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206467 | Discussion on Multi-cell PXSCH scheduling with a single DCI | discussion | NEC | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206599 | Discussions on multi-cell scheduling with a single DCI | discussion | Intel Corporation | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206627 | Discussion on the design of multi-cell scheduling with a single DCI | discussion | Xiaomi | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206663 | Multi-cell scheduling with a single DCI | discussion | InterDigital, Inc. | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206682 | Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CAICT | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206700 | Discussion on multi-cell scheduling with a single DCI | discussion | China Telecom | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206844 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Samsung | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2206929 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | CMCC | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207007 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | MediaTek Inc. | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207040 | Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | LG Electronics | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207097 | Discussion on Multicarrier scheduling with a single DCI | discussion | FGI | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207143 | Discussions on multi-cell scheduling with a single DCI | discussion | Sharp | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207251 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Qualcomm Incorporated | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207349 | On multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Apple | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207424 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | NTT DOCOMO, INC. | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207441 | Multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Ericsson | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207447 | Discussion on multi-cell scheduling with a single DCI | discussion | ITRI | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207553 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI | discussion | Google Inc. | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207695 | Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
discussion revision of R1-2206005 |
Spreadtrum Communications | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2207769 | 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 AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2207770 | 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 AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2207771 | 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 AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2208046 | 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 AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2208047 | Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
discussion revised to R1-2208048 |
Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
revised | [WTS] [JSN] | |
| R1-2208048 | Feature lead summary#6 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
discussion revision of R1-2208047 |
Moderator (Lenovo) | NR_MC_enh-Core | Rel-18 |
R1-110 AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2208401 | Discussion on power saving enhancements for XR | discussion | Ericsson | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2208420 | Discussion on XR-specific power saving techniques | discussion | Huawei, HiSilicon | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2208566 | Discussion on XR specific power saving techniques | discussion | Spreadtrum Communications | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2208660 | Discussion on XR specific power saving enhancements |
discussion revised to R1-2210273 |
vivo | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
revised | [WTS] [JSN] | |
| R1-2208781 | Discussion on XR specific power saving enhancement for NR | discussion | China Telecom | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2208862 | Discussion on XR specific power saving techniques | discussion | OPPO | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2208952 | UE Power saving techniques for XR | discussion | CATT | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2208999 | XR specific power saving techniques | discussion | TCL Communication Ltd. | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209069 | Discussion on XR specific power saving techniques | discussion | Intel Corporation | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209112 | Considerations on XR specific power saving techniques | discussion | Sony | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209128 | XR-specific power saving techniques | discussion | Lenovo | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209197 | Evaluation on XR specific power saving techniques | discussion | ZTE, Sanechips | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209263 | Discussions on techniques for XR Power Saving | discussion | xiaomi | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209354 | Discussion on XR-specific power saving techniques | discussion | CMCC | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209387 | Discussion on XR specific power saving techniques | discussion | Panasonic | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209410 | Discussion on power saving techniques for XR |
discussion revision of R1-2206959 |
ETRI | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209427 | Discussion on XR specific power saving techniques | discussion | NEC | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209456 | Discussion on XR-specific power saving techniques | discussion | LG Electronics | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209517 | On XR specific power saving techniques | discussion | MediaTek Inc. | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209535 | XR-specific power saving enhancements | discussion | Nokia, Nokia Shanghai Bell | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209597 | XR specific power saving techniques | discussion | Apple | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209619 | Power saving techniques for XR | discussion | Rakuten Symphony | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209636 | On XR-specific power saving techniques | discussion | Google Inc. | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209657 | Discussion on XR specific power saving techniques | discussion | InterDigital, Inc. | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209748 | Considerations on Power Savings for XR | discussion | Samsung | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2209919 | Discussion on XR specific power saving techniques | discussion | NTT DOCOMO, INC. | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2210002 | Power saving techniques for XR | discussion | Qualcomm Incorporated | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2210084 | Further Discussion on XR power saving | discussion | III | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2210152 | XR-specific power saving enhancements | discussion | Nokia, Nokia Shanghai Bell | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
withdrawn | [WTS] [JSN] | |
| R1-2210273 | Discussion on XR specific power saving enhancements |
discussion revision of R1-2208660 |
vivo | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
not treated | [WTS] [JSN] | |
| R1-2210337 | Moderator Summary#1 on XR specific power saving techniques | discussion | Moderator (Qualcomm Incorporated) | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2210338 | Moderator Summary#2 on XR specific power saving techniques | discussion | Moderator (Qualcomm Incorporated) | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2210339 | Moderator Summary#3 on XR specific power saving techniques | discussion | Moderator (Qualcomm Incorporated) | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
noted | [WTS] [JSN] | |
| R1-2210340 | Final Moderator Summary on XR specific power saving techniques | discussion | Moderator (Qualcomm Incorporated) | FS_NR_XR_enh | Rel-18 |
R1-110-bis-e AI: 9.10.1 |
withdrawn | [WTS] [JSN] |
70 documents (0.32947492599487 seconds)