[{"name":"R5-242116","title":"LS on development of FRMCS conformance test cases by ETSI TTF","source":"TC RT","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"The ETSI Technical Committee for Rail Telecommunications (TC RT) has initiated a Testing Task Force (TTF) dedicated to developing conformance test cases for the Future Railway Mobile Communication System (FRMCS). This TTF's mission is to develop conformance test cases (in prose) that target client side and server side for railway-specific and public safety Mission Critical Services (MCS) functionalities specified by 3GPP, following the test methodologies employed by the 3GPP RAN working group 5 (RAN5). Upon completion of dedicated Milestones as specified in TTF ToR, TC RT intention would be to forward those MCS client and server-side conformance test cases to RAN5, to be proposed for incorporation into the relevant 3GPP RAN5 Technical Specifications for MCS conformance._x000D_\n_x000D_\nDeliverable D1, Mission Critical Services over 5G, has been deemed beyond the scope of this TTF. Instead, the work on Mission Critical Services over 5G will proceed on a voluntary basis directly within the RAN5 group._x000D_\n_x000D_\nThe ability to demonstrate that MCS implementations conform to the standard is a key tenet in support of telecom interoperability and, in a railway context, in support of railway interoperability. Thorough conformance testing will increase the level of confidence that equipment from various suppliers is conformed to the standards and will interoperate. This is particularly relevant in a European context due to very frequent cross-border operations._x000D_\n_x000D_\n2. Actions:_x000D_\nETSI TC RT kindly asks RAN WG5 to take the above information into account.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":746,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":21160,"status":"noted","reservation_date":"2024-11-04 09:22:51","uploaded":"2024-04-11 09:29:27","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__103_Fukuoka\/Docs\/R5-242116.zip","group":"R5","meeting":"R5-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-242117","title":"LS on development of Server Side Conformance for Mission Critical Services by ETSI TTF","source":"TCCE","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS in","for":"Information","abstract":"The ETSI Technical Committee (TC) TCCE (TETRA and Critical Communications Evolution) has initiated a Testing Task Force (TTF) dedicated to developing conformance test cases for Mission Critical Services (MCS). This TTF's objective is to develop conformance test cases (in prose) that target server-side MCS functionalities specified by 3GPP, following the test methodologies employed by the 3GPP RAN working group 5 (RAN5). There are ongoing internal discussions within TCCA (The Critical Communications Association) and UIC (International Union of Railways) to formally ask to include server-side conformance tests into the 3GPP RAN5 terms of reference and we assume that RAN5 is the best place to address these. Upon completion of dedicated Milestones as specified in TTF ToR T028 (attached), TCCE\u2019s intention would be to forward those MCS server-side conformance test cases to RAN5, to be proposed for incorporation into the relevant 3GPP RAN5 Technical Specifications for MCS conformance._x000D_\n_x000D_\nThe ability to demonstrate that MCS application server conform to the 3GPP standards will be of critical importance to all potential users, especially in the public safety and railways sectors. Thorough conformance testing will increase the level of confidence that MCS server equipment from various suppliers is conformed to the standards and will interoperate. This in turn will reduce implementation and rollout times and costs. Not providing timely test specifications, would ultimately delay the deployment of MCS. Further consequences are a delay in deploying MCS equipment paired with a loss of confidence in MCS as there is a risk that early implementations of MCS are not standard conform or interoperable as expected and serious rework may be needed to solve that. _x000D_\nServer-side conformance plays a critical role in ensuring interoperability within multi-vendor MCS systems, as well as across interconnected MCS systems from various vendors and migration across systems in cross-border operations._x000D_\nThere is a high risk that proprietary implementations have to be or will be rolled-out in case no conformance tests are available.","secretary_remarks":"LS R5-206259 on failing initial registration without Retry-After header field from RAN5","agenda_item_sort_order":746,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":21170,"status":"noted","reservation_date":"2024-11-04 09:22:51","uploaded":"2024-04-11 09:29:27","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__103_Fukuoka\/Docs\/R5-242117.zip","group":"R5","meeting":"R5-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-242290","title":"Proposal for new test cases related to P-CSCF Restoration procedures","source":"Orange, Qualcomm","contact":"Guillaume Tesserault","contact-id":103462,"tdoctype":"discussion","for":"Endorsement","abstract":"With 3G\/2G sunset in some countries CS Fall Back won\u2019t be an option anymore when issue happens in IMS core network during call establishment. A set of standardized procedures for restoration of IMS connectivity after node or link failure is defined in TS","secretary_remarks":"","agenda_item_sort_order":746,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":22900,"status":"withdrawn","reservation_date":"2024-02-05 07:09:32","uploaded":"2024-05-10 08:13: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__103_Fukuoka\/Docs\/R5-242290.zip","group":"R5","meeting":"R5-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-243234","title":"Proposal for new test cases related to P-CSCF Restoration procedures","source":"Orange, Qualcomm","contact":"Guillaume Tesserault","contact-id":103462,"tdoctype":"discussion","for":"Endorsement","abstract":"With 3G\/2G sunset, in some countries CS Fall Back won\u2019t be an option anymore. Failures may occur during call establishment when issue happens in IMS core network. VoIMS service must be resilient. _x000D_\nA set of standardized procedures for restoration of IMS connectivity after node or link failure are defined in TS 23.380 [1] and TS 24.229 [2]. These procedures are also included in IR92 [3] and NG114 [4] in P-CSCF Discovery section._x000D_\n2\tDiscussion_x000D_\nThe discussion is about adding the following test cases in RAN5 specifications to cover IMS\/P-CSCF restoration procedures bellow:_x000D_\nProposal 2-1: Verify UE behaviour when P-CSCF addresses are included in PDU-Session Modification Command when UE is connected to 5GC _x000D_\nAs described in section U.2.2.1C of TS 24.229 [2] if the UE receives one or more P-CSCF address(es) in the extended Protocol Configuration Options information element of a PDU SESSION MODIFICATION COMMAND message and the one or more P-CSCF addressee(s) do not include the address of the currently used P-CSCF, then the UE shall acquire a different P-CSCF address from the one or more P-CSCF addresse(s) in the PDU SESSION MODIFICATION COMMAND message. If more than one P-CSCF address with the same container identifier (i.e. \"P-CSCF IPv6 Address\" or \"P-CSCF IPv4 Address\") are included, then the UE shall assume that the more than one P-CSCF addresses with the same container identifier are prioritised with the first P-CSCF address with the same container identifier within the Protocol Configuration Options information element as the P-CSCF address with the highest priority_x000D_\nProposal 2-2: Verify UE behavior when P-CSCF address are included in Modify EPS Bearer Context Request when UE is connected to EPS_x000D_\nAs described in section L.2.2.1C of TS 24.229 [2] if the UE used method II for P-CSCF discovery and if the UE receives one or more P-CSCF address(es) in the Protocol Configuration Options information element of a Modify EPS Bearer Context Request message the one or more P-CSCF addresse(s) do not include the address of the currently used P-CSCF, then the UE shall acquire a different P-CSCF address from the one or more P-CSCF addresse(s) in the Modify EPS Bearer Context Request message. If more than one P-CSCF address with the same container identifier (i.e. \u201cP-CSCF IPv6 Address\u201d or \u201cP-CSCF Ipv4 Address\u201d) are included, then the UE shall assume that the more than one P-CSCF addresses with the same container identifier are prioritised with the first P-CSCF address with the same container identifier within the Protocol Configuration Options information element as the P-CSCF address with the highest priority. _x000D_\nProposal 2-3: Verify UE behaviour when P-CSCSF address are included in IKEv2 INFORMATIONAL exchange when UE is connected to Non 3GPP Access_x000D_\nAs described in section 5.6.5.2 of TS 23.380 [1] if the UE has sent its capability the indication of the support of P-CSCF restoration to the ePDG by including the P-CSCF_RESELECTION_SUPPORT Notify payload within an IKE_AUTH request message (as defined in TS 24.302 [5]) and if the UE receives an IKEv2 informational exchange message containing a list of P-CSCF addresses, the UE shall first send a response to the ePDG, and then the UE must acquire a different P-CSCF from the currently used P-CSCF, and initiate a new initial SIP registration_x000D_\nProposal 2-4: _x000D_\n...","secretary_remarks":"","agenda_item_sort_order":746,"ainumber":"6.2","ainame":"Review incoming LS (fm A.I. 3) & new subject discussion papers","tdoc_agenda_sort_order":32340,"status":"noted","reservation_date":"2024-10-05 16:00:21","uploaded":"2024-05-11 08:19:55","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__103_Fukuoka\/Docs\/R5-243234.zip","group":"R5","meeting":"R5-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]