Equipment key management system, factory device, equipment device, key activation device, user terminal device, equipment key management method, and equipment key management program

By dividing the IoT device key into an initial and activation key and requiring concurrent user and device authentication, the system mitigates key theft and leakage risks, ensuring secure communication and reducing security costs.

WO2024236671A1PCT designated stage expired Publication Date: 2024-11-21MITSUBISHI ELECTRIC CORP

Patent Information

Application Number
PCT/JP2023/018014
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Existing IoT device key management systems face significant security risks due to the potential theft or leakage of device keys during transportation from manufacturing factories to customers, allowing attackers to decrypt authentication keys and compromise communication with cloud servers.

Method used

The device key is divided into an initial key and an activation key, requiring concurrent requests from both the user terminal device and the IoT device to calculate the device key, with user authentication ensuring legitimate activation and reducing the risk of theft and leakage.

Benefits of technology

This approach significantly reduces the risk of device key theft and leakage, ensuring secure communication by requiring legitimate user authentication and separate delivery of key components, thereby preventing unauthorized access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023018014_21112024_PF_FP_ABST
    Figure JP2023018014_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A factory device (100) generates an equipment key, an initial key for calculating the equipment key, and an activation key, transmits the initial key to an equipment device (200), and transmits the activation key to a key activation device (300). The key activation device (300) is provided with an activation permission flag indicating whether or not activation of the activation key is permitted. The key activation device (300), upon receiving, from a user terminal device (500), an activation permission request requesting activation of the activation key, sets the activation permission flag to a permission condition when authentication for a user is successful. The key activation device (300), upon receiving, from the equipment device (200), an activation key acquisition request, transmit the activation key to the equipment device (200) when the activation permission flag is set to the permission condition. The equipment device (200) calculates the equipment key on the basis of the initial key and the activation key received from the key activation device (300).
Need to check novelty before this filing date? Find Prior Art

Description

Device key operation system, factory device, device, key activation device, user terminal device, device key operation method, and device key operation program

[0001] The present disclosure relates to a device key operation system, a factory device, a device, a key activation device, a user terminal device, a device key operation method, and a device key operation program.

[0002] To provide cloud services to IoT devices, it is necessary to securely connect the IoT devices to a cloud server. To achieve this, it is necessary to embed a device key into the IoT device, which identifies the IoT device as an authorized device. IoT is an abbreviation for Internet of Things. It is desirable to address the security risks that arise when embedding a device key into a device.

[0003] For example, there is a technology that uses a symmetric key or an asymmetric key between an IoT device and a cloud server to authenticate the IoT device on the cloud server side and perform secure communication. To perform such secure communication, the IoT device must have a device key A, and the cloud server must have the same device key A or a key B that pairs with the device key A. The operation of assigning the device key to the IoT device is generally performed in a manufacturing factory when the IoT device is manufactured. Furthermore, the process of transporting the IoT device from the manufacturing factory to the customer may involve multiple external vendors. Under such circumstances, there is a high risk of theft or leakage of the device key after the IoT device is shipped, and the costs of measures to prevent this are high.

[0004] Patent Document 1 discloses a method of using a divided encryption key to decrypt an authentication key required for communication between a user's IC card and a communication terminal. IC is an abbreviation for Integrated Circuit.

[0005] JP 2012-065123 A

[0006] With conventional methods, there is a risk that IoT devices may be stolen before being delivered from the factory to a legitimate user, and fall into the hands of an attacker. Therefore, it is necessary to realize a system that prevents IoT devices from communicating with a cloud server even if they are stolen, that is, a system that prevents attackers from enjoying benefits without risk. Furthermore, even if key information is extracted from an IoT device, it is necessary to prevent communication with a cloud server from being established.

[0007] The technology of Patent Document 1 allows a user to decrypt the authentication key as long as they have the IC card information, even if they do not own the IC card itself. Therefore, it is not possible to authenticate whether the user who sent the IC card information from the mobile terminal is the legitimate user who owns the IC card. Therefore, if the IC card is stolen or the IC card information is leaked, there is a risk that an attacker will be able to decrypt the authentication key.

[0008] The present disclosure aims to reduce the risk of device key theft and leakage by dividing the device key into elements of an initial key and an activation key, and requiring requests from both the user terminal device and the IoT device to calculate the device key.

[0009] The device key operation system of the present disclosure is a device key operation system that operates a device key used to authenticate an information transmission device manufactured in a factory, and includes: a factory device that is used in the factory and generates the device key, an initial key for calculating the device key, and an activation key; a device device that is mounted on the information transmission device; a key activation device that manages the activation key; and a user terminal device that is used by a user of the information transmission device, wherein the factory device transmits a device identifier that identifies the information transmission device and the initial key to the device device, and transmits the device identifier and the activation key to the key activation device, and the key activation device has an activation permission flag that indicates whether activation of the activation key is permitted, and upon receiving an activation permission request requesting activation of the activation key from the user terminal device, authenticates the user, and sets the activation permission flag to "permit" if the user authentication is successful, and upon receiving an activation key acquisition request requesting acquisition of the activation key from the device device, refers to the activation permission flag, and if the activation permission flag is "permit", transmits the activation key to the device, and the device device The device key is calculated based on the initial key and the activation key received from the key activation device.

