Method and system for managing roaming services in a network

Abstract

The disclosure provides a method for managing roaming services associated with a UE 104 in a network 106. A Credit Control Request (CCR) is received by a Charging Function (CHF) (304) from a Session Management Function (SMF) (302). The CHF (304) extracts a PLMN ID from the CCR and evaluates whether the PLMN ID is absent from a list of PLMN IDs. Based on the determination, the CHF (304) identifies the UE (104) as an In-roamer UE. Additionally, the CHF (304) identifies whether a flag is true or false. Upon determining the flag is true, the CHF (304) handles the CCR by generating a Call Detail Record (CDR) and sending the CDR directly to the SMF (302). If the flag is false, the CHF (304) forwards the CCR to the OCS (306) for processing.

Description

METHOD AND SYSTEM FOR MANAGING ROAMING SERVICES IN A NETWORKRESERVATION OF RIGHTS

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

[0002] The present disclosure relates generally to the field of telecommunications. More particularly, the present disclosure relates to a method and a system for managing roaming services associated with a user equipment (UE) in a network.DEFINITION

[0003] The term ‘Network Function (NF)’ as used hereinafter in the specification may refer to a specific software or hardware component within a network that is designed to perform a particular function, such as routing, switching, firewalling, load balancing, traffic optimization, to enable the network operations and enhance performance.

[0004] The term ‘Charging Function (CHF)’ used herein in the specification refers to a network function in a telecommunication network (e.g., a Fifth Generation(5G) core network) that is responsible for managing and applying billing and charging rules in the telecommunication network. The CHF calculates and records charges for network services (i.e., the roaming services) based on data usage and policy rules, enabling accurate billing and financial management.

[0005] The term ‘Session Management Function (SMF)’ used herein in the specification refers to a network function in the telecommunication network that is responsible for session management, including session establishment, modification, and release.

[0006] The term ‘Online Charging System (OCS)’ used herein in the specification refers to a real-time billing system in the telecommunication network that allows network operators to manage and enforce charging policies, in real-time, based on the network services (e.g., data services, voice and video calls, and messaging, etc.) usage by users or customers.

[0007] The term ‘Public Land Mobile Network (PLMN)’ used herein in the specification refers to a network operated by a network operator that offers wireless communication services (i.e., the network services) to the users. The PLMN includes all the necessary infrastructure and equipment, such as base stations, switches, and associated technologies, for providing wireless coverage and connectivity to support a wireless communication, allowing the users to make calls, send messages, and access data services.

[0008] The term ‘Credit Control Request (CCR)’ used herein in the specification refers to a message request sent from the SMF to the CHF or the OCS to check a credit or a balance available for a user in real-time before allowing access to a network service (i.e., a roaming service). The CCR is used to ensure that the user has sufficient funds or credit before allowing access to a requested network service.

[0009] The term ‘Credit Control Answer (CCA)’ used herein in the specification refers to a response received from the OCS or the CHF back to the SMF, in reponse to the CCR. The CCA provides updates on the user's credit and balance, and instructions for handling the requested network service based on a current credit status or account limits for the user.

[0010] The term ‘In-roamers’ used herein in the specification refers to users (or User Equipments (UEs) associated with the users) that are roaming into a network (e.g., a visiting network) from another network (e.g., a home network). The In-roamers access the network services in the visiting network, and the network services usage of the In-roamers is monitored and managed to ensure proper billing and the network service authorization in the visited network.

[0011] These definitions are in addition to those expressed in the art.BACKGROUND

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

[0013] In modern mobile communication networks, managing network services and billing for both local and roaming subscribers is a critical function. When users travel outside their home network and connect to a visited network, they continue to access voice, messaging, and data services. To ensure accurate charging and realtime balance control, mobile operators mostly rely on Online Charging Systems (OCS), which perform credit validations and charging decisions based on service usage.

[0014] In traditional network architectures, all Credit Control Requests (CCRs) generated by users or User Equipments (UEs) associated with the users, such as the CCRs generated from roaming users (e.g., In-roamers), were directed to the OCS for processing. This centralized approach of routing all the CCRs to the OCS ensures that all the CCRs are processed in real-time by the OCS, providing immediate credit control and billing actions for the users. However, this centralized approach led to substantial traffic on the OCS, which introduced several challenges as the OCS had to handle each CCR in real-time.

[0015] Some of the challenges faced by the OCS using the traditional centralized approach include increased traffic load on the OCS, the formation of performance bottlenecks resulting in slower response times for credit control operations, increased network latency, potential congestion within the OCS, higher operational costs necessitating the need for more robust hardware and software infrastructure, limited scalability, inefficiency in handling CCRs, and so on. In particular, the increased volume of CCRs on the OCS not only increased the OCS’s processing load, but also contributed to potential delays and congestion in service operations, impacting overall performance and responsiveness.

[0016] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.SUMMARY OF THE DISCLOSURE

