Systems and methods for providing location based services

An subscriber location device for determining location information for User Equipment (UE) in a communication network monitors a network interface between a Mobility Management Entity node and an Evolved Serving Mobile Location Center (E-SMLC) node, receive location information from network interface between the MME node and the E-SMLC node, associates the received location information with corresponding UE to yield associated location information and stores the associated location information in a subscriber location database, indexed according to the UE.

BACKGROUND

1. Field of the Invention

The present disclosure relates generally to communication networks, and more specifically to techniques for improving location services.

2. Description of the Related Art

Long Term Evolution (LTE) networks generally use 4th generation (4G) wireless technologies and are considered a next evolution for GSM (Global System for Mobile Communications). LTE builds on the 3GPP family including GSM, GPRS (General packet radio service), EDGE (Enhanced Data rates for GSM Evolution), etc., and is an all-IP standard. LTE provides higher data transmission rates while efficiently utilizing the spectrum thereby supporting a multitude of subscribers than is possible with pre-4G spectral frequencies. LTE is all-IP permitting applications such as real time voice, video, gaming, social networking and location-based services. LTE networks may also co-operate with circuit-switched legacy networks and result in a seamless network environment and signals may be exchanged between traditional networks, the new 4G network and the Internet seamlessly.

LTE network also support location services and positioning. Positioning refers to a functionality that determines a geographical location of a target UE. Location services refer to any services based on or related to location information, which may include any information related to the location of a UE, e.g., measurements, a location estimate, etc. Often, it is desirable to find the location of a mobile, wireless or wired device for various reasons such as improved network performance, part of many services, emergency situations, and the like.

With respect to determining location of the UE in LTE networks, conventional LoCation Services (LCS) clients query locations for UE and communicate with, for example, Gateway Mobile Location Center(s) (GMLCs) in order to request the location of the UE. The GMLCs communicate with one or more additional nodes, which communicate with the UE, as necessary, to obtain a location estimate for the UE. The GMLC then returns the location estimate to the LCS client.

Although obtaining location via conventional LCS client requests/responses have generally been considered satisfactory for their intended purpose, there is still a need in the art for improved location services that, for example, maintain one or more subscriber location databases for UE.

SUMMARY

According to one or more embodiments of the invention, a network monitoring system extracts geographical location information associated with User Equipment (UE). The extracted location information is stored in a Subscriber Location Database (SLD), which can subsequently be queried by various network applications that need location based services (e.g., via a SLD Application Programming Interface (API)). The location information is obtained by monitoring a SLs network interface between a Mobility Management Entity (MME) node and an Evolved Serving Mobile Location Centre (E-SMLC) node. Location information includes, but is not limited to geographical coordinates (e.g., altitude, horizontal speed, vertical velocity, etc.). The network monitoring system provides the location of particular UE when, for example, it is queried by applications. Optionally, the networking monitoring system can transmit a LCS client request to a Gateway Mobile Location Center (GMLC) node thereby triggering a location information procedure from the UE, discussed in greater detail below.

According to another embodiment of the invention, a subscriber location node/device determines location information for User Equipment (UE) in a communication network using improved subscriber location techniques. For example, the subscriber location device monitors a network interface between a Mobility Management Entity node and an Evolved Serving Mobile Location Center (E-SMLC) node and receives location information (e.g., altitude, a horizontal speed and a vertical velocity, etc.) from network interface between the MME node and the E-SMLC node (e.g., an SLs network interface, etc.). The subscriber location device further associates the received location information with corresponding UE to yield associated location information, and stores the associated location information in a subscriber location database, indexed according to the UE.

In certain other embodiments, the subscriber location device also receives a request for the associated location information for the UE from an application and retrieves (e.g., in response to the request) the associated location information stored in the subscriber location database. The subscriber location database further provides the associated location information to the application in response to the received request. Additionally, in these embodiments, the subscriber location device determines the associated location information stored in the subscriber location database needs to be updated, using, for example, trigger criteria that includes a geographical position of the UE, a time, and a detected handover of the UE in the communication network, a geographical position of the UE relative to an emergency situation, a geographical position of the UE relative to retail facility, etc. Once determined, the subscriber location device triggers an update for the associated location information stored in the subscriber location database that causes a location services client to send a location services request to a Gateway Mobile Location Centre (GMLC) node. In turn, the GMLC node causes, via the MME node, the UE to send location information across the network interface between the MME node and the E-SMLC node.