[0010] In the device key management system according to the present disclosure, the device key is divided into an initial key and an activation key, and calculation of the device key requires requests from both the user terminal device and the device, thereby reducing the risk of device key theft and leakage.

[0011] 12. A diagram showing an example of the configuration of an apparatus key operation system according to embodiment 1. A diagram showing an example of the functional configuration of each device in the apparatus key operation system according to embodiment 1. A diagram showing an example of the hardware configuration of each device in the apparatus key operation system according to embodiment 1. A sequence diagram showing an example of the operation of each device in the apparatus key operation system according to embodiment 1. A schematic diagram showing steps S101 to S103 of FIG. 4. A schematic diagram showing steps S104 to S108 of FIG. 4. A sequence diagram showing an example of the operation of each device in the apparatus key operation system according to embodiment 1. A schematic diagram showing steps S109 to S111 of FIG. 7. A schematic diagram showing steps S112 to S116 of FIG. 7. A schematic diagram showing steps S117 to S118 of FIG. 7. A schematic diagram showing steps S119 to S121 of FIG. 7. A sequence diagram showing an example of the operation of each device in the apparatus key operation system according to embodiment 1. A schematic diagram showing step S122 of FIG. 12. A schematic diagram showing steps S123 to S128 of FIG. 12. FIG. 10 is a diagram showing an example of the hardware configuration of each device in the device key operation system according to a modification of the first embodiment.

[0012] The present embodiment will be described below with reference to the drawings. In each drawing, the same or corresponding parts are assigned the same reference numerals. In the description of the embodiment, the description of the same or corresponding parts will be omitted or simplified as appropriate. The arrows in the drawings mainly indicate the flow of data or the flow of processing.

[0013] Embodiment 1. ***Configuration*** Fig. 1 is a diagram showing an example of the configuration of a device key operation system 800 according to this embodiment. The device key operation system 800 is a system that operates a device key used to authenticate an information transmission device manufactured in a factory. In this embodiment, an IoT device will be used as an example of an information transmission device manufactured in a factory. The IoT device is connected to a network such as the Internet and transmits and receives information. The device key operation system 800 includes a factory device 100, a device device 200, a key activation device 300, an application device 400, and a user terminal device 500. The factory device 100, the device device 200, the key activation device 300, the application device 400, and the user terminal device 500 communicate via a network such as the Internet.

[0014] 2 is a diagram showing an example of the functional configuration of each device in the device key operation system 800 according to this embodiment. Hereinafter, the factory device 100, the device 200, the key activation device 300, the application device 400, and the user terminal device 500 may be referred to as each device in the device key operation system 800.

[0015] The factory device 100 is a computer used in a factory that manufactures IoT devices. The factory device 100 is installed, for example, in a factory that manufactures IoT devices. The factory device 100 is used in the factory to generate a device key 30, an initial key 31 for calculating the device key 30, and an activation key 32. The initial key 31 and the activation key 32 are generated so that the device key 30 cannot be inferred from either of them alone. Methods for generating the device key 30, the initial key 31, and the activation key 32 will be described later. The factory device 100 transmits a device identifier 20 and the initial key 31 that identify the IoT device to the device 200, and transmits the device identifier 20 and the activation key 32 to the key activation device 300. The factory device 100 includes, as functional elements, a device key generation unit 110, an activation key generation unit 120, and an initial key generation unit 130.

[0016] The device 200 is a computer installed in an IoT device. The device 200 manages an initial key associated with a device identifier that identifies the IoT device. In the following description, the device identifier is abbreviated as device ID. ID is an abbreviation for IDentifier. The device 200 includes, as functional elements, an initial key management unit 210, an activation key request unit 220, an activation processing unit 230, and a device key storage unit 240.

[0017] The key activation device 300 is a computer used to provide a device key management service in the device key management system 800. For example, the key activation device 300 manages activation keys associated with device IDs. The key activation device 300 also includes an activation permission flag 321 associated with the device ID and a status flag 322 associated with the device ID. The key activation device 300 includes, as functional elements, an activation key management unit 310 and a flag management unit 320. The flag management unit 320 manages the activation permission flag 321 and the status flag 322. The activation permission flag 321 is a flag indicating whether or not activation of an activation key is permitted. The activation permission flag 321 indicates whether or not activation of an activation key corresponding to a device ID is permitted. For example, the key activation device 300 includes a correspondence table between activation keys associated with device IDs and the activation permission flags 321. The status flag 322 is a flag indicating whether or not activation of an activation key has been performed for an IoT device. For example, the key activation device 300 includes a correspondence table between activation keys corresponding to device IDs and status flags 322 .

[0018] The application device 400 is a computer that provides application services to IoT devices. The application device 400 is also called an application server. The application device 400 is, for example, a cloud server. The application device 400 includes, as functional elements, a device key management unit 410 and a user management unit 420. Note that the key activation device 300 and the application device 400 may be installed in the same device.

[0019] The user terminal device 500 is a terminal used by a user of an IoT device. The user terminal device 500 is a computer such as a smartphone, a tablet terminal, or a portable information processing device. The user terminal device 500 includes an activation permission request unit 510 as a functional element.

