[{"name":"R5-242587","title":"Discussion on extending RAN5 scope to include MCPTT, MCVideo, and MCData Server Test Cases","source":"FisrtNet, NIST, Ericsson, AT&T, Samsung, Element","contact":"Satish Jha","contact-id":103337,"tdoctype":"discussion","for":"Decision","abstract":"For 3GPP Release 13, Mission Critical Push To Talk (MCPTT) was defined in core specifications. Consequently, and for commercial need, a Work Item [1] was opened in RAN5 to create conformance test cases. The Work Item created the TS 36.579 family of specifications. The TS 36.579 family of specifications included both UE\/Device\/Client conformance test cases as well as server conformance test cases. The server test cases, included in TS 36.579-3, were created for situations where an MCPTT server would exist outside of the core network and be controlled by an end user acting as a customer of a carrier. No network or core testing was part of the scope of the Work Item.\nThe justification of server-side conformance testing in Rel-13 Work Item Description [1] states:\n[...]\n2\tDiscussion\nThere are scenarios in the real world where a server, or a device that can perform as a server, interacts with the core and its mission critical services (MCX) servers. In these cases, a human user controls the device, so technically, it\u2019s an end user device. The most common instance of this is with the use of dispatch interfaces and mobile dispatch devices. A human uses the dispatch interface to enable groups, disable groups, create groups, etc. and interact with the carrier core servers. MCX (MCPTT, MCVideo, and MCData) Server conformance testing will be a mere extension of this concept, and does not represent a bridge for RAN5 to test the Network.\nServer side MCX conformance testing specs are critical to bring interoperability among MCX application server vendors\/providers and across interconnected MCX systems from various vendors. It can help in reducing implementation cost and rollout time. _x000D_\nServer-side conformance testing is currently not in scope of 3GPP RAN5. It has resulted in pausing all work for MCPTT, MCVideo, and MCData server test cases which were endorsed by RAN5 and approved by RAN plenaries in Rel-13 and Rel-16 WIDs for mission critical services. It will be beneficial to discuss and agree on a way forward to resume work on MCPTT, MCVideo, and MCData server test cases. Following proposals may be potential way forward:\nProposal 1: Accept that some human-controlled devices are able to act as Mission Critical Services servers, exist outside of the core network, and can therefore fit within the current scope of RAN5.\nor\nProposal 2: Extend the scope of RAN5 to include Mission Critical Services server conformance testing which would enable incorporating MCPTT, MCVideo, and MCData server test cases in RAN5 specs.\n3\tProposal\nProposal 1: Accept that some human-controlled devices are able to act as Mission Critical Services servers, exist outside of the core network, and can therefore fit within the current scope of RAN5.\nor\nProposal 2: Extend the scope of RAN5 to include Mission Critical Services server conformance testing which would enable incorporating MCPTT, MCVideo, and MCData server test cases in RAN5 specs.","secretary_remarks":"","agenda_item_sort_order":847,"ainumber":"6.3.13.","ainame":"Discussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":25870,"status":"noted","reservation_date":"2024-08-05 07:19:50","uploaded":"2024-05-09 21:02:06","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"MCProtoc16_enh2MCPTT_eMCData2-ConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5__103_Fukuoka\/Docs\/R5-242587.zip","group":"R5","meeting":"R5-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]