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 OBTAINING LOCATION PARAMETERS AT A GATEWAY MOBILE LOCATION
CENTRE SERVER”
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 OBTAINING LOCATION PARAMETERS AT A GATEWAY MOBILE LOCATION CENTRE SERVER
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to methods and systems for obtaining one or more location parameters at a gateway mobile location centre (GMLC) server.
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 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] In conventional networks, a Location Information Manager (LIM) server interacts with a Gateway Mobile Location Centre (GMLC) server to manage the location information of a user equipment (UE). The LIM server is responsible for overseeing and maintaining location information for various purposes. In some situations, the LIM server can send a Mobile Station International Subscriber Directory Number (MSISDN) to the GMLC server. In such situations, the GMLC server is needed to convert MSISDN to an International Mobile Subscriber Identity (IMSI) number for fetching location parameters from a location providing server and providing a SMS based location flow using a Short Message Peer to Peer (SMPP) protocol. While converting the MSISDN to the IMSI, in conventional approaches, the GMLC server is configured to communicate with a 4G Home Subscriber Server (4G HSS). In case a negative response is received from the 4G HSS, the GMLC server will be unable to convert the MSISDN to the IMSI and, consequently, will be unable to fetch the location parameters from the location providing server.
[0005] Thus, there exists an imperative need in the art for a system and method for obtaining one or more location parameters at a gateway mobile location centre (GMLC) server, which the present disclosure aims to address.
SUMMARY
[0006] 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.
[0007] An aspect of the present disclosure may relate to a method for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server. The method includes receiving, by a transceiver unit at the GMLC server, a Mobile Subscriber Integrated Service Digital Network (MSISDN), from a Location Information Manager (LIM) server. Next, the method includes initiating, by a processing unit at the GMLC server, a conversion of the MSISDN to an International Mobile Subscriber Identity (IMSI) based on the received MSISDN. Next, the method includes sending, by the transceiver unit from the GMLC server, an IMSI query to a first Home Subscriber Server (HSS). Next, the method includes sending, by the transceiver unit from the GMLC server, the IMSI query to a second HSS, if a negative response is received from the first HSS. Next, the method includes sending, by the transceiver unit from the GMLC server, a request for the one or more location parameters to a location-providing server upon reception of the IMSI from the second HSS. Thereafter, the method includes receiving, by the transceiver unit at the GMLC server, the one or more location parameters from the location-providing server.
[0008] In an exemplary aspect of the present disclosure, the method further comprises, wherein the MSISDN is received from the LIM server using Short Message Peer-to-Peer (SMPP) protocol.
[0009] In an exemplary aspect of the present disclosure, the method further comprises, wherein the first HSS comprises at least a 4G HSS.
[0010] In an exemplary aspect of the present disclosure, the method further comprises, wherein the second HSS comprises at least a 5G HSS.

[0011] In an exemplary aspect of the present disclosure, the method further comprises, wherein the one or more location parameters comprise at least one of a mobile country code (MCC) and a mobile network code (MNC).
[0012] In an exemplary aspect of the present disclosure, the method further comprises, wherein sending the request for the one or more location parameters from the GMLC server to the location-providing server is performed after receiving an authentication from an access and mobility management function (AMF) server.
[0013] In an exemplary aspect of the present disclosure, the method further comprises, wherein the location providing server is a Query Number Portability Database (QNPDB) server.
[0014] Another aspect of the present disclosure may relate to a system for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server. The system comprises a transceiver unit configured to receive, at the GMLC server, a Mobile Subscriber Integrated Service Digital Network (MSISDN), from a Location Information Manager (LIM) server. The system further comprises a processing unit connected to at least the transceiver unit, wherein the processing unit is configured to initiate, at the GMLC server, a conversion of the MSISDN to an International Mobile Subscriber Identity (IMSI) based on the received MSISDN. The system further comprises the transceiver unit, which is configured to send, from the GMLC server, an IMSI query to a first Home Subscriber Server (HSS); send, from the GMLC server, the IMSI query to a second HSS, if a negative response is received from the first HSS; send, from the GMLC server, a request for the one or more location parameters to a location-providing server upon reception of the IMSI from the second HSS; and receive, at the GMLC server, the one or more location parameters from the location-providing server.