[0017] In an exemplary embodiment, a method for managing one or more roaming services associated with a user equipment (UE) in a network is described. The method includes receiving, by a charging function (CHF), a charging request associated with the UE from a session management function (SMF). The method includes extracting, by the CHF, at least one parameter associated with the received charging request. The method includes determining, by the CHF, fulfilment of at least onecondition associated with the received charging request based on the at least one extracted parameter to identify if the UE is an in-roamer UE. The method includes upon the determination, performing, by the CHF, one or more operative steps for managing the one or more roaming services associated with the identified in roamer UE.

[0018] In some embodiments, the at least one extracted parameter comprises of a Public Land Mobile Network (PLMN) Identifier (ID) associated with the UE.

[0019] In some embodiments, the at least one condition includes determining an absence of the PLMN ID in a list of the PLMN IDs configured at the CHF.

[0020] In some embodiments, the one or more operative steps performed by the CHF include determining a status of a flag configured at the CHF to determine handling of the received charging request in the network. When the determined status of the configured flag is a true status, the received charging request is handled by performing following steps. The steps include generating a first response corresponding to the received charging request. Further, the steps include transmitting the generated first response towards the SMF. When the determined status of the configured flag is a false status, the received charging request is handled by forwarding the received charging request towards an online charging system (OCS).

[0021] In some embodiments, the method further includes forwarding, by the CHF, the at least one received charging request towards the OCS when a presence of the PLMN ID is determined in the configured list of the PLMN IDs.

[0022] In some embodiments, the method further includes processing, by the OCS, the received charging request to generate a second response and transmitting, by the OCS, the generated second response towards the SMF using the CHF.

[0023] In some embodiments, the first response and the second response include one or more call detail records (CDRs) associated with the received charging request.

[0024] In another exemplary embodiment, a system for managing one or more roaming services associated with a user equipment (UE) in a network is described. The system includes a memory and a processing engine coupled to the memory to execute a set of instructions stored in the memory. The processing engine is configured to receive, by a charging function (CHF), a charging request associated with the UE from a session management function (SMF). The processing engine is configured to extract, by the CHF, at least one parameter associated with the received charging request. The processing engine is configured to determine, by the CHF, fulfilment of at least one condition associated with the received charging request based on the at least one extracted parameter to identify if the UE is an in-roamer UE; and upon the determination, the processing engine is configured to perform, by the CHF, one or more operative steps for managing the one or more roaming services associated with the identified in roamer UE.

[0025] In an exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing one or more roaming services associated with a user equipment (UE) in a network. The method includes receiving, by a charging function (CHF), a charging request associated with the UE from a session management function (SMF). The method includes extracting, by the CHF, at least one parameter associated with the received charging request. The method includes determining, by the CHF, fulfilment of at least one condition associated with the received charging request based on the at least one extracted parameter to identify if the UE is an in-roamer UE. Upon the determination, performing, by the CHF, one ormore operative steps for managing the one or more roaming services associated with the identified in-roamer UE.

[0026] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure, and are not restrictive.OBJECTIVES OF THE PRESENT DISCLOSURE

[0027] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0028] An objective of the present disclosure is to provide a method and a system for managing roaming services for In-roamers in a telecommunication network.

[0029] Another objective of the present disclosure is to reduce traffic on an Online Charging System (OCS) by handling certain Credit Control Requests (CCRs) at a Charging Function (CHF) (also referred as a Charging Function-Protocol Convertor (CHF-PC)). This approach of handling the certain CCRs at the CHF decreases number of online CCR triggers to the OCS, thereby alleviating traffic and preventing potential congestion.

[0030] Another objective of the present disclosure is to enhance performance of the OCS by reducing the number of CCRs being sent to the OCS. This reduction of the number of CCRs improves the overall performance of the OCS, leading to faster processing times and better responsiveness for other critical operations.

[0031] Another objective of the present disclosure is to allow the system to handle a growing number CCRs received for the In-roamers without disproportionately increasing the load on the OCS, making the system more scalable. Furthermore, the specialized procedure of handling the certain CCRs at the CHF-PC can be tailored toaddress specific needs and scenarios, providing greater flexibility in handling various types of CCRs and user profiles.

[0032] Another objective of the present disclosure is to improve resource allocation by offloading the certain CCRs to the CHF-PC. This approach of offloading the certain CCRs to the CHF-PC allows the network to allocate resources (e.g., routers, switches, firewalls, bandwidth, etc.) more efficiently, enabling the OCS to focus on more complex or high-priority tasks.

[0033] Another objective of the present disclosure is to provides a structured approach that ensures that the CCRs are efficiently managed, balancing the load between the CHF and the OCS while maintaining consistent charging procedures.

[0034] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0035] 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 is 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.

[0036] FIG. 1 illustrates an exemplary network architecture in which or with a system configured for managing one or more roaming services associated with a user equipment (UE) in a network may be implemented, in accordance with embodiments of the present disclosure.

[0037] FIG. 2 illustrates an exemplary block diagram of the system configured for managing the one or more roaming services associated with the UE in the network, in accordance with embodiments of the present disclosure.

