Terminal device and program

Abstract

We provide a terminal device and program that uses an unconventional concept to enable recording on a blockchain. [Solution] In an information processing system having multiple terminal devices 100 and an information processing device 300 capable of communicating with the terminal devices 100, the terminal devices 100 have a memory unit 190 that stores a first key, and a read / record unit 160 that creates a second key using the first key and creation information, and records transaction information encrypted using the second key in a blockchain.

Description

[Technical Field]

[0001] The present invention relates to a terminal device and a program for recording data in a blockchain. [Background technology]

[0002] In recent years, efforts to utilize blockchains have been actively made. As an example, Patent Document 1 proposes an embodiment in which a privileged node and multiple ordinary nodes are provided, the ordinary node has a transaction input unit that accepts input of transaction data, a transaction sending unit that sends the transaction data, a transaction management unit that manages transaction histories as a blockchain, and a block receiving unit that receives blocks from the privileged node, the privileged node has a transaction receiving unit that receives transaction data from the ordinary node, a block generating unit that generates a signature value based on a private key and generates a block as a data set including the transaction data and the signature value, and a block sending unit that sends the block, and the transaction management unit of the ordinary node links the block to the blockchain on the condition that it can confirm the authenticity of the signature value of the block received from the privileged node using a public key. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2020-088864 Summary of the Invention [Problem to be solved by the invention]

[0004] The invention described in Patent Document 1 simply aims to achieve both stabilization and facilitation of transactions in blockchain.

[0005] The present invention provides a terminal device and a program that enable recording to a blockchain using an idea different from the idea conventionally used in Patent Document 1 and the like. [Means for solving the problem]

[0006] The terminal device according to the present invention comprises: a storage unit that stores a first key; a read / write unit that generates a second key using the first key and the generation information, and records the encrypted transaction information using the second key in the blockchain; may also be provided.

[0007] In the terminal device according to the present invention, the storage unit stores a plurality of software programs; the reading and recording unit creates a plurality of second type keys using the first key and different creation information, Each of the second-type keys is associated with predetermined information of one designated software, When recording information about a certain designated software, the reading and recording unit may record the information in the blockchain using a second type of key associated with predetermined information about the certain designated software.

[0008] In the terminal device according to the present invention, The reading and recording unit may record information in the designated software for each of one or more predetermined blockchains.

[0009] In the terminal device according to the present invention, the storage unit stores general-purpose software; When recording information about the general-purpose software, the reading and recording unit may record the information in the blockchain using the first key.

[0010] In the terminal device according to the present invention, The creation information may include user identification information or terminal identification information.

[0011] In the terminal device according to the present invention, When information encrypted using a specified private key is written to the blockchain from outside, the reading and recording unit may decrypt the information written to the blockchain using a specified public key corresponding to the specified private key, and may be controlled according to that information.

[0012] In the terminal device according to the present invention, When information regarding the use of designated software encrypted using a specified private key is written to the blockchain from outside, the reading and recording unit may decrypt the information written to the blockchain using a specified public key corresponding to the specified private key while the designated software is being used, and may be controlled according to that information.

[0013] The terminal device according to the present invention comprises: The device may further include a control unit that imposes operational restrictions if the device has not been running for a predetermined period of time or if the memory unit stores more than a predetermined amount of information to be written to the blockchain.

[0014] In the terminal device according to the present invention, The first key may be installed and associated with the terminal device when the terminal device is manufactured.

[0015] In the terminal device according to the present invention, the storage unit stores a plurality of software programs; the reading and recording unit creates a plurality of second type keys using the first key and different creation information, Each of the second type keys is associated with one designated piece of software; When recording information about a certain designated software, the reading and recording unit may record the information in the blockchain using a second type of key associated with the certain designated software.

[0016] In the terminal device according to the present invention, The reading and recording unit may record information in a different block chain for each designated software.

[0017] In the program according to the present invention, A program to be installed on a terminal device, The terminal device in which the program is installed a memory function for storing a first key; a recording function that generates a second key using the first key and the information for generation, and records the transaction information encrypted using the second key in the blockchain; may also be provided. [Effects of the Invention]

