JP7178235B2 - Control method, information processing device, management system, and program - Google Patents

Description

The present invention relates to a control method, an information processing device, a management system, and a program.

A technique for managing unlocking or locking of a container in which goods are stored, such as a delivery box, using a blockchain has been disclosed (see Non-Patent Document 1). Blockchain-based smart contracts can be used to manage the unlocking of the vault.

Here, some storage units not only store articles, but also have a temperature control function. There are also container systems that have a plurality of different containers.

GMO Internet Co., Ltd., “GMO Internet Group, Saison Information Systems, and PARCO jointly conduct second demonstration experiment utilizing blockchain and IoT”, [online], June 21, 2017, [Heisei 30 Searched on October 25, 2020], Internet <URL: https://cloud.z.com/jp/news-ep/iot2/>

However, conventionally, when there is a change in the configuration of the container system, such as an increase or decrease in the number of containers provided in the container system or a change in the function of the container, the entire container system has to be stopped. There is the problem of having to Stopping the entire container system hinders continued operation of the entire container system.

Therefore, the present invention provides a control method and the like that can operate without stopping the entire container system even if the configuration of the container system is changed.

A control method according to an aspect of the present invention is a control method that uses a distributed ledger to perform unlocking control, which is control of unlocking or locking one or more containers in which goods can be stored, wherein the distributed ledger One or more second smart contracts corresponding one-to-one with the one or more containers, and a first smart contract capable of managing the one or more second smart contracts by executing the stored code by a computer. and each of the one or more second smart contracts, under the management of the first smart contract, unlocks and controls the container corresponding to the second smart contract among the one or more containers. and the first smart contract controls whether or not each of the one or more second smart contracts is subject to the management.

In addition, these general or specific aspects may be realized by a system, device, integrated circuit, computer program, or a recording medium such as a computer-readable CD-ROM. and any combination of recording media.

According to the control method and the like of the present invention, even if the configuration of the container system is changed, the entire container system can be operated without stopping.

FIG. 1 is a block diagram schematically showing the configuration of a management system according to an embodiment. FIG. 2 is a block diagram of the hardware configuration of the server according to the embodiment. FIG. 3 is a block diagram showing the functional configuration of the server according to the embodiment. FIG. 4 is a block diagram schematically showing the configuration of the storage system according to the embodiment. FIG. 5 is an explanatory diagram of usage information of the storage system according to the embodiment. FIG. 6 is an explanatory diagram showing an address table in the embodiment. FIG. 7 is an explanatory diagram of function information in the embodiment. FIG. 8 is an explanatory diagram of adding and removing containers in the container system according to the embodiment. FIG. 9 is a sequence diagram showing processing when adding a container in the container system according to the embodiment. FIG. 10 is a sequence diagram illustrating processing when removing a container in the container system according to the embodiment. FIG. 11 is a first sequence diagram showing processing when using a storage device according to the embodiment. FIG. 12 is a second sequence diagram showing processing when using a storage device in the embodiment. FIG. 13 is a block diagram schematically showing the configuration of a management system according to Modification 1 of the embodiment. 14 is a block diagram illustrating a configuration of functions of a server according to Modification 1 of the embodiment; FIG. FIG. 15 is an explanatory diagram of usage information of the storage system according to Modification 1 of the embodiment. FIG. 16 is a flow diagram showing a control method in Modification 2 of the embodiment. FIG. 17 is a block diagram showing the configuration of an information processing apparatus according to Modification 2 of the embodiment.

(Knowledge on which the present invention is based)
A control method according to an aspect of the present invention is a control method that uses a distributed ledger to perform unlocking control, which is control of unlocking or locking one or more containers in which goods can be stored, wherein the distributed ledger One or more second smart contracts corresponding one-to-one with the one or more containers, and a first smart contract capable of managing the one or more second smart contracts by executing the stored code by a computer. and each of the one or more second smart contracts, under the management of the first smart contract, unlocks and controls the container corresponding to the second smart contract among the one or more containers. and the first smart contract controls whether or not each of the one or more second smart contracts is subject to the management.

According to the above aspect, the container system is controlled by first and second smart contracts. In addition, when there is a change such as an increase or decrease in the number of containers provided in the container system, or a change in function, it is sufficient to stop the operation of the second smart contract related to the change, in other words, the first smart The contract and the behavior of the second smart contract not involved in the modification can be maintained. If the container system were to be controlled by a single smart contract, the operation of the smart contract would have to be stopped when adding more containers, which would hinder the operation of the container system. According to the control method according to one aspect of the present invention, the entire container system can be operated without stopping even if the configuration of the container system is changed.

For example, further, when the first smart contract receives a request to delete a container included in the one or more containers, the one or more second smart contracts that are the target of the deletion A second smart contract corresponding to the container may be excluded from the management target.

According to the above aspect, when the container is removed, the first smart contract excludes the second smart contract corresponding to the container to be removed from the target of management. Therefore, it is possible to maintain the operation of the first smart contract and the second smart contract that is not subject to reduction when the container is reduced. Therefore, even if there is a change in the configuration of the container system, the entire container system can be operated without stopping.

For example, further, when the first smart contract receives a request to add a new container to the one or more containers, the second smart contract corresponding to the new container is set as the object of management. may be added.

According to the above aspect, when adding a container, the first smart contract adds the second smart contract corresponding to the container to be added to the target of management. Therefore, the operation of the first smart contract and the already operating second smart contract can be maintained when the storage is expanded. Therefore, even if there is a change in the configuration of the container system, the entire container system can be operated without stopping.

For example, further, when the first smart contract receives an inquiry as to whether the one or more containers are being used, it generates response information to the inquiry and transmits the generated response information. may

According to the above aspect, the first smart contract provides the response information to the inquiry about usage of the storage. Therefore, even if there is a change in the configuration of the container system, it is possible to respond to inquiries regarding the use of the container.

For example, the first smart contract further manages usage information indicating whether or not the one or more containers are being used, and whether or not one of the one or more containers is being used. When receiving a request, referring to the usage information, (a) rejecting the request if the one storage is in use, and (b) rejecting the request if the one storage is in use. If not, the request may be granted.

According to the above aspect, the storage can be managed so as to permit use of the storage when the storage is not in use. This makes it possible to avoid inconveniences such as multiple users using the container.

For example, if the one storage in (b) is not in use, the request may be granted only when billing for the use has been completed.

