WO2025038015A1

WO2025038015A1 - Usage of policy counters based on network slice information

Info

Publication number: WO2025038015A1
Application number: PCT/SE2023/051020
Authority: WO
Inventors: Ruben IBERNON; Ignacio RIVAS MOLINA; Annika ÅHLBERG
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2023-08-17
Filing date: 2023-10-13
Publication date: 2025-02-20

Abstract

A method for providing differential policy based on network slice information, performed by a policy control function (PCF) is provided. The method includes causing a subscription for status updates for a policy counter associated with a subscriber to be sent towards a charging function (CHF). The subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices. The method further includes receiving, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, a status for the policy counter associated with the subscriber and at least one of the one or more network slices.

Description

USAGE OF POLICY COUNTERS BASED ON NETWORK SLICE INFORMATION

TECHNICAL FIELD

[0001] Disclosed are embodiments related to usage of policy counters based on network slice information.

BACKGROUND

[0002] Third Generation Partnership Project (3GPP) Technical Specification (TS) 23.503 defines the policy and charging control framework for the 5G System. This includes the charging related requirements (clause 4.3.2), the interactions between Policy Charging Function (PCF) and Charging Function (CHF) (clause 5.3.8) for spending limit control, reporting of usage information from Session Management Function (SMF) to CHF (clause 6.1.3.3), and how the PCF takes policy decisions based on spending limits (clause 6.1.3.17).

[0003] 3 GPP TS 29.594 provides the stage 3 definition of the Spending Limit Control

Service of the 5G System and related procedures. The Spending Limit Control Service is provided by the CHF and enables the PCF as Network Function (NF) service consumer to retrieve policy counter status information relating to the subscriber spending from the CHF and use the status of each relevant policy counter as input for policy decisions as required by the decision logic.

[0004] The service operations defined for the Nchf_SpendingLimitControl service are shown in table 4.2.1-1 of 3GPP TS 29.594, and the data model is defined in clause 5.6.

[0005] Policy control subscription information

[0006] The Unified Data Repository (UDR) is the network entity in the 5G Core Network (5GC) supporting the functionality of storage and retrieval of policy data as specified in 3GPP TS 29.519.

[0007] The PCF may request subscription information at Protocol Data Unit (PDU) Session establishment, and the UDR provides the information for a subscriber connecting to a specific Data Network Name (DNN) and Single Network Slice Selection Assistance Information (S-NSSAI). This means that subscriber information may be different per DNN and S-NSSAI. For example a subscriber (e.g. Subscription Permanent Identifier (SUPI)/Generic Public Subscription Identifier (GPSI)) may belong to a group (e.g. subscCats = “Gold”) when connecting to a specific network slice, and belong to a different group (e.g. subscCats = “Silver”) when connecting to another network slice.

[0008] The PCF takes into account the subscription information received from the UDR to make policy decisions.

[0009] Ericsson N28 interface

[0010] The basic integration of PCF with Converged Charging System (CCS) for Spending Limit Reporting function allows setting the policies for the N7 session of a subscriber considering the changes in the policy counter status reported by the CCS. The subscription of the Data Plans applicable to the subscriber is provisioned in the UDR, and handled in both the PCF and the CCS. Rating policies and resource usage information are handled in the CCS, while user policies that consider changes in the policy counter status to set the policies for the N7 session are handled in the PCF. The 3GPP standard N28 interface only conveys (changes in) the status of Policy Counters.

[0011] The Ericsson N28 allows the centralization of the subscriber subscription to Data Plans in CCS, by adding proprietary extensions to the 3GPP standard N28 interface.

[0012] The management of the subscriber subscription to the Operator Service Offering is centralized in CCS, that indicates to the PCF the set of Data Plans available to the subscriber via the Ericsson N28 interface, using an Ericsson concept called Policy Groups.

[0013] The Ericsson N28 interface conveys then, together with Policy Counter status, the Policy Groups available to the subscriber. This is illustrated by FIG. 1.

[0014] The Policy Group is an Ericsson concept.

[0015] The Policy Groups are assigned to a subscriber and are sent over Ericsson N28 interface to indicate the Service Offering applicable to a subscriber. The Policy Group is implemented in the PCF by using Subscriber Groups. By configuration, the set of services (static data) and the set of conditions (dynamic data) that have to be applied to a Policy Group are configured in the associated Subscriber Group. The Policy Group identifier conveyed in Ericsson N28 reference point allows the PCF to be informed in real time by CCS about the Data Plans (or derived subscription information) subscribed by a particular subscriber.