[0018] In the present invention, a second key is generated using the first key and the generation information, and encryption is performed using the second key. If the transaction information is recorded in the blockchain, a new second key can be created in the terminal device and used to write to the blockchain, which is expected to have a wide range of applications. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a schematic block diagram of an information processing system according to an embodiment of the present invention. [Figure 2] 2 is a schematic block diagram of an information processing system according to an embodiment of the present invention, different from that of FIG. 1; [Figure 3] FIG. 1 is a diagram showing interactions between a reading and recording unit and a blockchain used in an embodiment of the present invention. [Figure 4] FIG. 10 is a diagram showing an example of how writing to a blockchain is performed in an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram showing another example of how writing to a blockchain is performed in an embodiment of the present invention. [Figure 6] FIG. 10 is a diagram showing an example of a screen displayed on a management terminal used in an embodiment of the present invention. [Figure 7] A figure showing the detailed status screen for "PC001" that appears when you tap "PC001" in Figure 6. [Figure 8]FIG. 4 is a diagram showing an example of a screen displayed on a user terminal used in an embodiment of the present invention. [Figure 9] FIG. 10 is a diagram showing an example of a screen displayed when a user terminal is operated on the management terminal used in the embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example of a screen displayed on the management terminal when an input is made to turn off the web camera of the user terminal in FIG. 9; [Figure 11] FIG. 10 is a diagram showing an example of a screen displayed on a user terminal after inputting, via the management terminal, that the web camera of the user terminal is to be turned off. [Figure 12] FIG. 2 is a diagram showing an example of a processing flow according to an embodiment of the present invention. [Figure 13] FIG. 10 is a diagram illustrating writing of a log according to an embodiment of the present invention. [Figure 14] FIG. 10 illustrates command issuance and command execution according to another embodiment of the present invention. [Figure 15] FIG. 10 illustrates command issuance and command execution according to yet another embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0020] Embodiment In this embodiment, not only a terminal device and a program are provided, but also a recording medium including a USB memory or the like for recording the program, an information processing device, an information processing system consisting of the information processing device and the terminal device, and an information processing method using these. In this embodiment, "or" and "alternative" also include the meanings of "and" and "as well." That is, for example, in this embodiment, "A or B" means either "A, B, or A and B."

[0021] As shown in FIG. 1, the information processing system of this embodiment may include a plurality of terminal devices 100 and an information processing device 300 capable of communicating with the terminal devices 100. The terminal devices 100 are typically smartphones, tablets, personal computers, etc. The information processing device 300 is typically a server. The information processing device 300 of this embodiment may be composed of one device or multiple devices. Furthermore, when the information processing device 300 is composed of multiple devices, the devices do not need to be installed in the same space, such as the same room, but may be installed in different rooms, different buildings, different regions, etc., and may have different administrators or owners. A typical example of an aspect in which the information processing device 300 is composed of multiple devices is when a distributed server is used as the information processing device 300.

[0022] 1 and 2, the terminal device 100 may have an operation unit 121 for inputting various information, a display unit 122 for displaying various information, a terminal transmission unit (transmission unit) 131 for transmitting data, and a terminal reception unit (reception unit) 132 for receiving data. The terminal device 100 is typically a personal computer, but may also be a tablet terminal, a smartphone, or the like. In the terminal device 100, the display unit 122 and the operation unit 121 may be integrated into one unit to form the operation display unit 120. Typically, when the terminal device 100 is a smartphone, a tablet, or the like, it is a touch panel, and this operation display unit 120 is employed.

[0023] The terminal device 100 includes a user terminal 100a used by a user such as an operator, and a management terminal 100b used by an administrator. One or more of each of the user terminal 100a and the management terminal 100b may be provided.

[0024] As shown in FIG. 1, the terminal device 100 may have a terminal memory unit (memory unit) 190 that stores a first key (first key information) K1, and a read / write unit 160 that reads the first key K1, creates a second key using the first key K1 and creation information, and records encrypted transaction information using the second key in a blockchain (see FIGS. 1 and 4). The first key K1 has a private key (first private key) and a public key (first public key). The second key also has a private key (second private key) and a public key (second public key). The first private key may be encrypted and stored in the terminal memory unit 190. The first private key may be decrypted only by the read / write unit 160 of the terminal device 100. The read / write unit 160 may then create a second key using the decrypted first private key. The encrypted first private key may be stored in the CPU / TPM / BIOS / EC, etc. The function of the read / write unit 160 may be implemented by executing a predetermined program. 3 shows an example in which the reading and recording unit 160 links the encrypted first private key, first public key, and device information (Machine ID) with application 1 and application 2, and writes the information to the blockchain. The first public key may be in plain text.