According to the above aspect, it is possible to manage so that the storage can be used only when the billing process for the usage of the storage is completed.

For example, further, when the first smart contract receives an inquiry about a function possessed by one of the one or more storages, the storage of the one of the one or more second smart contracts The inquiry may be forwarded to a second smart contract corresponding to the device, and answer information obtained from the one second smart contract may be sent as an answer to the inquiry.

According to the above aspect, when an inquiry is made about the function of each container, the inquiry is made to correspond to the smart contract corresponding to the container that is the object of the inquiry. Information different for each container is managed by the second smart contract corresponding to the container, thereby minimizing addition of functions to the first smart contract. Therefore, even if there is a change in the configuration of the container system, the entire container system can be operated without stopping.

For example, when the first smart contract newly manages the second smart contract, the address of the second smart contract is additionally stored in the memory of the computer running the first smart contract. , if the first smart contract excludes the second smart contract from being managed, the address of the second smart contract may be deleted from the memory of the computer running the first smart contract.

According to the above aspect, whether or not the second smart contract is to be managed is controlled based on whether or not the computer stores the address of the second smart contract in the memory. Therefore, it is possible to more easily construct a configuration that can be operated without stopping the entire container system even if the configuration of the container system is changed.

For example, operating the first smart contract includes operating one or more of the first smart contracts, and further operating a third smart contract capable of managing one or more of the first smart contracts. , the third smart contract may control whether or not each of the one or more first smart contracts is subject to the management.

According to the above aspect, the container system is controlled by first, second and third smart contracts. In addition, when there is a change such as addition, reduction, or function change of the container provided in the container system, it is only necessary to stop the operation of the second smart contract related to the change, in other words, the first and The operation of the third smart contract and the second smart contract not involved in the modification can be maintained. Furthermore, since the third smart contract controls whether or not the first smart contract is subject to management, it is possible to more easily control a plurality of first smart contracts.

Further, an information processing device according to an aspect of the present invention is a plurality of information processing devices that perform unlocking control, which is control of unlocking or locking one or more storage containers in which articles can be stored, using a distributed ledger. An information processing device among them, comprising a processor, a memory, and a storage device in which the distributed ledger in which code is stored is stored, the processor stores the code stored in the distributed ledger in the By executing using a memory, operates one or more second smart contracts corresponding one-to-one with the one or more storages, and a first smart contract capable of managing the one or more second smart contracts each of the one or more second smart contracts, under the management of the first smart contract, controls unlocking of the one or more containers corresponding to the second smart contract; The first smart contract controls whether each of the one or more second smart contracts is subject to the management.

This provides the same effect as the control method described above.

Further, a management system according to an aspect of the present invention includes: the plurality of information processing devices including the above information processing device; and the above container.

This provides the same effect as the control method described above.

A program according to an aspect of the present invention is a program for causing a computer to execute the above control method.

This provides the same effect as the control method described above.

In addition, these general or specific aspects may be realized by a system, device, integrated circuit, computer program, or a recording medium such as a computer-readable CD-ROM. Or it may be realized by any combination of recording media.

Hereinafter, embodiments will be specifically described with reference to the drawings.

It should be noted that the embodiments described below are all comprehensive or specific examples. Numerical values, shapes, materials, components, arrangement positions and connection forms of components, steps, order of steps, and the like shown in the following embodiments are examples and are not intended to limit the present invention. In addition, among the constituent elements in the following embodiments, constituent elements that are not described in independent claims representing the highest concept will be described as arbitrary constituent elements.

(Embodiment)
In this embodiment, a control method that can operate without stopping the entire container system even if the configuration of the container system is changed will be described. The control method according to the present embodiment is a control method that uses a distributed ledger to perform unlocking control, which is control of unlocking or locking one or more storage containers in which articles can be stored. The container is, for example, a delivery box or coin locker.

FIG. 1 is a block diagram showing the configuration of a management system 1 according to this embodiment.

As shown in FIG. 1, the management system 1 includes servers 10A, 10B, . The servers 10A, 10B, . . . , 10E are also called "servers 10A, etc.", and each of the servers 10A, etc. is also called "server 10".

The management system 1 is a system that manages the unlocking of the storage container 31 when the user U1 hands over the article 5 to the user U2 using the storage container 31 . For example, the case where the container 31 is a home delivery box and the management system 1 manages the unlocking of one or more home delivery boxes will be described. For example, when the recipient receives the article 5 via a home delivery company, user U1 corresponds to the home delivery company and user U2 corresponds to the recipient.

Each of the servers 10A and the like is a server device that is an information processing device that manages unlocking or locking of the container 31 of the container system 30 by a distributed ledger on a computer. Each of the servers 10A, etc., has a ledger for managing unlocking or locking. is updated. Distributed ledgers have the advantage that it is difficult to falsify recorded information. A distributed ledger can be realized by known technologies such as blockchain, IOTA, or hash graph.

The ledger held by the server 10A or the like contains information indicating whether the container 31 is unlocked or locked, and a contract, which is a program code for managing the container 31. code is stored. The server 10A or the like manages unlocking or locking of the container 31 by a smart contract, which is a function that operates by executing contract code. The server 10A and the like are connected to the terminals 21 and 22 and the storage system 30 via the network N so as to be communicable. The servers 10A and the like are connected by a network M so as to be able to communicate with each other. Note that the network M may be connected to the network N, or may be the network N.

The management device 20 is a device that manages the storage system 30 and the storage 31 using a computer. The management device 20 updates the ledger managed by the server 10A or the like at the time of addition or reduction. The management device 20 updates the information in the ledger, for example, based on the operation by the manager of the storage system 30 .

The terminals 21 and 22 are information processing terminals that receive an operation for unlocking or locking the container 31 from the user and transmit information related to the operation to the server 10A or the like. Here, it is assumed that the terminal 21 is the terminal owned by the user U1 who gives the item 5, and the terminal 22 is the terminal owned by the user U2 who receives the item 5. FIG. The terminals 21 and 22 are smart phones, personal computers, and the like.

A container system 30 is a system comprising one or more containers 31 . Each of the one or more containers 31 included in the container system 30 is a temporary storage location for the item 5 used when the item 5 is passed from the user U1 to the user U2. It is assumed that the number of persons authorized to unlock the container 31 at one time is limited to a predetermined number. The predetermined number of people is, for example, one, and this case will be described as an example, but the predetermined number of people is not limited to one.

