System and method for handling location request associated with a serving cell in communication network

Abstract

Disclosed is a system (400) and a method (500) for handling location request associated with a serving cell in a communication network. The system comprises a Gateway Mobile Location Center (GMLC) (240) which receives location request from a User Equipment (UE) (106), such as Lawfully Intercepted Management Client (LIM) (408), and identifies whether the request is solely to retrieve serving cell information. Based on identifiers such as IMSI or MSISDN, the GMLC queries a Home Subscriber Server (HSS) (402) or Unified Data Management (UDM) (210) to obtain corresponding subscriber data. The GMLC (240) fetches a destination realm from a Query Number Portability Database (QNPDB) (404) for proper routing. Instead of triggering a conventional Positioning Location Request (PER), the GMLC (240) uses cached mappings to determine the latitude-longitude coordinates of the serving cell. The location information is transmitted back to the UE (106), significantly reducing signaling load and improving response efficiency.

Description

SYSTEM AND METHOD FOR HANDLING LOCATION REQUEST ASSOCIATED WITH A SERVING CELL IN COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks and systems. More particularly, the present disclosure relates to a system and a method for handling location request associated with a serving cell in a communication network.BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely due to its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] With an advent of technological advancements in the field of telecommunications, several wireless technologies have been developed to meet a growing demand for high-speed broadband connectivity and better mobile applications and services. As mobile and cellular communication networks evolve, they are facing increased data traffic and a significant rise in the number of connected devices. As a result, achieving maximum throughput and ensuring uninterrupted service have become top priorities for network operators and service providers. To maintain optimal performance, mobile networks must manage various operational aspects efficiently, including a provisioning of location information for nodes within the network.

[0004] In telecommunication networks, an ability to accurately locate network nodes, such as mobile devices and base stations, is critical for ensuring efficient network operations. Location-based information is typically used to provideservices such as emergency response, traffic management, and network optimization. In certain scenarios, such as lawful interception or network diagnostics, it is often sufficient to know only serving cell location and its associated information, such as a cell identifier, and a Tracking Area Code (TAC). However, currently available techniques in 4thGeneration (4G) and 5thGeneration (5G) networks generally provide detailed subscriber location information which may not be necessary for these specific scenarios. These techniques fulfill requests for precise subscriber positioning but do not provide a provision of fetching only serving cell information in Provide Location Request (PLR) for both 4G and 5G subscribers using International Mobile Subscriber Identity (IMSI) or Mobile Station International Subscriber Directory Number (MSISDN). This limitation creates unnecessary complexity and increases a load on the network when only basic cell information is required.

[0005] Further, as the currently available techniques are designed to provide detailed location data, this requires a considerable number of resources to process and deliver, which includes querying multiple network elements. Each of these queries demands additional processing power, memory, and network bandwidth. In cases where only the serving cell information is needed, a retrieval of full location data introduces inefficiencies that waste network resources and increase operational costs.

[0006] In light of the aforementioned challenges, there is a need for a solution that allows for the retrieval of only necessary serving cell information.SUMMARY

[0007] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key / critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0008] According to an aspect of a present disclosure, a method for handling location request associated with a serving cell in a communication network is disclosed. The method comprises receiving, by a receiving module at a Gateway Mobile Location Centre (GMLC), the location request from a User Equipment (UE). The method further comprises identifying, by an identifying module based on the location request, if the location request is solely to retrieve serving cell information associated with a subscriber. The method further comprises retrieving, by a retrieving module from a subscriber database, the serving cell information based on a result of the identification that the location request is solely to retrieve the serving cell information. The method further comprises determining, by a determining module, location information of the serving cell using a cache memory based on the serving cell information and transmitting, by a transmitting module, the serving cell information including the location information of the serving cell to the UE.

[0009] In one or more implementations, the location request includes one of an International Mobile Subscriber Identity (IMSI) or a Mobile Station International Subscriber Directory Number (MSISDN) associated with the subscriber.

[0010] In one or more implementations, for retrieving the serving cell information associated with the subscriber, the method comprises sending, by the transmitting module, a first User Data Request (UDR) to the subscriber database when the location request excludes MSISDN and retrieving, by the retrieving module from the subscriber database, the MSISDN associated with the subscriber in response to the first UDR. The method further comprises sending, by the transmitting module, a second UDR to the subscriber database in response to the retrieved MSISDN and determining, by the determining module from the subscriber database, the serving cell information associated with the subscriber in response to the second UDR.

[0011] In one or more implementations, the subscriber database is at least one of a Home Subscriber Server (HSS) and a Unified Data Management (UDM).

[0012] In one or more implementations, the retrieving of the MSISDN and the determining of the serving cell information is performed using a Subscriber Handling (SH) microservice, and the transmitting of the serving cell information including the location information of the serving cell is performed using a Location Enabler (LE) microservice.

[0013] In one or more implementations, the method further comprises determining, by the determining module from a portability database, a network entity associated with MSISDN when the MSISDN is present in the location request and sending, by the transmitting module, a User Data Request (UDR) to the subscriber database associated with the network entity. The method further comprises determining, by the determining module from the subscriber database, the serving cell information associated with the subscriber in response to the UDR.

[0014] In one or more implementations, the serving cell information includes a cell identifier including a Tracking Area Code (TAC).