[0025] (1) When encrypting the first private key, a common key encryption algorithm may be used. For example, prepare 1. "jasmyblockchainpc1" <passphrase #1> and 2. "1cpniahckcolbymsaj" <passphrase #2>. (2) Next, generate a key for encryption. For example, prepare <passphrase #1>. Hash the query #1 with SHA-256<CK#1:256bit> Generate and enter <passphrase #2> Hash it with "SHA-256"<CK#2:256bit> The key length is 2 using SHA-256. The length of the two keys may be different by using different hash functions such as RIPEMD-160, etc. (3) Then, the two generated keys are used for encryption using Triple DES (DES-EDE2) or other encryption methods. It is also possible to encrypt in two stages by combining algorithms. By using a symmetric key encryption algorithm, it is possible to encrypt a bit string of any length. Note that the passphrase can be any string of characters, as it is only used to hash and generate two keys.

[0026] In a blockchain, transactions are recorded by linking blocks, which are collections of transactions (transaction information), in a chain. Transaction information may be hashed and written to the blockchain, for example using the above-mentioned SHA-256 (Secure Hash Algorithm 256-bit). Writing to the blockchain makes it impossible to tamper with and also makes it tamper-resistant. If you want to use a blockchain to create an electronic signature (digital signature), you can simply record the original data, the data obtained by hashing the original data and encrypting it using a private key, and the public key corresponding to the private key in the blockchain. When reading the blockchain, By verifying that the data hashed from the original data matches the data decrypted using the public key, it is possible to verify that the person who recorded the data is the person who signed it.

[0027] Any of the public, consortium, and private types of blockchains may be used. When a public type is used, mining is performed. On the other hand, when a consortium type is used, mining is not performed and consensus is reached by consensus between specific parties. When a private type is used, mining is also not performed and consensus is reached by approval within the organization. Note that when a consortium type is used, although there is an administrator for the blockchain, it is advantageous in that it is not centralized. When a consortium type is used, for example, Hyperledger Fabric may be used.

[0028] The first key K1 may be associated with the terminal device 100, or may be installed (pre-installed) during manufacturing at a factory, for example. When such an embodiment is adopted, a log from the moment the terminal device 100 is turned on can be written to the blockchain. When pre-installed, device information such as a Machine ID is stored in the terminal storage unit 190, and general-purpose software or predetermined designated software may also be pre-installed and stored in the terminal storage unit 190. When the first key K1 is associated with the terminal device 100, the first key K1 may be associated with device information such as a Machine ID. The general-purpose software or designated software may be installed after the terminal device 100 is purchased.

[0029] When recording in the blockchain, the second private key or the second public key may be used. However, if the second private key is used to record in the blockchain, the content can be externally confirmed, so for information that should not be externally confirmed, the reading and recording unit 160 may record in the blockchain using the second public key.

[0030] When a second key is created using the first key K1 and the creation information and then recorded to the blockchain using the second key, a unique second key can be used to record information to the blockchain. Therefore, even when the same terminal device is used, different creation information can be used to record information to the blockchain using different second keys. The creation information may include terminal identification information such as device information. The second key (second key information) may be generated by applying the first key (first key information) K1 and the creation information to a predetermined formula having predetermined variables. The predetermined variables and the predetermined formula may be managed by the same administrator, but the first administrator managing the predetermined variables and the second administrator managing the predetermined formula may be different persons. Adopting such an embodiment can further enhance security. Furthermore, even when such an embodiment is adopted, the predetermined formula having predetermined variables can be restored with the cooperation of the first administrator and the second administrator. Therefore, even if transaction information is encrypted using a second public key, the first private key can be restored and the transaction information can be ascertained using the first key K1 and the predetermined formula having the predetermined variables. As an example, suppose that the management terminal 100b creates a second key using the first key K1 and creation information, and the user terminal 100a records the second key to the blockchain using the second public key of the second key, and the management terminal 100b breaks down for some reason, making the second private key unusable. Even in such a case, the second private key can be restored using the first key K1 and a predetermined formula containing these predetermined variables, and the information that the user terminal 100a recorded to the blockchain can be decrypted using the second public key.

[0031] Furthermore, the read / write unit 160 writes the log of the user terminal 100a to the blockchain, so that the administrator can check the log. Conventionally, the log of the terminal device 100 is stored within the terminal device 100, but the log of the terminal device 100 can be stored in the blockchain. By writing the log to the terminal device 100, for example, an administrator can externally check the log of the terminal device 100. When the reading and recording unit 160 records to the blockchain using the second public key, only those who have the second private key can check the contents. In this regard, by adopting a mode in which the administrator receives the second private key, in principle, only the owner of the terminal device 100 and the administrator can check the log of the terminal device 100.

