Method and system for processing concurrent location requests in a network

Abstract

The present disclosure provides a method (400) and a system (108) for processing one or more concurrent location requests associated in a network. The method includes receiving, by a first location management entity, one or more concurrent location requests from at least one network entity, each comprising at least one parameter indicative of the UE. The first location management entity determines at least one network node associated with the UE and transmits the concurrent location requests to the determined network node. The at least one network node processes the received location requests by either adding them to a processing queue or initiating one or more tasks to handle each request independently. The method enables parallel and optimized processing of concurrent location requests, thereby reducing response time and improving network efficiency.

Description

METHOD AND SYSTEM FOR PROCESSING CONCURRENT LOCATION REQUESTS IN A NETWORKRESERVATION OF RIGHTS

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

[0002] The present disclosure relates generally to the field of telecommunications. More particularly, the present disclosure relates to a method and a system for processing one or more concurrent location requests in a network.DEFINITION

[0003] The term “evolved NodeB (eNodeB)” used hereinafter in the specification refers to a network component that serves as a base station responsible for managing the radio communication between a user equipment (UE) and the network. The eNodeB transmits and receives radio signals to and from the UE, enabling voice and data communication.

[0004] The term “Concurrent location requests” used hereinafter in the specification refers to multiple simultaneous requests made to a system or network to retrieve the location of one or more user devices (user equipment’s) at the same time. The concurrent location requests may originate from different entities, such asapplications, services, or authorized users, and may include requests for real-time location tracking, emergency services, or lawful interception.

[0005] The term “Mobility Management Entity (MME)” used hereinafter in the specification refers to a network component in a long-term evolution (LTE) core network that manages user mobility and session management. The MME helps in authentication, session management, and signaling in the network. The MME processes multiple concurrent location requests received from a requesting entity.

[0006] The term “Mobile Location Center (MLC)” used hereinafter in the specification refers to a network component that handles location-related requests and provides location information to the authorized entities. The MLC communicates with the MME to obtain the UE location data.

[0007] The term “Gateway Mobile Location Center (GMLC)” used hereinafter in the specification refers to a component within the MLC that provides location information of the UE. The GMLC acts as a gateway for receiving multiple concurrent location requests from the external entities, processing the requests and facilitating communication with the MME to retrieve the necessary location information.

[0008] The term “Home Subscriber Server (HSS)” used hereinafter in the specification refers to a network component that acts as a central repository for subscriber-related information and manages user identities and services. The HSS handles authentication requests from the network elements, such as MME, and provides credentials to verify the identity of the user and authorization for service access.

[0009] The term “Query Number Portability Database (QNPDB)” used hereinafter in the specification refers to a database that stores and manages information related to the portability of telephone numbers of the UE within the network. TheQNPDB provides essential data for routing location requests and ensures accurate retrieval of user information based on their mobile number.

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

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

[0012] In telecommunications, accurate tracking of mobile device locations is critical for services such as emergency response and lawful interception, where timely and precise user location information enables rapid assistance and compliance with legal obligations. To obtain accurate user location data, the network employs various entities, including a Mobility Management Entity (MME), which manages user connectivity, authentication, and location-related functions. Efficient handling of location requests received by the MME from authorized entities, such as lawful interception authorities, is therefore essential to ensure reliable and prompt delivery of location information, particularly during emergencies or lawful monitoring activities.

[0013] At present, the MMEs face limitations when handling multiple concurrent location requests. These limitations force the MME to either reject new location requests or cancel ongoing requests. Such actions lead to failures or delays in obtaining location information, impacting essential services that rely on accurate and immediate location information. For example, a lawful interception authority may experience delays or be unable to obtain required location data, and emergencyresponse systems may face challenges in locating the users promptly, which could hinder effective assistance in urgent situations.

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

[0015] In an exemplary embodiment, a method for processing one or more concurrent location requests in a network is described. The method includes receiving, by a first location management entity, the one or more concurrent location requests from at least one network entity for retrieving a location of at least one user equipment (UE), each of the one or more concurrent location requests includes at least one parameter. The method includes determining, by the first location management entity, at least one network node associated with the at least one UE. The method includes transmitting, by the first location management entity, the one or more concurrent location requests to the determined at least one network node. The method includes processing, by the at least one network node, the received one or more concurrent location requests by performing one of: adding, by the at least one network node, the received one or more concurrent location requests in a processing queue and initiating, by the at least one network node, at least one task for handling each of the received one or more concurrent location requests.

[0016] In some embodiments, the method further includes transmitting, by the at least one network node, at least one request to a second location management entity.

[0017] In some embodiments, the at least one parameter includes an international mobile subscriber identity (IMSI), an E-UTRAN Cell Global Identifier (ECGI), and a Quality of Service (QoS).

[0018] In some embodiments, the method further includes retrieving, by the first location management entity, information associated with the at least one network node based on the at least one parameter from a network server, the retrieved information includes at least one identifier corresponding to the at least one network node that is associated with the at least one UE, and selecting, by the first location management entity, the at least one network node based on the retrieved information.

[0019] In some embodiments, the method further includes on receiving the at least one request, interacting, by the second location management entity, with the at least one UE and a network element associated with the at least one UE to obtain measurement data corresponding to at least one measurement parameter associated with the at least one UE, computing, by the second location management entity, a location of the at least one UE based on the obtained measurement data, and transmitting, by the second location management entity, a location response to the at least one network node, the location response includes the computed location of the at least one UE.

[0020] In some embodiments, the at least one measurement parameter includes at least one of a UE receive-transmit time difference, a reference signal received power (RSRP), and a reference signal received quality (RSRQ).

[0021] In some embodiments, the method further includes receiving, by the at least one network node, the location response from the second location management entity, transmitting, by the at least one network node, the location response to the first location management entity, and forwarding, by the first location management entity, the location response to the at least one network entity.

[0022] In some embodiments, the method further includes adding the received one or more concurrent location requests in the processing queue comprising: determining, by the at least one network node, an insertion order for the received oneor more concurrent location requests based on the one or more parameters; and adding, by the at least one network node, the received one or more concurrent location requests to the processing queue in the determined insertion order.

