JP2020060920A - Server device, terminal device, license authentication method, and license authentication program - Google Patents

Abstract

To provide a server device, a terminal device, a license authentication method, and a license authentication program capable of performing user-friendly license authentication.SOLUTION: A server device 20 comprises: an acquisition unit 21 for acquiring software identification information of predetermined software included in a package file if the package file is decompressed, wherein the package file includes the predetermined software and an authentication result that contains the software identification information for identifying the predetermined software, wherein the package file and the authentication result further include package identification information for identifying the package file; and an authentication unit 22 for performing license authentication for the predetermined software using the acquired software identification information, the software identification information included in the authentication result, the package identification information included in the package file, and the package identification information included in the authentication result.SELECTED DRAWING: Figure 1

Description

  The present disclosure relates to a server device, a terminal device, a license authentication method, and a license authentication program.

  In recent years, the number of application execution servers is automatically changed according to the load status of the CPU (Central Processing Unit) and memory by using automatic environment building software that automatically builds the environment, such as configuration management tools and virtual infrastructure software. The operation is done.

  Generally, the license registration of the application execution base software is performed by the user manually inputting the license key when the software is installed in the server device or after the software is installed. Therefore, a third party may steal the input license key, obtain the license key, and use the obtained license key.

  Further, in the case of using the automatic environment construction software, and in the case of a commercial product for checking the license of the application execution base software, the user sets the license key in advance according to the function provided by the automatic environment construction software. Therefore, even when the automatic environment construction software is used, the license key can be referred to by the automatic environment construction software, and a third party obtains the license key and diverts the obtained license key. It is possible. Thus, it is desired to prevent the license key from leaking.

Therefore, related technologies for checking the license of the software without using the license key input by the user have been studied (for example, Patent Documents 1 to 3).
Patent Document 1 discloses a technique of determining whether or not to activate a software product based on a license having permission / prohibition information as to whether or not the use is permitted for each function of the software product.

Patent Document 2 discloses that the keying information of each package is collated with all the key information files at startup and compared with the key based on the hash of the manifest file and the universally unique identifier (UUID). . Further, Patent Document 2 discloses that the device is activated when the comparison is valid for any package.
Patent Document 3 discloses that a setting authentication package is used to verify the integrity of setting data.

JP, 2007-316938, A JP, 2005-182789, A JP, 2008-098786, A

  Here, in the technique disclosed in Patent Document 1, in order to generate a license, the user (user) needs to contact the administrator with information on the software products that are permitted to be used, and Interaction with the user is required. Further, the technique disclosed in Patent Document 2 enables the installation if the hash of the contents of the package to be installed and the UUID of the device is calculated and the result determined on the server side matches. That is, in the technique disclosed in Patent Document 2, the UUID of the device in which the package is installed needs to be notified by the user, and communication between the administrator and the user is required. As described above, the above-mentioned Patent Documents 1 and 2 do not provide high user-convenience technology because the communication between the administrator and the user is required.

  An object of the present disclosure is to solve the above-described problem, and to provide a server device, a terminal device, a license authentication method, and a license authentication program that can perform license authentication with high user convenience.

The server device according to the present disclosure is
A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. When the package file further included is expanded, an acquisition unit that acquires software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. A server device that includes an authenticating unit that performs the authentication.

The terminal device according to the present disclosure,
An authentication unit that performs license authentication on predetermined software and, when the license authentication is completed normally, outputs an authentication result including software identification information for identifying the predetermined software,
A generating unit that generates a package file including the predetermined software and the authentication result,
The generation unit is a terminal device that generates package identification information for identifying the package file, and includes the generated package identification information in the authentication result and the package file to generate the package file. .

The license authentication method according to the present disclosure is
A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. Further, when the included package file is expanded, acquiring software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. What to do and the license authentication method that includes it.

The license authentication program according to the present disclosure is
A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. Further, when the included package file is expanded, acquiring software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. This is a license authentication program that is executed by a computer.

  According to the present disclosure, it is possible to provide a server device, a terminal device, a license authentication method, and a license authentication program capable of license authentication with high user convenience.

FIG. 1 is a diagram showing a configuration example of an information processing system according to a first exemplary embodiment. FIG. 4 is a diagram showing a configuration example of an information processing system according to a second exemplary embodiment. FIG. 6 is a diagram showing a configuration example of a development PC according to the second embodiment. FIG. 9 is a diagram showing a configuration example of an application execution server according to the second exemplary embodiment. FIG. 9 is a diagram showing an operation example of the development PC according to the second embodiment. FIG. 8 is a diagram showing an operation example of an application execution server according to the second exemplary embodiment. It is a figure which shows the structural example of the information processing system concerning Embodiment 3. FIG. 11 is a diagram showing an operation example of the information processing system according to the third exemplary embodiment. FIG. 3 is a block diagram illustrating a hardware configuration of a terminal device or the like according to each embodiment of the present disclosure.

  Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Note that the following description and drawings are appropriately omitted and simplified for clarity of explanation. Further, in each of the following drawings, the same reference numerals are given to the same elements, and the duplicate description is omitted as necessary.

(Embodiment 1)
An information processing system 1 according to the first embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating a configuration example of an information processing system according to the outline of the embodiment. The information processing system 1 includes a terminal device 10 and a server device 20.

  The terminal device 10 is a device that performs license authentication on predetermined software and generates a package file including the software. Therefore, the terminal device 10 can be said to be a package file generation device. The terminal device 10 may be, for example, a computer device or a server device. The terminal device 10 includes an authentication unit 11 and a generation unit 12.

  The authentication unit 11 performs license authentication on the predetermined software and generates an authentication result including software identification information for identifying the predetermined software. The authentication unit 11 may use the license key of predetermined software stored in advance to perform license authentication on the software. Alternatively, the authentication unit 11 may perform license authentication on the software using a license key of predetermined software input from an input unit (not shown).

