FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
AND
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“A SYSTEM AND METHOD FOR FETCHING A LOCATION STATUS OF A
USER EQUIPMENT”
We, RELIANCE JIO INFOCOMM LIMITED, an Indian National, of, 3rd Floor, Maker Chamber- IV, 222, Nariman Point, Mumbai- 400021, Maharashtra, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

TECHNICAL FIELD:
The present disclosure generally relates to wireless communications and is more specifically, directed to system and method for fetching a location status of a user equipment.
BACKGROUND
An existing wireless network is typically deployed with multiple access networks to provide multiple communication services (e.g. video, data, advertisement, content, messaging, broadcast) by sharing available network resources with the users. One such network is an Evolved Universal Terrestrial Radio Access (E-UTRA) which is a Radio Access Network (RAN) standard and an entirely new air interface system that provides higher data rates, lower latency and is optimized for packet data unlike the High Speed Packet Access (HSPA) which is incompatible with the wireless code division multiple access (W-CDMA). In addition, the E-UTRA is considered as a replacement of Universal Mobile Telecommunications System (UMTS) and High Speed Downlink Packet Access/ High Speed Uplink Packet Access (HSDPA/HSUPA) technologies as covered under the 3GPP standards. The earlier UTRAN is the RAN that was defined as a part of the UMTS, a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP). The UMTS, a successor to Global System for Mobile Communications (GSM) technologies, currently supports various air interface standards, such as W-CDMA, Time Division-Code Division Multiple Access (TDCDMA), and Time Division-Synchronous Code Division Multiple Access (TDSCDMA). Also, the UMTS supports enhanced 3G data communications protocols, such as the HSPA, which provides higher data transfer speeds and capacity to associated UMTS networks. As the demand for mobile data and voice access increases, said technologies are upgrading for multiple advantages including, but not limiting to, meeting growing demand for access and enhanced user experience. In this regard, it is pertinent to note that

some of said technologies such as GSM/EDGE, UMTS/5 HSPA, CDMA2000/EV-DO and TD-SCDMA are evolved to provide a single evolution path for increased data speed and spectral efficiency as well as provision of more functionality. In the recent years, wireless device ecosystems have experienced an immense proliferation such that said ecosystems provide both voice and data services simultaneously and are therefore, becoming popular particularly in the countries where there are a plurality of service providers. Thus, this enables the users to implement different service plans or service providers on the devices and avail services based on the location of the user, thereby providing multiple options in different pricing plans for data and voice services in national as well as international locations. As a result, an Original Equipment Manufacturer (OEM) company started exploring options in the User Equipment (UE) with both voice and data and also with multi-SIM ecosystem with two antennas on receiver (Rx) path providing a precise location based out of the client application at the device/user equipment.
Further, a typical SIM card consists of a microprocessor, an I/O interface towards the UE, a memory (RAM, EEPROM / Non Volatile Memory (NVM)) and its file system. The EEPROM consists of an operating system code as well as codes of other applications. Also, the code of Auto IMSI Switch SIM application resides in the SIM. In the SIM file system, the USIM application contains the EF files (such as EFLOCI, EFPSLOCI, EFEPSLOCI, EFUST, EFFPLMN, etc.) along with application specific files and configuration files of the Auto IMSI Switch SIM application. A typical SIM card ecosystem comprises an integrated circuit chip for securely storing an International Mobile Subscriber Identity (IMSI) number and a related key which are used to identify and authenticate subscribers/users on the user equipments, GSM smartphones, CDMA smartphones and new LTE-capable handsets. The SIM card contains its unique serial number (ICCID), international mobile subscriber identity (IMSI) number, security authentication and ciphering information, temporary information related to the local network, a list of the