[0038] FIG. 3 illustrates an exemplary system architecture for managing the one or more roaming services associated with the UE in the network, in accordance with an embodiment of the present disclosure.

[0039] FIG. 4 illustrates an exemplary process flow diagram for managing the one or more roaming services associated with the UE in the network, in accordance with an embodiment of the present disclosure.

[0040] FIG. 5 illustrates an exemplary flow diagram of a method for managing the one or more roaming services associated with the UE in the network, in accordance with an embodiment of the present disclosure.

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

[0042] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - User(s)104 - User Equipments (UEs)106 - Network108 - System200 -Block Diagram 202 - Processor(s)204 - Memory206 - Interface(s)208 - Processing Engine210 - Database 300 - System Architecture302 - Session Management Function (SMF)304 - Charging Function (CHF)306 - Online Charging System (OCS)400 - Process Flow Diagram 500 - Method Flow Diagram600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port(S)670 - ProcessorDETAILED DESCRIPTION

[0043] 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 of the 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.

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

[0045] 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 specificdetails. 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.

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

[0047] 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

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

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

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

[0051] Traditionally, all Credit Control Requests (CCRs), including those generated by inbound roaming users (e.g., In-Roamers), were routed to an Online Charging System (OCS) for real-time processing. This centralized method ensured consistent enforcement of charging policies and immediate balance validation for all users, regardless of their network location. While effective for direct control and billing accuracy, this architecture imposed a significant burden on the OCS, particularly as the volume of CCRs increased due to rising numbers of roaming subscribers and data consumption patterns.

[0052] The dependence on real-time communication with the OCS for every CCR introduces several drawbacks. These include increased signaling traffic, higher processing demands on the OCS, and potential delays in charging decisions due to system congestion. As a result, the OCS may experience performance bottlenecks, slower response times, elevated latency in service provisioning, and increased infrastructure costs due to the need for highly scalable OCS deployments. Furthermore, this rigid model lacks flexibility in handling different roaming scenarios, where some requests do not necessarily require real-time OCS interaction.

[0053] In order to manage online triggers and reduce increasing traffic at the OCS for In-roamer CCR requests, the present disclosure provides a method and a system for managing roaming services for In-roamers in the network. In particular, the method relates to the management of roaming services for the In-roamers by enabling the handling of certain CCRs by a Charging Function (CHF), reducing the number of CCRs being sent to the OCS. The present disclosure provides a new approach, in which some CCR requests are processed at the CHF, reducing the number of online triggers to the OCS. Furthermore, the present disclosure improves the overall performance ofthe OCS, leading to faster processing times and better responsiveness for other critical operations. Additionally, the present disclosure allows the system to handle a growing number of In-roamer requests without disproportionately increasing the load on the OCS, making the system more scalable.

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

[0055] FIG. 1 illustrates an exemplary network architecture 100 in which or with which a system 108 configured for managing one or more roaming services associated with a user equipment (UE) 104 in a network 106 may be implemented, in accordance with embodiments of the present disclosure.

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

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

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

[0059] In FIG. 1 , the UE 104 may communicate with the system 108 through a network 106 for sending or receiving various types of data. In an example, the UE 104 may initiate a session or data transaction, which is handled by one or more networkfunctions, such as a Session Management Function (SMF). The SMF may generate a charging-related request that is forwarded to another network function such as the CHF. The CHF may then perform one or more processing steps, such as determining roaming-related parameters and conditions associated with the UE 104. Based on the evaluation, the CHF may choose to process the request internally or forward it to another network function, such as the OCS, thereby enabling efficient handling of the one or more roaming services. The detailed explanation and flow for managing the one or more roaming services are described further with reference to FIG. 2 to FIG. 5.

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

[0061] In an embodiment, the network 106 may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, 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.

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

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

[0064] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 configured for managing the one or more roaming services associated with the UE 104 in the network 106, in accordance with embodiments of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0065] In an embodiment, the system 108 may include one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 108. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packetsover a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

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

[0067] In an embodiment, the system 108 may include a processing engine 208 that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine 208. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine 208 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine 208 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine 208. In such examples, the system 108 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the processing engine 208 may be implemented by electronic circuitry.

[0068] In an embodiment, the processing engine 208 may include a Charging Function (CHF) (also referred to as the Charging Function- Protocol Converter (CHF- PC)).

[0069] In an embodiment, the processing engine 208 is configured to manage the one or more roaming services associated with the UE 104 in the network 106. Examples of the network 106 may include the 4G network, the 5G network, the 6G network, and the like. The one or more roaming services refer to the network services or mobile communication services provided to the UE 104 when the UE 104 is operating outside its home network. Examples of the one or more roaming services may include but are not limited to, billing services, voice calling services, video calling services, messaging services, data services, and the like. In other words, when the UE 104 is in a visited network, the one or more roaming services enable the UE 104 to continue accessing essential mobile services such as voice calling, video calling, messaging, and data connectivity, similar to those available in the home network. The one or more roaming services are facilitated through inter-network agreements and are subject to specific charging, policy enforcement, and service control mechanisms based on the roaming status of the UE 104.