These and other features of the systems and methods of the subject invention will become more readily apparent to those skilled in the art from the following detailed description of the preferred embodiments taken in conjunction with the drawings.

A component or a feature that is common to more than one drawing is indicated with the same reference number in each of the drawings.

DESCRIPTION OF EXAMPLE EMBODIMENTS

This disclosure provides network monitoring systems and techniques employed in communication networks such as cellular 4G/LTE communication networks. As discussed in greater detail herein, these network monitoring systems and techniques provide, for example, comprehensive location based services including, storing location information for associated User Equipment (UE), querying UE for updated location information, providing event based triggers (e.g., cellular network changes, handovers, time-based events, geo-fencing, etc.) that update UE location information, maintaining precise historical and current location information for UE, and the like.

For purposes of explanation and illustration, and not limitation, component network nodes that support location services for a communication network100(e.g., a 3GPP network) are shown inFIG. 1. Communication network100is a geographically distributed collection of nodes interconnected by communication links and segments for transporting data between end nodes, such as User Equipment (UE) or other devices.

As shown, User Equipment (UE)110communicates with an Evolved Node B (eNB)120in a radio access network (RAN) to obtain communication services. The RAN may include other network entities not shown inFIG. 1for simplicity and may also be referred to as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). eNB120is also referred to as a Node B, a base station, an access point, etc. UE110is also referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, etc. and includes, for example, mobile devices, cellular phones, laptops, wireless devices, wireless modems, wireless routers, and the like.

With respect to location information, UE110receives and measures signals from one or more satellites190and obtains pseudo-range measurements for the satellites. Satellite190is, for example, a Global Navigation Satellite System (GNSS) satellite, which uses the United States Global Positioning System (GPS), the European Galileo system, the Russian GLONASS system, or some other GNSS. UE110can also measure signals from eNBs and obtain timing measurements (e.g., for time of arrival (TOA) or observed time difference of arrival (OTDOA)), signal strength measurements, and/or signal quality measurements for the eNBs. The pseudo-range measurements, timing measurements, signal strength measurements, and/or signal quality measurements are used to derive a location estimate (e.g., a position estimate, a position fix, etc.) for UE110.

The eNB120also communicates with a Mobility Management Entity (MME) node130, which performs various control functions such as mobility management, gateway selection, authentication, bearer management, etc. MME node130communicates with an evolved Serving Mobile Location Center (E-SMLC)140node, a Home Subscriber Server (HSS) node150, and a Gateway Mobile Location Center (GMLC) node160. Notably, the E-SMLC node140supports UE-based, UE-assisted, network-based and/or network-assisted positioning methods. The E-SMLC node140also communicates with GMLC node160to support location services.

The GMLC node160performs various functions to support location services, interface with external LCS clients (e.g., an LCS client170), and provide services such as subscriber privacy, authorization, authentication, billing, etc. In certain configurations, the GMLC node160includes a Home GMLC node (H-GMLC), a Visited GMLC node (V-GMLC), and/or a Requesting GMLC node (R-GMLC) (not shown). HSS node150stores subscription information for users, performs authentication and authorization of users, and provides information about user location and routing information when requested.

A Serving Gateway (S-GW) node180performs various functions related to IP data transfer for UE(s) such as data routing and forwarding, mobility anchoring, etc. A Packet Data Network (PDN) Gateway node185performs various functions such as maintenance of data connectivity for UEs, IP address allocation, etc. and facilitates connection to a data network185(i.e., the Internet).

FIG. 1also shows various network interfaces between various network nodes or entities including, but not limited to: an SLs network interface between MME130and E-SMLC140; an SLg network interface between MME130and GMLC160; and an SLh network interface between HSS150and GMLC160.

The SLs network interface is used to convey location requests from the MME130node to the E-SMLC node140and to convey corresponding location reports back from the E-SMLC node140to the MME node130. The SLs interface is also used for tunneling core network measurement requests from the E-SMLC node140to the RAN/eNB120, using RAN specified protocols transparent to the MME (described in 3GPP TS 36.305). The SLh network interface is the Diameter based interface between the HSS and the GMLC as described in 3GPP TS 29.173. For example the SLh network interface enables HSS node150to provide the MME address, the VPLMN identity, and/or other information to GMLC node160. The SLg interface enables an H-GMLC to provide the MME address to a V-GMLC when the location of a particular UE is being requested by the H-GMLC.

