Mobile push notification

Patent metadata

Field	Value
Publication number	US-9232339-B2
Application number	US-201313761695-A
Country	US
Kind code	B2
Filing date	Feb 7, 2013
Priority date	Feb 7, 2013
Publication date	Jan 5, 2016
Grant date	Jan 5, 2016

Abstract

Systems and methods are described herein that provide a mobile push notification system that sends notifications to various types of mobile devices using a single cloud based interface. One example embodiment includes a registration logic configured to receive device data from a mobile device. A record of the device data is stored in a database. A token generator creates a registration token that identifies the mobile device. The registration logic is facilitates communication between the mobile device and a vendor service when the registration token is received from the mobile device.

First claim

What is claimed is:

1. A non-transitory computer-readable medium storing computer-executable instructions that when executed by a computer cause the computer to perform functions, the instructions comprising:
instructions for receiving, from a mobile device, a registration request that includes device data and a registration token that uniquely identifies the mobile device;
instructions for accessing a database that stores a registration record for the mobile device that includes the registration token and identifies an operating system of the mobile device;
instructions for accessing a central memory that stores security certificates for a plurality of operating systems and identifying a security certificate mapped to the operation system of the mobile device; and
instructions for, in response to the request, providing the security certificate to the mobile device for use in subscribing to push notifications;
such that security certificates for operating systems not utilized by the mobile device are not stored on the mobile device.

2. The non-transitory computer-readable medium of claim 1 , where the device data includes a vendor service name, a target descriptor that specifies an operating system of the mobile device, and the name of an application registered with a vendor service.

3. The non-transitory computer-readable medium of claim 1 , where the registration record includes a registration identification number resolved from the registration token.

4. The non-transitory computer-readable medium of claim 1 , where the instructions further comprise:
instructions for identifying a registration date for the mobile device based, based at least in part, on the device data;
instructions for determining whether the registration date is older than a deactivation date, where the deactivation date is a point in time that the mobile device is barred from receiving a push notifications; and
instructions for, in response to determining that the mobile device has not been previously registered, creating a registration token that identifies the mobile device.

5. A computing system, comprising:
a registration logic configured to receive a registration request that includes a registration token that uniquely describes a mobile device;
a database configured to store a registration record that includes device data that identifies an operating system of the mobile device mapped to the registration token;
memory configured to store security certificates for a plurality of operating systems;
where the registration logic is configured to, in response to the registration request, provide the security certificate for the mobile device's operating system to the mobile device for use in subscribing to push notifications, such that security certificates for operating systems not utilized by the mobile device are not stored on the mobile device.

6. The computing system of claim 5 , where the device data includes a vendor service name, a target descriptor that specifies an operating system of the mobile device, and a name of an application registered with a vendor service.

7. The computing system of claim 5 , further comprising:
a feedback logic configured to determine whether the mobile device is inactive by accessing a list of devices that are not to receive push notifications.

8. The computing system of claim 7 , where the feedback logic is configured to use the device data in the registration record to determine whether the mobile device is inactive.

9. The computing system of claim 8 , where the device data includes a registration date and where the feedback logic is configured to, in response to the registration date being older than a de-activation date, recording that the mobile device inactive.

10. A computer-implemented method, comprising:
instructions for receiving, from a mobile device, a registration request that includes device data and a registration token that uniquely identifies the mobile device;
instructions for accessing a database that stores a registration record for the mobile device that includes the registration token and identifies an operating system of the mobile device;
instructions for accessing a central memory that stores security certificates for a plurality of operating systems and identifying a security certificate mapped to the operation system of the mobile; and
instructions for, in response to the request, providing the security certificate to the mobile device for use in subscribing to push notifications;
such that security certificates for operating systems not utilized by the mobile device are not stored on the mobile device.

11. The computer-implemented method of claim 10 , where the device data includes a vendor service name, a target descriptor that specifies an operating system of the mobile device, and the name of an application registered with a vendor service.

12. The computer-implemented method of claim 10 , where the registration record includes a registration identification number resolved from the registration token.

13. The computer-implemented method of claim 10 , further comprising:
identifying a registration date for the mobile device based, based at least in part, on the device data;
instructions for determining whether the registration date is older than a deactivation date, where the deactivation date is a point in time that the mobile device is barred from receiving a push notifications; and
instructions for, in response to determining that the mobile device has not been previously registered, creating a registration token that identifies the mobile device.

Assignees

• Oracle Int Corp

Inventors

• Lynes Matthew
• Huang Chris
• Thomas Jayant
• Matskiv Victor

Classifications

• G06F16/9535 Primary

  Search customisation based on user profiles and personalisation · CPC title

• H04L12/1859

  adapted to provide push services, e.g. data channels · CPC title

• H04L51/00

  User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail · CPC title

• H04L63/0807

  using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213) · CPC title

• H04L12/189

  in combination with wireless systems (selective distribution or broadcast in wireless communication networks H04W4/06) · CPC title