IP Library › Granted Patent US 12,596,556
Granted Patent B2
US 12,596,556 · App. 18/479,254 · Granted Apr 7, 2026

System and method for automatically synchronizing responses to conditions on devices

Inventors: Jeffrey Brown (Mountain View, CA); Kristopher Giesing (Palo Alto, CA); Steffen Meschkat (Menlo Park, CA); Alhaad Gokhale (Sunnyvale, CA)
Assignee: GOOGLE LLC
G06F9/44526G06F8/61G06F16/178H04L7/0008H04L69/329H04L67/02
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,596,556
App. No.
18/479,254
Granted
Apr 7, 2026
Kind
B2
Abstract

A system and method are provided that permits different devices with different applications to respond to the occurrence of a condition in a similar manner. By way of example, trigger data may be synchronized across multiple devices, wherein trigger data identifies information to be provided to a program in response to the occurrence of a condition. If a program is not installed or running on a particular device when the trigger occurs, the device automatically installs and executes the application.

Claims (26)

1 . A method comprising:

modifying, by one or more processors of a first computing device, trigger data encapsulated by a first ledger stored in a first memory of the first computing device, wherein the modified trigger data is associated with a particular user of one or more users of the first computing device, the trigger data including one or more triggers, and each trigger being an association between a program installed on the first computing device and a detectable condition that may occur on the program including a notification corresponding to an event or action associated with an operation of the program, wherein the program is installed on the first computing device and not installed on a second computing device; and

instructing, by the one or more processors, the second computing device to synchronize a second ledger stored in a second memory of the second computing device to match the first ledger, wherein each of the first and second computing devices is configured to respond to an occurrence of one trigger of the one or more triggers included in the modified trigger data when the detectable condition corresponding to the one trigger is detected.

2 . The method of claim 1 , wherein the modifying includes adding an electronic communication trigger to the trigger data.

3 . The method of claim 1 , wherein the second computing device is configured to respond to the occurrence of the one trigger of the one or more triggers included in the modified trigger data by generating the notification for presentation to the particular user.

4 . The method of claim 1 , wherein an identifier of the program installed on the first computing device is a URL.

5 . The method of claim 1 , wherein the modified trigger data is associated with a value of a message to be provided to the program installed on the first computing device when the detectable condition occurs.

6 . The method of claim 1 , wherein the one trigger of the one or more triggers is associated with a set of parameters that define information to be included in a message.

7 . The method of claim 6 , wherein the message includes an indication that the detectable condition associated with the one trigger has occurred.

8 . The method of claim 1 , wherein each of the first ledger and the second ledger is associated with a one or more users.

9 . The method of claim 1 , wherein the one trigger of the one or more triggers includes a new email trigger that relies on a push notification from an email server to determine whether the detectable condition associated with the one trigger has occurred.

10 . A first computing device comprising:

a first memory; and

one or more processors operably coupled to the first memory, the one or more processors being configured to:

modify trigger data encapsulated by a first ledger stored in the first memory, wherein the modified trigger data is associated with a particular user of one or more users of the first computing device, the trigger data including one or more triggers, and each trigger being an association between a program installed on the first computing device and a detectable condition that may occur on the program including a notification corresponding to an event or action associated with an operation of the program, wherein the program is installed on the first computing device and not installed on a second computing device; and

instruct the second computing device to synchronize a second ledger stored in a second memory of the second computing device to match the first ledger, wherein each of the first and second computing devices is configured to respond to an occurrence of one trigger of the one or more triggers included in the modified trigger data when the detectable condition corresponding to the one trigger is detected.

11 . The first computing device of claim 10 , wherein the one or more processors are configured to modify the trigger data by adding an electronic communication trigger to the trigger data.

12 . The first computing device of claim 10 , wherein the second computing device is configured to respond to the occurrence of the one trigger of the one or more triggers included in the modified trigger data by generating the notification for presentation to the particular user.

13 . The first computing device of claim 10 , wherein an identifier of the program installed on the first computing device is a URL.

14 . The first computing device of claim 10 , wherein the modified trigger data is associated with a value of a message to be provided to the program installed on the first computing device when the detectable condition occurs.

15 . The first computing device of claim 10 , wherein the one trigger of the one or more triggers is associated with a set of parameters that define information to be included in a message.

16 . The first computing device of claim 15 , wherein the message includes an indication that the detectable condition associated with the one trigger of the one or more triggers has occurred.

17 . The first computing device of claim 10 , wherein the one or more triggers include a new email trigger that relies on a push notifications from an email server to determine whether the detectable condition associated with the one trigger of the one or more triggers has occurred.

18 . A non-transitory computing-device readable storage medium on which computing-device readable instructions are stored, the instructions, when executed by one or more processors, cause the one or more processors to perform a method that includes:

modifying trigger data encapsulated by a first ledger stored in a first memory of a first computing device, wherein the modified trigger data is associated with a particular user of one or more users of the first computing device, the trigger data including one or more triggers, and each trigger being an association between a program installed on the first computing device and a detectable condition that may occur on the program including a notification corresponding to an event or action associated with an operation of the program, wherein the program is installed on the first computing device and not installed on a second computing device; and

instructing the second computing device to synchronize a second ledger stored in a second memory of the second computing device to match the first ledger, wherein each of the first and second computing devices is configured to respond to an occurrence of one trigger of the one or more triggers included in the modified trigger data when the detectable condition corresponding to the one trigger is detected.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 3, 2023
From: BROWN, JEFFREY; GIESING, KRISTOPHER; MESCHKAT, STEFFEN; GOKHALE, ALHAAD
To: GOOGLE LLC
Reel/Frame 065102/0552 →
Continuity (3)
Continuation 17078178 · Oct 23, 2020
Continuation 15808153 · Nov 9, 2017
Related Publication 20240031120A1 · Jan 25, 2024
References Cited (36)
US 10061613B1 · Brooker et al. · 2018 [cited by applicant]
US 10606660B1 · Hartley et al. · 2020 [cited by applicant]
US 20020194334A1 · Focant · 2002 [cited by examiner]
US 20090158099A1 · Cui · 2009 [cited by examiner]
US 20100011352A1 · Chu et al. · 2010 [cited by applicant]
US 20120102153A1 · Kemp · 2012 [cited by examiner]
US 20130055237A1 · Fei et al. · 2013 [cited by applicant]
US 20130275553A1 · Shilo · 2013 [cited by examiner]
US 20130326502A1 · Brunsman · 2013 [cited by examiner]
US 20140359602A1 · Sawaya et al. · 2014 [cited by applicant]
US 20150113034A1 · Tome · 2015 [cited by examiner]
US 20170140408A1 · Wuehler · 2017 [cited by applicant]
US 20180088928A1 · Smith · 2018 [cited by examiner]
US 20180316637A1 · Desjardins · 2018 [cited by examiner]
CN 1781118A · 2006 [cited by applicant]
CN 1892652A · 2007 [cited by applicant]
CN 101763283A · 2010 [cited by applicant]
CN 103457994A · 2013 [cited by applicant]
CN 103514010A · 2014 [cited by applicant]
CN 106100909A · 2016 [cited by applicant]
JP 2016126419A · 2016 [cited by examiner]
SG 65350 · 1999 [cited by applicant]
WO WO2012105764A2 · 2012 [cited by examiner]
WO 2012105764A3 · 2012 [cited by applicant]
WO 2015078281A1 · 2015 [cited by applicant]
“Fuchsia-mirror/ledger/docs”, [online]. Retrieved Nov. 30, 2017. Retrieved from the internet: <https://github.comFuchsia-mirror/ledger/blob/20244de98604f39aaa261 bf6ab4e30cbbf1 b0a7f/docs/workflow .md>, 1 page, Oct. 27,… [cited by applicant]
“Fuchsia-mirror/ledger/docs/user_guide”, [online]. Retrieved Nov. 30, 2017. Retrieved from the internet: <ledger/user_guide.md at 20244de98604f39aaa261bf6ab4e30cbbf1 b0a7f-fuchsia-mirror/ledger-GitHub>, 1 page, Oct. 27,… [cited by applicant]
“Fuchsia-mirror/ledger/READEME”, [online]. Retrieved Nov. 30, 2017. Retrieved from the internet: <https://github.com/fuchsia-mirror/ledger/blob/20244de98604f39aaa261 bf6ab4e30cbbf1 b0a7f/README.md>, 1 page, Nov. 8, 2016. [cited by applicant]
“Fuchsia-mirror/ledger/services”, [online]. Retrieved Nov. 30, 2017. Retrieved from the internet: <https://github.com/fuchsia-mirror/ledger/blob/20244de98604f39aaa261 bf6ab4e30cbbf1b0a 7f/services/ledger.fidl>, 5 pages,… [cited by applicant]
“Fuchsia-mirror/ledger/src”, [online]. Retrieved Nov. 30, 2017. Retrieved from the internet: <https://github.com/fuchsia-mirror/ledger/tree/20244de98604f39aaa261 bf6ab4e30cbbf1 b0a7f/src>, 1 page, Nov. 8, 2016. [cited by applicant]
EP Office Action for Application No. 18762954.8 dated Nov. 20, 2020. [cited by applicant]
Extended European Search Report for Application No. EP22182809 dated Oct. 7, 2022. [cited by applicant]
International Search Report and Written Opinion for PCT Application No. PCT/US2018/045774, dated Nov. 22, 2018. 14 pages. [cited by applicant]
Ketan Bhardwaj, Ada Gavrilovska and Karsten Schwan, Ephemeral Apps, 2016, 6 pages. [cited by applicant]
Notice of Grant for Chinese Patent Application No. 201880027939.3, Apr. 20, 2023. [cited by applicant]
The First Office Action for Chinese Patent Application No. 201880027939.3, Sep. 14, 2022. [cited by applicant]