WO2013190685A1

WO2013190685A1 - Synchronization server, synchronization method, and program

Info

Publication number: WO2013190685A1
Application number: PCT/JP2012/065894
Authority: WO
Inventors: 那由他石井; 泰大山本; 恭平倉世古; 拓嗣島田
Original assignee: 株式会社Ｓｙｎｃｌｏｇｕｅ
Priority date: 2012-06-21
Filing date: 2012-06-21
Publication date: 2013-12-27

Abstract

The purpose of the invention is to reduce the storage capacity and the amount of communication when an application is synchronized among a plurality of computers. A synchronization server stores a plurality of components required when an application is executed, in a component storage section, receives, from a computer, component identification information identifying the content of each of the plurality of components of the application in the computer, identifies a component having a different content from the component stored in the component storage section among the components in the computer on the basis of the component identification information, sends component information indicating the identified component to the computer, receives the component corresponding to the component information from the computer, and stores the component received from the computer in the component storage section.

Description

Synchronization server, synchronization method, and program

The present invention relates to a synchronization server, a synchronization method, and a program.

An information processing apparatus such as a personal computer (PC) or a mobile terminal can execute various applications such as document creation software and a web browser. Normally, such an application is used after being installed for each information processing apparatus. Therefore, for example, when a user who has a plurality of PCs uses the same application on the plurality of PCs, it is necessary to individually install the application on each PC. Further, user settings for using the application need to be individually made in each PC. As described above, it is often very complicated to use the same application on a plurality of PCs.

In addition, by using services such as SaaS (Software as a Service) that are becoming popular in recent years, a configuration in which an application is not individually installed on each PC is also conceivable (for example, Patent Document 1). However, when such a service is used, available applications are limited to those provided by service providers.

JP 2009-277089 A

Therefore, for example, it is conceivable to synchronize the applications installed on one PC among a plurality of PCs, instead of installing the applications individually on each PC. For example, constituent elements such as an execution file and a data file that are required when executing an application to be synchronized can be synchronized between PCs via a synchronization server. In this case, for example, the synchronization server can store the components transmitted from each PC for each user. However, if the synchronization server stores the components for each user, the storage capacity required in the synchronization server and the communication amount between the PC and the synchronization server become enormous with the increase in users.

Accordingly, an object of the present invention is to reduce the storage capacity and communication amount when synchronizing applications among a plurality of computers.

A synchronization server according to an aspect of the present invention includes a component storage unit that stores a plurality of components necessary for executing an application, and a configuration for identifying the contents of each of the plurality of components of the application in the computer from the computer An identification information receiving unit that receives element identification information, and a configuration that identifies a component having a different content from the component stored in the component storage unit among a plurality of components in the computer based on the component identification information An element specifying unit, a component information transmitting unit that transmits component information indicating the specified component to the computer, a component receiving unit that receives a component according to the component information from the computer, and a component received from the computer A component management unit that stores the component in a component storage unit.

In the synchronization method according to one aspect of the present invention, the synchronization server stores a plurality of components necessary for executing the application in the component storage unit, and each of the plurality of components of the application in the computer from the computer. The component identification information for identifying the content of the component is received and, based on the component identification information, the component having a content different from the component stored in the component storage unit is specified among the plurality of components in the computer. The component information indicating the identified component is transmitted to the computer, the component corresponding to the component information is received from the computer, and the component received from the computer is stored in the component storage unit.

In addition, a program according to one aspect of the present invention includes an identification information generation unit that generates a component identification information for identifying the contents of each of a plurality of components necessary for executing a computer, and a generated component An identification information transmitting unit that transmits identification information to a synchronization server for synchronizing application components between a plurality of computers, and a component indicating a component that is not stored in the synchronization server with the same content among the plurality of components This is to function as a component information receiving unit that receives information and a component transmission unit that transmits the component indicated by the component information to the synchronization server.

In the present invention, the “unit” does not simply mean a physical means, but includes a case where the function of the “unit” is realized by software. Also, even if the functions of one “unit” or device are realized by two or more physical means or devices, the functions of two or more “units” or devices are realized by one physical means or device. May be.

According to the present invention, it is possible to reduce the storage capacity and communication amount when synchronizing applications among a plurality of computers.