The container 31 has at least a storage chamber for storing the article 5 . The container 31 may further have a temperature control function to adjust the temperature of the containment room, or produce a production effect such as outputting sound, light, smell, or smoke when unlocking or locking. may have functions. Control of unlocking or locking of the container 31, control of the temperature adjustment function, and control of the performance function are performed by a smart contract that operates on the server 10A or the like.

The storage device 31 is unlocked based on the operation by the user U1, and is locked after the article 5 is stored by the user U1. After that, it is unlocked based on the operation by the user U2, and the article 5 is carried out by the user U2.

FIG. 2 is a block diagram showing the hardware configuration of server 10 in this embodiment. FIG. 3 is a block diagram showing the functional configuration of the server 10 according to this embodiment. Here, the server 10 corresponds to each of the servers 10A and the like shown in FIG.

As shown in FIG. 2 , server 10 includes processor 11 , memory 12 , communication unit 13 , and ledger storage unit 14 .

The processor 11 is a processor that uses the memory 12 to execute a program. The processor 11 operates the smart contracts S1 and S2 by executing the contract codes C1 and C2 stored in the ledger storage unit 14 (see FIG. 3). The processor 11 also implements other functions of the server 10 by executing predetermined programs.

Memory 12 is a work area used when processor 11 executes a program.

The communication unit 13 is a communication interface device that is communicably connected to another device. The communication unit 13 is directly or indirectly connected to the networks N and M, and can communicate with other servers 10, terminals 21 and 22, and the storage system 30 via the networks N and M.

The ledger storage unit 14 is a storage device that stores a ledger for managing unlocking or locking of the container 31 . The ledger storage unit 14 is implemented by an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like.

The ledger storage unit 14 stores unlock history 15 and contract codes C1 and C2. The unlocking history 15 is the history of unlocking and locking of the container 31 and the history of the owner of the key. Contract codes C1 and C2 are program codes for operating smart contracts S1 and S2, respectively.

Next, functions of the server 10 will be described.

As shown in FIG. 3, the server 10 includes a synchronizer 17, a smart contract S1, and a smart contract S2. The server 10 operates one smart contract S1 capable of managing one or more smart contracts S2, and also operates the smart contract S2 corresponding to the storage 31 one-to-one. In other words, the server 10 controls the container system 30 with smart contracts S1 and S2 arranged in a hierarchy.

The synchronization unit 17 is a processing unit that synchronizes the ledger storage unit 14 between the servers 10 . Synchronization unit 17 can be implemented by processor 11 executing a predetermined program.

The synchronization unit 17 attempts to reach a consensus with the other servers 10 on the information to be stored in the ledger storage unit 14 based on a consensus algorithm at predetermined time intervals. Then, the synchronization unit 17 stores new information in the ledger storage unit 14 when consensus building is successful. Conventionally proposed consensus algorithms such as POW (Proof Of Work), POS (Proof Of Stake), and PBFT (Practical Byzantine Fault Tolerance) can be applied.

The smart contract S<b>1 includes a system management section 101 , an individual control section 103 and a reception section 105 . The smart contract S1 manages the entire container system 30, and is expected to continue operating even when the number of containers 31 is increased or decreased. The smart contract S1 controls whether or not to manage one or more smart contracts S2. Smart contract S1 corresponds to the first smart contract.

The system management unit 101 manages attribute information such as identification information and location of the container system 30, and usage information 102 indicating whether each container 31 included in the container system 30 is being used. When the system management unit 101 receives an inquiry about the attribute information and the usage information 102 of the container system 30 from the terminal 21 or the like, the system management unit 101 generates reply information based on the managed attribute information and the usage information 102. , to the terminal 21 or the like. Further, the system management unit 101 receives a request to use each storage device 31 from the terminal 21 or the like, and updates the usage information 102 .

Specifically, when the system management unit 101 receives an inquiry from the terminal 21 as to whether the storage device 31 is being used, the system management unit 101 generates response information to the inquiry, and transmits the generated response information to the terminal 21. do. Here, when receiving a request to use the storage unit 31, the system management unit 101 refers to the usage information 102 and rejects the request if the requested storage unit 31 is being used. is not in use, the request is granted. Note that the system management unit 101 may permit the request only when the billing process for new use is completed when the requested storage device 31 is not in use.

The individual control unit 103 is a processing unit that controls whether each container 31 included in the container system 30 is to be managed. The individual control section 103 has an address table 104 on the memory 12 . The address table 104 stores the storage address of the smart contract S2 corresponding to the storage device 31 managed by the individual control unit 103 .

Specifically, when the individual control unit 103 receives a request to delete the container 31 from the management device 20, the individual control unit 103 excludes the smart contract S2 corresponding to the container 31 to be deleted from the target of management. To exclude the smart contract S2 from the management target, the address of the smart contract S2 to be deleted is deleted from the address table 104 . When the individual control unit 103 receives a request to add a new container 31 from the management device 20, the individual control unit 103 adds the smart contract S2 corresponding to the new container 31 to the management target. To add the smart contract S2 to the management target, the address table 104 additionally stores the address of the smart contract S2.

The reception unit 105 is a processing unit that receives inquiries regarding the functions of the storage units 31 . Upon receiving an inquiry about the function of each storage device 31, the reception unit 105 reads the address of the smart contract S2 corresponding to the storage device 31 in question from the address table 104, and transfers the received inquiry to the address. In addition, it transmits to the terminal 21 or the like the reply information to the inquiry, which is transmitted as a result of the transfer.

The smart contract S<b>2 includes a reception unit 111 , an unlock management unit 112 and a function management unit 115 . The smart contract S2 has a one-to-one correspondence with the storage 31, and one smart contract S2 operates for one storage 31. FIG. It is assumed that the operation is started when the storage device 31 corresponding to the smart contract S2 is added, and the operation is finished when the storage device 31 is removed. Smart contract S2 corresponds to a second smart contract.

The receiving unit 111 is a processing unit that receives inquiries regarding the function of the storage device 31 . Upon receiving the function-related inquiry information transferred from the reception unit 105 of the smart contract S<b>1 , the reception unit 111 generates reply information to the inquiry and transmits the information to the reception unit 105 . The function inquiry information is, for example, information indicating whether or not the container 31 has a refrigerating function, whether or not it has a heat retaining function, and whether or not it has an effect function such as sound.