[0023] In another exemplary embodiment, a system for processing one or more concurrent location requests in a network is described. The system includes a first location management entity configured to receive the one or more concurrent location requests from at least one network entity for retrieving a location of at least one user equipment (UE), each of the one or more concurrent location requests includes at least one parameter. The first location management entity is further configured to determine at least one network node associated with the at least one UE. The first location management entity is further configured to transmit the one or more concurrent location requests to the determined at least one network node. The system further includes a receiving unit and a processing unit at the at least one network node. The receiving unit is configured to receive the one or more concurrent location requests. The processing unit is configured to perform either one of: add the received one or more concurrent location requests in a processing queue or initiate at least one task for handling each of the received one or more concurrent location requests.

[0024] In an exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for processing one or more concurrent location requests in a network is described. The method includes receiving, by a first location management entity, the one or more concurrent location requests from at least one network entity for retrieving a location of at least one user equipment (UE), each of the one or more concurrent location requests includes at least one parameter. The method includes determining, by the first location management entity, at least one network node associated with the at least one UE. The method includes transmitting, by the firstlocation management entity, the one or more concurrent location requests to the determined at least one network node. The method includes processing, by the at least one network node, the received one or more concurrent location requests by performing one of: adding, by the at least one network node, the received one or more concurrent location requests in a processing queue and initiating, by the at least one network node, at least one task for handling each of the received one or more concurrent location requests.

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

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

[0027] An objective of the present disclosure is to provide a system and a method for handling one or more concurrent location requests in a network.

[0028] Another objective of the present disclosure is to provide a system and a method that enhances the success rate of processing one or more location requests, particularly in high-priority scenarios involving lawful interception and emergency calls.

[0029] Yet another objective of the present disclosure is to provide a system and a method that optimizes network resource utilization by processing the one or more concurrent location requests, thereby minimizing rejections and improving network performance during high request loads.

[0030] Yet another objective of the present disclosure is to provide a system and a method that enhances user experience and service quality for location-based applications by reducing delays and failures in retrieving location data.

[0031] Yet another objective of the present disclosure is to eliminate the options of rejecting or canceling location requests from existing standards and to mandate the use of the disclosed method for handling concurrent location requests by processing each request concurrently and independently, rather than rejecting or canceling such requests.

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

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

[0034] FIG. 1 illustrates an exemplary network architecture in which or with which a system configured for processing one or more concurrent location requests in a network may be implemented, in accordance with embodiments of the present disclosure.

[0035] FIG. 2 illustrates an exemplary block diagram of the system configured for processing the one or more concurrent location requests in the network, in accordance with embodiments of the present disclosure.

[0036] FIG. 3 illustrates an exemplary system architecture for processing the one or more concurrent location requests in the network, in accordance with an embodiment of the present disclosure.

[0037] FIG. 4 illustrates an exemplary flow diagram of a method for processing the one or more concurrent location requests in the network, in accordance with an embodiment of the present disclosure.

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

[0039] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 - User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor204 - Memory206 - Interface(s)208 - Receiving unit210 - Processing unit 212 - Database300 - System Architecture302 - Network Entity304 - Load Balancer306 - Mobile location Center (MLC) 308- Wireless Location Application (WLA) / Location-Based Services Center (LBSC) node310 - Gateway Mobile Location Center (GMLC)312-1, 312-2 - Diameter Routing Agent mated pairs (DRAs)314 - Mobility Management Entity (MME) 316 - Evolved Serving Mobile location center (E SMLC)318 - Evolved Node B (eNodeB)320 - Home Subscriber Server (HSS)322 - Query Number Portability database (QNPDB)400 - Method Flow Diagram500 - Computer System510 - External Storage Device520 - Bus530 - Main Memory540 - Read Only Memory550 - Mass Storage Device560 - Communication Port(S)570 - ProcessorDETAILED DESCRIPTION

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

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

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

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

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

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

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

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

[0048] In telecommunications, to promptly provide operator with the accurate and timely location, the communication networks incorporate various components such as Mobility Management Entity (MME), Serving Gateway (SGW), Packet Data Network Gateway (PGW), and Home Subscriber Server (HSS) to effectively manage connectivity, authentication, and location services for users. Each element plays a vital role in ensuring seamless communication and service delivery. The efficient handling of location requests by the MME is essential for maintaining reliable service, particularly in scenarios that require immediate and precise user location data, such as during emergency calls or lawful interception operations.

[0049] In existing methods, when one or more location requests are sent to the MME, the MME typically performs operations such as rejecting new location requests, canceling one or more previous requests. However, rejecting or canceling the location requests may lead to failures in retrieving user location data, negatively impacting lawful interception clients and emergency call responses. Additionally, canceling requests increases the time needed to obtain location information, which is particularly critical in emergency or lawful interception situations where immediate responses are essential. This delay reduces service reliability and can lead to inefficiencies that failto meet urgent needs. Furthermore, the existing methods often lead to significant underutilization and inefficient allocation of resources due to the common practice of rejecting or canceling concurrent requests. The underutilization and inefficient allocation lead to the wastage of valuable processing power and network bandwidth, and create bottlenecks that could be avoided. By prioritizing the parallel handling of the requests instead of employing cancellations and rejections, the network can maximize resource utilization. Ultimately, these shortcomings result in reduced network performance and a reduced capacity for simultaneous service delivery, which damages the overall effectiveness and responsiveness of the system in meeting user demands. Hence, there is a need to provide a method and a system that can address the shortcomings of existing solutions.

[0050] The present disclosure relates to a method and system for processing one or more concurrent location requests in a network. In the present disclosure, the MME may be configured to manage each of the received concurrent location requests either by processing each location request concurrently or deferring the new concurrent location requests to process them later without failures. In the present disclosure, when the MME receives multiple concurrent location requests, the MME is configured not to reject the new location request nor cancel the existing location request. By processing each concurrent request, the present disclosure minimizes the delay associated with location retrieval, allowing each request to be handled without interruption. This ensures that each received request, such as emergency service-related requests and lawful interception services-related requests, is processed and the respective sender receives timely responses, meeting critical time requirements and enhancing reliability.

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

