Patent Application
20250142299
Methods and apparatus provide for granting and using group quotas, rather than individual quotas, wherein a granted group quota may be shared or divided by an edge Charging Function (eCHF) among individual user terminals among a group of affiliated user terminals.
The Third Generation Partnership Project (3GPP) Technical Specification (TS) 32.290 V17.4.0 specifies a service-based architecture in which respective network functions (NFs) request charging from one or more Charging Functions (CHFs). A Converged Charging System (CCS) in this framework includes four main parts, with the CHF being one part. The CHF terminates the interface towards the requesting NF and interacts with the other parts of the CCS, which include: an Account Balance Management Function (ABMF) that holds subscribers' account balances and any reservations against those balances; a Rating Function (RF) that determines the value of the network resource usage; and a Charging Data Function (CDF) that is responsible for generating charging data records.
As a simple example of “online” charging, consider a user terminal associated with a subscriber account initiating use of a communication service in a Fifth Generation (5G) telecommunication network-see 3GPP TS 38.300 V16.8.0, TS 38.401 V16.8.0, and TS 38.410 V16.4.0 for 5G architectural details. A Charging Trigger Function (CTF) in a Session Management Function (SMF) or other NF sends a charging request to a CHF, requesting authorization for consumption of the communication service by the user terminal. The CTF may request a number of “service units,” with each unit representing a quantum of service consumption, e.g., minutes, megabytes, etc.
The CHF sends a charging request towards an ABMF, which cooperates with a RF to determine the value of the requested number of service units. If the balance(s) or credit(s) in the associated subscriber account(s) is sufficient to cover the value, a quota is granted, with the size of the quota corresponding to the rated number of service units, and a corresponding charge reservation is recorded against the subscriber account(s). For policy or other reasons, the number of rated service units comprised in the granted quota may not be the same as the requested number. In any case, the CHF receives signaling indicating the granted quota and sends corresponding signaling towards the CTF that originated the request. For continuing services, like data connections, voice communications, etc., online charging includes initial and final charging requests, with any number of intermediate charging requests to cover ongoing consumption between initiation and termination of the service consumption.
Numerous challenges arise with respect to reducing or minimizing latencies associated with authorizing charging requests in cases where the communication services are “edge services”, such as computing services provided to user terminals at an “edge location” of the network. As used herein, “edge location” refers to the point of connection of a user terminal, and an “edge service” refers to a service provided at or near the point of connection of a user terminal. For example, a user terminal connects to the network over a radio link with an access node of the network, and the access node connects directly or indirectly to a local server that provides computing services or data processing services or one or more other types of services, such that the user traffic associated with the edge services is routed and processed locally, rather than traversing into and through the overall network.
In other words, edge services provided by the Mobile Network Operator (MNO), or third parties are hosted at or close to the point-edge location-where user terminals attach to the telecommunication network. For example, certain user traffic may be broken out at a base station of the telecommunication network using “Local Breakout” (LBO) techniques and processed at the network edge where, or nearby to where, the base station is located, rather than traversing through the telecommunication network to reach one or more application service provider (ASP) servers for processing. “Nearby” in a network sense refers, for example, to the number of hops or intermediate routing points that are in the traffic flow going from/to the involved access node and the entity/entities that provide the edge service(s).
See clause 4.2 of 3GGP TS 23.501 V17.3.0 for reference architectures supporting edge computing in the 5G System (5GS) context. As a particular example, in the 5GS context, a radio access node (AN) provides wireless connectivity to user terminals that are within the signal coverage of the AN, with the AN coupling to a User Plane Function (UPF) that provides access to a local Data Network (DN) offering computing or other edge services to authorized user terminals that are connected to the 5GS via the AN. Here, the “edge location” refers to the AN as the point of connectivity into the 5GS. Also, see 3GPP TS 23.548 V17.1.0 for 5GS enhancements for edge computing, clause 4 in 3GPP TR 23.748 V17.0.0, regarding example edge support in the 5G Core (5GC), and 3GPP Technical Report (TR) 28.815 V17.0.0, regarding charging aspects of edge computing that are under study by the 3GPP.
Methods and apparatus provide for granting and using group quotas, rather than individual quotas, wherein a granted group quota may be shared or divided by an edge Charging Function (eCHF) among individual user terminals among a group of affiliated user terminals. For example, an eCHF sends a charging request for consumption of an edge service by one user terminal among a group of affiliated user terminals. A charging node responds to the request by granting a group quota shareable or dividable among the affiliated user terminals, rather than an individual quota. Correspondingly, the eCHF makes local grant decisions, such as by granting respective fractions of the granted group quota to two or more ones of the affiliated user terminals operating at the involved edge location.
One embodiment comprises a method of charging control for a communication network, where the method is performed by a node operative as an edge charging function (eCHF). The method includes the eCHF receiving a charging request from a Charging Trigger Function (CTF), requesting a quota for authorizing consumption by a first user terminal of an edge service provided by the communication network, the first user terminal being a member of a defined group of affiliated user terminals. The method further includes the eCHF sending a corresponding charging request towards a charging node associated with the communication network, and receiving a charging response from the charging node, the charging response indicating a granted group quota usable for authorizing consumption of the edge service by members of the defined group. Still further, the method includes the eCHF deciding, as a locally-granted quota, what fraction of the granted group quota to grant to the first user terminal, and sending a charging response to the CTF, indicating the locally-granted quota.
In another example embodiment, a node is operative as an eCHF for a communication network, where the node includes communication interface circuitry configured to send and receive messages, including charging requests and charging responses, and further includes processing circuitry that is operatively associated with the communication interface circuitry. The processing circuitry is configured to receive a charging request from a CTF, requesting a quota for authorizing consumption by a first user terminal of an edge service provided by the communication network, the first user terminal being a member of a defined group of affiliated user terminals. Further, the processing circuitry is configured to: send a corresponding charging request towards a charging node associated with the communication network; receive a charging response from the charging node, the charging response indicating a granted group quota usable for authorizing consumption of the edge service by members of the defined group; decide, as a locally-granted quota, what fraction of the granted group quota to grant to the first user terminal; and send a charging response to the CTF, indicating the locally-granted quota.
Another example embodiment comprises a method of charging control for a communication network, where the method is performed by a charging node associated with the communication network. The method includes the charging node: receiving a charging request originating from an eCHF, requesting a quota for authorizing consumption by a first user terminal of an edge service provided by the communication network, the first user terminal being a member of a defined group of affiliated user terminals; granting a group quota usable for authorizing consumption of the edge service by members of the defined group; and sending a charging response for the eCHF, indicating the granted group quota.
A further, related embodiment comprises a charging node configured for charging control for a communication network. The charging node includes communication interface circuitry configured to send and receive messages, including requests and responses related to charging, and processing circuitry that is operatively associated with the communication interface circuitry. The processing circuitry is configured to: receive a request originating from an eCHF, requesting a quota for authorizing consumption by a first user terminal of an edge service provided by the communication network, the first user terminal being a member of a defined group of affiliated user terminals; grant a group quota usable for authorizing consumption of the edge service by members of the defined group; and send a response intended for the eCHF, indicating the granted group quota.
Of course, the present invention is not limited to the above features and advantages.
Indeed, those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.
A Core Network (CN) 16 comprising various CN nodes 18 is coupled with the RAN 12 and provides access control, mobility management, and traffic routing, for user terminals 20 that connect to the network 10 via radio links with respective ones of the access nodes 14. The CN nodes 18 provide, for example, access control, authentication, mobility management, and data routing functions to support respective user terminals 20 that connect to the network 10 for consumption—use—of one or more types of services provided by the network 10.
Here, “provided” means that the network 10 offers the service(s) directly, or gives access to such services, e.g., by acting as an “access network” that communicatively couples respective ones of the user terminals 20 with one or more Application Servers (ASs) 22 that are external to the network 10 and accessible via one or more networks 24 that are external to the network 10. For example, the network 10 provides IP-based routing of user traffic flowing between given ones of the user terminals 20 and given ASs 22 that are accessible via the Internet, where the Internet is an example external network to which the CN 16 couples.
Example services include voice services, such as Voice-over-IP (VOIP) services, push-to-talk services, data services, mobile broadband (MBB) services, such as for media streaming, video conferencing, social networking, etc. Additional service examples include Machine-Type-Communication (MTC) services in Machine-to-Machine (M2M) contexts, Internet-of-Things (IoT) services, vehicle-to-vehicle (V2V) and vehicle-to-everything (V2X) services, computing or data processing services, data storage services, etc.
In this regard, the various ones of the user terminals 20 may be of different types and have different capabilities and serve different purposes. Thus, different ones of the user terminals 20 may use different ones among the various services provided by the network 10. “Edge services” are of particular interest herein, wherein the term “edge service” does not necessarily connote a specific type of service and instead connotes where or how that service is provided by the network 10.
The edge networks 26 may be referred to as “data networks” (DNs). These DNs may also be reachable via the external network(s) 24 and the ASs 28 may be the same as the ASs 22 or affiliated with the ASs 22, with the difference being that user traffic handled in an edge network 26—i.e., at an edge location associated with a respective AN 14—does not have to traverse through the network 10 in any end-to-end sense. See the “END-TO-END USER TRAFFIC” depiction in the diagram. Instead, using Local Breakout (LBO) or other mechanisms, user traffic handled at the edge location traverses a shorter path, e.g., from the AN 14 to UPF node or other traffic-handling node in the CN 16, which is nearby the access node 14. See the “LOCAL USER TRAFFIC” depiction in the diagram.
In an example scenario, a user terminal 20 uses the network 10 to contact an AS 22 reachable via the external network(s) 24, with the AS 22 or some related node communicating with the network 10 to initiate an edge service for the user terminal 20, or to transition a service being used by the terminal 20 over to edge processing at the edge location of the user terminal 20. For example, a company or other third party uses the network 10 to provide computing or data-processing services to user terminals 20 that belong to or are otherwise authorized by the company.
Charging for the consumption of edge services raises numerous challenges. For example, there may be significant network distance between the edge location and centralized charging-system entities. That distance implies latency and meaningful signaling overhead in the network in association with requests for charging originating from the edge location and flowing to the central charging entity/entities and corresponding responses being returned to the edge location. See the charging system 30 and associated billing system 32 depicted in
Methods and apparatuses disclosed herein address a number of charging issues related to edge services and the involved techniques offer one or more advantages, such as reduced latencies in obtaining authorizations for edge-service consumption and reductions in the frequency or need for charging-related signaling to be exchanged between charging entities at an edge location and charging entities at a centralized location.
Assumptions specific to
An “edge” Charging Function (eCHF) 44 associated with the involved edge location receives incoming charging requests from the CTF 42 and includes a CTF 46 that sends corresponding charging requests towards another charging node, e.g., another CHF 48 that is centralized or associated with a centralized Account Balance Management Function (ABMF) 50, a Rating Function (RF) 52, a Charging Data Function (CDF) 56, and a Charging Gateway Function (CGF) 58. The eCHF 44 may be associated with one or more further CDFs 60. The ABMF, RF, CDF and CHF nodes or entities may be understood as constituting or belonging to the charging system 30 depicted in
The CHF 48 receives charging requests incoming from the eCHF 44 and passes them to the ABMF 50 for processing, with the ABMF 50 and the RF 52 cooperating to rate service units to be granted in response to the incoming charging requests and make corresponding value reservations against the involved subscriber account(s). Advantageously, as part of the charging requests sent by it towards the CHF 48, or in other signaling, the eCHF 44 identifies itself as an edge charging node or otherwise indicates that it is operative to make local grant decisions with respect to the consumption of edge services at the edge location with which the eCHF 44 is associated. As a further advantage, the ABMF 50 or another node associated therewith is operative to grant group quotas rather than individual quotas, at least under certain circumstances, e.g., when certain conditions are fulfilled.
Unlike an individual quota, which contains rated service units authorizing service consumption by a specific user terminal 20, a group quota contains rated service units that may be shared by or divided among multiple user terminals 20. As a particular example, there exists a defined group of affiliated user terminals 20, e.g., a group of user terminals 20 that are all associated with a particular company or other entity that uses the network 10 to provide an edge service for consumption by such user terminals 20. By granting a group quota in response to a charging request incoming from the eCHF 44, the ABMF 50 or other node provides the eCHF 44 with the opportunity to grant multiple local quotas at the edge location, using fractions of the group quota. In turn, that reduces charging authorization latency by eliminating or deferring the need for round-trip signaling between the eCHF 44 and the centralized charging entities, e.g., the CHF 48 and ABMF 50, and it reduces the number of overall signaling transactions between the eCHF 44 and the CHF 48/ABMF 50.
The communication interface circuitry 60 comprises one or more transmitter circuits and one or more receiver circuits that are configured for the transmission and reception of signaling over one or more types of physical interfaces, e.g., wired or wireless interfaces. In an example embodiment, the communication interface circuitry 60 comprises one or more ethernet interfaces or other data-network interfaces that are operative for sending and receiving charging messages.
The processing circuitry 62 comprises fixed circuitry or programmatically configured circuitry or a mix of fixed and programmatically configured circuitry. In at least one embodiment and with reference to
As such, the storage 64 in one or more embodiments comprises one or more types of computer readable media, such as volatile memory for program execution and nonvolatile memory for longer term program storage. Example computer readable media include any one or more of SRAM, DRAM, FLASH memory, EEPROM, or Solid State Disk (SSD). The storage 64 provides non-transitory storage of computer program instructions for execution by the one or more microprocessor(s) 72, where non-transitory does not necessarily mean permanent or unchanging but rather storage having at least some persistence.
With the above example details in mind, in one embodiment a node is operative as an eCHF 44 for a communication network 10, with the node comprising communication interface circuitry 60 configured to send and receive messages, including requests and responses for charging, and further comprising processing circuitry 62 operatively associated with the communication interface circuitry 60.
The processing circuitry 62 is configured to: (a) receive a charging request from a CTF, requesting a quota for authorizing consumption by a first user terminal 20 of an edge service provided by the communication network 10, where the first user terminal 20 is a member of a defined group of affiliated user terminals 20; (b) send a corresponding charging request towards a charging node associated with the communication network 10; (c) receive a charging response from the charging node, the charging response indicating a granted group quota usable for authorizing consumption of the edge service by members of the defined group; (d) decide, as a locally-granted quota, what fraction of the granted group quota to grant to the first user terminal 20; and (e) send a charging response to the CTF, indicating the locally-granted quota. For example, the CTF in question is the CTF 42 shown in
The processing circuitry 62 in one or more embodiments is configured to decide what fraction of the granted group quota to grant to the first user terminal 20 by deciding a size of the locally-granted quota in dependence on the edge service. Here, the size of the locally-granted quota is less than or equal to a size of the granted group quota. That is, the granted fraction constituting the locally-granted quota may be up to one-hundred percent of the granted group quota. Note that the granted group quota may only be applicable for a certain service, and the group may also only be defined for a specific edge service.
Saying that the size of the locally-granted quota depends on the edge service means that the eCHF 44 and one or more embodiments is configured to decide how much of—i.e., the fraction of—the granted group quota to allocate to the first user terminal 20 based on the type or nature of the edge service involved. As one example, responsive to determining that the edge service is a high data rate service or is otherwise of a nature such that the granted group quota is likely to be consumed quickly, the eCHF 44 makes the size of the locally-granted quota larger. Conversely, other types of edge services are known to have characteristically slow quota consumption—e.g., known based on information stored as configuration data 68 within the eCHF 44. For such edge services, the eCHF 44 makes the size of the locally-granted quota smaller. Here, “larger” and “smaller” are relative terms referenced to a default or nominal size.
The processing circuitry 62 in one or more embodiments is configured to decide what fraction of the granted group quota to grant to the first user terminal 20 by deciding a size of the locally-granted quota in dependence on whether one or more other ones of the affiliated user terminals 20 are connected to the communication network at a same edge location as the first user terminal 20. As before, the size of the locally-granted quota is less than or equal to a size of the granted group quota.
In an example of the decision logic described immediately above, the eCHF 44 allocates less than the total size of the granted group quota to the first user terminal 20, responsive to knowing or detecting that one or more of the other affiliated user terminals 20 are connected at the same edge location as the first user terminal 20. The eCHF 44 may determine that the other affiliated user terminals 20 are connected at the same edge location by detecting that they are accessing the network 10 through the same AN 14 used by the first user terminal 20 or are otherwise connecting to the network 10 through an AN 14 that is affiliated with the same edge-location designation as is associated with the AN 14 used by the first user terminal 20.
For example, based on detecting that one or more other ones of the affiliated user terminals 20 are connected at the same edge location, the eCHF 44 decides to grant less than the total size of the granted group quota to the first user terminal 20, in view of the likelihood that one or more other ones of the affiliated user terminals 20 will request use of the same edge service in the near future. The fraction of the granted group quota that is granted to the first user terminal 20 as the locally-granted quota may depend on the number of affiliated user terminals 20 that are active or otherwise connected at the edge location or may depend on the total number of affiliated user terminals in the group.
The processing circuitry in one or more embodiments is configured to decide what fraction of the granted group quota to grant to the first user terminal 20 by deciding a size of the locally-granted quota in dependence on whether one or more temporally-proximate charging requests have been received at the eCHF 44 for any other ones of the affiliated user terminals, for the edge service. As before, the size of the granted quota being less than or equal to a size of the granted group quota.
“Temporally-proximate” charging requests are charging requests received within a defined interval prior to the charging request received for the first user terminal 20. The defined interval may be a configured value, such as 30 seconds, one minute, two minutes, etc. the size of the interval may be configured according to network-operator policy, and the interval may be dependent upon the type of edge service involved. These details recognize that in some respects there is an advantage to giving the first user terminal 20 a larger quota, e.g. to avoid triggering a subsequent charging request for the first user terminal 20 unnecessarily soon, while on the other hand there is an advantage in preserving some of the granted group quota for use in making a low-latency local grant to another one of the affiliated user terminals 20 or even to the first user terminal 20, assuming it is consumption of the edge service continues.
The processing circuitry 62 of the eCHF 44 in one or more embodiments is configured to consider a multiplicity of factors or parameters when deciding what fraction of a granted group quota to allocate to a user terminal 20 as a locally-granted quota. For example, the processing circuitry 62 is configured to make a joint or weighted evaluation of any two or more of the following factors: the type of edge service, the number of affiliated user terminals 20 in the group, the number of affiliated user terminals that are concurrently connected at the same edge location, historical data indicating the frequency or the likelihood of receiving multiple charging requests for the edge service for respective ones of the affiliated user terminals 20, e.g., data indicating the number of temporally-proximate charging requests received from any of the affiliated user terminals for the edge service while operating at the involved edge location.
Further, in at least one embodiment, the processing circuitry 62 of the eCHF 44 is configured to learn or otherwise adapt its decision strategy for determining what fraction of a granted group quota to allocate to any given one of the affiliated user terminals 20 at any given time. For example, the eCHF 44 adjusts the nominal fractional allocation that it uses as a baseline, based on monitoring how quickly fractional quotas are consumed by respective ones of the affiliated user terminals 20 and monitoring how quickly the overall granted group quota is consumed.
Consider an example case where the locally-granted quota given to a first user terminal 20 leaves a remaining portion of the granted group quota as a remaining group quota. That is, the size of the locally-granted quota is smaller than the size of the granted group quota, where the “size” of a quota refers to the number rated service units in the quota. Referring to the remaining portion or fraction of the granted group quota as the “remaining group quota”, the processing circuitry 62 in one or more embodiments is configured to decide, as a further locally-granted quota, what fraction of the remaining group quota to grant to another one of the affiliated user terminals 20 in response to the eCHF 44 receiving a charging request for the other one of the affiliated user terminals 20, requesting a quota for authorizing consumption by the other one of the affiliated user terminals 20 of the edge service.
With respect to the eCHF 44 receiving a further charging request from the same or another CTF 42, the further charging request requesting a quota for authorizing consumption of the edge service by a second user terminal 20 among the affiliated user terminals 20, the processing circuitry 62 in one or more embodiments is configured to decide a further locally-granted quota for the second user terminal 20 from a then-remaining fraction of the granted group quota, and send a further charging response to the same or other CTF 42, indicating the further locally-granted quota.
With respect to the eCHF 44 receiving a further charging request from the same or another CTF 42, the further charging request requesting a quota for authorizing consumption of the edge service by a second user terminal 20 among the affiliated user terminals 20, the processing circuitry 62 in one or more embodiments is configured to communicate with the charging node, e.g., the CHF 48, to obtain a further quota from the charging node, to authorize consumption of the edge service by the second user terminal 20, in response to determining that the granted group quota has been exhausted or a then-remaining amount of the granted group quota is not sufficient for responding to the further charging request.
The charging request sent from the eCHF 44 towards the charging node, e.g., towards the CHF 48 shown in
For example, the eCHF 44 receives a charging request from the CTF 42, requesting consumption of an edge service by user terminal 20 and at this point in the charging process the eCHF 44 does not know that the user terminal 20 belongs to a group of affiliated user terminals 20 for which the use of group quotas may be advantageous. However, sending an edge charging request, triggers the charging system 30, e.g., the ABMF 50, in particular, to determine whether the involved user terminal 20 belongs to a group. In one or more embodiments, the response coming back to the eCHF 44, or signaling associated therewith, indicates the group affiliation of the user terminal 20.
For example, the eCHF 44 receives a group identifier or receives identifiers of the user terminals 20 constituting the group, and it understands from such information that the user terminal 20 belongs to a group of affiliated user terminals 20 and that the returned quota is a group quota that may be shared among or divided among two or more ones of the affiliated user terminals 20. In this sense, it should be understood that eCHF 44 is also operative to handle responses that involve individual, or per-terminal granted quotas, i.e., it can receive and recognize responses that contain a quota intended only for the user terminal 20 for which the eCHF 44 sent a charging request.
The processing circuitry 62 of the eCHF 44 in one or more embodiments is configured to evaluate group affiliations of other user terminals 20 connected to the communication network 10 at an edge location of the eCHF 44, to determine the presence of other members of the defined group in which the first user terminal 20 has membership. That is, for any given user terminal 20 for which the eCHF 44 receives a charging request, the eCHF 44 in one or more embodiments is configured to determine whether the user terminal 20 belongs to a group of affiliated user terminals 20 and correspondingly decide whether to grant a fraction of any granted group quota or remaining group quota that is currently available at the eCHF 44.
In more detail, assume that the eCHF 44 receives a charging request sent to the eCHF on behalf of a first user terminal 20, and assume that the charging response returned to eCHF 44 for that charging request indicates that the first user terminal 20 belongs to a group, such that the granted quota returned in the charging response is treated by the eCHF 44 as a granted group quota. Further, assume that the charging response lists or otherwise identifies the user terminals 20 that belong to a group.
As such, when the eCHF 44 receives a subsequent charging request sent for a second user terminal 20 connecting to the network 10 through the same edge location, the eCHF 44 evaluates the identity of the second user terminal 20 involved in that subsequent charging request against the group membership information in its possession, to determine whether the second user terminal 20 belongs a group for which there may be a granted group quota or remaining group quota available at the eCHF 44. In this context, in one or more embodiments, the processing circuitry 62 is configured to decide how much of a granted group quota—i.e., what fraction—to grant to a first user terminal 60 for which it receives a granted group quota, in dependence on the presence or absence of other members of the defined group in which the first user terminal 20 has membership.
The one or more receiving modules 76 are further configured to receive a response from the charging node, the response indicating a granted group quota usable for authorizing consumption of the edge service by members of the defined group. The eCHF 44 includes a deciding module 80 that is configured to decide, as a locally-granted quota, what fraction of the granted group quota to grant to the first user terminal 20, and the one or more sending modules 78 are configured to send a charging response to the CTF, indicating the locally-granted quota.
Deciding what fraction of the granted group quota to grant to the first user terminal 20 comprises, for example, deciding a size of the locally-granted quota, based on the edge service. As another example, deciding what fraction of the granted group quota to grant to the first user terminal 20 comprises deciding a size of the locally-granted quota, based on whether one or more other ones of the affiliated user terminals are connected to the network 10 at a same edge location as the first user terminal 20. As a further example, deciding what fraction of the granted group quota to grant to the first user terminal 20 comprises deciding a size of the locally-granted quota, based on whether one or more temporally-proximate charging requests have been received at the eCHF 44 for any other ones of the affiliated user terminals 20, for the edge service. Any two or more of these bases and other additional or alternate bases are considered jointly, in one or more embodiments, to decide what fraction of the granted user quota to grant as the locally-granted quota.
The fraction of the granted group quota that is granted as the locally-granted quota leaves a remaining portion of the granted group quota as a remaining group quota, for example. In such cases, the method 600 may further comprise the eCHF 44 deciding, as a further locally-granted quota, what fraction of the remaining group quota to grant to another one of the affiliated user terminals 20 in response to the eCHF 44 receiving a charging request for the other one of the affiliated user terminals 20, requesting a quota for authorizing consumption by the other one of the affiliated user terminals 20 of the edge service.
After granting a local quota to the first user terminal 20 from the granted group quota, the eCHF 44 may receive a further charging request from the same or another CTF, where the further charging request requests a quota for authorizing consumption of the edge service by a second user terminal 20 among the affiliated user terminals 20. In at least one embodiment of the method 600, the eCHF 44 decides a further locally-granted quota for the second user terminal 20 from a then-remaining fraction of the granted group quota and sends a further charging response to the same or other CTF, indicating the further locally-granted quota.
Broadly, consider an example case where the eCHF 44 receives a granted group quota in reply to a charging request sent from the eCHF 44 for a first user terminal 20 in a group of affiliated user terminals 20. Further, assume that the eCHF 44 grants less than all of the granted group quota to the first user terminal 20, as a locally-granted quota to authorize consumption of the edge service by the first user terminal 20. The eCHF 44 may then grant a fraction of the remaining group quota to another one of the user terminals 20 operating at the same edge location. However, at some point, the eCHF 44 determines that the remaining group quota is exhausted or insufficient to cover a charging request for one of the user terminals 20, and, in response, it communicates with the charging node to obtain a further quota from the charging node, to authorize consumption of the edge service by the involved user terminal 20. That further quota may be an individual quota targeted to the involved user terminal 20 or may be another group quota that is dividable among the user terminals 20 in the group. Such determination that the remaining group quota is exhausted or insufficient to cover a charging request may be performed at the receipt of a charging request but may also be performed by the eCHF 44 at any time irrespective of incoming charging request as the result of for example determining that the remaining quota is below a threshold or is consumed at a certain pace.
As for the ABMF 50, in the illustrated example it comprises communication interface circuitry 90, processing circuitry 92, and storage 94, which in one or more embodiments stores one or more computer programs 96 and one or more items of configuration data 98. The example ABMF 50 further comprises a power supply 100 that is configured to provide operating power to the various elements or subsystems comprising the ABMF 50.
The communication interface circuitry 90 comprises one or more transmitter circuits and one or more receiver circuits that are configured for the transmission and reception of signaling over one or more types of physical interfaces, e.g., wired or wireless interfaces. In an example embodiment, the communication interface circuitry 90 comprises one or more ethernet interfaces or other data-network interfaces that are operative for sending and receiving charging messages.
The processing circuitry 92 comprises fixed circuitry or programmatically configured circuitry or a mix of fixed and programmatically configured circuitry. In at least one embodiment and with reference to
As such, the storage 94 in one or more embodiments comprises one or more types of computer readable media, such as volatile memory for program execution and nonvolatile memory for longer term program storage. Example computer readable media include any one or more of SRAM, DRAM, FLASH memory, EEPROM, or Solid State Disk (SSD). The storage 104 provides non-transitory storage of computer program instructions for execution by the one or more microprocessor(s) 102, where non-transitory does not necessarily mean permanent or unchanging but rather storage having at least some persistence.
With the above example details in mind, in one embodiment a node is operative as an ABMF 50 for a communication network 10, with the node comprising communication interface circuitry 90 configured to receive and send messages, including requests and responses related to charging, and further comprising processing circuitry 92 operatively associated with the communication interface circuitry 90.
In an example embodiment, the processing circuitry 92 of the ABMF 50 is configured to: receive a request originating from an eCHF 44, requesting a quota for authorizing consumption by a first user terminal 20 of an edge service provided by the network 10, the first user terminal 20 being a member of a defined group of affiliated user terminals; grant a group quota usable for authorizing consumption of the edge service by members of the defined group; and send a response intended for the eCHF 44, indicating the granted group quota.
The processing circuitry 92 in one or more embodiments is configured to grant the group quota, rather than an individual quota, responsive to determining that the eCHF 44 is operative to decide locally-granted quotas from respective granted group quotas, for user terminals 20 that are connected to the network 10 at an edge location associated with the eCHF 44 and are members of respective defined groups. The processing circuitry 92 in one or more embodiments is configured to grant the group quota, rather than an individual quota, responsive to the charging node further determining that the first user terminal 20 belongs to the defined group, based on accessing a data store that indicates group memberships for individual user terminals 20. For example, the configuration data 98 comprises a table or other data structure that links identifiers of user terminals to group identifiers.
The processing circuitry in one or more embodiments is configured to determine that the eCHF 44 is operative to decide locally-granted quotas based on the charging request indicating that the eCHF 44 is operative to decide locally-granted quotas. The indication may be an explicit indication of the capability, e.g., an Information Element (IE) or other data field or element in the charging request message that indicates the capability. However, in at least one embodiment, the indication is implicit, e.g., based on the eCHF 44 identifying itself as an eCHF, the ABMF 50 infers that the eCHF 44 is operative to make local granting decisions—i.e., that the eCHF 44 is operative to use receive and manage group quotas for groups of affiliated user terminals 20.
The response intended for the eCHF identifies, for example, the defined group and the user terminals 20 that are members in the defined group, for use by the eCHF 44 in locally identifying other members of the defined group that connect, or are connected, to the network 10 at an edge location associated with the eCHF 44. The ABMF 50 may include group information in every response that contains a granted group quota, for uniformity. However, in at least one embodiment, if the involved user terminal 20 has already been identified to the eCHF 44 as belonging to a group, the response from the ABMF 50 omits group membership information, although it may still be marked or indicated as containing a group quota.
The ABMF 50 in one or more embodiments includes or communicates with a RF 52 that determines the granted group quota—i.e., rates the service units contained in the granted group quota. If the RF 52 is separate from the ABMF 50, interactions between the RF 52 and the ABMF 50 may be managed by or otherwise conducted through the CHF 48.
In at least one embodiment, the processing circuitry 92 of the ABMF 50 is configured to decide a size of a granted group quota based on at least one of: the edge service, or a known or estimated number of the affiliated user terminals 20 at an edge location associated with the eCHF 44. For example, the ABMF 50 may monitor which user terminals 20 are involved in a succession of charging requests incoming from the eCHF 44, such that it learns how many affiliated user terminals are active, or have recently been active, at the edge location associated with the eCHF 44. The ABMF 50 uses that information to, for example, decide to grant a group quota rather than an individual quota, or to decide the size of a granted group quota. A practical example is the ABMF 50 increasing the size of a granted group quota in response to the number of affiliated user terminals 20 that are active—connected to the network 10—at the edge location of the eCHF 44.
The charging node that performs the method 1000 is, for example, an ABMF 50 such as shown in
Granting the group quota is performed, for example, responsive to the charging node determining that the eCHF 44 is operative to decide locally-granted quotas from respective granted group quotas, for user terminals 20 that are connected to the communication network at an edge location associated with the eCHF 44 and are members of respective defined groups. In at least one embodiment, granting the group quota is performed responsive to the charging node further determining that the first user terminal 20 belongs to the defined group, based on accessing a data store that indicates group memberships for individual user terminals 20, or at least user terminals 20 that belong to the defined group or groups.
Determining that the eCHF 44 is operative to decide locally-granted quotas in one or more embodiments is based on the charging request indicating that the eCHF 44 is operative to decide locally-granted quotas. The response identifies the defined group and the user terminals that are members in the defined group, for use by the eCHF 44 in locally identifying other members of the defined group that connect, or are connected, to the communication network at an edge location associated with the eCHF 44. Further, the charging node in one or more embodiments decides a size of the granted group quota based on at least one of: the edge service, or a known or estimated number of the affiliated user terminals 20 at an edge location associated with the eCHF 44.
1. Service request: UE 1 request for a service that is provided by the NF (e.g., video streaming, internet connection).
2. Charging data request [Initial]: the NF (CTF) determines that the service is chargeable, including which rating group(s) it belongs to, and that it may require quota monitoring. It then sends the information about the rating group and the UE to the eCHF, requesting recording and possibly specifying the size of the requested quota for the service.
3. Data record request [Create]: the eCHF at the SDC 1 (at the edge deployment location) decides based on the charging information and internal configuration that it needs to create a record with the charging information and reservations made and it sends a request to the CDF at the SDC 1.
4. Data record response: the CDF at the SDC 1 records the information by creating a CDR, and it responds to the eCHF with the information that it has been created.
5. Check ongoing reservations: the eCHF checks whether it has any reservations matching the UE1 and the rating group(s) that can be used. The eCHF determines that there are no applicable reservations for UE1.
6. Edge charging request [Initial]: the eCHF sends a request to another charging node, here, a CHF of the SDC 2, requesting service units for UE1 and the rating groups(s). In one or more embodiments, the request may explicitly ask for identification of other UEs that are eligible to use the requested units.
7 Account data request [Get]: the CHF at the SDC 2 decides, based on the charging information in the charging data request and internal configuration information, that it needs to get account information for UE1.
8. Account data response: the ABMF at the SDC 2 checks the account and responds with the account information.
9. Rate request [Reservation]: the CHF at the SDC 2 decides based on the charging information, account data, and internal configuration information, that it needs to rate the service before it can reserve anything from the account.
10. Rate response: the RF at the SDC 2 rates the event based on charging information, account data, and internal configuration information, and responds with the amount to reserve and indicates that an eCHF requested the quota.
11. Account data request [Reserve]: the CHF at the SDC 2 decides, based on the rating, that it needs to reserve from the account.
12. Account data response: the ABMF at the SDC 2 checks the account and responds with a group quota corresponding to the reserved amount and an indication of the UEs connected to the account—i.e., an indication of affiliated UEs that constitute the group eligible to use the granted service units. The ABMF also starts monitoring for any account changes that affect which UEs are connected to the account. Any changes to the account affiliation are communicated to the eCHF, prompting it to make a reauthorization or to otherwise adjust which UEs it considers as being affiliated with respect to consumption of the group quota.
13. Data record request [Create]: the CHF at the SDC 2 decides, based on the charging information and internal configuration information that it needs to create a record with the charging information and reservations made, and it sends a request to the CDF.
14. Data record response: the CDF at the SDC 2 records the information by creating a CDR, it the responds with the information that it has been created.
15. Edge charging response: the CHF at the SDC 2 responds to the eCHF with the outcome of request, e.g., the granted units per rating groups and which UEs may use these units; which UEs are eligible to use the rated units may also be indicated on a per rating-group basis.
16. Data record request [Update]: the eCHF decides, based on the response from CHF at the SDC 2 and internal configuration information, that it needs to update the record with the new information and sends a request to the CDF at the SDC 1.
17. Data record response: the CDF at the SDC 1 records the information from the eCHF by updating the CDR, and it the responds with an indication that the information has been updated.
18. Charging data response: the eCHF responds to the CTF of the NF with the granted service units—i.e., it indicates a locally-granted quota that is a determined fraction of the quota returned from the CHF at the SDC 2. Note, too, that eCHF or the CHF at the SDC 2 may reserve more than needed at the moment for UE1. More generally, any one or more of the ABMF, CHF, or RF at the SDC 2 may allocate a group quota that is larger than that requested for UE 1, to increase the likelihood or practicality of the eCHF being able to serve divide the granted group quota across two or more service requests.
19. Service request: a second UE, UE2, requests for a service that is provided by the NF (e.g., video streaming, internet connection); here, it is assumed that the UE2 requests that same edge service for which the group quota was granted in conjunction with the request for service from UE1.
20. Charging data request [Initial]: the NF (CTF) determines that the service is chargeable, including determining to which rating group(s) it belongs, and that it may require quota monitoring. The CTF then sends information about the rating group and the UE to the eCHF, requesting recording and, possibly, specifying a quota size for the service.
21. Data record request [Create]: the eCHF decides, based on the charging information and internal configuration information that it needs to create a record with the charging information and reservations made and sends a request to the CDF at the SDC 1.
22. Data record response: the CDF at the SDC 1 records the information by creating a CDR and responds to the eCHF with an indication that the information has been created.
23. Check ongoing reservations: the eCHF checks whether it has any reservations matching UE2 and the rating group(s) that can be used for authorizing consumption of the edge service by UE2. The eCHF recognizes that it can use the reservation made for UE1, i.e., there is no need at this point for the eCHF to contact the CHF at the SDC 2, at this point, because the eCHF recognizes that UE2 is eligible to use any remaining service units in the granted group quota returned to it for the earlier service request involving UE1.
24. Charging data response: the eCHF responds to the service request from the CTF for UE2 with a locally-granted quota allocated from the service units remaining in the group quota, where this step presupposes that the fraction of the granted group quota that the eCHF granted for UE1 was less than one hundred percent—i.e., the size of the locally-granted quota provided for UE1 was smaller than the size of the granted group quota.
The steps 7 to 14 may be done in a different order or performed multiple times, depending upon CHF implementation details and what is needed from a request point of view. To avoid unnecessary signaling, the ABMF and the RF may be combined and in that case the CHF at the SDC 2 would make a “rate and reserve” request to the combined AMBF and RF at the SDC 2.
Notably, modifications and other embodiments of the disclosed invention(s) will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention(s) is/are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SE2022/050165 | 2/15/2022 | WO |