[0016] The Policy Group information consists of:

• Policy Group Identifier, that is, the identifier of the Policy Group.

• Policy Activation/Deactivation Time: Start and End date for the Policy Group association.

• Priority: the relative priority to be used by the PCF to sort out precedence among groups, Policy Groups, and Subscriber Groups. It depends on the priority of the applicable Data Plans.

[0017] For a subscriber and a traffic session, the PCF evaluates network operator policies to set the authorized data to apply for the traffic session. Network operator policies are operator configured conditions which make use of subscription data, subscriber dynamic information, accumulated usage, time and date conditions. Network operator policies are bound to Data Plans (for example, the policies to apply during Busy Hour and the policies to apply to YouTube service depend on whether the subscriber is subscribed to "Gold", "Silver" or "Bronze" Data Plans).

[0018] In 3 GPP policy control and charging architecture, policy subscription information (data plans) is stored in the UDR. The Ericsson N28 enables to deploy the PCF without subscribers provisioned in the UDR.

[0019] Current implementation of Ericsson N28 interface is based on a previous patent application [5] that refers to the Policy and Charging Rules Function (PCRF) within the EPC architecture, but it is applicable to the PCF within the 5G system.

[0020] The Abstract from US8630925B2, titled Method and apparatus for controlling service traffic in a communication network, is below:

A method and corresponding apparatus for controlling service traffic in a communication network including an online charging system performing the steps of receiving a request for service traffic control, the request including at least data identifying a first communication network account; determining, based on the received data and a predefined set of rules, a first network traffic policy profile associated with the first account; transmitting to a Policy and Charging Rules Function PCRF a first policy control command including an identifier identifying the first network traffic policy profile stored in an network traffic policy profile entity, to be applied in controlling the service.

[0021] References:

[1] 3GPP TS 23.503 version 18.0.0: Policy and charging control framework for the 5G System;

[2] 3GPP TS 29.594 version 18.0.0: 5G System; Spending Limit Control Service; Stage 3;

[3] 3GPP TS 32.291 version 18.0.0: 5G system, charging service; Stage 3;

[4] 3GPP TS 29.519 version 18.0.0: 5G System; Usage of the Unified Data Repository service for Policy Data, Application Data and Structured Data for Exposure; Stage 3;

[5] U. S. Patent Application US8630925B2: Method and apparatus for controlling service traffic in a communication network;

[6] 3GPP TS 32.255: version 17.8.0: Charging management; 5G data connectivity domain charging; Stage 2;

[7] 3GPP TS 29.513 version 18.0.0: Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3.

SUMMARY

[0022] Embodiments described herein may make use of policy counters based on network slice information.

[0023] One user equipment (UE) could connect to different Network Slices depending on conditions. The different Network Slices can provide added value to the UE connection, such as low latency or high data throughput.

[0024] The CHF and CCS store the policy counters of each subscriber and can consider the Network Slice information to update the policy counters, since S-NSSAI Id is received from the SMF. The PCF retrieves from the CHF or CCS the policy counters and provide policies for each PDU Session based on them.

[0025] In addition, there are Ericsson specific scenarios where the subscriber profile is stored in the CCS (Ericsson-N28 solution) instead of in the UDR. The PCF retrieves the subscriber profile from the CCS, that is only based on the Subscription Identifier of the UE. This implies that only one profile of the subscriber can be provided to the PCF.

[0026] Using the current solution, the CHF and CCS are not able to provide policy counters (and/or vendor specific information, e.g., in the case of Ericsson-N28 solution) based on Network Slice information, since they are based on the Subscription Identifier of the UE.

Therefore, it is not possible for the PCF to retrieve specific policy counters (and/or vendor specific information, e.g., in the case of Ericsson-N28 solution) for a Network Slice and provide policies based on a Network Slice.

[0027] Embodiments enables the network (e.g., 5G system) to perform slice based spending-limit-control. This is a new charging model, not currently included in 3GPP TS 23.503.

[0028] In relation to 3GPP Spending Limit Control Service (N28), embodiments provide at least the following advantages:

• Enables the PCF to retrieve policy counter status information applicable to specific network slice(s);

• Enables the PCF to subscribe to notification of changes in the status of the policy counters applicable to specific network slice(s); and

• Enables the CHF to notify the PCF about the change of the status of the subscribed policy counters applicable to specific network slice(s).

[0029] In relation to proprietary Spending Limit Control Services (e.g., E-N28), embodiments provide at least the following advantages:

• Enables the PCF to retrieve subscriber policy groups applicable to specific network slice(s);