[0052] FIG. 1 illustrates an exemplary network architecture 100 in which or with which a system 108 configured for processing one or more concurrent location requests in a network 106 may be implemented, in accordance with embodiments of the present disclosure.

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

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

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

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

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

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

[0059] In an embodiment, the UE 104 participates in communication with the system 108 through the network 106 to enable the exchange of signaling and data necessary for determining its geographic position. The UE 104 may transmit relevant information such as its identity, cell information, positioning capability, or measurement reports that assist in accurately computing or retrieving its location.

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

[0061] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 configured for processing the one or more concurrent location requests in the network 106, in accordance with embodiments of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1.

[0062] In an embodiment, the system 108 may include one or more processor(s) 202. The one or more processor(s) 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in memory 204 of the system 108. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device, including, for example, volatile memory such as 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.

[0063] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like.

[0064] In an embodiment, the system 108 may include a receiving unit 208 and a processing unit 210 and a database 212. The database 210 may store data (e.g., user information, error logs, historical user data, etc.) that may be either stored or generated as a result of functionalities implemented by any of the components of the processing unit 210.

[0065] In an embodiment, the interface(s) 206 may facilitate communication through the system 108. The interface(s) 206 may also provide a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the receiving unit 208, the processing unit 210, and a database 212.

[0066] In an embodiment, the processing unit 210 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit 210. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit 210 may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the processing unit 210 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit 210. In such examples, the system 108 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the processing unit 210 may be implemented by electronic circuitry. In yet another example, the receiving unit 208 and the processing unit 210 may be implemented by a first location management entity. The first location management entity may correspond to a Gateway Mobile Location Center (GMLC), a Location Management Function (LMF), Home Mobile Location Center (HMLC), etc.

[0067] In an embodiment, the receiving unit 208 at the first location management entity is configured to receive the one or more concurrent location requests from at least one network entity for retrieving a location of at least one userequipment (UE), such as the UE 104m. The one or more concurrent location requests are the multiple requests for location information that are received by the network node (such as the MME), simultaneously or within overlapping timeframes. In an aspect, the one or more concurrent location requests may be a mobile terminated location request (MT-LR), a mobile originated location request (MO-LR), a network induced location request (NI-LR), an immediate location request, or a deferred location request. The at least one network entity refers to an external service or application that initiates and transmits the one or more concurrent location requests to the first location management entity with the intent of retrieving the location data of the at least one UE 104. The at least one network entity may include various types of clients or services, but is not limited to lawful interception clients (authorities), emergency services, and locationbased services (LBS) providers. The lawful interception authorities are authorized entities, such as law enforcement or intelligence agencies, that request location data of the at least one UE to support investigative activities in compliance with legal and regulatory frameworks. The lawful interception authorities rely on accurate and timely location information for tracking and monitoring of the at least one UE 104 within the network 106. The emergency services may include, for example, police, fire, and medical response teams that may request the location of the at least one UE 104 to assist in critical situations. Further, the LBS providers, such as weather applications, social media applications, maps, etc., may use the location information to offer personalized services to users, such as navigation, geofencing, or targeted advertisements. These services depend on precise location data to enhance user experience and provide contextually relevant content.

[0068] In an aspect, the one or more concurrent location requests include at least one parameter, which may include, but is not limited to, an international mobile subscriber identity (IMSI), an E-UTRAN Cell Global Identifier (ECGI), and a Quality of Service (QoS). The IMSI uniquely identifies the at least one UE 104 in the network 106 and allows the system 108 to correlate location requests with a specific UEsubscription, ensuring that the correct user is targeted even if multiple sessions or devices exist. The ECGI represents the specific radio cell currently serving the at least one UE 104 and is essential for determining the geographical area or cell boundary from which the location measurement will be derived. The ECGI parameter enhances the accuracy and precision of the location estimation process. The QoS parameter specifies the level of service quality expected for the location determination, such as accuracy, response time, and reliability. For example, two or more location requests may be generated by different services, such as a lawful interception authority and an emergency call service, both referencing the same target UE, such as at least one UE 104. These requests may be received by the first location management entity, such as the LMF, and may include parameters such as the IMSI “404900123456789,” the ECGI “404-90- ABCDE1234” representing the serving LTE cell, and a QoS class identifier specifying the required accuracy (for instance, within 50 meters) and response time (for instance, within 5 seconds).

[0069] In an embodiment, the processing unit 210 at the first location management entity is configured to determine at least one network node associated with the at least one UE 104. The at least one network node refers to a network element responsible for managing communication sessions, mobility, and signaling procedures of the at least one UE 104 within the network 106. The at least one network node may include, but is not limited to, a Mobility Management Entity (MME), a Serving Gateway (SGW), or an Access and Mobility Management Function (AMF) in 5G networks. The determination of the network node is essential to ensure that the one or more concurrent location requests are accurately routed to the at least one network node that is currently serving the at least one UE. In order to determine, the processing unit 210 at the first location management entity is configured to retrieve information associated with the at least one network node based on the at least one parameter from a network server, where the retrieved information includes at least one identifier corresponding to the at least one network node that is associated with the at least oneUE 104. The retrieved information enables the first location management entity to accurately identify and forward the one or more concurrent location requests to the appropriate at least one network node for further processing. In an example, the network server may include, but is not limited to, a Home Subscriber Server (HSS), Home Location Register (HLR), or other network databases that store information related to the at least one network node corresponding to the at least one UE 104. When the first location management entity receives the one or more concurrent location requests for the same at least one UE 104, it initiates a request to the network server (such as the HSS or HLR) to retrieve the information associated with that UE. Based on the retrieved information, the processing unit 210 determines which specific MME is currently serving the UE. Further, the processing unit 210 at the first location management entity is configured to select the at least one network node based on the retrieved information. For example, if the received concurrent location request includes an IMSI parameter ‘310260123456789’, the processing unit 210 may retrieve, from the HSS, information indicating that the corresponding UE 104 is being served by a specific network node, such as the MME identified by MME-01. Similarly, based on the ECGI parameter ‘404-90-ABCDE1234’, the processing unit 210 may determine that the at least one UE 104 is connected to a particular cell site managed by that MME.

