Method and system for providing location of a user equipment

Abstract

The present disclosure relates to a method and a system for providing location of a user equipment The present disclosure encompasses: receiving, by a transceiver unit at a GMLC system from a client device, a request related to providing a location information of one or more UE in a desired format; transmitting, by the transceiver unit at the GMLC system to an AMF unit, a request related to receiving a geographical area description (GAD) information of the one or more UEs; receiving, by the transceiver unit at the GMLC system from the AMF unit, the GAD information of the one or more UEs; converting, by a converter unit at the GMLC system, the GAD information into the desired format; and transmitting, by the transceiver unit at the GMLC system to the client device, the location information of the one or more UE in the desired format.

Description

METHOD AND SYSTEM FOR PROVIDING LOCATION OF A USER EQUIPMENTFIELD OF DISCLOSURE

[0001] The present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for providing location of a user equipment.BACKGROUND

[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] Moreover, the 5G core networks are based on Service Based Architecture (SBA) that is centred around Network Function (NF) services. In said SBA a set of interconnected NFs delivers the control plane functionality and common data repositories of the 5G network, where each NF is authorized to access services of other NFs. Particularly, each NF can register itself and its supported services to a Network Repository Function (NRF), which is used by other NFS for the discovery of NF instances and their services. Also, Gateway Mobile Location Centre (GMLC) isa network entity in the 5G Core Network (SGC) supporting Location Services (LCS). Within the 5GC, the GMLC offers services to access and mobility management function (AMF), the GMLC and LCS client via Network Exposure Function (NEF) via the Ngmlc service-based interface. A Provide Location service operation is invoked by a NF Service Consumer, e.g., the AMF or the GMLC, towards the GMLC to request to provide the location information for a target UE or to subscribe to periodic or triggered deferred location for a target UE.

[0005] In the existing system, the location request or provide location request does not comprised of any specific / fixed coordinate format mentioned in that request. Therefore, while the network may determine the location of the UE using AMF, but the network is unable to determine and convert the location coordinates into a format desired by the client.

[0006] Thus, there exists an imperative need in the art to provide a client location coordinate of a plurality of UE in the format requested by the client, which the present disclosure aims to address.SUMMARY

[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0008] An aspect of the present disclosure may relate to a method for providing location of a user equipment. The method includes receiving, by a transceiver unit at a gateway mobile location center (GMLC) system from a client device, a request related to providing a location information of one or more user equipment (UE) in a desired format. The method further includes transmitting, by the transceiver unit at the GMLC system to an access and mobility management function (AMF) unit, a request related to receiving a geographical area description (GAD) information of the one or more UEs. The method further includes receiving, by the transceiver unit at the GMLC system from the AMF unit, the GAD information of the one or more UEs. The method further includes converting, by a converter unit at the GMLC system, the GAD information into the desired format. Finally, the method includes transmitting, by the transceiver unit at the GMLC system to the client device, the location information of the one or more UE in the desired format.

[0009] In an exemplary aspect of the present disclosure, the desired format is one of: a format defined in the request related to providing the location information, and a pre-defined format associated with the client.

[0010] In an exemplary aspect of the present disclosure, the method further comprises storing, in a storage unit, the predefined format associated with the client as a mapping data, wherein the mapping data comprises each client of the one or more clients mapped with a desired format among one or more pre-defined formats.

[0011] In an exemplary aspect of the present disclosure, the desired format is one of a Universal Transverse Mercator (UTM) format, and a Degrees Minutes Seconds (DMS) format.

[0012] In an exemplary aspect of the present disclosure, the client device belongs to a client among one or more clients.

[0013] Another aspect of the present disclosure may relate to a system for providing location of a user equipment. The system comprises a transceiver unit configured to receive, from a client device, a request related to providing a location information of one or more user equipment (UE) in a desired format. The transceiver unit is further configured to transmit, to an access and mobility management function (AMF) unit, a request related to receiving a geographical area description (GAD) information of the one or more UEs. The transceiver unit is further configured to receive, from the AMF unit, the GAD information of the one or more UEs. The system further comprises a converter unit connected to at least the transceiver unit. The converter unit is configured to convert the GAD information into the desired format. The transceiver unit is further configured to transmit, to the client device, the location information of the one or more UE in the desired format.

[0014] Yet another aspect of the present disclosure may relate to a non - transitory computer readable storage medium storing instructions for providing location of a user equipment, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit to receive, from a client device, a request related to providing a location information of one or more user equipment (UE) in a desired format. The executable code when executed further causes the transceiver unit to transmit, to an access and mobility management function (AMF) unit, a request related to receiving a geographical area description (GAD) information of the one or more UEs. The executable code when executed further causes the transceiver unit to receive, from the AMF unit, the GAD information of the one or more UEs. Theexecutable code when executed further causes a converter unit to convert the GAD information into the desired format. The executable code when executed further causes the transceiver unit to transmit, to the client device, the location information of the one or more UE in the desired format.OBJECTS OF THE DISCLOSURE

[0015] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0016] It is an object of the present disclosure to provide a system and a method for providing location of a user equipment.

[0017] It is an object of the present disclosure to provide a system and a method providing a client location coordinate of a plurality of UE in the format requested by the client.

[0018] It is another object of the present disclosure to provide a solution that uses GMLC to provide different co-ordinate format based on different client.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0020] FIG. 1 illustrates an exemplary block diagram representation of 5thgeneration core (5GC) network architecture.

