CN115604769A - Apparatus for use in a wireless communication system - Google Patents

Abstract

The present application relates to an apparatus for use in a wireless communication system. An apparatus for use in an SMF node comprises a processor circuit configured to cause the SMF node, upon detecting a start of use of an edge application by a User Equipment (UE): sending a first charging data request to a charging function (CHF) node, wherein the first charging data request is for requesting the CHF node to reserve an initial number of units for a service associated with an edge application; and receiving a first billing data response from the CHF node, wherein the first billing data response is to grant an initial number of units to the service associated with the edge application, wherein the first billing data request includes an initial quota requested for the rating group of the service associated with the edge application, and the initial number of units is reserved for the service associated with the edge application based on the account balance associated with the edge application and the initial quota requested for the rating group of the service associated with the edge application.

Description

Apparatus for use in a wireless communication system

Cross Reference to Related Applications

This application is based on and claims priority from U.S. application No.63/220,084, filed 7/9/2021, the entire contents of which are incorporated herein by reference.

Technical Field

Embodiments of the present disclosure relate generally to the field of wireless communications, and more particularly, to an apparatus for use in a wireless communication system.

Background

Mobile communications have evolved from early speech systems to today's highly sophisticated integrated communication platforms. A 5G or New Radio (NR) wireless communication system will provide access to information and sharing of data by various users and applications anytime and anywhere.

Drawings

Embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.

Fig. 1 illustrates a flow diagram of a quality of service (QoS) related charging method for use in a Session Management Function (SMF) node, according to some embodiments of the present disclosure.

Fig. 2 illustrates a flow diagram of a QoS-related charging method for use in a charging function (CHF) node, according to some embodiments of the disclosure.

Fig. 3 illustrates a timing diagram of a QoS-related charging procedure implemented between an SMF node and a CHF node, according to some embodiments of the present disclosure.

Fig. 4 illustrates a flow diagram of a session-related charging method with QoS for use in an edge-enabled server (EES) according to some embodiments of the present disclosure.

Fig. 5 illustrates a flow diagram of a session-related charging method with QoS for use in a CHF node according to some embodiments of the present disclosure.

Fig. 6 illustrates a timing diagram of an Immediate Event Charging (IEC) process for creating sessions with QoS, according to some embodiments of the disclosure.

Fig. 7 illustrates a timing diagram of a post-charging (PEC) process for creating sessions with QoS according to some embodiments of the present disclosure.

Fig. 8 illustrates a timing diagram of an IEC procedure for updating sessions with QoS according to some embodiments of the present disclosure.

Fig. 9 illustrates a timing diagram of a PEC process for updating sessions with QoS according to some embodiments of the present disclosure.

Fig. 10 illustrates a timing diagram of a PEC process for session notification with QoS according to some embodiments of the present disclosure.

Fig. 11 shows a schematic diagram of a network according to various embodiments of the present disclosure.

Fig. 12 shows a schematic diagram of a wireless network according to various embodiments of the present disclosure.

Fig. 13 illustrates a block diagram of components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, in accordance with various embodiments of the present disclosure.

Detailed Description

Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of the disclosure to others skilled in the art. It will be apparent, however, to one skilled in the art that many alternative embodiments may be practiced using portions of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. It will be apparent, however, to one skilled in the art that alternative embodiments may be practiced without these specific details. In other instances, well-known features may be omitted or simplified in order not to obscure the illustrative embodiments.

Further, various operations will be described as multiple discrete operations in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

The phrases "in an embodiment," "in one embodiment," and "in some embodiments" are used repeatedly herein. Such phrases are not generally referring to the same embodiment; however, they may also refer to the same embodiment. The terms "comprising," "having," and "including" are synonymous, unless the context dictates otherwise. The phrases "A or B" and "A/B" mean "(A), (B), or (A and B)".

Currently, 5G wireless communication systems can support not only edge computing, but also provide quality of service (QoS) control and delivery capabilities to support edge applications with sensitive performance requirements, especially in terms of delay.

The actual QoS delivered by a 5G wireless communication system to support edge computing may impact the billing of the system capabilities provided to the subscriber. For example, for two subscribers consuming the same amount of data for the same edge application in the same Public Land Mobile Network (PLMN), if different QoS is provided to the subscribers, they may need to be charged differently according to the QoS information monitored separately for the two subscribers.

However, there is no QoS-related charging scheme for the Application Service Provider (ASP) associated with the edge application and no session-related charging scheme with QoS associated with the edge application.

QoS-related charging scheme for ASPs associated with edge applications

Fig. 1 illustrates a flow diagram of a QoS-related charging method 100 for use in a Session Management Function (SMF) node, in which a Charging Trigger Function (CTF) is implemented in the SMF node, according to some embodiments of the present disclosure. As shown in fig. 1, the QoS-related charging method 100 includes: s102, when detecting that a User Equipment (UE) starts to use a marginal application, sending a first charging data request to a charging function (CHF) node, wherein the first charging data request is used for requesting the CHF node to reserve an initial unit number for a service associated with the marginal application and comprises an initial quota requested by a rating group of the service associated with the marginal application; and S104 receiving a first billing data response from the CHF node, wherein the first billing data response is to grant an initial number of units to the service associated with the edge application, and the initial number of units is reserved for the service associated with the edge application based on the account balance associated with the edge application and an initial quota requested for a rating group of the service associated with the edge application.

In some embodiments, the QoS-related charging method 100 further comprises, during use of the edge application by the UE: sending a second charging data request to the CHF node, wherein the second charging data request is for requesting the CHF node to reserve a new number of units for the service associated with the edge application and includes a new quota requested for a rating group for the service associated with the edge application; and receiving a second billing data response from the CHF node, wherein the second billing data response is for granting a new number of units to the service associated with the edge application, and the new number of units is reserved for the service associated with the edge application based on the account balance associated with the edge application and a new quota requested for the rating group of the service associated with the edge application.

In some embodiments, the QoS-related charging method 100 further comprises, during use of the edge application by the UE: sending a second charging data request to the CHF node, wherein the second charging data request is for reporting to the CHF node a current number of units that have been used for services associated with the edge application and QoS information monitored for service flows associated with the edge application; and receiving a second charging data response from the CHF node, wherein the second charging data response is to provide a notification to the SMF node as to whether more units should be requested for the service associated with the edge application or whether the service delivery associated with the edge application should be terminated, the second charging data request includes a current number of units subnumbers of the rating group that has been used for the service associated with the edge application, a determination is made as to whether more units should be requested for the service associated with the edge application or whether the service delivery associated with the edge application should be terminated based on the account balance associated with the edge application and the current number of units subnumbers of the rating group that has been used for the service associated with the edge application, and the account balance associated with the edge application is determined based on the current number of units of the rating group that has been used for the service associated with the edge application and the QoS information monitored for the service flow associated with the edge application.

In some embodiments, the QoS-related charging method 100 further comprises, upon detecting that the UE stops using the edge application: sending a third charging data request to the CHF node, wherein the third charging data request is for reporting to the CHF node charging data related to termination of a service associated with the edge application and a final number of units of the rating group that have been used for the service associated with the edge application; and receiving a third charging data response from the CHF node, wherein the third charging data response is for providing a notification to the SMF node that a charging termination process associated with the edge application has been performed, the charging termination process associated with the edge application being performed based on the charging data related to the service termination associated with the edge application and the final number of units of the rating group that have been used for the service associated with the edge application.

Fig. 2 illustrates a flow diagram of a QoS-related charging method 200 for use in a CHF node, according to some embodiments of the present disclosure. As shown in fig. 2, the QoS-related charging method 200 includes: s202, receiving a first charging data request from an SMF node, wherein the first charging data request is used for requesting the CHF node to reserve an initial unit number for a service associated with an edge application and comprises an initial quota requested for a rating group of the service associated with the edge application; s204, determining that an initial unit number can be reserved for the service associated with the edge application based on the account balance associated with the edge application and the initial quota requested for the rating group of the service associated with the edge application; and S206, sending a first charging data response to the SMF node, wherein the first charging data response is used to grant an initial number of units to the service associated with the edge application.

In some embodiments, the QoS-related charging method 200 further comprises: receiving a second billing data request from the SMF node, wherein the second billing data request requests that the CHF node reserve a new number of units for the service associated with the edge application and includes a new quota requested for a rating group for the service associated with the edge application; determining, based on an account balance associated with the edge application and a new quota requested for a rating group of services associated with the edge application, that a new number of units can be reserved for the services associated with the edge application; and sending a second charging data response to the SMF node, wherein the second charging data response is for granting a new number of units to the service associated with the edge application.

