FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR CONFIGURING A LOCATION CLIENT SERVICE(S)”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR CONFIGURING A LOCATION CLIENT
SERVICE(S)
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to the field of wireless communication. More particularly, embodiments of the present disclosure relate to configuring a location client services (LCS).
BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[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 antilog 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. The third generation (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] As the wireless communication technology has evolved to a great extent, the number of users/subscribers of the wireless networks has also increased to a great extent and it is important for the wireless networks to provide better and smooth services to its subscribers. Session management plays a critical role in providing better services to the customers/subscribers of a telecom network. Improved session management may lead to improved customer experience. Also, an increased number of sessions for the subscribers may create various problems at a network end and hence impact the user experience and network performance. Therefore, it is required to provide a session management solution that can efficiently handle the sessions created for the subscribers.
[0005] In a 5G network architecture, LIM stands for Lawful Interception and Monitoring systems [sometimes also called as Location Information Manager (LIM) or Location Client Service (LCS) or Location Service Function (LSF) or Location Based Services (LBS)]. LIM is a client or entity that interacts with the gateway mobile location center(s) (GMLC) to manage location information and provide location-based services (LBS). The GMLC is first network in the 5G network node which is accessed by an external location application. The GMLC is responsible for performing registration, authorization of user devices and requests routing information. The GMLC provides information about mobile devices by interfacing with other network elements. It is responsible for overseeing and maintaining location information of users for various purposes.
[0006] There are several limitations associated with GMLC(s) for configuring LCS through various interfaces as different LCS use different protocols and interfaces for communication. Thus, compatibility issues may arise if the GMLC lacks the requisite interface support for a specific LCS, especially based on its respective requirements.

[0007] Hence, in view of these and other existing limitations, there exists a need to configure LCS to overcome the above-mentioned limitations by providing a method and system for configuring LCS, which the present disclosure aims to address.
OBJECTS OF THE DISCLOSURE
[0008] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0009] It is an object of the present disclosure to provide a system and a method for configuring Location Client Service (LCS) through a plurality of interfaces.
[0010] It is yet another object of the present disclosure to ensure enhancement in a Gateway Mobile Location Centre (GMLC) to store or allow configuration of various interfaces like interfaces between the GMLC and a home subscriber server (HSS) like SH/SLH according to LIM client requirements.
SUMMARY
[0011] 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.
[0012] An aspect of the present disclosure may relate to a method for configuring a location client services (LCS). The method comprises receiving, by a transceiver unit at a Gateway Mobile Location Centre (GMLC), a location request from the LCS. The method further comprises fetching, by an identification unit at the GMLC, from the LCS, a set of identification data associated with the LCS. The

method further comprises selecting, by a determination unit at the GMLC, a first configured interface from a set of interfaces, based on the set of identification data associated with the LCS. The method further comprises transmitting, by the transceiver unit via the GMLC, an Access Mobility Management Function identifier (AMFID) request related to the first configured interface, to a Unified Data Management (UDM). The method further comprises receiving, by the transceiver unit at the GMLC, a response from the UDM. It is to be noted that the response is one of: a success response and a failure response. It is further noted that in response to receiving the failure response from the UDM, the method further comprises selecting, by the determination unit at the GMLC, a second configured interface from the set of interfaces, based on the set of identification data associated with the LCS. It is important to note that the second configured interface is different from the first configured interface.
[0013] In an exemplary aspect of the present disclosure, the LCS comprises at least one of location based services (LBS), and lawful interception and monitoring (LIM) systems.
[0014] In an exemplary aspect of the present disclosure, the set of interfaces comprises at least one of a GMLC-SH interface, a GMLC-SLH interface, and a GMLC-SLG interface.
[0015] In an exemplary aspect of the present disclosure, the method further comprises storing, by a storage unit at the GMLC, the set of identification data associated with the LCS in a cache memory unit.
[0016] In an exemplary aspect of the present disclosure, the first configured interface corresponds with one of a 5G network, and a 4G network, and the second configured interface corresponds with another of the 5G network and the 4G network.