[0032] For example, when a VDI (Virtual Desktop Infrastructure) is used, the administrator can check and manage the content of the work being performed on the user terminal 100a, but there is a problem that the burden on the user terminal 100a becomes heavy. On the other hand, by adopting a mode in which the user terminal 100a writes the log to the blockchain as in this mode, the burden on the user terminal 100a can be reduced.

[0033] Furthermore, when a mode of remotely controlling the user terminal 100a is adopted, there is a high risk of the terminal being hacked and controlled remotely, but by using a blockchain as in this mode, the risk of hacking can be reduced while allowing the administrator to check the logs on the terminal device 100. Such management of the user terminal 100a is beneficial when introducing remote work, which has been attracting attention recently.

[0034] The timing of writing the log data to the blockchain by the read / write unit 160 may be set to a predetermined timing. For example, the terminal device 100 may be intentionally set off-chain, and information such as logs may be written to the blockchain at a predetermined timing, such as when a predetermined time has elapsed or when logging out of a certain software. Furthermore, even in an environment without an Internet connection, the read / write unit 160 may record information to be written to the blockchain, and the terminal storage unit (storage unit) 190 may store the information. When the terminal device 100 is connected to the Internet, the read / write unit 160 may read the information stored in the terminal storage unit 190 and record it in the blockchain. Furthermore, the logs written to the blockchain by the read / write unit 160 may be all logs, or only logs that meet predetermined requirements (see FIG. 8). Information such as logs may be transmitted from the terminal device 100 to an information processing device 300 including a cloud, and the information processing device 300 may write the information such as logs to the blockchain. The information processing device 300 may have a device control unit 310 that controls the information processing device 300, and a device storage unit 390 that stores various information including information to be written to a blockchain (see FIG. 1).

[0035] The terminal storage unit 190 may store multiple pieces of software. The software may include designated software and general-purpose software. The reading and recording unit 160 may create multiple second-type keys K2 using creation information different from the first key K1. Changing the content of the creation information results in different types of second-type keys K2. The creation information may include information about the designated software. In this case, a second-type key K2 associated with the designated software is created using the first key K1 and the information about the designated software. The information about the designated software used as creation information may be a designated software key (designated software key information) associated with the designated software. This designated software key may be provided by an administrator or the like. When creating a second-type key K2 associated with a designated software or recording information about a certain designated software, the reading and recording unit 160 records the information in the blockchain using the second-type key K2 associated with the certain designated software. For example, when designated software A is used in the terminal device 100, processing information such as log information is recorded using a second-type key K2a dedicated to the designated software A, created from the first key K1 specific to the terminal device (see FIG. 4). In addition, when the terminal device 100 uses the designated software B, processing information such as log information is recorded using a second type of key K2b dedicated to the designated software B, which is created from the first key K1 specific to the terminal device. The second type of key K2 also has a private key (second type of private key) and a public key (second type of public key). The creation information may include predetermined information about the designated software (e.g., details about the type of information). For example, even when the same designated software is used, different second type keys K2 may be created depending on the type of information. In this case, the first key K1 and the predetermined information about the designated software are used to create a second type of key K2 associated with the predetermined information about the designated software. The reading and recording unit 160 may also record information about the designated software for one or more predetermined blockchains. For example, as described above, when different second type keys K2 are created depending on the type of information even when the same designated software is used, the information may be recorded in different blockchains depending on the type of information. In this case, the information may be written to the blockchain for each unit such as an application or library, but this is not limited to this. The information may be subdivided into functional units and written to the blockchain in a distributed manner.

[0036] When adopting a mode in which the reading and recording unit 160 records information in the blockchain using a different second type key K2 for each designated software, information can be recorded in the blockchain using a different second type key K2 for each designated software. Therefore, information can be recorded separately for each designated software. When adopting a mode in which information is recorded in the blockchain using a second type public key, the second type private key may be transmitted to an administrator, for example. In this case, the administrator can use the second type private key to confirm the information recorded in the blockchain using the second type public key. On the other hand, third parties other than the user and the administrator cannot confirm the information recorded in the blockchain using the second type public key, thereby maintaining confidentiality.

[0037] The reading and recording unit 160 may record information in the same blockchain (see FIG. 4), or may record information in a different blockchain for each designated software (see FIG. 5). In the example described above, when designated software A is used in the terminal device 100, processing information such as log information is recorded in the specific blockchain A corresponding to the designated software A using a second type of key K2a dedicated to the designated software A created from the first key K1 unique to the terminal device. Also, when designated software B is used in the terminal device 100, processing information such as log information is recorded in the specific blockchain B corresponding to the designated software B using a second type of key K2b dedicated to the designated software B created from the first key K1 unique to the terminal device.

