System and method for enabling real-time charging of a data session in a communication network

Abstract

Disclosed is a system and a method for enabling real-time charging of a data session in a communication network. A session charging request associated with a user device is received by a Charging Function (CHF). The CHF monitors data usage associated with the data session and determines occurrence of a predefined usage event prior to termination of the data session. Further, the CHF generates a Credit Control Request (CCR) message corresponding to the usage event and transmits the CCR message to an Online Charging System (OCS). The CHF receives a Credit Control Answer (CCA) message from the OCS indicating a charging decision for the data session and applies one or more control actions based on the charging decision. The disclosed method enables event-triggered charging during the data session, thereby facilitating near real-time charging settlement and reducing dependency on post-session charging data reconciliation.

Description

SYSTEM AND METHOD FOR ENABLING REAL-TIME CHARGING OF A DATA SESSION IN A COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks and systems. More particularly, the present disclosure relates to a system and a method for enabling real-time charging for a data session in a communication network.BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely due to its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] In the field of telecommunications, there has been an increase in demand for high-speed network connectivity owing to technological advancements. Broadband services, thus, have become essential for providing the high-speed network connectivity to users of modem digital infrastructure, catering to requirements of the users for data-intensive applications such as video streaming, online gaming, cloud computing, and the like. However, with expansion in adoption of the broadband services, service providers are facing a challenge of delivering reliable and scalable solutions that meets the demands of millions of users. For instance, the increasing demand for the broadband services has presented challenges related to accurate billing and efficient data usage reconciliation.

[0004] Broadband service providers, particularly those offering high speed connections like Fixed Wireless Access (FWA) Customer Premises Equipment (CPE) connectivity, must sufficiently reconcile data usage to maintain up-to-daterecords and deliver precise billing information to consumers. Existing billing systems typically rely on Call Data Records (CDRs) for data usage reconciliation. The CDRs are generated periodically, often at the end of a session, and are then processed and reconciled to create accurate billing records. This approach introduces significant delays in reflecting real time data usage, making the process unsuitable for scenarios that require immediate updates.

[0005] The dependency of the existing billing systems on CDR reconciliation poses particular challenges in broadband networks catering to high volume of users. A reconciliation process in the broadband networks is time intensive, resulting in delays that hinder timely updates to user accounts. Consequently, there are instances where discrepancies arise between actual data usage and billed amounts, leading to potential discrepancies in user accounts and delayed quota adjustments. For consumers and operators alike, this gap translates into a lack of transparency and potential disputes over billing.

[0006] Furthermore, the existing billing systems faced several limitations since the same relied on batch processing, where data is aggregated and reconciled in periodic intervals. This approach introduces significant delays in updating data usage and billing information. For consumers, the delays translate to a lag in viewing real-time data consumption, leading to potential discrepancies, especially in plans with usage caps or expiry periods. The delays are particularly problematic in the broadband networks serving the high volume of users, where real-time control over data consumption is critical for maintaining user satisfaction and operational efficiency.

[0007] Another significant challenge associated with the existing billing systems is the inability to handle dynamic network scenarios efficiently. Modem telecommunication networks often experience fluctuating traffic patterns, with sudden increase in data usage during events such as live streaming or software updates. The batch processing nature of the CDR reconciliation process struggles to adapt to these variations in real time, leading to sub optimal resource allocation and degraded network performance. This efficiency is further exacerbated in networkswith a high density of connected devices, such as those solving fixed wireless access or Internet of Things (loT) applications.

[0008] Moreover, the existing billing systems lack the capability to implement quota management in real time. The quota management plays a vital role in ensuring that users do not exceed their subscribed their limits, especially in prepaid or pay as you go models. However, due to reliance on offline reconciliation, the users may unknowingly exceed their quotas before their accounts are updated, resulting in bill shock and dissatisfaction. This limitation undermines an operator’s ability to enforce fair usage policies and maintain a balanced distribution of network resources.

[0009] In addition, user experience is significantly impacted by the limitations of the existing billing systems. The inability of the existing billing systems to provide real time updates on data consumption and account balance leaves the users in the dark regarding their usage patterns. This lack of transparency reduces trust in the operator and makes it challenging for the users to manage their data consumption effectively.

[0010] In light of the aforementioned, there is a need for a system and a method for enabling real-time charging for a data session in the communication network, while overcoming the challenges associated with the existing billing systems.SUMMARY

[0011] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key / critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0012] According to an aspect of the present disclosure, disclosed herein is a method for enabling real-time charging for a data session in a communication network. The method comprises receiving, by a receiving module of a Chargingfunction (CHF) co-located with a Broadband Network Gateway (BNG), from a Session Management Function (SMF), a session charging request associated with a user device connected via a Home Gateway (HGW). Deployment of the CHF colocated with the BNG enables distributed processing of charging operations at a network edge, thereby reducing centralized processing load. The method further comprises monitoring, by a monitoring module of the CHF, data usage associated with the data session based on the session charging request. The method further comprises determining, by a determining module of the CHF based on the monitored data usage, occurrence of a predefined usage event prior to termination of the data session. The method further comprises generating, by a generation module of the CHF upon determining the occurrence of the predefined usage event, a Credit Control Request (CCR) message prior to the termination of the data session. Event-triggered generation of the CCR messages reduces unnecessary signaling exchanges between the CHF and the OCS, thereby reducing signaling overhead. Further, the generation of the CCR messages prior to the termination of the data session enables real-time interaction with the OCS, thereby reducing latency in enforcing quota and charging decisions. The method further comprises transmitting, by a transmitting module of the CHF, the CCR message to an Online Charging System (OCS). The method further comprises receiving, by the receiving module from the OCS corresponding to the CCR message, a Credit Control Answer (CCA) message indicating a charging decision for the data session and applying, by a control module of the CHF, one or more control actions on the data session based on the CCA message. This event-triggered charging combined with distributed CHF deployment enables efficient handling of the charging operations across multiple sessions, thereby improving scalability in high-density broadband environments.

