[{"name":"S2-2311975","title":"LS from SA WG5: Reply LS on CHF Logic Realization wrt\/ Spending Limits functionality","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 thanks SA WG2 for the LS reply on CHF Logic Realization with respect to Spending Limits functionality. SA WG5 can confirm the CHF selection specified under TS 32.255 gives the priority to CHF Address(es) provided by the PCF at PDU session establishment to enable the same CHF to be selected for SMF and PCF due to Spending Limits. SA WG5 can also confirm the CHF selection by AMF, specified under TS 32.256 includes the option CHF address(es) provided by the PCF as part of Access and mobility policy control information , amongst other options (which one to use is per Operator policy). Meaning it is possible for the AMF not to select the same CHF as the one received from the PCF for the UE if any. Since UE mobility and connection (e.g. registrations) charging from AMF to CHF is an event-based approach, potential associated policy counter(s), if used by the PCF for policy decision enforcement in AMF, would be relevant only for subsequent UE mobility and connection(s) in the same or different AMF. For such reason SA WG5 sees no need to mandate having the same CHF for Policy decision. Action: SA WG5 kindly requests SA WG2 to take the above information into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23530,"status":"noted","reservation_date":"2023-10-18 16:41:40","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-236896","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311975.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312083","title":"Dynamically store identifiers and statuses of the policy counters in UDR","source":"Oracle, Verizon UK Ltd.","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: There is a benefit for an operator to store in the UDR a List of Policy Counters and their statuses for a subscriber or\/and for a PDU Session. This is already (partially) captured in clause 6.1.1.4, however it is not defined in clause 6.2.1.3. Hence there is a need to align these two clauses. In addition, there is a benefit for an operator to allow the PCF to adjust the list dynamically (e.g. based on policies, network conditions, subscription, other trigerrs such as Time of Day. Location, serving PLMN to name a few) either internally or\/and in the UDR. For example, if a user tops up their SL account, some restrictive PCs may not be relevant anymore for the subscriber. This will allow the PCF to keep SL related context between different registration periods or in case of a relocation with a new PCF. Furthermore, in the case of a new registration, the PCF receives from the AMF an AM Policy association establsihment request. Being able to download the list of PCs and their latest statuses from the UDR, can allow the PCF to respond to the AM Policy association establsihment request already before establishing an Nchf association with the CHF. This is also known as asynchronous mode. It can shorten registration time for the UE, and consequently provide a better experience for the subscriber. Similar considerations can be applicable to SM and\/or UE association establishments and their respective SL and respective policies. Consequently, this CR proposes to add SL info to SM, AM and UE policy subscription in the UDR and allow PCF to dynamically change it. Below are detailed examples for situation before and after incorporation of the logic of this CR. (The example is AM related. However, it can be replicated with minor adjustments to SM or\/and UE associations) Current behavior (ie before incorporation of this CR) - synchromnous mode ========================================================== AMF sends AMPolicyAssociationCreate. PCF sends GET:AMPolicyData to UDR. PCF sends N28 SubscribeRequest to CHF. PCF waits for N28 SubscribeResponse. PCF returns AMPolicyAssociationResponse to AMF considering N28 response. Summary: Long procedure time, no UDR-SL backup in case CHF is unavailable. Current behavior (ie before incorporation of this CR) - assynchromnous mode ========================================================== AMF sends AMPolicyAssociationCreate. PCF sends GET:AMPolicyData to UDR. PCF sends N28 SubscribeRequest to CHF. PCF makes policy decision based on AMPolicyData, without considering N28 response. PCF return AMPolicyAssociationResponse to AMF without waiting for N28 SubscribeResponse. When N28 SubscribeResponse is received, PCF may send AMPolicy Update-Notify to AMF (if needed). If CHF is not available, then the policy decision is made without any CHF input. Summary: Short procedure time, Update-Notify may have to be sent though, no UDR-SL backup in case CHF is unavailable. Future behavior (ie after incorporation of this CR) - assynchromnous mode ========================================================= UE de-registers, AMF sends AMPolicyAssociation Delete. AM-PCF stores Spending Limit info into UDR. AMF sends AMPolicyAssociation Create. PCF sends GET:AMPolicyData to UDR; UDR return both AMPolicyData and SpendingLimit info. PCF sends N28 SubscribeRequest to CHF. PCF will make policy decision based on both AMPolicyData and SL info from UDR. PCF return AMPolicyAssociationResponse to AMF without waiting for N28 SubscribeResponse. When N28 SubscribeResponse is received, in majority of case, PCF does not need to send AMPolicy Update-Notify to AMF, since SL info stored in UDR during previous registration shall be normally the same as what stored in CHF. when CHF is not available, PCF can still make policy decisions based on the most recent SL info stored in UDR, which may not be the latest. but in majority of the cases, SL stored in UDR is the same as N28 response. In mid of Registration, if CHF notifies PCF that","secretary_remarks":"Agreed in parallel session. Revised in parallel session to S2-2313530.","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23540,"status":"revised","reservation_date":"2023-01-11 04:50:41","uploaded":"2023-11-02 22:11:03","revisionof":"","revisedto":"S2-2313530","release":"Rel-18","crspec":"23.503","crspecversion":"18.3.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1196.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312083.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312282","title":"Spending Limits for AM and UE Policies in the 5GC","source":"Huawei, Oracle, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates for selection and discovery of CHF by the PCF for a UE","secretary_remarks":"Revised in parallel session to S2-2313335.","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23580,"status":"revised","reservation_date":"2023-02-11 08:46:38","uploaded":"2023-11-03 16:38:12","revisionof":"","revisedto":"S2-2313335","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":5104.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312282.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.3.11","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312283","title":"Spending Limits for AM and UE Policies in the 5GC","source":"Huawei, Oracle, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description refering to Subscriber spending limits control in clause 6.1.1.4 and also add the description on providing CHF address to AMF to align with SA WG5.","secretary_remarks":"Revised in parallel session to S2-2313334.","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23600,"status":"revised","reservation_date":"2023-02-11 08:46:39","uploaded":"2023-11-03 16:38:12","revisionof":"","revisedto":"S2-2313334","release":"Rel-18","crspec":"23.503","crspecversion":"18.3.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1210.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312283.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.1.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313334","title":"Spending Limits for AM and UE Policies in the 5GC","source":"Huawei, Oracle, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description refering to Subscriber spending limits control in clause 6.1.1.4 and also add the description on providing CHF address to AMF to align with SA WG5.","secretary_remarks":"Revision of S2-2312283. Agreed in parallel session. Block approved","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23610,"status":"agreed","reservation_date":"2023-11-16 19:55:10","uploaded":"2023-11-20 12:31:10","revisionof":"S2-2312283","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.3.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1210.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-231248","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313334.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.1.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313335","title":"Spending Limits for AM and UE Policies in the 5GC","source":"Huawei, Oracle, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates for selection and discovery of CHF by the PCF for a UE","secretary_remarks":"Revision of S2-2312282. Agreed in parallel session. Block approved","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23590,"status":"agreed","reservation_date":"2023-11-16 19:55:11","uploaded":"2023-11-20 12:31:10","revisionof":"S2-2312282","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":5104.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-231248","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313335.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.3.11","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313530","title":"Dynamically store identifiers and statuses of the policy counters in UDR","source":"Oracle, Verizon UK Ltd.","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: There is a benefit for an operator to store in the UDR a List of Policy Counters and their statuses for a subscriber or\/and for a PDU Session. This is already (partially) captured in clause 6.1.1.4, however it is not defined in clause 6.2.1.3. Hence there is a need to align these two clauses. In addition, there is a benefit for an operator to allow the PCF to adjust the list dynamically (e.g. based on policies, network conditions, subscription, other trigerrs such as Time of Day. Location, serving PLMN to name a few) either internally or\/and in the UDR. For example, if a user tops up their SL account, some restrictive PCs may not be relevant anymore for the subscriber. This will allow the PCF to keep SL related context between different registration periods or in case of a relocation with a new PCF. Furthermore, in the case of a new registration, the PCF receives from the AMF an AM Policy association establsihment request. Being able to download the list of PCs and their latest statuses from the UDR, can allow the PCF to respond to the AM Policy association establsihment request already before establishing an Nchf association with the CHF. This is also known as asynchronous mode. It can shorten registration time for the UE, and consequently provide a better experience for the subscriber. Similar considerations can be applicable to SM and\/or UE association establishments and their respective SL and respective policies. Consequently, this CR proposes to add SL info to SM, AM and UE policy subscription in the UDR and allow PCF to dynamically change it. Below are detailed examples for situation before and after incorporation of the logic of this CR. (The example is AM related. However, it can be replicated with minor adjustments to SM or\/and UE associations) Current behavior (ie before incorporation of this CR) - synchromnous mode ========================================================== AMF sends AMPolicyAssociationCreate. PCF sends GET:AMPolicyData to UDR. PCF sends N28 SubscribeRequest to CHF. PCF waits for N28 SubscribeResponse. PCF returns AMPolicyAssociationResponse to AMF considering N28 response. Summary: Long procedure time, no UDR-SL backup in case CHF is unavailable. Current behavior (ie before incorporation of this CR) - assynchromnous mode ========================================================== AMF sends AMPolicyAssociationCreate. PCF sends GET:AMPolicyData to UDR. PCF sends N28 SubscribeRequest to CHF. PCF makes policy decision based on AMPolicyData, without considering N28 response. PCF return AMPolicyAssociationResponse to AMF without waiting for N28 SubscribeResponse. When N28 SubscribeResponse is received, PCF may send AMPolicy Update-Notify to AMF (if needed). If CHF is not available, then the policy decision is made without any CHF input. Summary: Short procedure time, Update-Notify may have to be sent though, no UDR-SL backup in case CHF is unavailable. Future behavior in those deployments where this feature is available (ie after incorporation of this CR) - assynchromnous mode ========================================================= UE de-registers, AMF sends AMPolicyAssociation Delete. AM-PCF stores Spending Limit info into UDR. AMF sends AMPolicyAssociation Create. PCF sends GET:AMPolicyData to UDR; UDR return both AMPolicyData and SpendingLimit info. PCF sends N28 SubscribeRequest to CHF. PCF will make policy decision based on both AMPolicyData and SL info from UDR. PCF return AMPolicyAssociationResponse to AMF without waiting for N28 SubscribeResponse. When N28 SubscribeResponse is received, in majority of case, PCF does not need to send AMPolicy Update-Notify to AMF, since SL info stored in UDR during previous registration shall be normally the same as what stored in CHF. when CHF is not available, PCF can still make policy decisions based on the most recent SL info stored in UDR, which may not be the latest. but in majority of the cases, SL stored in UDR is the same as N28 respon","secretary_remarks":"Revision of S2-2312083. Revised in parallel session to S2-2313532.","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23550,"status":"revised","reservation_date":"2023-11-16 19:57:13","uploaded":"2023-11-20 12:31:12","revisionof":"S2-2312083","revisedto":"S2-2313532","release":"Rel-18","crspec":"23.503","crspecversion":"18.3.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1196.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313530.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313532","title":"Dynamically store identifiers and statuses of the policy counters in UDR","source":"Oracle, Verizon UK Ltd.","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: There is a benefit for an operator to store in the UDR a List of Policy Counters and their statuses for a subscriber or\/and for a PDU Session. This is already (partially) captured in clause 6.1.1.4, however it is not defined in clause 6.2.1.3. Hence there is a need to align these two clauses. In addition, there is a benefit for an operator to allow the PCF to adjust the list dynamically (e.g. based on policies, network conditions, subscription, other trigerrs such as Time of Day. Location, serving PLMN to name a few) either internally or\/and in the UDR. For example, if a user tops up their SL account, some restrictive PCs may not be relevant anymore for the subscriber. This will allow the PCF to keep SL related context between different registration periods or in case of a relocation with a new PCF. Furthermore, in the case of a new registration, the PCF receives from the AMF an AM Policy association establsihment request. Being able to download the list of PCs and their latest statuses from the UDR, can allow the PCF to respond to the AM Policy association establsihment request already before establishing an Nchf association with the CHF. This is also known as asynchronous mode. It can shorten registration time for the UE, and consequently provide a better experience for the subscriber. Similar considerations can be applicable to SM and\/or UE association establishments and their respective SL and respective policies. Consequently, this CR proposes to add SL info to SM, AM and UE policy subscription in the UDR and allow PCF to dynamically change it. Below are detailed examples for situation before and after incorporation of the logic of this CR. (The example is AM related. However, it can be replicated with minor adjustments to SM or\/and UE associations) Current behavior (ie before incorporation of this CR) - synchromnous mode ========================================================== AMF sends AMPolicyAssociationCreate. PCF sends GET:AMPolicyData to UDR. PCF sends N28 SubscribeRequest to CHF. PCF waits for N28 SubscribeResponse. PCF returns AMPolicyAssociationResponse to AMF considering N28 response. Summary: Long procedure time, no UDR-SL backup in case CHF is unavailable. Current behavior (ie before incorporation of this CR) - assynchromnous mode ========================================================== AMF sends AMPolicyAssociationCreate. PCF sends GET:AMPolicyData to UDR. PCF sends N28 SubscribeRequest to CHF. PCF makes policy decision based on AMPolicyData, without considering N28 response. PCF return AMPolicyAssociationResponse to AMF without waiting for N28 SubscribeResponse. When N28 SubscribeResponse is received, PCF may send AMPolicy Update-Notify to AMF (if needed). If CHF is not available, then the policy decision is made without any CHF input. Summary: Short procedure time, Update-Notify may have to be sent though, no UDR-SL backup in case CHF is unavailable. Future behavior in those deployments where this feature is available (ie after incorporation of this CR) - assynchromnous mode ========================================================= UE de-registers, AMF sends AMPolicyAssociation Delete. AM-PCF stores Spending Limit info into UDR. AMF sends AMPolicyAssociation Create. PCF sends GET:AMPolicyData to UDR; UDR return both AMPolicyData and SpendingLimit info. PCF sends N28 SubscribeRequest to CHF. PCF will make policy decision based on both AMPolicyData and SL info from UDR. PCF return AMPolicyAssociationResponse to AMF without waiting for N28 SubscribeResponse. When N28 SubscribeResponse is received, in majority of case, PCF does not need to send AMPolicy Update-Notify to AMF, since SL info stored in UDR during previous registration shall be normally the same as what stored in CHF. when CHF is not available, PCF can still make policy decisions based on the most recent SL info stored in UDR, which may not be the latest. but in majority of the cases, SL stored in UDR is the same as N28 respon","secretary_remarks":"Revision of S2-2313530. Agreed in parallel session. Revised in parallel session to S2-2313811.","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23560,"status":"revised","reservation_date":"2023-11-16 19:57:14","uploaded":"2023-11-20 12:31:12","revisionof":"S2-2313530","revisedto":"S2-2313811","release":"Rel-18","crspec":"23.503","crspecversion":"18.3.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1196.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313532.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313811","title":"Dynamically store identifiers and statuses of the policy counters in UDR","source":"Oracle, Verizon UK Ltd.","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: There is a benefit for an operator to store in the UDR a List of Policy Counters and their statuses for a subscriber or\/and for a PDU Session. This is already (partially) captured in clause 6.1.1.4, however it is not defined in clause 6.2.1.3. Hence there is a need to align these two clauses. In addition, there is a benefit for an operator to allow the PCF to adjust the list dynamically (e.g. based on policies, network conditions, subscription, other trigerrs such as Time of Day. Location, serving PLMN to name a few) either internally or\/and in the UDR. For example, if a user tops up their SL account, some restrictive PCs may not be relevant anymore for the subscriber. This will allow the PCF to keep SL related context between different registration periods or in case of a relocation with a new PCF. Furthermore, in the case of a new registration, the PCF receives from the AMF an AM Policy association establsihment request. Being able to download the list of PCs and their latest statuses from the UDR, can allow the PCF to respond to the AM Policy association establsihment request already before establishing an Nchf association with the CHF. This is also known as asynchronous mode. It can shorten registration time for the UE, and consequently provide a better experience for the subscriber. Similar considerations can be applicable to SM and\/or UE association establishments and their respective SL and respective policies. Consequently, this CR proposes to add SL info to SM, AM and UE policy subscription in the UDR and allow PCF to dynamically change it. Below are detailed examples for situation before and after incorporation of the logic of this CR. (The example is AM related. However, it can be replicated with minor adjustments to SM or\/and UE associations) Current behavior (ie before incorporation of this CR) - synchromnous mode ========================================================== AMF sends AMPolicyAssociationCreate. PCF sends GET:AMPolicyData to UDR. PCF sends N28 SubscribeRequest to CHF. PCF waits for N28 SubscribeResponse. PCF returns AMPolicyAssociationResponse to AMF considering N28 response. Summary: Long procedure time, no UDR-SL backup in case CHF is unavailable. Current behavior (ie before incorporation of this CR) - assynchromnous mode ========================================================== AMF sends AMPolicyAssociationCreate. PCF sends GET:AMPolicyData to UDR. PCF sends N28 SubscribeRequest to CHF. PCF makes policy decision based on AMPolicyData, without considering N28 response. PCF return AMPolicyAssociationResponse to AMF without waiting for N28 SubscribeResponse. When N28 SubscribeResponse is received, PCF may send AMPolicy Update-Notify to AMF (if needed). If CHF is not available, then the policy decision is made without any CHF input. Summary: Short procedure time, Update-Notify may have to be sent though, no UDR-SL backup in case CHF is unavailable. Future behavior in those deployments where this feature is available (ie after incorporation of this CR) - assynchromnous mode ========================================================= UE de-registers, AMF sends AMPolicyAssociation Delete. AM-PCF stores Spending Limit info into UDR. AMF sends AMPolicyAssociation Create. PCF sends GET:AMPolicyData to UDR; UDR return both AMPolicyData and SpendingLimit info. PCF sends N28 SubscribeRequest to CHF. PCF will make policy decision based on both AMPolicyData and SL info from UDR. PCF return AMPolicyAssociationResponse to AMF without waiting for N28 SubscribeResponse. When N28 SubscribeResponse is received, in majority of case, PCF does not need to send AMPolicy Update-Notify to AMF, since SL info stored in UDR during previous registration shall be normally the same as what stored in CHF. when CHF is not available, PCF can still make policy decisions based on the most recent SL info stored in UDR, which may not be the latest. but in majority of the cases, SL stored in UDR is the same as N28 respon","secretary_remarks":"Revision of S2-2313532. Agreed in parallel session. Block approved","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":23570,"status":"agreed","reservation_date":"2023-11-20 10:54:34","uploaded":"2023-11-20 12:41:11","revisionof":"S2-2313532","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.3.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1196.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-231248","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313811.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400187","title":"CHF discovery and selection, alignment with 23.502","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Whether the AMF and the PCF connected to the same CHF or not is an operator policies. Only if the operator policies in the PCF indicates that the CHF selected by the PCF and the AMF are the same CHF, then the PCF provides the selected C","secretary_remarks":"Merged into S2-2401573","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":17800,"status":"merged","reservation_date":"2024-10-01 19:43:57","uploaded":"2024-01-12 21:01:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.4.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1238.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400187.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400384","title":"A fix for Spending Limits for AM and UE Policies in the 5GC","source":"Oracle, Ericsson","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add to the PCF for the UE the ability to provide the selected CHF address(es) to the AMF via Npcf_UEPolicyControl service, i.e during UE Policy Association. In addition, define a new proper structure that will carry the selected CHF add","secretary_remarks":"r02 Agreed. Revised to S2-2401573, merging S2-2400187","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":17810,"status":"revised","reservation_date":"2024-11-01 16:21:25","uploaded":"2024-01-11 23:48:12","revisionof":"","revisedto":"S2-2401573","release":"Rel-18","crspec":"23.503","crspecversion":"18.4.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1246.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400384.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.1.4, 6.5, 6.6.X(New)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400385","title":"Spending Limits for AM and UE Policies in the 5GC","source":"Oracle, Ericsson","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add to the PCF for the UE the ability to provide the selected CHF address(es) to the AMF via Npcf_UEPolicyControl service, i.e during UE Policy Association. In addition, reference a new proper structure that will carry the selected CHF","secretary_remarks":"r01 Agreed. Revised to S2-2401574.","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":17830,"status":"revised","reservation_date":"2024-11-01 16:31:09","uploaded":"2024-01-11 23:48:12","revisionof":"","revisedto":"S2-2401574","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":5229.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400385.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.3.11","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2400687","title":"Corrections for spending limit information stored in UDR","source":"Huawei, HiSilicon, Oracle","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that only the relevant policy counter identifiers and policy counter statuses are stored. Some wording improvements for the general description on spending limits and the tables containing the subscription information.","secretary_remarks":"Approved","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":17850,"status":"agreed","reservation_date":"2024-12-01 07:50:58","uploaded":"2024-01-12 16:53:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.4.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1252.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-240136","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2400687.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.1.4, 6.2.1.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401573","title":"A fix for Spending Limits for AM and UE Policies in the 5GC","source":"Oracle, Ericsson","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add to the PCF for the UE the ability to provide the selected CHF address(es) to the AMF via Npcf_UEPolicyControl service, i.e during UE Policy Association. In addition, define a new proper structure that will carry the selected CHF add","secretary_remarks":"Revision of S2-2400384r02, merging S2-2400187. Approved","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":17820,"status":"agreed","reservation_date":"2024-01-28 14:03:28","uploaded":"2024-01-31 09:11:14","revisionof":"S2-2400384","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.4.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":1246.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-240136","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401573.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2401574","title":"Spending Limits for AM and UE Policies in the 5GC","source":"Oracle, Ericsson","contact":"Uri Baniel","contact-id":58644,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add to the PCF for the UE the ability to provide the selected CHF address(es) to the AMF via Npcf_UEPolicyControl service, i.e during UE Policy Association. In addition, reference a new proper structure that will carry the selected CHF","secretary_remarks":"Revision of S2-2400385r01. Approved","agenda_item_sort_order":104,"ainumber":"9.32","ainame":"Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)","tdoc_agenda_sort_order":17840,"status":"agreed","reservation_date":"2024-01-28 14:03:29","uploaded":"2024-01-31 09:11:14","revisionof":"S2-2400385","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.4.0","workitem":[{"winame":"TEI18_SLAMUP"}],"crnumber":5229.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-240136","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160AHE_Electronic_2024-01\/Docs\/S2-2401574.zip","group":"S2","meeting":"S2-160-Ad Hoc-e","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.3.11","crsinpack":null,"crsinpacknumber":0}]