services the user has access to, and passwords such as a personal identification number (PIN) for ordinary use, a personal unblocking code (PUK) for PIN unlocking, etc. The SIM card is designed to be transferable between different mobile devices and is also a part of a function of a Universal Integrated Circuit Card (UICC) physical smart card which is usually made of PVC with embedded contacts and semiconductors. The UICC smart card has multiple applications such as SIM (2G), USIM (3G/4G), ISIM (IMS), etc., wherein the UICC can be simply referred to as ‘SIM’ card herein. After SIM activation on UE boot up, the UE selects the applications in the SIM, for example, USIM for 4G LTE. The SIM file system consists of a Master File (MF), a Dedicated File (DF) and an Elementary File (EF). The MF is a unique mandatory file containing access conditions and other DF and EF, wherein the DF contains access conditions and EF contains the access conditions of data contained.
A typical USIM application has many EFs and/or DFs for controlling UE’s behavior in the network, securely registering the UE to a desired network, and enabling and restricting certain services while maintaining status lists and parameters. Each network operator has a unique Public Land Mobile Network (PLMN) number that consists of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). Every subscriber of service provider operator is identified by a unique International Mobile Subscriber Identity (IMSI) which consists of the PLMN (MCC,MNC) of the service provider operator and the Mobile Subscription Identification Number (MSIN). The PLMN contained in the subscriber’s IMSI is called Home PLMN (HPLMN) and the corresponding network is referred to as Home Network (HN). When a subscriber of an operator tries to attach to another network operator due to various reasons like unavailability of home network, etc. it is identified as a Roaming Subscriber (RS) and that network operator is referred to as Roamed Network (RN). Therefore, it is essential to provide good quality location service as well as maintain a location based service. When a user connects to a network, the network entities identifies the IMSI and IMEI along

with the cellular location of the user, wherein said location information is also available to the user equipment. There are various conventional applications (resided in the user equipment) that enable voice, video and messaging services in the devices that do not support native VoLTE calling. While said applications are compatible for android users, the applications have not been launched for iOS users, since the iOS prohibits such applications from fetching location from the device. In particular, said applications might not be able to perform the function of fetching the location due to various issues/reasons inter alia incompatibility with certain mobile platforms such as iPhone OS (iOS) that hinder said application from fetching the cellular location due to security aspects. Other issues lies in the inability of said application to host the SIM. Thus, said factors not only hinder said applications to fetch/discover the user location (conveyed by the user equipment) but also prohibits development of said applications over such environments. In the context of an IP Multimedia Subsystem (IMS), user’s location is conveyed over SIP header P-Access-Network-Info while making/ receiving calls. As per the regulation, it should be possible to track the location of the user while making/ receiving calls. In one of the conventional techniques, the user equipment learns the cellular location information by querying the network elements and uses the same during service realization, however, the user equipment is unable to track the change in the cellular location due to absence of additional intelligence that helps in notifying the user equipment whenever location changes.
Accordingly, in order to overcome the aforementioned problems inherent in the existing solutions for fetching user’s location, there exists a need of an efficient mechanism to fetch the user’s location status in a seamless manner irrespective of the platforms embedded in the user equipment.

SUMMARY
This section is provided to introduce certain objects and 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.
Embodiments of the present disclosure may relate to a method for fetching a location status of a user equipment, wherein the user equipment has a restrictive location sharing capability. The method comprises transmitting, by the user equipment, a location request to a location update server (LUS), wherein the user equipment has at least one subscriber identity module (SIM), and the location request comprises at least one of an international mobile subscriber identity (IMSI) and an international mobile equipment identity (IMEI) corresponding to each of the at least one SIM; fetching, by the LUS, the location status of the user equipment from an evolved packet core (EPC) network, wherein the LUS stores the location status against each of at least one of the IMSI and the IMEI; and fetching, by the user equipment, the location status from the LUS, wherein the location status comprises a current location of the user equipment.
Further, the embodiments of the present disclosure encompass a system for discovering a location status of a user equipment, wherein the user equipment has a restrictive location sharing capability. The system comprises the user equipment configured to transmit a location request to a location update server (LUS), wherein the user equipment has at least one subscriber identity module (SIM), and the location request comprises at least one of an international mobile subscriber identity (IMSI) and an international mobile equipment identity (IMEI) corresponding to each of the at least one SIM; and the LUS configured to fetch the location status of the user equipment from an evolved packet core (EPC) network, and wherein the LUS stores the location status against each of the at

