[{"name":"R5-204361","title":"LS on old unverified IMS test cases","source":"TSG WG RAN5","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"A number of test cases for IMS over EPC in 3GPP TS 34.229-1 have been available in prose and have been verifiable in TTCN for a long time but did not see progress in verification:\n1)\tTest case 8.14 on \u201cInitial registration for three implicit registration sets\u201d was introduced in Feb 2011 at RAN5#50, but never verified.\n2)\tTest case 12.16 on \u201cMO MTSI Text call\u201d was introduced in Feb 2008 at RAN5#38, but never verified.\n3)\tTest case 12.17 on \u201cMT MTSI Text call\u201d was introduced in Aug 2008 at RAN5#40, but never verified.\n4)\tTest case 15.21 on \u201cJoining a conference after being invited to it\u201d was introduced in Nov 2008 at RAN5#41, but never verified.\n5)\tTest case 15.21b on \u201cJoining a conference after being invited to it \/ Video\u201d was introduced in Aug 2014 at RAN5#64, but never verified.\n6)\tTest case G.15.19 on \u201cJoining a conference after being invited to it \/ WLAN\u201d was introduced in Nov 2016 at RAN5#73, but never verified.\n7)\tTest case G.15.22 on \u201cJoining a conference after being invited to it with video \/ WLAN\u201d was introduced in Nov 2016 at RAN5#73, but never verified.\nTherefore, RAN5 intends to void these test cases and does not plan to add corresponding test cases to its Work Plan for IMS over 5GS.\nActions: To GCF CAG, PTCRB, GSMA 5GJA groups: Take note of above intention of RAN5 to void mentioned test cases.","secretary_remarks":"","agenda_item_sort_order":683,"ainumber":"6.7","ainame":"\tOutgoing liaison statements for provisional approval","tdoc_agenda_sort_order":436100,"status":"approved","reservation_date":"2020-09-02 09:09:01","uploaded":"2020-09-02 09:11:11","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GCF CAG, PTCRB PVG","Cc":"GSMA 5GJA","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_88_Electronic\/Docs\/R5-204361.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204362","title":"LS on two consecutive invalid challenges","source":"TSG WG RAN5","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"When investigating IMS core specification TS 24.229 for appropriate test coverage for IMS over 5GS, relevant ambiguous text was detected. Specifically, TS 24.229 cl 5.1.1.5.12 contains the following text:\nA UE shall only respond to two consecutive invalid challenges and shall not automatically attempt authentication after receiving two consecutive invalid challenges. The UE may attempt to register with the network again after an implementation specific time.\nFirst the text asks to respond to two consecutive challenges (which is understood to send another REGISTER request after the second invalid challenge) and then it says not to attempt authentication after two consecutive invalid challenges (which is understood not to send another REGISTER request after the second invalid challenge). \nDoes the core specification expect the UE to send another REGISTER request after the second invalid 401 Unauthorized response or not?\nActions: To TSG CT WG1 group: TSG RAN WG5 respectfully asks TSG CT WG1 to clarify the above ambiguity.","secretary_remarks":"","agenda_item_sort_order":683,"ainumber":"6.7","ainame":"\tOutgoing liaison statements for provisional approval","tdoc_agenda_sort_order":436200,"status":"approved","reservation_date":"2020-09-02 09:09:01","uploaded":"2020-09-02 09:11:11","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG WG CT1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_88_Electronic\/Docs\/R5-204362.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204376","title":"Status of Conformance testing development for Mission Critical Services (MCS)","source":"TSG WG RAN5","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"RAN5 would like to provide information on the status of the conformance testing development for Mission Critical Services (MCS) as per the end of RAN5#88 meeting.\n\u2022\tAt this RAN5#88e meeting RAN5 endorsed the introduction of a new Work Item (WI) on UE Conformance Test Aspects for Mission Critical Enhancements for MCPTT, MCVideo and MCData for Rel-15\no\tThis MCS Rel-15 WI is pending approval at the 3GPP TSG RAN plenary in September 2020. RAN5 expects the proposal to be approved.\no\tAfter the approval the expectations from the supporting companies are work in the scope of the WI to start at the RAN5 meeting in November 2020.\no\tPending the approval, the target completion date for the WI is planned for Q4, 2021. Depending on the WI outcome the TTCN-3 test suite implementation could be expected to complete in 2022.\no\tThe intention of the supporting companies is to prioritise the work on the MCPTT Rel-15 in the WI Work Plan (WP) during the last quarter of 2020 and the first quarter of 2021. TTCN-3 test suite implementation is to follow during 2021.\n\u2022\tAt the same time, RAN5 agreed to continue with the development of the MCS test specification targeting the provision of TTCN-3 test suite which can be used for validating the conformance of MCS Clients compliant with the Rel-14 requirements.\no\tRAN5 will not develop testing for any Rel-13-only specific requirements. All MCPTT test case introduced as part of the MCS Rel-13 WI are being updated with Rel-14 requirements in both test specifications and TTCN-3 test suite implementation, wherever needed.\no\tThe MCS Rel-14 WI is expected to be closed at the TSG RAN meeting in September. TTCN-3 test suite implementation is to follow in 2021.","secretary_remarks":"","agenda_item_sort_order":683,"ainumber":"6.7","ainame":"\tOutgoing liaison statements for provisional approval","tdoc_agenda_sort_order":437600,"status":"approved","reservation_date":"2020-09-02 09:09:10","uploaded":"2020-09-02 09:11:11","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"PTCRB, PTCRB PVG","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_88_Electronic\/Docs\/R5-204376.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204383","title":"LS on MCS group document subscription procedures","source":"TSG WG RAN5","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":683,"ainumber":"6.7","ainame":"\tOutgoing liaison statements for provisional approval","tdoc_agenda_sort_order":438300,"status":"postponed","reservation_date":"2020-09-02 09:09:17","uploaded":"2020-09-09 18:21:08","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG WG CT1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_88_Electronic\/Docs\/R5-204383.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]