In some embodiments, the QoS-related charging method 200 further comprises: receiving a second charging data request from the SMF node, wherein the second charging data request is for reporting to the CHF node a current number of units that have been used for a service associated with the edge application and QoS information monitored for a service flow associated with the edge application and includes a current number of units of the rating group that have been used for the service associated with the edge application; determining whether more units should be requested for the service associated with the edge application or whether the service delivery associated with the edge application should be terminated based on the account balance associated with the edge application and the current number of units that have been used for the rating group for the service associated with the edge application; and sending a second charging data response to the SMF node, wherein the second charging data response is for providing a notification to the SMF node as to whether more units should be requested for the service associated with the edge application or whether the delivery of the service associated with the edge application should be terminated, and wherein the account balance associated with the edge application is determined based on the QoS information monitored for the service flow associated with the edge application and the current number of units of the rating group that have been used for the service associated with the edge application.

In some embodiments, the QoS-related charging method 200 further comprises: receiving a third charging data request from the SMF node, wherein the third charging data request is for reporting charging data relating to termination of a service associated with the edge application and a final number of units of the rating group that have been used for the service associated with the edge application; performing a billing termination process associated with the edge application based on the service termination related billing data associated with the edge application and the final number of units of the rating group that have been used for the service associated with the edge application; and sending a third charging data response to the SMF node, wherein the third charging data response is for providing notification to the SMF node that the charging termination process associated with the edge application has been performed.

In some embodiments, the QoS-related charging method 200 further comprises: aggregating usage reports associated with more than one edge application from the SMF nodes, wherein the usage reports associated with each edge application include a final number of units of a rating group that have been used for a service associated with the edge application and QoS information monitored for a service flow associated with the edge application; and sending, via a Charging Gateway Function (CGF) node, an aggregated usage report associated with more than one edge application to an accounting domain.

When implementing the QoS-related charging method 100 in an SMF node and/or the QoS charging method 200 in a CHF node, for two edge applications consuming the same amount of data in the same PLMN, the ASPs associated with the two edge applications may be charged differently because the rating group of the service associated with one of the two edge applications may be different from the rating group of the service associated with the other of the two edge applications, and the different rating groups are typically associated with different qoss. Further, when QoS information monitored for service flows respectively associated with two edge applications is provided from the SMF node to the CHF node, the ASPs associated with the two edge applications may be charged differently based on the QoS information monitored for the service flows respectively associated with the two edge applications.

Fig. 3 illustrates a timing diagram of a QoS-related charging procedure 300 implemented between an SMF node and a CHF node, according to some embodiments of the present disclosure. As shown in fig. 3, the QoS-related charging procedure 300 includes:

s301, the SMF node detects that the UE starts using the edge application, which triggers the delivery procedure.

S302, the SMF node sends a first accounting data request to the CHF node to request the CHF node to reserve an initial number of units for the service associated with the edge application, wherein an initial quota requested for a rating group for the service associated with the edge application is included in the first accounting data request.

S303, the CHF node performs account and reservation control associated with the edge application. In particular, the CHF node checks whether a respective fund on an account balance associated with the edge application can be reserved for each rating group of the service associated with the edge application based on the initial quota requested for the rating group of the service associated with the edge application, and performs the respective reservation for each rating group of the service associated with the edge application if the account balance associated with the edge application has sufficient funds.

S304, the CHF node opens a Charging Data Record (CDR) for the service associated with the edge application based on the first charging data request.

S305, the CHF node sends a first charging data response to the SMF node to grant a respective initial number of unit sub-numbers to each rating group for the service associated with the edge application.

S306, the SMF node executes the supervision and QoS monitoring of the grant unit. That is, the SMF monitors the consumption of units per rating group granted to services associated with the edge application and QoS information of service flows associated with the edge application.

S307, when the UE edge application usage continues, the SMF node continues to deliver the service associated with the edge application.

S308, a trigger for quota management or usage reporting is satisfied.

S309, the SMF node sends a second charging data request to the CHF node to request the CHF node to reserve a new number of units for the service associated with the edge application or to report a current number of units already used for the service associated with the edge application and the monitored QoS information for the service flow associated with the edge application. In the case that the second charging data request is for requesting that the CHF node reserve a new number of units for the service associated with the edge application, the new quota requested for the rating group for the service associated with the edge application is included in the second charging data request. In case the second charging data request is for reporting a current number of units already used for the service associated with the edge application, the current number of units of the rating group already used for the service associated with the edge application is included in the second charging data request.

S310, where the second charging data request is for requesting the CHF node to reserve a new number of units for the service associated with the edge application, the CHF node performs account and reservation control associated with the edge application (similar to the account and reservation control performed in S303). Where the second billing data request is for reporting a current number of units already used for services associated with the edge application and QoS information monitored for service flows associated with the edge application, the CHF node may deduct funds on an account balance associated with the edge application and determine whether more units should be requested for the services associated with the edge application or whether a service delivery associated with the edge application should be terminated.

S311, the CHF node updates the CDR for the service associated with the edge application based on the second charging data request.

S312, in the event that the second charging data request is for requesting the CHF node to reserve a new number of units for the service associated with the edge application, the CHF node sends a second charging data response to the SMF node to grant the new number of units to the service associated with the edge application. Where the second charging data request is for reporting a current number of units already used for the service associated with the edge application and the monitored QoS information for the service flow associated with the edge application, the CHF node sends a second charging data response to the SMF node to provide notification as to whether more units should be requested for the service associated with the edge application or whether the service delivery associated with the edge application should be terminated.

S313, the SMF node continues to deliver the service associated with the edge application.

S314, the SMF node detects that the UE stops using the edge application, which triggers the post-delivery procedure.

S315, the SMF node sends a third charging data request to the CHF node to report charging data related to termination of the service associated with the edge application to the CHF node, wherein a final number of units of the rating group that have been used for the service associated with the edge application is included in the third charging data request.

At S316, the CHF node performs account control associated with the edge application. In particular, the CHF node performs a service termination process that includes deducting funds on account balances associated with the edge application using the reported billing data and the final number of units of the rating group that have been used for the service associated with the edge application.

S317, the CHF node closes the CDR for the service associated with the edge application based on the third charging data request.

S318, the CHF node sends a third charging data response to the SMF node to inform the SMF node that the charging termination process associated with the edge application has been performed.

Session-related charging scheme with QoS associated with edge applications

Fig. 4 illustrates a flow diagram of a session-related charging method with QoS 400 for use in an edge-enabled server (EES) according to some embodiments of the present disclosure. As shown in fig. 4, the session related charging method with QoS 400 includes: s402, when receiving a session creation or update request with QoS from an Edge Application Server (EAS) or detecting a user plane event for the session with QoS from a 5G core network (5 GC), sending a charging data request to a CHF node; and S404, receiving a charging data response from the CHF node, the charging data response being used to inform the EES of the result of the charging data request.

In some embodiments, session related charging method with QoS 400 further includes, in the event a session creation or update request with QoS is received from EAS, after or before sending a request for charging data to the CHF node: a session creation or update with QoS response is sent to the EAS for notifying the EAS of the results of the session creation or update with QoS request.

In some embodiments, session related charging method with QoS 400 further includes, in the event that a user plane event for the session with QoS is detected from the 5GC, prior to sending the charging data request to the CHF node: a session event notification with QoS is sent to the EAS.

Fig. 5 illustrates a flow diagram of a session-related charging method 500 with QoS for use in a CHF node, according to some embodiments of the present disclosure. As shown in fig. 5, a method 500 for session related charging with QoS includes: s502, receiving a charging data request associated with a session with QoS from an EES; s504, creating CDR based on the charging data request; and S506, sending a charging data response associated with the session with QoS to the EES.

In some embodiments, the charging data request is associated with a session creation request with QoS, a session update request with QoS, or a session event notification with QoS.

In some embodiments, the charging data request is for Instant Event Charging (IEC) or post-event charging (PEC).

FIG. 6 illustrates a timing diagram of an IEC process 600 for creating a session with QoS according to some embodiments of the disclosure. As shown in FIG. 6, IEC process 600 includes:

s601, the EAS sends a session creation request with QoS to the EES.

S601ch-a, the EES generates charging data related to the session creation request with QoS and sends a charging data request to the CHF node to request the CHF node to process the related charging data to generate the CDR.

S601ch-b, the CHF node stores the relevant charging data and creates a CDR associated with the charging data request.

S601ch-c, the CHF node sends a charging data response to the EES to inform the EES of the result of the charging data request.

S602, the EES subscribes to Protocol Data Unit (PDU) session state monitoring from the 5GC and requests data related to the session with QoS.

S603, the EES sends a session creation response with QoS to the EAS.

Fig. 7 illustrates a timing diagram of a PEC process 700 for creating sessions with QoS according to some embodiments of the present disclosure. As shown in fig. 7, the PEC process 700 includes:

s701, the EAS sends a session creation request with QoS to the EES.

S702, the EES subscribes to the PDU session status monitor side from the 5GC and requests data related to the session with QoS.

S703, the EES sends a session creation response with QoS to the EAS.

S703ch-a, the EES generates charging data associated with the session creation request with QoS and sends a charging data request to the CHF node to request the CHF node to process the associated charging data to generate the CDR.

