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 |
|---|---|---|---|---|---|---|---|---|---|
| R1-2501716 | Enhancements for UE-initiated/event-driven beam management | discussion | FUTUREWEI | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2501742 | On Specifications of Rel-19 UE/Event-Driven Beam Management | discussion | InterDigital, Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2501780 | Discussion on enhancements for UE-initiated/event-driven beam management | discussion | ZTE Corporation, Sanechips | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2501799 | Remaining issues on UE-initiated/event-driven beam management | discussion | vivo | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2501850 | Enhancements for UE-initiated/event-driven beam management | discussion | MediaTek Inc. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2501862 | Discussion on UE-initiated/event-driven beam management | discussion | Spreadtrum, UNISOC | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2501985 | On enhancements for UE-initiated/event-driven beam management | discussion | CATT | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502038 | On UE-initiated/event-driven beam management | discussion | Ofinno | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502053 | Remaining issues for UE-initiated beam management | discussion | Ericsson | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502065 | Discussions on UEIBM | discussion | China Telecom | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502079 | Discussion on enhancements for UE-initiated or event-driven beam management | discussion | NEC | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502103 | UE-initiated beam management | discussion | LG Electronics | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502107 | Enhancements for UE-initiated/event-driven beam management | discussion | Lenovo | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502119 | Discussion on enhancements for UE-initiated/event-driven beam management | discussion | Fujitsu | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502153 | Discussion on enhancements for UE-initiated/event-driven beam management | discussion | CMCC | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502224 | On UE initiated/event-driven beam management | discussion | Huawei, HiSilicon | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502293 | Discussions on UE-initiated/event-driven beam management | discussion | OPPO | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502312 | Enhancements for UE-initiated/event-driven beam management | discussion | Sony | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502356 | Views on Rel-19 UE-initiated/event-driven beam management | discussion | Samsung | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502414 | Discussion on enhancements for UE-initiated/event-driven beam management | discussion | Ruijie Networks Co. Ltd | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502434 | Discussion on enhancements for UE-initiated/event-driven beam management | discussion | Xiaomi | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502505 | Enhancements for UE-initiated/event-driven beam management | discussion | ETRI | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502524 | Enhancements to facilitate UE-initiated/event-driven beam management | discussion | Nokia | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502538 | Enhancements for UE-initiated/event-driven beam management | discussion | Transsion Holdings | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502545 | Discussion on UE-initiated/event-driven beam management | discussion | TCL | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502598 | Remaining issues for UE-initiated beam management | discussion | Apple | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502665 | Enhancements for UE-initiated/event-driven beam management | discussion | Sharp | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502687 | Discussion on the UE-initiated/event-driven beam management | discussion | HONOR | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502744 | Offline summary for Rel-19 MIMO UEIBM (9.2.1) pre-RAN1#120b | discussion | Moderator (ZTE) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502745 | Moderator Summary #1 on UE-initiated/event-driven beam management | discussion | Moderator (ZTE) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
noted | [WTS] [JSN] | |
| R1-2502746 | Moderator Summary #2 on UE-initiated/event-driven beam management | discussion | Moderator (ZTE) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
noted | [WTS] [JSN] | |
| R1-2502747 | Moderator Summary #3 on UE-initiated/event-driven beam management | discussion | Moderator (ZTE) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
noted | [WTS] [JSN] | |
| R1-2502759 | Discussion on enhancements for UE-initiated/event-driven beam management | discussion | NTT DOCOMO, INC. | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502793 | Discussion on UE-initiated/event-driven beam management | discussion | ITRI | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502812 | Enhancements for UE-initiated/event-driven beam management | discussion | Panasonic | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502833 | UE-initiated/event-driven beam management | discussion | Qualcomm Incorporated | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502877 | Discussion on UE initiated beam report | discussion | ASUSTeK | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2502888 | Discussion on enhancements for UE-initiated or event-driven beam management | discussion | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | ||
| R1-2502897 | Discussions on enhancements for UE-initiated/event-driven beam management | discussion | KDDI Corporation (TTC) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
not treated | [WTS] [JSN] | |
| R1-2503092 | Moderator Summary #4 on UE-initiated/event-driven beam management | discussion | Moderator (ZTE) | NR_MIMO_Ph5-Core | Rel-19 |
R1-120-bis AI: 9.2.1 |
noted | [WTS] [JSN] |
40 documents (0.36063098907471 seconds)