Data exchange between a handheld device and another computer system using an exchange manager via synchronization

Abstract

A method and electronic system for exchanging data between a handheld device and another computer system are described. A data file is transferred to the handheld device using the install application of a synchronization manager. The transferred file is stored as a digital stream file with its native data encoding. After synchronization, a message is sent to notify the exchange manager about the data file. The exchange manager then uses an application registry to identify the application program that corresponds to the stream file based on the extension of the stream file. The pertinent application program is then invoked and the stream file is dispatched to the application for processing. During processing, the pertinent application then formats the stream file such that the data file becomes a record within the database file that is associated with the pertinent application.

Description

BACKGROUND OF THE INVENTION1. Field of the InventionThe present invention generally relates to the field of client / server data systems. More particularly, the present invention relates to the field of exporting and importing information with respect to two or more computer systems wherein one computer system is a handheld electronic device.2. Related ArtComputers and other electronic devices (e.g., personal digital assistants) have become integral tools used in a wide variety of different applications, such as in finance and commercial transactions, computer-aided design and manufacturing, health care, telecommunication, education, etc. Computers along with other electronic devices are finding new applications as a result of advances in hardware technology and rapid development in software technology. Furthermore, the functionality of a computer system or other type of electronic device is dramatically enhanced by coupling these stand-alone devices together in order to form a networ...

AI Technical Summary

Benefits of technology

Accordingly, what is needed is a standard interface that allows data to be imported or exported from a handheld device that works for all applications. What is needed is a system and method allowing the exchange of data files from a handheld device to another computer system without requiring complex conduit programs. What is needed is a system to be able to import data files to the handhold device by selecting data files with the install application. Exported data would then appear as files in an in-box after a synchronization process. The same user experience would then be available to all applications. What is needed is a system that would allow any file type, not only .PRC, .PDB and .PQA types, to be installed onto the handheld device at synchronization time. The present invention includes an updated exchange manager that can route files (downloaded by synchronization) by registered type to the correct application on the handheld device. The user can also send data from their applications to desktop files.

A method and electronic system for exchanging data between a handheld device and another computer system. The system allows a data file of any data format (known or unknown) and / or of any extension to be downloaded, e.g., installed, from one computer system onto a handheld device. In one embodiment, the computer system can be a host computer system, e.g., a personal computer, that is communicatively coupled to the handheld device using a communication link. The handheld device can be any portable electronic device, such as, a palmtop computer system, a phone, a PDA, a pager, etc. The data file is transferred to the handheld device using the install application of a synchronization manager. The transferred file is stored as a digital stream file with its native data encoding. After synchronization, a message is sent to notify the exchange manager about the data file. The exchange manager then uses an application registry to identify the application program that corresponds to the stream file based on the stream file's extension. The pertinent application program is then invoked and the stream file is dispatched to the application for processing. During processing, the pertinent application then formats the stream file such that the data file becomes a record within the database file that is associated with the pertinent application. Using this mechanism, a user can import records to an application program without requiring a custom conduit program to perform the data exchange. Data flow can also be reversed for data exporting, from the application program to the host computer so that data files can be installed on the host without requiring a custom conduit program for the pertinent application.

Problems solved by technology

However, the conduit mechanism is very complex and difficult to implement.

Further, different conduits are required for different host operating systems thereby making the conduit mechanism even more difficult to implement.

However, the synchronization model 5 of FIG. 1 does not provide an easy way to send data directly to or from the device 6.

In addition to the efforts involved in writing a conduit, there are the support issues.

However, there are several problems with the “whole-database” approach.

This is unnecessary overhead for the content and can lead to compatibility problems if anything in the format ever changes, e.g., future handhelds use different internal formats.

Another problem with this approach is that it requires each import data to be first translated into a database image (e.g., .PDB file) before it can be installed.

This prevents users from installing data encoded in otherwise universal file formats unless they first perform the bothersome translation.

Another problem with this “whole-database” approach is that the operating system on the handheld device 6 is designed to work well with many records in few databases.

This approach is very inefficient in terms of computer resource usage.

Furthermore, many features of the handheld's operating system that are developed for record processing cannot be applied to individual databases which are treated as “records.” For instance, the database manager of the handheld 6 is designed to sort records, not databases.

Also, the launcher of the handheld 6 was not designed to work well with large numbers of database files.

These types of functions are limited when an application manages data by the database instead of by the record.

Moreover, this method is limited because once a database is transferred to the handheld device, it becomes registered with only one application.

Unfortunately, these methods are very complex for most users to perform and they also clutter the memopad with data that the user has no need to read and forces their applications to read and write directly to the memopad's databases.

However, most people do not have the appropriate infrared setup on their desktop computers to utilize the exchange manager in this fashion.

Therefore, this solution is not widely accepted.

Images