System and method for tracing location of a subscriber in a network

Abstract

A method (700) for tracing location of a subscriber in a network (106) is disclosed. The method (700) includes receiving (602), at a provisioning node (212), a first customized request from a visited network node (226A). The provisioning node (212) parses the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber. The provisioning node (212) receives a second customized request from the visited network node (226A). The provisioning node (212) parses the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI. The provisioning node (212) stores the extracted SUPI, the extracted GPSI, and the roaming parameters in a database (210), The provisioning node (212) provides the one or more stored roaming parameters in response to a location information retrieval request for the SUPI or the GPSI to a requesting node (218).

Description

SYSTEM AND METHOD FOR TRACING LOCATION OF A SUBSCRIBER 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 generally relates to the field of telecommunication networks. More particularly, the present disclosure relates to a system and a method for tracing a location of an international subscriber in a network.DEFINITION

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

[0004] The expression “Network Function (NF)” used hereinafter in the specification refers to a software-based component that executes specific network tasks within a telecom network, including but not limited to functions related to authentication, authorization, location tracing, and session management. The NFs canbe instantiated and scaled dynamically, allowing for flexible network management and optimization in both 4G and 5G architectures.

[0005] The expression “International In-roamer Register (HR)” used hereinafter in the specification refers to a specialized network node that stores and manages the roaming data of international subscribers who are visiting a network. The HR facilitates the retrieval of critical information such as subscriber identity, location, and mobility data, enabling accurate location tracing and communication with the home network of the international in-roamer subscriber.

[0006] The expression “Diameter Edge Agent (DEA)” used hereinafter in the specification refers to a network function responsible for routing and managing diameter protocol messages at the edge of the network. The DEA serves as an intermediary that handles authentication, authorization, and accounting requests, ensuring secure and efficient communication between the visited network and external entities.

[0007] The expression “Gateway Mobile Location Centre (GMLC)” used hereinafter in the specification refers to a network node that manages the retrieval of location information for mobile subscribers. The GMLC interfaces with various network elements to obtain and provide accurate location data, supporting services such as emergency calls, location-based services, and lawful interception.

[0008] The expression “Diameter Routing Agent (DRA)” used hereinafter in the specification refers to a network component that optimizes the routing of diameter messages within the telecom network. The DRA ensures that messages are directed to the appropriate nodes, such as the DEA, GMLC, and HR, thereby reducing network congestion, improving response times, and enhancing overall network efficiency.

[0009] The expression “Mobility Management Entity (MME)” used hereinafter in the specification refers to a key control node in the network responsible for handlingsignalling related to mobility and session management. The MME coordinates with other network functions to manage handovers, attach / detach procedures, and bearer activation / deactivation for the subscribers.

[0010] The expression “Service Communication Proxy (SCP)” used hereinafter in the specification refers to a network function that acts as a communication facilitator, routing, and balancing a Hyper Text Transfer Protocol (HTTP) message in the network. The SCP plays a critical role in ensuring efficient and secure message routing between network functions, including facilitating communication between visited and home network entities.

[0011] The expression “Security Edge Protection Proxy (SEPP)” used hereinafter in the specification refers to a security-focused network function that protects and manages the inter-network interfaces between the visited and home networks. The SEPP ensures secure communication by encrypting and decrypting messages, thereby maintaining the confidentiality and integrity of data exchanged across network boundaries.

[0012] The expression “Unified Data Management (UDM)” used hereinafter in the specification refers to a central data repository in the 5G network that stores and manages subscriber-related information, including profiles, authentication credentials, and service subscriptions. The UDM facilitates access to this data by various network functions to support subscriber services, authentication, and policy management.

[0013] The expression “Access and Mobility Management Function (AMF)” used hereinafter in the specification refers to a core network function in the network that handles signalling related to access, mobility management, and connection setup. The AMF coordinates with the UDM and other network functions to manage registration, connection establishment, handovers, and session continuity for mobile subscribers.

[0014] The expression “Subscription Permanent Identifier (SUPI)” used hereinafter in the specification refers to a unique identifier assigned to each mobile subscriber in the network. The SUPI is used to identify and authenticate the subscriber within the network and is typically stored in the UDM. It is designed to be globally unique, allowing for efficient and secure subscriber identification, especially in scenarios involving roaming between different network operators.

[0015] The expression “Generic Public Subscription Identifier (GPSI)” used hereinafter in the specification refers to an identifier used to publicly reference a subscriber in the network. The GPSI is derived from the SUPI and is used for services that do not require the full security of the SUPI, such as making a voice call or sending a text message. The GPSI allows for a level of privacy protection by providing a public identifier that can be mapped to the SUPI without exposing the SUPI itself.

[0016] The expression “Visited Gateway Mobile Uocation Centre (V-GMLC)” used hereinafter in the specification refers to a network function deployed in a visited PUMN to provide gateway support for location-based services (UBS) in relation to roaming subscribers. The V-GMLC is configured to receive identifiers, such as the Subscription Permanent Identifier (SUPI) and the Generic Public Subscription Identifier (GPSI), along with dynamic roaming parameters from the IIR node. Based on this information, the V-GMLC establishes communication with serving network functions (e.g., AMF, SMF) to determine or refine the geographical location of the roaming subscriber. The V-GMLC thereby supports enhanced location-based services, emergency call handling, and regulatory compliance requirements within the visited network.

[0017] The expression “Visited Access and Mobility Management Function (V-AMF)” used hereinafter in the specification refers to a logical network function residing in the visited Public Land Mobile Network (VPLMN) and is responsible for managing access and mobility procedures for a roaming user equipment (UE),including registration, connection management, and mobility handling within the visited network domain. The V-AMF communicates with the Home AMF (H-AMF) in the UE’s Home PLMN (HPLMN) to perform authentication, subscription retrieval, and service authorization, while locally managing access network interactions, such as RAN signaling and the UE context establishment. The V-AMF supports interworking with other core network functions, including the SMF, Policy Control Function (PCF), and Network Slice Selection Function (NSSF), and plays a key role in enabling efficient and secure access for roaming users, consistent with operator policies and roaming agreements.

[0018] The expression “Home-Unified Data Management (H-UDM)” used hereinafter in the specification refers to a centralized network function within a subscriber’s home network that securely stores and manages subscriber profiles, authentication credentials, and service subscriptions in the 5G system, enabling other network functions to access this data for authentication, session management, and policy enforcement.

[0019] The expression “Network Slice Selection Assistance Information (NS SAI)” used hereinafter in the specification refers to a data element used in 5G networks to assist in selecting the appropriate network slice for a user. It consists of one or more Single Network Slice Selection Assistance Information (S-NSSAI) identifiers, each representing a specific network slice characterized by particular network capabilities and services. The NSSAI enables the 5G core and access network to efficiently route and manage user traffic according to the subscriber’s subscription and service requirements, ensuring tailored quality of service and resource allocation.

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

[0021] 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 reader's understanding with respect to the present disclosure, and not as admissions of prior art.

[0022] With the rapid adoption of 5G networks, there has been an increase in international roaming, which allows subscribers to use their mobile devices in foreign networks. These international in-roamer subscribers connect to the visited 5G network while still being managed by their home network subscriber management system. Traditionally, location of such roaming subscribers is tracked using various network components, including an Access and Mobility Management Function (AMF) and a Unified Data Management (UDM) system.

[0023] In existing 4G network, the International In-Roamer Register (IIR) facilitates the tracing of international roaming subscribers by interfacing with a Mobility Management Entity (MME) to retrieve and manage subscriber location information. This approach has been successful in enabling 4G networks to provide accurate location data for in-roamer subscribers.