[0070] In an aspect, the visited network or visiting network is a network (i.e., the telecommunication network) that the UE 104 temporarily connects to while travelling outside the home network. For instance, if the user 102 associated with the UE 104 from a network A (i.e., the home network) travels to a location covered by a network B, then the network B is the visiting network for the user 102.

[0071] In an embodiment, the CHF (i.e., the processing engine 208) may be configured to receive a charging request associated with the UE 104 from a session management function (SMF). The charging request is a message that contains information related to the usage of network resources by the UE 104, such as session initiation, modification, or termination details. The charging request may be receivedby the CHF over an internet protocol (IP)-based communication channel that is established between the SMF and the CHF as part of a service-based architecture (SB A) in the 5G network. The SMF initiates the charging request when the user session is created, modified, or terminated. Further, the SMF may send the charging request as a Diameter message encapsulated in a Transmission Control Protocol (TCP) or Stream Control Transmission Protocol (SCTP) transport layer connection. In an example, the charging request may be in the form of the CCR message, which is sent by the SMF over the Diameter-based interface. The CCR message may include attribute- value pairs (A VPs) which provide detailed context about the session established by the UE 104, such as a session identifier (ID), subscriber identity (e.g., Subscription Permanent Identifier (SUPI) or International Mobile Subscriber Identity (IMSI)), IP address, Quality of Service (QoS) parameters, data volume used, and service type (e.g., video, voice, or browsing). Further, the AVPs may also encapsulate information pertaining to the resource consumption associated with the UE 104. The resource consumption refers to metrics like the amount of data transmitted and received by the UE 104, duration of the session, and network bandwidth utilized, which are critical for accurate charging and policy enforcement. In particular, the CCR is a request sent from the SMF to the CHF to check a credit or a balance available for the UE 104 in real-time, before allowing access to the one or more roaming services (e.g., a voice calling service). The CCR is used to ensure that the UE 104 has sufficient balance or credit before allowing access to the one or more roaming services requested by the UE 104.

[0072] In an embodiment, the CHF (i.e., the processing engine 208) may be configured to extract at least one parameter associated with the received charging request. The at least one extracted parameter may comprise of a Public Land Mobile Network (PLMN) Identifier (ID) associated with the UE 104. The PLMN ID is a unique code that depicts the home network of the UE 104. In other words, the PLMN ID is used to identify the network, i.e., the home network from which the UE 104 is originating. The PLMN ID is derived from a first six digits of a Subscription PermanentIdentifier (SUPI). The first six digits of the SUPI typically includes a Mobile Country Code (MCC) and a Mobile Network Code (MNC) associated with the UE 104. In an example, the PLMN ID may be extracted by the CHF from the SUPI provided within the AVPs of the received CCR message. The CHF parses the SUPI to obtain the first six digits, which typically consist of the MCC and the MNC. These components collectively represent the PUMN ID, allowing the CHF to identify the originating home network of the UE 104 for further processing and roaming status determination.

[0073] In some embodiments, the at least one parameter extracted from the charging request may also include additional information such as a service type identifier, specifying whether the session involves data, voice, video, or messaging services, usage metrics, such as volume of data consumed, session duration, or charging rate information, access network type, such as the 4G, the 5G, which may influence charging policy decisions.

[0074] In an embodiment, the CHF may be configured to determine fulfilment of at least one condition associated with the received charging request based on the at least one extracted parameter to identify if the UE 104 is an in-roamer UE. The Inroamers may be defined as users (e.g., the users 102) or the UE (e.g., 104) associated with the users 102 that are roaming into the network (e.g., the visiting network) from another network (e.g., the home network). In an aspect, the at least one condition comprises of determining an absence of the PLMN ID in a list of the PLMN IDs configured at the CHF. In particular, upon receiving the charging request (i.e., the CCR), the CHF is configured to check whether the PLMN ID received with the charging request is present or not present in a list of configured PLMN IDs. In an embodiment, the configured list of PLMN ID is present in a PLMN sheet that is provisioned / configured at CHF end. The list of configured PLMN IDs includes a set of PLMN IDs for visiting networks. Each of the set of PLMN IDs is associated with handling instructions for CCRs managed by the CHF.

[0075] In an example, the CHF determines whether the UE 104 that sent the charging request is the in-roamer UE based on the PLMN ID extracted from the charging request. Upon receiving the CCR from the SMF, the CHF extracts the PLMN ID from the SUPI of the UE 104. In a scenario, if the extracted PLMN ID is 405901, which corresponds to the UE’s home network operator. The CHF compares the extracted PLMN ID with the list of PLMN IDs that is configured at the CHF internally. This list may include PLMN IDs associated with roaming partners or known visiting networks for which certain charging logic is predefined. In this example, let’s assume the list contains PLMN IDs like 405840, 405854, and 405799, but does not include 405901. Because 405901 is not present in the configured list, this satisfies the condition of “absence of PLMN ID” from the list, which is a trigger for in-roamer handling. Thus, through this process of extracting the PLMN ID, verifying its absence from the list of configured PLMN IDs, the CHF accurately identifies the UE 104 as the in-roamer and manages the received charging request accordingly.