[0020] 3 is a diagram showing an example of the hardware configuration of each device in device key operation system 800 according to this embodiment. For ease of explanation, the hardware of each device in device key operation system 800 is denoted by a common reference numeral. However, it is obvious that each device in device key operation system 800 has its own hardware.

[0021] Each device in the device key operation system 800 is a computer. Each device in the device key operation system 800 includes a processor 910, as well as other hardware such as a storage device such as a memory 921 or an auxiliary storage device 922, an input / output interface 930, and a communication interface 950. The processor 910 is connected to the other hardware via a signal line 80 and controls the other hardware.

[0022] As described above, each device in the device key operation system 800 has the functional elements. The functional elements of each device in the device key operation system 800 are realized, for example, by software.

[0023] The processor 910 is a device that executes a device key operation program. The device key operation program is a program that realizes the functions of each device in the device key operation system 800. The processor 910 is an IC that performs arithmetic processing. Specific examples of the processor 910 are a CPU, a DSP, and a GPU. IC is an abbreviation for Integrated Circuit. CPU is an abbreviation for Central Processing Unit. DSP is an abbreviation for Digital Signal Processor. GPU is an abbreviation for Graphics Processing Unit.

[0024] The memory 921 is a storage device that temporarily stores data. Specific examples of the memory 921 are SRAM and DRAM. SRAM is an abbreviation for Static Random Access Memory. DRAM is an abbreviation for Dynamic Random Access Memory. The auxiliary storage device 922 is a storage device that saves data. A specific example of the auxiliary storage device 922 is an HDD. The auxiliary storage device 922 may also be a portable storage medium such as an SD (registered trademark) memory card, CF, NAND flash, flexible disk, optical disk, compact disk, Blu-ray (registered trademark) disk, or DVD. Note that HDD is an abbreviation for Hard Disk Drive. SD (registered trademark) is an abbreviation for Secure Digital. CF is an abbreviation for CompactFlash (registered trademark). DVD is an abbreviation for Digital Versatile Disk.

[0025] The input / output interface 930 is an interface for connecting input / output devices. Specific examples of the input / output interface 930 include USB and HDMI (registered trademark) ports. USB stands for Universal Serial Bus. HDMI (registered trademark) stands for High-Definition Multimedia Interface.

[0026] The communication interface 950 is an interface for communicating with an external device, and is specifically an Ethernet (registered trademark) port or a device for wireless communication.

[0027] The device key operation program is executed in each device of the device key operation system 800. The device key operation program is read into the processor 910 and executed by the processor 910. The memory 921 stores not only the device key operation program but also an OS. OS is an abbreviation for Operating System. The processor 910 executes the device key operation program while executing the OS. The device key operation program and the OS may be stored in an auxiliary storage device 922. The device key operation program and the OS stored in the auxiliary storage device 922 are loaded into the memory 921 and executed by the processor 910. Note that part or all of the device key operation program may be incorporated into the OS.

[0028] Each device in the device key management system 800 may include multiple processors that replace the processor 910. These multiple processors share the task of executing the device key management program. Each processor is a device that executes the device key management program in the same way as the processor 910.

[0029] Data, information, signal values, and variable values ​​used, processed, or output by the device key operation program are stored in the memory 921, the auxiliary storage device 922, or a register or cache memory within the processor 910.

[0030] The "unit" of each unit of each device of device key operation system 800 may be interpreted as a "circuit," "step," "procedure," "process," or "circuitry." The device key operation program causes a computer to execute each process, where the "unit" of each unit of each device of device key operation system 800 is interpreted as a "process." The "process" of each process of each device of device key operation system 800 may be interpreted as a "program," "program product," "computer-readable storage medium storing a program," or "computer-readable recording medium recording a program." The device key operation method is a method performed by each device of device key operation system 800 executing a device key operation program. The device key operation program may be provided by being stored in a computer-readable recording medium. The device key operation program may be provided as a program product.

[0031] ***Explanation of Operation***

[0032] Next, we will explain the operation of each device in the device key operation system 800. The operation procedure of each device in the device key operation system 800 corresponds to a device key operation method. Furthermore, the program that realizes the operation of each device in the device key operation system 800 corresponds to a device key operation program.

[0033] Fig. 4 is a sequence diagram showing an example of the operation of each device in device key operation system 800 according to this embodiment. Fig. 5 is a schematic diagram showing steps S101 to S103 in Fig. 4. Fig. 6 is a schematic diagram showing steps S104 to S108 in Fig. 4.

[0034] <Processing in FIG. 5: Steps S101 to S103> The factory device 100 generates a device key 30 indicating that the IoT device is a legitimate device, and an initial key 31 and an activation key 32 for calculating the device key 30. The factory device 100 then transmits a device ID that identifies the IoT device and the initial key 31 to the device 200. The factory device 100 also transmits the device ID and the activation key 32 to the key activation device 300. The initial key 31 and the activation key 32 are elements that do not cause any problems even if they are leaked individually. Specifically, this is as follows.

