EA002956B1 - System and method for using a global translator to synchronize workspace elements across a network - Google Patents

Abstract

1. A system, comprising: a first store for storing a first workspace element in a first format; a second store for storing a second workspace element which is an independently-modifiable copy of the first workspace element in a second format; a communications channel coupling the first store to the second store; synchronization means for synchronizing the first workspace element and the second workspace element; and a translator for translating between the first format and the second format. 2. The system of claim 1, wherein the first format is the same as the second format. 3. The system of claim 1 wherein the second format includes HTML. 4. The system of claim 1, wherein the first store is in a LAN. 5. The system of claim 1, further comprising a firewall for protecting the first store. 6. The system of claim 1, further comprising a firewall for protecting the second store. 7. The system of claim 1, wherein the synchronization means includes a first general synchronization module for examining the first workspace element at the first store to determine whether it has been modified; and a second general synchronization module for examining the second workspace element at the second store to determine whether it has been modified. 8. The system of claim 7, wherein the first workspace element and the second workspace element each include version information; and the first and second general synchronization modules each examine the version information of each workspace element to a last synchronization signature to determine whether the workspace element was modified. 9. The system of claim 1, wherein the synchronization means includes a synchronization-start module for determining when to initiate synchronization. 10. The system of claim 1, wherein the first workspace element includes a first folder and the second workspace element includes a second folder. 11. The system of claim 10, further comprising a content-based synchronization module for examining content of the first workspace element and of the second workspace element when the first workspace element and the second workspace element have both been modified since the last synchronization. 12. The system of claim 11, wherein the content-based synchronization module determines if any conflicts exist, and if so then the content-based synchronization module reconciles the conflicts. 13. The system of claim 11, wherein the content-based synchronization module determines if any conflicts exist, and if not then the content-based synchronization module integrates the changes made to each workspace element. 14. The system of claim 1, further comprising a third store coupled to the second store for storing a third workspace element in a third format. 15. The system of claim 14, wherein the translator translates between the second format and the third format. 16. The system of claim 8, wherein the version information indicates the status of each workspace element as of the last synchronization. 17. A method, comprising: accessing a first store storing a first workspace element in a first format; accessing a second store storing a second workspace element which is an independently-modifiable copy of the first workspace element in a second format; synchronizing the first workspace element and the second workspace element; and translating between the first format and the second format. 18. The method of claim 17, wherein the first format is the same as the second format. 19. The method of claim 17, wherein the second format includes HTML. 20. The method of claim 17, wherein the first store is in a LAN. 21. The method of claim 17, wherein the first store is protected by a firewall. 22. The method of claim 17, wherein the second store is protected by a firewall. 23. The method of claim 17, further comprising examining the first workspace element to determine whether it has been modified; and examining the second workspace element to determine whether it has been modified. 24. The method of claim 23, wherein the first workspace element and the second workspace element each include version information; and further comprising the step of comparing the version information of each workspace element to a last synchronization signature to determine whether the workspace element was modified. 25. The method of claim 17, further comprising the step of determining when to initiate synchronization. 26. The method of claim 17, wherein the first workspace element includes a first folder and the second workspace element includes a second folder. 27. The method of claim 26, further comprising the step of examining content of the first workspace element and of the second workspace element when the first workspace element and the second workspace element have both been modified since the last synchronization. 28. The method of claim 27, further comprising the step of determining if any conflicts exist, and if so then reconciling the conflicts. 29. The method of claim 27, further comprising the step of determining if any conflicts exist, and if not then integrating the changes made to each workspace element. 30. The method of claim 17, further comprising the step of accessing a third store coupled to the second store storing a third workspace element in a third format. 31. The method of claim 30, wherein further comprising the step of translating between the second format and the third format. 32. The method of claim 24, wherein the version information indicates the status of each workspace element as of the last synchronization. 33. A system, comprising: means for accessing a first store storing a first workspace element in a first format; means for accessing a second store storing a second workspace element which is an independently-modifiable copy of the first workspace element in a second format; means for synchronizing the first workspace element and the second workspace element; and means for translating between the first format and the second format. 34. A computer-readable storage medium storing program code for causing a computer to perform the steps of: accessing a first store storing a first workspace element in a first format; accessing a second store storing a second workspace element which is an independently-modifiable copy of the first workspace element in a second format; synchronizing the first workspace element and the second workspace element; and translating between the first format and the second format.

Description

This invention relates to computer networks and, in particular, relates to a system and method for using a global translator to synchronize elements of a workspace, such as files, across an entire computer network.

