JP6910166B2 - Authentication mediator and authentication mediation program - Google Patents

Description

The present invention relates to an authentication intermediary device that authenticates an embedded device.

Conventionally, when authenticating the use of software in an embedded device that is not connected to a network, for example, a USB dongle that checks whether the software is used under a legitimate license is used. License information is written on the USB dongle. The software authenticated for the license information can be used when the USB dongle is attached to the embedded device, but the software cannot be used when the USB dongle is not attached to the embedded device.

In the authentication method using the USB dongle, not only the hardware cost due to the use of the USB dongle increases, but also the compatibility of the USB driver with the USB dongle and the physical restrictions for connecting the USB dongle. For example, it may be physically difficult to attach a USB dongle to a small device or a panel-mounted device.

As an authentication method without such inconvenience, there is a method of authenticating an embedded device via a device such as a computer connected to a network.

For example, in the client terminal control method disclosed in Patent Document 1, the offline terminal (embedded device) is not connected to the network of the license management server (authentication server) that issues the software license. In addition, software is installed on the offline terminal. The offline terminal includes a data input / output unit that writes to a USB memory connected to an online terminal (authentication mediator) connected to the network. The data input / output unit writes the lock code of the offline terminal itself to the USB memory. Further, the data input / output unit writes in the USB memory a license authentication application that causes the online terminal to send a license issuance request including a lock code to the license management server.

Japanese Unexamined Patent Publication No. 2015-108995 (published on June 11, 2015)

The software of the offline terminal disclosed in Patent Document 1 is pre-installed before the license is issued. Patent Document 1 does not specify when the software is installed on an offline terminal. However, at this time, it is conceivable that the software is installed on the offline terminal at the time of shipment of the offline terminal, or the software is installed on the offline terminal after the purchase of the offline terminal.

Some embedded devices have software installed after purchase. In the system disclosed in Patent Document 1, when such an embedded device is applied as an offline terminal, in order for the software to function on the offline terminal, the software must be installed on the offline terminal prior to issuing a license. There is a need. Therefore, the user needs to install the software on the offline terminal and to issue a license for the software.

Further, depending on the embedded device, it is necessary to download the data necessary for the operation after purchasing the embedded unit 243 device. In such an embedded device, work for downloading data to an offline terminal is also required.

One aspect of the present invention is to simplify the user's operation for introducing and licensing software or the like to an embedded device that is not connected to a licensing device.

In order to solve the above problems, the authentication intermediary device according to one aspect of the present invention licenses an embedded device that is not connected to the licensing device. The licensing device generates a license code including license information. The license code generation instruction unit for instructing the generation of the license code by obtaining the device-specific code unique to the embedded device and giving the device-specific code to the license-granting device, and the license-granting device. A license code transfer control unit that transfers the license code generated based on the device-specific code to the embedded device, and software required for the embedded device to operate after the license code generation is instructed. Alternatively, it is provided with a download control unit that downloads data to the built-in device.

According to the above configuration, the authentication process is performed at the same time when the software or data necessary for the operation of the embedded device is first downloaded. As a result, for example, the download is also executed by inputting the product key for authentication. Therefore, when the authentication is performed, the software or data is also downloaded, so that the user's operation can be simplified.

Even if the authentication intermediary device further includes a license code deletion control unit that controls the embedded device and the licensed device so as to delete the license code stored in the embedded device and the licensed device. good.

According to the above configuration, since the license code is deleted for the embedded device to be replaced due to a failure or the like, it is possible to prevent the embedded device from using the updated software or new data.

In the authentication mediation device, the license code transfer control unit may transfer the license code for the plurality of embedded devices to each of the plurality of connected embedded devices.

According to the above configuration, when there are a plurality of embedded devices, a license can be collectively granted to the plurality of embedded devices.

The authentication intermediary device requests a device-specific code of a plurality of the embedded devices from the embedded device, and acquires the device-specific code from the plurality of embedded devices, a device-specific code acquisition unit, and the device-specific code. The license code generation instruction unit further includes a storage device for storing the device-specific codes of the plurality of embedded devices acquired by the acquisition unit, and the license code generation instruction unit is unique to the devices of the plurality of embedded devices stored in the storage device. The code may be given to the licensing device.

According to the above configuration, when there are a plurality of embedded devices, the device-specific codes of the plurality of embedded devices can be collected and collectively given to the licensing device. As a result, it is possible to efficiently grant licenses to a plurality of embedded devices at once.

In the authentication intermediary device, the license code generation instruction unit has a device-specific code generation unit that generates the device-specific code based on hardware information unique to the embedded device acquired from the plurality of embedded devices. The authentication intermediary device further includes a storage device for storing the device-specific code of the plurality of embedded devices generated by the device-specific code generation unit, and the device-specific code generation unit is stored in the storage device. The device-specific code of the plurality of embedded devices may be given to the licensing device.

According to the above configuration, when there are a plurality of embedded devices, the device-specific codes of the plurality of embedded devices can be collected and collectively given to the licensing device. As a result, it is possible to efficiently grant licenses to a plurality of embedded devices at once.

In the authentication mediation device, the license code transfer control unit may write the license codes of a plurality of the embedded devices on a recording medium that can be attached to the embedded device.

According to the above configuration, when there are a plurality of embedded devices, a license can be collectively granted to the plurality of embedded devices.

The authentication mediation program is an authentication mediation program for operating the computer as any of the above authentication mediation devices, and causes the computer to function as each part.

The certificate authentication system includes any of the above-mentioned authentication intermediary devices, an embedded device that is not connected to the license-granting device, and a license-granting device that generates the license code.

According to the above aspect of the present invention, it is possible to simplify the user's operation for introducing and licensing software or the like to an embedded device that is not connected to the licensing device.

It is a block diagram which shows the structure of the authentication system which concerns on Embodiment 1 of this invention. (A) is a diagram showing the configuration of the authentication system including the authentication intermediary device which is a personal computer, and (b) is a diagram showing the configuration of the authentication system including the authentication intermediary device which is a smartphone. It is a flowchart which shows the procedure of the authentication process by the said authentication system. It is a block diagram which shows the structure of another authentication system which concerns on Embodiment 1 of this invention. It is a flowchart which shows the procedure of the authentication processing by the authentication system shown in FIG. It is a block diagram which shows the structure of the authentication system which concerns on Embodiment 2 of this invention. It is a flowchart which shows the procedure of the authentication processing by the authentication system shown in FIG. It is a block diagram which shows the structure of another authentication system which concerns on Embodiment 2 of this invention. It is a flowchart which shows the procedure of the authentication processing by the authentication system shown in FIG. It is a block diagram which shows the structure of the authentication system which concerns on Embodiment 3 of this invention. It is a flowchart which shows the procedure of the authentication processing by the authentication system shown in FIG. It is a block diagram which shows the structure of another authentication system which concerns on Embodiment 3 of this invention. It is a flowchart which shows the procedure of the authentication processing by the authentication system shown in FIG.