[0015] According to another aspect of the present disclosure, a system for handling location request associated with a serving cell in a communication network is disclosed. The system comprises a Gateway Mobile Location Centre (GMLC). The GMLC comprises a receiving module, an identifying module, a retrieval module, a determining module and a transmitting module. The receiving module is configured to receive the location request from a User Equipment (UE). The identifying module is configured to identify, based on the location request, if the location request is solely to retrieve serving cell information associated with a subscriber. The retrieval module is configured to retrieve, from a subscriber database, the serving cell information based on a result of the identification that the location request is solely to retrieve the serving cell information. The determining module is configured to determine location information of the serving cell using a cache memory based on the serving cell information and the transmitting module is configured to transmit the serving cell information including the location information of the serving cell to the UE.BRIEF DESCRIPTION OF DRAWINGS

[0016] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

[0017] FIG. 1 illustrates an exemplary communication environment, in accordance with an embodiment of the present disclosure.

[0018] FIG. 2 illustrates a block diagram depicting exemplary components of a core network, in accordance with an embodiment of the present disclosure.

[0019] FIG. 3 illustrates a block diagram depicting an architecture of a Gateway Mobile Location Center (GMLC), in accordance with an example embodiment of the present disclosure.

[0020] FIG. 4 illustrates a block diagram depicting an architecture of a communication system handling the location request associated with a serving cell in a communication network, in accordance with an embodiment of the present disclosure.

[0021] FIG. 5 illustrates a flowchart depicting a method for handling the location request associated with the serving cell in the communication network, in accordance with an embodiment of the present disclosure.

[0022] FIG. 6 illustrates a schematic block diagram of a computing system for handling the location request associated with the serving cell in the communication network, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

[0023] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0024] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0025] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” or “some implementations” which may each refer to one or more or all of the same or different embodiments or implementations. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” or “in an implementation” refers to one embodiment or one implementation and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.”.Further, the term, for example, “in one or more implementations” refers to “at least one implementation, or more than one implementation, or all implementations.

[0026] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0027] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.

[0028] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0029] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0030] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0031] An object of the present disclosure is to provide a system and a method for retrieving serving cell information in a communication network.

[0032] Another object of the present disclosure is to provide a system and a method that facilitates minimizing a consumption of network resources (processing power, bandwidth, and memory) by focusing solely on retrieving the serving cell information, thereby reducing an overhead associated with retrieving detailed subscriber location information.

[0033] The present disclosure relates to the system and the method for handling location request associated with a serving cell in the communication network, specifically in 4th Generation (4G) and 5th Generation (5G) networks. In particular, the present disclosure ensures that the location request is processed specifically (or solely) for retrieving the serving cell information, distinguishing it from other types of location-based queries.

[0034] Several key terms used in the description play pivotal roles in facilitating the system functionality. In order to facilitate an understanding of the description, the key terms are defined below.

[0035] User Equipment (UE)- The UE may refer to a device used by a subscriber to communicate with a wireless network. The UE may include, but is not limited to, smartphones, tablet computers, laptops, wearable devices such as smartwatches, or Internet of Things (loT) devices, or other terminal capable of initiating the location request. For instance, the subscriber using a 5G enabled smartphone may initiate the location request for navigation services.

[0036] Gateway Mobile Location Centre (GMLC)- The GMLC may refer to a core network entity responsible for receiving and processing location service requests from external applications and initiates retrieval of subscriber location data.

[0037] The serving cell information- The serving cell information may refer to subscriber location data information that identifies the serving cell currently handling communication for the subscriber and may include a cell identifier (ID) and Tracking Area Code (TAC).

[0038] Location information- The location information may refer to geographic coordinates (latitude and longitude) corresponding to the serving cell in which the subscriber is currently located.

[0039] Cache memory- The cache memory may refer to a memory component used to store mappings of cell identifiers (such as the cell ID and the TAC) to corresponding location coordinates (the latitude and the longitude), thereby enabling quick lookups.

[0040] International Mobile Subscriber Identity (IMSI)- The IMSI may refer to a unique identifier assigned to the subscriber in a cellular network.

[0041] Mobile Station International Subscriber Directory Number (MSISDN)- The MSISDN may refer to a number uniquely identifying a subscription in a mobile network (commonly referred to as a “mobile number”).

[0042] User Data Request (UDR)- The UDR may refer to a request sent to a subscriber database to retrieve subscriber-related data, such as the MSISDN or the serving cell information.

[0043] Subscriber handling (SH) microservice- The SH microservice may refer to a modular service that handles subscriber identity resolution, such as mapping the IMSI to the MSISDN.

[0044] Location Enabler (LE) microservice- The LE microservice may refer to the modular service that determines and transmits the location information based on serving cell data.

[0045] The TAC- The TAC may refer to a code used to identify a group of cells in the mobile network, used together with the cell ID to identify the serving cell uniquely.

[0046] Home Subscriber Server (HSS)- The HSS may refer to a core network database in Long Term Evolution (LTE) systems that contains user-related and subscription-related information.

[0047] Unified Data Management (UDM)- The UDM may refer to a 5G network function that serves as a centralized data repository for subscriber profiles, handling functions similar to the HSS in the 4G but is specifically for service-based architecture in the 5G networks.

[0048] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 6, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0049] FIG. 1 illustrates an exemplary communication environment 100, in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the communication environment 100 includes a core network 102 coupled with a plurality of nodes including Node 104-1 through Node 104-N and configured to facilitate a secured communication among the plurality of nodes (collectively referred to as the “nodes 104”, and individually referred to as the “node 104”, hereinafter).