[0013] In one or more implementations, the predefined usage event comprises the monitored data usage reaching or exceeding a predefined volume limit associatedwith the data session, or an expiry of a predefined validity time associated with the data session.

[0014] In one or more implementations, the generation of the CCR message in response to occurrence of the predefined usage event reduces post-session charging data record reconciliation by enabling the session charging request to be processed prior to the termination of the data session.

[0015] In one or more implementations, the monitored data usage is aggregated based on a Media Access Control (MAC) address associated with the HGW.

[0016] In one or more implementations, the session charging request comprises a quota management indicator indicating one of an online charging, an offline charging or an event-based charging.

[0017] In one or more implementations, the method further comprises generating, by the generation module upon determining that the quota management indicator indicates an offline charging, a Charging Data Record (CDR) corresponding to the data session and storing, by a storage module, the CDR in a charging data repository.

[0018] In one or more implementations, the CCA message comprises one of a granted service quota for the data session, or an indication to restrict usage of the data session.

[0019] In one or more implementations, the one or more control actions applied on the data session based on the CCA message comprise at least one of permitting continuation of the data session using a granted quota, suspending the data session upon absence of the granted quota or redirecting the user device to a predefined network endpoint to handle the data session.

[0020] According to another aspect of the present disclosure, disclosed is a system for enabling real-time charging for a data session in a communication network, the system comprising a Charging-function (CHF) co-located with a Broadband Network Gateway (BNG), the CHF comprises a receiving module, a monitoringmodule, a determining module, a generation module, a transmitting module, and a control module. The receiving module is configured to receive from a Session Management Function (SMF), a session charging request associated with a user device connected via a Home Gateway (HGW). The monitoring module is configured to monitor data usage associated with the data session based on the session charging request. The determining module is configured to determine, based on the monitored data usage, occurrence of a predefined usage event prior to termination of the data session. The generation module is configured to generate upon determining the occurrence of the predefined usage event, a Credit Control Request (CCR) message prior to the termination of the data session. The transmitting module is configured to transmit the CCR message to an Online Charging System (OCS). The receiving module is configured to receive from the OCS corresponding to the CCR message, a Credit Control Answer (CCA) message indicating a charging decision for the data session and the control module configured to apply one or more control actions on the data session based on the CCA message.BRIEF DESCRIPTION OF DRAWINGS

[0021] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

[0022] FIG. 1 illustrates a block diagram of an example system for enabling realtime charging for a data session in a communication network.

[0023] FIG.2 illustrates a block diagram depicting an example system architecture of a CHF-BNG for enabling the real-time charging for the data session in the communication network, in accordance with an embodiment of the present disclosure.

[0024] FIG. 3 illustrates an operational flow diagram for enabling the real-time charging for the data session in the communication network.

[0025] FIG. 4 illustrates a flow of a method for enabling the real-time charging for the data session in the communication network, in accordance with an embodiment of the present disclosure.

[0026] FIG. 5 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

[0027] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0028] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. Thepresent disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0029] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” or “some implementations” which may each refer to one or more or all of the same or different embodiments or implementations. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” or “in an implementation” refers to one embodiment or one implementation and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments ”. Further, the term, for example, “in one or more implementations” refers to “at least one implementation, or more than one implementation, or all implementations.

[0030] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.

[0032] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0033] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0034] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0035] In conventional charging systems, charging decisions are typically performed after termination of a data session based on accumulated usage information, resulting in delayed charging processing and increased reliance on post-session reconciliation mechanisms. However, the present disclosure enables generation of the charging requests during an active data session based on occurrence of predefined usage events. This allows charging decisions to be made in-session and, in certain implementations, at the network edge through deployment of a Charging Function (CHF) co-located with a Broadband Network Gateway (BNG). Thus, the present disclosure discloses a system and a method for real-time data usage reporting and billing in a broadband network by expediting ChargingData Record (CDR) reconciliation for Fixed Wireless Access (FWA) Customer premises equipment (CPE) consumers' data usage.

[0036] An aspect of the present disclosure is to provide a system and a method that may provide an event-based credit control mechanism for real-time data usage reporting and billing in the broadband network.

[0037] Another aspect of the present disclosure is to provide a system and a method that may eliminate delays associated with the CDR reconciliation.

[0038] Yet another aspect of the present disclosure is to provide a system and a method that may detect and report data usage events such as data usage nearing predefined limits (volume limit) or expiration of validity periods promptly.

[0039] A further aspect of the present disclosure is to provide a system and a method that may monitor and process the data usage from Home Gateway (HGW) devices during data sessions and may communicate the data usage to an Online Charging System (OCS) through the event-based triggers, ensuring accurate and real time billing.

[0040] Another aspect of the present disclosure is to provide a system and a method that may enhance the accuracy of data usage billing for broadband consumers, particularly in high-volume scenarios.

[0041] Several key terms used in the description play pivotal roles in facilitating the system functionality. In order to facilitate an understanding of the description, the key terms are defined below.