The level of technology

Data consistency is very important for computer users. For example, by supporting multiple, independently modifiable copies of a single document, the user is at risk of using an outdated version. By the time the user notices the inconsistency of the copies, the wrong data can be exchanged between the parties or the data will be lost. Then the user must spend extra time trying to reconcile conflicting versions and addressing the wrong messages.

The data inconsistency problem is exacerbated when multiple copies of a document are maintained in different parts of the network. For example, thanks to network security systems, such as the well-known technology of firewalls (access protection systems), a user can only access one specific place from among the specified places in the network. Without accessing other nodes, the user cannot be sure that the version in the accessible node is the most recent option.

Data consistency problems can also occur when using application programs from different vendors. For example, ^ eb-browser xpare ΝανφαΙΟΓ ™ and \ usbrowser 1n1gpe1 expr_gamer save each bookmark for quick access to the user of interest ^ eb-nodes. However, since each ^ eb browser uses different formats and remembers bookmarks in different files, these bookmarks are not interchangeable. In addition, one ^ eB-browser can save the necessary bookmark, and the other is not. A user who, for example, operates at home ^ eb-browser 1n1gpe1 Explеger ™, and at work uses ^ eb-browser no. Xarre Νανίda1og ™. runs the risk of having inconsistent bookmarks at each location.

Therefore, there is a need for a system and method that would ensure data consistency and, in particular, synchronization of multiple copies of a workspace element, such as a document, across the entire computer network.

Summary of Invention

The present invention provides a system and method for using a global translator to synchronize multiple copies of an element of a workspace in a secure network equipment. Secured network equipment includes a global server connected to multiple clients. Using this system and method, clients automatically synchronize workspace elements across multiple nodes, regardless of whether these nodes are protected by host firewalls. Using this system and method, clients can automatically synchronize workspace elements in different formats and can combine folders of workspace elements for cross-use.

The system includes a first storage device for storing the first workspace elements in the first format, a second storage device for storing the second workspace elements in the second format, a communication channel connecting the first memory device to the second storage device, a synchronization tool for synchronizing the first workspace elements and the second elements of the workspace, and the translator for translation between the first format and the second format.

Similarly, the method includes accessing the first storage device storing the first element of the workspace in the first format; referring to the second storage device, preserving the second element of the workspace in the second format; synchronization of the first element of the workspace and the second element of the workspace; and broadcast between the first format and the second format.

The system and method primarily uses a trusted third party to enable synchronization of workspace data across multiple nodes. Accordingly, a client user who supports a node at work, a node at home, a node on the side, and a node of the global server can synchronize the data of the workspace or separate parts of this data across all four nodes. In addition, predetermined criteria can be set (which specify the timing of synchronization initiation performed by the synchronization trigger module), so that the common synchronization module synchronizes the workspace data at the user's request at predetermined times during the day, for example, when the user performs switching , or after a predetermined user action, such as his exit from the network, or the user logging into the network. Since the system and method is implemented via the Internet, synchronization can occur at any distance. Since the system and method include a broadcast format, it is possible to combine elements of the working space between different application programs and different platforms. In addition, since synchronization is initiated from within the firewall, a typical firewall that prevents inbound communication does not prevent the synchronization of workspace elements. Also, since user preferences can be set in advance, this system and method can be implemented without client participation.

List of drawings

FIG. 1 is a block diagram illustrating a computer network according to the present invention;

FIG. 2 is a block diagram illustrating the details of the service server of FIG. one;

FIG. 3 is a block diagram illustrating the details of the desktop computer of FIG. one;

FIG. 4 is a block diagram illustrating the details of the base system of FIG. one;

FIG. 5 is a block diagram illustrating the details of the synchronization agent of FIG. one;

FIG. 6 is a graphical representation of an example bookmark in global format; and FIG. 7 is a block diagram illustrating a method for synchronizing multiple copies of a workspace element in a secure network.

Detailed Description of the Preferred Embodiment of the Invention

FIG. 1 is a block diagram showing a computer network 100 including a first node, such as a remote computer terminal 102, connected via a communication channel 104, for example, the Internet, to a global server 106. In turn, the global server 106 via a channel 108 communications, for example, the Internet, is connected to a second node, for example, a local area network (LAN) 110. The global server 106 is protected by a global firewall 112, and the LAN 110 is protected by a firewall LAN 114.