S703ch-b, the CHF node stores the relevant charging data and creates a CDR associated with the charging data request.

S703ch-c, the CHF node sends a charging data response to the EES to inform the EES of the result of the charging data request.

FIG. 8 illustrates a timing diagram of an IEC process 800 for updating a session with QoS according to some embodiments of the disclosure. As shown in fig. 8, IEC process 800 includes:

s801, the EAS sends a session update request with QoS to the EES.

S801ch-a, the EES generates charging data related to the session update request with QoS and sends a charging data request to the CHF node to request the CHF node to process the related charging data to generate the CDR.

S801ch-b, the CHF node stores the relevant charging data and creates a CDR associated with the session update request with QoS.

S801ch-c, the CHF node sends a charging data response to the EES to inform the EES of the result of the charging data request.

The EES updates data associated with the session having the QoS to 5GC S802.

S803, the EES sends a session update response with QoS to the EAS.

Fig. 9 illustrates a timing diagram of a PEC process 900 for updating sessions with QoS according to some embodiments of the present disclosure. As shown in fig. 9, the PEC process 900 includes:

s901, the EAS sends a session update request with QoS to the EES.

The EES updates data associated with the QoS session to 5GC S902.

S903, the EES sends a session update response with QoS to the EAS.

S903ch-a, the EES generates charging data related to the session update request with QoS and sends a charging data request to the CHF node to request the CHF node to process the related charging data to generate the CDR.

S903ch-b, the CHF node stores the relevant charging data and creates a CDR associated with the charging data request.

S903ch-c, the CHF node sends a charging data response to the EES to inform the EES of the result of the charging data request.

Fig. 10 illustrates a timing diagram of a PEC process 1000 for session notification with QoS according to some embodiments of the present disclosure. As shown in fig. 10, the PEC process 1000 includes:

s1001, EES detects a user plane event for a session with QoS from 5GC.

S1002, the EES sends a session notification with QoS to the EAS.

S1002ch-a, the EES generates charging data related to the session notification with QoS and sends a charging data request to the CHF node to request the CHF node to process the related charging data to generate the CDR.

S1002ch-b, the CHF node stores the relevant charging data and creates a CDR associated with the charging data request.

S1002ch-c, the CHF node sends a charging data response to the EES to inform the EES of the result of the charging data request.

FIGS. 11-12 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

Fig. 11 shows a schematic diagram of a network 1100 according to various embodiments of the present disclosure. The network 1100 may operate in accordance with 3GPP technical specifications for Long Term Evolution (LTE) or 5G/NR systems. However, the exemplary embodiments are not limited in this respect and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems and the like.

Network 1100 may include a UE 1102, which may include any mobile or non-mobile computing device designed to communicate with a Radio Access Network (RAN) 1104 via an over-the-air connection. The UE 1102 may be, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, a dashboard, a heads-up display device, an on-board diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic/engine control unit, an electronic/engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network device, a machine-to-machine (M2M) or device-to-device (D2D) device, an internet of things (IoT) device, and/or the like.

In some embodiments, the network 1100 may include multiple UEs directly coupled to each other through a sidelink interface. The UE may be an M2M/D2D device that communicates using a physical sidelink channel (e.g., without limitation, a Physical Sidelink Broadcast Channel (PSBCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Fundamental Channel (PSFCH), etc.).

In some embodiments, the UE 1102 may also communicate with an Access Point (AP) 1106 over an over-the-air connection. AP 1106 may manage Wireless Local Area Network (WLAN) connections, which may be used to offload some/all network traffic from RAN 1104. The connection between the UE 1102 and the AP 1106 may be consistent with any IEEE 802.11 protocol, wherein the AP 1106 may be wireless fidelity (WiFi)

A router. In some embodiments, the UE 1102, RAN 1104, and AP 1106 may utilize cellular WLAN aggregation (e.g., LTE-WLAN aggregation (LWA)/lightweight IP (LWIP)). Cellular WLAN aggregation may involve configuring the UE 1102 by the RAN 1104 to utilize both cellular radio resources and WLAN resources.

RAN 1104 may include one or more access nodes, e.g., access Node (AN) 1108. The AN 1108 can terminate air interface protocols of the UE 1102 by providing access stratum protocols including a Radio Resource Control (RRC) protocol, a Packet Data Convergence Protocol (PDCP), a Radio Link Control (RLC) protocol, a Medium Access Control (MAC) protocol, and AN L1 protocol. In this manner, the AN 1108 may enable a data/voice connection between the Core Network (CN) 1120 and the UE 1102. In some embodiments, the AN 1108 may be implemented in a discrete device or as one or more software entities running on a server computer (a virtual network may be referred to as a distributed RAN (CRAN) or virtual baseband unit pool, as part of a virtual network, for example). The AN 1108 may be referred to as a Base Station (BS), next generation base station (gNB), RAN node, evolved node B (eNB), next generation eNB (ng-eNB), node B (NodeB), roadside unit (RSU), transmit receive point (TRxP), transmit point (TRP), etc. The AN 1108 may be a macrocell base station or a low power base station that provides for microcells, picocells, or other similar cells having smaller coverage areas, smaller user capacities, or higher bandwidths than macrocells.

In embodiments where the RAN 1104 includes multiple ANs, the ANs may be coupled to each other over AN X2 interface (if the RAN 1104 is AN LTE RAN) or AN Xn interface (if the RAN 1104 is a 5G RAN). In some embodiments, the X2/Xn interface, which may be separated into a control/user plane interface, may allow the AN to communicate information related to handover, data/context transfer, mobility, load management, interference coordination, and the like.

The ANs of the RAN 1104 can each manage one or more cells, groups of cells, component carriers, etc., to provide the UE 1102 with AN air interface for network access. The UE 1102 may be simultaneously connected with multiple cells provided by the same or different ANs of the RAN 1104. For example, UE 1102 and RAN 1104 may use carrier aggregation to allow UE 1102 to connect with multiple component carriers, each corresponding to a primary cell (PCell) or a secondary cell (SCell). In a dual connectivity scenario, the first AN may be a master node providing a Master Cell Group (MCG) and the second AN may be a secondary node providing a Secondary Cell Group (SCG). The first/second AN can be any combination of eNB, gNB, ng-eNB, etc.

RAN 1104 may provide an air interface over a licensed spectrum or an unlicensed spectrum. To operate in unlicensed spectrum, a node may use a License Assisted Access (LAA), enhanced LAA (eLAA), and/or further enhanced LAA (feLAA) mechanism based on the Carrier Aggregation (CA) technology of PCell/Scell. Prior to accessing the unlicensed spectrum, the node may perform a media/carrier sensing operation based on, for example, a Listen Before Talk (LBT) protocol.

In a vehicle-to-everything (V2X) scenario, the UE 1102 or AN 1108 may be or act as a Road Side Unit (RSU), which may refer to any transport infrastructure entity for V2X communication. The RSU may be implemented in or by AN appropriate AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; an RSU implemented in or by a next generation NodeB (gNB) may be referred to as a "gNB-type RSU" or the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located at the roadside that provides connection support to passing vehicular UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic volume statistics, media, and applications/software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications required for high speed events (e.g., collision avoidance, traffic warnings, etc.). Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., ethernet) to a traffic signal controller or backhaul network.

In some embodiments, RAN 1104 may be an LTE RAN 1110 including an evolved node B (eNB), e.g., eNB 1112. The LTE RAN 1110 may provide an LTE air interface with the following characteristics: subcarrier spacing (SCS) of 15 kHz; a single carrier frequency division multiple access (SC-FDMA) waveform for Uplink (UL) and a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform for Downlink (DL); turbo codes for data and TBCC for control, etc. The LTE air interface may rely on channel state information reference signals (CSI-RS) for CSI acquisition and beam management; relying on a Physical Downlink Shared Channel (PDSCH)/Physical Downlink Control Channel (PDCCH) demodulation reference signal (DMRS) for PDSCH/PDCCH demodulation; and relying on Cell Reference Signals (CRS) for cell search and initial acquisition, channel quality measurements, and channel estimation, and on channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operate on the 6GHz sub-band.

In some embodiments, RAN 1104 may be a Next Generation (NG) -RAN 1114 having a gNB (e.g., gNB 1116) or a gn-eNB (e.g., NG-eNB 1118). The gNB 1116 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 1116 may be connected to the 5G core through an NG interface, which may include an N2 interface or an N3 interface. The NG-eNB 1118 may also be connected with the 5G core over the NG interface, but may be connected with the UE over the LTE air interface. The gNB 1116 and the ng-eNB 1118 may be connected to each other through an Xn interface.