[0035] In step S101, the device key generation unit 110 of the factory device 100 generates a different device key 30 for each IoT device using a technique such as random number generation. In step S102, the device key generation unit 110 associates the generated device key 30 with the device ID of the target IoT device and sends it to the application device 400. In step S103, the device key management unit 410 of the application device 400 stores the device ID and the device key 30 in a storage device. For example, the device key management unit 410 of the application device 400 stores a correspondence table in the storage device that associates device IDs with device keys 30.

[0036] <Processing in FIG. 6: Steps S104 to S108> In step S104, the activation key generation unit 120 of the factory device 100 generates the activation key 32 by using the initial key 31, which is a fixed value, for the device key 30. As an example, a hash value is created from the result of calculating the device key 30 and the initial key 31, and this is used as the activation key 32. Note that the initial key 31 and the activation key 32 may also be generated from the device key 30 by other methods.

[0037] For example, the device key generation unit 110 may generate the device key 30 using random numbers, and the activation key generation unit 120 may generate the activation key 32 using random numbers. Then, the initial key generation unit 130 may encrypt the device key 30 with the activation key 32 to generate the initial key 31. Alternatively, for example, the device key generation unit 110 may generate the device key 30 using random numbers, and the initial key generation unit 130 may generate the initial key 31 using random numbers. Then, the activation key generation unit 120 may encrypt the device key 30 with the initial key 31 to generate the activation key 32. Alternatively, for example, the initial key generation unit 130 may generate the initial key 31 using random numbers, and the activation key generation unit 120 may generate the activation key 32 using random numbers. Then, the device key generation unit 110 may generate the device key 30 by encrypting the initial key 31 with the activation key 32. Here, the encryption process may be encryption or hashing.

[0038] In step S105, the activation key generation unit 120 associates the generated activation key 32 with the device ID of the target IoT device and sends them to the key activation device 300. In step S106, the activation key management unit 310 of the key activation device 300 stores the device ID and the activation key 32 in a storage device. In addition, the flag management unit 320 sets the activation permission flag 321 corresponding to the device ID to "not possible" and sets the status flag 322 corresponding to the device ID to "not implemented."

[0039] In step S107, the initial key generation unit 130 associates the generated initial key 31 with the device ID of the target IoT device and sends them to the device 200. In step S108, the initial key management unit 210 of the device 200 stores the device ID and the initial key 31 in the storage device.

[0040] Fig. 7 is a sequence diagram showing an example of the operation of each device in device key operation system 800 according to this embodiment. Fig. 8 is a schematic diagram showing steps S109 to S111 in Fig. 7. Fig. 9 is a schematic diagram showing steps S112 to S116 in Fig. 7. Fig. 10 is a schematic diagram showing steps S117 to S118 in Fig. 7. Fig. 11 is a schematic diagram showing steps S119 to S121 in Fig. 7.

[0041] When the key activation device 300 receives an activation permission request 33 requesting activation of the activation key 32 from the user terminal device 500, the key activation device 300 performs user authentication. If the user authentication is successful, the key activation device 300 sets the activation permission flag 321 to "permitted." Furthermore, when the key activation device 300 receives an activation key acquisition request 34 requesting acquisition of an activation key from the equipment device 200, the key activation device 300 refers to the activation permission flag 321. If the activation permission flag 321 is "permitted," the key activation device 300 transmits the activation key 32 to the equipment device 200. Specifically, this is as follows.

[0042] <Processing in FIG. 8: Steps S109 to S111> The user terminal device 500 includes user information used for user authentication and a device ID in the activation permission request 33 and transmits the request to the key activation device 300. This is processing in which a user of an IoT device performs user registration in the application device 400 using the user terminal device 500 such as a smartphone.

[0043] In step S109, the activation permission request unit 510 of the user terminal device 500 accepts the device ID and user information such as the user's name and email address input by the user. In step S110, the activation permission request unit 510 transmits an activation permission request 33 including the device ID and user information accepted from the user to the key activation device 300. The activation permission request 33 requests activation of the activation key 32 corresponding to the device ID. In step S111, the key activation device 300 receives the activation permission request 33.

[0044] <Processing in FIG. 9: Steps S112 to S116> The key activation device 300 performs user authentication using the user information, and if the user authentication is successful, sets the activation permission flag 321 to "permitted." The key activation device 300 checks the user information included in the activation permission request 33 against user information previously stored in the application device 400. If the check shows that the user authentication is successful, the activation permission flag 321 corresponding to the device ID included in the activation permission request 33 is rewritten to "permitted." Specifically, this is as follows.

[0045] In step S112, the activation key management unit 310 transmits an authentication request for the user information included in the activation permission request 33 to the application device 400. In step S113, the user management unit 420 of the application device 400 compares the user information included in the activation permission request 33 with pre-stored user information. In step S114, the user management unit 420 transmits the result of the comparison to the key activation device 300 as an authentication response to the authentication request. In step S115, the activation key management unit 310 receives the authentication response. If the user authentication is successful, in step S116, the activation key management unit 310 rewrites the activation permission flag 321 corresponding to the device ID included in the activation permission request 33 to "permitted." Although not shown, if the user authentication fails, the activation key management unit 310 transmits an error notification to the user terminal device 500 indicating that the user authentication failed.

[0046] <Processing in FIG. 10: Steps S117 to S118> The device 200 includes the device ID in the activation key acquisition request 34 and transmits it to the key activation device 300. Specifically, the process is as follows.