[0050] In an implementation, each of the nodes are configured to be coupled with one or more User Equipment (UEs) 106-1, 106-2, 106-3, 106-4, through 106-(N-l), 106-N (collectively referred to as the “UE(s) 106”, hereinafter). The UE 106 may correspond to, but not limited to, mobile phones, tablets, or laptops. In one aspect, the core network 102 may establish a secured communication between the UEs 106 associated with the nodes 104. In another aspect, the core network 102 may establish the secured communication between the UEs 106 associated with the same node.

[0051] In an exemplary implementation, the core network 102 may effectively establish the secured communication between the UE 106-1 and the UE 106-2, where the UE 106-1 and the UE 106-2 both are coupled with the Node 104-1. In another implementation, the core network 102 may establish the secured communication between the UE 106-2 and the UE 106-N with equal effectiveness, where the UE 106-2 is coupled with the Node 104-1 and the UE 106-N is coupled with the Node 104-N.

[0052] In an example implementation, the core network 102 (also, referred to as a network 102, hereinafter) may be configured as an application server and may be communicably operational or may be integrated with the UE 106 via a network coupled with the application server. The network 102 may pertain to 5G servicebased architecture and may be configured to interconnect distinct networks associated with the architecture. Therefore, the network 102 may provide a path for the exchange of information between the networks, and corresponding subnetworks.

[0053] Although FIG. 1 illustrates one example of the communication environment 100, various changes may be made to FIG. 1. For example, the communication environment 100 may include any number of nodes and the UEs in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components in FIG. 1 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0054] FIG. 2 illustrates a block diagram depicting exemplary components of the network 102, in accordance with an embodiment of the present disclosure. As shownin FIG. 2, the network 102 may include the UE 106, a Radio Access Network (RAN) 236 i.e., the node 104 configured to communicate with an Access and Mobility Management Function (AMF) 202, a Unified Data Management (UDM) 210, a Network Exposure Function (NEF) 226, and a Gateway Mobile Location Center (GMLC) 240.

[0055] Further, the network 102 includes a Policy Control Function (PCF) 204, an Equipment Identity Register (EIR) 206, an Authentication Server Function (AUSF) 208, a Short Message Service Function (SMSF) 212, a Network Slice Selection Function (NSSF) 214, a Session Management Function (SMF) 216, a Network Data Analytics Function (NWDAF) 218, Charging Function-Protocol Converter (CHF- PC) 220, Signaling Transfer Point (STP) 222, a Diameter Routing Agent (DRA) 224, a Binding Support Function (BSF) 228, a User Plane Function (UPF) 230, a Data Network (DN) 232, a Location Management Function (LMF) 234, and Location Services (LCS) 238.

[0056] The components depicted in FIG. 2 may be implemented as dedicated hardware components or as virtualized functions implemented on top of a common shared physical infrastructure using Software-Defined Networking (SDN). For example, an SDN controller may implement one or more of the components of FIG. 2 using an adapter implementing a Virtual Network Function (VNF) virtual machine, an event driven serverless architecture interface, and / or another type of SDN architecture.

[0057] The AMF 202 may be a network element that is capable of performing registration management, connection management, reachability management, mobility management, lawful intercepts, Short Messaging Service (SMS) transport between the UE 106 and SMSF 212, session management messages transport between the UE 106 and the SMF 216, access authentication and authorization, location services management, functionality to support non-3GPP access networks, and / or other types of management processes. In an implementation, the AMF 202may help locate a serving cell associated with the UE 106 by responding to queries from the GMLC 240.

[0058] The PCF 204 is a network node capable of supporting policies to control network behavior, provide policy rules to control plane functions (e.g., to the SMF 216), access subscription information relevant to policy decisions, perform the policy decisions, and / or perform other types of processes associated with policy enforcement.

[0059] The EIR 206 may correspond to an independent network component that may help telecom operators in protecting the telecom networks. The EIR 206 may aid in protecting a network by providing a mechanism to restrict malicious user terminals or devices in the network. In an implementation, the EIR 206 may ensure that only legitimate devices are associated with the serving cell. Before processing the Provider Location Request (PLR), the GMLC 240 may query the EIR 206 to verify that the user device associated with the IMSI / MSISDN is authorized to operate in the network 102.

[0060] The AUSF 208 may be a network element that is capable of performing the authentication. In an implementation, the AUSF 208 may handle the authentication of UEs IMSI / MSISDN in coordination with the UDM 210 before the subscriber's serving cell information is retrieved. When the GMLC 240 initiates the PLR for the serving cell information, the AUSF 208 ensures that the UE 106 involved in the request is a valid and authorized entity in the network 102.

[0061] The UDM 210 may be a network element that is capable of maintaining subscription information for the UEs 106, manage subscriptions, generate authentication credentials, handle user identification, perform access authorization based on subscription data, perform network function registration management, maintain service and / or session continuity by maintaining assignment of the SMF 216 for ongoing sessions, support SMS delivery, support lawful intercept functionality, and / or perform other processes associated with managing user data. In an implementation, the UDM 210 is queried by the GMLC 240 during thelocation request process to fetch the subscriber information, such as a mapping of the IMSI to a corresponding serving AMF 202.