[Embodiment 1]
An embodiment of the present invention will be described below with reference to FIGS. 1 to 3. FIG. 1 is a block diagram showing a configuration of an authentication system 1 according to a first embodiment of the present invention. FIG. 2A is a diagram showing a configuration of an authentication system 1 including an authentication intermediary device 20 which is a personal computer 20a. FIG. 2B is a diagram showing a configuration of an authentication system 1 including an authentication intermediary device 20 which is a smartphone 20b.

<Configuration of authentication system 1>
As shown in FIG. 1, the authentication system 1 includes an embedded device 10, an authentication mediator 20, and an authentication server 30. The authentication system 1 authenticates the embedded device 10 by the authentication mediator 20 and the authentication server 30.

The embedded device 10 includes a display unit 110, an input unit 120, a storage unit 130 (storage device), a device control unit 140, and a communication unit 150. The embedded device 10 incorporates a dedicated OS (Operating System) for realizing a specific function. The embedded device 10 is not limited to a specific device as long as it operates by downloading a download file.

Here, the embedded device 10 shown in FIGS. 2A and 2B is an operation-type display device such as a programmable display that enables operation by a touch panel on the display unit 110 described later. Such a display device stores screen data as data for displaying a screen including images of parts for operation and display. Further, at the time of purchase, such a display device does not have the basic software for operating the display device installed, nor does it store screen data. Therefore, when starting to use the display device, it is necessary to install the software and download the screen data.

When authenticating the embedded device 10, the embedded device 10 is connected to the authentication intermediary device 20. The embedded device 10 and the authentication mediator 20 may be connected by a communication cable such as a USB cable, or may be connected by a wireless LAN (local area network) such as Wi-Fi (registered trademark). Further, as long as the embedded device 10 and the authentication intermediary device 20 can communicate with each other, their connection method is not particularly limited. Further, the embedded device 10 is not connected to the authentication server 30.

The display unit 110 displays the display information of the embedded device 10 supplied from the device control unit 140. The display information includes information indicating the operating state of the embedded device 10, information indicating the execution result of the application program, and the like.

The input unit 120 is a portion where the user inputs information to the embedded device 10. The input unit 120 allows the user to operate the embedded device 10. The input unit 120 gives the information input by the user to the device control unit 140.

The storage unit 130 includes a download file storage unit 131, a hardware information storage unit 132, a license code storage unit 133, and a device-specific code storage unit 134. The storage unit 130 is a storage device provided for storing various types of information, and is composed of various types of memory, internal registers, and the like.

The download file storage unit 131 stores the downloaded program for operating the embedded device 10 and a file of data necessary for the operation. The hardware information storage unit 132 stores the hardware information of the embedded device 10 and is assigned to an internal register. Examples of hardware information include a MAC (Media Access Control) address and an HDD (Hard Disk Drive) number. The license code storage unit 133 stores the license code generated by the authentication server 30. The device-specific code storage unit 134 stores the device-specific code generated by the device-specific code generation unit 145, which will be described later.

The device control unit 140 is a part that controls the embedded device 10, and includes a transmission control unit 141, a license code management unit 142, an operation control unit 143, and a device-specific code generation unit 145.

The transmission control unit 141 controls the communication unit 150 so as to receive the device-specific code request command from the authentication mediation device 20 and transmit the device-specific code generated by the device-specific code generation unit 145 to the authentication mediation device 20. The device-specific code request command is a command that requests the embedded device 10 to transmit the device-specific code, and is issued by the authentication intermediary device 20 as described later.

The license code management unit 142 checks the license code transferred from the authentication server 30 via the authentication intermediary device 20, and notifies the authentication intermediary device 20 of the check result (presence or absence of a problem).

The operation control unit 143 controls the basic operation of the embedded device 10 based on the program and data of the downloaded file.

The device-specific code generation unit 145 generates a unique device-specific code (for example, a locking code) based on the hardware information read from the hardware information storage unit 132 by the device-specific code request command received from the authentication intermediary device 20. do. Specifically, the device-specific code generation unit 145 generates the device-specific code as an encrypted character string by performing a specific calculation based on the hardware information. Since there are several well-known methods for performing this calculation, these methods are used as appropriate to generate device-specific codes. The device-specific code generation unit 145 transmits the generated device-specific code to the authentication intermediary device 20 via the transmission control unit 141 and the communication unit 150.

The hardware information may be used as a device-specific code. When the authentication system 1 is configured in this way, it is not necessary to generate the device-specific code based on the hardware information, so that the device-specific code generation unit 145 is omitted.

The communication unit 150 communicates with the communication unit 250 of the authentication intermediary device 20, transmits the information of the embedded device 10 to the communication unit 250, and receives the information from the authentication intermediary device 20.

The authentication mediation device 20 is a device that mediates authentication between the embedded device 10 and the authentication server 30, and includes a display unit 210, an input unit 220, a storage unit 230, an mediation control unit 240, and a communication unit 250. ..

The authentication intermediary device 20 may be a personal computer (PC) 20a as shown in FIG. 2A, as long as it is a device that can be connected to a network (Internet). As shown in, the smartphone 20b may be used. When the smartphone 20b is used as the authentication intermediary device 20, communication is performed between the authentication intermediary device 20 and the embedded device 10 and between the authentication intermediary device 20 and the authentication server 30 by 3G communication, LTE communication, or the like. As described above, since the smartphone 20b (mobile terminal) can be used as the authentication mediation device 20, portability and operability are improved.

The display unit 210 displays the display information of the authentication intermediary device 20. The display unit 210 displays display information such as the operating state of the authentication intermediary device 20 supplied from the intermediary control unit 240.

The input unit 220 is a portion where the user inputs information to the authentication intermediary device 20. The information is, for example, the product key of the embedded device 10. The product key is an encrypted character string generated from information such as the type of software that can be used, the version of the product (embedded device 10), and the production period of the product. Further, the input unit 220 is composed of a mouse, a keyboard, and the like. The input unit 220 allows the user to operate the authentication mediator 20.

The storage unit 230 includes a registration table 231 and a download file storage unit 232.

As shown in Table 1, the registration table 231 contains various information about the embedded device 10, such as a number, an authentication date, a device-specific code, a product code (product key), an activation status, and a license code. It lists and records download files, status, and comments. With the above number, it is possible to manage up to the number of embedded devices 10 permitted by the license. Therefore, for the plurality of embedded devices 10, the information of the embedded devices 10 that can be written in the registration table is written up to the number permitted by the license. The activation status indicates the activation status of the embedded device 10. The above status is the usage status of the license of the embedded device 10.

