Web-Based Push Messaging Methods and Systems

• US 20120191790A1
• Filed: 01/23/2012
• Published: 07/26/2012
• Est. Priority Date: 01/24/2011
• Status: Abandoned Application

• Current Assignee: AppMobi IPLC, Inc.
• Original Assignee: appMobi Inc
• Inventors: Abadir, Essam Ernest, Schock, Rosco
• Application Number:
  US13/356,412
• Publication Number:
  US 20120191790A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 51/214 using selective forwarding

Abstract

A system capable of coordinating push messages from among a plurality of sources is disclosed. The system includes a push message server communicatively connected to a plurality of publishers. The push message server includes a push subscription database containing a plurality of records, each record associating a user identity with a push message publisher and a user preference for receiving push messages from the publisher. The push message server also includes a communication component configured to receive push messages from one or more of the plurality of publishers and, based on user subscriptions managed in the push subscription database, transmit the push messages to one or more subscribers.

Claims

1. A system capable of coordinating push messages from among a plurality of sources, the system comprising:

a push message server communicatively connected to a plurality of publishers, the push message server including;

a push subscription database containing a plurality of records, each record associating a user identity with a push message publisher and a user preference for receiving push messages from the publisher;

a communication component configured to receive push messages from one or more of the plurality of publishers and, based on user subscriptions managed in the push subscription database, transmit the push messages to one or more subscribers.

2. The system of claim 1, wherein the push subscription database includes contact information for each of the one or more subscribers.

3. The system of claim 1, wherein the push message server is remote from each of the plurality of subscribers.

4. The system of claim 1, further comprising a push-enabled browser component installable at a subscriber device, wherein the push-enabled browser is configured to access information at one or more websites associated with the plurality of publishers and allow the subscriber to subscribe to push messages from one or more of the plurality of publishers.

5. The system of claim 4, wherein the push-enabled browser executes on a mobile device remote from the push message server.

6. The system of claim 5, wherein the push-enabled browser is capable of receiving push messages from the communication component of the push message server when the push-enabled browser is not running.

7. A method of distributing push messages to one or more users, the method comprising:

receiving at a push message server a push message and an identity of one or more intended recipients from a publisher;

checking the identity against a list of subscribed users to determine a list of one or more recipients of the push message; and

queuing the message for transmission to each of the one or more recipients.

8. The method of claim 7, further comprising transmitting the message to each of the one or more recipients.

9. The method of claim 7, further comprising receiving a subscription request associated with a user, the subscription request identifying a publisher from which the user wishes to receive push messages.

10. The method of claim 9, wherein receiving the subscription request comprises receiving a subscription request from a publisher, the subscription request further identifying a user associated with the subscription request.

11. The method of claim 7, further comprising, for each recipient, determining if a user device is active and, upon determining that the user device is active, transmitting the message to the recipient associated with that user device.

12. The method of claim 7, further comprising, for each recipient, determining if a user device is active and, upon determining that the user device is unavailable, maintaining the message in a push message queue for later transmission to the user device.

13. A method of sending push messages comprising:

receiving an indication from a user device at a publisher indicating an intent to subscribe to push messages associated with the publisher;

transmitting a subscription request to a push message server, the subscription request including information identifying the user, the publisher, and an intent to subscribe to push messages associated with the publisher;

transmitting a push message to the push message server alongside an identity of the user, thereby causing the push message server to transmit a push message to a push-enabled web browser of a user device.

14. The method of claim 13, wherein the user device is a mobile device.

15. The method of claim 13, wherein the information identifying the publisher includes domain information.

16. The method of claim 13, wherein the information identifying the publisher includes web page information.

17. The method of claim 13, wherein the information identifying the user includes a user identifier.

18. The method of claim 17, wherein the information identifying the user lacks user contact information.

19. The method of claim 13, further comprising storing at least some of the subscription request in a database at a push message server.

20. The method of claim 13, further comprising prompting a user to subscribe to push messages associated with the publisher prior to receiving the indication from the user device.

21. A method of receiving push messages comprising:

installing a push-enabled web browser at a mobile device;

visiting a web domain of a publisher;

taking one or more actions indicating a desire to subscribe to push messages associated with the publisher; and

at a later time, and after one or more push messages is transmitted from the publisher to a push message server, receiving a push message from the push message server that is originated from the publisher without transmitting a request to the push message server.