[0017] Another aspect of the present disclosure may relate to a system for configuring a location client services (LCS). The system comprises a transceiver unit, at a Gateway Mobile Location Centre (GMLC), configured to receive a location request from the LCS. The system further comprises an identification unit, at the GMLC, configured to fetch, from the LCS, a set of identification data associated with the LCS. The system further comprises a determination unit, at the GMLC, configured to select a first configured interface from a set of interfaces, based on the set of identification data associated with the LCS. The transceiver unit is further configured to transmit, via the GMLC, an Access Mobility Management Function identifier (AMFID) request related to the first configured interface, to a Unified Data Management (UDM). The transceiver unit is further configured to receive, at the GMLC, a response from the UDM. It is to be noted that the response is one of: a success response and a failure response. It is further noted that in response to receiving the failure response from the UDM, the determination unit is configured to select, at the GMLC, a second configured interface from the set of interfaces, based on the set of identification data associated with the LCS. It is important to note that the second configured interface is different from the first configured interface.
[0018] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium, storing instructions for configuring a location client services (LCS), the storage medium comprising executable code which, when executed by one or more units of a system, causes a transceiver unit to receive a location request from the LCS. Further, the executable code which, when executed causes an identification unit to fetch, from the LCS, a set of identification data associated with the LCS. Further, the executable code which, when executed causes a determination unit to select a first configured interface from a set of interfaces, based on the set of identification data associated with the LCS. Further, the executable code which, when executed causes the transceiver unit to transmit, via

the GMLC, an Access Mobility Management Function identifier (AMFID) request related to the first configured interface, to a Unified Data Management (UDM). Further, the executable code which, when executed causes the transceiver unit to receive a response from the UDM. It is to be noted that the response is one of: a success response and a failure response. It is further noted that in response to receiving the failure response from the UDM, the determination unit is configured to select a second configured interface from the set of interfaces, based on the set of identification data associated with the LCS. It is important to note that the second configured interface is different from the first configured interface.
DESCRIPTION OF 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. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0020] FIG.1 illustrates an exemplary block diagram representation of a 5th generation 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 configuring a location client services (LCS), in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 4 illustrates an exemplary method flow diagram for configuring a location client services (LCS), in accordance with the exemplary embodiments of the present disclosure.
[0024] FIG. 5 illustrates another exemplary system indicating the process of configuring a location client services (LCS) through a plurality of interfaces, in accordance with the exemplary embodiments 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 can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[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] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the disclosure. These terms are not intended to limit the scope of the disclosure or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The disclosure is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the disclosure as defined herein.
[0029] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0030] 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 can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a FIG.
[0031] 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.
[0032] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer,

mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0033] Further, the user device and/or a system as described herein to implement technical features as disclosed in the present disclosure may also comprise a “processor” or “processing unit”, wherein processor refers to any logic circuitry for processing instructions. The 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 Processor (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 is a hardware processor.
[0034] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “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, a mobile 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 at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.

[0035] 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.
[0036] 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 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.
[0037] 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.
[0038] 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.

[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 method and system configuring a location client service / location client service(s) (LCS) [142] in a communication network.
[0040] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture [100], in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], a gateway mobile location centre (GMLC) [140] and a location client service (LCS) [142], 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] The Radio Access Network (RAN) [104] is the part of a mobile telecommunications system that connects the user equipment (UE) [102] 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] The Access and Mobility Management Function (AMF) [106] is the 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] The Session Management Function (SMF) [108] is the 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) [128] for data forwarding and handles IP address allocation and Quality of Service (QoS) enforcement. Further, the SMF [108] facilitates enforcement of session management related policy decisions from the PCF [122].
[0044] The Service Communication Proxy (SCP) [110] 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.
[0045] The Authentication Server Function (AUSF) [112] is the network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
[0046] The Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is the 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.
[0047] The Network Slice Selection Function (NSSF) [116] is the network function responsible for selecting the appropriate network slice for the UE based on factors such as subscription, requested services, and network policies.

