[{"name":"R5-196204","title":"TS 36.523-1 Status before RAN5#84","source":"Rapporteur (BlackBerry)","contact":"Claude Arzelier","contact-id":14266,"tdoctype":"other","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":476,"ainumber":"6.4.6","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":62040,"status":"noted","reservation_date":"2019-08-14 15:18:00","uploaded":"2019-08-14 15:31:05","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_84_Ljubljana\/Docs\/R5-196204.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-196205","title":"TS 36.523-1 Status after RAN5#84","source":"Rapporteur (BlackBerry)","contact":"Claude Arzelier","contact-id":14266,"tdoctype":"other","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":476,"ainumber":"6.4.6","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":62050,"status":"noted","reservation_date":"2019-08-14 15:20:28","uploaded":"2019-11-05 16:26:05","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_84_Ljubljana\/Docs\/R5-196205.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-196349","title":"Discussion Document on 2 Proposed Test Cases","source":"NIST","contact":"Jason Kahn","contact-id":75979,"tdoctype":"discussion","for":"Agreement","abstract":"For commercial reasons, FirstNet and AT&T would like 2 test cases added to TS 36.523-1 that ocver adding additional default bearers and dedicated bearers related to Mission Critical Services (MCS).\nDetail:\nIn an effort to support 3GPP-based MCPTT, MCData, and MCVideo, FirstNet and AT&T are looking to implement a Mission Critical Services PDN. This PDN will establish a default bearer with a QCI of 69 and have associated dedicated bearers. The dedicated bearers will use QCIs of 65, 66, 70, and 2 (or instead of 2, possibly 7 or 8). When implemented in conjunction with the normal internet default bearer and the IMS\/VoLTE bearers, there will be 8 bearers overall. This is the maximum allowed in Release 14. FirstNet and AT&T are concerned that there are no test cases the cover the topic of multiple default and dedicated bearers that use an array of QCI values, especially QCI values concerning Mission Critical Services (MCS). For commercial reason, AT&T and FirstNet are proposing to create 2 new test cases for TS 36.523-1 in section 10.2. Although, there might be a more appropriate location for the proposed test cases. The PTRCB also has a need for more expansive test cases concerning the establishment of bearers associated with MCS. The 2 proposed test cases are:\n1)\tAfter the initial default bearer is created upon switch on of the UE, the UE performs a PDN CONNECTIVITY REQUEST to establish a default bearer for MCPTT signaling at a QCI value of 69. A dedicated bearer for MCPTT is then set up at QCI 65 or 66. No IMS is tested.\n2)\tAfter the initial default bearer is created upon switch on of the UE, the UE performs a normal PDN CONNECTIVITY REQUEST to establish a default bearer for IMS\/VoLTE signaling at a QCI value of 5. A associated dedicated bearer is then set up at QCI 1. The UE then performs a PDN CONNECTIVITY REQUEST to establish a default bearer for MCS signaling at a QCI value of 69. Dedicated bearers are then set up at QCI 65 and 66 for MCPTT, QCI 70 for MCData, and QCI 2 for MCVideo. A total of 8 bearers are created.","secretary_remarks":"","agenda_item_sort_order":476,"ainumber":"6.4.6","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":63490,"status":"noted","reservation_date":"2019-08-15 17:27:25","uploaded":"2019-08-15 22:42:22","revisionof":"","revisedto":"","release":"Rel-14","crspec":"36.523-1","crspecversion":"","workitem":[{"winame":"TEI14_Test"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_84_Ljubljana\/Docs\/R5-196349.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-196528","title":"NG.108 scope update for test cases applicable to CAT-M1 UEs","source":"Qualcomm Incorporated","contact":"Ankit Banaudha","contact-id":58157,"tdoctype":"discussion","for":"Decision","abstract":"The purpose of this paper is to discuss the applicability of GSMA NG.108 profile for test cases.\nDiscussion\nBased on the requirements defined in GSMA NG.108 profile, CAT-M1 UEs shall be NG.108 compliant to perform IMS operations. \nThere are two set of test cases, some are specific to CAT-M1 UEs (e.g. 6.1.2.2c, 8.2.4.27 etc) and there are LTE test cases which are extended to CAT-M1 requirements. Both these set of test cases can be executed with IMS enabled (pc_IMS:=TRUE) configuration but currently there is no scope defined or guidelines provided that should be followed when IMS is enabled on CAT-M1 UEs executing these set of test cases.\nIn RAN5#82, Prose CR was agreed, which extended the scope of Annex J to include NG.108 adherence for CAT-M1 UEs with IMS enabled. \nSimilar update is needed for scope of test cases as well, so only NG.108 compliant UEs will be able to execute CAT-M1 test cases with IMS enabled.\nProposal\nQualcomm would like to make following proposal:\n\tUpdate the scope (section 1) to allow CAT-M1 UEs adhering to GSMA NG.108 profile run the test cases with IMS enabled.","secretary_remarks":"","agenda_item_sort_order":476,"ainumber":"6.4.6","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":65280,"status":"noted","reservation_date":"2019-08-16 07:10:02","uploaded":"2019-08-16 17:02:02","revisionof":"","revisedto":"","release":"","crspec":"36.523-1","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_84_Ljubljana\/Docs\/R5-196528.zip","group":"R5","meeting":"R5-84","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]