For example, when the reception unit 111 receives an inquiry including a function ID from the terminal 21 or the like, the reception unit 111 refers to the function management unit 115 to determine whether or not the container 31 has a function related to the function ID. Generate and send reply information indicating the result. For example, the reception unit 111 generates answer information including "TRUE" if the storage device 31 has the function associated with the function ID, and "FAULSE" if the storage device 31 does not have the function. The function IDs are, for example, "1001" for the refrigerating function, "1002" for the warming function, and "1003" for the presentation function.

The unlock management unit 112 is a processing unit that manages unlocking of the container 31 corresponding to the smart contract S2. The unlock management unit 112 uses key state information 113 indicating whether the container 31 is unlocked or locked, and a person who has the authority to unlock the container 31 as a key holder. It manages the key holder information 114 shown. The key state information 113 and the key holder information 114 can be derived from the unlock history 15 stored in the ledger storage unit 14 .

When receiving a request to unlock or lock the container 31 corresponding to the smart contract S2, the unlock management unit 112 confirms the validity of the request and then receives the request to unlock or lock. is added as a history to the unlocking history 15, and the key state information 113 is updated to the unlocked state or the locked state. The key state information 113 is referred to by the unlock control unit 33 of the container 31 and reflected in the unlock control of the container 31 by the unlock control unit 33 . Therefore, it can be said that the unlocking management unit 112 controls unlocking of the container 31 via the unlocking control unit 33 .

Further, when the key owner of the storage device 31 is changed, the unlocking management unit 112 adds the history to the unlocking history 15 according to the change, and updates the key state information 113 according to the requested change. . For example, when an item 5 is handed over from user U2 to user U1, the key holder is initially user U1, and is changed to user U2 after user U1 stores item 5 in container 31. FIG.

The function management unit 115 is a processing unit that manages control of functions of the storage device 31 . The function management unit 115 individually manages the control of the refrigeration function, the heat retention function, the performance function, etc. of the container 31 based on the instruction information received from the terminal 21 or the like. Specifically, the function management unit 115 holds function information 116 indicating whether or not the container 31 is exhibiting the function for each function provided in the container 31, and instructs When the information is received, the function information 116 is updated. Note that the function management unit 115 is not an essential component.

As for the usage information, the mode in which the smart contract S1 manages the usage information of the entire container system 30 has been described. Alternatively, each of the plurality of smart contracts S2 may manage usage information for a single container, and the smart contract S1 may query each of the plurality of smart contracts S2 to collect the overall usage information.

FIG. 4 is a block diagram schematically showing the configuration of the storage system 30 according to this embodiment.

As shown in FIG. 4 , the container system 30 includes a communication section 32 , an unlock control section 33 and a function control section 34 . One unlock control unit 33 and one function control unit 34 are provided for each of the one or more containers 31 included in the container system 30 .

The communication unit 32 is a communication interface device that is communicably connected to another device. The communication unit 32 is connected to the network N and can communicate with other servers 10 via the network N. FIG.

The unlock control unit 33 is provided for each container 31 and controls whether the container 31 is unlocked or locked. The unlock control unit 33 repeatedly refers to the key state information 113 of the server 10 via the communication unit 32 and changes the key state of the container 31 so as to match the key state information 113 .

Specifically, when the key state information 113 indicates that the container 31 is unlocked, the unlock control unit 33 unlocks the container 31 if the container 31 is actually unlocked. The state is maintained, and if the container 31 is actually in the locked state, it is unlocked by unlocking it. Further, when the key state information 113 indicates that the container 31 is in the locked state, the unlock control unit 33 maintains the locked state if the container 31 is actually in the locked state, and stores the locked state. If the device 31 is actually unlocked, it is changed to a locked state by locking.

The function control unit 34 is a processing unit that controls the functions of the container 31 . If the container 31 has a refrigerating function, a heat retaining function, or a performance function, the function control unit 34 controls such function to be exhibited. Note that the function control unit 34 is not an essential component.

The function control unit 34 repeatedly refers to the function information 116 of the server 10 via the communication unit 32 in the same way that the unlocking control unit 33 refers to the key state information 113, and repeats the function information 116 so as to match the function information 116. The state is changed so that the function of the container 31 is exhibited or not exhibited.

FIG. 5 is an explanatory diagram of the usage information 102 of the storage device 31 in the management system 1 according to this embodiment.

Each entry of the usage information 102 corresponds to the storage 31 on a one-to-one basis, and includes each information of storage ID 41 and availability 42 .

The container ID 41 is an identifier that can uniquely identify the container 31 . The container ID 41 has an identifier for each of the one or more containers 31 corresponding to one or more smart contracts S2.

The usage status 42 is information indicating whether or not the storage device 31 is being used.

The usage information 102 is referenced to generate response information when the system management unit 101 receives usage inquiry information from the terminal 21 . Also, it is updated when a request for use is received from the terminal 21 or the like.

FIG. 6 is an explanatory diagram showing the address table 104 in this embodiment.

As shown in FIG. 6, the address table 104 stores address 1, address 2, . . . , address n as addresses of one or more smart contracts S2.

In the address table 104, the address of the smart contract S2 managed by the smart contract S1 is written by the individual control unit 103. FIG. The address table 104 is referred to by the reception unit 105, and is used as the address of the smart contract S2 to which the inquiry is transferred when the reception unit 105 receives a function inquiry.

FIG. 7 is an explanatory diagram of the function information 116 in this embodiment.

As shown in FIG. 7, each entry of the function information 116 corresponds to one function and includes information of function ID 44 and status 45 .

The function ID 44 is information indicating the function that the storage 31 has. For example, the function with the function ID 44 of "1001" is the refrigerating function, and the function with the function ID 44 of "1002" is the warming function.

The state 45 is information indicating whether the function associated with the entry is in the "ON" state, which is the state in which the storage unit 31 is activated, or whether it is in the "OFF" state, in which the function is not activated. .

The function information 116 shown in FIG. 7 indicates that the container 31 has a refrigerating function and a warming function. In addition, the function information 116 indicates that the refrigerating function is activated, that is, that the containment chamber is being cooled by the refrigerating function, and that the heat retaining function is not activated. ing.

Next, the processing of the management system 1 when adding or removing the container 31 will be described.

FIG. 8 is an explanatory diagram of adding and removing the storage device 31 in the storage device system 30 according to the present embodiment.

FIG. 8(a) shows a container system 30 comprising two containers 31, containers 31A and 31B. At this time, the server 10 operates smart contract S1 and smart contracts S2A and S2B respectively corresponding to the two storages 31A and 31B.

