[{"name":"S2-2105227","title":"LS from CT WG3: LS on Session Management Policy Data per PLMN","source":"CT WG3","contact":"Apostolos Papageorgiou","contact-id":81926,"tdoctype":"LS in","for":"Action","abstract":"In the procedure for SM Policy Association Establishment (TS 23.502 clause 4.16.4), SA WG2 has specified that in LBO, the V-PCF interacts with the UDR of the VPLMN but the retrieval of data using Nudr_DM_Query\/Subscribe from the UDR (or V-UDR) is specified per subscriber, as per the text highlighted below {. . .} In the LBO case, the Session Management Policy Data at the VPLMN cannot be stored per subscriber, since the subscribers of the HPLMN are not managed by the VPLMN, but the VPLMN can store Session Management Policy Data that are applicable to all the subscribers of a certain HPLMN. Although the above highlighted text could imply that the V-PCF can retrieve subscriber related data (which includes Session Management Policy Data) from the V-UDR, the key of Session Management Policy Data in the UDR is the SUPI. Based on the above, CT WG3 would like to ask the following clarification question to SA WG2: Q1. Can the UDR of the VPLMN store PDU Session policy control data per HPLMN? Q2. Is all the PDU Session policy control subscription information (specified in TS 23.503 Table 6.2-2) supported in the LBO scenario?. Action: CT WG3 kindly asks SA WG2 to provide feedback for questions Q1 and Q2 and update accordingly the specifications as necessary.","secretary_remarks":"Revision of postponed S2-2103722 from S2-145E. Response drafted in S2-2105703. Final response in S2-2106560","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11340,"status":"replied to","reservation_date":"2021-06-24 14:38:55","uploaded":"2021-06-25 10:42:11","revisionof":"S2-2103722","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-211469","lsreply":"S2-2106560","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105227.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105243","title":"LS from GSMA 5GJA: LS to 3GPP SA2 on URSP Traffic Descriptor","source":"GSMA 5GJA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Background: The purpose of this LS is to engage on proposed content changes to 3GPP TS23.503, specifically section 6.6.2.1: Structure Description. In particular, the following statements are made in Section 6.6.2.1: Each URSP rule contains a list of Route Selection Descriptors containing one or multiple Route Selection Descriptors each having a different Route Selection Descriptor Precedence value. A Route Selection Descriptor contains one or more of the following components: - DNN Selection: Indicates that the traffic of the matching application shall be routed via a PDU Session supporting any of the included DNNs. It includes one or more DNN(s). When DNN is used in Traffic descriptor, corresponding Route Selection Descriptor of the rule shall not include DNN Selection component. [End TS 23.530 Reference] GSMA 5GJA contends that 'DNN (Data Network Name) requested by the application' is a traffic descriptor that enables a match in the URSP rules. Once the match is identified, how to route it should be flexible. In some cases, the same DNN name can be used in route selector by either not specifying the DNN in the route selection or specify the DNN using the same string. However, in some other cases, MNO's should be able to route that traffic to a PDU session that has a different DNN string. The application owner may prefer to have one version of the application where it always asks for the same DNN string, independent of which MNO will be serving the devices that the app resides. Different MNOs may want to route that app's traffic differently. For example, one MNO may want to route it to a common internet PDU session, while another MNO may want to route it to a PDU session with a DNN name that is different than the DNN string requested by the app. Actions: The GSMA 5GJA task force requests the following adjustments be made to 3GPP TS 23.503: Removal of the second sentence in the bullet specific to DNN selection in Section 6.6.2.1: - DNN Selection: Indicates that the traffic of the matching application shall be routed via a PDU Session supporting any of the included DNNs. It includes one or more DNN(s). When DNN is used in Traffic descriptor, corresponding Route Selection Descriptor of the rule shall not include DNN Selection component. In addition, the following clarifications is proposed to be added to the same bullet point: If a DNN is provided in the Route Selection Descriptor then it must be used, instead of the DNN requested by the application in the traffic descriptor. If there is no DNN in the Route Selection Descriptor, then the UE should use the DNN requested in the traffic descriptor. Thus, the new bullet would read as follows: - DNN Selection: Indicates that the traffic of the matching application shall be routed via a PDU Session supporting any of the included DNNs. It includes one or more DNN(s). If a DNN is provided in the Route Selection Descriptor then it must be used, instead of the DNN requested by the application in the traffic descriptor. If there is no DNN in the Route Selection Descriptor, then the UE should use the DNN requested in the traffic descriptor","secretary_remarks":"Revision of postponed S2-2103774 from S2-145E. Responses drafted in S2-2105422 and S2-2106316. Final response in S2-2106556","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11210,"status":"replied to","reservation_date":"2021-06-24 14:38:56","uploaded":"2021-06-25 10:42:11","revisionof":"S2-2103774","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"5GJA16_109r2","lsreply":"S2-2106556","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105243.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105255","title":"LS from CT WG3: LS on Clarifications on the offline charging only indication","source":"CT WG3","contact":"Abdessamad EL MOATAMID","contact-id":80517,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is discussing and specifying the support of the 'PDU session with offline charging only' indication mechanism and needs in this sense further clarifications on the associated stage 2 requirements in TS 23.503 and TS 32.255 with regards to the interactions of this mechanism with the 'default charging method' mechanism. Indeed, the provisioning by the PCF of the 'PDU session with offline charging only' indication clearly means that the online charging method shall never be used for any PCC rule of the PDU session and shall not be provisioned by the PCF as a default charging method for the PDU session. It may also be interpreted as the offline charging method also does not need to be provisioned by the PCF neither as a default charging method for the PDU session nor as the charging method for any PCC rule of the PDU session because the 'PDU session with offline charging only' indication already mandates the usage of offline charging for the PDU session. There are different and conflicting views on whether this last point is correct or not in CT WG3. Therefore, CT WG3 would like to kindly ask SA WG2 and SA WG5 to study and answer the following questions: Question 1: When the 'PDU session with offline charging only' indication is provisioned by the PCF for a PDU session within the SM Policy Decision to indicate that the online charging method shall never be used for any PCC rule of the PDU session, does this also mean that the offline charging method shall be used for all the PCC rules of the PDU session? Question 2: If the answer to Question 1 is yes, then should the PCF be allowed to also provision the offline charging method as a default charging method for the PDU session when it provisions the 'PDU session with offline charging only' indication? In other words, does the provisioning by the PCF of the 'PDU session with offline charging only' indication mean that the offline charging method does not need to be provisioned by the PCF as the default charging method for the PDU session or as the charging method for any PCC rule of the PDU session? Question 3: Can the offline charging only indication be locally configured in the SMF and apply if no charging method is provided by the PCF (e.g. local policies indicate so)? If the answer is yes, then how to handle that the PCF may not be aware of it and would hence not be able to enforce that for all the PCC rules of the PDU session the online charging method cannot be set?. Action: CT WG3 kindly asks SA WG2 to answer the above questions and modify the SA WG2 specifications accordingly, where appropriate and if necessary.","secretary_remarks":"Response drafted in S2-2106150. Final response in S2-2106558","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11290,"status":"replied to","reservation_date":"2021-06-24 14:38:57","uploaded":"2021-06-25 10:42:11","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"","lsoriginalls":"C3-213546","lsreply":"S2-2106558","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105255.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105421","title":"DNN in URSP Traffic Descriptor and Route Selection Descriptor","source":"Ericsson, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of the limitation to not allow DNN in both Traffic Descriptor and Route Selection Descriptor. The UE shall use the DNN Selection in Route Selection Descriptor when DNN component is also in Traffic Descriptor.","secretary_remarks":"r01 + CC#2 changes agreed. Revised to S2-2106557, merging S2-2106330","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11240,"status":"revised","reservation_date":"2021-08-01 22:27:47","uploaded":"2021-08-10 21:47:17","revisionof":"","revisedto":"S2-2106557","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":607.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105421.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105422","title":"[DRAFT] LS reply to GSMA on URSP Traffic Descriptor","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS reply to GSMA on URSP Traffic Descriptor","secretary_remarks":"Response to S2-2105243. Revised to S2-2106556, merging S2-2106316","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11220,"status":"revised","reservation_date":"2021-08-01 22:27:48","uploaded":"2021-08-10 21:47:17","revisionof":"","revisedto":"S2-2106556","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105422.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105700","title":"Corrections on the AF related identifier","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Align the AF ID\/AF identity with AF Identifier.","secretary_remarks":"Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11390,"status":"agreed","reservation_date":"2021-08-09 13:49:04","uploaded":"2021-08-10 15:12:16","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.1.1","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":3064.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-210936","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105700.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105701","title":"Corrections on the AF related identifier","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the AF Application Identifier. Add the AF Identifier and Application Identifier. Align the AF ID with AF Identifier. Harmonize the terminology for the ASP Identifier.","secretary_remarks":"Revised to S2-2106562.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11400,"status":"revised","reservation_date":"2021-08-09 13:49:06","uploaded":"2021-08-10 15:12:16","revisionof":"","revisedto":"S2-2106562","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":2958.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105701.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105702","title":"Corrections on the AF related identifier","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the AF Application Identifier. Add the AF Identifier and Application Identifier.","secretary_remarks":"Revised to S2-2106563.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11420,"status":"revised","reservation_date":"2021-08-09 13:49:07","uploaded":"2021-08-10 15:12:16","revisionof":"","revisedto":"S2-2106563","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":619.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105702.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105703","title":"[DRAFT] LS Reply on Session Management Policy Data per PLMN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This contribution replies CT WG3 with some Clarification for SM related policy in roaming scenario.","secretary_remarks":"Response to S2-2105227. Revised to S2-2106560.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11350,"status":"revised","reservation_date":"2021-08-09 13:49:08","uploaded":"2021-08-10 15:12:16","revisionof":"","revisedto":"S2-2106560","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"SBIProtoc17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105703.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105704","title":"Clarification on Session Management Policy Data per PLMN","source":"Huawei, HiSilicon, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Some Notes are added to clarify that PDU Session policy control data and Remaining allowed Usage data are not available in V-UDR, and V-PCF uses locally configured policies according to the roaming agreement with the HPLMN operator.","secretary_remarks":"Revised to S2-2106561.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11370,"status":"revised","reservation_date":"2021-08-09 13:49:08","uploaded":"2021-08-10 15:12:16","revisionof":"","revisedto":"S2-2106561","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":2959.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2105704.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106142","title":"Usage monitoring for a user in SSC mode #3","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.3.5.2, it is clarified that SMF shall not include 'SMF Reallocation requested indication' in Namf_Communication_N1N2MessageTransfer, if usage monitoring is activated by the PCF.","secretary_remarks":"Postponed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11440,"status":"postponed","reservation_date":"2021-08-10 10:07:40","uploaded":"2021-08-10 10:17:14","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.9.0","workitem":[{"winame":"TEI16"}],"crnumber":3041.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106142.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106143","title":"Usage monitoring for a user in SSC mode #3","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: In clause 4.3.5.2, it is clarified that SMF shall not include 'SMF Reallocation requested indication' in Namf_Communication_N1N2MessageTransfer, if usage monitoring is activated by the PCF.","secretary_remarks":"Postponed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11450,"status":"postponed","reservation_date":"2021-08-10 10:07:42","uploaded":"2021-08-10 10:17:14","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"TEI16"}],"crnumber":3042.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106143.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106150","title":"[DRAFT] LS Reply on the offline charging only indication","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"This contribution clarifies the offline charging only indication.","secretary_remarks":"Response to S2-2105255. Revised to S2-2106558.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11300,"status":"revised","reservation_date":"2021-08-10 10:29:18","uploaded":"2021-08-10 15:07:26","revisionof":"","revisedto":"S2-2106558","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106150.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106151","title":"Clarifications on offline charging only indication","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Some clarifications are added about offline charging only indicator .","secretary_remarks":"Revised to S2-2106559.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11320,"status":"revised","reservation_date":"2021-08-10 10:29:19","uploaded":"2021-08-10 15:07:26","revisionof":"","revisedto":"S2-2106559","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":639.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106151.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106283","title":"Indication of default URSP rule not applicable for the application","source":"MediaTek Inc., Google, Intel","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the application indicates that the default URSP is not applicable for the application, the UE shall not evaluate the default URSP rule or associate the application with the PDU session of the default URSP rule.","secretary_remarks":"Noted","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11280,"status":"noted","reservation_date":"2021-08-10 12:50:06","uploaded":"2021-08-10 17:15:54","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":645.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106283.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106316","title":"[DRAFT] Reply LS from GSMA 5GJA on URSP Traffic Descriptor","source":"China Telecommunications","contact":"Pinghui Chen","contact-id":71975,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA 5GJA.","secretary_remarks":"Response to S2-2105243. Merged into S2-2106556","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11260,"status":"merged","reservation_date":"2021-08-10 14:07:29","uploaded":"2021-08-10 14:21:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GJA","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106316.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106330","title":"DNN Selection and match in URSP","source":"China Telecom","contact":"Pinghui Chen","contact-id":71975,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that When DNN is used in Traffic descriptor, corresponding Route Selection Descriptor of the rule may include DNN selection component, and the DNN in the route selection can be the same DNN or different DNN name from the DNN used in Traffic Descriptor.","secretary_remarks":"Merged into S2-2106557","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11270,"status":"merged","reservation_date":"2021-08-10 14:12:39","uploaded":"2021-08-10 14:21:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":646.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106330.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106556","title":"LS reply to GSMA on URSP Traffic Descriptor","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA NG 5GJA, CT WG1. Attachments: CR 0607 TS 23.503","secretary_remarks":"Revision of S2-2105422r01, merging S2-2106316. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11230,"status":"approved","reservation_date":"2021-08-23 08:42:24","uploaded":"2021-09-01 14:31:23","revisionof":"S2-2105422","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2105243","lsto":"GSMA NG 5GJA, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106556.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106557","title":"DNN in URSP Traffic Descriptor and Route Selection Descriptor","source":"Ericsson, AT&T, Deutsche Telekom, China Telecom, Convida Wireless, Nokia, Nokia Shangai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of the limitation to not allow DNN in both Traffic Descriptor and Route Selection Descriptor. The UE shall use the DNN Selection in Route Selection Descriptor when DNN component is also in Traffic Descriptor.","secretary_remarks":"Revision of S2-2105421r01 + CC#2 changes, merging S2-2106330. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11250,"status":"agreed","reservation_date":"2021-08-23 08:42:25","uploaded":"2021-09-01 14:31:23","revisionof":"S2-2105421","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":607.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-210936","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106557.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106558","title":"LS Reply on the offline charging only indication","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG5. CC: CT WG3","secretary_remarks":"Revision of S2-2106150r06. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11310,"status":"approved","reservation_date":"2021-08-23 08:42:26","uploaded":"2021-09-01 14:31:23","revisionof":"S2-2106150","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"en5GPccSer17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2105255","lsto":"CT WG3","Cc":"SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106558.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106559","title":"Clarifications on offline charging only indication","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Some clarifications are added about offline charging only indicator .","secretary_remarks":"Revision of S2-2106151r02. CC#2: Endorsed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11330,"status":"endorsed","reservation_date":"2021-08-23 08:42:26","uploaded":"2021-09-01 14:31:23","revisionof":"S2-2106151","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":639.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106559.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106560","title":"LS Reply on Session Management Policy Data per PLMN","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. Attachments: TS 23.502 CR 2959","secretary_remarks":"Revision of S2-2105703r01. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11360,"status":"approved","reservation_date":"2021-08-23 08:42:27","uploaded":"2021-09-01 14:31:23","revisionof":"S2-2105703","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"SBIProtoc17"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2105227","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106560.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106561","title":"Clarification on Session Management Policy Data per PLMN","source":"Huawei, HiSilicon, Ericsson, China Telecom","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Some Notes are added to clarify that PDU Session policy control data and Remaining allowed Usage data for monitoring control are not available in V-UDR, and V-PCF uses locally configured policies according to the roaming agreement with the HPLMN operator.","secretary_remarks":"Revision of S2-2105704r01. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11380,"status":"agreed","reservation_date":"2021-08-23 08:42:27","uploaded":"2021-09-01 14:31:23","revisionof":"S2-2105704","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2959.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210936","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106561.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106562","title":"Corrections on the AF related identifier","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the AF Identifier and Application Identifier. Align the AF ID with AF Identifier. Harmonize the terminology for the ASP Identifier.","secretary_remarks":"Revision of S2-2105701r02. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11410,"status":"agreed","reservation_date":"2021-08-23 08:42:28","uploaded":"2021-09-01 14:31:23","revisionof":"S2-2105701","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2958.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210936","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106562.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2106563","title":"Corrections on the AF related identifier","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifications on the use of the AF Application Identifier","secretary_remarks":"Revision of S2-2105702r07. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11430,"status":"agreed","reservation_date":"2021-08-23 08:42:29","uploaded":"2021-09-01 14:31:23","revisionof":"S2-2105702","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":619.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210936","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_146E_Electronic_2021-08\/Docs\/S2-2106563.zip","group":"S2","meeting":"S2-146-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]