Method and system for synchronizing data usage information in a network

Abstract

The present disclosure provides a method (500) and a system (108) for synchronizing data usage information in a network (106). The method (500) includes receiving, by a first network function (CHF-BNG) (304), a request(s) from a second network function (SMF) (302), the request comprising a session creation, update, or termination request, and an associated flag. Upon determining that the flag is a true flag, the first network function extracts data usage information from the request. Further, a Credit Control Request (CCR) message is generated by the first network function based on the extracted data usage information. The extracted data usage information is encoded in the form of AVPs. The CCR message is transmitted to an OCS (306) to ensure real-time synchronization of user data usage, enabling accurate charging and reporting. The method (500) improves latency, accuracy, and efficiency in data usage management and billing operations.

Description

METHOD AND SYSTEM FOR SYNCHRONIZING DATA USAGE INFORMATION IN A NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to JIO PLATFORMS LIMITED or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The embodiments of the present disclosure generally relate to telecommunication networks. In particular, the present disclosure relates to a method and a system for synchronizing data usage information in a network.DEFINITIONS

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term ‘data usage’ used herein in the specification refers to a total amount of data consumed by a user associated with a User Equipment (UE) within a telecommunication network. The data usage includes all types of data traffic, such as downloading, uploading, streaming, browsing, and other internet-related activities that utilize the network resources. The data usage encompasses both thevolume of data (measured in bytes or bits) and the rate at which the data is consumed over time, typically tracked in real-time by a Session Management Function (SMF) and Charging Function -Broadband Network Gateway (CHF- BNG).

[0005] The term ‘Charging Function-Broadband Network Gateway (CHF- BNG)’ used herein in the specification refers to a specific configuration of a network function (e.g., the CHF) integrated with a gateway (e.g., the BNG). In this configuration, the CHF manages billing and charging rules specifically for broadband services delivered via the BNG. The CHF calculates and records service charges based on usage data and policy rules, enabling accurate billing and financial management in a telecommunication network (e.g., a Fifth Generation (5G) core network).

[0006] The term ‘Session Management Function (SMF)’ used herein in the specification refers to a control-plane network function in the 5G core network responsible for managing and controlling user sessions, including establishment, modification, and termination of data sessions. The SMF interacts with various network functions, including the CHF -BNG, to manage data flows and apply session-related policies.

[0007] The term ‘network services’ used herein in the specification refers to a range of functionalities and capabilities provided by the 5G network infrastructure to support various applications and user requirements. These services include, but are not limited to, enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0008] The term ‘Credit Control Request (CCR)’ used herein in the specification refers to a diameter protocol message used in a real-time charging system to request and update credit or quota for a user session. The CCR is generated by the CHF -BNG and sent to an Online Charging System (OCS) to report user data usage when an event like a session update or termination occurs.

[0009] The term ‘Online Charging System (OCS)’ used herein in the specification refers to a system in the telecommunication network responsible for real-time credit control and billing. The OCS manages user accounts and ensures that services are charged according to a predefined tariff and user usage, using data received from the CHF-BNG via the CCR messages.

[0010] The term ‘Attribute- Value Pair (A VP)’ used herein in the specification refers to a data format used in a diameter protocol message (e.g., the CCR) to capture information such as user data usage and charging details. The AVP is a key-value pair that is used to convey information between network functions.

[0011] The term ‘event request’ used herein in the specification refers to a request, such as a session update or a session terminate request, received by the CHF-BNG from the SMF. These requests include information about the data usage during the session.

[0012] The term ‘flag’ used herein in the specification refers to an indicator to determine if the CHF-BNG has received any data usage or if the data has been utilized from a given quota during the session update or terminate requests. When the flag is set to true, it signifies that data usage has been detected, triggering a process for generating the CCR carrying data usage information, converting the data usage information into AVPs, and sending the AVPs to the OCS. If the flag is set to false, no data usage has been reported, and therefore, no CCR is generated or sent to the OCS.

[0013] The term ‘Sy interface’ as used hereinafter refers to a standardized interface used within the telecommunication network for communication between the Online Charging System (OCS) and a Policy and Charging Rules Function (PCRF). The Sy interface enables a selection and validation of the most appropriate data plan from a prioritized set of plans, facilitating dynamic charging and policy enforcement decisions.

[0014] The term ‘Gy interface’ as used hereinafter refers to a standardized interface used within the telecommunication network for real-time credit control of user sessions. The Gy interface enables sending the CCR to the OCS, facilitating online charging for the user sessions.BACKGROUND

[0015] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0016] In modem telecommunications networks, particularly in Fifth Generation (5G) and next-generation network architectures, accurate billing and charging of services is a critical process. A Charging Function (CHF) is crucial in managing and applying billing rules within the 5G network, ensuring that users are charged appropriately based on their data usage and other service-related metrics. This process is crucial for financial management and the sustainability of the telecommunication services.

[0017] In broadband networks, especially those involving a Broadband Network Gateway (BNG), managing and reporting data usage presents unique challenges. Conventionally, charging mechanisms are well-defined in mobile networks, where an Online Charging System (OCS) receives a real-time data usage reports via interfaces such as Gy and Sy. However, for broadband users that are managed through the BNG, the integration between the CHF and OCS is less efficient, often leading to discrepancies in a data usage reporting and billing.

[0018] Current approaches for the data usage reporting in the broadband networks may not provide real-time updates to the OCS, leading to potential delays in billing, inconsistencies in usage reports, and challenges in maintaining accuraterecords. This gap may result in financial inaccuracies, customer dissatisfaction, and an increased risk of disputes over billing.

[0019] There is, therefore, a need for a system and a method that overcomes the limitations of the prior art.OBJECTIVES OF THE PRESENT DISCLOSURE

[0020] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are listed herein below.

[0021] An objective of the present disclosure is to provide a system and a method for synchronizing data usage in a network.

[0022] Another obj ective of the present disclosure is to enable real-time data usage reporting from a Charging Function -Broadband Network Gateway (CHF- BNG) to an Online Charging System (OCS).

[0023] Another objective of the present disclosure is to ensure that the data usage is consistently synchronized between the CHF-BNG and the OCS, minimizing the risk of discrepancies in billing records.

[0024] Another objective of the present disclosure is to reduce a probability of errors in data usage reporting during a session update and a session termination request.

[0025] Another obj ective of the present disclosure is to utilize the data usage information from the OCS to support business insights and decision-making.