[0038] When adopting this mode of recording information in a different blockchain for each designated software, a consolidated blockchain is created for each designated software, making it easier to manage logs, etc. for each designated software. At the same time, since it is necessary to refer to records in different blockchains to compare logs, etc. for different designated software, this is beneficial from the perspective of security and privacy management.

[0039] When recording information about general-purpose software such as Windows (registered trademark), The reading and recording unit 160 may use the first key K1 to record information in the blockchain (see Figures 4 and 5). In this case, either the first secret key or the first public key may be used. However, if information is encrypted with the first secret key and then recorded in the blockchain, the content can be externally verified. Therefore, for information that should not be externally verified, the reading and recording unit 160 may encrypt it with the first public key before recording it in the blockchain. In this case, by adopting a mode in which the administrator receives the first secret key of the user terminal 100a, the administrator can verify the information recorded in the blockchain. When the reading and recording unit 160 records information in the blockchain, the information may be encrypted using a public key provided by the administrator. In this case, only the administrator has access to the private key. The public key provided by the administrator may be the first public key in the management terminal 100b, or may be a second key generated in the management terminal 100b from the first key and creation information, or may be a key different from these.

[0040] The general-purpose software may include a plurality of types of software, and the first key K1 may be used regardless of which type of software is used as long as it is included in the general-purpose software.

[0041] The present invention is not limited to the above-described embodiment, and the second key or second type of key K2 may also be used when recording information about general-purpose software. In this embodiment, the second key or second type of key K2 is mainly described as being generated from the first key and creation information, but the present invention is not limited to this embodiment, and the second key or second type of key K2 may be provided by a third party (especially a trusted third party).

[0042] The creation information may include user identification information such as an employee ID number. In this case, even if the same terminal device 100 is used, a different second type key K2 will be created if the user is different. Therefore, even if the operator using the terminal device 100 is changed, information such as logs can be written to the blockchain as belonging to a different user.

[0043] When information about designated software for a specific user is written to the blockchain using a specific private key, such as a private key held by an administrator (administrator private key), the read / write unit 160 of the user terminal 100a managed or owned by the specific user may read information about the designated software using a specific public key, such as an administrator public key, and the terminal control unit 110 may operate the designated software in accordance with the information. More specifically, when a command (instruction) for the specific user terminal 100a encrypted with a specific private key, such as an administrator private key, is written to the blockchain, the read / write unit 160 of the specific user terminal 100a may decrypt the command using a specific public key, such as an administrator public key, and the terminal control unit 110 of the specific user terminal 100a may control the specific user terminal 100a in accordance with the command. By adopting such an embodiment, the administrator can issue commands to the terminal device 100 from outside, and the user terminal 100a can be operated from outside only according to commands from the administrator. Note that the aforementioned electronic signature may be used to verify that the command is from the administrator. An external command may be accepted only when the read / write unit 160 can verify that the command is from a genuine administrator using an electronic signature.

[0044] In this manner, when information about the designated software is read using a predetermined public key corresponding to a predetermined private key and operations are performed on the designated software according to the information, the terminal device 100, which is typically a user terminal 100a, can be controlled from the outside according to information such as commands from a predetermined third party such as an administrator. Furthermore, since commands from the outside are received according to information written in the blockchain using the predetermined private key, commands from the outside can be received safely.

[0045] In addition, the time during which the designated software (designated application) can be used may be predetermined (for example, from 9:00 AM to 5:00 PM), and information such as logs when the designated software is used may only be written to the blockchain during that time. When such an embodiment is adopted, information such as logs is written to the blockchain only at predetermined times such as working hours, but it is possible to prevent information such as logs from being written to the blockchain at other times, thereby protecting the user's privacy. The use of the user device 100a for private use and the use of the user device 100a for business purposes can be distinguished.

[0046] Recording to the blockchain by the reading and recording unit 160 and reading from the blockchain by the reading and recording unit 160 may be performed using a predetermined drive (for example, D drive, F drive, etc.).

