[{"name":"R5-201621","title":"TS 36.523-1 Status before RAN5#87-e","source":"Rapporteur (BlackBerry)","contact":"Claude Arzelier","contact-id":14266,"tdoctype":"other","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":466,"ainumber":"6.4.6","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":16210,"status":"noted","reservation_date":"2020-05-05 16:24:47","uploaded":"2020-05-06 13:58:41","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_87_Electronic\/Docs\/R5-201621.zip","group":"R5","meeting":"R5-ah-38102","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-201622","title":"TS 36.523-1 Status after RAN5#87-e","source":"Rapporteur (BlackBerry)","contact":"Claude Arzelier","contact-id":14266,"tdoctype":"other","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":466,"ainumber":"6.4.6","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":16220,"status":"noted","reservation_date":"2020-05-05 16:27:50","uploaded":"2020-06-10 14:56:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_87_Electronic\/Docs\/R5-201622.zip","group":"R5","meeting":"R5-ah-38102","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-202018","title":"Discussion paper on applicability of legacy test cases for Cat-M2","source":"Ericsson","contact":"Calle Hagenfeldt","contact-id":38975,"tdoctype":"discussion","for":"Endorsement","abstract":"AP#86.04\naccompanying CR in R5-202019.\nWhen completing the Further Enhanced MTC work item, a review of the applicability of legacy LTE test cases, to see whether some should be made applicable (or not applicable) to Cat-M2, was not performed. An action point, AP#86.04, was raised to capture this task.\n2\tDiscussion\nIn TS 36.306 clause 4.1A the following is stated:\n4.1A\tue-CategoryDL and ue-CategoryUL\nThe fields ue-CategoryDL and ue-CategoryUL define downlink\/uplink capability respectively. The parameters set by the UE DL\/UL Categories are defined in subclause 4.2. Tables 4.1A-1 and 4.1A-2 define the downlink and, respectively, uplink physical layer parameter values for each UE DL\/UL Category. Table 4.1A-4 defines the minimum capability for the maximum number of bits of a MCH transport block received within a TTI for an MBMS capable UE capable of reception via MBSFN. Table 4.1A-6 defines the only combinations for UE UL and DL Categories that are allowed to be signalled with ue-CategoryDL and ue-CategoryUL. Table 4.1A-6 also defines which UE Categories a UE shall indicate in addition to the combinations for UE UL and DL Categories. A UE indicating DL category 13 may indicate category 9 or 10 in ue-Category-v1170. A UE indicating Category M2 shall also indicate Category M1.\nThis implies that there is no need to update applicability for TCs that are not applicable for CAT M1 nor CAT M2 \n\nFor Release-13, test cases covering inter-frequency and inter-band mobility\/measurement was not applicable for Rel-13 CAT M1. In Rel-14 those test cases are applicable for both CAT M1 and CAT M2, thus the applicability of those test cases needs to be updated to allow them to be executed for Release-14 CAT M1 and CAT M2 UEs. In the included document [1] there is a proposed list of test cases to be updated.\n3\tProposal\nProposal: It is proposed to update the applicabilities of the test cases listed in [1] by agreeing the CR in [2].","secretary_remarks":"","agenda_item_sort_order":466,"ainumber":"6.4.6","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":20180,"status":"noted","reservation_date":"2020-05-07 15:27:21","uploaded":"2020-05-08 14:56:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15_Test"},{"winame":"LTE_feMTC-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_87_Electronic\/Docs\/R5-202018.zip","group":"R5","meeting":"R5-ah-38102","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-202138","title":"Discussion paper on the need for testing UE handling of extended and spare fields in SI","source":"NTT DOCOMO INC.","contact":"Alan Aquino","contact-id":75436,"tdoctype":"discussion","for":"Discussion","abstract":"Extended\/spare fields in SI may be improperly handled by the UE, resulting in the UE being unable to Attach and the NW being unable to assist.\n\nDuring our rollout of commercial 5G, we discovered an issue in the field involving a Rel-9 UE being unable to properly decode a Rel-15 extended value being broadcast over System Information in our network. Normally, when UE receives an ASN.1 message on any logical channel and considers an optional value as not comprehended (e.g. when the value is set to one that is not defined in the version of the transfer syntax supported by the UE), the UE shall treat the message as if the field were absent and in accordance with the need code for absence of the concerned field. However, the observed behaviour was that the UE treated this as an ASN.1 violation or encoding error, ignoring the System Information message and as a result being unable to perform an attach to our network. \nSince the System Information is broadcast to all UEs and cannot be changed to account for decoding issues in a small number of UEs, and since the NW is unable to handle any issue when the UE is still in Idle, if this is not properly tested, the impact of this issue will be quite severe.\nAs far as we have checked, this error handling is not currently covered by any RAN5 test case, and so we propose that a test case be added as described in [1] to cover this issue in order to ensure that older UE are able to properly ignore newer extensions and spare fields that are added to System Information.\n\nThe issue that we have discussed concerns only improper handling of extended and spare fields, but if other companies have come across similar issues in other messages, then we are open to discussing those as well.\nProposal 1: RAN5 to add testing for this previously uncovered case for extended fields and spare fields.\nProposal 2: RAN5 to use index value 31 of SIB-Type for extended field testing from Rel-8 to Rel-16. \nProposal 3: RAN5 to use index value 15 of SIB-Type from Rel-8 to Rel-11, and index value 7 of si-WindowLength-BR from Rel-13 to Rel-16 for spare field testing.\nProposal 4: A CR for the extended field and spare field test can be found below in [1], and if this CR is agreed we will reflect the same change to the other existing NAS attach test cases.","secretary_remarks":"","agenda_item_sort_order":466,"ainumber":"6.4.6","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":21380,"status":"noted","reservation_date":"2020-05-08 01:44:51","uploaded":"2020-05-08 06:45:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI8_Test"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_87_Electronic\/Docs\/R5-202138.zip","group":"R5","meeting":"R5-ah-38102","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]