[0047] In step S117, the activation key request unit 220 of the device 200 transmits an activation key acquisition request 34 including the device ID to the key activation device 300. The activation key request unit 220 may include device authentication information generated based on the initial key 31 in the activation key acquisition request 34. In step S118, the key activation device 300 receives the activation key acquisition request 34.

[0048] <Processing in FIG. 11: Steps S119 to S121> When the key activation device 300 receives the activation key acquisition request 34, it refers to the activation permission flag 321. If the activation permission flag 321 is "permitted," the key activation device 300 transmits the activation key 32 to the equipment device 200. Specifically, this is as follows.

[0049] In step S119, the activation key management unit 310 refers to the activation permission flag 321 corresponding to the device ID included in the activation key acquisition request 34. In step S120, if the activation permission flag 321 is "permitted," the activation key management unit 310 transmits the activation key 32 corresponding to the device ID to the device 200. Although not shown, if the activation permission flag 321 is "not permitted," the activation key management unit 310 transmits an error notification to the device 200 or the user terminal device 500 indicating that the activation key 32 cannot be transmitted to the device 200. In step S121, the device 200 receives the activation key 32.

[0050] Fig. 12 is a sequence diagram showing an example of the operation of each device in device key operation system 800 according to this embodiment. Fig. 13 is a schematic diagram showing step S122 in Fig. 12. Fig. 14 is a schematic diagram showing steps S123 to S128 in Fig. 12.

[0051] <Processing in FIG. 13: Step S122> The device 200 calculates the device key 30 based on the initial key 31 and the activation key 32 received from the key activation device 300. Specifically, this is done as follows.

[0052] In step S122, the activation processing unit 230 of the device 200 generates a device key from the received activation key 32 and the initial key 31 stored in the storage device. For example, the activation processing unit 230 calculates the device key by cryptographically processing (encrypting or hashing) the initial key 31 with the activation key 32. Alternatively, the activation processing unit 230 calculates the device key by decrypting the initial key 31 with the activation key 32. The method for calculating the device key depends on the methods for generating the device key, the initial key, and the activation key. The activation processing unit 230 stores the calculated device key in the storage device.

[0053] <Processing in FIG. 14: Steps S123 to S128> The device 200 transmits a device key authentication request 35 to the application device 400, requesting authentication as to whether the calculated device key is authentic. The device key authentication request 35 includes the calculated device key and a device ID. The application device 400 authenticates whether the device key included in the device key authentication request 35 is authentic, based on the device ID and device key stored in advance in a storage device. Specifically, this is done as follows.

[0054] In step S123, the validation processing unit 230 of the device 200 transmits a device key authentication request 35 including the calculated device key and device ID to the application device 400. The device key authentication request 35 is a request to inquire whether the calculated device key is legitimate. In step S124, the application device 400 receives the device key authentication request 35. In step S125, the device key management unit 410 of the application device 400 compares the device ID and device key stored in advance in the storage device with the device ID and device key included in the device key authentication request 35.

[0055] If the device key included in the device key authentication request 35 is authentic, in step S126 the device key management unit 410 transmits a device key authentication confirmation notification 36 notifying that the device key is authentic to the key activation device 300 and the device 200. The device key authentication confirmation notification 36 includes a device ID corresponding to the calculated device key. Although not shown, if the device key is not authentic, the device key management unit 410 transmits a notification to the device 200 or the user terminal device 500 that the device key included in the device key authentication request 35 is not authentic.

[0056] In step S127, the key activation device 300 receives the device key authentication confirmation notification 36. In step S128, upon receiving the device key authentication confirmation notification 36, the flag management unit 320 of the key activation device 300 sets the activation permission flag 321 corresponding to the device ID to "not permitted." The flag management unit 320 also sets the status flag 322 corresponding to the device ID to "implemented." The key activation device 300 then writes the user information sent in step S111 to the storage device of the application device 400 in association with the device ID. The key activation device 300 may also notify the user terminal device 500 that activation of the device key 30 has been completed, based on the user information corresponding to the device ID.

[0057] When the device key is authenticated as authentic through the above process, communication between the device 200 and the application device 400 becomes possible.

[0058] ***Other Configurations*** <Variation 1> As Variation 1 of the present embodiment, the key activation device 300 may determine whether the activation key acquisition request 34 has been received within a certain time from the time the activation permission request 33 was received. The key activation device 300 then proceeds with processing, treating only the activation key acquisition request 34 received within the certain time as a valid activation key acquisition request 34. If the key activation device 300 receives the activation key acquisition request 34 after the certain time has elapsed, it transmits an error notification to the device 200 or the user terminal device 500. The error notification is displayed on the display device of the device 200 or the display device of the user terminal device 500. Variation 1 of the present embodiment improves security in device key activation.

[0059] <Variation 2> In Variation 2 of this embodiment, the application device 400 may store the expiration date of the device key in a storage device together with the device ID and device key transmitted from the factory device 100. When transmitting the device ID and device key to the application device 400, the factory device 100 also transmits the expiration date of the device key. The application device 400 authenticates whether the calculated device key included in the device key authentication request 35 is authentic based on the device ID, device key, and expiration date stored in the storage device. Specifically, the application device 400 holds a correspondence table of device IDs, device keys, and expiration dates, and checks the expiration date when authenticating whether the device key is authentic. Variation 2 of this embodiment improves the accuracy of device key verification and strengthens security.

