Method and system for providing subscriber identity information for billing of service usages

Abstract

The present disclosure relates to a method and a system for providing subscriber identity information for billing of service usages The disclosure encompasses retrieving through policy control function (PCF) [122], Global Public Subscriber Identity (GPSI) data from subscriber profile repository (SPR) database [3042]; transmitting through the PCF [122], to Session Management Function (SMF) [108], the retrieved GPSI data; adding through the SMF [108], the retrieved GPSI data for interacting with converged charging function (CHF) [132]; converting through the CHF [132], Hypertext Transfer Protocol (HTTP) request to diameter request along with the retrieved GPSI data; transmitting through the CHF [132], the diameter request to an online charging system (OCS) [310]; and responding through the CHF [132], an OCS response in response to the diameter request to at least one of: the SMF [108] and the PCF [122] for billing of service usages.

Description

METHOD AND SYSTEM FOR PROVIDING SUBSCRIBER IDENTITY INFORMATION FOR BILLING OF SERVICE USAGESFIELD OF THE DISCLOSURE

[0001] Embodiments of the present disclosure generally relate to the field of wireless communication system. More particularly, embodiments of the present disclosure relate to method and system providing subscriber identity information for billing of service usages.BACKGROUND

[0002] 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.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on antilog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] As the wireless communication technology has evolved to a great extent, the number of users / subscribers of the wireless networks has also increased to a great extent and it is important for the wireless networks to provide better and smooth services to its subscribers. In the 5G communication system, there is provided a plurality of network functions (NFs), for example an Access and Mobility Management Function (AMF), session management function (SMF), Policycontrol function (PCF), Converged Charging Function (CHF) and the like. One or more of the aforementioned NFs communicates with each other, to implement multiple activities on the 5G communication system. For example, CHF is one of the key network functions, which supports charging or billing services for user consumption of services.

[0005] Hence, in view of these and other existing limitations, there exists an imperative need in the art to provide an efficient system and method for providing subscriber identity information for charging or billing of service usages of a subscriber / user.OBJECTS OF THE DISCLOSURE

[0006] This section is provided to introduce certain objects and aspects of the present invention in a simplified form that are further described below in the description. In order to overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present invention is to substantially reduce the limitations and drawbacks of the prior arts as described hereinabove.

[0007] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0008] It is another object of the present disclosure to provide a system and a method for providing subscriber identity information for billing of service usages.

[0009] It is another object of the present disclosure to provide a system and a method for enabling efficiency to network and subscriber management by accurately creating connections.

[0010] It is yet another object of the present disclosure to provide an optimized resource allocation by ensuring a smoother network operation and better subscriber experiences.

[0011] It is another object of the present disclosure to simplify the billing and reconciliation processes thereby enabling telecom operators to accurately and efficiently bill their subscribers while maintaining transparency and reliability in their financial transactions.SUMMARY

[0012] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0013] An aspect of the present disclosure may relate to a method for providing subscriber identity information for billing of service charges. The method comprises retrieving, by a retrieving unit, through a policy control function (PCF), a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database. Thereafter, the retrieving unit sends the retrieved GPSI data to a transceiver unit. The method further comprises transmitting, by the transceiver unit through the PCF, to a Session Management Function (SMF), the retrieved GPSI data as an SMF response. The method further comprises adding, by a processing unit through the SMF, the retrieved GPSI data for interacting with a converged charging function (CHF). The method further comprises converting, by the processing unit through the CHF, a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data. The method further comprises transmitting, by the transceiver unit through the CHF, the diameter request to an online charging system (OCS). The method further comprises responding, by the processing unit through the CHF, an OCS response in response to the diameter request to at least one of the SMF and the PCF for billing of service usages.

[0014] In an exemplary aspect of the present disclosure, the GPSI data comprises at least one of a user identification information, a media access control-identifier (MAC -ID), and a network identifier.

[0015] In an implementation of the present disclosure, adding the retrieved GPSI data for interacting with the converged charging function (CHF), further comprises sending, by the processing unit, a request, comprising a dedicated field for the GPSI data, to the CHF.

[0016] In an implementation of the present disclosure, the method comprises storing, by a storage unit through the CHF, the GPSI data in a call data records (CDR).

[0017] In an implementation of the present disclosure, the method comprises performing, by the processing unit through the OCS a quota management and sending response back to the CHF.