It is a figure which shows the structural example of the application synchronization system which is one Embodiment of this invention. It is a block diagram which shows an example of the function which a synchronous server has. It is a figure which shows an example of a structure of the component-specific component memory | storage part. It is a figure which shows an example of a structure of a common component storage part. It is a figure for demonstrating an example of the data storage in a component memory | storage part. It is a block diagram which shows an example of the function which PC has. It is a figure which shows an example of the screen displayed in the case of a synchronous setting. It is a figure which shows an example of a structure of a synchronous setting memory | storage part. It is a figure which shows an example of the screen displayed when starting a synchronous application. It is a flowchart which shows an example of an application synchronous process.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of an application synchronization system according to an embodiment of the present invention. As shown in FIG. 1, the application synchronization system includes a synchronization server 10 and a plurality of personal computers (PCs) 20. The synchronization server 10 provides a service for enabling a user to synchronize an application among a plurality of PCs 20, and is configured using one or a plurality of information processing apparatuses. The PC 20 is an information processing apparatus that allows a user to execute an application, and can communicate with the synchronization server 10 via a network such as the Internet.

Here, for example, it is assumed that the user “USER001” has two PCs, PC20-1 and PC20-2. By using the application synchronization system provided by the synchronization server 10, the user “USER001” does not need to install an application individually on each PC or manually synchronize data, and the PC 20-1 and the PC 20- It is possible to execute the application in a synchronized state in FIG. Here, the application synchronization means that the execution environment of the application is in the same state. The execution environment includes components necessary for executing the application. The application components include, for example, an execution file, a user file, setting information, and the like. By synchronizing applications among a plurality of PCs, the user can execute the applications in the same state regardless of which PC is used.

FIG. 2 is a block diagram illustrating an example of the functions of the synchronization server 10. As shown in FIG. 2, the synchronization server 10 includes an account information storage unit 30, a component storage unit 32, and a synchronization processing unit 34. These units can be realized, for example, by using a storage area such as a memory or a storage device, or by executing a program stored in the storage area by a processor.

The account information storage unit 30 stores account information of users who use the application synchronization system. For example, the account information includes a user ID, a password, an email address, and the like.

The component storage unit 32 stores components of a synchronization target application (synchronization application). As described above, the component is necessary for executing the synchronization application, and includes an execution file, a user file, setting information, and the like. As shown in FIG. 2, the component storage unit 32 can include a common component storage unit 40 and an individual component storage unit 42.

The common component storage unit 40 stores a common component (common component) among a plurality of users. FIG. 3 shows an example of the configuration of the common component storage unit 40. As shown in FIG. 3, the common component storage unit 40 includes a common component table and data storage. The common component table stores application ID (APL-ID), file ID, attribute information, identification information, and common user ID, and the data storage stores data of the file indicated by the file ID. .

Application ID is for identifying the synchronous application selected by each user. This application ID may be set, for example, when the user registers the synchronization application in the synchronization server 10 or may be generated on the synchronization server 10 side.

The file is a file that is a component of the synchronization application. The file includes an execution file, an application file such as a DLL (Dynamic Link Library), and a user file having user data necessary for executing a synchronous application. Here, the user data is data for each user that is referred to when the application is executed. For example, each user's e-mail data in an e-mail application for sending and receiving e-mails and each user's data in a web browser For example, bookmark data.

The file ID is an identifier of the file, and can be a file name including folder information, for example. The attribute information is information indicating a file attribute, for example, information indicating a file size, a file update date, and the like. The identification information (component identification information) is information for identifying the contents of the file. In this embodiment, a hash value calculated based on the file contents is used as identification information. The identification information is not limited to the hash value, and any information can be used as long as the information can identify the contents of the file. The common user ID is for identifying users who share the constituent elements, and the user ID registered in the account information storage unit 30 is used.

In the data storage, file data indicated by the file ID is stored. In the example shown in FIG. 3, the data of each file is stored in the data storage using the file ID and identification information (hash value) as keys. As described above, by adding not only the file ID but also identification information to the key, it is possible to identify files having the same file ID but different contents. If the file can be uniquely identified only by the identification information, the data of each file may be stored in the data storage using only the identification information as a key.

The individual component storage unit 42 stores components (individual components) having different contents depending on the user. FIG. 4 shows an example of the configuration of the individual component storage unit 42. As shown in FIG. 4, the individual component storage unit 42 includes an individual component table and a data storage. The individual component table stores a user ID, an application ID (APL-ID), a file ID, attribute information, and identification information, and the data storage stores file data indicated by the file ID. Other data items are the same as those of the common component storage unit 40.

