Patent Grant
9619574
This disclosure generally relates to the field of search, and more particularly to techniques for generating search results that correspond to states within software applications.
In recent years, the use of computers, smartphones, and other Internet-connected computing devices has grown significantly. Correspondingly, the number of software applications available for such computing devices has also grown. Today, many diverse software applications can be accessed on a number of different computing devices, including, but not limited to, smartphones, personal computers, automobiles, and televisions. These software applications can include business driven applications, games, educational applications, news applications, shopping applications, messaging applications, media streaming applications, and social networking applications, as some examples. Because of the large number of software applications available today and the wide range of functionality they provide, computing device users often require the ability to search for and access specific software application functionality.
In one example, a method includes receiving a search query from a user device and identifying one or more function records using the search query. In this example, each function record includes an application access mechanism (AAM) and application state information (ASI). The AAM includes a reference to a native application and indicates one or more operations for the native application to perform. The ASI describes a state of the native application after the native application has performed the one or more operations indicated by the AAM. The method further includes selecting one or more AAMs from the identified one or more function records and identifying one or more AAMs of the selected one or more AAMs that are each compatible with the user device. The method also includes transmitting the identified one or more AAMs to the user device and refraining from transmitting any AAMs of the selected one or more AAMs that are not compatible with the user device.
In some examples, identifying the one or more AAMs of the selected one or more AAMs that are each compatible with the user device may include determining that the identified one or more AAMs are each compatible with an operating system of the user device. In some examples, each of the selected one or more AAMs may further include edition information that indicates an operating system with which the native application referenced by the AAM is compatible. In these examples, determining that the identified one or more AAMs are each compatible with the operating system of the user device may include receiving an indication of the operating system of the user device, and, for each of at least one of the selected one or more AAMs, determining whether the AAM is compatible with the operating system of the user device using the edition information included in the AAM and the indication, including the AAM in the identified one or more AAMs in response to determining that the AAM is compatible with the operating system of the user device, and excluding the AAM from the identified one or more AAMs in response to determining that the AAM is not compatible with the operating system of the user device.
In some examples, each of at least one of the identified one or more function records may further include an additional AAM in addition to the AAM. In these examples, the additional AAM may include a reference to an edition of the native application that is different than an edition of the native application referenced by the AAM. Also in these examples, the different editions of the native application may include different versions of the native application for different operating systems. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM and the additional AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with the operating system of the user device may include receiving an indication of the operating system, and, for each of the at least one of the identified one or more function records, determining whether one of the AAM and the additional AAM is compatible with the operating system using the indication, including one of the AAM and the additional AAM in the identified one or more AAMs in response to determining that the corresponding AAM is compatible with the operating system, and excluding any of the AAM and the additional AAM from the identified one or more AAMs in response to determining that the corresponding AAM is not compatible with the operating system.
In some examples, each of at least one of the identified one or more function records may further include a web address in addition to the AAM. In these examples, the web address may be configured to direct a web browser to a web version of the native application referenced by the AAM. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with the operating system of the user device may include receiving an indication of the operating system, and, for each of the at least one of the identified one or more function records, determining whether the AAM is compatible with the operating system using the indication, including the AAM in the identified one or more AAMs in response to determining that the AAM is compatible with the operating system, and excluding the AAM from the identified one or more AAMs and transmitting the web address to the user device in response to determining that the AAM is not compatible with the operating system.
In some examples, each of at least one of the identified one or more function records may further include an additional AAM in addition to the AAM and a web address. In these examples, the additional AAM may include a reference to an edition of the native application that is different than an edition of the native application referenced by the AAM. Also in these examples, the different editions of the native application may include different versions of the native application for different operating systems. Also in these examples, the web address may be configured to direct a web browser to a web version of the native application. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM and the additional AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with the operating system of the user device may include receiving an indication of the operating system, and, for each of the at least one of the identified one or more function records, determining whether one of the AAM and the additional AAM is compatible with the operating system using the indication, including one of the AAM and the additional AAM in the identified one or more AAMs in response to determining that the corresponding AAM is compatible with the operating system, and excluding the AAM and the additional AAM from the identified one or more AAMs and transmitting the web address to the user device in response to determining that the AAM and the additional AAM are not compatible with the operating system.
In some examples, identifying the one or more AAMs of the selected one or more AAMs that are each compatible with the user device may include determining that the identified one or more AAMs are each compatible with a native application that is installed on the user device. In some examples, each of the selected one or more AAMs may further include edition information that indicates a version the native application referenced by the AAM with which the AAM is compatible. In these examples, determining that the identified one or more AAMs are each compatible with a native application that is installed on the user device may include receiving an indication of a version of each of one or more native applications that are installed on the user device, and, for each of at least one of the selected one or more AAMs, determining whether the AAM is compatible with any of the one or more native applications using the edition information included in the AAM and the indication, including the AAM in the identified one or more AAMs in response to determining that the AAM is compatible with any of the one or more native applications, and excluding the AAM from the identified one or more AAMs in response to determining that the AAM is not compatible with any of the one or more native applications.
In some examples, each of at least one of the identified one or more function records may further include an additional AAM in addition to the AAM. In these examples, the additional AAM may include a reference to an edition of the native application that is different than an edition of the native application referenced by the AAM. Also in these examples, the different editions of the native application may include different versions of the native application for the same operating system. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM and the additional AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with a native application that is installed on the user device may include receiving an indication of a version of each of one or more native applications that are installed on the user device, and, for each of the at least one of the identified one or more function records, determining whether any of the AAM and the additional AAM is compatible with any of the one or more native applications using the indication, including any of the AAM and the additional AAM in the identified one or more AAMs in response to determining that the corresponding AAM is compatible with any of the one or more native applications, and excluding any of the AAM and the additional AAM from the identified one or more AAMs in response to determining that the corresponding AAM is not compatible with any of the one or more native applications.
In some examples, each of at least one of the identified one or more function records may further include a web address in addition to the AAM. In these examples, the web address may be configured to direct a web browser to a web version of the native application referenced by the AAM. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with a native application that is installed on the user device may include receiving an indication of a version of each of one or more native applications that are installed on the user device, and, for each of the at least one of the identified one or more function records, determining whether the AAM is compatible with any of the one or more native applications using the indication, including the AAM in the identified one or more AAMs in response to determining that the AAM is compatible with any of the one or more native applications, and excluding the AAM from the identified one or more AAMs and transmitting the web address to the user device in response to determining that the AAM is not compatible with any of the one or more native applications.
In some examples, each of at least one of the identified one or more function records may further include an additional AAM in addition to the AAM and a web address. In these examples, the additional AAM may include a reference to an edition of the native application that is different than an edition of the native application referenced by the AAM. Also in these examples, the different editions of the native application may include different versions of the native application for the same operating system. Also in these examples, the web address may be configured to direct a web browser to a web version of the native application. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM and the additional AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with a native application that is installed on the user device may include receiving an indication of a version of each of one or more native applications that are installed on the user device, and, for each of the at least one of the identified one or more function records, determining whether any of the AAM and the additional AAM is compatible with the one or more native applications using the indication, including any of the AAM and the additional AAM in the identified one or more AAMs in response to determining that the corresponding AAM is compatible with the one or more native applications, and excluding the AAM and the additional AAM from the identified one or more AAMs and transmitting the web address to the user device in response to determining that the AAM and the additional AAM are not compatible with any of the one or more native applications.
In some examples, identifying the one or more AAMs of the selected one or more AAMs that are each compatible with the user device may include determining that the identified one or more AAMs are each compatible with a device type of the user device. In some examples, each of the selected one or more AAMs may further include edition information that indicates a device type with which the native application referenced by the AAM is compatible. In these examples, determining that the identified one or more AAMs are each compatible with the device type of the user device may include receiving an indication of the device type of the user device, and, for each of at least one of the selected one or more AAMs, determining whether the AAM is compatible with the device type of the user device using the edition information included in the AAM and the indication, including the AAM in the identified one or more AAMs in response to determining that the AAM is compatible with the device type of the user device, and excluding the AAM from the identified one or more AAMs in response to determining that the AAM is not compatible with the device type of the user device.
In some examples, each of at least one of the identified one or more function records may further include an additional AAM in addition to the AAM. In these examples, the additional AAM may include a reference to an edition of the native application that is different than an edition of the native application referenced by the AAM. Also in these examples, the different editions of the native application may include different versions of the native application for different device types. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM and the additional AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with the device type of the user device may include receiving an indication of the device type, and, for each of the at least one of the identified one or more function records, determining whether one of the AAM and the additional AAM is compatible with the device type using the indication, including one of the AAM and the additional AAM in the identified one or more AAMs in response to determining that the corresponding AAM is compatible with the device type, and excluding any of the AAM and the additional AAM from the identified one or more AAMs in response to determining that the corresponding AAM is not compatible with the device type.
In some examples, each of at least one of the identified one or more function records may further include a web address in addition to the AAM. In these examples, the web address may be configured to direct a web browser to a web version of the native application referenced by the AAM. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with the device type of the user device may include receiving an indication of the device type, and, for each of the at least one of the identified one or more function records, determining whether the AAM is compatible with the device type using the indication, including the AAM in the identified one or more AAMs in response to determining that the AAM is compatible with the device type, and excluding the AAM from the identified one or more AAMs and transmitting the web address to the user device in response to determining that the AAM is not compatible with the device type.
In some examples, each of at least one of the identified one or more function records may further include an additional AAM in addition to the AAM and a web address. In these examples, the additional AAM may include a reference to an edition of the native application that is different than an edition of the native application referenced by the AAM. Also in these examples, the different editions of the native application may include different versions of the native application for different device types. Also in these examples, the web address may be configured to direct a web browser to a web version of the native application. Also in these examples, selecting the one or more AAMs from the identified one or more function records may include selecting the AAM and the additional AAM from each of the at least one of the identified one or more function records. Also in these examples, determining that the identified one or more AAMs are each compatible with the device type of the user device may include receiving an indication of the device type, and, for each of the at least one of the identified one or more function records, determining whether one of the AAM and the additional AAM is compatible with the device type using the indication, including one of the AAM and the additional AAM in the identified one or more AAMs in response to determining that the corresponding AAM is compatible with the device type, and excluding the AAM and the additional AAM from the identified one or more AAMs and transmitting the web address to the user device in response to determining that the AAM and the additional AAM are not compatible with the device type.
In some examples, identifying the one or more function records using the search query may include identifying the one or more function records based on one or more matches between one or more terms of the search query and one or more terms of the ASI included in the identified one or more function records. In some examples, the method may further include, for each of at least one of the identified one or more AAMs, transmitting link data to the user device, wherein the link data includes at least one of text and an image that are associated with the state of the native application described by the ASI included in the one of the identified one or more function records from which the AAM was selected.
In another example, a system includes one or more computing devices configured to receive a search query from a user device and identify one or more function records using the search query. In this example, each function record includes an AAM and ASI. The AAM includes a reference to a native application and indicates one or more operations for the native application to perform. The ASI describes a state of the native application after the native application has performed the one or more operations indicated by the AAM. The one or more computing devices are further configured to select one or more AAMs from the identified one or more function records and identify one or more AAMs of the selected one or more AAMs that are each compatible with the user device. The one or more computing devices are further configured to transmit the identified one or more AAMs to the user device and refrain from transmitting any AAMs of the selected one or more AAMs that are not compatible with the user device.
In another example, a non-transitory computer-readable storage medium includes instructions that cause one or more computing devices to receive a search query from a user device and identify one or more function records using the search query. In this example, each function record includes an AAM and ASI. The AAM includes a reference to a native application and indicates one or more operations for the native application to perform. The ASI describes a state of the native application after the native application has performed the one or more operations indicated by the AAM. The instructions further cause the one or more computing devices to select one or more AAMs from the identified one or more function records and identify one or more AAMs of the selected one or more AAMs that are each compatible with the user device. The instructions also cause the one or more computing devices to transmit the identified one or more AAMs to the user device and refrain from transmitting any AAMs of the selected one or more AAMs that are not compatible with the user device.
The details of one or more implementations of the disclosure are set forth in the accompanying drawings and the description below. Other aspects, features, and advantages will be apparent from the description and drawings, and from the claims.
The figures and the following description relate to example implementations by way of illustration only. It should be noted that from the following discussion, alternative implementations of the structures and methods disclosed herein will be readily recognized as viable alternatives that may be employed without departing from the scope of this disclosure.
A search system of the present disclosure receives a search query from a user device and generates search results in response to the received search query. The search system transmits the search results to the user device that generated the search query. The search results include a list of application access mechanisms (AAMs) that may be selected by a user. An AAM may be a string that includes a reference to a native application and indicates one or more operations for a user device to perform. In response to selection of an AAM on a user device, the user device may launch the native application referenced in the AAM and perform the one or more operations indicated in the AAM.
Native applications can perform a variety of different functions for a user. For example, a restaurant reservation application can make reservations for restaurants. As another example, an internet media player application can stream media (e.g., a song or movie) from the Internet. In some examples, a single native application can perform more than one function. For example, a restaurant reservation application may also allow a user to retrieve information about a restaurant and read user reviews for the restaurant in addition to making reservations. As another example, an internet media player application may also allow a user to perform searches for digital media, purchase digital media, and generate media playlists.
An AAM includes data that a user device can use to access functionality provided by a native application. For example, an AAM can include data that causes a user device to launch a native application and perform a function associated with the native application. Performance of a function according to the AAM may set the native application into a specified state. Accordingly, the process of launching a native application and performing a function according to an AAM may be referred to herein as launching the native application and setting the native application into a state that is specified by the AAM. In one example, an AAM for a restaurant reservation application can include data that causes a user device to launch the restaurant reservation application and make a reservation at a restaurant. In this example, the restaurant reservation application may be set in a state that displays reservation information to a user, such as a reservation time, a description of the restaurant, and user reviews. In another example, an AAM for an internet media player application can include data that causes a user device to launch the internet media player application and stream media from the Internet. In this example, the internet media player application may be set in a state that displays information regarding the media (e.g., music) being streamed, such as a song name, an artist, or an album name.
AAMs may have various different formats and content. The format and content of an AAM may depend on the native application with which the AAM is associated and the operations that are to be performed by the native application in response to selection of the AAM. For example, an AAM for an internet music player application may differ from an AAM for a shopping application. An AAM for an internet music player application may include references to musical artists, songs, and albums, for example. The AAM for the internet music player application may also reference operations, such as randomizing a list of songs and playing a song or album. An AAM for a shopping application may include references to different products that are for sale. The AAM for the shopping application may also include references to one or more operations, such as adding products to a shopping cart and proceeding to a checkout.
The search system transmits additional data in the search results along with the AAMs. For example, the search system may transmit data (e.g., text and/or images) which may be used by the user device to generate user selectable links (or “links”) in the search results. A link may include text and/or images that a user may select (e.g., touch, or click on) via a user interface of the user device. Each user selectable link may be associated with an AAM such that when a user selects a link, the user device launches the native application referenced in the AAM and performs the one or more operations indicated in the AAM. The text and/or images of a link displayed to a user may indicate the operations that will be performed in response to selection of the link. For example, if the link is to a song in a music playing application, the text and/or images may identify the music playing application that will be launched by the user device and the song that will be played by the music playing application when the user selects the link. Example links are illustrated in
A user may select a link to cause the user device to launch the native application identified in the link and perform one or more operations according to the AAM associated with the link. Put another way, when a user selects a link, the user device launches a native application and sets the native application into a state defined by the AAM associated with the link. In general, a state of a native application may refer to the operations and/or the resulting outcome of the native application in response to selection of a link. A state of a native application may also be referred to herein as an “application state.”
An application state specified by an AAM may depend on the functionality provided by the native application. For example, if a native application is configured to retrieve and display information from the Internet, the native application can be set into a state in which the native application retrieves information from the Internet and displays information to the user. In another example, if a native application is configured to play media from the Internet (e.g., music and/or video), the native application can be set into a state in which the native application is playing a song or a movie from the Internet. In another example, if a native application is configured to make restaurant reservations, the native application can be set into a state in which the native application displays available restaurant reservations to the user.
The search system includes a data store that the search system uses to generate the search results. The data store includes one or more different function records (e.g., the function record 150a of
An AAM included in a function record includes data that causes a user device to launch a native application and perform a function associated with the native application. For example, an AAM included in a function record may be a string that includes a reference to a native application and indicates one or more operations for a user device (e.g., the native application) to perform. An AAM may include an application resource identifier (ARI) and/or one or more operations for the user device to perform. An ARI may be a string having an application specific scheme in some examples. The ARI may include a reference to a native application and indicate one or more operations for the user device (e.g., the native application) to perform. For example, the ARI may include a reference to a native application, a domain name, and a path to be used by the native application to retrieve and display information to the user.
In some examples, the AAM may include operations for the user device to perform in addition to the operation(s) indicated in the ARI. For example, a search application on the user device, an operating system (OS) of the user device, and/or a native application on the user device may perform the operations included in the AAM. In some examples, the operations may be included in a script. Examples of operations may include, but are not limited to, launching a native application, creating and sending a search request to an application server, setting a current geographic location in a native application, making a restaurant reservation, sending a text message, and adding an appointment to a calendar.
In some examples, an AAM may not include an ARI. Instead, the AAM can include one or more operations that reference a native application and indicate one or more operations for the user device to perform. The one or more operations may include instructions for at least one of the search application, the OS, and/or a native application on the user device. In response to selection of the AAM, the user device may perform the operations included in the AAM.
A function ID included in a function record may be a string that uniquely identifies the function record among the other function records in the data store. In some examples, the function ID may describe a function and/or an application state in human readable form. For example, the function ID may be a human readable string that describes a function performed according to the AAM and/or an application state resulting from performance of the function according to the AAM. In a more specific example, a function ID for an internet music player application may include the name of the internet music player application along with the name of the song that will be played when the internet music player application is set into the state defined by the AAM included in the function record.
A function record includes ASI. The ASI includes data that describes an application state into which a native application is set according to the AAM in the function record. In some examples, the ASI may include data that describes the function performed according to the AAM included in the function record. The ASI can include text, numbers, and symbols that describe the application state. The types of data included in the ASI may depend on the type of information associated with the application state and the functionality specified by the AAM.
In some examples, the ASI may include data that may be presented to the user when the native application is in the application state defined by the AAM. For example, a function record associated with a shopping application may include ASI that describes products (e.g., names and prices) that are shown when the shopping application is set into the application state defined by the AAM of the function record. As another example, a function record associated with a music player application may include ASI that describes a song (e.g., name and artist) that is played when the music player application is set into the application state defined by the AAM of the function record.
The ASI included in a function record may be generated in a variety of different ways. In one example, data to be included in the ASI may be retrieved via partnerships with database owners and developers of native applications. For example, the data may be automatically retrieved from online databases that include, but are not limited to, data related to movies, television programs, music, and restaurants. In some examples, some data included in the ASI may be manually generated by a human operator. The data included in the ASI may be updated over time so that the search system provides up-to-date results.
The search system generates search results including a list of AAMs that are included in selected function records. Initially, the search system analyzes the search query received from a user device. The search system then identifies a set of function records based on the received search query. For example, the search system may identify the set of function records based on one or more matches (e.g., text matches) between one or more terms of the search query and one or more terms of the ASI included in the identified function records.
The search system processes (e.g., scores) the identified set of function records. For example, the search system may determine how well the function records match the received search query. The search system may then select the AAMs from the function records that best match the received search query. The search system transmits search results including the selected AAMs to the user device that generated the search query. The search system may also transmit additional data along with the AAMs. For example, the search system may transmit data (e.g., text and/or images) to be included in user selectable links.
In some implementations, a function record (e.g., the function record 220 of
The different AAMs included in the function record may cause the corresponding application editions to launch and perform similar functions. Accordingly, the different AAMs included in the function record may cause the corresponding application editions to be set into similar application states. In one example, if the different AAMs reference different editions of an information retrieval application, the different AAMs may cause the corresponding application editions to retrieve similar information. In another example, if the different AAMs reference different editions of an internet music player application, the different AAMs may cause the corresponding application editions to play the same song.
In a specific example, a function record for a native application that retrieves restaurant information may include multiple different AAMs for multiple different application editions. Assuming the function record is associated with a specific Mexican restaurant, the AAMs for the different application editions may cause each application edition to retrieve information for the same specific Mexican restaurant. For example, a first AAM may cause a first application edition (e.g., on a first OS) to retrieve information for the specific Mexican restaurant. A second AAM may cause a second application edition (e.g., on a second OS) to retrieve information for the specific Mexican restaurant.
During some searches, the search system may identify one or more function records that include multiple AAMs. In these scenarios, the search system may process (e.g., score) the identified set of function records in the manner described above. For each identified function record including multiple AAMs, the search system may select which of the AAMs to transmit to the user device. In some examples, the search system may transmit each of the multiple AAMs of the identified function record to the user device so that the user device may determine which AAM to use. In other examples, the search system may determine which of the multiple AAMs to transmit to the user device based on information included in a query wrapper received from the user device. For example, the search system may select and transmit one or more of the AAMs that are likely to be compatible with the user device, e.g., based on the OS version of the user device.
In some implementations, a function record (e.g., the function record 260 of
The WAM (e.g., a URL) included in a function record may be used by a web browser to access a web resource that includes similar information and/or performs similar functions as would be performed by a native application that receives an AAM of the function record. In one specific example, the WAM of a function record may direct the web browser of a user device to a web version of the native application referenced in the AAMs of the function record. For example, if the AAMs included in a function record for a specific Mexican restaurant cause each application edition to retrieve information for the specific Mexican restaurant, the WAM may direct the web browser of a user device to a web page entry for the specific Mexican restaurant.
During some searches, the search system may identify one or more function records that include AAMs and a WAM. In these scenarios, the search system may process (e.g., score) the identified set of function records in the manner described above. For each identified function record including AAMs and a WAM, the search system may determine whether to transmit the WAM and the AAMs. In some examples, the search system may transmit the WAM and each of the multiple AAMs to the user device so that the user device can determine which of the access mechanisms to use. In other examples, the search system may determine whether any of the AAMs should be transmitted to the user device. If the search system determines that none of the AAMs is likely to be compatible with the user device, the search system can refrain from sending the AAMs to the user device. Instead, the search system may transmit the WAM to the user device. As described above, the user device may use a web browser to access the web resource identified in the WAM.
In some implementations of the search system, a function record (e.g., the function record 300 of
The quality score may be determined based on metrics associated with a person, place, or thing described in the function record. For example, the quality score may be based on the popularity of a place described in the function record and/or ratings (e.g., user ratings) of the place described in the function record. In another example, if the function record describes a song, the quality score may be based on the popularity of the song described in the function record and/or ratings (e.g., user ratings) of the song described in the function record. The quality score may also be determined based on measurements associated with the function record. For example, the quality score may be determined based on data indicating how often the function record is retrieved during a search and how often access mechanisms (e.g., an AAM, a WAM, and/or an application download address) of the function record are selected by a user.
The user device 102 may generate user selectable links based on the received search results (e.g., the links 114a, 114b, . . . , 114e of
A software application may refer to computer software that causes a computing device to perform a task. In some examples, a software application may be referred to as an “application,” an “app,” or a “program.” Example applications include, but are not limited to, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and games.
Applications can be executed on a variety of different computing devices. For example, applications can be executed on mobile computing devices such as smart phones, tablets, and wearable computing devices (e.g., headsets and/or watches). Applications can also be executed on other types of computing devices having other form factors such as laptop computers, desktop computers, or other consumer electronic devices. In some examples, applications may be installed on a computing device prior to a user purchasing the device. In other examples, the user may download and install applications on the computing device.
The functionality of an application may be accessed on the computing device on which the application is installed. Additionally, or alternatively, the functionality of an application may be accessed via a remote computing device. In some examples, all of an application's functionality is included on the computing device on which the application is installed. These applications may function without communication with other computing devices (e.g., via the Internet). In other examples, an application installed on a computing device may access information from other remote computing devices during operation. For example, a weather application installed on a computing device may access the latest weather information via the Internet and display the accessed weather information to the user through the installed weather application. In still other examples, an application (e.g., a web based application) may be partially executed by the user's computing device and partially executed by a remote computing device. For example, a web application may be an application that is executed, at least in part, by a web server and accessed by a web browser of the user's computing device. Example web applications may include web-based email, online auctions, and online retail sites.
As described above, the search system 100 is configured to receive search queries from one or more user device(s) 102 via a network 106. A search query may include text, numbers, and/or symbols (e.g., punctuation) entered into the user device 102 by the user. For example, with reference to
In some examples, a user device 102 may transmit additional data along with the search query. The search query and the additional data may be referred to as a query wrapper. The query wrapper may include data associated with the search query, such as geo-location data (e.g., the location of the user device 102), platform data (e.g., a version of an OS 118 of the user device 102, a device type, and a web-browser version), an identity of a user of the user device 102 (e.g., a username), partner specific data, and other data. The user device 102 transmits the query wrapper to the search system 100. The search system 100 can use the search query and/or the additional data included in the query wrapper to generate the search results.
The search system 100 performs a search for function records included in the data store 108 in response to the received search query. The search system 100 generates search results that include a list of AAMs selected from the function records identified during the search. In some examples, the search system 100 generates result scores for the selected AAMs. Each AAM may be associated with a result score that indicates the rank of the AAM relative to the other AAM in the list of AAMs. The search system 100 may transmit the result scores to the user device 102 that generated the search query.
In some examples, the search system 100 may transmit additional data to the user device 102 along with the AAMs and result scores. For example, the search system 100 may transmit link data (e.g., text and/or images). Link data can refer to data that is to be included in user selectable links on the user device 102. The user device 102 displays the user selectable links to the user. Each user selectable link may be associated with an AAM included in the search results such that when a user selects a link, the user device 102 launches the native application referenced in the AAM and sets the native application into the state specified by the AAM. A user may select a link by touching (e.g., tapping) or clicking on the link.
In some examples described herein, the search system 100 may transmit one or more WAMs to the user device 102 along with AAMs. WAMs may include web addresses that are accessible via a web browser application 120 of the user device 102, as shown in
Referring back to
As described above, the search system 100 may communicate with the user devices 102 and the data sources 104 via the network 106. Examples of the user devices 102, the data sources 104, and the network 106 are now described in turn with reference to
User devices 102 can be any computing devices that are capable of providing search queries to the search system 100. User devices 102 include, but are not limited to, smart phones, tablet computers, laptop computers, and desktop computers. User devices 102 may also include other computing devices having other form factors, such as computing devices included in vehicles, gaming devices, televisions, or other appliances (e.g., networked home automation devices and home appliances).
The user devices 102 may use a variety of different operating systems. In an example where a user device 102 is a mobile device, the user device 102 may run an OS including, but not limited to, ANDROID® developed by Google Inc., IOS® developed by Apple Inc., or WINDOWS PHONE® developed by Microsoft Corporation. Accordingly, the OS 118 running on the user device 102 of
User devices 102 can communicate with the search system 100 via the network 106. In some examples, a user device 102 may communicate with the search system 100 using a native application installed on the user device 102 (e.g., the search application 116). In general, a user device 102 may communicate with the search system 100 using any application that can transmit search queries to the search system 100. In some examples, a user device 102 may run an application that is dedicated to interfacing with the search system 100, such as an application dedicated to searches (e.g., the search application 116). In other examples, a user device 102 may communicate with the search system 100 using a more general application, such as a web-browser application. The application run by a user device 102 to communicate with the search system 100 may display a search field 117 on a graphical user interface (GUI) in which the user may enter search queries. The user may enter a search query using a touchscreen or physical keyboard, a speech-to-text program, or other form of user input.
In general, a search query may be a request for information retrieval (e.g., search results) from the search system 100. For example, a search query may be directed to retrieving a list of links to native application functionality or application states in examples where the search system 100 is configured to generate a list of AAMs as search results. A search query directed to retrieving a list of links to native applications may indicate a user's desire to access functionality of one or more native applications described by the search query.
A user device 102 may receive a set of search results from the search system 100 that are responsive to the search query transmitted to the search system 100. The user device 102 may run a search application 116 including a GUI that displays the search results received from the search system 100. For example, the search application 116 used to transmit the search query to the search system 100 may also display the received search results to the user.
The GUI of the search application 116 running on the user device 102 may display the search results to the user in a variety of different ways, depending on what information is transmitted to the user device 102. In examples where the search results include a list of AAMs, the search system 100 may transmit the list of AAMs to the user device 102 along with additional data to be displayed in user selectable links. In some examples, the GUI may display the search results to the user as a list of user selectable links including text and images. The text and images in the links may include the native application names associated with the AAMs, text describing the AAMs, images associated with the native application referenced by the AAMs (e.g., application icons), and images associated with the application states (e.g., application screen images) defined by the AAMs.
In some examples, the GUI may display the search results as a list of links (e.g., links 114 of
In some examples, user devices 102 may communicate with the search system 100 via a partner computing system (not illustrated). The partner computing system may be a computing system of a third party that may leverage the search functionality of the search system 100. The partner computing system may belong to a company or organization other than that which operates the search system 100. Example third parties which may leverage the functionality of the search system 100 may include, but are not limited to, internet search providers and wireless communications service providers. The user devices 102 may send search queries to the search system 100 and receive search results via the partner computing system. The partner computing system may provide a user interface to the user devices 102 in some examples and/or modify the search experience provided on the user devices 102.
The data sources 104 may include a variety of different data providers. The data sources 104 may include data from application developers, such as application developers' websites and data feeds provided by developers. The data sources 104 may include operators of digital distribution platforms configured to distribute applications to user devices 102. The data sources 104 may also include other websites, such as websites that include web logs (i.e., blogs), application review websites, or other websites including data related to applications. Additionally, the data sources 104 may include social networking sites, such as “FACEBOOK®” by Facebook, Inc. (e.g., Facebook posts) and “TWITTER®” by Twitter, Inc. (e.g., text from tweets). The data sources 104 may also include online databases that include, but are not limited to, data related to movies, television programs, music, and restaurants. The data sources 104 may also include additional types of data sources in addition to the data sources described above. Different data sources may have their own content and update rate.
The search system 100 retrieves data from one or more of the data sources 104. The data retrieved from the data sources 104 can include any type of data related to application functionality and/or states. The search system 100 generates function records based on the data retrieved from the data sources 104. In some examples, some data included in the function records (e.g., ASI) is manually generated by a human operator. The data included in the function records may be updated over time so that the search system 100 provides up-to-date results.
As described above, the user devices 102, the search system 100, and the data sources 104 may be in communication with one another via the network 106. The network 106 may include various types of networks, such as a wide area network (WAN) and/or the Internet. Although the network 106 may represent a long range network (e.g., Internet or WAN), in some implementations, the network 106 may include a shorter range network, such as a local area network (LAN). In some implementations, the network 106 uses standard communications technologies and/or protocols. Thus, the network 106 can include links using technologies such as Ethernet. Wireless Fidelity (WiFi) (e.g., 802.11), worldwide interoperability for microwave access (WiMAX), 3G, Long Term Evolution (LTE), digital subscriber line (DSL), asynchronous transfer mode (ATM), InfiniBand. PCI Express Advanced Switching, etc. Similarly, the networking protocols used on the network 106 can include multiprotocol label switching (MPLS), the transmission control protocol/Internet protocol (TCP/IP), the User Datagram Protocol (UDP), HTTP, the simple mail transfer protocol (SMTP), the file transfer protocol (FTP), etc. The data exchanged over the network 106 can be represented using technologies and/or formats including the hypertext markup language (HTML), the extensible markup language (XML), etc. In addition, all or some of the links can be encrypted using conventional encryption technologies such as secure sockets layer (SSL), transport layer security (TLS), virtual private networks (VPNs), Internet Protocol security (IPsec), etc. In other examples, the network 106 can use custom and/or dedicated data communications technologies instead of, or in addition to, the ones described above.
Referring now to
The function ID 152a may be used to identify the function record 150a among other function records 150a included in the data store 108. The function ID 152a may be a string of alphabetic, numeric, and/or symbolic characters (e.g., punctuation marks) that uniquely identify the function record 150a in which the function ID 152a is included. In some examples, the function ID 152a may describe a function and/or an application state in human readable form. For example, the function ID 152a may include the name of the native application referenced in the AAM 156a. Additionally, or alternatively, the function ID 152a may be a human readable string that describes a function performed according to the AAM and/or an application state resulting from performance of the function according to the AAM. In some examples, the function ID 152a may include a string in the format of a URL of a WAM for the function record 150a, which may uniquely identify the function record, as described with respect to
In a more specific example, if the function record 150a describes a function of the native application Yelp the function ID 152a may include the name “Yelp” along with a description of the application state described in the ASI 154a. For example, the function ID 152a for a function record that describes the restaurant “The French Laundry®” (hereinafter, “The French Laundry”) may be “Yelp—The French Laundry.” In an example where the function ID 152a includes a string in the format of a URL, the function ID 152a may include the following string “www.yelp.com/biz/the-french-laundry-yountville-2?ob=1” to uniquely identify the function record 150a.
The ASI 154a may include data that describes an application state into which a native application is set according to the AAM 156a included in the function record 150a. Additionally, or alternatively, the ASI 154a may include data that describes the function performed according to the AAM 156a included in the function record 150a. The ASI 154a may include a variety of different types of data. For example, the ASI 154a may include structured, semi-structured, and/or unstructured data. The ASI 154a may be extracted or inferred from documents retrieved from the data sources 104. In some examples, the ASI 154a may include data that is manually generated. The ASI 154a may be updated so that up-to-date search results can be provided in response to a user search query.
In some examples, the ASI 154a may include data that may be presented to the user when the native application is in the application state defined by the AAM 156a. For example, the ASI 154a may include data that describes a state of the native application after the user device 102 has performed the one or more operations indicated in the AAM 156a. In one example, if the function record 150a is associated with a shopping application, the ASI 154a may include data that describes products (e.g., names and prices) that are shown when the shopping application is set to the application state defined by the AAM 156a of the function record 150a. As another example, if the function record 150a is associated with a music player application, the ASI 154a may include data that describes a song (e.g., name and artist) that is played when the music player application is set to the application state defined by the AAM 156a of the function record 150a.
The types of data included in the ASI 154a may depend on the type of information associated with the application state and the functionality defined by the AAM 156a. In one example, if the function record 150a is for a native application that provides reviews of restaurants, the ASI 154a may include information (e.g., text and numbers) related to a restaurant, such as a category of the restaurant, reviews of the restaurant, and a menu for the restaurant. In this example, the AAM 156a may cause the native application to launch and retrieve information for the restaurant. As another example, if the function record 150a is for a native application that plays music, the ASI 154a may include information related to a song, such as the name of the song, the artist, lyrics, and listener reviews. In this example, the AAM 156a may cause the native application to launch and play the song described in the ASI 154a.
The AAM 156a may include an ARI and/or one or more operations for a user device 102 to perform. For example, an ARI may be a string having an application specific scheme. The ARI may include a reference to a native application and indicate one or more operations for the user device 102 (e.g., the native application) to perform. For example, the ARI may include a reference to a native application, a domain name, and a path to be used by the native application to retrieve and display information to the user.
An example ARI for the native application “OPENTABLE®” by OpenTable, Inc. (hereinafter, “OpenTable”) on the ANDROID® OS is “vnd.opentable.deeplink://opentable.com/restaurant/profile?rid=88333&refid=1.” A portion of the example ARI references the OpenTable native application. For example, the substring “vnd.opentable.deeplink” of the ARI references the OpenTable native application. The example ARI also indicates one or more operations for the OpenTable native application to perform. For example, the OpenTable native application may retrieve and display the information included in the ARI domain and path defined by the substring “opentable.com/restaurant/profile?rid=88333&refid=1.” In response to receiving the ARI, a user device 102 may launch the OpenTable native application and display information retrieved from the location indicated in the ARI. The ARI may be provided by an app developer, for example.
In some examples, the AAM 156a may include operations for the user device 102 to perform in addition to the operation(s) indicated in the ARI. For example, the search application 116 on the user device 102, the OS 118 of the user device 102, and/or a native application installed on the user device 102 may perform the operations included in the AAM 156a in order to set the native application into an application state specified by the AAM 156a. In some examples, the operations may be included in a script. Examples of operations may include, but are not limited to, launching a native application, waiting for the native application to start, creating and sending a search request to a server associated with the native application, setting a current geo-location in a native application, making a restaurant reservation, sending a text message, and adding an appointment to a calendar.
In some examples, the AAM 156a may not include an ARI. Instead, the AAM 156a can include one or more other operations that reference a native application. The operations may be performed by the user device 102. The operations may include instructions for at least one of the search application 116, the OS 118, and a native application on the user device 102. In response to selection of the AAM 156a, the user device 102 may perform the operations included in the AAM 156a. In some examples, the operations may be included in a script.
The AAM 156a may also include edition information that indicates the native application edition with which the AAM 156a is compatible. For example, the edition information may indicate the OS with which the AAM 156a is compatible. In some examples, the search system 100 can determine whether to transmit the AAM 156a in the search results based on whether the user device 102 (e.g., the OS 118) can handle the AAM 156a. As one example, the search system 100 may transmit the edition information for the AAM 156a to the user device 102. In the event the user device 102 does not include the native application edition (e.g., for a particular OS) with which the AAM 156a is compatible, the user device 102 may not display a user selectable link for the AAM 156a. In some examples, e.g., in instances where none of the AAM(s) of the function record 150a is compatible with the user device 102 but where the function record 150a also includes a WAM, the user device 102 may instead display a user selectable link for the WAM. In other examples, in cases where the user device 102 does not include the native application edition with which the AAM 156a is compatible, the user device 102 may display a download and install user selectable link for the native application edition to the user. Upon the user selecting the link, the user device 102 may download and install the native application edition, launch the native application edition, and set the native application edition into an application state specified by the AAM 156.
In some examples, an ARI is an application specific resource identifier that is defined by the developer of the application. In this example, the search application 116 receives the ARI and the OS 118 may send the ARI to the native application referenced in the ARI. The native application referenced in the ARI launches and is set into the state specified by the ARI.
In some examples, a native application function may not be accessible using an ARI. For example, a function of the native application may not include a corresponding ARI that the application may use to perform the function. As another example, some native applications may not be configured to receive ARIs. In these examples, an AAM for the native application can include one or more operations that cause the native application to perform the function that may not otherwise be accessible using an ARI. For example, the search application 116 may receive the one or more operations and execute the one or more operations to set the native application into the desired application state. In a specific example, the one or more operations may include launching the native application along with additional operations for the native application to perform. For example, the search application 116 may initially trigger the native application to start the application, and then wait for a period of time for the native application to start. Then the search application 116 may perform additional operations included in the received AAM, such as issuing a search instruction to the native application.
In still other examples, a native application may be configured to directly receive the operations transmitted by the search system 100. In these examples, the native application may be launched according to the AAM and then the launched native application may directly perform the operations received from the search system 100.
A single native application can provide a variety of different functionalities. For example, a restaurant reservation application can access reviews for a variety of different restaurants and set up reservations at a variety of different restaurants. Similarly, a travel application can book hotels, book flights, and provide reviews for different travel destinations. The different functionalities associated with a single native application may be accessed using a plurality of different AAMs. For example, with respect to the restaurant reservation application, the data store 108 may include function records having different AAMs for accessing different restaurant reviews and setting up reservations. Similarly, the data store 108 may include function records having different AAMs for booking hotels, booking flights, and accessing reviews for different travel destinations.
The AAMs for a single native application may vary in complexity. In some examples, the AAMs may cause a native application to launch (e.g., the OS 118 may be instructed to launch the application) and then perform additional operations after launching, as described above. In other examples, the AAMs may cause a native application to launch into a default state (e.g., a default homepage) without performing any additional operations. A function record including an AAM that causes a native application to launch into a default state may be thought of as an access mechanism that is related to the native application, but not to any particular state which may be accessed by the application. A function record including such an AAM may include ASI describing the native application, instead of any particular application state. For example, the ASI may include the name of the developer of the application, the publisher of the application, a category (e.g., genre) of the application, a description of the application (e.g., a developer's description), and the price of the application. The ASI may also include security or privacy data about the application, battery usage of the application, and bandwidth usage of the application. The ASI may also include application statistics. Application statistics may refer to numerical data related to a native application. For example, application statistics may include, but are not limited to, a number of downloads, a download rate (e.g., downloads per month), a number of ratings, and a number of reviews.
The function record 160 includes the function ID “Opentable—The French Laundry” indicated at 162, which may uniquely identify the function record 160. In other examples, the function ID 162 could include a URL as a unique identifier for the function record 160. For example, the function ID 162 may include the string “http://www.opentable.com/the-french-laundry” as a unique identifier for the function record 160. Such a function ID may be included in a WAM of a function record. In another example, the function ID could be a string of characters, numbers, and/or symbols that are not in human readable form.
The function record 160 includes ASI 164. The ASI 164 includes a data fields for restaurant category of the French Laundry, description of the French Laundry, user reviews of the French Laundry, and additional data fields. The restaurant category field may include the text “French cuisine” and “contemporary,” for example. The description field for The French Laundry may include text that describes The French Laundry. The user reviews field may include text of user reviews for The French Laundry. The additional data fields may include additional data for The French Laundry that may not specifically fit within the other defined fields, such as a menu for the restaurant, prices, and operating hours for the restaurant.
The function record 160 includes an AAM 166. The AAM 166 may include a reference to the native application OpenTable along with one or more operations to be performed by a user device 102. For example, the AAM 166 may include a native ARI 168 and/or one or more operations 170 that cause the user device 102 to access the entry for The French Laundry in the OpenTable native application. An example ARI 168 may be “vnd.opentable.deeplink://opentable.com/restaurant/profile?rid=1180&refid=1.”
Referring back to
The set generation module 124 identifies a set of function records (i.e., the consideration set) based on the search query 128. In some examples, the set generation module 124 may identify the set of function records based on matches between terms of the search query 128 and terms in the function records. For example, the set generation module 124 may identify a set of function records in the data store 108 based on matches between tokens generated by the query analysis module 122 and words included in the function records, such as words included in the ASI and/or function IDs of the function records.
The set processing module 126 processes the consideration set to generate a set of search results 130 that includes a list of AAMs. In some examples, the set processing module 126 scores the functions records included in the consideration set. The scores associated with the function records may be referred to as “result scores.” Accordingly, in some examples, each of the function records in the consideration set may have a corresponding result score. The set processing module 126 may then select function records from the consideration set based on the result scores associated with the function records. For example, the set processing module 126 may select the highest scoring function records of the consideration set.
The set processing module 126 selects AAMs from the selected function records (e.g., the highest scoring function records). The set processing module 126 transmits the selected AAMs to the user device 102 that generated the search query 128. The set processing module 126 may also transmit the result scores associated with the AAMs. For example, an AAM may be associated with the result score of the function record from which the AAM was selected.
The information conveyed by the search results 130 may depend on how the result scores are calculated by the set processing module 126. For example, the result scores may indicate the relevance of an application function or state to the search query 128, the popularity of an application function or state, or other properties of the application function or state, depending on what parameters the set processing module 126 uses to score the function records.
The set processing module 126 may generate result scores for function records in a variety of different ways. In some implementations, the set processing module 126 generates a result score for a function record based on one or more scoring features. The scoring features may be associated with the function record and/or the search query 128. A function record scoring feature (hereinafter, “record scoring feature”) may be based on any data associated with a function record. For example, record scoring features may be based on any data included in the ASI of the function record. Example record scoring features may be a quality score and whether the function record includes an AAM that leads to a default state or a deeper native application state. A query scoring feature may include any data associated with the search query 128. For example, query scoring features may include, but are not limited to, a number of words in the search query 128, the popularity of the search query 128, and the expected frequency of the words in the search query 128. A record-query scoring feature may include any data which may be generated based on data associated with both the function record and the search query 128 that resulted in identification of the function record by the set generation module 124. For example, record-query scoring features may include, but are not limited to, parameters that indicate how well the terms of the search query 128 match the terms of the ASI of the identified function record. The set processing module 126 may generate a result score for a function record based on at least one of the record scoring features, the query scoring features, and the record-query scoring features.
The set processing module 126 may determine a result score based on one or more of the scoring features listed herein and/or additional scoring features not explicitly listed. In some examples, the set processing module 126 may include one or more machine learned models (e.g., a supervised learning model) configured to receive one or more scoring features. The one or more machine learned models may generate result scores based on at least one of the record scoring features, the query scoring features, and the record-query scoring features. For example, the set processing module 126 may pair the search query 128 with each function record and calculate a vector of features for each (query, record) pair. The vector of features may include one or more record scoring features, one or more query scoring features, and one or more record-query scoring features. The set processing module 126 may then input the vector of features into a machine-learned regression model to calculate a result score for the function record. In some examples, the machine-learned regression model may include a set of decision trees (e.g., gradient boosted decision trees). In another example, the machine-learned regression model may include a logistic probability formula. In some examples, the machine learned task described above can be framed as a semi-supervised learning task, where a minority of the training data is labeled with human curated scores and the rest of the data is used without human labels.
The result scores associated with the AAMs may be used in a variety of different ways. In some examples, the result scores associates with AAMs may be used to rank the list of AAMs. In these examples, a higher result score may indicate that the AAM (e.g., the function or application state) is more relevant to a user than an AAM having a smaller result score. In examples where the search results 130 are displayed as a list on a user device 102, the links for AAMs associated with larger result scores may be listed closer to the top of the results list (e.g., near to the top of the screen). In these examples, links for AAMs having lower result scores may be located farther down the list (e.g., off screen) and may be accessed by scrolling down the screen of the user device 102. In some examples, as illustrated in
As shown in
As also shown in
Referring again to
As explained herein, the data store 108 may include one or more databases, indices (e.g., inverted indices), tables, files, or other data structures which may be used to implement the disclosed techniques. In some examples, the data store 108 may also include one or more access tables that each include one or more different access mechanisms (e.g., one or more AAMs, WAMs, and application download addresses). For example, the access table 174 of
The access table 184 of
In block 506, the set generation module 124 identifies a consideration set of function records based on the search query 128 (e.g., based on output from the query analysis module 122). In blocks 508-510, the set processing module 126 processes the consideration set of function records. In block 508, the set processing module 126 generates result scores for the function records included in the consideration set. In block 510, the set processing module 126 selects function records from the consideration set based on the result scores associated with the function records. For example, the set processing module 126 may select function records having the highest result scores.
In block 512, the set processing module 126 selects AAMs from the selected function records. In block 514, the set processing module 126 generates search results including a list of the selected AAMs. In block 516, the set processing module 126 transmits the search results 130 to the user device 102 that generated the search query 128.
In block 602, the search application 116 receives a search query 128 from the user. For example, the search query 128 may have been entered into the GUI of the search application 116. In block 604, the user device 102 transmits the search query 128 to the search system 100. In block 606, the user device 102 waits for the search results to be received. The method 600 continues in block 608 when the search results are received from the search system 100. The search results may include a list of AAMs. the search results may also include result scores associated with the AAMs. Additionally, the search results may include link data (e.g., text and/or images) for each of the AAMs. the search application 116 may generate user selectable links in the GUI based on the received link data.
Accordingly, in block 608, the search application 116 generates one or more user selectable links that include the AAMs included in the search results 130. The search results 130 may include links for each of the AAMs included in the search results. In block 610, the search application 116 waits for the user to select one of the user selectable links. The method 600 continues in block 612 when the user selects (e.g., touches) one of the links in the search results. In response to selection of a link for an AAM, the user device 102 launches the native application referenced in the AAM and performs one or more operations indicated in the AAM in block 612.
The search system 100 receives the query wrapper and identifies one or more function records based on the search query 202 included in the query wrapper. The search system 100 processes the identified function records and selects AAMs from the identified function records. In the example of
The search results transmitted to the user device 200 include AAMs for the application functions/states indicated in the links 206a, 206b, . . . , 206f (collectively, the “links 206”). The search results also include link data (e.g., text and images) associated with each of the AAMs. For example, the “IHOP” link 206a includes the text “IHOP” and an image of pancakes. A user may select (e.g., touch or click) the links 206 to access the application function/state indicated in the links 206. For example, a user may select the area of the GUI including the “IHOP” link 206a in order to access the entry in the Yelp native application for “IHOP.” In
In the example of
The different AAMs 226 included in the function record 220 may be associated with different editions of a native application. For example, the first, second, and third AAMs 226 may be associated with first, second, and third editions of a native application, respectively. The different AAMs 226 in the function record 220 may be associated with different operating systems and/or different versions of a native application. In a specific example, the AAMs 226 may be associated with different operating systems. For example, the AAMs 226 may each include an ARI that is specific to a different OS, such as ANDROID®, IOS®, or WINDOWS PHONE®. More specifically, an ARI for a first edition of a native application that runs on a first OS may be different than an ARI for a second edition of the native application that runs on a second OS. As another example, the ARIs of the AAMs 226 may be different for native application editions that are different versions, but run on the same OS. The operations included in the AAMs 226 may also be specific to different operating systems and/or versions.
In some examples, the different AAMs 226 in the function record 220 may be associated with different versions of a native application for the same OS. For example, the AAMs 226 may each be associated with a different version of a native application for the ANDROID® OS. Different versions may include a version 1.0 of a native application and a later released version 2.0 of the native application. In another example, different versions of a native application may be versions of the native application designed for different devices. For example, a first version of a native application may be designed for a smart phone. A second version of the native application may be designed for a tablet computing device having a different set of specifications (e.g., screen size and resolution) than the smart phone for which the first version of the native application was designed.
As described with respect to
The different AAMs 226 included in the function record 220 may cause the corresponding native application editions to launch and perform similar functions so that the application editions are set into similar application states. For example, the different AAMs 226 included in the function record 220 may cause the corresponding native application editions to be set into the application state described by the function record 220 (e.g., the ASI 224). Accordingly, although the ARIs and/or the operations included in the AAMs 226 may be different, the different AAMs 226 may cause the different native application editions to be set into similar application states. In one example, if the different AAMs 226 reference different editions of an internet music player application, the different AAMs 226 may cause the different application editions to play the same song. In another example, if the different AAMs 226 reference different editions of a restaurant reservation application, the different AAMs 226 may cause the different editions to retrieve reservation information for the same restaurant.
The function record 240 includes two AAMs 246a, 246b. The first AAM 246a is associated with an edition of OpenTable that runs on the ANDROID® OS. Accordingly, the edition (i.e., ANDROID®) information 248a may indicate that the ANDROID® operations 250a and the ANDROID® native ARI 252a are compatible with the ANDROID® OS. Furthermore, the edition information 248a may specify one or more specific versions of the ANDROID® OS and one or more versions of the OpenTable application with which the ARI 252a and the operations 250a are compatible. The second AAM 246b is associated with an edition of OpenTable that runs on the IOS® OS. Accordingly, the edition (i.e., IOS) information 248b may indicate that the IOS® operations 250b and the IOS® native ARI 252b are compatible with the IOS® OS. Furthermore, the edition information 248b may specify one or more specific versions of the IOS® OS and one or more versions of the OpenTable application with which the ARI 252b and the operations 250b are compatible.
During a search for function records, the search system 100 (e.g., the set generation module 124) may identify one or more function records that include multiple AAMs, as described above. In these scenarios, the set processing module 126 may process (e.g., score) the identified set of function records in the manner described above. For example, the set processing module 126 may select function records from the consideration set based on the result scores associated with function records.
As described above, the set processing module 126 selects AAMs from the selected function records (e.g., the highest scoring function records) and transmits the selected AAMs to the user device 102 that generated the search query 128. In some implementations of the search system 100, the set processing module 126 may transmit each of the multiple AAMs of a function record to the user device 102 so that the user device 102 can determine which AAM to use. For example, assuming the function record 240 of
In some implementations of the search system 100, the set processing module 126 determines which of the multiple AAMs in a function record to transmit to the user device 102. The set processing module 126 may determine which of the multiple AAMs to transmit based on information included in the query wrapper received from the user device 102. For example, the set processing module 126 may select and transmit one or more of the AAMs that are likely to be compatible with the user device 102. In a scenario where the function record 240 of
The WAM 262 (e.g., a URL) included in the function record 260 may be used by a web browser application to access a web resource that includes similar information and/or performs similar functions as would be performed by a native application that receives the AAM(s) 268 of the function record 260. In one example, the WAM 262 may direct a web browser to a web version of the native application referenced in the AAM(s) 268. If the function record 260 is for a specific Mexican restaurant in Yelp, the AAM(s) 268 may include a reference to the Yelp native application and one or more operations that access an entry for the specific Mexican restaurant in the Yelp native application. In this example, the WAM 262 may include a web address that a web browser may use to access the entry for the specific Mexican restaurant on a Yelp web page.
During a search for function records, the search system 100 (e.g., the set generation module 124) may identify one or more function records that each include a WAM. In these scenarios, the set processing module 126 may process (e.g., score) the identified set of function records in the manner described above. For example, the set processing module 126 may select function records from the consideration set based on the result scores associated with the identified function records.
In some implementations of the search system 100, the set processing module 126 determines which of the multiple AAM(s) 268 and the WAM 262 should be transmitted to the user device 102. The set processing module 126 may determine whether to transmit the WAM 262 and/or the AAM(s) 268 of the function record 260 based on information included in the query wrapper received from the user device 102. For example, the set processing module 126 may select and transmit the WAM 262 and/or the AAM(s) 268 based on which of the WAM 262 and/or the AAM(s) 268 are likely to be compatible with the user device 102.
In scenarios where the set processing module 126 determines that one or more of the AAM(s) 268 is compatible with the user device 102, the set processing module 126 may transmit the one or more compatible AAMs. In these scenarios, the set processing module 126 may refrain from transmitting the WAM 262 and those AAMs that are determined to be incompatible with the user device 102. In other scenarios, if the set processing module 126 determines that none of the AAM(s) 268 is compatible with the user device 102, the set processing module 126 may transmit the WAM 262 and refrain from transmitting the AAM(s) 268.
During a search, the search system 100 (e.g., the set generation module 124) may identify one or more function records that each include an application download address 282. In these scenarios, the set processing module 126 may process (e.g., score) the identified set of function records in the manner described above. The set processing module 126 may also select function records from the consideration set and select which AAMs of the selected function records to transmit to the user device 102, as described above. The set processing module 126 may transmit the selected AAMs and the one or more application download addresses 282 to the user device 102.
As described above, different AAMs in a function record may be associated with different operating systems. A first AAM may be for a native application running on the ANDROID® OS. A second AAM may be for the native application running on the IOS® OS. In this example, the first AAM can be associated with a first application download address for downloading the ANDROID® edition of the native application. The second AAM can be associated with a second application download address for downloading the IOS® edition of the native application.
As described above, the search system 100 may transmit an AAM 288 and an application download address 282 for downloading the native application referenced in the AAM 288. If the user device 102 has the native application that is referenced in the AAM 288 installed, then the user device 102 (e.g., the search application 116) can generate a user selectable link that uses the AAM 288. For example, in response to selection of the user selectable link using the AAM 288, the user device 102 launches the native application referenced in the AAM 288 and performs one or more operations included in the AAM 288. If the user device 102 does not have the native application installed, the user device 102 can determine that the native application is not installed and then generate a user selectable link that uses the application download address 282. In response to selection of the user selectable link using the application download address 282, the user device 102 can launch the web browser or a native application and direct the user to a site (e.g., a digital distribution platform) where the native application can be downloaded. A user selectable link including the application download address 282 may include link data (e.g., text and/or images) indicating that the user can download the native application by selecting (e.g., touching) the user selectable link.
As described above, the data store 108 may include one or more databases, indices (e.g., inverted indices), tables, files, or other data structures which may be used to implement the techniques of the present disclosure. In some examples, as described above with reference to
Multiple different ways for accessing native application functionality and/or web application functionality are described above. For example, a user device 102 may access functionality of a native application using an AAM. In the case where the user device 102 does not have a native application installed, the user device 102 may download the native application by following the application download address, thereby allowing the user device 102 to use the AAM in the search results. Additionally, or alternatively, the user device 102 may also access functionality of a web application using a WAM. For example, if the user device 102 does not have a native application installed, the user device 102 may instead generate a user selectable link including a WAM to access similar functionality. Providing these different mechanisms for accessing functionality may help ensure that a user device 102 has the ability to access the desired functionality present in the search results.
In some examples, the search application 116 may be configured to generate user selectable links according to a hierarchy. For example, the search application 116 may be configured to generate a link including an AAM if a compatible AAM is received and the native application is currently installed. If the native application is not installed, then the search application 116 may generate a link including the WAM or including the application download address. In some examples, instructions to the search application 116 for which mechanism to use may be included along with the search results.
Referring now to
The quality score 302 may be determined based on metrics associated with the person, place, or thing described in the function record 300 (e.g., in the ASI 306). For example, the quality score 302 may be based on the popularity of a place described in the function record 300 and/or ratings (e.g., user ratings) of the place described in the function record 300. In another example, the quality score 302 may be based on the popularity of a song described in the function record 300 and/or ratings (e.g., user ratings) of the song described in the function record 300. The quality score 302 may also be determined based on measurements associated with the function record 300. For example, the quality score 302 may be determined based on data indicating how often the function record 300 is retrieved during a search and how often the AAM(s) 308 of the function record 300 are selected by a user.
The GUI of
The link 324c may be associated with an AAM for the TripAdvisor native application. For example, the AAM included in the link 324c may cause the user device 320 to launch the TripAdvisor native application to a default state, as described above. In other examples, the AAM included in The link 324c may cause the user device 320 to launch TripAdvisor and cause TripAdvisor to perform a search within TripAdvisor using the search query 322 (i.e., cause TripAdvisor to search for “Late night diners by me”). In other words, in some examples, a user device 102 may receive an AAM along with search results 130 received in response to transmitting a search query 128 to the search system 100. The user device 102 may include the AAM in a user selectable link as part of displaying the search results 130 to a user. Upon the user selecting the user selectable link, the AAM may cause the user device to perform a search within a native application included on the user device using the search query. In some examples, the AAM may reference the native application. In this manner, the AAM may be used as part of so-called “search forwarding.” In search forwarding, a search result 130 received by a user device 102 from the search system 100 in response to a search query 128 causes a native application included on the user device 102 to perform a search using the same search query 128.
The link 324d may include a WAM for the OpenTable web-based application. For example, the WAM may direct a web browser of the user device 320 to entries for one or more late night diners in the OpenTable web-based application. In some examples, the WAM included in the link 324d may cause the user device 320 to launch the OpenTable web-based application and cause it to perform a search using the search query 322 in a similar manner as described above with respect to search forwarding. Accordingly, in response to selection of the link 324d, the user device 320 may launch a web browser and retrieve information at the web address included in the WAM. As described above, since the OpenTable native application is not installed on the user device 320, the search application may have presented the link 324d to the user so that the user could access the desired functionality via a WAM.
The link 324e may include an application download address for the Urbanspoon native application. Since the user device 320 does not have the Urbanspoon native application installed, the user device 320 displays the link 324e that includes an application download address for the Urbanspoon native application. The user device 320 also displays the link 324e such that it includes a GUI element 330 with a string “Download,” which prompts the user to select the link 324e to download and install Urbanspoon. In response to selection of the link 324e, the user device 320 may access a site (e.g., a digital distribution platform) for downloading the Urbanspoon native application.
In some implementations, a function record may include location data. The search system 100 may use the location data in the function records to filter out function records that may not be relevant to a user because of the location of the user relative to the places described in the function records. For example, the search system 100 may filter out function records in which the user is located too far from the place described in the function record for the place to be relevant to the user.
Modules and data stores included in the search system 100 represent features that may be included in the search system 100 of the present disclosure. For example, the search module 110 and the data store 108 may represent features included in the search system 100.
The modules and data stores described herein may be embodied by electronic hardware, software, firmware, or any combination thereof. Depiction of different features as separate modules and data stores does not necessarily imply whether the modules and data stores are embodied by common or separate electronic hardware or software components. In some implementations, the features associated with the one or more modules and data stores depicted herein may be realized by common electronic hardware and software components. In some implementations, the features associated with the one or more modules and data stores depicted herein may be realized by separate electronic hardware and software components.
The modules and data stores may be embodied by electronic hardware and software components including, but not limited to, one or more processing units, one or more memory components, one or more input/output (I/O) components, and interconnect components. The interconnect components may be configured to provide communication between the one or more processing units, the one or more memory components, and the one or more I/O components. For example, the interconnect components may include one or more buses that are configured to transfer data between electronic components. The interconnect components may also include control circuits (e.g., a memory controller and/or an I/O controller) that are configured to control communication between electronic components.
The one or more processing units may include one or more central processing units (CPUs), graphics processing units (GPUs), digital signal processing units (DSPs), or other processing units. The one or more processing units may be configured to communicate with the one or more memory components and I/O components. For example, the one or more processing units may be configured to communicate with the one or more memory components and I/O components via the interconnect components.
A memory component, or memory, may include any volatile or non-volatile media. For example, the memory may include, but is not limited to, electrical media, magnetic media, and/or optical media, such as a random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), electrically-erasable programmable ROM (EEPROM), Flash memory, hard disk drives (HDD), magnetic tape drives, optical storage technology (e.g., compact disc, digital versatile disc, and/or Blu-ray Disc), or any other memory components.
The one or more memory components may include (e.g., store) the data described herein. For example, the one or more memory components may include the data included in the function records of the data store 108. The one or more memory components may also include instructions that may be executed by the one or more processing units. For example, the one or more memory components may include computer-readable instructions that, when executed by one or more processing units, cause the one or more processing units to perform the various functions attributed to the modules and data stores described herein.
The one or more I/O components may refer to electronic hardware and software that provides communication with a variety of different devices. For example, the one or more I/O components may provide communication between other devices and the one or more processing units and memory components. In some examples, the one or more I/O components may be configured to communicate with a computer network. For example, the one or more I/O components may be configured to exchange data over a computer network using a variety of different physical connections, wireless connections, and protocols. The one or more I/O components may include network interface components (e.g., a network interface controller), repeaters, network bridges, network switches, routers, and firewalls. In some examples, the one or more I/O components may include hardware and software that is configured to communicate with various human interface devices, including, but not limited to, display screens, keyboards, pointer devices (e.g., a mouse), touchscreens, speakers, and microphones. In some examples, the one or more I/O components may include hardware and software that is configured to communicate with additional devices, such as external memory (e.g., external HDDs).
In some implementations, the search system 100 may be a system of one or more computing devices (e.g., a computer search system) that is configured to implement the techniques described herein. Put another way, the features attributed to the modules and data stores described herein may be implemented by one or more computing devices. Each of the one or more computing devices may include any combination of electronic hardware, software, and/or firmware described above. For example, each of the one or more computing devices may include any combination of the one or more processing units, memory components, I/O components, and the interconnect components described above. The one or more computing devices may also include various human interface devices, including, but not limited to, display screens, keyboards, pointing devices (e.g., a mouse), touchscreens, speakers, and microphones. The one or more computing devices may also be configured to communicate with additional devices, such as external memory (e.g., external HDDs).
The one or more computing devices of the search system 100 may be configured to communicate with the network 106. The one or more computing devices may also be configured to communicate with one another via a computer network. In some examples, the one or more computing devices may include one or more server computing devices configured to communicate with the user devices 102 (e.g., receive search queries 128, and transmit search results 130), gather data from the data sources 104, index the data, store the data, and store other documents. The one or more computing devices may reside within a single machine at a single geographic location in some examples. In other examples, the one or more computing devices may reside within multiple machines at a single geographic location. In still other examples, the one or more computing devices may be distributed across a number of geographic locations.
Additionally, the various implementations of the search system 100 described above (e.g., using one or more computing devices that include one or more processing units, memory components, I/O components, and interconnect components) are equally applicable to any of the user devices 102, as well as to the various components thereof, as described herein.
This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Application 61/943,105, filed Feb. 21, 2014, which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8099332 | Lemay et al. | Jan 2012 | B2 |
| 8661033 | Leppert et al. | Feb 2014 | B2 |
| 20060287985 | Castro et al. | Dec 2006 | A1 |
| 20060294063 | Ali et al. | Dec 2006 | A1 |
| 20080009268 | Ramer | Jan 2008 | A1 |
| 20100306191 | LeBeau et al. | Dec 2010 | A1 |
| 20110072001 | Basu et al. | Mar 2011 | A1 |
| 20110209143 | Ierullo | Aug 2011 | A1 |
| 20110307833 | Dale et al. | Dec 2011 | A1 |
| 20120124062 | Macbeth | May 2012 | A1 |
| 20120284247 | Jiang | Nov 2012 | A1 |
| 20120316955 | Panguluri et al. | Dec 2012 | A1 |
| 20120323898 | Kumar | Dec 2012 | A1 |
| 20130132896 | Lee et al. | May 2013 | A1 |
| 20130268673 | Graham-Cumming | Oct 2013 | A1 |
| 20130290321 | Shapira et al. | Oct 2013 | A1 |
| 20130290344 | Glover et al. | Oct 2013 | A1 |
| 20130304729 | Jiang | Nov 2013 | A1 |
| 20130325892 | Edwards | Dec 2013 | A1 |
| 20140006409 | Prosnitz | Jan 2014 | A1 |
| 20140019442 | Mahaniok et al. | Jan 2014 | A1 |
| 20140052683 | Kirkham et al. | Feb 2014 | A1 |
| 20140067846 | Edwards et al. | Mar 2014 | A1 |
| 20140172840 | Kumar et al. | Jun 2014 | A1 |
| 20140201179 | Chang et al. | Jul 2014 | A1 |
| 20140358887 | Morris et al. | Dec 2014 | A1 |
| 20140359598 | Oliver et al. | Dec 2014 | A1 |
| 20140365462 | Chang | Dec 2014 | A1 |
| Entry |
|---|
| App Indexing: <https://web.archive.org/web/20140225132807/https://developers.google.com/app-indexing/webmasters/>, Dec. 4, 2013. |
| App Indexing Technical Details: <https://web.archive.org/web/20140210182226/https://developers.google.com/app-indexing/webmasters/details>, Feb. 1, 2014. |
| Indexing Apps Just Like Websites: <http://googlewebmastercentral.blogspot.com/2013/10/indexing-apps-just-like-websites.html>, Oct. 31, 2013. |
| Google Search Now Discovers Content Within Android Apps: http://searchengineland.com/google-search-now-discovers-content-within-android-apps-178960, Dec. 4, 2013. |
| Google's Search Results Can Deep-Link to Your Android Apps: <http://techcrunch.com/2013/10/31/android-4-4-kitkat-app-indexing/>, Oct. 31, 2013. |
| International Search Report and Written Opinion for related WO Application No. PCT/US2015/016866, dated May 26, 2015. |
| Google Testing SERP With Up to 16 Product Listing ADS: http://www.rimmkaufman.com/blog/google-testing-serp-with16-product-listing-ads/16072013 accessed on Sep. 2, 2014. |
| Secrets of the 7-Result Sep. 2, 2014. SERP: http://moz.com/blog/secrets-of-the-7-result-serp, accessed on Sep. 2, 2014. |
| SERPs: A Primer: http://www.goinflow.com/serps-primer/, accessed on Sep. 2, 2014. |
| Ask.com SERP: http://www.ask.com/web?qq=katy+perry, accessed on Sep. 2, 2014. |
| Bing.com SERP: http://www.bing.com/search?q=katy+perry, accessed on Sep. 2, 2014. |
| Google.com SERP: https://www.google.com/?#q=katy+perry, accessed on Sep. 2, 2014. |
| PCT International Preliminary Report on Patentability dated Sep. 1, 2016 for PCT/US2015/016866, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150242507 A1 | Aug 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61943105 | Feb 2014 | US |