The predetermined software may be application execution base software, for example.
The software identification information is information that identifies predetermined software. The software identification information may be, for example, a product name of predetermined software, a product code, or a product ID (Identifier). Alternatively, the software identification information may be information using two or more of the above.

The generation unit 12 generates a package file including predetermined software and the authentication result generated by the authentication unit 11. Further, the generation unit 12 generates the package identification information for identifying the generated package file, and includes the generated package identification information in the authentication result and the package file to generate the package file. The generation unit 12 may store the generated package identification information in predetermined software included in the package file.
The package identification information is information for identifying the package file, and may be, for example, a package ID.

  The server device 20 executes predetermined software included in the package file generated by the terminal device 10, and performs license authentication of the predetermined software. Therefore, the server device 20 may also be referred to as an authentication device. The server device 20 includes an acquisition unit 21 and an authentication unit 22.

  When the package file generated by the terminal device 10 is expanded, the acquisition unit 21 acquires the software identification information of the predetermined software included in the package file.

  The authentication unit 22 uses the acquired software identification information, the software identification information included in the authentication result, the package identification information included in the package file, and the package identification information included in the authentication result to perform license authentication of predetermined software. To do.

  As described above, the terminal device 10 generates the package file including the authentication result file including the identification information of the predetermined software and the package identification information, and the package identification information. The server device 20 acquires the software identification information of the predetermined software included in the expanded package file. The server device 20 uses the acquired software identification information, the software identification information included in the authentication result, the package identification information included in the package file, and the package identification information included in the authentication result to perform license authentication of predetermined software. To do. That is, the server device 20 can perform license authentication of the predetermined software included in the package file without requiring additional input information from the user, for example. Therefore, according to the information processing system 1 according to the first embodiment, it is possible to perform license authentication with high user convenience.

(Embodiment 2)
Next, the second embodiment will be described. The second embodiment is a detailed embodiment of the first embodiment.

<Example of configuration of information processing system>
An information processing system 100 according to the second embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating a configuration example of the information processing system according to the second embodiment. The information processing system 100 includes a development PC 30 and an application execution server (AP execution server) 50.

  The development PC 30 and the application execution server 50 are connected via a computer network 40, and communicate with each other via the computer network 40. Although the information processing system 100 is described as a configuration including only one development PC 30 and one application execution server 50, a plurality of development PCs 30 and a plurality of application execution servers 50 are provided. It may be provided.

  The development PC 30 corresponds to the terminal device 10 according to the first embodiment. The development PC 30 is a computer device or a server device in which each functional unit described later operates by causing the CPU to execute the packaging software.

  The development PC 30 includes a storage 32. The storage 32 is a general term for a memory and a file system that can be used in a computer, and is also called a storage section. The storage 32 includes a storage area 33 that stores application execution base software, a storage area 34 that stores a user application, and a storage area 35 that stores a package file.

  The development PC 30 authenticates the application execution base software. Further, the development PC 30 creates (generates) a package file that is expanded and executed by the application execution server 50. The package file is a package file including application execution base software and a user application. The created package file is copied to the application execution server 50 and expanded.

  The application execution server 50 corresponds to the server device 20 according to the first embodiment. The application execution server 50 expands the package file generated by the development PC 30. When the license registration of the application execution base software is not performed, the application execution server 50 performs the license authentication of the application execution base software and performs the license registration. The application execution base software is software for executing a predetermined application such as a user application. The application execution base software corresponds to the predetermined software according to the first embodiment.

  The application execution server 50 includes a storage 51. The storage 51 is a general term for a memory and a file system that can be used in a computer, and is also called a storage section. The storage 51 stores and expands the package file generated by the development PC 30. The storage 51 includes a storage area 53 that stores a package file.