Note that the components stored in the individual component storage unit 42 may be encrypted. For example, the data of the constituent elements may be stored in the data storage in a state encrypted with a predetermined encryption method. Further, the data storage of the common component storage unit 40 and the data storage of the individual component storage unit 42 may be configured by the same data storage. Even in this case, by using the file ID and the identification information (hash value) as a key, the data of each file of the common component and the individual component can be stored in the data storage.

FIG. 5 is a diagram for explaining an example of data storage in the component storage unit 32. An example of storing a component of an application in the component storage unit 32 will be described. FIG. 5 shows an example in which the component storage unit 32 stores components owned by two users (USER001, USER002).

As shown in FIG. 5, as a component of an application, a user (USER001) has A, B, C, and D, and a user (USER002) has A, B ′, C, and D ′. Suppose you are. That is, the components A and C are common among users, and other components are different for each user. The components B and B ′ are files having the same file ID but different contents. The same applies to the components D and D ′.

First, the user (USER001) uses his / her PC 20 to transmit a component to the synchronization server 10, and then the user (USER002) uses his / her PC 20 to transmit the component to the synchronization server 10. And In this case, the components A and C are already stored in the component storage unit 32 when the user (USER002) transmits the components to the synchronization server 10. Therefore, the components A and C are stored in the common component storage unit 40, and the user (USER002) does not need to transmit the components A and C to the synchronization server 10. On the other hand, the components B and D are stored in the individual component storage unit 42 as components dedicated to the user (USER001). Similarly, the constituent elements B ′ and D ′ are stored in the individual constituent element storage unit 42 as constituent elements dedicated to the user (USER002).

2, the synchronization processing unit 34 can execute various processes for synchronizing application components between the synchronization server 10 and the PC 20. As shown in FIG. 2, the synchronization processing unit 34 includes an authentication processing unit 50, an identification information receiving unit 52, a component specifying unit 54, a component transmitting unit 56, a component information transmitting unit 58, a component receiving unit 60, and The component management unit 62 may be included.

The authentication processing unit 50 performs user authentication in response to an authentication request from the PC 20. The authentication request includes, for example, account information such as a user ID and a password. The authentication processing unit 50 can perform user authentication by checking account information received from the PC 20 with account information stored in the account information storage unit 30.

The identification information receiving unit 52 can receive an application ID, a file ID, attribute information, and identification information for each component of the synchronous application in the PC 20 from the PC 20.

The component specifying unit 54 can specify a component transmitted (uploaded) from the PC 20 to the synchronization server 10 and a component transmitted (downloaded) from the synchronization server 10 to the PC 20. Specifically, the component specifying unit 54 specifies a component having a content different from that of the component stored in the component storage unit 32 based on the identification information received by the identification information receiving unit 52. For example, for each application ID and file ID, the component specifying unit 54 determines the difference between the components by comparing the identification information received from the PC 20 with the identification information stored in the component storage unit 32. can do. Note that the component specifying unit 54 also compares the components stored in the individual component storage unit 42 in association with the user IDs of other users. Here, it is not necessary to upload the components determined to have the same contents between the synchronization server 10 and the PC 20.

On the other hand, constituent elements determined to have different contents between the synchronization server 10 and the PC 20 are subject to upload or download. Then, the component specifying unit 54 determines whether to perform upload or download by comparing the update date and time for the components determined to have different contents between the synchronization server 10 and the PC 20.

Specifically, the constituent element specifying unit 54 stores the constituent elements determined to have different contents in the synchronization server 10 by comparing the update date and time for each user ID, application ID, and file ID. It can be determined which of the component and the component stored in the PC 20 is newer. Then, the component specifying unit 54 specifies, as upload targets, components that have a newer update date and time on the PC 20 and components that exist only on the PC 20. Further, the component specifying unit 54 specifies, as download targets, components that have a newer update date and time in the synchronization server 10 and components that exist only in the synchronization server 10.

The component transmitting unit 56 transmits the component specified as the download target by the component specifying unit 54 to the PC 20 that has transmitted the identification information.

The component information transmitting unit 58 transmits component information indicating the component to be uploaded identified by the component identifying unit 54 to the PC 20 that has transmitted the identification information. The component element information is information with which the component element can be specified in the PC 20, and can be a file ID, for example.

