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-231206 | Discussion on Xn impact of ME | discussion | Samsung | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231376 | AIML Mobility Enhancement | discussion | NEC | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231435 | Discussion on future UE trajectory collection | discussion | Lenovo, Intel Corporation, ZTE |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |||
R3-231436 | (TP for TS38.423) on future UE trajectory collection | other | Lenovo |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |||
R3-231467 | Discussion on XnAP impacts of AI/ML for UE associated metrics | discussion | CATT |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |||
R3-231468 | (TP for 38.423) Support of AI/ML based mobility optimization | other | CATT |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |||
R3-231514 | Discussion on AI/ML based mobility optimization | discussion | China Telecommunication | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231538 | Mobility Optimization Outputs | discussion | InterDigital | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231539 | (TP for AIML BLCR for TS 38.423) Mobility Optimization Outputs | other | InterDigital Finland Oy | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231608 | Cell based UE trajectory prediction exchange | discussion | Ericsson, InterDigital, Qualcomm | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231609 | (TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange | other | Ericsson, InterDigital, Qualcomm | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231619 | Open points on validity time and prediction accuracy | discussion | Ericsson | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231650 | Discussion on cell based UE trajectory prediction | discussion | LG Electronics Inc. |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |||
R3-231651 | (TP for NR_AIML_NGRAN-Core BL CR for TS 38.423) Discussion on cell based UE trajectory prediction | other | LG Electronics Inc. |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |||
R3-231657 | (TP for TS 38.423) AI/ML Mobility Optimization | other | Nokia, Nokia Shanghai Bell | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231658 | (TP for TS 38.423) Cell-based UE Trajectory Prediction | other | Nokia, Nokia Shanghai Bell | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231683 | Discussion on left issues of AI based mobility optimization | other | ZTE | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | ||
R3-231799 | On Predicted UE Trajectory Information | discussion | CMCC | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231825 | (TP for AIML BLCR for TS 38.423) Remaining open issues for mobility enhancements | other | Huawei | NR_AIML_NGRAN-Core | Rel-18 |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] | |
R3-231880 | CB: # AIRAN3_ME- Summary of email discussion |
discussion revised to R3-232026 |
NEC - moderator |
R3-119-bis-e AI: 12.2.2.2 |
revised | [WTS] [JSN] | |||
R3-232026 | CB: # AIRAN3_ME- Summary of email discussion |
discussion revision of R3-231880 |
NEC - moderator |
R3-119-bis-e AI: 12.2.2.2 |
noted | [WTS] [JSN] |
21 documents (0.34147906303406 seconds)