[{"name":"R1-1715441","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":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-05 01:40:29","uploaded":"2017-09-12 05:59: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_AH\/NR_AH_1709\/Docs\/R1-1715441.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1715468","title":"Beam Failure Recovery Design Details","source":"Huawei, HiSilicon","contact":"Xiao Weimin","contact-id":56706,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-05 17:15:50","uploaded":"2017-09-11 20:33: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_1709\/Docs\/R1-1715468.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1715531","title":"Discussion of beam recovery mechanism","source":"Lenovo, Motorola Mobility","contact":"Chenxi Zhu","contact-id":64707,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-06 13:49:19","uploaded":"2017-09-11 02:23:08","revisionof":"R1-1712672","revisedto":"R1-1717867","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_1709\/Docs\/R1-1715531.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1715620","title":"Discussion on beam failure recovery","source":"vivo","contact":"Yu Ding","contact-id":67720,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 00:18:30","uploaded":"2017-09-11 16:22: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_1709\/Docs\/R1-1715620.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1715697","title":"Discussion on Beam Recovery Mechanism","source":"Guangdong OPPO Mobile Telecom.","contact":"Weijie Xu","contact-id":72356,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 02:07:12","uploaded":"2017-09-11 10:51:50","revisionof":"","revisedto":"R1-1718055","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_1709\/Docs\/R1-1715697.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1715708","title":"Discussion on beam failure recovery","source":"NEC","contact":"Wang Gang","contact-id":43643,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 03:14:27","uploaded":"2017-09-11 08:43:08","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_AH\/NR_AH_1709\/Docs\/R1-1715708.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1715802","title":"Beam failure detection and recovery","source":"CATT","contact":"Teng Ma","contact-id":67340,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 08:39:49","uploaded":"2017-09-12 04:40:38","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_1709\/Docs\/R1-1715802.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1715860","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":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 08:58:52","uploaded":"2017-09-12 05:42:28","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_1709\/Docs\/R1-1715860.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1715941","title":"Beam failure recovery","source":"Samsung","contact":"Youngbum Kim","contact-id":39963,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 09:05:37","uploaded":"2017-09-12 01:21: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_1709\/Docs\/R1-1715941.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716083","title":"Views on Beam Recovery","source":"NTT DOCOMO, INC.","contact":"Kazuaki Takeda","contact-id":43136,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 10:57:32","uploaded":"2017-09-12 05:56: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_1709\/Docs\/R1-1716083.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716169","title":"On beam recovery for partial and full control channel failure","source":"AT&T","contact":"Arun Ghosh","contact-id":57084,"tdoctype":"discussion","for":"Decision","abstract":"1. Per CORESET based Recovery\n2. CORESET specific PUCCH for recovery\n3. Discuss the relationship between RLF and beam failure. \n4. Contention based PRACH can be used to convey SSB id.","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 15:04:38","uploaded":"2017-09-12 02:18: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_1709\/Docs\/R1-1716169.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716214","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":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 15:31:48","uploaded":"2017-09-12 05:36:35","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_1709\/Docs\/R1-1716214.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716241","title":"Considerations on beam recovery","source":"Sony","contact":"Martin Beale","contact-id":82077,"tdoctype":"discussion","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-08 18:48:17","uploaded":"2017-09-11 22:00:51","revisionof":"R1-1712967","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_1709\/Docs\/R1-1716241.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716268","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":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2017-09-09 01:07:13","uploaded":"2017-09-12 01:51:24","revisionof":"","revisedto":"R1-1716660","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_1709\/Docs\/R1-1716268.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716295","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":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-09 01:14:45","uploaded":"2017-09-12 06:02: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_AH\/NR_AH_1709\/Docs\/R1-1716295.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716351","title":"Basic beam recovery","source":"Ericsson","contact":"Stephen Grant","contact-id":65572,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-09 05:51:28","uploaded":"2017-09-12 04: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_1709\/Docs\/R1-1716351.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716397","title":"Beam recovery procedures","source":"Qualcomm Incorporated","contact":"Peter Gaal","contact-id":57198,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-09 08:05:59","uploaded":"2017-09-12 06:26:04","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_1709\/Docs\/R1-1716397.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716469","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":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-10 04:20:45","uploaded":"2017-09-12 02:04: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_AH\/NR_AH_1709\/Docs\/R1-1716469.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716500","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":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-10 04:46:30","uploaded":"2017-09-11 19:19: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_AH\/NR_AH_1709\/Docs\/R1-1716500.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716543","title":"Details of Improved Beam Failure Handling","source":"National Instruments Corp.","contact":"Nikhil Kundargi","contact-id":57928,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-11 04:18:38","uploaded":"2017-09-11 21:11: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_1709\/Docs\/R1-1716543.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716660","title":"Discussion on mechanisms for beam failure recovery","source":"Sharp","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-12 19:29:29","uploaded":"2017-09-13 08:02:30","revisionof":"R1-1716268","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_1709\/Docs\/R1-1716660.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716690","title":"On beam recovery for partial and full control channel failure","source":"AT&T","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2017-09-19 23:17:52","uploaded":"2017-09-19 23:27: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_AH\/NR_AH_1709\/Docs\/R1-1716690.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716767","title":"Summary of beam recovery mechanism","source":"MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-09-19 23:17:55","uploaded":"2017-09-20 14:27: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_AH\/NR_AH_1709\/Docs\/R1-1716767.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716872","title":"WF on relationship between RLF and beam recovery","source":"NTT DOCOMO, CHTTL, Ericsson, InterDigital, LGE, CMCC, AT&T","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-09-20 14:21:32","uploaded":"2017-09-25 07:47: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_AH\/NR_AH_1709\/Docs\/R1-1716872.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716874","title":"Offline summary on beam recovery mechanism","source":"MediaTek","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-09-20 14:21:32","uploaded":"2017-09-25 07:47: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_AH\/NR_AH_1709\/Docs\/R1-1716874.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716881","title":"WF on Beam Failure Recovery Request Transmission","source":"Intel, ZTE, Sanechips, Oppo, vivo","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-10-06 21:54:04","uploaded":"2017-10-06 21:57: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_AH\/NR_AH_1709\/Docs\/R1-1716881.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716920","title":"WF on dedicated PRACH allocation for beam failure recovery mechanism","source":"MediaTek, InterDigital, Huawei, Hisilicon, LG, Intel, Ericsson","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-10-06 21:54:09","uploaded":"2017-10-06 21:57: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_AH\/NR_AH_1709\/Docs\/R1-1716920.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R1-1716922","title":"WF on candidate beam identification for beam failure recovery","source":"Huawei, Hisilicon, LG, Intel, InterDigital","contact":"Patrick Merias","contact-id":52292,"tdoctype":"other","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":34,"ainumber":"6.2.2.4","ainame":"Mechanism to recover from beam failure","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2017-10-06 21:54:09","uploaded":"2017-10-06 21:57: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_AH\/NR_AH_1709\/Docs\/R1-1716922.zip","group":"R1","meeting":"R1-ah-18959","year":2017,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]