• Enables the PCF to subscribe to notification of changes in the subscriber policy groups applicable to specific network slice(s); and

Enables the CCS to notify the PCF about the change subscriber policy groups applicable to specific network slice(s). [0030] According to a first aspect, a method for providing differential policy based on network slice information, performed by a policy control function (PCF) is provided. The method includes causing a subscription for status updates for a policy counter associated with a subscriber to be sent towards a charging function (CHF). The subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices. The method further includes receiving, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, a status for the policy counter associated with the subscriber and at least one of the one or more network slices.

[0031] According to a second aspect, a method for providing differential policy based on network slice information, performed by a charging function (CHF) is provided. The method includes receiving a subscription for status updates for a policy counter associated with a subscriber from a policy control function (PCF). The subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices. The method further includes causing to be sent towards the PCF, in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF, a status for the policy counter associated with the subscriber and at least one of the one or more network slices.

[0032] According to a third aspect, a policy control function (PCF) node is provided. The node includes processing circuitry; and a memory. The memory contains instructions executable by the processing circuitry, whereby when executed the processing circuitry is configured to cause a subscription for status updates for a policy counter associated with a subscriber to be sent towards a charging function (CHF). The subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices. The processing circuitry is further configured to receive, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, a status for the policy counter associated with the subscriber and at least one of the one or more network slices. [0033] According to a fourth aspect, a charging function (CHF) node is provided. The node includes processing circuitry; and a memory. The memory contains instructions executable by the processing circuitry, whereby when executed the processing circuitry is configured to receive a subscription for status updates for a policy counter associated with a subscriber from a policy control function (PCF). The subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices. The processing circuitry is further configured to cause to be sent towards the PCF, in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF, a status for the policy counter associated with the subscriber and at least one of the one or more network slices.

[0034] According to a fifth aspect, a computer program is provided, comprising instructions which when executed by the processing circuitry of a node cause the node to perform the method of any of the embodiments of the first or second aspects.

[0035] According to a sixth aspect, a carrier is provided, containing the computer program of the fifth aspect. The carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

[0037] FIG. 1 illustrates an Ericsson N28 interface.

[0038] FIG. 2 illustrates a 5G reference architecture according to an embodiment.

[0039] FIG. 3 illustrates a sequence diagram according to an embodiment.

[0040] FIG. 4 illustrates a sequence diagram according to some embodiments.

[0041] FIG. 5 illustrates a flowchart according to an embodiment.

[0042] FIG. 6 illustrates a flowchart according to an embodiment.

[0043] FIG. 7 is a block diagram of an apparatus according to an embodiment.

DETAILED DESCRIPTION [0044] In Network Slicing scenarios it is interesting for the PCF to provide different policies to the PDU Session based on the policy counters of each Network Slice, so it is possible to provide service differentiation to each subscriber depending on the policy counters in each Network Slice.

[0045] Embodiments described herein may extend the existing Nchf_SpendingLimitControl Service API to enable the possibility for the PCF to include the Network Slice information in the Spending Limit Retrieval Subscriptions. The Network Slice information of the PDU session is obtained by the PCF from the SMF during the Npcf_SMPolicyControl_Create service operation. The PCF could subscribe to notification of changes in the status of the policy counters available and to retrieve the status of the policy counters for which the subscription is accepted and that are associated to the requested Network Slices.

[0046] The PCF could add the required Network Slice information of the PDU Session that the subscriber is using in the Nchf_SpendingLimitControl_Subscribe service operation. The CHF can use this information to provide specific policy counters (or subscriber profile in the case of Ericsson-N28 solution) for the requested subscriber in a particular Network Slice.

[0047] When a policy counter for a Network Slice is modified in the CHF, the information of the Network Slice modified is also included in the notification, so the NFs that are subscribed to changes can know to which Network Slice apply the policy counters modified.

[0048] Embodiments disclosed herein provide a method for the PCF to retrieve policy counters associated to specific Network Slice(s) from the CHF, with the purpose to enable service differentiation based on charging information per Network Slice.

[0049] Embodiments disclosed herein provide a method for a proprietary PCF, e.g., the Ericsson PCF, to retrieve subscriber information, e.g., policy groups, associated to specific Network Slice(s) from the CCS, with the purpose to enable subscriber and service differentiation based on subscription information and the status of the policy counters per Network Slice.