<Example of development PC configuration>
Next, a configuration example of the development PC 30 according to the second embodiment will be described with reference to FIG. FIG. 3 is a diagram illustrating a configuration example of the development PC according to the second embodiment. As shown in FIG. 3, the development PC 30 includes a storage 32, an input unit 36, an authentication unit 37, and a generation unit 38.

  The storage 32 is a memory (storage unit) that stores software and files required to generate a package file. The storage 32 includes a storage area 33 in which application execution base software is stored, a storage area 34 in which a user application is stored, and a storage area 35 in which a package file is stored.

  The package file includes a user application, application execution base software that internally stores a package ID file, and a license authentication result file. Therefore, the storage 32 includes a storage area 35 for storing the package file, a storage area 351 for storing the application execution base software, and a storage area 354 for storing the license authentication result file. Further, the storage 32 includes a storage area 351 for storing application execution base software, a storage area 352 for storing a user application, and a storage area 353 for storing a package ID file.

  The input unit 36 inputs a parameter required to generate a package file including an application execution base software and a user application from an operator (user) who operates the development PC 30.

  Specifically, the input unit 36 inputs the storage destination directory name of the application execution base software and the storage destination directory name of the user application. The input unit 36 also inputs the license key of the application execution base software.

  The input unit 36 specifies the input license key, requests the license authentication from the authentication unit 37, and receives the authentication result from the authentication unit 37. When the authentication result is normal, the input unit 36 acquires the software identification information of the application execution base software from the authentication unit 37 together with the authentication result.

  The software identification information may be, for example, a product name, a product code, or a product ID (Identifier). In the following description, the software identification information will be described as a product name. That is, the input unit 36 acquires the product name of the application execution base software as the license-authenticated product name from the authentication unit 37.

  The input unit 36 transmits the license-authenticated product name, the application execution base software storage destination directory name, and the user application storage destination directory name to the generation unit 38. Then, the input unit 36 specifies the output information and requests the generation unit 38 to perform packaging indicating that a package file is to be generated.

  The authentication unit 37 corresponds to the authentication unit 11 according to the first embodiment. The authentication unit 37 performs license authentication of the application execution base software and outputs the authentication result. The license authentication process performed by the authentication unit 37 may be performed using a known method.

  Specifically, the authentication unit 37 performs license authentication using the license key received from the input unit 36, and transmits the authentication result (normal or abnormal) to the input unit 36. When the authentication result is normal, the authentication unit 37 acquires the product name of the application execution base software as the license-authenticated product name together with the authentication result (normal), and sends it to the input unit 36.

  When the license authentication is completed normally, the authentication unit 37 may include the license-authenticated product name in the authentication result in addition to the normal result. In other words, the authentication unit 37 may output the authentication result including the licensed product name.

  The generation unit 38 corresponds to the generation unit 12 according to the first embodiment. The generation unit 38 generates a package ID that is package identification information that identifies a package file. The generation unit 38 generates a package file including the application execution base software, the user application, the license authentication result file, and the package ID file. Although the package ID is used as the identification information for identifying the package file in the present embodiment, other information may be used as long as the information uniquely identifies the package file.

  The generation unit 38 includes a package generation unit 381, a file copy unit 382, an ID storage unit 383, an ID acquisition unit 384, and an authentication result storage unit 385.

  The package generation unit 381 stores the software and files for generating the package file in the file copy unit 382, the ID storage unit 383, and the authentication result storage unit 385 in the storage area 35 of the storage 32 in which the package file is stored. To request. The package generation unit 381 compresses the stored files into one file and generates a package file after each processing requested to the file copy unit 382, the ID storage unit 383, and the authentication result storage unit 385 is completed.

  The package generation unit 381 generates a package file in which the license authentication result file and the application execution base software are stored. The application execution base software included in the package file is included in the package file in the state where the user application and the package ID file are stored. The license authentication result file is included in the package file in a state in which the license-authenticated product name and the package ID are stored.

  It should be noted that the user application and the package ID file may be included in the package file in a state of being incorporated inside the application execution base software. Further, in the following description, the package ID file is described as being stored in the application execution base software, but the package ID file does not have to be stored in the application execution base software. In other words, the package generation unit 381 may generate a package file in which the license authentication result file, the application execution base software, and the package ID file are stored.

  The package generation unit 381 requests the file copy unit 382 to copy the file to the storage area 35 by designating the storage destination directory name of the application execution base software and the storage destination directory name of the user application.

  The package generation unit 381 requests the ID storage unit 383 to store the package ID file in the storage area 353 that stores the package ID file.

  The package generation unit 381 specifies the package ID file transmitted from the ID storage unit 383 and the license-authenticated product name, and requests the authentication result storage unit 385 to store the license authentication result file in the storage area 35.

  The file copy unit 382 creates a working directory in the storage area 351 that stores the application execution base software under the storage area 35. The file copy unit 382 copies to the created work directory while maintaining the file structure under the storage destination directory of the received application execution base software.

  The file copy unit 382 also creates a working directory in the storage area 352 that stores user applications under the storage area 35. The file copy unit 382 copies to the storage area 352 while holding the file configuration of the storage directory of the user application.

  The ID storage unit 383 stores the package ID file in which the package ID allocated to the package file generated by the package generation unit 381 is stored. Specifically, the ID storage unit 383 requests the ID acquisition unit 384 to generate a package ID, and receives the package ID generated by the ID acquisition unit 384. The ID storage unit 383 sets the received package ID in the package ID file and stores it in the storage area 353 under the storage area 351.

  The package ID file may be a text file or a binary file. The package ID file may have any file format as long as it can be referenced and updated by the application execution base software, such as an encrypted file using a known method.

  The ID acquisition unit 384 generates a package ID in response to the request from the ID storage unit 383, and transmits it to the ID storage unit 383 that is the caller. The package ID may be an ID that can ensure uniqueness such as a UUID (Universally Unique Identifier). Therefore, the format of the package ID may be any format.

  The authentication result storage unit 385 stores the license authentication result file including the license-authenticated product name and the package ID in the storage area 354 that stores the license authentication result file. The license authentication result file may be a text file or a binary file. The file format of the license authentication result file may be any format as long as it can be referenced and updated by the application execution base software, such as an encrypted file using a known method.

