Simplified scheme of rich content messaging from PC to mobile devices

• US 20060184609A1
• Filed: 02/16/2005
• Published: 08/17/2006
• Est. Priority Date: 02/16/2005
• Status: Abandoned Application

• Current Assignee: Li Deng
• Original Assignee: Li Deng
• Inventors: Deng, Li
• Application Number:
  US11/058,933
• Publication Number:
  US 20060184609A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method, apparatus, client and server are directed at providing a simplified scheme to deliver rich content messages that include text, audio, video, and images from desktop computing devices to multimedia capable phones. A web form is provided for users to specify rich content elements such as text, audio, video, and images either from their local desktop computing device or from rich content store on a network. Also provided in the form are input fields for users to enter device numbers and the service providers for recipients. Upon submitting the form, rich content elements are uploaded and stored on the server. A WAP page that contains the links to all the rich content elements is generated dynamically and stored on the server. The server sends a notification message with an embedded link to the specified mobile devices. The link, such as a URL, a script, an executable, a program, and the like, pointing to the WAP page, can be invoked from mobile devices. When the link is invoked on the mobile device, it sends a request to the server for the rich content WAP page. Upon receiving the request from the mobile device, the server collects the information about the mobile device; locates and loads the rich content WAP page; converts the rich content elements to the formats supported by the mobile device; optimizes the WAP page for display on the mobile device; delivers the optimized rich content WAP page to the mobile device. The rich content WAP page can be viewed, downloaded, saved, and played on the mobile device. The scheme of the present invention can also be implemented to deliver rich content messages to multiple mobile devices.

Claims

1. A client, server, and method providing a simplified scheme to deliver rich content messages that include texts, audio, video, and images from desktop computing devices to multimedia capable phones, comprising:

Uploading rich content components such as texts, audio, video, and images from user'"'"'s desktop computing device to server;

Browsing and searching the rich content database to select rich content items on a network.

Collecting targeted mobile device info such as phone number and/or carrier information from sender;

Store rich contend components in rich content store on server;

Arranging and laying out texts, audio, video, and images to generate a WAP page so that it can be saved, viewed, downloaded and played on the mobile device with a micro browser;

Generating a unique id for each dynamically generated rich content WAP page using any of a variety of mechanisms, including a counter, a MD5 hash;

Mapping the unique id to the rich content WAP page;

Store the generated WAP page on server;

Sending a notification message to the mobile device, wherein the notification message includes a link to the rich content WAP page;

Employing the link to access rich content WAP page;

Colleting device info on the fly from HTTP header and user agent profiles;

Converting the rich content elements to formats supported by the requesting mobile device.

Optimizing the WAP page for display on the particular mobile device;

Delivering the WAP page to the mobile device for viewing, saving, and downloading.

2. The method of claim 1, wherein arranging and laying out rich content elements dynamically into a WAP page that can be accessed through a micro browser.

3. The method of claim 2, wherein all the rich content components in the WAP page are constructed to be viewed, previewed, downloaded, saved, and played back on a mobile device.

4. The method of claim 1, wherein generating a link that can be used to invoke a request from mobile device to retrieve the WAP page that contains all the rich content elements.

5. The method of claim 4, wherein the link further comprises of a Uniform Resource Locator (URL), a script, an executable, program, and the like.

6. The method of claim 1, wherein sending the notification message to mobile device further comprises:

Associating the link with the WAP page that contains all the rich content elements uploaded and stored on the server;

Associating links with all the rich content elements within the WAP page;

Sending the notification message including the associated link to the mobile device, wherein the link is employable to locate the rich content WAP page and all the rich content elements on the server.

7. The method of claim 1, wherein offering options to specify multiple recipients of the rich content message and delivering notifications to a group of devices at the same time.

8. The method of claim 1, wherein collecting the information about the mobile device from the request of the mobile device on the fly.

9. The method of claim 8, where device info collected on the fly via user agent profile and HTTP headers, etc.

10. The method of claim 8, wherein using the info collected about a device on the fly through requests to query a device database to find out about the capabilities and formats supported by the device, and the like.

11. The method of claim 1, wherein converting rich content elements into formats that are supported by the mobile device so that they can be saved, viewed, previewed, downloaded and played on the mobile device.

12. The method of claim 1, wherein optimizing the WAP page for display on a particular mobile device.

13. The method of claim 1, wherein the uploaded rich content elements are stored in a rich content store.

14. The method of claim 6, wherein the WAP page contains links to rich content elements. Users can use those links to view, preview, download, and save the rich content elements stored in the server.

15. The method of claim 1, wherein uploading the rich content elements to the server further comprises:

Uploading the rich content elements into web server;

Storing the rich content elements at a rich content store;

17. The method of claim 1, wherein the rich content elements are converted to the formats supported by the mobile device identified from the request when the link is invoked from mobile device to retrieve the rich content WAP page.

18. The method of claim 1, wherein the rich content WAP page is optimized according to the mobile device identified from the request when the link is invoked from mobile device to retrieve the rich content WAP page.

19. In addition to claim 1, the simplified scheme may further comprise authenticating the request to retrieve the rich content WAP page using mobile device numbers, wherein the authentication of recipients further comprises

Associating the generated unique id to the mobile device numbers of recipients;

Store the association between the unique id of rich content WAP page and the mobile device number of the recipient.

Prompting user to enter mobile device number at the time of retrieving the rich content WAP page;

Validating the mobile device number against the saved device number in the association between the mobile device number and the unique id of rich content WAP page.

16. A client adapted for use in a mobile device to receive messages from a server over a network, the client being configured to perform actions, comprising:

Receiving a notification message from the server, wherein the notification message includes a link;

Employing the link to access the rich content WAP page, wherein the rich content WAP page contains links to rich content elements that can be readily saved, previewed, viewed, and played on mobile device.

20. A server for managing a communication with a mobile device over a network, comprising:

Handling http request from PC;

A transceiver for receiving and sending messages to the mobile device;

Receiving rich content elements and saving them into rich content store;

Generating a rich content WAP page that contains links to all the rich content elements stored in the server;

Generating a unique ID for each rich content WAP page;

Mapping the unique ID to each rich content WAP page;

Delivering a notification message to the mobile device, wherein the notification message includes a link;

Handling http request from the mobile device for the WAP page using the link;

Employing the link to enable access to the rich content WAP page for view, preview and download;

Saving the association between the mobile device number and the unique id of the rich content WAP page for authentication of recipients;

Collecting characteristics of the mobile device from the mobile request.

Querying device database for additional device information.

Converting rich content elements to formats supported by mobile device;

Optimizing the WAP page for display on a particular mobile device;

Delivering the WAP to mobile devices.