[0018] Another aspect of the present disclosure may relate to a system for providing subscriber identity information for billing of service usages. The system comprises a retrieving unitconfigured to retrieve, through a policy control function (PCF), a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database. The system further comprises a transceiver unit configured to transmit, through the PCF, to a Session Management Function (SMF), the retrieved GPSI data. The system further comprises a processing unit configured to add, through the SMF, the retrieved GPSI data for interacting with a converged charging function (CHF). The processing unit is further configured to convert, through the CHF, a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data. The transceiver unit of the system is further configured to transmit, through the CHF, the diameter request to an online charging system (OCS). The processing unit of the system is further configured to respond, through the CHF, an OCS response in response to the diameter request to at least one of the SMF and the PCF for billing of service usages.

[0019] Another aspect of the present disclosure may relate to a non-transitory computer-readable storage medium storing instruction for providing subscriber identity information for billing of service usages, the storage medium comprising executable code which, when executed by one or more units of a system, causes a retrieving unit, of the system, to retrieve, through a policy control function (PCF), a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database. Further, the executable code which, when executed causes a transceiver unit, of the system, to transmit, through the PCF, to a Session Management Function (SMF), the retrieved GPSI data. Further, the executable code which, when executed causes a processing unit, of the system, to add, through the SMF, the retrieved GPSI data for interacting with a converged charging function (CHF). Further, the executable code which, when executed causes the processing unit to convert, through the CHF, a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data. Further, the executable code which, when executed causes the transceiver unit to transmit, through the CHF, the diameter request to an online charging system (OCS). Further, the executable code which, when executed causes the processing unit to respond, through the CHF, an OCS response in response to the diameter request to at least one of the SMF and the PCF for billing of service usages.DESCRIPTION OF DRAWINGS

[0020] 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 thedrawings 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 disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0021] FIG.1 illustrates an exemplary block diagram representation of a 5th generation core (5GC) network architecture, in accordance with an exemplary implementation.

[0022] FIG.2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0023] FIG.3 illustrates an exemplary block diagram of a system for providing subscriber identity information for billing of service usages, in accordance with exemplary implementations of the present disclosure.

[0024] FIG.4 illustrates an exemplary method flow diagram for providing subscriber identity information for billing of service usages, in accordance with the exemplary embodiments of the present disclosure.

[0025] FIG.5 illustrates another exemplary flow chart depicting the process of for providing subscriber identity information for billing of service usages, in accordance with the exemplary embodiments of the present disclosure.

[0026] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0027] 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 any ofthe problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully 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.

[0028] 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.

[0029] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the disclosure. These terms are not intended to limit the scope of the disclosure 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 disclosure 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 disclosure as defined herein.

[0030] 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.

[0031] 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 operationsmay be re-arranged. A process is terminated when its operations are completed but could have additional steps that may not be included in figures.

[0032] 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.

[0033] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and / or transmitting one or parameters, performing function / s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0034] Further, the user device and / or a system as described herein to implement technical features as disclosed in the present disclosure may also comprise a “processor” or “processing unit”, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processor (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or anyother functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.

[0036] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0037] As used herein “interface” or “user interface” refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0038] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0039] As used herein the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units / components within the system and / or connected with the system.

[0040] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing methods and systems, that integrates GPSI (Global Public Subscriber Identity) into call data records (CDRs) within the communication network. The present disclosure provides a solution, in which Converged Charging Function (CHF) integrates GPSI / Mobile Station International Subscriber Directory Number (MSISDN) into CDRs for billing and reconciliation purposes. The present disclosure also provides a solution, in which the CHF provides GPSI / MSISDN in CDR to a mediation and Online Charging Systems (OCS), by Session Management Function (SMF), with the help of Policy Control Function (PCF) and a Subscriber Profile Repository (SPR) database. The present disclosure thus provides a simplified and enhanced billing and reconciliation process. By seamlessly incorporating GPSI into CDRs, the accurate subscriber data may readily be available for billing purposes, leading to more precise and transparent financial transactions. The present disclosure improves the efficiency of the network along with setting a solution by addressing a crucial aspect of subscriber management in an optimized and effective manner.

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

[0042] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture

[0100] , in accordance with an exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

[0104] , an access and mobility management function (AMF)

[0106] , a Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , an Authentication Server Function (AUSF)

[0112] , a Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] , a Network Slice Selection Function (NSSF)

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a Policy Control Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function (AF)

[0126] , a User Plane Function (UPF)

[0128] , a data network (DN)

[0130] , and a converged charging function (CHF)