[0050] FIG. 2 illustrates The reference architecture in 5G, which includes the PCF 212, the SMF 216, and CHF 210 network functions, and interact using the interfaces shown in FIG. 2. The reference architecture also includes UDR 202, AF 204, NWDAF 206, NEF 208, AMF 214, and UPF 218, along with the associated interfaces shown in FIG. 2 (e.g., N4, N5, N7, N15, N23, N28, N29, N30, N36, N40).

[0051] When the SMF 216 receives a PDU session establishment in a network slice from a UE, the SMF 216 invokes the Npcf_SMPolicyControl_Create service operation, that includes the S-NSSAI (identifier of the network slice). The PCF 212 initiates an Initial Spending Eimit Report Retrieval to make policy decision based on the received policy counters and/or groups [7].

[0052] Including the network slice identifier to the Nchf interface (N28) enables the CHF 210 to provide the association between the policy counters and/or groups, and the network slice identifier to the PCF 212. Then, the PCF 212 can make the policy decision based on the policy counter and/or group associated to the network slice of the PDU session.

[0053] Embodiments include at least these two scenarios, depending on the interface used for the communication between PCF 212 and CHF 210.

• Scenario 1: Interface defined in 3GPP Spending Limit Control Service (N28)

• Scenario 2: Proprietary interface for Spending Limit Control Services (e.g., E- N28)

[0054] These two scenarios are addressed below.

[0055] Scenario 1: Proposed embodiments for 3GPP Spending Limit Control Service (N28)

[0056] As described in 3GPP TS 32.255 [6], the SMF 216 shall be able to perform converged charging for each of charging data related to PDU session. The charging information collected by the SMF 216 per PDU session includes the network slice instance the PDU session belongs to, and reported to the CHF 210 using the Nchf_ConvergedCharging service [3]. It enables the CHF 210 to maintain usage counters associated to different network slices, so each usage counter would increase depending on the usage of each network slice. The CHF 210 provides the value of the policy counters, that are based on the usage counters and defined thresholds, to the PCF. [0057] A proposed embodiment is to extend existing Nchf data types used in the Nchf_SpendingLimitControl service operations: the SpendingLimitContext and the PolicyCounterlnfo (used in the attribute statusinfos of the type SpendingLimitStatus).

[0058] The modification of the SpendingLimitContext data type enables the possibility to the NF service consumer to subscribe to notification of changes in the status of the policy counters and to retrieve the status of the policy counters that are associated to a specific list of Network Slices.

[0059] The modification of the PolicyCounterlnfo data type enables the association between a policy counter and a Network Slice.

[0060] The proposed changes in SpendingLimitContext are shown in the table below, in which the sliceinfos attribute is new:

[0061] Table 1: Changes on the type SpendingLimitContext

[0062] A new feature “NetworkSliceAssociation” is proposed to be added in the supported features of the 3GPP Spending Limit Control Service to enable the new attribute sliceinfos and avoid backward compatibilities issues.

[0063] Table 2: Supported Features

[0064] The proposed changes in PolicyCounterlnfo are shown in the table below, in which the sliceinfos attribute is new:

[0065] Table 3: Changes on the type PolicyCounterlnfo

[0066] FIG. 3 illustrates a flow diagram according to an embodiment. The following example shows a use case enabled with this embodiment for a given subscriber, referred to here as subscriber-A. The simplified flow illustrates the interactions between PCF 212 and CHF 210 and how the extension of the interface is used, pointing to the steps of the example. Steps 5-15, illustrating actions of and communication between PCF 212 and CHF 210 are shown in FIG. 3. Steps 1-4, described below, may occur before the illustrated steps 5-15.

[0067] 1. An operator deploys two network slices (NS -A and NS-B). The NS -A is for mobile broadband (MBB) traffic and the NS-B is for low latency services (gaming).

[0068] 2. The CHF 210 is configured to report two policy counters, each one associated to a network slice (PC-A is associated to NS-A and PC-B is associated to NS-B).

[0069] 3. The PC-A and PC-B are configured with two status:

• “BELOW” - when the data limit of (for example) 50 GB and 500 GB respectively are not surpassed; and

• “ABOVE” - when the data limit of (for example) 50 GB and 500 GB respectively are surpassed.

[0070] 4. The SMF 216 requests the creation of the SM Policy Association-A with the

PCF 212 for the subscriber-A in the NS-A using the Npcf_SMPolicyControl_Create operation.

[0071] 5. The PCF 212 requests a subscription to changes to the status of the policy counters associated to the subscriber-A and NS-A, and its current status. [0072] 6. The CHF 210 create the subscription and reports to the PCF 212 the status

“BELOW” for the PC-A.

[0073] 7. The PCF 212 sends in the response to the SMF 216 the corresponding Session

