Systems, methods, and media for sharing information with vendor applications in secure environments
US-2024403071-A1 · Dec 5, 2024 · US
US2016321052A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016321052-A1 |
| Application number | US-201514724965-A |
| Country | US |
| Kind code | A1 |
| Filing date | May 29, 2015 |
| Priority date | Apr 28, 2015 |
| Publication date | Nov 3, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods are provided for suggesting actions for entities discovered in content on a mobile device. An example method can include running a mobile device emulator with a deep-link for a mobile application, determining a main entity for the deep link, mapping the main entity to the deep link, storing the mapping of the main entity to the deep link in a memory, and providing the mapping to a mobile device, the mapping enabling a user of the mobile device to select the deep link when the main entity is displayed on a screen of the mobile device. Another example method can include identifying at least one entity in content generated by a mobile application, identifying an action mapped to the at least one entity, the action representing a deep link into a second mobile application, and providing a control to initiate the action for the entity.
Opening claim text (preview).
1 . A mobile device comprising: at least one processor; and memory storing instructions that, when executed by the at least one processor, cause the mobile device to: identify, in response to a user request, at least one entity in content generated by a mobile application, identify an action mapped to the at least one entity, the action representing a deep link into a second mobile application, and provide a control that allows the user to initiate the action for the entity. 2 . The mobile device of claim 1 , wherein the second mobile application is not installed on the mobile device. 3 . The mobile device of claim 1 , wherein the second mobile application is not installed on the mobile device and wherein the memory further stores instructions that, when executed by the at least one processor, causes the mobile device to: receive a selection of the control; download, responsive to the selection, and install the second mobile application on the mobile device; and use the deep link to open the second mobile application after installation. 4 . The mobile device of claim 1 , wherein the memory further stores instructions that, when executed by the at least one processor, causes the mobile device to: receive a selection of the control; and upweight the mapping between the at least one entity and the action for the user. 5 . The mobile device of claim 1 , wherein the memory further stores instructions that, when executed by the at least one processor, causes the mobile device to: receive a command clearing the control without selection; and down-weight the mapping between the at least one entity and the action for the user. 6 . The mobile device of claim 1 , wherein the action is a first action and the memory further stores instructions that, when executed by the at least one processor, causes the mobile device to: determine that the at least one entity is mapped to the first action and to a second action, the second action representing a second deep link into a third mobile application; determine that the second mobile application is installed on the mobile device but the third mobile application is not; and select, in response, the first action over the second action. 7 . The mobile device of claim 1 , wherein the action is a first action and the memory further stores instructions that, when executed by the at least one processor, causes the mobile device to: determine that the at least one entity is mapped to the first action and to a second action, the second action representing a second deep link into a third mobile application; determine that the user uses the second mobile application more frequently than the third mobile application; and select, in response, the first action over the second action. 8 . The mobile device of claim 1 , wherein the action is a first action and the memory further stores instructions that, when executed by the at least one processor, causes the mobile device to: determine that the at least one entity is mapped to the first action and to a second action, the second action representing a second deep link into a third mobile application; determine that the entity has a higher topicality score with respect to the second mobile application than the third mobile application; and select, in response, the first action over the second action. 9 . A method comprising: running a mobile device emulator with a deep-link for a mobile application; determining a main entity for the deep link; mapping the main entity to the deep link; storing the mapping of the main entity to the deep link in a memory; and providing the mapping to a mobile device, the mapping enabling a user of the mobile device to select the deep link when the main entity is displayed on a screen of the mobile device. 10 . The method of claim 9 , further comprising: ranking the mapping based on attributes of the mobile application in an application store, wherein providing the mapping occurs when the ranking satisfies a threshold. 11 . The method of claim 9 , wherein the deep-link is generated based on a deep-link template provided by a developer of the mobile application. 12 . The method of claim 9 , wherein the deep-link is generated based on a deep-link list provided by a developer of the mobile application. 13 . The method of claim 9 , wherein the deep-link is generated based on a deep-link template provided by a developer of the mobile application, and the method further comprises: generating a plurality of deep links from the template; determining, for each of the plurality of deep links, whether the deep link is valid and, when the deep link is valid, a main entity for the deep link; mapping respective main entities to deep links; and storing the mappings in the memory. 14 . The method of claim 9 , wherein the mobile application is a first mobile application and wherein the mobile device uses the mapping to identify a deep link mapped to at least one entity recognized in a second mobile application running on the mobile device and to provide a control that allows a user to navigate to the deep link in the first mobile application. 15 . The method of claim 9 , further including: selecting an entity from a knowledge base for input into a search intent for the mobile application prior to running the mobile device emulator, wherein running the mobile device emulator includes using the emulator to submit the search using the entity, and performing the mapping, storing, and ranking when the mobile application returns content for the entity. 16 . A method comprising: identifying, in response to a user gesture on a mobile device, at least one entity in content generated by a mobile application; identifying an action mapped to the at least one entity, the action representing a deep link into a second mobile application; and providing a control that allows the user to initiate the action for the entity. 17 . The method of claim 16 , wherein the second mobile application is not installed on the mobile device. 18 . The method of claim 16 , wherein the second mobile application is not installed on the mobile device and wherein the method further includes: receiving a selection of the control; downloading and installing the second mobile application on the mobile device. 19 . The method of claim 16 , wherein the entity matches an entity template and the entity is mapped to the action via the entity template. 20 . The method of claim 16 , wherein the entity is a first entity of a plurality of entities identified in the content, and the method further includes: selecting the first entity from among the plurality of entities based on relevance to the user. 21 . The method of claim 16 , wherein the entity is a first entity of a plurality of entities identified in the content, and the method further includes selecting the first entity from among the plurality of entities based on topicality to the content. 22 . The method of claim 16 , wherein the action is a first action and the method further includes: determining that the at least one entity is mapped to the first action and to a second action, the second action representing a second deep link into a third mobile application; determining that the user uses the second mobile application more than the third mobile application; and selecting, in response, the first action over the second action.
Electricity · mapped topic
Installation · CPC title
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
Search customisation based on user profiles and personalisation · CPC title
Arrangements for interaction with the human body, e.g. for user immersion in virtual reality (blind teaching G09B21/00) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.