The LAN 110 includes a system bus 126 connecting the LAN firewall 114 to an email server 128 having an email folder 138 that contains email; with a server of 132 files having a folder of 142 files containing files; with a calendar server 130 having a calendar folder 140 containing calendar data; and with a desktop computer 134, having an ^ eB browser 152 and a folder of 144 bookmarks containing bookmarks. It is obvious that the e-mail folder 137, the folder 142 of files, the folder 140 of the calendar and the folder 144 of the bookmarks or their parts can be saved in different places, for example, in the desktop computer 134. The e-mail folder 138, the folder 142 of the files, folder 140 of the calendar and folder 144 bookmarks are grouped, for example, on the principle of such information and are defined here together as data 136 workspace. It will be obvious to those skilled in the art that workspace data 136 may include other types of data, such as an application program, such as

М1СГО8ОЙ νοτά 6.0.1 and documents created by using it. In addition, it is obvious that each of the email folders 138, files 142, calendar 140 and bookmarks 144 can be broken down into workspace elements, where each folder of workspace elements or each workspace element separately is identified by specific version information 255 ( described below with reference to Fig. 2). Accordingly, each email message or email folder, file or file folder, calendar data or calendar folder, bookmark or bookmark folder, document or document folder, etc. can be defined as an element of the workspace.

Each data element 136 of the workspace in the LAN 110 is supported in a predetermined format, referred to herein as Format A, which is based on the service (service) subsystem 245 (FIG. 2) that created it. For example, the ^ eB browser 152 in the desktop computer 134 may be the ^ eB browser Iisare ΝανφαΙοΓ ™. and the bookmarks created by him in the bookmark folder 144 are supported in format A. Although format A is described as a single format, it is obvious to those skilled in the art that format A actually contains a format for each data type, for example, there is format A for bookmarks , A format for files, A format for calendar data, A format for e-mail, etc.