FIG. 8(b) shows a storage system 30 comprising three storages 31, storages 31A, 31B and 31C. At this time, the server 10 operates the smart contract S1 and the smart contracts S2A, S2B and S2C corresponding to the three storages 31A, 31B and 31C, respectively.

In the state of (a) of FIG. 8, if the container 31C is added, the state of (b) of FIG. 8 is obtained. Further, if the container 31C is removed from the state shown in FIG. 8(b), the state shown in FIG. 8(a) is obtained.

In the following, the processing of the management system 1 when adding or removing containers will be described.

FIG. 9 is a sequence diagram showing processing when adding a container 31 in the management system 1 according to this embodiment.

As shown in FIG. 9, when adding a storage device 31, in step S101, a new storage device 31 (for example, the storage device 31C in FIG. 8B) is physically managed in the storage system 30. installed by the

In step S<b>111 , the management device 20 transmits addition request information indicating a request for addition of the storage device 31 to the smart contract S<b>1 . The individual control unit 103 of the smart contract S1 receives the additional request information.

At step S131, the smart contract S2 starts operating. Note that if the smart contract S2 is operating from the beginning, execution of step S131 is unnecessary.

In step S<b>121 , the individual control unit 103 of the smart contract S<b>1 adds the address of the smart contract S<b>2 corresponding to the new storage 31 to the address table 104 . As a result, the smart contract S1 manages the smart contract S2 corresponding to the new container 31 .

A new container 31 is added by the series of processes shown in FIG.

FIG. 10 is a sequence diagram showing processing when removing the storage device 31 in the storage device system 30 according to the present embodiment.

As shown in FIG. 10, when the storage 31 is removed, in step S201, the storage 31 included in the storage system 30 (for example, the storage 31C in FIG. 8B) is physically be removed.

In step S211, the management device 20 transmits usage request information indicating a usage request to the smart contract S1. This is to prevent the use of the storage device 31 that is removed by the user U1 or the like.

In step S212, the management device 20 transmits deletion request information indicating a request for deletion to the smart contract S1. The individual control unit 103 of the smart contract S1 receives the deletion request information.

In step S221, the individual control unit 103 of the smart contract S1 deletes from the address table 104 the address of the smart contract S2 corresponding to the storage 31 to be removed. As a result, the smart contract S1 excludes the smart contract S2 corresponding to the container 31 to be deleted from the management targets.

At step S231, the smart contract S2 stops operating. Execution of step S231 is not essential.

By the series of processes shown in FIG. 10 , the storage device 31 is removed and excluded from the management target of the management system 1 .

Next, processing of the management system 1 when using the container 31 will be described.

11 and 12 are sequence diagrams showing processing when using the storage device 31 in this embodiment. When the processing shown in FIG. 11 is completed, the process proceeds to the processing shown in FIG.

Here, among the one or more storage containers 31, storage containers 31A and 31C are used, and in a situation where storage container 31B is not used, user U1 delivers article 5 to user U2 via storage container 31B. Assuming a case, the processing when using the storage device 31 will be described. It is also assumed that article 5 requires refrigeration.

In step S301, the user U1 transmits usage inquiry information to the smart contract S1 from the terminal 21 to inquire whether the storage device 31 of the storage system 30 is being used. Upon receiving the usage inquiry information, the smart contract S1 transmits usage information indicating whether or not the storage 31 is being used to the terminal 21 . In addition, the smart contract S1 transmits to the terminal 21 the address of the smart contract S2 corresponding to the available storage 31B. For example, the smart contract S1 includes usage information indicating that the storages 31A and 31C of the storages 31A, 31B, and 31C are being used and the storage 31B is not being used, and the smart contract S1 corresponding to the storage 31B. The address of the contract S2 is sent to the terminal 21. User U1 can see that container 31B is available for storage of item 5. FIG.

In step S302, the user U1 uses the terminal 21 to send function inquiry information to the smart contract S1 to inquire whether the container 31B has a refrigeration function. Upon receiving the function inquiry information, the smart contract S1 transfers the received function inquiry information to the smart contract S2B corresponding to the storage 31B.

Upon receiving the function inquiry information, the smart contract S2B confirms the content of the function inquiry information and transmits function response information indicating whether the container 31B has a refrigeration function to the smart contract S1. Upon receiving the function reply information, the smart contract S1 transfers the received function reply information to the terminal 21 . For example, smart contract S2B transmits function response information indicating that container 31B has a refrigeration function. User U1 knows that container 31B can be used to deliver article 5 to user U2 because container 31B has a refrigeration function, and decides to use container 31B.

It should be noted that instead of performing steps S301 and S302 separately, processing corresponding to steps S301 and S302 may be performed collectively by inquiring whether or not the storage device 31 having a specific function is being used. good.

In step S303, the user U1 transmits usage request information for using the storage device 31B to the smart contract S1. The smart contract S1 receives the usage request information.

In step S321, the smart contract S1 performs processing to start using the storage device 31B in response to receiving the use request information in step S303. In the start process, holder change request information indicating that the holder of the key of the storage device 31B is to be changed from the administrator to the user U1 is sent to the smart contract S2B. Upon receiving the owner change request information, the smart contract S2B changes the owner of the key of the storage device 31B from the administrator to the user U1 based on the contents.

In step S304, the user U1 uses the terminal 21 to send function request information for setting the function of the storage device 31B to the smart contract S2B. For example, user U1 transmits to smart contract S2B function request information indicating that the accommodation room of container 31B is to be cooled by the refrigerating function. At this time, the temperature of the housing chamber of the container 31B may be changed with the lapse of time. For example, the temperature of the storage room may be gradually changed from the low temperature to the normal temperature toward the time when the user U2 unloads the article 5 from the container 31B. To specify when the user U2 unloads the article 5 from the container 31B, a predetermined time may be obtained, or the current position of the terminal 22 of the user U2 may be obtained by GPS (Global Positioning System). , by specifying the time when the user U2 reaches the position of the storage 31B using the position and the speed of movement.

In step S331, the smart contract S2 receives the function request information and changes the function information 116 in the storage 31B based on the received function request information. For example, the refrigerating function is changed to the ON state according to the function request information.

In step S341, the function control unit 34 of the container system 30 refers to the function information 116 held by the smart contract S2B, and determines that the refrigeration function has been updated to the ON state in the function information 116 of the container 31B. .