<Example of application execution server configuration>
Next, a configuration example of the application execution server 50 will be described with reference to FIG. FIG. 4 is a diagram illustrating a configuration example of the application execution server according to the second embodiment. The application execution server 50 includes a storage 51, an acquisition unit 54, an authentication unit 55, and an application execution processing unit 56.

  The storage 51 is a memory (storage unit) in which the package file generated by the development PC 30 is stored. Further, the storage 51 expands the package file generated by the development PC 30 and stores the software and files included in the package file.

  The storage 51 includes a storage area 53 in which a package file is stored. The storage area 53 includes a storage area 531 in which application execution base software is stored when the package file is expanded, and a storage area 534 in which a license authentication result file is stored. The storage area 531 also includes a storage area 532 in which a user application is stored and a storage area 533 in which a package ID file is stored. That is, when the package file is expanded, the software and files included in the package file are stored in the corresponding storage areas.

  The acquisition unit 54 corresponds to the acquisition unit 21 according to the first embodiment. When the application execution base software included in the package file is activated, the acquisition unit 54 acquires the product name of the application execution base software included in the package file as its own product name. The acquisition unit 54 acquires the product name of the application execution base software using a known method.

  Upon acquiring the own product name of the application execution base software, the acquisition unit 54 requests the license management unit 551 of the authentication unit 55 to specify the own product name of the application execution base software and determine whether the license has been registered. When the determination result indicating that the license has been registered is received from the license management unit 551, the application execution processing unit 56 is requested to start using the user application.

  On the other hand, when the judgment result indicating that the license is not registered (unregistered) is received from the license management unit 551, the license authentication result judgment unit 552 requests the license authentication and license registration by designating the own product name of the application execution base software. To do. When the license authentication is normally completed and the license registration is normally completed, the license authentication result determination unit 552 requests the application execution processing unit 56 to start using the user application.

  The authentication unit 55 determines whether or not the license of the application execution base software included in the package file is registered. If the license of the application execution base software included in the package file is not registered, the authentication unit 55 performs the license authentication of the application execution base software and performs the license registration. That is, the authentication unit 55 determines whether or not the license of the application execution base software is registered in the own device based on the own product name of the application execution base software acquired by the acquisition unit 54. Then, when the license of the application execution base software is not registered, the authentication unit 55 performs the license authentication of the application execution base software.

  The authentication unit 55 performs license authentication using the own product name acquired by the acquisition unit 54 and the license authentication result file and the package ID file included in the package file generated in the development PC 30.

  The authentication unit 55 includes a license management unit 551, a license authentication result determination unit 552, and a package ID determination unit 553.

  The license management unit 551 determines whether or not the license of the own product name received from the acquisition unit 54 is already registered in the application execution server 50. The license management unit 551 transmits to the acquisition unit 54 a determination result indicating whether the license of the product name is registered or unregistered. It should be noted that the license management unit 551 performs license management by a known method, such as a license check as to whether or not a license is registered.

  The license authentication result determination unit 552 determines whether or not a license authentication result file exists in the storage area 534 of the storage 51 in response to the license registration request from the acquisition unit 54. If the license authentication result file does not exist, the license authentication result determination unit 552 returns the result of license registration as abnormal. That is, if the package file does not include the license authentication result file, the license authentication result determination unit 552 does not perform the license authentication of the application execution base software.

  On the other hand, when the license authentication result file exists in the storage area 534, the license authentication result determination unit 552 determines the own product name received from the acquisition unit 54 and the license-authenticated product name included in the license authentication result file in the storage area 534. It is determined whether and match.

  When the own product name received from the acquisition unit 54 and the license-authenticated product name included in the license authentication result file in the storage area 534 match, the license authentication result determination unit 552 determines that the package ID included in the license authentication result file. To send. Further, in this case, the license authentication result determination unit 552 requests the package ID determination unit 553 to determine the package ID.

  When receiving the determination result that the package IDs match from the package ID determination unit 553, the license authentication result determination unit 552 performs license registration with the license-authenticated product name. When the license registration is completed normally, the license authentication result determination unit 552 transmits the registration result indicating that the license registration is normally completed to the acquisition unit 54. Further, the license authentication result judging unit 552 deletes the authentication result file when the license authentication and the license registration of the application execution base software are normally completed. A known method may be used for license management such as license registration performed by the license authentication result determination unit 552.

  The package ID determination unit 553 determines whether or not the package ID received from the license authentication result determination unit 552 matches the package ID included in the package ID file in the storage area 533. The package ID determination unit 553 transmits the determination result of matching or mismatching to the license authentication result determining unit 552.

  In response to the request from the acquisition unit 54 to start using the user application, the application execution processing unit 56 sets the user application in a usable state after performing necessary initial settings for the application execution base software. In other words, the application execution processing unit 56 executes a predetermined application such as a user application when the license authentication and the license registration of the application execution base software are normally completed.

<Operation example of development PC>
Next, an operation example of the development PC 30 will be described with reference to FIG. FIG. 5 is a diagram illustrating an operation example of the development PC according to the second embodiment. Specifically, FIG. 5 is a diagram illustrating an operation when the development PC 30 generates a package file. As described above, the package file includes the application execution base software that internally stores the user application and the package ID file, and the license authentication result file.

  First, the input unit 36 inputs parameters required for generation (packaging) of a package file (step A1).

  Specifically, the input unit 36 inputs the storage destination directory name of the application execution base software, the storage destination directory name of the user application, and the license key of the application execution base software from the operator who operates the development PC 30.

  Next, the input unit 36 requests the authentication unit 37 for license authentication of the input license key, and determines whether the authentication result is normal (step A2).

  Specifically, the input unit 36 requests the authentication unit 37 for license authentication of the input license key. The authentication unit 37 uses the license key received from the input unit 36 to perform license authentication of the application execution base software.

  When the license authentication is completed normally, the authentication unit 37 transmits the authentication result indicating that the license authentication is normal and the license-authenticated product name to the input unit 36. The authentication unit 37 may include the license-authenticated product name in the authentication result and send it to the input unit 36. On the other hand, when the license authentication is not normally completed, the authentication unit 37 transmits the authentication result indicating the abnormality to the input unit 36.

  The input unit 36 determines whether the authentication result received from the authentication unit 37 is normal, and when the authentication result is normal (YES in step A2), executes step A3. On the other hand, if the authentication result is abnormal (NO in step A2), the development PC 30 ends the process.

  Next, the input unit 36 acquires the license-authenticated product name from the authentication result of the authentication unit 37 (step A3). The input unit 36 sends the license-authenticated product name, the application execution base software storage destination directory name, and the user application storage destination directory name to the package generation unit 381, and requests packaging.

  Next, the file copy unit 382 creates a working directory in the storage area 351 under the storage area 35 and copies the file of the application execution base software to the storage area 351 (step A4).

  Specifically, the package generation unit 381 transmits the storage destination directory name of the application execution base software, the storage destination directory name of the user application, and the file copy unit 382. Further, the package generation unit 381 requests the file copy unit 382 to copy the file of the application execution base software to the storage area 351 under the storage area 35.

  The file copy unit 382 creates a working directory in the storage area 351 in response to a request from the package generation unit 381. The file copy unit 382 copies the application execution base software to the created working directory while maintaining the file structure under the storage directory of the application execution base software received from the package generation unit 381.

  Next, the file copy unit 382 creates a working directory in the storage area 352 that stores the user application under the storage area 35, and copies the file of the user application to the working directory (step A5).

  Specifically, the file copy unit 382 creates a work directory in the storage area 352, and copies the application execution base software to the work directory in which the file structure under the storage directory of the user application is maintained.

  Next, the ID acquisition unit 384 generates a package ID that identifies the package file to be created (step A6).

  Specifically, the package generation unit 381 requests the ID storage unit 383 to store the package ID file in the storage area 353 under the storage area 351. The ID storage unit 383 requests the ID acquisition unit 384 to generate a package ID, and the ID acquisition unit 384 generates a package ID and transmits it to the request source ID storage unit 383.

  Next, the ID storage unit 383 stores the generated package ID as a package ID file in the work directory created in step A4 (step A7).

  Specifically, the ID storage unit 383 stores the package ID as a package ID file under the storage area 351 and sends the package ID to the package generation unit 381 that is the calling source.

  Next, the authentication result storage unit 385 stores the license authentication result file including the license-authenticated product name and the package ID (step A8).

  Specifically, the package generation unit 381 transmits the package ID and the license-authenticated product name to the authentication result storage unit 385, and requests the authentication result storage unit 385 to store the license authentication result file. The authentication result storage unit 385 stores the license authentication result file including the received license-authenticated product name and package ID in the storage area 354.

  Finally, the package generation unit 381 compresses the software and files existing under the storage area 35 as a package file (step A9).

