[{"name":"R1-1719423","title":"Remaining details on beam failure recovery","source":"Huawei, HiSilicon","contact":"Xiao Weimin","contact-id":56706,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":94230,"status":"available","reservation_date":"2017-11-09 02:43:05","uploaded":"2017-11-18 01:57: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_91\/Docs\/R1-1719423.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719534","title":"Discussion on beam recovery","source":"ZTE, Sanechips","contact":"Ruyue Yu-Ngok Li","contact-id":43128,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":95340,"status":"available","reservation_date":"2017-11-13 03:12:58","uploaded":"2017-11-18 06:51:14","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_91\/Docs\/R1-1719534.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719566","title":"Further details on beam failure recovery","source":"MediaTek Inc.","contact":"Tao Chen","contact-id":56050,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":95660,"status":"revised","reservation_date":"2017-11-13 05:02:08","uploaded":"2017-11-18 06:53:20","revisionof":"","revisedto":"R1-1721056","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_91\/Docs\/R1-1719566.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719619","title":"Discussion on beam failure recovery","source":"Fujitsu","contact":"Tim Moulsley","contact-id":10954,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":96190,"status":"available","reservation_date":"2017-11-13 20:07:54","uploaded":"2017-11-17 14:52: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_91\/Docs\/R1-1719619.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719633","title":"Remaining details on mechanisms to recover from beam failure","source":"AT&T","contact":"Arun Ghosh","contact-id":57084,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":96330,"status":"available","reservation_date":"2017-11-14 00:23:06","uploaded":"2017-11-18 03:55:30","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_91\/Docs\/R1-1719633.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719695","title":"Remaining issues on UE initiated beam failure recovery","source":"Spreadtrum Communications","contact":"Arto Lehti","contact-id":61519,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":96950,"status":"available","reservation_date":"2017-11-14 08:05:22","uploaded":"2017-11-17 12:57:25","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_91\/Docs\/R1-1719695.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719735","title":"Discussion of beam failure recovery","source":"Lenovo, Motorola Mobility","contact":"Chenxi Zhu","contact-id":64707,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"Late contribution","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":97350,"status":"available","reservation_date":"2017-11-15 04:07:56","uploaded":"2017-11-19 12:45: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_91\/Docs\/R1-1719735.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719770","title":"Remaining details on mechanism to recover from beam failure","source":"vivo","contact":"Yu Ding","contact-id":67720,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":97700,"status":"available","reservation_date":"2017-11-15 06:47:12","uploaded":"2017-11-18 05:07:12","revisionof":"R1-1717473","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_91\/Docs\/R1-1719770.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719908","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":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":99080,"status":"available","reservation_date":"2017-11-15 10:33:02","uploaded":"2017-11-18 06:11:17","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_91\/Docs\/R1-1719908.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1719988","title":"Discussion on Beam Recovery Mechanism","source":"Guangdong OPPO Mobile Telecom","contact":"Zhihua SHI","contact-id":67442,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":99880,"status":"available","reservation_date":"2017-11-15 13:43:44","uploaded":"2017-11-18 02:17:11","revisionof":"R1-1718055","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_91\/Docs\/R1-1719988.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720072","title":"Remaining issues on beam failure recovery","source":"Intel Corporation","contact":"Seunghee Han","contact-id":47329,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":720,"status":"available","reservation_date":"2017-11-15 16:30:08","uploaded":"2017-11-18 07:17:40","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_91\/Docs\/R1-1720072.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720183","title":"Remaining issues on DL beam failure recovery","source":"CATT","contact":"Teng Ma","contact-id":67340,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":1830,"status":"available","reservation_date":"2017-11-16 03:33:30","uploaded":"2017-11-18 05:26:12","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_91\/Docs\/R1-1720183.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720291","title":"Beam failure recovery","source":"Samsung","contact":"Youngbum Kim","contact-id":39963,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":2910,"status":"available","reservation_date":"2017-11-16 08:28:13","uploaded":"2017-11-17 20:14:01","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_91\/Docs\/R1-1720291.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720567","title":"Remaining Issues for Beam Failure Recovery Procedure","source":"ASUSTEK COMPUTER (SHANGHAI)","contact":"Alex Liou","contact-id":65894,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":5670,"status":"available","reservation_date":"2017-11-17 02:05:45","uploaded":"2017-11-17 10:01:46","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_91\/Docs\/R1-1720567.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720574","title":"On partial beam failure recovery","source":"NEC","contact":"Wang Gang","contact-id":43643,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":5740,"status":"available","reservation_date":"2017-11-17 02:15:24","uploaded":"2017-11-17 08:00:57","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_91\/Docs\/R1-1720574.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720587","title":"Discontinuous beam recovery mechanism","source":"CMCC","contact":"Hui Tong","contact-id":58245,"tdoctype":"other","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":5870,"status":"available","reservation_date":"2017-11-17 02:21:59","uploaded":"2017-11-18 01:38: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_91\/Docs\/R1-1720587.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720613","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":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":6130,"status":"available","reservation_date":"2017-11-17 03:08:14","uploaded":"2017-11-18 02:47:16","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_91\/Docs\/R1-1720613.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720631","title":"Remaining issues on beam recovery","source":"InterDigital, Inc.","contact":"Shahrokh Nayeb Nazar","contact-id":72080,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":6310,"status":"available","reservation_date":"2017-11-17 04:09:23","uploaded":"2017-11-18 05:03:50","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_91\/Docs\/R1-1720631.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720663","title":"Beam recovery procedures","source":"Qualcomm Incorporated","contact":"Peter Gaal","contact-id":57198,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":6630,"status":"available","reservation_date":"2017-11-17 04:26:42","uploaded":"2017-11-18 06:29:03","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_91\/Docs\/R1-1720663.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720737","title":"Remaining details of beam recovery","source":"Ericsson","contact":"Stephen Grant","contact-id":65572,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":7370,"status":"available","reservation_date":"2017-11-17 04:37:31","uploaded":"2017-11-18 07:02: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_91\/Docs\/R1-1720737.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720804","title":"Remaining issues on beam recovery","source":"NTT DOCOMO, INC.","contact":"Kazuaki Takeda","contact-id":43136,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":8040,"status":"available","reservation_date":"2017-11-17 07:20:43","uploaded":"2017-11-18 05:24:13","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_91\/Docs\/R1-1720804.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1720891","title":"Beam Recovery in NR","source":"Nokia, Nokia Shanghai Bell","contact":"Mihai Enescu","contact-id":68296,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":8910,"status":"available","reservation_date":"2017-11-17 10:22:41","uploaded":"2017-11-18 05:34: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_91\/Docs\/R1-1720891.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721056","title":"Further details on beam failure recovery","source":"MediaTek Inc.","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":10560,"status":"available","reservation_date":"2017-11-21 14:00:28","uploaded":"2017-11-23 07:33:45","revisionof":"R1-1719566","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_91\/Docs\/R1-1721056.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721346","title":"LS to RAN2 on Beam Failure Recovery","source":"RAN1, MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"approved","reservation_date":"2017-12-07 09:32:51","uploaded":"2017-12-12 17:06:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_91\/Docs\/R1-1721346.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721494","title":"Summary for Remaining issues on Beam Failure Recovery","source":"MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":149400,"status":"noted","reservation_date":"2017-11-29 06:11:41","uploaded":"2017-11-29 06:11:41","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_91\/Docs\/R1-1721494.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721523","title":"WF on handling partial beam failure","source":"NTT DOCOMO, Samsung, MediaTek, AT&T, ZTE, Intel, Huawei","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":152300,"status":"available","reservation_date":"2017-12-01 02:09:43","uploaded":"2017-12-01 02:09: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_91\/Docs\/R1-1721523.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721549","title":"Offline Summary for Remaining issues on Beam Failure Recovery","source":"MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":154900,"status":"noted","reservation_date":"2017-11-30 02:44:31","uploaded":"2017-11-30 02:44: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_91\/Docs\/R1-1721549.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721615","title":"WF on new beam identification for beam failure recovery","source":"LG Electronics, InterDigital, Huawei, HiSilicon, AT&T","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":161500,"status":"noted","reservation_date":"2017-12-01 17:54:04","uploaded":"2017-12-01 17:54:04","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_91\/Docs\/R1-1721615.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721645","title":"Offline summary on remaining issues on Beam Failure Recovery","source":"MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":164500,"status":"noted","reservation_date":"2017-12-01 17:54:04","uploaded":"2017-12-01 17:54:04","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_91\/Docs\/R1-1721645.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721665","title":"WF for BFR Candidate Beam Selection","source":"Huawei, HiSilicon, Mediatek, LGE, Intel, NEC, Lenovo, Motorola Mobility, Spreadtrum, ATT, Fujitsu, Sharp, Ericsson","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":166500,"status":"revised","reservation_date":"2017-12-01 17:54:04","uploaded":"2017-12-01 17:54:04","revisionof":"","revisedto":"R1-1721670","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_91\/Docs\/R1-1721665.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721670","title":"WF for BFR Candidate Beam Selection","source":"Huawei, HiSilicon, Mediatek, LGE, Intel, NEC, Lenovo, Motorola Mobility, Spreadtrum, ATT, Fujitsu, Ericsson","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":166501,"status":"noted","reservation_date":"2017-12-01 17:54:04","uploaded":"2017-12-01 17:54:04","revisionof":"R1-1721665","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_91\/Docs\/R1-1721670.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721673","title":"WF for handling partial beam failure","source":"NTT DOCOMO, Intel, Huawei, NEC, Spreadtrum, MediaTek, China Telecom, AT&T","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":167300,"status":"noted","reservation_date":"2017-12-01 17:54:04","uploaded":"2017-12-01 17:54:04","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_91\/Docs\/R1-1721673.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721699","title":"Offline discussion summary on remaining issues on Beam Failure Recovery","source":"MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":169900,"status":"noted","reservation_date":"2017-12-02 15:48:24","uploaded":"2017-12-02 15:48:24","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_91\/Docs\/R1-1721699.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721700","title":"[DRAFT] LS to RAN2 on Beam Failure Recovery","source":"MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"LS out","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":170000,"status":"noted","reservation_date":"2017-12-02 15:48:24","uploaded":"2017-12-02 15:48:24","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_91\/Docs\/R1-1721700.zip","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1721710","title":"WF on beam recovery","source":"ZTE","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":112,"ainumber":"7.2.2.4","ainame":"Remaining details on mechanism to recover from beam failure","tdoc_agenda_sort_order":171000,"status":"withdrawn","reservation_date":"2017-12-07 09:36:24","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"R1","meeting":"R1-91","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]