Data synchronization interface

Description

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of Provisional Application No. 60/312,737, filed Aug. 15, 2001, pending, which application is incorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

I. Field of the Invention

The present invention generally relates to communication between systems. More particularly, the invention relates to a communication interface to aid transferring of data and information between systems and/or databases.

II. Description of the Related Art

Wireless devices, such as cellular telephones, personal digital assistants (“PDAs”), pagers, laptops with wireless connectivity, etc., communicate packets including voice and data over a wireless network. These wireless devices have installed application programming interfaces (“APIs”) onto their local computer platform that allow software developers to create software applications that operate on the wireless device. The API sits between the wireless device system software and the software application, making the wireless device functionality available to the application without requiring the software developer to have the specific wireless device system source code.

These wireless devices typically need to communicate with other systems and databases within the other systems. Unfortunately, the wireless device may lose a signal during communication or be otherwise unavailable when transmitting information to other systems. This may cause errors when attempting to access a database when the signal is lost. The wireless device may be required to reinitiate the database access and resubmit the database request when the signal is reacquired.

Extended beyond wireless devices, often wire-based systems need to communicate with each other but do not share a similar “language” for communication. For example, as with wireless devices, one system may need to communicate with the database in another system to receive or insert data. To communicate with the database, the system must be aware of the database language, record and field structures, and formats in order to access and store information in the database. While current technologies provide for the ability for the interface between the system and the database to include the language, structure and format of the database, this becomes more complex when multiple databases, possibly requiring multiple unique database languages, etc., need to be accessed.

Furthermore, when data is to be sent to multiple systems, or conversely received from multiple systems, a common interface does not exist to integrate across the multiple systems to simplify the data transmission. This is problematic for systems communicating with several other systems.

Therefore, what is needed in the art is an interface that simplifies the communication between one or multiple databases and provides reliable and secure transfer of information between multiple systems.

Current methods in the art do not address this need. Database replication services and custom built database interfaces can become very complex and unwieldy if multiple databases need to be accessed. In addition, all systems that access the custom database must have that interface. Also, custom built databases are required to stay online for transactions to occur.

Electronic Data Interchange (EDI) only addresses the need for pre-defined message types and content specific to electronic commerce. The EDI message formats do not address the data exchange needs as it relates to wireless services, system integration considerations and billing specificity.

SUMMARY OF THE INVENTION

System and methods consistent with the present invention overcome the shortcoming of existing systems by providing an interface to facilitate communication between systems. A source system translates data into an common format, such as, the XML format, and transmits the data to an data synchronizer interface tool. The tool stores the data in the common format in a persistent intermediate storage, such as, a queue, allowing the source system to go offline or to perform other tasks. The interface transmits the data in the common format to a target system, which may ackwnowlege receipt of the data, thereby permitting the tool to decide whether to reinitiate the transfer or to delete the data from the persistent intermediate storage.

In one embodiment, the present invention provides a method of processing information in an interface comprising receiving data in a first format from a source system, storing the data in a persistent intermediate storage, initiating the transmission of the information to the target system while retaining the information, receiving an indication that the transmission of information to the target system was unsuccessful, and reinitiating the transmission of the information to the target system. The method may further include storing data received from multiple source systems associated with multiple target systems, and initiating the transmission of the data from multiple source systems to the associated multiple target systems. Also, the method may include receiving an source system acknowledgement indicating the acknowledgement was received and removing the data from the persistent intermediate storage.

Other objects, advantages, and features of the present invention will become apparent after review of the hereinafter set forth Brief Description of the Drawings, Detailed Description of the Invention, and the Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate presently preferred embodiments of the invention and, together with the general description given above and the detailed description of the preferred embodiments given below, serve to explain the principles of the invention. In the drawings:

FIG. 1 is a representative diagram of a wireless network and the computer hardware and wireless devices that can be used in an exemplary embodiment of the present invention;

FIG. 2 is a block diagram of the hardware components of the wireless network providing communication between different wireless devices, an application download server, and a database in an exemplary embodiment of the present invention;

FIG. 3 is a block diagram detecting the architecture of the synchronizer tool interface in an exemplary embodiment of the present invention; and

FIG. 4 is a flowchart depicting the process of the synchronizer tool interface in an exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the presently exemplary and preferred embodiments of the invention as illustrated in the accompanying drawings, in which like reference characters designate like or corresponding parts throughout the several drawings. The nature, objectives and advantages of the present invention will become more apparent to those skilled in the art after considering the following detailed description in connection with the accompanying drawings.

