Enhanced Curfew and Protection Associated with a Device Group
US-2017295258-A1 · Oct 12, 2017 · US
US11320968B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11320968-B2 |
| Application number | US-201916578841-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 23, 2019 |
| Priority date | Jan 27, 2014 |
| Publication date | May 3, 2022 |
| Grant date | May 3, 2022 |
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.
An actionable event notification disclosed herein provides actionable push notifications that allow an application server to collect information from end users. The actionable event notification includes a notification server that receives notification requests from application servers and communicates notifications to users where the notifications include specification for a notification UI form. In one implementation, the notification server modifies the callback identification on the notification from identification for the application server to identification for the notification server. A client device presents the notification UI form to a user to receive user responses. The user responses are communicated back to the notification server. The notification server processes the user responses and communicates them to the application server as necessary. Alternatively, the user responses are communicated directly to the application server requesting the notifications.
Opening claim text (preview).
What is claimed: 1. A processor-implemented method comprising: receiving, at a client device, a notification including a notification UI form specification, and a callback specification, the notification being sent to the client device in response to a notification request received from an application server associated with an application installed on the client device, and the callback specification specifying both an expected callback from a user in response to the notification and a uniform resource identifier (URI) or uniform resource locator (URL), the notification pertaining to the application installed on the client device; displaying, by the client device and without invoking the installed application, a notification UI form for the received notification and defined by the notification UI form specification in a user interface of the client device, the notification UI form including at least one input control; collecting user input associated with the installed application via the at least one input control of the notification UI form displayed in the user interface of the client device according to the callback specification without invoking the installed application; and communicating the collected user input to the application server associated with the installed application that the notification pertains to according to the callback specification without invoking the installed application. 2. The processor-implemented method of claim 1 further comprising: authenticating the received notification before displaying the notification UI form in the user interface of the client device. 3. The processor-implemented method of claim 1 further comprising: validating the received notification before displaying the notification UI form in the user interface of the client device. 4. The processor-implemented method of claim 1 wherein the collected user input is communicated to the application server. 5. The processor-implemented method of claim 1 wherein: the notification UI form allows a user to specify an alternative device at which to receive the notification; and the notification is a graphical display that pops up over part of a graphical user interface display of the client device. 6. The processor-implemented method of claim 1 wherein user interface elements of the notification UI form are transferred to the client device in a communication that is separate from receipt of the notification; and the notification is a graphical display that pops up over part of a graphical user interface display of the client device. 7. The processor-implemented method of claim 1 , wherein: the notification UI form includes a comment field to input text; and the notification is a graphical display that pops up over part of a graphical user interface display of the client device. 8. The processor-implemented method of claim 1 wherein the callback specification further specifies a notification server as a destination for responding to the notification, the method further comprising: communicating the collected user input to the notification server according to the callback specification. 9. A communications-network-connected client device comprising: a memory; one or more processor units; a notification server interface stored in the memory and executable by the one or more processor units, the notification server interface configured to receive a notification including a notification UI form specification and a callback specification, the notification being sent to the notification server interface in response to a notification request received from an application server associated with an application installed on the client device, the callback specification specifying both an expected callback from a user in response to the notification and a uniform resource identifier (URI) or uniform resource locator (URL), the notification pertaining to the application installed on the client device; a notification UI forms processing module stored in the memory and executable by the one or more processor units, the notification UI forms processing module configured to present a notification UI form for the received notification and defined by the notification UI form specification for display in a user interface of the client device without invoking the installed application, the notification UI form including at least one input control; and an input/output module stored in the memory and executable by the one or more processor units, the input/output module configured to collect user input associated with the installed application via the at least one input control of the notification UI form displayed in the user interface of the client device without invoking the installed application and to communicate the collected user input to the application server associated with the installed application that the notification pertains to according to the callback specification without invoking the installed application. 10. The communications-network-connected client device of claim 9 , wherein: the notification UI form includes a comment field to input text; and the notification is a graphical display that pops up over part of a graphical user interface display of the client device. 11. The communications-network-connected client device of claim 9 , wherein the callback specification further specifies the notification server as a destination for responding to the notification, the notification server interface being further configured to communicate the collected user input to the notification server according to the callback specification. 12. One or more tangible computer-readable storage media storing computer executable instructions for performing a computer process on a client device, the computer process comprising: receiving, at the client device, a notification including a notification UI form specification and a callback specification, the notification being sent to a client device in response to a notification request received from an application server associated with an application installed on the client device, and the callback specification specifying both an expected callback in response to the notification and a uniform resource identifier (URI) or uniform resource locator (URL), the notification pertaining to the application installed on the client device; displaying, by the client device and without invoking the installed application, a notification UI form for the received notification and defined by the notification UI form specification in a user interface of the client device, the notification UI form including at least one input control; collecting user input associated with the installed application via the at least one input control of the notification UI form displayed in the user interface of the client device according to the callback specification; and communicating the collected user input to the application server associated with the installed application that the notification pertains to according to the callback specification without invoking the installed application. 13. The one or more tangible computer-readable storage media of claim 12 wherein the computer process further comprises: validating the received notification before displaying the notification UI form in the user interface of the client computing device. 14. The one or more tangible computer-readable storage media of claim 12 wherein the collected user input is communicated to the application server. 15. The one or more tangible computer-readable storage media of claim 12 wherein: the notification UI form allow
Push-based network services · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
User profiles · CPC title
Targeted advertisements · CPC title
for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.