Rules associated to the “BELOW” status for the SM Policy Association-A in the NS-A.

[0074] 8. The SMF 216 requests the creation of a new SM Policy Association-B with the

PCF for the subscriber-A in the NS-B using the Npcf_SMPolicyControl_Create operation.

[0075] 9. The PCF 212 updates the subscription for the subscriber-A to include the NS-

B to the subscription, and retrieves the current status of the policy counters associated to NS-A and NS-B.

[0076] 10. The CHF 210 updates the subscription and reports to the PCF 212 the status

“BELOW” for the PC-A and PC-B.

[0077] 11. The PCF 212 sends in the response to the SMF 216 the corresponding

Session Rules associated to the “BELOW” counter for the SM Policy Association in the NS-B.

[0078] 12. The SMF 216 reports service usage of the subscriber-A in the NS-B higher than 500 GB to the CHF 210 using the Nchf_ConvergedCharging_Update operation and the CHF 210 changes the value of the PC-B to “ABOVE”

[0079] 13. The CHF 210 notifies the PCF 212 of the change in the status of the PC-B associated to NS-B to “ABOVE” using the Nchf_SpendingLimitControl_Notify service operation.

[0080] 14. The PCF 212 responds to the CHF 210.

[0081] 15. The PCF 212 sends the Session Rules associated to the “ABOVE” status

(degraded QoS profile) to the SM Policy Association-B in the NS-B using the Npcf_SMPolicyControl_Notify service operation, but the Session Rules of the SM Policy Association-A remains.

[0082] Scenario 2: Proposed embodiments for proprietary interface Spending Limit Control Services (e.g., E-N28) [0083] In scenarios where the Ericsson N28 interface is used the subscriber subscription is centralized and managed by the Ericsson CCS, that indicates to the PCF 212 the set of Data Plans (Policy Groups) available to the subscriber.

[0084] The proposed embodiment for E-N28 is to extend the existing Nchf data type SpendingLimitContext (used in the Nchf_SpendingLimitControl service operation) in the same way as described in Scenario 1 above, to enable the possibility to the NF service consumer to subscribe to notification of changes in the status of the subscriber subscription (Policy Groups) and to retrieve the status of the subscriber subscription (Policy Groups) that are associated to an specific list of Network Slices.

[0085] The data structure used by the CCS to provide the Policy Group information (PolicyGroupVendorl93) in the response to the Nchf_SpendingLimitControl_Subscribe service operation and the notification to changes to the PCF 212 (Nchf_SpendingEimitControl_Notify service operation) should be modified to include the association between Policy Group and Network Slice, in a similar way as described in Scenario 1 above for the association between policy counter and Network Slice.

[0086] Table 4: Changes on the type PolicyGroupVendorl93

[0087] FIG. 4 illustrates a flow diagram according to an embodiment. The following example shows a use case enabled with this embodiment for a given subscriber, referred to here as subscriber-A. The CSS can manage both subscriber subscription and policy counters. As shown here, only the management of the subscriber subscriptions are illustrated, but the management of the policy counters is also contemplated. The simplified flow illustrates the interactions between PCF 212 and CHF 210 and how the extension of the interface is used, pointing to the steps of the example. Steps 5-15, illustrating actions of and communication between PCF 212 and CHF 210 are shown in FIG. 4. Steps 1-4, described below, may occur before the illustrated steps 5-15.

[0088] 1. An operator deploys two network slices (NS -A and NS-B). The NS -A is for

MBB traffic and the NS-B is for low latency services (gaming).

[0089] 2. The CCS is configured to assign the Policy Group PG-A to the subscriber when using the NS-A and the PG-B when using the NS-B. [0090] 3. The PCF 212 is configured to provide low bit rate QoS for MBB when the subscriber is subscribed to the Policy Group PG-A, low latency QoS for gaming if subscribed to PG-B and high bit rate QoS for MBB if subscribed to PG-C.

[0091] 4. The SMF 216 requests the creation of the SM Policy Association-A with the

PCF for the subscriber-A in the NS-A using the Npcf_SMPolicyControl_Create operation.

[0092] 5. The PCF 212 requests the subscription to changes to the status of the subscriber subscription associated to the subscriber-A and NS-A, and its current status.

[0093] 6. The CCS creates the subscription and reports to the PCF 212 the Policy Group

PG-A.

[0094] 7. The PCF 212 sends in the response to the SMF 216 the corresponding Session

Rules for low bit rate MBB associated to the PG-A for the SM Policy Association-A in the NS- A.