By recording the activation history in the registration table 231 in this way, it is possible to manage the situation at the time of failure of the embedded device 10. Further, based on this history, it is possible to manage the number of repairs and the number of replacements of the embedded device 10. The download file storage unit 232 stores a file for downloading a file of a program or data for operating the embedded device 10 downloaded to the embedded device 10.

The mediation control unit 240 includes a device-specific code acquisition unit 241, a device-specific code transfer control unit 242 (license code generation instruction unit), a download control unit 243, and a license code transfer control unit 244.

The device-specific code acquisition unit 241 controls the communication unit 250 so that the device-specific code request command is transmitted to the embedded device 10 to the communication unit 250 when the product key is input to the input unit 220.

The device-specific code transfer control unit 242 controls the communication unit 250 so as to transfer the device-specific code transmitted from the embedded device 10 to the authentication server 30 in order to provide the device-specific code to the authentication server 30. The device-specific code transfer control unit 242 instructs the authentication server 30 to generate a license code by giving the device-specific code to the authentication server 30 via the communication unit 250.

The download control unit 243 receives the license code check result (there is no problem with the license code) from the embedded device 10 by the license code management unit 142, and transfers the download file read from the download file storage unit 232 to the embedded device 10. to download.

The license code transfer control unit 244 controls the communication unit 250 so as to transfer the license code described later transmitted from the authentication server 30 to the embedded device 10 in order to provide the license code to the embedded device 10.

The communication unit 250 communicates with the communication unit 150 of the embedded device 10 without going through the Internet, and also communicates with the communication unit 330 of the authentication server 30, which will be described later, via the Internet (not shown). As a result, the communication unit 250 transmits the information of the authentication intermediary device 20 to the communication unit 150 and the communication unit 330, and receives the information transmitted from the communication unit 150 and the communication unit 330.

The authentication server 30 is a server that authenticates the embedded device 10, and includes a database unit 310, an activation control unit 320, and a communication unit 330.

The database unit 310 stores the license code for authentication in association with the device-specific code acquired from the authentication intermediary device 20. Further, the database unit 310 stores the product key created by the authentication server 30 and the device-specific code of the embedded device 10 in association with each other. By storing the product key and the device-specific code in the database unit 310, the embedded device 10 has a qualification (license grant qualification) for which the license code by the authentication server 30 is granted. The database unit 310 stores the license code generated by the license code generation unit 321 described later in association with the product key, the device-specific code, and the like.

The activation control unit 320 includes a license code generation unit 321 and a determination unit 322. The determination unit 322 refers to the database unit 310 based on the hardware information reflected in the device-specific code transferred from the authentication intermediary device 20, and determines whether or not the license is granted. If the embedded device 10 corresponding to the device-specific code is licensed, the determination unit 322 gives the device-specific code to the license code generation unit 321. The license code generation unit 321 receives the determination of the license granting qualification by the determination unit 322, and generates a license code based on the device-specific code acquired from the authentication intermediary device 20.

The communication unit 330 communicates with the communication unit 250 of the authentication intermediary device 20, transmits the license code to the communication unit 250 of the embedded device 10, and receives the device-specific code from the communication unit 250.

<Procedure of authentication processing by authentication system 1>
Next, the procedure of the authentication process by the authentication system 1 will be described below with reference to FIG. FIG. 3 is a flowchart showing the procedure of the authentication process by the authentication system 1.

As shown in FIG. 3, the processes performed by the embedded device 10 are steps S110 to S140. The process performed by the authentication mediator 20 is steps S210 to S250. The processing performed by the authentication server 30 is steps S310 to S330.

The embedded device 10 is in a state in which software or data necessary for its operation has not been downloaded.

First, when the user inputs the product key to the authentication intermediary device 20 by the input unit 220, the input unit 220 accepts the input of the product key in the authentication intermediary device 20 (step S210).

When the product key is input, the device-specific code acquisition unit 241 requests the device-specific code from the embedded device 10 (step S220). Specifically, the device-specific code acquisition unit 241 issues a device-specific code request command, and outputs the device-specific code request command to the communication unit 250. The communication unit 250 transmits a device-specific code request command to the embedded device 10.

In the embedded device 10, the communication unit 150 gives the received device-specific code request command to the transmission control unit 141. When the transmission control unit 141 receives the received device-specific code request command, the transmission control unit 141 outputs the device-specific code request command to the device-specific code generation unit 145. When the device-specific code generation unit 145 receives the device-specific code request command from the transmission control unit 141, the device-specific code generation unit 145 acquires hardware information from the hardware information storage unit 132. The device-specific code generation unit 145 generates a device-specific code using a known coding technique based on the hardware information. The device-specific code generation unit 145 outputs the device-specific code to the communication unit 150 via the transmission control unit 141, and stores the generated device-specific code in the device-specific code storage unit 134. The communication unit 150 transmits the device-specific code to the authentication intermediary device 20 (step S110).

In the authentication intermediary device 20, the communication unit 250 notifies the device-specific code transfer control unit 242 that the device-specific code has been received. Upon receiving the notification, the device-specific code transfer control unit 242 instructs the communication unit 250 to transfer the device-specific code to the authentication server 30. In response to this instruction, the communication unit 250 transfers the device-specific code to the authentication server 30 (step S230).

In the authentication server 30, the determination unit 322 refers to the database unit 310 (step S310) and determines whether or not the embedded device 10 corresponding to the device-specific code received by the communication unit 330 is licensed (licensing qualification). Step S320).

When the determination unit 322 determines that the license is qualified, the determination unit 322 assigns the device-specific code to the license code generation unit 321. The license code generation unit 321 generates a license code based on the device-specific code received from the determination unit 322 (step S330).

The license code generation unit 321 stores the generated license code in the database unit 310 and outputs it to the communication unit 330. The communication unit 330 transmits the license code from the license code generation unit 321 to the authentication intermediary device 20.

In the authentication mediation device 20, the communication unit 250 notifies the license code transfer control unit 244 that the license code has been received. Upon receiving the notification, the license code transfer control unit 244 instructs the communication unit 250 to transfer the license code to the embedded device 10. Upon receiving this instruction, the communication unit 250 transfers the license code to the embedded device 10 (step S240).

In the embedded device 10, the communication unit 150 gives the license code received from the authentication intermediary device 20 to the license code management unit 142. The license code management unit 142 stores the license code in the license code storage unit 133 (step S120). Further, the license code management unit 142 checks whether or not there is a problem with the saved license code (step S130).

