[{"name":"R1-1803622","title":"Remaining issues on beam failure recovery","source":"NEC","contact":"Wang Gang","contact-id":43643,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":36220,"status":"available","reservation_date":"2018-04-02 02:54:56","uploaded":"2018-04-05 22:22:22","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_92b\/Docs\/R1-1803622.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1803637","title":"Summary of remaining issues on beam failure recovery","source":"Huawei, HiSilicon","contact":"Brian Classon","contact-id":45750,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":36370,"status":"available","reservation_date":"2018-04-02 03:07:06","uploaded":"2018-04-06 18:22: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_92b\/Docs\/R1-1803637.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1803745","title":"Remaining issues on beam failure recovery","source":"CATT","contact":"Teng Ma","contact-id":67340,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":37450,"status":"available","reservation_date":"2018-04-02 06:22:46","uploaded":"2018-04-07 05:58: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_92b\/Docs\/R1-1803745.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1803818","title":"Remaining issues on mechanism to recover from beam failure","source":"vivo","contact":"Xueming Pan","contact-id":72721,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":38180,"status":"available","reservation_date":"2018-04-02 06:53:16","uploaded":"2018-04-06 07:39: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_92b\/Docs\/R1-1803818.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1803909","title":"Remaining issues on beam recovery","source":"ZTE, Sanechips","contact":"Ruyue Yu-Ngok Li","contact-id":43128,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":39090,"status":"noted","reservation_date":"2018-04-02 16:12:39","uploaded":"2018-04-07 05:19: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_92b\/Docs\/R1-1803909.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804001","title":"Text Proposal for Beam Failure Recovery","source":"OPPO","contact":"Wenhong Chen","contact-id":66023,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":40010,"status":"available","reservation_date":"2018-04-03 08:31:31","uploaded":"2018-04-06 14:13:19","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_92b\/Docs\/R1-1804001.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804036","title":"Remaining issues on beam failure recovery procedure","source":"ASUSTEK COMPUTER (SHANGHAI)","contact":"Alex Liou","contact-id":65894,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":40360,"status":"available","reservation_date":"2018-04-03 09:41:48","uploaded":"2018-04-03 11:28:28","revisionof":"","revisedto":"R1-1807211","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_92b\/Docs\/R1-1804036.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804059","title":"Remaining issues in beam failure recovery","source":"MediaTek Inc.","contact":"Tao Chen","contact-id":56050,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":40590,"status":"available","reservation_date":"2018-04-03 10:07:55","uploaded":"2018-04-07 06:16:19","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_92b\/Docs\/R1-1804059.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804094","title":"Discussion on remaining issues on beam failure recovery","source":"CMCC","contact":"Xueying Hou","contact-id":58561,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":40940,"status":"available","reservation_date":"2018-04-03 11:21:56","uploaded":"2018-04-07 02:44:15","revisionof":"","revisedto":"R1-1806359","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_92b\/Docs\/R1-1804094.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804211","title":"Discussion of beam failure recovery for carrier aggregation","source":"Lenovo, Motorola Mobility","contact":"Chenxi Zhu","contact-id":64707,"tdoctype":"discussion","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":42110,"status":"available","reservation_date":"2018-04-04 03:11:55","uploaded":"2018-04-06 15:15: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_92b\/Docs\/R1-1804211.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804359","title":"Corrections on beam failure recovery","source":"Samsung","contact":"Youngbum Kim","contact-id":39963,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":43590,"status":"available","reservation_date":"2018-04-04 10:49:01","uploaded":"2018-04-06 18:16:02","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_92b\/Docs\/R1-1804359.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804494","title":"Corrections on beam failure recovery","source":"ETRI","contact":"Jihyung Kim","contact-id":88131,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":44940,"status":"available","reservation_date":"2018-04-05 04:54:57","uploaded":"2018-04-07 03:13: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_92b\/Docs\/R1-1804494.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804545","title":"Remaining issues on beam failure recovery","source":"LG Electronics","contact":"Youngwoo Yun","contact-id":45048,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":45450,"status":"available","reservation_date":"2018-04-05 07:20:45","uploaded":"2018-04-07 05:49: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_92b\/Docs\/R1-1804545.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804715","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":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":47150,"status":"available","reservation_date":"2018-04-05 17:49:46","uploaded":"2018-04-07 06:06: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_92b\/Docs\/R1-1804715.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804788","title":"Beam recovery procedures","source":"Qualcomm Incorporated","contact":"Peter Gaal","contact-id":57198,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":47880,"status":"available","reservation_date":"2018-04-05 22:36:41","uploaded":"2018-04-07 05:45: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_92b\/Docs\/R1-1804788.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804846","title":"Remaining issues on beam failure recovery","source":"InterDigital, Inc.","contact":"Shahrokh Nayeb Nazar","contact-id":72080,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":48460,"status":"available","reservation_date":"2018-04-05 22:43:26","uploaded":"2018-04-07 02:40:34","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_92b\/Docs\/R1-1804846.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1804975","title":"Remaining issues on beam recovery","source":"Ericsson","contact":"Stephen Grant","contact-id":65572,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":49750,"status":"available","reservation_date":"2018-04-06 04:53:22","uploaded":"2018-04-07 02:45: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_92b\/Docs\/R1-1804975.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805042","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":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":50420,"status":"available","reservation_date":"2018-04-06 05:45:01","uploaded":"2018-04-07 05:58:09","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_92b\/Docs\/R1-1805042.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805105","title":"Remaining Details on Beam Recovery","source":"Nokia, Nokia Shanghai Bell","contact":"Mihai Enescu","contact-id":68296,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":51050,"status":"available","reservation_date":"2018-04-06 09:18:21","uploaded":"2018-04-07 04:07:15","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_92b\/Docs\/R1-1805105.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805563","title":"Summary 1 on Remaining issues on Beam Failure Recovery","source":"MediaTek Inc.","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":556300,"status":"revised","reservation_date":"2018-04-16 12:41:39","uploaded":"2018-04-16 12:41:39","revisionof":"","revisedto":"R1-1805583","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_92b\/Docs\/R1-1805563.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805565","title":"WF on remaining issues for beam failure recovery","source":"Intel, MediaTek, ZTE, Sanechips, Huawei, HiSilicon","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":556500,"status":"noted","reservation_date":"2018-04-17 12:22:31","uploaded":"2018-04-17 12:22: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_92b\/Docs\/R1-1805565.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805583","title":"Revised Summary 1 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":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":558300,"status":"noted","reservation_date":"2018-04-17 12:22:31","uploaded":"2018-04-17 12:22:31","revisionof":"R1-1805563","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_92b\/Docs\/R1-1805583.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805604","title":"WF on beamFailureRecoveryTimer","source":"InterDigital, MediaTek, Ericsson, ZTE, SaneChips, Huawei, HiSilicon, NTT DOCOMO, Intel, Samsung","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":560400,"status":"noted","reservation_date":"2018-04-17 12:22:31","uploaded":"2018-04-17 12:22: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_92b\/Docs\/R1-1805604.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805622","title":"LS on beamFailureRecoveryTimer","source":"RAN1, InterDigital","contact":"Patrick Merias","contact-id":52292,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":560400,"status":"approved","reservation_date":"2018-04-20 03:44:56","uploaded":"2018-04-20 03:44:56","revisionof":"R1-1805716","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_92b\/Docs\/R1-1805622.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805623","title":"LS on NR BFR","source":"RAN1, Huawei","contact":"Patrick Merias","contact-id":52292,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":560400,"status":"approved","reservation_date":"2018-04-20 06:24:06","uploaded":"2018-04-20 06:24:06","revisionof":"R1-1805714","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_92b\/Docs\/R1-1805623.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805675","title":"WF on Beam Failure Recovery","source":"Samsung, CATT, Intel, MediaTek, OPPO, Spreadtrum, ASUSTEK, NEC, InterDigital, Qualcomm, ZTE, Sanechips, Huawei, HiSilicon, CHTTL, CMCC","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":567500,"status":"available","reservation_date":"2018-04-20 03:44:57","uploaded":"2018-04-20 03:44: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_92b\/Docs\/R1-1805675.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805689","title":"Summary 2 on Remaining issues on Beam Failure Recovery","source":"MediaTek Inc.","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":568900,"status":"noted","reservation_date":"2018-04-19 12:38:29","uploaded":"2018-04-19 12:38:29","revisionof":"","revisedto":"R1-1805730","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_92b\/Docs\/R1-1805689.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805714","title":"[Draft] LS on NR BFR","source":"Huawei, HiSilicon","contact":"Patrick Merias","contact-id":52292,"tdoctype":"LS out","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":571400,"status":"revised","reservation_date":"2018-04-19 12:38:29","uploaded":"2018-04-19 12:38:29","revisionof":"","revisedto":"R1-1805623","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_92b\/Docs\/R1-1805714.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805716","title":"[DRAFT] LS on beamFailureRecoveryTimer","source":"InterDigital","contact":"Patrick Merias","contact-id":52292,"tdoctype":"LS out","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":571600,"status":"revised","reservation_date":"2018-04-19 12:38:29","uploaded":"2018-04-19 12:38:29","revisionof":"","revisedto":"R1-1805622","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_92b\/Docs\/R1-1805716.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1805730","title":"Summary 3 on Remaining issues on Beam Failure Recovery","source":"MediaTek Inc.","contact":"Patrick Merias","contact-id":52292,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":115,"ainumber":"7.1.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":568901,"status":"noted","reservation_date":"2018-04-20 03:44:57","uploaded":"2018-04-20 03:44:57","revisionof":"R1-1805689","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG1_RL1\/TSGR1_92b\/Docs\/R1-1805730.zip","group":"R1","meeting":"R1-92","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]