[0026] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY OF THE DISCLOSURE

[0027] In an exemplary embodiment, a method for synchronizing data usage information in a network is described. The method includes receiving, by a first network function, at least one request from a second network function. The at least one request comprises one of a session creation request, a session update request, a session termination request, and a flag. The method includes determining, by the first network function, whether the flag associated with at least one received request is a true flag. The true flag indicates that the at least one received request is at least one of the session update request and the session termination request. The method includes extracting, by the first network function, the data usage information associated with a user session from the at least one of the session update request and the session termination request upon determining that the flag is the true flag. The method includes generating, by the first network function, a Credit Control Request (CCR) message corresponding to the at least one of the session update request and the session termination request based on the extracted data usage information. The generated CCR message comprises the extracted data usage information. The extracted data usage information is encoded into the generated CCR message in a form of one or more Attribute Value Pairs (A VPs). The method includes transmitting, by the first network function, the triggered CCR message to an online charging system (OCS) to synchronize the data usage information between the first network function and the OCS.

[0028] In some embodiments, the first network function comprises a Charging Function -Broadband Network Gateway (CHF-BNG), and the second network function comprises a Session Management Function (SMF).

[0029] In some embodiments, the method further includes deducting, by the first network function, consumed data from a remaining quota of a particular user session. The consumed data is determined based on the extracted data usage information. The method further includes determining, by the first network function, whether the remaining quota is exhausted based on the deduction. Themethod further includes allocating, by the first network function, additional data to the user based on the remaining quota after the deduction. The additional data is allocated by selecting a new data plan from a plurality of data plans placed in a stack based on a predefined priority rule.

[0030] In some embodiments, the method further includes calculating, by the OCS, a real-time charge for the user session based on the data usage information and the allocated additional data.

[0031] In some embodiments, the method further includes generating, by the OCS, a report. The report comprises the data usage information and the calculated real-time charge information for billing and business analytics purposes.

[0032] In some embodiments, each AVP of the one or more AVPs comprise at least one parameter associated with each user session.

[0033] In some embodiments, the at least one parameter comprises one of a unique identifier (ID) associated with each user session, the data usage information for each of the user session, and a timestamp corresponding to the data usage.

[0034] In another exemplary embodiment, a system for synchronizing data usage information in a network is described. The system includes a memory and a processing engine coupled to the memory. The processing engine is configured to execute instructions stored in the memory to receive, by a first network function, at least one request from a second network function. The at least one request comprises one of a session creation request, a session update request, a session termination request, and a flag. The first network function is configured to determine whether the flag associated with the at least one received request is a true flag. The true flag indicates that the at least one received request is at least one of the session update request and the session termination request. The first network function is configured to extract the data usage information associated with a user session from the at least one of the session update request and the session termination request upon determining that the flag is the true flag. The first networkfunction is configured to generate a Credit Control Request (CCR) message corresponding to the at least one of the session update request and the session termination request based on the extracted data usage information. The generated CCR message comprises the extracted data usage information. The extracted data usage information is encoded into the generated CCR message in a form of one or more Attribute Value Pairs (A VPs). The first network function is configured to transmit the triggered CCR message to an online charging system (OCS) to synchronize the data usage information between the first network function and the OCS.

[0035] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for synchronizing data usage information in a network. The method includes receiving, by a first network function, at least one request from a second network function. The at least one request comprises one of a session creation request, a session update request, a session termination request, and a flag. The method includes determining, by the first network function, whether the flag associated with at least one received request is a true flag. The true flag indicates that the at least one received request is at least one of the session update request and the session termination request. The method includes extracting, by the first network function, the data usage information associated with a user session from the at least one of the session update request and the session termination request upon determining that the flag is the true flag. The method includes generating, by the first network function, a Credit Control Request (CCR) message corresponding to the at least one of the session update request and the session termination request based on the extracted data usage information. The generated CCR message comprises the extracted data usage information. The extracted data usage information is encoded into the generated CCR message in a form of one or more Attribute Value Pairs (A VPs). The method includes transmitting, by the first network function, the triggered CCR message to an online charging system (OCS)to synchronize the data usage information between the first network function and the OC.

[0036] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

[0037] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0038] FIG. 1 illustrates an exemplary network architecture of a system for synchronizing data usage information in a network, in accordance with an embodiment of the present disclosure.

[0039] FIG. 2 illustrates a block diagram of the system for synchronizing data usage information in the network, in accordance with an embodiment of the present disclosure.

[0040] FIG. 3 illustrates an exemplary system architecture for synchronizing data usage information in the network, in accordance with an embodiment of the present disclosure.

[0041] FIG. 4 illustrates an exemplary process flow diagram of a method for synchronizing data usage information in the network, in accordance with an embodiment of the present disclosure.

[0042] FIG. 5 illustrates a flow diagram of a method for synchronizing data usage information in the network, in accordance with an embodiment of the present disclosure.

[0043] FIG. 6 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented.

[0044] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 - User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 - Interface(s)208 -Processing Engine210 - Database300 - System architecture302 - Session Management Function (SMF)304 - Charging Function (CHF)- Broadband Network Gateway (BNG)306 - Online Charging System (OCS)400 - Process Flow500 - Method600 - Computer system610 - External storage device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0045] 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. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not befully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0046] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0047] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0048] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0049] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

[0050] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0051] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar termsare used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0052] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0053] In Fifth Generation (5G) network and beyond, the accurate and efficient management of data usage is crucial for maintaining service quality and ensuring proper billing. However, current techniques for updating user data usage, especially in real-time, pose significant challenges that can lead to errors, inconsistencies, and inefficiencies in billing processes.

[0054] One of the primary challenges is managing data usage between a Charging Function -Broadband Network Gateway (CHF-BNG) and an Online Charging System (OCS), particularly in broadband networks (BNGs). In conventional approaches, for broadband users that are managed through the BNG, the data usage updates from a user equipment (UE) are often not relayed to the OCS in real-time, leading to delays in reporting the data usage. This may result in inaccurate billing, where customers or users may be charged incorrectly due to outdated data usage information. Furthermore, any discrepancies in the data usagereporting between the CHF-BGN and the OCS may introduce errors, causing customer dissatisfaction and complicating the reconciliation process.