If there is no problem with the license code, in the authentication mediation device 20, the download control unit 243 starts downloading the download file according to the download start instruction from the license code management unit 142 (step S250). Specifically, the download control unit 243 reads the download file stored in the download file storage unit 232 and downloads it to the embedded device 10 via the communication unit 250. In this way, when the activation is completed, the software or data is downloaded to the embedded device 10.

After the download is completed, the download control unit 243 notifies the embedded device 10 that the download is completed via the communication unit 250.

In the above example, the download control unit 243 downloads the software or data after the authentication intermediary device 20 receives the license code and the activation is completed. However, the download control unit 243 licenses the device-specific code by the authentication intermediary device 20 after the device-specific code is transferred from the authentication intermediary device 20 to the authentication server 30 and the generation of the license code is instructed to the authentication server 30. Software or data may be downloaded with or without code reception. However, if the download is performed before receiving the license code, the embedded device 10 cannot use the downloaded software or data even if the software or data is downloaded, unless the activation is completed.

In the embedded device 10, the communication unit 150 transmits the download end notification from the download control unit 243 of the authentication intermediary device 20 to the operation control unit 143. Upon receiving the download end notification, the operation control unit 143 executes the operation of the embedded device 10 using the download file (step S140).

When executing the operation of the embedded device 10, the operation control unit 143 reads the device-specific code from the device-specific code storage unit 134 and acquires the license code from the license code storage unit 133 via the license code management unit 142. .. Then, the operation control unit 143 decrypts the information embedded in the license code by encryption using the device-specific code as a key. The license code includes the functions, conditions, and period that the software can execute. Therefore, the operation control unit 143 determines whether or not the embedded device 10 can operate based on the above information. The operation control unit 143 cannot execute the operation of the embedded device 10 unless the license code can be deciphered. Therefore, the embedded device 10 needs to have a device-specific code together with the license code.

Here, when there are a plurality of embedded devices 10, licenses may be collectively granted to these embedded devices 10. Next, the procedure will be described.

First, the device-specific code acquisition unit 241 issues a device-specific code request command to a plurality of embedded devices 10. The device-specific code acquisition unit 241 temporarily stores and collects the device-specific codes transmitted from the plurality of embedded devices 10 in the storage unit 230 in response to the device-specific code request command.

When collecting the device-specific code from the plurality of embedded devices 10, the device-specific code request command and the device-specific code are exchanged according to the connection form between the embedded device 10 and the authentication intermediary device 20. In the case of a connection form using a communication cable, a plurality of embedded devices 10 are sequentially connected to the authentication intermediary device 20 via a communication cable, and a device-specific code request command is sent between the connected embedded device 10 and the authentication intermediary device 20. And the device-specific code is exchanged. In the case of this connection form, the authentication intermediary device 20 is brought to the site where the embedded device 10 is installed, and the authentication intermediary device 20 and the plurality of embedded devices 10 are connected. Further, in the case of the connection form by wireless LAN, the device-specific code request command and the device-specific code are exchanged in a state where the embedded device 10 to be connected is searched from the plurality of embedded devices 10 by the authentication intermediary device 20 and connected. ..

The communication unit 250 transmits the device-specific code collected in the storage unit 230 to the authentication server 30 under the control of the device-specific code transfer control unit 242. In the authentication server 30, the license code generation unit 321 generates license codes for a plurality of embedded devices 10 based on the device-specific codes.

In the authentication intermediary device 20, the license code transfer control unit 244 temporarily stores and collects a plurality of license codes transmitted from the authentication server 30 in the storage unit 230. Then, the license code transfer control unit 244 sequentially transfers the license codes collected in the storage unit 230 so as to be written to the plurality of embedded devices 10. At this time, the license code is written with the authentication intermediary device 20 and the plurality of embedded devices 10 individually connected in the same manner as when the device-specific code is acquired. At this time, the authentication intermediary device 20 also acquires a download start instruction as a result of checking the license code in the plurality of embedded devices 10 from the connected embedded device 10, and downloads a download file to the embedded device 10. to download.

In this way, by connecting the authentication intermediary device 20 to the plurality of embedded devices 10 by bringing the authentication intermediary device 20 to the site or the like, the device-specific codes of the plurality of embedded devices 10 can be collectively acquired. As a result, in an office or the like, the authentication intermediary device 20 is connected to the authentication server 30 via the Internet, device-specific codes of a plurality of embedded devices 10 are transmitted to the authentication server 30, and the authentication server 30 transmits the device-specific codes of the plurality of embedded devices 10. You can get all the license codes for. Therefore, it is possible to activate a plurality of embedded devices 10 at once. Further, the authentication mediator 20 can collectively store the download files for the plurality of embedded devices 10.

The authentication intermediary device 20 stores the combination of the embedded device 10 (number), the license code, and the download file in association with the above-mentioned registration table. As a result, the authentication mediator 20 can correctly provide the license code and download the download file to each of the plurality of embedded devices 10. Further, when the plurality of embedded devices 10 and the authentication intermediary device 20 are connected via the wireless LAN, the license code can be provided and the download file can be automatically downloaded.

As a result, it is possible to efficiently license the plurality of embedded devices 10 and save the download file.

As described above, in the authentication system 1 of the present embodiment, the authentication intermediary device 20 plays a central role in executing the authentication process for the embedded device 10. Specifically, the authentication intermediary device 20 receives the input of the product key and requests the embedded device 10 for the device-specific code. When the embedded device 10 receives a request for the device-specific code from the authentication mediator 20, the embedded device 10 generates the device-specific code based on the hardware information and transmits the device-specific code to the authentication mediator 20. The authentication mediator 20 transfers the device-specific code received from the embedded device 10 to the authentication server 30. Further, the authentication intermediary device 20 transfers the license code transmitted from the authentication server 30 to the embedded device 10. Further, when the embedded device 10 confirms that there is no problem with the license code, the authentication intermediary device 20 starts downloading the file to the embedded device 10.

According to the above configuration, the authentication process is performed at the same time when the software or data necessary for the operation of the embedded device 10 is first downloaded. As a result, the download is also executed by inputting the product key for authentication, so that the user's operation can be simplified.

When the embedded device 10 downloads software or data for the first time, the operation is automatically executed. The operation is the operation of steps S110 to S140, steps S210 to S250, and steps S310 to S330. Since the authentication mediator 20 automatically authenticates the embedded device 10, the user can easily perform the activation process.

Without the authentication mediator 20, all information exchange between the embedded device 10 and the authentication server 30 must be performed by the user using a USB memory or the like. However, it is not necessary to use the authentication intermediary device 20 between the embedded device 10 and the authentication server 30.

Further, when the embedded device 10 downloads the software or data for the second time or later, the authentication intermediary device 20 determines whether or not the embedded device 10 has been licensed. Further, if the embedded device 10 is not licensed, software or data may not be downloaded to the embedded device 10.