least one IMSI, and wherein the user equipment is further configured to fetch the location status from the LUS, wherein the location status comprises a current location of the user equipment.
BRIEF DESCRIPTION OF THE DRAWINGS
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 or circuitry commonly used to implement such components.
FIG.1 illustrates an exemplary system architecture [100] for fetching a location status of a user equipment [110] in accordance with an embodiment of the present disclosure.
FIG. 2 illustrates an exemplary Location Update Server (LUS) [114] for fetching a location status of a user equipment [110] in accordance with an embodiment of the present disclosure.
FIG. 3 and FIG. 4 illustrate a high level architecture for implementation of the Location Update Server (LUS) [114] in a network.
FIG.5 illustrates an exemplary method flow diagram [500] comprising the method for fetching a location status of a user equipment [110] in accordance with an embodiment of the present disclosure.

FIG.6 illustrates an exemplary signaling flow diagram [600] for fetching a location status of a user equipment [110] in accordance with an embodiment of the present disclosure.
DETAILED DESCRIPTION
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 one 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.
Embodiments of the present disclosure may relate to a mechanism for fetching a location status of a user equipment (UE) having a restrictive location sharing capability. The user equipment has said restrictive location sharing capability in two scenarios, firstly when the user equipment is incapable of using and transmitting the current location directly fetched from an Evolved Packet Core (EPC) network, and secondly, when the user equipment is itself capable of using and transmitting the current location fetched from the EPC network via a new server element named location update server (LUS). In said two scenarios, the user equipment, having at least one SIM, establishes a bidirectional web-socket connection with the LUS to transmit the location request, wherein the location request comprises at least one of an international mobile subscriber identity (IMSI) and an international mobile equipment identity (IMEI) corresponding to

each of the at least one SIM. On receiving said location request from the user equipment, the LUS fetches the location status of the user equipment from the EPC network. Said location status comprises a current location against each of at least one of the IMSI and the IMEI. Thereafter, the LUS notifies/updates the updated location to the user equipment. The user equipment further transmits the location status (current location) to an IMS network to avail at least one service.
The user equipment as used herein may refer to any computing device operable with at least one subscriber identity module (SIM), wherein each of the at least one SIM comprises the IMSI, the IMEI, a unique key shared with the network operator. Further, the user equipment includes, but not limited to, a smart phone, a mobile phone, a tablet, a phablet and any such device as obvious to a person skilled in the art. Furthermore, the user equipment may comprise an input means such as a keyboard, an operating system, a memory unit, a display interface, etc. which may be configured to function/communicate with base station or any such network equipment with the help of the at least one SIM.
The bidirectional web-socket connection as used herein may refer to a bidirectional connection established between the user equipment and the LUS. In particular, the bidirectional web-socket connection may enable a full-duplex communication over a single Transmission Control Protocol (TCP) connection without any security issue of the internet/web.
The current location as used herein may refer to an instantaneous /real-time location of the user equipment. In particular, the current location may comprise a cellular location and a geographical location of the user equipment. Said cellular location may refer to a cell location and a corresponding sector information, while said geographical location may comprise latitude and longitude information.

The evolved packet core (EPC) as used herein may refer to a framework standardized in Release 8 of the 3GPP for providing converged voice and data on a 4G Long-Term Evolution (LTE) network. Also, the EPC may be considered as an essential component for end-to-end Internet Protocol service delivery across the LTE network.
The Location Update Server (LUS) may be referred to as a server element residing alongside a telephony server component behind the EPC network. The LUS may be responsible for interfacing with the user equipment and the EPC to discover/fetch the cellular location of the user equipment. LUS may be further configured to maintain said bidirectional web-socket connection.
The at least one service as used herein may include, but not limited to, a voice call, a video call, a short message service, an instant message service, a group message service, a file transfer service and an enriched calling service.
FIG.1 illustrates a system architecture [100] for fetching a location status of a user equipment in accordance with an embodiment of the present disclosure. The system [100] may comprise a user equipment [110] and a network entity [120], wherein the user equipment [110] and the network entity [120] may be connected to each other through a wireless medium. More particularly and as illustrated in FIG. 1 and FIG. 2, the user equipment [110], having at least one SIM, may comprise an Over-the-top (OTT) application [102], a location manager [104] and a platform [106] on which it is operating. The network entity [120] may comprise an IMS [112], a Location Update Server (LUS) [114] and an Evolved Packet Core (EPC) [116]. Said LUS [114] may comprise a client manager [202], a server manager [204], a session manager [206], a connection manager [208], a subscription manager [210], an authentication manager [212] and a user database [214]. The user equipment [110], the network entity [120] and the sub-components therein may be configured to work in conjunction and provide respective functionalities in order to achieve the objective of the present