[0062] The SMSF 212 may be a network element that is capable of performing SMS services for the UEs 106. The NSSF 214 includes devices that select network slice instances for the UEs 106. By providing network slicing, the NSSF 214 allows an operator to deploy multiple substantially independent end-to-end networks potentially with the same infrastructure. In an implementation, the NSSF 214 may ensure that a correct network slice is selected for the UE 106 based on the location or service request.

[0063] The SMF 216 may be a network element that is capable of performing session establishment, session modification, and / or session release, perform IP address allocation and management, perform Dynamic Host Configuration Protocol (DHCP) functions, perform selection and control of the UPF 230, configure traffic steering at the UPF 230 to guide the traffic to the correct destinations, terminate interfaces toward the PCF 204, perform lawful intercepts, charge data collection, support charging interfaces, control and coordinate of charging data collection, terminate session management parts of NAS messages, perform downlink data notification, manage roaming functionality, and / or perform other types of control plane processes for managing user plane data.

[0064] The NWDAF 218 may be a network element that is capable of collecting analytics information associated with RAN and / or the network 102. The CHF -PC 220 may be a network element that is capable of controlling and managing charging- related operations within the network 102. The CHF-PC 220 coordinates communication between the CHF, the PCF 204, and session management entities to ensure accurate and timely charging of subscriber services.

[0065] The STP 222 corresponds to a centralized system responsible for managing the transition of network services between multi-RATs. The DRA 224 may be a network element that is used for signaling in mobile networks, particularly for the authentication, authorization, accounting (AAA), and the location requests. In animplementation, the DRA 224 may handle signaling messages related to the PLR. The DRA 224 may route the Diameter messages between various network nodes, such as the GMLC 240 and other core network elements.

[0066] The NEF 226 may be a network element that is capable of exposing capabilities and events to other Network Functions (NFs), including third party NFs, AFs, edge computing NFs, and / or other types of NFs. In an implementation, the NEF 226 may provide additional contextual information to the GMLC 240 if required for lawful interception or other purposes.

[0067] The BSF 228 may be a network element that is capable of managing session bindings and subscriber contexts within the network 102. The UPF 230 may be a network element that is capable of maintaining an anchor point for intra / inter-RAT mobility, maintain an external Packet Data Unit (PDU) point of interconnect to the DN 232, perform packet routing and forwarding, perform the user plane part of policy rule enforcement, perform packet inspection, perform lawful intercept, perform traffic usage reporting, perform QoS handling in the user plane, perform uplink traffic verification, perform transport level packet marking, perform downlink packet buffering, forward an “end marker” to the RAN 236 (e.g., gNB), and / or perform other types of user plane processes.

[0068] The LMF 234 may be a network element that is capable of managing subscriber location information within the network 102. The LMF 234 may track the current location of mobile devices, handles location updates, and supports mobility management functions such as handover and roaming. The LMF 234 may interface with network elements such as the RAN 236, the AMF 202, and locationbased service platforms to ensure seamless mobility management and locationbased service provisioning for the subscribers. In an implementation, the LMF 234 processes the PLR that are related to the serving cell of the subscriber. When the PLR is sent, the LMF 234 ensures that the LMF retrieves correct location information (such as the cell ID and the TAC) for the requested subscriber.

[0069] The LCS 238 may be a network element that is capable of enabling provisions of location-based functionalities and applications within the network 102. The LCS 238 may interface with application servers, service platforms, and subscriber devices to deliver personalized and context-aware location-based experiences. In an implementation, the LCS 238 is responsible for handling the PLR requests and ensuring that the requested serving cell information is available. When the PLR is initiated (using the IMSI or the MSISDN), the LCS 238 may ensure that the serving cell data is retrieved and passed to relevant network functions.

[0070] The GMLC 240 is configured to provide location-based services within the network 102. The GMLC 240 facilitates the retrieval of mobile device location information, enabling services such as emergency call routing, location-based advertising, and asset tracking. The GMLC 240 may interface with location-based service applications and network elements to provide accurate location data while ensuring user privacy and compliance with regulatory requirements.

[0071] Although FIG. 2 shows exemplary components of the network 102, in other implementations, the network 102 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the network 102 may perform functions described as being performed by one or more other components of the network 102.

[0072] FIG. 3 illustrates a block diagram depicting an architecture of the GMLC 240, in accordance with an example embodiment of the present disclosure.

[0073] As shown in FIG. 3, the GMLC 240 includes a processor 302, a memory 304, a communication interface 306, an Input / Output (I / O) interface 308, and processing modules 310. Components of the GMLC 240 are coupled to each other via a first communication bus 300-2. The processor 302 interacts with each component for handling the location request associated with the serving cell in the communication network. In an embodiment, the GMLC 240 is implemented on a GMLC server.

[0074] The processor 302 may include various processing circuitry and communicate with the memory 304, and the communication interface 306 via the first communication bus 300-2. The processor 302 is configured to execute instructions or a set of instructions stored in the memory 304 to perform various processes. In an implementation, the processor 302 may also include the processing modules 310. Components of the processing modules are coupled to each other via a second communication bus 300-4.

[0075] The processor 302 may include a general-purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, a Graphics-only Processing Unit such as a Graphics Processing Unit (GPU) or the like, a programmable logic device, or any combination thereof.

[0076] The memory 304 stores the set of instructions required by the processor 302 of the GMLC 240 for controlling its overall operations. The memory 304 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of Electrically Programmable Memories (EPROM) or Electrically Erasable and Programmable (EEPROM) memories. In addition, the memory 304 may, in some examples, be considered a non -transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted as the memory 304 is non-movable. In some examples, the memory 304 may be configured to store larger amounts of information. In certain examples, a non- transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 304 may be an internal storage unit or an external storage unit of the GMLC 240, cloud storage, or any other type of external storage.