[0070] In an embodiment, the processing unit 210 at the first location management entity is further configured to transmit the one or more concurrent location requests to the determined at least one network node. The determined at least one network node then acts as an intermediary between the UE and the first location management entity, facilitating accurate location information of the at least one UE 104.

[0071] In an embodiment, the receiving unit 208 at the determined network node is configured to receive the one or more concurrent requests. Further, the processing unit 210 at the determined network node is configured to process the one ormore concurrent location requests. In an aspect, the processing unit 210 may add the received one or more concurrent location requests to a processing queue. The processing queue is a structured data storage mechanism that stores the one or more received concurrent location requests in a specific order, allowing for efficient management and sequential handling.

[0072] In an embodiment, for adding the received one or more concurrent location requests in the processing queue, the processing unit 210 at the at least one network node is configured to determine an insertion order for the received one or more concurrent location requests based on one or more parameters. The one or more parameters may include, but are not limited to, a Quality of Service (QoS) requirement specifying accuracy or response time, a timestamp indicating the order of request arrival, a type of location service (such as real-time tracking or periodic reporting), and a network load condition representing current processing capacity. These parameters enable the processing unit 210 to efficiently organize and manage concurrent location requests, ensuring that critical requests are processed with minimal delay. Further, the processing unit 210 adds the received one or more concurrent location requests to the processing queue in the determined insertion order. In an example, when the one or more concurrent location requests are added to the processing queue, the processing unit 210 is configured to handle these requests sequentially, ensuring that each location request is managed orderly. For example, upon receiving three concurrent location requests, one from the emergency services provider, one from the lawful interception client, and one from the LBS provider, the processing unit 210 may add these requests to the processing queue and assign an execution time based on their respective arrival times. During processing, the processing unit 210 executes the earliest-arrived location request first, followed by subsequent requests in their order of arrival, ensuring that each location request is handled systematically without rejection. In an aspect, the processing unit 210 may enable the option of adding the received one or more concurrent location requests to the processing queue by managing them sequentially,allowing the one or more concurrent location requests to be processed sequentially without rejecting the new location requests. This method ensures that no ongoing location requests are rejected or canceled by the at least one network node and each location request is executed concurrently and independently. By processing requests in this manner, the system 108 enhances overall processing efficiency and minimizes delays, improving response times and resource utilization across the network 106.

[0073] In an aspect, the processing unit 210 is configured to initiate at least one task for handling each of the received one or more concurrent location requests. The processing unit 210 may initiate the at least one task by creating a dedicated instance for each concurrent location request, enabling independent processing. This parallel processing approach minimizes delays, as each location request is handled by its own instance. For example, if the one or more concurrent location requests are received simultaneously, each location request is assigned an individual processing instance i.e., a dedicated instance. In an aspect, the dedicated instance may refer to a specific, independently allocated module created to handle a particular task or request. Each dedicated instance has its own resources (such as memory, processing power, and storage) and operates separately from other instances. For example, in the case of handling the one or more concurrent location requests, the dedicated instance for each request ensures that the processing of one request does not interfere with others. This allows for parallel execution, improving efficiency and reducing latency, particularly in scenarios where multiple requests are made simultaneously. This instance acts as an independent entity dedicated solely to managing and fulfilling that particular location request, allowing the system to handle multiple requests in parallel without interference. Each instance is created dynamically, allowing the system 108 scale with demand by generating additional instances as new requests arrive.

[0074] In an aspect, the processing unit 210 at the network node may monitor a status of each created processing instance to ensure efficient resource use and preventoverload by managing the lifecycle of each processing instance from creation to completion. When the processing instance completes its task, the processing unit 210 releases its resources, making them available for new requests. This cycle of processing instance generation and completion allows the system 108 to handle high volumes of concurrent requests without sacrificing performance. Since a dedicated processing instance manages each request, there is no need to cancel or reject ongoing requests to accommodate new ones. This ensures that all requests, including those from critical services such as lawful interception clients, are processed reliably. The system 108 minimizes wait times and improves overall response speed by processing requests in parallel. Each instance can retrieve and respond to its request independently, resulting in quicker location retrieval for each user or service. In an embodiment, instance-based processing enhances the ability of the system 108 to manage the one or more concurrent requests concurrently, improving scalability, efficiency, and reliability across the network 106. This allows simultaneous processing of multiple requests, ensuring that each request can be managed concurrently and separately, without causing delays or cancellations in other requests.

[0075] In an embodiment, the processing unit 210 at the at least one network node is configured to transmit at least one request to a second location management entity. The second location management entity corresponds to a network element responsible for performing the actual computation or determination of the geographical location of the at least one UE 104. The second location management entity may include, but is not limited to, a Serving Mobile Location Center (SMLC) in GSM / UMTS networks, an Enhanced Serving Mobile Location Center (E-SMLC) in LTE networks, or a Location Management Function (LMF) in 5G networks. For example, when the at least one network node (such as an MME) receives the one or more concurrent location requests for the at least one UE 104, it may forward the request to the E-SMLC. The E-SMLC then determines the precise location of the at least one UE 104.

[0076] In an aspect, on receiving the at least one request, the second location management entity is configured to interact with the at least one UE 104 and a network element associated with the at least one UE 104 to obtain measurement data corresponding to at least one measurement parameter associated with the at least one UE 104. Herein, the network element refers to the radio access network component that is directly responsible for maintaining the communication link with the UE and providing radio measurement data required for positioning. Specifically, the network element may include, but is not limited to, an eNodeB (eNB) in LTE networks, a gNodeB (gNB) in 5G networks. The network element assists the second location management entity (such as the E-SMLC or LMF) by providing measurement data such as timing advance, signal strength, timing of reference signals, or angle of arrival, which are then used to compute the geographical location of the at least one UE 104. The term measurement data refers to the set of radio and network-level observations collected from the at least one UE 104 and the associated network element (for example, eNodeB or gNodeB) that indicate the approximate position of the at least one UE 104 with respect to nearby network nodes. The measurement data is obtained corresponding to the at least one measurement parameter, such as the receive-transmit time difference, reference signal received power (RSRP), and reference signal received quality (RSRQ), reported by the UE 104 or measured by the serving and neighboring cells.

