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-2109565 | QoE configuration, reporting and mobility | discussion | Qualcomm Incorporated | NR_QoE-Core |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | ||
R2-2109662 | QoE measurement configuration and general aspects | discussion | Intel Corporation | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2109832 | Further discussion on transmission of QoE reports | discussion | Lenovo, Motorola Mobility | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2109866 | Configuration and reporting of QoE measurements | discussion | Ericsson | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2109867 | QoE measurements at handover, resume and re-establishment | discussion | Ericsson, China Unicom | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
noted | [WTS] [JSN] | |
R2-2109984 | Discussion on QoE configuration | discussion | vivo | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2110073 | Supporting mobility for NR QoE |
discussion revised to R2-2201183 |
Apple | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2110074 | RRC segmentation for NR QoE | discussion | Apple | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2110099 | Discussion on QoE measurement collection in NR | discussion | OPPO | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2110605 | Discussion on QoE measurement configuration and reporting | discussion | Huawei, HiSilicon | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2110606 | QoE handling during UE mobility | discussion | Huawei, HiSilicon | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2110609 | Draft reply LS on QoE configuration and reporting related issues |
LS out LS To: SA4, SA5 |
Huawei, HiSilicon | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2110720 | QoE configuration handling |
discussion revision of R2-2107513 |
Nokia, Nokia Shanghai Bell | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | |
R2-2110991 | Discussion on NR QoE configuration | discussion | ZTE Corporation, Sanechips | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | ||
R2-2110993 | Discussion on NR QoE configuration | discussion | CATT | NR_QoE-Core |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | ||
R2-2111062 | Remaining issues on configuration and reporting | discussion | CMCC | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | ||
R2-2111132 | QoE configuration in general aspects | discussion | Samsung | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | ||
R2-2111133 | RRC segmentation for QoE configuration and report | discussion | Samsung | Rel-17 |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | ||
R2-2111188 | Discussion on NR QoE measurement and configurations | discussion | China Unicom | NR_QoE-Core |
R2-116-e AI: 8.14.2.1 |
available | [WTS] [JSN] | ||
R2-2111536 | Feature summary for 8.14.2.1 | discussion | Ericsson | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
noted | [WTS] [JSN] | |
R2-2111663 | LS on SA4 requirements for QoE |
LS out LS To: SA4 revised to R2-2111665 |
RAN2 | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
revised | [WTS] [JSN] | |
R2-2111665 | LS on SA4 requirements for QoE |
LS out LS To: SA4 revision of R2-2111663 |
RAN2 | NR_QoE-Core | Rel-17 |
R2-116-e AI: 8.14.2.1 |
approved | [WTS] [JSN] |
22 documents (0.33436393737793 seconds)