[0015] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to receive, at the GMLC server, a Mobile Subscriber Integrated Service Digital Network (MSISDN), from a Location Information Manager (LIM) server; a processing unit of the system connected to at least the transceiver unit, to initiate a conversion of the MSISDN to an International Mobile Subscriber Identity (IMSI) based on the received MSISDN; the transceiver unit of the system is further to send, from the GMLC server, an IMSI query to a first Home Subscriber Server (HSS); to send, from the GMLC server, the IMSI query to a second HSS, if a negative response is received from the first HSS; to send, from the GMLC server, a request for the one or more location parameters to a location-providing server upon reception of the IMSI from the second HSS; and to receive, at the GMLC server, the one or more location parameters from the location-providing server.
OBJECTS OF THE INVENTION
[0016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0017] It is an object of the present disclosure to provide a system and a method for obtaining location parameters despite receiving negative response from 4G HSS.
[0018] It is another object of the present disclosure to provide a solution that provides SMS based location flow by SMPP protocol, despite receiving negative response from 4G HSS.

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 of a computing device upon which the features of the present disclosure may be implemented, in accordance with exemplary implementations of the present disclosure.
[0021] FIG. 2 illustrates an exemplary block diagram of a system for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server, in accordance with exemplary implementations of the present disclosure.
[0022] FIG. 3 illustrates a flow diagram of a method for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server, in accordance with exemplary implementations of the present disclosure.

[0023] FIG. 4 illustrates a sequence flow diagram for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server, in accordance with exemplary implementations of the present disclosure.
[0024] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0025] 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.
[0026] 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.
[0027] 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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 refer 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. 5
[0034] 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
10 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.
[0035] As used herein the transceiver unit includes at least one receiver and at least
15 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.
[0036] As used herein, Gateway Mobile Location Centre (GMLC) contains the
20 functionality required to support LCS. In a wireless network, such as a Public Land
Mobile Network (PLMN), there may be more than one GMLC. A GMLC may be a first node of contact that an external Location Services (LCS) client may access in the PLMN.
25 [0037] As used herein, Mobile Station International Subscriber Directory Number
(MSISDN) is a number that uniquely identifies a subscription in a mobile network, such as a GSM, a UMTS, a 4G, or a 5G network.
11

[0038] As used herein, International Mobile Subscriber Identity (IMSI) is a
globally unique number allocated to each mobile subscriber in the network system,
such as GSM. IMSI may comprise 3-bit mobile country code (MCC) and 2-bit or
3-bit mobile network code. The MCC is a unique identifier for every country in the
5 world. The MNC is a unique identifier for every network inside the country.
[0039] As used herein, Home Subscriber Server (HSS) is a subscriber database used within the IP Multimedia Subsystem (IMS) which provides details of the subscribers to other network entities within the network. 10
[0040] As used herein, a Location Information Manager (LIM) server refers to a service that is configured to manage and provide location-related information about a subscriber or a user equipment (UE) or mobile devices located within a network.
15 [0041] As used herein, an Access and Mobility Management Function (AMF) 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.
20 [0042] As used herein, a Location Services (LCS) refers to a service concept in
system (e.g. GSM or UMTS) standardization. LCS specifies all the necessary network elements and entities, their functionalities, interfaces, as well as communication messages, due to implement the positioning functionality in a cellular network.
25
[0043] As used herein, an LCS Client interacts with an LCS Server for the purpose of obtaining location information for one or more Mobile Stations (MS) or user equipment (UE).
12