[0077] In an aspect, the second location management entity is configured to compute a location of the at least one UE 104 based on the obtained measurement data. For example, the receive- transmit time difference provides the propagation delay between the at least one UE 104 and the serving cell, while RSRP and RSRQ values indicate the received signal strength and quality from the network element (i.e., the base station). These measurements are collected through a radio resource control (RRC) signaling between the at least one UE 104 and the network element, and then transmitted to the second location management entity (such as the E-SMLC or LMF).Based on the received measurement data, the second location management entity applies one or more positioning algorithms such as Observed Time Difference of Arrival (OTDOA), Enhanced Cell ID (E-CID), or Angle of Arrival (AoA) to compute the geographical coordinates of the at least one UE 104. Further, the second location management entity is configured to transmit a location response to the at least one network node. The location response includes the computed location of the at least one UE 104. For example, the computed location may include parameters such as latitude, longitude, altitude, velocity, timestamp, and an accuracy or uncertainty value indicating the confidence level of the location estimate. It may also include additional information such as the serving cell identifier (ECGI or NR Cell ID) and the positioning method used (for example, OTDOA, E-CID, or GNSS-assisted) to derive the location. Further, the location response is forwarded to the MME for further transmission to the requesting first location management entity.

[0078] In an embodiment, upon receiving the location response from the second location management entity, the processing unit (210) at the at least one network node is configured to forward the received location response to the first location management entity. The first location management entity further transmits the location response to the requesting at least one network entity for further processing or utilization.

[0079] FIG. 3 illustrates an exemplary system architecture 300 configured for processing the one or more concurrent location requests in the network 106, in accordance with an embodiment of the present disclosure.

[0080] In an embodiment, the system architecture 300 may include the network entity 302 (referred to as the at least one network entity in FIG.2), a load balancer (LB) 304, a mobile location center (MLC) 306, one or more pairs of Diameter Routing Agents (DRAs) 312-1 and 312- 2 (collectively referred to as DRA 312), a MME 314 (referred to as the at least one network node in FIG.2), an Evolved Serving Mobilelocation center (E SMLC) 316, an Evolved Node B (eNodeB) 318, the UE 104, a Home Subscriber Server (HSS) 320 and a Query Number Portability database (QNPDB) 322.

[0081] In an embodiment, the network entity 302 may represent the external service that initiates the one or more concurrent location requests. These requests may originate from lawful interception agencies, emergency services, or other locationbased applications that need to determine the geographic position of the UE 104. The network entity 302 sends the one or more concurrent location requests as a web-based query, typically in a format compatible with web protocols (e.g., Representational State Transfer Application Programming Interface call (REST API call) or Hypertext Transfer Protocol POST / GET request (HTTP POST / GET request)). This method is used for transmitting requests over the network 106 while supporting standard web security measures, such as encryption and authentication.

[0082] In an embodiment, the network 106 routes the one or more concurrent location requests from the network entity 302 towards the LB 304. The LB 304 is configured to distribute the incoming one or more concurrent location requests to the appropriate processing node, such as the MLC 306, within the system architecture 300 to prevent overload. By balancing the load, the LB 304 helps maintain optimal performance and reliability within the system architecture 300, ensuring efficient request handling.

[0083] In an embodiment, the MLC 306 is a component within the architecture 300 that processes the received the one or more concurrent location requests and manages the retrieval of location data of the UE 104. The MLC 306 coordinates with other network nodes or components, such as the MME 314 and the E-SMLC 316, to determine the precise location of the UE 104.

[0084] In an aspect, within the MLC 306, a Wireless Location Application (WLA) / Location-Based Services Client (LBSC) node 308 and an X / Gateway MobileLocation Center) (GMLC) 310 are communicating using a Le interface. The X typically refers to an interface or reference point between multiple GMLCs or between GMLC and external entities. The Le interface is a standardized interface specified for exchanging location information between location service nodes within the network 106, particularly between the WLA / LBSC 308 and the GMLC 310. The Le interface is responsible for facilitating communication related to location queries, updates, and responses, ensuring that location data is effectively shared between internal locationprocessing nodes. The primary function of the WLA / LBSC node 308 is to process location data obtained from diverse sources, including mobile devices, network infrastructure, and satellite systems. By interpreting and managing this data, the WLA / LBSC node 308 may offer users services such as navigation, emergency response, tracking, and location-aware marketing. Additionally, the WLA / LBSC node 308 integrates seamlessly with other network components, such as the MME 314 and the X / GMLC 310, to ensure smooth data flow and service delivery. The WLA / LBSC node 308 also manages user preferences and privacy settings, safeguarding compliance with regulations and ensuring that location data is utilized only with user consent.

[0085] In an embodiment, the WLA / LBSC node 308 initiates a request for receiving domain details of the UE 104 to the QNPDB 322, which is needed to process the one or more concurrent location requests. The communication between the WLA / LBSC node 308 and the QNPDB 322 may occur using a protocol such as ENUM. The ENUM protocol translates phone numbers into routing information, enabling the mapping of telephone numbers to the relevant network domains.

[0086] Upon receiving the request for domain details, the QNPDB 322 responds with MCC (Mobile Country Code) and MNC (Mobile Network Code) values (MCC+MNC). These values identify the country and specific network operator of the UE 104 associated with the one or more concurrent location requests. The MCC is a unique code assigned to each country, enabling the network 106 to identify the originof the UE 104. The MNC is a code that identifies a specific mobile network operator within a country. Combined with the MCC, the MNC helps pinpoint the user's network provider uniquely, facilitating accurate routing and network services. MCC and MNC data enable the WLA / LBSC node 308 to determine the relevant network context, assisting in accurately routing the location request and enhancing the location data's precision.