[0024] However, the transition to 5G networks introduces new complexities and requirements for tracing location, particularly for international in-roamer subscribers. In a typical 5G international roaming scenario, the AMF and a Gateway Mobile Location Centre (GMLC) of a visited network handle subscriber management, while the UDM resides in the home network of the international operator to which the subscriber belongs. One of the key challenges arises from the fact that the current 5Groaming guidelines do not specify use of a standardized interface between the 5G GMLC and the UDM hosted in the home network of international operators.

[0025] The absence of the standardized interface for direct communication between the GMLC of the visited network and the UDM of the home network presents a significant challenge for tracing location of an international in-roamer subscribers. Without the standardized interface, it becomes difficult for the serving 5G operator to accurately determine the current location of international subscribers under lawful interception or other regulatory compliance scenarios. This gap in communication can lead to compliance issues with Lawful Enforcement Agencies (LEAs), which require precise and real-time location data for lawful interception purposes.

[0026] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.OBJECTIVE

[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 system and a method for tracing a location of an international in-roamer register (HR) subscriber in a network.

[0029] Another objective of the present disclosure is to provide the system and the method that enables extraction of a Generic Public Subscription Identifier (GPSI), when available, from an Access and Mobility Subscription Data Retrieval response, and maintaining a mapping between the GPSI and a Subscription Permanent Identifier (SUPI) of the subscriber.

[0030] Another objective of the present disclosure is to provide the system and the method that ensures accurate location information retrieval for regulatory and lawful interception purposes, ensuring that operators can comply with regulatory requirements without violating international agreements.

[0031] Another objective of the present disclosure is to provide the system and the method for enhancing the security and privacy of the international in-roamer subscriber data by minimizing the transmission of sensitive information between networks.

[0032] Another objective of the present disclosure is to provide the system and the method for enhancing efficiency of international roaming operations by minimizing signaling overhead and avoiding explicit identifier translation queries to a home network entity.

[0033] Another objective of the present disclosure is to provide the system and the method that supports error handling when GPSI is unavailable, thereby ensuring robust and predictable responses to lawful location queries.

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

[0035] In an exemplary embodiment, a method for tracing location of a subscriber in a network is disclosed. The method includes receiving, at a provisioning node, a first customized request from a visited network node. The method includes parsing, by the provisioning node, the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber. The method includes receiving, by the provisioning node, a secondcustomized request from the visited network node. The method includes parsing, by the provisioning node, the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI. The method includes storing, by the provisioning node, the extracted SUPI, the extracted GPSI, and the one or more roaming parameters in a database. The method includes providing, by the provisioning node, the one or more stored roaming parameters in response to a location information retrieval request for the SUPI or the GPSI to a requesting node, to enable tracing the location of the subscriber.

[0036] In an embodiment, wherein the first customized request includes an Access and Mobility Management Function (AMF) access registration request and an AMF access registration response exchanged between a visited- AMF (V-AMF) and a home network node of the subscriber.

[0037] In an embodiment, wherein the second customized request includes an Access and Mobility Subscription Data Retrieval request and an Access and Mobility Subscription Data Retrieval response exchanged between the V-AMF and the home network node. The provisioning node extracts the GPSI from the Access and Mobility Subscription Data Retrieval response when the GPSI is present and stores the GPSI to the SUPI in the database.

[0038] In an embodiment, the provisioning node maintains a mapping between the SUPI and the GPSI when the GPSI is present in the second customized request.

[0039] In an embodiment, the one or more dynamic roaming parameters comprises additional location identifying parameters including an Access and Mobility Management Function (AMF) instance identifier, deregistration callback Uniform Resource Identifier (URI), global unique AMF identifier, radio access technology type, and, a permanent equipment identifier.

[0040] In an embodiment, providing the stored roaming parameters comprises receiving, by the provisioning node, an access registration information retrieval request from the requesting node through the visited network node, wherein the access registration information retrieval request includes the SUPI or the GPSI of the subscriber. The provisioning node retrieves the one or more stored dynamic roaming parameters from the database based on the SUPI or the GPSI. The provisioning node transmits an access registration information retrieval response to the requesting node through the visited network node, wherein the access registration information retrieval response comprising the stored one or more dynamic roaming parameters.

[0041] In an embodiment, the provisioning node generates an error response to the requesting node through the visited network node when the access registration information retrieval request is based on the GPSI that is not mapped to the SUPI in the database.

[0042] In an embodiment, wherein the provisioning node updates the stored dynamic roaming parameters and mapping between the SUPI and the GPSI in the database upon receiving updated information related to the subscriber.

[0043] In an exemplary embodiment, a system for tracing location of a subscriber in a network is disclosed. The system includes a provisioning node configured to receive a first customized request from a visited network node. The provisioning node parses the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber. The provisioning node receives a second customized request from the visited network node. The provisioning node parses the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI. The provisioning node stores the extracted SUPI, the extracted GPSI and the one or more roaming parameters in a database. The provisioning node provides the one or more stored roaming parameters in response to a location information retrieval request forthe SUPI or the GPSI to a requesting node, to enable tracing the location of the subscriber.

[0044] In an exemplary embodiment, a computer program product includes a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for tracing location of a subscriber in a network is disclosed. The method includes receiving, at a provisioning node, a first customized request from a visited network node. The method includes parsing, by the provisioning node, the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber. The method includes receiving, by the provisioning node, a second customized request from the visited network node. The method includes parsing, by the provisioning node, the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI. The method includes storing, by the provisioning node, the extracted SUPI, the extracted SUPI, and the one or more roaming parameters in a database. The method includes providing, by the provisioning node, the one or more stored roaming parameters in response to a location information retrieval request for the SUPI or the GPSI to a requesting node, to enable tracing the location of the subscriber.

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

[0046] 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 toscale 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.

[0047] FIG. 1 illustrates an exemplary network architecture for tracing location of a subscriber in a network, in accordance with an embodiment of the present disclosure.

[0048] FIG. 2A illustrates an exemplary system architecture for tracing the location of the subscriber in the network, in accordance with an embodiment of the present disclosure.

[0049] FIG. 2B illustrates an exemplary block diagram of a system tracing the location of the subscriber in the network, in accordance with an embodiment of the present disclosure.

[0050] FIG. 3 illustrates an exemplary flowchart for a first customized request, in accordance with an embodiment of the present disclosure.

[0051] FIG. 4 illustrates another exemplary flowchart for a second customized request, in accordance with an embodiment of the present disclosure.

[0052] FIG. 5 illustrates another exemplary flowchart of an Access and mobility management function (AMF) access registration information retrieval request / response, in accordance with an embodiment of the present disclosure.

[0053] FIG. 6 illustrates yet another exemplary flowchart of the method for tracing the location of the subscriber in the network, in accordance with an embodiment of the present disclosure.

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

[0055] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102- 1 , 102-2... 102-N - Plurality of Users104- 1 , 104-2... 104-N - Plurality of User Equipments106 - Network108 - System200A - System architecture202 - Processors204 - Memory206 - Interface(s)208 - Processing engine210 - Database200B - Block diagram212 - International In-roamer Register (IIR) server / Provisioning node214A - Visited-Diameter Edge Agent (V-DEA)214B - Home-Diameter Edge Agent (H-DEA)216 - Visited-Diameter Routing Agent (V-DRA) 218 - Visited-Gateway Mobile Location Centre (V-GMLC) / requesting node220 - Visited-4G / 5G network222 - Visited-Mobility Management Entity (V-MME)224A- Visited-Other network elements / Unified Data Management (V-UDM)224B- Home-Other network elements / Unified Data Management (H-UDM) / home network node226A - Visited-Service Communication Proxy (V-SCP) / visited network node226B - Home-Service Communication Proxy (H-SCP)228A - Visited-Security Edge Protection Proxy (V-SEPP)228B - Home-Security Edge Protection Proxy (H-SEPP) 230 - Home 4G / 5G network300 - Flow diagram400 - Flow diagram500 - Flow diagram600 - Method flow diagram700 - Computer system710 - External storage device720 - Bus730 - Main memory740 - Read-only memory750 - Mass storage device760 - Communication port(s)770 - ProcessorDETAILED DESCRIPTION

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

[0057] 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 theart 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.

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

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

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

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

[0062] 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 “includes” 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 otherequivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

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

[0064] International roaming in fifth-generation (5G) networks allows subscribers from a home network to connect to services in a visited network. In such roaming scenarios, for tracing location of international in-roamer subscribers is a regulatory requirement for Lawful Enforcement Agencies (LEAs). While in a visited 5G network, the Access and Mobility Management Function (AMF) and a location management node handle the subscriber, whereas subscription data remains in the home network’s subscriber database. The current 5G roaming guidelines do not provide for a direct standardized interface between the location management node of the visited network and the subscriber database of the home network, creating challenges for retrieving real-time location information of roaming subscribers.

[0065] Therefore, there is a need for systems and methods to enable the visited network to trace the location of international in-roamer subscribers without relying on direct integration with the home network subscriber database.

[0066] The present disclosure provides a system and a method for tracing the location of international in-roamer subscribers in a 5G network. The system introduces a provisioning node that receives customized registration and subscription datarequests forwarded by a proxy in the visited network. The provisioning node extracts identifiers such as the Subscription Permanent Identifier (SUPI) and, when available, a Generic Public Subscription Identifier (GPSI), along with dynamic roaming parameters of the subscriber, and stores them in a database. When a lawful query is made by a location management node in the visited network, the provisioning node provides the stored roaming parameters to enable accurate and regulatory-compliant location tracing of international in-roamer subscribers.

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

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

[0069] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (108) for tracing a location of the subscriber in the network (106), in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the network architecture (100) may include one or more computing devices or 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 individually referred to as the user (102) and 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 individually referred to as the UE (104) and collectively referred to as the UEs (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three UEs (104) are depicted in FIG. 1, however, any number of the UEs (104) may be included without departing from the scope of the ongoing description.

[0070] 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 is not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical sensor, a thermal sensor, an electrical sensor, a magnetic sensor, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart televisions (TVs), computers, smart security systems, smart home systems, other devices for monitoring or interacting with or for the user (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 is not limited to, intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0071] In an embodiment, the UE (104) may include, but is 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), the GPSI 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 is 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, 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 touch pad,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.

[0072] In FIG. 1, the UE (104) may communicate with the system (108) through the network (106). In particular, the UE (104) may be communicatively coupled with the network (106). The coupling includes steps of receiving, by the network (106), a connection request from UE (104). Upon receiving the connection request, the coupling includes steps of sending, by the network (106), an acknowledgment of the connection request to the UE (104). Further, the coupling includes steps of transmitting a plurality of signals in response to the connection request.

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

[0074] In another exemplary embodiment, the network architecture (100) may include a centralized server (not shown) may include or include, by way of example but not limitation, one or more of a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, a hardware supporting a part of a cloud service or a system, a home server, a 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.

[0075] The system (108) is configured for tracing location of a subscriber in a network (106), as explained in detail in FIG. 2B.

[0076] 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).