In the above authentication system 1, the embedded device 10 generates the device-specific code, but the authentication mediator 20 may generate the device-specific code. The authentication system configured in this way will be described below.

FIG. 4 is a block diagram showing the configuration of another authentication system 2 according to the present embodiment. In the authentication system 2, the same reference numerals are added to the components having the same functions as the components in the authentication system 1, and the description thereof will be omitted.

<Configuration of authentication system 2>
As shown in FIG. 4, the authentication system 2 includes an embedded device 11, an authentication intermediary device 21, and an authentication server 30. The authentication system 2 is different from the authentication system 1 in that the authentication intermediary device 21 generates a device-specific code.

The embedded device 11 is different from the embedded device 10 in the authentication system 1 in that the device control unit 140 is changed to the device control unit 140a. The device control unit 140a is different from the device control unit 140 in that it does not include the device-specific code generation unit 145.

Further, unlike the device-specific code storage unit 134 of the storage unit 130 in the embedded device 10, the device-specific code storage unit 134 in the storage unit 130 receives the device-specific code transmitted from the authentication intermediary device 21 from the communication unit 150 and receives the device. Stores unique code.

The authentication mediation device 21 is different from the authentication mediation device 20 in that the mediation control unit 240 is changed to the mediation control unit 240a. In the intermediary control unit 240a, the device-specific code acquisition unit 241 has been changed to the hardware information request unit 248 as compared with the intermediary control unit 240, and the device-specific code transfer control unit 242 has the device-specific code generation unit 249 ( The difference is that it has been changed to the license code generation instruction section).

The hardware information request unit 248 controls the communication unit 250 so that the hardware information request command is transmitted to the embedded device 11 to the communication unit 250 when the product key is input to the input unit 220. The device-specific code generation unit 249 generates a device-specific code unique to the embedded device 11 based on the hardware information of the embedded device 11 received from the embedded device 11. The device-specific code generation unit 249 instructs the authentication server 30 to generate a license code by giving the generated device-specific code to the authentication server 30 via the communication unit 250.

<Procedure of authentication processing by authentication system 2>
Next, the procedure of the authentication process by the authentication system 2 will be described below with reference to FIG. FIG. 5 is a flowchart showing the procedure of the authentication process by the authentication system 2.

As shown in FIG. 5, in the embedded device 11, the communication unit 150 gives the received hardware information request command to the transmission control unit 141. Upon receiving the received hardware information request command, the transmission control unit 141 acquires the hardware information from the hardware information storage unit 132 and outputs the hardware information to the communication unit 150. The communication unit 150 transmits the hardware information to the authentication intermediary device 21 (step S110a).

In the authentication intermediary device 21, the device-specific code generation unit 249 generates a device-specific code from the hardware information received by the communication unit 250 using a known coding technique (step S230a). The device-specific code generation unit 249 outputs the generated device-specific code to the communication unit 250. The communication unit 250 transmits the device-specific code to the communication unit 150 of the embedded device 11 and the communication unit 330 of the authentication server 30.

At this time, in the embedded device 11, the communication unit 150 stores the device-specific code in the device-specific code storage unit 134.

The processing after the processing in step S230a is the same as in the case of the authentication system 1. Specifically, the processes of steps S120 to S140 performed by the embedded device 11, the processes of steps S240 and S250 performed by the authentication intermediary device 21, and the processes performed by the authentication server 30 are the same as in the case of the authentication system 1. The same is true.

In the authentication system 2, the download control unit 243 also generates a device-specific code in the authentication intermediary device 20 and sends it to the authentication server 30, so that the license code is generated after the authentication server 30 is instructed to generate the license code. If so, the software or data may be downloaded regardless of whether or not the authentication intermediary device 20 has received the license code. Further, when downloading is performed before receiving the license code, the embedded device 11 cannot use the downloaded software or data unless the activation is completed, which is the same as the authentication system 1.

In the authentication system 2, when there are a plurality of embedded devices 11, licenses may be collectively granted to these embedded devices 11. Next, the procedure will be described.

First, the hardware information request unit 248 issues a hardware information request command to the plurality of embedded devices 11. The device-specific code generation unit 249 generates and stores a device-specific code based on the hardware information each time the hardware information request unit 248 acquires hardware information from the embedded device 11 in response to a hardware information request command. It is temporarily stored in part 230 and collected.

When collecting hardware information from a plurality of embedded devices 11, the hardware information is exchanged according to the connection form between the embedded device 11 and the authentication intermediary device 21. In the case of a connection form using a communication cable, a plurality of embedded devices 11 are sequentially connected to the authentication intermediary device 21 via a communication cable, and hardware information is exchanged between the connected embedded device 11 and the authentication intermediary device 21. Is done. In the case of this connection form, the authentication intermediary device 21 is brought to the site where the embedded device 11 is installed, and the authentication intermediary device 21 and the plurality of embedded devices 11 are connected. Further, in the case of the connection form by wireless LAN, the hardware information is exchanged in a state where the authentication intermediary device 21 searches for the embedded device 11 to be connected from the plurality of embedded devices 11 and connects them.

The transmission of the device-specific codes of the plurality of embedded devices 11 from the authentication intermediary device 21 to the authentication server 30 and the transmission of the license codes of the plurality of embedded devices 11 from the authentication server 30 to the authentication intermediary device 21 are the same as those of the authentication system 1. It is done like this. Further, the writing of the license code and the download of the download file from the authentication intermediary device 21 to the plurality of embedded devices 11 are performed in the same manner as in the authentication system 1.

[Embodiment 2]
The other embodiments of the present invention will be described below with reference to FIGS. 6 and 7. In the present embodiment, the same reference numerals will be added to the components having the same functions as the components in the above embodiment, and the description thereof will be omitted. FIG. 6 is a block diagram showing the configuration of the authentication system 3 according to the second embodiment of the present invention.

<Configuration of authentication system 3>
As shown in FIG. 6, the authentication system 3 includes an embedded device 10, an authentication intermediary device 22, and an authentication server 31 (license licensing device). The authentication system 3 deletes the license code of the pre-replacement embedded device 10a, and authenticates the post-replacement embedded device 10b by the authentication mediator 22 and the authentication server 31. The pre-replacement embedded device 10a is the embedded device 10 before replacement when the embedded device 10 must be replaced due to a failure or the like. In the above case, the embedded device 10b after replacement is the embedded device 10 after replacement.

The authentication mediation device 22 is different from the authentication mediation device 20 in that the mediation control unit 240 is changed to the mediation control unit 240b. The intermediary control unit 240b is different from the intermediary control unit 240 in that it includes the license code deletion control unit 245. The license code deletion control unit 245 requests the license code from the pre-replacement embedded device 10a, and instructs the pre-replacement embedded device 10a and the authentication server 31 to delete the license code given to the pre-replacement embedded device 10a.

