JP5378119B2 - Wrapping file update system and wrapping file update method - Google Patents

Description

  The present invention relates to a wrapping file update system and a wrapping file update method.

Conventionally, there is a technology related to a system that executes license management using encryption information or the like. In such a system, the license management server that has received the encryption unique information from the client terminal registers the encryption unique information and determines whether or not a legitimate user having a license is operating the client terminal. .
Here, when it is determined that the user is a legitimate user, the license management server transmits key information to the client terminal. The client terminal sets various environment information in the registry based on the key information, and can execute an executable application program to which a license is granted, that is, a license for use.

  For example, Patent Document 1 discloses a technique related to a license management system. In the case of the technology described in Patent Literature 1, even if there is no change in the execution application provided by the developer of the execution application to be distributed, the authentication module, the deployment module, and the monitoring provided by the platform application provider When other elements constituting the wrapping file such as a module are changed or updated, the wrapping operation occurs again, which is troublesome for the executing application developer.

  In addition, users of distribution destinations (application service users) need to update even if there is a change or update of a part that is not directly related to the application function. . Furthermore, in an execution application such as a Microsoft Excel (registered trademark) macro application that stores data in a cell, input data is not reflected in the wrapping file, and the application range is narrowed.

  On the other hand, Patent Document 2 describes a technique related to a self-extracting program including an update program for automatically updating an executable file itself. According to this document, an update program for updating the self-extracting program is included in the self-extracting program itself, which may improve convenience.

  However, even with the technique described in Patent Document 2, if there is a change in the update program itself, it is necessary to create a wrapping file again, and the user also needs to update.

JP 2008-117191 A JP 2008-204344 A

The present invention has been made in view of the above circumstances. By separating version management of a target file to be distributed and other elements, partial maintenance is efficient for both the developer and user of the target file. An object of the present invention is to provide a wrapping file update system and a wrapping file update method that can be implemented in an automated manner.
In addition, the present invention separates the data portion from the wrapping file and stores it on the server, thereby preventing subsets of the wrapping file and realizing data generation management and sharing with others to improve convenience. Another object is to provide a wrapping file update system and a wrapping file update method.

According to the present invention, a server that distributes, via a communication line, a wrapping file that includes at least a target file to be distributed, a deployment module having at least a function of releasing wrapping, and an authentication module, and a wrapping file Is received via the communication line, the deployment module and the authentication module included in the wrapping file are executed, and the client terminal that uses the target file is requested to deliver one of the modules. A wrapping file update system is provided that includes a license management server that distributes a module and a wrapping program for which a request is made via a communication line.
In the wrapping file update system, a client terminal executes a deployment module to cancel wrapping, a client terminal executes an authentication module and sends authentication information to a license management server, and the license management server If it is determined that the information is authentic, the update of any of the modules is confirmed, and if there is an update of the module, the updated module is distributed to the client terminal, and the client terminal And the module in the client terminal is updated.

  In the wrapping file update system having the above-described configuration, partial maintenance can be efficiently performed by both the developer and the user of the target file by separating version management of the target file to be distributed and the other portions.