FIG. 1 illustrates an architecture in which one embodiment of the present invention may be implemented using one or more wireless devices, such as cellular telephone 12, in communication across a wireless network 14 with at least one network server, such as application download server 16, that selectively downloads or provided access to software applications or other data to the wireless devices across a wireless communication portal or other data access to the wireless network 14. As shown here, the wireless device can be a cellular telephone 12, with a graphics display 13, a personal digital assistant 18 with PDA screen 19, a pager 20 with a graphics display 21, which is shown here as a two-way text pager, or even a separate computer platform 22 that has a wireless communication portal and a display 23, and may otherwise have a wired connection 24 to a network or the Internet. The system 10 can include any form of remote computer module including a wireless communication portal, including without limitation, wireless modems, PCMCIA cards, access terminals, personal computers, access terminals, telephones without a display or keypad, or any combination or sub-combination thereof.

The application download server 16 is shown here on a local server-side network 26 with other computer elements in communication with the wireless network 14, such as a database 28 with stored applications and data that contains software applications and data that are accessible and downloadable to the wireless devices 12,18,20,22.

FIG. 2 is a block diagram of the hardware components of the wireless network providing communication between different wireless devices, an application download server, and a database in an exemplary embodiment of the present invention. The wireless network 14 is merely exemplary and can include any system whereby remote modules, such as wireless devices 12,18,20,22, communicate over-the-air between and among each other and/or between and among components of a wireless network 14, including, without limitation, wireless network carriers and/or servers. The application download server (“ADS”) 16 and the stored applications database 28 will be present on the cellular data network with any other components that are needed to provide cellular telecommunication services. The server 32 may provide other functions used by one or other components, such as application management functions for the application download server. The server 32 and ADS may use a synchronizer interface tool (not shown) to communicate data between the systems. The server or other components of the system may interface with other systems not shown to transmit or receive data. The synchronizer tool may be used in supporting communication with these other systems as well.

The application download server 16, and/or other servers communicate with a carrier network 40, through a data link, such as the Internet, a secure LAN, WAN, or other network. The carrier network 40 controls messages (generally being data packets) sent to a messaging service controller (“MSC”) 42. The carrier network 40 communicates with the MSC 42 by a network, the Internet and/or POTS (“plain ordinary telephone system”). Typically, the network or Internet connection between the carrier network 40 and the MSC 42 transfers data, and the POTS transfers voice information. The MSC 42 is connected to multiple base stations (“BTS”) 44. In a similar manner to the carrier network, the MSC 42 is typically connected to the BTS 44 by both the network and/or Internet for data transfer and POTS for voice information. The BTS 44 ultimately broadcasts messages wirelessly to the wireless devices, such as cellular telephone 12, by short messaging service (“SMS”), or other over-the-air methods known in the art.

The wireless device, such as cellular telephone 12, has a computer platform 50 that can receive and execute software applications and display data transmitted from the application download server 16. The computer platform 50 also allows the wireless device to interact with data and applications resident on network servers. The computer platform 50 includes, among other components, a display driver 52 that drives the graphics display 13 and renders images on the graphics display 13 based upon graphics data received at the computer platform 50. The computer platform 50 also includes an application-specific integrated circuit (“ASIC”) 54, or other processor, microprocessor, logic circuit, or other data processing device. The ASIC 52 is installed at the time of manufacture of the wireless device and is not normally upgradeable. The ASIC 52 or other processor executes the application programming interface (“API”) layer 56 that interfaces with any resident programs in the memory 58 of the wireless device. The memory can be comprised of read-only or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards, or any memory common to computer platforms. The computer platform 50 also includes a local database 60 that can hold the software applications not actively used in memory 58, such as the software applications downloaded from the application download server 16. The local database 60 is typically comprised of one or more flash memory cells, but can be any secondary or tertiary storage device as known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape, or soft or hard disk.

The wireless device, such as cellular telephone 12, can access and download many types of applications, such as games and stock monitors, or simply data such as news and sports-related data. The downloaded data can be immediately displayed on the display or stored in the local database 60 when not in use. The software applications can be treated as a regular software application resident on the wireless device 12,18,20,22, and the user of the wireless device can selectively upload stored resident applications from the local database 60 to memory 58 for execution on the API 56. The end-user of the wireless device 12,18,20,22 can also selectively delete a software application from the local database 60.

FIG. 3 is a block diagram depicting the architecture of a synchronizer tool interface in an exemplary embodiment of the present invention. In one embodiment, the synchronizer tool 305 enables tables in one RDBMS system to be synchronized with a destination system via a standard XML interface. It will be recognized by those skilled in the art that the XML language is an implementation choice and other languages may be used. Furthermore, it will also be recognized that the synchronizer tool may be used to synchronize or communicate other information, not just information from RDBMS tables, between computer systems or subsystems. In addition, the connections between the interface and the target and source systems may be by any communication media available, such as wireless, including RF, satellite and infrared communication, and wire-based communication methods. In one embodiment, the communications medium is IP based.