[0047] If the transaction information recorded on the blockchain includes information linked to the administrator, such as the administrator's public key, information related to the administrator can be collected on the blockchain, allowing the administrator to compile information related to themselves. Furthermore, if the transaction information recorded on the blockchain includes information pointing to designated software, information related to the designated software can be collected on the blockchain, allowing the administrator to compile information related to the designated software they manage. Furthermore, if the transaction information recorded on the blockchain includes information pointing to a user, the administrator can compile information related to a specific user. Furthermore, if the transaction information recorded on the blockchain includes terminal identification information, such as device information, the administrator can compile information related to a specific terminal device 100. Even if the transaction information recorded on the blockchain includes a different specific blockchain for each designated software and a general-purpose software, compiles appropriate information, such as terminal identification information, to understand the series of logs for the target terminal device 100.

[0048] Processing information such as logs for the designated software may be recorded on the blockchain only when the designated software is running. If such an embodiment is adopted, processing information such as logs will be recorded on the blockchain only when the designated software is being operated. On the other hand, when software other than the designated software is being used, processing information such as logs will not be recorded on the blockchain. For example, if the designated software is business software, processing information such as logs will be recorded on the blockchain when the designated software is being used for business purposes, but processing information such as logs will not be recorded when the terminal device 100 is used for other purposes. As a result, it is possible to manage the user's operation of the terminal device 100 when the designated business software is being used, while at the same time protecting the user's privacy.

[0049] As described above, one example of a manner in which writing to a blockchain from an external management terminal 100b enables operation with software corresponding to that blockchain is when writing to a specific blockchain from an external management terminal 100b enables operation of the user terminal 100a with designated software corresponding to that specific blockchain. Similarly, writing to a general-purpose blockchain from an external source may enable operation of the user terminal 100a with general-purpose software corresponding to that general-purpose blockchain.

[0050] As an example, when using the camera function of the user terminal 100a with the specified software A, it is possible to disable the camera function on the user terminal 100a or, conversely, activate the camera function by specifying the user terminal 100a from the external management terminal 100b and writing to the specific blockchain C corresponding to the specified software A.

[0051] When an external management terminal 100b writes data to the blockchain, the blockchain can be operated using software that supports the blockchain. This can prevent mistakes by users (e.g., operators) using the user terminal 100a. According to this embodiment, for example, data encryption and access restrictions can be performed by accessing from an external management terminal 100b. Even if data is accidentally deleted, a record remains in the blockchain, so the data can be restored, for example, from the management terminal 100b using the remaining record. Furthermore, if a record remains in the blockchain of a copy or the like, it is possible to write from outside to delete the copy. Furthermore, if confidential information is recorded in a location where it should not be recorded, the user terminal 100a can be operated from outside to delete the information.

[0052] In this manner, if a legitimate administrator can externally operate the user terminal 100a, for example, when an operator resigns, the deletion of business-related data and the uninstallation of business-related applications can be written to the blockchain from the external management terminal 100b. Therefore, tasks such as deleting business-related data and uninstalling business-related applications can be easily performed externally. This eliminates the need for the resigning employee to bring their terminal device to their workplace and request the uninstallation of specific software or data from their terminal device upon resignation. In this case, processing information such as logs may be retained in the blockchain. Furthermore, if a manner is adopted in which uninstallation information is written to the blockchain, the fact that the software has been uninstalled is recorded in the blockchain, allowing the uninstallation to be confirmed later.

[0053] If the read / write unit 160 writes a log related to the designated software to the blockchain while the user terminal 100a is using the designated software, the terminal log written to the blockchain can be viewed from the management terminal 100b. For example, the management terminal 100b may be configured to display various statuses of multiple user terminals 100a, such as whether the terminals are in use, who last used them, offline, or in sleep mode. Detailed information about each user terminal 100a may also be viewed from the management terminal 100b. For example, tapping "PC001" on the operation display unit 120 of the management terminal 100b in FIG. 6 may display detailed status information for "PC001" as shown in FIG. 7. The detailed status information for "PC001" may include the operating status of the user terminal 100a, such as the date and time when the camera shutdown command was received and successfully completed, the date and time when the microphone shutdown command was received and successfully completed, and the date and time when the speaker shutdown command was received and successfully completed. In addition, the login date and time, logout date and time, sleep date and time, etc. of a specified application on the user terminal 100a may be displayed. The user terminal 100a may display a screen such as that shown in Fig. 8. The user terminal 100a may be configured to be able to check all system logs, carefully selected system logs, system logs recorded in the blockchain, and the history of commands obtained from the management terminal 100b.

