[{"name":"R1-1709907","title":"Discussion on Beam Failure Recovery","source":"Beijing Xinwei Telecom Techn.","contact":"Peng Sun","contact-id":62183,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-08 13:20:33","uploaded":"2017-06-16 09:52:56","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_AH\/NR_AH_1706\/Docs\/R1-1709907.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1709929","title":"General views on beam failure recovery","source":"Huawei, HiSilicon","contact":"Brian Classon","contact-id":45750,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-08 13:23:32","uploaded":"2017-06-17 02:58: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_AH\/NR_AH_1706\/Docs\/R1-1709929.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710058","title":"Consideration on DL beam failure and recovery","source":"CATT","contact":"Yanping Xing","contact-id":57090,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-09 04:09:14","uploaded":"2017-06-17 03:10:43","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_AH\/NR_AH_1706\/Docs\/R1-1710058.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710144","title":"On Beam Recovery Mechanism","source":"Guangdong OPPO Mobile Telecom.","contact":"Jia Shen","contact-id":67727,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-11 13:52:19","uploaded":"2017-06-16 10:20: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_AH\/NR_AH_1706\/Docs\/R1-1710144.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710185","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":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-12 04:53:26","uploaded":"2017-06-17 06:03:44","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_AH\/NR_AH_1706\/Docs\/R1-1710185.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710236","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":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-13 16:37:38","uploaded":"2017-06-16 16:40:56","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_AH\/NR_AH_1706\/Docs\/R1-1710236.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710251","title":"Discussion on beam failure recovery request","source":"NEC Corporation","contact":"Yukai Gao","contact-id":62939,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-14 03:06:12","uploaded":"2017-06-16 08:51:56","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_AH\/NR_AH_1706\/Docs\/R1-1710251.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710283","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":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-06-14 07:52:45","uploaded":"2017-06-17 05:32:05","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_AH\/NR_AH_1706\/Docs\/R1-1710283.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710364","title":"Discussion on beam failure recovery","source":"Spreadtrum Communications","contact":"Arto Lehti","contact-id":61519,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-14 09:08:41","uploaded":"2017-06-16 10:31:11","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_AH\/NR_AH_1706\/Docs\/R1-1710364.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710400","title":"Beam failure recovery procedure","source":"vivo","contact":"Yu Ding","contact-id":67720,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-14 12:28:06","uploaded":"2017-06-17 06:44:33","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_AH\/NR_AH_1706\/Docs\/R1-1710400.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710431","title":"Considerations on beam failure recovery mechanism","source":"AT&T","contact":"Milap Majmundar","contact-id":70953,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-14 18:45:45","uploaded":"2017-06-17 03:18:23","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_AH\/NR_AH_1706\/Docs\/R1-1710431.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710527","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":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-06-15 00:22:53","uploaded":"2017-06-17 06:19:31","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_AH\/NR_AH_1706\/Docs\/R1-1710527.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710596","title":"Discussion of beam recovery procedure","source":"Lenovo, Motorola Mobility","contact":"Chenxi Zhu","contact-id":64707,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-15 02:53:57","uploaded":"2017-06-16 18:49:37","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_AH\/NR_AH_1706\/Docs\/R1-1710596.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710655","title":"Beam failure recovery","source":"Samsung","contact":"Younsun Kim","contact-id":43499,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-15 08:06:47","uploaded":"2017-06-17 01:50:10","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_AH\/NR_AH_1706\/Docs\/R1-1710655.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710810","title":"Mechanism for flexible beam failure recovery","source":"MediaTek Inc.","contact":"Tao Chen","contact-id":56050,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-06-15 10:24:15","uploaded":"2017-06-17 05:19:18","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_AH\/NR_AH_1706\/Docs\/R1-1710810.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1710926","title":"On Remaining Details of Beam Failure Recovery","source":"InterDigital, Inc.","contact":"Shahrokh Nayeb Nazar","contact-id":72080,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-16 00:26:35","uploaded":"2017-06-16 23:51:11","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_AH\/NR_AH_1706\/Docs\/R1-1710926.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711017","title":"Mechanism to recover from beam failure","source":"Ericsson","contact":"Stephen Grant","contact-id":65572,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-16 03:22:19","uploaded":"2017-06-17 05:29:06","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_AH\/NR_AH_1706\/Docs\/R1-1711017.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711076","title":"Further views on mechanism to recover from beam failure","source":"NTT DOCOMO, INC.","contact":"Kazuaki Takeda","contact-id":43136,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-06-16 03:35:04","uploaded":"2017-06-17 05:25:40","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_AH\/NR_AH_1706\/Docs\/R1-1711076.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711161","title":"Beam recovery procedures","source":"Qualcomm Incorporated","contact":"Peter Gaal","contact-id":57198,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-16 03:51:27","uploaded":"2017-06-17 05:16:31","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_AH\/NR_AH_1706\/Docs\/R1-1711161.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711234","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":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-16 03:52:44","uploaded":"2017-06-17 01:26: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_AH\/NR_AH_1706\/Docs\/R1-1711234.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711291","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":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-06-16 07:40:21","uploaded":"2017-06-16 21:15: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_AH\/NR_AH_1706\/Docs\/R1-1711291.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711717","title":"WF on using SS block for beam recovery","source":"ZTE, Ericsson, NTT DOCOMO, MediaTek, Spreadtrum, vivo, OPPO, Qualcomm, Xinwei, LG Electronics, AT&T, Lenovo, CMCC, China Unicom, China Telecom, ASTRI, Samsung, Nokia, ASB, III, MTI, Sharp, National Instruments","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-06-27 15:10:27","uploaded":"2017-07-01 00:57:51","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_AH\/NR_AH_1706\/Docs\/R1-1711717.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711858","title":"WF on beam failure recovery request","source":"LG Electronics, Intel, Huawei, HiSilcon, vivo","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-29 12:30:10","uploaded":"2017-06-29 12:37:51","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_AH\/NR_AH_1706\/Docs\/R1-1711858.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711897","title":"Offline discussion summary on beam recovery","source":"MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-06-29 12:30:13","uploaded":"2017-07-01 00:57:51","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_AH\/NR_AH_1706\/Docs\/R1-1711897.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711927","title":"WF on gNB response for beam failure request","source":"Huawei, HiSilicon, LG Electronics, Intel","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-29 12:30:14","uploaded":"2017-07-01 00:57:51","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_AH\/NR_AH_1706\/Docs\/R1-1711927.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1711928","title":"WF on PRACH for beam failure recovery request transmission","source":"Huawei, HiSilicon, LG Electronics, Ericsson, CATT, NTT DOCOMO","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":42,"ainumber":"5.1.2.2.2","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-06-29 12:30:14","uploaded":"2017-07-01 00:57:51","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_AH\/NR_AH_1706\/Docs\/R1-1711928.zip","group":"R1","meeting":"R1-ah-18512","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]