In some embodiments, the NG interface may be divided into two parts, an NG user plane (NG-U) interface, which carries traffic data between nodes of the UPF 1148 and the NG-RAN 1114 (e.g., an N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between nodes of the access and mobility management function (AMF) 1144 and the NG-RAN 1114 (e.g., an N2 interface).

The NG-RAN 1114 may provide a 5G-NR air interface with the following characteristics: variable SCS; cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) for DL, CP-OFDM and DFT-s-OFDM for UL; polarity, repetition, simplex, and reed-muller codes for control; and low density parity check codes (LDPC) for the data. The 5G-NR air interface may rely on channel state reference signals (CSI-RS), PDSCH/PDCCH demodulation reference signals (DMRS), similar to the LTE air interface. The 5G-NR air interface may not use Cell Reference Signals (CRS), but may use Physical Broadcast Channel (PBCH) demodulation reference signals (DMRS) for PBCH demodulation; performing phase tracking of the PDSCH using a Phase Tracking Reference Signal (PTRS); and time tracking using the tracking reference signal. The 5G-NR air interface may operate over the FR1 frequency band, which includes the 6GHz sub-band, or the FR2 frequency band, which includes the 24.25GHz to 52.6GHz frequency band. The 5G-NR air interface may include synchronization signals and PBCH blocks (SSBs), which are regions of a downlink resource grid including Primary Synchronization Signals (PSS)/Secondary Synchronization Signals (SSS)/PBCH.

In some embodiments, the 5G-NR air interface may use a bandwidth portion (BWP) for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, the UE 1102 may be configured with multiple BWPs, where each BWP configuration has a different SCS. When the BWP change is indicated to the UE 1102, the SCS of the transmission also changes. Another use case for BWP is related to power saving. In particular, the UE 1102 may be configured with multiple BWPs with different numbers of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWPs containing a smaller number of PRBs may be used for data transmission with smaller traffic load while allowing power savings at the UE 1102 and, in some cases, at the gNB 1116. BWPs containing a large number of PRBs may be used in scenarios with higher traffic loads.

RAN 1104 is communicatively coupled to CN 1120, which comprises network elements, to provide various functions to support data and telecommunications services to customers/subscribers (e.g., users of UE 1102). The components of CN 1120 may be implemented in one physical node or in different physical nodes. In some embodiments, network Function Virtualization (NFV) may be used to virtualize any or all functions provided by network elements of CN 1120 onto physical computing/storage resources in servers, switches, and the like. Logical instances of CN 1120 may be referred to as network slices and logical instances of a portion of CN 1120 may be referred to as network subslices.

In some embodiments, CN 1120 may be LTE CN 1122, which may also be referred to as an Evolved Packet Core (EPC). LTE CN 1122 may include a Mobility Management Entity (MME) 1124, a Serving Gateway (SGW) 1126, a serving General Packet Radio Service (GPRS) support node (SGSN) 1128, a Home Subscriber Server (HSS) 1130, a Proxy Gateway (PGW) 1132, and a policy control and charging rules function (PCRF) 1134, which are coupled to each other by an interface (or "reference point") as shown. The functions of the elements of LTE CN 1122 can be briefly introduced as follows.

The MME 1124 may implement mobility management functions to track the current location of the UE 1102 to facilitate paging, bearer activation/deactivation, handover, gateway selection, authentication, etc.

The SGW 1126 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 1122. SGW 1126 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

The SGSN 1128 may track the location of the UE 1102 and perform security functions and access control. In addition, SGSN 1128 may perform EPC inter-node signaling for mobility between different Radio Access Technology (RAT) networks; PDN and S-GW selection specified by the MME 1124; MME selection for handover, etc. An S3 reference point between the MME 1124 and SGSN 1128 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active state.

HSS 1130 may include a database for network users that includes subscription-related information that supports network entities handling communication sessions. HSS 1130 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependency, etc. An S6a reference point between HSS 1130 and MME 1124 may enable transmission of subscription and authentication data for authenticating/authorizing user access to LTE CN 1120.

PGW 1132 may terminate the SGi interface towards a Data Network (DN) 1136, which may include an application/content server 1138. PGW 1132 may route data packets between LTE CN 1122 and data network 1136. PGW 1132 may couple with SGW 1126 through an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 1132 may also include nodes (e.g., PCEFs) for policy enforcement and charging data collection. Additionally, the SGi reference point between PGW 1132 and data network 1136 may be, for example, an operator external public, private PDN, or an operator internal packet data network used to provide IP Multimedia Subsystem (IMS) services. PGW 1132 may be coupled to PCRF 1134 via a Gx reference point.

PCRF 1134 is a policy and charging control element of LTE CN 1122. The PCRF 1134 may be communicatively coupled to the application/content server 1138 to determine appropriate quality of service (QoS) and charging parameters for the service flow. PCRF 1132 may provide relevant rules to the PCEF (via the Gx reference point) with appropriate Traffic Flow Templates (TFTs) and QoS Class Identifiers (QCIs).

In some embodiments, CN 1120 may be a 5G core network (5 GC) 1140. The 5GC 1140 may include an authentication server function (AUSF) 1142, an access and mobility management function (AMF) 1144, a Session Management Function (SMF) 1146, a User Plane Function (UPF) 1148, a Network Slice Selection Function (NSSF) 1150, a network open function (NEF) 1152, an NF storage function (NRF) 1154, a Policy Control Function (PCF) 1156, a Unified Data Management (UDM) 1158, and an Application Function (AF) 1160, which are coupled to each other by an interface (or "reference point") as shown. The functions of the elements of 5GC 1140 can be briefly described as follows.

The AUSF 1142 may store data for authentication of the UE 1102 and process authentication related functions. The AUSF 1142 may facilitate a common authentication framework for various access types. The AUSF 1142 may exhibit a Nausf service based interface in addition to communicating with other elements of the 5GC 1140 through reference points as shown.

The AMF 1144 may allow other functions of the 5GC 1140 to communicate with the UE 1102 and the RAN 1104 and subscribe to notifications about mobility events of the UE 1102. The AMF 1144 may be responsible for registration management (e.g., registering the UE 1102), connection management, reachability management, mobility management, lawful interception of AMF related events, and access authentication and authorization. AMF 1144 may provide for transmission of Session Management (SM) messages between UE 1102 and SMF 1146 and act as a transparent proxy for routing SM messages. The AMF 1144 may also provide for the transmission of SMS messages between the UE 1102 and the SMSF. The AMF 1144 may interact with the AUSF 1142 and the UE 1102 to perform various security anchor and context management functions. Further, AMF 1144 may be a termination point of the RAN CP interface, which may include or be an N2 reference point between RAN 1104 and AMF 1144; the AMF 1144 may serve as a termination point for NAS (N1) signaling and perform NAS ciphering and integrity protection. The AMF 1144 may also support NAS signaling with the UE 1102 over the N3 IWF interface.

The SMF 1146 may be responsible for SM (e.g., tunnel management between the UPF 1148 and the AN 1108, session establishment); UE IP address assignment and management (including optional authorization); selection and control of the UP function; configuring flow control at the UPF 1148 to route traffic to the appropriate destination; termination of the interface to the policy control function; controlling a portion of policy enforcement, charging, and QoS; lawful interception (for SM events and interface to the LI system); terminate the SM portion of the NAS message; a downlink data notification; initiating AN specific SM message (sent to AN 1108 over N2 via AMF 1144); and determining the SSC pattern for the session. SM may refer to management of PDU sessions, and a PDU session or "session" may refer to a PDU connection service that provides or enables exchange of PDUs between the UE 1102 and the data network 1136.

The UPF 1148 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point to interconnect with the data network 1136, and a branch point to support multi-homed PDU sessions. The UPF 1148 may also perform packet routing and forwarding, perform packet inspection, perform user plane part of policy rules, lawful intercepted packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1148 may include an uplink classifier to support routing of traffic flows to a data network.

The NSSF 1150 may select a set of network slice instances that serve the UE 1102. NSSF 1150 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and mapping to a single NSSAI (S-NSSAI) of the subscription, if desired. The NSSF 1150 may also determine a set of AMFs to use for serving UE 1102, or determine a list of candidate AMFs, based on a suitable configuration and possibly by querying NRF 1154. The selection of a set of network slice instances for the UE 1102 may be triggered by the AMF 1144 (to which the UE 1102 registers by interacting with the NSSF 1150), which may result in a change in the AMF. NSSF 1150 may interact with AMF 1144 via the N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). Further, the NSSF 1150 may expose an interface based on the NSSF service.

NEF 1152 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure/re-exposure, AF (e.g., AF 1160), edge computing or fog computing systems, and the like. In these embodiments, NEF 1152 may authenticate, authorize, or limit AF. NEF 1152 may also translate information exchanged with AF 1160 and information exchanged with internal network functions. For example, the NEF 1152 may convert between the AF service identifier and the internal 5GC information. NEF 1152 may also receive information from other NFs based on their public capabilities. This information may be stored as structured data at NEF 1152 or at data store NF using a standardized interface. NEF 1152 may then re-expose the stored information to other NFs and AFs, or for other purposes such as analysis. In addition, NEF 1152 may expose an interface based on the Nnef service.