[0021] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.

[0022] FIG. 3 illustrates an exemplary block diagram of a system for providing location of a user equipment, in accordance with exemplary implementations of the present disclosure.

[0023] FIG. 4 illustrates a method flow diagram for providing location of a user equipment in accordance with exemplary implementations of the present disclosure.

[0024] FIG. 5 illustrates a process flow diagram for providing location of a user equipment, in accordance with exemplary implementations of the present disclosure.

[0025] The foregoing shall be more apparent from the following more detailed description of the disclosure.DETAILED DESCRIPTION

[0026] 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 may 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.

[0027] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0028] 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 skills in the art that the embodiments may be practiced without these specific details. For example, circuits, systems,processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0029] Also, it is noted that individual embodiments may be described as a process which 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 may 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.

[0030] 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 — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0031] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.

[0032] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and / or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment / device may include, but is not limited to, amobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.

[0033] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.

[0034] As used herein “interface” or “user interface” refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to as a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.

[0035] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.

[0036] As used herein the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units / components within the system and / or connected with the system.

[0037] As used herein, Location-based services (LBS) refer to services that are based on the location of a mobile user as determined by the device's geographical location.

[0038] As used herein, lawful interception management (LIM) to services that assists telecommunication service providers in complying with electronic surveillance law enforcement orders.

[0039] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and system for providing location of a user equipment.

[0040] FIG. 1 illustrates an exemplary block diagram representation of 5thgeneration core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in fig. 1, the 5GC network architecture

[0100] includes a user equipment (UE)

[0102] , a radio access network (RAN)

[0104] , an access and mobility management function (AMF) unit

[0106] , a Location Management Function (LMF) [106a], a Session Management Function (SMF)

[0108] , a Service Communication Proxy (SCP)

[0110] , an Authentication Server Function (AUSF)

[0112] , a Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] , a Network Slice Selection Function (NSSF)

[0116] , a Network Exposure Function (NEF)

[0118] , a Network Repository Function (NRF)

[0120] , a Policy Control Function (PCF)

[0122] , a Unified Data Management (UDM)

[0124] , an application function (AF)

[0126] , a User Plane Function (UPF)

[0128] , a data network (DN)

[0130] , a Gateway Mobile Location Centre (GMLC) system

[0132] , and Location service client

[0134] wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0041] Radio Access Network (RAN)

[0104] is the part of a mobile telecommunications system that connects user equipment (UE)