[0132] , wherein all the components are assumed to beconnected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0043] The Radio Access Network (RAN)

[0104] is the part of a mobile telecommunications system that connects the user equipment (UE)

[0102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.

[0044] The Access and Mobility Management Function (AMF)

[0106] is the 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.

[0045] The Session Management Function (SMF)

[0108] is the 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF)

[0128] for data forwarding and handles IP address allocation and Quality of Service (QoS) enforcement. Further, the SMF

[0108] facilitates enforcement of session management related policy decisions from the PCF

[0122] ,

[0046] The Service Communication Proxy (SCP)

[0110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.

[0047] The Authentication Server Function (AUSF)

[0112] is the network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.

[0048] The Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] is the network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.

[0049] The Network Slice Selection Function (NSSF)

[0116] is the network function responsible for selecting the appropriate network slice for the UE based on factors such as subscription, requested services, and network policies.

[0050] The Network Exposure Function (NEF)

[0118] is the network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0051] The Network Repository Function (NRF)

[0120] is the network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.

[0052] The Policy Control Function (PCF)

[0122] enables efficient policy control and management, facilitating network behaviour control, network slicing, user equipment (UE) activities, and communication with other 5G core network functions. PCF is responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. The PCF is responsible for policy control decisions and flow-based charging control functionalities.

[0053] The Unified Data Management (UDM)

[0124] is the network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0054] The Application Function (AF)

[0126] is the network function that represents external applications interfacing with the 5G core network to access network capabilities and services. In an exemplary implementation, the application function (AF)

[0126] as shown in FIG. 1, resembles an application server that can interact with the other control-plane NFs. AF(s)

[0126] can exist for different application services and can be owned by the network operator or by trusted third parties. For instance, the AF

[0126] of an over-the-top application provider can influence routing, steering its traffic towards its external edge servers. For services considered to be trusted by the operator, the AF

[0126] can access Network Function(s) (NF) directly whereas untrusted or third-party AF(s)

[0126] would access the Network Functions through the NEF

[0118] ,

[0055] The User Plane Function (UPF)

[0128] is the network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0056] The Data Network (DN)

[0130] refers to a network that provides data services to user equipment (UE)

[0102] in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.

[0057] The 5GC network architecture also comprises a plurality of interfaces for connecting the network functions with a network entity for performing the network functions. The network is designed as an interconnected system of Network Functions (NFs) [also known as fifth generation communication network (5GCN) network function NF)] that communicate through the one or more interfaces (i.e., service-based interfaces or reference point interfaces). The Network Functions (NF(s)) within the 5G control plane will use service-based interfaces for their interactions. The user plane function (UPF)

[0128] , and radio interactions shall use the reference point interfaces. Each NF exposes specific functionality and provides services to other NFs. Therefore, any communication or routing between NFs or between the network nodes and NFs takes place through these interfaces. Interfaces are self-contained software modules that are reusable independently of each other and can be thought of as micro services. Further, as shown in the FIG. 1, the following service-based interfaces are defined:Namf: Service-based interface exhibited by AMF

[0106] , Nsmf: Service-based interface exhibited by SMF

[0108] , Nnef: Service-based interface exhibited by NEF

[0118] , Npcf: Service-based interface exhibited by PCF

[0122] , Nudm: Service-based interface exhibited by UDM

[0124] , Naf: Service-based interface exhibited by AF

[0126] , Nchf: Service-based interface exhibited by CHF

[0132] , Nnrf: Service-based interface exhibited by NRF

[0120] , Nnssf: Service-based interface exhibited by NSSF

[0116] , Nausf: Service-based interface exhibited by AUSF

[0112] , Nnssaaf: Service-based interface exhibited by NSSAAF

[0114] , Nlmf: Service-based interface exhibited by LMF

[0144] Nscp: Service-based interface exhibited by SCP

[0110] ,

[0058] Further, the 5G System Architecture as shown in FIG. 1, contains the following reference points:N1 : Reference point between the UE

[0102] and the AMF

[0106] , N2: Reference point between the RAN

[0104] and the AMF

[0106] , N3: Reference point between the RAN

[0104] and the UPF

[0128] , N4: Reference point between the SMF

[0108] and the UPF

[0128] , N6: Reference point between the UPF

[0128] and a Data Network.

[0059] The present disclosure can be implemented on a computing device

[0200] as shown in FIG. 2. The computing device

[0200] implements the present disclosure in accordance with the 5G communication network architecture

