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-2308863 | Considerations on the system parameters for FR2-NTN | discussion | THALES | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2308872 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | Work Plan | THALES | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
withdrawn | [WTS] [JSN] | |
| R1-2309149 | Discussion on the RAN1 related aspects for NTN above 10 GHz | discussion | ZTE | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2309333 | Discussion on RAN4 LS on FR2-NTN PRACH aspects | discussion | LG Electronics | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2309492 | Discussion on FR2 issues for NR NTN | discussion | CATT | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2309543 | Discussion on the RAN1 impact for NTN above 10GHz | discussion | Beijing Xiaomi Mobile Software | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2309849 | Discussion on NTN above 10 GHz | discussion | Apple | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2309988 | Discussion on RAN4 LS on the system parameters for NTN above 10 GHz | discussion | MediaTek Inc. | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2310049 | Discussion on FR2-NTN for NR NTN | discussion | NTT DOCOMO, INC. | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2310108 | Discussions on RAN4 LS on FR2-NTN aspects | discussion | Sharp | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2310158 | Power control for RACH-less handover in NR NTN | discussion | Qualcomm Incorporated | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2310221 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | Work Plan | THALES | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2310412 | Discussion on RAN4 LS on FR2-NTN aspects | discussion | Moderator (Nokia) | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
noted | [WTS] [JSN] | |
| R1-2310496 | Summary of discussion on remaining issues for RACH-less handover | discussion | Moderator (Samsung) | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
noted | [WTS] [JSN] | |
| R1-2310544 | Session notes for 8.13 (Maintenance on NTN (Non-Terrestrial Networks) enhancements) | other | Ad-Hoc Chair (Huawei) | NR_NTN_enh-Core, IoT_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
endorsed | [WTS] [JSN] | |
| R1-2310564 | Discussion on RAN4 LS on FR2-NTN aspects, second round | discussion | Moderator (Nokia) | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
noted | [WTS] [JSN] | |
| R1-2310650 | Rel-18 Higher Layer Parameters for NR NTN | discussion | Moderator (Thales) | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
noted | [WTS] [JSN] | |
| R1-2310682 | Rel-18 Higher Layer Parameters for IoT NTN | discussion | Moderator (MediaTek) | IoT_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2310687 | RAN1 agreements for Rel-18 WI on NR NTN enhancements up to RAN1#114-bis | discussion | WI rapporteur (Thales) | NR_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] | |
| R1-2310689 | RAN1 agreements for Rel-18 WI on IoT NTN enhancements up to RAN1#114bis | discussion | Moderator (MediaTek) | IoT_NTN_enh-Core | Rel-18 |
R1-114-bis AI: 8.13 |
not treated | [WTS] [JSN] |
20 documents (0.32537412643433 seconds)