[{"name":"R5-224024","title":"UE Conformance Test Aspects for NR Positioning Enhancements","source":"CATT, CAICT","contact":"Xiaozhong Chen","contact-id":50266,"tdoctype":"WID new","for":"Endorsement","abstract":"The objective of the parent work item is to specify solutions to enable RAT dependent (for both FR1 and FR2) and RAT independent NR positioning enhancements for improving positioning accuracy, latency, network and\/or device efficiency. The objective of this work item also includes the support of A-GNSS enhancements. A-GNSS enhancements include support of NavIC, BDS B2a signal and BDS B3I signal.\nThe specification work in the parent work item except the performance parts is finished. The overall completion level for performance part is 40% at RP#96(June-2022). There is a need to introduce an associated RAN5 work item to enable UE conformance testing for NR positioning enhancements.\n4\tObjecive\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to define the UE conformance requirements corresponding to WID on NR positioning enhancements completed by RAN1, RAN2 and RAN4. This work item will cover signalling and RRM conformance test specifications aspects for NR positioning enhancements including the Applicability, Test Environment, Initial Conditions, Test Procedure, Message Exceptions, Test Setup, Connection Diagram, etc.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":40240,"status":"revised","reservation_date":"2022-07-22 02:53:18","uploaded":"2022-08-08 01:38:34","revisionof":"","revisedto":"R5-225250","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_96_Electronic\/Docs\/R5-224024.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-224098","title":"New WID on UE Conformance \u2013 Access Traffic Steering, Switch and Splitting support for NR","source":"China Telecom,CATT,ZTE","contact":"JING ZHAO","contact-id":85327,"tdoctype":"WID new","for":"Endorsement","abstract":"Today, non-3GPP access is a vital companion access infrastructure for mobile networks that can help mobile operators deal with the explosive rate of growth in network traffic. Non-3GPP access such as Wi-Fi can relieve the pressure on the mobile network and can offer fast indoor data connections.\nIncreasingly, many operators are seeking ways to balance data traffic between mobile networks and non-3GPP access in a way that is transparent to users and reduces mobile network congestion. This can be achieved by not only steering traffic from the mobile network onto non-3GPP access, but also to switch or split traffic in a managed way between the two types of accesses in order to deliver the best customer experience. \nFor UEs that can be simultaneously connected to both 3GPP access and non-3GPP access, the 5G system is able to take advantage of these multiple accesses in a way that improves the user experience, optimizes the traffic distribution across various accesses, enables the provision of new high-data-rate services and achieve seamless handover between different accesses, etc.  \n3GPP had initiated the Access Traffic Steering, Switch and Splitting (ATSSS) standardization work from 2019, defined Multi Access-PDU (MA-PDU) session over one 3GPP access and one non-3GPP access and the related NAS ATSSS rule, the Stage 2 of ATSSS had been completed in Sep 2019, and the CT1 aspects of ATSSS had been finished in June,2020. More and more operators are interested in the commercial of ATSSS to enhance their customers experience and a multi-path demo based on MPTCP for NR had also been demonstrated in MWC22, so it\u2019s the proper time for RAN5 to start the R16 protocol conformance test for ATSSS at this time.\n\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to define the UE conformance requirements corresponding to the R16 WI on devices that support ATSSS. This work item will cover NAS Protocol conformance test specifications with Rel-16 ATSSS","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":40980,"status":"revised","reservation_date":"2022-07-29 07:01:34","uploaded":"2022-08-08 10:09:39","revisionof":"","revisedto":"R5-225251","release":"Rel-16","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_96_Electronic\/Docs\/R5-224098.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-224146","title":"New WID on UE Conformance \u2013 Further enhancements of NR RF requirements for frequency range 2 (FR2)","source":"Nokia, Nokia Shanghai Bell, Apple","contact":"Tuomo S\u00e4yn\u00e4j\u00e4kangas","contact-id":69937,"tdoctype":"WID new","for":"Endorsement","abstract":"RAN5 has completed definition of several FR2 enhancement-based test requirements in Release 16. It is now critical to continue the work on further FR2 RF enhancements in RAN5 as part of Rel-17 scope.\n\nUntil RAN#96e, the core part of Rel-17 WI \u2018Further enhancements of NR RF requirements for frequency range 2\u2019 is 100% completed, and the performance part is 80% completed. It is justified to now start the work on the corresponding UE conformance test specifications in 3GPP RAN WG5 to meet the market requirements in time.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe purpose of this work item is to specify conformance test cases for the following FR2 UE features and associated requirements:\n\u2022\tInter-band DL CA enhancements [RAN4 RF\/RRM]\n\u2022\tAgree a method how applicable IBM information is captured into specification for a particular CA configuration. Agree how it is decided whether a certain CA configuration is assuming IBM based requirements (for-example is applicability based on operator request or some general rule or are all CA configurations applicable for IBM). \n\u2022\tDefine test requirements for CA_n258A-n260A and CA_n257A-n259A based on IBM\n\u2022\tDefine UE RF test requirements for CA_n258-n261 inter-band CA within the same freq. group (e.g. 28GHz + 28GHz) for (IBM) \n\u2022\tBoth RF and RRM requirement aspects are in scope for DL inter-band CA.\n\u2022\tInter-band UL CA [RAN4 RF\/RRM] \n\u2022\tSpecify requirements for inter-band UL CA for two bands between different frequency groups based on IBM.\n\u2022\tDefine test requirements for  CA_n257A-n259A and CA_n260-n261 based on IBM \n\u2022\tBoth RF and RRM requirement aspects are in scope for UL inter-band CA.\n\n\u2022\tTest cases to measure performance gain due to UL gaps. Align with RAN4 defined UE specific and NW configured gap for UE Tx power management\n\u2022\tDefine RAN5 test procedures that evaluate the RAN4 defined performance gain over the current baseline (Rel.16 requirements). Include any RAN4-provided definitions related to UE self-calibration and monitoring, impact of UE emissions during UL gap, if any.\n\u2022\tAlign with RAN4 defined UL gap configuration(s), related UE capability and interruptions, Included definition of release independence aspects.\n\u2022\tNote: The work of FR2 UL gaps includes (NG) EN-DC, NE-DC, NR-DC and SA with leverage across the options suitably defined in the test specifications. \n\u2022\tIntroduce new FR2 CA BW classes and related Rx requirements to support of contiguous downlink aggregated channel BW up to 1600 MHz [RAN4 RF]  \n\n\u2022\tSpecify DC location reporting scheme to cover intra-band UL CA with 2 CCs and more for FR1 and FR2, and intra-band DL CA for FR2. (RAN4, RAN2)\n\n\u2022\tNOTE: No impact on Rel-16 method (uplinkTxDC-TwoCarrierReport-r16)","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":41460,"status":"revised","reservation_date":"2022-08-01 07:51:46","uploaded":"2022-08-09 11:29:37","revisionof":"","revisedto":"R5-225252","release":"Rel-17","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_96_Electronic\/Docs\/R5-224146.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-224197","title":"New WID on UE Conformance - NR QoE management and optimizations for diverse services","source":"Ericsson","contact":"Bo J\u00f6nsson","contact-id":76116,"tdoctype":"WID new","for":"Endorsement","abstract":"QoE Measurement Collection mechanism for streaming has been specified for UTRAN and E-UTRAN. 5G is designed for providing various types of new services, therefore operators have strong demand to continuously upgrade 5G network to provide sufficient good quality of experiences for the corresponding services. \nWith the new emerging 5G services, 5G QoE management collection specifies the mechanism to collect the experience parameters for the eMBB services and the URLLC services, including streaming, MTSI, MBMS, VR, XR, etc.\nSignalling-based activation\/deactivation, management-based activation\/deactivation, QoE measurement handling at RAN overload, multiple QMC support, QoE continuity for intra-RAT mobility, QoE measurement in RRC_INACTIVE, RAN-visible QoE, per-slice QoE measurement, alignment of MDT and QoE measurements were part of the specification in the Rel-17 normative phase.\nThe release 17 work items NR_QoE and NR_QoE-Core are 100% complete at RAN #95e. RAN5 should start an associated work item for testing the feature. \n \n4\tObjective\n4.1\tObjective of Testing part WI\nThe objective of this work item is to define the UE conformance requirements corresponding to the WID on Rel-17 NR_QoE, analyse the test case impact, applicability, test environment, and update the relevant conformance specifications for Rel-17.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":41970,"status":"revised","reservation_date":"2022-08-01 12:30:20","uploaded":"2022-08-09 09:25:24","revisionof":"","revisedto":"R5-225253","release":"Rel-17","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_96_Electronic\/Docs\/R5-224197.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-224431","title":"New WID Enhancement for the 5G Control Plane Steering of Roaming for UE in Connected mode","source":"NTT DOCOMO INC.","contact":"Masahiro Takano","contact-id":96944,"tdoctype":"WID new","for":"Endorsement","abstract":"Control plane Steering of Roaming (CP-SOR) is introduced in 5GS Rel-15 and enhanced in Rel-16. \nIn 5GS, CP-SOR information is provided to the UE over NAS signalling. The home operator can request the UE to acknowledge the successful reception of SOR information by returning an ACK to the Unified Data Management (UDM) \/ Steering of Roaming Application Function (SOR-AF).\nUpon receiving CP-SOR information while the UE is in CONNECTED mode, the UE waits until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive before performing SOR and attempting to obtain service on a higher priority PLMN.\nThe UEs in 5G may stay in connected mode for a rather long time, whole day or longer, without going to idle mode. The HPLMN operator may have means to evaluate what is more convenient to provide the service for the user (e.g., based on their subscription profile, more efficient economically from wholesale perspective, allow users to use dedicated \"economical\" retail plans on specific VPLMN, etc.) and decide which VPLMN is more appropriate for the user to register on. Therefore, new requirements are introduced to allow the HPLMN to enforce the interruption of the ongoing sessions for the sake of performing SOR and moving the UE to another VPLMN to obtain service on a higher priority PLMN.\nThis work item is intended to implement the additional new requirements introduced in Rel-17 for CP-SOR as indicated in TS 22.261 clause 6.30.2.\nConsidering the new requirements for CP-SOR, it is needed to define means to allow the HPLMN to control the timing when to move a UE from connected mode to Idle mode for the purpose of performing SOR taking into consideration the type of ongoing communication\/sessions, with the exception for high priority services.\n4\tObjective\nThe objective of this WI is to propose UE conformance requirements corresponding to Rel-17 Enhancement for the 5G Control Plane Steering of Roaming for UE in Connected mode, analyse the test case impact, applicability, test environment, and update the relevant conformance specifications for Rel-17.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":44310,"status":"revised","reservation_date":"2022-08-04 07:14:21","uploaded":"2022-08-05 05:50:38","revisionof":"","revisedto":"R5-225254","release":"Rel-17","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_96_Electronic\/Docs\/R5-224431.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-224496","title":"New WID on Conformance Test Aspects - Protocol enhancements for Mission Critical Services for Rel-16","source":"NIST","contact":"Jason Kahn","contact-id":75979,"tdoctype":"WID new","for":"Endorsement","abstract":"The demand and need for Mission Critical Services (MCS) on 3GPP-compliant networks is growing. And, the need to enhance MCS functionality is also growing. 3GPP has answered this demand with enhancements to core specifications for MCS. MCS includes Mission Critical Push To Talk (MCPTT), Mission Critical Video (MCVideo), and Mission Critical Data (MCData). RAN5 has completed the UE conformance tests for MCS for Release 15. RAN5 needs to address developing test specifications that relate to Release 16 MCPTT, MCVideo and MCData requirements.\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to provide conformance test specifications for the Rel-16 core requirements for MCPTT, MCVideo and MCData by updating the TS 36.579 family of specifications to Rel-16. The RAT for this Work Item is LTE. Any new test added to TS 36.579-2, TS 36.579-3, TS 36.579-6, and TS 36.579-7 will be included in this work item. It is possible that the core specifications may have included the functionality in releases prior to Rel-16 for a new test case, but it was deemed not necessary to test at the time under previous RAN5 work items. Associated generic test procedures, default message definitions, and other related material for the new test cases will be included in TS 36.579-1. Applicability and other related material for the new test cases will be included in TS 36.579-4. TS 36.579-5 will have inclusions for the new test cases as needed.\nIn general, in SA1, SA2, SA3, SA4 and SA6, functional architecture and information flows to support mission critical communication services are defined which will be reflected in this RAN5 work item. In CT1, CT3, CT4 and CT6, MCPTT, MCVideo, and MCData protocol aspects are defined which, whenever relevant, will be reflected in this RAN5 work item. In CT1, IMS profiles to support MCPTT, MCVideo, and MCData are defined which will be reflected in this RAN5 work item.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":44960,"status":"revised","reservation_date":"2022-08-04 22:00:28","uploaded":"2022-08-08 15:56:32","revisionof":"","revisedto":"R5-225255","release":"Rel-16","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_96_Electronic\/Docs\/R5-224496.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-224702","title":"New WID for IMS Data Channel test","source":"Huawei, Hisilicon","contact":"zhaobing yang","contact-id":80062,"tdoctype":"WID new","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":47020,"status":"withdrawn","reservation_date":"2022-08-05 13:17:28","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-224761","title":"New WID on UE Conformance - User Plane Integrity Protection support for EPC connected architectures","source":"Vodafone GmbH","contact":"Petra Rauer","contact-id":16070,"tdoctype":"WID new","for":"Endorsement","abstract":"In order to provide additional user plane data security (i.e. in addition to user plane data ciphering), SA3 agreed in their WI on \u201cUser Plane Integrity Protection for LTE\u201d to additionally support user plane integrity protection (UPIP) for data transferred over Uu interface for UE connected to EPC. \nAs a result, at TSG RAN #94e in December 2021, RAN agreed a Building Block WID with the objectives of:\n-\tSpecify RAN basic functions for optional support and use of UPIP (at the full data rate supported by the UE) for the EPC connected architectures using NR PDCP (RAN2, RAN3)\nFor this release, it is intended that this feature only applies to EN-DC capable devices.\n\n\nNote: For security related reasons, the UE\u2019s support\/non-support for EPS-UPIP is not sent in the UE Radio Access Capabilities, and instead, it is sent from the UE to the MME in NAS messages and then sent by the MME to the RAN in S1-AP signalling.\n\n          EN-DC capable devices need to support NR-PDCP, and the support of EN-DC is signalled to the eNB within existing R15 UE Radio Access Capabilities. Hence no changes to TS 36.306 were made.\n\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to enable UE conformance testing for Rel-17 User Plane Integrity Protection support for EPC connected architectures corresponding to the WID on UPIP_SEC_LTE-RAN-Core with Unique identifier 941111.\nNOTE 1: While the Rel 17 specifications only support LTE UPIP for EN-DC capable devices, the use of LTE UPIP is applicable to both LTE-only and EN-DC radio configurations for EN-DC capable devices. \n\nIt is intended that the User Plane Integrity Protection is tested at a data rate above that normally used for signalling (i.e. >> 64 kbps), but, owing to the anticipated performance demands on test equipment, it is not expected that User Plane Integrity Protection will be verified by the test equipment at \u201cthe full data rate supported by the UE\u201d.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":47610,"status":"revised","reservation_date":"2022-08-05 14:31:32","uploaded":"2022-08-08 07:50:25","revisionof":"","revisedto":"R5-225256","release":"Rel-17","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_96_Electronic\/Docs\/R5-224761.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-224908","title":"New WID on UE Conformance - Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) requirements for NR UEs","source":"Apple, CAICT, Keysight","contact":"Istvan Szini","contact-id":91966,"tdoctype":"WID new","for":"Endorsement","abstract":"This work item aims to enable the UE conformance testing corresponding to NR MIMO OTA WI analyzing the test cases impact, applicability, and test environment.\nWireless cellular systems based on the fifth generation (5G) are expected to enable superior end-user experience on environments with high traffic, allowing higher downlink and uplink speeds. To enable important innovations in this area Millimeter-wave technology had been deployed. The forefront of the NR deployment is the channel coding and multi-antenna reception featuring Multiple-Input-Multiple-Output (MIMO), therefore, is paramount that 3GPP standardization definitions enable robust MIMO radiated performance that correlates with realistic user case scenarios.\nThe core part of RAN4 MIMO OTA WI has reached 100% completion on RAN#96 with progress being made in the performance part as well. According to the requirements of NR network deployment and performance optimization, it\u2019s justified now to start the work on the corresponding UE conformance test specifications for NR MIMO features in 3GPP RAN WG5 to meet the market requirements in time.\nFR1 and FR2 MIMO OTA activities are relatively independent and with different progress in RAN4. This WI defines two tasks, one dedicated for FR1 and one for  FR2. The progress in RAN4 will be closely monitored, status and expectations will be updated accordingly.\nRAN4 defined preliminary Measurement Uncertainty (MU) to support FR1 MIMO OTA lab alignment effort, it had been agreed by RAN4 that the final definition of MU and Test Tolerances (TT) and test procedures will be handled by RAN5. \nDuring the course of this work item, ongoing communication with 3GPP RAN WG4, CTIA OTA Working Group (MOSG, 5G mm-wave OTA Sub-Working group and MUSG), and CCSA TC9 WG1 shall be maintained to ensure industry coordination on this topic.\n\n4\tObjective\n4.1\tObjective of SI or Core part WI or Testing part WI\nThe objective of this work item is to enable the UE conformance testing corresponding to NR MIMO OTA WI listed under clause 2.2, by analysing the test cases impact, applicability and test environment.  The work item\u2019s outcome shall be captured in TS 38.5xy.\nThis work item will investigate and specify the following aspects:\nTask 1 (FR1 MIMO) and task 2 (FR2 MIMO) shall progress in parallel.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"New Work Item proposals - for intro only","tdoc_agenda_sort_order":49080,"status":"revised","reservation_date":"2022-08-08 00:20:16","uploaded":"2022-08-08 15:41:17","revisionof":"","revisedto":"R5-225257","release":"Rel-17","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_96_Electronic\/Docs\/R5-224908.zip","group":"R5","meeting":"R5-96-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]