[0087] In an aspect, the X / GMLC 310 serves as the entry point for the one or more location requests to communicate with the MME 314 to retrieve or confirm location information. The MME 314 receives the one or more concurrent location requests from the X / GMLC 310. Upon receiving the one or more concurrent location requests, the X / GMLC 310 initiates a signaling message to the MME 314 through a secure interface, typically using a SLg interface. The SLg interface enables the transfer of the one or more concurrent location requests from the X / GMLC 310 to the MME 314, allowing the MME 314 to obtain the necessary location data from the eNodeB 318 or the E- SMLC 316. By managing this interaction, the MME 314 may process and respond to the one or more concurrent location requests, either by retrieving current location details or confirming previously gathered data, ensuring accurate and timely response to the network entity 302.

[0088] The primary function of the E-SMLC 316 is to acquire precise location information from the UE 104 using various methods, including GPS, Assisted GPS (A- GPS), and network-based positioning techniques. This capability allows the E-SMLC 316 to provide high-accuracy positioning services, which are essential for applications such as emergency response, where accurate location data can be critical. Additionally, the E-SMLC 316 facilitates the delivery of location-based services by ensuring timely access to location information for applications like navigation, tracking, and targeted marketing, thus improving user engagement and experience. The E-SMLC 316 also interfaces seamlessly with other network components, including the MME 314 and theX / GMLC 310, ensuring efficient management of location requests. Furthermore, the E-SMLC 316 supports lawful interception, providing authorized entities access to location data while maintaining compliance with legal standards and protecting user privacy.

[0089] The Le interface allows the WLA / LBSC 308 to query the X / GMLC 310 for further processing, retrieve updated location data, or verify the accuracy of the location provided. In turn, the X / GMLC 310 uses the Le interface to send back precise location data or updates to the WLA / LBSC 308.

[0090] In an embodiment, the HSS 320 may be configured to manage the user information and authentication processes. The HSS 320 stores the user information, such as a subscriber profile, a service detail, and an authentication detail that helps to manage network service for the user. The HSS 320 authenticates the users when they connect to the network 106 and validates the user identity to ensure secure access to the network. The HSS 320 works with the DRAs 312 and the MME 314 to enable location-based services. The WLA / LBSC node 308 communicates with the HSS 320 using a Simple Object Access Protocol (SOAP). The SOAP is a messaging protocol used for exchanging structured information between networked systems, such as the WLA / LBSC node 308 and the HSS 320, typically over a hypertext transfer protocol (HTTP) or simple mail transfer protocol (SMTP). The SOAP protocol is used by the WLA / LBSC node 308 to communicate with the HSS 320, as it ensures the secure, standardized, and interoperable exchange of subscriber and location-related data, thereby ensuring reliability and compliance in mission-critical telecom operations. The WLA / LBSC node 308 queries the HSS 320 to authenticate and authorize the received one or more concurrent location requests.

[0091] In an aspect, when the GMLC 310 receives the one or more concurrent location requests, it will send a query to the HSS 320 to determine the MME 314 that contains the UE 104 context or details of the MME 314 to which the UE 104 is attached.The HSS 320 provides the information requested by the X / GMLC 310. Further the X / GMLC 310 sends the one or more concurrent location requests to the MME 314 via the DRAs 312.

[0092] In an embodiment, the DRA mated pairs 312-1 and 312-2 handle diameter protocol messages used for authentication, authorization, and accounting (AAA) functions within the network 106. The DRAs 312 ensure that location and other signaling messages are routed accurately between the HSS 320, X / GMLC 310 and the MME 314, enhancing reliability and communication efficiency. The DRAs 312 also perform message prioritization, and failover handling, ensuring continuous operation even during node or link failures. In some implementations, the DRAs 312 may also support policy enforcement and subscriber-based routing decisions, further optimizing signaling paths and maintaining session integrity across multiple network domains. The X / GMLC 310 uses Sh and SLg interface with 2 DRAs (312-1, 312-2) to route the one or more concurrent location requests to the MME 314. The Sh interface facilitates the retrieval of location data by communicating with the DRAs 312. The SLg interface enables the transfer of the one or more concurrent location requests from the X / GMLC 310 to the MME 314 via the DRAs 312. Further, the DRA mated pairs 312-1 and 312- 2 are routed using inter DRA routing.

[0093] In an embodiment, once the MME receives the one or more concurrent location requests, it connects to the E-SMLC 316. The E-SMLC 316 determines the exact location of the UE 104. The E-SMLC 316 may utilize various positioning methods, such as GPS or network-based positioning, to retrieve precise location data.

[0094] In an aspect, the MME 314 communicates with the eNodeB 318 using an S 1 -MME interface to determine if the UE 104 is in idle or active mode. The S 1 - MME interface is responsible for the transfer of signaling messages between the eNodeB 318 and the MME 314. The signaling messages are related to user authentication, attachment, session management, and mobility management. If the UE104 is in active mode or has an active session, the UE 104 location message is shared with the eNodeB 318.

[0095] After receiving the location message, the eNodeB 318 sends the location information response to the E-SMLC 316. This response consolidates the data collected from the UE 104 and any additional processing done by the eNodeB 318. This message may include the calculated location of the UE 104, derived from the measurements and positioning techniques applied, along with any contextual information regarding the measurement (e.g., timestamps when the location is collected).

[0096] Once the E-SMLC 316 has calculated the location based on the information received from the eNodeB 318 and UE 104, the E-SMLC 316 sends the location results to the MME 314, the MME 314 further send it to the GMLC 310. After receiving the location data, the GMLC 310 further sent it to the network entity 302 that requested the one or more concurrent location requests.

[0097] FIG. 4 illustrates another exemplary flow diagram of a method 400 for processing the one or more concurrent location requests in the network 106, in accordance with an embodiment of the present disclosure. FIG. 4 is explained with reference to FIGI, FIG. 2, and FIG. 3.