[0055] Furthermore, the absence of an appropriate mechanism to manage the real-time data usage update can lead to increased error probability. For instance, when data allocation or deduction occurs on the BNG side, the failure to immediately update the OCS can result in discrepancies that affect the accuracy of usage reporting. This issue arises in large-scale networks where multiple sessions and updates are processed concurrently, making it difficult to ensure that all data is correctly captured and reported.

[0056] To address these challenges, the present disclosure provides a method and a system for synchronizing data usage in the network. The disclosed method provides an event based Credit Control Request (CCR) approach, in which the CHF-BNG receives a session update request or a terminate request from a Session Management Function (SMF) and promptly reports the corresponding data usage to the OCS. This real-time update mechanism ensures that the OCS always has an up-to-date and accurate record of the user data, particularly for broadband users, thereby ensuring consistent reporting of data usage, which further reduces the likelihood of errors in billing .

[0057] The present disclosure further discloses a flag-based mechanism within the CHF-BNG to determine whether the data usage should be reported to the OCS. When the flag is set to true, any reported data usage is immediately converted into one or Attribute Value Pairs (A VPs) and sent to the OCS. This approach simplifies the process of updating the OCS, minimizing the risk of errors and enhancing the overall efficiency of data usage management in the network.

[0058] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0059] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 6.

[0060] FIG. 1 illustrates an exemplary network architecture 100 of a system 108 for synchronizing data usage information in a network 106, in accordance with embodiments of the present disclosure.

[0061] As illustrated in FIG. 1, the network architecture 100 may include one or more User Equipments (UEs) 104-1, 104-2, 104-3 104-N associated with one or more users 102-1, 102-2. .. 102 -N in an environment. A person of ordinary skill in the art will understand that one or more users 102-1, 102-2. . . 102- N may be collectively referred to as the users or network operators 102. Similarly, a person of ordinary skill in the art will understand that one or more UEs 104-1, 104-2, 104-3. .. 104-N may be collectively referred to as the UE 104 or the UEs 104. Although only four UE 104 are depicted in FIG. 1, however, any number of the UE 104 may be included without departing from the scope of the ongoing description.

[0062] In an embodiment, the UE 104 may include smart devices operating in a smart environment, for example, loT system. In such an embodiment, the UE 104 may include, but are not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical, a thermal, an electrical, a magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users 102 and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE 104 may include, but not limited to, intelligent, multisensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0063] Additionally, in some embodiments, the UE 104 may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatchcomputer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE 104 may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general -purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE 104 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or an entity such as a touchpad, a touch-enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE 104 may not be restricted to the mentioned devices, and various other devices may be used.

[0064] In an embodiment, the system 108 receives a request (e.g., a session update request, a session termination request and the like) from a session management function (SMF). The system 108 then extracts the data usage information associated with a user session from the session update request and the session termination request. Further, the system 108 encodes the extracted data usage information in a Credit Control Request (CCR) in the form of one or more attribute value pairs (A VPs). This CCR request is then triggered to an online charging system (OCS) for every usage reported by the SMF at the system 108. The system 108 then synchronizes the data usage information, enabling the OCS to always be aware of the data usage associated with the user session. In an aspect, the OCS converts the synchronized data usage information into reports. These reports are helpful for businesses to find meaningful insights. In an embodiment, the UE 104 may communicate with the system 108 through the network 106 to receive various types of data. In an example embodiment, the UE 104 may receive thesereports generated by the OCS. Further, the user 102 may utilize these reports to find meaningful insights and trends beneficial for the business needs.

[0065] In an embodiment, the network 106 may include at least one of a 5th Generation (5G) network, a 6th Generation (6G) network, or the like. The network 106 may enable the UE 104 to communicate with other devices in the network architecture 100 and / or with the system 108. The network 106 may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0066] In an embodiment, the network 106 may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, one or more of, a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, the PSTN, a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0067] In an embodiment, the UE 104 is communicatively coupled with the network 106. The network 106 may receive a connection request from the UE 104. The network 106 may send an acknowledgment of the connection request to the UE 104. The UE 104 may transmit a plurality of signals in response to the connection request.

[0068] Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture 100 may includefewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture 100 may perform functions described as being performed by one or more other components of the network architecture 100.

[0069] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 for synchronizing data usage information in the network 106, in accordance with an embodiment of the present disclosure.

[0070] Referring to FIG. 2, in an embodiment, the system 108 may include one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions.

[0071] In an embodiment, the system 108 may include a processing engine 208 that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine 208. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine 208 may be processorexecutable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine 208 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 engine 208. In such examples, the system 108 may include 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 system and the processing resource. In other examples, the processing engine 208 may be implemented by electronic circuitry. Among othercapabilities, the processing engine 208 may be configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 108. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or nonvolatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.

[0072] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) 206 may facilitate communication through the system 108. The interface(s) 206 may also provide a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the processing engine 208 and a database 210.

[0073] In an embodiment, the processing engine 208 may be implemented by a first network function. In some embodiments, the processing engine 208 is associated with or embedded in the first network function. In an aspect, the first network function is a Charging Function-Broadband Network Gateway (CHF- BNG). The first network function handles the charging control and broadband data handling within the network 106.

[0074] In order to synchronize the data usage information in the network 106, initially, the first network function (i.e., the CHF-BNG) is configured to receive at least one request from a second network function. In an embodiment, the second network function may be a Session Management Function (SMF). The second network function is responsible for efficiently managing user sessions within the network 106. The at least one request comprises one of a session creation request, a session update request, a session termination request, and a flag. In anexample, the first network function may include a plurality of interfaces that are configured to continuously monitor and receive the at least one request from the second network function (i.e., the SMF). Specifically, the plurality of interfaces may be designed to receive and manage the session creation request, the session update request, and the session termination request.

[0075] In an aspect, the session creation request is sent to the first network function to inform the first network function about the initiation of a new user session. The session creation request may typically include essential session parameters such as the user identifier, requested service types, and initial quality of service (QoS) configurations. Upon receiving the session creation request, the first network function may use the session parameters to initialize charging control for the new user session. For instance, the first network function may allocate resources accordingly and establish a baseline for monitoring and managing the user’s data usage throughout the session lifecycle.

[0076] In an aspect, the session update request is sent to the first network function to inform it about any changes or modifications to an active user session. The session update request is a critical event that occurs when there is a change in the active user session between an end user device and the network 106. For instance, the session update request may include information such as updates to the active user session, data usage limits, changes in the quality of service (QoS), or adjustments to other session parameters. The first network function processes this information to ensure that the data usage is accurately tracked and reported and that any modifications are appropriately managed. In an example, when the second network function detects a change in the active user session, such as an increase in data usage, the second network function generates the session update request. Further, the session update request is communicated to the first network function to ensure that the session continues to operate smoothly, and the billing remains accurate.