[0100] (as shown in FIG. 1). FIG. 2 illustrates an exemplary block diagram of the computing device

[0200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device

[0200] may also implement a method

[0400] for providing subscriber identity information for billing of service usages in a communication network utilising the system

[0300] , In another implementation, the computing device

[0200] itself implements the method for providing subscriber identity information for billing of service usages using one or more units configured within the computing device

[0200] , wherein said one or more units can implement the features as disclosed in the present disclosure.

[0060] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general-purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] , The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] ,

[0061] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] , Another type of user input device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] ,and for controlling cursor movement on the display

[0212] , The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0062] The computing device

[0200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and / or program logic which in combination with the computing device

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] , Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] , Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

[0204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0063] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] , The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] , For example, the communication interface

[0218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface

[0218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

[0218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0064] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] , In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , the local network

[0222] , a host

[0224] and the communication interface

[0218] , The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0065] The present disclosure is implemented by the system

[0300] (as shown in FIG. 3). The system

[0300] may be implemented using the computing device

[0200] (as shown in FIG. 2). In an implementation, the computing device

[0200] may be connected to the system

[0300] to perform the present disclosure.

[0066] Referring to FIG. 3, an exemplary block diagram of the system

[0300] for providing subscriber identity information for billing of service usages in a communication network, is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0300] comprises at least one converged charging function (CHF)

[0132] ; at least one policy control function (PCF)

[0122] , and at least one online charging system (OCS)

[0310] , The PCF

[0122] further comprises at least one retrieving unit

[0302] ; at least one storage unit

[0304] ; at least one transceiver unit

[0306] ; and at least one processing unit

[0308] , The at least one storage unit

[0304] further comprises a subscriber profile repository (SPR) database

[3042] Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in the FIG.3, all units shown within the system

