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-2600088 | Discussion on RRM measurement prediction | discussion | vivo | NR_AIML_Mob-Core | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |
| R2-2600104 | Discussion on RRM measurement prediction | discussion | Xiaomi |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |||
| R2-2600128 | Discussion on RRM measurement prediction | discussion | BYD | Rel-20 |
R2-133 AI: 9.3.2 |
withdrawn | [WTS] [JSN] | ||
| R2-2600258 | Discussion on functionality management for RRM measurement prediction |
discussion revised to R2-2601125 |
OPPO | NR_AIML_Mob-Core | Rel-20 |
R2-133 AI: 9.3.2 |
revised | [WTS] [JSN] | |
| R2-2600284 | Discussion on UE sided RRM measurement prediction | discussion | Transsion Holdings |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |||
| R2-2600313 | Discussion on RRM measurement prediction | discussion | Lekha Wireless Solutions | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2600332 | Functionality management for RRM measurement prediction | discussion | CATT, Turkcell | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |
| R2-2600343 | Discussion on RRM measurement prediction | discussion | Fujitsu | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |
| R2-2600363 | Discussion on RRM measurement prediction | discussion | Samsung | NR_AIML_Mob-Core | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |
| R2-2600375 | Discussion on Functionality Management for RRM Measurement Prediction | discussion | MediaTek Inc. | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | ||
| R2-2600380 | Discussion on RRM measurement prediction | discussion | NEC | NR_AIML_Mob-Core | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |
| R2-2600402 | RRM measurement prediction | discussion | Lenovo |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |||
| R2-2600416 | Discussion on RRM measurement prediction | discussion | Huawei, HiSilicon | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |
| R2-2600424 | Functionality management for UE sided model for RRM measurement prediction | discussion | InterDigital, Inc. | NR_AIML_Mob-Core | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |
| R2-2600451 | Measurement prediction | discussion | Apple | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |
| R2-2600485 | Discussion on inference configuration and reporting | discussion | China Telecom | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |
| R2-2600521 | Discussion on RRM measurement prediction | discussion | HONOR | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |
| R2-2600566 | LCM for UE-sided RRM measurement prediction | discussion | LG Electronics Inc. | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | ||
| R2-2600575 | Discussion on RRM prediction | discussion | ASUSTeK | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |
| R2-2600609 | Discussion on RRM measurement prediction | discussion | Tejas Network Limited | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2600612 | Discussions on RRM measurement prediction | discussion | NTT DOCOMO, INC. |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |||
| R2-2600671 | Discussion on LCM for RRM prediction | discussion | Spreadtrum, UNISOC | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2600716 | Discussion on RRM measurement prediction | discussion | BYD | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2600717 | Enhancements to support RRM measurement prediction |
discussion revision of R2-2508479 |
Fraunhofer IIS, Fraunhofer HHI |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |||
| R2-2600742 | Discussion on RRM Measurement Prediction | discussion | Ericsson | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |
| R2-2600837 | On NR RRM measurement prediction for UE-side models | discussion | Qualcomm Incorporated | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |
| R2-2600868 | RRM measurement prediction | discussion | Ofinno | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | |
| R2-2600875 | Discussion on RRM measurement prediction | discussion | Nokia | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2600902 | Discussion on RRM Measurement Prediction Functionality Management | discussion | Sharp | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2600958 | Discussion on UE sided RRM measurement prediction | discussion | CMCC | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |
| R2-2600971 | Discussion on RRM Measurement Prediction | discussion | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2601010 | Discussion on inference configuration and report for RRM measurement prediction for UE sided model | discussion | KT Corp. | NR_AIML_Mob |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2601026 | Discussion on RRM measurement prediction | discussion | ZTE Corporation | NR_AIML_Mob | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] | |
| R2-2601068 | Discussion on RRM measurement prediction | discussion | KDDI Corporation | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2601070 | Functionality management for RRM measurement prediction | discussion | Turkcell, CATT | Rel-20 |
R2-133 AI: 9.3.2 |
available | [WTS] [JSN] | ||
| R2-2601125 | Discussion on functionality management for RRM measurement prediction |
discussion revision of R2-2600258 |
OPPO | NR_AIML_Mob-Core | Rel-20 |
R2-133 AI: 9.3.2 |
noted | [WTS] [JSN] |
36 documents (0.37757015228271 seconds)