In step S342, the function control unit 34 controls the container 31B to exhibit the refrigerating function. This is done based on the fact that the function control unit 34 has determined in step S341 that the refrigerating function has been updated to the ON state in the function information 116 of the container 31B.

In step S305, the user U1 uses the terminal 21 to control the unlocking of the container 31B. In unlocking control, the terminal 21 transmits an unlocking request for unlocking the container 31B to the smart contract S2B.

In step S332, the smart contract S2B updates the unlock history 15 by adding information indicating that the unlock request has been received, and changes the key state information 113 to the unlocked state.

In step S343, the unlock control unit 33 of the container system 30 refers to the key state information 113 held by the smart contract S2B, and determines that the key state information 113 of the container 31B has been updated to the unlocked state. .

In step S344, the container 31B is unlocked. This is done based on the fact that the unlock control unit 33 has determined in step S343 that the key state information 113 of the container 31B has been updated to the unlocked state.

In step S345, the item 5 is stored in the storage 31B by the user U1.

In step S306, the user U1 uses the terminal 21 to control the locking of the container 31B. In the locking control, the terminal 21 transmits a locking request for locking the container 31B to the smart contract S2B.

In step S333, the smart contract S2B updates the unlock history 15 by adding information indicating that the lock request has been received, and changes the key state information 113 to the locked state.

In step S346, the unlock control unit 33 of the container system 30 refers to the key state information 113 held by the smart contract S2B and determines that the key state information 113 of the container 31B has been updated to the locked state.

In step S347, the container 31B is locked. This is done based on the fact that the unlock control unit 33 has determined in step S346 that the key state information 113 of the container 31B has been updated to the locked state.

In step S322, smart contract S1 transmits to smart contract S2B owner change request information indicating that the owner of the key of storage device 31B is to be changed from user U1 to user U2. Upon receiving the owner change request information, the smart contract S2B changes the owner of the key in the storage device 31B from the user U1 to the user U2 based on the content of the owner change request information.

12, in step S311, the user U2 uses the terminal 22 to control the unlocking of the container 31B. In unlocking control, the terminal 22 transmits an unlocking request for unlocking the container 31B to the smart contract S2B.

In step S334, the smart contract S2B updates the unlock history 15 by adding information indicating that the unlock request has been received, and changes the key state information 113 to the unlocked state.

In step S348, the unlock control unit 33 of the container system 30 refers to the key state information 113 held by the smart contract S2B, and determines that the key state information 113 of the container 31B has been updated to the unlocked state. .

In step S349, the container 31B is unlocked. This is done based on the fact that the unlock control unit 33 has determined in step S348 that the key state information 113 of the container 31B has been updated to the unlocked state.

In step S350, the article 5 is unloaded from the container 31B by the user U2.

In step S323, the smart contract S1 performs processing for terminating the use of the storage 31B. In the termination process, the smart contract S1 transmits owner change request information to the smart contract S2B to change the owner of the key of the storage device 31B from the user U2 to the administrator. Upon receiving the owner change request information, the smart contract S2B changes the owner of the key of the storage device 31B from the user U2 to the administrator based on the content.

Through the series of processes shown in FIGS. 11 and 12, the article 5 can be passed from the user U1 to the user U2 via the container 31B.

Note that the storage device 31 can be changed by successively removing the storage device 31 and adding a new storage device 31 . When the functions provided in the reduced storage container 31 and the expanded storage container 31 are different, it is possible to add or delete the function in the storage container 31 by this reduction and expansion.

For example, a state in which the storage system 30 includes storages 31A, 31B, and 31C ((b) in FIG. 6) is changed to a state in which storage 31C is changed to storage 31D ((c) in FIG. 6). can be done. Here, the storage device 31D is a storage device different from the storage device 31C, and has, for example, a function different from that of the storage device 31C. If the storage 31D has a function different from that of the storage 31C, the smart contract S1 on the server 10 operates the smart contract S2D corresponding to the storage 31D.

By doing so, when the configuration of the management system 1 is changed, the entire management system 1 can be continuously operated without stopping the entire system.

(Modification 1 of Embodiment)
The management system according to this modification includes a plurality of the container systems 30 in the above-described embodiment, and enables the use of the plurality of container systems 30 with high convenience.

FIG. 13 is a block diagram schematically showing the configuration of the management system 2 in this modified example.

The management system 2 shown in FIG. 13 comprises a plurality of container systems 30A, 30B and 30C.

When there are a plurality of container systems 30, the user may not be able to determine which container system 30 belongs to which container can be used. For example, if there are multiple container systems 30 available to the user in various facilities or regions, the user can select any container 31 belonging to any of the container systems 30, so that the user can select which container 31 is available. want to use In such a case, the management system 2 of this modified example can identify the container system 30 to which the container 31 that can be used by the user belongs, and allow the user to use the container 31 .

FIG. 14 is a block diagram showing the functional configuration of the server 10AA in this modification. The server 10AA operates as each of the servers 10A and the like in FIG. Regarding the server 10AA, differences from the server 10A and the like in the first embodiment will be mainly described.

As shown in FIG. 14, the server 10AA comprises a synchronizer 17 and smart contracts S1, S2 and S3.

The management system 2 comprises one smart contract S3, one or more smart contracts S1, and one or more smart contracts S2.

Smart contract S3 may manage one or more smart contracts S1. Also, each of the one or more smart contracts S1 can manage one or more smart contracts S2 in the same manner as the smart contract S1 in the above embodiment. In other words, the server 10AA controls the container system 30 by means of smart contracts S3, S1 and S2, which are hierarchically structured in three layers.

The smart contract S3 manages which container system 30 is installed at which location. The smart contract S3 is a function realized by the server 10AA executing the contract code C3 (not shown) stored in the ledger stored in the ledger storage unit 14. FIG.

The smart contract S3 includes a system management unit 121, an individual control unit 123, and a reception unit 125. The smart contract S3 manages a plurality of container systems 30, and is expected to continue operating even when the number of containers 31 is increased or decreased. Smart contract S3 corresponds to a third smart contract.

The system management unit 121 stores attribute information such as identification information and locations of the container systems 30A, 30B, and 30C, and usage information 122 indicating whether or not each container 31 included in each of the container systems 30A, etc., is being used. managing. When the system management unit 121 receives an inquiry about the attribute information and usage information 122 of the container system 30A and the like from the terminal 21 and the like, the system management unit 121 provides response information based on the managed attribute information and usage information 122. Generate and transmit to the terminal 21 or the like. In addition, the system management unit 121 receives a request to use each storage device 31 from the terminal 21 or the like, and updates the usage information 122 .