According to the present invention, a wrapping file including at least a target file to be distributed, a decompression module having at least a function of canceling wrapping, an authentication module, and a data part is distributed via a communication line. A server that receives the wrapping file via a communication line, executes a deployment module and an authentication module included in the wrapping file, and uses a client terminal of a user who uses the target file, and one of the modules When distribution is requested, a wrapping file update system is provided that includes a module and a license management server that distributes a module and a wrapping program requested for distribution via a communication line.
In the wrapping file update system, a client terminal executes a deployment module to cancel wrapping, a client terminal executes an authentication module and sends authentication information to a license management server, and the license management server If it is determined that the information is authentic, the update of any of the modules is confirmed, and if there is an update of the module, the updated module is distributed to the client terminal, and the client terminal The license management server generates the version information of the data in the data section and distributes it to the client terminal, and the client terminal must have the version selected by the user. Version selected by the license management server Requesting delivery of data, the license management server is characterized by distributing the data of the requested version.

  In the wrapping file update system having the above-described configuration, partial maintenance can be efficiently performed by both the developer and the user of the target file by separating version management of the target file to be distributed and the other portions.

  According to another aspect of the present invention, in the wrapping file update system, the license management server includes a storage unit that stores the data. As a result, it is possible to prevent the wrapping file from being sub-set, and to realize data generation management and sharing with others to improve convenience.

  In addition, according to the present invention, at least a process for requesting distribution of a wrapping file including a target file to be distributed, a target file, a deployment module having at least a function of releasing wrapping, and an authentication module are included. The process of receiving the wrapping file via the communication line, the process of executing the decompression module included in the wrapping file to cancel the wrapping, and the authentication module included in the wrapping file are executed to execute the authentication information to the server. If the module is updated after the authentication process has been confirmed that the authentication information is authentic, the process of receiving the updated module from the server, and receiving the updated module to update the module. And a method for updating a wrapping file, comprising: .

  Further, according to the present invention, a process for requesting distribution of a wrapping file including a target file to be distributed, a target file, a development module having at least a function of canceling wrapping, an authentication module, and a data unit A process for receiving a wrapping file including at least a communication line, a process for canceling wrapping by executing a decompression module included in the wrapping file, and an authentication module executing the authentication module included in the wrapping file The process of sending information to the server, the process of receiving the updated module from the server and the updated module if there is a module update after the authentication information is certified as authentic. The process of updating the module and the data version of the data part generated by the server A process of receiving information, a process of selecting a version from the version information of data received from the server, and a process of requesting the server to deliver the selected version of the data if the client terminal does not have the selected version And a method for updating a wrapping file, comprising: receiving a requested version of data.

  According to the present invention, in response to a request from a client terminal, a wrapping file including at least a target file, a deployment module having at least a function of canceling wrapping, and an authentication module is transmitted via a communication line. The process of distributing, the process of receiving authentication information from the client terminal, the process of determining whether the authentication information is legitimate, the authentication information is legitimate, and updated if there is a module update A method for updating a wrapping file is provided, comprising the step of delivering a module to a client terminal.

  Further, according to the present invention, in response to a request from a client terminal, a target file, a wrapping file including at least a deployment module having a function of releasing wrapping, an authentication module, and a data part are communicated. If the process of distributing via the line, the process of receiving authentication information from the client terminal, the process of determining whether the authentication information is legitimate, the authentication information is legitimate, and there is a module update A process of distributing the updated module to the client terminal, a process of generating version information of data in the data section, and a process of distributing data of a version selected based on the version information of the data A wrapping file update method is provided.

  In the wrapping file update method configured as described above, partial maintenance can be efficiently performed for both the developer and the user of the target file by separating version management of the target file to be distributed and the other portions.

  According to the aspect of the invention, in the wrapping file update system or the wrapping file update method, the wrapping file further includes a monitoring module that monitors use of the target file. Thereby, unauthorized use of the target file can be suppressed.

Here, terms used in the present specification are defined as follows.
The target file refers to a distribution target file for which a distribution request is made from the client terminal to the license management server. In the present invention, the target file is given as a file including an execution application, an execution format file with the extension “.EXE”, a data file used in an application program such as Microsoft Office (registered trademark), a moving image file, or the like. This means digital content etc.

The wrapping file includes at least the target file, a development (decompression) module having at least a function of releasing wrapping, an authentication module having at least a function of transmitting authentication information to the license management server, A file that is created by combining a monitoring module having at least a function for monitoring usage and is distributed from a server to a client terminal as an apparent single file.
Note that the wrapping file may include a data portion related to the target file.

  Unpacking means that if the target file is wrapped as it is without data conversion, the wrapping is canceled and the wrapping file is disassembled, and the target file, authentication module, monitoring module, etc. are each made into individual files. To make it in a state where it can be handled.

  In addition, when data conversion processing based on a predetermined algorithm such as encryption processing, compression processing, or a combination of encryption processing and compression processing is applied to the target file, decompression is wrapping If the data conversion applied to the target file is an encryption process, the target file is decrypted. If the data conversion applied to the target file is a compression process, the target file is This means that the target file is restored to a usable state by applying reverse data conversion processing based on a predetermined algorithm to the target file, such as performing decompression processing.

Use of the target file means to execute the target file if the target file is an executable format file, and to execute an existing application program or other executable format if the target file is a file other than the executable format file. This refers to execution by applying the target file to a file, and is composed of a first target file that is an executable file and a second target file that is one or more files other than the executable file. In this case, the second target file is applied to the first target file and executed.
The communication line is a network such as the Internet that can transmit and receive data.

  ADVANTAGE OF THE INVENTION According to this invention, the wrapping file update system and wrapping file update method which can implement a partial maintenance efficiently for the developer and user of an object file are provided.

