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-2400165 | Tolerable key stream re-use | discussion | Xiaomi | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400184 | Coexistence of LTM with other features | discussion | Xiaomi | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400197 | Handling keystream reuse at recovery | discussion | Samsung Electronics Co., Ltd | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400209 | Discussion on key stream reuse during LTM fast recovery | discussion | Transsion Holdings | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2400221 | [B100] SCG LTM with fast MCG link recovery | discussion | Lenovo, Samsung | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2400222 | UE measured TA and No L2 reset in coexistence case of L3 handover and LTM | discussion | Lenovo | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2400275 | Issue on the association between CSI-RS and SSB of the LTM candidate cell | discussion | CATT | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400311 | Discussion on coexistence of LTM and other features | discussion | ZTE Corporation, Sanechips | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400312 | Consideration on remaining issues for LTM | discussion | ZTE Corporation, Sanechips | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400356 | RRC signaling related TCI state configurations | discussion | Panasonic |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |||
| R2-2400391 | [FeMob][Issue 4] Handling of key stream re-used in case of fast LTM recovery | discussion | Intel Corporation | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400441 | Coexistence of LTM and other features | discussion | vivo | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400442 | Discussion on the key stream reuse issue for LTM | discussion | vivo | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400443 | Discussion on the impact of s-Measure on L1 measurement | discussion | vivo | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400444 | [V121][V122]Unknown target configuration ID in LTM cell switch command | discussion | vivo | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400468 | Discussion on LTM remaining issues | discussion | LG Electronics | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400492 | Discussion on remaining issues for LTM | discussion | Samsung |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |||
| R2-2400496 | Analysis of Keystream reuse issue | discussion | Lenovo, Motorola Mobility | NR_Mob_enh2-Core |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2400509 | Remaining issue for LTM | discussion | NTTDOCOMO, INC. | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2400574 | Discussion on coexistence of LTM with other features | discussion | China Telecom | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400603 | Discussion on security issue of LTM | discussion | NEC | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400668 | On Reference Configuration in Rel-18 LTM | discussion | Nokia, Nokia Shanghai Bell | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400795 | Views on fast cell recovery during LTM failures | discussion | Panasonic | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | ||
| R2-2400796 | PDCP keystream handling for LTM fast recovery | discussion | Panasonic | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2400806 | On the interworking of LTM with L3 Mobility and Dual Connectivity | discussion | Nokia, Nokia Shanghai Bell | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400807 | On the cell switch aspects in LTM | discussion | Nokia, Nokia Shanghai Bell | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400812 | RRC Remaining issues on LTM | discussion | Huawei, HiSilicon | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400814 | Reply LS on n-TimingAdvanceOffset for PDCCH order RACH |
LS out LS is reply to R2-2400051 LS To: RAN1 |
Huawei, HiSilicon | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400815 | Early RACH for inter-DU LTM | discussion | Huawei, HiSilicon | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400816 | [H018][H035] LTM configuration | discussion | Huawei, HiSilicon | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400817 | [H020] SRB L2 behaviour | discussion | Huawei, HiSilicon | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2400835 | Coexistence of LTM and other features | discussion | Interdigital, Inc. | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400839 | Security issues during LTM failure recovery | discussion | Interdigital, Inc. | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400840 | Draft LS on Key Stream Reuse during fast LTM recovery |
LS out LS To: SA3 |
Interdigital, Inc. | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2400872 | Solutions for keystream reuse issue caused by fast LTM recovery | discussion | Fujitsu | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2400956 | Coexistence of LTM and Other Mobility Procedures and Features | discussion | MediaTek Inc. | NR_Mob_enh2 | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2401054 | Coexistence of LTM and other features | discussion | Sharp | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
postponed | [WTS] [JSN] | |
| R2-2401062 | Considerations on LTM related open issues | discussion | Fujitsu | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2401063 | [F015] Default value of n-TimingAdvanceOffset in IE EarlyUL-SyncConfig | discussion | Fujitsu | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2401123 | Keystream Reuse Issue in LTM Fast Recovery | discussion | MediaTek Inc. | NR_Mob_enh2 | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2401179 | Discussion on fast recovery and co-existence with other features | discussion | Qualcomm Incorporated |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |||
| R2-2401242 | Correction on 38.331 for LTM | CR | Langbo | 38.331 18.0.0 CR#4592 catF | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] |
| R2-2401284 | Discussion on keystream reuse issue at LTM fast recovery | discussion | NTT DOCOMO, INC. | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | ||
| R2-2401364 | Discussion on LTM candidate ID value range and related issue (G001) | discussion | Google Inc. | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | ||
| R2-2401379 | Co-existence of LTM with other features | discussion | Ericsson | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2401383 | Clarify presence of securityConfig in case of LTM [E068] | draftCR | Ericsson | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2401384 | Corrections on UE-based TA measurements [C113, Z051, B105, B202, C114, M002, B106, L005, Z030, C116, A702, Z059] | draftCR | Ericsson | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2401468 | Discussion on RRC issues of LTM | discussion | OPPO | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
available | [WTS] [JSN] | |
| R2-2401471 | Discussion on cross-feature issues for LTM | discussion | OPPO | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] | |
| R2-2401926 | Summary of [AT125][510][feMob] LTM RRC issues | discussion | Ericsson | NR_Mob_enh2-Core | Rel-18 |
R2-125 AI: 7.4.1.3.1 |
noted | [WTS] [JSN] |
50 documents (0.36177802085876 seconds)