[0095] 8. The SMF 216 requests the creation of a new SM Policy Association-B with the

PCF 212 for the subscriber-A in the NS-B using the Npcf_SMPolicyControl_Create operation.

[0096] 9. The PCF 212 updates the subscription for the subscriber-A to include the NS-

B to the subscription, and retrieves the current status of the subscriber subscription associated to NS-A and NS-B.

[0097] 10. The CCS updates the subscription and reports to the PCF 212 the PG-A associated to the NS-A and the PG-B associated to the NS-B.

[0098] 11. The PCF 212 sends in the response to the SMF 216 the corresponding

Session Rules for low latency gaming associated to the PG-B for the SM Policy Association-B in the NS-B.

[0099] 12. The operator adds a new PG-C associated to the NS-A to the subscriber-A subscription.

[0100] 13. The CCS notifies the PCF 212 of the change in the subscriber subscription, adding the PG-C associated to NS-A, using the Nchf_SpendingLimitControl_Notify service operation. [0101] 14. The PCF 212 responds to the CCS.

[0102] 15. The PCF 212 sends the Session Rules associated to high bit rate MBB to the

SM Policy Association-A in the NS-A using the Npcf_SMPolicyControl_Notify service operation, but the Session Rules of the SM Policy Association-B remains.

[0103] FIG. 5 is a flowchart illustrating a process 500 for providing differential policy based on network slice information, according to an embodiment, performed by a policy control function (PCF) (212). Process 500 may begin in step s502.

[0104] Step s502 comprises causing (s502) a subscription (302, 306, 402, 406) for status updates for a policy counter associated with a subscriber to be sent towards a charging function (CHF) (210). The subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices.

[0105] Step s504 comprises receiving (s504), in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF (210), a status (304, 308, 310, 404, 408, 410) for the policy counter associated with the subscriber and at least one of the one or more network slices.

[0106] In some embodiments, the method further includes sending towards a session management function (SMF) rules associated with the status for the policy counter associated with the subscriber and at least one of the one or more network slices, in response to a request to create or update a policy association for the subscriber and at least one of the one or more network slices. In some embodiments, the step of receiving (s504) further comprises updating (306) the subscription for status updates for the policy counter associated with the subscriber by modifying the network slice information identifying one or more network slices associated with the subscriber. In some embodiments, causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF comprises sending a Nchf_SpendingLimitControl_Subscribe message (302, 306, 402, 406) to the CHF.

[0107] In some embodiments, receiving, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises receiving a Nchf_SpendingLimitControl_Notify message (310, 410) from the CHF. In some embodiments, sending towards the SMF rules associated with the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises sending a Npcf jSMPolicyControl_Notify message to the SMF. In some embodiments, the subscription for status updates for the policy counter associated with the subscriber further includes status updates for additional subscriber subscription information associated with the subscriber and any of the one or more network slices, and the method further includes receiving, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, the status (404, 408, 410) for the additional subscriber information associated with the subscriber and at least one of the one or more network slices. In some embodiments, the additional subscriber information comprises information about a policy group.

[0108] FIG. 6 is a flowchart illustrating a process 600 for providing differential policy based on network slice information, according to an embodiment, performed by a charging function (CHF) (210). Process 600 may begin in step s602.

[0109] Step s602 comprises receiving (s602) a subscription (302, 306, 402, 406) for status updates for a policy counter associated with a subscriber from a policy control function (PCF) (212). The subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices.

[0110] Step s604 comprises causing (s604) to be sent towards the PCF (212), in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF (212), a status (304, 308, 310, 404, 408, 410) for the policy counter associated with the subscriber and at least one of the one or more network slices.

[0111] In some embodiments, the step of causing (s604) to be sent further comprises updating the subscription for status updates for the policy counter associated with the subscriber by modifying the network slice information identifying one or more network slices associated with the subscriber. In some embodiments, receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF comprises receiving a Nchf_SpendingLimitControl_Subscribe message (302, 306, 402, 406) from the PCF. In some embodiments, causing to be sent towards the PCF, in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF, the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises causing to be sent a Nchf_SpendingLimitControl_Notify message (310, 410) towards the PCF.

[0112] In some embodiments, the subscription for status updates for the policy counter associated with the subscriber further includes status updates for additional subscriber subscription information associated with the subscriber and any of the one or more network slices, and the method further comprises causing to be sent towards the PCF, in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF, the status (404, 408, 410) for the additional subscriber information associated with the subscriber and at least one of the one or more network slices. In some embodiments, the additional subscriber information comprises information about a policy group.