It is the schematic which shows an example of a structure of the wrapping file update system which concerns on this invention. It is a flowchart at the time of application execution of the wrapping file update system which concerns on Embodiment 1 of this invention. It is a flowchart at the time of application execution of the wrapping file update system which concerns on Embodiment 2 of this invention. It is a flowchart at the time of the application end of the wrapping file update system which concerns on embodiment of this invention.

100 Wrapping file update system 101 Execution application file 102 Deployment module 103a Authentication module V1
103b Authentication module V2
104 Wrapping file 105 Server 106 Client terminal 107 Wrapping program 108 License management server 109 Monitoring module 110 Data part 111 Storage part (user area)
112 Wrapping configuration file 113 Version management file 114 Authentication / permission file 115 Wrapping tool

  Hereinafter, a wrapping file update system and a wrapping file update method according to the present invention will be described based on embodiments. These embodiments are described in order to help understanding of the present invention. Obviously, it is not intended to be limited to what is described below.

[Embodiment 1]
FIG. 1 is a diagram showing a configuration of a wrapping file update system according to the present invention.
In the following description, the target file is described as an execution application file. As an example, a case where the authentication module is updated from V1 (103a) to V2 (103b) will be described, but the present invention is not limited to this.

  As shown in FIG. 1, a wrapping file update system 100 according to the present embodiment includes a target file (execution application) 101 to be distributed, a decompression module 102 having at least a function of canceling wrapping, and an authentication module 103a. A server 105 that distributes a wrapping file 104 including at least a communication line (not shown), a wrapping file 104 received via the communication line, and an expansion module 102 and authentication included in the wrapping file 104 Module 103a is executed, and when the distribution of any one of the modules is requested to the client terminal 106 using the target file 101, the module requested for distribution and the wrapping program 107 are distributed via the communication line. License Constructed and a management server 108.

  In the wrapping file update system 100, the client terminal 106 executes the deployment module 102 to cancel the wrapping, and the client terminal 106 executes the authentication module 103a to transmit the authentication information to the license management server 108. If it is determined that the authentication information is authentic, the license management server 108 confirms the update of any of the modules. If there is an update of the module, the license management server 108 updates the updated module (the authentication module in FIG. 1). V2 (103b)) is distributed to the client terminal 106, and the client terminal 106 receives the updated module and updates the module in the client terminal 106.

  In the wrapping file update system 100, the wrapping file 104 may further include a monitoring module 109 that monitors the use of the target file 101. In the wrapping file update system 100, the license management server 108 may include a storage unit 111 that stores data of the data unit 110 included in the wrapping file 104.

  The license management server 108 includes, for example, a keyboard, a mouse, a display, a network interface unit that controls communication with a communication line, a keyboard, a mouse, and other input means connected to the license management server 108 and a display means such as a display. I / O interface unit for controlling data transmission to and from the control unit, a control unit for controlling components in the license management server 108 given as a CPU, and a data transmitting / receiving unit for transmitting and receiving data such as files via a communication line Etc.

The license management server 108 may include, for example, a storage unit that stores the wrapping configuration file 112, the version management file 113, the authentication / permission file 114, and the like of FIG.
As the wrapping configuration file 112, for example, at least data such as a target file, a module, an execution environment path, and a registry key name are stored in the provided application type.

As the version management file 113, version information of data including information such as update date and updater, a difference file, and the like are stored. Here, the difference file is a file in which differences between files are recorded. For example, it is used for software version upgrade and to express the difference between source code of old and new programs.
As the authentication / permission file 114, an ID, a password, an ID for each function for limiting the function for the client terminal, and the like are stored.

  The client terminal 106 includes, for example, a calculation unit that performs calculation such as a CPU, a storage unit that stores information such as a magnetic disk and a semiconductor memory, an input unit such as a keyboard and a mouse, a display unit such as a display, and a network module. It is a computer provided with the communication means etc. for performing transmission / reception of data with an external device.

  In FIG. 1, the license management server 108 and the server 105 that distributes the wrapping file 104 are provided separately, but they may be the same.

Next, a flow at the time of executing and ending an application in the wrapping file update system according to the present embodiment will be described.
2 to 4 are flowcharts for explaining the flow of processing in the client terminal and the server. The process of the license management server (server) is described on the left side of the client terminal (computer).