[0044] As discussed in the background section, the current known solutions have
several shortcomings and there are no known solutions for obtaining location
parameters after receiving a negative response from a 4G HSS. The present
disclosure aims to overcome the above-mentioned and other existing problems in
5 this field of technology by a method and a system for obtaining one or more location
parameters at a Gateway Mobile Location Centre (GMLC) server.
[0045] Further, as per known methods or solutions, when the GMLC server receives a location request from a location service (LCS) client, the location request
10 may comprise MSISDN or IMSI of the subscriber or user equipment (UE). The
GMLC server may route the location request from the HSS over supported interface. Further, the GMLC server may verify, or authenticate the LCS client, and/or verify the UE before forwarding the location request to an AMF or to another GMLC. However, in response to this request, if HSS provides a negative response,
15 there is no further method or solution to proceed with the GMLC request. The
present disclosure provides a method and a system for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server during an event when a negative response is received from a first HSS.
20 [0046] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
[0047] FIG. 1 illustrates an exemplary block diagram of a computing device [100] (also referred to herein as a computer system [100]) upon which the features of the
25 present disclosure may be implemented, in accordance with exemplary
implementations of the present disclosure. In an implementation, the computing device [100] may also implement a method for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server utilising the system. In another implementation, the computing device [100] itself implements
30 the method for obtaining one or more location parameters at a Gateway Mobile
13

Location Centre (GMLC) server using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
5 [0048] The computing device [100] may include a bus [102] or other
communication mechanism for communicating information, and a hardware
processor [104] coupled with bus [102] for processing information. The hardware
processor [104] may be, for example, a general-purpose microprocessor. The
computing device [100] may also include a main memory [106], such as a random-
10 access memory (RAM), or other dynamic storage device, coupled to the bus [102]
for storing information and instructions to be executed by the processor [104]. The
main memory [106] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [104]. Such instructions, when stored in non-transitory storage media
15 accessible to the processor [104], render the computing device [100] into a special-
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [100] further includes a read only memory
(ROM) [108] or other static storage device coupled to the bus [102] for storing static
information and instructions for the processor [104].
20
[0049] A storage device [110], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [102] for storing information and
instructions. The computing device [100] may be coupled by the bus [102] to a
display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
25 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [114], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [102] for communicating information and command selections to the processor
[104]. Another type of user input device may be a cursor controller [116], such as
30 a mouse, a trackball, or cursor direction keys, for communicating direction
14

information and command selections to the processor [104], and for controlling cursor movement on the display [112]. This 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. 5
[0050] The computing device [100] 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 [100] causes or programs the computing device [100] to be a special-purpose machine.
10 According to one implementation, the techniques herein are performed by the
computing device [100] in response to the processor [104] executing one or more sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions
15 contained in the main memory [106] causes the processor [104] 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.
20 [0051] The computing device [100] also may include a communication interface
[118] coupled to the bus [102]. The communication interface [118] provides a two-way data communication coupling to a network link [120] that is connected to a local network [122]. For example, the communication interface [118] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
25 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [118] 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 [118] sends and receives electrical,
15

electromagnetic or optical signals that carry digital data streams representing various types of information.
[0052] The computing device [100] can send messages and receive data, including
5 program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [128], the
ISP [126], the local network [122], host [124] and the communication interface
[118]. The received code may be executed by the processor [104] as it is received,
10 and/or stored in the storage device [110], or other non-volatile storage for later
execution.
[0053] The computing device [100] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of the
15 computing device [100] includes, but is not limited 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, the computing device [100] may include peripheral devices, such as monitors, keyboards, and printers, as well as
20 integrated components within larger electronic systems, showcasing their
versatility in various technological applications.
[0054] Referring to FIG. 2, an exemplary block diagram of a system [200] for obtaining one or more location parameters at a Gateway Mobile Location Centre
25 (GMLC) server, is shown, in accordance with the exemplary implementations of
the present disclosure. The system [200] comprises at least one transceiver unit [202], at least one processing unit [204], at least one GMLC server [206], at least one LIM server [208], at least one first home subscriber server (HSS) [210], at least one second HSS [212], at least one location providing server [214], and at least one
30 AMF server [216]. Also, all of the components/ units of the system [200] are
16

