DESC:
FORM 2

THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR CHARGING A USER IN A NETWORK

2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention pertains to the field of telecommunications, specifically addressing the challenges associated with charging out roamer users for Short Message Service (SMS) in an online environment. The invention relates to resolving the problem of accurately determining the charging parameters for the out roamer users based on their location and global title (GT) information.
BACKGROUND OF THE INVENTION
[0002] In the telecommunications industry, out roamer users are individuals who maintain connectivity with their home network while traveling abroad. This seamless connectivity ensures uninterrupted access to selected services and enables accurate billing for the services utilized. In the case of out roamer users connected to second generation (2G)/third generation (3G) networks, their messages are transmitted through a Signaling System number 7 (SS7) interface, including the GT information of a sender's Short Message Service Centers (SMSCs).
[0003] The Global Title (GT) information plays a vital role in an Online Charging System (OCS), as it helps determine whether the out roamer user is in their home network or roaming in another network. This information is crucial for applying the appropriate charging policies and ensuring accurate billing.
[0004] In telecommunications, a Global Title (GT) refers to a unique identifier assigned to network elements such as Service Switching Points (SSPs), Service Control Points (SCPs), Short Message Service Centers (SMSCs), and other network entities. The GT acts as an address that helps identify and route messages within a telecommunication network. It typically consists of digits or alphanumeric characters and provides information about the network entity's location or function.
[0005] The GT plays a crucial role in various signaling protocols, including the SS7 interface, which is widely used for signaling and control in telecommunications network. When the out roamer user sends a message through the SS7 interface, the GT of the sender's SMSC is included in the message. This GT information is utilized by the network elements, particularly the OCS, to determine whether the user is in their home network or roaming in another network.
[0006] The OCS is a component within a telecommunications network that is responsible for real-time charging and billing of various services. It performs the critical function of monitoring, controlling, and applying charging policies based on the usage of network resources and services by subscribers. The OCS ensures that users are accurately billed for the services they consume, enabling revenue generation for service providers.
[0007] The OCS interacts with various network elements, such as the Home Subscriber Server (HSS), Policy and Charging Rules Function (PCRF), and Service Delivery Platforms (SDPs), to gather information about service usage, charging policies, and subscriber profiles. It applies the appropriate charging mechanisms, tariff plans, and rating schemes to calculate the charges incurred by users in real-time
[0008] For the out roamer users, the OCS relies on the GT information received through signaling interfaces (such as SS7 or SIP) to determine the user's location and apply the relevant charging rules. However, in the case of the out roamer users connected to 4G networks through the Session Initiation Protocol (SIP) interface, the GT information may not be available. This poses a challenge for the OCS to accurately charge the out roamer users without the necessary GT data.
[0009] However, a significant challenge arises when the out roamer users are connected to the 4G or 5G network in a foreign country. The out roamer users are individuals who maintain connectivity with their home network while traveling abroad. This seamless connectivity ensures uninterrupted access to selected services and enables accurate billing for the services utilized. In the case of the out roamer users connected to the 2G/3G networks, their messages are transmitted through the SS7 interface, including the GT information of the sender's SMSC. In such cases, messages are received through the Session Initiation Protocol (SIP) interface, but no GT information is provided.
[0010] The absence of the GT information in the 4G or 5G network scenarios creates difficulties for the OCS to accurately charge the out roamer users based on their location. Consequently, there is a need for an innovative solution that can address this limitation and enable accurate charging for the out roamer users connected to the 4G or 5G networks. Therefore, there is a need to overcome the challenges posed by the lack of GT information for the out roamer users connected to the 4G networks.
[0011] In conclusion, a circle-wise GT mapping for charging out roamer users addresses the critical need for accurate charging of the out roamer users connected to the 4G or 5G networks. By overcoming the challenges associated with the lack of GT information, the invention ensures appropriate billing, revenue optimization, and enhanced customer experience in the telecommunications industry.
SUMMARY OF THE INVENTION
[0012] One or more embodiments of the present disclosure provide a system and a method for charging a user in a network.
[0013] In one aspect of the present invention, a method of charging a user in a network is disclosed. The method includes receiving, by one or more processors, a Session Initiation Protocol (SIP) message from a user equipment (UE) associated with the user. Further, the method includes extracting, by the one or more processors, a network identifier from a header of the SIP message, wherein the network identifier is associated to a network from which the UE sent the SIP message. Further, the method includes identifying, by the one or more processors, a global title (GT) value from the network identifier by using a map, wherein the map stores a plurality of network identifiers of a plurality of permitted networks and a plurality of GT values. Each network identifier of the plurality of network identifiers is associated with a unique GT value. Each network identifier is associated to a permitted network of the plurality of permitted network. Further, the method includes identifying, by the one or more processors, the address of a home network of the UE from the GT value. Further, the method includes adding, by the one or more processors, the GT value in the address of the home network, wherein the GT value is used by an online charging system (OCS) to charge the user for using the network.
[0014] In an embodiment, the network from which the UE sends the SIP message is one of the plurality of permitted networks that the user visits. In an embodiment, the permitted network is one of a partner network and a home network.
[0015] In an embodiment, the mapping of each network identifier to the unique GT value enables differentiating the user as a local user and a roaming user.
[0016] In an embodiment, the user is considered as the local user in the home network and is considered as a roaming user in a partner network. The local user is a subscriber of the home network.
[0017] In an embodiment, the user is considered a roaming user when the GT value indicates the permitted network from which the UE sent the SIP message is different from the home network of the user.
[0018] In an embodiment, the user is considered as a local user when the GT value indicates the permitted network from which the UE sent the SIP message is the home network of the user.
[0019] In an embodiment, the charge applicable for using the network is higher for a roaming user than a local user.
[0020] In an embodiment, a subscriber module is configured to retrieve information related to service usage, charging policies, and profiles of a plurality of users from one or more of a Home Subscriber Server (HSS), a Policy and Charging Rules Function (PCRF), and Service Delivery Platforms (SDPs).
[0021] In an embodiment, the GT is one of: an alphanumeric code and an unique identifier assigned to a network element, and wherein the unique identifier provides information related to a location and function of the network element.
[0022] In an embodiment, the unique identifier is the GT assigned to the network element, and wherein the network element is one of a service switching point (SSP), a service control point (SCPs), and short message service centres (SMSCs).
[0023] In another aspect of the present invention, a system for charging a user of a network is disclosed. The system includes a gateway node and an extraction module. The gateway node is configured to store a map of a plurality of network identifiers of a plurality of permitted networks, and a plurality of GT values. Each network identifier of the plurality of network identifiers is associated with a unique GT value. Each network identifier is associated to a permitted network of the plurality of permitted networks. The gateway node is configured to receive a SIP message from a UE associated with the user. The extraction module is configured to extract the network identifier from a header of the SIP message, wherein the network identifier is associated to the permitted network from which the UE sent the SIP message. Further, the extraction module is configured to identify a GT value from the network identifier by using the map. Further, the extraction module is configured to identify an address of a home network of the UE from the GT value. Further, the extraction module is configured to add the GT value in the address of the home network, wherein the GT value is used by an online charging system (OCS) to charge the user for using the network.
[0024] In another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor, cause the processor to receive a SIP message from a UE associated with the user, extract a network identifier from a header of the SIP message, wherein the network identifier is associated to a network from which the UE sent the SIP message, identify a GT value from the network identifier by using a map, identify the address of a home network of the UE from the GT value, and add the GT value in the address of the home network, wherein the GT value is used by an online charging system (OCS) to charge the user for using the network. The map stores a plurality of network identifiers of a plurality of permitted networks, and a plurality of GT values, wherein each network identifier of the plurality of network identifiers is associated with a unique GT value, and wherein each network identifier is associated to a permitted network;
[0025] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS
[0026] 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 disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0027] FIG. 1 is an exemplary block diagram of an environment for charging a user of a network, according to various embodiments of the present disclosure.
[0028] FIG. 2 is a block diagram of a system of FIG. 1, according to various embodiments of the present disclosure.
[0029] FIG. 3 is an example schematic representation of the system of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system.
[0030] FIG. 4 illustrates a IPSMGW system architecture, in accordance with an embodiment of the invention.
[0031] FIG. 5 is a block diagram of a processor in the system of FIG. 1, according to various embodiments of the present disclosure.
[0032] FIG. 6 shows a sequence flow diagram illustrating a method for charging a user in a network, according to various embodiments of the present disclosure.
[0033] FIG. 7 is an example flow diagram illustrating the method for circle-wise GT mapping process while charging the user of the network, according to various embodiments of the present disclosure.
[0034] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.
[0035] The foregoing shall be more apparent from the following detailed description of the invention.