[0048] The Network Exposure Function (NEF) [118] is the network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0049] The Network Repository Function (NRF) [120] is the 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.
[0050] The Policy Control Function (PCF) [122] enables efficient policy control and management, facilitating network behaviour control, network slicing, user equipment (UE) activities, and communication with other 5G core network functions. PCF is responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. The PCF is responsible for policy control decisions and flow-based charging control functionalities.
[0051] The Unified Data Management (UDM) [124] is the network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0052] The Application Function (AF) [126] is the network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
[0053] The User Plane Function (UPF) [128] is the network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0054] The Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) [102] in a telecommunications system. The data

services may include but are not limited to Internet services, private data network related services.
[0055] The gateway mobile location centre (GMLC) [140] is a first network in the 5G network architecture [100] which is accessed by an external location application. The GMLC [140] is responsible for performing registration, authorization and requests routing information.
[0056] The location client service (LCS) [142] is used to facilitate information exchange related to as user equipment (UE) location within the network elements. It uses various interfaces such as but not limited to NLs, NLg and NLh interfaces to interact with the AMF [106] and UDM [124].
[0057] The present disclosure can be implemented on a computing device [200] as shown in FIG. 2. The computing device [200] implements the present disclosure in accordance with the 5G communication network architecture (as shown in FIG. 1). FIG. 2 illustrates an exemplary block diagram of the computing device [200] 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 [200] may also implement a method [400] for configuring a location client services (LCS) [142] utilising a system [300] (as shown in FIG. 3) and a system [500] (as shown in FIG. 5). In another implementation, the computing device [200] itself implements the method [400] for configuring the location client services (LCS) [142] using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0058] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The

computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
[0059] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], 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 [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. 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.
[0060] The computing device [200] 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 [200] causes

or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] 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.
[0061] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] 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 [218] 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 [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0062] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], the host [224] and the communication interface [218]. The received code may be executed by the processor [204] as it is received,

and/or stored in the storage device [210], or other non-volatile storage for later execution.
[0063] The present disclosure is implemented by the system [300] (as shown in
5 FIG. 3) and the system [500] (as shown in FIG. 5). The system [300] may be
implemented using the computing device [200] (as shown in FIG. 2). In an implementation, the computing device [200] may be connected to the system [300] to perform the present disclosure.
10 [0064] Referring to FIG. 3, an exemplary block diagram of a system [300] for
configuring location client service(s)/a location client service (LCS) [142], is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one transceiver unit [301], at least one identification unit [302], at least one determination unit [303], at least one set
15 of interfaces [304] comprising at least one first configured interface [3041] and at
least one second configured interface [3042], at least one storage unit [305] comprising at least one cache memory unit [3051]. The system [300] is stationed at a gateway mobile location centre(s) (GMLC) [140] in a network. Also, all of the components/ units of the system [300] are assumed to be connected to each other
20 unless otherwise indicated below. As shown in the FIG. 3, all units shown within
the system [300] should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such number of said units, as required to implement the features of the present disclosure. In another
25 implementation, the system [300] may reside in a server or a network entity. In yet
another implementation, the system [300] may reside partly in the server/ network entity.
[0065] The system [300] is configured for configuring a location client services
30 (LCS) [142] in a network, with the help of the interconnection between the
components/units of the system [300]. The configuration is performed by the
19