[0300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such number of said units, as required to implement the features of the present disclosure. In an implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity. In an implementation a process

[0500] (as shown in FIG. 5) is performed by the system

[0300] ,

[0067] The system

[0300] is configured for providing subscriber identity information for billing of service usages in the communication network, with the help of the interconnection between the components / units of the system

[0300] ,

[0068] The retrieving unit

[0302] of the system

[0300] is configured to retrieve, through a policy control function (PCF)

[0122] , a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database

[3042] , The GPSI is a number that uniquely identifies every user / subscriber of the communication network. It is stored as a 64-bit field and is sent by the user device to the communication network.

[0069] Upon retrieval of the GPSI data from the SPR database

[3042] , the transceiver unit

[0306] transmits, through the PCF

[0122] , to a Session Management Function (SMF)

[0108] , the retrieved GPSI data.

[0070] Thereafter, the processing unit

[0308] adds, through the SMF

[0108] , the retrieved GPSI data for interacting with a converged charging function (CHF)

[0132] , The processing unit

[0308] is configured to convert, through the CHF

[0132] , a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data. The HTTP2 (modified form of HTTP) offers weighted prioritization that helps in deciding which network resources will load first, every time. In HTTP2 (as used in the present disclosure), when a client makes a request for a webpage, the server sends several streams of data to the client at once, instead of sending one thing after another. The diameter request here refers a next-generation industry-standard protocol used to exchange authentication, authorization, and accounting (AAA) information in Long-Term Evolution (LTE) and IP Multimedia Systems (IMS) networks. The diameter request is designed to manage network access, resource usage, and billing more effectively than its predecessor, RADIUS protocol.

[0071] The diameter request may include one or more features as mentioned below:1. Command Code: It specifies the type of request (e.g., for user authentication, service authorization, or accounting).2. Session ID: This is a unique identifier which is associated with a particular session, allowing the network operators to track interactions.3. AVPs (Attribute- Value Pairs): These are flexible data structures used to carry various parameters, such as user identity, service details, and additional data like GPSI (Global Public Subscriber Identity).4. Transport Protocol: This refers to TCP or SCTP, thereby providing reliable and ordered delivery of messages.

[0072] The CHF

[0132] (as explained in FIG. 1) is a network function (NF) in a 5G network for managing online charging for a plurality of services (such as voice call service, video streaming service, etc.) used by subscribers. Further, the PCF

[0122] (as explained in FIG. 1) is a NF responsible for policy enforcement and quality of service (QoS) control to effectively allocate / manage one or more resources of the network during the session. A policy counter is a mechanism within the CHF

[0132] to track spending applicable to a subscriber. These policy counters must be available in the CHF

[0132] prior to their use by other network functions, such as PCF. The CHF

[0132] stores the policy counter information against the subscriber pricing plan and notifies the PCF

[0122] whenever the subscriber breaches the policy thresholds based on usage consumption.

[0073] After conversion of the HTTP request to the diameter request, the transceiver unit

[0306] transmits, through the CHF

[0132] , the diameter request to an online charging system (OCS)

[0310] ,The Online Charging System (OCS)

[0310] is a network function connected in the 5G network system that manages the real-time charging and billing of services for subscribers, manages all the transactions within the system, including the subscriber's account balance and charges. The OCS

[0310] enables operators to ensure accurate billing for services by implementing advanced policy rules, enforcing credit limits, accessing advanced analytics, and more. The OCS

[0310] is a cloudnative platform that supports charging across multiple generations of telecom networks. This is achieved by providing multi -protocol support for integration. The OCS

[0310] supports charging customers for their usage based on the device they use. A single plan or bucket may have tariffs for multiple devices as well as the option to have tariffs for device / s or default tariffs. It enables duration-based charging for LTE, Wi-Fi, and FTTH services to support non-monetary entitlements in the form of seconds, minutes, or hours.

[0074] Then, the processing unit

[0308] responds, through the CHF

[0132] , an OCS response in response to the diameter request to at least one of the SMF

[0108] and the PCF

[0122] for billing of service usages.

[0075] In an implementation of the present disclosure, the GPSI data comprises at least one of: a user identification information, a media access control-identifier (MAC -ID), and a network identifier.

[0076] In an implementation of the present disclosure, wherein, to add the retrieved GPSI data for interacting with the converged charging function (CHF)

[0132] , the processing unit

[0308] is configured to send a request, comprising a dedicated field for the GPSI data, to the CHF

[0132] ,

[0077] In an implementation of the present disclosure, the system

[0300] further includes a storage unit

[0304] configured to store, through the CHF

[0132] , the GPSI data in a call data records (CDR).

[0078] In an implementation of the present disclosure, the processing unit

[0308] is configured to perform, through the OCS

[0310] , a quota management and sending response back to the CHF

[0132] , The quota management refers to the process of monitoring and controlling the usage of network resources or services by the processing unit

[0308] within a network environment. The quota management ensures that users stay within their allocated limits, which can be based on various parameters, such as but not limited to data usage, call minutes, or message counts. The quota management may include:Resource Allocation: The telecom service providers, through the processing unit

[0308] , set specific quotas for different services (e.g., data plans, voice calls, SMS) based on the subscriber’s plan.Usage Tracking: The telecom service provider continuously tracks the subscriber’s usage in real-time to determine how much of their quota has been consumed.- Alerts and Notifications: The subscribers may receive notifications as they approach their limits, allowing them to manage their usage proactively.Service Denial or Throttling: If a subscriber exceeds their quota, the processing unit

[0308] of the system

[0300] can either deny further access to services or throttle their speeds, depending on the provider’s policies.Recharging and Upgrading: The subscribers may have the option to recharge their accounts or upgrade to a higher plan if they frequently reach their quotas.

[0079] Overall, quota management helps ensure fair usage of network resources and facilitate accurate bill.

[0080] Referring to FIG. 4, an exemplary method flow diagram

[0400] for providing subscriber identity information for billing of service usages, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0400] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method

[0400] starts at step

[0402] ,

[0081] At step

[0404] , the method

[0400] comprises retrieving, by a retrieving unit

[0302] , through a policy control function (PCF)

[0122] , a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database

[3042] , Thereafter, the retrieving unit

[0302] sends the retrieved GPSI data to a transceiver unit

[0306] , The GPSI is a number that uniquely identifies every user / subscriber of the communication network. It is stored as a 64-bit field and is sent by the user device to the communication network.

[0082] In an implementation of the present disclosure, the GPSI data comprises at least one of: a user identification information, a media access control-identifier (MAC -ID), and a network identifier.

[0083] At step

[0406] , the method

[0400] comprises transmitting, by the transceiver unit

[0306] through the PCF

[0122] , to a Session Management Function (SMF)

[0108] , the retrieved GPSI data as an SMF response.

[0084] At step

[0408] , the method

[0400] comprises adding, by a processing unit

[0308] through the SMF

[0108] , the retrieved GPSI data for interacting with a converged charging function (CHF)

[0132] ,

[0085] In an implementation of the present disclosure, wherein, adding the retrieved GPSI data for interacting with the converged charging function (CHF)

[0132] , further comprises sending, by the processing unit

