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 |
---|---|---|---|---|---|---|---|---|---|
R2-1813603 | Proposed RAN2 work plan on NTN | Work Plan | Thales, Nomor Research GmbH | Rel-16 |
R2-103 AI: 11.6 |
noted | [WTS] [JSN] | ||
R2-1813610 | RAN2 Skeleton Report on NTN |
pCR revised to R2-1815650 |
Thales, Nomor Research GmbH | 38.821 0.1.0 | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
revised | [WTS] [JSN] |
R2-1813613 | RAN2 requirements on NTN | Work Plan | Nomor Research GmbH, Thales | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | ||
R2-1813615 | Considerations on MAC Control Loops and Timings in Non-Terrestrial Networks (NTN) | discussion | Nomor Research GmbH, Thales | Rel-16 |
R2-103 AI: 11.6 |
noted | [WTS] [JSN] | ||
R2-1813616 | Considerations on RLC Control Loops and Timings in Non-Terrestrial Networks (NTN) | discussion | Nomor Research GmbH, Thales | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | ||
R2-1813617 | Considerations on PDCP Control Loops and Timings in Non-Terrestrial Networks (NTN) | discussion | Nomor Research GmbH, Thales | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | ||
R2-1813881 | Overview of NTN impacts to RAN2 | discussion | Spreadtrum Communications | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | ||
R2-1813890 | Considerations on architecture and deployment scenarios of NTN | discussion | Huawei, HiSilicon | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1813891 | Consideration on the impact of rapid motion of satellite in NTN | discussion | Huawei, HiSilicon | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
noted | [WTS] [JSN] | |
R2-1813892 | Consideration on the impact of high propagation delay in NTN | discussion | Huawei, HiSilicon | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
noted | [WTS] [JSN] | |
R2-1813947 | Discussion on the mobility for Non Terrestrial Network | discussion | ZTE Corporation, Sanechips | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1813948 | TP on mobility aspect for Non Terrestrial Network | discussion | ZTE Corporation, Sanechips | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1814031 | Challenge on the paging performance in NTN |
discussion revised to R2-1816718 |
ZTE Corporation, Sanechips | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | ||
R2-1814243 | Discussion on Tracking Area Management in NTN | discussion | ZTE Corporation, Sanechips | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1814244 | Discussion on Network Identities in NTN | discussion | ZTE Corporation, Sanechips | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1814740 | Consideration on RAN2 impacts of NTN support in NR | discussion | Sony | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1814816 | Impacts of propagation delay in TDD mode | discussion | Ericsson | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
noted | [WTS] [JSN] | |
R2-1814877 | Considerations on NTN deployment scenarios | discussion | Nokia, Nokia Shanghai Bell | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
noted | [WTS] [JSN] | |
R2-1814888 | Impacts of propagation delay on user plane | discussion | Ericsson | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
noted | [WTS] [JSN] | |
R2-1814889 | Impacts of propagation delay on control plane | discussion | Ericsson | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1814890 | Overview on impacts of propagation delay | discussion | Ericsson | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1814931 | Spot beam versus cell in NTN NR | discussion | Ericsson | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1814932 | Scenarios for NTN NR REL-16 SI | discussion | Ericsson | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
noted | [WTS] [JSN] | |
R2-1814933 | Mobility aspects for NTN NR | discussion | Ericsson | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1814934 | Requirements for NTN NR | discussion | Ericsson | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1815254 | Impact of NTN cell movement | discussion | CMCC |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |||
R2-1815255 | Issues of UE mobility state estimation in NTN | discussion | CMCC |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |||
R2-1815256 | Utilization of beam footprint information |
discussion revised to R2-1818133 |
CMCC |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |||
R2-1815336 | Discussion on the Issue for paging in NTN |
discussion revised to R2-1816447 |
LG Electronics Inc. | FS_NR_NTN_solutions |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | ||
R2-1815387 | Considerations on RRC connection handling in NTN | discussion | LG Electronics Deutschland | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1815499 | Signalling Delay in NTN |
discussion revised to R2-1818333 |
LG Electronics Inc. | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] | |
R2-1815650 | RAN2 Skeleton Report on NTN |
pCR revision of R2-1813610 revised to R2-1815953 |
Thales, Nomor Research GmbH | 38.821 0.1.0 | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
revised | [WTS] [JSN] |
R2-1815953 | RAN2 Skeleton Report on NTN |
pCR revision of R2-1815650 |
Thales, Nomor Research GmbH | 38.821 0.1.0 | FS_NR_NTN_solutions | Rel-16 |
R2-103 AI: 11.6 |
not treated | [WTS] [JSN] |
33 documents (0.36640381813049 seconds)