[0054] As shown in FIG. 9, various functions of each user terminal 100a, such as the web camera, microphone, speaker, USB, and window, may be controlled to be turned on or off by writing a command (a command encrypted with a private key) from the management terminal 100b to the blockchain. The aspect shown in FIG. 9 is advantageous in that various functions can be easily turned on or off by tapping a predetermined button on the operation display unit 120 of the management terminal 100b. In FIG. 9, if an instruction to turn off the web camera of the user terminal 100a is input, an image such as that shown in FIG. 10 is displayed on the operation display unit 120 of the management terminal 100b, as an example. When a command is input in this way, the command history is updated by obtaining it from the management terminal 100b (see FIG. 11).

[0055] If the user terminal 100a has not been in operation for a predetermined period or more, or if there is a block in the terminal storage unit 190, When the amount of information to be written to the blockchain exceeds a predetermined capacity, the terminal control unit 110 may impose an operational restriction on the terminal device 100. To lift the operational restriction, the terminal device 100 may request a connection to the Internet, receive a predetermined password via the Internet, and enter the password to lift the operational restriction. The operational restriction may also be such that login to the terminal control unit 110 is not permitted. In this case, login may be permitted only with permission from an administrator. For example, the administrator may write a predetermined command to the blockchain, causing the terminal device 100 to read the blockchain and thereby permit login to the terminal control unit 110. This configuration can prevent a situation in which the user terminal 100a is not connected to the Internet for a long period of time and thus does not write information such as logs. Even if such a situation occurs, the operational restriction can be lifted by the administrator's control, thereby appropriately addressing problems that may arise when the user terminal 100a, which has not been connected to the Internet for a long period of time, reconnects to the Internet.

[0056] The management terminal 100b may be provided with a monitoring unit 180 that monitors the operation of the terminal device 100 (see FIG. 1). The terminal control unit 110 of the management terminal 100b may control the monitoring unit 180 to impose operational restrictions if the terminal device 100 does not operate for a predetermined period of time or longer. Such a monitoring unit 180 may be provided in an information processing device 300 such as a server, rather than in the management terminal 100b. In this case, the device control unit 310 may receive information from the monitoring unit 380 and control the user terminal 100a.

[0057] The terminal control unit 110 or the device control unit 310 of the management terminal 100b may perform control so as not to allow the terminal device 100 to log in if it has not been activated for a predetermined period of time or more.

[0058] Next, an example of an aspect using the terminal device 100 of this embodiment will be described. In the following aspect, an aspect in which a log is recorded in a specific blockchain A will be described, but this is not limited to this, and a log may be recorded in one blockchain.

[0059] When the terminal device 100 is started up and the designated software A is driven, the second type key K2 corresponding to the designated software A, which is created using the first key K1 unique to the terminal device 100 and the creation information, is read by the read-out / recording unit 160. Then, information such as logs obtained while the designated software A is being used is encrypted using the second type key K2 and written to the unique block chain A. For example, the read-out / recording unit 160 writes to the unique block chain A that at this point in time there is nothing plugged into the USB (USB OFF) and the web camera is not running (WEB camera OFF) (see S1 in FIG. 12).

[0060] If the online conference is scheduled to start at 10:30, the reading and recording unit 160 will write to the unique blockchain A just before that that the web camera and microphone will be turned on (web camera ON and microphone ON) (see S2 in Figure 12).

[0061] When the webcam and screen are turned off at 12 o'clock, which is the break time, the fact that the webcam and screen have been turned off is written to the specific blockchain A (see S3 in FIG. 12). At this time, the management terminal writes to the specific blockchain A for the target user terminal 100a, and a command to turn off the webcam and screen is entered, forcing the terminal device 100 to become unusable.

[0062] When the screen is turned off at 3 p.m. to take a short break, the fact that the screen has been turned off is written to the unique blockchain A (see S4 in Figure 12).

[0063] When the operating hours end at 5:00 PM and the operation of designated software A is stopped, writing to the unique blockchain A is terminated (see S5 in FIG. 12). If writing to the unique blockchain A is performed only when designated software A is being used, and if other software is being used, writing to the blockchain to obtain processing information such as logs is not performed, writing to the blockchain for the day will be terminated at this point, and from then on, even if the terminal device 100 is used, processing information such as logs will not be recorded. As a result, it is possible to protect the user's privacy.

[0064] In the above example, when general-purpose software is used, processing information such as logs when the general-purpose software is used may be recorded in a general-purpose blockchain. Also, when designated software other than designated software A is used, processing information such as logs may be recorded in a specific blockchain corresponding to each designated software. Also, unlike this embodiment, information such as logs when the general-purpose software is used and logs when designated software other than designated software A is used may be recorded in the same blockchain that records information such as logs when designated software A is used.