[0042] The HGW- The HGW may refer to a local access point through which a user device connects to a fixed access network. The HGW may act as a bridge or router between the user’s internal network and a Broadband Network Gateway (BNG).

[0043] The BNG- The BNG may refer to a network node in fixed broadband networks responsible for initiating and managing subscriber sessions, enforcingpolicies, and forwarding charging requests. The BNG may be responsible for triggering session charging requests based on detected user traffic.

[0044] Session charging request - The term session charging request may refer to a message or signal generated to initiate charging operations for the data session associated with the user. The session charging request may include session-specific parameters such as session ID, MAC address, quota management indicator, or service parameters.

[0045] The quota management indicator- The quota management indicator may refer to a flag or field in the session charging request that indicates whether quotabased online charging is applicable for the session. The indicator may signal one of: online charging required, offline charging applicable, or quota-less event based charging.

[0046] Converged Charging Function (CHF)- The CHF may refer to a network function responsible for managing charging decisions in real time, generating charging messages Credit Control Request (CCR), interpreting responses say Credit Control Answer (CCA) and interfacing with the Online Charging System (OCS).

[0047] The CCR- The CCR may refer to a request message generated by the CHF to the charging decision system to obtain quota or credit authorization for the data session. The CCR may include details such as subscriber ID, usage context, requested quota, and service category.

[0048] The CCA- The CCA may refer to a response message from the charging decision system to the CHF, indicating whether quota is granted, denied, or redirected. The message may contain granted quota units, validity time, redirection addresses, or session control instructions.

[0049] The CDR- The CDR may refer to a structured record generated when the offline charging is applied or when fallback occurs. The CDR typically includessession information, usage volume, duration, and subscriber details, and is used for post-processing, billing, or audit purposes.

[0050] Redirection instruction- The term redirection instruction may refer to an instruction within the CCA message that causes the user device’s session to be redirected to a specific network endpoint, such as a notification service, recharge portal, or policy server, typically in response to lack of quota or a usage restriction event.

[0051] Session Management Function (SMF)- The term SMF may refer to a network function configured to manage establishment, modification, and termination of the data sessions associated with user devices in the communication network. The SMF is configured to communicate session-related information to the charging functions of the network, including the session charging requests and usage-related parameters associated with the data session.

[0052] The OCS- The term OCS may refer to a network charging entity configured to perform real-time charging control for the data sessions by evaluating the session charging requests received from the CHF. The OCS is configured to process the CCR messages associated with data usage events and to return corresponding CCA messages indicating charging decisions, including granting service quotas, restricting data usage, or terminating the data session.

[0053] Fault, Configuration, Accounting and Performance (FCAP) Manager- The term FCAP Manager may refer to a network management component configured to monitor, manage, and control operational parameters of network elements within the communication network. The FCAP Manager is configured to perform management functions including fault detection and reporting, configuration management, accounting information collection, and performance monitoring for network nodes and services.

[0054] Service Data Layer Command Line Interface (SDL CLI)- The term SDL CLI may refer to an administrative interface configured to allow authorized users ormanagement systems to interact with the SDL for performing configuration, monitoring, and operational management tasks. The SDL CLI may be used to issue command-line instructions for accessing service-related data, configuring system parameters, or retrieving operational information associated with network services and charging functions within the communication network.

[0055] High Availability State Manager (HSM)- The term HSM may refer to a network management component configured to coordinate operational states of multiple instances of the network function, including instances operating in active mode and standby mode, and to facilitate state synchronization, monitoring, and controlled switchover between the instances.

[0056] Service Communication Proxy (SCP)- The term SCP may refer to the network function configured to facilitate communication between network services in a service-based architecture. The SCP is configured to route, proxy, and manage service requests exchanged between the network functions, including forwarding requests, performing service discovery, and applying routing or policy rules associated with service communication.

[0057] Active mode- The term active mode, as referred to in the present disclosure, may refer to an operational state of the network instance in which the instance actively processes network traffic, service requests, or operational tasks associated with the network function implemented by the instance.

[0058] Hot standby mode- The term Hot standby mode, as referred to in the present disclosure, may refer to the operational state of a redundant network instance that remains operational and synchronized with an active instance while not actively processing primary service requests. The instance operating in hot standby mode maintains updated configuration and operational state information and is prepared to assume active operational responsibilities with minimal delay in response to failure, unavailability, or switchover of the active instance.

[0059] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 5, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0060] FIG. 1 illustrates a block diagram of an example communication system 100 for enabling real-time charging for the data session in the communication network, in accordance with an embodiment of the present disclosure. The communication system 100 includes a primary site 110 and a secondary site 120 to ensure uninterrupted session data management and service continuity in the communication network. Each of the primary site 110 and the secondary site 120 includes components that work in coordination to manage the user data sessions, handle failures, and synchronize the session data.

[0061] The primary site 110 includes active components responsible for service management and data processing, whereas the secondary site 120 operates as a standby or backup site, ready to take over operations in an event of the failure at the primary site 110. Both the primary site 110 and the secondary site 120 are interconnected and enables the synchronization of the session data under normal operational conditions.

[0062] The primary site 110 represents a central hub where the core functionalities of the communication system 100, such as traffic management, quota allocation, and event-based charging are performed. The primary site 110 is responsible for hosting key subsystems and modules (of the communication system 100) that ensure high speed data processing, quota monitoring and efficient communication with external management systems. The primary site 110 includes various components such as an FCAP Manager (active) 116, a High Availability State Manager- 1 (HSM-1), and an HSM-2.