Notably, whileFIG. 1shows a specific design of an LTE network architecture, (i.e., with E-SMLC140being connected to MME130, with E-SMLC140in communication with eNB120, etc.)). However, other network architectures may also be used to support location services and positioning and may include network entities that may be coupled in other manners. These various network architectures may also include network entities not shown inFIG. 1.

FIG. 2is a schematic block diagram of an example node/device200that may be used with one or more embodiments described herein, e.g., as a one of the gateway nodes/devices shown inFIG. 1or as a subscriber location device/node (discussed with respect toFIG. 4, below). The device200comprises one or more network interfaces210, at least one processor220, and a memory240interconnected by a system bus250.

The network interface(s)210contain the mechanical, electrical, and signaling circuitry for communicating data over physical and/or wireless links coupled to the network100. The network interfaces may be configured to transmit and/or receive data using a variety of different communication protocols, including, inter alia, TCP/IP, UDP, wireless protocols (e.g., IEEE Std. 802.15.4, WiFi, Bluetooth®,), Ethernet, powerline communication (PLC) protocols, etc.

The memory240comprises a plurality of storage locations that are addressable by the processor220and the network interfaces210for storing software programs and data structures (e.g., subscriber information, etc.) associated with the embodiments described herein. As noted above, certain devices may have limited memory or no memory (e.g., no memory for storage other than for programs/processes operating on the device). The processor220may comprise necessary elements or logic adapted to execute the software programs and manipulate data structures245, such as addresses, routes or prefixes (notably on capable devices only). An operating system242, portions of which are typically resident in memory240and executed by the processor, functionally organizes the device by, inter alia, invoking operations in support of software processes and/or services executing on the device. These software processes and/or services include subscriber location process/services244. It will be apparent to those skilled in the art that other processor and memory types, including various computer-readable media, may be used to store and execute program instructions pertaining to the techniques described herein. Also, while the description illustrates various processes, it is expressly contemplated that various processes may be embodied as modules configured to operate in accordance with the techniques herein (e.g., according to the functionality of a similar process).

Illustratively, the techniques described herein may be performed by hardware, software, and/or firmware, such as in accordance with the subscriber location244, which may contain computer executable instructions executed by the processor220(or independent processor of network interfaces210) to perform functions relating to the techniques described herein.

Referring now toFIG. 3, a signaling diagram300illustrates various call flows or messages that support location services and positioning. Each call flow may include a sequence of messages exchanged between various network node entities. As discussed above, different network architectures may support communication between different network entities. However, for clarity, the description below is for the network architecture shown inFIG. 1, with E-SMLC140being able to communicate directly with MME140but not eNB120or GMLC160.

FIG. 3shows a signaling diagram300for a Mobile Terminated Location Request (MT-LR) procedure (e.g., in packet-switched (PS) and circuit-switched (CS) domain) for the first network architecture shown inFIG. 1, as described in 3GPP TS 23.271, incorporated by reference herein in its entirety. The location request procedure, as illustrated in signaling diagram300, is in response to an LCS client request (step301) from LCS client170. LCS client170sends a service request to GMLC node160, which then performs a common MT-LR procedure described in 3GPP TS 23.271, which (briefly) includes resolving routing information between the GMLC node160and the HSS node150. Once resolved, GMLC node160sends a Provide Subscriber Location (PSL) message, at step302to MME node130(which MME node was indicated by HSS150during step301). The PSL message includes, for example, the type of location information being requested (e.g., current location, velocity, etc.), an International Mobile Subscriber Identity (IMSI) of the UE subscriber, LCS quality-of-service (QoS) information (e.g., accuracy, response time, etc.), privacy related action for the UE subscriber, etc.

In response, MME node130, eNB/RAN120and UE110perform network triggered service requests (step303), notification and privacy verifications (step304), etc. For example, if UE110is in an idle state, then MME node130may perform a network triggered service request procedure in order to establish a signaling connection for UE110and to assign a specific eNB (e.g., eNB120) to UE110(step303). If the PSL message indicates that UE110should either be notified or be notified with privacy verification (step304), then MME130may notify UE110of the location request and may verify its privacy preference. Step304may also include sending a Location Notification Invoke message to UE110. UE110may wait for the user to grant or withhold permission and may then return a Location Notification Return Result message to MME130.