system [300] through a plurality of interfaces such as but not limited to a GMLC-
SH interface, a GMLC-SLG interface and a GMLC-SLH interface. It is to be noted
that the GMLC-SH interface, the GMLC-SLG interface and the GMLC-SLH
interface are diameter protocol-based interface as per standard document RFC
5 3588. The diameter-based protocol/diameter protocol is intended to provide
authentication and accounting for various network applications and IP mobility.
[0066] In an exemplary aspect of the present disclosure, the transceiver unit [301], at the Gateway Mobile Location Centre (GMLC) [140], is configured to receive a
10 location request from the LCS [142]. The location request may be a Network
Induced Location Request (NI-LR), a Mobile Terminated Location Request (MT-LR), a Mobile Originated Location Request (MO-LR), an Immediate Location Request or a Deferred Location Request. The location request may include a target UE identifier such as a Generic Public Subscription Identifier (GPSI) or a
15 Subscription Permanent Identifier (SUPI). The GPSI is used as a means of
addressing a 3GPP subscription in data networks outside the 3GPP system. These are public identifiers such as MSISDN. The 3GPP system stores within the subscription data the association between the GPSI and the corresponding SUPI. The Subscription Permanent Identifier is a globally unique identifier that is assigned
20 to each subscriber in the 5G communication network, which is provisioned in the
UDM [124] (as shown in FIG.1). The location request may include but not limited to an indication for event trigger, i.e. UE entering/leaving the network; a location estimate of the target UE; duration of event reporting; time interval; linear distance threshold, etc. The transceiver unit [301] is further configured to transmit, via the
25 GMLC [140], an Access Mobility Management Function identifier (AMFID)
request related to the first configured interface [3041], to a Unified Data Management (UDM) [124]. The AMFID request may include initiating an NI-LR location request for the UE with an emergency call situation. In an implementation of the present disclosure, along with transmitting the AMFID request, the
30 transceiver unit [301] may also receive and manage location requests from the
20

GMLC [140] for periodic, triggered and UE available location events. In an implementation of the present disclosure, transceiver unit [301] may also receive and manage location requests from the UE for location information from the NEF [118] (as shown in FIG. 1). In an implementation of the present disclosure, the transceiver unit [301] may also receive updated privacy requirements from the UE. In an implementation of the present disclosure, the transceiver unit [301] may also support cancelation of periodic or triggered location reporting for the target UE, etc. The transceiver unit [301] is further configured to receive, at the GMLC [140], a response from the UDM [124]. It is to be noted that the response is one of: a success response and a failure response.
[0067] In an exemplary aspect of the present disclosure, the identification unit [302], at the GMLC [140], is configured to fetch, from the LCS [142], a set of identification data associated with the LCS [142]. It is to be noted that the set of identification data include but may not be limited to authentication information such as client ID, client password, and the like. This authentication information is stored at the GMLC [140].
[0068] In an exemplary aspect of the present disclosure, the determination unit [303], at the GMLC [140], is configured to select a first configured interface [3041] from a set of interfaces [304], based on the set of identification data associated with the LCS [142].
[0069] In an exemplary aspect of the present disclosure, it is further noted that in response to receiving the failure response from the UDM [124], the determination unit [303] is configured to select, at the GMLC [140], a second configured interface [3042] from the set of interfaces [304], based on the set of identification data associated with the LCS [142]. It is important to note that the second configured interface [3042] is different from the first configured interface [3041].

[0070] In an exemplary aspect of the present disclosure, the LCS [142] comprises at least one of a location based services (LBS), and a lawful interception and monitoring (LIM) systems. It is to be noted that the LBS in a communication network is used for user device applications that requires knowledge about where the user device is geographically located. The LBS helps in collecting geodata of the user device. The geodata may include data gathered in real time using location tracking. Further, the LIM allows legal enforcement authorities of a particular jurisdiction to get the necessary information from the communication network as per specific security requirements without disruption of the normal mode of operations and without jeopardizing the privacy of the user.
[0071] In an exemplary aspect of the present disclosure, the set of interfaces [304] comprises at least one of: a GMLC-SH interface, a GMLC-SLH interface, and a GMLC-SLG interface.
[0072] In an exemplary aspect of the present disclosure, the storage unit [305] is configured to store, at the GMLC [140], the set of identification data associated with the LCS [142] in the cache memory unit [3051].
[0073] In an exemplary aspect of the present disclosure, the first configured interface [3041] corresponds with one of a 5G network, and a 4G network, and the second configured interface [3042] corresponds with another of the 5G network and the 4G network.
[0074] Referring to FIG. 4, an exemplary method flow diagram [400] for configuring a location client services (LCS) [142] in a network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300] (as shown in FIG. 3) and a system [500] (as shown in FIG. 5). Further, in an implementation, the system [300] and the system [500] may be present in a server device to

implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
[0075] At step [404], the method [400] comprises receiving, by the transceiver unit [301] at a Gateway Mobile Location Centre (GMLC) [140], a location request from the LCS [142]. It is to be noted that the location request may be a Network Induced Location Request (NI-LR), a Mobile Terminated Location Request (MT-LR), a Mobile Originated Location Request (MO-LR), an Immediate Location Request or a Deferred Location Request. The location request may include but not limited to an indication for event trigger, i.e. UE entering/leaving the network; a location estimate of the target UE; duration of event reporting; time interval; linear distance threshold, etc.
[0076] In an exemplary aspect of the present disclosure, the LCS [142] comprises at least one of a location based services (LBS), and a lawful interception and monitoring (LIM) systems.
[0077] At step [406], the method [400] comprises fetching, by the identification unit [302] at the GMLC [140], from the LCS [142], the set of identification data associated with the LCS [142].
[0078] At step [408], the method [400] comprises selecting, by the determination unit [303] at the GMLC [140], the first configured interface [3041] from the set of interfaces [304], based on the set of identification data associated with the LCS [142].
[0079] In an exemplary aspect of the present disclosure, the set of interfaces [304] comprises at least one of a GMLC-SH interface, a GMLC-SLH interface, and a GMLC-SLG interface.

[0080] At step [410], the method [400] comprises transmitting, by the transceiver unit [301] via the GMLC [140], the Access Mobility Management Function identifier (AMFID) request related to the first configured interface [3041], to the Unified Data Management (UDM) [124].
[0081] At step [412], the method [400] comprises receiving, by the transceiver unit [301] at the GMLC [140], a response from the UDM [124]. It is to be noted that the response is one of: a success response and a failure response.
[0082] At step [414], in response to receiving the failure response from the UDM [124], the method [400] further comprises selecting, by the determination unit [303] at the GMLC [140], the second configured interface [3042] from the set of interfaces [304], based on the set of identification data associated with the LCS [142]. It is important to note that the second configured interface [3042] is different from the first configured interface [3041]. It is further important to note that in the case of success response, the method [400] leads to termination step.
[0083] In an exemplary aspect of the present disclosure, the first configured interface [3041] corresponds with one of a 5G network, and a 4G network, and the second configured interface [3042] corresponds with another of the 5G network and the 4G network.
[0084] In an exemplary aspect of the present disclosure, the method further comprises storing, by a storage unit [305] at the GMLC [140], the set of identification data associated with the LCS [142] in a cache memory unit [3051].
[0085] Thereafter, the method [400] terminates at step [416].
[0086] Referring to FIG. 5, another exemplary system [500] indicating the process of configuring a location client services (LCS) [142] through a plurality/set of interfaces is shown in accordance with the present disclosure. Further, the method