Specifically, when the system management unit 121 receives an inquiry from the terminal 21 as to whether or not the storage device 31 is being used, the system management unit 121 generates response information to the inquiry, and transmits the generated response information to the terminal 21. do. Here, when receiving a request to use the storage unit 31, the system management unit 121 refers to the usage information 122 and rejects the request if the storage unit 31 related to the request is being used. is not in use, the request is granted. Note that the system management unit 121 may permit the request only when the billing process for new use is completed when the requested storage device 31 is not in use.

The individual control unit 123 is a processing unit that controls whether each of the container systems 30A and the like is to be managed. The individual control section 123 has an address location table 124 on the memory 12 . The address location table 124 stores the storage address of the smart contract S1 corresponding to the container system 30A and the like managed by the individual control unit 123. FIG.

Specifically, when the individual control unit 123 receives a request to delete the container system 30A or the like from the management device 20, the individual control unit 123 selects the smart contract S1 corresponding to the deletion target container system 30A or the like as the management target. Exclude from To exclude smart contract S1 from management, the address of smart contract S1 to be deleted is deleted from address location table 124 . Further, when the individual control unit 123 receives a request to add a new container system 30A or the like from the smart contract S1, the individual control unit 123 adds the smart contract S1 corresponding to the new container system 30A to the management target. To add smart contract S1 to the management target, address location table 124 additionally stores the address of smart contract S1.

The receiving unit 125 is a processing unit that receives inquiries regarding the functions of the storage units 31 . Upon receiving an inquiry about the function of each container 31, the reception unit 125 reads the address of the smart contract S1 corresponding to the container system 30A or the like to which the container 31 related to the inquiry belongs from the address location table 124, and responds to the received inquiry. forward to that address. In addition, it transmits to the terminal 21 or the like the reply information to the inquiry, which is transmitted as a result of the transfer.

Synchronization unit 17 and smart contracts S1 and S2 are the same as in the above embodiment.

FIG. 15 is an explanatory diagram of the usage information 122 of the management system 2 in this modified example.

The usage information 122 includes each information of a container ID 61 , usage presence/absence 62 , and system ID 63 .

The container ID 61 is an identifier that can uniquely identify the container 31 .

The usage status 62 is information indicating whether or not the storage device 31 is being used.

The system ID 63 is an identifier of the container system 30A or the like to which the container 31 belongs.

When the system management unit 121 receives inquiry information from the terminal 21 of the user U1 to inquire about the available storage containers 31, the system management unit 121 refers to the usage information 122 and obtains the identifier of the storage system 30A or the like to which the available storage containers 31 belong. The answer information shown is generated and transmitted to the terminal 21 .

The terminal 21 that has received the reply information can select and use the container system to which the available container 31 belongs from among the container systems 30A and the like. The method of using the management system to which the available storage device 31 belongs is the same as the method shown in the above embodiment.

By adopting such a configuration, the management system 2 can specify the container system 30 to which the container 31 that can be used by the user belongs and allow the user to use the container 31 .

(Modification 2 of Embodiment)
In this modified example, another form of the control method and the information processing apparatus according to the above-described embodiment and modified example will be described.

FIG. 16 is a flowchart showing the control method in this modified example.

As shown in FIG. 16, the control method in this modified example is a control method that uses a distributed ledger to perform unlocking control, which is control of unlocking or locking one or more storage containers in which articles can be stored.

In step S401, a computer executes the code stored in the distributed ledger to manage one or more second smart contracts corresponding to one or more containers and one or more second smart contracts. Run the first smart contract.

In step S402, each of the one or more second smart contracts controls unlocking of one or more containers corresponding to the second smart contract under the control of the first smart contract.

In step S403, the first smart contract controls whether to manage each of the one or more second smart contracts.

As a result, even if the configuration of the container system is changed, the entire container system can be operated without stopping.

FIG. 17 is a block diagram showing the configuration of the information processing device in this modified example.

As shown in FIG. 17, the information processing device 10F according to the present modification uses a distributed ledger to perform unlocking control, which is control of unlocking or locking one or more containers in which articles 5 can be stored. It is one information processing device 10F among a plurality of information processing devices.

The information processing device 10F includes a processor 11A, a memory 12A, and a storage device 14A in which a distributed ledger storing code is stored.

The processor 11A manages one or more second smart contracts in one-to-one correspondence with one or more storages and one or more second smart contracts by executing code stored in the distributed ledger. Activate the smart contract.

Then, each of the one or more second smart contracts performs unlocking control of the container corresponding to the second smart contract among the one or more containers under the management of the first smart contract.

Also, the first smart contract controls whether or not each of the one or more second smart contracts is subject to management.

As a result, even if the configuration of the container system is changed, the entire container system can be operated without stopping.

As described above, according to the control method according to the present embodiment, the container system is controlled by the first and second smart contracts. In addition, when there is a change such as an increase or decrease in the number of containers provided in the container system, or a change in function, it is sufficient to stop the operation of the second smart contract related to the change, in other words, the first smart The contract and the behavior of the second smart contract not involved in the modification can be maintained. If the container system were to be controlled by a single smart contract, the operation of the smart contract would have to be stopped when adding more containers, which would hinder the operation of the container system. According to the control method according to one aspect of the present invention, the entire container system can be operated without stopping even if the configuration of the container system is changed.

Also, when a container is removed, the first smart contract excludes the second smart contract corresponding to the container to be removed from the target of management. Therefore, it is possible to maintain the operation of the first smart contract and the second smart contract that is not subject to reduction when the container is reduced. Therefore, even if there is a change in the configuration of the container system, the entire container system can be operated without stopping.

Also, when adding a storage container, the first smart contract adds a second smart contract corresponding to the storage container to be added to the target of management. Therefore, the operation of the first smart contract and the already operating second smart contract can be maintained when the storage is expanded. Therefore, even if there is a change in the configuration of the container system, the entire container system can be operated without stopping.

In addition, the first smart contract provides answer information to the inquiry about the use of the storage. Therefore, even if there is a change in the configuration of the container system, it is possible to respond to inquiries regarding the use of the container.

Also, a container can be managed to allow use of the container when the container is not being used. This makes it possible to avoid inconveniences such as multiple users using the container.

In addition, it is possible to manage so that the storage can be used only when the billing process for the usage of the storage is completed.