NRF 1154 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 1154 also maintains information on available NF instances and the services it supports. As used herein, the terms "instantiate," "instance," and the like, may refer to creating an instance, "instance" may refer to a specific occurrence of an object, which may occur, for example, during execution of program code. Further, NRF 1154 may expose an interface based on an nrrf service.

PCF 1156 may provide policy rules to control plane functions to enforce these policy rules and may also support a unified policy framework to manage network behavior. The PCF 1156 may also implement a front end to access subscription information related to policy decisions in the UDR of the UDM 1158. In addition to communicating with functions through reference points as shown, PCF 1156 also presents an interface based on Npcf services.

UDM 1158 may process subscription-related information to support network entities handling communication sessions and may store subscription data for UE 1102. For example, subscription data may be communicated via an N8 reference point between UDM 1158 and AMF 1144. The UDM 1158 may comprise two parts: application front end and User Data Record (UDR). The UDR may store policy data and subscription data for UDM 1158 and PCF 1156, and/or structured data and application data for exposure for NEF 1152 (including PFD for application detection, application request information for multiple UEs 1102). The UDR may expose a Nudr service-based interface to allow UDM 1158, PCF 1156, and NEF 1152 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM may include a UDM-FE (UDM front end) that is responsible for handling credentials, location management, subscription management, and the like. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration/mobility management, and subscription management. UDM 1158 may expose a numm service based interface in addition to communicating with other NFs through reference points as shown.

The AF 1160 may provide application impact on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 1140 may enable edge computation by selecting operator/third party services that are geographically close to the point where the UE 1102 connects to the network. This may reduce delay and load on the network. To provide an edge calculation implementation, the 5GC 1140 may select the UPF 1148 near the UE 1102 and perform traffic steering from the UPF 1148 to the data network 1136 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by AF 1160. Thus, AF 1160 may affect UPF (re) selection and traffic routing. Based on operator deployment, the network operator may allow AF 1160 to interact directly with the relevant NFs when AF 1160 is considered a trusted entity. In addition, AF 1160 may expose interfaces based on Naf services.

The data network 1136 may represent various network operator services, internet access, or third party services that may be provided by one or more servers, including, for example, an application/content server 1138.

Fig. 12 schematically illustrates a wireless network 1200 in accordance with various embodiments. The wireless network 1200 may include a UE 1202 in wireless communication with AN 1204. The UE 1202 and the AN 1204 may be similar to and substantially interchangeable with like-named components described elsewhere herein.

The UE 1202 may be communicatively coupled with AN 1204 via a connection 1206. Connection 1206 is shown as an air interface to enable communicative coupling and may operate at millimeter wave or below 6GHz frequencies in accordance with a cellular communication protocol, such as an LTE protocol or a 5G NR protocol.

The UE 1202 may include a host platform 1208 coupled with a modem platform 1210. Host platform 1208 may include application processing circuitry 1212, which may be coupled with protocol processing circuitry 1214 of modem platform 1210. The application processing circuitry 1212 may run various applications for the UE 1202 to obtain/receive its application data. The application processing circuitry 1212 may also implement one or more layers of operations to send/receive application data to/from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

The protocol processing circuitry 1214 may implement one or more layers of operations to facilitate the transmission or reception of data over connection 1206. Layer operations implemented by the protocol processing circuit 1214 may include, for example, medium Access Control (MAC), radio Link Control (RLC), packet Data Convergence Protocol (PDCP), radio Resource Control (RRC), and non-access stratum (NAS) operations.

The modem platform 1210 may further include digital baseband circuitry 1216, which digital baseband circuitry 1216 may implement one or more layer operations "below" the layer operations performed by the protocol processing circuitry 1214 in the network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/demapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, wherein these functions may include one or more of space-time, space-frequency, or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

Modem platform 1210 may further include transmit circuitry 1218, receive circuitry 1220, RF circuitry 1222, and RF front end (RFFE) circuitry 1224, which may include or be connected to one or more antenna panels 1226. Briefly, the transmit circuit 1218 may include a digital-to-analog converter, a mixer, an Intermediate Frequency (IF) component, and so on; the receive circuit 1220 may include an analog-to-digital converter, a mixer, IF components, etc.; the RF circuitry 1222 may include low noise amplifiers, power tracking components, and so forth; the RFFE circuitry 1224 can include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beam-forming components (e.g., phased-array antenna components), and so forth. The selection and arrangement of components of transmit circuitry 1218, receive circuitry 1220, RF circuitry 1222, RFFE circuitry 1224, and antenna panel 1226 (collectively, "transmit/receive components") may be specific to details of the particular implementation, e.g., whether the communication is Time Division Multiplexed (TDM) or Frequency Division Multiplexed (FDM), at mmWave or below 6GHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in a plurality of parallel transmit/receive chains, and may be arranged in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 1214 may include one or more instances of control circuitry (not shown) to provide control functionality for the transmit/receive components.

UE reception may be established by and via antenna panel 1226, RFFE circuitry 1224, RF circuitry 1222, receive circuitry 1220, digital baseband circuitry 1216, and protocol processing circuitry 1214. In some embodiments, antenna panel 1226 may receive transmissions from AN 1204 by receiving beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 1226.

UE transmissions may be established via and through protocol processing circuitry 1214, digital baseband circuitry 1216, transmit circuitry 1218, RF circuitry 1222, RFFE circuitry 1224, and antenna panel 1226. In some embodiments, transmit components of UE 1202 may apply spatial filtering to the data to be transmitted to form transmit beams transmitted by the antenna elements of antenna panel 1226.

Similar to UE 1202, AN 1204 can include a host platform 1228 coupled with a modem platform 1230. The host platform 1228 may include application processing circuitry 1232 coupled to protocol processing circuitry 1234 of the modem platform 1230. The modem platform may also include digital baseband circuitry 1236, transmit circuitry 1238, receive circuitry 1240, RF circuitry 1242, RFFE circuitry 1244, and antenna panel 1246. The components of AN 1204 can be similar to, and substantially interchangeable with, the synonymous components of UE 1202. In addition to performing data transmission/reception as described above, the components of AN 1204 may also perform various logical functions including, for example, radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Fig. 13 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments. In particular, fig. 13 shows a schematic diagram of hardware resources 1300, hardware resources 1300 including one or more processors (or processor cores) 1310, one or more memory/storage devices 1320, and one or more communication resources 1330, where each of these processors, memory/storage devices, and communication resources may be communicatively coupled via a bus 1340 or other interface circuitry. For embodiments utilizing node virtualization (e.g., network Function Virtualization (NFV)), hypervisor 1302 may be executed to provide an execution environment for one or more network slices/subslices to utilize hardware resources 1300.

Processor 1310 may include, for example, processor 1312 and processor 1314. The processor 1310 may be, for example, a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP) such as a baseband processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Radio Frequency Integrated Circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

Memory/storage 1320 may include a main memory, a disk storage device, or any suitable combination thereof. The memory/storage 1320 may include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as Dynamic Random Access Memory (DRAM), static Random Access Memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, and the like.

Communication resources 1330 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripherals 1304 or one or more databases 1306 or other network elements via a network 1308. For example, communication resources 1330 can include wired communication components (e.g., for coupling via USB, ethernet, etc.), cellular communication components, near Field Communication (NFC) components, a wireless communication link, and/or the like,

(or

Low energy) assembly,

Components, and other communication components.

The instructions 1350 may include software, a program, an application, an applet, an app, or other executable code for causing at least any one of the processors 1310 to perform any one or more of the methods discussed herein. The instructions 1350 may reside, completely or partially, within at least one of the processor 1310 (e.g., in a cache of the processor), the memory/storage 1320, or any suitable combination thereof. Further, any portion of instructions 1350 may be transmitted to hardware resource 1300 from any combination of peripherals 1304 or database 1306. Thus, the memory of processor 1310, memory/storage 1320, peripherals 1304, and database 1306 are examples of computer-readable and machine-readable media.

The following paragraphs describe examples of various embodiments.

Example 1 includes an apparatus for use in a Session Management Function (SMF) node, comprising processor circuitry configured to cause the SMF node, upon detecting that a User Equipment (UE) begins using an edge application: sending a first charging data request to a charging function (CHF) node, wherein the first charging data request requests the CHF node to reserve an initial number of units for a service associated with the edge application; and receiving a first billing data response from the CHF node, wherein the first billing data response is to grant the initial number of units to the service associated with the edge application, wherein the first billing data request includes an initial quota requested for the rating group for the service associated with the edge application, and the initial number of units is reserved for the service associated with the edge application based on the account balance associated with the edge application and the initial quota requested for the rating group for the service associated with the edge application.