[0098] At step 402, the method 400 includes receiving, by the first location management entity, the one or more concurrent location requests from the at least one network entity for retrieving the location of the at least one UE 104, where each of the one or more concurrent location requests includes the at least one parameter. The at least one parameter may include but not limited to the IMSI, ECGI, and the QoS.

[0099] At step 404, the method 400 includes determining, by the first location management entity, the at least one network node associated with the at least one UE 104. To determine the at least one network node, the first location management enityis configured to retrieve information associated with the at least one network node based on the at least one parameter from the network server, where the retrieved information includes at least one identifier corresponding to the at least one network node that is associated with the at least one UE 104. Further, the first location management entity is configured to select the at least one network node based on the retrieved information.

[0100] At step 406 the method 400 includes transmitting, by the first location management entity, the one or more concurrent location requests to the determined at least one network node.

[0101] At step 408, the method 400 includes processing, by the at least one network node, the received one or more concurrent location requests by performing one of adding, by the at least one network node, the received one or more concurrent location requests in a processing queue. For adding the received one or more concurrent location requests in the processing queue the at least one network node is configured to determine an insertion order for the received one or more concurrent location requests based on the one or more parameters and add the received one or more concurrent location requests to the processing queue in the determined insertion order.

[0102] Alternatively, at step 410, the method includes initiating, by the at least one network node, at least one task for handling each of the received one or more concurrent location requests.

[0103] In an aspect, the method 400 includes transmitting, by the at least one network node, the at least one request to the second location management entity. On receiving the at least one request, the second location management entity is configured to interact with the at least one UE 104 and the network element associated with the at least one UE 104 to obtain the measurement data corresponding to the at least one measurement parameter associated with the at least one UE 104. The at least onemeasurement parameter may include, but is not limited to, the UE receive-transmit time difference, the RSRP, and the RSRQ. Further, the second location management entity is configured to compute a location of at least one UE 104 based on the obtained measurement data and transmit the location response to at least one network node, where the location response includes the computed location of at least one UE 104.

[0104] In an aspect, the at least one network node is configured to receive the location response from the second location management entity. Additionally, the at least one network node is configured to transmit the location response to the first location management entity. Further, the first location management entity forwards, the location response to the at least one network entity.

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

[0106] As shown in FIG. 5, the computer system 500 may include an external storage device 510, a bus 520, a main memory 530, a read-only memory 540, a mass storage device 550, communication port(s) 560, and a processor 570. A person skilled in the art will appreciate that the computer system 500 may include more than one processor and communication ports. The processor 570 may include various modules associated with embodiments of the present disclosure. The communication port(s) 560 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) 560 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 500 connects.

[0107] In an embodiment, the main memory 530 may be a Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 540 may be any static storage device(s) e.g., but not limited to, aProgrammable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor 570. The mass storage device 550 may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device 550 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 Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.

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

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

[0110] In an exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for processing one or more concurrent location requests in a network is described. The method includes receiving, by a first locationmanagement entity, the one or more concurrent location requests from at least one network entity for retrieving a location of at least one user equipment (UE), each of the one or more concurrent location requests includes at least one parameter. The method includes determining, by the first location management entity, at least one network node associated with the at least one UE. The method includes transmitting, by the first location management entity, the one or more concurrent location requests to the determined at least one network node. The method includes processing, by the at least one network node, the received one or more concurrent location requests by performing one of: adding, by the at least one network node, the received one or more concurrent location requests in a processing queue and initiating, by the at least one network node, at least one task for handling each of the received one or more concurrent location requests.

[0111] The present disclosure provides a technical advancement in the field of network-based location service management. Conventionally, location requests associated with multiple UEs are processed sequentially, resulting in increased latency, higher processing load on location management entities, and delayed delivery of positioning information. The disclosed method enables concurrent processing of multiple location requests by intelligently managing request queuing, prioritization, and execution across network nodes and location management entities. This concurrent handling reduces response time, improves resource utilization, enhances scalability under heavy load conditions, and ensures faster and more reliable determination of UE location.

[0112] In an operative aspect, the existing methods for handling concurrent location requests in telecommunications typically involve rejecting new requests when a Mobility Management Entity (MME) is already processing a request. This approach can lead to inefficiencies and missed opportunities for timely service. Further, in some existing methods, when the MME receives several concurrent location requests, it oftenprioritizes existing ones by rejecting additional incoming requests. This can result in critical delays, particularly when timely location data, such as emergency services or lawful interception, is essential.

[0113] If the options to reject, cancel, or defer new requests are removed from these methods, the MME must adopt a more proactive approach to manage all incoming requests concurrently and independently. This shift would enable the MME to process multiple requests simultaneously without prioritizing one over another. As a result, the MME would become more responsive, ensuring that location requests from various agencies, such as police, fire departments, and emergency medical services, are handled without failure or delay.

[0114] The change disclosed by the present disclosure would significantly enhance the reliability and efficiency of location services. By eliminating the need to reject or defer requests, the MME would ensure that no critical data is lost or delayed, improving overall service delivery. Furthermore, this parallel processing capability would foster better inter-agency collaboration during emergencies, where every second counts. In summary, transitioning to a model that allows for concurrent processing of location requests would optimize resource utilization and support the effectiveness of critical services reliant on accurate and timely location data.

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

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

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

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

[0119] The present disclosure effectively manages multiple location requests, ensuring that each location request is processed efficiently and without delay, thus improving overall responsiveness.

[0120] The present disclosure improves the success rate for location requests by processing the received requests in parallel rather than rejecting the received concurrent location requests.

[0121] The present disclosure improves location-related key performance indicators (KPIs), leading to minimal chances of failures when location is requested by the lawful interception clients or during emergency calls.

[0122] The present disclosure optimizes the approach of MME allocating network resources when processing the one or more concurrent location requests, reducing unnecessary rejections and cancellations. This improved resource management allows for a higher overall throughput of the location requests, leading to a more stable network and minimizing congestion during high-demand periods.

[0123] The present disclosure provides a method that enhances network reliability by ensuring consistent and predictable handling of concurrent location requests, even under heavy signaling load conditions.