[0077] In an aspect, the session termination request is sent to the first network function to inform the first network function about the end of the active user session. The session termination request is a crucial event in a lifecycle of the active user session, as it ends the data transmission associated with that session. In an example, the second network function may initiate the session termination request upon detecting one or more conditions, such as voluntary disconnection by the user, session timeout due to inactivity, network-triggered events, including handovers, link failures, or service disruptions.

[0078] In an aspect, the flag is an indicator, typically a Boolean value, that may be included in the at least one request to indicate a particular condition. The flag acts as an indicator or identifier that helps the first network function to determine the nature of the at least one received request.

[0079] In an embodiment, the first network function may be configured to determine whether the flag associated with the at least one received request is a true flag. The true flag indicates that the at least one received request is at least one of the session update request and the session termination request. In an example, the flag may be represented as the Boolean value (e.g., true or false) or a predefined status code. When the flag is set to a true value, it signals to the first network function that the received at least one request contains data usage information that may be used for the data synchronization process. In contrast, a false flag may indicate that the received at least one request is related to the session creation request or another event that does not require data usage synchronization. By evaluating the flag, the first network function can ensure that only relevant data usage events are used for the data synchronization process, which further improves efficiency and ensures real-time synchronization of the charging data.

[0080] In an embodiment, upon determining that the flag is the true flag, the first network function is configured to extract the data usage information associated with a user session from the at least one of the session update request and the session termination request. In an example, the session update request, when received bythe first network function, may contain various types of session-related information, such as session identifiers, quality of service (QoS) parameters, timestamps, and data usage statistics. Upon determining that the flag associated with the session update request is the true flag, the first network function proceeds to extract the data usage information. The data usage information may include data usage fields structured using pre-configured logic, which incorporates the data usage information, for instance, a field stating the volume of data consumed since the last update, a field stating the cumulative data transferred during the active user session, or a field stating the data usage specific to downlink and uplink directions. The first network function may identify these specific data usage fields from within the session update request and recognizes the expected field names or data paths. It then retrieves the corresponding values.

[0081] In another example, the session termination request may also carry multiple session parameters, similar to the session update request. The first network function may extract the data usage information from the session termination request. The data usage information may include the total volume of data consumed during the entire active session, final timestamps, and total active session duration. Then, the first network function may extract the data usage information by parsing the structured fields of the session termination request and mapping them to internal variables that are used for charging and quota updates. This ensures that the complete session usage is accurately captured and reported before the session is closed.

[0082] In an embodiment, the first network function is configured to generate a credit control request (CCR) message corresponding to the at least of the session update request and the session termination request based on the extracted data usage information. The CCR message is typically generated in accordance with a Diameter protocol or a similar signaling protocol, and may include a plurality of fields that provide detailed context about the user's session. In other words, the CCR message is a critical message that includes detailed information about the user data usage, which is vital for charging and billing purposes.

[0083] In an aspect, the CCR message comprises the extracted data usage information. In an example, when the flag associated with the at least one of the session update request and the session termination request is determined to be true, it signifies that the data usage has been detected. In such a scenario, the first network function triggers the process to generate the CCR message that carries the extracted data usage information of the user session. The CCR message is essentially a report that provides the necessary data to update a billing record of the user. Alternatively, if the flag is determined as a false flag, it signifies that no data usage has been reported, and therefore, the first network function does not generate the CCR message.

[0084] In an aspect, the extracted data usage information is encoded into the generated CCR message in a form of one or more Attribute Value Pairs (A VPs). The one or more AVPs are fundamental data structures used in the diameter protocol, which is widely employed in the telecommunication network, such as the network 106 for authentication, authorization, and accounting (AAA) functions. The AVP consists of two key components i.e., an attribute (or identifier) and its corresponding value.

[0085] In an aspect, each AVP of the one or more AVPs comprises at least one parameter associated with the user session. The at least one parameter comprises one of a unique identifier (ID) associated with the user session, the data usage information of the user session, and a timestamp corresponding to the data usage. In a scenario, the first network function receives the session update request from the second network function, and upon determining that the flag associated with the session update request is the true flag, the first network function (CHF- BNG) extracts a data usage value of 5000 KB consumed during the active user session. The user session is identified by a unique Session-ID of "abcl23xyz" and occurred at a timestamp of "2025-04-23Tl l :45:00Z". The extracted data usage information is then encoded into the CCR message using the following AVPs:Session-Id AVP = "abcl23xyz"Used-Service-Unit AVP = “5000 KB”Event-Timestamp AVP = "2025-04-23Tl l:45:00Z

[0086] In an embodiment, the first network function is configured to transmit the generated CCR message to an online charging system (OCS) to synchronize the data usage information between the first network function and the OCS. The synchronization helps in maintaining consistency across the charging and billing systems, preventing discrepancies in user accounts. The OCS is responsible for managing the billing and charging of the users in the telecommunication network, such as the network (106).

[0087] The OCS handles real-time billing and charging for network services. The OCS applies charging rules based on service usage metrics, such as data consumption or call duration, and updates user accounts in real-time. The OCS interfaces with the first network function to obtain accurate data on service usage, allowing the OCS to compute charges and manage user account balances promptly. The OCS also handles payment processing, account adjustments, and billing disputes, ensuring that users are billed accurately and efficiently for the services they consume.

[0088] By receiving the CCR message, the OCS is updated with the most current data usage information, ensuring that the billing is accurate and up-to-date. This real-time communication between the first network function (CHF-BNG) and the OCS is crucial for maintaining the integrity of the billing process, preventing errors, and ensuring that the customers or users are charged correctly for their data usage.

[0089] In an aspect, the first network function is configured to deduct consumed data from a remaining quota of a particular user session. The consumed data is determined based on the extracted data usage information. For example, the first network function receives the session update request, indicating that the user has consumed 1000 KB of data since the last report. The first network functionidentifies the corresponding user session using the session identifier "session789" and retrieves the user’s remaining quota from its internal quota management system, which shows 5000 KB remaining. The first network function then deducts the 1000 KB from the 5000 KB, updating the user's remaining quota to 4000 KB. This updated quota is stored in the system's memory or associated session state, ensuring that further usage is measured against the correct balance.