In step305, MME node130selects E-SMLC node140and sends a Location Request message to E-SMLC140. The Location Request message includes the type of location information being requested, the requested LCS QoS, the identity of the serving eNB, the UE positioning capabilities, etc. If the requested location information and location accuracy within the LCS QoS can be satisfied based on parameters (e.g., eNB identity) received from MME node130, then E-SMLC node140send a Location Response message immediately (not shown inFIG. 3). Otherwise, E-SMLC140may determine one or more positioning methods to use and prompt a positioning procedure for the positioning method(s) (step306). E-SMLC node140may receive measurements from the positioning procedure and may determine a location estimate for UE110based on the measurements. If E-SMLC node140fails to receive measurements, then it may use the current eNB identity to obtain an approximate location estimate for UE110. E-SMLC node140also receives a location estimate from UE110, which may be obtained with a UE-based positioning method, and may verify consistency of this location estimate with the current eNB location. If the location estimate does not satisfy the requested accuracy and sufficient response time still remains, then E-SMLC node140may instigate another positioning procedure using the same or different positioning method. After completing the positioning procedure in step306, E-SMLC node140sends a Location Response message to MME130(step307). The Location Response message includes a location estimate for UE110obtained from the positioning procedure, an indication of whether the location estimate satisfies the requested accuracy, the positioning method used to obtain the location estimate, a failure cause if a location estimate could not be obtained, etc.

At step308, MME node130returns the requested location information to GMLC node160. MME130may return an error response to GMLC node160if, for example, permission is not granted by the user or is not received from UE110for the privacy verification in step304or a valid location estimate is not obtained from E-SMLC node140in step307. MME node130may also return the last known location of UE110if allowed and if a valid location estimate is not obtained. MME node130may record charging information. The common MT-LR procedure in PS and CS domain is then performed to return the location information to LCS client170(step309).

As noted above, although obtaining location via conventional LCS client requests/responses have generally been considered satisfactory for their intended purpose, there is still a need in the art for improved location services. Accordingly, the subject disclosure provides improved location services techniques to obtain location information for UE(s), maintain the location information for the UE(s) in a location services database and trigger location information lookup for UE(s) based on specific events (e.g., network changes, handovers, time-based, geo-fencing, etc.). Further, these improved location services techniques provide historical and current geographical location information for UE, make on-demand location requests (when location information is not readily available in the location services database), and provide information location data to third party applications.

Referring now toFIG. 4, the communication network shown inFIG. 1is provided along with a subscriber location device410. As discussed above, subscriber location device410can comprise the components of device/node200, shown inFIG. 2. Additionally, subscriber location device410can include any number of additional remote or resident devices/nodes/etc. For example, as shown, subscriber location device410incorporates the LCS client170as well as a subscriber location database415.

Subscriber location device415extracts key location information (e.g., geographical information) for UE(s)110and store the location information in the subscriber location database415. The subscriber location database415is queried by a variety of applications420(e.g., network operations, other applications, etc.). The subscriber location database415can include, for example, an application programming interface (API).

Operatively, location information for UE(s)110is obtained by monitoring, via the subscriber location device, the diameter SLs network interface between E-SMLC node140and MME node130. Such location information includes, for example, precise geographical coordinates such as altitude, horizontal speed and vertical velocity of UE110. Subscriber location device410location monitors location information via a tap/probe on the SLs network interface and stores the location information in the subscriber location database415. Typically, the location information is, for example, stored and indexed according to an associated UE.

An application420queries subscriber location device410for location information for UE (e.g., UE110). If the location information associated with UE110is not up-to-date or otherwise unavailable, subscriber location device410optionally launches or triggers the LCS Client170to request location information to/from the GMLC node160.

Notably, in certain embodiments, the application420and/or the subscriber location device410can also establish trigger criteria, which causes a request for updated location information for the UE. For example, trigger criteria can include out-of-date subscriber location information, a geographical position of the UE (e.g., geo-fencing, etc.), a time, a detected handover of the UE in a communication network, a geographical location of the UE relative to an emergency situation, a retail facility, etc. In addition, the subscriber location database415can work in conjunction with the application420(e.g., via the application programming interface (API)) to support online near-real-time complex event processing (e.g., the application can configure certain triggers based on subscriber events). Additionally, application420can include a complex event processing engine that triggers dynamic queries to the network to fetch (e.g., update) subscriber data.

