Mobile messaging platform

• US 20100159961A1
• Filed: 12/18/2008
• Published: 06/24/2010
• Est. Priority Date: 12/18/2008
• Status: Active Grant

• Current Assignee: Bamtech LLC (The Walt Disney Company)
• Original Assignee: MLB Advanced Media, L.P. (Major League Baseball)
• Inventors: Evans, Charles, Hochberg, Lincoln, Ritter, Adam D., Schoenherr, Jeremy Hunt, Pesin, Tracy, Spychala, Robert, Bowman, Robert A.
• Granted Patent: US 9,397,860 B2
• Time in Patent Office: Days
• US Class Current: 455/466
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

A method for providing mobile messages includes generating a message based on received content. A first functional bind to an aggregator is identified. A second functional bind to the aggregator is also identified. The first functional bind and the second functional bind are distinct communication connections to the aggregator. First message recipients are associated with the first functional bind, and second message recipients are associated with the second functional bind. The message is provided in parallel to the aggregator for the first message recipients through the first functional bind and for the second message recipients through the second functional bind.

Claims

1. A method for providing mobile messages comprising:

generating a message based on received content;

identifying a first functional bind to an aggregator;

identifying a second functional bind to the aggregator, wherein the first functional bind and the second functional bind are distinct communication connections;

associating first message recipients with the first functional bind;

associating second message recipients with the second functional bind; and

providing the message in parallel to the aggregator for the first message recipients through the first functional bind and for the second message recipients through the second functional bind.

2. The method of claim 1, further comprising receiving the received content from one of a plurality of content sources.

3. The method of claim 1, further comprising:

identifying a total number of subscribers;

dividing the total number of subscribers into a plurality of groups, wherein the plurality of groups includes a first group of subscribers and a second group of subscribers;

identifying the first message recipients within the first group of subscribers; and

identifying the second message recipients within the second group of subscribers.

4. The method of claim 3, wherein the total number of subscribers is divided into the plurality of groups based on a number of functional binds to the aggregator.

5. The method of claim 3, wherein the first message recipients and the second message recipients are identified in parallel.

6. A mobile messaging system comprising:

a mobile messaging platform comprising

a connectivity engine configured to establish a plurality of binds to an aggregator;

a bridge framework enterprise service bus in communication with the connectivity engine and configured to receive content from a content source; and

a publishing engine in communication with the bridge framework enterprise service bus and configured to

generate a message based on the received content; and

provide the generated message to the aggregator through at least two of the plurality of binds in parallel.

7. The system of claim 6, wherein the connectivity engine is further configured to:

monitor the plurality of binds;

based on the monitoring, identify a non-functional bind in the plurality of binds; and

inform the publishing engine of the non-functional bind such that the generated message is not provided to the aggregator through the non-functional bind.

8. The system of claim 6, wherein the received content comprises first content having a first format, and further wherein the bridge framework enterprise service bus is configured to:

receive second content having a second format from a second content source;

convert the first content into a third format for generation of the message; and

convert the second content into the third format for generation of a second message.

9. The system of claim 6, wherein the connectivity engine is further configured to establish a second plurality of binds with a carrier, and further wherein the publishing engine is configured to provide the generated message to the carrier through at least two of the second plurality of binds in parallel.

10. The system of claim 6, wherein the publishing engine is further configured to:

identify a total number of subscribers;

divide the total number of subscribers into a plurality of groups, wherein the plurality of groups includes a first group of subscribers and a second group of subscribers;

identify first message recipients within the first group of subscribers; and

identify second message recipients within the second group of subscribers;

wherein the generated message is provided to the aggregator through a first bind of the plurality of binds and a second bind of the plurality of binds in parallel, wherein the first bind is used for the first message recipients and the second bind is used for the second message recipients.

11. The system of claim 6, further comprising:

the content source; and

the aggregator, wherein the aggregator is configured to

receive the generated message from the publishing engine through a first bind of the plurality of binds between the aggregator and the mobile messaging platform;

receive the generated message from the publishing engine through a second bind of the plurality of binds between the aggregator and the mobile messaging platform;

provide the generated message received through the first bind to a first carrier; and

provide the generated message received through the second bind to a second carrier.

12. A computer-readable medium having computer-readable instructions stored thereon, wherein, upon execution by a processor, the computer-readable instructions cause the processor to:

establish a plurality of binds with an aggregator;

receive content from a content source;

generate a message based on the received content; and

provide the generated message to the aggregator through at least two of the plurality of binds in parallel.

13. The computer-readable medium of claim 12, wherein the processor is further caused to:

identify a total number of subscribers;

divide the total number of subscribers into a plurality of groups, wherein the plurality of groups includes a first group of subscribers and a second group of subscribers;

identify first message recipients within the first group of subscribers; and

identify second message recipients within the second group of subscribers;

wherein the generated message is provided to the aggregator through a first bind of the plurality of binds and a second bind of the plurality of binds in parallel, wherein the first bind is used for the first message recipients and the second bind is used for the second message recipients.

14. The computer-readable medium of claim 12, wherein the processor is further caused to:

monitor the plurality of binds;

based on the monitoring, identify a non-functional bind in the plurality of binds; and

provide the generated message to the aggregator without using the non-functional bind.

15. The computer-readable medium of claim 12, wherein the received content comprises first content having a first format, and further wherein the processor is caused to:

receive second content having a second format from a second content source;

convert the first content into a third format for generation of the message; and

convert the second content into the third format for generation of a second message.

16. A method for maintaining service subscribers, the method comprising:

identifying first information associated with a first subscriber device of a subscriber to a messaging service;

establishing a subscriber profile based at least in part on the identified first information;

receiving second information from the subscriber;

comparing the second information to the subscriber profile;

determining, based on the comparison, whether the second information was received from the first subscriber device or a second subscriber device;

if the second information was received from the second subscriber device, automatically updating the subscriber profile to associate the subscriber with the second subscriber device.

17. The method of claim 16, further comprising:

receiving a subscription request for the messaging service from the first subscriber device;

providing a response to the subscription request, wherein the response includes a link;

identifying an activation of the link by the first subscriber device, wherein the first information associated with the first subscriber device is identified based on the activation of the link.

18. The method of claim 16, further comprising identifying third information associated with a carrier used by the subscriber, wherein the subscriber profile is based at least in part on the third information.

19. The method of claim 16, wherein the first information includes a telephone number of the first subscriber device and a capability of the first subscriber device.

20. The method of 16, wherein automatically updating the subscriber profile further comprises replacing at least a portion of the first information that is specific to the first subscriber device with at least a portion of the second information that is specific to the second subscriber device.