[0102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.

[0042] Access and Mobility Management Function (AMF) unit

[0106] (also referred to herein as AMF unit

[0106] ) is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.

[0043] Location Management Function (LMF) [ 106a] is a component within the 5G Core Network architecture which is responsible to manage the location of mobile devices such as but not limited to smartphones, tablets, loT devices, within the mobile network. In an exemplary aspect, NL1 interface connects the LMF [106a] to the UE

[0102] ,

[0044] Furthermore, the Location Management Function (LMF) [106a] supports functionalities such as but not limited only to obtaining downlink location measurements or a location estimate from the UE, obtaining uplink location measurements from the NG RAN, obtaining non-UE associated assistance data from the NG RAN, providing broadcast assistance data to UEs and forwarding associated ciphering keys to an AMF unit

[0106] ,

[0045] Session Management Function (SMF)

[0108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.

[0046] Service Communication Proxy (SCP)

[0110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.

[0047] Authentication Server Function (AUSF)

[0112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.

[0048] Network Slice Specific Authentication and Authorization Function (NSSAAF)

[0114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.

[0049] Network Slice Selection Function (NSSF)

[0116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.

[0050] Network Exposure Function (NEF)

[0118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0051] Network Repository Function (NRF)

[0120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.

[0052] Policy Control Function (PCF)

[0122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.

[0053] Unified Data Management (UDM)

[0124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0054] Application Function (AF)

[0126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.

[0055] User Plane Function (UPF)

[0128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0056] Data Network (DN)

[0130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.

[0057] Gateway Mobile Location Centre (GMLC) system

[0132] (also referred to herein as GMLC system

[0132] ) is the network entity in the 5G Core Network (5GC) supporting Location Services (LCS). Within the 5GC, the GMLC offers services to the AMF, GMLC and NEF. As used herein, Location services (LCS) are location-based services, with the goal of obtaining information of where the mobile is (location information). With the standardization of the format of the location information ( latitude and longitude) the operators can offer different types of services. And these services can be used in several ways, such as for pricing, legal requirements such as intercept, location services, emergency call services, among others.

[0058] Location services (LCS) client

[0134] is a software and / or hardware entity that interacts with a LCS Server for the purpose of obtaining location information for one or more Mobile Stations. LCS Clients subscribe to LCS in order to obtain location information. LCS Clients may or maynot interact with human users. The LCS Client is responsible for formatting and presenting data and managing the user interface.

[0059] FIG. 2 illustrates an exemplary block diagram of a computing device

[0200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device

[0200] may also implement a method for providing location of a user equipment utilising the system

[0300] , In another implementation, the computing device

[0200] itself implements the method for providing location of a user equipment using one or more units configured within the computing device

[0200] , wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0060] The computing device

[0200] may include a bus

[0202] or other communication mechanism for communicating information, and a hardware processor

[0204] coupled with bus

[0202] for processing information. The hardware processor

[0204] may be, for example, a general-purpose microprocessor. The computing device

[0200] may also include a main memory

[0206] , such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus

[0202] for storing information and instructions to be executed by the processor

[0204] , The main memory

[0206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor

[0204] , Such instructions, when stored in non-transitory storage media accessible to the processor

[0204] , render the computing device

[0200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device

[0200] further includes a read only memory (ROM)

[0208] or other static storage device coupled to the bus

[0202] for storing static information and instructions for the processor

[0204] ,

[0061] A storage device

[0210] , such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus

[0202] for storing information and instructions. The computing device

[0200] may be coupled via the bus

[0202] to a display

[0212] , such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device

[0214] , including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus

[0202] for communicating information and command selections to the processor

[0204] , Another type of user input device may be a cursor controller

[0216] , such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor

[0204] , and forcontrolling cursor movement on the display

[0212] , The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0062] The computing device

[0200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware, and / or program logic which in combination with the computing device

[0200] causes or programs the computing device

[0200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device

[0200] in response to the processor

[0204] executing one or more sequences of one or more instructions contained in the main memory

[0206] , Such instructions may be read into the main memory

[0206] from another storage medium, such as the storage device

[0210] , Execution of the sequences of instructions contained in the main memory

[0206] causes the processor

[0204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.

[0063] The computing device

[0200] also may include a communication interface

[0218] coupled to the bus

[0202] , The communication interface

[0218] provides a two-way data communication coupling to a network link

[0220] that is connected to a local network

[0222] , For example, the communication interface

[0218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface

[0218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface

[0218] sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.

[0064] The computing device

[0200] can send messages and receive data, including program code, through the network(s), the network link

[0220] and the communication interface

[0218] , In the Internet example, a server

[0230] might transmit a requested code for an application program through the Internet

[0228] , the ISP

[0226] , the local network

[0222] , a host

[0224] and the communication interface

[0218] , The received code may be executed by the processor

[0204] as it is received, and / or stored in the storage device

[0210] , or other non-volatile storage for later execution.

[0065] The computing device

[0200] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device

[0200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device

[0200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.

[0066] Referring to FIG. 3, an exemplary block diagram of a system

[0300] for providing location of a user equipment, is shown, in accordance with the exemplary implementations of the present disclosure. The system

[0300] comprises at least one GMLC system

[0132] , at least one transceiver unit

[0302] , at least one converter unit

[0304] , and at least one storage unit

[0306] , Also, all of the components / units of the system

[0300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system

[0300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system

[0300] may comprise multiple such units or the system

[0300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system

[0300] may be present in a user device / user equipment

[0102] to implement the features of the present disclosure. The system

[0300] may be a part of the user device

[0102] / or may be independent of but in communication with the user device

[0102] (alternatively referred to herein as a UE

[0102] ). In another implementation, the system

[0300] may reside in a server or a network entity. In yet another implementation, the system

[0300] may reside partly in the server / network entity and partly in the user device.

[0067] The system

[0300] is configured for providing location of a user equipment, with the help of the interconnection between the components / units of the system

[0300] ,

[0068] The system

[0300] comprises a gateway mobile location centre (GMLC) system

[0132] , The GMLC system

[0132] further comprises a transceiver unit

[0302] configured to receive, from a client device, a request related to providing a location information of one or more user equipment (UE)

[0102] in a desired format.

[0069] The transceiver unit

[0302] receives, at the GMLC system

[0132] , the request related to providing the location information of one or more UE

[0102] in the desired format from the clientdevice. In an exemplary aspect, the request to provide the location information of one or more UE

[0102] may include location-based services (LBS) request, lawful interception management (LIM) request etc. In an exemplary aspect, the request to provide the location information of one or more UE

[0102] may also include the UE

[0102] identifier such as but not limited to an International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), Subscription Permanent Identifier (SUPI), Generic Public Subscription Identifier (GPSI), etc. The client device sends a request to the GMLC system

[0132] , specifying the need for location information of one or more UEs

[0102] , where the requested location data is expected to be delivered in a particular format defined either by the request itself or pre-configured settings associated with the client.

[0070] In an exemplary aspect, the request may include such as but not limited only to Ngmlc Location request, ProvideLocation request, LocationUpdateSubscribe request etc.

[0071] For example, if a location-based service provider (LBSP) requires the location of a UE

[0102] in the Universal Transverse Mercator (UTM) format for accurate positioning on a regional map, the transceiver unit

[0302] receives this specific request. In another example, a different client, such as a LIM, might request the location of the same UE

[0102] , but in Degrees Minutes Seconds (DMS) format, which is more suitable for global coordinates. The transceiver unit

[0302] ensures that the GMLC system

[0132] can accommodate these varied requests by receiving the required format specifications and further processing them to deliver the information accordingly.

[0072] In an exemplary aspect, the client device may include such as but not limited to mobile device, laptop, etc.

[0073] In an exemplary aspect, the client device belongs to a client among one or more clients. In an exemplary aspect the client device is an LCS client which is external to the network and may be operated by a network administrator or by an external network such as emergency service, lawful interception, etc.

[0074] In an exemplary aspect, the desired format is one of the formats defined in the request related to providing the location information, and a pre-defined format associated with the client.

[0075] In an exemplary aspect, the desired format is the format defined in the request in which the network administrator wants to receive the data related to providing the location information.

[0076] In an exemplary aspect, the pre-defined format is the default format already present in the client device. If the network administrator does not specify in the request, the specific format in which the client wants to receive the location information then the client device may automatically request to receive location information in the predefined / default format.

[0077] In an exemplary aspect, the desired format is one of a Universal Transverse Mercator (UTM) format, and a Degrees Minutes Seconds (DMS) format.

[0078] In an exemplary aspect, the UTM format, a plane coordinate grid format that consists of 60 zones, each 6-degrees of longitude in width. The zones are numbered 1-60, beginning at 180- degrees longitude, and increasing to the east.

[0079] In an exemplary aspect, Degrees minutes seconds (DMS) format is a type of format used for measuring angles, as an alternative to decimal way of stating the size of an angle. It is a known fact that there are 360 degrees in a whole circle, with l / 60th of those being 1 minute, and l / 60th of one minute being 1 second. DMS includes degrees (°), minutes ('), seconds ("), with the corresponding symbols, and a size of any angle can be stated like, for example, 30 degrees, 10 minutes, 50 seconds.

[0080] The system

[0300] further comprises a storage unit

[0306] , The storage unit

[0306] is configured to store the pre-defined format associated with the client as a mapping data, wherein the mapping data comprises each client of the one or more clients mapped with a desired format among one or more predefined formats.

[0081] The storage unit

[0306] stores the pre-defined format associated with the client in the form of mapping data.

[0082] The transceiver unit

[0302] is further configured to transmit to an access and mobility management function (AMF) unit

[0106] , a request related to receiving a geographical area description (GAD) information of the one or more UEs

[0102] , Upon receiving a location request from a client device, the transceiver unit

[0302] initiates communication with the AMF unit

[0106] to retrieve the geographical positioning data associated with the specified UE(s)

[0102] , The GAD information typically includes essential location details such as latitude, longitude, and possibly altitude, which are necessary for determining the exact geographical position of the UE(s)

[0102] , In an exemplary aspect, GAD information includes at least one GAD shape supported by the LCSclient. Geographical Area Description (GAD) information refers to the standardized representation of geographic locations or areas, typically used in telecommunications to describe the position of user equipment (UE) or other points of interest. It consists of coordinates, such as latitude and longitude, along with additional geometrical attributes that define the extent and shape of the area.

[0083] In an exemplary aspect, various shapes can be used to represent geographic areas through GAD information. One common example of the GAD shapes is the Point with Uncertainty Ellipse, which describes a specific point (latitude and longitude) along with an elliptical uncertainty region. This ellipse represents the range within which the actual location may fall, with the major and minor axes indicating the levels of uncertainty. Another standard GAD shape is the Polygon, which consists of multiple latitude and longitude pairs that form a closed, multi-sided figure. Polygons are ideal for defining large or irregular areas, such as city boundaries or specific zones of interest. Similarly, the Circle shape is used to represent a round area centred on a defined point, with a specified radius. Circles are frequently used in applications like geofencing, where proximity to a particular landmark is important. Other standardized shapes include the Ellipse, which differs from the circle by having distinct major and minor axes, providing more accurate representation of areas with non-uniform location uncertainty. Finally, the Arc Band shape, defined by a centre point, radius, and two angles, forms a sector-shaped area. This shape is useful in applications where coverage or influence is directional, such as broadcast zones or radar ranges. These GAD shapes, coupled with different coordinate systems such as Universal Transverse Mercator (UTM) or Degrees Minutes Seconds (DMS), offer flexibility and precision in describing geographic areas for various network services.

[0084] In an exemplary aspect, the request and response between the GMLC and the AMF related to receiving the GAD information of the one or more UEs

[0102] is alternatively called as ProvidePositioninglnfo, RequestPasInfo etc.

[0085] In an exemplary aspect, the request related to receiving the GAD information of the one or more UEs

[0102] include various attributes which may include such as but not limited to IcsClientType, IcsLocation, priority, IcsQoS, additionalSuppGADShape etc.

[0086] For example, when a location-based service provider (LBSP) requests the real-time location of a delivery vehicle (the UE

[0102] ), the transceiver unit

[0302] transmits a request to the AMF unit

[0106] to obtain the relevant GAD information. The AMF unit

[0106] , which is responsible for mobility management and session handling within the mobile network, retrieves the mostrecent location data of the UE

[0102] and transmits it back to the GMLC system

[0132] , In another example, if a public safety organization requires the location of a lost individual’s mobile device (the UE

[0102] ), the transceiver unit

[0302] would send a request to the AMF unit

[0106] for GAD information. The AMF unit

[0106] may then pull the last known location of the device and return this data to the GMLC system

[0132] for further processing.

[0087] The transceiver unit

[0302] transmits, from the GMLC system

[0132] , the request related to receiving the geographical area description (GAD) information of the one or more UEs

[0102] to the AMF unit

[0106] , In an exemplary aspect, the transceiver unit sends a request to the AMF unit

[0106] in order to retrieve GAD information that may include such as but not limited only to information such as shape of the geographical location of the one or more UEs

[0102] , latitudinal and longitudinal coordinates the one or more UEs

[0102] etc.

[0088] The transceiver unit

[0302] is further configured to receive, from the AMF unit

[0106] , the GAD information of the one or more UEs

[0102] , Once the transceiver unit

[0302] transmits a request to the AMF unit

[0106] for the GAD information, the AMF unit

[0106] retrieves the required geographical data, which includes the current location coordinates of the UE(s)

[0102] , such as latitude and longitude. This information is then sent back to the GMLC system

[0132] via the transceiver unit

[0302] , allowing the system to process the location data further. In an exemplary aspect, the received GAD information in the form of response is alternatively called as ProvidePosInfoExt. In an exemplary aspect, the received GAD information includes various attributes which may include such as but not limited to IcsClientType, IcsLocation, priority, IcsQoS, additionalSuppGADShape etc.

[0089] For example, in a scenario where a client device, such as a location-based service provider (LBSP), requests the location of a fleet vehicle ( such as UE

[0102] ), the AMF unit

[0106] collects the real-time GAD information from the network and transmits it to the GMLC system

[0132] , The transceiver unit

[0302] is responsible for receiving this data and ensuring it is delivered to the appropriate components within the GMLC system

[0132] for further processing, such as format conversion or storage.

[0090] Based on the request sent by the transceiver unit

[0302] to the AMF unit

[0106] for receiving GAD information of one or more UEs

[0102] , the transceiver unit

[0302] receives, at the GMLC system

[0132] , the GAD information of one or more UEs

[0102] from the AMF unit

[0106] ,

[0091] The GMLC system

[0132] further comprises a converter unit

[0304] connected to at least the transceiver unit

[0302] , The converter unit

[0304] is configured to convert the GAD information into the desired format. Upon receiving the GAD information from the AMF unit

[0106] , which typically includes raw geographical coordinates such as latitude and longitude, the converter unit

[0304] processes and transforms this data into a format specified either by the client request or a preconfigured format associated with the client. This conversion capability allows the GMLC system

[0132] to support various location data formats, ensuring that the location information provided is compatible with the specific requirements of different clients.

[0092] For example, if the GAD information received contains coordinates in a DMS format, but the client device requests the data in the Universal Transverse Mercator (UTM) format, the converter unit

[0304] will translate the raw latitude and longitude values into the UTM format. Similarly, in a case where another client, such as a location information management (LIM) service, requests the location in Degrees, Minutes, and Seconds (DMS) format, the converter unit

[0304] converts the GAD information, accordingly, ensuring the data is presented in the required structure.

[0093] Upon receiving at the transceiver unit

[0302] the GAD information related to the one or more UEs

[0102] , the converter unit

[0304] converts, at the GMLC system

[0132] , the GAD information into the desirable format.

[0094] In an exemplary aspect, the converter unit

[0304] fetches the predefined format from the storage unit

[0306] ,

[0095] In an exemplary aspect, the GAD information includes such as but not limited only to information such as the shape of the UE’s geographical location, latitudinal and longitudinal coordinates of the UE, and other uncertain information related to location of the UE. Only latitudinal and longitudinal coordinates are extracted or retrieved from the GAD information can be converted to the desirable format.

[0096] The transceiver unit

[0302] is further configured to transmit to the client device, the location information of the one or more UE

[0102] in the desired format. After the converter unit

[0304] processes and transforms the geographical area description (GAD) information into the format specified by the client, the transceiver unit

[0302] is responsible for relaying this formatted location data back to the client device.

[0097] For example, a location-based service provider (LBSP) may have requested the coordinates of a user equipment (UE)

[0102] in Universal Transverse Mercator (UTM) format. Once the GMLC system

[0132] receives the GAD information from the AMF unit

[0106] and the converter unit

[0304] processes it into UTM format, the transceiver unit

[0302] transmits this UTM data back to the client device. In another scenario, a different client, such as a public safety organization, may have requested the same location data in Degrees Minutes Seconds (DMS) format.

[0098] The transceiver unit

[0302] transmits, from the GMLC system

[0132] , the location information of one or more UE

[0102] in the desired format to the client device. In an exemplary aspect, the transceiver unit

[0302] may transmit the location information of the one or more UE

[0102] in the predefined format to the client device.

[0099] Referring to FIG. 4, an exemplary method flow diagram

[0400] for providing location of a user equipment, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method

[0400] is performed by the system

[0300] , Further, in an implementation, the system

[0300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method

[0400] starts at step

[0402] ,

[0100] At step 404, the method

[0400] comprises receiving, by a transceiver unit

[0302] at a gateway mobile location centre (GMLC) system

[0132] from a client device, a request related to providing a location information of one or more user equipment (UE)

[0102] in a desired format.

[0101] The transceiver unit

[0302] receives, at the GMLC system

[0132] , the request related to providing the location information of one or more UE

[0102] in the desired format from the client device. In an exemplary aspect, the request to provide the location information of one or more UE

[0102] may include location-based services (LBS) request, lawful interception management (LIM) request etc. In an exemplary aspect, the request to provide the location information of one or more UE

[0102] may also include the UE

[0102] identifier such as but not limited to an International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), Subscription Permanent Identifier (SUPI) Generic Public Subscription Identifier (GPSI), etc. The client device sends a request to the GMLC system

[0132] , specifying the need for location information of one or more UEs

[0102] , where the requested location data is expected to be delivered in a particular format defined either by the request itself or pre-configured settings associated with the client.

[0102] In an exemplary aspect, the request may include such as but not limited only to Ngmlc Location request, ProvideLocation request, LocationUpdateSubscribe request etc.

[0103] For example, if a location-based service provider (LBSP) requires the location of a UE

[0102] in the Universal Transverse Mercator (UTM) format for accurate positioning on a regional map, the transceiver unit

[0302] receives this specific request. In another example, a different client, such as a LIM, might request the location of the same UE

[0102] , but in Degrees Minutes Seconds (DMS) format, which is more suitable for global coordinates. The transceiver unit

[0302] ensures that the GMLC system

[0132] can accommodate these varied requests by receiving the required format specifications and further processing them to deliver the information accordingly.

[0104] In an exemplary aspect, the client device may include such as but not limited to mobile device, laptop, routers etc.

[0105] In an exemplary aspect, the client device belongs to a client among one or more clients. In an exemplary aspect the client device is an LCS client which is external to the network and may be operated by a network administrator or by an external network such as emergency service, lawful interception, etc.

[0106] In an exemplary aspect, the desired format is one of a format defined in the request related to providing the location information, and a pre-defined format associated with the client.

[0107] In an exemplary aspect, the desired format is the format defined in the request in which the network administrator wants to receive the data related to providing the location information.

[0108] In an exemplary aspect, the pre-defined format is the default format already present in the client device. If the network administrator does not specify in the request, the specific format in which the client wants to receive the location information then the client device may automatically request to receive location information in the predefined / default format.

[0109] In an exemplary aspect, the desired format is one of a Universal Transverse Mercator (UTM) format, and a Degrees Minutes Seconds (DMS) format.

[0110] In an exemplary aspect, the UTM format, a plane coordinate grid format that consists of 60 zones, each 6-degrees of longitude in width. The zones are numbered 1-60, beginning at 180- degrees longitude, and increasing to the east.[OHl] In an exemplary aspect, Degrees minutes seconds (DMS) format is a type of format used for measuring angles, as an alternative to decimal way of stating the size of an angle. It is a known fact that there are 360 degrees in a whole circle, with l / 60th of those being 1 minute, and l / 60th of one minute being 1 second. DMS includes degrees (°), minutes ('), seconds ("), with the corresponding symbols, and a size of any angle can be stated like, for example, 30 degrees, 10 minutes, 50 seconds.

[0112] The method

[0400] further comprises storing, in a storage unit

[0306] , the predefined format associated with the client as a mapping data, wherein the mapping data comprises each client of the one or more clients mapped with a desired format among one or more pre-defined formats.

[0113] The storage unit

[0306] stores the predefined format associated with the clients in the form of mapping data.

[0114] At step 406, the method

[0400] comprises transmitting, by the transceiver unit

[0302] at the GMLC system

[0132] to an access and mobility management function (AMF) unit

[0106] , a request related to receiving a geographical area description (GAD) information of the one or more UEs

[0102] ,

[0115] Upon receiving a location request from a client device, the transceiver unit

[0302] initiates communication with the AMF unit

[0106] to retrieve the geographical positioning data associated with the specified UE(s)

[0102] , The GAD information typically includes essential location details such as latitude, longitude, and possibly altitude, which are necessary for determining the exact geographical position of the UE(s)

[0102] , In an exemplary aspect, GAD information includes at least one GAD shape supported by the LCS client.

[0116] In an exemplary aspect, the request and response between the GMLC and the AMF related to receiving the GAD information of the one or more UEs

[0102] is alternatively called as ProvidePositioninglnfo, RequestPasInfo etc.

[0117] In an exemplary aspect, the request and response between the GMLC and the AMF related to receiving the GAD information of the one or more UEs

[0102] include various attributes which may include such as but not limited to IcsClientType, IcsLocation, priority, IcsQoS, additionalSuppGADShape etc.

[0118] For example, when a location-based service provider (LBSP) requests the real-time location of a delivery vehicle (the UE

[0102] ), the transceiver unit

[0302] transmits a request to the AMF unit

[0106] to obtain the relevant GAD information. The AMF unit

[0106] , which is responsible for mobility management and session handling within the mobile network, retrieves the most recent location data of the UE

[0102] and transmits it back to the GMLC system

[0132] , In another example, if a public safety organization requires the location of a lost individual’s mobile device (the UE

[0102] ), the transceiver unit

[0302] would send a request to the AMF unit

[0106] for GAD information. The AMF unit

[0106] may then pull the last known location of the device and return this data to the GMLC system

[0132] for further processing.

[0119] The transceiver unit

[0302] transmits, at the GMLC system

[0132] , the request related to receiving the geographical area description (GAD) information of the one or more UEs

[0102] to the AMF unit

[0106] , In an exemplary aspect, the transceiver unit sends a request to the AMF unit

[0106] in order to retrieve GAD information that may include such as but not limited only to information such as shape of the geographical location of the one or more UEs

[0102] , latitudinal and longitudinal coordinates the one or more UEs

[0102] etc.

[0120] At step 408, the method

[0400] comprises receiving, by the transceiver unit

[0302] at the GMLC system

[0132] from the AMF unit

[0106] , the GAD information of the one or more UEs

[0102] , Once the transceiver unit

[0302] transmits a request to the AMF unit

[0106] for the GAD information, the AMF unit retrieves the required geographical data, which includes the current location coordinates of the UE(s)

[0102] , such as latitude and longitude. This information is then sent back to the GMLC system

[0132] via the transceiver unit

[0302] , allowing the system to process the location data further. In an exemplary aspect, the received GAD information in the form of response is alternatively called as ProvidePosInfoExt. In an exemplary aspect, the received GAD information includes various attributes which may include such as but not limited to IcsClientType, IcsLocation, priority, IcsQoS, additionalSuppGADShape etc.

[0121] For example, in a scenario where a client device, such as a location-based service provider (LBSP), requests the location of a fleet vehicle (such as UE

[0102] ), the AMF unit

[0106] collectsthe real-time GAD information from the network and transmits it to the GMLC system

[0132] , The transceiver unit

[0302] is responsible for receiving this data and ensuring it is delivered to the appropriate components within the GMLC system

[0132] for further processing, such as format conversion or storage.

[0122] Based on the request sent by the transceiver unit

[0302] to the AMF unit

[0106] for receiving GAD information of one or more UEs

[0102] , the transceiver unit

[0302] receives, at the GMLC system

[0132] , the GAD information of one or more UEs

[0102] from the AMF unit

[0106] ,

[0123] At step 410, the method

[0400] comprises converting, by a converter unit

[0304] at the GMLC system

[0132] , the GAD information into the desired format. Upon receiving the GAD information from the AMF unit

[0106] , which typically includes raw geographical coordinates such as latitude and longitude, the converter unit

[0304] processes and transforms this data into a format specified either by the client request or a pre-configured format associated with the client. This conversion capability allows the GMLC system

[0132] to support various location data formats, ensuring that the location information provided is compatible with the specific requirements of different clients.

[0124] For example, if the GAD information received contains coordinates in a DMS format, but the client device requests the data in the Universal Transverse Mercator (UTM) format, the converter unit

[0304] will translate the raw latitude and longitude values into the UTM format. Similarly, in a case where another client, such as a location information management (LIM) service, requests the location in Degrees, Minutes, and Seconds (DMS) format, the converter unit

[0304] converts the GAD information, accordingly, ensuring the data is presented in the required structure.

[0125] Upon receiving at the transceiver unit

[0302] the GAD information related to the one or more UEs

[0102] , the converter unit

[0304] converts, at the GMLC system

[0132] , the GAD information into the desirable format. In an exemplary aspect, the desired format is a format that is easily understood by the network administrator.

[0126] In an exemplary aspect, the converter unit

[0304] fetches the predefined format from the storage unit

[0306] ,

[0127] In an exemplary aspect, the GAD information includes such as but not limited only to information such as the shape of the UE’s geographical location, latitudinal and longitudinalcoordinates of the UE, and other uncertain information related to location of the UE. Only latitudinal and longitudinal coordinates extracted from the GAD information can be converted to the desirable format.

[0128] At step 412, the method

[0400] transmitting, by the transceiver unit

[0302] at the GMLC system

[0132] to the client device, the location information of the one or more UE

[0102] in the desired format. After the converter unit

[0304] processes and transforms the geographical area description (GAD) information into the format specified by the client, the transceiver unit

[0302] is responsible for relaying this formatted location data back to the client device.

[0129] For example, a location-based service provider (LBSP) may have requested the coordinates of a user equipment (UE)

[0102] in Universal Transverse Mercator (UTM) format. Once the GMLC system

[0132] receives the GAD information from the AMF unit

[0106] and the converter unit

[0304] processes it into UTM format, the transceiver unit

[0302] transmits this UTM data back to the client device. In another scenario, a different client, such as a public safety organization, may have requested the same location data in Degrees Minutes Seconds (DMS) format.

[0130] The transceiver unit

[0302] transmits, from the GMLC system

[0132] , the location information of one or more UE

[0102] in the desired format to the client device. In an exemplary aspect, the transceiver unit

[0302] may transmit the location information of the one or more UE

[0102] in the predefined format to the client device.

[0131] Thereafter, at step

[0414] , the method

[0400] is terminated.

[0132] Referring to FIG. 5, an exemplary diagram of a process flow

[0500] for providing location of a user equipment, is shown, in accordance with the exemplary implementations of the present disclosure.

[0133] At step SI, the process comprises transmitting, from at least one LIM client

[0502] which is the client device, a request for providing location information of the one or more UE

[0102] to the GMLC system

[0132] , In an exemple, the GMLC system

[0132] receives the request related to providing the location information of one or more UE

[0102] in the desired format from the LIM client

[0502] , In an exemplary aspect, the request to provide the location information of one or more UE

[0102] may include location-based services (LBS) request, lawful interception management (LIM) request etc. In an exemplary aspect, the request to provide the location information of oneor more UE

[0102] may also include the UE

[0102] identifier such as but not limited to an International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), Subscription Permanent Identifier (SUPI) etc.

[0134] At step S2, the process

[0500] comprises transmitting, from the GMLC system

[0132] , a request for providing location information of the one or more UE to the AMF unit

[0106] , In an exemplary aspect, the GMLC system

[0132] transmits the request related to receiving the geographical area description (GAD) information of the one or more UEs

[0102] to the AMF unit

[0106] , In an exemplary aspect, the GMLC system

[0132] sends a request to the AMF unit

[0106] in order to retrieve GAD information that may include such as but not limited only to information such as shape of the geographical location of the one or more UEs

[0102] , latitudinal and longitudinal coordinates the one or more UEs

[0102] etc.

[0135] At step S3, the process

[0500] comprises receiving, at the GMLC system

[0132] from the AMF unit

[0106] , a response that includes location information of the one or more UEs

[0102] , Based on the request sent by the GMLC system

[0132] to the AMF unit

[0106] for receiving GAD information of one or more UEs

[0102] , the GMLC system

[0132] receives the GAD information of one or more UEs

[0102] from the AMF unit

[0106] ,

[0136] At step S4, the process

[0500] comprises retrieving, from configuration unit

[0504] , the client related information in a client configured format (also referred to herein as pre-configured format). In an exemplary aspect, the configuration unit

[0504] stores client related information. Alternatively, the configuration unit

[0504] is also called as storage unit

[0306] , In an exemplary aspect, the storage unit

[0306] stores the pre-defined format associated with the clients in the form of mapping data.

[0137] In an exemplary aspect, the GMLC system

[0132] fetches / retrieves the predefined format from the configuration unit

[0504] ,

[0138] Finally, at step S5, the process

[0500] comprises transmitting, by the GMLC system

[0132] , the location information of one or more UE

[0102] in the desired format to the LIM client

[0502] , In an exemplary aspect, the GMLC system

[0132] may transmit the location information of the one or more UE

[0102] in the predefined format to the LIM client

[0502] ,

[0139] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for providing location of a user equipment, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit

[0302] to receive, from a client device, a request related to providing a location information of one or more user equipment (UE)

[0102] in a desired format. The executable code when executed further causes the transceiver unit

[0302] to transmit, to an access and mobility management function (AMF) unit

[0106] , a request related to receiving a geographical area description (GAD) information of the one or more UEs

[0102] , The executable code when executed further causes the transceiver unit

[0302] to receive, from the AMF unit

[0106] , the GAD information of the one or more UEs

[0102] , The executable code when executed further causes a converter unit

[0304] to convert the GAD information into the desired format. The executable code when executed further causes the transceiver unit

[0302] to transmit, to the client device, the location information of the one or more UE

[0102] in the desired format.

[0140] As is evident from the above, the present disclosure provides a technically advanced solution for providing location of a user equipment. The main advantage of the present solution is that GMLC allows providing different location co-ordinate configuration format based on different clients.

[0141] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

[0142] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components / units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

Claims

We Claim:

1. A method for providing location of a user equipment, the method comprising: receiving, by a transceiver unit [302] at a gateway mobile location centre (GMLC) system [132] from a client device, a request related to providing a location information of one or more user equipment (UE) [102] in a desired format; transmitting, by the transceiver unit [302] at the GMLC system [132] to an access and mobility management function (AMF) unit [106], a request related to receiving a geographical area description (GAD) information of the one or more UEs [102]; receiving, by the transceiver unit [302] at the GMLC system [132] from the AMF unit [106], the GAD information of the one or more UEs [102]; converting, by a converter unit [304] at the GMLC system [132], the GAD information into the desired format; and transmitting, by the transceiver unit [302] at the GMLC system [132] to the client device, the location information of the one or more UE [102] in the desired format.

2. The method as claimed in claim 1 wherein the desired format is one of: a format defined in the request related to providing the location information, and a pre-defined format associated with the client.

3. The method as claimed in claim 2, wherein storing, in a storage unit [306], the pre-defined format associated with the client as a mapping data, wherein the mapping data comprises each client of the one or more clients mapped with a desired format among one or more pre-defined formats.

4. The method as claimed in claim 1, wherein the desired format is one of a Universal Transverse Mercator (UTM) format, and a Degrees Minutes Seconds (DMS) format.

5. The method as claimed in claim 1 wherein the client device belongs to a client among one or more clients.

6. A system for providing location of a user equipment, the system comprising a gateway mobile location centre (GMLC) system [132], the GMLC system [132] further comprising: a transceiver unit [302] configured to: o receive, from a client device, a request related to providing a location information of one or more user equipment (UE) [102] in a desired format;o transmit, to an access and mobility management function (AMF) unit [106], a request related to receiving a geographical area description (GAD) information of the one or more UEs [102]; o receive, from the AMF unit [106], the GAD information of the one or more UEs [102]; a converter unit [304] connected to at least the transceiver unit [302], the converter unit [304] configured to: o convert the GAD information into the desired format; the transceiver unit [302] further configured to: o transmit, to the client device, the location information of the one or more UE [102] in the desired format.

7. The system as claimed in claim 6, wherein the desired format is one of: a format defined in the request related to providing the location information, and a pre-defined format associated with the client.

8. The system as claimed in claim 7, wherein the system [300] comprises a storage unit [306], the storage unit [306] configured to store the pre-defined format associated with the client as a mapping data, wherein the mapping data comprises each client of the one or more clients mapped with a desired format among one or more pre-defined formats.

9. The system as claimed in claim 6, wherein the desired format is one of a Universal Transverse Mercator (UTM) format, and a Degrees Minutes Seconds (DMS) format.

10. The system as claimed in claim 6 wherein the client device belongs to a client among one or more clients.

11. A non-transitory computer-readable storage medium storing instruction for providing location of a user equipment which, when executed by one or more units of a system, causes: a transceiver unit [302] to: o receive, from a client device , a request related to providing a location information of one or more user equipment (UE) [102] in a desired format;o transmit, to an access and mobility management function (AMF) unit [106], a request related to receiving a geographical area description (GAD) information of the one or more UEs [102]; o receive, from the AMF unit [106], the GAD information of the one or more UEs [102]; a converter unit [304] to at least the transceiver unit [302], the converter unit [304] configured to: o convert the GAD information into the desired format; the transceiver unit [302] further to: o transmit, to the client device, the location information of the one or more UE[102] in the desired format.

Images