assumed to be connected to each other unless otherwise indicated below. Also, in
FIG. 2 only a few units are shown; however, the system [200] may comprise
multiple such units or the system [200] may comprise any such numbers of said
units, as required to implement the features of the present disclosure. Further, in an
5 implementation, the system [200] may be present in a user equipment (UE) (such
as, a user device) to implement the features of the present invention. The system
[200] may be a part of the UE or may be independent of but in communication with
the UE. In another implementation, the system [200] may reside in a server or a
network entity. In yet another implementation, the system [200] may reside partly
10 in the server/ network entity and partly in the UE.
[0055] The system [200] is configured for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server, with the help of the interconnection between the components/units of the system [200].
15
[0056] The system [200] comprises a transceiver unit [202]. The transceiver unit [202] is configured to receive, at the GMLC server [206], a Mobile Subscriber Integrated Service Digital Network (MSISDN), from a Location Information Manager (LIM) server [208]. The transceiver unit [202] is configured to receive
20 location information such as MSISDN, a uniquely identifying number of a
subscriber in a network (e.g. GSM, 4G and 5G), from the LIM server [208] using Short Message Peer-to-Peer (SMPP) protocol. The SMPP protocol may facilitate communication interface between Short Message Service Centre (SMSC) and external message entities, web application and routing entities.
25
[0057] The system [200] comprises a processing unit [204]. The processing unit [204] is connected to at least the transceiver unit [202]. The processing unit [204] is configured to initiate, at the GMLC server [206], a conversion of the MSISDN to an International Mobile Subscriber Identity (IMSI) based on the received
30 MSISDN.
17

[0058] The transceiver unit [202] is configured to send the received MSISDN
number to the processing unit [204]. The processing unit [204] is configured to
5 initiate the conversion of the MSISDN to the IMSI based on the received MSISDN
by communicating with one or more network devices such as, but not limited to, home subscriber server (HSS). The IMSI number is a unique number associated with the subscriber, user equipment (UE) or mobile station (MS) only.
10 [0059] The transceiver unit [202] is further configured to send, from the GMLC
server [206], an IMSI query to a first Home Subscriber Server (HSS) [210].
[0060] The transceiver unit [202] is further configured to send, from the GMLC
server [206], the IMSI query to a second HSS [212], if a negative response is
15 received from the first HSS [210]. After IMSI querying with the first HSS [210] if
the transceiver unit [202] receives a negative response from the first HSS [210], the transceiver unit [302] may send further the IMSI query to the second HSS [212] for getting IMSI information associated with the subscriber or UE or target UE.
20 [0061] For example, the transceiver unit [202] may send the IMSI query to the first
HSS [210] (such as a 4G HSS) for getting IMSI information associated with the subscriber or UE or target UE. The first HSS [210] may respond with a negative notification indicative of an inability of the first HSS [210] to provide the information associated with the subscriber or UE or target UE. In such a case, the
25 transceiver unit [202] may send the IMSI query to the second HSS [212] (such as a
5G HSS) for getting IMSI information associated with the subscriber or UE or target UE.
18

