[{"name":"R5-192091","title":"MCPTT test environment","source":"MCC TF160, NIST, Samsung, Motorola Solutions UK Ltd, Suomen virveverkko Oy, TCCA, BDBOS, BMWi, The Police of the Netherlands, MINISTERE DE L\u2019INTERIEUR, Leonardo SpA, SyncTechno Inc., FirstNet, Nokia, Nkom","contact":"Olivier Genoud","contact-id":58316,"tdoctype":"discussion","for":"Decision","abstract":"In the present contribution we discuss about MCPTT TTCN-3 test case verification hurdles and means to alleviate those hurdles. \nNOTE:\tThe focus of the paper is on MCPTT client, and on-network scenarios. However, the issues and solutions also encompass other features of MCPTT client testing (e.g. off-network), as well as upcoming MCDATA and MCVIDEO. So, in the present paper, one could replace MCPTT by MCS or MCX.  \nProposals\nThe following proposals are made to RAN5: \nProposal1: RAN5 shall decide whether the IP-based MCPTT test model can be specified formally in TS 36.579-5 [4] and can be used by MCC TF160 to implement and release an IP-based MCPTT test suite. \nProposal2: If yes to Proposal1, RAN5 shall decide whether the IP-based MCPTT test suite can only be used for pre-verification testing or can also be used for formal RAN5 verification. \nProposal3: If the answer to Proposal2 is \u2018formal RAN5 verification\u2019, RAN5 shall decide whether the IP-based MCPTT test model shall replace the LTE-based MCPTT test model or be considered as an additional alternative implementation. \nNote that if the answer to Proposal3 is \u2018additional alternative implementation\u2019, then MCC TF160 will prioritize work on the IP-based MCPTT test suite until such a time when there is clear evidence of availability of an LTE-based MCPTT SS. \nProposal4: If the answer to Proposal2 is \u2018formal RAN5 verification\u2019, RAN5 shall:\n-\tinvestigate how to update TS 36.579-1 [1], TS 36.579-2 [2] and TS 36.579-4 [4] to enable the IUT to be the MCPTT client application, \n-\treview the list of MCPTT test cases that can operate without an LTE protocol stack, \n-\tanalyse whether additional\/new LTE conformance test cases should be created to provide coverage the implicitly tested LTE features (see section 4.1 case B-).","secretary_remarks":"","agenda_item_sort_order":501,"ainumber":"6.5.9.7","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":209100,"status":"revised","reservation_date":"2019-02-15 15:00:48","uploaded":"2019-02-22 08:24:17","revisionof":"","revisedto":"R5-192709","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_82_Athens\/Docs\/R5-192091.zip","group":"R5","meeting":"R5-82","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-192709","title":"MCPTT test environment","source":"MCC TF160","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":501,"ainumber":"6.5.9.7","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":209110,"status":"noted","reservation_date":"2019-03-04 14:51:39","uploaded":"2019-03-07 11:10:40","revisionof":"R5-192091","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_82_Athens\/Docs\/R5-192709.zip","group":"R5","meeting":"R5-82","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]