[0060] <Variation 3> As Variation 3 of this embodiment, a mode of reissuing a device key for an IoT device will be described. Reissuing a device key for an IoT device is effective when the IoT device is transferred or reused. The factory device 100 receives a device key reissue request from the user terminal device 500, requesting the reissue of a device key for an IoT device corresponding to the device ID. Upon receiving the device key reissue request, the factory device 100 transmits an expiration notification of the device key corresponding to the device ID to the device device 200 or the user terminal device 500. The factory device 100 manages an expiration flag. The factory device 100 then regenerates a device key and an activation key corresponding to the device ID. Here, it is assumed that the initial key has a fixed value. The regeneration method is the same as the method of generating the device key and the activation key described above. The application device 400 stores the device ID and the regenerated device key transmitted from the factory device 100 in a storage device. The key activation device 300 stores the device ID and the regenerated activation key transmitted from the factory device 100 in a storage device. Then, the key activation device 300 sets the status flag 322 of the regenerated activation key corresponding to the device ID from "activated" to "not activated." Thereafter, the activation process of the activation key is performed in the same manner as in the first embodiment described above. According to the third variation of the present embodiment, the device key operation process can be performed in the same manner as in the first embodiment using the regenerated activation key.

[0061] The device key reissue request may be transmitted from the user terminal device 500 to the key activation device 300 or the application device 400. Then, the key activation device 300 or the application device 400 that has received the device key reissue request requests the factory device 100 to reissue the device key. By transmitting the device key reissue request from the user terminal device 500 to the key activation device 300 or the application device 400, user authentication can be performed by the key activation device 300 or the application device 400. In this case, the revocation flag is managed by the key activation device 300 or the application device 400.

[0062] The device key reissue request may also be transmitted from the device 200 to the key activation device 300 or the application device 400. For example, when the device 200 is operated and initialized, communication with the key activation device 300 or the application device 400 can be performed, and the device key can be revoked and reissued at the same time.

[0063] <Variation 4> As Variation 4 of this embodiment, an aspect of performing device key revocation processing for an IoT device will be described. The device key revocation processing for an IoT device can improve security when the IoT device is disposed of. The key activation device 300 receives a device key revocation request from the user terminal device 500, requesting the revocation of the device key of the IoT device corresponding to the device ID. Upon receiving the device key revocation request, the key activation device 300 sets a revocation flag corresponding to the device ID. Furthermore, the key activation device 300 transmits a revocation notification of the device key corresponding to the device ID to the device device 200 and the application device 400. In this way, when the key activation device 300 manages device key revocation, the key activation device 300 is provided with a revocation flag. The revocation flag is set with two pieces of information, such as "expired" and "issued," indicating whether the device key is usable. Variation 4 of this embodiment can improve security when the device is disposed of.

[0064] <Fifth Modification> In a fifth modification of this embodiment, the user terminal device 500 transmits the activation permission request 33 to the key activation device 300, including information indicating that the communication is via the same network as the equipment device 200. For example, the user terminal device 500 includes information indicating that the communication is via the same LAN as the equipment device 200 in the activation permission request 33. When the key activation device 300 receives the activation key acquisition request 34 from the equipment device 200, it checks whether the communication is via the same LAN as the user terminal device 500. If the networks are different, it transmits an error notification to the user terminal device 500 or the equipment device 200. The fifth modification of this embodiment improves security in confirming whether an IoT device is owned by a user.

[0065] <Variation 6> In this embodiment, the functions of each unit of each device in the device key operation system 800 are implemented by software. As a variation, the functions of each device in the device key operation system 800 may be implemented by hardware. Specifically, each device in the device key operation system 800 includes an electronic circuit 909 instead of the processor 910.

[0066] 15 is a diagram showing an example of the hardware configuration of each device in a device key operation system 800 according to a modified example of this embodiment. The electronic circuit 909 is a dedicated electronic circuit that realizes the functions of each unit in each device in the device key operation system 800. Specifically, the electronic circuit 909 is a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field-Programmable Gate Array.

[0067] The functions of each unit of each device in the device key operation system 800 may be realized by a single electronic circuit, or may be distributed and realized by multiple electronic circuits.

[0068] As another modification, some of the functions of each unit of each device in device key operation system 800 may be implemented by electronic circuits, and the remaining functions may be implemented by software. Also, some or all of the functions of each unit of each device in device key operation system 800 may be implemented by firmware.

[0069] Each of the processors and electronic circuits is also called a processing circuitry. That is, the functions of each device in the device key operation system 800 are realized by the processing circuitry.

[0070] ***Description of Effects of the Present Embodiment*** In the device key management system according to the present embodiment, the device key stored in an IoT device is divided into an initial key and an activation key, which can be leaked independently without causing any problems, and each is delivered via a separate route. Only the initial key is stored in the IoT device, and the activation key is stored in the key activation device. Furthermore, it is possible to calculate the device key from the two parts, the initial key and the activation key, in response to requests from both the user terminal device used by the IoT device user and the device installed in the IoT device. Specifically, it is possible to restore the device key by activating the initial key with the activation key.

