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 |
---|---|---|---|---|---|---|---|---|---|
R4-2311619 | Discussion on RRM requirements of LPHAP | discussion | CATT | NR_pos_enh2 | Rel-18 |
R4-108 AI: 8.22.3.3 |
noted | [WTS] [JSN] | |
R4-2311887 | Discussion on LPHA positioning | discussion | CMCC |
R4-108 AI: 8.22.3.3 |
noted | [WTS] [JSN] | |||
R4-2311983 | On requirements for LPHAP | other | Qualcomm Incorporated | NR_pos_enh2-Core | Rel-18 |
R4-108 AI: 8.22.3.3 |
noted | [WTS] [JSN] | |
R4-2312074 | RRM aspects in the study on LPHAP use case | other | ZTE Corporation | NR_pos_enh2-Core | Rel-18 |
R4-108 AI: 8.22.3.3 |
noted | [WTS] [JSN] | |
R4-2312671 | Discussion on LPHAP use case | other | OPPO | NR_pos_enh2-Core | Rel-18 |
R4-108 AI: 8.22.3.3 |
noted | [WTS] [JSN] | |
R4-2312735 | On issues related to LPHAP requirements | other | Ericsson | NR_pos_enh2-Core | Rel-18 |
R4-108 AI: 8.22.3.3 |
noted | [WTS] [JSN] | |
R4-2312838 | Discussion on RRM requirements for LPHAP |
LS out LS is reply to R1-2306248 LS To: RAN1 |
Huawei, HiSilicon | NR_pos_enh2 | Rel-18 |
R4-108 AI: 8.22.3.3 |
noted | [WTS] [JSN] | |
R4-2313530 | RRM Core Requirements for LPHAP Use Case 6 in NR Positioning | discussion | Nokia, Nokia Shanghai Bell | NR_pos_enh2-Core | Rel-18 |
R4-108 AI: 8.22.3.3 |
noted | [WTS] [JSN] |
8 documents (0.33223986625671 seconds)