disclosure. Also, the respective subcomponents of the LUS [114], the network entity [120] and the user equipment [110] may be internally connected to each other for facilitating internal communication in accordance with the present disclosure.
The location manager [104] of the user equipment [110] may be configured to establish a bidirectional web-socket connection with the LUS [114] in an event the user equipment [110] is unable to fetch the location i.e. the user equipment [110] may be incapable of using and transmitting the location that is being directly fetched (via the platform [106]) from the EPC network [116] and in fact may be capable of using and transmitting the location fetched from the EPC network [116] via the LUS [114]. The connection manager [208] of the LUS [114] may be configured to maintain said bidirectional web-socket connection between the user equipment [110] and the LUS [114]. Also, in an event the web-socket connection is detached/broken, the connection manager [208] may be configured to notify at least one of the user equipment [110] and the server manager [204] about said detached connection. Further, pursuant to a successful bidirectional web-socket connection between the user equipment [110] and the LUS [114], the location manager [104] may be configured to transmit a location request to the client manager [202] of the LUS [114], wherein said location request may comprise at least one of the international mobile subscriber identity (IMSI) and the international mobile equipment identity (IMEI) corresponding to each of the at least one SIM of the user equipment [110].
Further, the session manager [206] may be configured to manage a session from the particular user equipment [110], wherein said session may start with the establishment of the bidirectional web-socket connection. In an embodiment, the session manager [206] may be configured to run a timer for every location request received from the user equipment [110] and may be further configured to close said session in an event the session is timed out and simultaneously notify the user equipment [110] about the processing error relating to timed out

session. In another embodiment, the session manager [206] may be configured to convert the format of the location status fetched by the server manager [204] to a user compatible format.
The authentication module [212] of the LUS [114] may be configured to verify if the location request is authentic. In addition, the authentication module [212] may be configured to check if the IMSI and the IMEI contained in each location request are same as the IMSI and the IMEI used while establishing the bidirectional web-socket connection between the user equipment [110] and the LUS [114]. In an event of the authentic location request, the server manager [204] of the LUS [114] may be configured to interact with the EPC [116] pursuant to an internal communication between the client manager [202], the authentication manager [212] and the server manager [204]. Thereafter, the server manager [204] may be configured to fetch the location status of the user equipment [110] from the EPC network [116]. The location status may comprise the current location of the user equipment [110], wherein said current location may comprise the cellular location and the geographical location of the user equipment [110]. In an embodiment, the server manager [204] may be configured to fetch the location status of the user equipment [110] by transmitting a location delivery request to the EPC [116], wherein the location delivery request comprises said IMSI and said IMEI, and the location delivery request is transmitted using a Mobile Location Protocol (MLP). In another embodiment, the server manager [204] of the LUS [114] may be configured to ensure that multiple said location delivery requests including the same IMSI are avoided even if the user equipment [110] transmits multiple location requests comprising the same IMSI for requesting the location status. Also, the server manager [204] may be configured to put said multiple location requests in a waiting queue until the complete processing of the first location request. In an embodiment, the server manager [204] may be configured to fetch the location status of the user equipment [110] based on a preference request received from

