IP Library Granted Patent US 7,609,686
Granted Patent B1
US 7,609,686 · App. 10/978,322 · Granted Oct 27, 2009

Mass multimedia messaging

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,609,686
App. No.
10/978,322
Granted
Oct 27, 2009
Kind
B1
Abstract

A method and system of mass multimedia messaging in a system having a service provider and a plurality of subscriber communication terminals supported by the service provider, wherein at least some of the subscriber terminals have different messaging capabilities and different message format requirements. The method includes adaptation and handling of a mass multimedia message, and mass multimedia message notification. The system uses a retrieval platform and a processing platform. The retrieval platform generates a unique message identifier for the mass multimedia message, and pre-adapts the message into adapted content messages for the terminal types supported by the service provider. The processing platform formats message notifications for the subscriber terminals based on each terminal's messaging capabilities, with each notification containing the unique message identifier.

Claims (144)

1. A method of mass multimedia messaging in a system including a service provider and a plurality of terminals supported by the service provider, wherein at least some of said terminals are of terminal types have differing messaging capabilities and differing message format requirements, said method comprising:

receiving a multimedia message and a list of subscriber terminal addresses from a content provider;

generating a unique message identifier for said multimedia message;

adapting said multimedia message into adapted content messages for each supported terminal type using terminal format requirements information for the terminal types supported by the service provider;

indexing each said adapted content message with a corresponding terminal type identifier and said message identifier; and

formatting message notifications containing said message identifier for each subscriber address based on subscriber terminal messaging capabilities information for the corresponding subscriber terminals,

wherein said subscriber terminal messaging capabilities information includes information as to whether each subscriber terminal is SMS capable, WAP Push capable, or MMS capable, wherein said step of formatting each message notification further comprises:

determining if the subscriber terminal is capable of receiving MMS messages;

if it is determined that the subscriber terminal is capable of receiving MMS messages, then formatting the message notification as a MMS WAP Push notification;

if it is determined that the subscriber terminal is not capable of receiving MMS messages, then determining if the subscriber terminal is capable of receiving WAP Push messages;

if it is determined that the subscriber terminal is capable of receiving WAP Push messages, then formatting the message notification as a WAP Push notification; and

if it is determined that the subscriber terminal is not capable of receiving WAP Push messages, then formatting the message notification as an SMS message.

2. The method of claim 1 , further comprising:

sending said formatted message notifications to said subscriber terminal addresses;

receiving requests for said multimedia message from subscriber terminals in response to sending said formatted message notifications to said subscriber terminal addresses, each request containing terminal type information, an address for the requesting subscriber terminal, and said message identifier;

selecting an adapted content message for each request based on said message identifier and said terminal type information; and

sending said selected adapted message to the corresponding subscriber terminal address associated with each request.

3. The method of claim 1 , further including adapting said multimedia message into a default adapted content message for a default terminal type using default terminal format requirements information, and indexing said default adapted content message with a default terminal type identifier and said message identifier.

4. The method of claim 2 , further including:

generating a promotional identifier associated with said multimedia message; and

returning said promotional identifier to said content provider.

5. The method of claim 4 , further including:

receiving an order from said content provider to replace or cancel said multimedia message or to replace or cancel at least one parameter associated with said multimedia message, said order containing said promotional identifier.

6. The method of claim 4 , further including:

tallying retrieval information for said multimedia message in a report associated with said promotional identifier; and

periodically publishing said report to said content provider.

7. The method of claim 6 , further including:

receiving a request for said report from said content provider; and

publishing said report to said content provider in response to said request for said report.

8. A method of providing mass multimedia message notification to subscriber terminals wherein at least some of said terminals have different messaging capabilities, said method comprising:

receiving a multimedia message and a list of subscriber terminal addresses from a content provider;

obtaining a unique message identifier for said multimedia message;

obtaining subscriber terminal messaging capabilities information for each subscriber address; and

formatting message notifications for each subscriber terminal address based on said subscriber terminal messaging capabilities information, said message notifications each including said message identifier,

wherein said subscriber terminal messaging capabilities information includes information as to whether each subscriber terminal is SMS capable, WAP Push capable, or MMS capable, wherein said step of formatting each message notification further comprises:

determining if the subscriber terminal is capable of receiving MMS messages;

if it is determined that the subscriber terminal is capable of receiving MMS messages, then formatting the message notification as a MMS WAP Push notification;

if it is determined that the subscriber terminal is not capable of receiving MMS messages, then determining if the subscriber terminal is capable of receiving WAP Push messages;

if it is determined that the subscriber terminal is capable of receiving WAP Push messages, then formatting the message notification as a WAP Push notification; and

if it is determined that the subscriber terminal is not capable of receiving WAP Push messages, then formatting the message notification as an SMS message.

9. The method of claim 8 , wherein said step of obtaining a unique message identifier for said multimedia message includes:

sending said multimedia message to a retrieval platform; and

receiving said unique identifier from said retrieval platform.

10. The method of claim 8 , wherein said step of obtaining subscriber terminal messaging capabilities information includes:

requesting said subscriber terminal messaging capabilities information for each subscriber terminal from a subscriber information database using said subscriber terminal addresses; and

receiving said subscriber terminal messaging capabilities information for each subscriber terminal from said subscriber information database.

11. The method of claim 8 , further including sending said formatted message notifications to said subscriber terminals using said subscriber terminal addresses.

12. A method of mass multimedia message adaptation and handling in a system including a service provider and a plurality of terminals supported by the service provider, wherein at least some of said terminals have different message format requirements, said method comprising:

receiving a multimedia message;

providing a unique message identifier for said multimedia message;

adapting said multimedia message into adapted content messages for each supported terminal type using terminal format requirements information for the terminal types supported by the service provider;

indexing each of said adapted content messages with a corresponding terminal type identifier and with said message identifier, so as to enable the adapted content message to be later retrieved by subscriber terminals requesting the multimedia message using the message identifier and terminal type identifiers, wherein requests by subscriber terminals include subscriber terminal messaging capabilities information including information as to whether a requesting subscriber terminal is SMS capable, WAP Push capable, or MMS capable; and

formatting each requested message the formatting further comprising:

determining if the requesting subscriber terminal is capable of receiving MMS messages;

if it is determined that the requesting subscriber terminal is capable of receiving MMS messages, then formatting the message as a MMS WAP Push message;

if it is determined that the requesting subscriber terminal is not capable of receiving MMS messages, then determining if the requesting subscriber terminal is capable of receiving WAP Push messages;

if it is determined that the requesting subscriber terminal is capable of receiving WAP Push messages, then formatting the message as a WAP Push message; and

if it is determined that the requesting subscriber terminal is not capable of receiving WAP Push messages, then formatting the message as an SMS message.

13. The method of claim 12 , wherein said step of receiving a multimedia message includes receiving the multimedia message from a processing platform.

14. The method of claim 12 , further including sending said message identifier to a processing platform.

15. The method of claim 12 , wherein said terminal format requirements information is stored in a user agent profiles database, further including obtaining said terminal format requirements information for terminal types supported by the system from said user agent profiles database.

16. The method of claim 12 , further including storing said indexed adapted content messages in a table associated with said message identifier.

17. The method of claim 12 , further comprising:

receiving requests for said multimedia message from subscriber terminals, each said request containing terminal type information for the requested subscriber terminal, an address for the requesting subscriber terminal, and said message identifier;

selecting an adapted content message for each request based on said message identifier and said terminal type information; and

sending said selected adapted message to the corresponding subscriber terminal address associated with each request.

18. The method of claim 12 , further including adapting said multimedia message into a default adapted content message for a default terminal type using default terminal format requirements information, and indexing said default adapted content message with a default terminal type identifier and said message identifier.

19. The method of claim 12 , further including:

generating a promotional identifier associated with said multimedia message.

20. The method of claim 19 , further including:

receiving an order to replace or cancel said multimedia message or to replace or cancel at least one parameter associated with said multimedia message, said order containing said promotional identifier.

21. The method of claim 19 , further including:

tallying retrieval information for said multimedia message in a report associated with said promotional identifier; and

periodically publishing said report.

22. The method of claim 21 , further including:

receiving a request for said report; and

publishing said report in response to said request for said report.

23. A system for mass multimedia messaging by a service provider, wherein the service provider supports communication terminals having different format requirements and different messaging capabilities, and wherein a content provider provides a multimedia message and a list of subscriber terminal addresses to which the service provider is to deliver the message, said system comprising:

a retrieval platform for:

providing a unique message identifier for said multimedia message;

adapting said multimedia message into adapted content messages for each supported terminal type based on terminal format requirements information for the terminal types supported by the service provider; and

indexing each of said adapted content messages with a corresponding terminal type identifier and with said message identifier, so as to enable the adapted content message to be retrieved by a subscriber terminal requesting the multimedia message using the message identifier and terminal type identifiers; and

a processing platform in communication with said retrieval platform, said processing platform for:

obtaining subscriber terminal messaging capabilities information for each subscriber address; and

formatting message notifications for each subscriber terminal address based on said subscriber terminal messaging capabilities information, said messaging notifications each containing said message identifier,

wherein said subscriber terminal messaging capabilities information includes information as to whether each subscriber terminal is SMS capable, WAP Push capable, or MMS capable, wherein said step of formatting each message notification further comprises:

determining if the subscriber terminal is capable of receiving MMS messages;

if it is determined that the subscriber terminal is capable of receiving MMS messages, then formatting the message notification as a MMS WAP Push notification;

if it is determined that the subscriber terminal is not capable of receiving MMS messages, then determining if the subscriber terminal is capable of receiving WAP Push messages;

if it is determined that the subscriber terminal is capable of receiving WAP Push messages, then formatting the message notification as a WAP Push notification; and

if it is determined that the subscriber terminal is not capable of receiving WAP Push messages, then formatting the message notification as an SMS message.

24. The system of claim 23 , further having a user agent profiles database relating supported terminal type information with terminal format requirements information, and an adaptation engine for adapting multimedia messages for supported terminal types, said adaptation engine being in communication with said user agent profiles database and said retrieval platform, said adaptation engine for:

receiving said multimedia message from said retrieval platform;

obtaining terminal format requirements information for terminal types supported by said service provider system from said user agent profiles database;

adapting said multimedia message into adapted content messages for each supported terminal type using said terminal format requirements information; and

returning said adapted content messages and corresponding terminal type identifiers to said retrieval platform.

25. The system of claim 23 , further having a subscriber information database relating subscriber terminal address information with subscriber terminal messaging capabilities information, said subscriber information database being in communication with said processing platform, such that said processing platform is able to obtain said subscriber terminal messaging capabilities information from said subscriber information database.

26. The system of claim 23 , wherein said retrieval platform is further for:

receiving requests for said multimedia message from subscriber terminals, each request containing terminal type information for the requesting terminal, an address for the requesting terminal and said message identifier;

selecting an adapted content message for each request using said message identifier and said terminal type information.

27. The system of claim 23 , further having a reporting platform for tracking how many subscribers have retrieved the multimedia message, said reporting platform in communication with said processing platform, said retrieval platform and said content provider.

28. A computer readable medium having computer executable instructions for performing a method of mass multimedia messaging in a system including a service provider and a plurality of terminals supported by the service provider, wherein at least some of said terminals are of terminal types have differing messaging capabilities and differing message format requirements, said method comprising:

receiving a multimedia message and a list of subscriber terminal addresses from a content provider;

generating a unique message identifier for said multimedia message;

adapting said multimedia message into adapted content messages for each supported terminal type using terminal format requirements information for the terminal types supported by the service provider;

indexing each said adapted content message with a corresponding terminal type identifier and said message identifier; and

formatting message notifications containing said message identifier for each subscriber address based on subscriber terminal messaging capabilities information for the corresponding subscriber terminals,

wherein said subscriber terminal messaging capabilities information includes information as to whether each subscriber terminal is SMS capable, WAP Push capable, or MMS capable, wherein said step of formatting each message notification further comprises:

determining if the subscriber terminal is capable of receiving MMS messages;

if it is determined that the subscriber terminal is capable of receiving MMS messages, then formatting the message notification as a MMS WAP Push notification;

if it is determined that the subscriber terminal is not capable of receiving MMS messages, then determining if the subscriber terminal is capable of receiving WAP Push messages;

if it is determined that the subscriber terminal is capable of receiving WAP Push messages, then formatting the message notification as a WAP Push notification; and

