Context-based notification processing system
Abstract
In some implementations, a method may involve determining first feature vectors for a plurality of data items accessed by a user of one or more client devices, the first feature vectors representing first contextual data about the one or more client devices at times that respective data items of the plurality of data items were accessed, the plurality of data items including a first data item. A predictive model, configured to classify input feature vectors into context types, may be used to determine that the first feature vector for the first data item is classified as a first context type. A second feature vector representing second contextual data about a first client device operated by the user may be determined and the predictive model may be used to determined that the second feature vector is classified as the first context type. Based at least in part on the first and second feature vectors being classified as the first context type and the first and second data items being of a first data item type, the first client device may be caused to present the second data item.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method, comprising:
generating, by a computing system, at least first and second notifications to be sent to a client device operated by a user, the first and second notifications indicating, respectively, first and second events of first and second applications accessible by the user; receiving, by the computing system from the client device, first data indicative of a current context of the client device; and sending, by the computing system and based at least in part on the first data, the first notification, but not the second notification, to the client device.
2 . The method of claim 1 , wherein generating the first and second notifications further comprises:
causing the first and second notifications to include respective user interface elements enabling the user to take corresponding actions with respect to the first and second applications.
3 . The method of claim 1 , wherein the first data comprises at least one of an identifier of the client device, a current time, a network to which the client device is connected, or a location of the client device.
4 . The method of claim 1 , further comprising:
prior to receiving the first data, receiving, by the computing system, second data indicative of one or more other notifications accessed by the user operating one or more client devices, and a context of the one or more client devices when the one or more other notifications were accessed by the user; wherein sending the first notification, but not the second notification, to the client device is further based at least in part on the second data.
5 . The method of claim 1 , further comprising:
receiving, from the client device, a request for a context-based view of an activity feed of notifications, the request including the first data; wherein sending the first notification to the client device is performed in response to the request.
6 . The method of claim 1 , further comprising:
retrieving, by the computing system, second data from the first application using first access credentials associated with the user; determining, by the computing system, that the second data is indicative of the first event; retrieving, by the computing system, third data from the second application using second access credentials associated with the user; and determining, by the computing system, that the third data is indicative of the second event.
7 . The method of claim 6 , wherein:
the computing system retrieves the second data from first application via a first application programming interface (API) of the first application; and the computing system retrieves the third data from second application via a second API of the second application.
8 . A system, comprising:
at least one processor; and at least one computer-readable medium encoded with instructions which, when executed by the at least one processor, cause the system to:
generate at least first and second notifications to be sent to a client device operated by a user, the first and second notifications indicating, respectively, first and second events of first and second applications accessible by the user,
receive, from the client device, first data indicative of a current context of the client device, and
send, based at least in part on the first data, the first notification, but not the second notification, to the client device.
9 . The system of claim 8 , wherein the at least one computer-readable medium is further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
cause the first and second notifications to include respective user interface elements enabling the user to take corresponding actions with respect to the first and second applications.
10 . The system of claim 8 , wherein the first data comprises at least one of an identifier of the client device, a current time, a network to which the client device is connected, or a location of the client device.
11 . The system of claim 8 , wherein the at least one computer-readable medium is further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
prior to receiving the first data, receive second data indicative of one or more other notifications accessed by the user operating one or more client devices, and a context of the one or more client devices when the one or more other notifications were accessed by the user; and send the first notification, but not the second notification, to the client device further based at least in part on the second data.
12 . The system of claim 8 , wherein the at least one computer-readable medium is further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
receive, from the client device, a request for a context-based view of an activity feed of notifications, the request including the first data; and send the first notification to the client device in response to the request.
13 . The system of claim 8 , wherein the at least one computer-readable medium is further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
retrieve second data from the first application using first access credentials associated with the user; determine that the second data is indicative of the first event; retrieve third data from the second application using second access credentials associated with the user; and determine that the third data is indicative of the second event.
14 . The system of claim 13 , wherein the at least one computer-readable medium is further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
retrieve the second data from first application via a first application programming interface (API) of the first application; and retrieve the third data from second application via a second API of the second application.
15 . At least one non-transitory computer-readable medium encoded with instructions which, when executed by at least one processor of a system, cause the system to:
generate at least first and second notifications to be sent to a client device operated by a user, the first and second notifications indicating, respectively, first and second events of first and second applications accessible by the user; receive, from the client device, first data indicative of a current context of the client device; and send, based at least in part on the first data, the first notification, but not the second notification, to the client device.
16 . The at least one non-transitory computer-readable medium of claim 15 , further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
cause the first and second notifications to include respective user interface elements enabling the user to take corresponding actions with respect to the first and second applications.
17 . The at least one non-transitory computer-readable medium of claim 15 , wherein the first data comprises at least one of an identifier of the client device, a current time, a network to which the client device is connected, or a location of the client device.
18 . The at least one non-transitory computer-readable medium of claim 15 , further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
prior to receiving the first data, receive second data indicative of one or more other notifications accessed by the user operating one or more client devices, and a context of the one or more client devices when the one or more other notifications were accessed by the user; and send the first notification, but not the second notification, to the client device further based at least in part on the second data.
19 . The at least one non-transitory computer-readable medium of claim 15 , further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
retrieve second data from the first application using first access credentials associated with the user; determine that the second data is indicative of the first event; retrieve third data from the second application using second access credentials associated with the user; and determine that the third data is indicative of the second event.
20 . The at least one non-transitory computer-readable medium of claim 19 , further encoded with additional instructions which, when executed by the at least one processor, further cause the system to:
retrieve the second data from first application via a first application programming interface (API) of the first application; and retrieve the third data from second application via a second API of the second application.Join the waitlist — get patent alerts
Track US2022261300A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.