the user equipment [110], wherein the preference request may indicate a preference of the user equipment [110] i.e. to fetch the location status of the user equipment [110] in a periodic manner or a real time manner. Thus, the server manager [204] may be configured to update the user equipment [110] about the location status based on the preference of user equipment [110]. The user database [214] of the LUS [114] may be configured to store the location status against each of at least one of the IMSI and the IMEI of each user equipment [110]. In an embodiment, the user database [214] may store the location status in the form of a table such that each of the cellular location is stored against the corresponding geographical information. In an embodiment, the user database [214] of the LUS [114] may be configured to update said table (comprising the cellular location and the geographical location) against each user equipment [110] as soon as the server manager [204] fetches the updated current location.
On fetching the location status from the EPC network [116], the server manager [204] may be configured to notify/update the change in the current location of the user equipment [110] to the location manager [104]. The location manager [104] may be further configured to notify/update the current location of the user equipment [110] to the OTT application [102]. The OTT application [102] may be then configured to transmit the current location to the IMS network [112] in order to avail the at least one service, wherein the IMS network [112] may be configured to use/utilise the cellular location to enable the user equipment [110] to avail the at least one service. Said at least one service may include, but not limited to, a voice call, a video call, a short message service, an instant message service, a group message service, a file transfer service and an enriched calling service.
The subscription manager [210] of the LUS [114] may be configured to manage normal and fast subscription per user of the user equipment [110]. In an embodiment, the subscription manager [210] may be configured to set a timer

during which the subscription manager [210] may be configured to compare the current location with previous stored location. In an embodiment, the timer may be set based on a frequency. In an embodiment of change in the location of the user equipment [110], the subscription manager [210] may be configured to update the user database [214]. The subscription manager [210] may be configured to notify the user equipment [110] about said updation in the location.
FIG. 3 and FIG. 4 illustrate a high level architecture for implementation of the Location Update Server (LUS) [114] in the network, wherein the network may comprise the user equipment [110], the IMS network [112], the EPC [116], LUS [114] and any such component as may be obvious to person skilled in the art. As illustrated, the user equipment [110] may create the web-socket connection with the LUS [114] to enquire about the current location of the user equipment [110]. Thereafter, the LUS [114] may create the Mobile Location Protocol (MLP) request and transmit said MLP request to a LCS server [408] of the EPC [116]. The LCS server [408] may then transmit a query (for the location) to a Home Subscriber Server (HSS) [406] over a Sh interface (UDR). The HSS [406] may further forward said query to a Mobile Management Entity (MME) [402] over a S6a interface (IDR). On receiving the query, the MME [402] may be configured to return a cell-id detail to the HSS [406] over the S6a interface (IDA) which may be further forwarded to the LCS server [408] by the HSS [406] over Sh interface (UDA). Pursuant to receiving said cell-id detail, the LCS server [408] may transmit the cell-id detail to the LUS [114] which may be then updated to the user equipment [110]. The user equipment [110] may then finally use said cell-id details to prepare a PANI header and transmit the same to a P-CSCF module [404], wherein the P-CSCF module [404A] may be internally connected to S-CSCF module [404B] in the IMS network [112].
FIG. 5 illustrates an exemplary method flow diagram [500] comprising the method for fetching the location status of the user equipment [110] in

accordance with an embodiment of the present disclosure. The method [500] may initiate at step 502 where the user equipment [110] may have the restrictive location sharing capability i.e. the user equipment [110] may be incapable of using and transmitting the location that is being directly fetched from the EPC network [116] and in fact may be capable of using and transmitting the location fetched from the EPC network [116] via the LUS [114].
At step 504, in an event the user equipment [110] is unable to fetch the location from the EPC [116] directly or indirectly, the location manager [104] may establish the bidirectional web-socket connection with the LUS [114], while the connection manager [208] of the LUS [114] may maintain said bidirectional web-socket connection. Also, in an event said web-socket connection is detached/broken, the connection manager [208] may notify at least one of the user equipment [110] and the server manager [204] about said detached connection.
At step 506, the location manager [104] may transmit the location request to the client manager [202] of the LUS [114], wherein said location request may comprise at least one of the IMSI and the IMEI corresponding to each of the at least one SIM of the user equipment [110]. In addition, the session manager [206] may be configured to manage the session from the particular user equipment [110], wherein said session may start with the establishment of the bidirectional web-socket connection. In an embodiment, the session manager [206] may run a timer for every location request received and may further close said session in an event the session is timed out. Said session manager [206] may then notify the user equipment [110] about the processing error relating to the timed out session.
At step 508, the authentication module [212] of the LUS [114] may check whether the IMSI and the IMEI contained in the location request are same as the IMSI and IMEI used while establishing of the bidirectional web-socket connection