[0063] The communication system 100 further includes an Element Management System (EMS) 128 for centralized control and monitoring of the communication system 100. The EMS 128 interfaces with the components at both the primary site 110 and the secondary site 120. The EMS 128 communicates directly with FCAP managers and other interfaces at both the primary site 110 and the secondary site 120.

[0064] Further, a SDL CLI module 112 may provide an administrative access for configuring and managing an SDL 118, and modules such as Ml, M2, M3, M1S1, M2S1 and M3 SI, and related components at the primary site 110.

[0065] An App CLI 114 and an APP CLI 124 at the primary site 110 and the secondary site 120 respectively may enable network operators to manage application-specific configurations, monitor application-level statistics, and resolve issues directly at an application layer.

[0066] The FCAP Manager (active) 116 is responsible for managing the configuration, fault detection, accounting data, and performance data at the primary site 110 and operates in an active state to coordinate the session management. The HSM-1 serves as a service manager active instance and manages user session data, and interacts with other system components, such as the SDL 118. The HSM-1 governs all Charging Function Broadband Network Gateway (CHF-BNG) instances registered in a cluster at the primary site 110. The system cluster refers to a collection of the CHF-BNG instances running at the primary site 110. The CHF-BNG instances are responsible for managing and processing the session charging-related requests by the users. The cluster ensures that multiple CHF-BNG instances work together to handle load, provide redundancy, and ensure high availability. In an implementation, the CHF-BNG instances 1, 2 are managed at the primary site 110.

[0067] An incoming traffic from a Service Communication Proxy (SCP) is directed to the primary site 110 for processing by the CHF-BNG instances. The incoming traffic includes user-specific quota requests.

[0068] The HSM-2 operates in a hot standby mode and may take over service management if the HSM-1 fails. The HSM-2 continuously monitors state of the HSM-1 and ensures readiness to transition to active mode if required.

[0069] The secondary site 120 ensures session redundancy by replicating the session data from the primary site 110. In an implementation, the CHF-BNG instance 3 is managed at the secondary site 120. During split brain scenarios, the primary site 110 and the secondary site 120 switches to an active-active mode to process the quota requests. The secondary site 120 includes backup and standby components. The components include an FCAP Manager (standby) 126 which operates in a standby mode, synchronized with the FCAP Manager (active) 116 at the primary site 110. The FCAP Manager (standby) 126 becomes active in the event of the failure at the primary site 110 taking over the configuration and fault management functions. An HSM-3 serves as a service manager spare instance, providing additional backup support to the HSMs at the primary site 110.

[0070] In various embodiments, similar to the primary site 110, the SDL 118 at the secondary site 120 may manage the session data generated during operations and comprises various modules like M1S2, M2S2 and M3S2. These components enable the secondary site 120 to provide failover support and data synchronization.

[0071] Similar to the SDL CLI 112 at the primary site 110, an SDL CLI 122 may provide the administrative access to configure and manage modules of the SDL 118.

[0072] A monitoring tool 140 communicates with both the primary site 110 and the secondary site 120 and provides real-time visibility into the system's performance, detects faults, and assists in troubleshooting operational issues. The monitoring tool 140 is configured to monitor, analyze, and report various performance metrics associated with the system’s components and processes. The monitoring tool 140 is configured to collect data on system’s performance metrics in real time, including processing delays, data throughput, quota utilization, and event triggers within the network. The performance monitoring tool 140 is further configured to monitor health and status of system components, to ensure they are functioning withindefined operational parameters. The monitoring tool 140 interacts with the EMS 128 and the FCAP managers to provide insights about system efficiency and detect anomalies.

[0073] Although FIG. 1 illustrates one example of the communication system 100, various changes may be made to FIG. 1. For example, the communication system 100 may include any number of FCAP managers and SDLs in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components in FIG. 1 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0074] FIG. 2 illustrates a block diagram 200 (may also be referred as the system 200) depicting an example system architecture of a CHF 202 for enabling the realtime charging for the data session in the communication network, in accordance with an embodiment of the present disclosure. The embodiment of the system architecture of the CHF 202 as shown in FIG. 2 is for illustration only. However, the CHF 202 may come in a wide variety of configurations, and FIG. 2 does not limit the scope of the present disclosure to any particular system architecture of the CHF 202.

[0075] As shown in FIG. 2, the system architecture of the CHF 202 includes one or more processors 210 (hereinafter also referred to as “processor 210”), a memory 220, a communication unit 230, an interface(s) 240, and a processing unit(s) / module(s) 250. These components may be in electronic communication via one or more buses (e.g., communication bus 260).

[0076] The one or more components of the CHF 202 are communicatively coupled with the processor 210 (described below) to perform operations for enabling the real-time charging for the data session. The processor 210 may include various processing circuitry and configured to execute programs or computer readable instructions stored in the memory 220. The processor 210 may also include an intelligent hardware device including a general -purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an ApplicationProcessor (AP), a dedicated processor, or the like, a microcontroller, a Field-Programmable Gate Array (FPGA), a programmable logic device, a discrete hardware component, or any combination thereof. In some cases, the processor 210 may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into the processor 210. The processor 210 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 220) to cause the CHF 202 to perform various functions.