The component receiving unit 60 receives components transmitted from the PC 20 according to the component information. That is, the component receiving unit 60 receives the component specified by the component specifying unit 54 from the PC 20. The component receiving unit 60 can receive the user ID, application ID, and identification information (hash value) from the PC 20 together with the components.

The component management unit 62 manages the components stored in the component storage unit 32. Specifically, the component management unit 62 stores the component received by the component reception unit 60 in the individual component storage unit 42 in association with the user ID, application ID, and identification information (hash value). To do. In addition, the component management unit 62 includes components determined to be the same among a plurality of users by the component specifying unit 54 among the components stored in the individual component storage unit 42. Move to the common component storage unit 40.

Furthermore, the component management unit 62 uploads a new component having a different content as the component of the user for the component stored in the common component storage unit 40 in association with the user ID of a certain user. In this case, the user ID can be deleted from the components stored in the common component storage unit 40. When there is one user ID (common user ID) associated with the component by this deletion, the component management unit 62 can move this component to the individual component storage unit 42.

FIG. 6 is a block diagram illustrating an example of functions that the PC 20 has. As illustrated in FIG. 6, the PC 20 includes a file storage unit 100, an application execution unit 102, a synchronization setting unit 104, a synchronization setting storage unit 106, an application activation unit 108, and a synchronization processing unit 110. These units can be realized, for example, by using a storage area such as a memory or a storage device, or by executing a program stored in the storage area by a processor.

The file storage unit 100 stores various files used in the PC 20. The various files include, for example, an operating system (OS) and programs and data used in a synchronization application. Each file can be identified by a file ID including a file path name and a file name.

The application execution unit 102 executes an application stored in the file storage unit 100 in response to a user operation.

The synchronization setting unit 104 performs settings for synchronizing applications among a plurality of PCs 20. FIG. 7 shows an example of a screen displayed at the time of synchronization setting. This screen is displayed, for example, when an application synchronization system program is started. By using this screen, the user can register the synchronization application or start the synchronization application. For example, when the user moves a shortcut 210 of an application “APL001” on the desktop of the PC 20 to the display area 212 of the screen 200 by drag and drop, the synchronization setting unit 104 selects an application specified by the shortcut. Recognize as a synchronous application. In addition, not only drag and drop but the arbitrary methods for making the synchronous setting part 104 recognize a synchronous application can be used. For example, as shown in FIG. 7, the application to be registered may be recognized by pressing the application addition button 214 to display a file reference interface. Then, the synchronization setting unit 104 stores information regarding the recognized synchronization application in the synchronization setting storage unit 106.

The synchronization setting storage unit 106 stores synchronization settings that are setting information for using the application synchronization system. FIG. 8 is a diagram illustrating an example of the configuration of the synchronization setting storage unit 106. In the example illustrated in FIG. 8, the synchronization setting storage unit 106 stores information related to the synchronization application in addition to account information such as a user ID and a password. As information regarding a synchronous application, application ID, file ID, attribute information, and identification information (hash value) are contained, for example.

Various information stored in the synchronization setting storage unit 106 can be updated by the synchronization setting unit 104. For example, when a file that is a component of the synchronization application is updated, the synchronization setting unit 104 can update the attribute information and identification information of the file stored in the synchronization setting storage unit 106. The generation of identification information can be performed by an identification information generation unit 154 described later.

Returning to FIG. 6, the application activation unit 108 activates the synchronization application in response to a user operation. For example, when the display area 220 assigned to the application “APL001” is selected on the screen 200 shown in FIG. 9, the application activation unit 108 refers to the synchronization setting stored in the synchronization setting storage unit 106, and The synchronization application stored in the storage unit 100 is activated.

The synchronization processing unit 110 can execute various processes for synchronizing application components between the synchronization server 10 and the PC 20. 6, the synchronization processing unit 110 includes an authentication processing unit 150, a component specifying unit 152, an identification information generation unit 154, an identification information transmission unit 156, a component reception unit 158, a component information reception unit 160, and The component transmission unit 162 may be included.

Authentication processing unit 150 executes authentication processing for using the application synchronization system. Specifically, the authentication processing unit 150 transmits an authentication request for using the application synchronization system to the synchronization server 10 by using the account information stored in the synchronization setting storage unit 106. Note that the authentication processing unit 150 may receive account information from the user, for example, by outputting a screen for inputting account information, instead of acquiring account information from the synchronization setting storage unit 106.