<Operation example of application execution server>
Next, an operation example of the application execution server 50 will be described with reference to FIG. FIG. 6 is a diagram illustrating an operation example of the application execution server according to the second exemplary embodiment. FIG. 6 is a diagram for explaining the operation of the application execution server 50 when performing license registration of the application execution base software included in the package file.

  It is assumed that the package file generated in the development PC 30 is copied and expanded in the application execution server 50 using a known method. As described above, the package file includes the application execution base software in which the user application and the package ID file are stored, and the license authentication result file.

  First, the acquisition unit 54 determines whether the license of the application execution base software included in the package file has been registered via the license management unit 551 (step B1).

  Specifically, the acquisition unit 54 acquires the product name of the application execution base software included in the package file as its own product name. The acquisition unit 54 transmits the product name of the application execution base software to the license management unit 551. The acquisition unit 54 requests the license management unit 551 to determine whether the license of the application execution base software has been registered.

  The license management unit 551 determines whether the license of the own product name received from the acquisition unit 54 is already registered in the application execution server 50. When the license of the own product name is registered, the license management unit 551 transmits a determination result indicating that the license has been registered to the acquisition unit 54. On the other hand, when the license of the product name is not registered, the license management unit 551 sends a determination result indicating that the license is not registered to the acquisition unit 54.

  If the received determination result is registered (YES in step B1), the process proceeds to step B8, and if the received determination result is not registered (NO in step B1), the process proceeds to step B2.

  Next, the license authentication result determination unit 552 determines whether or not the license authentication result file exists (step B2).

  Specifically, the acquisition unit 54 transmits the own product name of the application execution base software to the license authentication result determination unit 552 and requests license registration using the license authentication result. The license authentication result determination unit 552 determines whether or not the license authentication result file exists.

  If the license authentication result file exists (YES in step B2), the process proceeds to step B3. On the other hand, if the license authentication result file does not exist (NO in step B2), the license authentication result determination unit 552 transmits a registration result indicating that the license registration result is abnormal to the acquisition unit 54, and the process ends. .

  Next, the license authentication result determination unit 552 determines whether the license-authenticated product name included in the license authentication result file matches the own product name received from the acquisition unit 54 (step B3).

  When the license-authenticated product name included in the license authentication result file and the self-product name match (YES in step B3), the process proceeds to step B4. On the other hand, when the license-authenticated product name included in the license authentication result file and the own product name do not match (NO in step B3), the license authentication result determination unit 552 determines that the license registration result is abnormal in the acquisition unit 54. A registration result indicating that there is is transmitted, and the process ends.

  Next, the package ID determination unit 553 determines whether or not the package ID included in the license authentication result file and the package ID of the package ID file match (step B4).

  Specifically, the license authentication result determination unit 552 acquires the package ID included in the license authentication result file and sends it to the package ID determination unit 553. The license authentication result determination unit 552 requests whether the transmitted package ID matches the package ID of the package ID file.

  The package ID determination unit 553 determines whether or not the package ID received from the license authentication result determination unit 552 and the package ID of the package ID file match. The package ID determination unit 553 transmits a determination result of whether the package ID received from the license authentication result determination unit 552 and the package ID of the package ID file match or do not match, to the license authentication result determination unit 552.

  When the package ID received from the license authentication result determination unit 552 and the package ID of the package ID file match (YES in step B4), the package ID determination unit 553 determines that the license ID authentication result determination unit 552 matches. Submit the result. Then, the process proceeds to step B5.

  On the other hand, when the received package ID and the package ID of the package ID file do not match (NO in step B4), the package ID determination unit 553 also registers in the acquisition unit 54 that the license registration is abnormal. Is transmitted, and the process ends.

  Next, the license authentication result determination unit 552 performs license registration of the application execution base software included in the package file (step B5).