[0090] In an embodiment, the first network function is configured to determine whether the remaining quota is exhausted based on the deduction. This ensures that users do not exceed their allocated data limits without appropriate charging or reallocation. Upon detecting that the remaining quota is exhausted, the first network function may trigger additional actions such as initiating the allocation of a new data plan, generating a notification to the OCS, or applying predefined policies to manage the user session such as throttling the data speed or suspending the session until further quota is added. This proactive check safeguards against unauthorized data usage and supports real-time quota enforcement for a consistent user experience and accurate billing.

[0091] In an embodiment, upon determining that the remaining quota is exhausted, the first network function is configured to allocate additional data to the user. The additional data is allocated by selecting a new data plan from a plurality of data plans placed in a stack based on a predefined priority rule. The additional data is selected from the stack of the plurality of data plans associated with the user's account. When a session update or termination request is received, and the data usage is deducted from the currently active plan, the first network function (CHF- BNG) automatically evaluates the stack of multiple data plans. Based on predefined priority rules, the first network function selects the next applicable data plan and allocates the corresponding data to the user.

[0092] The plurality of data plans may include various plan types, such as daily plans, booster packs, rollover data, or bundled promotional plans. These plans are arranged in the stack and are prioritized based on criteria such as a plan validityperiod, a remaining data volume, a plan type or a hierarchy (e.g., primary vs. secondary plans), an expiry date proximity, user preferences, or operator-defined policies.

[0093] Upon receiving the session update or termination request and deducting the used data from the currently active plan, the CHF-BNG, i.e., the first network function, evaluates the next available plans in the stack. If the active plan has insufficient quota to serve the current session, the first network function automatically applies the next eligible data plan from the stack based on the predefined priority rules. This ensures seamless continuity of service without requiring user intervention.

[0094] In an exemplary scenario, assume a user has the following stack of data plans: Daily Plan - 100 MB remaining (expires at midnight), Monthly Plan - 2 GB remaining (expires in 20 days), Booster Pack - 500 MB remaining (expires in 5 days). If the session update request reports a data consumption of 150 MB, the first network function deducts 100 MB from the Daily Plan (depleting it), and then automatically switches to the Booster Pack to deduct the remaining 50 MB, based on the priority defined (e.g., use shortest-validity plans first). The updated quota values are stored accordingly, and the active session continues with the updated quota context. This process enables real-time, dynamic quota management, ensuring optimal usage of available plans while complying with operator policies.

[0095] In an embodiment, the processing engine 208 may be implemented by the OCS. In some embodiments, the processing engine 208 is embedded in the OCS. In some embodiments, the first network function, the second network function, and the OCS may be present within the system 108.

[0096] In an embodiment, the OCS is configured to calculate a real-time charge for the user session based on the data usage information and the allocated additional data. The calculation may typically be based on one or more factors, such as volume of data consumed during the session (e.g., in KB, MB, or GB), type of data plan used (e.g., regular plan, booster, promotional), rate per unit data definedin the user's subscribed plan, time of usage (e.g., peak vs. off-peak pricing), applicable discounts or promotional credits, and policy or rating rules configured within the charging system.

[0097] In an example, when the CCR message is received from the first network function, the OCS parses the one or more AVPs to extract the at least one parameter. The OCS then refers to its rating engine, which applies the appropriate tariff model to determine the cost associated with the usage. If additional data was allocated during the session, the OCS identifies the source plan and its respective pricing. After computation, the OCS may perform one or more actions such as deduct the charge from a prepaid balance, accumulate the charge for postpaid billing, and / or update the user account with transaction records and usage logs. This enables real-time, accurate, and transparent charging aligned with the service provider’s billing policies and user entitlements.

[0098] In an embodiment, the OCS is configured to generate a report. The report comprises the usage information and the calculated real-time charge information for billing and business analytics purposes.

[0099] In an example, the generated report may include parameters such as total data consumed per session, timestamp of usage events, plan or tariff details used, applied charges, and remaining quota information.

[0100] The generated report is essential for enabling accurate billing of users. Additionally, the generated report provides valuable insights to service providers for understanding user behavior, usage patterns, and demand trends. This data can support strategic decisions such as optimizing data plans, offering targeted promotions, or planning network capacity upgrades. Furthermore, such detailed usage records enhance transparency for customers, support dispute resolution, and ensure regulatory compliance in markets where telecom billing must meet audit and reporting standards.

[0101] In an embodiment, the system 108 may include a database 210 that stores a wide range of information essential for managing the data usage and billing. The database 210 includes data (e.g., data plan details, details of data usage from a given quota, subscriber information, etc.) that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (208).

[0102] Although FIG. 2 shows exemplary components of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108).

[0103] FIG. 3 illustrates an exemplary system architecture 300 for synchronizing data usage information in the network 106, in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with the FIGs. 1 and 2.

[0104] The system architecture 300 includes an SMF 302 (referred to as the second network function in FIG. 2), a CHF-BNG 304 (referred to as the first network function in FIG.2), and an OCS 306. The SMF 302 is responsible for handling session-related operations for the end user devices in the network 106. In the present FIG. 3, the SMF 302 acts as an initial point of interaction, where the SMF 302 generates at least one request comprising the session creation request, the session update request, or the session terminate request, and the flag based on user activity or network event. These requests contain essential information about the session, such as data usage, session status, or termination details. For example, when the user 102 initiates or terminates the session, the SMF 302 detects this change and sends the corresponding request to the CHF-BNG via a user interface.

[0105] The CHF-BNG 304, upon receiving at least one request and the flag from the SMF, processes these requests to manage the data usage. In an aspect, theCHF-BNG determines whether the flag associated with the at least one received request is a true flag. The true flag indicates that the at least one received request is at least one of the session update request and the session termination request. Upon determining that the flag is the true flag, the CHF-BNG 304 extracts the data usage information associated with a user session from the at least one of the session update request and the session termination request.

[0106] One of the primary roles of the CHF-BNG 304 is to charge and allocate data quota as per data usage by the user and to manage the session for the user. The CHF-BNG 304 detects changes in the data usage and generates the event CCR based on the data usage information and the session update or session terminate requests. The CHF-BNG 304 assesses whether the information needs to be reported to the OCS 306 by checking the flag status (e.g., true flag or false flag) associated with the at least one request. For example, if the SMF 302 sends the session update request indicating that the user has consumed additional data from the given quota, the CHF-BNG 304 may generate the CCR message reflecting this data usage and prepare it for transmission to the OCS 306.