[0077] The communication interface 306 may include an electronic circuit specific to a standard that enables wired or wireless communication. The communication interface 306 is configured for communicating with external devices via networks.

[0078] The I / O interface 308 may include suitable logic, circuitry, interfaces, and / or codes that may be configured to receive input(s) and present (or display) output(s) on the GMLC 240. For example, the I / O interface 308 may have an input interface (not shown) and an output interface (not shown). The input interface may be configured to enable a user to provide input(s) to trigger (or configure) the GMLC 240 for performing data processing operation(s). Examples of the input interface may include, but are not limited to, a touch interface, a mouse, a keyboard, a motion recognition unit, a gesture recognition unit, a voice recognition unit, or the like. The output interface may be configured to display (or present) output(s) generated (or provided) by the GMLC 240. In some aspects of the present disclosure, the output interface may provide the output(s) based on an instruction provided by the user of the GMLC 240, by way of the input interface. Examples of the output interface may include, but are not limited to, a digital display, an analog display, a touch screen display, an appearance of a desktop, and / or illuminated characters. Aspects of the present disclosure are intended to include or otherwise cover any type of the input interface and output interface in the I / O interface 308, including known, related art, and / or later developed technologies without deviating from the scope of the present disclosure.

[0079] The processing modules 310 include a receiving module 320, an identifying module 330, a retrieving module 340, a determining module 350 and a transmitting module 360. The receiving module 320 is configured to receive, at the GMLC, the location request from the UE 106. The identifying module 330 is configured to identify, based on the location request, if the location request is solely to retrieve the serving cell information associated with the subscriber. The retrieving module 340 is configured to retrieve, from the subscriber database, the serving cell information based on a result of the identification that the location request is solely to retrieve the serving cell information. The determining module 350 is configured todetermine the location information of the serving cell using the cache memory based on the serving cell information and the transmitting module 360 is configured to transmit the serving cell information including the location information of the serving cell to the UE 106.

[0080] Further, to retrieve the serving cell information associated with the subscriber, the transmitting module 360 is configured to send a first UDR to the subscriber database when the location request excludes the MSISDN. The retrieving module 340 is configured to retrieve, from the subscriber database, the MSISDN associated with the subscriber in response to the first UDR. The transmitting module 360 is configured to send a second UDR to the subscriber database in response to the retrieved MSISDN and the determining module 350 is configured to determine, from the subscriber database, the serving cell information associated with the subscriber in response to the second UDR. The first UDR is initiated when the location request received from the UE 106 does not include the MSISDN, but only includes the IMSI. The primary objective of the first UDR is to retrieve the MSISDN associated with the IMSI. The subscriber database responds to the first UDR by mapping the IMSI to the corresponding MSISDN. Upon successful retrieval of the MSISDN via the first UDR, the second UDR is issued. The second UDR is used to retrieve the actual serving cell information, such as the cell ID, the TAC. Again, the subscriber database processes this request and utilizes the resolved MSISDN to locate the subscriber’s serving cell data.

[0081] The determining module 350 is further configured to determine, from a portability database, a network entity associated with MSISDN when the MSISDN is present in the location request. The transmitting module 360 is further configured to send the UDR to the subscriber database associated with the network entity and the determining module 350 is configured to determine the serving cell information associated with the subscriber in response to the UDR.

[0082] Although FIG. 3 illustrates one example of the GMLC 240, various changes may be made to FIG. 3. Further, various components in FIG. 3 may be combined,further subdivided, or omitted, and additional components may be added according to particular needs.

[0083] FIG. 4 illustrates a block diagram depicting an architecture of a communication system 400 for handling the location request associated with the serving cell in the communication network, in accordance with an embodiment of the present disclosure. The embodiment of the communication system 400 as shown in FIG. 4 is for illustration only. However, the communication system 400 may come in a wide variety of configurations, and FIG. 4 does not limit the scope of the present disclosure to any particular implementation of the communication system 400 (may also be referred as the “system 400”).

[0084] As shown in FIG. 4, the system 400 includes the GMLC 240, the UDM 210, a Home Subscriber Server (HSS) 402, a Query Number Portability Database (QNPDB) 404, and a Mobility Management Entity (MME) 406. The GMLC 240 is communicatively coupled with the UDM 210, the HSS 402, the QNPDB 404, and the MME 406 within the network 102.

[0085] The GMLC 240 receives the location request from the UE 106. The UE may be a Lawfully Intercepted Management (LIM) client 408 who is authorized for obtaining the serving cell information. The location request may include identifiers, such as the IMSI, the MSISDN.

[0086] In one or more embodiments, if the location request includes the IMSI, the GMLC 240 sends the first UDR to the HSS 402 to retrieve the MSISDN associated with the IMSI. The HSS responds with the corresponding MSISDN. Once the MSISDN is obtained, the GMLC 240 proceeds to send the second UDR to the HSS 402 to retrieve the serving cell information. The serving cell information includes details such as the cell ID, the TAC or network-specific information about a subscriber's current serving cell. In one or more embodiments, the HSS 402 is queried when the location request applies to the subscriber operating in the LTE. The HSS 402 contains subscription data including mappings between the subscriber’s IMSI, the MSISDN, and currently assigned MME 406.