[400] (as depicted in FIG. 4) is performed by the system [300] (as depicted in FIG. 3) and the system [500] (as depicted in FIG. 5). The system [500] comprises at least one LCS [142], at least one GMLC [140] and a Mobility Management Entity (MME) [504]. The MME [504] (also known as evolved packet core (EPC)). The MME [504] is responsible for managing session states, authentication, paging, mobility of user devices/ user equipment (UE) (not shown in figure). By managing the movement of UE, the MME [504] ensures seamless connectivity of UE with the communication network without interruption. The GMLC [140] is connected to a UDM [124]. The UDM [124] is configured to get an AMF ID request from the GMLC [140]. The LCS [142] sends a request to the GMLC [140] for a location for a target UE identified by the GPSI/ SUPI. The GMLC [140] invokes a “Nudm_UEContextManagement_Get service” operation (also known as AMF ID request) towards the UDM [124] of the target UE to be located with the GPSI/ SUPI. The “Nudm_UEContextManagement_Get service” perform various service operations such as but not limited to an AMF [106] registration, the AMF [106] deregistration etc. For instance, the Nudm_UEContextManagement Service is used by NFs (such as the AMF [106], a SMF [108] etc.) to register at the UDM [124] by means of the registration service operation; the Nudm_UEContextManagement Service is also used by the AMF [106] to get notified by means of the DeregistrationNotification service operation when the UDM [124] decides to deregister the registered NFs.
[0087] The system [500] is configured to receive a location request from the LCS [142] at the GMLC [140]. On receiving the location request, the GMLC [140] is configured to identify and store a set of identification data (containing the LCS [142] details) in a cache memory [3051]. The GMLC [140] is further configured to send an Access Mobility Management Function Identifier (AMFID) request to the UDM [124]. After receiving a failure response (such as but not limited to 404 response) from the UDM [124], the GMLC [140] is configured to delegate the request to a plurality/set of interfaces based on a configured interface in the LCS

[142] details. The plurality of interfaces comprises a GMLC-SH [501] interface, a GMLC-SLH [502] interface and a GMLC-SLG [503] interface but the present disclosure is not limited thereto. It is important to note that the GMLC-SLG interface [503] is a mandatory interface. The GMLC-SLG interface [503] works in tandem with either the GMLC-SH [501] interface or the GMLC-SLH [502] interface. The application of the GMLC-SH [501] interface and the GMLC-SLH [502] interface vary depending upon the type of request they handle. For e.g. the GMLC-SH [501] interface is responsible for handling requests such as a User Data Request (UDR) etc. While the GMLC-SLH [502] interface handles Routing Information Request (RIR). Either of the GMLC-SH [501] interface and the GMLC-SLH [502] interface is selected based on the delegation of the Access Mobility Management Function Identifier (AMFID) request. This delegation is carried out based on the configured interface in client details by the GMLC [140].
[0088] Another aspect of the present disclosure may relate to a non-transitory computer readable storage medium, storing instructions for configuring a location client services (LCS) [142], the storage medium comprising executable code which, when executed by one or more units of a system [300], causes a transceiver unit [301] to receive a location request from the LCS [142]. Further, the executable code which, when executed causes an identification unit [302] to fetch, from the LCS [142], a set of identification data associated with the LCS [142]. Further, the executable code which, when executed causes a determination unit [303] to select a first configured interface [3041] from a set of interfaces [304], based on the set of identification data associated with the LCS [142]. Further, the executable code which, when executed causes the transceiver unit [301] to transmit, via the GMLC [140], an Access Mobility Management Function identifier (AMFID) request related to the first configured interface [3041], to a Unified Data Management (UDM) [106]. Further, the executable code which, when executed causes the transceiver unit [301] to receive, at the GMLC [140], a response from the UDM [124]. It is to be noted that the response is one of: a success response and a failure

response. It is further noted that in response to receiving the failure response from the UDM [124], the determination unit [303] is configured to select, at the GMLC [140], a second configured interface [3042] from the set of interfaces [304], based on the set of identification data associated with the LCS [142]. It is important to note that the second configured interface [3042] is different from the first configured interface [3041].
[0089] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the 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.
[0090] As is evident from the above, the present disclosure provides a technically advanced solution for configuring the location client services (LCS) [142] through a plurality/set of interfaces based on the client requirements and thereby giving enhanced utilities to the gateway mobile location centres (GMLC) [140]. This is achieved when the GMLC [140] sends the AMF_ID request to the UDM [124] and receives success or failure response in return depending upon the presence of the AMF ID in the response. Thus, the failure response indicates that the user equipment (UE) is not in the same network.
[0091] 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.