[0107] The OCS 306 is the final destination for the CCR message generated by the CHF-BNG 304. The OCS 306 handles all the charging-related functions within the network 106, ensuring that the data usage is accurately recorded and billed to the user. The OCS 306 processes the CCR message using Gy and Sy interfaces. The Gy and Sy interfaces are standard interfaces used for real-time charging and session management. The Gy interface is specifically used between the CHF-BNG 304 and the OCS. The Gy interface allows the CHF-BNG 304 to communicate with the OCS 306 to handle real-time charging events and queries. Through the Gy interface, the CHF-BNG 304 sends data usage records, session start and stop events, and other relevant information to the OCS 306. The OCS 306 then uses this information to calculate and apply charges in real-time, ensuring that users are billed accurately for their usage of network services. The Gy interface supports dynamic charging scenarios and provides feedback to the CHF-BNG 304 regarding the charging status and any adjustments required. The Sy interface is used forsession management between the SMF 302 and the CHF-BNG 304. The Sy interface facilitates the exchange of session-related information, including session creation, modification, and termination requests. The Sy interface is crucial for synchronizing session management activities with real-time billing requirements, enabling seamless coordination between session handling and financial transactions. Further, the Sy interface allows the OCS 306 to communicate with other network elements, like the Policy Control Function PCF, to enforce policies based on the user subscription and current session status. For example, once the OCS 306 receives the CCR message from the CHF-BNG 304 in the form of AVPs, the OCS 306 updates the user’s account balance and data usage records, ensuring that the billing reflects the most recent data consumption accurately. If the user data usage exceeds a given data plan or quota, the OCS 306 may share this information with an external system (e.g., billing system) to trigger additional charges or notifications to the user associated with the UE 104.

[0108] FIG. 4 illustrates an exemplary process flow diagram 400 of a method for synchronizing data usage information in the network 106, in accordance with an embodiment of the present disclosure. Examples of the telecommunication network may include, a Fourth Generation (4G) network, the 5G network, a Sixth- Generation network (6G) network, and the like. FIG. 4 is explained in conjunction with FIGs. 1, 2, and 3.

[0109] The flow diagram begins at step 402, which initiates the method 400 for synchronizing data usage information within the network 106.

[0110] At step 404, the SMF 302 sends at least one request, i.e., the session update request or session terminate request, to the CHF-BNG 304. The session update request or session terminate request may be triggered for various reasons, such as a change in the session status of a user, modification in data usage, or termination of a user session. For example, if a user exhausts his existing data plan or quota (e.g., exhausts remaining 500 MB of data from their current 1 GB dataplan) or manually disconnects from the network after reaching his data limit, the SMF 302 sends the session terminate request to the CHF-BNG 304.

[0111] At step 406, the CHF-BNG 304 receives the session update or terminate request from the SMF 302. The CHF-BNG 304 is responsible for handling these requests and determining the necessary actions, such as updating the data usage and updating or terminating the ongoing session. For example, if the session update request indicates additional data usage by the user, such as when a user streams an additional 500 MB of video content on top of their current usage, the CHF-BNG 304 processes this information by updating the user’s session to reflect the extra 500 MB of data consumed. For example, if the user had previously consumed 1 GB of data, the CHF-BNG 304 now updates the total usage to 1.5 GB. This ensures that the user's total data usage for the session is accurately tracked and reported for billing.

[0112] At step 408, the CHF-BNG 304 checks the flag associated with the session update or session terminate request. This flag acts as a decision-making criterion to determine whether or not to proceed with generating the Credit Control Request (CCR). The flag is either a true flag or a false flag.

[0113] The true flag indicates that the data usage information is received by the CHF-BNG 304 during the session update or session terminate request and needs to be reported to the OCS 306. This could be the case when there is a significant change in the data usage or any changes in the session that must be logged for billing purposes. The false flag implies that the CHF-BNG 304 receives no data usage information during the session update or session terminate request. Therefore, there is no need to report the data usage to the OCS 306, possibly because there has been no significant change in the user’s data usage, or the data has already been accounted for in a previous transaction. In this case, a check may be performed iteratively for every event request to determine if the CHF-BNG 304 receives any data usage information. If there is no reporting of the data usage information andthe flag remains a false flag for a predefined time interval, then in such a scenario, the method 400 ends at step 414.

[0114] If the flag is the true flag, the method 400 proceeds to step 410, where the CHF-BNG 304 manages the data usage by generating the event Credit Control Request (CCR) (i.e., the CCR message) and sends it to the OCS 306 based on the session update or session terminate requests. In particular, when the CHF- BNG 304 generates the event CCR, the CHF-BNG 304 assesses the data consumption and deducts the reported data usage from the remaining quota allocated to the user. For example, if the user had a remaining quota of 5 GB and the session update indicates the use of an additional 1 GB, the CHF-BNG 304 would deduct this from the available quota, leaving the user with 4 GB of data. After managing the current data usage, the CHF-BNG 304 may also allocate a new quota or data. This updated data usage information is present in the CCR, in the form of the one or more AVPs. One or more AVPs are sent to the OCS 306 to ensure the user’s account is updated with the latest usage information. This ensures that the user’s billing is accurate and up-to-date.

[0115] At step 412, the OCS 306 receives the event CCR sent from the CHF-BNG 304. The purpose of this step is to synchronize the data usage between the CHF-BNG 304 and the OCS 306. By sending the CCR to the OCS 306, the CHF-BNG 306 ensures that the OCS 306 has the up-to-date data usage information, which is essential for accurate billing and usage tracking. The synchronization helps in maintaining consistency across the charging and billing systems, preventing discrepancies in user accounts. In particular, the OCS 306 processes the event CCR by extracting the AVPs and updating the user’s account based on the reported data usage. This is to ensure that the billing system reflects the correct data consumption for the session, and any charges are accurately applied. For example, if the event CCR reports that the user has exceeded their data quota (e.g., 1 day of data quota, 1 month of data quota, or 1 year of data quota), the billing system may use this information from the OCS 306 to adjust the billing, accordingly, possibly applying additional charges for that user. Finally, the method 400 ends at step 414. Themethod 400 ensures that the data usage is correctly managed and reported, thereby maintaining consistency and accuracy in billing within the telecommunication network.