FIG. 2 is an example of a flow when executing an application (application).
When requesting distribution of a wrapping file including a target file to be distributed at a client terminal, a wrapping file including at least the target file, a deployment module having at least a function of canceling wrapping, and an authentication module is connected to a communication line. Via the server.

In order to execute the application, the user executes the decompression module included in the wrapping file to cancel the wrapping, and executes the authentication module included in the wrapping file to transmit the authentication information to the server.
In order for the user of the client terminal to which the wrapping file is distributed to use the target file, it is necessary to receive a license from the license management server. In order to be granted a license, an ID and a password (PW ) Is input and transmitted to the server (step S202).

  In the server, when the authentication information (ID and password) is transmitted, the transmitted authentication information is compared with the registered authentication information, and the user is qualified to be licensed for the target file. It is determined whether it has (step S204). The license means a use right with use conditions of a target file given as an application program, a data file, digital content, or the like.

  After the authentication information is authentic and the user is authenticated, the version of the application is confirmed (step S206). The application version is confirmed (step S208), and if the application version is not the latest version, the application version is updated (step S210).

When the user is authenticated, that is, when it is confirmed that the user is qualified to receive the license, a message indicating that the license has been granted may be notified to the client terminal. On the other hand, if the user is not authenticated, a message indicating that the license is not granted may be notified to the client terminal.
For example, if the user is not authenticated, after completing the notification of a message indicating that the license is not granted, the processing related to the target file for the client terminal that has requested the distribution of the target file is terminated.

  If the application version is the latest version, the tool version is checked (step S212).

  Next, the version of the tool is confirmed (step S214). If the tool is updated, the updated tool is received from the server. Here, the tool means a deployment module, an authentication module, a monitoring module, a module having other functions, or the like.

  Here, it is preferable to receive a wrapping program for performing wrapping again together with the updated tool. The wrapping program may be temporarily stored and deleted after updating the tool.

  The client terminal receives the updated tool and updates the version of the tool (step S216). Here, when updating the tool version to the latest version, it is possible to overwrite the conventional tool.

  If the version of the tool is the latest version, the application is activated (step S218).

  Note that the method of obtaining the wrapping file for the first time by the user may be a method via a communication line such as the Internet, or may be obtained by purchasing a storage medium storing data.

FIG. 3 is an example of a flow at the end of the application.
At the end of the application, it is determined whether or not there is data update (step S302). If there is data update, an update destination is selected (step S304). If there is no data update, the process ends. Note that the update destination may be implicitly set by the application setting information, and the set update destination may be automatically selected when the application ends.

  In the example of FIG. 1, the data update destination is a user area in the storage unit 111 of the license management server. Here, when the data storage area is provided in a device different from the client terminal, the data storage area may be divided into an area that can be accessed only by the user, an area that can be used by others, and the like. Further, the data update destination may be a file storage unit in the client terminal.

  After the update destination is determined, the data is transferred (step S306), and the data is stored in the selected data storage area in the server (step S308).

  After the data is stored, the license is returned (step S310). The server performs a license return process (step S312). The license is returned only when necessary.

[Embodiment 2]

FIG. 4 is an example of a flow at the time of application execution in the wrapping file update system according to the second embodiment.
In the wrapping file update system according to the second embodiment, after updating the module in the client terminal, the license management server generates version information of data in the data part and distributes it to the client terminal. If the version selected by the user does not exist, the license management server is requested to distribute the selected version of the data, and the license management server distributes the requested version of the data.
That is, in the second embodiment, data version management is different from the wrapping file update system and the like of the first embodiment. In FIG. 4, the same reference numerals as those in FIG.

  After the license management server confirms that the version of the tool is the latest version, data version list information is generated (step S402).

The data version information is distributed to the client terminal, and the user selects the data version (step S404). The selection of the data version is not particularly limited. For example, the data version is selected by a user interface in which data is arranged in a list format. Here, it is preferable that the user interface is such that the user can easily select the last updated data.
You can also choose another file that is not related to the version.

Next, it is determined whether the version of the data in the client terminal is the selected version (step S406). If it is the selected data version, the application is activated (step S408).
If the client terminal does not have the version selected by the user, the license management server requests distribution of the selected version data, and the license management server extracts the selected version data (step S410). Deliver to client terminals.

  As described above, in the wrapping file update system and the wrapping file update method according to the present invention, by dividing the version management of the target file to be delivered and the other parts, both the developer and the user of the target file Since efficient maintenance can be carried out efficiently, it is possible to improve efficiency in operations such as application distribution services.

