BACKGROUND

Portable devices such as mobile phones are typically small, lightweight, and easily carried by users. As technology has advanced, such portable devices have provided users with an increasing amount of “on-the-go” functionality. For example, portable devices can incorporate a digital camera, a media player, and Internet-surfing capabilities. Some portable devices also include a global positioning system (GPS) transceiver. The ability to detect a current location of the portable device may enable location-based searches at the portable device. For example, a user of a mobile phone may perform (e.g., via a browser or a maps application) a search for restaurants that are near the current location. However, such a listing may not always be useful. For example, if the user is in a car that is traveling on a highway, identifying restaurants that the user has already travelled past may not be useful.

Other devices, such as vehicle navigation systems, may identify points of interest that are along a route of the vehicle. However, the vehicle navigation system may not be able to identify such points of interest unless a user has previously identified their intended destination.

SUMMARY

Systems and methods of performing a search at a mobile computing device and generating search results based on a predicted (e.g., future) location of the mobile computing device are disclosed. When a user enters one or more search terms into the mobile computing device, the mobile computing device may transmit a search query that includes the one or more search terms and a location history of the mobile computing device to a server. For example, the location history may be used (e.g., by a location prediction service accessible to the server) to predict a future location of the mobile computing device. The predicted location of the mobile computing device may be a predicted destination of the mobile computing device, a point along a predicted route of the mobile computing device, or some other location. The search terms from the user may be augmented with information regarding the predicted location, thereby creating a trajectory-aware search query. The trajectory-aware search query may be transmitted to a search engine to identify trajectory-aware search results that may be more relevant to a travelling user than search results identified solely based on a current location of the user.

In alternate implementations, the future location(s) of the mobile computing device may be predicted at the mobile computing device instead of at a server or by a location prediction service. The mobile search techniques disclosed herein may identify trajectory-aware search results even when an intended destination or an intended route of the mobile computing device are not expressly input by a user. Thus, the disclosed systems and methods may be operable “out of the box.”

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram to illustrate a particular embodiment of a system to perform mobile search based on a predicted location;

FIG. 2 is a diagram to illustrate another particular embodiment of a system to perform mobile search based on a predicted location;

FIG. 3 is a diagram to illustrate a particular embodiment of a grid of geographic elements useable by the system of FIG. 1 or the system of FIG. 2;

FIG. 4 is a diagram to illustrate a particular embodiment of a predicted route and a predicted destination at the grid of FIG. 3;

FIG. 5 is a diagram to illustrate a particular embodiment of a displayed interface at the mobile computing device of FIG. 1 or the mobile computing device of FIG. 2;

FIG. 6 is a flow diagram to illustrate a particular embodiment of a method of performing mobile search based on a predicted location;

FIG. 7 is a flow diagram to illustrate another particular embodiment of a method of performing mobile search based on a predicted location; and

FIG. 8 is a block diagram of a computing environment including a computing device operable to support embodiments of computer-implemented methods, computer program products, and system components as illustrated in FIGS. 1-7.

DETAILED DESCRIPTION

In a particular embodiment, a method includes receiving one or more search terms at a mobile computing device while the mobile computing device is located at a particular location. The method also includes transmitting a search query to a server. The search query includes the one or more search terms and a location history of the mobile computing device. The method further includes receiving a search result in response to the search query, where the search result includes content identified based on a predicted destination of the mobile computing device. The method includes displaying an interface at the mobile computing device that identifies the search result.

In another particular embodiment, a non-transitory computer-readable storage medium includes instructions that, when executed by a computer, cause the computer to receive a search query from a mobile computing device. The search query includes one or more search terms and a set of geographic elements traversed by the mobile computing device during a trip. The instructions are also executable to cause the computer to determine a predicted location of the mobile computing device based on the set of geographic elements and to create a trajectory-aware search query based on the one or more search terms and the predicted location. The instructions are further executable to cause the computer to identify one or more search results in response to the trajectory-aware search query and to transmit the one or more search results to the mobile computing device.

