[{"name":"R1-1707121","title":"Discussion on beam recovery mechanism","source":"ZTE","contact":"Ruyue Yu-Ngok Li","contact-id":43128,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-04-26 14:34:23","uploaded":"2017-05-08 08:27:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707121.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707245","title":"Beam recovery based on NR-PDCCH and NR-PDSCH","source":"vivo","contact":"Yu Ding","contact-id":67720,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-01 17:07:09","uploaded":"2017-05-06 15:27:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707245.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707255","title":"Discussion on beam failure recovery procedure","source":"Fujitsu","contact":"Tim Moulsley","contact-id":10954,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-01 20:58:25","uploaded":"2017-05-05 17:11:53","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707255.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707356","title":"Discussion for Mechanism to Recover from Beam Failure","source":"Intel Corporation","contact":"Seunghee Han","contact-id":47329,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-02 03:00:58","uploaded":"2017-05-07 04:41:43","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707356.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707477","title":"Discussion on DL beam recovery","source":"CATT","contact":"Teng Ma","contact-id":67340,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-02 03:19:22","uploaded":"2017-05-06 13:55:58","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707477.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707606","title":"Discussion on beam failure recovery","source":"LG Electronics","contact":"Youngwoo Yun","contact-id":45048,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-02 07:18:49","uploaded":"2017-05-06 07:08:39","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707606.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707698","title":"On Beam Recovery Mechanism","source":"Guangdong OPPO Mobile Telecom.","contact":"Jia Shen","contact-id":67727,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-03 02:43:22","uploaded":"2017-05-06 12:47:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707698.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707751","title":"Design principles of beam recovery mechanism","source":"AT&T","contact":"Arun Ghosh","contact-id":57084,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-03 03:26:40","uploaded":"2017-05-07 08:17:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707751.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707782","title":"Discussion on beam recovery","source":"Spreadtrum Communications","contact":"Arto Lehti","contact-id":61519,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-03 08:49:50","uploaded":"2017-05-05 18:04:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707782.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707814","title":"Low latency beam failure recovery by PRACH\/PRACH-like","source":"NEC","contact":"Wang Gang","contact-id":43643,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-04 01:27:47","uploaded":"2017-05-05 08:18:06","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"FS_NR_newRAT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707814.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707832","title":"Discussion on Beam Recovery Mechanism","source":"MediaTek Inc.","contact":"Tao Chen","contact-id":56050,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-04 01:40:59","uploaded":"2017-05-07 03:07:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707832.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1707954","title":"Discussion on beam recovery procedure","source":"Samsung","contact":"Younsun Kim","contact-id":43499,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-04 02:57:34","uploaded":"2017-05-06 12:38:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1707954.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708135","title":"Beam failure recovery","source":"Huawei, HiSilicon","contact":"Brian Classon","contact-id":45750,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-04 06:10:48","uploaded":"2017-05-06 12:38:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1708135.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708336","title":"Remaining Issues on Beam Recovery for NR","source":"InterDigital, Inc.","contact":"Shahrokh Nayeb Nazar","contact-id":72080,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-05 00:07:45","uploaded":"2017-05-06 12:27:58","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1708336.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708369","title":"Discussion on mechanisms for beam failure recovery","source":"Sharp","contact":"Toshizo Nogami","contact-id":60264,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-05 01:13:12","uploaded":"2017-05-05 18:32:48","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1708369.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708380","title":"Discussion on beam failure recovery","source":"CHTTL","contact":"Chih Hsuan Chen","contact-id":57648,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-05 01:30:40","uploaded":"2017-05-06 11:28:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1708380.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708452","title":"Further views on mechanism to recover from beam failure","source":"NTT DOCOMO, INC.","contact":"Hiroki Harada","contact-id":47533,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-05 01:58:54","uploaded":"2017-05-05 08:00:39","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1708452.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708587","title":"Beam recovery procedures","source":"Qualcomm Incorporated","contact":"Peter Gaal","contact-id":57198,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2017-05-05 05:33:25","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708678","title":"Beam failure recovery mechanism","source":"Ericsson","contact":"Stephen Grant","contact-id":65572,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-05 06:14:57","uploaded":"2017-05-06 17:06:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1708678.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708874","title":"Discussion on beam failure recovery mechanism","source":"Institute for Information Industry (III)","contact":"Hai-Han Wang","contact-id":63209,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-05 10:12:45","uploaded":"2017-05-05 10:23:08","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1708874.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1708905","title":"Beam Recovery in NR","source":"Nokia, Alcatel-Lucent Shanghai Bell","contact":"Mihai Enescu","contact-id":68296,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-05 10:52:44","uploaded":"2017-05-06 17:27:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1708905.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1709127","title":"Discussion on beam failure recovery mechanism","source":"Institute for Information Industry (III)","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2017-05-08 08:59:18","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1709309","title":"WF on beam recovery","source":"ZTE, MediaTek, vivo, Spreadtrum, Qualcomm, ASTRI, AT&T,  OPPO, Ericsson, LGE, Xinwei","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-16 00:24:07","uploaded":"2017-05-18 00:32:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1709309.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1709498","title":"WF on handling beam failure recovery for unexpected cases","source":"Vivo, Qualcomm","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2017-05-16 23:28:31","uploaded":"2017-05-17 00:33:32","revisionof":"","revisedto":"R1-1709639","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1709498.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1709606","title":"Summary from offline for beam recovery mechanism","source":"MediaTek Inc.","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-18 00:20:07","uploaded":"2017-05-18 00:27:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1709606.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1709613","title":"WF on information carried by beam failure recovery request","source":"LG Electronics, ZTE","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-05-18 00:20:12","uploaded":"2017-05-18 00:27:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1709613.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1709639","title":"WF on handling beam failure recovery for unexpected cases","source":"Vivo, Qualcomm, KT Corp., Ericsson","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":157,"ainumber":"7.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-05-18 00:20:28","uploaded":"2017-05-18 00:22:43","revisionof":"R1-1709498","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_89\/Docs\/R1-1709639.zip","group":"R1","meeting":"R1-89","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]