[0308] , a request, comprising a dedicated field for the GPSI data, to the CHF

[0132] ,

[0086] At step

[0410] , the method

[0400] comprises converting, by the processing unit

[0308] through the CHF

[0132] , a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data. The HTTP2 (modified form of HTTP) offers weighted prioritization that helps in deciding which network resources will load first, every time. In HTTP2 (as used in the present disclosure), when a client makes a request for a webpage, the server sends several streams of data to the client at once, instead of sending one thing after another. The diameter request here refers a next-generation industry-standard protocol used to exchange authentication, authorization, and accounting (AAA) information in Long-Term Evolution (LTE) and IP Multimedia Systems (IMS) networks. The diameter request is designed to manage network access, resource usage, and billing more effectively than its predecessor, RADIUS protocol.The diameter request may include one or more features as mentioned below:1. Command Code: It specifies the type of request (e.g., for user authentication, service authorization, or accounting).2. Session ID: This is a unique identifier which is associated with a particular session, allowing the network operators to track interactions.3. AVPs (Attribute- Value Pairs): These are flexible data structures used to carry various parameters, such as user identity, service details, and additional data like GPSI (Global Public Subscriber Identity).4. Transport Protocol: This refers to TCP or SCTP, thereby providing reliable and ordered delivery of messages.

[0087] The CHF

[0132] (as explained in FIG. 1) is a network function (NF) in a 5G network for managing online charging for a plurality of services (such as voice call service, video streamingservice, etc.) used by subscribers. Further, the PCF

[0122] (as explained in FIG. 1) is a NF responsible for policy enforcement and quality of service (QoS) control to effectively allocate / manage one or more resources of the network during the session. A policy counter is a mechanism within the CHF

[0132] to track spending applicable to a subscriber. These policy counters must be available in the CHF

[0132] prior to their use by other network functions, such as PCF. The CHF

[0132] stores the policy counter information against the subscriber pricing plan and notifies the PCF

[0122] whenever the subscriber breaches the policy thresholds based on usage consumption.

[0088] At step

[0412] , the method

[0400] comprises transmitting, by the transceiver unit

[0306] through the CHF

[0132] , the diameter request to an online charging system (OCS)

[0310] , The Online Charging System (OCS)

[0310] is a network function connected in the 5G network system that manages the real-time charging and billing of services for subscribers, manages all the transactions within the system, including the subscriber's account balance and charges. The OCS

[0310] enables operators to ensure accurate billing for services by implementing advanced policy rules, enforcing credit limits, accessing advanced analytics, and more. The OCS

[0310] is a cloud-native platform that supports charging across multiple generations of telecom networks. This is achieved by providing multi -protocol support for integration. The OCS

[0310] supports charging customers for their usage based on the device they use. A single plan or bucket may have tariffs for multiple devices as well as the option to have tariffs for device / s or default tariffs. It enables duration-based charging for LTE, Wi-Fi, and FTTH services to support non-monetary entitlements in the form of seconds, minutes, or hours.

[0089] At step

[0414] , the method

[0400] comprises responding, by the processing unit

[0308] through the CHF

[0132] , an OCS response in response to the diameter request to at least one of: the SMF

[0108] and the PCF

[0122] for billing of service usages.

[0090] In an implementation of the present disclosure, the method

[0400] comprises storing, by a storage unit

[0304] through the CHF

[0132] , the GPSI data in a call data records (CDR).

[0091] In an implementation of the present disclosure, the method

[0400] comprises performing, by the processing unit

[0308] through the OCS

[0310] a quota management and sending response back to the CHF

[0132] , The quota management refers to the process of monitoring and controlling the usage of network resources or services by the processing unit

[0308] within a network environment. The quota management ensures that users stay within their allocated limits, which can be based on various parameters, such as but not limited to data usage, call minutes, or message counts. The quota management may include:Resource Allocation: The telecom service providers, through the processing unit

[0308] , set specific quotas for different services (e.g., data plans, voice calls, SMS) based on the subscriber’s plan.Usage Tracking: The telecom service provider continuously tracks the subscriber’s usage in real-time to determine how much of their quota has been consumed.- Alerts and Notifications: The subscribers may receive notifications as they approach their limits, allowing them to manage their usage proactively.Service Denial or Throttling: If a subscriber exceeds their quota, the processing unit

[0308] of the system

[0300] can either deny further access to services or throttle their speeds, depending on the provider’s policies.Recharging and Upgrading: The subscribers may have the option to recharge their accounts or upgrade to a higher plan if they frequently reach their quotas.

