[{"name":"R5-205327","title":"Discussion paper for RRC Segmentation in Rel-16 RACS","source":"Qualcomm Korea","contact":"yogesh tugnawat","contact-id":63855,"tdoctype":"discussion","for":"Discussion","abstract":"Rel-16 WI for RACS introduced the capability to send\/receive RRC message in segments in of the message is larger than maximum supported size of a PDCP SDU (9k in NR, 7k LTE). Below are the core spec requirements which creates challenges in conformance testing for a reliable and consistent outcome. [..]\n2.\tConformance test challenges and possible solution\n2.1\tTest Challenges\nThe size of UE capability message depends on UE's support of different features specially the support of different RF bands, CA combinations and different RAT. Thus, for a UE, which supports Rel-16 RACS \"and\" whose UE capability message is larger than the maximum supported PDU size, would-be a candidate for possible testing of this optional feature. However, it is not known in advance how many segments can be expected. This creates challenges in creating a reliable test outcome. \n2.2\tPossible Solutions\nProposal-1 - Testing using PICS\/PIXIT Declaration\nUE's shall declare the size of its RRC UE Capability message assuming we exercise maximum bands in UE Capability enquiry, below can be achieved by declaring the support of below PICS items, which can be defined in TS 38.508-2 and will  be applied in the prose\n1. PC_RACS - This is the overall capability for UE to support R16 RACS feature\n2. PC_UECapabilitySegement - PICS to declare if UE does support RACS feature and if so, will it be segmenting the UE capability message\n3. PC_No. of UECapability Segment (or the total size) - Total number of UE Capability segments\nBased on 2) and 3) above, it can be deduced no of segments and last segments and the test prose can reliably test UE capability message. \nThe testability will be limited to what UE supports and  no overall flexibility in sending segments and further creating more scenarios for a loss of segment. However, the UE can be tested in real world like scenario  based on its current capability.\nAlternatively, below logic can be incorporated in prose to automatically determine number of segments and allow all segments until the last segment has been received. The results can then be optionally compared with PC_No. of UECapability Segment [..]\nProposal-2 - Introduce a new TLB\nCreate a  new RRC TLB Function which will be defined in TS38.509 and create a loopback at RRC level. However, since we have to make several dummy messages for the UE to treat as segments that will require complicated implementation at UE end. Also, the DL segmentation support is further optional and hence such considerations had to be put in place. However, if this can be achieved we can exercise all scenarios in a controlled environment. \nThe implementation, complexity and optionality of certain features makes this UE RRC TLB function more of development hassle for UE and overall gain might not be worth pursuing. Further, it may violate some core spec requirement.\nProposal-3 - Controlled PDCP size\nAn RRC TLB or CMD to restrict max PDCP size as such the UE will always segment the message at RRC. This might create unique challenges at L2 level but will avoid UE declaration in Proposal-1. However, the test might deviate from real world and core spec requirements and hence might not be feasible.\n3.\tConclusion and Way Forward\nConsidering the pro's and con's of each proposal above, Proposal-1 promises to be the optimum way to test UL part of RACS feature.","secretary_remarks":"","agenda_item_sort_order":595,"ainumber":"6.3.20.","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":53270,"status":"revised","reservation_date":"2020-10-27 17:21:33","uploaded":"2020-10-30 23:52:35","revisionof":"","revisedto":"R5-206279","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"RACS-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-205327.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-206279","title":"Discussion paper for RRC Segmentation in Rel-16 RACS","source":"Qualcomm Korea","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":595,"ainumber":"6.3.20.","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":53271,"status":"noted","reservation_date":"2020-11-22 12:48:33","uploaded":"2020-11-22 12:51:21","revisionof":"R5-205327","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"RACS-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_89_Electronic\/Docs\/R5-206279.zip","group":"R5","meeting":"R5-89-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]