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-2304575 | Discussion on improved GNSS operations for IoT NTN | discussion | Spreadtrum Communications | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2304635 | Discussion on improved GNSS operations for IoT NTN | discussion | Huawei, HiSilicon | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2304688 | Enhancements for long connections in NB-IoT/eMTC over NTN | discussion | Nokia, Nokia Shanghai Bell | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2304754 | Discussion on remaining issues of improved GNSS operations for IoT NTN | discussion | CATT | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2304782 | Improved GNSS operations for IoT NTN | discussion | InterDigital, Inc. | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2304852 | Improved GNSS operations for IoT NTN | discussion | Lenovo | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2304919 | Discussion on the improved GNSS operation for IoT NTN | discussion | xiaomi | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305069 | On Improved GNSS Operations for IoT NTN | discussion | NEC | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305111 | Discussion on improved GNSS operations for IoT NTN | discussion | CMCC | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305262 | On improved GNSS operations for IoT NTN | discussion | Apple | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305286 | Remaining issues on improved GNSS operations for IoT NTN | discussion | Sharp | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305355 | Improved GNSS Operations for IoT-NTN | discussion | Qualcomm Incorporated | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305439 | Discussion on improved GNSS operations for IoT NTN | discussion | OPPO | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305532 | Improved GNSS operations for IoT NTN | discussion | Samsung | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305559 | Discussion on improved GNSS operation for IoT-NTN | discussion | ZTE | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305651 | Improved GNSS operations for IoT NTN | discussion | MediaTek Inc. | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305910 | Improved GNSS operations for IoT NTN | discussion | Nordic Semiconductor ASA | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305916 | On improved GNSS operation in IoT NTN | discussion | Ericsson | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
not treated | [WTS] [JSN] | |
R1-2305998 | Feature lead summary#1 of AI 9.9.4 on improved GNSS operations | discussion | Moderator (MediaTek) | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
noted | [WTS] [JSN] | |
R1-2305999 | Feature lead summary#2 of AI 9.9.4 on improved GNSS operations | discussion | Moderator (MediaTek) | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
noted | [WTS] [JSN] | |
R1-2306202 | Feature lead summary#3 of AI 9.9.4 on improved GNSS operations | discussion | Moderator (MediaTek) | IoT_NTN_enh-Core | Rel-18 |
R1-113 AI: 9.9.4 |
noted | [WTS] [JSN] |
21 documents (0.3292350769043 seconds)