The component element specifying unit 152 can specify a component element that is required when the synchronization application is executed. Specifically, the component specifying unit 152 can specify the component (file) of the synchronization application by referring to the synchronization setting storage unit 106. The component specifying unit 152 may specify the component by monitoring the execution of the synchronization application. For example, the component specifying unit 152 may specify a component in the synchronous application by monitoring a file access request or a registry access request from the process of the synchronous application.

The identification information generation unit 154 generates identification information of the component identified by the component identification unit 152. In this embodiment, a hash value is used as the identifier of the component. For example, the identification information generation unit 154 can calculate the hash value of the component by using a predetermined hash function.

The identification information transmission unit 156 transmits the user ID, application ID, file ID, attribute information, and identification information (hash value) to the synchronization server 10 for the component identified by the component identification unit 152.

The component receiving unit 158 receives the component transmitted from the synchronization server 10 according to the identification information and stores it in the file storage unit 100. That is, the component receiving unit 158 can download a component having a newer update date and time from the synchronization server 10 and a component that exists only in the synchronization server 10 from the synchronization server 10.

The component information receiving unit 160 receives the component information transmitted from the synchronization server 10 according to the identification information. This component element information indicates a component to be uploaded from the PC 20 to the synchronization server 10.

The component transmission unit 162 transmits the component indicated by the component information to the synchronization server 10. In other words, the component transmission unit 162 is different from the component stored in the synchronization server 10 among the components of the synchronization application, and has a newer update date than the component stored in the synchronization server 10. Elements can be uploaded to the synchronization server 10. Thereby, for example, a component already stored in the synchronization server 10 and having the same content as a component uploaded by another user is not uploaded.

FIG. 10 is a flowchart showing an example of application synchronization processing. This synchronization process can be executed, for example, at the timing when the application synchronization system program is started on the PC 20 or when the synchronization application is terminated.

First, an authentication process is executed between the authentication processing unit 150 of the PC 20 and the authentication processing unit 50 of the synchronization server 10 (S1001, S1002). When the authentication process is completed, the component specifying unit 152 of the PC 20 specifies the component of the synchronization application by referring to the synchronization setting storage unit 106 (S1003). Then, the identification information generation unit 154 of the PC 20 generates identification information (hash value) of the identified component (S1004). Note that the timing at which the identification information is generated is not limited to this. For example, the identification information may be generated at an arbitrary timing before the synchronization process is executed with the synchronization server 10. For example, the identification information generation unit 154 may generate the identification information of the component and store it in the synchronization setting storage unit 106 at the timing when the content of the component is updated in the synchronization application.

Subsequently, the identification information transmission unit 156 transmits the identification information (hash value) generated by the identification information generation unit 154 to the synchronization server 10 together with the user ID, application ID, file ID, and attribute information (S1005). The identification information receiving unit 52 of the synchronization server 10 receives information transmitted from the PC 20 (S1006).

The component specifying unit 54 of the synchronization server 10 determines the difference between the component in the PC 20 and the component already stored in the component storage unit 32 of the synchronization server 10 based on the identification information received from the PC 20. (S1007). Specifically, the component specifying unit 54 compares the identification information received from the PC 20 with the identification information stored in the component storage unit 32 for each application ID and file ID, thereby Differences can be determined. Here, the components determined to be identical do not need to be uploaded between the synchronization server 10 and the PC 20.

Then, the component specifying unit 54 determines whether to perform upload or download by comparing the update date and time for the components determined to have different contents between the synchronization server 10 and the PC 20. (S1008). Specifically, the component specifying unit 54 specifies a component having a newer update date and time on the PC 20 and a component that exists only on the PC 20 as upload targets. Further, the component specifying unit 54 specifies, as download targets, components that have a newer update date and time in the synchronization server 10 and components that exist only in the synchronization server 10.

The component transmitting unit 56 of the synchronization server 10 transmits the component specified as the download target by the component specifying unit 54 to the PC 20 (S1009). The component reception unit 158 of the PC 20 receives the component transmitted from the synchronization server 10 and stores it in the file storage unit 100 (S1010).

Subsequently, the component information transmitting unit 58 of the synchronization server 10 transmits component information indicating the component specified as the upload target by the component specifying unit 54 to the PC 20 (S1011). The component information receiving unit 160 of the PC 20 receives the component information transmitted from the synchronization server 10 (S1012). Then, the component transmission unit 162 of the PC 20 transmits the component indicated by the component information to the synchronization server 10 (S1013).