[0087] Once the MSISDN is retrieved, the GMLC 240 sends a get MME ID request to the HSS 402 to determine the MME that currently serves the subscriber. The MME ID is required for routing the PLR. In a non-limiting example, if the subscriber is currently registered with the MME, and the location request includes only the IMSI. The GMLC 240 queries the HSS 402 to resolve the MSISDN say, “9876543210” and then queries again the HSS 402 to obtain the serving MME ID.

[0088] In one or more embodiments, the UDM 210 replaces the HSS 402 in the 5G networks. The GMLC 240 sends a get AMF ID request to the UDM 210 to retrieve the AMF associated with the subscriber. The AMF is a 5G equivalent of the MME 406 and handles registration and mobility management functions. The response from the UDM 210 may include an AMF ID, the TAC and other serving node identifiers. The AMF ID and the TAC are used to determine the serving cell of the subscriber in the 5G network. In a non-limiting example, the subscriber with the MSISDN “1234567890” is served by the AMF with the AMF ID and the GMLC 240 retrieves this information from the UDM 210 to enable location lookup logic or serving cell caching.

[0089] In another non-limiting example, in the 4G networks, the GMLC 240 may query the HSS 402 using a MSISDN “9876543210” and obtains the corresponding MME ID, which in turn points to a serving cell ID “Cell-ABC123” and TAC “TAC- 456”. In the 5G networks, the retrieving module 340 may query the UDM 210 to obtain the AMF ID “AMF-NP5G-001” and retrieves associated information.

[0090] Further, in one or more embodiments, especially in cases of number-ported subscribers (i.e., where the MSISDN has been ported from one network to another), the GMLC 240 consults the QNPDB 404 to enable accurate query routing. The QNPDB provides the destination realm, which is a network-specific domain used to correctly route the location requests to the appropriate HSS 402 or UDM 210. In a non-limiting example, if the MSISDN “9876543210” is ported out from an operator A to an operator B, the QNPDB 404 identifies the appropriate destination realm associated with the operator B. The GMLC 240 then routes the UDRs accordingly.

[0091] FIG. 5 illustrates a flowchart depicting a method for handling the location request associated with the serving cell in the communication network, in accordance with an embodiment of the present disclosure. The method 500 comprises a series of operation steps indicated by steps 502 through 510. The method 500 starts at step 502.

[0092] At step 502, the receiving module 320 may receive the location request from the UE. The location request may correspond to a standardized location request, such as a Standard Location Immediate Request (SLIR). Such requests may be used to retrieve the geographical location of the UE. The location request may include one of the identifiers associated with the UE, such as the IMSI, or the MSISDN. In one or more embodiments, the location request may be received over secure signaling protocols and is parsed by the receiving module 320 to extract the subscriber information. In a non-limiting example, an LIM client may transmit the location request containing a MSISDN “1234567890” to the receiving module 320 to determine the currently active cell in which the subscriber is registered.

[0093] At step 504, the identifying module 330 may identify whether the received location request is intended solely to retrieve the serving cell information associated with the subscriber. In one or more embodiments, the identification may be made by analyzing fields in the location request, for instance, a request type = current location and positioning and method = seving cell lD. The serving cell information typically includes data such as the cell ID, the TAC and other relevant details identifying the cell currently serving the subscriber. The identification is necessary to decide whether the PLR should be bypassed (when only the serving cell information is needed) or to be involved (for precise geolocation).

[0094] At step 506, the retrieving module 340 may retrieve the serving cell information corresponding to the subscriber, based on the identification. To retrieve the serving cell information, the transmitting module 360 is configured to send the first UDR to the subscriber database. In an implementation, the subscriber database may correspond to one of the HSS 402 or the UDM 210 to fetch additionalsubscriber details. The first UDR includes one of the IMSI or MSISDN, depending on the information provided in the received location request. If the IMSI is included in the location request, it is used as a primary identifier in the UDR. The retrieving module 340 is further configured to retrieve the response from the subscriber database containing the MSISDN associated with the subscriber and then transmitting module 360 is configured to send the second UDR to the subscriber database. The second UDR is used to retrieve the serving cell information associated with the subscriber. The MSISDN serves as the required identifier for further data retrieval operations.

[0095] At step 508, the determining module 350 may determine the location information of the serving cell using a cache memory based on the serving cell information. The cache memory stores predefined mappings between the serving cell identifiers and precise geographic coordinates, particularly latitude and longitude values. In a non-limiting example, the serving cell information retrieved from the HSS or the UDM 210 includes cell ID “C7990” and TAC “TAC25”. The determining module 350 then queries the cache memory, which maps the cell ID and the TAC to coordinates latitude: 37.779° N, longitude: 122.414°W.

[0096] At step 510, the transmitting module 360 may transmit the serving cell information and the determined location of the serving cell to the UE or to a requesting network node. Thus, if latitude and longitude information was retrieved from the cache memory, the information is included in the response along with the serving cell information. If the latitude and the longitude information is unavailable, the response includes only the serving cell information. This completes the process flow for efficiently responding to the location requests for serving cell data without invoking the PLR to the MME or AMF. In a non-limiting example, the transmitting module 360 may send the information such as:("MSISDN": "1234567890", "Serving Cell": "Cell-ABC123", "TAC": "456", "Location": "Scotland, London") to the LIM 408.