The license authentication result determination unit 552 determines whether the result of license registration is normal (step B6).
When the license registration is completed normally (YES in step B6), the process proceeds to step B7. On the other hand, when the license registration is not normally completed (NO in step B6), the license authentication result determination unit 552 transmits the registration result indicating that the license registration result is abnormal to the acquisition unit 54, and the processing is performed. To finish.

  Next, when the license authentication and license registration of the application execution base software included in the package file are completed normally, the license authentication result determination unit 552 deletes the license authentication result file (step B7).

  Finally, the application execution processing unit 56 sets the user application in a usable state after performing necessary initial settings for the application execution base software in response to the request from the acquisition unit 54 to start using the user application (step B8).

  As described above, the development PC 30 performs license authentication on the application execution base software. When the license authentication is normally completed, the development PC 30 generates a package file including the authentication result including the product name of the application execution base software and the application execution base software. The development PC 30 also generates a package ID to be assigned to the package file, and includes the generated package ID in the package file.

  The application execution server 50 acquires the own product name of the application execution base software included in the package file. The application execution server 50 performs license authentication based on the acquired own product name and the license-authenticated product name included in the license authentication result file of the package file. Furthermore, the application execution server 50 performs license authentication based on the package ID of the package ID file and the package ID included in the license authentication result file. That is, the application execution server 50 can perform license authentication without requiring additional input information from the user. Therefore, according to the information processing system 100 according to the second embodiment, it is possible to perform license authentication with high user convenience.

  Further, the application execution server 50 enables license authentication using the license authentication result file and the package ID file without inputting a license key. That is, since the application execution server 50 performs the license authentication without using the license key, the license key is not seen by a third party or illegally acquired. Therefore, according to the information processing system 100 according to the second embodiment, it is possible to prevent the license key from being leaked to others, so that it is possible to perform the license authentication while ensuring the security.

  Furthermore, according to the present embodiment, the application execution base software can be executed only with the license-authenticated package file. This is because if the license authentication result file does not exist when the application execution base software is first started, the application execution base software is terminated. This is because the application execution base software is terminated even when the license-authenticated product name in the license authentication result file and the own product name of the application execution base software do not match. Furthermore, when the package ID of the license authentication result file does not match the package ID stored in the application execution base software, the application execution base software is terminated.

(Modification)
The following modifications may be made to the second embodiment described above.
(1) In the above-described embodiment, the package file is described as including one user application, but it may include two or more user applications. That is, the development PC 30 may generate a package file including two or more user applications, and the application execution server 50 may execute the two or more user applications included in the package file.

(2) In the above-described embodiment, it has been described that the application execution base software is already stored (expanded) in the development PC 30, but the application execution base software remains compressed. Good. In this case, the input unit 36 inputs the path name of the compressed file of the application execution base software as a parameter required for packaging. Then, the file copy unit 382 may be configured to expand the compressed file of the application execution base software into the work directory of the storage area 35 as the application execution base software.

(3) In the above-described embodiment, the description has been made assuming that the user application has already been stored (expanded) in the development PC 30, but the user application may remain compressed. In this case, the input unit 36 inputs the path name to the compressed file of the user application as a parameter required for packaging. Then, the file copy unit 382 expands the compressed file of the user application as a user application in an application storage directory such as auto-deployment of application execution base software.

(4) In the above-described embodiment, the package file generated by the development PC 30 is described as being copied and expanded in the application execution server 50. For example, the development PC 30 may further include a transmission unit that operates to transmit the generated package file to the application execution server 50 and expand the package file in the application execution server 50. Even in this case, the same effect as that of the above-described embodiment can be obtained.

(Embodiment 3)
Subsequently, a third embodiment will be described. The third embodiment differs from the information processing system 100 according to the second embodiment in the configuration of the information processing system.

<Example of configuration of information processing system>
An information processing system 200 according to the third exemplary embodiment will be described with reference to FIG. 7. FIG. 7 is a diagram illustrating a configuration example of the information processing system according to the third embodiment. As shown in FIG. 7, the information processing system 200 includes a development PC 30, an application execution server 50, and an automatic environment construction server 60. That is, the information processing system 200 according to the third embodiment includes the automatic environment construction server 60 in addition to the configuration of the information processing system 100 according to the second embodiment.

  The development PC 30, the application execution server 50, and the automatic environment construction server 60 are connected to each other via a computer network 40, and communicate with each other via the computer network 40. The development PC 30 and the application execution server 50 have the same configurations as those in the second embodiment. Therefore, in the present embodiment, the detailed description of the development PC 30 and the application execution server 50 will be omitted as appropriate, and the points different from the second embodiment will be described. The information processing system 200 is configured to include one development PC 30, one application execution server 50, and one automatic environment construction server 60, but may be configured to include two or more each.

  The development PC 30 authenticates the application execution base software and creates (generates) a package file. The package file generated by the development PC 30 is copied to a directory used by the automatic environment construction software 41 of the automatic environment construction server 60 for distribution using a known method. For example, the development PC 30 may include a transmission unit (not shown), and the transmission unit may copy the package file.

  The automatic environment construction server 60 is a server device in which each functional unit described later operates by causing the CPU to execute the automatic environment construction software. The automatic environment construction server 60 is a server device that automatically constructs the environment of the application execution server 50. The automatic environment construction server 60 distributes the package file generated by the development PC 30 to the application execution server 50 and expands it. For example, if the information processing system 200 includes a plurality of application execution servers 50, the automatic environment construction server 60 distributes and expands the package file to all the application execution servers 50. The automatic environment construction server 60 remotely and automatically executes the application execution base software included in the package file expanded in the application execution server 50.

  When the automatic environment construction server 60 automatically executes the application execution base software included in the package file, the application execution server 50 determines whether the application execution base software license is registered. Then, when the license registration of the application execution base software is not performed, the application execution server 50 performs license authentication and license registration.

