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-233709 | LS on beam application time, contents of cell switch command, TCI state activation and UE based TA measurement for LTM |
LS in source LS: R1-2306259 LS To: RAN2, RAN3, RAN4 |
RAN1(Fujitsu/Mediatek/CATT) | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-233719 | LS on Early TA and RACH-less |
LS in source LS: R2-2306897 LS To: RAN1, RAN3 |
RAN2(Ericsson) | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-233720 | LS on L1 measurements for LTM |
LS in source LS: R2-2306898 LS To: RAN1, RAN3 |
RAN2(Ericsson) | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-233827 | TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures | other | Nokia, Nokia Shanghai Bell | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-233828 | TP (BL CR TS 38.473) Additional Implications to L1/2 Triggered Mobility (LTM) | other | Nokia, Nokia Shanghai Bell | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-233840 | (TP to Mob_enh2 BL CR TS38.401) Discussion on L1/L2 based Inter-cell Mobility | other | Samsung Beijing | NR_Mob_enh2-Core |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-233869 | Rel-18 LTM issues | discussion | NEC | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-233870 | (TP to TS 38.473 on LTM) co-existence between LTM and L3 mobility |
other revised to R3-234661 |
NEC | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-233886 | (TP for L1L2Mob BLCR for TS 38.401) Reference configuration and Target Configuration ID in LTM | other | Google Inc. | LTE_NR_DC_enh2-Core |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-233887 | (TP for L1L2Mob BLCR for TS 38.473) Reference configuration and Target Configuration ID in LTM | other | Google Inc. | LTE_NR_DC_enh2-Core |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-233888 | (TP for L1L2Mob BL CR for TS 38.473) UE Context identification | other | Google Inc. | LTE_NR_DC_enh2-Core |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-233905 | (TP for LTM BL CR to TS 38.401) Solutions for LTM | other | Ericsson | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-233906 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
other revised to R3-234690 |
Ericsson | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-233984 | Signalling Support for LTM | discussion | Qualcomm Incorporated | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-234040 | Resource management at gNB-DU for LTM | discussion | Rakuten Symphony | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-234041 | Intra gNB CU-UP relocation during LTM | discussion | Rakuten Symphony | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-234074 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on RAN3 impacts from the incoming LSs |
other revised to R3-234642 |
Huawei |
R3-121 AI: 14.2 |
revised | [WTS] [JSN] | |||
| R3-234075 | (TP for L1L2Mob BLCR for TS 38.473): L1/L2 Mobility | other | Huawei |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |||
| R3-234165 | Discussion on L1L2 based inter-cell mobility | discussion | Lenovo |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |||
| R3-234166 | (TP to TS 38.401 & TS 38.470) Support of L1L2 based inter-cell mobility | other | Lenovo |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |||
| R3-234201 | (TP for BLCR of 38.401)Further consideration about LTM execution procedure | other | CATT |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |||
| R3-234202 | (TP for 38.473 BLCR) Further consideration about candidate cell configuration | other | CATT |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |||
| R3-234348 | Discussions on stage-3 and inter-DU LTM | discussion | LG Electronics Inc. | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-234349 | (TP for LTM BL CR for TS 38.473) | other | LG Electronics Inc. | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-234368 | Further discussion on LTM | discussion | NTT DOCOMO INC.. | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-234446 | (TP to TS 38.401) L1/L2 based Inter-Cell Mobility | other | CMCC | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-234447 | Discussion on L1L2 based Inter-Cell Mobility | discussion | CMCC | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-234459 | (TP for LTM BL CR to TS 38.473) Discussion on L1L2 triggered mobility | other | ZTE | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-234460 | TP for LTM BL CR to TS 38.401 |
other revised to R3-234709 |
ZTE | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-234574 | CB:#MobilityEhn_L1L2Mobility | other | Huawei |
R3-121 AI: 14.2 |
noted | [WTS] [JSN] | |||
| R3-234642 | (TP for L1L2Mob BLCR for TS 38.401): Inter-DU LTM procedure update |
other revision of R3-234074 revised to R3-234758 |
Huawei, Nokia, Nokia Shanghai Bell, ZTE, LG Electronics, Ericsson |
R3-121 AI: 14.2 |
revised | [WTS] [JSN] | |||
| R3-234661 | (TP to TS 38.473 on LTM) co-existence between LTM and L3 mobility |
other revision of R3-233870 revised to R3-234759 |
NEC, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, LG Electronics, ZTE, Google | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-234690 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
other revision of R3-233906 revised to R3-234760 |
Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Lenovo, LG Electronics | NR_Mob_enh2 | Rel-18 |
R3-121 AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-234709 | TP for LTM BL CR to TS 38.401 |
other revision of R3-234460 revised to R3-234757 |
ZTE, Nokia, Nokia Shanghai Bell, LG Electronics, Huawei, Ericsson | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-234757 | TP for LTM BL CR to TS 38.401 |
other revision of R3-234709 |
ZTE, Nokia, Nokia Shanghai Bell, LG Electronics, Huawei, Ericsson, CMCC | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
agreed | [WTS] [JSN] | |
| R3-234758 | (TP for L1L2Mob BLCR for TS 38.401): Inter-DU LTM procedure update |
other revision of R3-234642 |
Huawei, Nokia, Nokia Shanghai Bell, ZTE, LG Electronics, Ericsson, CMCC | NR_Mob_enh2-Core |
R3-121 AI: 14.2 |
agreed | [WTS] [JSN] | ||
| R3-234759 | (TP to TS 38.473 on LTM) co-existence between LTM and L3 mobility |
other revision of R3-234661 |
NEC, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, LG Electronics, ZTE, Google, Samsung, CMCC | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
agreed | [WTS] [JSN] | |
| R3-234760 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
other revision of R3-234690 |
Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Lenovo, LG Electronics, CMCC | NR_Mob_enh2-Core | Rel-18 |
R3-121 AI: 14.2 |
agreed | [WTS] [JSN] | |
| R3-235008 | LS on L1 measurement and TA management for LTM |
LS in source LS: R1-2308625 LS To: RAN2, RAN3, RAN4 |
RAN1(Fujitsu, Mediatek) | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235014 | Reply LS to R3-230889 on Approaches during execution for inter-DU LTM |
LS in LS is reply to R2-2302458 source LS: R2-2309251 LS To: RAN3 |
RAN2(Ericsson) | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235016 | LS on RAN2 progress on LTM |
LS in source LS: R2-2309288 LS To: RAN1 |
RAN2(Huawei) | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235019 | Reply LS on beam application time and UE based TA measurement for LTM |
LS in LS is reply to R1-2306259 source LS: R4-2314455 LS To: RAN1 |
RAN4(Ericsson) | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235040 | (TP to BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures | other | Nokia, Nokia Shanghai Bell | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235041 | (TPs to BL CRs for TS 38.473 and TS 38.423) On Reference Configuration and SCG Release for L1/2 Triggered Mobility (LTM) | other | Nokia, Nokia Shanghai Bell | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235135 | Discussion about candidate cell RS configuration | discussion | CATT | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235136 | (TP for 38.473 BLCR) Left issues remaining in LTM | other | CATT | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235164 | Discussion on L1 measurement reporting configuration in Inter-DU LTM | discussion | LG Electronics Inc. | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235177 | (TP to Mob_enh2 BL CR TS 38.473) Discussion on L1/L2 based Inter-cell Mobility | other | Samsung | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235247 | Discussion on L1L2 based inter-cell mobility | discussion | Lenovo | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235248 | (TPs to TS 38.401 BLCR & TS 38.470) Support of L1/L2 based inter-cell mobility | other | Lenovo | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235264 | Signalling Support for LTM | discussion | Qualcomm Incorporated | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235266 | (TP for LTM BL CR to TS 38.401) Solutions for LTM | other | Ericsson | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235267 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
other revised to R3-235894 |
Ericsson | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-235283 | (TP to TS38.473 on LTM) Rel-18 LTM Configuration ID and other | other | NEC | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235284 | (TP to TS38.401 on LTM) Informing of other candidate Cell(s) in other candidate gNB-DU(s) to candidate gNB-DU | other | NEC | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235341 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on LTM procedures |
other revised to R3-235827 |
Huawei | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-235342 | (TP for L1L2Mob BLCR for TS 38.473): LTM procedure design | other | Huawei | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235368 | Resource management at gNB-DU for LTM | discussion | Rakuten Symphony | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235370 | (TP for L1L2Mob BLCR for TS 38.401) Reference configuration and Target Configuration ID in LTM | other | Google Inc. | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235371 | (TP for L1L2Mob BLCR for TS 38.473) Reference configuration and Target Configuration ID in LTM | other | Google Inc. | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235372 | (TP for L1L2Mob BL CR for TS 38.473) UE Context identification after successful cell switch | other | Google Inc. | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235375 | (TP for LTM BL CR to TS 38.401) Discussion on L1L2 triggered mobility | other | ZTE | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235621 | Further discussion on LTM | discussion | NTT DOCOMO INC.. | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235642 | Discussion on L1L2 based Inter-Cell Mobility | discussion | CMCC | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235643 | (TP to TS 38.401) L1L2 based Inter-Cell Mobility | other | CMCC | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235691 | [DRAFT] Reply LS to R2-2309251 = R3-235014 on Approaches during execution for inter-DU LTM (to: RAN2; cc: -; contact: Ericsson) |
LS out LS is reply to R2-2309251 = R3-235014 LS To: RAN2 |
Ericsson | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
not pursued | [WTS] [JSN] | |
| R3-235764 | Summary of offline discussion MobilityEnh_LTM | report | Huawei | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-235827 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on LTM procedures |
other revision of R3-235341 revised to R3-235926 |
Huawei | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-235894 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM |
other revision of R3-235267 |
Ericsson | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
agreed | [WTS] [JSN] | |
| R3-235926 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on LTM procedures |
other revision of R3-235827 |
Huawei, Samsung | NR_Mob_enh2-Core | Rel-18 |
R3-121-bis AI: 14.2 |
agreed | [WTS] [JSN] |
70 documents (0.29548001289368 seconds)