[0092] Overall, quota management helps ensure fair usage of network resources and facilitate accurate bill.

[0093] Thereafter, the method

[0400] terminates at step

[0016] ,

[0094] Referring to FIG. 5, an exemplary flow chart depicting the process

[0500] of for providing subscriber identity information for billing of service usages in a communication network is shown, in accordance with the present disclosure.

[0095] The billing of service usages is performed in the following manner:Step 1 (SI): A Policy Control Function (PCF)

[0122] to another network function (NF) such as a Session Management Function (SMF)

[0108] viaHTTP2 protocol. Thereafter, a HTTP request is sent to a Converged Charging Function (CHF)

[0132] , It is to be noted that prior to sending the HTTP request, a Global Public Subscriber Identity (GPSI) data is fetched via the PCF

[0122] from a subscriber profile repository (SPR) database

[3042] (as shown in FIG. 3) and the GPSI is further sent in the SMF’s

[0108] response. Thus, the GPSI data is attached via the SMF

[0108] in interaction with the CHF

[0132] ,Step 2 (S2): Upon receipt of the HTTP request, the CHF

[0132] proceeds to convert the received HTTP request into a DIAMETER REQUEST and forwards the DIAMETER REQUEST along with the GPSI data to an Online Charging System (OCS)

[0310] , It is also to be noted that the GPSI data is entered into a local call data record (CDRs).Step 3 (S3): Thereafter, the OCS

[0310] performs quota management and send back the OCS’s

[0310] response. The CHF

[0132] converts the OCS’s

[0310] response from the DIAMETER request to the HTTP2 request and the responds back to the SMF

[0108] , Thus, the process

[0500] for providing subscriber identity information for billing of service usages is therefore concluded.

[0096] The OCS’s

[0310] response may include quota status, usage records, charging information, validity period and the like. The quota status indicates whether the subscriber has sufficient balance or quota to continue using the service. For example, it may return values such as "Sufficient Balance" or "Insufficient Balance." The usage records may include details about the current usage session, such as the amount of data consumed, time spent, or other relevant metrics. The usage records help in tracking how much of the allocated quota has been used. Further, charging information may involve information on the rate being applied for the current session. For instance, it could specify the cost per megabyte of data used or per minute of call time. Also, validity period indicates how long the current quota or balance is valid. For example, it may state that the balance is valid for the next 30 days.

[0097] The present disclosure further discloses a non-transitory computer-readable storage medium storing instruction for providing subscriber identity information for billing of service usages, the storage medium comprising executable code which, when executed by one or more units of a system

[0300] , causes a retrieving unit

[0302] , of the system

[0300] , to retrieve, through a policy control function (PCF)

[0122] , a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database

[3042] , Further, the executable code which, when executed causes a transceiver unit

[0306] , of the system

[0300] to transmit, through the PCF

[0122] , to a Session Management Function (SMF)

[0108] , the retrieved GPSI data. Further, the executable code which, when executed causes a processing unit

[0308] , of the system

[0300] , to add, through the SMF

[0108] , the retrieved GPSI data for interacting with a converged charging function (CHF)

[0132] , Further, the executable code which, when executed causes the processing unit

[0308] to convert, through the CHF

[0132] , a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data. Further, the executable code which, when executed causes the transceiver unit

[0306] to transmit, through the CHF

[0132] , the diameter request to an online charging system (OCS)

[0310] , Further, the executable code which, when executed causes the processing unit

[0308] to respond, through the CHF

[0132] , an OCS response in response to the diameter request to the SMF

[0108] or the PCF

[0122] for billing of service usages.

[0098] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

[0099] As is evident from the above, the present disclosure provides a technically advanced solution of providing efficient systems and methods for providing subscriber identity information for billing of service usages. The present disclosure integrates GPSI (Global Public Subscriber Identity) into call data records (CDRs) within the communication network. The present disclosure further provides a solution, in which Converged Charging Function (CHF)

[0132] integrates GPSI into CDRs for billing and reconciliation purposes. The present disclosure also provides a solution, in which the CHF

[0132] provides GPSI in CDR to an Online Charging Systems (OCS)

[0310] , by a Session Management Function (SMF)

[0310] , with the help of Policy Control Function (PCF)

[0122] and Subscriber Profile Repository (SPR) database