[0076] In an embodiment, upon determination that the PLMN ID is absent in the list of PLMN IDs, the CHF is configured to perform one or more operative steps for managing the one or more roaming services associated with the identified in-roamer UE 104. The one or more one or more operative steps performed by the CHF comprises of determining a status of a flag configured at the CHF to determine handling of the received charging request in the network 106. The flag is a configurable control indicator that is configured within the CHF to influence the decision-making logic for processing the receiving charging request. Specifically, the flag, referred to as the Inroamer flag, is used to determine whether the charging request for the identified inroamer UE 104 should be handled locally at the CHF or not. This allows the CHF to optimize charging behaviour based on roaming status, system load, or commercial agreements. In an aspect, the flag may be implemented at the CHF in various forms. Examples of such flag my include but are not limited to a Boolean flag (e.g., true / false), a bitmask or enumerated type flag, and a dynamic runtime flag, that may be determinedbased on real-time data such as system congestion level, charging thresholds, or UE- specific attributes. In some embodiments, the flag may be pre- configured by a network operator based on known roaming agreements or evaluated dynamically by the CHF using the at least one extracted parameter such as the PLMN ID. Further, a status of the flag for the identified In-roamer UE 104 represents whether the identified In-roamer UE 104 is roaming in the visiting network or not.

[0077] In an embodiment, when the determined status of the configured flag is a true status, the received charging request is handled by the CHF by generating a first response corresponding to the received charging request and transmitting the generated first response towards the SMF. The first response comprises of one or more CDRs associated with the received charging request. In an example, upon receiving the charging request (i.e., CCR), the CHF is configured to check whether the status of the flag for the identified In- roamer UE 104 is a true flag status or a false flag status. Further, upon determination that the flag is a true flag status, based on the check performed, the CHF is configured to generate the CDR corresponding to the CCR received from the SMF, for the identified In- roamer UE 104. The CDR is a data record that captures detailed information about the roaming service and an associated session, such as a duration of the roaming service (e.g., the duration of a voice call), a number of participants, a roaming service type (e.g., the voice calling service), billing details, etc. Once the response is generated by the CHF, the CHF is configured to send the response to the SMF.

[0078] In an embodiment, when the determined status of the configured flag is a false status, the received charging request is handled by forwarding the received charging request towards the OCS. The false status of the flag represents a condition where local handling of the received charging request at the CHF is not permitted or not preferred. In an example, after evaluating the flag status, if the flag is false, the CHF forwards the received CCR towards the OCS for online charging.

[0079] In an embodiment, the CHF is configured to forward the received charging request towards the OCS when the presence of the PLMN ID is determined in the configured list of the PLMN IDs. In an example, upon receiving the charging request (e.g., the CCR) from the SMF, the CHF extracts the PLMN ID associated with the UE 104 and checks whether it exists in the list of PLMN IDs maintained at the CHF. If the PLMN ID is found in the list, regardless of the status of the flag, the CHF routes the received charging request to the OCS for centralized processing.

[0080] In an embodiment, the OCS may be included in the processing engine 208. In an embodiment, the OCS may be present within a processing engine of another corresponding system that is in communication with the system 108. In another embodiment, the CHF may be present within the processing engine 208 of the system 108, while the OCS may be present within a processing engine of another system. In some embodiments, the CHF and the OCS may be present within the processing engine 208 of the system 108.

[0081] In an embodiment, the OCS may be configured to process the received charging request to generate a second response. The generated second response is the CDR. The OCS processes the charging request (e.g., CCR) by evaluating various parameters such as the subscriber’s account status, tariff plans, usage quotas, and service type involved. Based on this evaluation, the OCS applies pre-defined charging rules and policies to authorize the session and simultaneously generate the CDR. In an embodiment, the generated second response may also be referred to as a Credit Control Answer (CCA). Further, the OCS is configured to transmit the generated second response towards the SMF using the CHF.

[0082] FIG. 3 illustrates an exemplary system architecture 300 for managing the one or more roaming services associated with the UE 104 in the network 106, in accordance with an embodiment of the present disclosure. FIG. 3 is described in conjunction with FIGs 1 and 2.

[0083] The exemplary system architecture 300 includes the SMF 302, the CHF 304, and the OCS 306 for managing the one or more roaming services for the UE 104 in the network 106.

[0084] At step 308, the SMF 302 is configured to transmit a charging request (CCR-1) associated with the UE 104 towards the CHF 304. Upon receiving the charging request, the CHF 304 extracts the at least one parameter such as the PLMN ID associated with the received charging request. In an embodiment, the PLMN ID is derived from the first six digits of the SUPI included in the charging request. Further, upon receiving the CCR-1, the CHF 304 is configured to check whether the PLMN ID received with the CCR-1 is present in the configured list of the PLMN IDs.

