[{"name":"R5-254101","title":"NG.114 and 5GS voice applicability","source":"Ericsson","contact":"Bo J\u00f6nsson","contact-id":76116,"tdoctype":"discussion","for":"Endorsement","abstract":"5GS voice test cases refers to GSMA PRD NG.114 [1]. However, some test cases are not referring and\/or aligned with NG.114.\n2\tDiscussion\nThe applicability is defined in TS 34.229-2 [2] and TS 38.523-2 [3] for 5GS voice test cases and refers to GSMA PRD NG.114 [1]. In our understanding it\u2019s agreed to align all 5GS voice test cases applicability and refer to NG.114.\nFor TS 34.229-2 [2]:\nObservation 2-1:\nThe test case 7.11 is not referring to NG.114. \nProposal 2-1:\nIt\u2019s proposed to align test case 7.11 with NG.114.\nFor TS 38.523-2 [3]:\nObservation 2-2:\nThe test case 11.1.1 is not referring to NG.114. The TPs are also identical with test case 11.1.1a for NG.114.\nProposal 2-2:\nIt\u2019s proposed to void test case 11.1.1.\nObservation 2-3:\nThe test case 11.1.3 is not referring to NG.114. The TP is also identical with test case 11.1.3a for NG.114.\nProposal 2-3:\nIt\u2019s proposed to void test case 11.1.3.\nObservation 2-4:\nThe test case 11.1.2 is not referring to NG.114. The TP 1, \u201cwithout N26 interface supported\", cannot be aligned with NG.114 since the UE and the network must support the N26 interface.\nProposal 2-4:\nIt\u2019s proposed to void test case 11.1.2.\nObservation 2-5:\nThe test case 11.1.5 is not referring to NG.114. The TP 1, \u201cwithout N26 interface supported\", cannot be aligned with NG.114 since the UE and the network must support the N26 interface.\nProposal 2-5:\nIt\u2019s proposed to void test case 11.1.5.\nObservation 2-6:\nThe test case 11.1.6 is not referring to NG.114. The TP 1, \u201cwithout N26 interface supported\", cannot be aligned with NG.114 since the UE and the network must support the N26 interface.\nProposal 2-6:\nIt\u2019s proposed to void test case 11.1.6.\nObservation 2-7:\nThe test case 11.1.4 is not referring to NG.114\nProposal 2-7:\nIt\u2019s proposed to align test case 11.1.4 with NG.114.\nObservation 2-8:\nThe test case 11.1.8 is not referring to NG.114\nProposal 2-8:\nIt\u2019s proposed to align test case 11.1.8 with NG.114.\nObservation 2-9:\nThe test case 11.1.9 is not referring to NG.114\nProposal 2-9:\nIt\u2019s proposed to align test case 11.1.9 with NG.114.","secretary_remarks":"","agenda_item_sort_order":1155,"ainumber":"6.6.6.6","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":41010,"status":"noted","reservation_date":"2025-08-12 13:49:05","uploaded":"2025-08-14 12:52:39","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__108_Bangalore\/Docs\/R5-254101.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"R5-254502","title":"Discussion on support of NR RedCap in P-Access-Network-Info header field","source":"Qualcomm India Pvt Ltd","contact":"Anamika Ghosh","contact-id":111899,"tdoctype":"discussion","for":"Discussion","abstract":"With [1], 3GPP CT1 has introduced support for the NR RedCap RAT type by defining the value '3GPP-NR-REDCAP' in the access-class and access-type parameters of P-Access-Network-Info header in [2]. This enhancement enables IMS networks to identify and differentiate traffic associated with NR RedCap UEs, which is critical for functions such as charging. These parameter values are currently not specified in [3] and affects test cases in [4] and [5] when run on a UE supporting NR RedCap.\n2.\tDiscussion\nP-Access-Network-Info header is checked across multiple SIP messages, as specified in default messages such as A.1.1, A.2.1, A.3.1, etc., in [3]. UE including access-class or access-type parameter of P-Access-Network-Info header with value as '3GPP-NR-REDCAP' would fail all IMS test cases in [4] and [5]. Hence, all impacted default message contents of [3] needs update.\nHowever, as these changes were introduced late in [2], some NR RedCap UEs may still not adhere to the requirement of adding \u201c3GPP-NR-REDCAP\u201d value in access-type and access-class parameters of P-Access-Network-Info header. It would be prudent to provide a grace period (TBD) for such UEs to comply with the requirement. During this period, UEs including access-class parameter with \u201c3GPP-NR\u201d or access-type parameter with value \u201c3GPP-NR-TDD\u201d or \u201c3GPP-NR-FDD\u201d instead of \u201c3GPP-NR-REDCAP\u201d shall not fail existing test cases.\n3.  Proposals\nProposal 1: Update default message contents of [3] to allow inclusion of '3GPP-NR-REDCAP' in the access-class and access-type parameter of P-Access-Network-Info header.\nProposal 2: A grace period (TBD) to be granted for inclusion of '3GPP-NR-REDCAP' in the P-Access-Network-Info header.\nRAN5 CR [6] has been raised at this meeting to handle both the proposals.","secretary_remarks":"","agenda_item_sort_order":1155,"ainumber":"6.6.6.6","ainame":"Discussion Papers, Work Plan, TC lists","tdoc_agenda_sort_order":45020,"status":"noted","reservation_date":"2025-08-15 03:25:50","uploaded":"2025-08-26 06:01:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"NR_redcap_plus_ARCH-UEConTest"},{"winame":" TEI17_Test"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5__108_Bangalore\/Docs\/R5-254502.zip","group":"R5","meeting":"R5-108","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]