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-255011 | LS on RAN2 agreements for SP CSI-RS activation/deactivation |
LS in source LS: R2-2504727 LS To: RAN3 |
RAN2(CATT) | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-255027 | Reply LS on security handling for inter-CU LTM in non-DC cases |
LS in source LS: S3-252398 LS To: RAN3 |
SA3(Huawei) | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-255138 | TP (BL CR TS 38.300, TS 38.473, TS 38.423) Remaining issues on Inter-CU LTM procedure |
other revised to R3-255857 |
Nokia | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-255139 | Discussion on Inter-CU LTM with Dual Connectivity | discussion | Nokia | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255149 | (TP to 38.423, 38.473) Inter-CU LTM | other | ZTE Corporation | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255150 | (TP to BL CR for TS 38.300, 38.473, 38.423) Rel-19 Set ID assignment | other | ZTE Corporation | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255197 | (TP to BL CR for TS 38.423 and 38.473 on Inter-CU LTM) Remaining Rel-19 inter-CU LTM issues | other | NEC | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255198 | (TP to BL CR for TS 38.423 and 37.340 on Inter-CU LTM with DC) Remaining issues of Rel-19 inter-CU LTM in DC scenario | other | NEC | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255268 | Completion of Inter-CU LTM | discussion | Ericsson | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255269 | (TP for LTM BL CR for TS 38.423, TS 38.473, TS 38.300, TS 38.401) – Support for inter-CU LTM |
other revised to R3-255842 |
Ericsson | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-255281 | Remaining Issues on Data Forwarding for SN initiated Inter-SN LTM | discussion | Ofinno, LLC | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255282 | (TP for TS 38.423) Cell Switch Notification for LTM DC Scenario | other | Ofinno, LLC | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255283 | Open Issues on Access Success for Inter-SN SCG LTM | discussion | Ofinno, LLC | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255301 | Signalling enhancements for Inter-CU LTM handover | discussion | Qualcomm India Pvt Ltd | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255374 | (TP for TS38.401) On support of inter-CU LTM |
other revised to R3-255871 |
China Telecom | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-255375 | Discussion on inter-CU LTM in DC scenario | discussion | China Telecom | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255403 | [TP to BLCR for TS 38.401] Inter-CU LTM | other | Lenovo | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255404 | [TP to BLCR for TS 38.423] Inter-CU LTM in DC | other | Lenovo | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255405 | [TP to BLCR for TS 38.423] Inter-CU LTM in DC - text update | other | Lenovo | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255418 | (TP to BL CR 38.423) Clarification on inter-CU LTM and LTM with SCG in NR-DC | other | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | ||
| R3-255419 | (TP to BL CR 37.340 and 38.473) Clarification on inter-CU LTM and LTM with SCG in NR-DCs | other | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | ||
| R3-255421 | Discussion on inter-CU LTM | discussion | NTT DOCOMO INC.. | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255424 | (TP for LTM BLCR for TS38.300): Inter-CU LTM | other | Huawei | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255425 | (TP for LTM BLCR for TS38.473):Inter-CU LTM |
other revised to R3-255835 |
Huawei | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-255426 | [DRAFT] Reply LS on security handling for inter-CU LTM in non-DC cases |
LS out LS is reply to S3-252398 LS To: SA3 |
Huawei | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255440 | (TP for LTM CR for TS38.423): LTM Resource Lifecycle Management in inter-CU LTM | other | Jio Platforms | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255532 | PRACH resources for RACH-less LTM | discussion | Ericsson, Jio Platforms, Lenovo, NTT DoCoMo | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255533 | (TP to BL CR for TS 38.423) – PRACH Resources for RACH-less LTM | other | Ericsson, Jio Platforms, Lenovo, NTT DoCoMo | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255534 | (TP to BL CR for TS 38.473) – PRACH Resources for RACH-less LTM | other | Ericsson, Jio Platforms, Lenovo, NTT DoCoMo | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255550 | gNB-DU initiated LTM resource reconfiguration | discussion | Rakuten Mobile Inc, Qualcomm Inc, NTT DOCOMO INC | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255601 | Inter-CU LTM Robustness Enhancements | discussion | Jio Platforms | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255604 | Discussion for general issues in Inter-CU LTM | discussion | CATT | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255605 | (TP to BL CR for TS37.340) Discussion for Inter-CU LTM in DC |
other revised to R3-255904 |
CATT | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-255614 | Discussions on finalizing the essential aspects of Inter-CU LTM | discussion | LG Electronics Inc. | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255615 | (TP for NR_Mob_Ph4 TS 38.423) Inter-CU LTM | other | LG Electronics Inc. | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255625 | Fetching reference configuration from candidate gNB in inter-CU LTM | discussion | Huawei, Google, Nokia, Jio Platforms, CATT, CMCC, NTT Docomo, Lenovo, China Telecom, Samsung | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255626 | (TP for LTM BLCR for TS38.423): Fetching reference configuration from candidate gNB in inter-CU LTM | other | Huawei, Google, Nokia, Jio Platforms, CATT, CMCC, NTT Docomo, Lenovo, China Telecom, Samsung | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255627 | (TP for LTM BLCR for TS38.300): Fetching reference configuration from candidate gNB in inter-CU LTM | other | Huawei, Google, Nokia, Jio Platforms, CATT, CMCC, NTT Docomo, Lenovo, China Telecom, Samsung | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255628 | Clarification on the single UE XnAP association in inter-CU LTM | discussion | Huawei, NEC, LG Electronics | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255629 | (TP for LTM BLCR for TS38.300): Clarification on the single Xn UE association in inter-CU LTM | other | Huawei, NEC, LG Electronics | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255630 | (TP for LTM BLCR for TS38.423): Clarification on the single Xn UE association in inter-CU LTM | other | Huawei, NEC, LG Electronics | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255659 | (TP to BLCR for TS38.423 and TS38.473) Inter-gNB-CU LTM | other | Samsung | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255660 | Additional Discussion on inter-gNB-CU LTM | discussion | Samsung | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255724 | Support for Semi-persistent CSI-RS transmission | discussion | Ericsson, Jio Platforms, Verizon Wireless, ZTE, Ofinno | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255725 | (TP to BL CR for TS 38.423) Support for Semi-persistent CSI-RS transmission (Option 1) | other | Ericsson, Jio Platforms, Verizon Wireless, ZTE | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255726 | (TP to BL CR for TS 38.473) Support for Semi-persistent CSI-RS transmission (Option 1) | other | Ericsson, Jio Platforms, Verizon Wireless, ZTE | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255727 | (TP to BL CR for TS 38.423) Support for Semi-persistent CSI-RS transmission (Option 2) | other | Ericsson, Jio Platforms, Verizon Wireless, ZTE | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255728 | (TP to BL CR for TS 38.473) Support for Semi-persistent CSI-RS transmission (Option 2) | other | Ericsson, Jio Platforms, Verizon Wireless, ZTE | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
available | [WTS] [JSN] | |
| R3-255772 | Summary of offline discussion on inter-CU LTM | discussion | China Telecom | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-255781 | CB:#MobilityEnh_LTM | discussion | China Telecom | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-255782 | CB:#MobilityEnh_LTMNR-DC | discussion | Lenovo | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-255835 | (TP for LTM BLCR for TS38.473):Inter-CU LTM |
other revision of R3-255425 revised to R3-255962 |
Huawei | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-255842 | (TP for LTM BL CR for TS 38.423) - Support for inter-CU LTM |
other revision of R3-255269 revised to R3-255961 |
Ericsson | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-255857 | TP (BL CR TS 38.300) Remaining issues on Inter-CU LTM procedure |
other revision of R3-255138 |
Nokia, China Telecom, NEC, LG Electronics, CATT, Samsung, Huawei, Google, Ericsson, ZTE, Ofinno | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
agreed | [WTS] [JSN] | |
| R3-255871 | (TP for TS38.401) On support of inter-CU LTM |
other revision of R3-255374 |
China Telecom, Ericsson, Nokia, Google, LG Electronics, Samsung, CATT, ZTE, NEC, Qualcomm | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
agreed | [WTS] [JSN] | |
| R3-255903 | (TP to BLCR for TS 38.423) Inter-CU LTM in DC | other | LG Electronics Inc., Nokia, NEC, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, Ofinno, Jio Platforms (JPL) | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
agreed | [WTS] [JSN] | |
| R3-255904 | (TP for 37.340) Discussion for Inter-CU LTM in DC |
other revision of R3-255605 |
CATT, Google, China Telecom, Samsung, Nokia, NEC, ZTE, Ofinno, Ericsson, LG Electronics, Huawei | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
agreed | [WTS] [JSN] | |
| R3-255961 | (TP for LTM BL CR for TS 38.423) - Support for inter-CU LTM |
other revision of R3-255842 |
Ericsson, NEC, Nokia, ZTE, Lenovo, Samsung, Qualcomm, Verizon Wireless, Huawei, China Telecom, Ofinno, CATT, Google, LG Electronics | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
agreed | [WTS] [JSN] | |
| R3-255962 | (TP for LTM BLCR for TS 38.473):Inter-CU LTM |
other revision of R3-255835 |
Huawei, China Telecom, Google, Nokia, NEC, Ericsson, CATT, Samsung, ZTE, LG Electronics | NR_Mob_Ph4-Core | Rel-19 |
R3-129 AI: 13.2 |
agreed | [WTS] [JSN] | |
| R3-256528 | Discussion on ISAC Architecture and General Aspects | other | Xiaomi | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-256558 | Discussion on Network Architecture for ISAC |
other revised to R3-257294 |
ZTE Corporation | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-256586 | (TP for 38.765) Network architecture solution for gNB-based mono-static sensing | other | China Telecom | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-256676 | (TP for ISAC TR) Network architecture for ISAC | other | Huawei | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-256685 | Discussion on Network Architecture for NR ISAC | discussion | Tejas Network Limited | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
noted | [WTS] [JSN] | |
| R3-256771 | Discussion on network architecture for ISAC | discussion | CATT | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-256784 | The discussion on ISAC network architecture | discussion | NEC | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-256826 | Network Architecture and Protocol Aspects for NR Sensing Support | discussion | Qualcomm Incorporated | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-256854 | Discussion on Network Architecture for Sensing | discussion | CMCC | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-256895 | Discussion on architecture for ISAC | discussion | Nokia, Nokia Shanghai Bell | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-256914 | Discussion on ISAC network architecture | discussion | Lenovo | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-256922 | Discussion on Network Architecture for ISAC | discussion | Ericsson, Jio Platforms | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-256941 | Discussions on the framework of ISAC | discussion | China Unicom | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-256947 | Network architecture enhancements for NR ISAC | discussion | Hanbat National University | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-257111 | Discussion paper on ISAC network architecuture | discussion | CEWiT | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-257118 | NR ISAC Network Architecture | discussion | InterDigital, Inc. | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-257123 | Discussions for ISAC network architecture in RAN3 | discussion | LG Electronics Inc. | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-257144 | Discussion on network architecture for ISAC | discussion | Samsung | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
available | [WTS] [JSN] | |
| R3-257294 | TP to TR 38.765 for Network Architecture |
other revision of R3-256558 revised to R3-257325 |
ZTE Corporation | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
revised | [WTS] [JSN] | |
| R3-257325 | (TP to BL pCR to 38.765) Network Architecture |
other revision of R3-257294 |
ZTE Corporation, Huawei, Xiaomi, Nokia, Nokia Shanghai Bell, NEC, Ericsson, China Telecom, Samsung, LG Electronics, CATT, InterDigital | FS_Sensing_NR_bis | Rel-20 |
R3-129-bis AI: 13.2 |
agreed | [WTS] [JSN] |
79 documents (0.36073398590088 seconds)