DETAILED DESCRIPTION OF THE INVENTION
[0036] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0037] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0038] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0039] Various embodiments of the invention provide a method of charging a user in a network. The method includes receiving, by one or more processors, a SIP message from a UE associated with the user. Further, the method includes extracting, by the one or more processors, a network identifier from a header of the SIP message, wherein the network identifier is associated to a network from which the UE sent the SIP message. Further, the method includes identifying, by the one or more processors, a GT value from the network identifier by using a map, wherein the map stores a plurality of network identifiers of a plurality of permitted networks and a plurality of GT values. Each network identifier of the plurality of network identifiers is associated with a unique GT value. Each network identifier is associated to a permitted network of the plurality of permitted network. Further, the method includes identifying, by the one or more processors, the address of a home network of the UE from the GT value. Further, the method includes adding, by the one or more processors, the GT value in the address of the home network, wherein the GT value is used by an OCS to charge the user for using the network.
[0040] The invention addresses the challenge of accurately charging the out roamer users in 4G networks, where the GT information is unavailable. By establishing a mapping between a P-Visited Network Identifier (PVNI) and GT, this solution enables the OCS to correctly charge users based on their domain, preventing revenue loss due to insufficient out roamer GT information.
[0041] The technical advance of the present invention lies amongst others, in the implementation of the solution at the IP Short Message Gateway (IPSMGW) node in the IMS network. The IPSMGW maintains a map of PVNI for allowed domains (e.g., partner network or own network) and stores unique GTs associated with each PVNI. When a SIP MESSAGE request is received, the IPSMGW checks the PVNI header to determine the visited domain of the user. It then sends the corresponding GT mapped against that PVNI to the OCS in an Originator-SCCP-Address Sub-AVP. The OCS utilizes this GT information for differential charging, accurately billing the out roamer and local users.
[0042] By implementing this invention, service providers can ensure accurate charging for the out roamer users in the 4G networks, enhancing revenue optimization and customer satisfaction. The circle-wise GT mapping solution optimizes the charging process by leveraging PVNI and GT mapping, effectively overcoming the limitations of GT unavailability in the 4G network scenarios.
[0043] Overall, by implementing this solution at the IPSMGW node, it facilitates differential charging based on PVNI and GT mapping, ensuring precise billing and revenue assurance in modern telecommunications networks.
[0044] FIG. 1 illustrates an exemplary block diagram of an environment (100) for charging a user of a network (106), according to various embodiments of the present disclosure. The environment (100) comprises a plurality of user equipment’s (UEs) 102-1, 102-2, ……,102-n. The at least one UE (102-n) from the plurality of the UEs (102-1, 102-2, ……102-n) is configured to connect to a system (108) via the communication network (or telecommunication network) (106). The terms “communication network” and “telecommunication network” are used interchangeably in the patent disclosure. The communication network includes a home network (106a) and a partner network (106b). Hereafter, label for the plurality of UEs or one or more UEs is 102.
[0045] In accordance with yet another aspect of the exemplary embodiment, the plurality of UEs (102) may be a wireless device or a communication device that may be a part of the system (108). The wireless device or the UE (102) may include, but are not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), 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 or VoIP capabilities. In an embodiment, the UEs may include, but are not limited to, any electrical, electronic, electro-mechanical or an equipment or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the computing device may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as camera, audio aid, a microphone, a keyboard, input devices for receiving input from a user such as touch pad, touch enabled screen, electronic pen and the like. It may be appreciated that the UEs may not be restricted to the mentioned devices and various other devices may be used. A person skilled in the art will appreciate that the plurality of UEs (102) may include a fixed landline, a landline with assigned extension within the communication network (106).
[0046] The plurality of UEs (102) may comprise a memory such as a volatile memory (e.g., RAM), a non-volatile memory (e.g., disk memory, FLASH memory, EPROMs, etc.), an unalterable memory, and/or other types of memory. In one implementation, the memory might be configured or designed to store data. The data may pertain to attributes and access rights specifically defined for the plurality of UEs (102). The UE (102) may be accessed by the user, to receive the requests related to an order determined by the system (108). The communication network (106), may use one or more communication interfaces/protocols such as, for example, Voice Over Internet Protocol (VoIP), 802.11 (Wi-Fi), 802.15 (including Bluetooth™), 802.16 (Wi-Max), 802.22, Cellular standards such as Code Division Multiple Access (CDMA), CDMA2000, Wideband CDMA (WCDMA), Radio Frequency Identification (e.g., RFID), Infrared, laser, Near Field Magnetics, etc.
[0047] The system (108) is communicatively coupled to a server (104) via the communication network (106). The server (104) can be, for example, but not limited to a standalone server, a server blade, a server rack, an application server, a bank of servers, a business telephony application server (BTAS), a server farm, a cloud server, an edge server, home server, a virtualized server, one or more processors executing code to function as a server, or the like. In an implementation, the server (104) may operate at various entities or a single entity (include, but is not limited to, a vendor side, a service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, a defence facility side, or any other facility) that provides service.
[0048] The communication network (106) includes, 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, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The communication network (106) may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0049] The communication network (106) may also 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 communication 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, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0050] One or more network elements can be, for example, but not limited to a base station that is located in the fixed or stationary part of the communication network (106). The base station may correspond to a remote radio head, a transmission point, an access point or access node, a macro cell, a small cell, a micro cell, a femto cell, a metro cell. The base station enables transmission of radio signals to the UE or mobile transceiver. Such a radio signal may comply with radio signals as, for example, standardized by a 3GPP or, generally, in line with one or more of the above listed systems. Thus, a base station may correspond to a NodeB, an eNodeB, a Base Transceiver Station (BTS), an access point, a remote radio head, a transmission point, which may be further divided into a remote unit and a central unit.
[0051] 3GPP: The term “3GPP” is a 3rd Generation Partnership Project and is a collaborative project between a group of telecommunications associations with the initial goal of developing globally applicable specifications for Third Generation (3G) mobile systems. The 3GPP specifications cover cellular telecommunications technologies, including radio access, core network, and service capabilities, which provide a complete system description for mobile telecommunications. The 3GPP specifications also provide hooks for non-radio access to the core network, and for networking with non-3GPP networks.
[0052] The system (108) may include one or more processors (202) coupled with a memory (204), wherein the memory (204) may store instructions which when executed by the one or more processors (202) may cause the system (108) executing requests in the communication network (106) or the server (104). An exemplary representation of the system (108) for such purpose, in accordance with embodiments of the present disclosure, is shown in FIG. 2 as system (108). 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, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in the 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.
[0053] The environment (100) further includes the system (108) communicably coupled to the remote server (104) and each UE of the plurality of UEs (102) via the communication network (106). The remote server (104) is configured to execute the requests in the communication network (106).
[0054] The system (108) is adapted to be embedded within the remote server (104) or is embedded as the individual entity. The system (108) is designed to provide a centralized and unified view of data and facilitate efficient business operations. The system (108) is authorized to access to update/create/delete one or more parameters of their relationship between the requests for the workflow, which gets reflected in real-time independent of the complexity of network.
[0055] In another embodiment, the system (108) may include an enterprise provisioning server (for example), which may connect with the remote server (104). The enterprise provisioning server provides flexibility for enterprises, ecommerce, finance to update/create/delete information related to the requests in real time as per their business needs. A user with administrator rights can access and retrieve the requests for the workflow and perform real-time analysis in the system (108).
[0056] The system (108) may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a business telephony application server (BTAS), a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an implementation, system (108) may operate at various entities or single entity (for example include, but is not limited to, a vendor side, service provider side, a network operator side, a company side, an organization side, a university side, a lab facility side, a business enterprise side, ecommerce side, finance side, a defence facility side, or any other facility) that provides service.
[0057] However, for the purpose of description, the system (108) is described as an integral part of the remote server (104), without deviating from the scope of the present disclosure. Operational and construction features of the system (108) will be explained in detail with respect to the following figures.
[0058] FIG. 2 illustrates a block diagram of the system (108) provided for charging the user of the network (104), according to one or more embodiments of the present invention. As per the illustrated embodiment, the system (108) includes the one or more processors (202), the memory (204), an input/output interface unit (206), a display (208), an input device (210), and a centralized database (or database) (214). Further the system (108) may comprise one or more processors (202). The one or more processors (202), hereinafter referred to as the processor (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions. As per the illustrated embodiment, the system (108) includes one processor. However, it is to be noted that the system (108) may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.
[0059] The information related to the request may be provided or stored in the memory (204) of the system (108). Among other capabilities, the processor (202) is configured to fetch and execute computer-readable instructions stored in the memory (204). 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 RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0060] The memory (204) may comprise any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like. In an embodiment, the system (108) may include an interface(s). The interface(s) may comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as input/output (I/O) devices, storage devices, and the like. The interface(s) may facilitate communication for the system. The interface(s) may also provide a communication pathway for one or more components of the system. Examples of such components include, but are not limited to, processing unit/engine(s) and a database. The processing unit/engine(s) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s).
[0061] The information related to the requests may further be configured to render on the user interface (206). The user interface (206) may include functionality similar to at least a portion of functionality implemented by one or more computer system interfaces such as those described herein and/or generally known to one having ordinary skill in the art. The user interface (206) may be rendered on the display (208), implemented using Liquid Crystal Display (LCD) display technology, Organic Light-Emitting Diode (OLED) display technology, and/or other types of conventional display technology. The display (208) may be integrated within the system (108) or connected externally. Further the input device(s) (210) may include, but not limited to, keyboard, buttons, scroll wheels, cursors, touchscreen sensors, audio command interfaces, magnetic strip reader, optical scanner, etc.
[0062] The centralized database (214) may be communicably connected to the processor (202) and the memory (204). The centralized database (214) may be configured to store and retrieve the request pertaining to features, or services or workflow of the system (108), access rights, attributes, approved list, and authentication data provided by an administrator. Further the remote server (104) may allow the system (108) to update/create/delete one or more parameters of their information related to the request, which provides flexibility to roll out multiple variants of the request as per business needs. In another embodiment, the centralized database (214) may be outside the system (108) and communicated through a wired medium and wireless medium.
[0063] Further, the processor (202), in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor (202). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor (202) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor (202) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory (204) may store instructions that, when executed by the processing resource, implement the processor (202). In such examples, the system (108) may comprise the memory (204) storing the instructions and the processing resource to execute the instructions, or the memory (204) may be separate but accessible to the system (108) and the processing resource. In other examples, the processor (202) may be implemented by an electronic circuitry.
[0064] In order for the system (108) for charging the user in the network (106), the processor (202) includes a gateway node (216), an extraction module (218), an OCS (220), and a subscriber module (222). The gateway node (216), the extraction module (218), the OCS (220), and the subscriber module (222) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor (202). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor (202) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor (202) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory (204) may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system (108) may comprise the memory (204) storing the instructions and the processing resource to execute the instructions, or the memory (204) may be separate but accessible to the system (108) and the processing resource. In other examples, the processor (202) may be implemented by the electronic circuitry.
[0065] In order for the system (108) for charging the user in the network (106), the gateway node (216), the extraction module (218), the OCS (220), and the subscriber module (222) are communicably coupled to each other. In an example embodiment, the gateway node (216) stores a map of a plurality of network identifiers of a plurality of permitted networks and a plurality of GT values. The GT value is one of: an alphanumeric code and an unique identifier assigned to the network element. The unique identifier provides information related to a location and function of the network element. The unique identifier is a GT assigned to the network element. The network element is one of a SSP, SCPs, and SMSCs. Each network identifier of the plurality of network identifiers is associated with a unique GT value, and each network identifier is associated to a permitted network of the plurality of permitted networks. Further, the gateway node (216) receives a SIP message from the UE associated with the user. The extraction module (218) extracts the network identifier from a header of the SIP message. The network identifier is associated to the permitted network from which the UE sent the SIP message. Further, the extraction module (218) identifies a GT value from the network identifier by using the map. In an embodiment, the mapping of each network identifier from the unique GT value enables differentiating the user as a local user and a roaming user, where the user is considered as a local user in the home network (106a) and is considered as a roaming user in a partner network (106b), and wherein the local user is a subscriber of the home network (106a). Further, the extraction module (218) identifies an address of the home network (106a) of the UE from the GT value. Further, the extraction module (218) adds the GT value in the address of the home network (106a), where the GT value is used by the OCS (220) to charge the user for using the network (106).
[0066] In an embodiment, the UE sends the SIP message to the gateway node (216) from one of the plurality of permitted networks that the user visits. The permitted network is one of the partner network (106b) and the home network (106a).
[0067] In an embodiment, the user is considered as a roaming user when the GT value indicates the permitted network from which the UE sent the SIP message is different from the home network (106a) of the user.
[0068] In an embodiment, the user is considered as the local user when the GT value indicates the permitted network from which the UE sent the SIP message is the home network (106a) of the user. In an embodiment, the charge applicable for using the network (106) is higher for the roaming user than the local user.
[0069] FIG. 3 is an example schematic representation of the system (300) of FIG. 1 in which various entities operations are explained, according to various embodiments of the present system. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE (102-1) and the system (108) for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0070] As mentioned earlier, the first UE (102-1) includes one or more primary processors (305) communicably coupled to the one or more processors (202) of the system (108). The one or more primary processors (305) are coupled with a memory (310) storing instructions which are executed by the one or more primary processors (305). Execution of the stored instructions by the one or more primary processors (305) enables the UE (102-1). The execution of the stored instructions by the one or more primary processors (305) further enables the UE (102-1) to execute the requests in the communication network (106).
[0071] As mentioned earlier, the one or more processors (202) is configured to transmit a response content related to the request to the UE (102-1). More specifically, the one or more processors (202) of the system (108) is configured to transmit the response content from a kernel (315) to at least one of the UE (102-1). The kernel (315) is a core component serving as the primary interface between hardware components of the UE (102-1) and the system (108). The kernel (315) is configured to provide the plurality of response contents hosted on the system (108) to access resources available in the communication network (106). The resources include one of a Central Processing Unit (CPU), memory components such as Random Access Memory (RAM) and Read Only Memory (ROM).
[0072] As per the illustrated embodiment, the system (108) includes the one or more processors (202), the memory (204), the input/output interface unit (206), the display (208), and the input device (210). The operations and functions of the one or more processors (202), the memory (204), the input/output interface unit (206), the display (208), and the input device (210) are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure. Further, the processor (202) includes the gateway node (216), the extraction module (218), the OCS (220), and the subscriber module (222). The operations and functions of the gateway node (216), the extraction module (218), the OCS (220), and the subscriber module (222) are already explained in FIG. 2. For the sake of brevity, we are not explaining the same operations (or repeated information) in the patent disclosure.
[0073] FIG. 4 illustrates a IPSMGW system architecture (400), in accordance with an embodiment of the invention. The system architecture of the IPSMGW (IP Short Message Gateway) (402) is illustrated in FIG. 4, comprising various components and their integration interfaces for seamless operation within the telecommunications network (106).
[0074] The IPSMGW Application component (or IPSMGW) (402): The IPSMGW Application component (402) integrates with a S-CSCF (Serving Call Session Control Function) (408) over an ISC (IP Service Control) interface. This integration enables the IPSMGW Application component (402) to handle third-party registrations and forward SMS messages originated from the UE towards the IPSMGW (402).
[0075] Additionally, the IPSMGW (402) integrates with a MNP (Mobile Number Portability) DB (Database) (418) over a SIP (Session Initiation Protocol) interface. This integration allows the IPSMGW (402) to perform MNP queries to obtain Routable Numbers (RN) and outbound Mobile Numbers for message routing. A load balancer (e.g., F5 Load balancer) (412, 416), in one implementation, is configured for routing the queries.
[0076] The IPSMGW (402) also connects with the OCS (Online Charging System) (422) over the RO (Request-Answer) interface based on a Diameter protocol. This integration facilitates IMS (IP Multimedia Subsystem) online charging for both pre-paid and post-paid subscribers. In an embodiment, the OCS (422) is outside the system (108).
[0077] Furthermore, the IPSMGW (402) communicates with a HSS (Home Subscriber Server) (424) over an SD (Subscriber Data) interface to retrieve user registration data. The IPSMGW (402) integrates with SMPP Content Providers (CP) (414) over a SMPP (Short Message Peer-to-Peer) interface, enabling P2A (Person-to-Application) or A2P (Application-to-Person) SMS services. The A2P IPSMGW (402) connects with the P2P IPSMGW Application over the SMPP interface. This integration facilitates the transfer of SMPP requests from User Equipment (UE) to the A2P IPSMGW Application.
[0078] The IPSMGW (402) also connects with the SCEF (Service Capability Exposure Function) (426) over a T4 (Application Layer Traffic Optimization) interface based on a Diameter protocol. This integration allows the IPSMGW (402) to receive device trigger messages. Additionally, the IPSMGW (402) connects with an MME (Mobility Management Entity) (428) over a SGd (Diameter Routing) interface. These integrations enable the IPSMGW (402) to fetch the terminating IPSMGW address and terminate device trigger messages for users.
[0079] IPSMGW Signalling Frontend: The IPSMGW Signalling Frontend component integrates with a HLR (Home Location Register) or STP (114) over the MAPE (Mobile Application Part-Enhanced) interface. This integration allows the IPSMGW Signalling Frontend to fetch the registration status of end users.
[0080] The IPSMGW Signalling Frontend also integrates with an EMS (Element Management System) (404) over a REST (Representational State Transfer) interface. This integration facilitates the sharing of FCAPS (Fault, Configuration, Accounting, Performance, and Security) data between the IPSMGW Signalling Frontend, IPSMGW Application, and IPSMGW Antispam Manager. It supports fault management, performance management, and configuration management of these nodes. The EMS component integrates with various northbound OSS/BSS (Operations Support System/Business Support System) nodes, such as TeMIP, MyCOM, HPOO, Granite, and DnR. These integrations enable the sharing of FCAPS data with the operations team for effective management of the IPSMGW system.
[0081] In one implementation, a STP (406) and a DRA (420) are provided with the IPSMGW (402). The STP (114) is a MAP router deployed to manage MAP traffic. In one implementation, a database (214) is provided in the processor (202).
[0082] FIG. 5 is a block diagram of a processor in the system of FIG. 1, according to various embodiments of the present disclosure. FIG. 5 illustrates the components and their interactions within the circle-wise GT mapping system, which enables accurate charging for the out roamer users based on their domain.
[0083] In an IPSMGW Node (502): The IPSMGW (IP Short Message Gateway) node (502) serves as the central component of the system, responsible for handling SMS service-related decisions within the IMS (IP Multimedia Subsystem) network. In an implementation, the IPSMGW Node (502) may be the gateway node (216).
[0084] In a PVNI and GT Mapping unit (504): The IPSMGW node (502) maintains a map of the P-visited-network-identifier (PVNI) for all allowed domains, including partner networks and the operator's own network. Each PVNI is associated with the unique GT value.
[0085] In a SIP MESSAGE Request Processing unit (506): When a SIP MESSAGE request is received by the IPSMGW node (502), it checks the PVNI header included in the request. This PVNI header contains information about the visited domain of the user.
[0086] In a GT Selection and Mapping unit (508): Based on the PVNI information extracted from the SIP MESSAGE request, the IPSMGW node (502) identifies the corresponding GT value associated with that PVNI. This GT value will be used for accurate charging.
[0087] In an originator-SCCP-Address Sub-AVP unit (510): The IPSMGW node (502) adds the GT value to the Originator-SCCP-Address Sub-AVP (Attribute Value Pair), which is a component of the SIP message sent to the OCS (Online Charging System).
[0088] In an OCS Differential Charging unit (512): The OCS differential charging unit (512) receives the SIP message from the IPSMGW containing the Originator-SCCP-Address Sub-AVP. The OCS has differential charging information for the GTs associated with different domains. It utilizes this information to correctly charge Out roamer and local users based on their respective GT values.
[0089] The circle-wise GT mapping system ensures accurate charging by mapping PVNI values to GTs, enabling the OCS to differentiate between Out roamer and local users and apply the appropriate charging policies.
[0090] By implementing this system architecture, service providers can prevent revenue loss resulting from insufficient information about Out roamer GTs, thereby improving revenue assurance and customer satisfaction. The described system architecture provides a comprehensive understanding of the components, their interactions, and the inventive step of mapping PVNI to GTs, performed by the IPSMGW node.
[0091] FIG. 6 shows a sequence flow diagram (600) illustrating a method for charging the user in the network (106), according to various embodiments of the present disclosure.
[0092] At 602, the method includes receiving the SIP message from the UE associated with the user. In an embodiment, the method allows the gateway node (216) to receive the SIP message from the UE associated with the user.
[0093] At 604, the method includes extracting the network identifier from the header of the SIP message. The network identifier is associated to the network from which the UE sent the SIP message. In an embodiment, the method allows the extraction module (218) to extract the network identifier from the header of the SIP message.
[0094] At 606, the method includes identifying the GT value from the network identifier by using the map. The map stores the plurality of network identifiers of the plurality of permitted networks and a plurality of GT values. Each network identifier of the plurality of network identifiers is associated with a unique GT value. Each network identifier is associated to a permitted network of the plurality of permitted network. In an embodiment, the method allows the extraction module (218) to identify the GT value from the network identifier by using the map.
[0095] At 608, the method includes identifying the address of the home network (106a) of the UE from the GT value. In an embodiment, the method allows the extraction module (218) to identify the address of the home network (106a) of the UE from the GT value.
[0096] At 610, the method includes adding the GT value in the address of the home network (106a). The GT value is used by the OCS (220) to charge the user for using the network. In an embodiment, the method allows the extraction module (218) to add the GT value in the address of the home network (106a).
[0097] This invention relates a system and method of the circle-wise GT mapping which addresses the challenge of accurately charging Out roamer users in telecommunications networks, specifically in 4G scenarios where the GT information may not be available. By establishing a mapping between the P-Visited-Network-Identifier (PVNI) and GT, the invention enables precise charging based on the user's domain. This mapping is performed within the IPSMGW node (502) of the IP Multimedia Subsystem (IMS) network.
[0098] FIG. 7 is an example flow diagram (700) illustrating the method for Circle-wise GT Mapping process, according to various embodiments of the present disclosure.
[0099] The Circle-wise GT Mapping process enables accurate charging for Out roamer users based on their domain. The method is performed within the IPSMGW (IP Short Message Gateway) node (502) of the IMS (IP Multimedia Subsystem) network.
[00100] At step 702, the IPSMGW node (502) stores the mapping of the PVNI for all allowed domains, including partner networks and the operator's own network. Each PVNI is associated with the unique GT value.
[00101] At step 704, when the IPSMGW node (502) receives the SIP MESSAGE request from a user, it extracts the PVNI header included in the request. The PVNI header contains information about the visited domain of the user.
[00102] At step 706, based on the PVNI information extracted from the SIP MESSAGE request, the IPSMGW node (502) identifies the corresponding GT value associated with that PVNI. This mapping allows the IPSMGW to determine the user's domain.
[00103] At step 708, once the GT value is identified, the IPSMGW adds this GT value to the Originator-SCCP-Address Sub-AVP (Attribute Value Pair) of the SIP message. This ensures that the GT information is included in the message sent to the OCS (220).
[00104] At step 710, the OCS receives the SIP message from the IPSMGW node (502), which contains the Originator-SCCP-Address Sub-AVP with the GT value. The OCS (220) has differential charging information for the GTs associated with different domains. It utilizes this information to correctly charge Out roamer and local users based on their respective GT values.
[00105] The Circle-wise GT Mapping method enables accurate charging by mapping PVNI values to GTs and ensuring the correct application of charging policies by the OCS. By implementing this method, service providers can prevent revenue loss resulting from insufficient information about Out roamer GTs and improve the overall accuracy of charging for users.
[00106] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIGS. 1-7) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[00107] Method steps: A person of ordinary skill in the art will readily ascertain that the illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[00108] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS
[00109] Environment - 100
[00110] UEs– 102, 102-1-102-n
[00111] Server - 104
[00112] Communication network – 106
[00113] Home network - 106a
[00114] Partner network - 106b
[00115] System – 108
[00116] Processor – 202
[00117] Memory – 204
[00118] User Interface – 206
[00119] Display – 208
[00120] Input device – 210
[00121] Centralized Database – 214
[00122] Gateway node – 216
[00123] Extraction module – 218
[00124] Online charging system (OCS) - 220
[00125] Subscriber module - 222
[00126] System - 300
[00127] Primary processors -305
[00128] Memory– 310
[00129] Kernel– 315
[00130] IPSMGW system architecture - 400
[00131] IPSMGW – 402
[00132] EMS – 404
[00133] STP – 406
[00134] SCSCF – 408
[00135] F5 Load balancer – 412, 416
[00136] SMPP CP – 414
[00137] MNP server – 418
[00138] DRA – 420
[00139] OCS – 422
[00140] HSS - 424
[00141] SCEF - 426
[00142] MME – 428
[00143] IPSMGW node – 502
[00144] PVNI and GT mapping unit – 504
[00145] IP MESSAGE request processing unit – 506
[00146] GT selection and mapping unit – 508
[00147] Originator SCCP address sub-AVP unit – 510
[00148] OCS differential charging unit - 512