[0062] However, in another implementation, the GMLC server [206] may receive a positive response from the first HSS [210]. In other words, upon sending the query to the first HSS [210], the first HSS [210] may provide IMSI information associated with the subscriber or UE or target UE. 5
[0063] The transceiver unit [202] is further configured to send, from the GMLC server [206], a request for the one or more location parameters to a location-providing server [214] upon receipt of the IMSI from the second HSS [212]. The one or more location parameters may include, without limitations, at least one of a
10 mobile country code (MCC) and a mobile network code (MNC). The transceiver
unit [202] may send the request for the one or more location parameters from the GMLC server [206] to the location-providing server [214] after receiving an authentication from an access and mobility management function (AMF) server [216]. The authentication may be associated with the subscriber or UE identity. In
15 an exemplary implementation, the GMLC may check authentication of the LIM
server/client or location service (LCS) client.
[0064] The transceiver unit [202] is further configured to receive, at the GMLC
server [206], the one or more location parameters from the location-providing
20 server [214]. Further in response to the received request, the location-providing
server is configured to transmit the one or more location parameters, which the transceiver unit [202] receives. The location-providing server [214] may be a Query Number Portability Database (QNPDB) server.
25 [0065] The QNPDB is configured to support MNP (mobile number portability)
services. When a request is sent for porting a number, it is passed on to the QNPDB server. The QNPDB in turn, passes the request to an existing operator (also known as a donor operator). The donor operator then checks the billing operator for any uncleared dues, plans or contracts. Once this verification happens in the donor
30 operator's database, the number is cleared for porting. The porting code received
19

from the donor operator is then passed on to a new operator (also known as a receiving operator).
[0066] Further, in accordance with the present disclosure, it is to be acknowledged
5 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
10 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.
15 [0067] Referring to FIG. 3 an exemplary flow diagram for a method [300], for
obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [300] is performed by the system [200]. As shown in FIG. 3, the method [300] starts at step [302].
20
[0068] At step [304], the method [300] comprises receiving, by a transceiver unit [202] at the GMLC server [206], a Mobile Subscriber Integrated Service Digital Network (MSISDN), from a Location Information Manager (LIM) server [208]. The transceiver unit [202] may receive location information such as MSISDN, a
25 uniquely identifying number of a subscriber in a network (e.g. GSM, 4G and 5G),
from the LIM server [208] using Short Message Peer-to-Peer (SMPP) protocol. The SMPP protocol may facilitate communication interface between Short Message Service Centre (SMSC) and external message entities, web application and routing entities.
30
20

[0069] Next, at step [306], the method [300] comprises initiating, by a processing unit [204] at the GMLC server [206], a conversion of the MSISDN to an International Mobile Subscriber Identity (IMSI) based on the received MSISDN. The transceiver unit [202] may send the received MSISDN number to the processing unit [204]. The processing unit [204] is configured to initiate the conversion of the MSISDN to the IMSI based on the received MSISDN by communicating with one or more network devices such as, but not limited to, home subscriber server (HSS). The IMSI number is a unique number associated with the subscriber, user equipment (UE) or mobile station (MS) only.
[0070] Next, at step [308], the method [300] comprises sending, by the transceiver unit [202] from the GMLC server [206], an IMSI query to a first Home Subscriber Server (HSS) [210].
[0071] Next, at step [310], the method [300] comprises sending, by the transceiver unit [202] from the GMLC server [206], the IMSI query to a second HSS [212], if a negative response is received from the first HSS [210]. After IMSI querying with the first HSS [210] if the transceiver unit [202] receives a negative response from the first HSS [210], the transceiver unit [302] may send further the IMSI query to the second HSS [212] for getting IMSI information associated with the subscriber or UE or target UE.
[0072] For example, the transceiver unit [202] may send the IMSI query to the first HSS [210] (such as a 4G HSS) for getting IMSI information associated with the subscriber or UE or target UE. The first HSS [210] may respond with a negative notification indicative of an inability of the first HSS [210] to provide the information associated with the subscriber or UE or target UE. In such a case, the transceiver unit [202] may send the IMSI query to the second HSS [212] (such as a 5G HSS) for getting IMSI information associated with the subscriber or UE or target UE.