[0097] In an embodiment, the retrieving of the MSISDN and the determining of the serving cell information is performed using a Subscriber Handling (SH) microservice, and the transmitting of the serving cell information including the location information of the serving cell is performed using a Location Enabler (LE) microservice. When the location request is received that does not contain the MSISDN, the transmitting module 360 using the SH microservice sends the first UDR to the subscriber database using the IMSI to retrieve the corresponding MSISDN. Upon successful retrieval, the transmitting module 360 using the SH microservice then sends the second UDR to obtain the serving cell information associated with the subscriber. The SH microservice may handle parsing, validation, and data handling of these responses to extract the relevant details needed to obtain the serving cell information. The LE microservice is configured to convert the serving cell information into geographical location coordinates and transmit this data. Specifically, the transmitting module 360 using the LE microservice uses the cache memory to resolve the received Cell ID and the TAC into the latitude and the longitude coordinates. After determining the location information, the LE microservice formats the output and securely transmits the final serving cell location data to the requesting UE.

[0098] FIG. 6 illustrates a schematic block diagram depicting an architecture of a computing system 600 for providing the serving cell information in the communication network, in accordance with an embodiment of the present disclosure.

[0099] The computing system 600 includes a network 610, a network interface 620, a processor 630, an Input / Output (I / O) interface 640 and a non-transitory computer readable storage medium 650 (hereinafter may also be referred to as the “storage medium 650” or the “storage media 650”).

[0100] The network interface 620 includes wireless network interfaces such as Bluetooth, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access(WCDMA) or wired network interfaces such as Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers-864 (IEEE-864).

[0101] The processor 630 may include various processing circuitry and communicate with the storage medium 650 and the VO interface 540. The processor 630 is configured to execute instructions stored in the storage medium 650 and to perform various processes. The processor 630 may include an intelligent hardware device including a general-purpose processor, such as, for example, and without limitation, the CPU, the AP, the dedicated processor, or the like, the graphics-only processing unit such as the GPU, a microcontroller, a Field-Programmable Gate Array (FPGA), a programmable logic device, a discrete hardware component, or any combination thereof. The processor 630 may be configured to execute computer-readable instructions 652 stored in the storage medium 650 to cause the server to perform various functions.

[0102] The storage medium 650 stores a set of instructions 652 required by the processor 630 for controlling its overall operations.

[0103] The storage media 650 may include an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, or the like. For example, the storage media 650 may include, but are not limited to, hard drives, floppy diskettes, optical disks, ROMs, RAMs, EPROMs, EEPROMs, flash memory, magnetic or optical cards, solid-state memory devices, or other types of physical media suitable for storing electronic instructions. In one or more implementations, the storage media 650 includes a Compact Disk-Read Only Memory (CD-ROM), a Compact Disk-Read / Write (CD-R / W), and / or a Digital Video Disc (DVD).

[0104] In one or more implementations, the storage medium 650 stores computer program code configured to cause the computing system 600 to perform at least a portion of the processes and / or methods. Accordingly, in at least one embodiment, the computing system 600 performs the method for handling the location request associated with the serving cell in the communication network.

[0105] Now, referring to the technical abilities and advantageous effect of the present disclosure, disclosed herein is the system and the method that provide the serving cell information in response to the PLR for both 4G and 5G subscribers using the IMSI or the MSISDN. In certain scenarios, the LIM clients may require only the serving cell location and its associated information, such as the cell location, the cell id, and the TAC. The method provides the requested serving cell information in the response to the PLR. As a result, performance of the communication network and resource utilization of the network resources are enhanced, service quality for end-users is improved, and overhead on the GMLC is reduced.

[0106] Further, the proposed system and the method enhance speed of response times for the location requests, particularly in scenarios where only the serving cell information is needed. This will help ensure more timely delivery of the location data, which is critical in use cases like lawful interception, emergency services, and network diagnostics.

[0107] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[0108] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.1

[0109] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.LIST OF REFERENCE NUMERALS

[0110] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:100 - Communication environment102- Core network104 / 104-1 to 104-N - Node / Nodes / Plurality Nodes106 / 106-1 to 106-N - One or more User Equipment (UE) / UEs 202 - Access and Mobility Management Function (AMF) 204 - Policy Control Function (PCF) 206 - Equipment Identity Register (EIR) 208 - Authentication Server Function (AUSF) 210 - Unified Data Management (UDM)212 - Short Message Service Function (SMSF)214 - Network Slice Selection Function (NSSF)216 - Session Management Function (SMF)218 - Network Data Analytics Function (NWDAF)220 - Charging Function-Protocol Converter (CHF -PC)222 - Signaling Transfer Point224 - Diameter Routing Agent226 - Network Exposure Function (NEF)228 - Binding Support Function (BSF)230 - User Plane Function (UPF)232- Data Network (DN)234- Location Management Function (LMF)236- Radio Access Network (RAN)238- Location Services (LCS)240- Gateway Mobile Location Center (GMLC)300-2- First communication bus300-4- Second communication bus302 - Processor304 - Memory306 - Communication interface308 - Input / Output interface310- Processing module320 - Receiving module330 - Identifying module340 - Retrieving module350- Determining module360 - Transmitting module400 - Communication system / system402 - Home Subscriber Server (HSS)404- Query Number Portability Database (QNPDB)406- Mobility Management Entity (MME)408- Lawfully Intercepted Management (LIM)500 - Method for handling the location request associated with the serving cell502-510 - Operation steps of the method 500600 - A computing system610 - Network620 - Network interface630 - Processor of the computing system640 - Input / Output (I / O) interface of the computing system650 - Non-transitory computer readable storage medium652 - Set of instructions