[0077] The memory 220 is communicatively coupled to the processor 210. A part of the memory 220 may include a RAM, and another part of the memory 220 may include a flash memory or other ROM. The memory 220 is configured to store a set of instructions required by the processor 210 for controlling overall operations of the CHF 202. The memory 220 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of Electrically Programmable Memories (EPROM) or Electrically Erasable and Programmable (EEPROM) Memories. In addition, the memory 220 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory 220 is non-movable. In some examples, the memory 220 can be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 220 can be an internal storage unit or it can be an external storage unit of the CHF, cloud storage, or any other type of external storage.

[0078] More specifically, the memory 220 may store computer-readable instructions including instructions that, when executed by a processor (e.g., the processor 210) cause the CHF 202 to perform various functions described herein. In some cases, the memory 220 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0079] The communication unit 230 includes an electronic circuit specific to a standard that enables wired or wireless communication. The communication unit 230 is configured to communicate internally between internal hardware components and with external devices via one or more networks. The communication unit 230 may be configured to enable the CHF 202 to communicate with various entities through backhaul connection (e.g. wired backhaul or wireless backhaul) or a network. Examples of the communication unit 230 may include, but are not limited to, a modem, a network interface such as an Ethernet card, a communication port, and / or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and a local buffer circuit. It will be apparent to a person of ordinary skill in the art that the communication unit 230 may include any device and / or apparatus capable of providing wireless or wired communications between the CHF 202 and various other entities of the communication network.

[0080] The interface(s) 240 may include suitable logic, circuitry, a variety of interfaces, and / or codes that may be configured to receive input(s) and present output(s) to the user devices. The variety of interfaces may include interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. For example, the I / O interface may have an input interface and an output interface. The interface(s) 240 may facilitate communication of the CHF 202 with various devices and systems connected to it. The interface(s) 240 may also provide a communication pathway for one or more components of the CHF 202. Examples of such components include, but are not limited to, the processing units(s) / module(s) 250.

[0081] In one or more embodiments, the processing unit(s) / module(s) 250 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the CHF. In non-limiting examples, described herein, such combinations of hardware andprogramming may be implemented in several different ways. For example, the programming for the processing unit(s) / module(s) 250 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor 210 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit(s) / module(s) 250. In such examples, the CHF 202 may also comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the CHF 202 and the processing resource. In other examples, the processing unit(s) / module(s) 250 may be implemented using an electronic circuitry.

[0082] In one or more embodiments, the processing unit(s) / module(s) 250 may include one or more units / modules. The receiving module 250-2 is configured to receive from the SMF, the session charging request associated with the user device connected via the HGW. The session charging request includes the quota management indicator. A monitoring module 250-4 is configured to monitor the data usage associated with the data session based on the session charging request. A determining module 250-6 is configured to determine based on the monitored data usage, occurrence of a predefined usage event prior to termination of the data session. A generation module 250-8 is configured to generate upon the determination of the occurrence of the predefined usage event, the CCR message prior to the termination of the data session and a transmitting module 250-10 is configured to transmit the CCR to the OCS. The receiving module 250-2 is configured to receive from the OCS corresponding to the CCR message, the CCA message indicating the charging decision for the data session and a control module 250-12 is configured to apply one or more control actions on the data session based on the CCA message.

[0083] The generation module 250-8 is configured to generate, upon determining that the quota management indicator indicates an offline charging, the CDRcorresponding to the data session and a storage module 250-14 is configured to store the CDR in a charging data repository.

[0084] Although FIG. 2 illustrates one example of the system architecture of the CHF 202, various changes may be made to FIG. 2. Further, the CHF 202 may include any number of components in addition to those shown in FIG. 2, without deviating from the scope of the present disclosure. Further, various components in FIG. 2 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0085] FIG.3 illustrates an operational flow diagram 300 for enabling the real-time charging for the data session in the communication network, in accordance with an embodiment of the present disclosure.

[0086] The flow diagram 300 indicating communication between a Session Management Function (SMF) 302, a CHF 202 and an Online Charging System (OCS) 304 is represented in FIG. 3. The flow diagram 300 involves real data usage reporting of the HGW devices based on specific events such as usage volume threshold and a time quota. Subsequently, the CHF 202 issues an event-based charging trigger, reporting the data consumed by the HGW devices to the OCS 304 for final billing.

[0087] At step 301, the SMF 302 initiates a converged charging update / release request and sends the converged charging update / release request to the CHF 202 using a POST method. The converged charging update / release request includes information associated with requested units (amount of data required) and used units (amount of data already consumed). The converged charging update / release request also specifies triggering events such as the usage volume threshold (when data usage threshold is reached) and the time quota (when user’s subscription validity expires). The converged charging update / release request specifies whether a quota request is to be handled locally by the CHF 202 without OCS 304 intervention or whether the CHF 202 needs to report the data usage events to the OCS 304. Upon receiving the converged charging update / release request, the CHF 202 processes and analyzes theconverged charging update / release request to determine whether the data usage events need to be reported to the OCS 304 for quota deduction.

[0088] At step 303, the CHF 202 triggers an event based CCRto the OCS 304. The CCR contains details of the data consumed by the HGW device i.e., used units reported in Multiple Services Credit Control (MSCC) and is triggered by specific events (for example, volume or validity triggers). The CHF 202 requests a quota update or deduction based on user’s plan. The OCS 304 processes the CCR to determine whether the user has sufficient data balance or an active data plan.

[0089] At step 305, the OCS 304 computes the updated quota status by deducting the reported data usage. Once the deduction is complete, the OCS 304 sends an event based CCA to the CHF 202. The CCA confirms that the data usage has been successfully reported and the corresponding quota has been adjusted in real time.