if it is determined that the subscriber terminal is not capable of receiving WAP Push messages, then formatting the message notification as an SMS message.

29. The computer readable medium of claim 28 , including executable instructions further including the steps of:

sending said formatted message notifications to said subscriber terminal addresses;

receiving requests for said multimedia message from subscriber terminals in response to sending said formatted message notifications to said subscriber terminal addresses, each request containing terminal type information, an address for the requesting subscriber terminal, and said message identifier;

selecting a said adapted content message for each request based on said message identifier and said terminal type information; and

sending said selected adapted message to the corresponding subscriber terminal address associated with each request.

30. A computer readable medium having executable instructions for performing a method of providing mass multimedia message notification to subscriber terminals wherein at least some of said terminals have different messaging capabilities, where said method comprises:

receiving a multimedia message and a list of subscriber terminal addresses from a content provider;

obtaining a unique message identifier for said multimedia message;

obtaining subscriber terminal messaging capabilities information for each subscriber address; and

formatting message notifications for each subscriber terminal address based on said subscriber terminal messaging capabilities information, said message notifications each including said message identifier,

wherein said subscriber terminal messaging capabilities information includes information as to whether each subscriber terminal is SMS capable, WAP Push capable, or MMS capable, wherein said step of formatting each message notification further comprises:

determining if the subscriber terminal is capable of receiving MMS messages;

if it is determined that the subscriber terminal is capable of receiving MMS messages, then formatting the message notification as a MMS WAP Push notification;

if it is determined that the subscriber terminal is not capable of receiving MMS messages, then determining if the subscriber terminal is capable of receiving WAP Push messages;

if it is determined that the subscriber terminal is capable of receiving WAP Push messages, then formatting the message notification as a WAP Push notification; and

if it is determined that the subscriber terminal is not capable of receiving WAP Push messages, then formatting the message notification as an SMS message.

31. A computer readable medium having computer executable instructions for performing a method of mass multimedia message adaptation and handling in a system including a service provider and a plurality of terminals supported by the service provider, wherein at least some of said terminals have different message format requirements, where said method comprises:

receiving a multimedia message;

providing a unique message identifier for said multimedia message;

adapting said multimedia message into adapted content messages for each supported terminal type using terminal format requirements information for the terminal types supported by the service provider;

indexing each of said adapted content messages with a corresponding terminal type identifier and with said message identifier, so as to enable the adapted content message to be later retrieved by subscriber terminals requesting the multimedia message using the message identifier and terminal type identifiers, wherein requests by subscriber terminals include subscriber terminal messaging capabilities information including information as to whether a requesting subscriber terminal is SMS capable, WAP Push capable, or MMS capable; and

formatting each requested message the formatting further comprising:

determining if the requesting subscriber terminal is capable of receiving MMS messages;

if it is determined that the requesting subscriber terminal is capable of receiving MMS messages, then formatting the message as a MMS WAP Push message;

if it is determined that the requesting subscriber terminal is not capable of receiving MMS messages, then determining if the requesting subscriber terminal is capable of receiving WAP Push messages;

if it is determined that the requesting subscriber terminal is capable of receiving WAP Push messages, then formatting the message as a WAP Push message; and

if it is determined that the requesting subscriber terminal is not capable of receiving WAP Push messages, then formatting the message as an SMS message.

32. The computer readable medium of claim 31 , including executable instructions further including the steps of:

receiving requests for said multimedia message from subscriber terminals, each said request containing terminal type information for the requested subscriber terminal, an address for the requesting subscriber terminal, and said message identifier;

selecting an adapted content message for each request using said message identifier and said terminal type information; and

sending said selected adapted message to the corresponding subscriber terminal address associated with each request.

Assignments (3)
CERTIFICATE OF CONVERSION Recorded Feb 14, 2006
From: CINGULAR WIRELESS II, INC.
To: CINGULAR WIRELESS II, LLC
Reel/Frame 017165/0428 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2005
From: CINGULAR WIRELESS, LLC
To: CINGULAR WIRELESS II, INC.
Reel/Frame 016566/0348 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 1, 2004
From: MCNAMARA, JUSTIN; KEFALAS, ANASTASIOS
To: CINGULAR WIRELESS LLC
Reel/Frame 015949/0044 →