The component receiving unit 60 of the synchronization server 10 receives the component transmitted from the PC 20 (S1014). Then, the component management unit 62 of the synchronization server 10 updates the component storage unit 32 using the received component (S1015). Specifically, the component management unit 62 stores the received component in the individual component storage unit 42 in association with the user ID, application ID, attribute information, and identification information (hash value). In addition, the component management unit 62 includes components determined to be the same among a plurality of users by the component specifying unit 54 among the components stored in the individual component storage unit 42. Move to the common component storage unit 40.

Through the above processing, application components can be synchronized between the PC 20 and the synchronization server 10. In the present embodiment, among the components in the PC 20, components having the same contents are already stored in the component storage unit 32 of the synchronization server 10 and uploaded from the PC 20 to the synchronization server 10. Absent. Therefore, the data capacity stored in the component storage unit 32 can be reduced, and the communication amount between the PC 20 and the synchronization server 10 can be reduced.

In addition, this embodiment is for making an understanding of this invention easy, and is not for limiting and interpreting this invention. The present invention can be changed / improved without departing from the spirit thereof, and the present invention includes equivalents thereof.

For example, in this embodiment, a client that executes an application in the application synchronization system is a PC. However, the client is not limited to a PC, and any information processing apparatus such as a mobile terminal can be used.

In addition, for example, in the present embodiment, the synchronization process is executed between the PC 20 and the synchronization server 10 at the timing when the program for the application synchronization system is started or when the synchronization application is terminated. The timing of the synchronization processing is not limited to this, and any timing can be adopted.

DESCRIPTION OF SYMBOLS 10 Synchronization server 20 Personal computer 30 Account information memory | storage part 32 Component element memory | storage part 34 Synchronization processing part 40 Common component element memory | storage part 42 Individual component element memory | storage part 50 Authentication process part 52 Identification information receiving part 54 Component element specific | specification part 56 Component element transmission Unit 58 component element information transmission unit 60 component element reception unit 62 component element management unit 100 file storage unit 102 application execution unit 104 synchronization setting unit 106 synchronization setting storage unit 108 application activation unit 110 synchronization processing unit 150 authentication processing unit 152 component identification Unit 154 identification information generation unit 156 identification information transmission unit 158 component element reception unit 160 component element information reception unit 162 component element transmission unit

Claims

A component storage unit that stores a plurality of components required when executing the application;
An identification information receiving unit for receiving, from a computer, component element identification information for identifying the contents of each of the plurality of component elements of the application in the computer;
Based on the component identification information, among the plurality of components in the computer, a component identifying unit that identifies a component that differs in content from the component stored in the component storage unit;
A component information transmitting unit that transmits component information indicating the identified component to the computer;
A component receiving unit that receives a component corresponding to the component information from the computer;
A component management unit that stores the component received from the computer in the component storage unit;
A synchronization server comprising:
The synchronization server according to claim 1,
The component storage unit stores the component identification information in the component storage unit in association with the component,
The component identifying unit identifies a component having a different content by comparing the component identification information stored in the component storage unit with the component identification information received from the computer.
Sync server.
The synchronization server according to claim 1 or 2,
The component storage unit stores the component in association with a user identifier,
The component specifying unit specifies components having different contents regardless of the user identifier,
The component management unit associates the component received from the computer with the user identifier of the user of the computer for the component having a different content among the components in the computer. Store in the
Sync server.
The synchronization server according to any one of claims 1 to 3,
The component identification information includes a hash value of the component,
Sync server.
Sync server is
A plurality of components necessary for executing the application are stored in the component storage unit,
Receiving, from the computer, component identification information for identifying the contents of each of the components of the application in the computer;
Based on the component identification information, among the plurality of components in the computer, a component having a content different from the component stored in the component storage unit is specified,
Transmitting component information indicating the identified component to the computer;
Receiving a component according to the component information from the computer;
Storing the component received from the computer in the component storage unit;
Synchronization method.
Computer
An identification information generation unit for generating component element identification information for identifying the contents of each of the plurality of component elements required when executing the application;
An identification information transmitting unit that transmits the generated component identification information to a synchronization server for synchronizing the components of the application among a plurality of computers;
A component information receiving unit that receives component information indicating a component that is not stored in the synchronization server with the same content among the plurality of components,
A component transmission unit that transmits the component indicated by the component information to the synchronization server;
Program to function as.