[0090] At step 307, the CHF 304 upon receiving the CCA from the OCS 304, sends a 200 OK message (converged charging answer) to the SMF 302. If the quota is granted, the CHF 202 informs the SMF 302 that the user has received Granted Service Units (GSUs).

[0091] If the quota management indicator detects that the OCS 304 is offline or unresponsive, the CHF 202 generates the CDR capturing the data usage event. The CDR is stored locally and later reconciled with the OCS 304 when connectivity is restored. The CDR serves as a backup record of the user's data usage, ensuring that billing and reconciliation processes can proceed accurately when the system becomes fully operational. This fallback mechanism guarantees uninterrupted service and reliable data tracking, even during system downtimes.

[0092] FIG.4 illustrates a flow of a method 400 for enabling the real-time charging for the data session in the communication network, in accordance with an embodiment of the present disclosure.

[0093] The method 400 illustrates a process for enabling real-time charging for the data session in the communication network, such as a fixed broadband access network involving a Broadband Network Gateway (BNG). The method may be executed at the CHF, or the CHF co-located with the BNG node.

[0094] At step 402, the receiving module 250-2 may receive, from the SMF, the session charging request associated with the user device. The user device may be connected via the HGW to the broadband access network. The session charging request may include various session parameters, including the quota management indicator that identifies whether the session is to be subjected to online charging, offline charging, or event-based charging. The request may be triggered when the user initiates the session that consumes chargeable network resources, such as internet access via the HGW. The SMF 302 may detect session initiation and transmit the session charging request toward the CHF -BNG node accordingly. If the quota management indicator signifies the offline charging, the system may fallback to traditional CDR generation and skip the CCR generation. If the quota management indicator signifies online quota-based charging, the method 400 continues toward real-time charging authorization.

[0095] At step 404, the monitoring module 250-4 may monitor the data usage associated with the data session based on the received session charging request. In some implementations, monitoring the data usage may include tracking the amount of data consumed during the data session associated with the HGW. The monitoring operation may be performed continuously or periodically throughout the duration of the data session. The monitored data usage information may be used to evaluate whether predefined charging conditions or usage thresholds associated with the data session is reached. In an embodiment, the monitored data usage is aggregated based on a Media Access Control (MAC) address associated with the HGW.

[0096] At step 406, the determining module 250-6 may determine, based on the monitored data usage, whether the predefined usage event has occurred prior to termination of the data session. The predefined usage event may correspond to acharging trigger condition associated with the data session. In certain implementations, the predefined usage event may include one or more of reaching the predefined data usage threshold, expiry of the validity time associated with the granted quota, or the occurrence of the predefined charging trigger configured for the data session. In an example implementation, the determining module 250-6 may periodically or continuously compare monitored data usage against the predefined data usage threshold. The predefined usage event occurs when the monitored data usage reaches or exceeds the predefined data usage threshold (may also be referred as “the threshold”). For instance, when the monitored data usage increases from a value below the threshold to a value equal to or greater than the threshold, the threshold crossing condition is detected. In another implementation, the CHF 202 may maintain a validity timer associated with the granted service quota. The determining module 250-6 may determine the occurrence of the predefined usage event upon expiry of the validity time, irrespective of the consumed data volume. For example, a quota validity time of 10 minutes may be configured, and upon expiry of the validity time, the determining module 250-6 determines occurrence of the predefined usage event. In certain implementations, the predefined usage event may be defined based on configuration policies provisioned in the CHF 202, where the configuration policies specify one or more threshold conditions, trigger types, and reporting rules associated with the data session. The determination of the predefined usage event enables event-based charging operations to be initiated during the data session rather than after completion of the session.

[0097] At step 408, upon determining that the predefined usage event has occurred, the generation module 250-8 generates the CCR message corresponding to the detected usage event. The CCR message is generated prior to termination of the data session, thereby enabling the charging information associated with the session to be processed during the session. In one or more embodiments, the CCR message may include charging-related parameters such as, but not limited to, usage volume information, subscriber identifiers (e.g., MAC address associated with HGW-MAC), the session ID, service type (e.g., data, video), quota request parameters, orother charging attributes associated with the data session. The generation of the CCR message based on the predefined usage event enables event-triggered reporting of charging information.

[0098] At step 410, the generated CCR message is transmitted by the transmitting module 250-10 to the OCS 304. The OCS 304 is configured to process the received CCR message and evaluate charging policies associated with the data session. The CCR message provides the OCS 304 with the information required to determine whether additional service quota should be granted or whether restrictions should be applied to the ongoing data session. At step 412, the receiving module 250-2 receives the CCA message from the OCS 304 in response to the transmitted CCR message. The CCA message may include the charging decision associated with the data session. The charging decision may indicate one or more of granting of the service quota for continuation of the data session (e.g., volume in MB or duration in seconds, the validity time), restriction of further data usage, termination of the data session, or other charging control instructions.

[0099] At step 414, the control module 250-12 applies the one or more control actions to the data session based on the charging decision included in the received CCA message. The control actions may include, for example, permitting continuation of the data session with the granted quota, restricting or throttling the data usage, suspending or terminating the data session, or redirecting the user device to a predefined network endpoint.

[0100] By generating the CCR messages based on occurrence of the predefined usage events prior to termination of the data session, the disclosed method enables event-triggered charging and near real-time settlement of the charging information, thereby reducing reliance on post-session charging data reconciliation.