[0077] FIG. 2A illustrates an exemplary system architecture (200A) for retrieving one or more information of the international in-roamer subscriber in the network (106), in accordance with embodiments of the present disclosure. FIG. 2 A is explained in conjunction with FIG. 1.

[0078] In an embodiment, the system architecture (200A) further includes a visited 4G / 5G network and a home 4G / 5G network. The Visited 4G / 5G network includes the IIR node (212), a Visited-Diameter Edge Agent (V-DEA) (214A), a V-Diameter Routing Agent (V-DRA) (216), the V-GMLC (218), a Visited-Mobility Management Entity (V-MME) (222), other Visited-network elements / Visited Unified Data Management (V-UDM) (224A), the V-SCP (226A), and a Visited-Security Edge Protection Proxy (V-SEPP). A Home (H) 4G / 5G network (230) includes a Home- Diameter Edge Agent (V-DEA) (214B), a Home-Security Edge Protection Proxy (H- SEPP) (228B) and a Home-other network elements / Home Unified Data Management (H-UDM) (224B). In an embodiment, the other network elements may include an Access and Mobility Management Function (AMF).

[0079] In an embodiment, the HR node (212), serves as a repository for storing and managing the international in-roamer subscriber identity and location information. In the Visited 4G / 5G network, the HR node (212) interacts with components such as the V-DEA (214 A), which handles authentication and message forwarding, and the V- GMLC (218), which retrieves location information (one or more information) used for tracing the international in-roamer subscriber, while the V-SCP (226A) in the 5G networks manages a Hyper Text Transfer Protocol 2 (HTTP2)-based signalling, facilitating the smooth transmission of requests and responses between servers. The V- SCP (226A) in the 5G environment manages HTTP2-based signalling, analogous to the V-DRA (216) in the 4G context, ensuring efficient communication pathways. The V-SEPP (228A) and the H-SEPP (228B) servers provide secure communication interfaces between a visited 4G / 5G network (220) and the home 4G / 5G network (230). In the home 4G / 5G network (230), a home Diameter Edge Agent (H-DEA) (214B) and the home-other network elements (224B) work alongside the H-SEPP (228B) to facilitate interactions with the Home Subscriber Server (HSS) and the UDM, which store the profile and identity data of the international in-roamer subscriber. By integrating these components, the architecture enables seamless and secure location tracing, ensuring compliance with regulatory requirements and supporting efficient network operations for international in-roamer subscribers.

[0080] In an embodiment, the visited 4G / 5G network (220) is the network where the international in-roamer subscriber is currently located and receiving service. The visited 4G / 5G network (220) is the network that provides immediate access and connectivity to the international in-roamer subscriber.

[0081] In an embodiment, the IIR node (212) may store essential international in-roamer subscriber information, including the SUPI and the GPSI. This enables the V-GMLC (218) to query the HR node (212) using either identifier, to determine current location of the international in-roamer subscriber. The HR node (212) interacts with other network elements, such as the V-SCP (226 A) and the home-other network elements / H-UDM (224B), to exchange data and coordinate location tracing processes.

[0082] In an embodiment, the visited-other network elements / V -UDM (224A) may include a visited AMF (V-AMF). The visited other network elements / V-UDM (224A) also manage the AMF registration process and store dynamic roaming data.

[0083] In an embodiment, the IIR node (212) may trace the location of the international in-roamer subscriber within the network (106). The HR node (212), operates with the home-other network elements / H-UDM (224B).

[0084] In an embodiment, the IIR node (212) processes the AMF registration access request and response, which are sent in a single request by the V-SCP (226A). The AMF registration access request includes the UE identity, which may be the SUPI, and the AMF registration information. The V-SCP (226A) copies both the request and response of the AMF registration, which is sent initially from the V-AMF to the home- other network elements / H-UDM (224B).

[0085] In an embodiment, the IIR node (212) maintains the international inroamer subscriber roaming data against the Subscription Permanent Identifier (SUPI) of the international in-roamer subscriber.