The remote terminal 102 stores service subsystems 154 to maintain workspace data 116, which may include information in common with workspace data 136. Workspace data 116 is supported in a format defined as format B, which may differ from format A. Format B is also based on service subsystems 154 that create elements of the work space. For example, if one of the subsystems 154 of the service is ^ eB-browser! N (erg1 Expl6dag ™ (not shown), then bookmarks created with it (not shown) are supported in format B. Although format B is described as a single format, for Those skilled in the art will appreciate that Format B actually contains a separate format for each type of information.In addition, workspace data 116 also contains version information 150, similar to version information 255, described below with reference to Fig. 2.

It is obvious that the remote terminal 102 may include an intelligent phone, a personal electronic assistant (organizer) (PEP), for example, the Paht Ρϊΐοΐ system, supplied and 8.WOBOYS5, 1ps., A laptop computer, etc. In the case of an intelligent telephone, the workspace data 116 may include phone numbers and email. In the case of PEP, the workspace data 116 may include addresses, calendar data and email. In the case of using a laptop computer, the workspace data 116 may include the same types of information as the workspace data 136.

The global server 106 acts as a third-party administrator. The global server 106 stores independently modified copies of selected pieces of workspace data 136 and 116, defined here together as workspace data 120. Accordingly, workspace data 120 includes an independently modifiable copy of each workspace element in selected portions of the workspace data 136 and 116, and an independently modifiable copy of each corresponding information 255 (FIG. 2) and version 150. Copies of version information are defined here together as version information 148, which is also described with reference to FIG. 2

The global server 106 maintains the workspace data 120 in a format defined as a global format that is chosen so that the global translator 122 can easily translate it to and from format A, as well as to and from format B. Although the global format is described as a single format , it will be obvious to those skilled in the art that the global format actually includes a global format for each type of information, for example, there is a global format for bookmarks, a global format for ph fishing, a global format for calendar data, a global format for e-mail, etc. An example of a data space for a bookmark in global format is described in detail below with reference to FIG. 6

The network 100 further comprises a synchronization tool, which includes the base system 146 stored in the LAN 110, and, for example, in the desktop computer 134. The network 100 further includes a synchronization agent 124 stored outside the LAN firewall 114, preferably in global server 106. The underlying system 146 and the synchronization agent 124 act together to synchronize selected portions of the workspace data 136 with selected portions of the workspace data 129. The synchronization tool can synchronize elements of the workspace separately, for example, certain documents of a word processor, or it can synchronize folders of elements of the workspace, for example, a folder of bookmarks. Typically, the base system 146 controls the selected portion of the workspace data 136 in the LAN 110, and the synchronization agent 124 manages the selected portions of the workspace data 120 in the global server 106. Obviously, the global translator 122 acts together with the synchronization tool, translating the data formats to or from global format. As described in more detail below with reference to FIG. 4, the underlying system 190 preferably initiates and manages data synchronization.

The synchronization tool may also include the base system 118 stored at the remote terminal 102, which operates similarly to the base system 146. The base system 118 at the remote terminal 102 works in conjunction with the synchronization agent 124, synchronizing selected portions of the data 116 of the workspace with the selected portions of the data 120 working space. As described in more detail below with reference to FIG. 4, the base system 118 at the remote terminal 102 also preferably initiates and manages data synchronization with the global server 106. It should be noted that the distribution of workload between the base system 118 at the remote terminal 102 and the synchronization agent 124 in the global server 106 may vary. Sometimes, mainly when the remote terminal 102 is a device with relatively lower computing power (such as a smart phone or PEP), a greater amount of real intensive computing is performed at the synchronization agent 124 in the global server 106. In other situations, for example, when the remote terminal 102 is a full configuration PC, the bulk of the intensive computations are performed in place in the base system 118 at the remote terminal 102.

Accordingly, the synchronization tool synchronizes the independently selected portions of the workspace data 116 and 136 with the selected portions of the workspace data 120. Therefore, the synchronization tool indirectly synchronizes the workspace data 136 with the workspace data 116.

FIG. 2 is a block diagram illustrating the details of the serving server 200, where the variant of the serving server 200 is any of the servers, including an email server 145, a file server 150, a calendar server 155, or a desktop computer 160. The service server 200 includes a central processing unit (CPU) 205, for example, a microprocessor I1e1 Reiyit® or a microprocessor MoI1a Ro / er PC®. An input device 210, for example, a keyboard and a mouse, and an output device 215, for example, a screen display with a cathode ray tube (CRT), are connected via the signal bus 220 to the CPU 205. In addition, the CPU 205 is connected through the signal bus 220 communication interface 225 (for example, port E111SGPS1). a data storage device 230 (for example, a magnetic disk) and a random access memory (RAM).

Operating system 240 includes a program for controlling the processing performed by CPU 205; it is usually stored in data storage 230 and loaded into RAM 235 for execution. The maintenance subsystem 245 contains a program to perform a particular service, for example, maintaining an email database, a file database, a calendar database, or a bookmark database. The maintenance subsystem 245 may also be stored in the data memory 230 and loaded into the RAM 235 for execution.

To perform the service, the service subsystem 245 creates service data 250 (eg, an email or an email folder 138 containing an email; a file or folder 142 files containing files; calendar data or a calendar folder 140 containing calendar data; a bookmark or folder 144 of bookmarks containing bookmarks, etc.) in format A according to predefined protocols. The maintenance subsystem 245 stores the data 250 in the data memory 230. Service data 250 includes version information 255 indicating the date and time of the last modification based on the last interaction with the global server 106.

For example, if service data 250 is created and selected to combine it with global server workspace data 120, then version information 255 for service data 250 may include the last modified date and an empty (zero) set indicating the state based on the last interaction with the global server 106. Based on the version information 255, the base system 146 determines that the service data 250 was not generally combined with the data of the global server workspace 120. Similarly, if the service data 255 included items 1, 2, and 3, based on the last modification, then the previous state, based on the last modification, would indicate that the service data 255 included items 1, 2, and 3. If the data 255 services currently include elements 2, 3 and 4, then the base system 140 will determine that element 1 has been removed since the last synchronization and element 4 has been added.

Obviously, the version information 148 on the global server 106 includes information similar to the version information 255. That is, version information 148 will include information indicating the date and time when this version was last modified, and the state based on the last interaction with each client. The maintenance subsystem 245 operates to update version information 255 after the modifications have been made and after synchronization has taken place.

FIG. 3 is a block diagram illustrating the details of the desktop computer 160, which includes the CPU 305, an input device 310, an output device 315, a communication interface 325, a data storage device 330, and RAM 335 associated with a signal bus 320.

The operating system 340 includes a program for controlling the processing performed by the CPU 305; it is usually stored in data storage 330 and is loaded into RAM 335 for execution. The browser browser 152 (i.e., the specific service subsystem 245, FIG. 2) includes a format A service program for managing the bookmark folder 144 (that is, the specific service data 250 of FIG. 2) containing version information 350 ( that is, the specific version information 255, Fig. 2). The ^ eB browser 152 may also be stored in the data memory 330 and loaded into the RAM 335 for execution. Folder 144 bookmarks can be stored in the storage device 330 data. As stated above with reference to FIG. 1, the base system 146 operates to synchronize the workspace data 136 (which includes the 144 bookmarks folder) with the workspace data 120. Base system 146 may also be stored in data storage 330 and loaded into RAM 335 for execution.

FIG. 4 is a block diagram illustrating the details of the base system 400, which represents, for example, the base systems 146 and 118. The base system 400 includes a communication module 405, a user interface module 410, locator modules 415, a sync trigger module 420 (startup-sync ), common synchronization module 425 and content based synchronization module. In order to simplify, it is shown that each module is connected to the other via the signal bus 440.

The communication module 405 includes procedures for data compression and procedures for communicating with the synchronization agent 124 (FIG. 1) via the communication interface 325 (FIG. 3). The communication module 405 may additionally include procedures for applying the 88B technology (secure socket protocol) and methods of identifying and authenticating users (i.e., digital certificates) to establish a secure communication channel passing through the global firewall 112. Examples of communication modules 405 may include The TCP / 1P stacks or the ArrleTa1k® protocol.

The user interface module 410 includes procedures for communicating with a user, and may also include a well-known graphical user interface (GUI). The user interface module 410 works in conjunction with the other system components described here.

Locator modules 415 include procedures for identifying memory cells of free space elements in workspace data 136 or 116 and in workspace data 120. Identification of memory cells of workspace elements can be implemented using intelligent software, that is, pre-installed memory addresses or the system registry, or by using dialog boxes to ask questions to the user. In particular, the locator modules 415 in the base system 146 determine the memory addresses for the email folder 138, the file folder 142, the calendar folder 140 and the bookmark folder 144, as well as the memory addresses for the workspace elements in them. Locator modules 415 also determine the corresponding memory addresses for the corresponding folders in the workspace data 120 and the corresponding workspace elements in them.

Similarly, the locator modules 415 in the base system 118 define the memory cells of the workspace data elements 116 of the workspace and the memory cells of the corresponding workspace elements in the data spaces 120 of the workspace.

Obviously, locator modules 415 may include locator modules 415 specifically allocated for each folder or each type of data in the workspace. That is, locator modules 415 may include a locator module 415 allocated for determining the position of bookmarks, a locator module 415 dedicated for determining the position of an email, a locator module 415 dedicated for determining the position of files, a locator module 415 dedicated for determining the position of the calendar data for assigned events, etc. In addition, it is obvious that the locator modules 415 can identify the memory cells of the workspace elements at system startup or after each communication session with the global server 120 to maintain updated memory addresses of the workspace elements.

The sync trigger module 420 includes procedures for determining when to initiate synchronization of workspace data 136 or 116 with workspace data 120. For example, the synchronization start module 420 may initiate data synchronization upon a user's request at a specific time of the day, after a predetermined time interval has elapsed, after a predetermined number of changes, after some user action, for example, user’s logoff, or similar criteria. . A sync trigger module 420 initiates data synchronization, instructing common sync module (described below) to begin executing its procedures. Obviously, it is preferable to initiate communication with the synchronization agent 124 from within the LAN 110, since the conventional firewall 114 prevents the incoming communication from occurring and allows the outgoing communication.

General synchronization module 425 contains procedures for receiving version information 148 for modified versions from synchronization agent 124 (FIG. 1) and procedures for evaluating version information 255 or 150 compared to the latest synchronization signature 435 (for example, the last synchronization date and time ) to determine which versions have been modified. General synchronization module 425 also contains procedures for evaluating version information 148 and version information 255 or 150 to determine whether one or both versions of a particular workspace item or workspace items folder has been modified.

In addition, the common synchronization module 425 contains procedures for performing an appropriate synchronizing response action. The corresponding synchronization response actions may include (if only one version of the workspace element in the workspace data 136 or 116 has been modified) sending the modified version (as the preferred version) to another storage device (s) or determining and directing only the changes made. The calculation of the changes made can be performed by assessing the current state in comparison with the previous state, based on the last synchronization, or by comparing the two versions. Obviously, there is no need to consider changes based on the contents of the data. It is obvious that one storage device preferably sends only changes to another storage device in order to optimize the use of the processing power of the processor and minimize data transfer over communication channel 108 or 104.

Other appropriate sync responses may include (if two versions of the workspace element have been modified independently) instructing the sync module 430 described below to perform its procedures on content. That is, if two versions of the same workspace element were independently modified, it is preferable to review the changes based on the data content. After the data synchronization is complete, the general synchronization module 425 updates the latest synchronization signature 435.

Content synchronization module 430 includes procedures for agreeing on two or more modified versions of a workspace element. For example, if the user independently modified the original and a copy of the workspace element after the last synchronization, then the content synchronization module 430 determines the appropriate response action. Content synchronization module 430 may ask the user to choose a preferred version from among the modified versions, or may respond based on pre-defined preferences, that is, by storing both versions in both storage devices, or, preferably, by integrating the modified versions into a single preferred version. which replaces each modified version in both storage devices.

The synchronization module 430, by content, evaluates the changes made to each version and determines if there are any inconsistencies between them. When merging versions, a contradiction may arise if inconsistent modifications were made, such as deleting a paragraph in one version and changing the same paragraph in another version. If a contradiction occurs, then the content synchronization module 430 will attempt to remove the contradiction, for example, by asking the user to make his choice, or by storing both versions in both storage devices. Otherwise, if there is no contradiction, then the content synchronization module 430 merges the changes for each version and updates the information 148, 150 or 255 about the version, respectively.

FIG. 5 is a block diagram illustrating the details of the synchronization agent 124, which contains a communication module 505 (similar to the communication module 405, described above with reference to FIG. 4) and a general synchronization module 515 (similar to the general synchronization module 425, also described above with reference to Fig. 4).

The communication module 505 includes procedures for data compression and procedures for communicating with the base system 146 through the communication channel 108, or with the base system 118 through the communication channel 104. The communication module 505 may also include procedures for establishing a secure communication channel through the global firewall 112 and the LAN firewall 114 with the communication module 405.

Similar to general synchronization module 425, general synchronization module 515 includes procedures for evaluating version information 148 and the latest synchronization signature 435 (FIG. 4) for determining which versions have been modified and which changes have been made. Obviously, the common synchronization module 515 may maintain its own copy of the latest synchronization signature 435 (not shown), or it may request the latest synchronization signature 435 from the basic system 146 or 118. The general synchronization module 515 also includes procedures for sending data 120 of the workspace defined for the modification to the general synchronization module 425 and procedures for receiving preferred versions of the elements of the data workspace 136 or 116 of the workspace, or simply changing from the general synchronization module 425.

FIG. 6 shows an example of a bookmark workspace element in global format. Global translator 122 combines all the information needed for both formats (format A and format B) to create a global format. For example, if a bookmark in format A requires the elements X, Υ and Ζ, and a bookmark in format B requires the elements X and Υ, then the global translator 122 includes the elements X, Υ and Ζ to create the bookmark in a global format. In addition, the global translator 122 includes information that is required by the synchronization tool, for example, the last modified date. Accordingly, the tab in the global format contains the user ID (ID) 605, the record ID 610, the parent ID 615, the folder ID flag 620, the name 625, the description 630, the unified information resource pointer 635 (UIR, iKB). position 640, flag 645 of the remote ID, the last modified date 650, the created date 655, and flag 660 the partition ID.

FIG. 7 is a flowchart illustrating a method 700 of using the global translator 122 to synchronize multiple copies of a workspace element in a protected network 10. The implementation of the method begins with the fact that at step 705 the user interface module 410 allows the user to select the data workspace elements 136 and 118 space for the synchronization tool to synchronize. At step 710, locator modules 415 identify the memory cells of the elements of the workspace in the workspace data 136 and 116 and the corresponding memory cells in the workspace data 120. If the selected workspace element does not have a corresponding memory cell, for example, if a new work space element is added to the global server 106, then the memory cell is selected. The selected memory cell may represent a previously existing workspace element or a new workspace element. As stated above, identification of the memory cells of the workspace elements can be implemented using intelligent software tools or dialog boxes. A common synchronization module 425 and a common synchronization module 515, at step 715, set the previous state of the workspace elements to an empty set. Setting the previous state to an empty set indicates that all the information of the workspace element has been added.

At step 720, the sync trigger module 420 determines whether the predefined criteria are met, indicating that synchronization of the workspace elements selected in step 705 should be started. If the criteria are not met, then in sync trigger block 420 will remain in the idle state at 725, and it returns to step 720. Otherwise, the communication module 405 and the communication module 505 in step 730 establish a secure communication channel between themselves.

In step 735, the common synchronization module 425 and the common synchronization module 515 determine whether any elements of the workspace have been modified. That is, in step 740, the common synchronization module 425 evaluates information 255 or 150 about the version of each selected workspace element in the workspace data 136 or 116, matching it with the latest synchronization signature 435 to determine the position of the modified workspace elements. This comparison may include comparing the date of the last modification with the date of the last synchronization, or it may include comparing the current state with the previous state, based on the last interaction. Similarly, the common synchronization module 515 evaluates the version information 148 of each corresponding workspace element in the workspace data 120 and the last synchronization signature 435 to determine the position of the modified workspace elements.

If at step 735 the modified elements of the workspace or folder are not found, then at step 760, the common synchronization modules 425 and 515 update the last synchronization signature 435, and the execution of method 700 ends. Otherwise, shared synchronization module 425 determines at step 740 whether more than one version of the workspace element has been modified since the last synchronization.

If only one version has been modified, then at step 745, the corresponding shared synchronization module 425 or 515 determines the changes made. As stated above, the definition of the changes made can be implemented by comparing the current state of the workspace element with the previous state of the workspace element, based on the last interaction between them. If changes were made only to the version in the workspace data 120, then at step 750, the global translator 122 translates the changes to the format used by another storage device, and at step 755, the common synchronization module 515 sends the translated changes to the common synchronization module 425 element of the workspace in the data space 136 or 116. If the updated version is a workspace element in the workspace data 135 or 116, then the common synchronization module 425 sends these changes to the updated version to the global translator 122 for translation, and then to the common synchronization module 515 to update the obsolete workspace element in the desktop data space. General synchronization module 425 and general synchronization module 515 update 757 the previous state to reflect the current state based on this interaction. Then, execution of method 700 returns to step 735.

If shared sync module 425 determines at step 740 that multiple versions have been modified, then common sync module 425 calculates the changes for each version and instructs sync module 430 to evaluate content by data sync to determine if there are any contradictions. For example, synchronization module 430 by content may determine that there is a contradiction when the user deletes a paragraph in one version and modifies the same paragraph in another version. Content synchronization module 430 can determine that a contradiction does not exist if the user deletes different paragraphs in each version. If no contradiction is found, then the execution of method 700 proceeds to step 750 for broadcasting and sending changes in each version to another storage device. However, if a contradiction is found, then at step 775, the synchronization module 430 reconciles the modified versions by content. As stated above, the negotiation may include a request for instructions from the user, or be based on pre-selected preferences that involve the implementation of response actions, such as storing both versions in both storage devices. Then, execution of method 700 continues at step 750.

Obviously, at step 710, new work space elements and already existing work space elements with which new work space elements will be combined are set as modified, and the previous state is set to an empty set. Thus, the common synchronization module 425 will determine at step 740 that more than one version has been modified, and the content synchronization module 430 will determine at step 770 that inconsistencies do not exist. Changes in each storage device are broadcast and sent to another storage device. Accordingly, the two versions will be effectively combined and stored in each storage device.

For example, if a first bookmark folder was created on a desktop computer with a 134 ^ eB browser 152, a second folder was created on a remote terminal with a 102 ^ eB browser (not shown), the folder did not exist in the global server 106, and the user selected each of these folders for synchronization, then the synchronization tool effectively combines the first and second folders. That is, the common synchronization module 425 in the desktop computer 134 will determine that the first folder has been modified and the previous state is equal to the empty set. Shared sync module 425 will detect and send changes, that is, all elements of the first folder's workspace, to a new global folder in global server 106. Similarly, common sync module 425 on remote terminal 102 determines that, based on the last interaction, the previous state of any folder ( second or global) is an empty set. A common sync module 425 will command the sync module 430 to evaluate the changes made to each folder by content in order to determine if there is a conflict. Since there is no contradiction, shared sync module 425 will send changes to a global folder, and common sync module 515 will send its changes to a second storage device, merging the workspace elements of the first and second folders in the global folder and the second folder. The common sync module 515 will inform the common sync module 425 that the global folder has been modified since the last interaction and will send new changes to the first folder. Thus, the first and second folders will be merged and stored in each storage device.

As a second example, consider the case when the user can select a document in the LAN 110 that needs to be synchronized. The common synchronization module 425 will send this document to the global server 106. Similarly, the user can select the same document to synchronize on the remote terminal 102. The general synchronization module 515 will send this document to the remote terminal 102. If changes were made to these documents independently, then The sync module 430 by content will evaluate the contents of these documents to determine if there is a contradiction. If there is no contradiction, then, as described above, common synchronization modules 425 and 515 will merge these documents. Otherwise, if a contradiction exists, then the synchronization module 430 will agree on the changes by content, and then the common synchronization modules 425 and 515 will send the agreed changes to each other.

The above description of the preferred embodiments of the invention is given by way of example only; The present invention provides other versions of the above options and methods. For example, although global server 106 is shown as a single device, it may include several computers networked together. The elements of this invention can be implemented by using a general-purpose programmable digital computer, by using specialized integrated circuits, or by using a network consisting of interconnected known components and circuits. The options described here were presented for the purpose of illustration, and should not be considered exhaustive or considered as limitations. In the light of the above principles, many variations and modifications are possible.

Claims (33)

1. A system including a first storage device for storing a first workspace element in a first format, a second storage device for storing a second workspace element, which is an independently modifiable copy of a first workspace element, in a second format, a communication channel connecting the first storage a device with a second storage device, synchronization means for synchronizing the first element of the working space and the second element of the working space nstva and means for broadcasting between the first format and the second format. 2. The system of claim 1, wherein the first format is the same as the second format. 3. The system according to claim 1, in which the second format includes the language NTMB (hypertext language for describing documents). 4. The system according to claim 1, in which the first storage device is located in a local area network (LAN). 5. The system of claim 1, further comprising a firewall (access protection system) for protecting the first storage device. 6. The system of claim 1, further comprising a firewall for protecting the second storage device. 7. The system according to claim 1, in which the synchronization tool includes a first general synchronization module for checking the first workspace element in the first storage device to determine whether it has been modified, and a second general synchronization module for checking the second workspace element in a second memory device to determine if it has been modified. 8. The system according to claim 7, in which the first element of the workspace and the second element of the workspace contain each version information, and the first and second general synchronization modules check each version information of each element of the workspace according to the latest synchronization signature in order to determine if Whether this workspace item has been modified. 9. The system of claim 1, wherein the synchronization means includes a synchronization triggering module for determining when to initiate synchronization. 10. The system of claim 1, wherein the first workspace element includes a first folder and the second workspace element includes a second folder. 11. The system of claim 10, further comprising a content synchronization module for checking the contents of the first workspace element and the second workspace element, the first workspace element and the second workspace element being both modified after the last synchronization. 12. The system according to claim 11, in which the content synchronization module determines whether there are any contradictions, and if they exist, then the content synchronization module coordinates these contradictions. 13. The system according to claim 11, in which the content synchronization module determines whether there are any contradictions, and if there are none, then the content synchronization module integrates the changes made to each element of the workspace. 14. The system according to claim 1, further comprising a third storage device associated with the second storage device for storing the third element of the workspace in a third format. 15. The system of claim 14, wherein the translator broadcasts between the second format and the third format. 16. The system of claim 8, in which version information indicates the status of each element of the workspace according to the last synchronization. 17. A method including accessing a first storage device storing a first workspace element in a first format, accessing a second storage device storing a second workspace element, which is an independently modifiable copy of a first workspace element, in a second format, synchronizing the first a workspace element and a second workspace element and broadcast between the first format and the second format. 18. The method according to 17, in which the first format is the same as the second format. 19. The method according to 17, in which the second format includes the language NTM. 20. The method according to 17, in which the first storage device is located in a local area network (LAN). 21. The method according to 17, in which the first storage device is protected by a firewall. 22. The method according to 17, in which the second storage device is protected by a firewall. 23. The method according to 17, further comprising checking the first element of the workspace to determine whether it has been modified, and checking the second element of the workspace to determine whether it has been modified. 24. The method according to item 23, in which the first element of the workspace and the second element of the workspace include each version information, and additionally compares the version information of each element of the workspace according to the last synchronization signature in order to determine whether the element has been modified work space. 25. The method according to 17, further comprising determining the moment of initiation of synchronization. 26. The method according to 17, in which the first element of the workspace includes a first folder, and the second element of the workspace includes a second folder. 27. The method according to p. 26, further comprising checking the contents of the first element of the workspace and the second element of the workspace, and the first element of the workspace and the second element of the workspace are modified after the last synchronization. 28. The method according to item 27, further comprising determining whether there are any contradictions, and if they exist, then the coordination of these contradictions. 29. The method according to item 27, further comprising determining whether there are any contradictions, and if there are none, then the changes made to each element of the workspace are integrated. 30. The method according to 17, further comprising accessing a third storage device associated with a second storage device storing a third element of the workspace in a third format. 31. The method of claim 30, further comprising broadcasting between the second format and the third format. 32. The method according to paragraph 24, in which version information indicates the status of each element of the workspace according to the last synchronization. 33. A system including means for accessing a first storage device storing a first operating element