between the user equipment [110] and the LUS [114]. In an event, the IMSI and IMEI contained in the location request are similar to the IMSI and IMEI used in the connection, the method [500] may lead to step 510. Alternatively, the method [500] may terminate at step 518.
At step 510, the server manager [204] may fetch the location status of the user equipment [110] from the EPC network [116]. Said location status may comprise a current location of the user equipment [110], wherein said current location may comprise the cellular location and the geographical location of the user equipment [110]. In an embodiment, the server manager [204] may fetch the location status based on the preference request received from the user equipment [110] i.e. fetch the location status of the user equipment [110] in one the periodic manner and the real time manner. The user database [214] of the LUS [114] may store as well as update the location status against each of at least one of the IMSI and the IMEI of each user equipment [110].
At step 512 and pursuant to accomplishment of step 510 relating to the fetching of the location status from the EPC network [116], the server manager [204] may notify/update the change in the current location of the user equipment [110] to the location manager [104] of the user equipment [110]. The location manager [104] may further notify/update the location status (current location) of the user equipment [110] to the OTT application [102].
At step 514, the OTT application [102] of the user equipment [110] may transmit the location status (i.e. current location) to the IMS network [112] in order to avail the at least one service. In an event, the IMS network [112] enables the user equipment [110] to avail the at least one service on the basis of the current location received from the user equipment [110], the method [500] may lead to step 516. Alternatively, the method [500] may terminate at step 518.
At step 516, the user equipment [110] may avail the at least one service, wherein said at least one service may include, but not limited to, a voice call, a video call,

a short message service, an instant message service, a group message service, a file transfer service and an enriched calling service. The method [500] may then terminate at step 518.
FIG.6 illustrates an exemplary embodiment of the present disclosure that encompasses a method [600] flow signalling diagram for fetching the location status of the user equipment [110], wherein the user equipment [110] has the restrictive location sharing capability.
At step 602, the location manager [104] of the user equipment [110] may establish the bidirectional web-socket connection with the LUS [114], while the LUS [114] may maintain said connection.
At step 604, the location manager [104] of the user equipment [110] may transmit the location request to the client manager [202] of the LUS [114] for requesting the location of the user equipment [110].
At step 606, the authentication module [212] of the LUS [114] may check whether the IMSI and the IMEI contained in the location request are same as the IMSI and IMEI used while establishing of the bidirectional web-socket connection between the user equipment [110] and the LUS [114].
At step 608, the server manager [204] of the LUS [114] may fetch the location status of the user equipment [110] from the EPC network [116]. Said location status may comprise the current location of the user equipment [110], wherein said current location may comprise the cellular location and the geographical location of the user equipment [110].
At step 610, the EPC network [116] may provide the location status of the user equipment [110] to the LUS [114].
At step 612, the user database [214] of the LUS [114] may store the location status against each of at least one of the IMSI and the IMEI of each user equipment [110].