[0086] In an embodiment, the IIR node (212) maintains a mapping of both the SUPI and the Generic Public Subscription Identifier (GPSI) if the GPSI is also received in the forwarded request from the V-SCP (226 A). The mapping ensures that the subscriber can be uniquely identified using either identifier in subsequent queries from the V-GMLC (218). In an example, a subscriber may be identified in the network with a SUPI such as “001010123456789”. During the Access and Mobility Subscription Data Retrieval response, if the corresponding GPSI “tel:+919812345678” is present, the IIR node (212) creates and stores a mapping between the SUPI “001010123456789” and the GPSI “tel:+919812345678”. This mapping allows the V- GMLC (218) to request location information using either the SUPI or the GPSI. If a lawful interception body queries the IIR node (212) using the GPSI, the IIR node (212) translates the query to the SUPI and retrieves the associated roaming parameters from the database (210). In another example, if the GPSI is not included in the subscription data retrieval response, the IIR node (212) maintains only the SUPLbased record. In such a case, when a query is made using a GPSI, the IIR node (212) returns an error response, such as “404 resource not found.”

[0087] In an embodiment, the IIR node (212) provides the international inroamer subscriber roaming data, to the V-GMLC (218) when a lawful interception body performs a query on the V-GMLC (218) to fetch the international in-roamer subscriber location based on either the SUPI or the GPSI.

[0088] In an embodiment, the V-DEA (214 A) is a gateway for diameter signalling between different network domains. The V-DEA (214A) is used in routing and processing diameter messages related to the international in-roamer subscriber information and location tracing. In an embodiment, the custom request incorporates the original request and response headers and bodies within a single JavaScript Object Notation (JSON) structure, preserving the essential information for processing by the IIR node (212). By forwarding this custom request to the IIR node (212), the V-DEA(214A) enables the IIR node (212) to analyze the international in-roamer subscriber interaction, extract relevant data, and update its stored information accordingly. This process is used for accurate location tracing and effective management of international in-roamer subscriber. The V-DEA (214 A) forwards the response to the HR node (212), ensuring the IIR node (212) has up-to-date information on the international in-roamer subscriber location. In the 5G, the V-DEA (214A) is complemented by the V-SCP (226A), which handles HTTP2-based signalling.

[0089] In an embodiment, the V-DRA (216) routes diameter messages within the network (106). The V-DRA (216) is connected to the V-DEA (214A), the V-GMLC (218) and the V-MME (222). The V-DRA (216) is responsible for directing diameter messages between the visited 4G / 5G network (220) and the home 4G / 5G network (230), ensuring efficient communication and data exchange. The V-DRA (216) may determine the appropriate destination for incoming diameter messages based on their content and the network topology. The V-DRA (216) may distribute diameter messages across multiple network elements to optimize performance and avoid congestion. The V-DRA (216) may handle errors and exceptions that may occur during message processing and routing.

[0090] In an embodiment, the V-GMLC (218) is responsible for location-based services within the network. The V-GMLC (218) may be used in tracing the location of the international in-roamer subscriber and providing the necessary information to the home 4G / 5G network (230). The V-GMLC (218) handles the location information of the international in-roamer subscribers. The present disclosure supports emergency services and lawful interception by providing real-time location data of the international in-roamer subscriber. The V-GMLC (218) queries the IIR node (212) to retrieve international in-roamer subscriber location information. In the 5G, it involves the AMF registration information retrieval via a standardized interface to fetch the AMF identity and other related data. The V-GMLC (218) interacts with the HR node(212) to retrieve the location information of the international in-roamer subscriber based on the SUPI or the GPSI. The V-GMLC (218) may determine the approximate location of the international in-roamer subscriber based on the serving cell ID and other network information. The V-GMLC (218) may interact with the IIR node (212) to retrieve additional subscriber information, such as the SUPI and the GPSI, which can be used for more location tracing. The V-GMLC (218) may generate a response containing the location information of the international in-roamer subscriber, which is then sent back to the requesting entity (e.g., the home 4G / 5G network (230)). The V- GMLC (218) may interact with other network elements, such as the AMF and the V- SEPP (228A), to coordinate location-based services and may provide location tracing. By effectively tracing the one or more information such as the location of the international in-roamer subscriber and providing this information to the home 4G / 5G network (230), the V-GMLC (218) enables various location-based services and supports the overall management of international in-roaming subscribers.

[0091] In an embodiment, the V-MME (222) is responsible for managing mobile device registration, bearer activation / deactivation, and mobility management. The V-MME (222) communicates with the V-DEA (214A) to update the HSS of the location of the international in-roamer subscriber. These updates provide the international in-roamer subscriber which can receive services seamlessly, regardless of their location.

[0092] In an embodiment, the V-SCP (226A) plays a role in routing messages between the visited 4G / 5G network (220) and the home 4G / 5G network (230). The V- SCP (226A) handles the exchange of the diameter messages, including those related to the international in-roamer subscriber location tracing. The V-SCP (226A) may be used in the 5G network, performing similar functions to the V-DRA (216) in the 4G but adapted for HTTP2.

[0093] In an embodiment, the V-SCP (226A) creates a copy of the AMF registration for the access and the access and mobility subscription data retrieval request / response for the international in-roamer subscriber and forwards the same to the IIR node (212) in a single message.

[0094] In an embodiment, the V-SCP (226 A) creates a new request with an authority, path, scheme and method headers with same values as the AMF registration for the access. Then the SCP appends the original request and response headers to the custom request, prefixing them with a “request ” and a “response ”. The resulting header names will be request_path, request scheme, request method, and response status.

[0095] In an embodiment, the V-SCP (226 A) constructs a new request by setting the authority, path, scheme, and method headers to match those used in the AMF registration access request. The V-SCP (226A) then appends the original request and response headers, prefixed with the “request_” and the “response_” respectively, to this new request. Specifically, the headers added include request_path, request scheme, request method, response status, and response content-type, allowing for a comprehensive transfer of both request and response data from the AMF registration access request to the IIR node (212). This approach may support the encapsulation of all relevant information within the new request, facilitating seamless communication and data processing by the IIR node (212).

[0096] In an embodiment, the V-SEPP (228A) provides security and protection functions at the edge of the network (106). It enforces security policies, protects against unauthorized access, and may support the integrity of communications. The V-SEPP (228A) is involved in routing messages between the visited network (220) and the home network (230), ensuring that they are transmitted securely.

[0097] In an implementation, when the international in-roamer subscriber attaches to the 5G network, the international in-roamer subscriber initiates an Access and Mobility Management Function (AMF) registration access request with the H- UDM (224B) of the home network (230) of the international in-roamer subscriber via the H-SEPP (228B). The V-SCP (226 A) in the visited network (220) copies and forwards both the AMF registration access request and response to the IIR node (212).

[0098] The HR node (212) processes the forwarded AMF registration access request and response, parsing and storing the dynamic roaming data of the international in-roamer subscriber.

[0099] Subsequently, the V-GMLC (218) performs an Access and Mobility Management Function (AMF) information retrieval from the IIR node (212), using either the Subscription Permanent Identifier (SUPI) or Generic Public Subscription Identifier (GPSI). The IIR node (212) responds by providing the stored information.

[0100] In an embodiment, the AMF access registration information retrieval request is performed by the V-GMLC (218) against the SUPI. If the HR node (212) receives the GPSI for the SUPI in the AMF subscription data retrieval response (which is copied and forwarded), it will map the GPSI to the SUPI. This allows the V-GMLC (218) to retrieve information using the SUPI or the GPSI. However, if the GPSI is not included in the response, and the V-GMLC (218) attempts to retrieve information using the GPSI, the HR node (212) may return an error message indicating “resource not found.” In an example, the error message may include a 404 error message. For this solution, it is assumed that the H-UDM (224B) will consistently provide the GPSI in response to the AMF subscription data retrieval request. The AMF subscription data retrieval request and its corresponding response, sent by the V-MME (222) to the H- UDM (224B), are copied and forwarded by the V-SCP (226A) to the IIR node (212).