Also, when an inquiry is made about the function of each container, the inquiry is made to correspond to the smart contract corresponding to the container that is the object of the inquiry. Information different for each container is managed by the second smart contract corresponding to the container, thereby minimizing addition of functions to the first smart contract. Therefore, even if there is a change in the configuration of the container system, the entire container system can be operated without stopping.

Further, whether or not the second smart contract is subject to management is controlled based on whether or not the computer stores the address of the second smart contract in its memory. Therefore, it is possible to more easily construct a configuration that can be operated without stopping the entire container system even if the configuration of the container system is changed.

Also, the container system is controlled by the first, second and third smart contracts. In addition, when there is a change such as addition, reduction, or function change of the container provided in the container system, it is only necessary to stop the operation of the second smart contract related to the change, in other words, the first and The operation of the third smart contract and the second smart contract not involved in the modification can be maintained. Furthermore, since the third smart contract controls whether or not the first smart contract is subject to management, it is possible to more easily control a plurality of first smart contracts.

In the above embodiments, each component may be implemented by dedicated hardware or by executing a software program suitable for each component. Each component may be realized by reading and executing a software program recorded in a recording medium such as a hard disk or a semiconductor memory by a program execution unit such as a CPU or processor. Here, the software that implements the information processing apparatus and the like of the above embodiment is the following program.

That is, this program is a control method that uses a distributed ledger to perform unlocking control, which is control of unlocking or locking one or more containers in which goods can be stored, in a computer. A computer executes the code to generate one or more second smart contracts corresponding to the one or more containers one-to-one, and a first smart contract capable of managing the one or more second smart contracts. and each of the one or more second smart contracts controls unlocking of a container corresponding to the second smart contract among the one or more containers under the management of the first smart contract. , causing the first smart contract to execute a control method for controlling whether or not each of the one or more second smart contracts is subject to the management.

Although the control method and the like according to one or more aspects have been described above based on the embodiments, the present invention is not limited to these embodiments. As long as it does not deviate from the spirit of the present invention, the scope of one or more embodiments includes various modifications that can be made by those skilled in the art, and configurations constructed by combining the components of different embodiments. may be included within

INDUSTRIAL APPLICABILITY The present invention can be used for a control method that can operate without stopping the entire container system even if the configuration of the container system is changed. Specifically, it can be used as a locker for public use.

1, 2 Management System 5 Article 10, 10A, 10B, 10C, 10D, 10E, 10AA Server 10F Information Processing Device 11, 11A Processor 12, 12A Memory 13, 32 Communication Section 14 Ledger Storage Section 14A Storage Device 15 Unlock History 17 Synchronization unit 20 Management device 21, 22 Terminal 30, 30A, 30B, 30C Container system 31, 31A, 31B, 31C, 31D Container 33 Unlock control unit 34 Function control unit 41, 61 Container ID
42, 62 Use or not 63 System ID
101, 121 system management unit 102, 122 usage information 103, 123 individual control unit 104 address table 105, 111, 125 reception unit 112 unlock management unit 113 key state information 114 key holder information 115 function management unit 116 function information 124 address Location Table C1, C2 Contract Code N, M Network S1, S2, S2A, S2B, S2C, S2D, S3 Smart Contract U1, U2 User

Claims (12)

A control method that uses a distributed ledger to perform unlocking or locking control for unlocking or locking one or more containers in which articles can be stored,
A computer executes code stored in the distributed ledger to manage one or more second smart contracts corresponding one-to-one with the one or more storages and the one or more second smart contracts. operate the first smart contract,
Each of the one or more second smart contracts performs unlocking control of a container corresponding to the second smart contract among the one or more containers under the management of the first smart contract,
A control method, wherein the first smart contract controls whether each of the one or more second smart contracts is subject to the management. Further, when the first smart contract receives a request to delete a container included in the one or more containers, the container to be deleted among the one or more second smart contracts The control method according to claim 1, wherein the second smart contract corresponding to is excluded from the management target. Further, when the first smart contract receives a request to add a new container to the one or more containers, it adds a second smart contract corresponding to the new container to the management target. The control method according to claim 1 or 2. Further, when the first smart contract receives an inquiry as to whether the one or more containers are in use, it generates response information to the inquiry and transmits the generated response information. 4. The control method according to any one of 1 to 3. Further, the first smart contract may:
managing usage information indicating whether the one or more containers are being used;
When receiving a request to use one of the one or more storages, referring to the usage information,
(a) deny the request if the one container is in use;
5. The control method of claim 4, further comprising: (b) granting the request if the one store is not in use. 6. The control method according to claim 5, wherein if the one store in (b) is not used, the request is granted only when billing for the use is completed. Further, the first smart contract may:
When receiving an inquiry about the function of one of the one or more containers, to one of the one or more second smart contracts corresponding to the one container forward said inquiry;
The control method according to any one of claims 1 to 6, wherein reply information obtained from said one second smart contract is transmitted as a reply to said inquiry. when the first smart contract newly manages the second smart contract, additionally storing the address of the second smart contract in the memory of the computer running the first smart contract;
When the first smart contract excludes the second smart contract from management, the address of the second smart contract is deleted from the memory of the computer running the first smart contract. A control method according to any one of the preceding items. operating the first smart contract includes operating one or more of the first smart contracts;
Furthermore, operate a third smart contract that can manage one or more of the first smart contracts,
The control method according to any one of claims 1 to 8, wherein the third smart contract controls whether or not each of the one or more first smart contracts is subject to the management. An information processing device among a plurality of information processing devices that performs unlocking control, which is control of unlocking or locking one or more containers in which articles can be stored, using a distributed ledger,
a processor;
memory;
A storage device in which the distributed ledger storing the code is stored,
The processor executes the code stored in the distributed ledger using the memory, thereby creating one or more second smart contracts corresponding one-to-one with the one or more storages, and the one or more second smart contracts. operate a first smart contract capable of managing two smart contracts;
Each of the one or more second smart contracts performs unlocking control of a container corresponding to the second smart contract among the one or more containers under the management of the first smart contract,
An information processing device that controls whether or not the first smart contract makes each of the one or more second smart contracts subject to the management. The plurality of information processing devices including the information processing device according to claim 10;
A management system, comprising: the one or more containers in which the unlocking control is performed by the plurality of information processing devices using the distributed ledger. A program for causing a computer to execute the control method according to claim 1.

Images