,CLAIMS:CLAIMS:
We Claim
1. A method of charging a user in a network (106), the method comprising the steps of:
receiving, by one or more processors (202), a Session Initiation Protocol (SIP) message from a user equipment (UE) associated with the user,
extracting, by the one or more processors (202), a network identifier from a header of the SIP message, wherein the network identifier is associated to a network (106) from which the UE sent the SIP message;
identifying, by the one or more processors (202), a global title (GT) value from the network identifier by using a map, wherein the map stores a plurality of network identifiers of a plurality of permitted networks and a plurality of GT values, wherein each network identifier of the plurality of network identifiers is associated with a unique GT value, and wherein each network identifier is associated to a permitted network of the plurality of permitted network;
identifying, by the one or more processors (202), the address of a home network (106a) of the UE from the GT value; and
adding, by the one or more processors (202), the GT value in the address of the home network (106a), wherein the GT value is used by an online charging system (OCS) (220) to charge the user for using the network (106).

2. The method as claimed in claim 1, wherein the network (106) from which the UE sends the SIP message is one of the plurality of permitted networks that the user visits, and wherein the permitted network is one of a partner network (106b) and the home network (106a).

3. The method as claimed in claim 1, wherein the mapping of each network identifier to the unique GT value enables differentiating the user as a local user and a roaming user, wherein the user is considered as the local user in the home network (106a) and is considered as a roaming user in a partner network (106b), and wherein the local user is a subscriber of the home network (106a).