[0101] FIG.5 illustrates an exemplary computer system 500 in which or with which embodiments of the present disclosure may be implemented, in accordance with an embodiment of the present disclosure.

[0102] As shown in FIG. 5, the computer system 500 may include a bus 510, a processing unit 520, a main memory 530, a Read Only Memory (ROM) 540, a storage device 550, an input device 560, an output device 570, and a communication interface 580. The bus 510 may include a path that permits communication among the other components of the computer system 500.

[0103] The processing unit 520 may include one or more processors or microprocessors which may interpret and execute stored instructions associated with one or more processes, or processing logic that implements the one or more processes. For example, the processing unit 520 may include, but is not limited to, programmable logic such as Field Programmable Gate Arrays (FPGAs) or accelerators. The processing unit 520 may include software, hardware, or a combination of software and hardware for executing the processes described herein.

[0104] The main memory 530 may include a random-access memory (RAM) or another type of dynamic storage device that may store information and, in some implementations, instructions for execution by the processing unit 520. The ROM 540 may include a ROM device or another type of static storage device (e.g., Electrically Erasable Programmable ROM (EEPROM)) that may store static information and, in some implementations, instructions for use by the processing unit 520.

[0105] The storage device 550 may include a magnetic, an optical, and / or a solid state (e.g., flash drive) recording medium and its corresponding drive. The main memory 530, the ROM 540 and the storage device 550 may each be referred to herein as a “non-transitory computer-readable medium” or a “non-transitory storage medium.” The process / methods set forth herein can be implemented as instructions that are stored in the main memory 530, the ROM 540, and / or the storage device 550 for execution by the processing unit 520.

[0106] The input device 560 may include one or more devices that permit an operator to input information to the computer system 500, such as, for example, a keypad or a keyboard, a display with a touch sensitive panel, voice recognitionT1and / or biometric mechanisms etc. The output device 570 may include one or more devices that output information to the operator, including a display, a speaker, etc. The input device 560 and the output device 570 may, in some implementations, be implemented as a user interface (UI) that displays UI information and which receives user input via the UI. The communication interface 580 may include one or more transceivers that enable the computer system 500 to communicate with other devices and / or systems.

[0107] The computer system 500 may perform certain operations or processes, as may be described herein. The computer system 500 may perform these operations in response to the processing unit 520 executing software instructions contained in a computer-readable medium, such as the main memory 530. The “computer-readable medium” may be defined as a physical or logical memory device. The logical memory device may include memory space within a single physical memory device or spread across multiple physical memory devices. The software instructions may be read into the main memory 530 from another computer-readable medium, such as the storage device 550, or from another device via the communication interface 580. The software instructions contained in the main memory 530 may cause the processing unit 520 to perform the operations or processes, as described herein. Alternatively, hardwired circuitry (e.g., logic hardware) may be used in place of, or in combination with, software instructions to implement the operations or processes, as described herein. Thus, exemplary implementations are not limited to any specific combination of hardware circuitry and software.

[0108] The configuration of components of the computer system 500 illustrated in FIG. 5 is for illustrative purposes only. Other configurations may be implemented. Therefore, the computer system 500 may include additional, fewer and / or different components, arranged in a different configuration, than depicted in FIG. 5.

[0109] Now, referring to the technical abilities and advantageous effect of the present disclosure, the embodiments disclosed herein provide a system and amethod that enables generation of the charging requests upon occurrence of the predefined usage events during the data session. The charging information is thus processed during the data session rather than after the session termination, thereby improving charging timeliness and reducing reconciliation delay associated with post-session charging data processing. Another noteworthy advantage provided by the one or more embodiments of the present disclosure includes providing the system and the method that ensures accurate and timely updates to the user data usage and quota allocation by leveraging event-based communication between the SMF, the CHF-BNG and the OCS. Additionally, generation of charging requests during the data session reduces reliance on post-session charging data records, thereby minimizing post-session processing load on charging systems and reducing dependency on offline reconciliation mechanisms. Further, the use of the quota management indicator enables optimized interaction with the OCS, thereby reducing unnecessary signaling and improving overall system performance and scalability, particularly in high-density broadband environments.

[0110] Furthermore, real-time monitoring of session data usage enables precise and dynamic charging decisions based on actual usage conditions, while also allowing charging control actions to be applied without requiring termination of the data session, thereby avoiding unnecessary session interruption. Thus, the event-triggered generation of the charging requests reduces signaling load on centralized charging systems and improves real-time control of network resources. The method can be implemented in the CHF-BNG to support large-scale subscriber networks. Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[0111] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.

[0112] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.LIST OF REFERENCE NUMERALS

[0113] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:100 - Communication system110- Primary site112- SDL CLI module at primary site114- App CLI at primary site116- FCAP manager (active)118- SDL120- Secondary site122- SDL CLI module at secondary site124- App CLI at secondary site126- FCAP manager (Standby)128- Element Management System (EMS)140-Monitoring tool200- System202 - CHF210 - Processor220 - Memory230- Communication Unit240 - Interface(s)250 - Processing Unit(s)250-2 - Receiving module250-4 - Monitoring module250-6 - Determining module250-8 - Generation module250-10 - Transmitting module250-12 - Control module250-14- Storage module260 - Bus300 - Operational flow diagramSteps 301-307- Method steps of flow diagram 300 302- Session Management Function (SMF)304-OCS400 - Method402-414- Steps to perform the method 400500 - Computer System510 -Bus520 - Processing Unit530 - Main Memory540 -ROM550 - Storage Device560 - Input Device570 - Output Device580 - Communication Interface