<Example of automatic environment construction server configuration>
Next, a configuration example of the automatic environment construction server 60 will be described. As shown in FIG. 7, the automatic environment construction server 60 includes a storage 61 and a distribution development unit 64.

  The storage 61 includes a storage area 62 for storing the automatic environment construction software and a storage area 63 for storing the package file. The automatic environment construction software is stored in advance in the storage area 62, and the automatic environment construction software is installed in advance in the automatic environment construction server 60. The package file generated by the development PC 30 is copied to the storage area 63. The storage area 63 is also called a distribution directory for distributing and expanding the package file to the application execution server 50 by the distribution expanding unit 64.

  The distribution expansion unit 64 distributes the package file copied to the storage area 63 to the application execution server 50 and expands it. The distribution expanding unit 64 sets in advance for starting the application execution base software included in the expanded package file, and automatically executes it remotely according to the setting.

<Operation example of information processing system>
Next, an operation example of the information processing system 200 will be described with reference to FIG. FIG. 8 is a diagram illustrating an operation example of the information processing system according to the third embodiment. Specifically, FIG. 8 is an operation example when the automatic environment construction server 60 distributes and expands the package file to the application execution server 50 after the package file is generated in the development PC 30. That is, FIG. 8 is an operation executed after the operation example executed in FIG. 5, and FIG. 6 is executed after executing FIG. The operation example in the development PC 30 and the application execution server 50 is the same as that in the second embodiment, and is the operation example described in FIGS. 5 and 6.

  First, the package file generated in the development PC 30 is copied to the distribution directory of the automatic environment construction server 60 (step C1).

  Next, the distribution expansion unit 64 distributes the package file to the application execution server 50, expands it, and sets for starting the application execution base software included in the package file (step C2). The distribution expanding unit 64 sets according to the function provided by the automatic environment construction software.

  Next, the distribution expanding unit 64 distributes and expands the package file to the application execution server 50 (step C3).

  Finally, the distribution expanding unit 64 makes settings for starting the application execution base software included in the expanded package file in the application execution server 50 (step C4). Note that when the process is executed up to step C4, the application execution server 50 executes the operation described in FIG.

  As described above, also in the present embodiment, as in the second embodiment, the development PC 30 performs license authentication on the application execution base software. The development PC 30 generates a package file including the authentication result including the product name of the application execution base software and the application execution base software. The development PC 30 also generates a package ID to be assigned to the package file, and includes the generated package ID in the package file.

  The application execution server 50 performs license authentication and license registration using the own product name of the application execution base software included in the package file, the authentication result included in the package file, and the package ID. That is, the application execution server 50 can perform license authentication of the application execution base software included in the package file without requiring additional input information from the user. Therefore, according to the information processing system 100 according to the third embodiment, it is possible to perform license authentication with high user convenience.

  Further, the application execution server 50 enables license authentication using the license authentication result file and the package ID file without inputting a license key. That is, since the application execution server 50 performs the license authentication without using the license key, the license key is not seen by a third party or illegally acquired. Therefore, according to the information processing system 100 according to the third embodiment, it is possible to prevent the license key from being leaked to others, so that it is possible to perform the license authentication while ensuring the security.

  Furthermore, according to the present embodiment, the application execution base software can be executed only with the license-authenticated package file.

  In general, when the environment of the application execution server 50 is constructed using the automatic environment construction server 60, it is necessary to set a license key in advance in order to check the license of the application execution base software. However, in the present embodiment, it is possible to perform the license authentication of the application execution base software in the application execution server 50 without setting the license key in the automatic environment construction server 60. Therefore, by using the information processing system 200 according to the present embodiment, the user can save the trouble of setting the license key in advance in the automatic environment construction server 60. Furthermore, by using the information processing system 200 according to the present embodiment, it is not necessary for the user to set the license key, so that it is possible to reduce the risk of the license key leaking to a third party.

(Other embodiments)

  In FIG. 9, the terminal device 10, the server device 20, the development PC 30, the application execution server 50, and the automatic environment construction server 60 (hereinafter, referred to as the terminal device 10 or the like) described in the above-described embodiment are as follows. It may have a hardware configuration. FIG. 9 is a block diagram illustrating a hardware configuration of a terminal device and the like according to each embodiment of the present disclosure.

Referring to FIG. 9, the terminal device 10 or the like includes a processor 1202 and a memory 1203.
The processor 1202 reads the software (computer program) from the memory 1203 and executes the software to perform the processing of the terminal device 10 and the like described using the flowcharts in the above-described embodiment. The processor 1202 may be, for example, a microprocessor, MPU (Micro Processing Unit), or CPU (Central Processing Unit). The processor 1202 may include multiple processors.

  The memory 1203 is composed of a combination of a volatile memory and a non-volatile memory. Memory 1203 may include storage located remotely from processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O interface (not shown).

  In the example of FIG. 9, the memory 1203 is used to store a software module group. The processor 1202 can perform the processing of the terminal device 10 and the like described in the above embodiment by reading out and executing these software module groups from the memory 1203.

  As described with reference to FIG. 9, each of the processors included in the terminal device 10 and the like executes one or a plurality of programs including a group of instructions for causing a computer to execute the algorithm described with reference to the drawings.

  In the above example, the program can be stored using various types of non-transitory computer readable media and supplied to the computer. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer readable media include magnetic recording media (eg, flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg, magneto-optical disks). Further, examples of the non-transitory computer-readable medium include a CD-ROM (Read Only Memory), a CD-R, and a CD-R / W. Further, examples of non-transitory computer readable media include semiconductor memory. The semiconductor memory includes, for example, a mask ROM, a PROM (Programmable ROM), an EPROM (Erasable PROM), a flash ROM, and a RAM (Random Access Memory). In addition, the program may be supplied to the computer by various types of transitory computer readable media. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. The transitory computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.

  It should be noted that the present disclosure is not limited to the above embodiment, and can be modified as appropriate without departing from the spirit of the present disclosure. Further, the present disclosure may be implemented by appropriately combining the respective embodiments.