Example 2 includes the apparatus of example 1, wherein the processor circuitry is further configured to cause the SMF node, in use of the edge application by the UE, to: sending a second charging data request to the CHF node, wherein the second charging data request requests that the CHF node reserve a new number of units for a service associated with the edge application; and receiving a second billing data response from the CHF node, wherein the second billing data response is to grant the new number of units to the service associated with the edge application, wherein the second billing data request includes a new quota requested for the rating group for the service associated with the edge application, and the new number of units is reserved for the service associated with the edge application based on the account balance associated with the edge application and the new quota requested for the rating group for the service associated with the edge application.

Example 3 includes the apparatus of example 1, wherein the processor circuitry is further configured to cause the SMF node, in use of the edge application by the UE, to: sending a second charging data request to the CHF node, wherein the second charging data request is for reporting to the CHF node a current number of units that have been used for a service associated with the edge application and quality of service (QoS) information monitored for a service flow associated with the edge application; and receiving a second charging data response from the CHF node, wherein the second charging data response is to provide a notification to the SMF node as to whether more units should be requested for the service associated with the edge application or whether delivery of the service associated with the edge application should be terminated, wherein the second charging data request includes a current number of units of the rating group that has been used for the service associated with the edge application, determine whether more units should be requested for the service associated with the edge application or delivery of the service associated with the edge application should be terminated based on the account balance associated with the edge application and the current number of units of the rating group that has been used for the service associated with the edge application, and the account balance associated with the edge application is determined based on the current number of units of the rating group that has been used for the service associated with the edge application and the QoS information monitored for the service flow associated with the edge application.

Example 4 includes the apparatus of example 1, wherein the processor circuitry is further configured to cause the SMF node, upon detecting that the UE stops using the edge application, to: sending a third charging data request to the CHF node, wherein the third charging data request is for reporting to the CHF node charging data related to termination of a service associated with the edge application and a final number of units of a rating group that have been used for the service associated with the edge application; and receiving a third charging data response from the CHF node, wherein the third charging data response is used to provide notification to the SMF node that charging termination processing associated with the edge application has been performed, wherein the charging termination processing associated with the edge application is performed based on charging data related to service termination associated with the edge application and a final number of units of the rating group that have been used for the service associated with the edge application.

Example 5 includes an apparatus for use in a charging function (CHF) node, wherein the apparatus includes a processor circuit configured to cause the CHF node to: receiving a first charging data request from a Session Management Function (SMF) node, wherein the first charging data request requests that the CHF node reserve an initial number of units for a service associated with an edge application and includes an initial quota requested for a rating group for the service associated with the edge application; determining that the initial number of units can be reserved for the service associated with the edge application based on an account balance associated with the edge application and an initial quota requested for a rating group of the service associated with the edge application; and sending a first charging data response to the SMF node, wherein the first charging data response is to grant the initial number of units to a service associated with the edge application.

Example 6 includes the apparatus of example 5, wherein the processor circuit is further configured to cause the CHF node to: receiving a second billing data request from the SMF node, wherein the second billing data request requests that the CHF node reserve a new number of units for the service associated with the edge application and includes a new quota requested for a rating group of the service associated with the edge application; determining that the new number of units can be reserved for the service associated with the edge application based on an account balance associated with the edge application and a new quota requested for a rating group of the service associated with the edge application; and sending a second charging data response to the SMF node, wherein the second charging data response is to grant the new number of units to the service associated with the edge application.

Example 7 includes the apparatus of example 5, wherein the processor circuit is further configured to cause the CHF node to: receiving a second charging data request from the SMF node, wherein the second charging data request is for reporting to the CHF node a current number of units that have been used for a service associated with the edge application and quality of service (QoS) information monitored for a service flow associated with the edge application and includes a current number of units of a rating group that have been used for the service associated with the edge application; determining whether more units should be requested for a service associated with the edge application or whether a service delivery associated with the edge application should be terminated based on an account balance associated with the edge application and a current number of units of a rating group that has been used for the service associated with the edge application; and sending a second charging data response to the SMF node, wherein the second charging data response is to provide a notification to the SMF node as to whether more units should be requested for a service associated with the edge application or whether a service delivery associated with the edge application should be terminated, wherein an account balance associated with the edge application is determined based on QoS information monitored for a service flow associated with the edge application and a current number of units of a rating group that has been used for the service associated with the edge application.

Example 8 includes the apparatus of example 5, wherein the processor circuit is further configured to cause the CHF node to: receiving a third charging data request from the SMF node, wherein the third charging data request is for reporting charging data related to service termination associated with the edge application and a final number of units of a rating group that have been used for a service associated with the edge application; performing a charging termination process associated with the edge application based on charging data related to service termination associated with the edge application and a final number of units of a rating group that has been used for a service associated with the edge application; and sending a third charging data response to the SMF node, wherein the third charging data response is for providing notification to the SMF node that charging termination processing associated with the edge application has been performed.

Example 9 includes the apparatus of example 5, wherein the processor circuit is further configured to cause the CHF node to: aggregating usage reports associated with more than one edge application from the SMF nodes, wherein the usage reports associated with each edge application include a final number of units of a rating group that have been used for a service associated with that edge application and QoS information monitored for a service flow associated with that edge application; and sending, via a Charging Gateway Function (CGF) node, an aggregate usage report associated with the more than one edge application to an accounting domain.

Example 10 includes an apparatus for use in an edge-enabled server (EES), wherein the apparatus comprises a processor circuit configured to cause the EES, upon receiving a session creation or update request with quality of service (QoS) from an Edge Application Server (EAS) or upon detecting a user plane event for a session with QoS from a 5G core network (5 GC): sending a charging data request to a charging function (CHF) node; and receiving a charging data response from the CHF node, the charging data response for informing the EES of the result of the charging data request.

Example 11 includes the apparatus of example 10, wherein the processor circuit is further configured to cause the EES, upon receiving the session creation or update with QoS request from the EAS, to, after or before transmitting the charging data request to the CHF node: transmitting a session creation or update response with QoS to the EAS, the session creation or update response with QoS for notifying the EAS of a result of the session creation or update request with QoS.

Example 12 includes the apparatus of example 10, wherein the processor circuit is further configured to cause the EES, upon detecting a user plane event for the session with QoS from the 5GC, to, prior to sending the charging data request to the CHF node: sending a session event notification with QoS to the EAS.

Example 13 includes an apparatus for use in a charging function (CHF) node, wherein the apparatus includes a processor circuit configured to cause the CHF node to: receiving, from an edge-enabled server (EES), a charging data request associated with a session having a quality of service (QoS); creating a Charging Data Record (CDR) based on the charging data request; and sending a charging data response associated with the session with QoS to the EES.

Example 14 includes the apparatus of example 13, wherein the charging data request is associated with a session creation request with QoS, a session update request with QoS, or a session event notification with QoS.

Example 15 includes the apparatus of example 13, wherein the charging data request is for Instant Event Charging (IEC).

Example 16 includes the apparatus of example 13, wherein the charging data request is for post-hoc charging (PEC).

Example 17 includes a method in a Session Management Function (SMF) node, comprising, upon detecting that a User Equipment (UE) starts using an edge application: sending a first charging data request to a charging function (CHF) node, wherein the first charging data request requests that the CHF node reserve an initial number of units for a service associated with the edge application; and receiving a first billing data response from the CHF node, wherein the first billing data response is to grant the initial number of units to the service associated with the edge application, wherein the first billing data request includes an initial quota requested for a rating group for the service associated with the edge application, and the initial number of units is reserved for the service associated with the edge application based on an account balance associated with the edge application and the initial quota requested for the rating group for the service associated with the edge application.

Example 18 includes the method of example 17, further comprising, during use of the edge application by the UE: sending a second charging data request to the CHF node, wherein the second charging data request requests that the CHF node reserve a new number of units for a service associated with the edge application; and receiving a second billing data response from the CHF node, wherein the second billing data response is to grant the new number of units to the service associated with the edge application, wherein the second billing data request includes a new quota requested for the rating group for the service associated with the edge application, and the new number of units is reserved for the service associated with the edge application based on the account balance associated with the edge application and the new quota requested for the rating group for the service associated with the edge application.

Example 19 includes the method of example 17, further comprising, during use of the edge application by the UE: sending a second charging data request to the CHF node, wherein the second charging data request is for reporting to the CHF node a current number of units that have been used for a service associated with the edge application and quality of service (QoS) information monitored for a service flow associated with the edge application; and receiving a second charging data response from the CHF node, wherein the second charging data response is to provide a notification to the SMF node as to whether more units should be requested for the service associated with the edge application or whether the service delivery associated with the edge application should be terminated, wherein the second charging data request includes a current number of units of the rating group that has been used for the service associated with the edge application, determine whether more units should be requested for the service associated with the edge application or whether the service delivery associated with the edge application should be terminated based on an account balance associated with the edge application and a current number of units of the rating group that has been used for the service associated with the edge application, and the account balance associated with the edge application is determined based on the current number of units of the rating group that has been used for the service associated with the edge application and QoS information monitored for the service flow associated with the edge application.