4. The method as claimed in claim 1, wherein the user is considered a roaming user when the GT value indicates the permitted network from which the UE sent the SIP message is different from the home network (106a) of the user, and wherein the user is considered as a local user when the GT value indicates the permitted network from which the UE sent the SIP message is the home network (106a) of the user.

5. The method as claimed in claim 1, wherein the charge applicable for using the network is higher for a roaming user than a local user.

6. The method as claimed in claim 1, wherein a subscriber module (222) is configured to retrieve information related to service usage, charging policies, and profiles of a plurality of users from one or more of a Home Subscriber Server (HSS) (424), a Policy and Charging Rules Function (PCRF), and Service Delivery Platforms (SDPs).

7. The method as claimed in claim 1, wherein the global title (GT) is one of: an alphanumeric code and an unique identifier assigned to a network element, and wherein the unique identifier provides information related to a location and function of the network element.

8. The method as claimed in claim 7, wherein the unique identifier is a global title (GT) assigned to the network element, and wherein the network element is one of a service switching point (SSP), a service control point (SCPs), and short message service centres (SMSCs).

9. A system (108) for charging a user of a network (106), the system (108) comprising:
a gateway node (216) configured to:
store a map of a plurality of network identifiers of a plurality of permitted networks, and a plurality of global title (GT) values, wherein each network identifier of the plurality of network identifiers is associated with a unique GT value, and wherein each network identifier is associated to a permitted network of the plurality of permitted networks; and
receive a Session Initiation Protocol (SIP) message from a user equipment (UE) associated with the user; and
an extraction module (218) configured to:
extract the network identifier from a header of the SIP message, wherein the network identifier is associated to the permitted network from which the UE sent the SIP message;
identify a GT value from the network identifier by using the map;
identify an address of a home network (106a) of the UE from the GT value; and
add the GT value in the address of the home network (106a), wherein the GT value is used by an online charging system (OCS) (220) to charge the user for using the network (106).

10. The system (108) as claimed in claim 9, wherein the UE sends the SIP message to the gateway node (216) from one of the plurality of permitted networks that the user visits, and wherein the permitted network is one of a partner network (106b) and the home network (106a).

11. The system (108) as claimed in claim 9, wherein the mapping of each network identifier from the unique GT value enables differentiating the user as a local user and a roaming user, wherein the user is considered as a local user in the home network (106a) and is considered as a roaming user in a partner network (106b), and wherein the local user is a subscriber of the home network (106a).

12. The system (108) as claimed in claim 9, wherein the user is considered as a roaming user when the GT value indicates the permitted network from which the UE sent the SIP message is different from the home network (106a) of the user, and wherein the user is considered as the local user when the GT value indicates the permitted network from which the UE sent the SIP message is the home network (106a) of the user.

13. The system (108) as claimed in claim 9, wherein the charge applicable for using the network is higher for the roaming user than the local user.

14. A User Equipment (UE) (102-1), comprising:
one or more primary processors (305) communicatively coupled to one or more processors (202) of a system (108), the one or more primary processors (305) coupled with a memory (310), wherein said memory (310) stores instructions which when executed by the one or more primary processors (305) causes the UE (102-1) to:
transmit a SIP message to the one or more processers (202);
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.