We Claim:
1. A method [400] for configuring a location client services (LCS) [142], the
method [400] comprising:
- receiving, by a transceiver unit [301] at a Gateway Mobile Location Centre (GMLC) [140], a location request from the LCS [142];
- fetching, by an identification unit [302] at the GMLC [140], from the LCS [142], a set of identification data associated with the LCS [142];
- selecting, by a determination unit [303] at the GMLC [140], a first configured interface [3041] from a set of interfaces [304], based on the set of identification data associated with the LCS [142];
- transmitting, by the transceiver unit [301] via the GMLC [140], an Access Mobility Management Function identifier (AMF ID) request related to the first configured interface [3041], to a Unified Data Management (UDM) [124]; and
- receiving, by the transceiver unit [301] at the GMLC [140], a response from the UDM [124], wherein the response is one of: a success response and a failure response, and
wherein, in response to receiving the failure response from the UDM [124], the method [400] comprises:
- selecting, by the determination unit [303] at the GMLC [140], a second
configured interface [3042] from the set of interfaces [304], based on the set
of identification data associated with the LCS [142], wherein the second
configured interface [3042] is different from the first configured interface
[3041].
2. The method [400] as claimed in claim 1, wherein the LCS [142] comprises at least one of location based services (LBS), and lawful interception and monitoring (LIM) systems.
3. The method [400] as claimed in claim 1, wherein the set of interfaces [304] comprises at least one of a GMLC-SH interface, a GMLC-SLH interface, and a GMLC-SLG interface.

4. The method [400] as claimed in claim 1, wherein the method [400] comprises storing, by a storage unit [305] at the GMLC [140], the set of identification data associated with the LCS [142] in a cache memory unit [3051].
5. The method [400] as claimed in claim 1, wherein the first configured interface [3041] corresponds with one of a 5G network, and a 4G network, and the second configured interface [3042] corresponds with another of the 5G network and the 4G network.
6. A system [300] for configuring a location client services (LCS) [142], the system [300] comprising:

- a transceiver unit [301], at a Gateway Mobile Location Centre (GMLC) [140], configured to receive a location request from the LCS [142];
- an identification unit [302], at the GMLC [140], configured to fetch, from the LCS [142], a set of identification data associated with the LCS [142]; and
- a determination unit [303], at the GMLC [140], configured to select a first configured interface [3041] from a set of interfaces [304], based on the set of identification data associated with the LCS [142];
the transceiver unit [301] configured to:
- transmit, via the GMLC [140], an Access Mobility Management Function identifier (AMFID) request related to the first configured interface [3041], to a Unified Data Management (UDM) [124]; and
- receive, at the GMLC [140], a response from the UDM [124], wherein the response is one of: a success response and a failure response, and
wherein, in response to receiving the failure response from the UDM [124], the determination unit [303] is configured to:
- select, at the GMLC [140], a second configured interface [3042] from the
set of interfaces [304], based on the set of identification data associated with
the LCS [142], wherein the second configured interface [3042] is different
from the first configured interface [3041].

7. The system [300] as claimed in claim 6, wherein the LCS [142] comprises at least one of location based services (LBS), and lawful interception and monitoring (LIM) systems.
8. The system [300] as claimed in claim 6, wherein the set of interfaces [304] comprises at least one of a GMLC-SH interface, a GMLC-SLH interface, and a GMLC-SLG interface.
9. The system [300] as claimed in claim 6, wherein the system [300] comprises a storage unit [305] configured to store, at the GMLC [140], the set of identification data associated with the LCS [142] in a cache memory unit [3051].
10. The system [300] as claimed in claim 6, wherein the first configured interface [3041] corresponds with one of a 5G network, and a 4G network, and the second configured interface [3042] corresponds with another of the 5G network and the 4G network.