Example 20 includes the method of example 17, further comprising, upon detecting that the UE stops using the edge application: sending a third charging data request to the CHF node, wherein the third charging data request is for reporting to the CHF node charging data related to termination of services associated with the edge application and a final number of units of the rating group that have been used for services associated with the edge application; and receiving a third charging data response from the CHF node, wherein the third charging data response is to provide a notification to the SMF node that charging termination processing associated with the edge application has been performed, wherein charging termination processing associated with the edge application is performed based on charging data related to service termination associated with the edge application and a final number of units of the rating group that have been used for the service associated with the edge application.

Example 21 includes a method in a charging function (CHF) node, comprising: receiving a first charging data request from a Session Management Function (SMF) node, wherein the first charging data request requests that the CHF node reserve an initial number of units for a service associated with an edge application and includes an initial quota requested for a rating group of services associated with the edge application; determining that the initial number of units can be reserved for the service associated with the edge application based on an account balance associated with the edge application and an initial quota requested for a rating group of the service associated with the edge application; and sending a first charging data response to the SMF node, wherein the first charging data response is for granting the initial number of units to a service associated with the edge application.

Example 22 includes the method of example 21, further comprising: receiving a second billing data request from the SMF node, wherein the second billing data request requests that the CHF node reserve a new number of units for the service associated with the edge application and includes a new quota requested for a rating group of the service associated with the edge application; determining that the new number of units can be reserved for the service associated with the edge application based on an account balance associated with the edge application and a new quota requested for a rating group of the service associated with the edge application; and sending a second charging data response to the SMF node, wherein the second charging data response is to grant the new number of units to the service associated with the edge application.

Example 23 includes the method of example 21, further comprising: receiving a second charging data request from the SMF node, wherein the second charging data request is for reporting to the CHF node a current number of units that have been used for a service associated with the edge application and quality of service (QoS) information monitored for a service flow associated with the edge application and includes a current number of units of a rating group that have been used for the service associated with the edge application; determining, based on an account balance associated with the edge application and a current number of units of a rating group that has been used for a service associated with the edge application, whether more units should be requested for the service associated with the edge application or whether a service delivery associated with the edge application should be terminated; and sending a second charging data response to the SMF node, wherein the second charging data response is to provide a notification to the SMF node as to whether more units should be requested for the service associated with the edge application or whether the delivery of the service associated with the edge application should be terminated, wherein an account balance associated with the edge application is determined based on the QoS information monitored for the service flow associated with the edge application and the current number of units in the rating group that have been used for the service associated with the edge application.

Example 24 includes the method of example 21, further comprising: receiving a third charging data request from the SMF node, wherein the third charging data request is for reporting charging data related to service termination associated with the edge application and a final number of units of a rating group that have been used for a service associated with the edge application; performing a billing termination process associated with the edge application based on billing data related to service termination associated with the edge application and a final number of units of a rating group that have been used for the service associated with the edge application; and sending a third charging data response to the SMF node, wherein the third charging data response is to provide notification to the SMF node that charging termination processing associated with the edge application has been performed.

Example 25 includes the method of example 21, further comprising: aggregating usage reports associated with more than one edge application from the SMF nodes, wherein the usage reports associated with each edge application include a final number of units of a rating group that have been used for a service associated with that edge application and QoS information monitored for a service flow associated with that edge application; and sending, via a Charging Gateway Function (CGF) node, an aggregated usage report associated with the more than one edge application to an accounting domain.

Example 26 includes a method for use in an edge-enabled server (EES), comprising, upon receiving a session creation or update request with quality of service (QoS) from an Edge Application Server (EAS) or upon detecting a user plane event for a session with QoS from a 5G core network (5 GC): sending a charging data request to a charging function (CHF) node; and receiving a charging data response from the CHF node, the charging data response notifying the EES of the result of the charging data request.

Example 27 includes the method of example 26, further including, in a case where the session creation or update with QoS request is received from the EAS, after or before sending the charging data request to the CHF node: transmitting a session creation or update with QoS response to the EAS for informing the EAS of a result of the session creation or update with QoS request.

Example 28 includes the method of example 26, further including, in an instance in which a user plane event is detected from the 5GC for the session with QoS, prior to sending the charging data request to the CHF node: sending a session event notification with QoS to the EAS.

Example 29 includes a method in a charging function (CHF) node, comprising: receiving, from an edge-enabled server (EES), a charging data request associated with a session having a quality of service (QoS); creating a Charging Data Record (CDR) based on the charging data request; and sending a charging data response associated with the session with QoS to the EES.

Example 30 includes the method of example 29, wherein the charging data request is associated with a session creation request with QoS, a session update request with QoS, or a session event notification with QoS.

Example 31 includes the method of example 29, wherein the charging data request is for Instant Event Charging (IEC).

Example 32 includes the method of example 29, wherein the charging data request is for post-hoc charging (PEC).

Example 33 includes a computer-readable storage medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed by processor circuitry of a Session Management Function (SMF) node, cause the SMF node to perform the method of any of examples 17-20.

Example 34 includes a computer-readable storage medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed by a processor circuit of a charging function (CHF) node, cause the CHF node to perform the method of any of examples 21-25.

Example 35 includes a computer-readable storage medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed by a processor circuit of an edge-enabled server (EES), cause the EES to perform the method of any of examples 26-28.

Example 36 includes a computer-readable storage medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed by a processor circuit of a charging function (CHF) node, cause the CHF node to perform the method of any of examples 29-32.

Example 37 includes an apparatus for use in a Session Management Function (SMF) node, comprising means for performing the method of any of examples 17-20.

Example 38 includes an apparatus for use in a charging function (CHF) node, comprising means for performing the method of any of examples 21-25.

Example 39 includes an apparatus for use in an edge-enabled server (EES), comprising means for performing the method of any of examples 26-28.

Example 40 includes an apparatus for use in a charging function (CHF) node, comprising means for performing the method of any of examples 29-32.

Although certain embodiments have been illustrated and described herein for purposes of description, a wide variety of alternate and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly intended that the embodiments described herein be limited only by the claims and the equivalents thereof.

Claims (24)

1. An apparatus for use in a Session Management Function (SMF) node, the apparatus comprising processor circuitry configured to cause the SMF node, upon detecting that a User Equipment (UE) starts using an edge application:

sending a first charging data request to a charging function (CHF) node, wherein the first charging data request requests that the CHF node reserve an initial number of units for a service associated with the edge application; and

receiving a first charging data response from the CHF node, wherein the first charging data response is used to grant the initial number of units to a service associated with the edge application, wherein

The first charging data request includes an initial quota requested for a rating group of a service associated with the edge application, and

the initial number of units is reserved for a service associated with the edge application based on an account balance associated with the edge application and an initial quota requested for a rating group of the service associated with the edge application.

2. The apparatus of claim 1, wherein the processor circuit is further configured to cause the SMF node, in use of the edge application by the UE, to:

sending a second charging data request to the CHF node, wherein the second charging data request requests that the CHF node reserve a new number of units for a service associated with the edge application; and

receiving a second charging data response from the CHF node, wherein the second charging data response is used to grant the new number of units to a service associated with the edge application, wherein

The second billing data request includes a new quota requested for a rating group of a service associated with the edge application, and

the new number of units is reserved for the service associated with the edge application based on an account balance associated with the edge application and a new quota requested for a rating group for the service associated with the edge application.

3. The apparatus of claim 1, wherein the processor circuitry is further configured to cause the SMF node, in use of the edge application by the UE, to:

sending a second charging data request to the CHF node, wherein the second charging data request is for reporting to the CHF node a current number of units that have been used for a service associated with the edge application and quality of service (QoS) information monitored for a service flow associated with the edge application; and

receiving a second charging data response from the CHF node, wherein the second charging data response is used to provide a notification to the SMF node whether more units should be requested for the service associated with the edge application or whether the service delivery associated with the edge application should be terminated, wherein

The second charging data request comprises a current number of unit sub-groups of rating groups already used for services associated with the edge application,

based on an account balance associated with the edge application and a current number of units of a rating group that has been used for a service associated with the edge application, determining whether more units should be requested for the service associated with the edge application or whether a service delivery associated with the edge application should be terminated, and

an account balance associated with the edge application is determined based on a current number of units of a rating group that has been used for a service associated with the edge application and QoS information monitored for a service flow associated with the edge application.

4. The apparatus of claim 1, wherein the processor circuit is further configured to cause the SMF node, upon detecting that the UE ceases to use the edge application:

sending a third charging data request to the CHF node, wherein the third charging data request is for reporting to the CHF node charging data related to termination of services associated with the edge application and a final number of units of the rating group that have been used for services associated with the edge application; and

receiving a third charging data response from the CHF node, wherein the third charging data response is used to provide notification to the SMF node that charging termination processing associated with the edge application has been performed, wherein