Data received from the RDBMS 320 in the source system 310 is stored in the queue 325 of the synchronizer tool 305. This data is translated into a common file format such as XML. By having a storage mechanism, such as a queue, the synchronizer tool can maintain the data for the RDBMS 315 even if the source system 310 is off line. The synchronizer tool 305 may also be implemented to provide an acknowledgement to the source system 310 when the data sent to the target system 315 is replicated in the RDBMS 315 (the target system may provide an acknowledgement to the synchronizer tool 305 indicating this replication has occurred, acknowledge the receipt of the data, or acknowledge other processing was performed).

The source system 310 is connected to the synchronizer tool 305. This connection may be by any communication mechanism, including wireless and/or wire-based connection (or combination thereof). The synchronizer tool 305 may be local to the source system 310 or it may be remote to it. The source system transfers information to the synchronizer via this connection. This information may be data for replication to a remote database, or may be any type of information destined for another system, such as a message request, data request or other data transfer. In one embodiment, the source system 310 sends this information to the synchronizer tool 305 using an XML format.

The target system receives the information from the synchronizer tool 305 and may respond with an acknowledgement to the synchronizer tool 305. Alternatively, the synchronizer tool may interact directly with a subsystem in the target system 300 (such as a RDBMS 315) to perform a task such as data replication.

Note the definition of a target system 300 and source system 310 is somewhat arbitrary. In one instance a system may be the source system sending data to a target system while in another instance the same system is acting as the target system receiving data from another system.

FIG. 4 is a flowchart depicting the process of the synchronizer tool interface in an exemplary embodiment of the present invention. The method begins by having the source system translate data into a XML format (Step 400) or some other common format. This data may be in the form of scalar data for the target system, a request for information from the target system or other information to be transferred for processing by the target system. Next the data is transmitted to and received by the synchronizer tool (Step 405).

The data is stored in a persistent intermediate storage (Step 405), such as a queue within a synchronizer tool. This allows some independence between the source and target systems. The source system may make the request, have it stored in the queue and can go offline while the request gets transmitted to and/or processed by the target system. In addition, the synchronizer tool may send an acknowledgement to the source system that it received the data.

The data in XML format is then transmitted from the synchronizer tool to the target system (Step 415). Note that the “data” can be any piece of information desired to be sent to the target system. It may be data used for replication into an RDBMS of the target system. Alternatively, it may be any type of command or information sent to the target system for possible processing by the target system. In addition, there may be multiple target systems receiving this data. The synchronization tool may queue multiple data transmission requests for multiple destinations, including multi-target system destination requests.

The method continues to initiate the translated command on a RDBMS (Step 415). After translating the command into the appropriate language for the RDBMS, it initiates this command by direct access to the target system's RDBMS or by sending the command to a processor, such as one in the target system, for execution.

If the data is received at the target (Step 420), the “Yes” branch is followed and an acknowledgement is sent to the source system (Step 425). The source system formats this acknowledgement into a format readable by the source system, such as in XML. If the source system is not online, the acknowledgement may be queued and further attempts may be made to the source system to inform it that the data was transmitted to the target system. The synchronizer tool may determine if the data was received by receiving an acknowledgement from the target system.

If data is received at the target as determined in Step 420, such as may occur when the target system or RDBMS is offline, then the “No” branch is followed and the data remains in the queue and will retry (Step 430) to initiate a transmission of the data to the target system as described in Step 415. There are many queuing algorithms and time parameters possible to determine when to initiate another transmission to the target system. The preferred algorithm and time is based on the processing capacity, efficiency, available resources (such as available queuing memory) as well as other implementation factors of the systems involved.

The foregoing description of an implementation of the invention has been presented for purposes of illustration and description. It is not exhaustive and does not limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practicing of the invention. For example, the described implementation includes software but one embodiment of the present invention may be implemented as a combination of hardware and software or in hardware alone. The invention may be implemented with both object-oriented and non-object-oriented programming systems. Additionally, although aspects of the present invention are described as being stored in memory, those skilled in the art will appreciate that these aspects can also be stored on other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or CD-ROM; a carrier wave from the Internet or other propagation medium; or other forms of RAM or ROM.

In addition, it should be noted that various changes and modifications could be made herein without departing from the scope of the invention as defined by the appended claims and their equivalents. Furthermore, although elements of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.