The GMLC node receives the request and operates to obtain location information (e.g., exchanging messages between MME node130, eNB/RAN120, E-SMLC node140, UE110, etc.). Subscriber location device410continues to monitor the SLs network interface for updated location information for UE110and receives the location information (e.g., an altitude, a horizontal speed and a vertical velocity, etc.). The subscriber location device410further associates the received location information with the corresponding UE to yield associated location information, stores the updated location information (e.g., indexed according to the associated UE), and sends the updated location information to the application.

With respect to triggers, applications420and/or subscriber location device410establish criteria to trigger requests for location information for UEs. For example, as previously discussed, if the location information does not exist and/or if the location information is out-of-date, a trigger is executed to obtain location information. In other embodiments, the triggers can be based on UE position (e.g., geo-fencing), a time (e.g., a time of day), a detected handover for the UE in the communication network (e.g., moving from coverage areas and/or moving from 3GPP to non-3GPP coverage, etc.), or even advertisement based location triggering (e.g., vicinity to a shopping center, etc.).

FIG. 5, similar to signaling diagram300(ref.FIG. 3above), provides a signaling diagram500for the Mobile Terminated Location Request (MT-LR) procedure. Different than signaling diagram300, the signaling diagram500further illustrates the subscriber location device410and highlights the improved location services techniques discussed above.

In particular, the subscriber location device410triggers, via the LCS client170, a location request (i.e., LCS service request) at step301. As discussed above, subscriber location device410also monitors the SLs network interface between E-SMLC node140and MME node130for location information. For example, as shown in signaling diagram500, the subscriber location device410monitors the location requests (step305, the positioning procedure (step306) and the location response (step307). In this fashion, the subscriber location device410receives location information for UE110. Further, as discussed above, the location information is subsequently stored in subscriber location database415and can be queried by third party applications.

FIG. 6illustrates an example simplified procedure600for improved location services (e.g., subscriber location process/services244), particularly, from the perspective of a subscriber location device (e.g., subscriber location device410), in accordance with one or more embodiments described herein.

Procedure600starts at step605and continues to step610where, as discussed above the subscriber location device monitors a network interface between a Mobility Management Entity (MME) node and an Evolved Serving Mobile Location Center (E-SMLC) node (e.g., SLs network interface, etc.). The subscriber location device receives, in step610, location information (e.g., an altitude, a horizontal speed and a vertical velocity, etc.) from network interface between the MME node and the E-SMLC node. At step615, the subscriber location device associates the received location information with corresponding UE to yield associated location information and stores the associated location information in a subscriber location database (e.g., subscriber location database415), indexed according to the UE.

In certain embodiments, the subscriber location device receive, at step630, a request for the associated location information for the UE from an application (e.g., applications420) and determines (at step635) that the associated location information stored in the subscriber location database needs to be updated (e.g., based on trigger criteria such as out-of-date subscriber location information, based on a geographical position (of the UE), a time, a detected handover of the UE in a communication network, geographical location relative to an emergency situation, geographical location relative to a retail facility, etc.). Once determined, the subscriber location device triggers, at step635, an update for the associated location information stored in the subscriber location database that causes a location services client to send a location services request to a Gateway Mobile Location Centre (GMLC) node. As discussed above, the GMLC node subsequently causes, via the MME node, the UE to send location information across the network interface between the MME node and the E-SMLC node.

At step645, the subscriber location device retrieves the associated location information stored in the subscriber location database and at step650, the subscriber location device provides the associated location information to the application in response to the received request. Subsequently, procedure600ends at step655, or it can subsequently proceed to step610where the subscriber location device monitors the network interface between the MME node and the E-SMLC node, discussed above.

The techniques described herein, therefore, provide for improved location services using a subscriber location device. In particular, the techniques herein provide for storing and otherwise making available subscriber location information of UE for third party applications, which can be used in various types of location-based uses (e.g., geo-fencing, emergency situations, targeted retailing, etc.). Moreover, these techniques are scalable to various other types of networks and obviate restrictive permissions of service providers.

While there have been shown and described illustrative embodiments that provide for improved location services, it is to be understood that various other adaptations and modifications may be made within the spirit and scope of the embodiments herein. For example, the embodiments have been shown and described herein with relation to a using a subscriber location device that monitors and stores subscriber location information for LTE/3GPP networks. However, the embodiments in their broader sense are not as limited, and may, in fact, be used with other types of networks and/or protocols.