[0085] At step 310, upon determining that the PLMN ID is not present (absent) in the configured list of the PLMN IDs, the CHF 304 is configured to determine that the UE 104 is an in-roamer UE. In an embodiment, the CHF 304 is configured to check the status of the in-roamer flag as the true flag status. Based on the check performed, when the PLMN ID is determined to be absent in the list of configured PLMN IDs, and the flag status is determined to be the true flag status, the CHF 304 is configured to process the CCR-1 to generate a response (Response- 1) for the received CCR-1. In an embodiment, the Response- 1 may include the CDR for the received CCR-1. Once the Response- 1 is generated, the CHF 304 is configured to send the response- 1 to the SMF 302.

[0086] At step 312, the SMF 302 is configured to transmit charging request (CCR-2) towards the CHF 304.

[0087] At step 314, upon receiving the CCR-2, the CHF 304 extracts the at least one parameter such as the PLMN ID associated with the UE 104. Further, upon receiving the CCR-2, the CHF 304 is configured to check that the PLMN ID is absent in the configured list of the PLMN IDs and the status of the in-roamer flag as the falseflag status. Based on the check performed, the CHF 304 is configured to forward the CCR-2 to the OCS 306. Further, the OCS 306 is configured to process the CCR-2 to generate a second response, such as response-2 (e.g., the CDR), for the CCR-2 received from the CHF 304.

[0088] By way of another example, when the PLMN ID corresponding to the CCR received at the CHF 304 is determined to be present in the list of configured PLMN IDs, then the check for the flag status is not performed. In this case, the CHF 304 may directly forward the CCR to the OCS 306 for generating the CDR.

[0089] At step 316, once the Response-2 for the CCR-2 is generated, the OCS 306 forwards the Response-2 towards the CHF 304.

[0090] At step 318, the CHF 304 is configured to forward the Response-2 to the SMF 302.

[0091] FIG. 4 illustrates an exemplary process flow 400 diagram for managing the one or more roaming services associated with the UE 104 in the network 106, in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIGS. 1, and 3.

[0092] The process flow 400 for managing the one or more roaming services associated with the UE 104 starts at step 402.

[0093] Initially, at step 404, the SMF 302 sends the charging request (i.e., the CCR) received corresponding to the UE 104 to the CHF 304.

[0094] At step 406, the CHF 304 receives the CCR from the SMF 302. The CCR corresponds to the UE 104 may include the PLMN ID. Upon receiving the CCR, the CHF 304 is configured to perform the check to determine the successful fulfilmentof at least one condition, i.e., the absence of the PLMN ID in the list of configured PLMN IDs.

[0095] In particular, upon receiving the CCR, at step 408, the CHF 304 is configured to perform the check to determine whether the PLMN ID associated with the CCR is present in the configured list PLMN IDs, or not. In one embodiment, based on the check performed at step 408, when the absence of the PLMN ID in the configured list of PLMN IDs is determined, then the step 410 is executed.

[0096] At step 410, the check is performed to determine whether the status of the flag (also referred to as an In-roamer flag) is the true flag status or the false flag status for the UE 104 for whom the CCR is received. In an embodiment, the flag status is determined to be the true flag status when the UE 104 is identified as the In-roamer UE i.e., the UE 104 is roaming in the visiting network (e.g., an external network). Further, the flag status is determined to be the false flag status when the UE is not roaming (or is not present) in the visiting network.

[0097] Further, based on the check performed at step 410, when the flag status is determined to be the true flag status, at step 412, the CHF 304 is configured to generate the response, i.e., the CDR for the CCR. In this embodiment, the CHF 304 generates the response as the at least one condition (i.e, the absence of the PLMN ID in the list of configured PLMN IDs) is successfully fulfilled.

[0098] At step 414, the CHF 304 send the response generated for the CCR to the SMF 302.

[0099] In another embodiment, based on the check performed at step 408, when the absence of the PLMN ID in the list of configured PLMN IDs is determined, then at step 410 the check is performed to determine whether the flag is the true flag status or the false flag status. In this embodiment, based on the check performed at step 410, when the flag status is determined to be the false flag status, then step 418 may beexecuted. In yet another embodiment, based the check performed at step 408, when the presence of the PLMN ID in the list of configured PLMN IDs is determined, then step 418 may be executed.

[0100] At step 418, the CHF 304 is configured to direct the CCR to the OCS 306. The OCS 306 is configured to process the CCR to generate the response, i.e., the CDR (also referred as the CCA) for the received CCR.

[0101] Once the response for the CCR is generated by the OCS 306, at step 420, the OCS 306 is configured to send the response to the CHF 304. Once the OCS 306 sends the response to the CHF 304, the CHF 304 forwards the response to the SMF 302 as mentioned in step 414.

[0102] Once the SMF receives the response for the CCR, then the process flow 400 ends as mentioned in step 416.