In another particular embodiment, a system includes a location indicator, an input interface, an output interface, and a network interface. The system also includes a processor and a memory storing instructions executable by the processor to track a location history based on outputs of the location indicator. The instructions are also executable by the processor to receive one or more search terms via the input interface and to predict a destination based on the location history. The instructions are further executable to create a trajectory-aware search query based on the one or more search terms and the predicted destination. The instructions are executable to transmit the trajectory-aware search query to a search engine via the network interface and to receive one or more search results from the search engine via the network interface. The instructions are also executable to display content associated with the one or more search results via the output interface.

FIG. 1 is a diagram to illustrate a particular embodiment of a system 100 to perform mobile search based on a predicted location. The system 100 includes a server 130 communicatively coupled to a mobile computing device 110, a location prediction service 140, and a search engine server 160. However, it should be noted that alternate implementations may include one or more of the server 130, the location prediction service 140, and the search engine server 160 incorporated into a single device.

The mobile computing device 110 may be a mobile telephone, a smartphone, a portable digital assistant (PDA), a laptop computer, a tablet computer, a netbook computer, a navigation device, a digital camera, a watch or other electronic apparel or accessory, or some other portable electronic device or portable computing device. The mobile computing device 110 may include one or more input and output interfaces or devices. For example, the mobile computing device 110 may be a mobile telephone that includes input devices such as a keypad and a microphone, output devices such as a speaker, and combination input/output devices such as a capacitive touchscreen. The mobile computing device 110 may also include a location indicator such as a GPS transceiver. When sampled, the location indicator may return a current location of the mobile computing device 110. In alternate embodiments, other forms of location measurement may be used by or provided to the mobile computing device 110. For example, the current location of the mobile computing device 110 may be determined from one or more wireless (e.g., Wi-Fi) access points, cellular towers, Bluetooth radios, or a separate location determining device (e.g., a vehicle's navigation system).

In a particular embodiment, the mobile computing device 110 is operable to detect the start and stop of a trip made by a user that possesses the mobile computing device 110. Trips may be detected automatically or in response to user input. For example, the start of a car trip may be detected when the mobile computing device 110 experiences a sudden and large change in velocity. During the trip, the mobile computing device 110 may sample the location indicator to maintain a location history 124 of the mobile computing device 110. For example, the location history 124 may identify a set of one or more geographic elements (e.g., geographic cells, road segments, or other geographic elements) traversed by the mobile computing device 110 during the trip.

In a particular embodiment, the mobile computing device 110 samples the location indicator periodically (e.g., upon expiration of a sampling period such as 5 seconds). The mobile computing device 110 may identify a geographic element corresponding to the location returned by the location indicator and add the geographic element to the location history 124. In a particular embodiment, the geographic element is not added to the location history 124 unless the geographic element is more than a threshold distance (e.g., 20 meters) from a previously returned location. In alternate embodiments, a sampling period other than 5 seconds and a threshold distance other than 20 meters may be used.

When the mobile computing device receives 110 a search query 120 including one or more search terms 122 from the user, the mobile computing device 120 may add the location history 124 (or information related to the location history 124) to the search query 120 before transmitting the search query 120 to the server 130. For example, the search terms 122 may be received via a browser application or a maps application executing at the mobile computing device 110.

The server 130 may receive the search query 120 from the mobile computing device 110. In a particular embodiment, the server 130 identifies a predicted location 142 of the mobile computing device 110 after receiving the search query 120. For example, the predicted location 142 may be a predicted destination of the mobile computing device 110, a point on a predicted route of the mobile computing device 110, or some other location. In certain situations, a predicted destination of the mobile computing device 110 may correspond to the current location of the mobile computing device 110 (i.e., the location of the mobile computing device 110 when the search terms 122 were entered). That is, the server 130 may predict that a user has arrived at his or her intended destination, will make a round-trip, or will not travel anywhere else for a period of time. Alternately, the predicted destination of the mobile computing device 110 may be different than the current location of the mobile computing device 110.

The server 130 may add information regarding the predicted location 142 to the search query 120 to generate a trajectory-aware search query 132. For example, the trajectory-aware search query 132 may include the search terms 122 and geographic coordinates or keywords corresponding to the predicted location 142. To illustrate, if the search terms 122 included “hardware store” and the predicted location was “Seattle, Washington,” the trajectory-aware search query 132 may include “hardware store Seattle, Washington.” The trajectory-aware search query 132 may be transmitted to a search engine server 160 to generate the search results 162. For example, the search engine server 160 may correspond to an Internet-accessible search engine.

In a particular embodiment, the server 130 utilizes a location prediction service 140 to identify the predicted location 142. For example, the server 130 may extract the location history 124 from the search query 120 and may transmit the location history 124 to the location prediction service 140. The location prediction service 140 may use the location history 124 to determine the predicted location 142 and may transmit the predicted location 142 to the server 130. For example, the location prediction service 140 may include or may have access to stored travel times 150 corresponding to a geographic region. The stored travel times 150 may include estimates of how long it takes to travel (e.g., by foot, bicycle, motorcycle, car, public transportation, or any combination thereof) between two points in the geographic region. The location prediction service 140 may use the stored travel times 150 and other information or assumptions (e.g., that most trips are less than half an hour in duration) to determine the predicted location 142. An exemplary method of predicting a future location based on a location history is described with reference to FIGS. 3-4.

In a particular embodiment, the mobile computing device 110 transmits updated location histories to the server 130 during a trip. For example, an updated location history may indicate movement of the mobile computing device 110 from a first location to a second location. The server 130 may use the updated location histories to refine the predicted location 142 and to identify updated search results via the search engine server 160. For example, the trajectory-aware search query 132 may be transmitted to the search engine server 160 via a search engine application programming interface (API). The server 130 may transmit the updated search results to the mobile computing device 110, where the updated search results are displayed alongside or instead of the search results 162 (e.g., at a graphical user interface (GUI) generated by the mobile computing device 110). An exemplary search interface is further described with reference to FIG. 5.

In another particular embodiment, trajectory-aware search is not performed if the search terms 122 include a geographic search term. To illustrate, if the search terms 122 or a second search query included “hardware store Portland, Oregon” instead of merely “hardware store,” the mobile computing device 120 may not add the location history 124 to the search query 120, since the search terms 122 already specify a geographic target. Alternately, the mobile computing device 110 may add the location history 124, but the server 130 may ignore the location history 124 and may transmit the search query 120 to the search engine server 160 as-is to retrieve search results regarding hardware stores in the Portland, Oregon area (e.g., independently of a trajectory of the mobile computing device 110).

In yet another embodiment, the location history 124 may be used for disambiguation purposes. For example, if the search terms 122 included “hardware store Portland,” the server 130 may use the location history 124 and the predicted location 142 to deduce that a mobile phone is travelling towards Portland, Oregon and not Portland, Maine. The server 130 may thus prioritize search results associated with Portland, Oregon over those associated with Portland, Maine. Alternately, or in addition, the location history 124 may be used to suggest auto-complete search terms. For example, if a user located in Bellevue, Washington types “Kir” into a search interface while the user is traveling from Bellevue, Washington towards Kirkland, Washington, the search term “Kirkland” may be provided as a suggested auto-completion of the user's partially entered search query.

In another particular embodiment, the server 130 or the location prediction service 140 may compute a speed of the mobile computing device 110. For example, each geographic element in the location history 124 may have an associated timestamp representing when the mobile computing device 110 added the geographic element to the location history 124. The speed of the mobile computing device 110 may be computed based on the timestamps and may be used to augment the trajectory-aware search query 132, refine the trajectory-aware search results 162, identify additional search results, or any combination thereof. For example, a user may traverse the same sequence of geographic cells or road segments via a highway or via city streets. The computed speed of the mobile computing device 110 may be greater when the user is on the highway than when the user is on city streets. When the speed indicates that the user is on the highway (e.g., the speed is greater than a threshold), search results close to or associated with one or more exits on the highway may be prioritized. In other embodiments, a predicted location of a mobile computing device may also be used for non-search related purposes. For example, the predicted location may be used to determine traffic conditions en-route to the predicted location, to suggest alternate routes to the predicted location, or for other non-search related purposes.

In operation, the mobile computing device 110 may receive the search terms 122 and may generate the search query 120 based on the search terms 122. The mobile computing device 110 may also add the location history 124 to the search query 120 and transmit the search query 120 with the location history 124 to the server 130. The server 130 may identify the predicted location 142 of the mobile computing device 110 based on the location history 124. For example, the server 130 may transmit the location history 124 to the location prediction service 140 and receive the predicted location 142 from the location prediction service 140. The server may augment the search terms 122 with the predicted location 142 to generate the trajectory-aware search query 132. The server may identify the one or more trajectory-aware search results 162 based on the trajectory-aware search query 132 (e.g., via the search engine server 160). The server 130 may transmit the trajectory-aware search results 162 to the mobile computing device 110.

It will be appreciated that the system 100 of FIG. 1 may improve the mobile search experience in multiple ways. For example, the system 100 of FIG. 1 may decrease the amount of time and/or number of searches a user performs before the user locates a desired point of interest. As another example, the system 100 of FIG. 1 may provide trajectory-aware search results that are not returned by conventional search techniques, thereby providing greater choice to the user. In addition, the system 100 of FIG. 1 may provide mobile and localized search capabilities in situations where the user is unfamiliar with his or her surroundings.

It should be noted that although the system 100 of FIG. 1 depicts a separate mobile computing device 110, server 130, location prediction service 140, and search engine server 160, one or more components of the system 100 may be integrated into a single device. For example, FIG. 2 illustrates a particular embodiment of a mobile computing device 200 operable to perform mobile search based on a predicted location.

The mobile computing device 200 may integrate the functionality and operations described with reference to the mobile computing device 100, the server 130, and the location prediction service 140 of FIG. 1. For example, the mobile computing device 200 may include an input interface 210, such as a touchscreen or keypad. The input interface 210 may be operable to receive input 201 from a user. The mobile computing device 200 may also include a location indicator 230 (e.g., a GPS transceiver). When sampled, the location indicator 230 may provide a location (e.g., GPS coordinates) of the mobile computing device 200.

The mobile computing device 200 may further include a network interface 250. For example, the network interface 250 may be a wireless interface such as a cellular network interface or Wi-Fi network interface. The network interface 250 may be operable to communicate with network-based entities such as an Internet-accessible search engine. In a particular embodiment, the mobile computing device 200 communicates with the Internet-accessible search engine via an API 202. The mobile computing device 200 may also include an output interface 260 operable to provide output 203 to a user. For example, the output interface 260 may be a display screen. In a particular embodiment, the input interface 210 and the output interface 260 are integrated into a single device, such as a capacitive touchscreen.

The mobile computing device 200 may also include a trajectory-aware search and location prediction module 220. In a particular embodiment, the module 220 is implemented by processor-executable instructions. For example, such instructions may be stored at a memory of the mobile computing device 200 and may be executed by a processor of the mobile computing device 200. It should be noted that although the trajectory-aware search and location prediction module 220 is illustrated in FIG. 2 as a single module, functionality of the trajectory-aware search and location prediction module 220 may be implemented using any number of hardware or software logic blocks or modules.

During operation, the location indicator 230 may be sampled (e.g., periodically) to track a location history 232 of the mobile computing device 200. The input interface 210 may receive the input 201 from a user, where the input 201 represents one or more search terms 212. The search terms 212 may be input into the trajectory-aware search and location prediction module 220. The trajectory-aware search and location prediction module 220 may determine a predicted location of the mobile computing device 200 based on the location history 232. In a particular embodiment, predicting the location includes reference to a database or table of stored travel times 240. For example, the stored travel times 240 may be stored in a non-volatile memory of the mobile computing device 200.

The module 220 may generate a trajectory-aware search query 222 that includes the predicted location. For example, the predicted location may be a predicted destination of the mobile computing device 200 or may be a point on a predicted route of the mobile computing device 222. The trajectory-aware search query 222 may be transmitted to a search engine via the network interface 250. The search engine may return one or more trajectory-aware search results 224 that may be displayed to the user via the output interface 260 as the output 203. For example, the search results 224 may be associated with the predicted location of the mobile computing device 200. Alternately, the trajectory-aware search query 222 may be used to search one or more local data stores (e.g., local databases, files, or applications) at the mobile computing device 200 instead of a search engine.

It will be appreciated that the system 200 of FIG. 2 may integrate trajectory-aware search functionality into a single device, such as a mobile phone or a portable navigation system. The system 200 of FIG. 2 may thus enhance user convenience and provide mobile device hardware or software manufacturers with a differentiating location-based search feature.

FIGS. 3-4 illustrate a particular embodiment of a method of predicting a location based on a location history. It should be noted that the illustrated location prediction method is for example only. Various location prediction methods may be used in conjunction with the trajectory-aware mobile search techniques disclosed herein.

In a particular embodiment, predicting locations based on location histories includes performing one or more initial (e.g., preparation) operations prior to making any predictions. A geographic area may be divided into a plurality of geographic elements. For example, FIG. 3 depicts a grid 300 divided into a plurality of equal-sized (e.g., 150 meter×150 meter) geographic elements representing a portion of the greater Seattle, Washington area.

The grid 300 may include one or more navigable geographic elements 302 and one or more non-navigable geographic elements 304. In a particular embodiment, the navigable geographic elements 302 represent geographic elements that are within a threshold distance (e.g., 150 meters) from a navigable roadway. When the grid 300 is divided into geographic elements, a corresponding set of geographic elements may be created. A subset of the navigable geographic elements 302 may then be identified (e.g., by removing non-navigable geographic elements from the set) and travel times may be determined between each pair of navigable geographic elements. The travel times may be stored for future reference at one or more data storage devices (e.g., as the stored travel times 150 of FIG. 1 or the stored travel times 240 of FIG. 2). In a particular embodiment, the number of calculations to be performed may be reduced by a factor of two by assuming that travel time between two geographic cells will be equal regardless of travel direction.

As a mobile computing device (e.g., the mobile computing device 100 of FIG. 1 or the mobile computing device 200 of FIG. 2) traverses the geographic elements of the grid 300, a location history of the mobile computing device may be tracked. For example, the location history may represent the trajectory illustrated in FIG. 3, where the trajectory includes an initial geographic element 310 (e.g., a start of a trip) and a most recent detected geographic element 320 (e.g., a current location). The trajectory may be used to determine one or more of a predicted destination 402 and a predicted route 404 of the mobile computing device, as illustrated in FIG. 4.

In a particular embodiment, one or more destination elements are identified, where the destination elements are reachable within a predetermined time from the initial geographic element 310. For example, the predetermined time may be 30 minutes, based on an assumption or an empirical observation that most trips take less than 30 minutes to complete. The destination elements may be identified based on the previously stored travel times. For each such destination geographic element, a probability of whether the destination geographic element is a future location (e.g., destination) of the mobile computing device may be computed. Based on the computed probabilities, one or more of the predicted destination 402 and the predicted route 404 may be determined. The predicted destination 402 and/or the predicted route 404 may be used to identify trajectory-aware search results (e.g., search results near the predicted destination and/or along the predicted route 404).

In another particular embodiment, the predicted destination 402, the predicted route 404, and the computed probabilities may be stored for each user session to improve performance. Thus, when an updated location history is received, the predicted destination 402 and predicted route 404 may be updated without re-computing the probabilities. In another particular embodiment, each geographic element in a location history may be associated with a timestamp (e.g., representing when the mobile computing device entered, exited, or was located in the geographic element). The timestamps may be used to compute a speed of the mobile computing device, and the computed speed may be used to identify additional trajectory-aware search results or may be used to prioritize or refine previously identified search results. For example, when the computed speed is greater than a threshold (e.g., 55 miles per hour), search results associated with highway exits may be identified or prioritized.

It will be appreciated that the location prediction method of FIGS. 3-4 may enable trajectory-aware search at mobile computing devices. It will also be appreciated that the method of FIGS. 3-4 may protect user privacy. For example, only those locations relevant to a current trip may be tracked, and locations traversed during old trips may be deleted once a trip has been completed. In addition, the method of FIGS. 3-4 may operate based on a broad resolution of 150 meter×150 meter areas instead of tracking more precise addresses or coordinates visited by users.

FIG. 5 is a diagram to illustrate a particular embodiment of a trajectory-aware search interface 500. For example, the interface 500 may be displayed by the mobile computing device 110 of FIG. 1 or the mobile computing device 200 of FIG. 2.

In a particular embodiment, the interface includes a search field 501 and a search control 502. For example, the search field 501 may accept text input corresponding to one or more search terms, and the search control 502 may be a button operable to submit the search query to a trajectory-aware search program. To illustrate, a user presented with the interface 500 may enter a search term “pizza,” indicating that he or she is interested in finding a pizza restaurant. The interface 500 may also include a map area 510. The map area 510 may depict a region surrounding a current location 511 of a mobile computing device. The interface 500 may also include a bulls-eye icon 503 operable to center the map area 510 on the current location 511 and a timer icon 504 operable to view a history of previously conducted searches. Alternately, other icons or text-based controls may be displayed. In a particular embodiment, the map area 510 is interactive and may support panning and zooming operations.

In response to a search query (e.g., “pizza”), one or more search results may be generated and displayed (e.g., overlaid) on the map area 510. For example, the search results may be generated as described with reference to the search results 162 of FIG. 1 or the search results 224 of FIG. 2. The search results may include trajectory-aware search results, trajectory-unaware search results (e.g., results based on just the term “pizza” and/or the current location 511 of the mobile computing device), or any combination thereof. To illustrate, trajectory-aware search results (e.g., a search result 512 “E”) may be denoted by a white flag at the interface 500, and trajectory-unaware search results (e.g., a search result 515 “A”) may be denoted by a gray flag at the interface.

In a particular embodiment, each search result is interactive. For example, the user may select the search result 512 “E,” and the associated flag may change from white to black, as illustrated at 513. In addition, an information box 514 may be displayed, where the information block 514 includes information associated with the location or business corresponding to the selected search result 512 “E”. For example, for a pizza restaurant, the information box 514 may include a name, a price range, an address, and a phone number of the pizza restaurant. In other embodiments, the information box 514 may also include or be operable (e.g., via selection) to view reviews of the pizza restaurant submitted by other users.

It should be noted that the retail (e.g., “hardware store”) and restaurant (e.g., “pizza”) searches described herein are for example only. The disclosed mobile search techniques may be applied to any other search domain. For example, trajectory-aware mobile search may be performed on local (e.g., city, state, or municipal) content, web content, advertising, traffic information, friends or friend groups (e.g., in social networks), and other information domains. Moreover, trajectory information may not only be used to identify search results, but also to prioritize or rank search results, to compute information related to the trajectory (e.g., a remaining time to arrival at the predicted destination), and to pre-fetch search results or content likely to be retrieved by a user during subsequent searches or Internet-browsing sessions.

FIG. 6 is a flow diagram to illustrate a particular embodiment of a method 600 of performing mobile search based on predicted location. In an illustrative embodiment, the method 600 may be performed at the mobile computing device 110 of FIG. 1 or the mobile computing device 200 of FIG. 2.

The method 600 may include detecting a start of a trip by a mobile computing device, at 602. For example, in FIG. 2, the trajectory-aware search and location prediction module 220 may detect the start of a trip. The method 600 may also include maintaining a location history of the mobile computing device, at 604. In a particular embodiment, maintaining the location history includes performing an iterative process. The process may include sampling a location indicator, at 606. For example, the location indicator may be sampled every five seconds. When it is determined, at 608, that a location returned by the sample indicator is a new location, the process may include adding a geographic element corresponding to the returned location to a set of geographic elements, at 610. When the returned location is not a new location, the process may iterate back to 606. The location history may continue to be tracked until the trip ends, at which point the location history may be deleted. In other embodiments, the location histories may be saved (e.g., on a per-user basis).

The method 600 may further include receiving one or more search terms at the mobile computing device while the mobile computing device is at a particular location, at 612. For example, in FIG. 2, the search terms 212 may be received via the input interface 210. The method 600 may include predicting a location of the mobile computing device based on the location history, at 614. The predicted location may be a predicted destination of the mobile computing device or a point along a predicted route of the mobile computing device. For example, in FIG. 2, the trajectory-aware search and location prediction module 220 may determine the predicted location based on the location history 232.

The method 600 may also include creating a trajectory-aware search query based on the one or more search terms and the predicted location, at 616. For example, in FIG. 2, the trajectory-aware search and location prediction module 220 may create the trajectory-aware search query 222. The method 600 may further include receiving a search result or search results in response to the search query, at 618. The search result includes content identified based on the predicted location. For example, in FIG. 2, the search results 224 may be received via the network interface 250.

The method 600 may include displaying an interface at the mobile computing device that identifies the search result, a 620. For example, in FIG. 2, the interface may be displayed via the output interface 260. In an illustrative embodiment, the displayed interface is the interface 500 of FIG. 5.

FIG. 7 is a flow diagram to illustrate another particular embodiment of a method 700 of performing mobile search based on a predicted location. In a particular embodiment, the method 700 may be performed at the system 100 of FIG. 1 and is illustrated with reference to FIGS. 3-4.

The method 700 may include dividing a geographic area into a plurality of geographic elements, at 702. For example, in FIG. 1, the location prediction service 140 may divide a geographic area into a plurality of geographic elements. To illustrate, the geographic area may be divided into the grid 300 of FIG. 3.

The method 700 may also include identifying a subset of navigable geographic elements that are within a threshold distance of a navigable roadway, at 704. For example, in FIG. 1, the location prediction service 140 may identify a subset of geographic elements. To illustrate, the subset of navigable geographic elements may be the subset of navigable geographic elements 302 of FIG. 3.

The method 700 may further include determining and storing travel times between each pair of navigable geographic elements, at 706. For example, in FIG. 1, the location prediction service may generate the stored travel times 150. The method 700 may include receiving a search query from a mobile computing device, at 708. The search query may include one or more search terms and a set of geographic elements traversed by the mobile computing device during a trip. For example, in FIG. 1, the server 130 may receive the search query 120 from the mobile computing device 110, where the search query 120 includes the search terms 122 and the location history 124. In an illustrative embodiment, the location history 124 includes a set of geographic elements traversed by the mobile computing device 110 during the trip. The method 700 may also include identifying one or more destination geographic elements that are reachable from an initial geographic element, at 710. For example, referring to FIG. 3. the initial geographic element may be the initial geographic element 310 of FIG. 3.

The method 700 may further include computing probabilities of whether the destination geographic elements are a destination of the mobile computing device, at 712, and determining a predicted destination based on the probabilities, at 714. For example, referring to FIG. 4 the predicted destination may be the predicted destination 402. Alternately, a point on the predicted route 404 may be determined. In a particular embodiment, the probabilities are computed based on an algorithm that relies on an assumption that travelers typically choose at least moderately efficient routes to a desired destination. Based on a user's trajectory (e.g., location history), the algorithm may compute how efficiently the user has approached or is approaching each potential destination (e.g., cell in the grid 300 of FIG. 3). The efficiencies may be used to compute the probability that each potential destination is the intended destination of the user. In some embodiments, a Markov model may be used during execution of the prediction algorithm. However, it should be noted that other models or other location prediction algorithms may also be used.

The method 700 may include creating a trajectory-aware search query based on the one or more search terms and the predicted destination, at 716, and identifying one or more search results in response to the trajectory-aware search query, at 718. For example, in FIG. 1, the server 130 may create the trajectory-aware search query 132 and may receive the search results 162. The method 700 may further include transmitting the one or more search results to the mobile computing device, at 720. For example, in FIG. 1, the server 130 may transmit the search results 162 to the mobile computing device 110. All or a portion of the method 700 may be re-executed to update the search results (e.g., as the user travels towards the predicted location or performs additional searches).

FIG. 8 shows a block diagram of a computing environment 800 including a computing device 810 operable to support embodiments of computer-implemented methods, computer program products, and system components according to the present disclosure. For example, the computing device 810 or components thereof may include, implement, or be included as a component of the mobile computing device 110 of FIG. 1, the server 130 of FIG. 1, the location prediction service 140 of FIG. 1, the mobile computing device 200 of FIG. 2, the search engine server 160, or any portions thereof.

The computing device 810 includes at least one processor 820 and a system memory 830. For example, the computing device 810 may be a desktop computer, a laptop computer, a tablet computer, a mobile phone, a server, or any other fixed or mobile computing device. Depending on the configuration and type of computing device, the system memory 830 may be volatile (such as random access memory or “RAM”), non-volatile (such as read-only memory or “ROM,” flash memory, and similar memory devices that maintain stored data even when power is not provided), non-transitory, some combination of the three, or some other memory. The system memory 830 may include an operating system 832, one or more application platforms 834, one or more applications 836, and program data 838. In the embodiment illustrated, the system memory 830 includes a trajectory-aware search and location prediction module 837. In an illustrative embodiment, the trajectory-aware search and location prediction module 837 is the trajectory-aware search and location prediction module 220 of FIG. 2 or is incorporated into one or more of the mobile computing device 110, the server 130, and the location prediction service 140 of FIG. 1.

The computing device 810 may also have additional features or functionality. For example, the computing device 810 may also include removable and/or non-removable additional data storage devices such as magnetic disks, optical disks, tape, and memory cards. Such additional storage is illustrated in FIG. 8 by removable storage 840 and non-removable storage 850. Computer storage media may include volatile and/or non-volatile storage and removable and/or non-removable media implemented in any technology for storage of information such as computer-readable instructions, data structures, program components or other data. The system memory 830, the removable storage 840, and the non-removable storage 850 are all examples of computer storage media. The computer storage media includes, but is not limited to, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disks (CD), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store information and that can be accessed by the computing device 810. Any such computer storage media may be part of the computing device 810. In an illustrative embodiment, such computer storage media is used to store the stored travel times 150 of FIG. 1 or the stored travel times 240 of FIG. 2.

The computing device 810 may also have input device(s) 860, such as a keyboard, mouse, pen, voice input device, touch input device, etc. connected via one or more input interfaces. In an illustrative embodiment, the input device(s) 860 include the input interface 210 of FIG. 2. Output device(s) 870, such as a display, speakers, printer, etc. may also be included and connected via one or more output interfaces. In an illustrative embodiment, the output device(s) 870 include the output interface 260 of FIG. 2.

The computing device 810 also contains one or more communication connections 880 that allow the computing device 810 to communicate with other computing devices over a wired or a wireless network. In an illustrative embodiment, the communication connections 880 include the network interface 250 of FIG. 2. The other computing devices may include one or more of a mobile computing device 892 (e.g., the mobile computing device 100 of FIG. 1 or the mobile computing device 200 of FIG. 2), a location prediction service 894 (e.g., the location prediction service 140 of FIG. 1), and a search engine 896 (e.g., the search engine server 160 of FIG. 1). For example, the one or more communication connections 880 may represent an interface that communicates with other computing devices via a network.

It will be appreciated that not all of the components or devices illustrated in FIG. 8 or otherwise described in the previous paragraphs are necessary to support embodiments as herein described. For example, the removable storage 840 may be optional.

The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.

Those of skill would further appreciate that the various illustrative logical blocks, configurations, modules, and process steps or instructions described in connection with the embodiments disclosed herein may be implemented as electronic hardware or computer software. Various illustrative components, blocks, configurations, modules, or steps have been described generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The steps of a method described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in computer readable media, such as random access memory (RAM), flash memory, read only memory (ROM), registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor or the processor and the storage medium may reside as discrete components in a computing device or computer system.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments.

The Abstract is provided with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments.

The previous description of the embodiments is provided to enable a person skilled in the art to make or use the embodiments. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope possible consistent with the principles and novel features as defined by the following claims.