The charging termination process associated with the edge application is performed based on charging data related to service termination associated with the edge application and a final number of unit subsets of a rating group that have been used for a service associated with the edge application.

5. An apparatus for use in a charging function (CHF) node, wherein the apparatus comprises a processor circuit configured to cause the CHF node to:

receiving a first charging data request from a Session Management Function (SMF) node, wherein the first charging data request requests that the CHF node reserve an initial number of units for a service associated with an edge application and includes an initial quota requested for a rating group for the service associated with the edge application;

determining that the initial number of units can be reserved for the service associated with the edge application based on an account balance associated with the edge application and an initial quota requested for a rating group of the service associated with the edge application; and

sending a first charging data response to the SMF node, wherein the first charging data response is used for granting the initial number of units to the service associated with the edge application.

6. The apparatus of claim 5, wherein the processor circuit is further configured to cause the CHF node to:

receiving a second billing data request from the SMF node, wherein the second billing data request requests that the CHF node reserve a new number of units for a service associated with the edge application and include a new quota requested for a rating group of the service associated with the edge application;

determining that the new number of units can be reserved for the service associated with the edge application based on an account balance associated with the edge application and a new quota requested for a rating group of the service associated with the edge application; and

sending a second billing data response to the SMF node, wherein the second billing data response is for granting the new number of units to the service associated with the edge application.

7. The apparatus of claim 5, wherein the processor circuit is further configured to cause the CHF node to:

receiving a second charging data request from the SMF node, wherein the second charging data request is for reporting to the CHF node a current number of units that have been used for a service associated with the edge application and quality of service (QoS) information monitored for a service flow associated with the edge application, and includes a current number of units of a rating group that have been used for the service associated with the edge application;

determining whether more units should be requested for a service associated with the edge application or whether a service delivery associated with the edge application should be terminated based on an account balance associated with the edge application and a current number of units of a rating group that has been used for the service associated with the edge application; and

sending a second charging data response to the SMF node, wherein the second charging data response is used for providing the SMF node with a notice whether more units should be requested for the service associated with the edge application or whether the service delivery associated with the edge application should be terminated, wherein the notice is that the service delivery is not required for the service associated with the edge application

An account balance associated with the edge application is determined based on QoS information monitored for a service flow associated with the edge application and a current number of units of a rating group that have been used for a service associated with the edge application.

8. The apparatus of claim 5, wherein the processor circuit is further configured to cause the CHF node to:

receiving a third charging data request from the SMF node, wherein the third charging data request is for reporting charging data related to service termination associated with the edge application and a final number of units of a rating group that have been used for a service associated with the edge application;

performing a billing termination process associated with the edge application based on billing data related to service termination associated with the edge application and a final number of units of a rating group that have been used for the service associated with the edge application; and

sending a third charging data response to the SMF node, wherein the third charging data response is used for providing the SMF node with a notice that the charging termination processing associated with the edge application is executed.

9. The apparatus of claim 5, wherein the processor circuit is further configured to cause the CHF node to:

aggregating usage reports associated with more than one edge application from the SMF nodes, wherein the usage reports associated with each edge application include a final number of units of a rating group that have been used for a service associated with that edge application and QoS information monitored for a service flow associated with that edge application; and

sending, via a Charging Gateway Function (CGF) node, an aggregate usage report associated with the more than one edge application to an accounting domain.

10. An apparatus for use in an edge-enabled server (EES), wherein the apparatus comprises a processor circuit configured to cause the EES, upon receiving a session creation or update request with quality of service (QoS) from an Edge Application Server (EAS) or upon detecting a user plane event for a session with QoS from a 5G core network (5 GC):

sending a charging data request to a charging function (CHF) node; and

receiving a charging data response from the CHF node, the charging data response for informing the EES of the result of the charging data request.

11. The apparatus of claim 10, wherein the processor circuit is further configured to cause the EES, upon receiving the session creation or update with QoS request from the EAS, to, after or before transmitting the accounting data request to the CHF node:

transmitting a session creation or update response with QoS to the EAS, the session creation or update response with QoS for notifying the EAS of a result of the session creation or update request with QoS.

12. The apparatus of claim 10, wherein the processor circuit is further configured to cause the EES, upon detecting a user plane event for the session with QoS from the 5GC, to, prior to sending the charging data request to the CHF node:

sending a session event notification with QoS to the EAS.

13. An apparatus for use in a charging function (CHF) node, wherein the apparatus comprises a processor circuit configured to cause the CHF node to:

receiving a charging data request associated with a session having a quality of service (QoS) from an edge-enabled server (EES);

creating a Charging Data Record (CDR) based on the charging data request; and

sending a charging data response associated with the session with QoS to the EES.

14. The apparatus of claim 13, wherein the charging data request is associated with a session creation request with QoS, a session update request with QoS, or a session event notification with QoS.

15. The apparatus of claim 13, wherein the charging data request is for Immediate Event Charging (IEC).

16. The apparatus of claim 13, wherein the charging data request is for post-hoc charging (PEC).

17. A computer-readable storage medium having stored thereon computer-executable instructions, wherein the computer-executable instructions, when executed by processor circuitry of a Session Management Function (SMF) node, cause the SMF node, upon detecting that a User Equipment (UE) begins using an edge application:

sending a first charging data request to a charging function (CHF) node, wherein the first charging data request requests the CHF node to reserve an initial number of units for a service associated with the edge application; and

receiving a first charging data response from the CHF node, wherein the first charging data response is used to grant the initial number of units to a service associated with the edge application, wherein

The first billing data request includes an initial quota requested for a rating group of a service associated with the edge application, and

the initial number of units is reserved for a service associated with the edge application based on an account balance associated with the edge application and an initial quota requested for a rating group of the service associated with the edge application.

18. The computer-readable storage media of claim 17, wherein the computer-executable instructions, when executed by the processor circuitry of the SMF node, further cause the SMF node, in using the edge application by the UE, to:

sending a second charging data request to the CHF node, wherein the second charging data request requests that the CHF node reserve a new number of units for a service associated with the edge application; and

receiving a second charging data response from the CHF node, wherein the second charging data response is used to grant the new number of units to the service associated with the edge application, wherein

The second billing data request includes a new quota requested for a rating group of a service associated with the edge application, and

the new number of units is reserved for the service associated with the edge application based on an account balance associated with the edge application and a new quota requested for a rating group for the service associated with the edge application.

19. A computer-readable storage medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed by a processor circuit of a charging function (CHF) node, cause the CHF node to:

receiving a first charging data request from a Session Management Function (SMF) node, wherein the first charging data request requests that the CHF node reserve an initial number of units for a service associated with an edge application and includes an initial quota requested for a rating group for the service associated with the edge application;

determining that the initial number of units can be reserved for the service associated with the edge application based on an account balance associated with the edge application and an initial quota requested for a rating group of the service associated with the edge application; and

sending a first charging data response to the SMF node, wherein the first charging data response is used to grant the initial number of units to a service associated with the edge application.

20. The computer-readable storage medium according to claim 19, wherein the computer-executable instructions, when executed by the processor circuit of the CHF node, further cause the CHF node to:

receiving a second billing data request from the SMF node, wherein the second billing data request requests that the CHF node reserve a new number of units for a service associated with the edge application and include a new quota requested for a rating group of the service associated with the edge application;

determining that the new number of units can be reserved for the service associated with the edge application based on an account balance associated with the edge application and a new quota requested for a rating group of the service associated with the edge application; and

sending a second billing data response to the SMF node, wherein the second billing data response is for granting the new number of units to the service associated with the edge application.

21. A computer readable storage medium having stored thereon computer executable instructions, wherein the computer executable instructions, when executed by a processor circuit of an edge-enabled server (EES), cause the EES, upon receiving a session creation or update request with quality of service (QoS) from an Edge Application Server (EAS) or detecting a user plane event for a session with QoS from a 5G core network (5 GC):

sending a charging data request to a charging function (CHF) node; and

receiving a charging data response from the CHF node, the charging data response for informing the EES of a result of the charging data request.

22. The computer-readable storage media of claim 21, wherein the computer-executable instructions, when executed by the processor circuit of the EES, further cause the EES, upon receiving the session creation or update with QoS request from the EAS, to, after or before sending the charging data request to the CHF node:

transmitting a session creation or update response with QoS to the EAS, the session creation or update response with QoS for informing the EAS of a result of the session creation or update request with QoS.

23. A computer-readable storage medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed by a processor circuit of a charging function (CHF) node, cause the CHF node to:

receiving a charging data request associated with a session having a quality of service (QoS) from an edge-enabled server (EES);

creating a Charging Data Record (CDR) based on the charging data request; and

sending a charging data response associated with the session with QoS to the EES.

24. The computer-readable storage medium of claim 23, wherein the charging data request is associated with a session creation request with QoS, a session update request with QoS, or a session event notification with QoS.

Images