[0103] FIG. 5 illustrates another exemplary flow diagram of a method500 for managing the one or more roaming services associated with the UE 104 in the network 106, in accordance with an embodiment of the present disclosure. FIG. 5 is explained with reference to FIG.1, FIG. 2, and FIG. 3.

[0104] At step 502, the method 500 includes receiving, by a charging function (CHF) 304, a charging request associated with the UE 104 from a session management function (SMF) 302.

[0105] At step 504, the method 500 includes extracting, by the CHF 304, at least one parameter associated with the received charging request. The at least one extracted parameter comprises of a Public Land Mobile Network (PLMN) Identifier (ID) associated with the UE 104.

[0106] At step 506, the method 500 includes determining, by the CHF 304, fulfilment of at least one condition associated with the received charging request based on the at least one extracted parameter to identify if the UE 104 is an in-roamer UE. The at least one condition comprises of determining an absence of the PLMN ID in a list of the PLMN IDs configured at the CHF 304.

[0107] At step 508, the method 500 includes, upon the determination, performing, by the CHF 304, one or more operative steps for managing the one or more roaming services associated with the identified in-roamer UE 104. The one or more operative steps performed by the CHF 304 comprise: determining a status of a flag configured at the CHF 304 to determine handling of the received charging request in the network 106. When the determined status of the configured flag is a true status, the received charging request is handled by generating a first response corresponding to the received charging request and transmitting the generated first response towards the SMF. When the determined status of the configured flag is a false status, the received charging request is handled by forwarding the received charging request towards an online charging system (OCS) 306.

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

[0109] As shown in FIG. 6, the computer system 600 may include an external storage device 610, a bus 620, a main memory 630, a read-only memory 640, a mass storage device 650, a communication port(s) 660, and a processor 670. A person skilled in the art will appreciate that the computer system 600 may include more than one processor and communication ports. The processor 670 may include various modules associated with embodiments of the present disclosure. The communication port(s) 660 may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) 660 may be chosendepending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.

[0110] In an embodiment, the main memory 630 may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 640 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor 670. The mass storage device 650 may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PAT A) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

[0111] In an embodiment, the bus 620 may communicatively couple the processor(s) 670 with the other memory, storage, and communication blocks. The bus 620 may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 670 to the computer system 600.

[0112] In another embodiment, operator, and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus 620 to support direct operator interaction with the computer system 600. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 660. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 600 limit the scope of the present disclosure.

[0113] In an exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing one or more roaming services associated with a user equipment (UE) in a network. The method includes receiving, by a charging function (CHF), a charging request associated with the UE from a session management function (SMF). The method includes extracting, by the CHF, at least one parameter associated with the received charging request. The method includes determining, by the CHF, fulfilment of at least one condition associated with the received charging request based on the at least one extracted parameter to identify if the UE is an in-roamer UE. Upon the determination, performing, by the CHF, one or more operative steps for managing the one or more roaming services associated with the identified in-roamer UE.

[0114] The present disclosure provides a technical advancement in the field of network charging and roaming service management. By introducing a dynamic and intelligent method of handling charging requests based on parameters such as the PLMN ID and an in-roamer identification flag, the system enables selective routing of charging requests either locally at the Charging Function (CHF) or towards the Online Charging System (OCS). This conditional routing mechanism reduces unnecessary signaling traffic to the OCS, thereby improving system efficiency and scalability. The use of configurable flags and PLMN ID mapping allows for flexible charging behavior tailored to specific network and user scenarios, especially for in-roaming subscribers. Additionally, by enabling localized decision-making at the CHF for eligible cases, the system enhances processing speed, reduces latency, and lowers the risk of OCS congestion. Overall, the disclosure offers an optimized charging architecture that balances load distribution, improves operational efficiency, and ensures consistent enforcement of charging policies across varying roaming conditions.

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

[0116] The present disclosure described herein above has several technical advantages as follows:

[0117] The present disclosure provides a method and a system for managing roaming services associated with a user equipment (UE) in a network.

[0118] The present disclosure reduces traffic on an Online Charging System (OCS) by handling certain Credit Control Requests (CCRs) at a Charging Function (CHF) (also referred as a Charging Function-Protocol Convertor (CHF-PC)). This approach of handling the certain CCRs at the CHF decreases number of online CCR triggers to the OCS, thereby alleviating traffic and preventing potential congestion.

[0119] The present disclosure provides enhancement in performance of the OCS by reducing the number of CCRs being sent to the OCS. This reduction of the number of CCRs improves the overall performance of the OCS, leading to faster processing times and better responsiveness for other critical operations.

[0120] The present disclosure allows the system to handle a growing number CCRs received for the In- roamers without disproportionately increasing the load on the OCS, making the system more scalable. Furthermore, the specialized procedure of handling certain CCRs at the CHF-PC can be tailored to address specific needs andscenarios, providing greater flexibility in handling various types of CCRs and user profiles.

[0121] The present disclosure improves resource allocation by offloading the certain CCRs to the CHF-PC. This approach of offloading the certain CCRs to the CHF-PC allows the telecommunication network to allocate resources (e.g., routers, switches, firewall, bandwidth, etc.) more efficiently, enabling the OCS to focus on more complex or high-priority tasks.