The authentication server 31 is different from the authentication server 30 in that the activation control unit 320 is changed to the activation control unit 320a. The activation control unit 320a is different from the activation control unit 320 in that the activation control unit 320a includes a license code deletion unit 323. The license code deletion unit 323 deletes the license code from the database unit 310 according to the license code deletion instruction from the license code deletion control unit 245.

<Procedure of authentication processing by authentication system 3>
Next, the procedure of the authentication process by the authentication system 3 will be described below with reference to FIG. 7. FIG. 7 is a flowchart showing the procedure of the authentication process by the authentication system 2.

As shown in FIG. 7, the processes performed by the pre-replacement embedded device 10a are steps S410 and S420. The process performed by the embedded device 10b after the replacement is step S110 to step S140. The processes performed by the authentication mediator 22 are steps S201a, S201b, and steps S210 to S250. The processes performed by the authentication server 31 are steps S301 and S310 to steps S330.

First, in the authentication intermediary device 22, the license code deletion control unit 245 requests the license code from the pre-replacement embedded device 10a (step S201a). Specifically, the license code deletion control unit 245 issues a license code request command for requesting a license code, and outputs the license code request command to the communication unit 250. The communication unit 250 transmits the license code request command to the pre-exchange embedded device 10a.

In the embedded device 10a, the communication unit 150 gives the received license code request command to the license code management unit 142. When the license code management unit 142 receives the license code request command from the communication unit 150, the license code management unit 142 reads the license code from the license code storage unit 133 and outputs the license code to the communication unit 150. The communication unit 150 transmits the license code to the authentication mediator 22 (step S410).

In the authentication intermediary device 22, the communication unit 250 gives the license code received from the pre-exchange embedded device 10a to the license code deletion control unit 245. The license code deletion control unit 245 issues a license code deletion command for deleting the license code from the communication unit 250, and transmits the license code deletion command to the pre-exchange embedded device 10a and the authentication server 31 via the communication unit 250. .. As a result, the license code deletion control unit 245 instructs the embedded device 11 and the authentication server 31 to delete the license code (step S201b).

In the pre-replacement embedded device 10a, the communication unit 150 gives the license code deletion command received from the authentication intermediary device 22 to the license code management unit 142. The license code management unit 142 deletes the license code stored in the license code storage unit 133 according to the license code deletion command (step S420).

On the other hand, in the authentication server 31, the communication unit 330 gives the license code deletion command received from the authentication intermediary device 22 to the license code deletion unit 323. The license code deletion unit 323 deletes the license code to be deleted from the database unit 310 of the database unit 310 according to the license code deletion command (step S301).

Regarding the embedded device 10b after replacement, the authentication processes of steps S120 to S140, steps S210 to S250, and steps S310 to 330 are the same as the authentication processes performed by the authentication system 1.

As described above, in the authentication system 3 of the present embodiment, the authentication process is performed at the same time when the software or data necessary for the operation of the embedded device 10 is first downloaded. As a result, as in the authentication system 1 of the first embodiment, the download is also executed by inputting the product key for authentication, so that the user's operation can be simplified.

Further, the license code stored in the pre-exchange embedded device 10a and the authentication server 31 is deleted by the instruction from the license code deletion control unit 245 of the authentication intermediary device 22. In addition, a new license code is provided to the post-replacement embedded device 10b to be replaced with the pre-replacement embedded device 10a. As a result, since the license of the pre-replacement embedded device 10a is not recognized, the updated software and new data cannot be downloaded. Therefore, it is possible to prevent the updated software and new data from being used in the pre-exchange embedded device 10a.

In the above authentication system 3, the embedded device 10 generates the device-specific code, but the authentication mediator 22 may generate the device-specific code. The authentication system configured in this way will be described below.

FIG. 8 is a block diagram showing the configuration of another authentication system 4 according to the present embodiment. In the authentication system 4, the same reference numerals are added to the components having the same functions as the components in the authentication systems 2 and 3, and the description thereof will be omitted.

<Configuration of authentication system 4>
As shown in FIG. 8, the authentication system 4 includes an embedded device 11, an authentication mediator 23, and an authentication server 31. The authentication system 4 is common to the other authentication systems 2 of the first embodiment in that the authentication intermediary device 23 generates a device-specific code. Further, the authentication system 4 is common to the authentication system 3 of the present embodiment in that the license code of the pre-replacement embedded device 11a is deleted and the post-replacement embedded device 11b is authenticated by the authentication intermediary device 23 and the authentication server 31. is doing.

The authentication mediation device 23 is different from the authentication mediation device 21 in the authentication system 2 in that the mediation control unit 240a is changed to the mediation control unit 240c. The intermediary control unit 240c is different from the intermediary control unit 240a in that it includes the license code deletion control unit 245. The license code deletion control unit 245 is the same as the license code deletion control unit 245 of the authentication intermediary device 21 in the authentication system 3.

<Procedure of authentication processing by authentication system 4>
Next, the procedure of the authentication process by the authentication system 4 will be described below with reference to FIG. FIG. 9 is a flowchart showing the procedure of the authentication process by the authentication system 4.

As shown in FIG. 9, in the processing of the authentication system 4, the steps S110, S220, and S230 are in steps S110a, S220a, and S230a, respectively, as compared with the processing of the authentication system 3 (see FIG. 7). The difference is that it has been changed. Further, steps S110a, step S220a, and step S230a are the same as the processes (see FIG. 5) performed by the embedded device 11 of the authentication system 2.

[Embodiment 3]
Other embodiments of the present invention will be described below with reference to FIGS. 10 and 11. In the present embodiment, the same reference numerals will be added to the components having the same functions as the components in the above embodiment, and the description thereof will be omitted. FIG. 10 is a block diagram showing the configuration of the authentication system 5 according to the third embodiment of the present invention.

<Configuration of authentication system 5>
As shown in FIG. 10, the authentication system 5 includes an embedded device 12, an authentication intermediary device 24, an authentication server 30 (license granting device), and a USB memory (storage medium). The authentication system 5 communicates between the embedded device 12 and the authentication intermediary device 24 via a USB memory that can be attached to the embedded device 12.

The embedded device 12 is different from the embedded device 10 in that the device control unit 140 is changed to the device control unit 140b. The device control unit 140b is different from the device control unit 140 in that it includes a download control unit 144. The download control unit 144 executes software or data download in response to an instruction from the communication unit 150 to start downloading while the USB memory is connected.