[0071] As described above, the device key management system according to the present embodiment divides the device key into two elements and delivers them via separate routes, thereby reducing the risk of theft and leakage during key delivery. Furthermore, the device key management system according to the present embodiment introduces a mechanism in which a user requests activation of an activation key from a user terminal device, thereby reducing the risk of device key theft. Furthermore, when an activation key is activated, a user authentication function (confirming that the user owns an IoT device) is performed, thereby reducing the risk of IoT device theft and ensuring the safety of the device keys of installed IoT devices. Furthermore, the device key management system according to the present embodiment is expected to reduce the cost of countermeasures by reducing the risk of device key theft and leakage.

[0072] In the above-described first embodiment, each unit of each device of device key operation system 800 has been described as an independent functional block. However, the configuration of each device of device key operation system 800 does not have to be the same as that of the above-described embodiment. The functional blocks of each device of device key operation system 800 may have any configuration as long as they can realize the functions described in the above-described embodiment. Furthermore, each device of device key operation system 800 may not be a single device, but may be a system composed of multiple devices. Furthermore, multiple parts of the first embodiment may be combined to implement the present invention. Alternatively, only one part of this embodiment may be implemented. In addition, this embodiment may be combined in any way, either as a whole or in part. That is, in the first embodiment, parts of the embodiments may be freely combined, or any component of the embodiments may be modified, or any component of the embodiments may be omitted.

[0073] The above-described embodiments are essentially preferred examples and are not intended to limit the scope of the present disclosure, the scope of application of the present disclosure, or the scope of use of the present disclosure. The above-described embodiments can be modified in various ways as needed. For example, the procedures described using flow charts or sequence diagrams may be modified as appropriate.

[0074] 20 Device identifier, 30 Device key, 31 Initial key, 32 Activation key, 33 Activation permission request, 34 Activation key acquisition request, 35 Device key authentication request, 36 Device key authentication confirmation notification, 100 Factory device, 110 Device key generation unit, 120 Activation key generation unit, 130 Initial key generation unit, 200 Device device, 210 Initial key management unit, 220 Activation key request unit, 230 Activation processing unit, 240 Device key storage unit, 300 Key activation device, 310 Activation key management unit, 320 Flag management unit, 321 Activation permission flag, 322 Status flag, 400 Application device, 410 Device key management unit, 420 User management unit, 500 User terminal device, 510 Activation permission request unit, 800 Device key operation system, 80 Signal line, 909 Electronic circuit, 910 Processor, 921 Memory, 922 auxiliary storage device, 930 input / output interface, 950 communication interface.

Claims

1. A device key operation system that operates a device key used to authenticate an information transmission device manufactured in a factory, comprising: a factory device that is used in the factory and generates the device key, an initial key for calculating the device key, and an activation key; a device mounted on the information transmission device; a key activation device that manages the activation key; and a user terminal device used by a user of the information transmission device, wherein the factory device transmits a device identifier that identifies the information transmission device and the initial key to the device, and transmits the device identifier and the activation key to the key activation device, and the key activation device has an activation permission flag that indicates whether or not the activation of the activation key is permitted, and upon receiving an activation permission request from the user terminal device requesting activation of the activation key, authenticates the user, and sets the activation permission flag to "permission" if the authentication of the user is successful, and upon receiving an activation key acquisition request from the device requesting acquisition of the activation key, refers to the activation permission flag, and if the activation permission flag is "permission", transmits the activation key to the device, and the device an apparatus key operation system that calculates the apparatus key based on the initial key and the activation key received from the key activation device; 2. The device key operation system of claim 1, wherein the user terminal device sends the activation permission request to the key activation device, including user information used to authenticate the user and the device identifier, the key activation device authenticates the user using the user information and sets the activation permission flag to permitted if the user authentication is successful, the device device sends the activation key acquisition request to the key activation device, including the device identifier, and the key activation device, upon receiving the activation key acquisition request, refers to the activation permission flag, and if the activation permission flag is permitted, sends the activation key to the device device.

3. The factory equipment transmits the equipment identifier and the equipment key to an application equipment which communicates with the information transmission equipment, the application equipment stores the equipment identifier and the equipment key transmitted from the factory equipment in a storage device, the equipment equipment transmits an equipment key authentication request including the calculated equipment key and the equipment identifier to the application equipment, the equipment key authentication request requesting authentication as to whether the calculated equipment key is genuine, the equipment key authentication request including the calculated equipment key and the equipment identifier, and the application equipment authenticates as to whether the calculated equipment key included in the equipment key authentication request is genuine based on the equipment identifier and the equipment key stored in the storage device. The equipment key operation system according to claim 1 or claim 2.

4. The device key operation system of claim 3, wherein the application device stores in a storage device the device identifier and the device key transmitted from the factory device, together with the expiration date of the device key, and authenticates whether the calculated device key included in the device key authentication request is genuine based on the device identifier, the device key, and the expiration date stored in the storage device.

5. A device key operation system as described in any one of claims 1 to 4, wherein the factory device generates the initial key as a random number, generates the activation key as a random number, and generates the device key by encrypting the initial key with the activation key.

