System and method for updating a remote database in a network
Abstract
This record has no abstract on file.
Term
Term ended
Expired 21 September 2019, 7 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
33 claims: 12 independent, 21 dependent
- 1クライアント・デバイス及び作業スペース・データベースに接続されているコンピュータ・ネットワークとともに使用するためのコンピュータ・ベースの方法であって、 前記クライアント・デバイスがダウンローダブルの識別を前記コンピュータ・ネットワークから受信するステップと、 前記クライアント・デバイスがダウンローダブルをダウンロードするステップと、 前記クライアント・デバイスが前記ダウンローダブルの実行を開始するステップと、 前記クライアント・デバイスが同期化すべき作業スペース・データを指定し、かつ同期化モードを指定する情報を受信するステップであって、指定された作業スペース・データは、前記作業スペース・データベースに格納されている、前記受信するステップと、 前記クライアント・デバイスが前記ダウンローダブルを使用して、前記クライアント・デバイスに保持された個人情報マネージャ(PIM)に、前記指定された作業スペース・データを検索するように指示するステップと、 前記クライアント・デバイスが前記ダウンローダブルを使用して、検索により得られた前記同期化すべき作業スペース・データおよび指定された前記同期化モードに基づいて、第1更新データを決定するステップと、そして 前記クライアント・デバイスが前記ダウンローダブルを使用して、前記第1更新データを前記コンピュータ・ネットワークに接続されたサーバ・データベースに供給するステップとを含むコンピュータ・ベースの方法。
- 2前記クライアント・デバイスは、前記作業スペース・データベースを含む、請求項1に記載の方法。
- 3前記クライアント・デバイスは、ブラウザを保持し、方法はダウンローダブルの前記識別を前記ブラウザを介して受信することを含む請求項1に記載の方法。
- 4前記同期化モードが、一方向置換同期化、一方向マージ同期化、および両方向同期化のうちの1つである請求項1に記載の方法。
- 5前記クライアント・デバイスが、前記サーバ・データベースと通信を行って、検索により得られた前記作業スペース・データと関連する前記サーバ・データベース内容を認識するステップと、そして 前記サーバ・データベース内容と検索により得られた前記作業スペース・データとを比較するステップとをさらに含む請求項1に記載の方法。
- 6第1更新データを決定するステップが、前記比較に基づく請求項5に記載の方法。
- 7前記クライアント・デバイスが第2更新データを前記比較に基づいて決定するステップであって、前記第2更新データは、前記作業スペース・データベースに格納された作業スペース・データを更新するためのものである、前記決定するステップと、そして検索により得られた前記作業スペース・データを前記第2更新データによって変更するように、前記PIMに指示するステップとをさらに含む請求項6に記載の方法。
- 8ダウンローダブルが前記サーバ・データベースからダウンロードされる、請求項1に記載の方法。
- 9前記作業スペース・データがEメール作業スペース・データを含む、請求項1-8のいずれかに記載の方法。
- 10前記受信情報がEメール・サービスを識別する、請求項9に記載の方法。
- 11同期化モードを選択し、そして前記同期化すべき作業スペース・データを含むデータベースを指定する、ことをユーザに可能にするためのユーザ・インタフェースを前記ダウンローダブルが含む、請求項1-10のいずれかに記載の方法。
- 12前記ダウンローダブルが前記更新データを計算するための同期化モジュールを含む、請求項1-11に記載の方法。
- 13前記ダウンローダブルがJavaアプレットを含む、請求項1-12に記載の方法。
- 14前記ダウンローダブルがActiveXコントロールを含む、請求項1-13に記載の方法。
- 15前記ダウンローダブルがプラグインを含む、請求項1-14に記載の方法。
- 16請求項1-15のいずれかに記載のステップをコンピュータに実行させるためのプログラム・コードを記憶しているコンピュータ可読記憶媒体。
- 17クライアント・デバイスであって、 ダウンローダブルの識別をコンピュータ・ネットワークから受信する手段と、 ダウンローダブルを前記クライアント・デバイスにダウンロードする手段と、 前記ダウンローダブルの実行を開始する手段と、 作業スペース・データを指定し、かつ同期化モードを指定する情報を受信する手段であって、指定された作業スペース・データは、前記コンピュータ・ネットワークに接続され た作 業スペース・データベースに格納されている、前記情報を受信する手段と、 前記ダウンローダブルを使用して、前記クライアント・デバイスに保持された個人情報マネージャ(PIM)に、指定された前記作業スペース・データを検索するように指示する手段と、 前記ダウンローダブルを使用して、第1更新データを検索により得られた前記作業スペース・データおよび前記同期化モードに基づいて決定する手段と、そして 前記ダウンローダブルを使用して、前記第1更新データを前記コンピュータ・ネットワークに接続されたサーバ・データベースに供給する手段とを含むクライアント・デバイス。
- 18前記クライアント・デバイスは、前記作業スペース・データベースを含む、請求項 17 に記載のクライアント・デバイス。
- 19前記同期化モードが一方向置換同期化、一方向マージ同期化、および両方向同期化のうちの1つである、請求項17に記載のクライアント・デバイス。
- 20前記ダウンローダブルが前記第1更新データを計算するための同期化モジュールを含む、請求項18または19に記載のクライアント・デバイス。
- 21Eメール作業スペース・データに対応するサーバ・データベース・コンテンツを学習し、前記サーバ・データベース・コンテンツと前記同期化モジュールとを比較するように、前記同期化モジュールが配置されている、請求項20に記載のクライアント・デバイス。
- 22前記比較に基づいて前記第1更新データを決定するように前記同期化モジュールが配置されている、請求項20に記載のクライアント・デバイス。
- 23前記比較に基づいて前記作業スペース・データベースに格納された作業スペース・データを更新するためのものである第2更新データを決定し、前記第2更新データにより検索により得られた前記作業スペース・データを修正するように前記PIMに命令するように、前記同期化モジュールが配置されている、請求項20に記載のクライアント・デバイス。
- 24前記ダウンローダブルが前記サーバ・データベースからダウンロードされる、請求項17-23に記載のクライアント・デバイス。
- 25前記作業スペース・データがユーザ・データ・ストアに含まれる、請求項17-24のいずれかに記載のクライアント・デバイス。
- 26前記作業スペース・データがEメール作業スペース・データを含む、請求項17-25のいずれかに記載のクライアント・デバイス。
- 27前記情報がEメール・サービスの識別を含む、請求項17-26のいずれかに記載のクライアント・デバイス。
- 28同期化モードを選択し、前記同期化すべき作業スペース・データを含むデータベースを指定する、ことをユーザに可能にするためのユーザ・インタフェースを前記ダウンローダブルが含む、請求項17-27のいずれかに記載のクライアント・デバイス。
- 29前記ダウンローダブルが前記更新データを計算するための同期化モジュールを含む、請求項17-28に記載のクライアント・デバイス。
- 30前記ダウンローダブルがJavaアプレットを含む、請求項17-29に記載のクライアント・デバイス。
- 31前記ダウンローダブルがActiveXコントロールを含む、請求項17-30に記載のクライアント・デバイス。
- 32前記ダウンローダブルがプラグインを含む、請求項17-31に記載のクライアント・デバイス。
- 33クライアント・コンピューティング・デバイスに実行させるプログラム・コードを記憶するコンピュータ可読記憶媒体であって、 ダウンローダブルの識別をコンピュータ・ネットワークから受信するステップと、 ダウンローダブルをダウンロードするステップと、 前記ダウンローダブルの実行を開始するステップと、 同期化すべき作業スペース・データを指定し、かつ同期化モードを指定する情報を受信するステップであって、指定された作業スペース・データは 、作 業スペース・データベースに格納されている、前記情報を受信するステップと、 前記ダウンローダブルを使用して、前記クライアント・コンピューティング・デバイスに保持された個人情報マネージャ(PIM)に、指定された前記作業スペース・データを検索するように指示するステップと、 前記ダウンローダブルを使用して、検索により得られた前記作業スペース・データおよび前記同期化モードに基づいて、第1更新データを決定するステップと、そして 前記ダウンローダブルを使用して、前記第1更新データを前記コンピュータ・ネットワークに接続されたサーバ・データベースに供給するステップとをコンピュータに実行させるプログラム・コードを記憶するコンピュータ可読記憶媒体。
Independent claims33
1 paragraph, as filed
[0001] (Background of invention) (1. Field of invention) The present invention relates generally to computer networks, and more particularly to providing systems and methods for updating remote databases in computer networks. [0002] (2. Explanation of background technology) Data accessibility and integrity are important concerns for computer users. For example, when a roaming user, that is, a user moving to a remote location, needs to review or manipulate data such as calendar or address information, the roaming user either carries the data to the remote location or remotely. You have to access the workstation. Keeping a genuine copy of the database is a tedious process. Therefore, system designers are developing a set of techniques for connecting remote terminals to workstations that store data over computer networks. [0003] To ensure the readability of the downloaded data, the user carries or requires a laptop computer that contains all the applications necessary to present the downloaded data and enable its operation. -You must find a networked computer that contains the program. In addition, users must keep a record of all identification and credentials for each database site they want to access. [0004] Therefore, there is a need for systems and methods that allow roaming users to easily access personal information stored on remote databases from any site connected over the network. It is also remote from the user's local data store, favorably using existing infrastructure such as browser technology and Internet communication infrastructure to make such systems easier to use and to facilitate the distribution of remote databases. Systems and methods are needed to easily move workspace data (such as in PIM) to the data store. [0005] (Outline of the invention) The present invention provides a system and method for updating a remote database in a computer network. Computer networks include global servers coupled to local and remote clients. The local client uses a browser to establish a communication link with the web server on the global server. The global server has memory for storing independently modifiable copies of workspace data (files, emails, calendar information, etc.) maintained by a personal information manager (PIM) on the local client. , Has a PIM downloadable to interface with these PIMs. [0006] A local client requests synchronization for a particular PIM. The global server sends a PIM download for a particular PIM to a local client, which installs the PIM download and starts running it. Therefore, the user interface receives information that specifies the workspace data to be synchronized and information that selects a synchronization mode such as one-way replacement synchronization, one-way merge synchronization, and two-way synchronization. The PIM interface directs a particular PIM to search for workspace data to be synchronized. The synchronization module determines the update data based on the selected synchronization mode and, in some cases, the actual comparison with the corresponding workspace data copy on the global server. The communication engine supplies the first update data to the global server, which updates the server workspace data. [0007] The billing system should search for the user interface, workspace data to be synchronized, to receive information that specifies the workspace data to be synchronized, and to receive information that selects the synchronization mode. Determine the first update data based on the PIM interface for directing the Personal Information Manager (PIM), the synchronization module coupled to the user interface, and the workspace data to be synchronized and the synchronization mode selected. Includes a PIM interface to do this, as well as a communication engine coupled to a synchronization module to supply the first update data to the server database. [0008] Another billing system is a memory that stores workspace data and PIM downloadability, a web server to establish a communication link with the client, to receive requests from the client for synchronization capabilities, and to synchronize. Memory-bound Personal Information Manager (PIM) downloadable search engine that transfers PIM downloadables, including features, to clients for installation, as well as to receive update data from downloadables and received update data. A memory-bound user data store manager for updating workspace data based on. [0009] The method of billing is to receive the information that specifies the workspace data to be synchronized, the step to receive the information to select the synchronization mode, and the personal information manager to search for the workspace data to be synchronized. A step to instruct (PIM), a step to determine the first update data based on the workspace data to be synchronized and the synchronization mode selected, and a step to supply the first update data to the server database. Including. [0010] Another billing method includes the step of storing workspace data and downloads, the step of establishing a communication link with the client, the step of receiving a request for the synchronization function from the client, and the synchronization function. It includes a step of transferring the downloadable to the client for installation, a step of receiving update data from the downloadable, and a step of updating the workspace data based on the received update data. [0011] The systems and methods of the present invention can advantageously allow synchronization of data corresponding to a particular PIM, or its one-way import to a global server over a network. This system and method can select the mode of synchronization or import. The system and method can automatically configure both local and remote clients to carry out the present invention. That is, the PIM download is downloaded from the global server, so the local client only needs to have the communication engine as provided by traditional browsers, as well as the PIM to get synchronization or import capabilities. .. [0012] (Detailed description of preferred embodiments) The present invention provides a system and method for updating a network database to store current PIM data, which data is coupled to the network and any remote running a communication engine such as a web browser. It can be accessed from the site. [0013] FIG. 1 is a block diagram illustrating a computer network 100 according to the present invention. The computer network 100 includes a global server 105 coupled to a local area network (LAN), commonly referred to as the intranet 115, via a computer network, such as a wide area network (WAN) commonly referred to as the Internet 110. A local client 120 and a personal computer with a calendar (PC) 125 are coupled to the intranet 115. The intranet 115, local client 120, and calendared PC 125 can be protected by firewall 130. Global server 105 will be protected by a global firewall (not shown). The computer network 100 further includes a remote client 135 coupled to the Internet 110. [0014] The global server 105 is a computer that includes a web server 140 for communicating with and responding to requests from a web browser. The global server 105 further includes a user data store 150 for storing user workspace data (files, calendar information, emails, bookmarks, etc.). FIG. 8 is a block diagram illustrating details of the user data store 150. The user data store 150 will include a first store 805 for user # 1, a second store 845 for user # 2, and so on. In addition, each store 805, 845 may contain a separate folder for each program. For example, the first store contains a first folder 815 for calendar data, a second folder 820 for address data, a third folder 825 for other PIM data, and so on. In addition, each folder 815, 820, 825 will also contain a separate workspace database specified by the user. For example, calendar data folder 815 contains a single calendar database 830 for personal calendars. Address data folder 820 contains three separate databases 835 (one for business addresses, one for personal addresses, and one for various addresses). Also, the other PIM data folder 825 may contain three separate databases 840. It will be appreciated that for synchronization purposes, individual records can be selected from one or more PIM workspace databases and recognized as a single database. [0015] Global Server 105 also includes PIM Downloadable 145. Downloadable is executable or interpretable application code that is downloaded from the source computer and executed on the destination computer. As used herein, the term "executable" includes "interpretable." Downloadables are typically required by ongoing processing, such as by an internet browser or web client. An example of a downloadable is Java developed by Sun Microsystems, Inc.<sup>TM</sup>Java designed for use in a distribution environment<sup>TM</sup>Applet, JavaScript also developed by Sun Microsystems, Inc.<sup>TM</sup>Script, ActiveX developed by Microsoft<sup>TM</sup>ActiveX designed for use in a distribution environment<sup>TM</sup>Controls, including Visual Basic, also developed by Microsoft. Downloadables can also include plug-ins, which enhance the functionality of existing application programs. It will be appreciated that each downloadable may include one or more applets, one or more ActiveX controls, one or more plugins, and / or a combination thereof. In addition, it will be understood that downloadables do not need to be deleted at logoff. Each PIM downloadable 145 can communicate with the corresponding PIM and can communicate with the global server 105 to update the user data store 150. Details of the PIM Downloadable 145 are shown in Figure 3. [0016] Global server 105 also includes an update engine 195, which searches for the appropriate PIM downloadable and downloads it to the local client 120. The update engine 195 also searches for workspace data contained within the user data store 150 and responds to requests to update it. The update engine is described in more detail in the context of Figure 3B. [0017] The local client 120 is a computer that includes a browser 175 for communicating with the global server 105 via the web server 140. It will be appreciated that the browser 175 may include a traditional web browser. The local client 120 further includes a first PIM 155 and a first PIM data 160. The first PIM155 may include a calendar program for managing calendar data, an address book program for managing addresses, an e-mail program for controlling e-mail, a browser for controlling bookmarks, and the like. Examples of the first PIM155 are Symantec's ACT !, Lotus Development's Lotus. Organazer (R) stand-alone organizer, Quicken<sup>TM</sup>, PeopleSoft<sup>TM</sup>, Salesperson automation information program, general-purpose file manager, etc. The local client further includes a second PIM client 165 and a second PIM data 170 for communicating with a second PIM server located on another computer connected to the local client 120. [0018] The second PIM PC 125 is a computer that includes a second PIM server 180 that responds to requests made by the second PIM client 165. The second PIM server and its interface can jointly provide calendar services, address services, electronic services, and so on. The second PIM PC 125 includes second PIM data 185 that is unique to the second PIM data 170 stored on the local client 120. Experts in the art have a second PIM 180 and a second PIM client 165 jointly on the local client 120 only, on the second PIM PC 125 only, on both the local client 120 and the second PIM PC 125, or Local client 120 and 2nd PIM It will be appreciated that the second PIM data can be stored on both PC125s in duplicate. For example, for email services, the second PIM PC125 remembers a copy of the received email, but downloads the copy to the local client 120 when requested by the email server interface. An example of the second PIM client 165 and server 180 is Microsoft Outlook<sup>TM</sup>And Exchange<sup>TM</sup>, Lotus Development's Lotus Organizer (R) and Lotus Notes<sup>TM</sup>, Novell, Inc. GroupWise<sup>TM</sup>And so on. [0019] The first PIM155 knows the location of the first PIM data 160. The second PIM client 165 knows the location of the second PIM data 170 on the local client 120. The second PIM server 180 knows the location of the second PIM data 185 located on the second PIM PC 125. Therefore, each component can search for its corresponding data. [0020] The remote client 135, including the browser 190, can connect to the web server 140 of the global server 105, access and review the workspace data stored in the user data store 150. , And in some cases, it can be operated. [0021] [0021] FIG. 2 is a block diagram illustrating computer system 200 showing details of the global server 105, local client 120, second PIM PC 125, and remote client 135, respectively. Computer system 200 is coupled to communication channel 220, Intel Includes a processor 205 such as a Pentium (R) microprocessor or Motorola Power PC (R) microprocessor. The computer system 200 also includes input devices 210 such as keyboards and mice, output devices 215 such as cathode ray tubes (CRT) displays, communication devices 225, data storage 230 such as magnetic disks, and random access memory (RAM). Such as working memory 235, each of which is coupled to communication channel 220. Communication channel 220 can be coupled to a network such as Internet 110 or Intranet 115. Data storage 230 and working memory 235 are illustrated as separate units to experts in the art, while data storage 230 and working memory are integrated or partially integrated units. It will be understood that it can be. [0022] Operating system 240 controls processing by processor 205 and is typically stored in data storage 230 and loaded into working memory 235 (shown) for execution. Other programs such as browsers, servers, downloadables, and data will also be stored in data storage 230 and loaded into working memory 235 (shown) for execution by processor 205. [0023] Experts in the field also include input / output lines for the computer system 200 to transmit information over network connections, additional memory, additional processors, LANs, and hardware channels, the Internet, or intranets. You will understand that it can be included. Experts in the art will also understand that programs and data can be received and stored by the system in an alternative manner. For example, computer readable storage media (CRSM) readers 245 such as floppy disk drives, hard disk drives, CD-ROM readers, magneto-optical readers, CPUs (for RAM), magnetic disks, hard disks, optical It can be coupled to communication channel 220 to read computer readable storage media (CRSM) 250 such as magneto-optical disks, RAM. Therefore, the system 200 is capable of receiving programs and data via the CRSM reader 240. [0024] FIG. 3A is a block diagram showing the details of the PIM downloadable 145. Each PIM downloadable 145 includes a user interface 305, a first PIM application program interface (API) 310, a second PIM client interface 315, a communication engine 320, and a synchronization module 325. [0025] User interface 305 allows the user to specify the workspace data to be synchronized, allows the user to select a synchronization mode (one-way replacement, one-way merge, or two-way synchronization), and the user. But allows synchronization to start. Examples of different modes of synchronization are shown in FIGS. 5, 6, and 7, respectively. Specifying the workspace data to be synchronized is separate within the user data store (eg, user # 1 store 805) that corresponds to the identified user (eg, user # 1), as shown in Figure 8. Database (eg, database 830) is maintained on web server 140. For example, the user can use Outlook for synchronization.<sup>TM</sup>You can select the user's business address data maintained by the address book. The synchronization module 325 will recognize this database for synchronization. Web server 140 determines if the corresponding database already exists. If it does not exist, the web server 140 creates the corresponding empty database and adds this empty database to the user data store 150. [0026] The first PIM interface 310 contains program code for enabling the PIM downloadable 145 to communicate with the first PIM 155. In addition, the first PIM interface 310 requests the first PIM 155 to search the appropriate database of the first PIM data 160 for synchronization. In response, the first PIM155 searches the appropriate databases and passes them to the PIM downloadable 145. Alternatively, the first PIM155 informs the PIM downloadable 145 of the appropriate database location. [0027] The second PIM client interface 315 contains program code that allows the PIM downloadable 145 to communicate with the second PIM client 165. In addition, the second PIM client interface 315 requests the second PIM client 165 to search the appropriate database for the second PIM data 170 and the second PIM data 185. In response, the second PIM client 165 tells the second PIM server 180 to search the second PIM data 170 for the appropriate workspace data and the second PIM data 185 for the appropriate workspace data. Request. The second PIM client 165 passes the workspace data from the second PIM data 170 and the second PIM data 185 to the PIM downloadable 145. Alternatively, the second PIM client 165 can notify the PIM downloadable 145 of the location of the database on the second PIM data 170 and the second PIM data 185. In another alternative, the second PIM client 165 is the second PIM. Appropriate workspace data can be retrieved from the second PIM data 185 on the PC125 and stored locally with the second PIM data 170. The second PIM client 165 can then notify the PIM downloadable 145 of the appropriate database location. It will be appreciated that other ways are possible to allow the PIM Downloadable 145 to access workspace data. It will be appreciated that the second PIM client interface 315 can be contained within a separate PIM downloadable 145 with a second instance of user interface 305, a communication engine 320, and a synchronization module 325. [0028] The communication engine 320 contains program code that enables the PIM downloadable 145 to communicate with the web server 140, optionally via a browser 175. [0029] Upon request, the synchronization module 325 directs the first PIM interface 310 or the second PIM client interface 315 to perform a service that retrieves workspace data to be synchronized. The synchronization module 325 also requests the web server 140 to retrieve workspace data from the user data store 150 on the global server 105 and requests this information from the local client over the Internet. Pass to 120. Alternatively, if the previous status of the database stored on global server 105 is known, synchronization module 325 can only request changes made since then. In any case, the synchronization module 325 only needs to know the contents of the corresponding database stored in the user data store 250 on the global server 105. The synchronization module 325 compares the data contained in the local client 120 database with the data contained in the corresponding global server 105 database and performs a synchronization response accordingly. The three modes of synchronization, namely one-way merge synchronization, one-way substitution synchronization, and two-way synchronization, are illustrated and described below in the context of FIGS. 5, 6, and 7. When performing a one-way replace operation, synchronization module 325 does not need to know what is contained in the corresponding database stored in user data store 150 on global server 105 (because it does not need to know what is contained in the corresponding database. It will be understood (because its contents are overwritten and therefore irrelevant). [0030] FIG. 3B is a block diagram illustrating details of the update engine 195. Update engines include a communications engine 350, a PIM downloadable search engine 355, and a user data store manager 360. The communication engine 350 communicates with the communication engine 320 of the PIM downloadable 145. The PIM Downloadable Search Engine 355 receives a request for synchronization from the local client 120. Each request can identify a particular PIM, or otherwise, a service such as an address book, calendar, or email for which synchronization is desired. If only the service is identified, the PIM Downloadable Search Engine 355 determines the PIM based on the previous selection corresponding to the identified service. User data store manager 360 controls the retrieval and manipulation of workspace data contained within user data store 150. That is, the user data store manager 360 looks up the workspace data for the server database identified by PIM Downloadable 145 as the database to synchronize. User Data Store Manager 360 transfers the corresponding workspace data to PIM Downloadable 145 for comparison with the database maintained by PIM. User Data Store Manager 360 also modifies the server database based on the update data received from PIM Downloadable 145. [0031] FIG. 4 is a flow chart illustrating a method 400 of synchronizing PIM data with the global server 105 according to the present invention. Method 400 begins in step 405 by requesting a connection to global server 105 by local client 120 using browser 175 and common URL technology. Browser 175 and web server 140 establish a communication link in step 410. The web server 140 sends HTML data to the browser 175 to set up the user interface in step 415. This includes requests for user identification and authentication information. In step 420, browser 175 sends user identification and authentication information to web server 140, which identifies and authenticates the user. [0032] The local client 120 makes a request for synchronization functionality for a particular PIM, such as for the first PIM155, in step 425. The PIM downloadable search engine 355 downloads the PIM downloadable 145 for a particular PIM to the local client 120 via the browser 175 in step 430, if necessary. Step 430 is unnecessary if the downloadable 145 has already been downloaded or stored on the local client 120. Browser 175 installs PIM Downloadable 145 in step 435. Installing the downloadable 145 involves moving the downloadable to working memory for execution. Local client 120 requests synchronization of a particular PIM database in step 440. The local client 120 selects one of the three available modes of synchronization described in detail in the context of Figures 5-7, although other modes are possible in step 443. Consists of PIM Downloadable 145. Browser 175 initiates execution of PIM Downloadable 145 in step 445. As the PIM interface corresponding to the PIM that maintains the database (eg, first PIM interface 310) searches for PIM workspace data (eg, PIM data 160 contained within the PIM database) in step 450. Request to PIM (eg PIM155). The PIM downloadable 145 performs synchronization with the global server 105 in step 455 according to the synchronization mode previously selected in step 440. Method 400 ends here. [0033] FIG. 5 is a flow chart illustrating a method 500 for replacing data, which is referred to as a replacement synchronization mode in the present specification. Method 500 shows a first example of performing step 455. Method 500 begins with synchronization module 325 receiving PIM data for the selected database from PIM, eg, first PIM155, in step 505. The synchronization module 325 uses the communication module in step 510 to transfer the PIM data to the web server 140. In step 515, the user data store manager 360 replaces the workspace data of the selected database in the user data store 150 with the transferred workspace data. Method 500 ends here. [0034] For example, if the database maintained by PIM contains strictly records A, B, D, then synchronization module 325 will be on global server 105 regardless of the contents of the database on global server 105. , B, D will be uploaded. User Data Store Manager 360 will replace the workspace data on Global Server 105 with the uploaded workspace data. Therefore, both the database maintained by Global Server 105 and the database maintained by PIM will store exactly A, B, and D. [0035] FIG. 6 is a flow chart illustrating a method 600 for merging data, which is referred to herein as a "merging synchronization mode". Method 600 shows a second example of performing step 455. Method 600 begins with synchronization module 325 receiving PIM data for the selected database from a PIM, eg, a first PIM 155, in step 605. The synchronization module 325 knows the contents of the corresponding database on the global server 105 in step 610. Knowing the contents of the database on Global Server 105 may include downloading the entire contents of the database, or using software cache technology to download the differences from the last download. The synchronization module 325 compares the database contents in step 615 and how the database maintained by PIM has changed (updated) in relation to the database maintained on global server 105. ) Determine the update data indicating. For example, a record can be deleted, added, or modified since the last connection, a document can have been modified since the last connection, and so on. The synchronization module 325 instructs the communication module in step 620 to send the update data to the global server 105. User data store manager 360 adds (etc.) update data to the database in user data store 150 in step 625. Method 600 ends here. [0036] For example, the database maintained by PIM may contain records A, B, D, and the database maintained by global server 105 may contain records A, B, C. Synchronization module 325 compares the contents of the database and finds that the database maintained by global server 105 does not contain record D. Therefore, synchronization module 325 transfers record D to global server 105, which records the record in the corresponding database. Therefore, the database maintained by Global Server 105 will contain records A, B, C, D, and the database maintained by PIM will contain records A, B, D. [0037] In another example, the database maintained by PIM may contain records A, B, C, D and the database on the global server may contain records A, B, C, D. In that case, when record C is deleted, the synchronization module 325 determines that record C has been deleted based on the version information. Therefore, synchronization module 325 may do nothing so that the superset is maintained on global server 105. Therefore, the database on global server 105 will contain records A, B, C, D, and the database maintained by PIM will contain records A, B, D. Alternatively, synchronization module 325 can notify web server 140 that record C has been deleted, and user data store manager 360 will address record C on global server 105. It can be deleted from the database. In this case, the database maintained by global server 105 and the database maintained by PIM will contain records A, B, and D, respectively. [0038] FIG. 7 is a flow chart illustrating a method 700 for performing bidirectional synchronization, referred to herein as a "bidirectional synchronization mode". Method 700 begins with synchronization module 325 receiving PIM data for the selected database from PIM, eg, first PIM155, in step 705. The synchronization module 325 knows the contents of the corresponding database on the global server 105 in step 710. The synchronization module 325 compares the workspace data from the database in step 715 and how the database maintained by PIM is updated in relation to the database maintained on global server 105. Determines the update data that indicates how it was updated, as well as the update data that indicates how the database on the global server was updated in relation to the database maintained by PIM. As mentioned earlier, workspace data in the database maintained by PIM may have been deleted, added, or modified. The synchronization module 325 sends the update data to the global server 105 in step 720. User data store manager 360 adds update data to the database in user data store 150 in step 725. The PIM interface, eg, the first PIM interface 310, instructs the PIM, eg, the first PIM155, in step 730 to add the update information to the PIM data 160 in the appropriate database. PIM adds the update data to the database in step 735. Method 700 ends here. [0039] For example, the database maintained by PIM may contain records A, B, D, and the database on global server 105 may contain records A, B, C. Synchronization module 325 compares the workspace data and finds that the database maintained by PIM does not contain record C and the database on global server 105 does not contain record D. Therefore, synchronization module 325 will send record D to global server 105, and the PIM interface will instruct PIM to store record C in the appropriate database. [0040] The above description of preferred embodiments of the present invention is merely an example, and other modifications and modifications of the above embodiments and methods are possible in the light of the above teachings. For example, although the present invention has been described in the context of a browser, any web engine for communicating with a web server can be used as an alternative. Although this system has been described as having only two PIMs (and therefore only two PIM interfaces, only two PIM downloadables, etc.), experts in the art have stated that any number of PIMs , Will understand that it can be controlled by the systems and methods of the invention. Workspace data was defined primarily in relation to email, calendars, bookmarks, etc., but experts in the art have found that workspace data includes other types of data such as files, financial transactions, etc. You will understand what you get. The PIM downloadable has been described as including a PIM interface to communicate with the PIM and obtain the data to be synchronized, but experts in the art know that the downloadable has the location of the data. If so, you will understand that you don't need a PIM interface. Therefore, downloadables can use the engine to retrieve data from known locations without the assistance of PIM. Network sites have been described as separate and distinct sites, but experts in the art have stated that these sites may be part of an integrated site, each of which may contain parts of multiple sites, or You will understand that it can include a combination of single site and multiple sites. Although each of the network sites has been described as a single computer, experts in the art will understand that each site can contain multiple computers. In addition, the components of the invention are conventional components that use programmed general purpose digital computers, use application-specific integrated circuits, or are interconnected. It can be implemented using a network of components and circuits. The connection can be wired, wireless, modem, etc. The embodiments described herein are not intended to be exhaustive or restrictive. The present invention is limited only by the above claims. [Simple explanation of drawings] FIG. 1 is a block diagram illustrating a computer network according to the present invention. FIG. 2 is a block diagram illustrating details of a computer. 3A is a block diagram illustrating details of the PIM downloadable of FIG. 1. FIG. 3B is a block diagram illustrating details of the update engine of FIG. 1. FIG. FIG. 4 is a flow chart illustrating a method of updating a global server according to the present invention. FIG. 5 is a flow chart illustrating a synchronization mode of one-way data replacement. FIG. 6 is a flow chart illustrating a synchronization mode of unidirectional data merging. FIG. 7 is a flow chart illustrating a synchronization mode for bidirectional data synchronization. 8 is a block diagram illustrating details of the user data store of FIG. 1. FIG.
Every citation, both waysCites: the store holds 0 of 1
| Reference | Relation |
|---|---|
| ファイル同期術,CYBIZ CYBIZ,日本,株式会社サイビズ,1997年 8月 1日,第2巻,第9号,p.42-43 | Non-patent |
| 笠原 一輝,デスクトップパソコンとノートパソコンとの連携,Mobile PC,日本,ソフトバンク株式会社,1997年12月 1日,第3巻,第12号,p.48-53 | Non-patent |
| 村上 健太,ノーツとザウルスの情報の同期を実現ロータスイージーシンクR2.0[ロータス],Lotus Notesmagazine,日本,ソフトバンク株式会社,1998年10月13日,No.24,p.56-57 | Non-patent |
| 笠原 一輝,PDA活用最前線:ノーツと携帯端末の賢い使い方を考える,Lotus Notes magazine,日本,ソフトバンク株式会社 SOFTBANK CORP.,1998年 7月13日,No.21,p.51-54 | Non-patent |
14 members in 8 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 09167044 | United States of America | – | |
| 16704498 | United States of America | A | |
| 16704498 | United States of America | A | |
| 9921723 | United States of America | W | |
| 9921723 | United States of America | W | |
| 1998167044 | – | – | – |
| 1999021723 | – | – | – |
| US19980167044 | – | – | – |
| WO1999US21723 | – | – | – |
Members14
| Document | Office | Kind | |
|---|---|---|---|
| WO0020994A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US6131096A | United States of America | A | |
| EP1127321A1 | European Patent Office (EPO) | A1 | |
| EA200100420A1 | Eurasian Patent Organization (EAPO) | A1 | |
| CN1325515A | China | A | |
| HK1042572A1 | Hong Kong, China | A1 | |
| JP2002526864A | Japan | A | |
| EA003156B1 | Eurasian Patent Organization (EAPO) | B1 | |
| CN1129083C | China | C | |
| HK1042572B | Hong Kong, China | B | |
| EP1127321A4 | European Patent Office (EPO) | A4 | |
| JP4757384B2This record | Japan | B2 | |
| EP1127321B1 | European Patent Office (EPO) | B1 | |
| ES2415179T3 | Spain | T3 |
40 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of completion of termEXPY | EXPY | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Written notification of registration of transferJAPANESE INTERMEDIATE CODE: R350R350 | R350 | |
| Request for change of ownership or part of ownershipJAPANESE INTERMEDIATE CODE: R313113S111 | S111 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Written notification of registration of transferJAPANESE INTERMEDIATE CODE: R350R350 | R350 | |
| Request for change of ownership or part of ownershipJAPANESE INTERMEDIATE CODE: R313113S111 | S111 | |
| Written request for registration of change of domicileJAPANESE INTERMEDIATE CODE: R313531S531 | S531 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Written notification of registration of transferJAPANESE INTERMEDIATE CODE: R350R350 | R350 | |
| Written request for registration of change of domicileJAPANESE INTERMEDIATE CODE: R313531S531 | S531 | |
| Written request for registration of change of nameJAPANESE INTERMEDIATE CODE: R313533S533 | S533 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Notification of resignation of power of attorneyJAPANESE INTERMEDIATE CODE: A7424RD04 | RD04 | |
| Notification of appointment of power of attorneyJAPANESE INTERMEDIATE CODE: A7423RD03 | RD03 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 4757384
- Publication, DOCDB
- 4757384
- Publication, EPODOC
- JP4757384B
- Application
- 2000575049
- Application, DOCDB
- 2000575049
- Application, EPODOC
- JP20000575049
Titles2
- Japanese
- ネットワークにおいて遠隔データベースを更新するためのシステムおよび方法
- English
- Systems and methods for updating remote databases in your network
Classification
- CPC, 2
- G06F16/275
- G06F16/273
- IPC, 2
- G06F12 00
- G06F17 30