[0101] If the GPSI is present in the AMF subscription data retrieval response, the IIR node (212) extracts and stores it alongside the SUPI obtained earlier during the AMF registration access request. In the absence of the GPSI, the IIR node (212) will not have the GPSI to the SUPI mapping. Therefore, if the V-GMLC (218) in the visited network (220) requests AMF access registration information based on the GPSI of the international in-roamer subscriber, the IIR node (212) will return a 404-error due to the lack of the GPSI to the SUPI mapping.

[0102] However, if the information retrieval is performed using the SUPI, the IIR node (212) will successfully provide the dynamic location data associated with the international in-roamer subscriber.

[0103] FIG. 2B illustrates an exemplary block diagram 200B of the system (108) for tracing the location of the subscriber in the network (106), in accordance with an embodiment of the disclosure. FIG. 2B is explained in conjunction with FIG. 1 and FIG. 2A. In an embodiment, the network may be, for example, the 4G network, the 5G network, the 6G network, and the like.

[0104] In an embodiment, the system (108) may include a provisioning node (212). The provisioning node may also be referred to as the IIR node (212) throughout the specification. The IIR node (212) 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 packets over a network service. The memory (204) may include any non-transitory storage deviceincluding, 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.

[0105] In an embodiment, the HR node (212) 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). In an embodiment, the processing engine (208) is configured to execute functionalities of the HR node (212).

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

[0107] In an embodiment, the processing engine (208) is configured to receive a request from a requesting node (218), which, in this embodiment, is the Visited- Gateway Mobile Location Centre (V-GMLC) in the visited network to retrieve location information for the international in-roamer subscriber. The request is typically triggered when the international in-roamer subscriber is registered or updated within the visited network. The V-GMLC (218), identifies that the subscriber is the international in-roamer and forwards the location information request to the HR node (212).

[0108] In an embodiment, a home network (referred to as H network) refers to the network that the international in-roamer subscriber belongs to and is registered with. This is typically the network operated by the home service provider of the international in-roamer subscriber. Further, a visited network (referred to as V network) refers to the network that the international in-roamer subscriber is currently roaming in. The visited network provides the international in-roamer subscriber with access to services while they are away from their home network. In the context of international in-roaming, the home network is the network in the home country of the international in-roamer subscriber, while the visited network is the network in the country where the international in-roamer subscriber is currently located.

[0109] In an embodiment, the processing engine (208) of the provisioning node (212) is configured to receive the first customized request from a visited network node (226A), which, in this embodiment, is the Visited Service Communication Proxy (V- SCP). The V-SCP (226A) is a network function in the visited network that acts as an intermediary for network signalling. The V-SCP (226A) is configured to monitor and copy specific messages exchanged between network functions. The first customized request is generated by the V-SCP (226A) by copying an Access and Mobility Management Function (AMF) access registration request and an AMF access registration response originally exchanged between a visited- AMF (301) and a homenetwork node which, in this embodiment, is the H-UDM (224B). The AMF access registration request is transmitted when the subscriber attaches to the visited network, and the AMF access registration response is generated by the H-UDM (224B) after processing the subscriber registration. The first customized request is generated by duplicating an AMF registration exchange between a visited-AMF and the H-UDM (224B). In this procedure, the V-AMF sends a PUT request to the H-UDM to create or update AMF registration information for 3 GPP access, including the subscriber’s SUPI and registration data. The H-UDM processes the request and responds with one of several outcomes: a “200 OK” or “204 No Content” if updated successfully, a “201 Created” if no prior record existed, or a “403 Forbidden” with problem details if the subscriber is unauthorized due to restrictions such as roaming limitations or subscription data mismatch. The V-SCP duplicates this signaling into the first customized request and forwards it to the provisioning node (212). The provisioning node (212) parses the first customized request to extract a Subscription Permanent Identifier (SUPI) of the subscriber and one or more dynamic roaming parameters such as AMF instance identifier, deregistration callback URI, global unique AMF identifier (GUAMI), radio access technology type, and optionally a permanent equipment identifier (PEI). These parameters are then stored in the database (210) along with the SUPI.

[0110] In an embodiment, the processing engine (208) is further configured to receive a second customized request from the V-SCP (226A). The second customized request is generated by the V-SCP (226A) by copying an Access and Mobility Subscription Data Retrieval request and response exchanged between the V-AMF (301) and the H-UDM (224B). The second request is generated by duplicating an Access and Mobility Subscription Data Retrieval procedure initiated by the V-AMF towards the H-UDM (224B). The request includes the SUPI of the subscriber and may also contain query parameters such as supported features and PEMN identifier. The H- UDM responds with one of several outcomes: a “200 OK” including the subscriber’sAccess and Mobility Subscription Data, or a “404 Not Found” with problem details if no valid subscription data exists. The V-SCP duplicates this signaling into the second customized request and forwards it to the provisioning node (212). The provisioning node (212) parses the subscription data response contained in the second customized request and extracts a Generic Public Subscription Identifier (GPSI) when the GPSI is present. Upon extraction, the provisioning node (212) stores the GPSI alongside the SUPI in the database (210), thereby maintaining a mapping between the SUPI and the GPSI for the subscriber. This mapping enables the system to respond to queries based on either identifier.

[0111] In an embodiment, the database (210) may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processing engine (208). The database (210) stores subscriber identifiers and roaming parameters. When the provisioning node (212) extracts the SUPI and dynamic roaming parameters, these are recorded in the database (210). When the GPSI is extracted from the second customized request, the provisioning node (212) maintains a mapping between the SUPI and GPSI in the database (210). The mapping is optional and dependent on the presence of the GPSI in the subscription data response. This database ensures that subsequent location retrieval queries can be resolved efficiently without needing repeated interactions with the H-UDM (224B).

[0112] In an embodiment, the one or more dynamic roaming parameters extracted and stored by the provisioning node (212) include at least one of: an Access and Mobility Management Function (AMF) instance identifier, a deregistration callback Uniform Resource Identifier (URI), a global unique AMF identifier, a radio access technology type, and a permanent equipment identifier. The one or more dynamic roaming parameters may improve the system (108) capability to accurately identify and manage subscriber locations and related information, improving network reliability and service delivery. The one or more dynamic roaming parameterscollectively describe the dynamic context of the mobility of the subscriber and are essential for tracing the location of the subscriber.

[0113] In an embodiment, the provisioning node (212) is configured to provide the stored roaming parameters in response to a location information retrieval request initiated by the V-GMLC (218). The location information retrieval request is routed to the provisioning node (212) via the V-SCP (226A). The request may include either the SUPI or GPSI of the subscriber. Upon receiving the request, the provisioning node (212) queries the database (210) for the corresponding stored parameters. The retrieved parameters are then compiled into a location information retrieval response, which is transmitted back to the V-GMLC (218) through the V-SCP (226A). This operation allows the visited network to provide accurate subscriber location information to fulfill lawful interception obligations.

[0114] In an embodiment, the provisioning node (212) is configured to handle scenarios where the GPSI is not mapped to a SUPI in the database (210). In such cases, when the V-GMLC (218) submits a retrieval request based on the GPSI, the provisioning node (212) generates an error response, such as a “404 resource not found.” This guarantees reliable operation by notifying the V-GMLC (218) that the GPSI identifier is inaccessible, while continuing to support SUPI-based procedures queries.

[0115] In an embodiment, the provisioning node (212) is further configured to update the stored dynamic roaming parameters and the SUPI-to-GPSI mapping in the database (210) upon receiving updated information related to the subscriber. Updated information may be received through subsequent customized requests forwarded by the V-SCP (226A) whenever the subscriber undergoes re-registration, session modification, or mobility events. By continuously updating the stored information, the provisioning node (212) ensures that the V-GMLC (218) always receives the most current and accurate subscriber location data.