At step 614, the session manager [204] may notify/update a change in the location to the location manager [104] of the user equipment [110], pursuant to which the location manager [104] may notify the change in the current location to the OTT application [102].
At step 616, the user equipment [110] may subscribe to the subscription manager [210] of the LUS [114] for periodic updation in the change in the location status.
At step 618, the session manager [206] may fetch the periodic location status from the EPC [116] for the update in the location status.
At step 620, the EPC [116] may provide the LUS [114] with the updated location status.
At step 622, the LUS notifies the updated location status to the user equipment [110].
Therefore, the present disclosure encompasses a mechanism for fetching the location status of the user equipment [110], wherein the user equipment [110] is unable to fetch the location from EPC [116] directly or indirectly. The present disclosure further encompasses a server element called LUS [114] that is configured to fetch the location from the EPC [116], thereby enabling the equipment [110] to further fetch the location from the LUS [114]. Thus, the present disclosure encompasses secured mechanism for fetching the user equipment’s location.
Though a limited number of the user equipment [110], the network entity [120], the LUS [114], the EPC [116] and other components/sub systems therein, have been shown in the figures; however, it will be appreciated by those skilled in the art that the system [100] of the present disclosure encompasses any number and varied types of said entities/elements/sub systems.

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 [500] for fetching a location status of a user equipment [110],
wherein the user equipment [110] has a restrictive location sharing
capability, the method [500] comprising:
- transmitting, by the user equipment [110], a location request to a
location update server (LUS) [114], wherein
the user equipment [110] has at least one subscriber identity module (SIM), and
the location request comprises at least one of an international mobile subscriber identity (IMSI) and an international mobile equipment identity (IMEI) corresponding to each of the at least one SIM;
- fetching, by the LUS [114], the location status of the user equipment from an evolved packet core (EPC) network [116], wherein the LUS [114] stores the location status against each of at least one of the IMSI and the IMEI; and
- fetching, by the user equipment [110], the location status from the LUS [114], wherein the location status comprises a current location of the user equipment [110].

2. The method [500] as claimed in claim 1, further comprising establishing, by the user equipment [110], a bidirectional web-socket connection with the LUS [114] to transmit the location request to the LUS [114].
3. The method [500] as claimed in claim 2, wherein the bidirectional web-socket connection is maintained by the LUS [114].
4. The method [500] as claimed in claim 1, further comprising transmitting, by the user equipment [110], the current location to an IMS network [112] to avail at least one service.

5. The method [500] as claimed in claim 4, wherein the at least one service comprises at least one of a voice call, a video call, a short message service, an instant message service, a group message service, a file transfer service and an enriched calling service.
6. The method [500] as claimed in claim 1, wherein the restrictive location sharing capability corresponds to an event the user equipment [110] is incapable of using and transmitting the current location directly fetched from the EPC network [116].
7. The method [500] as claimed in claim 1, wherein the restrictive location sharing capability corresponds to the event the user equipment [110] is capable of using and transmitting the current location fetched from the EPC network [116] via the LUS [114].
8. The method [500] as claimed in claim 1, wherein the location status is fetched by the LUS [114] from the EPC network [116] based on a preference request received, by the LUS [114], from the user equipment [110].
9. The method [500] as claimed in claim 8, wherein the preference request indicates a preference of the user equipment [110] to fetch the location status in one of a periodic manner and a real time manner.
10. The method [500] as claimed in claim 1, wherein the current location comprises a cellular location and a geographical location of the user equipment [110].
11. The method [500] as claimed in claim 1, wherein the LUS [114] resides alongside a telephony server component behind the EPC network [116].
12. A system [100] for discovering a location status of a user equipment [110], wherein the user equipment [110] has a restrictive location sharing capability, the system [100] comprising:

- the user equipment [110] configured to transmit a location
request to a location update server (LUS) [114], wherein
the user equipment [110] has at least one subscriber identity module (SIM), and
the location request comprises at least one of an international mobile subscriber identity (IMSI) and an international mobile equipment identity (IMEI) corresponding to each of the at least one SIM; and
- the LUS [114] configured to:
fetch the location status of the user equipment [110] from an evolved packet core (EPC) network [116], wherein the LUS [114] stores the location status against each of the at least one IMSI, and
wherein the user equipment [110] is further configured to fetch the location status from the LUS [114], wherein the location status comprises a current location of the user equipment [110].
13. The system [100] as claimed in claim 12, wherein the user equipment [110] is further configured to establish a bidirectional web-socket connection with the LUS [114] to transmit the location request to the LUS [114].
14. The system [100] as claimed in claim 13, wherein the LUS [114] is further configured to maintain the bidirectional web-socket connection.
15. The system [100] as claimed in claim 12, wherein the user equipment [110] is further configured to transmit the current location to an IMS network [112] to avail at least one service.
16. The system [100] as claimed in claim 15, wherein the at least one service comprises at least one of a voice call, a video call, a short message

service, an instant message service, a group message service, a file transfer service and an enriched calling service.