The whole or part of the exemplary embodiments disclosed above can be described as, but not limited to, the following supplementary notes.
(Appendix 1)
A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. When the package file further included is expanded, an acquisition unit that acquires software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. A server device comprising: an authenticating unit for performing.
(Appendix 2)
The authentication unit is configured such that the acquired software identification information matches the software identification information included in the authentication result, and the package identification information included in the package file and the package identification information included in the authentication result. The server device according to appendix 1, wherein the license authentication is normally completed when the above and the above match.
(Appendix 3)
The authentication unit determines whether or not a license for the predetermined software is registered in the own device based on the acquired software identification information, and if the license is not registered, the license authentication is performed. The server device according to appendix 1 or 2.
(Appendix 4)
4. The server device according to any one of appendices 1 to 3, wherein the authentication unit does not perform the license authentication when the package file does not include the authentication result.
(Appendix 5)
5. The server device according to any one of appendices 1 to 4, wherein the authentication unit deletes the authentication result when the license authentication and the license registration are normally completed.
(Appendix 6)
The predetermined software included in the package file stores the package identification information and an application,
6. The server device according to any one of appendices 1 to 5, further comprising a processing unit that executes the application when the license authentication and the license registration are normally completed.
(Appendix 7)
7. The server device according to any one of appendices 1 to 6, wherein the package file is distributed from another server device and expanded by the other server.
(Appendix 8)
8. The server device according to any one of appendices 1 to 7, wherein the software identification information includes at least one of a product name, a product code, and a product ID (Identifier) of the predetermined software.
(Appendix 9)
9. The server device according to any one of appendices 1 to 8, wherein the predetermined software is application execution base software.
(Appendix 10)
An authentication unit that performs license authentication on predetermined software and, when the license authentication is completed normally, outputs an authentication result including software identification information for identifying the predetermined software,
A generating unit that generates a package file including the predetermined software and the authentication result,
The generation unit generates package identification information for identifying the package file, and includes the generated package identification information in the authentication result and the package file to generate the package file.
(Appendix 11)
Further comprising an input unit for inputting the license key of the predetermined software,
The terminal device according to appendix 10, wherein the authentication unit performs the license authentication using the input license key.
(Appendix 12)
A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. Further, when the included package file is expanded, acquiring software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. What to do and how to activate.
(Appendix 13)
A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. Further, when the included package file is expanded, acquiring software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. An activation program that lets your computer do what you do.
(Appendix 14)
A package file including predetermined software, wherein the package file includes an authentication result including software identification information for identifying the predetermined software and package identification information for identifying the package file, and the package identification information. A terminal device for generating
When the package file is expanded, the software identification information of the predetermined software included in the package file is acquired, and the acquired software identification information, the software identification information included in the authentication result, and the package file are included. And a server device that performs license authentication of the predetermined software using the package identification information included in the authentication result and the package identification information included in the authentication result.
(Appendix 15)
The server device is a first server device,
15. The information processing system according to appendix 14, further comprising a second server device that distributes the package file to the first server device and expands the package file.

1, 100, 200 Information processing system 10 Terminal device 11, 22, 37, 55 Authentication unit 12, 38 Generation unit 20 Server device 21, 54 Acquisition unit 30 Development PC
32, 51, 61 storage 33-35, 53, 62, 63, 351-354 and 531-534 storage area 36 input unit 40 computer network 50 application execution server 56 application execution processing unit 60 automatic environment construction server 64 distribution expansion unit 381 Package generation unit 382 File copy unit 383 ID storage unit 384 ID acquisition unit 385 Authentication result storage unit 551 License management unit 552 License authentication result determination unit 553 Package ID determination unit

Claims (10)

A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. When the package file further included is expanded, an acquisition unit that acquires software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. A server device comprising: an authenticating unit for performing.   The authentication unit is configured such that the acquired software identification information matches the software identification information included in the authentication result, and the package identification information included in the package file and the package identification information included in the authentication result. The server device according to claim 1, wherein the license authentication is normally completed when the two match.   The authentication unit determines whether or not a license for the predetermined software is registered in the own device based on the acquired software identification information, and if the license is not registered, the authentication unit performs the license authentication. The server device according to claim 1 or 2.   The server device according to claim 1, wherein the authentication unit does not perform the license authentication when the package file does not include the authentication result.   The server device according to claim 1, wherein the authentication unit deletes the authentication result when the license authentication and the license registration are normally completed. The predetermined software included in the package file stores the package identification information and an application,
The server device according to claim 1, further comprising a processing unit that executes the application when the license authentication and the license registration are normally completed.   The server device according to claim 1, wherein the software identification information includes at least one of a product name, a product code, and a product ID (Identifier) of the predetermined software. An authentication unit that performs license authentication on predetermined software and, when the license authentication is normally completed, outputs an authentication result including software identification information for identifying the predetermined software,
A generating unit that generates a package file including the predetermined software and the authentication result,
A terminal device, wherein the generation unit generates package identification information for identifying the package file, and includes the generated package identification information in the authentication result and the package file to generate the package file. . A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. Further, when the included package file is expanded, acquiring software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. What to do and how to activate. A package file including predetermined software and an authentication result including software identification information for identifying the predetermined software, wherein package identification information for identifying the package file is included in the package file and the authentication result. Further, when the included package file is expanded, acquiring software identification information of the predetermined software included in the package file,
License authentication of the predetermined software is performed by using the acquired software identification information, software identification information included in the authentication result, package identification information included in the package file, and package identification information included in the authentication result. An activation program that lets your computer do what you do.

Images