[0065] As another example, automatic login and logout may be possible. For example, when a user who has a pre-registered predetermined mobile terminal (such as a smartphone) comes close to the user terminal 100a, the user is notified of this by a proximity communication means such as Bluetooth (registered trademark). The user terminal 100a may detect this and automatically log in. On the other hand, if a predetermined mobile terminal (such as a smartphone) is separated from the user terminal 100a, the user may be automatically logged out.

[0066] The record in the blockchain from login to logout may adopt the form shown in FIG. 13, and may include terminal identification information such as Machine ID, user identification information such as User ID, Login information including date and time information such as IP address, GPS, and time stamp, and information about the application used such as the application path, may each be encrypted with a predetermined key such as a first key or a second key and recorded on the blockchain. Note that while the example shows a mode in which the information is recorded every three minutes after login, this is merely an example, and information such as logs may be recorded on the blockchain at various intervals or with various triggers.

[0067] When an administrator issues a command, the mode shown in Fig. 14 can also be adopted. In this mode, information such as management terminal identification information such as the Machine ID of the management terminal 100b, user terminal identification information such as the Machine ID of a specific user terminal 100a, the command, issuance time, and signature is encrypted from the management terminal 100b using public keys such as the first public key, second public key, and second type public key of the user terminal 100a, and is recorded in the blockchain.

[0068] When recording to the blockchain is performed in this manner, the read / write unit 160 of the specified user terminal 100a in question reads the information written to the blockchain, decrypts it with the private key corresponding to the public key, checks the signature and management terminal identification information to confirm whether it is an instruction from a legitimate administrator, checks the user terminal identification information to confirm whether it is a command intended for itself, and if these confirmations are successful, the specified command may be executed by the terminal control unit 110. In this case, the command execution result is not returned to the management terminal 100b, but a log may be recorded in the blockchain.

[0069] Unlike Fig. 14, when an administrator issues a command, it is also possible to adopt a mode as shown in Fig. 15. In this mode, management terminal identification information such as the Machine ID of the management terminal 100b and user terminal identification information such as the Machine ID of a predetermined user terminal 100a are transmitted from the management terminal 100b. Other information, commands, issuance time, signatures, and other information are encrypted using the private key of the management terminal 100b and the private key of the user terminal 100a (first private key, second private key, second type private key, etc.) and recorded in the blockchain.

[0070] When recording to the blockchain is performed in this manner, the read / write unit 160 of the specified user terminal 100a in question reads the information written to the blockchain, decrypts it with the public key corresponding to the private key, checks the signature and management terminal identification information to confirm whether it is an instruction from a legitimate administrator, checks the user terminal identification information to confirm whether it is a command intended for itself, and if these confirmations are successful, the specified command may be executed by the terminal control unit 110. In this case, the command execution result is not returned to the management terminal 100b, but a log may be recorded in the blockchain.

[0071] Each component including the read / write unit 160, the terminal control unit 110, etc. in each of the above embodiments may be realized by a logic circuit (hardware) formed in an integrated circuit such as an IC chip or an LSI, or a dedicated circuit, or may be realized by software using a CPU, memory, etc. Furthermore, each component may be realized by one or more integrated circuits, or multiple components may be realized by one integrated circuit.

[0072] The above-mentioned description of each embodiment and the disclosure of the drawings are merely examples for explaining the invention described in the claims, and the above-mentioned description of the embodiment or the disclosure of the drawings does not limit the invention described in the claims. [Explanation of symbols]

[0073] 100 Terminal Device 110 Terminal control unit (control unit) 160 Read / record unit 190 Terminal memory unit (memory unit) 300 Information processing device

Claims

1. A terminal device different from the server, a storage unit that stores a first key and a plurality of designated software programs; a read / write unit that creates a plurality of second-type keys using creation information different from the first key, encrypts information directly generated by a certain designated software while the certain designated software is being used using the second-type keys created using creation information including predetermined information about the certain designated software, stores the encrypted information in a block, and records the block in the blockchain; A terminal device comprising:

2. 2. The terminal device according to claim 1, wherein information directly generated by the specified software while the specified software is being used is hashed and stored in a block.

3. A program installed on a terminal device different from the server, The terminal device a function of storing a first key and a plurality of designated software; a function of creating a plurality of second-type keys using creation information different from the first key, encrypting information directly generated by a certain designated software while the certain designated software is being used using the second-type keys created using creation information including predetermined information of the certain designated software, storing the encrypted information in a block, and recording the block in the blockchain; A program to execute.

Images