Claims

We Claim:

1. A method (500) for handling location request associated with a serving cell in a communication network, the method (500) comprising: receiving (502), by a receiving module (320) at a Gateway Mobile Location Centre (GMLC), the location request from a User Equipment (UE) (106); identifying (504), by an identifying module (330) based on the location request, if the location request is solely to retrieve serving cell information associated with a subscriber; retrieving (506), by a retrieving module (340) from a subscriber database, the serving cell information based on a result of the identification that the location request is solely to retrieve the serving cell information; determining (508), by a determining module (350), location information of the serving cell using a cache memory based on the serving cell information; and transmitting (510), by a transmitting module (360), the serving cell information including the location information of the serving cell to the UE (106).

2. The method (500) as claimed in claim 1, wherein the location request includes one of an International Mobile Subscriber Identity (IMSI) or a Mobile Station International Subscriber Directory Number (MSISDN) associated with the subscriber.

3. The method (500) as claimed in claim 1, wherein for retrieving the serving cell information associated with the subscriber, the method comprises: sending, by the transmitting module (360), a first User Data Request (UDR) to the subscriber database when the location request excludes MSISDN; retrieving, by the retrieving module (340) from the subscriber database, the MSISDN associated with the subscriber in response to the first UDR; sending, by the transmitting module (360), a second UDR to the subscriber database in response to the retrieved MSISDN; anddetermining, by the determining module (350) from the subscriber database, the serving cell information associated with the subscriber in response to the second UDR.

4. The method (500) as claimed in claim 1, wherein the subscriber database is at least one of a Home Subscriber Server (HSS) (402) and a Unified Data Management (UDM) (210).

5. The method (500) as claimed in claim 3, wherein the retrieving of the MSISDN and the determining of the serving cell information is performed using a Subscriber Handling (SH) microservice, and the transmitting of the serving cell information including the location information of the serving cell is performed using a Location Enabler (LE) microservice.

6. The method (500) as claimed in claim 1, further comprising: determining, by the determining module (350) from a portability database, a network entity associated with MSISDN when the MSISDN is present in the location request; sending, by the transmitting module (360), a User Data Request (UDR) to the subscriber database associated with the network entity; and determining, by the determining module (350) from the subscriber database, the serving cell information associated with the subscriber in response to the UDR.

7. The method (500) as claimed in claim 1, wherein the serving cell information includes a cell identifier including a Tracking Area Code (TAC).

8. A system (400) for handling location request associated with a serving cell in a communication network, the system (400) comprising a Gateway Mobile Location Centre (GMLC) (240), wherein the GMLC (240) comprises: a receiving module (320) configured to receive the location request from a User Equipment (UE) (106);an identifying module (330) configured to identify, based on the location request, if the location request is solely to retrieve serving cell information associated with a subscriber; a retrieving module (340) configured to retrieve, from a subscriber database, the serving cell information based on a result of the identification that the location request is solely to retrieve the serving cell information; a determining module (350) configured to determine location information of the serving cell using a cache memory based on the serving cell information; and a transmitting module (360) configured to transmit the serving cell information including the location information of the serving cell to the UE (106).

9. The system (400) as claimed in claim 8, wherein the location request includes one of an International Mobile Subscriber Identity (IMSI) or a Mobile Station International Subscriber Directory Number (MSISDN) associated with the subscriber.

10. The system (400) as claimed in claim 8, wherein to retrieve the serving cell information associated with the subscriber: the transmitting module (360) is configured to send a first User Data Request (UDR) to the subscriber database when the location request excludes MSISDN; the retrieving module (340) is configured to retrieve, from the subscriber database, the MSISDN associated with the subscriber in response to the first UDR; the transmitting module (360) is configured to send a second UDR to the subscriber database in response to the retrieved MSISDN; and the determining module (350) is configured to determine, from the subscriber database, the serving cell information associated with the subscriber in response to the second UDR.

11. The system (400) as claimed in claim 8, wherein the subscriber database is at least one of a Home Subscriber Server (HSS) (402) and a Unified Data Management (UDM) (210).

12. The system (400) as claimed in claim 10, wherein the retrieving of the MSISDN and the determining of the serving cell information is performed using a Subscriber Handling (SH) microservice, and the transmitting of the serving cell information including the location information of the serving cell is performed using a Location Enabler (LE) microservice.

13. The system (400) as claimed in claim 8, wherein: the determining module (350) is further configured to determine, from a portability database, a network entity associated with MSISDN when the MSISDN is present in the location request; the transmitting module (360) is further configured to send a User Data Request (UDR) to the subscriber database associated with the network entity; and the determining module (350) is configured to determine the serving cell information associated with the subscriber in response to the UDR.

14. The system (400) as claimed in claim 8, wherein the serving cell information includes a cell identifier including a Tracking Area Code (TAC).

15. A computer program product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations comprising: receiving a location request from a User Equipment (106); identifying, based on the location request, if the location request is solely to retrieve serving cell information associated with a subscriber; retrieving, from a subscriber database, the serving cell information based on a result of the identification that the location request is solely to retrieve the serving cell information; determining location information of a serving cell using a cache memory based on the serving cell information; and transmitting the serving cell information including the location information of the serving cell to the UE (106).

Images