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-2203156 | Overview of evaluation on NR duplex evolution | discussion | Huawei, HiSilicon | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
noted | [WTS] [JSN] | |
| R1-2203203 | Discussion of evaluation on NR duplex evolution | discussion | ZTE | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2203214 | Discussion for Evaluation on NR duplex evolution | discussion | New H3C Technologies Co., Ltd. | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2203327 | Discussion on evaluation on NR duplex evolution | discussion | Spreadtrum Communications,BUPT | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2203458 | Discussion on deployment scenario and evaluation methodology for duplex operation | discussion | CATT | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2203557 | Evaluation on NR duplex evolution | discussion | vivo | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2203814 | Discussion on evaluation on NR duplex evolution | discussion | xiaomi | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2203903 | Deployment scenario and evaluation methodology for duplex evolution | discussion | Samsung | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204021 | Discussion on evaluation on NR duplex evolution | discussion | OPPO | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204053 | Evaluation on NR duplex evolution | discussion | SHARP Corporation | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204068 | Evaluation assumption and methodology for study on NR-duplex | discussion | InterDigital, Inc. | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204106 | Evaluation of NR duplex evolution | discussion | Ericsson | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204122 | Discussion on deployment scenario of NR duplex evolution | discussion | KT Corp. | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204135 | Discussion on evaluation on NR duplex evolution | discussion | Panasonic | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204244 | Initial evaluation on NR duplex evolution | discussion | Apple | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204303 | Discussion on evaluation on NR duplex evolution | discussion | CMCC | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204379 | Discussion on evaluation on NR duplex evolution | discussion | NTT DOCOMO, INC. | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
noted | [WTS] [JSN] | |
| R1-2204430 | On the evaluation methodology for NR duplexing enhancements | discussion | Nokia, Nokia Shanghai Bell | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204473 | Discussion on evaluation on NR duplex evolution | discussion | Spreadtrum Communications,BUPT | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
withdrawn | [WTS] [JSN] | |
| R1-2204529 | Study on Evaluation for NR duplex evolution | discussion | LG Electronics | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204721 | Deployment scenarios and evaluation methodology for NR duplex evolution | discussion | MediaTek Inc. | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204750 | Discussion on evaluation on NR duplex evolution | discussion | CEWiT | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2204799 | On evaluations for NR duplex evolution | discussion | Intel Corporation | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2205030 | On Deployment scenarios and evaluation Methodology for NR duplex evolution | discussion | Qualcomm Incorporated | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
not treated | [WTS] [JSN] | |
| R1-2205311 | Summary#1 on email discussion on evaluation of NR duplex evolution | discussion | Moderator(CMCC) | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
noted | [WTS] [JSN] | |
| R1-2205312 | Summary#2 on email discussion on evaluation of NR duplex evolution |
discussion revised to R1-2205313 |
Moderator(CMCC) | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
revised | [WTS] [JSN] | |
| R1-2205313 | Summary#3 on email discussion on evaluation of NR duplex evolution |
discussion revision of R1-2205312 |
Moderator(CMCC) | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
noted | [WTS] [JSN] | |
| R1-2205540 | Summary#4 on email discussion on evaluation of NR duplex evolution | discussion | Moderator(CMCC) | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
noted | [WTS] [JSN] | |
| R1-2205541 | Summary#5 on email discussion on evaluation of NR duplex evolution | discussion | Moderator(CMCC) | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
noted | [WTS] [JSN] | |
| R1-2205542 | Draft LS on interference modelling for duplex evolution |
LS out LS To: RAN4 |
Moderator(CMCC) | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
revised | [WTS] [JSN] | |
| R1-2205543 | LS on interference modelling for duplex evolution |
LS out LS To: RAN4 |
RAN1, CMCC | FS_NR_duplex_evo | Rel-18 |
R1-109-e AI: 9.3.1 |
approved | [WTS] [JSN] |
31 documents (0.35907387733459 seconds)