[0116] FIG. 5 illustrates a flow diagram of a method 500 for synchronizing data usage information in the network 106, in accordance with embodiments of the present disclosure. The steps of the method 500 of the present disclosure will now be explained with reference to the components of the system 108 as depicted in FIGs. 2 and 3.

[0117] At step 502, the method 500 includes receiving, by a first network function, at least one request from a second network function. The at least one request comprises one of a session creation request, a session update request, a session termination request, and a flag. The first network function comprises a Charging Function-Broadband Network Gateway (CHF-BNG) 304, and the second network function comprises a Session Management Function (SMF) 302.

[0118] At step 504, the method 500 includes determining, by the first network function, whether the flag associated with the at least one received request is a true flag. The true flag indicates that the at least one received request is at least one of the session update request and the session termination request.

[0119] At step 506, the method includes extracting, by the first network function, the data usage information associated with a user session from the at least one of the session update request and the session termination request, upon determining that the flag is the true flag.

[0120] At step 508, the method 500 includes generating, by the first network function, a Credit Control Request (CCR) message corresponding to the at least one of the session update request and the session termination request based on the extracted data usage information. The generated CCR message comprises the extracted data usage information. The extracted data usage information is encoded into the generated CCR message in the form of one or more Attribute Value Pairs(A VPs). In an aspect, each AVP of the one or more AVPs comprises at least one parameter associated with each user session. The at least one parameter comprises one of a unique identifier (ID) associated with each user session, the data usage information for each of the user session, and a timestamp corresponding to the data usage.

[0121] At step 510, the method 500 includes transmitting, by the first network function, the triggered CCR message to an online charging system (OCS) 306 to synchronize the data usage information between the first network function and the OCS.

[0122] In an aspect, the method 500 includes deducting, by the first network function, consumed data from the remaining quota of a particular user session. The consumed data is determined based on the extracted data usage information. Further, the method 500 includes allocating, by the first network function, additional data to the user based on the remaining quota after the deduction. The additional data is allocated by selecting a new data plan from a plurality of data plans placed in a stack based on a predefined priority rule.

[0123] In an aspect, the method 500 includes calculating, by the OCS, a real-time charge for the user session based on the data usage information and the allocated additional data. Further, the method 500 includes generating, by the OCS, a report. The report comprises the data usage information and the calculated realtime charge information for billing and business analytics purposes

[0124] FIG. 6 illustrates an exemplary computer system 600 in which or with which embodiments of the present disclosure may be implemented.

[0125] As shown in FIG. 6, the computer system 600 may include an external storage device 610, a bus 620, a main memory 630, a read-only memory 640, a mass storage device 650, communication port(s) 660, and a processor 670. A person skilled in the art will appreciate that the computer system 600 may include more than one processor and communication ports. The processor 670 may includevarious modules associated with embodiments of the present disclosure. The communication port(s) 660 may be any of an RS-232 port for use with a modembased dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) 660 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 600 connects. The main memory 630 may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 640 may be any static storage device(s) including, but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor 670. The mass storage device 650 may be any current or future mass storage solution, which may be used to store information and / or instructions.

[0126] The bus 620 communicatively couples the processor 670 with the other memory, storage, and communication blocks. The bus 620 can be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCLX) bus, Small Computer System Interface (SCSI), universal serial bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 670 to the computer system 600.

[0127] Optionally, operator and administrative interfaces, e.g. a display, keyboard, and a cursor control device, may also be coupled to the bus 620 to support direct operator interaction with the computer system 600. Other operator and administrative interfaces may be provided through network connections connected through the communication port(s) 660. In no way should the aforementioned exemplary computer system 600 limit the scope of the present disclosure.

[0128] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined bythe claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0129] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0130] The present disclosure provides a technical advancement over conventional charging architectures by shifting the responsibility of Credit Control Request (CCR) message generation from traditionally centralized functions such as a Session Management Function (SMF) or a User Plane Function (UPF) to a decentralized and session-aware function, namely the Charging Function - Broadband Network Gateway (CHF-BNG). In existing implementations, the SMF or UPF typically initiates CCR messages to report data usage to the Online Charging System (OCS). However, such approaches may introduce latency and desynchronization in the reporting and processing of user data usage, thereby affecting the accuracy and timeliness of charging operations.

[0131] The disclosed invention addresses these limitations by empowering the CHF-BNG to autonomously generate CCR messages based on real-time session activity. This is achieved through the implementation of a flag-based decisionmechanism, wherein each received request from the SMF, such as a session update or termination, is accompanied by a flag. Upon determining that the flag is true, indicating that the received request corresponds to either a session update or a session termination, the CHF-BNG is configured to extract the reported data usage information and encode it into a CCR message using one or more Attribute Value Pairs (A VPs). The CCR is then transmitted to the OCS, enabling accurate, consistent, and near real-time synchronization of data usage and billing records. This architecture eliminates the reliance on SMF or UPF for triggering CCRs, thereby reducing potential bottlenecks and improving the responsiveness and scalability of the charging framework. Consequently, the disclosed system demonstrates a clear technical improvement over prior art by achieving enhanced data integrity, improved session-level granularity in charging, and reduced latency in billing updates, contributing to a more efficient and robust charging infrastructure.

[0132] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.ADVANTAGES OF THE PRESENT DISCLOSURE

[0133] As is evident from the above, the present disclosure provides a technically advanced solution by providing an improved method and system for synchronizing data usage information in a network.

[0134] The present disclosure provides an efficient approach for updating the OCS with real-time data usage. The implementation of an event based CCRapproach allows the CHF-BNG to update the data usage in real-time as updates are received from the SMF.

[0135] The present disclosure simplifies communication between the CHF- BNG and OCS, ensuring that the OCS is continuously updated with the latest user session data usage. This enables the OCS to maintain an end-to-end accurate record of data usage, leading to more precise billing and resource management.

[0136] The present disclosure provides a system and a method that enables the update of data usage in the OCS. By updating the data usage, a probability of errors in the data usage is minimized. Every data allocation and deduction on the BNG side triggers an event CCR, which is sent to the OCS in the form of Attribute Value Pairs (A VPs). This ensures that data usage is accurately recorded, reducing the likelihood of discrepancies.

[0137] The present disclosure provides a consistent and reliable data usage reporting of sessions and the users to support business operations. The data usage recorded by the OCS may be used by analysts and data scientists to extract meaningful insights that are beneficial for business decision-making and strategy development.