The authentication mediator 24 is different from the authentication mediator 20 in that the storage unit 230 is changed to the storage unit 230a (storage device). The storage unit 230a is different from the storage unit 230 in that it includes a license code storage unit 233. The license code storage unit 233 temporarily stores the license code transmitted from the authentication server 30. Further, the authentication mediation device 24 is different from the authentication mediation device 20 in that the mediation control unit 240 is changed to the mediation control unit 240d. The intermediary control unit 240d is different from the intermediary control unit 240 in that it does not include the device-specific code acquisition unit 241 and includes the registration table generation unit 246. The registration table generation unit 246 generates a registration table in the USB memory via the communication unit 250.

The USB memory is connected to the communication unit 150 of the embedded device 11 and the communication unit 250 of the authentication intermediary device 24.

<Procedure of authentication processing by authentication system 5>
Next, the processing procedure of the authentication system 5 will be described below with reference to FIG. FIG. 11 is a flowchart showing the procedure of the authentication process by the authentication system 3.

As shown in FIG. 11, the processes performed by the embedded device 12 are step S115, and steps S125 and S140. The processes performed by the authentication mediator 24 are step S202a, step S202b, step S230, and steps S241 to S243. The process performed by the authentication server 30 is the same as that of the authentication system 1.

First, when the USB memory is connected to the communication unit 250 of the authentication mediation device 24, the authentication mediation device 24 initializes the USB memory (step S202a). After the USB memory is initialized, the registration table generation unit 246 generates a registration table in the USB memory (step S202b).

When the USB memory is connected to the communication unit 150 after the registration table is generated in the USB memory, the transmission control unit 141 instructs the device-specific code generation unit 145 to generate the device-specific code. Upon receiving the instruction from the transmission control unit 141, the device-specific code generation unit 145 acquires the hardware information from the hardware information storage unit 132. The device-specific code generation unit 145 generates a device-specific code based on the hardware information. The device-specific code generation unit 145 outputs the device-specific code to the communication unit 150 via the transmission control unit 141, and stores the generated device-specific code in the device-specific code storage unit 134. The communication unit 150 writes the device-specific code in the registration table of the USB memory (step S115).

After the device-specific code is written in the USB memory, when the USB memory is connected to the communication unit 250, the communication unit 250 reads the device-specific code from the USB memory and gives it to the device-specific code transfer control unit 242. The device-specific code transfer control unit 242 transfers the device-specific code to the authentication server 30 (step S230).

When the communication unit 330 receives the device-specific code in the authentication server 30, the process of steps S310 to S330 described above is performed.

After the process of step S330, the license code generation unit 321 outputs the generated license code to the communication unit 330. The communication unit 330 transmits the license code to the authentication intermediary device 22.

In the authentication intermediary device 24, the communication unit 250 gives the license code received from the authentication server 30 to the license code transfer control unit 244. In the present embodiment, the license code transfer control unit 244 stores the license code in the license code storage unit 233 (step S241).

After saving the license code, in the authentication mediation device 24, the download control unit 243 saves the download file in the download file storage unit 232 (step S242). Specifically, when a recording medium (CD, memory card, etc.) in which a download file is stored is attached to the authentication mediation device 24, the authentication mediation device 24 transfers the download file from the recording medium to the download file storage unit 232. save.

When the USB memory is connected to the authentication mediator 24, the license code transfer control unit 244 reads the license code from the license code storage unit 233 and outputs it to the communication unit 250. When the USB memory is connected to the authentication mediator 24, the download control unit 243 reads the download file from the download file storage unit 232 and outputs it to the communication unit 250. The communication unit 250 performs a process of writing the license code to the USB memory under the control of the license code transfer control unit 244. Further, the communication unit 250 writes the download file to the USB memory (step S243).

When the USB memory is connected to the communication unit 150 in the embedded device 12, the download control unit 144 reads the download file from the USB memory via the communication unit 150 and saves it in the download file storage unit 131 (step S125). .. Further, the license code management unit 142 reads the license code from the USB memory via the communication unit 150 and stores it in the license code storage unit 133.

After the license code and the download file are saved, the operation control unit 143 is notified that the download is completed. Upon receiving that the download is completed, the operation control unit 143 executes the operation of the embedded device 12 (step S140).

As described above, in the authentication system 5 of the present embodiment, the authentication process is performed at the same time when the software or data necessary for the operation of the embedded device 12 is first downloaded. As a result, as in the authentication system 1 of the first embodiment, the download is also executed by inputting the product key for authentication, so that the user's operation can be simplified.

Further, in the authentication system 5, a USB memory is connected to the embedded device 12 and the device-specific code from the embedded device 12 is stored in the USB memory. As a result, even when there are a plurality of embedded devices 12, the device-specific codes of the plurality of embedded devices 12 can be collectively stored in the USB memory.

Further, the authentication mediator 24 can collectively activate the plurality of embedded devices 12 by acquiring the device-specific codes generated by the plurality of embedded devices 12 from the USB memory. Specifically, the authentication intermediary device 24 acquires the device-specific codes of the plurality of embedded devices 12 stored in the USB memory from the connected USB memory and transfers them to the authentication server 30, and the authentication intermediary device 24. The device-specific code and the license code for the plurality of embedded devices 12 are exchanged between the 24 and the authentication server 30. Then, the USB memory in which the license code and the download file are written from the authentication intermediary device 24 is attached to each of the plurality of embedded devices 12. As a result, even when the plurality of embedded devices 12 are installed at a location away from the location where the authentication intermediary device 24 is installed, the license code and the download file can be easily saved for the plurality of embedded devices 12. Can be done.

In the above authentication system 5, the embedded device 12 generates the device-specific code, but the authentication mediator 24 may generate the device-specific code. The authentication system configured in this way will be described below.

FIG. 12 is a block diagram showing the configuration of another authentication system 6 according to the present embodiment. In the authentication system 6, the same reference numerals are added to the components having the same functions as the components in the authentication systems 2 and 5, and the description thereof will be omitted.

<Configuration of authentication system 6>
As shown in FIG. 12, the authentication system 6 includes an embedded device 13, an authentication mediator 25, and an authentication server 30. The authentication system 6 is common to the other authentication systems 2 of the first embodiment in that the authentication intermediary device 25 generates a device-specific code. Further, the authentication system 6 is common to the authentication system 5 of the present embodiment in that data and download files are exchanged between the embedded device 13 and the authentication intermediary device 25 via a USB memory.

The embedded device 13 is different from the embedded device 12 in the authentication system 5 in that the device control unit 140b is changed to the device control unit 140c. The device control unit 140c is different from the device control unit 140b in that it does not include the device-specific code generation unit 145.

The authentication mediation device 25 is different from the authentication mediation device 24 in the authentication system 5 in that the mediation control unit 240d is changed to the mediation control unit 240e. The intermediary control unit 240e is different from the intermediary control unit 240d in that the device-specific code transfer control unit 242 is changed to the device-specific code generation unit 249. The registration table generation unit 246 is the same as the registration table generation unit 246 included in the authentication intermediary device 24 in the authentication system 5 of the third embodiment.