[3042] , The present disclosure thus provides a simplified and enhanced billing and reconciliation process. By seamlessly incorporating GPSI into CDRs, the accurate subscriber information data may readily be available for billing purposes, leading to more precise and transparent financial transactions. The present disclosure therefore improves the efficiency of the network along with setting a solution by addressing a crucial aspect of subscriber management in an optimized and effective manner.

[0100] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

Claims

We Claim:

1. A method [400] for providing subscriber identity information for billing of service usages, the method [400] comprising: retrieving, by a retrieving unit [302], through a policy control function (PCF) [122], a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database [3042], wherein the retrieving unit [302] sends the retrieved GPSI data to a transceiver unit [306];- transmitting, by the transceiver unit [306] through the PCF [122], to a Session Management Function (SMF) [108], the retrieved GPSI data as an SMF response; adding, by a processing unit [308] through the SMF unit [108], the retrieved GPSI data for interacting with a converged charging function (CHF) [132]; converting, by the processing unit [308] through the CHF [132], a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data;- transmitting, by the transceiver unit [306] through the CHF [132], the diameter request to an online charging system (OCS) [310]; and responding, by the processing unit [308] through the CHF [132], an OCS response in response to the diameter request to at least one of: the SMF [108] and the PCF [122] for billing of service usages.

2. The method [400] as claimed in claim 1, wherein the GPSI data comprises at least one of: a user identification information, a media access control-identifier (MAC-ID), and a network identifier.

3. The method [400] as claimed in claim 1, wherein, adding the retrieved GPSI data for interacting with the converged charging function (CHF) [132], further comprises sending, by the processing unit [308], a request, comprising a dedicated field for the GPSI data, to the CHF [132],4. The method [400] as claimed in claim 1, wherein the method [400] comprises storing, by a storage unit [304] through the CHF [132], the GPSI data in a call data records (CDR).

5. The method [400] as claimed in claim 1, wherein the method [400] comprises performing, by the processing unit [308] through the OCS [310] a quota management and sending response back to the CHF [132],6. A system [300] for providing subscriber identity information for billing of service usages, the system [300] comprising: a retrieving unit [302] configured to:retrieve, through a policy control function (PCF) [122], a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database [3042]; a transceiver unit [306] configured to: transmit, through the PCF [122], to a Session Management Function (SMF) [108], the retrieved GPSI data; a processing unit [308] configured to: add, through the SMF [108], the retrieved GPSI data for interacting with a converged charging function (CHF) [132]; convert, through the CHF [132], a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data;- the transceiver unit [306] configured to: transmit, through the CHF [132], the diameter request to an online charging system (OCS) [310]; and- the processing unit [308] configured to: respond, through the CHF [132], an OCS response in response to the diameter request to at least one of: the SMF [108] and the PCF [122] for billing of service usages.

7. The system [300] as claimed in claim 6, wherein the GPSI data comprises at least one of: a user identification information, a media access control-identifier (MAC-ID), and a network identifier.

8. The system [300] as claimed in claim 6, wherein, to add the retrieved GPSI data for interacting with the converged charging function (CHF) [132], the processing unit [308] is configured to send a request, comprising a dedicated field for the GPSI data, to the CHF [132],9. The system [300] as claimed in claim 6, wherein the system [300] further comprising a storage unit [304] configured to store, through the CHF [132], the GPSI data in a call data records (CDR).

10. The system [300] as claimed in claim 6, wherein the processing unit [308] is configured to perform, through the OCS [310], a quota management and sending response back to the CHF [132],11. A non-transitory computer-readable storage medium storing instructions for providing subscriber identity information for billing of service usages, the storage medium comprising executable code which, when executed by one or more units of a system [300], causes: a retrieving unit [302] to: retrieve, through a policy control function (PCF) [122], a Global Public Subscriber Identity (GPSI) data from a subscriber profile repository (SPR) database [3042]; a transceiver unit [306] to:transmit, through the PCF [122], to a Session Management Function (SMF) [108], the retrieved GPSI data; a processing unit [308] to: add, through the SMF [108], the retrieved GPSI data for interacting with a converged charging function (CHF) [132]; convert, through the CHF [132], a Hypertext Transfer Protocol (HTTP) request to a diameter request along with the retrieved GPSI data;- the transceiver unit [306] to: transmit, through the CHF [132], the diameter request to an online charging system(OCS) [310]; and- the processing unit [308] to: respond, through the CHF [132], an OCS response in response to the diameter request to at least one of: the SMF [108] and the PCF [122] for billing of service usages.

Images