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-2203138 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | Huawei, HiSilicon | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2203211 | Discussion on support of two overlapping CRS patterns for DSS | discussion | ZTE | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
noted | [WTS] [JSN] | |
R1-2203345 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | Spreadtrum Communications | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2203582 | Discussion on two overlapping CRS rate matching patterns | discussion | vivo | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
noted | [WTS] [JSN] | |
R1-2203649 | Supporting two overlapping CRS rate matching patterns | discussion | InterDigital, Inc. | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2203835 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | xiaomi | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2203924 | Two overlapping CRS rate matching patterns | discussion | Samsung | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2204025 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | OPPO | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2204261 | Discussion on UE supporting for two overlapping CRS rate matching patterns | discussion | Apple | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2204396 | Discussion on LTE CRS rate matching pattern | discussion | NTT DOCOMO, INC. | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2204491 | Discussion on UE support for two overlapping CRS rate matching patterns | discussion | Spreadtrum Communications | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
withdrawn | [WTS] [JSN] | |
R1-2204710 | Discussion on supporting two overlapping CRS rate matching pattern | discussion | MediaTek Inc. | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2204824 | Support for 2 overlapping CRS patterns | discussion | Nokia, Nokia Shanghai Bell | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2204886 | UE support for overlapping CRS rate matching patterns | discussion | Ericsson | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2205050 | UE support for two overlapping CRS rate-matching patterns | discussion | Qualcomm Incorporated | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
not treated | [WTS] [JSN] | |
R1-2205258 | Feature lead summary #1 on UE support for two overlapping CRS rate matching patterns | discussion | Moderator (ZTE) | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
noted | [WTS] [JSN] | |
R1-2205259 | Feature lead summary #2 on UE support for two overlapping CRS rate matching patterns | discussion | Moderator (ZTE) | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
noted | [WTS] [JSN] | |
R1-2205499 | Feature lead summary #3 on UE support for two overlapping CRS rate matching patterns | discussion | Moderator (ZTE) | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
noted | [WTS] [JSN] | |
R1-2205500 | Feature lead summary #4 on UE support for two overlapping CRS rate matching patterns | discussion | Moderator (ZTE) | NR_DSS_enh-Core | Rel-18 |
R1-109-e AI: 9.9.2 |
noted | [WTS] [JSN] |
19 documents (0.33091020584106 seconds)