US 11,889,027 B2
Telephony web event system and method
Jeffrey Gordon Lawson, San Francisco, CA (US); John Robert Wolthuis, San Francisco, CA (US); and Evan Mansfield Cooke, San Francisco, CA (US)
Assigned to Twilio Inc., San Francisco, CA (US)
Filed by Twilio Inc., San Francisco, CA (US)
Filed on Mar. 22, 2023, as Appl. No. 18/125,026.
Application 18/125,026 is a continuation of application No. 17/301,335, filed on Mar. 31, 2021, granted, now 11,665,285.
Application 17/301,335 is a continuation of application No. 16/557,001, filed on Aug. 30, 2019, granted, now 11,005,998.
Application 16/557,001 is a continuation of application No. 16/241,746, filed on Jan. 7, 2019, granted, now 10,455,094.
Application 16/241,746 is a continuation of application No. 15/709,905, filed on Sep. 20, 2017, granted, now 10,187,530.
Application 15/709,905 is a continuation of application No. 15/193,416, filed on Jun. 27, 2016, granted, now 9,807,244.
Application 15/193,416 is a continuation of application No. 14/591,279, filed on Jan. 7, 2015, granted, now 9,407,597.
Application 14/591,279 is a continuation of application No. 12/572,258, filed on Oct. 1, 2009, granted, now 8,964,726.
Claims priority of provisional application 61/102,007, filed on Oct. 1, 2008.
Prior Publication US 2023/0231952 A1, Jul. 20, 2023
Int. Cl. H04M 7/00 (2006.01); H04L 12/66 (2006.01); H04M 3/22 (2006.01); H04M 15/00 (2006.01); H04L 51/52 (2022.01); H04L 67/02 (2022.01); H04M 7/12 (2006.01); H04M 3/42 (2006.01)
CPC H04M 7/0012 (2013.01) [H04L 12/66 (2013.01); H04L 51/52 (2022.05); H04L 67/02 (2013.01); H04M 3/2209 (2013.01); H04M 3/2218 (2013.01); H04M 7/006 (2013.01); H04M 15/00 (2013.01); H04M 15/44 (2013.01); H04M 15/90 (2013.01); H04M 3/42229 (2013.01); H04M 7/123 (2013.01); H04M 7/128 (2013.01); H04M 2215/0104 (2013.01); H04M 2215/016 (2013.01); H04M 2215/018 (2013.01)] 20 Claims
OG exemplary drawing
 
8. A system comprising:
a computing device configured to perform operations comprising:
receiving, from a client device and via a network, a request to subscribe to events of one or more event types, the request including an account identifier and having an appended first verification token;
determining, based on the account identifier, an encryption key;
generating, based on the encryption key and the request, a second verification token;
based on the appended first verification token matching the second verification token, establishing a subscription to events of the one or more event types; and
an event proxy server configured to perform operations comprising:
detecting an occurrence of an event of the one or more event types; and
based on the subscription having been established, sending a notification of the event to the client device.