Web server resident on a mobile computing device

• US 20040255005A1
• Filed: 02/24/2004
• Published: 12/16/2004
• Est. Priority Date: 08/24/2001
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Spooner, David
• Application Number:
  US10/487,643
• Publication Number:
  US 20040255005A1
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

A mobile computing device comprising a web server; wherein the web server is capable of converting application specific data from a binary data format optimised for the device to a first agreed format which is a standard format not optimised for the device, in order to enable both (i) an application A, running on the mobile computing device and which can handle the standard format and also (ii) an application B, running on a further device remotely connected to the mobile computing device and which can also handle the standard I format, to read the application specific data stored on the mobile computing device. Converting application specific data stored on the mobile computing device in a native, proprietary binary format into an agreed standards based format, such as a mark-up language like HTML, makes that application specific data fully portable, a major advantage whilst mobile networks are expensive, and have reliability and latency issues.

Claims

1. A mobile computing device comprising a web server;

wherein the web server is capable of converting application specific data from a binary data format optimised for the device to a first agreed format which is a standard format not optimised for the device, in order to enable both (i) an application A, running on the mobile computing device and which can handle the standard format and also (ii) an application B, running on a further device remotely connected to the mobile computing device and which can also handle the standard format, to read the application specific data stored on the mobile computing device.

2. The mobile computing device of claim 1 in which the web server is capable of converting application specific data from a second agreed format to the binary data format in order to enable each application A and B to write or manipulate application specific data.

3. The mobile computing device of claim 1 in which the web server comprises plug-in modules connected in a pipeline, the pipeline terminating in multiple data conversion modules each dynamically selectable to retrieve data from a different source of the application specific data, each data conversion module capable of converting data between one or more binary data formats and the first agreed format.

4. The mobile computing device of claim 1 in which the first agreed format is a mark up language format and the application A on both the device and the application B on the further device is a web browser.

5. The mobile computing device of claim 4 in which the browser resident on the mobile computing device provides a graphical user interface which brings together application specific data from several different sources.

6. The mobile computing device of claim 5 in which the browser becomes the complete user interface to the device.

7. The mobile computing device of claim 6 in which the user interface to the device can be changed or update or customised over the air to take into account user preferences or enable greater product differentiation.

8. The mobile computing device of claim 1 in which the first agreed format is a text string format for use in an application A or B which then formats the text string data appropriately.

9. The mobile computing device of claim 2 in which the second agreed format is form data format.

10. The mobile computing device of claim 1 in which the mobile computing device is remotely connectable to the further device over a WAN, or a local area network or a piconet.

11. The mobile computing device of claim 1 in which the web server is programmed to alter its behaviour or operation in dependence on the location or environment of the mobile computing device.

12. The mobile computing device of claim 11 in which, only when the mobile computing device determines that it is solely in a network with high security clearance, is it programmed to make available highly sensitive application specific data.

13. The mobile computing device of claim 1 in which the application specific data is one of the following types:

personal information management (“

PIM”

) data, messages, word processor documents, image files and sound files.

14. The mobile computing device of claim 1 which also stores synchronisation and backup configuration parameters.

15. A method of enabling an application A running on a mobile computing device and an application B running on a further device which is remotely connected to the mobile computing device to read application specific data which is stored on the mobile computing device, comprising the step of:

converting, at a web server resident on the mobile computing device, the application specific data from a binary data format optimised for the device to a first agreed format which is a standard format not optimised for the device but which can be handled by both applications A and B.

16. The method of claim 15 in which either application is enabled to write new application specific data or manipulate the application specific data, comprising the further steps of:

converting, at the web server resident on the mobile computing device, the new or manipulated application specific data from a second agreed format to the binary data format; and

storing the new or manipulated data in the binary data format.

17. The method of claim 15 in which the step of conversion is preceded by the step of selecting an appropriate data conversion plug-in module, the available data conversion modules being each dynamically selectable to retrieve data from a different source of application specific data.

18. The method of claim 15 comprising the step of the web server interacting with a browser resident on the mobile computing device and the first agreed format is a mark up language format that can be rendered by the web browser.

19. The method of claim 18 comprising the step of the browser resident on the mobile computing device providing a graphical interface which brings together application specific data from several different sources.

20. The method of claim 19 comprising the step of the browser on the mobile computing device operating as the complete user interface to the device.

21. The method of claim 20 comprising the further step of changing or customising the user interface to the device over the air to take into account user preferences or enable greater product differentiation.

22. The method of claim 16 in which the second agreed format is form data format.

23. The method of claim 15 comprising the further step of outputting the application specific data in text string format from the web server, the text string format data being used in an application A or B which formats the data appropriately.

24. The method of claim 15 in which the further device, which is remotely connected to the mobile computing device, displays data stored on the mobile computing device in a format determined by the further device.

25. The method of claim 15 comprising the step of remotely connecting the mobile computing device to the further device over a WAN, or a local area network or a piconet.

26. The method of claim 15 comprising the step of the web server altering its behaviour or operation in dependence on the location or environment of the mobile computing device.

27. The method of claim 26 in which, only if the mobile computing device determines that it is solely in a network with high security clearance, does it make available highly sensitive application specific data.

28. The method of claim 15 in which the application specific data is one of the following types:

personal information management (“

PIM”

) data, messages, word processed documents, image files and sound files.

29. The method of claim 15 comprising the step of the mobile computing device storing synchronisation and backup configuration parameters.

30. Computer software when stored on a carrier medium, the software enabling a mobile computing device and associated further device to perform the method of claim 15 when running on the mobile computing device.

31. Computer software when transmitted over a network, the software enabling a mobile computing device and associated further device to perform the method of claim 15 when running on the mobile computing device.