[0073] However, in another implementation, the GMLC server [206] may receive a positive response from the first HSS [210]. In other words, upon sending the query to the first HSS [210], the first HSS [210] may provide IMSI information associated with the subscriber or UE or target UE.
[0074] Next, at step [312], the method [300] comprises sending, by the transceiver unit [202] from the GMLC server [206], a request for the one or more location parameters to a location-providing server [214] upon receipt of the IMSI from the second HSS [212]. The one or more location parameters may include, without limitations, at least one of a mobile country code (MCC) and a mobile network code (MNC). The transceiver unit [202] may send the request for the one or more location parameters from the GMLC server [206] to the location-providing server [214] after receiving an authentication from an access and mobility management function (AMF) server [216]. The authentication may be associated with the subscriber or UE identity. In an exemplary implementation, the GMLC may check authentication of the LIM client or location service (LCS) client.
[0075] Next, at step [314], the method [300] comprises receiving, by the transceiver unit [202] at the GMLC server [206], the one or more location parameters from the location-providing server [214].
[0076] Further in response to the received request, the location-providing server is configured to transmit the one or more location parameters, which the transceiver unit [202] receives. The location-providing server [214] may be a Query Number Portability Database (QNPDB) server.
[0077] Thereafter, the method [300] terminates at step [316].

[0078] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server, the instructions include executable code which, when executed by a one or more units of a system [200], causes: a transceiver unit [202] of the system to receive, at the GMLC server [206], a Mobile Subscriber Integrated Service Digital Network (MSISDN), from a Location Information Manager (LIM) server [208]; a processing unit [204] of the system connected to at least the transceiver unit [202], to initiate, at the GMLC server [206], a conversion of the MSISDN to an International Mobile Subscriber Identity (IMSI) based on the received MSISDN; the transceiver unit [202] of the system further to send, from the GMLC server [206], an IMSI query to a first Home Subscriber Server (HSS) [210]; to send, from the GMLC server [206], the IMSI query to a second HSS [212], if a negative response is received from the first HSS [210]; to send, from the GMLC server [206], a request for the one or more location parameters to a location-providing server [214] upon reception of the IMSI from the second HSS [212]; and to receive, at the GMLC server [206], the one or more location parameters from the location-providing server [214].
[0079] FIG. 4 illustrates a sequence flow diagram [400] for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server, in accordance with exemplary implementations of the present disclosure. As shown in FIG. 4, the sequence flow [400] comprises a LIM server [208], a GMLC server [206], a 4G HSS [402], a 5G HSS [404], a QNPDB server [406] and AMF server [216].
[0080] At step S1, LIM server [208] sends a location request with MSISDN information of the subscriber or UE or target UE to the GMLC server [206] by SMPP protocol.

[0081] At step S2, the GMLC server [206] initiates conversion of the received MSISDN to IMSI number of the subscriber or UE or target UE by communicating with network device or network functions, such as home subscriber server (HSS).
[0082] At step S3, the GMLC server [206] sends an IMSI Query for getting the IMSI information associated with the subscriber or UE or target UE to the 4G HSS [402].
[0083] At step S4, in response to the query, the 4G HSS [402] sends a negative response to the GMLC server [206] for not getting IMSI information of the requested subscriber or UE or target UE.
[0084] At step S5, after receiving a negative response from the 4G HSS [402], the GMLC server [206] sends or resends IMSI query to the 5G HSS [404] for getting the IMSI information associated with the subscriber or UE or target UE to the 4G HSS [402].
[0085] At step S6, the GMLC server [206] receives a successful response from the 5G HSS [404] with IMSI information of the requested subscriber or UE or target UE.
[0086] At step S7, after getting the successful response, the GMLC server [206] sends an authentication request to the AMF server [216] for checking or verifying the requested subscriber or UE or target UE.
[0087] At step S8, the GMLC server [206] receives an authentication response from the AMF server [216].

