Differentiated charging based on policy change reasons in wireless networks
By adding a 'policy change reason' information element in the PCC rule, the solution addresses inefficient charging in wireless networks, allowing for dynamic and differentiated charging based on energy efficiency or congestion, thereby optimizing network operations and maintaining KPIs.
Patent Information
- Application Number
- PCT/EP2026/063379
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless networks lack a solution for differentiated charging based on policy changes, particularly in scenarios involving energy efficiency and network congestion, leading to inefficient charging and inability to track service delivery impacts.
Incorporating a 'policy change reason' information element in the PCC rule sent from the PCF to the SMF, enabling the CHF to apply differentiated charging and monitor service delivery impacts, such as energy efficiency or network congestion.
Enables dynamic and differentiated charging, reducing costs for UEs and maintaining key performance indicators (KPIs) by considering the rationale behind service delivery adjustments.
Smart Images

Figure EP2026063379_12112026_PF_FP_ABST
Abstract
Description
P113660W0021DIFFERENTIATED CHARGING BASED ON POLICY CHANGE REASONS IN WIRELESS NETWORKSTECHNICAL FIELD
[0001] The present disclosure relates generally to communications, and more particularly to methods and related devices and network nodes performing cellular based communications and signaling. More particularly, the present disclosure relates to differentiated charging based on policy decisions in wireless networks, including charging adjustments when service adjustments are performed by the network.BACKGROUND
[0002] In 5GC, Network Functions (NF) are network entities that provide and consume services to and from each other, through a Service Based Architecture (SBA). The Energy Information Function (EIF) is a NF designed primarily to monitor energy consumption in the network and provide related metrics. Currently, these metrics are calculated per user equipment (UE), per packet data unit (PDU) session, or per Quality of Service (QoS) Flow, based on the fraction of energy consumed by the gNB and user plane function (UPF). This calculation is derived from the ratio of i) traffic consumed by a UE to ii) the total user plane traffic. In some instances, a service consumer shall be able to subscribe to EIF energy metrics and receive the calculations.
[0003] According to 3GPP standards, the subscription data for a UE may include an Energy Saving indicator that indicates that the UE is subject to network energy saving operations. The Access and Mobility Management Function (AMF) receives the Energy Saving indicator in the UE subscription data. The AMF forwards the Energy Saving indicator to the Next Generation Radio Access Network (NG-RAN) and the Policy Control Function (PCF). Specifically, during the access and mobility (AM) policy association establishment procedure, the AMF sends the Energy Saving indicator to the PCF. Based on the Energy Saving indicator, the PCF may make policy decisions reusing the existing parameters according to configured operator policies.SUMMARY
[0004] Aspects of the disclosure may provide solutions to these or other challenges.P113660W0022
[0005] According to one aspect, a method is performed by a policy control function (PCF). The method includes obtaining energy consumption data; applying one or more policy decisions based on the obtained energy consumption data; generating a Policy and Charging Control (PCC) rule that includes at least a policy change reason information element; sending the PCC rule to a Session Management Function (SMF).
[0006] According to another aspect, a network node hosts a PCF, the network node comprising processing circuitry, and at least one memory storing instructions executable by the processing circuitry to perform operations to: obtain energy consumption data; apply one or more policy decisions based on the obtained energy consumption data; generate a PCC rule that includes at least a policy change reason information element; send the PCC rule to a SMF.
[0007] According to another aspect, a computer program product comprises a non-transitory computer readable medium storing instructions executable by processing circuitry of a network node hosting a policy control function, the instructions executed by the processing circuitry to perform operations to: obtain energy consumption data; apply one or more policy decisions based on the obtained energy consumption data; generate a PCC rule that includes at least a policy change reason information element; send the PCC rule to a SMF.
[0008] According to another aspect, a method is performed by a PCF. The method includes obtaining network related data; applying one or more policy decisions based on the obtained network related data; generating a PCC rule that includes at least a policy change reason IE; and sending the PCC rule to a management function in a network.
[0009] In some aspects, the management function includes a Session Management Function (SMF) or an Access and Mobility Management Function (AMF). While described herein with reference to Session Policies, the solution can also be applied for AM policies and incorporate a reason for change for AM policy updates via the AMF to the CHF.
[0010] According to another aspect, a network node hosts a PCF, the network node comprising processing circuitry, and at least one memory storing instructions executable by the processing circuitry to perform operations to: obtain network related data; apply one or more policy decisions based on the obtained network related data; generate a PCC rule that includes at least a policy change reason information element; send the PCC rule to a management function in a network.
[0011] According to another aspect, a computer program product comprises a non-transitory computer readable medium storing instructions executable by processing circuitryP113660W0023of a network node hosting a policy control function, the instructions executed by the processing circuitry to perform operations to: obtain network related data; apply one or more policy decisions based on the obtained network related data; generate a PCC rule that includes at least a policy change reason information element; send the PCC rule to a management function in a network.
[0012] Certain aspects may provide one or more of the following technical advantage(s). Notably, aspects enable a network to apply differentiated (e.g., reduced) charging for the packet traffic of a UE in the event the network applies some actions related with energy efficiency and energy saving. Examples of differentiated charging may include reduced rates or flat fees.
[0013] Aspects also enable the monitoring and management of some key performance indicators (KPIs) including information about whether the service delivery of a UE has been impacted by the network applying actions related to energy efficiency and energy saving.
[0014] The solution afforded by aspects is not solely related to energy efficiency cases, but is general enough to cover other scenarios where the PCF and / or network applies one or more policy decisions that can have an impact in the service delivery of the UE for other reasons. For example, in scenarios where network congestion exists, throttling may be applied to the packet traffic associated with some UEs in order to control and / or reduce congestion.BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:
[0016] Figure l is a block diagram of 3GPP reference architecture for Energy Efficiency and Energy Saving;
[0017] Figure 2a and 2b are exemplary sequence diagram for differentiated charging based on energy efficiency policy decisions in accordance with some embodiments;
[0018] Figure 3 is a flow chart illustrating example operations for conducting energy efficiency differentiated charging in accordance with some embodiments;
[0019] Figure 4 is a flow chart illustrating example operations for conducting differentiated charging in accordance with some embodiments;P113660W0024
[0020] Figure 5 is a block diagram of a communication system in accordance with some embodiments;
[0021] Figure 6 is a block diagram of a second communication system in accordance with some embodiments;
[0022] Figure 7 is a block diagram of a wireless device in accordance with some embodiments.
[0023] Figure 8 is a block diagram of a network node in accordance with some embodiments; and
[0024] Figure 9 is a block diagram of a virtualization environment in accordance with some embodiments.DETAILED DESCRIPTION
[0025] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
[0026] As used herein, the use of quotation marks around terms such as "reason for a policy change," "policy change reason," " energy _effi ci ency," or similar expressions is for purposes of identification and clarity only, and is not intended to limit the scope of the present disclosure. The actual meaning of the term as used in context is to be understood.
[0027] The present disclosure pertains to performing differentiated charging when the network performs a service adjustment. At a high level, the present disclosure is based on a policy control function (PCF) adding an information element (IE) containing a reason for a policy change (i.e., ‘policy change reason’) in the charging information of the associated PCC rule when service adjustment is applied for a service data flow (SDF). In some embodiments, the session management function (SMF) sends the reason for a policy change together with existing charging information to a charging function (CHF).
[0028] The solution is based on following principles: PCF adds an IE of “reason for a policy change” in charging info of the associated PCC rule when service adjustment is applied for an SDF. SMF sends the reason for a policy change together with existing charging info to CHF. While described herein with reference to Session Policies, the solution can also be applied for AM policies and incorporate a “reason for change” for AM policy updates via the AMF to the CHF.P113660W0025
[0029] Figure 1 depicts a block diagram of an exemplary 3 GPP reference architecture for Energy Efficiency and Energy Saving. Specifically, Figure 1 represents a segment of the 5G Core (5GC) architecture focused on policy control, which is largely managed by the Policy Control Function (PCF) 106. Notably, the PCF 106 is responsible for making policy decisions related to access, session management, QoS enforcement, and charging. PCF 106 interacts with several key functions: the Application Function (AF) 102, which provides application-specific policy and QoS requirements; the Network Exposure Function (NEF) 104, which acts as a mediator between external AFs and core network functions; the Session Management Function (SMF) 108, which uses policies from the PCF 106 to manage data sessions and apply QoS rules; and the Unified Data Management (UDM) function 110, which supplies user and subscription data to the PCF 106. Figure also depicts an Energy Information Function (EIF) 112, which may represent a vendor-specific component used to logically group or mediate access to PCF services. In some instances, the EIF 112 is an NF designed primarily to monitor energy consumption in the network (e.g., network slices, UEs, etc.) and provide related metrics.
[0030] In some scenarios, the PCF 106 may make policy decisions related with energy efficiency and energy saving. Notably, these policy decisions can have an impact in the network traffic delivered to the UE. However, no specific solution has been defined to enable a differentiated charging (e.g., a dynamic reduction in charging) for the UE when energy efficiency -related actions (which are based on the aforementioned policy decisions) are taken for the UE. When the network applies such actions to enhance energy efficiency (which can affect service delivery to the UE), the charging applied to this network traffic for the UE should be different (i.e., reduced) compared to the charging that is applied in regular or legacy circumstances.
[0031] Note that relying on existing legacy charging architecture and tasking the PCF to assign a different service-specific Rating Group for Internet protocol (IP) packet flows when energy efficiency decisions have been applied may prove to be overly simplistic and restrictive. Such an approach could lead to needing multiple Rating Groups for the same service, thereby becoming unmanageable in scenarios involving multiple services and energy efficiency decisions.
[0032] In addition, beyond applying a differentiated (e.g., reduced) charging for the UE when energy efficiency actions are applied to the UE, the network is unable to keep track ofP113660W0026any impact in the service delivery for a UE caused by applying actions related with energy efficiency and energy saving.
[0033] Any resulting change of QoS would lead to providing a new update to the charging function (CHF), which can already be changed differently. However, if the reason is “Energy Efficiency”, one may choose to reduce the price while other reasons may not impact the price at all. Further, making QoS changes can also increase the price.
[0034] The present disclosure proposes to extend and / or expand the charging information that is provided in a policy and charging control (PCC) rule sent by the PCF to the SMF (e.g., via the N7 interface). Notably, the PCC rule may include additional information about the reason for a policy change (i.e., “policy change reason”), where energy efficiency could be one indicated reason. In some embodiments, the policy change reason may be implemented using a reason indicator, such as a cause code. When the PCF applies policy decisions based on energy efficiency reasons, the PCF can send to the SMF an update of the PCC rule that includes the additional charging information with the policy change reason indicating energy efficiency.
[0035] As described herein, the new charging information (e.g., the reason for a policy change) along with the charging rate will be forwarded by the SMF to the CHF. Notably, the CHF can consider the new information when applying the charging and billing for the UE. For example, the CHF can take this new charging information (i.e., ‘additional information’) to apply a differentiated charging of the packet traffic of the UE for which some energy efficiency policy decisions have been applied. The CHF can also keep track of any impact in the service delivery for a UE that is caused by applying actions related to energy efficiency and energy saving.
[0036] One solution afforded by embodiments extends beyond energy efficiency and can also be used in other scenarios where the PCF applies a policy decision that can impact the service delivery of the UE. For example, in scenarios where network congestion exists, throttling may be applied to the packet traffic associated with some UEs in order to control and / or reduce congestion.
[0037] Some embodiments afford a solution that enables the dynamic and differentiated charging for a UE and / or service based on whether the network applies energy saving and / or energy efficiency related actions that could impact network traffic delivery for a UE. Moreover, the present disclosure is sufficiently broad to cover other scenarios that are not necessarily related with energy efficiency actions, such as where the network applies one or more policyP113660W0027decisions that can impact the service delivery of the UE’s packet traffic for other reasons (e.g., scenarios related to network traffic congestion).
[0038] As indicated above, the present disclosure proposes to extend the charging information that is provided in a PCC rule that is sent from the PCF to the SMF (e.g., over the N7 interface) with an additional information element (IE). Notably, the new additional IE comprises a “reason for a policy change” field that indicates the reason for a policy decision applied to a UE, such as energy efficiency among others. In some embodiments, the “Reason for a Policy Change” IE indicates the reason of a policy decision that can imply an impact in the service delivery of the UE, being energy efficiency (with different severity levels) one of the reasons. The new policy data may also be included.
[0039] As shown below, Table 1 illustrates how the new IE indicator fits within an example PCC Rule:Information Description Category NameCharging key The charging system (CHF) uses the charging key to Optional determine the tariff to apply to the service data flow.Reason for a This indicator indicates the reason of a policy Optional Policy Change decision that can imply an impact in the servicedelivery of the UE, such as energy efficiency (with different severity levels) being one of the reasons.The new policy data may also be includedService identifier The identity of the service or service component the Optional service data flow in a rule relates to.Sponsor Identifier An identifier, provided from the AF, which identifies Optional the Sponsor, used for sponsored flows to correlate measurements from different users for accounting purposes.Application An identifier, provided from the AF, which identifies Optional Service Provider the Application Service Provider, used for sponsoredIdentifier flows to correlate measurements from different usersP113660W0028for accounting purposes.Charging method Indicates the required charging method for the PCC Optional rule.Values: online or offline or none.Service Data flow Indicates whether the service data flow is allowed to Optional handling while start while the SMF is waiting for the response to therequesting credit credit request.Only applicable for charging method online.Measurement Indicates whether the service data flow data volume, Optional method duration, combined volume / duration or event shall bemeasured.This is applicable to reporting if the charging method is online or offline.Note: Event based charging is only applicable topredefined PCC rules and PCC rules used forapplication detection filter (i.e. with an application identifier).Application An identifier, provided from the AF, correlating the Optional Function Record measurement for the Charging key / Service identifierInformation values in this PCC rule with application level reports.Service identifier Indicates that separate usage reports shall be generated Optional level reporting for this Service identifier.Values: mandated or not required.Table 1
[0040] In some embodiments, this new information (e.g., information element) will be forwarded by the SMF to the CHF along with the charging rate. Upon receiving this information from the SMF, the CHF can consider the IE and / or charging rate when the CHFP113660W0029applies the charging and billing rules to the UE. The new information can be also used by the CHF to maintain some KPIs, such as information about whether the impact in the service delivery of a UE has been caused by the network applying actions, such as actions related to energy efficiency and energy saving (or any other reason).
[0041] Table 2 below shows how the new indicator fits within a charging request (e.g., example structure of a PDU container information):1 nformat ion Category DescriptionFlein entTime of F irst Oc This field holds the Timestamp when the first transmitted data Usage packet of the service data flow matching the current used unit containerTime of Last Oc This field holds the Timestamp when the last transmitted data Usage packet of the service data flow matching the current used unit containerQoS Information Oc This field holds the QoS applied during the service data container intervalQoS Oc This field holds the QoS characteristics applied for QoS Characteristics information. It is only be used when the non-standardized 5QI is present in QoS information.Reason for Oc It indicates the reason of a policy decision impacting the Policy Change service delivery, e.g. energy efficiency (with different severity levels). The new policy data may also be includedTable 2
[0042] Figure 2a provides a high-level view of the steps involved in differentiated charging, while Figure 2b provides a more detailed sequence diagram showing the signaling interactions among the network functions involved in the procedure.
[0043] Figure 2a illustrates a high-level procedure for applying differentiated charging based on energy efficiency policy decisions. It illustrates a method performed by a policy control function (PCF). The method includes: triggering a PDU session establishmentP113660W00210procedure; making policy decisions to determine regular QoS and charging information for traffic associated with an application; monitoring energy consumption data; applying one or more policy decisions based on the energy consumption data to reduce energy consumption; generating a PCC rule including updated QoS, a rating group indication, and a policy change reason information element indicating energy efficiency and a severity level; sending the PCC rule to a Session Management Function (SMF); and forwarding charging information including the policy change reason to a Charging Function (CHF), wherein the CHF applies differentiated charging based on the policy change reason.
[0044] More specifically, Figure 2a depicts a sequence of interactions for differentiated charging when the network performs service adjustment. At 1, the UE triggers a PDU session establishment procedure according to 3GPP TS 23.502 clause 4.3.2. During the establishment procedure, the PCF makes policy decisions and determines regular QoS (QoSl) and charging information (Rating Group 1) for the traffic associated with application ‘appl’. At 2, the CHF applies charging based on Rating Group 1 to the traffic of the UE for appl. At 3, based on the energy consumption (EnC) of the slice (e.g., the EnC goes above a threshold according to operator policies), the PCF is triggered to apply some policy decisions (e.g., to change QoS although some other actions could be decided) to reduce the energy consumption of the UE and / or network slice. The PCF generates a corresponding PCC rule including the new QoS (QoS_2) for the service, the same Rating Group (RG_1), and the new “reason for policy decision” IE including “energy efficiency” as the reason and a severity level. The PCF delivers the PCC rule to the SMF, and the SMF forwards the charging information to the CHF. At 4, upon reception of the information from the SMF, the CHF uses the rating group plus the additional “Reason for policy decision” (the reason and the severity level) to apply differentiated (e.g., reduced) charging to the traffic of the UE. At 5, the CHF also updates KPIs with information about the reason for policy decisions and impacts on the service delivery.
[0045] Figure 2b illustrates a sequence diagram with an example of the signaling procedure for applying differentiated charging based on energy efficiency policy decisions. Notably, Figure 2b illustrates a sequence of interactions among key 5G network functions including an Operations, Administration, and Maintenance (0AM) node 220, EIF 222, CHF 224, PCF 226, SMF 228, and UE 230. Figure 2b is primarily focused on the different signaling that is needed to implement differentiated charging and energy efficiency. In box 201, the UE 220 triggers a PDU session establishment procedure (e.g., according to 3GPP TS 23.502,P113660W00211section 4.3.2), which prompts the PCF 226 to create one or more PPC rules that include charging and QoS information. During the establishment procedure, the PCF 226 makes policy decisions and determines that regular QoS (‘QoSl’) and charging information (‘Rating Group 1’) should be used for the packet traffic associated with application ‘appl’. In some embodiments, SMF 228 provides and / or exchanges the Rating Group 1 charging information for ‘Appl’ to CHF 224 (see signaling 202).
[0046] In block 203, the CHF 224 applies charging based on Rating Group 1 to the network traffic of the UE 230 for ‘Appl’ .
[0047] However, based on the UE’s subscription profile (e.g., Energy Saving indicator from the UDM) and operator-defined policies, the PCF 226 initiates (see block 204) monitoring of UE energy consumption by obtaining and / or collecting UE energy consumption data from the EIF 222 and / or network slice energy consumption data from 0AM node 220. More specifically, the PCF 226 may be configured to send aNEIF event exposure subscription and / or notification message 205 to EIF 222 to collect UE energy consumption data. Likewise, the PCF 226 may be configured to conduct network slice energy consumption measurement related signaling 206 with the 0AM node 220 to obtain the network slice energy consumption data.
[0048] At some point in time and based on the UE energy consumption measures received from the EIF 222 and / or the network slice consumption measures (and / or measurements) from 0AM node 220 and according to the operator policies, the PCF 226 may decide to apply one or more policy decisions. In some embodiments, the PCF 226 may collect network slice level energy consumption (EnC) data from the 0AM, e.g., using SA 5 defined services. The PCF 226 may then compare the collected EnC data to threshold levels defined in the network slice policy data. Similarly, the PCF 226 may be configured to collect EnC data of UE level, SDF, and the PDU session. The PCF 226 may compare the collected EnC data to the threshold levels defined in the UE, SDF, and session policy data.
[0049] In some embodiments, the PCF is triggered to apply some policy decisions (e.g., to change QoS although some other actions could be decided) to reduce the energy consumption of the UE and / or network slice. The trigger may be based on energy consumption data, network congestion data, or other network-related metrics.
[0050] As shown in block 207, the applied policy decisions may be configured to change QoS (e.g., apply a reduced QoS) and / or other actions that reduce the energy consumption of the UE and / or network slice. In some embodiments, the PCF 226 generates a newP113660W00212corresponding PCC rule that includes the new QoS (e.g., QoS_2) for the service, the same Rating Group indication (e.g., RG_1), and the new “reason for policy decision” IE, which includes “ energy _effi ci ency” as the reason and “X” as the severity level. For other use cases, another cause code and / or an optional severity level can be used.
[0051] In signalling message 208, the PCF 226 delivers the new PCC rule to the SMF 228. In some embodiments, the PCF 226 sends to SMF 228 an NPCF policy authorization update request message containing the new PCC rule. After receiving message 208, SMF 228 forwards the updated charging information to the CHF 224 via signalling message 209. In some embodiments, message 209 contains the application identifier “appl”, the rating group indication (e.g., Rating Group 1), and the reason for the updated policy decision (e.g., energy efficiency reason and its corresponding severity level). Notably, changing the level of QoS is just one policy example, as any service adjustment related policy decision can be applied as described herein.
[0052] In box 210, the CHF 224 applies differentiated charging for appl. For example, upon the reception of the information from the SMF 228, the CHF 224 uses the rating group indication and / or the charging rate along with the additional “Reason for policy decision” information (e.g., the indicated reason and the associated severity level) to apply differentiated (e.g., reduced) charging to the network traffic of the UE 230.
[0053] In box 211, the CHF 224 may also update new KPIs with information about the reason for the policy decisions and impacts on the service delivery.
[0054] As energy usage data is reported, the PCF analyzes it and, if it detects inefficiencies, it may adjust the QoS or take other energy-saving actions. These decisions are communicated back to the network functions, including an update to the charging policy, now differentiated based on the energy efficiency considerations. Finally, the system updates its KPIs to reflect the rationale behind service impacts, ensuring transparency in policy-driven service modifications.
[0055] Although not explicitly depicted in Figure 2b, the PCF may also include the new IE “reason for policy decisions” to the AMF as part of AM / UE policies that may be considered by the AMF in the event the AMF is applying some charging actions.
[0056] In some embodiments, addition of “reason for change” for AM policy updates via the AMF to the CHF enables differentiated charging for access and mobility related policyP113660W00213decisions. The AMF may extract and forward to the CHF charging information that includes data contained in the policy change reason information element.
[0057] Figure 3 is a flow chart illustrating method 300 depicting exemplary operations for performing differentiated charging according to one embodiment. Operations of the network node 800 hosting a PCF which may be implemented using the structure of the block diagram of Figure 8, will now be discussed with reference to the flow chart of Figure 3 according to some embodiments. For example, one or more modules may be stored in memory 804 of Figure 8, and these modules may provide instructions so that when the instructions of a module are executed by respective processing circuitry 802, the network node 800 performs respective operations of the flow chart. In some embodiments, memory 804 may store the necessary software to implement and / or support a PCF.
[0058] In step 301, the method 300 includes obtaining energy consumption data. In some embodiments, the energy consumption data includes one or more of UE energy consumption measures (or measurements) and / or network slice level energy consumption measures (or measurements). In some embodiments, the UE energy consumption data is obtained from an EIF and / or the network slice level energy consumption data is obtained from an 0AM function or node.
[0059] In step 302, the method 300 includes applying one or more policy decisions based on the obtained energy consumption data. In some embodiments, the one or more policy decisions pertain to reducing energy consumption of a UE and / or a network slice. In some embodiments, the policy change reason information element includes a reason indicator (e.g., reason code or cause code) and a severity level indicator (e.g., ‘X’ level of severity). In some embodiments, the reason indicator comprises an energy efficiency reason indicator or energy saving reason indicator. In some embodiments, the PCF is trigged to apply the one or more policy decisions based on a service adjustment applicable to the UE is performed.
[0060] In step 303, the method 300 includes generating a PCC rule that includes at least a policy change reason information element. In some embodiments, the PCC rule includes an updated QoS level and / or a rating group indicator.
[0061] In step 304, the method 300 includes sending the PCC rule to a SMF. In some embodiments, the SMF extracts and forwards to a CHF charging information that includes data contained in the policy change reason information element.PII3660W00214
[0062] In some embodiments, the policy change reason information element includes new policy data indicating the updated policy parameters applied by the PCF. The new policy data may be forwarded along with the reason indicator and severity level indicator to the CHF.
[0063] In some embodiments, the CHF utilizes at least the energy efficiency reason code and the severity level indicator to apply differentiated charging to packet traffic of the UE. In some embodiments, the CHF also utilizes the rating group indicator to apply the differentiated charging to the packet traffic of the UE. In some embodiments, the CHF is configured to update at least one KPI with information related to the policy change reason.
[0064] Figure 4 is a flow chart illustrating method 300 depicting exemplary operations for performing differentiated charging according to one embodiment. Operations of the network node 800 hosting a PCF which may be implemented using the structure of the block diagram of Figure 8, will now be discussed with reference to the flow chart of Figure 4 according to some embodiments. For example, one or more modules may be stored in memory 804 of Figure 8, and these modules may provide instructions so that when the instructions of a module are executed by respective processing circuitry 802, the network node 800 performs respective operations of the flow chart. In some embodiments, memory 804 may store the necessary software to implement and / or support a PCF.
[0065] In step 401, the method 400 includes obtaining network related data. In some embodiments, the network data includes one or more of UE energy consumption measures, network slice level energy consumption measures, network load measures, network congestion measures, network traffic measures. In some embodiments, the network related data is obtained from an EIF and / or an 0AM function or node.
[0066] In step 402, the method 400 includes applying one or more policy decisions based on the obtained network data. In some embodiments, the one or more policy decisions pertains to access(AM) / user equipment (UE) policies. In some embodiments, the policy change reason information element includes a reason indicator (e.g., reason code or cause code) and a severity level indicator (e.g., ‘X’ level of severity). In some embodiments, the PCF is trigged to apply the one or more policy decisions based on a service adjustment applicable to the UE is performed.
[0067] In step 403, the method 400 includes generating a PCC rule that includes at least a policy change reason information element. In some embodiments, the PCC rule includes an updated QoS level and / or a rating group indicator.P113660W00215
[0068] In step 404, the method 400 includes sending the PCC rule to a management function. In some embodiments, the management function includes a SMF or a Access and Mobility Management Function (AMF). In some embodiments, the management function extracts and forwards to a CHF charging information that includes data contained in the policy change reason information element.
[0069] In some embodiments, the CHF utilizes at least the charging information to apply differentiated charging to packet traffic of the UE. In some embodiments, the CHF also utilizes the rating group indicator to apply the differentiated charging to the packet traffic of the UE. In some embodiments, the CHF is configured to update at least one KPI with information related to the policy change reason.
[0070] Figure 5 shows an example of a communication system 500 in accordance with some embodiments. In the example, the communication system 500 includes a telecommunications network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes or base stations of various types, access network nodes 510A and 510B are depicted (which may be collectively referred to as network nodes 510), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 504 may include more than one access network technology. The network nodes 510 of access network 504 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.
[0071] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of anyP113660W00216network node in the telecommunications network 502, including one or more access network nodes 510 and / or core network nodes 508.
[0072] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
[0073] The network nodes 510 facilitate direct or indirect connection of one or more UEs 512 to the core network 506 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0074] The UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 510 and other communication devices. Similarly, the network nodes 508, 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g.,P113660W00217via other devices of telecommunications network 502) with the UEs 512 and / or with other network nodes or equipment in the telecommunications network 502 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 502. More specifically, UEs 512 may send messages, data, and / or other signals to network nodes 508, 510 or other elements of the telecommunications network 502 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 508, 510 may send messages, data, and other signals to UEs 5122, other network nodes 508, 510, and other devices in telecommunications network 502 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 512 by transmitting the message to an access network node 510 that will then transmit the message to the intended UE 512. Similarly, a core network node 108 may receive a particular message from a UE 512 by receiving the message from an access network node 510 that itself received the message from the UE 512.
[0075] In the depicted example, the core network 506 connects elements of the access network 504 (e.g., one or more of the network nodes 510) to one or more host computing systems, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 506 includes one or more core network nodes (e.g., core network node 508) of various types, one or more of which may be generally referred to as network nodes 508. Network nodes 508 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).P113660W00218
[0076] The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunications network 502. The host 516 may be operated by the service provider or on behalf of the service provider. The host 516 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0077] As a whole, the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 500 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 500 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 500 supporting different standards, protocols, or rule sets.
[0078] As one example, in certain embodiments, access network 504 may contain some access network nodes 510 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 510 support (or the same access network nodes 510 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 502 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple differentP113660W00219standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.
[0079] Telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0080] In some examples, one or more of the UEs 512 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0081] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and / or 512D) and network nodes (e.g., network node 510B). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514.
[0082] As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing localP113660W00220processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0083] The hub 514 may have a constant / persistent or intermittent connection to the network node 510B. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g., UE 512C and / or 512D), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to an M2M service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 510B. In other embodiments, the hub 514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 510B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0084] Figure 6 is another example of a communication system 600 according to some embodiments. As used herein, the communication system 600 includes multiple access points (APs) 610 (with four exemplary APs 610A, 610B, 610C, and 610D being depicted) and multiple wireless devices, referred to in the context of communication system 600 as stations (ST As) 612 (referred to individually as STA 612A, ST A 612B, ST A 612C, ST A 612D, and STA 612E). STA 612A is served by AP 610A in a first basic service set (BSS) 620A. STA 610B and STA 610C are served by AP 610B in a second BSS, BSS 620B. STA 612D is served by AP 610C in a third BSS, BSS 620C. STA 612E is served by AP 610D in a fourth BSS, BSS 620D. Stations 612 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 612 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.P113660W00221
[0085] Each of STAs 612 may connect through a radio link to one of APs 610. For example, depending on location or channel conditions experienced by a given STA 612, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0086] Each AP 610 may provide data connectivity to STAs 612 connected to a particular AP 610. As illustrated, APs 610 may be connected to a data network 630. In this way, APs 610 may also provide data connectivity between STAs 612 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 612 and its serving AP 610 may be used for providing various kinds of services to STA 612, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 612 and / or on a device linked to STA 612. By way of example, Figure 6 illustrates an application service platform 632 provided in data network 630. The application(s) executed on STA 612 and / or on one or more other devices linked to STA 612 may use the radio link for data communication with one or more other STA 612 and / or the application service platform 632, thereby enabling utilization of the corresponding service(s) at STA 612.
[0087] Figure 7 shows a wireless device 700, which may be configured to operate in communication system 500 of Figure 5 or in communication system 600 of Figure 60. The wireless device 700 may be alternatively referred to as a UE 700, like a UE 512 within the context of communication system 500, or as a station (STA) 700 or as a non-access-point station (non-AP STA) 700, like a STA 612 within the context of the communication system 600, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle,P113660W00222vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0088] A wireless device 700 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 700 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 700 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 700 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0089] In particular embodiments, wireless device 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain embodiments of wireless device 700 may include all or a subset of the components shown in Figure 7. The level of integration between the components may vary from one embodiment of wireless device 700 to another. In general, in a particular embodiment of wireless device 700, processing circuitry 702, input / output interface 706, power source 708, memory 710, and communication interface 712 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 700. Further, certain embodiments of wireless devices 700 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0090] The processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 710. The processing circuitry 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more storedP113660W00223computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 702 may include multiple central processing units (CPUs).
[0091] In the example, the input / output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0092] In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of wireless device 700 via input circuitry or an interface such as an electrical power cable. Power source 708 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 700 to which power is supplied.
[0093] The memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 710 includes one or more programs 714, such as an operating system, web browser application, a widget, gadgetP113660W00224engine, or other application, and corresponding data 716. The memory 710 may store, for use by wireless device 700, any of a variety of various operating systems or combinations of operating systems.
[0094] The memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 710 may allow wireless device 700 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.
[0095] The processing circuitry 702 may be configured to communicate with an access network or other network via or using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0096] In the illustrated embodiment, communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voiceP113660W00225communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0097] In particular embodiments, wireless device 700 may provide an output of data captured via a sensor, through its communication interface 712, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 700 can be communicated through a wireless connection to a network node via another wireless device 700. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0098] As another example, wireless device 700 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 700 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0099] Wireless device 700, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical doorP113660W00226lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 700 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 700 shown in Figure 7.
[0100] As yet another specific example, in an loT scenario, wireless device 700 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 700 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 700 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 700 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0101] In practice, any number of wireless devices 700 may be used together with respect to a single use case. For example, a first wireless device 700 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 700 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 700 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 700 can also include more than one of the functionalities described above. For example, wireless device 700 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0102] Figure 8 shows a network node 800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network nodeP113660W00227800 may be configured to operate in communication system 500 of Figure 5, like network nodes 508 or 510, or in communication system 600 of Figure 6, like an AP 610 or a station 612. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, O-DU, O-CU).
[0103] Network nodes 800 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 800 may be a relay node or a relay donor node controlling a relay. Network nodes 800 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0104] Other examples of network nodes 800 include multiple transmission point (multi-TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0105] In particular embodiments, network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. In general, in a particular embodiment of network node 800, processing circuitry 802, memory 804, communication interface 806, and power source 808 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 800.
[0106] The network node 800 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which theP113660W00228network node 800 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 804 or portions of memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 800.
[0107] The processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 804, to provide network node 800 functionality.
[0108] In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.
[0109] The memory 804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-P113660W00229executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 802. The memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804 is integrated.
[0110] The communication interface 806 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 700 may be capable of wireless communication and communication interface 806 may also include radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, an antenna 810. Particular embodiments of radio front-end circuitry 818 include filter(s) 820 and amplifier(s) 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio frontend circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 818 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal(s) may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.[OHl] In certain alternative embodiments, network node 800 may be capable of wireless communication but does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806P113660W00230includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).
[0112] The antenna 810 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through one or more interfaces or ports.
[0113] The antenna 810, communication interface 806, and / or the processing circuitry 802 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 800. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuitry 802 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 800. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0114] The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808. As a further example, the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0115] Embodiments of the network node 800 may include additional components beyond those shown in Figure 8 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary toP113660W00231support the subject matter described herein. For example, the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.
[0116] Figure 9 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
[0117] Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0118] Hardware 904 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 908A and VM 908B (which may be collectively referred to as VMs 908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 908.P113660W00232
[0119] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0120] In the context of NFV, each of the VMs 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 908, and that part of hardware 904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 908 on top of the hardware 904 and corresponds to an application 902.
[0121] Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.
[0122] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein.P113660W00233Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0123] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
[0124] The following describes an embodiment according to 3GPP specifications.
[0125] According to the WI#2, the PCF may make policy decisions related with energy efficiency and energy saving. Those policy decisions can have an impact in the traffic delivered to the UE. However, no specific solution has been defined to enable a differentiated charging for the UE when those energy efficiency-related actions are taken for this UE. Ideally, when the network applies such an action to enhance energy efficiency that affects service delivery,P113660W00234the charging applied to this traffic should be different (i.e., reduced) compared to the one in regular circumstances.
[0126] Relying on existing charging mechanism to have the PCF assigning a different service-specific Rating Group for IP flows where energy efficiency decisions have been applied might be overly simplistic and restrictive. This approach could lead to the need for multiple Rating Groups for the same service, becoming unmanageable in scenarios involving multiple services and energy efficiency decisions.
[0127] This contribution proposes to extend the charging information provided in a PCC rule from the PCF to the SMF (N7 interface) including additional information about the “reason for a policy change”, where the energy efficiency could be one reason. Therefore, when the PCF applies policy decisions based on energy efficiency reasons, the PCF sends an update of the PCC rule to the SMF including the additional information with the reason indicating energy efficiency.
[0128] The solution enables the network may apply a differentiated (reduced) charging for the UE when service adjustment actions such as ones triggered by energy efficiency and energy saving energy are performed by the network. It also enables 5GC network to keep track of the reason of the impact in the service delivery.
[0129] The solution is made general enough to cover scenarios for actions not only related with energy efficiency but also other reasons, e.g. in traffic congestion scenarios.
[0130] It is proposed to agree the following solution to 3GPP TR 23.700-67 Solution related to Differentiated Charging when network performs service adjustment High-level solution principlesThe solution is based on following principles:- PCF adds an IE of “reason for a policy change” in charging info of the associated PCC rule when service adjustment is applied for an SDF.- SMF sends the reason for a policy change together with existing charging info to CHF.P113660W00235Although currently described for Session Policies, the solution can also be applied for AM policies and incorporate a “reason for change” for AM policy updates via the AMF to the CHF.Functional DescriptionThis solution addresses KI#2.It is proposed to extend the charging information provided in a PCC rule from the PCF to the SMF over the N7 interface with an additional IE (“reason for a policy change”) which indicates the reason for a policy decision applied for a UE, where the energy efficiency could be one of the reasons. See the example IE, marked in bolded text, in the table 4.1.4.2.1-1 of TS 29.512.Table 4.1.4.2.1-1: PCC rule information elementsInformation name Description Category Rule identifier Uniquely identifies the PCC rule, within a PDU Session. Mandatory It is used between PCF and SMF for referencing PCC rules.Service data flow detectionPrecedence Determines the order, in which the service data flow templates Mandatory are applied at service data flow detection, enforcement andcharging.Service Data Flow For IP PDU traffic: Either a list of service data flow filters or an Mandatory Template application identifier that references the corresponding application detection filter for the detection of the service data flow.For Ethernet PDU traffic: Combination of traffic patterns of theEthernet PDU traffic.Mute for notification Defines whether application's start or stop notification is to be Optional muted.ChargingCharging key The charging system (CHF) uses the charging key to determine Optional the tariff to apply to the service data flow.Reason for a Policy It indicates the reason of a policy decision that can imply an Optional Change impact in the service delivery of the UE, being energyP113660W00236efficiency (with different severity levels) one of the reasons.The new policy data may also be included.Service identifier The identity of the service or service component the service data Optional flow in a rule relates to.Sponsor Identifier An identifier, provided from the AF, which identifies the Sponsor, Optional used for sponsored flows to correlate measurements fromdifferent users for accounting purposes.Application Service An identifier, provided from the AF, which identifies the Optional Provider Identifier Application Service Provider, used for sponsored flows tocorrelate measurements from different users for accountingpurposes.Charging method Indicates the required charging method for the PCC rule. Optional Values: online or offline or none.Service Data flow Indicates whether the service data flow is allowed to start while Optional handling while the SMF is waiting for the response to the credit request. requesting credit Only applicable for charging method online.Measurement method Indicates whether the service data flow data volume, duration, Optional combined volume / duration or event shall be measured. This is applicable to reporting if the charging method is online or offline. Note: Event based charging is only applicable to predefined PCC rules and PCC rules used for application detection filter (i.e. with an application identifier).Application Function An identifier, provided from the AF, correlating the measurement Optional Record Information for the Charging key / Service identifier values in this PCC rule with application level reports.This new IE information element together with the charging rate will be forwarded by the SMF to the CHF. The CHF can take it into account when applying the charging and billing for the UE. The new information can be also used by the CHF to maintain some KPIs including information about whether the impact in the service delivery of a UE has been caused by network applying actions.P113660W00237The table below (from Table 6.2.1.3.1 of TS 32.255) shows how the example new IES, marked in bolded text, fits within a charging request:Table 6.2.1.3.1: Structure of PDU Container Information Information Element Category DescriptionTime of First Usage Oc This field holds the Timestamp when the first transmitted data packet of the service data flow matching the current used unit containerTime of Last Usage Oc This field holds the Timestamp when the last transmitted data packet of the service data flow matching the current used unit containerQoS Information Oc This field holds the QoS applied during the service data container intervalQoS Characteristics Oc This field holds the QoS characteristics applied for QoS information. It is only be used when the non-standardized 5QI is present in QoS information.AF Charging Identifier Oc A Charging Identifier, provided from the AF, may be used to correlate the measurement for the Charging key / Service identifier values in this PCC rule with application level reports.AF Charging Id String Oc A string that, may be provided from the AF instead of AF Charging Identifier, depending on support.Reason for Policy Change Oc It indicates the reason of a policy decision impacting the service delivery, e.g. energy efficiency (with different severity levels). The new policy data may also be included.User Location Information Oc This field holds the user location during the used unit container intervalP113660W00238Information Element Category DescriptionUE Time Zone Oc This field holds the Time Zone of where the UE is located, during the used unit container interval.Presence Reporting Area Oc This field holds the Presence Reporting Area Information Information of UE during the used unit container interval.Serving Network Function ID Oc Serving Network Function identifier.RAT Type Oc This field holds the RAT type during the used unit container interval.For MA PDU session, this field holds the RAT type associated to the access which activated the rating group.Sponsor Identity Oc This field holds the identifier of the sponsor when sponsored data connectivity is usedApplication Service Provider Oc This field holds the identifier of the application service Identity provider that is delivering a service to the end user.Charging Rule Base Name Oc This field holds the reference to group of PCC rules predefined at the SMF3GPP PS Data Off Status Oc This field holds the 3GPP Data off Status during the used unit container intervalMA PDU Steering functionality Oc This field holds the Steering functionality used during the used unit container interval when MA PDU sessionMA PDU Steering mode Oc This field holds the Steering mode used during the used unit container interval when MA PDU session.P113660W00239Information Element Category DescriptionT raffic Forwarding Way Oc This field holds the traffic forwarding way for the 5G VN group communication if present.If the SMF can distinguish the traffic forwarding way, the SMF reports the volume per traffic forwarding way. If the SMF cannot distinguish, the SMF reports the traffic and the corresponding traffic forwarding way (may be multiple).QoS Monitoring Report Oc This field holds the QoS monitoring result (i.e. , average packet delay per QoS flow per UE) for the service data flow.MBS Session ID Oc This field holds the MBS session identifier for the service data flow referring to clause 6.5.1 of TS 23.247
[0204] if present.MBS Delivery Method Oc This field holds the MBS traffic delivery method (i.e. 5GC Shared MBS traffic delivery method and 5GC Individual MBS traffic delivery method referring to clause 4.1 of TS 23.247
[0204] ) for the multicast communication if present.ProceduresThe picture (Figure 2a) shows the procedure for applying differentiated charging based on energy efficiency policy decisions as one reason example.Prerequisite: The PCF is retrieving the slice level energy consumption from OAM system.1. The UE triggers a PDU session establishment procedure according to 3GPP TS 23.502 clause 4.3.2.During the establishment procedure the PCF makes policy decisions and determines regular QoS (QoSl) and Charging information (Rating Group 1) for the traffic associated with appl.2. The CHF applies charging based on Rating Group 1 to the traffic of the UE for appl 3. At some point in time, the PCF is triggered to apply some policy decisions (e.g. to change QoS although some other actions could be decided), e.g. to reduce the energy consumption of the UE and / or NW slice.The PCF generates corresponding PCC rule including the new QoS (Qos_2) for the service, same Rating Group (RG_1) and the new “reason for policy decision” IEP113660W00240including “ energy _effi ci ency” as reason and “X” as severity level (for other use cases, other cause code and optionally severity level should be used). The PCF delivers the PCC rule to the SMF and SMF forwards the charging information to the CHF. Note: the changing the QoS is just one policy example, any service adjustment related policy decision can be applied to.4. Upon the reception of the information from the SMF, the CHF uses the rating group plus additional “Reason for policy decision” (the reason + the severity level) to apply differentiated (reduced) charging to the traffic of the UE.5. The CHF updates also new KPIs with information about reason for policy decisions and impacts on the service delivery.Impacts on existing services, entities and interfacesPCF:- Receive an anergy related trigger to update session policy data.Generate reason for policy decisions and include it as additional charging info of PCC rule to the SMF. The new policy data may also be includedSMFSend the reason for policy decisions to the CHF. The new policy data may also be includedCHF:Receive the reason for policy decisions from SMF.Use the reason for differentiated charging and KPI.AMF:Addition of “reason for change” for AM policy updates via the AMF to the CHF.P113660W00241ABBREVIATIONSAbbreviation Meaning3 GPP 3rd Generation Partnership Project5GC 5G CoreAF Application FunctionAM Access and MobilityAMF Access and Mobility Management Function CHF Charging FunctionEIF Energy Information FunctionEnC Energy ConsumptiongNB NR Node BIE Information ElementKPI Key Performance IndicatorLTE Long Term EvolutionNEF Network Exposure FunctionNF Network FunctionNG-RAN Next Generation Radio Access Network NR New RadioOAM Operations, Administration, and Maintenance 0-RAN Open Radio Access NetworkPCC Policy and Charging ControlPCF Policy Control FunctionPDU Packet Data UnitQoS Quality of ServiceRAN Radio Access NetworkRAT Radio Access TechnologyRG Rating GroupP113660W00242Abbreviation MeaningSBA Service Based Architecture SDF Service Data FlowSMF Session Management Function STA StationUDM Unified Data Management UE User EquipmentUPF User Plane FunctionVM Virtual MachineWLAN Wireless Local Area Network
Claims
P113660W00243CLAIMS1. A method performed by a policy control function (226), PCF, the method comprising:obtaining (301) energy consumption data;applying (302) one or more policy decisions based on the obtained energy consumption data;generating (303) a Policy and Charging Control, PCC, rule that includes at least a policy change reason information element, IE;sending (304) the PCC rule to a Session Management Function (228), SMF.
2. The method according to claim 1, wherein the energy consumption data includes one or more of user equipment (230), UE, energy consumption measures and / or network slice level energy consumption measures.
3. The method according to any one of claims 1 to 2, wherein the UE energy consumption data is obtained from an Energy Information Function (222), EIF, and / or the network slice level energy consumption data is obtained from an Operations, Administration, and Maintenance, 0AM, node.
4. The method according to any one of claims 1 to 3, wherein the one or more policy decisions pertain to reducing energy consumption of a UE and / or a network slice.
5. The method according to any one of claims 1 to 4, wherein the policy change reason information element includes a reason indicator and a severity level indicator.
6. The method according to any one of claims 1 to 5, wherein the reason indicator comprises an energy efficiency reason indicator or energy saving reason indicator.
7. The method according to any one of claims 1 to 6, wherein the PCC rule includes an updated Quality of Service, QoS, level and / or a rating group indicator.P113660W002448. The method according to any one of claims 1 to 7, wherein the SMF extracts and forwards to a charging function (224), CHF, charging information that includes data contained in the policy change reason information element.
9. The method according to any one of claims 1 to 8, wherein the CHF utilizes at least the policy change reason information element to apply differentiated charging to packet traffic of a user equipment (UE).
10. The method according to any one of claims 1 to 9, wherein the CHF also utilizes a rating group indicator to apply the differentiated charging to the packet traffic of the UE.
11. The method according to any one of claims 1 to 10, wherein the CHF is configured to update at least one key performance indicator, KPI, with information related to the policy change reason.
12. The method according to any one of claims 1 to 11, wherein the PCF is triggered to apply the one or more policy decisions based on a service adjustment applicable to the UE being performed.
13. A network node configured to host a policy control function, PCF, the network node comprising:a processing circuitry (802); andat least one memory (804) storing instructions executable by the processing circuitry to perform operations to:obtain (301) energy consumption data;apply (302) one or more policy decisions based on the obtained energy consumption data;generate (303) a Policy and Charging Control, PCC, rule that includes at least a policy change reason information element, IE;send (304) the PCC rule to a Session Management Function (228), SMF.P113660W0024514. The network node according to claim 13, wherein the at least one memory stores further instructions executable by the processing circuitry to perform further operations comprising operations of any one of claims 2 to 12.
15. A computer program product comprising a non-transitory computer readable medium storing instructions executable by processing circuitry of a network node (800) hosting a policy control function (226), PCF, the instructions executed by the processing circuitry (802) to perform operations comprising:obtain (301) energy consumption data;apply (302) one or more policy decisions based on the obtained energy consumption data;generate (303) a Policy and Charging Control, PCC, rule that includes at least a policy change reason information element, IE;send (304) the PCC rule to a Session Management Function (228), SMF.
16. The computer program product according to claim 15, wherein the non-transitory computer readable medium stores further instructions executable by the processing circuitry of the network node, the further instructions executed by the processing circuitry to perform further operations comprising operations of any one of claims 2 to 12.
17. A method performed by a policy control function, PCF, the method comprising:obtaining (401) network related data;applying (402) one or more policy decisions based on the obtained network related data;generating (403) a Policy and Charging Control, PCC, rule that includes at least a policy change reason information element, IE;sending (404) the PCC rule to a management function in a network.
18. The method according to claim 17, wherein the management function includes a Session Management Function (228), SMF, or an Access and Mobility Management Function, AMF.P113660W0024619. The method according to any one of claims 17 to 18, wherein the network related data includes one or more of user equipment (230), UE, energy consumption measures, and / or network slice level energy consumption measures.
20. The method according to any one of claims 17 to 19, wherein the one or more policy decisions pertain to access and mobility (AM) policies and / or user equipment (UE) policies.
21. The method according to any one of claims 17 to 20, wherein the policy change reason information element includes a reason indicator and a severity level indicator.
22. The method according to any one of claims 17 to 21, wherein the PCC rule includes an updated Quality of Service, QoS, level and / or a rating group indicator.
23. The method according to any one of claims 17 to 22, wherein the AMF extracts and forwards to a charging function (224), CHF, charging information that includes data contained in the policy change reason information element.
24. The method according to any one of claims 17 to 23, wherein the CHF utilizes the charging information to apply differentiated charging to packet traffic of a user equipment (UE).
25. The method according to any one of claims 17 to 24, wherein the CHF also utilizes a rating group indicator to apply the differentiated charging to the packet traffic of the UE.
26. The method according to any one of claims 17 to 25, wherein the CHF is configured to update at least one key performance indicator, KPI, with information related to the policy change reason.
27. The method according to any one of claims 17 to 26, wherein the PCF is triggered to apply the one or more policy decisions based on a service adjustment applicable to a user equipment (UE) being performed.