[0122] The present disclosure provides a structured approach that ensures that the CCRs are efficiently managed, balancing the load between the CHF and the OCS while maintaining consistent charging procedures.

Claims

CLAIMSWe claim:

1. A method (500) for managing one or more roaming services associated with a user equipment (UE) (104) in a network (106), the method (500) comprising: receiving (502), by a charging function (CHF) (304), a charging request associated with the UE (104) from a session management function (SMF) (302); extracting (504), by the CHF (304), at least one parameter associated with the received charging request; determining (506), by the CHF (304), fulfilment of at least one condition associated with the received charging request based on the at least one extracted parameter to identify if the UE (104) is an in-roamer UE; and upon the determination, performing (508), by the CHF (304), one or more operative steps for managing the one or more roaming services associated with the identified in-roamer UE.

2. The method (500) as claimed in claim 1, wherein the at least one extracted parameter comprises of a Public Land Mobile Network (PLMN) Identifier (ID) associated with the UE (104).

3. The method (500) as claimed in claim 1, wherein the at least one condition comprises of: determining an absence of the PLMN ID in a list of the PLMN IDs configured at the CHF (304).

4. The method (500) as claimed in claim 1, wherein the one or more operative steps performed by the CHF (304) comprises of:determining a status of a flag configured at the CHF (304) to determine handling of the received charging request in the network; when the determined status of the configured flag is a true status, the received charging request is handled by performing following steps: generating a first response corresponding to the received charging request; transmitting the generated first response towards the SMF (302); and when the determined status of the configured flag is a false status, the received charging request is handled by forwarding the received charging request towards an online charging system (OCS) (306).

5. The method (500) as claimed in claim 4, further comprising of: forwarding, by the CHF (304), the at least one received charging request towards the OCS (306) when a presence of the PLMN ID is determined in the configured list of the PLMN IDs.

6. The method (500) as claimed in 4, further comprising of: processing, by the OCS (306), the received charging request to generate a second response; and transmitting, by the OCS (306), the generated second response towards the SMF (302) using the CHF (304).

7. The method (500) as claimed in claim 4, wherein the first response and the second response comprises of one or more call detail records (CDRs) associated with the received charging request.

8. A system (108) for managing one or more roaming services associated with a user equipment (UE) (104) in a network (106), the system (108) comprising:a memory (204); and a processing engine (208) coupled to the memory (204) to execute a set of instructions stored in the memory (204), the processing engine (208) is configured to: receive, by a charging function (CHF) (304), a charging request associated with the UE from a session management function (SMF) (302); extract, by the CHF (304), at least one parameter associated with the received charging request; determine, by the CHF (304), fulfilment of at least one condition associated with the received charging request based on the at least one extracted parameter to identify if the UE (104) is an in-roamer UE; and upon the determination, perform, by the CHF (304), one or more operative steps for managing the one or more roaming services associated with the identified in-roamer UE.

9. The system (108) as claimed in claim 8, wherein the at least one extracted parameter comprises a Public Land Mobile Network (PLMN) Identifier (ID) associated with the UE (104).

10. The system (108) as claimed in claim 8, wherein the at least one condition comprises of: determining an absence of the PLMN ID in a list of the PLMN IDs configured at the CHF (304).

11. The system (108) as claimed in claim 8, wherein for the one or more operative steps performed by the CHF (304) comprises of: determine a status of a flag configured at the CHF (304) to determine handling of the received charging request in the network;when the determined status of the configured flag is a true status, the received charging request is handled by performing following steps: generate a first response corresponding to the received charging request; transmit the generated first response towards the SMF (302); and when the determined status of the configured flag is a false status, the received charging request is handled by forwarding the received charging request towards an online charging system (OCS) (306).

12. The system (108) as claimed in claim 11, further configured to forward, by the CHF (304), the at least one received charging request towards the OCS (306) when a presence of the PLMN ID is determined in the configured list of the PLMN IDs.

13. The system (108) as claimed in claim 11, further configured to: process, by the OCS (306), the received charging request to generate a second response; and transmit, by the OCS (306), the generated second response towards the SMF (302) using the CHF (304).

14. The system (108) as claimed in claim 11, wherein the first response and the second response comprises of one or more call detail records (CDRs) associated with the received charging request.

15. A computer program product comprising a non -transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (500) formanaging one or more roaming services associated with a user equipment (UE) (104) in a network (106), the method (500) comprising: receiving (502), by a charging function (CHF) (304), a charging request associated with the UE (104) from a session management function (SMF) (302); extracting (504), by the CHF (304), at least one parameter associated with the received charging request; determining (506), by the CHF (304), fulfilment of at least one condition associated with the received charging request based on the at least one extracted parameter to identify if the UE (104) is an in-roamer UE; and upon the determination, performing (508), by the CHF (304), one or more operative steps for managing the one or more roaming services associated with the identified in-roamer UE.

Images