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-2205809 | Correction on HARQ-ACK transmission in NTN | draftCR | Huawei, HiSilicon | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2205828 | Maintenance on Release-17 NR NTN | discussion | THALES | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2205833 | Discussion on Common TA Drift Variation | discussion | Lockheed Martin | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2205973 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | discussion | Spreadtrum Communications | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2206013 | Remaining issues on NR-NTN | discussion | ZTE | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2206014 | Corrections on NR-NTN synchronization | draftCR | ZTE | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2206157 | Maintenance on Solutions for NR to support NTN | discussion | MediaTek Inc. | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2206178 | Maintenance on Solutions for NR to support non-terrestrial networks (NTN) | discussion | PANASONIC | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2206233 | Correction on HARQ process number for NTN | draftCR | ASUSTeK | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2206295 | Discussion on remaining issue for NTN-NR | discussion | OPPO | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2206296 | Draft CR on time relationship for MAC-CE activation | draftCR | OPPO | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2206854 | Draft CR on interpretation SFN indicating epoch time | draftCR | OPPO | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2206855 | Draft CR on editorial correction on Koffset MAC CE command | draftCR | OPPO | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2207137 | Further aspects of Rel-17 maintenance of NR over NTN | discussion | Nokia, Nokia Shanghai Bell | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2207138 | Draft CR for 38.211 to ensure correct interworking between open and closed loop TA | draftCR | Nokia, Nokia Shanghai Bell | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2207139 | Draft CR for 38.213 to capture correct validity timer expiry behavior for UL synchronization | draftCR | Nokia, Nokia Shanghai Bell | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2207193 | Maintenance for R17 NR NTN | discussion | Qualcomm Incorporated | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2207311 | Maintenance on NR NTN | discussion | Apple | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2207357 | Remaining issues on UL time and frequency synchronization enhancements in NTN | discussion | LG Electronics | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2207496 | Correction on HARQ feedback enabling for NTN | draftCR | ASUSTeK | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2207497 | Correction on HARQ feedback enabling for the first SPS PDSCH | draftCR | ASUSTeK | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2207512 | Correction on UE-specific TA for NTN | draftCR | Huawei, HiSilicon | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2207554 | On NR NTN maintenance issues | discussion | Ericsson | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2207632 | FL Summary #1: Maintenance on UL time/frequency synchronization and timing relationship for NR NTN | discussion | THALES | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2207633 | FL Summary #2: Maintenance on UL time/frequency synchronization and timing relationship for NR NTN | discussion | THALES | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2207634 | FL Summary #3: Maintenance on UL time/frequency synchronization and timing relationship for NR NTN | discussion | THALES | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2207635 | FL Summary #4: Maintenance on UL time/frequency synchronization and timing relationship for NR NTN | discussion | THALES | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
withdrawn | [WTS] [JSN] | |
| R1-2207666 | Discussion on interpretation of SFN indicating Epoch time | discussion | Huawei, HiSilicon | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2207687 | Summary#1 of maintenance on scheduling and HARQ for NR NTN | discussion | Moderator (ZTE) | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2208042 | CR on the clarification of PUCCH resource determination in 38.213 |
CR revised to R1-2208124 |
Moderator (ZTE), Huawei, HiSilicon, Xiaomi, OPPO, Ericsson | 38.213 17.2.0 CR#339 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
revised | [WTS] [JSN] |
| R1-2208043 | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.213 |
CR revised to R1-2208125 |
Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson | 38.213 17.2.0 CR#340 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
revised | [WTS] [JSN] |
| R1-2208044 | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.214 |
CR revised to R1-2208126 |
Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson | 38.214 17.2.0 CR#307 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
revised | [WTS] [JSN] |
| R1-2208045 | CR on DCI size for Rel-17 NTN HARQ in 38.212 |
CR revised to R1-2208127 |
Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson | 38.212 17.2.0 CR#116 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
revised | [WTS] [JSN] |
| R1-2208124 | CR on the clarification of PUCCH resource determination in 38.213 |
CR revision of R1-2208042 |
Moderator (ZTE), Huawei, HiSilicon, Xiaomi, OPPO, Ericsson | 38.213 17.2.0 CR#3391 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
agreed | [WTS] [JSN] |
| R1-2208125 | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.213 |
CR revision of R1-2208043 |
Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson | 38.213 17.2.0 CR#3401 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
agreed | [WTS] [JSN] |
| R1-2208126 | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.214 |
CR revision of R1-2208044 |
Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson | 38.214 17.2.0 CR#3071 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
agreed | [WTS] [JSN] |
| R1-2208127 | CR on DCI size for Rel-17 NTN HARQ in 38.212 |
CR revision of R1-2208045 |
Moderator (ZTE), Huawei, HiSilicon, ASUSTek, Xiaomi, OPPO, Ericsson | 38.212 17.2.0 CR#1161 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
agreed | [WTS] [JSN] |
| R1-2208135 | Session notes for 8.4 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) | other | Ad-Hoc Chair (Huawei) | NR_NTN_solutions-Core | Rel-17 |
R1-110 AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2208829 | Discussion on remaining issue for NTN-NR | discussion | OPPO | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2208830 | Draft CR on interpretation SFN indicating epoch time | draftCR | OPPO | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2208886 | Draft CR on the indication of downlink disabled HARQ feedback for NR NTN | draftCR | vivo | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2208993 | Correction on determination of the number of HARQ-ACK information bits for NTN | draftCR | Langbo | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2208994 | Correction on Type-2 HARQ-ACK codebook in PUSCH for NTN | draftCR | Langbo | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2209654 | On the validity of assistance information for R17 NR NTN | discussion | Ericsson | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2209823 | Correction on timing relationship parameter for NR NTN | draftCR | Huawei, HiSilicon | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2210019 | Remaining issues on solutions for NR to support NTN | discussion | Lenovo | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2210045 | Additional aspects of Rel-17 maintenance for NR over NTN | discussion | Nokia, Nokia Shanghai Bell | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not treated | [WTS] [JSN] | |
| R1-2210046 | Draft CR for 38.211 to ensure correct interworking between open and closed loop TA | draftCR | Nokia, Nokia Shanghai Bell | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2210047 | Draft CR for 38.213 to capture correct validity timer expiry behavior for UL synchronization | draftCR | Nokia, Nokia Shanghai Bell | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2210048 | Draft CR for 38.213 to clarify calculation and application of timing advance values for common TA and UE specific TA | draftCR | Nokia, Nokia Shanghai Bell | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
not pursued | [WTS] [JSN] | |
| R1-2210436 | Summary of [110bis-e-R17-NR-NTN-01] Email discussion to determine maintenance issues to be handled in RAN1#110bis-e | discussion | Moderator (Thales) | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2210580 | Summary#1 of [110bis-e-R17-NR-NTN-02] Email discussion for maintenance on timing relationship enhancements and UL time and frequency synchronization for NR NTN for issues 1-6, 1-1 and 1-4. | discussion | Moderator (Thales) | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2210581 | Summary#2 of [110bis-e-R17-NR-NTN-02] Email discussion for maintenance on timing relationship enhancements and UL time and frequency synchronization for NR NTN for issues 1-6, 1-1 and 1-4. | discussion | Moderator (Thales) | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2210587 | Summary#1 of maintenance on HARQ for Rel-17 NR-NTN | discussion | Moderator (ZTE) | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
noted | [WTS] [JSN] | |
| R1-2210588 | CR on the Type-2 HARQ-ACK codebook |
draftCR revised to R1-2210589 |
Moderator (ZTE) | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
revised | [WTS] [JSN] | |
| R1-2210589 | CR on the Type-2 HARQ-ACK codebook |
CR revision of R1-2210588 |
Moderator (ZTE), Ericsson, Nokia, Thales | 38.213 17.3.0 CR#375 catF | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
agreed | [WTS] [JSN] |
| R1-2210680 | Session notes for 8.4 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) | other | Ad-Hoc Chair (Huawei) | NR_NTN_solutions-Core | Rel-17 |
R1-110-bis-e AI: 8.4 |
noted | [WTS] [JSN] |
57 documents (0.39290308952332 seconds)