[{"name":"S2-2200315","title":"Correction to UE Configuration Update procedure for transparent UE Policy delivery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.2.4.3, Add description that PCF subscribes to AMF to be notified of the reception of the UE Policy container in step 0, and update step 5 accordingly. Figure 4.2.4.3-1, the dashed lines\/boxes of steps 0, 1 and 5 are changed to solid.","secretary_remarks":"r02 + changes agreed. Revised to S2-2201673.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11010,"status":"revised","reservation_date":"2022-01-26 19:42:20","uploaded":"2022-01-28 20:48:14","revisionof":"","revisedto":"S2-2201673","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3341.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200315.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200343","title":"Selecting the same PCF for all UE PDU Sessions to a DNN, S-NSSAI when SSC mode 3 applies","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - A change of SMF for a PDU Session with SSC mode 3 applies transfers the PCF ID for the Old PDU Session ID that is stored in the PDU Session Context at the SMF. - PDU Session establishment includes an additional check in the AMF to set the Same PCF Selection Indication to the SMF, and include the PCF ID stored in the PDU Session Context for this DNN,S-NSSAI.","secretary_remarks":"Revision of (Noted) S2-2108902 from S2#148E. Postponed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10970,"status":"postponed","reservation_date":"2022-01-26 21:30:33","uploaded":"2022-01-28 20:54:50","revisionof":"S2-2108902","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.11.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":3305.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200343.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200344","title":"Selecting the same PCF for all UE PDU Sessions to a DNN, S-NSSAI when SSC mode 3 applies","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: - A change of SMF for a PDU Session with SSC mode 3 applies transfers the PCF ID for the Old PDU Session ID that is stored in the PDU Session Context at the SMF. - PDU Session establishment includes an additional check in the AMF to set the Same PCF Selection Indication to the SMF, and include the PCF ID stored in the PDU Session Context for this DNN,S-NSSAI.","secretary_remarks":"Revision of (Noted) S2-2108903 from S2#148E. Postponed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10980,"status":"postponed","reservation_date":"2022-01-26 21:30:34","uploaded":"2022-01-28 20:54:50","revisionof":"S2-2108903","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":3306.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200344.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200409","title":"Selecting the same PCF when usage monitoring and SSC mode 3 applies","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that upon SSC Mode 3 redirection and a new PDU Session establishment, when the new SMF retrieves the SM Context from the old SMF, the old SMF returns the PCF ID and the SM Policy Association ID to the new SMF. If the old SMF has received one or more Usage Monitoring Key(s) from the PCF (i.e. usage monitoring is active for the PDU Session), the old SMF includes also the 'same PCF' indicator set to true in the response. The new SMF uses the received PCF ID for the SM policy association establishment of the new PDU Session. In this case, the SMF includes the SM Policy Association ID to the SM policy association establishment request and the PCF uses it to correlate request with the old SM policy association. The change of the SMF during the SSC Mode 3 PDU Session redirection is creatly improved in Rel-17 in TS 23.502 CR2549R1 (under eEDGE_5GC), where the old SMF can assist the AMF to re-select a new SMF based on the target DNAI. In Rel-16 this assistance on SMF re-selection is not possible. Therefore also the solution described in this CR is proposed to Rel-17 and onwards, and not to previous releases.","secretary_remarks":"Confirm Spec version used - CR states 17.10.0! Noted","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10990,"status":"noted","reservation_date":"2022-01-27 15:02:21","uploaded":"2022-01-28 13:15:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"},{"winame":" eEDGE_5GC"}],"crnumber":3351.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200409.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200424","title":"Selecting the same PCF when usage monitoring and SSC mode 3 applies","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that an SMF can include an old SM Policy Association ID to the SM policy association establishment request and the PCF uses it to correlate request with the old SM policy association.","secretary_remarks":"Noted","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11000,"status":"noted","reservation_date":"2022-01-27 15:19:45","uploaded":"2022-01-28 13:15:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"},{"winame":" eEDGE_5GC"}],"crnumber":693.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200424.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200682","title":"Alignment of PCC input parameter documentation","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of the parameters that are used in the different procedures and service operations is updated by adding missing parameters documented in 23.503. The references to parameter lists doumented in 23.503 are reduced to the Policy Control Request Triggers. In addition, the description and the terminology is aligned in several places and some misleading references are corrected.","secretary_remarks":"r01 agreed. Revised to S2-2201484, merging S2-2201096 and S2-2200898","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11030,"status":"revised","reservation_date":"2022-01-28 08:05:46","uploaded":"2022-01-28 14:50:10","revisionof":"","revisedto":"S2-2201484","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":3373.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200682.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200683","title":"Clarification of PCC input parameter AF application identifier","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of the PCC input parameter AF application identifier is clarified by listing all possible information it can contain, i.e. an AF identifier, an external application identifier (if the NEF is involved and performs the mapping to the application identifier) or an application identifier (if the AF is configured accordingly).","secretary_remarks":"Postponed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11050,"status":"postponed","reservation_date":"2022-01-28 08:05:47","uploaded":"2022-01-28 14:50:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.3.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":697.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200683.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200736","title":"UP path change notification to the AF","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Issues 1 and 2: In clause 4.3.6.3, if the AF is notified that the UE IP address has changed, the AF needs to create a new AF-session with the PCF, by invoking a _Create operation and using the new IP address of the UE. Whether the AF instance has changed or not does not make a difference to the above; it is proposed that unless the UE IP address has changed, the AF uses _Update operation. Issue 3: The UP path change notification is enhanced by including a 'new PCF ID' parameter. The SMF includes the PCF ID of the new PDU Session of SSC Mode 3 to the late notification. The AF does not need to discover PCF from the BSF, instead the AF uses this PCF ID to send the _Create operation.","secretary_remarks":"r03 agreed. Revised to S2-2201485.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11060,"status":"revised","reservation_date":"2022-01-28 09:31:07","uploaded":"2022-01-28 13:15:04","revisionof":"","revisedto":"S2-2201485","release":"Rel-16","crspec":"23.502","crspecversion":"16.11.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3375.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200736.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200756","title":"UP path change notification to the AF","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Issues 1 and 2: In clause 4.3.6.3, if the AF is notified that the UE IP address has changed, the AF needs to create a new AF-session with the PCF, by invoking a _Create operation and using the new IP address of the UE. Whether the AF instance has changed or not does not make a difference to the above; it is proposed that unless the UE IP address has changed, the AF uses _Update operation. Issue 3: The UP path change notification is enhanced by including a 'new PCF ID' parameter. The SMF includes the PCF ID of the new PDU Session of SSC Mode 3 to the late notification. The AF does not need to discover PCF from the BSF, instead the AF uses this PCF ID to send the _Create operation.","secretary_remarks":"r00 agreed. Revised to S2-2201486.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11080,"status":"revised","reservation_date":"2022-01-28 09:36:46","uploaded":"2022-01-28 13:15:04","revisionof":"","revisedto":"S2-2201486","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3376.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200756.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200842","title":"BSF service update for session binding information update","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding BSF notify AF with session binding information update","secretary_remarks":"Revision of (Noted) S2-2108421 from S2#148E. Postponed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11100,"status":"postponed","reservation_date":"2022-01-28 11:11:35","uploaded":"2022-01-28 12:21:41","revisionof":"S2-2108421","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":673.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200842.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200844","title":"BSF service update for session binding information update","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding BSF notify AF with session binding information update","secretary_remarks":"Revision of (Noted) S2-2108420 from S2#148E. Postponed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11110,"status":"postponed","reservation_date":"2022-01-28 11:20:03","uploaded":"2022-01-28 12:21:41","revisionof":"S2-2108420","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3234.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200844.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201484","title":"Alignment of PCC input parameter documentation","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of the parameters that are used in the different procedures and service operations is updated by adding missing parameters documented in 23.503. The references to parameter lists doumented in 23.503 are reduced to the Policy Control Request Triggers. In addition, the description and the terminology is aligned in several places and some misleading references are corrected.","secretary_remarks":"Revision of S2-2200682r01, merging S2-2201096, merging S2-2201096 and S2-2200898. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11040,"status":"agreed","reservation_date":"2022-02-23 07:38:17","uploaded":"2022-03-01 08:41:21","revisionof":"S2-2200682","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3373.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201484.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201485","title":"UP path change notification to the AF","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Issues 1 and 2: In clause 4.3.6.3, if the AF is notified that the UE IP address has changed, the AF needs to create a new AF-session with the PCF, by invoking a _Create operation and using the new IP address of the UE. Whether the AF instance has changed or not does not make a difference to the above; it is proposed that unless the UE IP address has changed, the AF uses _Update operation.","secretary_remarks":"Revision of S2-2200736r03. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11070,"status":"agreed","reservation_date":"2022-02-23 07:38:18","uploaded":"2022-03-01 08:41:21","revisionof":"S2-2200736","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.11.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3375.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220045","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201485.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201486","title":"UP path change notification to the AF","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: Issues 1 and 2: In clause 4.3.6.3, if the AF is notified that the UE IP address has changed, the AF needs to create a new AF-session with the PCF, by invoking a _Create operation and using the new IP address of the UE. Whether the AF instance has changed or not does not make a difference to the above; it is proposed that unless the UE IP address has changed, the AF uses _Update operation.","secretary_remarks":"Revision of S2-2200756r00. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11090,"status":"agreed","reservation_date":"2022-02-23 07:38:19","uploaded":"2022-03-01 08:41:21","revisionof":"S2-2200756","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":3376.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-220045","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201486.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201673","title":"Correction to UE Configuration Update procedure for transparent UE Policy delivery","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.2.4.3, Add description that PCF subscribes to AMF to be notified of the reception of the UE Policy container in step 0, and update step 5 accordingly. Figure 4.2.4.3-1, the dashed lines\/boxes of steps 0, 1 and 5 are changed to solid.","secretary_remarks":"Revision of S2-2200315r02 + changes. This CR was agreed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11020,"status":"agreed","reservation_date":"2022-02-23 07:39:02","uploaded":"2022-03-01 08:41:20","revisionof":"S2-2200315","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3341.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201673.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]