6. A device key operation system as described in any one of claims 1 to 4, wherein the factory device generates the device key as a random number, generates the activation key as a random number, and generates the initial key by encrypting the device key with the activation key.

7. The device key operation system according to claim 5, wherein the device comprises a device key management unit that calculates the device key by encrypting the initial key with the activation key.

8. The device key operation system according to claim 6, wherein the device device comprises a device key management unit that calculates the device key by decrypting the initial key with the activation key.

9. A device key operation system as described in any one of claims 1 to 8, wherein the key activation device determines whether the activation key acquisition request is received within a certain time period from the time the activation permission request is received, and determines that the activation key acquisition request received within the certain time period is a valid activation key acquisition request.

10. The device key operation system of claim 3 or claim 4, wherein the key activation device has a status flag indicating whether activation of the activation key has been performed or not for the information transmission device, and when it receives the device identifier and the activation key from the factory equipment, it stores the device identifier and the activation key in a storage device, sets the activation permission flag corresponding to the device identifier to disabled, and sets the status flag corresponding to the device identifier to not performed.

11. The device key operation system of claim 10, wherein the application device transmits a device key authentication confirmation notification, which certifies that the calculated device key is legitimate, to the device device and the key activation device, the device key authentication confirmation notification including the device identifier, and upon receiving the device key authentication confirmation notification, the key activation device sets the activation permission flag corresponding to the device identifier to "not enabled" and sets the status flag corresponding to the device identifier to "implemented." 12. The device key operation system of claim 11, wherein, upon receiving a device key reissue request requesting reissue of the device key of the information transmission device corresponding to the device identifier, the factory device transmits an expiration notification of the device key corresponding to the device identifier to the device device and regenerates the device key and activation key corresponding to the device identifier; the application device stores the device identifier and the regenerated device key transmitted from the factory device in a storage device; and the key activation device stores the device identifier and the regenerated activation key transmitted from the factory device in a storage device and sets the status flag of the regenerated activation key corresponding to the device identifier from implemented to not implemented.

13. A device key operation system as described in claim 11 or claim 12, wherein, when the key activation device receives a device key revocation request requesting the revocation of the device key of the information transmission device corresponding to the device identifier, the key activation device sets the status flag corresponding to the device identifier to revoked and transmits a revocation notification of the device key corresponding to the device identifier to the device device and the application device.

14. The device key operation system according to any one of claims 1 to 13, wherein the information transmission device is an IoT (Internet of Things) device.

15. A factory device included in the device key operation system according to any one of claims 1 to 14.

16. A device included in the device key operation system according to any one of claims 1 to 14.

17. A key activation device included in the device key operation system according to any one of claims 1 to 14.

18. A user terminal device included in the device key operation system according to any one of claims 1 to 14.

19. A device key operation method used in a device key operation system that operates a device key used to authenticate an information transmission device manufactured in a factory, comprising: a factory device used in the factory generates the device key, an initial key for calculating the device key, and an activation key, transmits a device identifier that identifies the information transmission device and the initial key to a device device mounted on the information transmission device, and transmits the device identifier and the activation key to a key activation device that manages the activation key; the key activation device has an activation permission flag that indicates whether or not the activation of the activation key is permitted, and upon receiving an activation permission request requesting activation of the activation key from a user terminal device used by a user of the information transmission device, authenticates the user, and sets the activation permission flag to "permission" if the authentication of the user is successful, and upon receiving an activation key acquisition request requesting acquisition of the activation key from the device, refers to the activation permission flag, and if the activation permission flag is "permission", transmits the activation key to the device, and the device calculates the device key based on the initial key and the activation key received from the key activation device.

20. A device key operation program used in a device key operation system that operates a device key used to authenticate an information transmission device manufactured in a factory, the program comprising: causing a computer that is a factory device used in the factory to execute processes of generating the device key, an initial key for calculating the device key, and an activation key, transmitting a device identifier that identifies the information transmission device and the initial key to a device device mounted on the information transmission device, and transmitting the device identifier and the activation key to a key activation device that manages the activation key; the key activation device has an activation permission flag that indicates whether or not the activation of the activation key is permitted; upon receiving an activation permission request requesting activation of the activation key from a user terminal device used by a user of the information transmission device, the key activation device authenticates the user, and sets the activation permission flag to "permission" if the authentication of the user is successful; and upon receiving an activation key acquisition request requesting acquisition of the activation key from the device, the key activation device refers to the activation permission flag, and if the activation permission flag is "permission," causes the computer that is the key activation device to execute processes of an apparatus key operation program that causes a computer that is the apparatus to execute a process of calculating the apparatus key based on the initial key and the activation key received from the key activation device;

Citation Information

Patent Citations

  • Information processing apparatus, server apparatus, information processing method, and program

    JP2011258034A

  • Use control system and use control method

    JP2016105300A

  • Equipment authentication system, manufacturer key generation device, equipment key generation device, production equipment, cooperative authentication device, equipment playback key generation device, equipment authentication method, and equipment authentication program

    WO2015001600A1

Cited By

  • Function authorization method, electronic equipment, program product and storage medium

    CN120296771A