[0116] In an embodiment, the system (108) operates as follows: when a roaming subscriber attaches to the visited network, the V-AMF (301) exchanges registration and subscription data with the H-UDM (224B). The V-SCP (226A) intercepts and duplicates these exchanges, creating customized requests that are sent to the provisioning node (212). The provisioning node (212) extracts the SUPI, GPSI (when available), and dynamic roaming parameters, and stores them in the database (210). When a lawful request is made by the V-GMLC (218), the provisioning node (212) retrieves the relevant parameters and provides them to the V-GMLC (218). If a query is based on a GPSI that is not mapped, the provisioning node (212) responds with the error. The system (108) thereby enables efficient, accurate, and regulatory - compliant tracing of international in-roamer subscribers without requiring direct integration between the V-GMLC (218) and the H-UDM (224B).

[0117] FIG. 3 illustrates an exemplary flow diagram (300) of the first customized request, in accordance with embodiments of the present disclosure. FIG. 3 is explained in conjunction with FIG. 1, FIG. 2 A and FIG. 2B.

[0118] The following steps outline the multi-layered approach for the AMF registration access request for an international subscriber.

[0119] At 302: The process initiates with an AMF registration access request sent by a V-AMF (301) to a V-SCP (226A). The AMF registration access request aims to discover the requested Network Function (NF) based on parameters such as NF type, Data Network Name (DNN), or slice information to refine the search. This step is triggered when an international in-roamer subscriber attempts a location update or attachment in the network (106), prompting the V-AMF (301) to send an AMF registration access request to the home-other network elements / H-UDM (224B) via the V-SCP (226A). The V-SCP (226A), may upon receiving the registration request, recognizes that the international in-roamer subscriber is international based on thePublic Land Mobile Network (PLMN) identifier. The V-SCP (226A) decides to store and route this request.

[0120] At 304: The AMF registration access request is sent by the V-SCP (226A) to the V-Security Edge Protection Proxy (V-SEPP) (288A). The V-SCP (226A) forwards the AMF registration request to the V-SEPP (228A) based on a Subscription Permanent Identifier (SUPI).

[0121] At 306: The AMF registration access request is sent by the V-SEPP (228A) to the H-SEPP (228B).

[0122] At 308: Upon receiving the AMF registration access request, the H- SEPP (228B) forwards the AMF registration access request to a Home Service Communication Proxy (H-SCP) (226B).

[0123] At 310: The AMF registration access request is sent by the H-SCP (226B) to a H-UDM (224B). This routing may support the delivery of the AMF registration access request to the appropriate network functions responsible for managing the profile of the international in-roamer subscriber.

[0124] At 312: The AMF registration access response is sent by the H-UDM (224B) to the H-SCP (226B). The H-UDM (224B), which maintains the international in-roamer subscriber profile, processes the incoming request. The H-UDM (224B) then prepares an AMF registration response based on the profile data of the international inroamer subscriber.

[0125] At 314: The AMF registration access response is sent by the H-SCP (226B) to the H-SEPP (228B).

[0126] At 316: The AMF registration access response is sent by the H-SEPP (228B) to the V-SEPP (228A).

[0127] At 318: The AMF registration access response is sent by the V-SEPP (228A) to the V-SCP (226A).

[0128] At 320: The AMF registration access response is sent by the V-SCP (226A) to the V-AMF (301), completing the initial registration process.

[0129] At 322: The AMF request / response (the AMF registration access request / AMF registration access response) is copied in a PUT request and is sent from the V-SCP (226A) to the IIR node (212). In parallel, the V-SCP (226A) creates the first customized request containing the actual AMF registration request and response messages that occurred between the V-AMF (301) and the H-UDM (224B). The customized request is sent to the IIR node (212) to store the necessary information of the international in-roamer subscriber. The V-SCP (226A) sends the PUT request to the IIR node (212) to record and maintain data about the international in-roamer subscriber.

[0130] At 324: A PUT response is sent from the IIR node (212) to the V-SCP (226A). The IIR node (212) parses the first customized request to extract essential subscriber information such as the SUPI. The IIR node (212) stores this information in its database (210) and sends a PUT response back to the V-SCP (226A), acknowledging the storage of the roaming data of the international in-roamer subscriber.

[0131] FIG. 4 illustrates another exemplary flow diagram (400) the second customised request, in accordance with embodiments of the present disclosure. FIG. 4 is explained in conjunction with FIG. 1, FIG. 2 A, FIG. 2B and FIG. 3.

[0132] The following steps outline an access and mobility subscription data retrieval call flow of the international in-roamer subscriber. An Access and Mobility (AM) data retrieval request is initiated by the V-AMF (301) towards the H-UDM (224B)

[0133] At 402: The AM data retrieval request is routed by the V-AMF (301) to the V-SCP (226A). The V-SCP (226A) determines that the subscriber is an international roamer based on a Public Land Mobile Network (PLMN) of the international in-roamer subscriber. The V-SCP (226A) may store the AM data retrieval request sent to the home 4G / 5G network (230).

[0134] At 404: The AM data retrieval request is routed by the V-SCP (226A) to the V-SEPP (228A) based on the SUPI.

[0135] At 406: The AM data retrieval request is routed by the V-SEPP (228A) to the H-SEPP (228B). The V-SEPP (228A) is on the edge of the visited 4G / 5G network (220) that is communicating with the H-SEPP (228B) of the home 4G / 5G network (230) of the international in-roamer subscriber.

[0136] At 408: The H-SEPP (228B) routes the AM data retrieval request to the H-SCP (226B).

[0137] At 410: The H-SCP (226B) delivers the AM data retrieval request to the H-UDM (224B).

[0138] At 412: The H-UDM (224B) responds to the H-SCP (226B) with an AM data retrieval response. The H-UDM (224B) has subscription data, and the H- UDM (224B) further processes the incoming AM data GET request and sends the response to the H-SCP (226B)

[0139] At 414: The AM data retrieval response is communicated from the H- SCP (226B) to the H-SEPP (228B).

[0140] At 416: The AM data retrieval response is communicated from the H- SEPP (228B) to the V-SEPP (228A).

[0141] At 418: The AM data retrieval response is communicated from the V- SEPP (228) to the V-SCP (226A).

[0142] At 420: The AM data retrieval response is communicated from the V- SCP (226A) to the V-AMF (301).

[0143] At 422: The AM data retrieval request / AM data retrieval response is copied in a GET request and is sent from the V-SCP (226A) to the HR node (212). The V-SCP (226A) creates the second customized request of the AM data retrieval request / AM data retrieval response, which has headers and data of actual request and response messages (already happened between the V-AMF (301) and the H-UDM (224B)).

[0144] At 424: A GET response is sent from the HR node (212) to the V-SCP (226A). The HR node (212) will parse the copied request / response and check if there is the GPSI in the copied response (GPSI is optional). If GPSI is present in the copied response, then the HR node (212) stores the GPSI to the SUPI mapping and responds to the V-SCP (226A). If the GPSI is not present, then the HR node (212) is not able to keep the GPSI to the SUPI mapping and responds to the V-SCP (226 A).

[0145] FIG. 5 illustrates an exemplary flow diagram of the Access and mobility management function (AMF) access registration information retrieval request / response, in accordance with embodiments of the present disclosure. FIG. 5 is explained in conjunction with FIG. 1, FIG. 2A, FIG. 2B, FIG. 3 and FIG. 4.

[0146] The following steps outline the AMF access registration information retrieval from HR node (212).

[0147] At 502: An AMF access registration information retrieval request is sent from the V-GMLC (218) to the V-SCP (226A) to retrieve the AMF access registration information for the international in-roamer subscriber.