Claims

We Claim:

1. A method (400) for enabling real-time charging for a data session in a communication network, the method comprising:receiving, by a receiving module (250-2) of a Charging-function (CHF) (202) co-located with a Broadband Network Gateway (BNG), from a Session Management Function (SMF), a session charging request associated with a user device connected via a Home Gateway (HGW);monitoring, by a monitoring module (250-4) of the CHF (202), data usage associated with the data session based on the session charging request;determining, by a determining module (250-6) of the CHF (202) based on the monitored data usage, occurrence of a predefined usage event prior to termination of the data session;generating, by a generation module (250-8) of the CHF (202) upon determining the occurrence of the predefined usage event, a Credit Control Request (CCR) message prior to the termination of the data session;transmitting, by a transmitting module (250-10) of the CHF (202), the CCR message to an Online Charging System (OCS);receiving, by the receiving module (250-2) from the OCS corresponding to the CCR message, a Credit Control Answer (CCA) message indicating a charging decision for the data session; andapplying, by a control module (250-12) of the CHF (202), one or more control actions on the data session based on the CCA message.

2. The method (400) as claimed in claim 1, wherein the predefined usage event comprises the monitored data usage reaching or exceeding a predefined volume limit associated with the data session, or an expiry of a predefined validity time associated with the data session.

3. The method (400) as claimed in claim 1, wherein the generation of the CCR message in response to occurrence of the predefined usage event reduces post-session charging data record reconciliation by enabling the session charging request to be processed prior to the termination of the data session.

4. The method (400) as claimed in claim 1, wherein the monitored data usage is aggregated based on a Media Access Control (MAC) address associated with the HGW.

5. The method (400) as claimed in claim 1, wherein the session charging request comprises a quota management indicator indicating one of an online charging, an offline charging or an event-based charging.

6. The method (400) as claimed in claim 1, further comprising:generating, by the generation module upon determining that the quota management indicator indicates an offline charging, a Charging Data Record (CDR) corresponding to the data session; andstoring, by a storage module (250-14), the CDR in a charging data repository.

7. The method (400) as claimed in claim 1, wherein the CCA message comprises one of a granted service quota for the data session, or an indication to restrict usage of the data session.

8. The method (400) as claimed in claim 1, wherein the one or more control actions applied on the data session based on the CCA message comprise at least one of permitting continuation of the data session using a granted quota, suspending the data session upon absence of the granted quota or redirecting the user device to a predefined network endpoint to handle the data session.

9. A system (200) for enabling real-time charging for a data session in a communication network, the system comprising a Charging-function (CHF) (202) co-located with a Broadband Network Gateway (BNG), the CHF (202) comprising:a receiving module (250-2) configured to receive from a Session Management Function (SMF), a session charging request associated with a user device connected via a Home Gateway (HGW);a monitoring module (250-4) configured to monitor data usage associated with the data session based on the session charging request;a determining module (250-6) configured to determine, based on the monitored data usage, occurrence of a predefined usage event prior to termination of the data session;a generation module (250-8) configured to generate upon determining the occurrence of the predefined usage event, a Credit Control Request (CCR) message prior to the termination of the data session;a transmitting module (250-10) configured to transmit the CCR message to an Online Charging System (OCS)(304);the receiving module (250-2) configured to receive from the OCS corresponding to the CCR message, a Credit Control Answer (CCA) message indicating a charging decision for the data session; anda control module (250-12) configured to apply one or more control actions on the data session based on the CCA message.

10. The system (200) as claimed in claim 9, wherein the predefined usage event comprises the monitored data usage reaching or exceeding a predefined volume limit associated with the data session, or an expiry of a predefined validity time associated with the data session.

11. The system (200) as claimed in claim 9, wherein the generation of the CCR message in response to occurrence of the predefined usage event reduces postsession charging data record reconciliation by enabling the session charging request to be processed prior to the termination of the data session.

12. The system (200) as claimed in claim 9, wherein the monitored data usage is aggregated based on a Media Access Control (MAC) address associated with the HGW13. The system (200) as claimed in claim 9, wherein the session charging request comprises a quota management indicator including one of an online charging, an offline charging or an event-based charging.

14. The system (200) as claimed in claim 9, wherein:the generation module (250-8) is configured to generate, upon determining that the quota management indicator indicates an offline charging, a Charging Data Record (CDR) corresponding to the data session; anda storage module (250-14) is configured to store the CDR in a charging data repository.

15. The system (200) as claimed in claim 9, wherein the CCA message indicates one of a granted service quota for the data session, or an indication to restrict usage of the data session.

16. The system (200) as claimed in claim 9, wherein the one or more control actions applied on the data session based on the CCA message comprise at least one of permitting continuation of the data session using a granted quota or suspending the data session upon absence of the granted quota or redirecting the user device to a predefined network endpoint to handle the data session.

17. A computer program product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations comprising:receiving a session charging request associated with a user device connected via a Home Gateway (HGW);monitoring data usage associated with the data session based on the session charging request;determining, based on the monitored data usage, occurrence of a predefined usage event prior to termination of the data session;generating, upon determining the occurrence of the predefined usage event, a Credit Control Request (CCR) message prior to the termination of the data session;transmitting the CCR message to an Online Charging System (OCS) (304); receiving a Credit Control Answer (CCA) message indicating a charging decision for the data session corresponding to the CCR message; andapplying one or more control actions on the data session based on the CCA message.

Images