[{"name":"R4-2014889","title":"NR-U CA bandwidth classes","source":"Apple Inc.","contact":"Anatoliy Ioffe","contact-id":76818,"tdoctype":"discussion","for":"Decision","abstract":"Proposal 1: Revise NR CA BW classes definition based on the changes shown in Table 2.1-3 to support NR-U intra-band contiguous CA.\n\nProposal 2: Merge NR-U CA configurations CA_n46G, CA_n46H, and CA_n46I into CA_n46M, n46N, and n46O respectively as shown in Table 2.2-2.\n\nProposal 3: Remove CA BW class \u201cI\u201d from NR-U DL CA Rx requirements for ACS, in-band blocking, and out-of-band blocking as it can be covered by CA BW class \u201cO\u201d.","secretary_remarks":"[97e][106] NR_unlic_SysParameters","agenda_item_sort_order":90,"ainumber":"7.1.1.3","ainame":"Others [NR_unlic-Core]","tdoc_agenda_sort_order":6620,"status":"noted","reservation_date":"2020-10-23 06:13:50","uploaded":"2020-10-23 22:48:32","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"NR_unlic-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG4_Radio\/TSGR4_97_e\/Docs\/R4-2014889.zip","group":"R4","meeting":"R4-97-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R4-2015973","title":"Correction to CA bandwidth classes M, N and O","source":"Ericsson","contact":"Christian Bergljung","contact-id":21143,"tdoctype":"CR","for":"Agreement","abstract":"The aggregated bandwidth of CA BW classes M, N and O should support bandwidth combinations down to 10 + 2*20 MHz, 3*20 MHz and 4*20 MHz, respectively. This is not allowed by the strict inequalities in the lower limits for M and N.\nThe upper limits of the aggregated bandwidths are within square brackets, the tentative limits based on *60 MHz. Aggregation of up to four carriers with 80 MHz and 100 MHz channel bandwidths is covered by the respective classes B, C, D and E. To that end, the square brackets for M and N can be removed. For 5 CC a new (general) CA BW class applicable for all relevant bands can be defined when needed.\nUse of BCS is likely regardless of the value of the upper limit.","secretary_remarks":"[97e][106] NR_unlic_SysParameters","agenda_item_sort_order":90,"ainumber":"7.1.1.3","ainame":"Others [NR_unlic-Core]","tdoc_agenda_sort_order":6630,"status":"not pursued","reservation_date":"2020-10-23 14:25:59","uploaded":"2020-10-23 20:54:03","revisionof":"","revisedto":"","release":"Rel-16","crspec":"38.101-1","crspecversion":"16.5.0","workitem":[{"winame":"NR_unlic-Core"}],"crnumber":551.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG4_Radio\/TSGR4_97_e\/Docs\/R4-2015973.zip","group":"R4","meeting":"R4-97-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R4-2016123","title":"Discussion on NR-U channel arrangement for 6GHz","source":"ZTE Corporation","contact":"Fei Xue","contact-id":59676,"tdoctype":"other","for":"Approval","abstract":"Proposal 1: further discuss how to apply the FCC requirements and AFC or non-AFC policy for the carriers across U-NII bands;\n\nObservation: it is very challenging to achieve the required attenuation for lower edge and upper edge of 6GHz assuming -27dBm\/MHz emission limit needed out of 6GHz band in FCC report.\n\nProposal 2: to achieve emission limit -27dBm\/MHz required by FCC, either lower the BS output power or reserve more guard band or reserve guard band and put the fitter within the 6GHz band.","secretary_remarks":"[97e][106] NR_unlic_SysParameters","agenda_item_sort_order":90,"ainumber":"7.1.1.3","ainame":"Others [NR_unlic-Core]","tdoc_agenda_sort_order":6640,"status":"noted","reservation_date":"2020-10-23 15:45:25","uploaded":"2020-10-23 16:18: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\/WG4_Radio\/TSGR4_97_e\/Docs\/R4-2016123.zip","group":"R4","meeting":"R4-97-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R4-2016501","title":"NRU small enhancement and exception sheet leftovers beyond RAN4#97e","source":"Skyworks Solutions Inc.","contact":"Dominique Brunel","contact-id":75756,"tdoctype":"discussion","for":"Approval","abstract":"In this contribution we discuss the options to continue the work next year on some of the Release 16 NRU topics that are leftovers from the last NRU WI exception sheet.\n\nProposal: Companies views on NRU continuation work in 2021\/Release 17 should be collected in order to enable small enhancement steps from Release 16 and devise a strategy for December plenary RAN#90e.","secretary_remarks":"[97e][106] NR_unlic_SysParameters","agenda_item_sort_order":90,"ainumber":"7.1.1.3","ainame":"Others [NR_unlic-Core]","tdoc_agenda_sort_order":6650,"status":"noted","reservation_date":"2020-10-23 22:02:54","uploaded":"2020-10-23 23:33:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":"38.101-1","crspecversion":"","workitem":[{"winame":"NR_unlic-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG4_Radio\/TSGR4_97_e\/Docs\/R4-2016501.zip","group":"R4","meeting":"R4-97-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]