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-237140 | LS on CSI resource configuration and on early RACH for LTM |
LS in source LS: R2-2311332 LS To: RAN3 |
RAN2(Huawei) | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237147 | Reply LS on beam application time for LTM |
LS in LS is reply to R1-2306259 source LS: R4-2317331 LS To: RAN1, RAN2 |
RAN4(Ericsson) | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237163 | TP (BL CR TS 38.401) LTM RS Configuration and Signaling | other | Nokia, Nokia Shanghai Bell | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237164 | TP (BL CR TS 38.473) On remaining Stage 3 issues for L1/2 Triggered Mobility (LTM) | other | Nokia, Nokia Shanghai Bell | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237170 | (TP to BLCR for TS 38.423) Left issues remaining in LTM |
other revised to R3-238005 |
CATT | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
revised | [WTS] [JSN] | ||
| R3-237171 | TP to BLCR for TS 38.473 on LTM | other | CATT | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-237182 | (TP to Mob_enh2 BL CR TS38.401&TS38.473) Discussion on L1/L2 based Inter-cell Mobility | other | Samsung | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237208 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on LTM procedures |
other revised to R3-238018 |
Huawei | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
revised | [WTS] [JSN] | ||
| R3-237209 | (TP for L1L2Mob BLCR for TS 38.473): LTM procedure design | other | Huawei | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-237212 | Remaining issues on TA management for LTM | discussion | Fujitsu | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237234 | (TP to TS38.473 on LTM) Rel-18 LTM Configuration ID, RS Configuration and other | other | NEC | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237235 | (TP to TS38.401 on LTM) Updating the serving gNB-DU of other candidate Cell(s) in other candidate gNB-DU(s) | other | NEC | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237236 | One or two procedures, consider general Class 2 procedure for information transfer in F1AP | discussion | NEC | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237284 | Further discussion on LTM | discussion | NTT DOCOMO INC.. | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237286 | Signalling Support for LTM | discussion | Qualcomm Incorporated | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237316 | (TP for LTM BL CR to TS 38.401) Solutions for LTM | other | Ericsson | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237317 | (TP for LTM BL CR to TS 38.473) Solutions for LTM |
other revised to R3-237980 |
Ericsson | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-237415 | Discussion on L1L2 based inter-cell mobility | discussion | Lenovo | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-237416 | (TPs to BLCR for TS 38.401 & TS 38.470) Support of L1/L2 based inter-cell mobility | other | Lenovo | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-237466 | (TP for L1L2Mob BLCR for TS 38.473) Reference configuration and Target Configuration ID in LTM | other | Google Inc. | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-237467 | (TP for L1L2Mob BLCR for TS 38.401) Resolving FFS in LTM execution | other | Google Inc. | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-237468 | (TP for L1L2Mob BL CR for TS 38.473) UE Context identification after successful cell switch | other | Google Inc. | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | ||
| R3-237620 | (TP for LTM BL CR to TS 38.401/38.423/38.473) Discussion on L1L2 triggered mobility | other | ZTE | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237621 | TP for LTM BL CR to TS 38.470 |
other revised to R3-237981 |
ZTE, Huawei, CMCC, China Telecom, China Unicom, CATT | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
revised | [WTS] [JSN] | |
| R3-237645 | Almost complete discussions on LTM (TPs for TS 38.473 and TS 38.401) | discussion | LG Electronics Inc. | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237675 | Discussion on L1L2 based Inter-Cell Mobility | discussion | CMCC | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |
| R3-237819 | CB:#Mobility_LTM | other | Huawei |
R3-122 AI: 14.2 |
noted | [WTS] [JSN] | |||
| R3-237980 | (TP for LTM BL CR to TS 38.473) Solutions for LTM |
other revision of R3-237317 |
Ericsson, Google, ZTE, CATT, NEC, Nokia, Nokia Shanghai Bell, Huawei, Samsung, LG Electronics Inc. | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
agreed | [WTS] [JSN] | |
| R3-237981 | TP for LTM BL CR to TS 38.470 |
other revision of R3-237621 |
ZTE, Huawei, CMCC, China Telecom, China Unicom, CATT, Nokia, Nokia Shanghai Bell, NEC, Google, LG Electronics, Ericsson | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
agreed | [WTS] [JSN] | |
| R3-238005 | (TP to BLCR for TS 38.423) Left issues remaining in LTM |
other revision of R3-237170 revised to R3-238060 |
CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, CMCC, LG Electronics | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
revised | [WTS] [JSN] | ||
| R3-238018 | (TP for L1L2Mob BLCR for TS 38.401): LTM procedure update |
other revision of R3-237208 revised to R3-238059 |
Huawei | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
revised | [WTS] [JSN] | ||
| R3-238059 | (TP for L1L2Mob BLCR for TS 38.401): LTM procedure update |
other revision of R3-238018 |
Huawei, Nokia, Nokia Shanghai Bell, NEC, Google, ZTE, Samsung, CATT, Ericsson, LG Electronics, Qualcomm Incorporated | NR_Mob_enh2-Core |
R3-122 AI: 14.2 |
agreed | [WTS] [JSN] | ||
| R3-238060 | (BLCR to 38.423) for LTM |
CR revision of R3-238005 revised to R3-238154 |
CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, CMCC, LG Electronics, Huawei, NEC | 38.423 17.6.0 CR#1113 catB | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
revised | [WTS] [JSN] |
| R3-238091 | Introduction of LTM | CR | CMCC, ZTE, Huawei, China Telecom, China Unicom, CATT, Nokia, Nokia Shanghai Bell, NEC, Google, LG Electronics, Ericsson, Lenovo | 38.47 17.6.0 CR#123 catB | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
agreed | [WTS] [JSN] |
| R3-238092 | (BL CR to TS 38.473) Solutions for LTM | CR | Ericsson, Google, ZTE, CATT, NEC, Nokia, Nokia Shanghai Bell, Huawei, Samsung, LG Electronics Inc. | 38.473 17.6.0 CR#1249 catB | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
withdrawn | [WTS] [JSN] |
| R3-238154 | (CR to 38.423) Introduction of L1/L2 triggered mobility |
CR revision of R3-238060 |
CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, CMCC, LG Electronics, Huawei, NEC, Lenovo | 38.423 17.6.0 CR#11131 catB | NR_Mob_enh2-Core | Rel-18 |
R3-122 AI: 14.2 |
agreed | [WTS] [JSN] |
36 documents (0.30237793922424 seconds)