Claims (9)

A server for distributing a wrapping file including at least a target file to be distributed, a deployment module having at least a function of canceling wrapping, and an authentication module;
A client terminal that receives a wrapping file via a communication line, executes a deployment module and an authentication module included in the wrapping file, and uses the target file;
When distribution of any of the modules is requested, the module and the wrapping program requested to be distributed are configured to have a license management server that distributes them via a communication line,
The client terminal executes the deployment module to release the wrapping,
The client terminal executes the authentication module and sends the authentication information to the license management server.
The license management server confirms the update of any one of the modules if the authentication information is authorized, and distributes the updated module to the client terminal if there is a module update.
A wrapping file update system, wherein a client terminal receives an updated module and updates a module in the client terminal. A server for distributing a wrapping file including at least a target file to be distributed, a decompression module having at least a function of canceling wrapping, an authentication module, and a data part via a communication line;
A client terminal of a user who receives a wrapping file via a communication line, executes a deployment module and an authentication module included in the wrapping file, and uses the target file;
When distribution of any of the modules is requested, the module and the wrapping program requested to be distributed are configured to have a license management server that distributes them via a communication line,
The client terminal executes the deployment module to release the wrapping,
The client terminal executes the authentication module and sends the authentication information to the license management server.
The license management server confirms the update of any one of the modules if the authentication information is authorized, and distributes the updated module to the client terminal if there is a module update.
The client terminal receives the updated module, updates the module in the client terminal,
The license management server generates the data version information of the data part and distributes it to the client terminal,
If the client terminal does not have the version selected by the user, the client terminal requests the license management server to distribute the selected version of data,
The wrapping file update system, wherein the license management server distributes the requested version of data.   The wrapping file update system according to claim 2, wherein the license management server includes a storage unit that stores the data.   The wrapping file update system according to any one of claims 1 to 3, wherein the wrapping file further includes a monitoring module for monitoring the use of the target file. A process of requesting delivery of a wrapping file containing a target file to be delivered;
A process of receiving, via a communication line, a wrapping file including at least a target file, a deployment module having at least a function of releasing wrapping, and an authentication module;
The process of releasing the wrapping by executing the decompression module included in the wrapping file,
The process of executing the authentication module included in the wrapping file and transmitting the authentication information to the server,
If the module is updated after the authentication information is certified as authentic, the process of receiving the updated module from the server;
A method for updating a wrapping file, comprising: receiving an updated module and updating the module. A process of requesting delivery of a wrapping file containing a target file to be delivered;
A process of receiving a wrapping file including at least a target file, a deployment module having at least a function of releasing wrapping, an authentication module, and a data part via a communication line;
The process of releasing the wrapping by executing the decompression module included in the wrapping file,
The process of executing the authentication module included in the wrapping file and transmitting the authentication information to the server,
If the module is updated after the authentication information is certified as authentic, the process of receiving the updated module from the server;
Receiving the updated module and updating the module;
The process of receiving the version information of the data of the data part generated by the server,
The process of selecting the version from the version information of the data received from the server,
If the client terminal does not have the selected version, requesting the server to deliver the selected version of the data;
Receiving a requested version of the data, and a method for updating the wrapping file.   The wrapping file update method according to claim 5 or 6, wherein the wrapping file further includes a monitoring module for monitoring use of the target file. In response to a request from a client terminal, a process of delivering a wrapping file including at least a target file, a deployment module having at least a function of canceling wrapping, and an authentication module;
Receiving authentication information from the client terminal;
A process of determining whether the authentication information is authentic,
A method for updating a wrapping file, characterized in that the authentication information is authentic and if the module is updated, the updated module is distributed to the client terminal. In response to a request from a client terminal, a process of delivering a wrapping file including at least a target file, a decompression module having at least a function of canceling wrapping, an authentication module, and a data part via a communication line; ,
Receiving authentication information from the client terminal;
A process of determining whether the authentication information is authentic,
If the authentication information is authentic and the module is updated, the process of distributing the updated module to the client terminal;
A process of generating version information of data in the data part;
And a method of delivering a version of data selected based on the version information of the data.