[0113] FIG. 7 is a block diagram of apparatus 700 (e.g., CHF 210, PCF 212), according to some embodiments, for performing the methods disclosed herein. As shown in FIG. 7, apparatus 700 may comprise: processing circuitry (PC) 702, which may include one or more processors (P) 755 (e.g., a general purpose microprocessor and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (i.e., apparatus 700 may be a distributed computing apparatus); at least one network interface 748 comprising a transmitter (Tx) 745 and a receiver (Rx) 747 for enabling apparatus 700 to transmit data to and receive data from other nodes connected to a network 710 (e.g., an Internet Protocol (IP) network) to which network interface 748 is connected (directly or indirectly) (e.g., network interface 748 may be wirelessly connected to the network 710, in which case network interface 748 is connected to an antenna arrangement); and a storage unit (a.k.a., “data storage system”) 708, which may include one or more non-volatile storage devices and/or one or more volatile storage devices. Interface 760 may connect PC 702 and storage unit 708, interface 762 may connect PC 702 and network interface 748, and interface 764 may connect network interface 748 and network 710. In embodiments where PC 702 includes a programmable processor, a computer program product (CPP) 741 may be provided. CPP 741 includes a computer readable medium (CRM) 742 storing a computer program (CP) 743 comprising computer readable instructions (CRI) 744. CRM 742 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI 744 of computer program 743 is configured such that when executed by PC 702, the CRI causes apparatus 700 to perform steps described herein (e.g., steps described herein with reference to the flow charts). In other embodiments, apparatus 700 may be configured to perform steps described herein without the need for code. That is, for example, PC 702 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.

[0114] While various embodiments are described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of this disclosure should not be limited by any of the above described exemplary embodiments. Moreover, any combination of the above-described embodiments in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

[0115] Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.

Claims

1. A method for providing differential policy based on network slice information, performed by a policy control function (PCF) (212), the method comprising: causing (s502) a subscription (302, 306, 402, 406) for status updates for a policy counter associated with a subscriber to be sent towards a charging function (CHF) (210), wherein the subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices; and receiving (s504), in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF (210), a status (304, 308, 310, 404, 408, 410) for the policy counter associated with the subscriber and at least one of the one or more network slices.

2. The method of claim 1, further comprising sending towards a session management function (SMF) rules associated with the status for the policy counter associated with the subscriber and at least one of the one or more network slices, in response to a request to create or update a policy association for the subscriber and at least one of the one or more network slices.

3. The method of any one of claims 1-2, wherein the step of receiving (s504) further comprises updating (306) the subscription for status updates for the policy counter associated with the subscriber by modifying the network slice information identifying one or more network slices associated with the subscriber.

4. The method of any one of claims 1-3, wherein causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF comprises sending a Nchf_SpendingLimitControl_Subscribe message (302, 306, 402, 406) to the CHF.

5. The method of any one of claims 1-4, wherein receiving, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises receiving a Nchf SpendingLimitControl Notify message (310, 410) from the CHF.

6. The method of claim 2, wherein sending towards the SMF rules associated with the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises sending a Npcf_SMPolicyControl_Notify message to the SMF.

7. The method of any one of claims 1 -6, wherein the subscription for status updates for the policy counter associated with the subscriber further includes status updates for additional subscriber subscription information associated with the subscriber and any of the one or more network slices, and wherein the method further comprises receiving, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, the status (404, 408, 410) for the additional subscriber information associated with the subscriber and at least one of the one or more network slices.

8. The method of claim 7, wherein the additional subscriber information comprises information about a policy group.

9. A method for providing differential policy based on network slice information, performed by a charging function (CHF) (210), the method comprising: receiving (s602) a subscription (302, 306, 402, 406) for status updates for a policy counter associated with a subscriber from a policy control function (PCF) (212), wherein the subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices; and causing (s604) to be sent towards the PCF (212), in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF (212), a status (304, 308, 310, 404, 408, 410) for the policy counter associated with the subscriber and at least one of the one or more network slices.

10. The method of claim 9, wherein the step of causing (s604) to be sent further comprises updating the subscription for status updates for the policy counter associated with the subscriber by modifying the network slice information identifying one or more network slices associated with the subscriber.

11. The method of any one of claims 9-10, wherein receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF comprises receiving a Nchf_SpendingLimitControl_Subscribe message (302, 306, 402, 406) from the PCF.

12. The method of any one of claims 9-11, wherein causing to be sent towards the PCF, in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF, the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises causing to be sent a Nchf_SpendingLimitControl_Notify message (310, 410) towards the PCF.

13. The method of any one of claims 9-12, wherein the subscription for status updates for the policy counter associated with the subscriber further includes status updates for additional subscriber subscription information associated with the subscriber and any of the one or more network slices, and wherein the method further comprises causing to be sent towards the PCF, in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF, the status (404, 408, 410) for the additional subscriber information associated with the subscriber and at least one of the one or more network slices.

14. The method of claim 13, wherein the additional subscriber information comprises information about a policy group.

15. A policy control function (PCF) (212) comprising: processing circuitry (702); and a memory, the memory containing instructions (744) executable by the processing circuitry (702), whereby when executed the processing circuitry (702) is configured to: cause (s502) a subscription (302, 306, 402, 406) for status updates for a policy counter associated with a subscriber to be sent towards a charging function (CHF) (210), wherein the subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices; and receive (s504), in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF (210), a status (304, 308, 310, 404, 408, 410) for the policy counter associated with the subscriber and at least one of the one or more network slices.

16. The PCF of claim 15, wherein when executed the processing circuitry (702) is further configured to send towards a session management function (SMF) rules associated with the status for the policy counter associated with the subscriber and at least one of the one or more network slices, in response to a request to create or update a policy association for the subscriber and at least one of the one or more network slices.

17. The PCF of any one of claims 15-16, wherein the step of receiving (s504) further comprises updating (306) the subscription for status updates for the policy counter associated with the subscriber by modifying the network slice information identifying one or more network slices associated with the subscriber.

18. The PCF of any one of claims 15-17, wherein causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF comprises sending a Nchf_SpendingLimitControl_Subscribe message (302, 306, 402, 406) to the CHF.

19. The PCF of any one of claims 15-18, wherein receiving, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises receiving a Nchf SpendingLimitControl Notify message (310, 410) from the CHF.

20. The PCF of claim 16, wherein sending towards the SMF rules associated with the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises sending a Npcf_SMPolicyControl_Notify message to the SMF.

21. The PCF of any one of claims 15-20, wherein the subscription for status updates for the policy counter associated with the subscriber further includes status updates for additional subscriber subscription information associated with the subscriber and any of the one or more network slices, and wherein the method further comprises receiving, in response to causing the subscription for status updates for the policy counter associated with the subscriber to be sent towards the CHF, the status (404, 408, 410) for the additional subscriber information associated with the subscriber and at least one of the one or more network slices.

22. The PCF of claim 21, wherein the additional subscriber information comprises information about a policy group.

23. A charging function (CHF) (210) comprising: processing circuitry (702); and a memory, the memory containing instructions (744) executable by the processing circuitry (702), whereby when executed the processing circuitry (702) is configured to: receive (s602) a subscription (302, 306, 402, 406) for status updates for a policy counter associated with a subscriber from a policy control function (PCF) (212), wherein the subscription includes network slice information identifying one or more network slices associated with the subscriber and requests status updates associated with the subscriber and any of the one or more network slices; and cause (s604) to be sent towards the PCF (212), in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF (212), a status (304, 308, 310, 404, 408, 410) for the policy counter associated with the subscriber and at least one of the one or more network slices.

24. The CHF of claim 23, wherein t causing (s604) to be sent further comprises updating the subscription for status updates for the policy counter associated with the subscriber by modifying the network slice information identifying one or more network slices associated with the subscriber.

25. The CHF of any one of claims 23-24, wherein receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF comprises receiving a Nchf_SpendingLimitControl_Subscribe message (302, 306, 402, 406) from the PCF.

26. The CHF of any one of claims 23-25, wherein causing to be sent towards the PCF, in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF, the status for the policy counter associated with the subscriber and at least one of the one or more network slices comprises causing to be sent a Nchf_SpendingLimitControl_Notify message (310, 410) towards the PCF.

27. The CHF of any one of claims 23-26, wherein the subscription for status updates for the policy counter associated with the subscriber further includes status updates for additional subscriber subscription information associated with the subscriber and any of the one or more network slices, and wherein the method further comprises causing to be sent towards the PCF, in response to receiving the subscription for status updates for the policy counter associated with the subscriber from the PCF, the status (404, 408, 410) for the additional subscriber information associated with the subscriber and at least one of the one or more network slices.

28. The CHF of claim 27, wherein the additional subscriber information comprises information about a policy group.

29. A computer program (743) comprising instructions which when executed by processing circuitry (702) of a node (700), causes the node (700) to perform the method of any one of claims 1-14.

30. A carrier containing the computer program (743) of claim 29, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium (742).