<Procedure of authentication processing by authentication system 6>
Next, the procedure of the authentication process by the authentication system 6 will be described below with reference to FIG. FIG. 13 is a flowchart showing the procedure of the authentication process by the authentication system 6.

As shown in FIG. 13, the process of the authentication system 6 is different from the process of the authentication system 5 in that steps S115 and S230 are changed to step S115a and step S230a, respectively. Further, step S230a is the same as step S230a performed by the authentication mediator 21 of the authentication system 2.

Here, only steps S115a and S230a will be described. Other than these processes, the processes are the same as those performed by the authentication system 5. When the USB memory for which the registration table is generated by the process of step S202b is connected to the communication unit 150, the transmission control unit 141 reads the hardware information from the hardware information storage unit 132 and outputs it to the communication unit 150. The communication unit 150 writes the hardware information to the USB memory (step S115a).

When the USB memory in which the hardware information is written is connected to the communication unit 250, the communication unit 250 reads the hardware information from the USB memory and gives it to the device-specific code generation unit 249. The device-specific code generation unit 249 generates a device-specific code based on the hardware information (step S230a). The communication unit 250 transmits the device-specific code to the authentication server 30.

In step S243, the communication unit 250 writes not only the license code and the download file but also the device-specific code to the USB memory. As a result, the license code, the download file, and the device-specific code supplied via the USB memory are stored in the embedded device 13.

The embedded device 13 does not have to hold the hardware information internally. For example, the embedded device 13 holds hardware information in the form of a bar code, a QR code (registered trademark), or the like outside the embedded device 13. For example, a sticker on which a barcode indicating hardware information is written is attached to the surface of the embedded device 13. The authentication mediator 25 reads this hardware information with a connected reading device (such as a bar code reader). The device-specific code generation unit 249 of the authentication mediator 25 generates a device-specific code based on the hardware information read by the reading device.

As a result, when acquiring hardware information from the embedded device 13, it is not necessary to turn on the power of the embedded device 13 as in the case of connecting a USB memory or a USB cable, and it does not take time and effort. Further, when the embedded device 13 is out of order, it may not be possible to access the embedded device 13 when the license code of the embedded device 13 is deleted. Even if the embedded device 13 cannot be accessed, the hardware information of the embedded device 13 can be obtained by the method using the barcode reader, so that the process of deleting the license code shown in the second embodiment is performed. It can be performed. Hardware information may also be acquired in this way for the authentication intermediary device 23 of the fourth embodiment and the authentication intermediary device 24 of the fifth embodiment.

[Example of realization by software]
Each control block (device control units 140, 140a, 140b, 140c and mediation control units 240, 240a to 240e) of the embedded devices 10 to 13 and the authentication mediation devices 20 to 25 is formed in an integrated circuit (IC chip) or the like. It may be realized by a logic circuit (hardware). Further, the control block may be realized by software using a CPU (Central Processing Unit).

In the latter case, the embedded devices 10 to 13 and the authentication intermediary devices 20 to 25 are a CPU that executes an instruction of a program (authentication intermediary program for the authentication intermediary devices 20 to 25) which is software for realizing each function, the above program, and the above program. It is equipped with a ROM (Read Only Memory) or storage device (these are referred to as "recording media") in which various data are readablely recorded by a computer (or CPU), a RAM (Random Access Memory) for developing the above program, and the like. There is. Then, the object of the present invention is achieved by the computer (or CPU) reading the program from the recording medium and executing the program. As the recording medium, a "non-temporary tangible medium", for example, a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used. Further, the program may be supplied to the computer via an arbitrary transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program. It should be noted that one aspect of the present invention can also be realized in the form of a data signal embedded in a carrier wave, in which the above program is embodied by electronic transmission.

The present invention is not limited to the above-described embodiments, and various modifications can be made within the scope of the claims, and the embodiments obtained by appropriately combining the technical means disclosed in the different embodiments. Is also included in the technical scope of the present invention.

1, 2, 3, 4, 5, 6 Authentication system 10, 10a, 10b, 11, 12, 13 Embedded device 20, 21, 22, 23, 24, 25 Authentication mediator 30, 31 Authentication server (license granting device)
141 Transmission control unit 144 Download control unit 145 Device-specific code generation unit 230, 230a Storage unit (storage device)
241 Device-specific code acquisition unit 242 Device-specific code transfer control unit (license code generation instruction unit)
243 Download control unit 244 License code transfer control unit 248 Hardware information request unit 249 Device-specific code generation unit (license code generation instruction unit)

Claims (7)

License to an embedded device that is not connected to a licensing device Obtain a device-specific code specific to the embedded device for the licensing device to generate a license code containing license information, and obtain the device-specific code. To the license-granting device to instruct the generation of the license code, and a license code generation instruction unit.
A license code transfer control unit that transfers the license code generated by the license-granting device based on the device-specific code to the embedded device.
A download control unit that downloads software or data necessary for the embedded device to operate after the instruction to generate the license code is given to the embedded device .
An authentication intermediary device including a storage device that stores a combination of the device-specific code, the license code, and information of a download file for downloading the software or data in association with a registration table. .. The first aspect of claim 1 is further provided with a license code deletion control unit that controls the embedded device and the licensed device so as to delete the license code stored in the embedded device and the licensed device. The listed authentication intermediary device. The authentication intermediary device according to claim 1 or 2, wherein the license code transfer control unit transfers the license code for the plurality of embedded devices to each of the plurality of connected embedded devices. A device-specific code acquisition unit that requests the device-specific code of the plurality of embedded devices from the embedded device and acquires the device-specific code from the plurality of embedded devices is further provided.
Said storage device stores the device-specific code for a plurality of the embedded device obtained by the device-specific code acquiring unit,
The authentication intermediary device according to claim 3, wherein the license code generation instruction unit gives the license-granting device the device-specific codes of the plurality of embedded devices stored in the storage device. The license code generation instruction unit has a device-specific code generation unit that generates the device-specific code based on hardware information unique to the embedded device acquired from the plurality of embedded devices.
Said storage device stores the device-specific code for a plurality of the embedded device generated by the device-specific code generation unit,
The authentication intermediary device according to claim 3, wherein the device-specific code generation unit gives the device-specific code of a plurality of the embedded devices stored in the storage device to the licensing device. The authentication intermediary device according to claim 1 or 2, wherein the license code transfer control unit writes the license codes of a plurality of the embedded devices on a recording medium that can be attached to the embedded devices. The authentication mediation program for operating a computer as the authentication mediation device according to any one of claims 1 to 6, and the authentication mediation program for operating the computer as each part.

Images