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-2205865 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | Huawei, HiSilicon | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2205965 | Discussion on support of two overlapping CRS patterns for DSS | discussion | ZTE, China Telecom | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2206004 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | Spreadtrum Communications | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2206058 | Discussion on two overlapping CRS rate matching patterns | discussion | vivo | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2206325 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | OPPO | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2206433 | Support for 2 overlapping CRS patterns | discussion | Nokia, Nokia Shanghai Bell | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2206659 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | Xiaomi | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2206843 | Two overlapping CRS rate matching patterns | discussion | Samsung | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2207012 | Discussion on supporting two overlapping CRS rate matching pattern | discussion | MediaTek Inc. | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2207131 | Supporting two overlapping CRS rate matching patterns | discussion | InterDigital, Inc. | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2207250 | UE support for two overlapping CRS rate matching patterns | discussion | Qualcomm Incorporated | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2207348 | Disucssion on UE supporting for two overlapping CRS rate matching patterns | discussion | Apple | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2207423 | Discussion on LTE CRS rate matching pattern | discussion | NTT DOCOMO, INC. | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2207440 | UE support for overlapping CRS rate matching patterns | discussion | Ericsson | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2207842 | Feature lead summary #1 on UE support for two overlapping CRS rate matching patterns |
discussion revised to R1-2207843 |
Moderator (ZTE) | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
revised | [WTS] [JSN] | |
| R1-2207843 | Feature lead summary #2 on UE support for two overlapping CRS rate matching patterns |
discussion revision of R1-2207842 |
Moderator (ZTE) | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
noted | [WTS] [JSN] | |
| R1-2207844 | Feature lead summary #3 on UE support for two overlapping CRS rate matching patterns | discussion | Moderator (ZTE) | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
noted | [WTS] [JSN] | |
| R1-2208193 | [Draft] LS to RAN2 on two overlapping LTE-CRS patterns in Rel-18 DSS |
LS out LS To: RAN2 |
ZTE | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
revised | [WTS] [JSN] | |
| R1-2208194 | LS to RAN2 on two overlapping LTE-CRS patterns in Rel-18 DSS |
LS out LS To: RAN2 |
RAN1, ZTE | NR_DSS_enh-Core | Rel-18 |
R1-110 AI: 9.9.2 |
approved | [WTS] [JSN] | |
| R1-2208427 | Discussion on multi-carrier UL Tx switching | discussion | Huawei, HiSilicon | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2208487 | Discussion on Multi-carrier UL Tx switching scheme | discussion | ZTE | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2208565 | Discussion on multi-carrier UL Tx switching scheme | discussion | Spreadtrum Communications | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2208659 | Discussion on UL TX switching | discussion | vivo | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2208780 | Discussion on UL Tx switching across up to 3 or 4 bands | discussion | China Telecom | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2208861 | Discussion on multi-carrier UL Tx switching scheme | discussion | OPPO | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2208992 | Discussion on multi-carrier UL Tx switching scheme | discussion | CATT | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209068 | Discussions on multi-carrier UL Tx switching scheme | discussion | Intel Corporation | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209111 | Considerations on Multi-carrier UL Tx switching scheme | discussion | Sony | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
withdrawn | [WTS] [JSN] | |
| R1-2209300 | Discussion on multi-carrier UL Tx switching scheme | discussion | xiaomi | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209353 | Discussion on multi-carrier UL Tx switching scheme | discussion | CMCC | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209455 | Discussion on Multi-carrier UL Tx switching scheme | discussion | LG Electronics | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209596 | On multi-carrier UL Tx switching | discussion | Apple | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209747 | On multi-carrier UL Tx switching | discussion | Samsung | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209772 | On multi-carrier UL Tx switching scheme | discussion | MediaTek Inc. | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209861 | Multi-carrier UL Tx switching | discussion | Ericsson | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2209918 | Discussion on Multi-carrier UL Tx switching scheme | discussion | NTT DOCOMO, INC. | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2210001 | Discussion on Rel-18 UL Tx switching | discussion | Qualcomm Incorporated | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2210035 | Discussion on multi-carrier UL Tx switching scheme | discussion | Google Inc. | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2210192 | On Multi-Carrier UL Tx Switching | discussion | Nokia, Nokia Shanghai Bell | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
| R1-2210280 | Summary#1 of discussion on multi-carrier UL Tx switching scheme | discussion | Moderator (NTT DOCOMO, INC.) | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
noted | [WTS] [JSN] | |
| R1-2210455 | Summary#2 of discussion on multi-carrier UL Tx switching scheme | discussion | Moderator (NTT DOCOMO, INC.) | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
noted | [WTS] [JSN] | |
| R1-2210548 | Summary#3 of discussion on multi-carrier UL Tx switching scheme |
discussion revised to R1-2210723 |
Moderator (NTT DOCOMO, INC.) | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
revised | [WTS] [JSN] | |
| R1-2210723 | Summary#4 of discussion on multi-carrier UL Tx switching scheme |
discussion revision of R1-2210548 |
Moderator (NTT DOCOMO, INC.) | NR_MC_enh-Core | Rel-17 |
R1-110-bis-e AI: 9.9.2 |
noted | [WTS] [JSN] | |
| R1-2210724 | LS on UE capability and gNB configuration for UL Tx switching across 3 or 4 bands in Rel-18 |
LS out LS To: RAN2 |
RAN1, NTT DOCOMO | NR_MC_enh-Core | Rel-18 |
R1-110-bis-e AI: 9.9.2 |
approved | [WTS] [JSN] |
44 documents (0.35027194023132 seconds)