[0124] The present disclosure provides a scalable solution that can adapt to increasing volumes of location requests as network traffic grows, ensuring sustained performance and service continuity in evolving network architectures such as 4G, 5G, and beyond.

Claims

CLAIMS1. A method (400) for processing one or more concurrent location requests in a network (106), the method (400) comprising: receiving (402), by a first location management entity, the one or more concurrent location requests from at least one network entity for retrieving a location of at least one user equipment (UE), wherein each of the one or more concurrent location requests comprises at least one parameter; determining (404), by the first location management entity, at least one network node associated with the at least one UE; transmitting (406), by the first location management entity, the one or more concurrent location requests to the determined at least one network node; processing (408), by the at least one network node, the received one or more concurrent location requests by performing one of: adding, by at least one network node, the received one or more concurrent location requests in a processing queue; and initiating (410), by the at least one network node, at least one task for handling each of the received one or more concurrent location requests.

2. The method (400) as claimed in claim 1, comprising: transmitting, by the at least one network node, at least one request to a second location management entity.

3. The method (400) as claimed in claim 1, wherein the at least one parameter comprises an international mobile subscriber identity (IMSI), an E-UTRAN Cell Global Identifier (ECGI), and a Quality of Service (QoS).

4. The method (400) as claimed in claim 1, comprising: retrieving, by the first location management entity, information associated with the at least one network node based on the at least one parameter from a network server, wherein the retrieved information includes at least one identifier corresponding to the at least one network node that is associated with the at least one UE, and selecting, by the first location management entity, the at least one network node based on the retrieved information.

5. The method (400) as claimed in claim 2, further comprising: on receiving the at least one request, interacting, by the second location management entity, with the at least one UE and a network element associated with the at least one UE to obtain measurement data corresponding to at least one measurement parameter associated with the at least one UE; computing, by the second location management entity, a location of the at least one UE based on the obtained measurement data; and transmitting, by the second location management entity, a location response to the at least one network node wherein the location response includes the computed location of the at least one UE.

6. The method (400) as claimed in claim 5, wherein the at least one measurement parameter includes at least one of a UE receive-transmit time difference, a reference signal received power (RSRP), and a reference signal received quality (RSRQ).

7. The method (400) as claimed in claim 5, further comprising: receiving, by the at least one network node, the location response from the second location management entity; transmitting, by the at least one network node, the location response to the first location management entity; and forwarding, by the first location management entity, the location response to the at least one network entity.

8. The method (400) as claimed in claim 1, wherein adding the received one or more concurrent location requests in the processing queue comprising: determining, by the at least one network node, an insertion order for the received one or more concurrent location requests based on one or more parameters; and adding, by the at least one network node, the received one or more concurrent location requests to the processing queue in the determined insertion order.

9. A system (108) for processing one or more concurrent location requests in a network (106), the system (108) comprising: a receiving unit (208) at a first location management entity configured to receive the one or more concurrent location requests from at least one network entity for retrieving a location of at least one user equipment (UE), wherein each of the one or more concurrent location requests comprises at least one parameter; a processing unit (210) at the first location management entity determine at least one network node associated with the at least one UE;transmit the one or more concurrent location requests to the determined at least one network node; wherein the receiving unit (208) at the at least one network node is configured to receive the one or more concurrent location requests, and the processing unit (210) at the at least one network node is configured to perform one of: add the received one or more concurrent location requests in a processing queue; and initiate at least one task for handling each of the received one or more concurrent location requests.

10. The system (108) as claimed in claim 9, wherein the processing unit (210) at the at least one network node is configured to transmit at least one request to a second location management entity.

11. The system (108) as claimed in claim 9, wherein the at least one parameter comprises an international mobile subscriber identity (IMSI), an E-UTRAN Cell Global Identifier (ECGI), and a Quality of services (QoS).

12. The system (108) as claimed in claim 9, wherein to determine at least one network node associated with the at least one UE, the processing unit (210) at the first location management entity is configured to: retrieve information associated with the at least one network node based on the at least one parameter from a network server, wherein the retrieved information includes at least one identifier corresponding to the at least one network node that is associated with the at least one UE, and select the at least one network node based on the retrieved information.

13. The system (108) as claimed in claim 9, wherein on receiving the at least one request, the second location management entity is configured to: interact with the at least one UE and a network element associated with the at least one UE to obtain measurement data corresponding to at least one measurement parameter associated with the at least one UE; compute a location of the at least one UE based on the obtained measurement data; and transmit a location response to the at least one network node, wherein the location response includes the computed location of the at least one UE.

14. The system (108) as claimed in claim 13, wherein the at least one measurement parameter includes at least one of a UE receive-transmit time difference, a reference signal received power (RSRP), and a reference signal received quality (RSRQ).

15. The system (108) as claimed in claim 13 comprises: the receiving unit (208) at the at least one network node is configured to receive the location response from the second location management entity; the processing unit (210) at the at least one network node is configured to transmit the location response to the first location management entity and forward the location response to the at least one network entity.

16. The system (108) as claimed in claim 9, wherein for adding the received one or more concurrent location requests in the processing queue, the processing unit (210) at the at least one network node is configured to: determine an insertion order for the received one or more concurrent location requests based on the one or more parameters; andadd the received one or more concurrent location requests to the processing queue in the determined insertion order.

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 (400) for processing one or more concurrent location requests in a network (106), the method comprising: receiving (402), by a first location management entity, the one or more concurrent location requests from at least one network entity for retrieving a location of at least one user equipment (UE), wherein each of the one or more concurrent location requests comprises at least one parameter; determining (404), by the first location management entity, at least one network node associated with the at least one UE; transmitting (406), by the first location management entity, the one or more concurrent location requests to the determined at least one network node; processing (408), by the at least one network node, the received one or more concurrent location requests by performing one of: adding, by the at least one network node, the received one or more concurrent location requests in a processing queue; and initiating (410), by the at least one network node, at least one task for handling each of the received one or more concurrent location requests.

Images