[0088] At step S9, after getting the successful response from the AMF server [216], the GMLC server [206] sends location parameters request, such as mobile country code (MCC) and mobile network code (MNC), to the QNPDB Server [406].
[0089] Thereafter, at step S10, the GMLC server receives location parameters (MCC and MNC) from the QNPDB Server [406].
[0090] As is evident from the above, the present disclosure provides a technically advanced solution for obtaining location parameters despite receiving negative response from 4G HSS. The present invention provides a solution that provides SMS based location flow by SMPP protocol, despite receiving negative response from 4G HSS, which was not possible in conventional implementations of the network.
[0091] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments 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 for obtaining one or more location parameters at a Gateway
Mobile Location Centre (GMLC) server [206], the method comprising:
- receiving, by a transceiver unit [202] at the GMLC server [206], a Mobile Subscriber Integrated Service Digital Network (MSISDN), from a Location Information Manager (LIM) server [208];
- initiating, by a processing unit [204] at the GMLC server [206], a conversion of the MSISDN to an International Mobile Subscriber Identity (IMSI) based on the received MSISDN;
- sending, by the transceiver unit [202] from the GMLC server [206], an IMSI query to a first Home Subscriber Server (HSS) [210];
- sending, by the transceiver unit [202] from the GMLC server [206], the IMSI query to a second HSS [212], if a negative response is received from the first HSS [210];
- sending, by the transceiver unit [202] from the GMLC server [206], a request for the one or more location parameters to a location-providing server [214] upon reception of the IMSI from the second HSS [212]; and
- receiving, by the transceiver unit [202] at the GMLC server [206], the one or more location parameters from the location-providing server [214].

2. The method as claimed in claim 1, wherein the MSISDN is received from the LIM server [208] using Short Message Peer-to-Peer (SMPP) protocol.
3. The method as claimed in claim 1, wherein the first HSS [210] comprises at least a 4G HSS.

4. The method as claimed in claim 1, wherein the second HSS [212] comprises at least a 5G HSS.
5. The method as claimed in claim 1, wherein the one or more location parameters comprise at least one of a mobile country code (MCC) and a mobile network code (MNC).
6. The method as claimed in claim 1, wherein sending the request for the one or more location parameters from the GMLC server [206] to the location-providing server [214] is performed after receiving an authentication from an access and mobility management function (AMF) server [216].
7. The method as claimed in claim 1, wherein the location providing server [214] is a Query Number Portability Database (QNPDB) server.
8. A system for obtaining one or more location parameters at a Gateway Mobile Location Centre (GMLC) server [206], the system comprising:

- a transceiver unit [202] configured to receive, at the GMLC server [206], a Mobile Subscriber Integrated Service Digital Network (MSISDN), from a Location Information Manager (LIM) server [208];
- a processing unit [204] connected to at least the transceiver unit [202], wherein the processing unit [204] is configured to initiate, at the GMLC server [206], a conversion of the MSISDN to an International Mobile Subscriber Identity (IMSI) based on the received MSISDN; and
- the transceiver unit [202] is further configured to:
o send, from the GMLC server [206], an IMSI query to a first Home Subscriber Server (HSS) [210];

o send, from the GMLC server [206], the IMSI query to a second HSS [212], if a negative response is received from the first HSS [210];
o send, from the GMLC server [206], a request for the one or more location parameters to a location-providing server [214] upon reception of the IMSI from the second HSS [212]; and
o receive, at the GMLC server [206], the one or more location parameters from the location-providing server [214].
9. The system as claimed in claim 8, wherein the MSISDN is received from the LIM server [208] using Short Message Peer-to-Peer (SMPP) protocol.
10. The system as claimed in claim 8, wherein the first HSS [210] comprises at least a 4G HSS.
11. The system as claimed in claim 8, wherein the second HSS [212] comprises at least a 5G HSS.
12. The system as claimed in claim 8, wherein the one or more location parameters comprise at least one of a mobile country code (MCC) and a mobile network code (MNC).
13. The system as claimed in claim 8, wherein the request for the one or more location parameters from the GMLC server [206] is sent to the location-providing server [214] after receiving an authentication from an access and mobility management function (AMF) server [216].
14. The system as claimed in claim 8, wherein the location-providing server [214] is a Query Number Portability Database (QNPDB) server.