[0138] The present disclosure provides enhanced flexibility by allowing the CHF-BNG to independently handle CCR generation without relying on the SMF or UPF. This reduces dependency on other network functions and improves system scalability, enabling easier integration and maintenance in complex network architectures.

[0139] The present disclosure enables improved responsiveness during dynamic network conditions. By allowing CCR generation to occur directly at the CHF-BNG based on real-time triggers, the system can promptly reflect changes in data consumption, which is essential for enforcing policy controls, preventing quota exhaustion, and enhancing user experience.

Claims

CLAIMSWe claim:

1. A method (500) for synchronizing data usage information in a network (106), the method (500) comprising: receiving (502), by a first network function, at least one request from a second network function, wherein the at least one request comprises one of a session creation request, a session update request, a session termination request, and a flag; determining (504), by the first network function, whether the flag associated with the at least one received request is a true flag, wherein the true flag indicates that the at least one received request is at least one of the session update request and the session termination request; upon determining that the flag is the true flag, extracting (506), by the first network function, the data usage information associated with a user session from the at least one of the session update request and the session termination request; generating (508), by the first network function, a Credit Control Request (CCR) message corresponding to the at least one of the session update request and the session termination request based on the extracted data usage information, wherein the generated CCR message comprises the extracted data usage information, and wherein the extracted data usage information is encoded into the generated CCR message in a form of one or more Attribute Value Pairs (A VPs); and transmitting (510), by the first network function, the generated CCR message to an online charging system (OCS) (306) to synchronize the data usage information between the first network function and the OCS (306).

2. The method (500) as claimed in claim 1, wherein the first network function comprises a Charging Function-Broadband Network Gateway (CHF-BNG) (304),and wherein the second network function comprises a Session Management Function (SMF) (302).

3. The method (500) as claimed in claim 1, comprising: deducting, by the first network function, consumed data from a remaining quota of the user session, wherein the consumed data is determined based on the extracted data usage information; determining, by the first network function, whether the remaining quota is exhausted based on the deduction; and upon determining that the remaining quota is exhausted, allocating, by the first network function, additional data to a user, wherein the additional data is allocated by selecting a new data plan from a plurality of data plans placed in a stack based on a predefined priority rule.

4. The method (500) as claimed in claim 3, comprising: calculating, by the OCS (306), a real-time charge for the user session based on the data usage information and the allocated additional data.

5. The method (500) as claimed in claim 4, comprising: generating, by the OCS (306), a report, wherein the report comprises the data usage information, and the calculated real-time charge information for billing and business analytics purposes.

6. The method (500) as claimed in claim 1, wherein each AVP of the one or more AVPs comprises at least one parameter associated with each user session.

7. The method (500) as claimed in claim 6, wherein the at least one parameter comprises one of a unique identifier (ID) associated with each user session, the data usage information for each of the user session, and a timestamp corresponding to the data usage.

8. A system (108) for synchronizing data usage information in a network (106), the system (108) comprising: a memory (204); a processing engine (208) coupled to the memory (204) and is configured to execute instructions stored in the memory (204) to: receive, by a first network function, at least one request from a second network function, wherein the at least one request comprises one of a session creation request, a session update request, a session termination request, and a flag; determine, by the first network function, whether the flag associated with the at least one received request is a true flag, wherein the true flag indicates that the at least one received request is at least one of the session update request and the session termination request; upon determining that the flag is the true flag, extract, by the first network function, the data usage information associated with a user session from the at least one of the session update request and the session termination request; generate, by the first network function, a Credit Control Request (CCR) message corresponding to the at least one of the session update request and the session termination request based on the extracted data usage information, wherein the generated CCR message comprises the extracted data usage information, and wherein the extracted data usage information is encoded into the generated CCR message in a form of one or more Attribute Value Pairs (A VPs); and transmit, by the first network function, the generated CCR message to an online charging system (OCS) (306) to synchronize the data usage information between the first network function and the OCS (306).

9. The system (108) as claimed in claim 8, wherein the first network function comprises a Charging Function-Broadband Network Gateway (CHF-BNG) (304),and wherein the second network function comprises a Session Management Function (SMF) (302).

10. The system (108) as claimed in claim 8, wherein the processing engine is configured to: deduct, by the first network function, consumed data from a remaining quota of the user session, wherein the consumed data is determined based on the extracted data usage information; determine, by the first network function, whether the remaining quota is exhausted based on the deduction; and upon determining that the remaining quota is exhausted, allocate, by the first network function, additional data to a user, wherein the additional data is allocated by selecting a new data plan from a plurality of data plans placed in a stack based on a predefined priority rule.

11. The system (108) as claimed in claim 10, wherein the processing engine is configured to: calculate, by the OCS (306), a real-time charge for the user session based on the data usage information and the allocated additional data.

12. The system (108) as claimed in claim 11, wherein the processing engine is configured to: generate, by the OCS (306), a report, wherein the report comprises the data usage information, and the calculated real-time charge information for billing and business analytics purposes.

13. The system (108) as claimed in claim 8, wherein each AVP of the one or more AVPs comprise at least one parameter associated with each user session.

14. The system (108) as claimed in claim 13, wherein the at least one parameter comprises one of a unique identifier (ID) associated with each user session, the data usage information for each of the user session, and a timestamp corresponding to the data usage.

15. A computer program product comprising a non -transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for synchronizing data usage information in a network (106), the method (500) comprising: receiving (502), by a first network function, at least one request from a second network function, wherein the at least one request comprises one of a session creation request, a session update request, a session termination request, and a flag; determining (504), by the first network function, whether the flag associated with the at least one received request is a true flag, wherein the true flag indicates that the at least one received request is at least one of the session update request and the session termination request; upon determining that the flag is the true flag, extracting (506), by the first network function, the data usage information associated with a user session from the at least one of the session update request and the session termination request; generating (508), by the first network function, a Credit Control Request (CCR) message corresponding to the at least one of the session update request and the session termination request based on the extracted data usage information, wherein the generated CCR message comprises the extracted data usage information, and wherein the extracted data usage information is encoded into the generated CCR message in a form of one or more Attribute Value Pairs (A VPs); andtransmitting (510), by the first network function, the generated CCR message to an online charging system (OCS) (306) to synchronize the data usage information between the first network function and the OCS (306).

Images