IP Library Granted Patent US 12,430,368
Granted Patent B2
US 12,430,368 · App. 18/495,558 · Granted Sep 30, 2025

Search suggestions based on native application history

Inventors: Ulas Kirazci (Mountain View, CA); Othar Hansson (Sunnyvale, CA); Anton Hansson (London, GB)
Assignee: GOOGLE LLC
G06F16/3322
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,430,368
App. No.
18/495,558
Granted
Sep 30, 2025
Kind
B2
Abstract

Methods, systems, and apparatus, for automatically generating search suggestions based on history data for multiple native application on a user device.

Claims (41)

1. A computer-implemented method for generating a search suggestion, the method comprising:

generating, by one or more processors, native application history data for a plurality of native applications at a first user device, the native application history data describing content presented by the plurality of native applications;

receiving, by one or more processors, a partial query in a search environment of a first native application of the plurality of native applications, the partial query being indicative of an incomplete search query;

providing, by the one or more processors, the partial query from the first native application, second native application history data associated with a second native application of the plurality of native applications and the native application history data associated with at least the first native application to a search service; and

receiving, by the one or more processors, one or more completed search query suggestions generated by the search service, the one or more completed search query suggestions being generated using the partial query from the first native application and the second native application history data associated with the second native application.

2. The computer-implemented method of claim 1 , further comprising

providing, by the one or more processors, the native history application history data for the plurality of native applications periodically to the search service in response to receiving a pull request from a pull API of the search service.

3. The computer-implemented method of claim 2 , wherein the native application history data is anonymized before providing the native application history data to the search service.

4. The computer-implemented method of claim 1 , wherein the native application history data is limited to a rate limit by the first user device over time.

5. The computer-implemented method of claim 1 , wherein the native application history data is generated in response to a user selecting content displayed in the plurality of native applications.

6. The computer-implemented method of claim 5 , wherein the native application history data is generated based on a usage report indicating a type of usage of content and a resource location of the content.

7. The computer-implemented method of claim 1 , wherein the native application history data includes native application history data for a second user device associated with a user of the first user device.

8. The computer-implemented method of claim 1 , further comprising:

providing, by the one or more processors, at least one search suggestion of one or more completed search suggestions to the second native application of the plurality of native applications; and

performing, by the one or more processors, a search in the second native application using the at least one search suggestion.

9. A computing system, comprising:

one or more processors; and

a non-transitory, computer-readable medium comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations, the operations comprising:

generating native application history data for a plurality of native applications at a first user device, the native application history data describing content presented by the plurality of native applications;

receiving a partial query in a search environment of a first native application of the plurality of native applications, the partial query being indicative of an incomplete search query;

providing the partial query from the first native application, second native application history data associated with a second native application of the plurality of native applications, and the native application history data associated with at least the first native application to a search service; and

receiving one or more completed search query suggestions generated by the search service, the one or more completed search query suggestions being generated using the partial query from the first native application and the second native application history data associated with the second native application.

10. The computing system of claim 9 , the operations further comprising

providing the native history application history data for the plurality of native applications periodically to the search service in response to receiving a pull request from a pull API of the search service.

11. The computing system of claim 10 , wherein the native application history data is anonymized before providing the native application history data to the search service.

12. The computing system of claim 10 , wherein the native application history data is limited to a rate limit by the first user device over time.

13. The computing system of claim 9 , wherein the native application history data is generated in response to a user selecting content displayed in the one or more native applications.

14. The computing system of claim 13 , wherein the native application history data is generated based on a usage report indicating a type of usage of content and a resource location of the content.

15. The computing system of claim 9 , wherein the native application history data includes native application history data for a second user device associated with a user of the first user device.

16. The computing system of claim 9 , the operations further comprising:

providing at least one search suggestion of one or more completed search suggestions to the second native application of the plurality of native applications; and

performing a search in the second native application using the at least one search suggestion.

17. A non-transitory, computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform operations, the operations comprising:

generating native application history data for a plurality of native applications at a first user device, the native application history data describing content presented by the plurality of native applications;

receiving a partial query in a search environment of a first native application of the plurality of native applications, the partial query being indicative of an incomplete search query;

providing the partial query and the native application history data associated with at least a second native application of the plurality of native applications to a search service, the second native application being different than the first native application; and

receiving one or more completed search query suggestions generated by the search service, the one or more completed search query suggestions being generated using the partial query and the native application history data associated with at least the second native application.

18. The non-transitory, computer-readable medium of claim 17 , the operations further comprising

providing the native history application history data for the plurality of native applications periodically to the search service in response to receiving a pull request from a pull API of the search service.

19. The non-transitory, computer-readable medium of claim 17 , wherein the native application history data is anonymized before providing the native application history data to the search service.

20. The non-transitory, computer-readable medium of claim 17 , wherein the native application history data is generated in response to a user selecting content displayed in the plurality of native applications.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 27, 2023
From: KIRAZCI, ULAS; HANSSON, OTHAR; HANSSON, ANTON
To: GOOGLE INC.
Reel/Frame 065368/0145 →
CHANGE OF NAME Recorded Oct 27, 2023
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 065385/0533 →
Continuity (6)
Continuation 17536199 · Nov 29, 2021
Continuation 16518379 · Jul 22, 2019
Continuation 15860409 · Jan 2, 2018
Continuation 14747956 · Jun 23, 2015
Provisional Application 62017242 · Jun 25, 2014
Related Publication 20240346055A1 · Oct 17, 2024
References Cited (49)
US 7617225B2 · Arrouye · 2009 [cited by applicant]
US 8086957B2 · Bauchot · 2011 [cited by applicant]
US 8458384B2 · Johnson · 2013 [cited by applicant]
US 8510764B1 · Deselaers · 2013 [cited by applicant]
US 8515979B2 · Mehta · 2013 [cited by applicant]
US 8554345B2 · Fernandez · 2013 [cited by applicant]
US 8595450B2 · Nguyen · 2013 [cited by applicant]
US 20040030882A1 · Forman · 2004 [cited by applicant]
US 20070209080A1 · Ture et al. · 2007 [cited by applicant]
US 20100257466A1 · Wroblewski et al. · 2010 [cited by applicant]
US 20100306191A1 · LeBeau et al. · 2010 [cited by applicant]
US 20110055189A1 · Effrat et al. · 2011 [cited by applicant]
US 20110252038A1 · Schmidt et al. · 2011 [cited by applicant]
US 20110314004A1 · Mehta · 2011 [cited by applicant]
US 20120124061A1 · Macbeth et al. · 2012 [cited by applicant]
US 20120179706A1 · Hobbs et al. · 2012 [cited by applicant]
US 20120179955A1 · French et al. · 2012 [cited by applicant]
US 20120290584A1 · De Bona et al. · 2012 [cited by applicant]
US 20120316955A1 · Panguluri et al. · 2012 [cited by applicant]
US 20120323898A1 · Kumar et al. · 2012 [cited by applicant]
US 20130006897A1 · Jain et al. · 2013 [cited by applicant]
US 20130054555A1 · Guha · 2013 [cited by examiner]
US 20130110815A1 · Tankovich et al. · 2013 [cited by applicant]
US 20130111328A1 · Khanna et al. · 2013 [cited by applicant]
US 20130122861A1 · Kim et al. · 2013 [cited by applicant]
US 20130124606A1 · Carpenter et al. · 2013 [cited by applicant]
US 20130191360A1 · Burkard et al. · 2013 [cited by applicant]
US 20130212081A1 · Shenoy et al. · 2013 [cited by applicant]
US 20130232256A1 · Lee et al. · 2013 [cited by applicant]
US 20130298007A1 · Cullen et al. · 2013 [cited by applicant]
US 20130325856A1 · Matamala et al. · 2013 [cited by applicant]
US 20140172562A1 · Weatherford · 2014 [cited by applicant]
EP 2474905 · 2012 [cited by applicant]
EP 2495670 · 2012 [cited by applicant]
“Adding deep linking to Google+ posts shared from your iOS app, ”[online][Retrieved on Jan. 7, 2014]; Retrieved from the Internet URL: https://developers.google.com/+/mobile/ios/share/deep-link; 3 pages. [cited by applicant]
“App Linking,” [online ][Retrieved on Jan. 7, 2014]; Retrieved from the Internet URL: https://developers.facebook.com/docs/android/link-to-your-native-app/; 14 pages. [cited by applicant]
“Class Gecko View Content,” [online][Retrieved on Jan. 2, 2014]; Retrieved from the Internet URL:people.mozilla. org/-mfinkl elgeckoview/docs/org/Mozilla/gecko/GeckoViewContent.html; 4 pages. [cited by applicant]
“Deeplink.me Lets Mobile Users Navigate Through a “Web” of Apps,” [online][Retrieved on Dec. 13, 2013]; Retrieved from the Internet URL: techcrunch.com/2013/05/22/new-servi ce-called-deeplink-me-will-let-mobile-users-na… [cited by applicant]
“Frequently Asked Questions—General Information,” [online][Retrieved on Jan. 7, 2014]; Retrieved from the Internet URL: https://linksmanager.com/Frequently+Asked+Questi ons+-+General +Information; 8 pages. [cited by applicant]
“Google's Search Results Can Deep-Link to Your Android Apps, ”[online][Retrieved on Dec. 13, 2013]; Retrieved from the Internet URL: techcrunch.com/2013/10/31/android-4-4-kitkat-app-indexing/; 6 pages. [cited by applicant]
“How to determine when an application is fully launched?” [online][Retrieved on Jan. 2, 2014]; Retrieved from the Internet URL: social.msdn.microsoft.com/Forums/en-US/27e7353-eb4b-4e23-bf56-84f3efbbecba/how-to-determine… [cited by applicant]
“How to get a deep link of my application from the Windows Phone Marketplace using NET code?” [online][Retrieved on Dec. 13, 2013]; Retrieved from stackoverflow.com/questions/13639564/how-to-get-a-deep-link-of-my-applic… [cited by applicant]
“Indexing apps just like websites,” [online][Retrieved on Dec. 13, 2013]; Retrieved from the Internet URL:googlewebmastercentral.blogspot.com/2013/10/indexing-apps-just-like-websites.html; 4 pages. [cited by applicant]
“Instant Pages on Google Chrome,” [online][Retrieved on Dec. 16, 2013]; Retrieved from the Internet URL: chrome.blogspot.jp/2011/08/instant-pages-on- google-chrome.html; 3 pages. [cited by applicant]
“Mobile deep linking,” [online][Retrieved on Dec. 13, 2013]; Retrieved from the Internet URL: en.wikipedia.org/wiki/Mobile deep linking; 2 pages. [cited by applicant]
“NSApplication Class Reference,” [online][Retrieved on Jan. 2, 2014]; Retrieved from the Internet URL: https://developer.apple.com/library/mac/documentation/cocoa/reference/applicationkit/classes/NSApplication Class/Ref… [cited by applicant]
“Ready for a “Web” of Apps? Quixey Launches AppURL, A New Way to Enable Deep Linking Across Mobile Applications,” [online][Retrieved on Dec. 13, 2013]; Retrieved from the Internet URL: techcrunch.com/2013/08/02/ready-fo… [cited by applicant]
“Seven Tips for Supercharging Your Links,” [online][Retrieved on Jan. 7, 2014]; Retrieved from the Internet URL: goarticles.com/article/Seven-Tips-For- Supercharging-Your-Links/3056299/; 5 pages. [cited by applicant]
“Sharing to Google+ from your Android app,” [online][Retrieved on Jan. 7, 2014]; Retrieved from the Internet URL: https://<levelopers.google.com/+/mobilelandroid/share/#handling_incoming_deep_links; 2 pages. [cited by applicant]