[0148] At 504: The AMF access registration information retrieval request is sent from the V-SCP (226A) to the IIR node (212). When the HR node (212) receives the AMF access registration information retrieval request against the Subscription Permanent Identifier (SUPI), the IIR node (212) checks the database (210) and fetches the stored one or more parameters against the SUPI if the SUPI / Generic Public Subscription Identifier (GPSI) comes in the AMF access registration information retrieval request.

[0149] At 506: An AMF access registration information retrieval response is sent from the HR node (212) to the V-SCP (226A). The HR node (212) frames the AMF access registration information retrieval response with the help of the fetched stored one or more parameters. The AMF access registration information retrieval response may include one or parameters such as Globally Unique AMF Identifier (GUAMI), radio access technology type etc.

[0150] At 508: The AMF access registration information retrieval response is sent from the V-SCP (226A) to the V-GMUC (218).

[0151] In an embodiment, if the GPSI is not available against the SUPI and a request for the GPSI is made, the International In-Roamer Register (HR) node (212) may respond with a 404 (resource not found) error code.

[0152] FIG. 6 illustrates an exemplary flow diagram of a method (600) for tracing the location of the subscriber in the network (106), in accordance with an embodiment of the present disclosure. FIG. 6 is explained in conjunction with FIG. 1, FIG. 2A, FIG. 2B, FIG. 3, FIG. 4 and FIG. 5.

[0153] At step 602, the method (600) comprises receiving, at a provisioning node (212), a first customized request from a visited network node (226A). In an embodiment, the visited network node (226A), also referred to as the Visited Service Communication Proxy (V-SCP), duplicates signalling exchanged between the visitedAccess and Mobility Management Function (V-AMF) (301) and the Home Unified Data Management (H-UDM) (224B). The V-SCP (226A) generates the first customized request of the AMF access registration request and response and forwards this to the provisioning node (212). The first customized request includes the AMF access registration request and the AMF access registration response exchanged between the visited- AMF (V-AMF) (301) and the home network node (224B) of the subscriber. When the subscriber attaches to the visited network, the V-AMF (301) initiates an AMF access registration request to the H-UDM (224B). The H-UDM (224B) processes the request and returns an AMF access registration response. The V- SCP (226A) intercepts and copies these messages, forming the first customized request. The provisioning node (212) receives and parses this request to obtain the SUPI and the one or more dynamic roaming parameters. This step enables the provisioning node (212) to obtain registration information of international in-roamer subscribers without requiring direct interaction between the V-GMLC (218) and the H-UDM (224B).

[0154] At step 604, the method (600) comprises parsing, by the provisioning node (212), the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber. In an embodiment, the provisioning node (212) analyzes the customized request payload to identify the SUPI, which uniquely identifies the subscriber. Along with the SUPI, the provisioning node (212) extracts the one or more dynamic roaming parameters. The one or more dynamic roaming parameters represent the subscriber’s session and mobility context, which are essential for location tracing.

[0155] At step 606, the method (600) comprises receiving, by the provisioning node (212), the second customized request from the visited network node (226A). In an embodiment, the V-SCP (226A) duplicates the Access and Mobility Subscription Data Retrieval request and response exchanged between the V-AMF (301) and the H-UDM (224B) and forwards them to the provisioning node (212). The second customized request contains subscription-level information, which may include the Generic Public Subscription Identifier (GPSI) of the subscriber. The second customized request includes an Access and Mobility Subscription Data Retrieval request and response exchanged between the V-AMF and the H-UDM. The provisioning node (212) extracts the GPSI from the response when present and stores the GPSI with the SUPI in the database (210). The provisioning node (212) examines the subscription data response copied into the second customized request. If the GPSI is present, the provisioning node (212) records it in the database (210) alongside the SUPI.

[0156] At step 608, the method (600) comprises parsing, by the provisioning node (212), the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI. In an embodiment, the provisioning node (212) parses the subscription data response contained in the customized request. If the GPSI is present, it is extracted and logically associated with the SUPI of the subscriber. This association ensures that subsequent queries from lawful authorities can be resolved using either SUPI or GPSI. If the GPSI is absent, no mapping is created, and the system (108) defaults to SUPLonly support.

[0157] At step 610, the method (600) comprises storing, by the provisioning node (212), the extracted SUPI and the one or more roaming parameters in the database (210). The provisioning node (212) maintains the SUPLto-GPSI mappings and updates the database (210) when new information arrives. In an embodiment, the mapping is maintained in the database (210) and updated whenever the provisioning node receives new subscription data responses containing GPSI.

[0158] At step 612, the method (600) comprises providing, by the provisioning node (212), the one or more stored roaming parameters in response to a location information retrieval request for the SUPI or the GPSI to a requesting node (218), toenable tracing the location of the subscriber. In an embodiment, the requesting node (218), also referred to as the V-GMLC, generates a location information retrieval request when an LEA requires subscriber location data. The request is routed via the V-SCP (226A) to the provisioning node (212). The provisioning node (212) queries the database (210) based on the identifier (SUPI or GPSI) provided in the request. The provisioning node (212) retrieves the corresponding roaming parameters and transmits them in a structured response back to the V-GMLC (218) via the V-SCP (226A). This step completes the location tracing workflow by delivering accurate subscriber information to the V-GMLC (218).

[0159] In an embodiment, the provisioning node (212) provides the stored roaming parameters in response to the location information retrieval request initiated by the requesting node (218), which, in this embodiment, is the V-GMLC. The location information retrieval request is routed to the provisioning node (212) via the V-SCP (226A). The request may include either the SUPI or GPSI of the subscriber. Upon receiving the request, the provisioning node (212) queries the database (210) for the corresponding stored parameters. The retrieved parameters are then compiled into the location information retrieval response, which is transmitted back to the V-GMLC (218) through the V-SCP (226A). This operation allows the visited network to provide accurate subscriber location information to fulfill lawful interception obligations

[0160] In an embodiment, the method (600) comprises generating, by the provisioning node (212), the error response to the V-GMLC (218) through the V-SCP (226A) when the retrieval request is based on the GPSI that is not mapped to the SUPI in the database (210). The error response may be a standardized message such as “404 resource not found.” This ensures transparency and robustness by indicating that GPSI- based resolution is unavailable, while still supporting SUPI-based queries.

[0161] In an embodiment, the provisioning node (212) updates the stored dynamic roaming parameters and mapping between the SUPI and GPSI in the database(210) upon receiving updated information related to the subscriber. This occurs when the V-AMF (301) re-initiates registration procedures or when new subscription data retrieval responses are received. The provisioning node updates the database (210) to reflect the latest subscriber context, ensuring accurate results for future lawful queries.

[0162] FIG. 7 illustrates a computer system (700) in which or with which the embodiments of the present disclosure may be implemented.

[0163] As shown in FIG. 7, the computer system (700) may include an external storage device (710), a bus (720), a main memory (730), a read-only memory (740), a mass storage device (750), communication port(s) (760), and a processor (770). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (770) may include various modules associated with embodiments of the present disclosure. The communication port(s) (760) 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 port(s) (760) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0164] The main memory (730) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (740) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (770). The mass storage device (750) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device (750) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) 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 Firewireinterfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0165] The bus (720) communicatively couples the processor (770) with the other memory, storage, and communication blocks. The bus (720) may be, e.g., a Peripheral Component Interconnect / Peripheral Component Interconnect Extended 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 (770) to the computer system.

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

[0167] In an exemplary embodiment, a computer program product includes a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for tracing location of a subscriber in a network is disclosed. The method includes receiving, at a provisioning node, a first customized request from a visited network node. The method includes parsing, by the provisioning node, the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber. The method includes receiving, by the provisioning node, a second customized request from the visited network node. The method includes parsing, by the provisioning node, the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI. Themethod includes storing, by the provisioning node, the extracted SUPI, the extracted SUPI, and the one or more roaming parameters in a database. The method includes providing, by the provisioning node, the one or more stored roaming parameters in response to a location information retrieval request for the SUPI or the GPSI to a requesting node, to enable tracing the location of the subscriber.

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

