[{"name":"R5-205132","title":"TS 36.523-1 Status before RAN5#89-e","source":"Samsung (Rapporteur)","contact":"Stoyan Baev","contact-id":2367,"tdoctype":"other","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":705,"ainumber":"6.5.6","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":51320,"status":"noted","reservation_date":"2020-10-21 14:03:26","uploaded":"2020-10-29 10:36:23","revisionof":"","revisedto":"","release":"","crspec":"36.523-1","crspecversion":"","workitem":"","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-205132.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-205151","title":"Specifying a single LTE multi-layer test for MCPTT enabled devices","source":"Samsung, NIST, FirstNet, AT&T","contact":"Stoyan Baev","contact-id":2367,"tdoctype":"discussion","for":"Approval","abstract":"RAN5 has specified testing of MCPTT Client in the TS 36.579-x series with MCPTT Client conformance test cases defined in 36.579-2.\nRAN5 has considered different test models in response to market interest and currently is not focusing on the option of so called \"traditional\" testing of an Application communication over a 3GPP RAT (in this case LTE) where the MCPTT enabled device's behaviour in the RAT is implicitly tested during the testing of the Application.\nFor the strictly LTE behaviour of a device, RAN5 has specified testing in the TS 36.523-1. However, due to test design historical reasons, a MCPTT enabled Device cannot be tested for its LTE behaviour unless the MCPTT Client is disabled (the LTE specification cannot handle the MCPTT specific APN\/PDN\/Bearer establishments).\nThe consequence from the above is that RAN5 test specs today do not provide means for verifying the LTE behaviour of a MCPTT enabled UE.\n2\tProposal\nConsidering the criticality of the service which MCPTT enabled devices are expected to provide and the high requirements for the device reliability, it is proposed that RAN5 agrees on the specification of a single LTE test aimed at verifying the LTE relevant behaviour when the MCPTT Client\n-\tRegisters for MCPTT Services\n-\tInitiates an MCPTT Call\nTo facilitate development of such a test on the existing LTE test platforms, the MCPTT Client application relevant exchange throughout the test should be kept to a minimum and should not be strictly verified for compliance with the MCPTT requirements.","secretary_remarks":"","agenda_item_sort_order":705,"ainumber":"6.5.6","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":51510,"status":"noted","reservation_date":"2020-10-21 14:03:38","uploaded":"2020-10-30 12:49:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","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-205151.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}]