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 |
---|---|---|---|---|---|---|---|---|---|
R3-230142 | Discussion on Support for legacy QoE in NR-DC | discussion | CATT | NR_QoE_enh-Core |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | ||
R3-230143 | TP for Support for legacy QoE in NR-DC | other | CATT | NR_QoE_enh-Core | Rel-18 |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |
R3-230144 | Discussion on Support for RV-QoE in NR-DC | discussion | CATT | NR_QoE_enh-Core |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | ||
R3-230185 | Discussion on QoE configuration and reporting in NR-DC | discussion | Xiaomi | NR_QoE_enh-Core | Rel-18 |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |
R3-230330 | QoE measurement in NR-DC | discussion | Lenovo |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-230331 | (TP to TS 38.420&423) Support of QoE measurement in NR-DC | other | Lenovo |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-230370 | Support for QoE in NR-DC | discussion | Qualcomm Incorporated | NR_QoE_enh | Rel-18 |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |
R3-230378 | Further discussions on the support for QoE in NR-DC | discussion | Huawei | NR_QoE_enh | Rel-18 |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |
R3-230396 | The Support for QoE and RVQoE Measurements and Reporting in NR-DC Scenarios | discussion | Ericsson | NR_QoE_enh | Rel-18 |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |
R3-230524 | Further discussion on SN-triggered m-based QMC | discussion | Nokia, Nokia Shanghai Bell |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-230622 | Remaining issues on support of NR-DC | discussion | Samsung | NR_QoE_enh-Core | Rel-18 |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |
R3-230699 | Discussion on QoE measurement in NR-DC | discussion | China Unicom | NR_QoE_enh-Core | Rel-18 |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |
R3-230774 | Discussion on QoE configuration procedures in NR-RC | discussion | ZTE, China Telecom, CMCC |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-230775 | Discussion on MDT alignment and mobility in NR-DC | discussion | ZTE, China Unicom, CMCC |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-230776 | (TPs to BLCRs of 38.300 and 37.340) QoE measurement collection in NR-DC | other | ZTE |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-230900 | Summary of offline discussion on QoE measurements for NRDC | other | Ericsson |
R3-119 AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-231217 | Remaining open issues on support of NR-DC | discussion | Samsung | NR_QoE_enh-Core | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |
R3-231319 | Discussion on Support for legacy QoE in NR-DC | discussion | CATT | NR_QoE_enh-Core |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | ||
R3-231320 | Discussion on Support for RV-QoE in NR-DC | discussion | CATT | NR_QoE_enh-Core |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | ||
R3-231346 | Support for QoE in NR-DC | discussion | Qualcomm Incorporated | NR_QoE_enh | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |
R3-231431 | Discussion on QoE measurement in NR-DC | discussion | Lenovo |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-231488 | (TP for QoE BL CR for TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios |
other revised to R3-232035 |
Ericsson | NR_QoE_enh | Rel-18 |
R3-119-bis-e AI: 11.3 |
revised | [WTS] [JSN] | |
R3-231520 | Discussion on QoE configuration and reporting in NR-DC | discussion | Xiaomi | NR_QoE_enh-Core | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |
R3-231626 | Further discussion on SN-triggered m-based QMC | discussion | Nokia, Nokia Shanghai Bell |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-231776 | Further Consideration on QoE in NR-DC | discussion | ZTE, China Telecom, CMCC | NR_QoE_enh-Core | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |
R3-231777 | Dicussion on MDT alignment and mobility in NR-DC | discussion | ZTE, China Telecom | NR_QoE_enh-Core | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |
R3-231778 | TPs to BL CR of 38.401 and BL CR of 38.423 on NR QoE | other | ZTE, China Telecom | NR_QoE_enh-Core | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |
R3-231818 | Further discussions on the support for QoE in NR-DC | discussion | Huawei | NR_QoE_enh | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |
R3-231830 | Further discussion on QoE measurement in NR-DC | discussion | China Unicom | NR_QoE_enh-Core | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |
R3-231876 | CB: # QoE3_NR-DC- Summary of email discussion |
discussion revised to R3-231947 |
Ericsson - moderator |
R3-119-bis-e AI: 11.3 |
revised | [WTS] [JSN] | |||
R3-231919 | (draftCR TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios | draftCR | Ericsson | NR_QoE_enh | Rel-18 |
R3-119-bis-e AI: 11.3 |
reserved | [WTS] [JSN] | |
R3-231947 | CB: # QoE3_NR-DC- Summary of email discussion |
discussion revision of R3-231876 |
Ericsson - moderator |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] | |||
R3-232035 | (TP for QoE BL CR for TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios |
other revision of R3-231488 |
Ericsson | NR_QoE_enh | Rel-18 |
R3-119-bis-e AI: 11.3 |
noted | [WTS] [JSN] |
33 documents (0.35506319999695 seconds)