[0169] The present disclosure provides the method and system for tracing location of international in-roamer subscribers in a 5G network. Unlike traditional approaches that rely on identifier translation with a home network, the provisioning node parses customized registration and subscription data requests to extract the SUPI and, when available, the GPSI along with dynamic roaming parameters. This enables efficient identifier management, reduces signaling overhead, and ensures accurate and timely location retrieval by the requesting node, thereby improving regulatory compliance and operational efficiency in international roaming scenarios.ADVANTAGES OF THE PRESENT DISCLOSURE

[0170] The present disclosure described herein above has several technical advantages including, but not limited to, the realization of the system and the method where:

[0171] By storing both the Subscription Permanent Identifier (SUPI) and the Generic Public Subscription Identifier (GPSI) information, the International In-roamerregister (IIR) node can provide more accurate location tracing, especially in cases where the GPSI might not be readily available or might change over time;

[0172] The IIR node centralizes international in-roamer subscriber information, making it easier for the Gateway Mobile Location Centre (GMLC) to retrieve the data for location tracing. This can reduce latency and improve overall performance; and

[0173] By storing subscriber information within the HR node, the home network can potentially reduce the amount of sensitive data that needs to be transmitted over the network, enhancing security and privacy.

Claims

CLAIMS1. A method (600) for tracing location of a subscriber in a network (106), the method (600) comprising: receiving (602), at a provisioning node (212), a first customized request from a visited network node (226A); parsing (604), by the provisioning node (212), the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber; receiving (606), by the provisioning node (212), a second customized request from the visited network node (226A); parsing (608), by the provisioning node (212), the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI; storing (610), by the provisioning node (212), the extracted SUPI, the extracted GPSI, and the one or more roaming parameters in a database (210); and providing (612), by the provisioning node (212), the one or more stored roaming parameters in response to a location information retrieval request for the SUPI or the GPSI to a requesting node (218), to enable tracing the location of the subscriber.

2. The method (600) as claimed in claim 1, wherein: the first customized request includes an Access and Mobility Management Function (AMF) access registration request and an AMF access registration response exchanged between a visited- AMF (V-AMF) (301) and a home network node (224B) of the subscriber.

3. The method (600) as claimed in claim 1, wherein: the second customized request includes an Access and Mobility Subscription Data Retrieval request and an Access and Mobility Subscription Data Retrieval response exchanged between the V-AMF (301) and the home network node (224B), wherein the provisioning node (212) extracts the GPSI from the Access and Mobility Subscription Data Retrieval response when the GPSI is present and stores the GPSI to the SUPI in the database (210).

4. The method (600) as claimed in claim 3, comprising, maintaining by the provisioning node (212), a mapping between the SUPI and the GPSI when the GPSI is present in the second customized request.

5. The method (600) as claimed in claim 1, wherein the one or more dynamic roaming parameters comprises at least one of an Access and Mobility Management Function (AMF) instance identifier, a deregistration callback Uniform Resource Identifier (URI), a global unique AMF identifier, a radio access technology type, and a permanent equipment identifier.

6. The method (600) as claimed in claim 1, wherein providing the stored roaming parameters comprises: receiving, by the provisioning node (212), an access registration information retrieval request from the requesting node (218) through the visited network node (226A), wherein the access registration information retrieval request includes the SUPI or the GPSI of the subscriber;retrieving, by the provisioning node (212), the one or more stored dynamic roaming parameters from the database (210) based on the SUPI or the GPSI; and transmitting, by the provisioning node (212), an access registration information retrieval response to the requesting node (218) through the visited network node (226A), wherein the access registration information retrieval response comprising the stored one or more dynamic roaming parameters.

7. The method (600) as claimed in claim 6, comprising generating, by the provisioning node (212), an error response to the requesting node (218) through the visited network node (226A) when the access registration information retrieval request is based on the GPSI that is not mapped to the SUPI in the database (210).

8. The method (600) as claimed in claim 1, wherein the provisioning node (212) updates the stored dynamic roaming parameters and mapping between the SUPI and the GPSI in the database (210) upon receiving updated information related to the subscriber.

9. A system (108) for tracing location of a subscriber in a network (106), the system (108) comprising: a provisioning node (212) configured to: receive a first customized request from a visited network node (226A); parse the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber;receive a second customized request from the visited network node (226 A); parse the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI; store the extracted SUPI, the extracted GPSI, and the one or more roaming parameters in a database (210); and provide the one or more stored roaming parameters in response to a location information retrieval request for the SUPI or the GPSI to a requesting node (218), to enable tracing the location of the subscriber.

10. The system (108) as claimed in claim 9, wherein the first customized request includes an Access and Mobility Management Function (AMF) access registration request and an AMF access registration response exchanged between a visited- AMF (V-AMF) (301) and a home network node (224B) of the subscriber.

11. The system (108) as claimed in claim 9, wherein: the second customized request includes an Access and Mobility Subscription Data Retrieval request and an Access and Mobility Subscription Data Retrieval response exchanged between the V-AMF (301) and the home network node (224B), wherein the provisioning node (212) extracts the GPSI from the Access and Mobility Subscription Data Retrieval response when the GPSI is present and stores the GPSI to the SUPI in the database (210).

12. The system (108) as claimed in claim 11, wherein the provisioning node (212) is configured to maintain a mapping between the SUPI and the GPSI when the GPSI is present in the second customized request.

13. The system (108) as claimed in claim 9, wherein the one or more dynamic roaming parameters comprises at least one of an Access and Mobility Management Function (AMF) instance identifier, a deregistration callback Uniform Resource Identifier (URI), a global unique AMF identifier, a radio access technology type, and a permanent equipment identifier.

14. The system (108) as claimed in claim 8, wherein providing the stored roaming parameters comprises the provisioning node (212) configured to: receive an access registration information retrieval request from the requesting node (218) through the visited network node (226 A), wherein the access registration information retrieval request includes the SUPI or the GPSI of the subscriber; retrieve the one or more stored dynamic roaming parameters from the database (210) based on the SUPI or the GPSI; and transmit an access registration information retrieval response to the requesting node (218) through the visited network node (226 A), wherein the access registration information retrieval response comprising the stored one or more dynamic roaming parameters.

15. The system (108) as claimed in claim 14, wherein the provisioning node (212) is configured to generate an error response to the requesting node (218) through the visited network node (226A) when the access registration information retrieval request is based on the GPSI that is not mapped to the SUPI in the database (210).

16. The system (108) as claimed in claim 9, wherein the provisioning node (212) updates the stored dynamic roaming parameters and mapping between the SUPIand the GPSI in the database (210) upon receiving updated information related to the subscriber.

17. A computer program product comprising a non -transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (600) for tracing location of a subscriber in a network (106), the method (600) comprising: receiving (602), at a provisioning node (212), a first customized request from a visited network node (226A); parsing (604), by the provisioning node (212), the first customized request to extract a Subscription Permanent Identifier (SUPI) and one or more dynamic roaming parameters associated with the subscriber; receiving (606), by the provisioning node (212), a second customized request from the visited network node (226A); parsing (608), by the provisioning node (212), the second customized request to extract a Generic Public Subscription Identifier (GPSI) to the extracted SUPI; storing (610), by the provisioning node (212), the extracted SUPI, the extracted GPSI, and the one or more roaming parameters in a database (210); and providing (612), by the provisioning node (212), the one or more stored roaming parameters in response to a location information retrieval request for the SUPI or the GPSI to a requesting node (218), to enable tracing the location of the subscriber.

Images