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-2205746 | Potential sidelink positioning solutions | other | FUTUREWEI | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2205838 | Potential solutions for SL positioning | discussion | Nokia, Nokia Shanghai Bell | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2205855 | Discussion on potential solutions for SL positioning | discussion | LG Electronics | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2205868 | Discussion on solutions to support SL positioning | discussion | Huawei, HiSilicon | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2205901 | Discussion on potential solutions for SL positioning | discussion | ZTE | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2205994 | Discussion on potential solutions for SL positioning | discussion | Spreadtrum Communications | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206046 | Discussion on potential solutions for sidelink positioning | discussion | vivo | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206124 | Discussion on potential solutions for SL positioning | discussion | Sony | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206240 | Discussion on Potential Solutions for SL Positioning | discussion | NEC | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206289 | Discussion on potential solutions for SL positioning | discussion | OPPO | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206405 | Discussion on potential solutions for SL positioning | discussion | CATT, GOHIGH | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206498 | On Potential SL Positioning Solutions | discussion | Lenovo | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206589 | Potential solutions for SL positioning | discussion | Intel Corporation | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206649 | Discussion on sidelink positioning solutions | discussion | Xiaomi | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
withdrawn | [WTS] [JSN] | |
R1-2206693 | Discussion on potential solutions for sidelink positioning | discussion | China Telecom | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206831 | Discussion on Potential Solutions for SL Positioning | discussion | Samsung | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2206917 | Discussion on potential solutions for SL positioning | discussion | CMCC | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207073 | Discussion on enhancement for sidelink positioning support | discussion | CEWiT | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207087 | Potential solutions for SL positioning | discussion | InterDigital, Inc. | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207125 | Potential solutions for SL positioning | discussion | Fraunhofer IIS, Fraunhofer HHI | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207238 | Potential Solutions for Sidelink Positioning | discussion | Qualcomm Incorporated | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207283 | Views on potential solutions for SL positioning | discussion | Sharp | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207341 | Discussions on Potential solutions for SL positioning | discussion | Apple | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207411 | Discussion on potential solutions for SL positioning | discussion | NTT DOCOMO, INC. | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207443 | Discussion on handling Anchor UE | discussion | DENSO AUTOMOTIVE | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207479 | The potential solutions for sidelink positioning | discussion | MediaTek Inc. | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207484 | Discussion on sidelink positioning |
discussion revised to R1-2209797 |
ASUSTeK | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207579 | Discussion on sidelink positioning solutions | discussion | Xiaomi | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207620 | On potential solutions for SL positioning | discussion | Ericsson | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
not treated | [WTS] [JSN] | |
R1-2207846 | Moderator Summary #1 on potential solutions for SL positioning |
discussion revised to R1-2207875 |
Moderator (Qualcomm) | FS_NR_pos_enh2 | Rel-18 |
R1-110 AI: 9.5.1.3 |
revised | [WTS] [JSN] | |
R1-2207875 | Moderator Summary #2 on potential solutions for SL positioning |
discussion revision of R1-2207846 |
Moderator (Qualcomm) | Rel-18 |
R1-110 AI: 9.5.1.3 |
noted | [WTS] [JSN] | ||
R1-2207974 | Moderator Summary #3 on potential solutions for SL positioning | discussion | Moderator (Qualcomm) | Rel-18 |
R1-110 AI: 9.5.1.3 |
noted | [WTS] [JSN] | ||
R1-2208186 | Moderator Summary #4 on potential solutions for SL positioning | discussion | Moderator (Qualcomm) | Rel-18 |
R1-110 AI: 9.5.1.3 |
noted | [WTS] [JSN] |
33 documents (0.30881500244141 seconds)