JP7163813B2 - Key management system, key management method and program - Google Patents

Description

The present invention relates to a key management system, key management method and program.

IoT (Internet of Things) is a general term for a mechanism in which "things" that have not been connected to a network (for example, the Internet) are connected to a network and exchange information with a server or the like. The above "things" include, for example, sensors, smart devices, in-vehicle equipment, drones, and the like.

One of the characteristics of IoT is that it does not require human intervention. For example, devices operating in places where people are not usually present, such as factories and remote locations, are connected to the Internet and exchange data with each other. IoT devices use "keys" to mutually authenticate each other and to securely transmit and receive data. For example, data to be sent and received is encrypted and decrypted using the key.

Patent Literature 1 describes improving safety when a client device remotely controls an IoT device through communication. Patent Literature 1 discloses key information for communication between devices, and a mechanism for securely communicating between devices using the information.

Patent Literature 2 discloses a technique related to key management and encryption key update.

Patent Document 3 describes that data can be distributed to devices located within a specific range without depending on the communication method. Patent Document 3 discloses that when decrypting encrypted data, the data that can be decrypted differs depending on the area.

JP 2018-152796 A JP 2018-139369 A JP 2009-290669 A

In addition, each disclosure of the above prior art documents is incorporated into this document by reference. The following analysis was made by the inventors.

As described above, in IoT, data is exchanged between devices without human intervention, so each individual device needs to authenticate the other device. However, it is difficult to manage keys used for the authentication. The reasons why key management is difficult are as follows.

Firstly, many devices used in IoT do not have specs sufficient for public key authentication. In other words, if the device used for IoT is a sensor, etc., the hardware (CPU (Central Processing Unit), etc.) sufficient for the sensor to operate is installed, and it has the specs to perform public key authentication. A CPU or the like is often not mounted on the sensor.

As described above, since public key authentication cannot be used in devices used in IoT, "common key authentication" is used as authentication that can be used even in devices with a small processing load and relatively low specs.

A key used in common key authentication must be held between devices that authenticate each other. Therefore, it is necessary to share the key safely and reliably between devices, but if the device specifications are limited, the means of sharing and the means of ensuring security when sharing are limited.

Secondly, when there are a large number of partner devices, the number of keys to be used (exchanged) in common key authentication becomes enormous, making management difficult. For example, when one device communicates with many devices, the problem becomes significant. That is, the more devices mutually authenticate each other, the greater the number of keys to be used (exchanged).

Thirdly, the key update frequency increases. The key used in common key authentication has a low strength and a high possibility of being compromised. Therefore, it is necessary to update the key used in common key authentication in a short period of time. That is, since IoT is operated without human intervention, it is necessary to reliably update the key in a short period of time.

Fourthly, in the unlikely event that a key is compromised, it is necessary to immediately and reliably redistribute the key.

As described above, keys used for authentication in IoT are periodically updated in a short period of time to ensure security. Here, there are two types of methods for updating and managing keys (common keys): a centralized management type and a distributed management type.

FIG. 15 is a diagram for explaining centralized key management. FIG. 16 is a diagram for explaining distributed management type key management.

As shown in FIG. 15, in the centralized management type, key update is performed at one location, and management is also performed at one repository (component described as "key management" in FIG. 15). As shown in FIG. 16, in the distributed management type, the key is updated by the IoT device itself, and the key is managed by the repository of each IoT device.

In the case of the centralized management type, the key management repository can communicate with a fixedly arranged IoT device (for example, IoT device B in FIG. 15) using a wired network. Therefore, the key will be reliably updated except for network failures and the like. However, even in the case of the centralized management type, for a mobile IoT device (for example, IoT device A in FIG. 15), due to the characteristics of a mobile device, wireless communication between the repository and the mobile device is interrupted. It may break. In such a case, the IoT device may fail to make a key update request or to obtain an updated key.

In the case of the distributed management type shown in FIG. 16, for authentication between IoT devices and data encryption/decryption, it is necessary for IoT devices to directly request key updates and obtain updated keys. In order for mobile IoT devices to request key updates and obtain updated keys, it is necessary for the IoT devices to be able to communicate with each other. The availability of key updates cannot be guaranteed.

Patent Documents 1 to 3 only disclose technologies related to key management and encryption. you can't.

A main object of the present invention is to provide a key management system, a key management method, and a program that contribute to improving the availability of key updates for mobile devices.

According to a first aspect of the present invention or disclosure, a key management device that manages keys used by a mobile unit, receives a key update request from the mobile unit to the key management unit, and receives a key update request from the mobile unit to the key management unit, a mobile unit management device for controlling operations in forwarding the key update request to the key management device.

According to a second aspect of the present invention or disclosure, in a key management system including a key management device that manages keys used by a mobile device, receiving a key update request from the mobile device to the key management device; and a step of controlling an operation when transferring the key update request to the key management device according to the location of the mobile body.

According to a third aspect of the present invention or disclosure, a process of accepting a key update request from a mobile to a key management device that manages keys used by the mobile, and updating the key according to the location of the mobile. A program for causing a computer to execute a process of controlling an operation when transferring a request to the key management device is provided.
This program can be recorded in a computer-readable storage medium. The storage medium can be non-transient such as semiconductor memory, hard disk, magnetic recording medium, optical recording medium, and the like. The invention can also be embodied as a computer program product.

According to each aspect of the present invention and disclosure, there are provided a key management system, key management method, and program that contribute to improving the availability of key updates for mobiles.

1 is a diagram for explaining an overview of an embodiment; FIG. 1 is a diagram illustrating an example of a key management system according to a first embodiment; FIG. 4 is a diagram for explaining the operation of the key management system according to the first embodiment; FIG. FIG. 4 is a diagram for explaining key update processing in the key management system according to the first embodiment; FIG. 4 is a diagram for explaining key distribution processing in the key management system according to the first embodiment; 4 is a flow chart showing an example of the operation of the IoT device according to the first embodiment; 4 is a flow chart showing an example of the operation of the mobile management apparatus according to the first embodiment; 4 is a flow chart showing an example of the operation of the key management device according to the first embodiment; 4 is a flow chart showing an example of the operation of the key distribution device according to the first embodiment; FIG. 3 is a diagram showing an example of the relationship between the positions of IoT devices and their priorities; It is a figure which shows an example of the key management system which concerns on a modification. FIG. 3 is a diagram showing an example of the relationship between the positions of IoT devices and their priorities; It is a figure which shows an example of the key management system which concerns on a modification. 1 is a block diagram showing an example of a hardware configuration of a mobile management apparatus according to the first embodiment; FIG. FIG. 4 is a diagram for explaining centralized key management; FIG. 4 is a diagram for explaining key management by a distributed management type;

First, an overview of one embodiment will be described. It should be noted that the drawing reference numerals added to this outline are added to each element for convenience as an example to aid understanding, and the description of this outline does not intend any limitation. Also, connecting lines between blocks in each figure include both bi-directional and uni-directional. The unidirectional arrows schematically show the flow of main signals (data) and do not exclude bidirectionality. Furthermore, in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, etc. disclosed in the present application, an input port and an output port exist at the input end and the output end of each connection line, respectively, although not explicitly shown. Input/output interfaces are similar.

A key management system according to one embodiment includes a key management device 101 and a mobile management device 102 (see FIG. 1). The key management device 101 manages keys used by mobile units. The mobile unit management apparatus 102 receives a key update request from the mobile unit to the key management unit 101 and controls the operation of transferring the key update request to the key management unit 101 according to the location of the mobile unit.

For example, when the mobile is located far from the wireless access point and the radio wave condition is not favorable, the mobile management device 102 lowers the priority of the key update request from the mobile, and gives other priority. Higher rekey requests are processed first. The reason for lowering the priority of key update requests from mobile units is that even if key update requests from mobile units with unstable radio wave conditions are preferentially processed, the keys will not reach the mobile units in the end. This is to avoid Increased availability of key updates for mobiles by processing key update requests first to ensure that updated keys reach mobiles, rather than allocating key update system resources to such processes do.

Specific embodiments will be described in more detail below with reference to the drawings. In addition, the same code|symbol is attached|subjected to the same component in each embodiment, and the description is abbreviate|omitted.

[First embodiment]
The first embodiment will be described in more detail with reference to the drawings.

FIG. 2 is a diagram illustrating an example of a key management system according to the first embodiment; Referring to FIG. 2, the key management system includes a key management device 10, a key distribution device 20, a mobile management device 30, a wireless AP (Access Point) 40, and a plurality of IoT devices 50-1, 50- 2 and .

The key management device 10, key distribution device 20, mobile management device 30 and wireless AP 40 are interconnected by a wired network. The wireless AP 40 provides wireless connection to the mobile IoT devices 50-1 and 50-2.

In the following description, unless there is a particular reason to distinguish between the IoT devices 50-1 and 50-2, they will simply be referred to as "the IoT device 50."

The key management device 10 is a device that manages keys used by the IoT device 50 using existing technology. That is, in the first embodiment, the keys used by the IoT device 50 are managed by centralized management.

The key management device 10 includes a key update processing section 201 and a key distribution processing section 202 .

The key update processing unit 201 generates a new key (for example, a common key) in response to a key update request from the IoT device 50 and delivers the generated key to the key distribution processing unit 202 .

The key distribution processing unit 202 distributes the new key to the target IoT device 50 . Specifically, the key distribution processing unit 202 distributes the key to the pair of IoT devices 50 for mutual authentication using the generated key.

Since the existing technology can be used for generating a new key and distributing the key by the key update processing unit 201, detailed description thereof will be omitted.

The key distribution device 20 is a device that distributes keys for the IoT device 50 . Specifically, the key distribution device 20 transmits the key acquired from the key management device 10 to the IoT device 50 to which the key is to be distributed.

The key distribution device 20 includes processing modules (functions) of a distribution target determination unit 301 and a key distribution unit 302 . The key distribution device 20 uses the processing module to receive the key distribution request sent from the key management device 10 at least to the IoT device 50 that sent the key update request.

The mobile device management device 30 is a device that manages the IoT device 50, which is a mobile device. Specifically, the mobile management device 30 accepts the key update request transmitted by the IoT device 50 and determines whether to transfer the key update request to the key management device 10 .

At the time of the determination, the mobile unit management apparatus 30 determines the importance (priority) of the key update request according to the position of the mobile IoT device 50 (position centered on the wireless AP 40), and determines the priority. , the key update request is transferred to the key management device 10.

The mobile unit management apparatus 30 includes processing modules (functions) of an update target determination unit 401 , a position/time acquisition unit 402 and a key update reception unit 403 . The mobile management device 30 uses the above module to receive a key update request from the mobile IoT device 50 to the key management device 10, and transfer the key update request to the key management device 10 according to the location of the mobile device. control the behavior when

The IoT device 50 has an agent (processing module) for communicating with the key distribution device 20 and the mobile management device 30 via the wireless AP 40 . The agent is a processing module related to the key, and when it determines that the key needs to be updated, it transmits a "key update request" to the mobile management apparatus 30. FIG. At that time, the agent includes the strength of the radio wave received from the wireless AP 40 in the key update request. However, the radio wave intensity may not be included in the key update request. For example, the IoT device 50 may transmit the radio wave intensity to the mobile management apparatus 30 through communication different from the key update request. Alternatively, the IoT device 50 may transmit the radio wave intensity to the wireless AP 40 , and the wireless AP 40 may transmit the radio wave intensity to the mobile management apparatus 30 . The agent is a module that handles a key for authenticating a terminal (IoT device 50), and can be realized using existing technology, so a detailed description thereof will be omitted.

[Overview of system operation]
First, an outline of the operation of the key management system according to the first embodiment will be described with reference to FIG.

The mobile management device 30 is a device that receives a key update request from the mobile IoT device 50 and requests the key management device 10 to update the key. The mobile unit management apparatus 30 has a function of ascertaining the position of the IoT device 50 and determining the priority of key update. Between the key management device 10 and the wireless AP 40, the mobile management device 30 is wired and arranged.

The key distribution device 20 is a device that distributes a key to an IoT device 50 and another IoT device 50 that communicates with the IoT device. The key distribution device 20 has a function of determining the priority of key distribution based on the location of the IoT device 50 and the length of stay at that location. The key distribution device 20 is wired and arranged between the mobile management device 30 and the wireless AP 40 . Further, the key distribution device 20 is also connected to the mobile management device 30 by wire.

The mobile unit management apparatus 30 divides the location of the IoT device 50 into areas based on the distance from the wireless AP 40, and determines whether or not to update the key for each area. For example, if the IoT device 50 is located in a farther area than the wireless AP 40, the key is not updated. If the IoT device 50 is located in an area closer to the wireless AP 40, the priority is raised and the key is updated.

The key distribution device 20 also divides the location of the IoT device 50 into areas based on the distance, similarly to the mobile unit management device 30, and determines whether or not to distribute the key for each area. For example, when located in an area far from the wireless AP 40, the priority is raised and the key is distributed. If the IoT device 50 is located in an area closer to the wireless AP 40, the priority is lowered and the key is distributed.

By dividing areas as described above, key update can be reliably performed, and the availability of key update is ensured by identifying the IoT device 50 . That is, when keys are periodically updated in key management, the keys are delivered to the device without failure, improving the availability of key updates.

[Explanation of operation]
Next, operations of the key management system according to the first embodiment will be described in detail with reference to the drawings. FIG. 3 is a diagram for explaining the operation of the key management system according to the first embodiment. Note that illustration of the key management device 10 is omitted in FIG. As shown in FIG. 3, the wireless AP 40 provides wireless connectivity to the IoT device 50 . Also, the wireless radio wave range of the wireless AP 40 is assumed to be the inside of the circle labeled Area C. FIG.

Detailed exchange of processing between devices will be described with reference to FIG. 4 (key update processing) and FIG. 5 (key distribution processing). Further, the operation of each device alone will be described with reference to the flow charts of FIGS. 6 to 9. FIG. 4, 5, 6, etc., the same reference numerals (steps) are given to common processes.

First, the agent of the mobile IoT device 50 transmits a key update request to the mobile management device 30 (step S01 in FIGS. 4 and 6).

The key update reception unit 403 of the mobile unit management apparatus 30 receives the key update request from the agent (step S02 in FIGS. 4 and 7).

The position/time grasping unit 402 of the mobile unit management apparatus 30 divides the wireless area in which the wireless AP 40 can communicate in advance based on the radio wave intensity radiated by the wireless AP 40 . The number of divisions of the area (wireless area) by the position/time grasping unit 402 can be any number. In the drawings including FIG. 3, the number of divisions is set to "3", and three areas A to C are illustrated as ranges in which the position of the IoT device 50 can be detected.

When the key update receiving unit 403 receives the key update request from the agent (step S02 above), the position/time grasping unit 402 determines which area the IoT device 50 belongs to based on the radio wave intensity of the IoT device 50 acquired from the wireless AP 40. It is determined (ascertained) whether or not (step S03 in FIGS. 4 and 7). That is, the mobile object management apparatus 30 grasps the position of the IoT device 50 based on the intensity of the radio waves received by the IoT device 50 as a mobile object from the wireless AP 40 . Further, the mobile management device 30 divides the range of radio waves emitted by the wireless AP 40 into a plurality of areas, and manages the position of the IoT device 50 by the divided areas.

In addition, the position/time grasping unit 402 calculates (grasps) the time during which the IoT device 50 stays in each area based on the grasped position information. Specifically, the position/time grasping unit 402 stores history information that associates the time when the key update request acquired from the IoT device 50 was received with the position (location area) of the IoT device 50 at the time of transmission of the key update request. to create The position/time grasping unit 402 calculates the time (period) during which the IoT device 50 stayed in each area based on the history information.

The update target determination unit 401 of the mobile unit management apparatus 30 determines the key of the IoT device 50 based on the location information (area of existence; for example, any of areas A to C) of the IoT device 50 grasped by the position/time grasping unit 402. A decision is made as to whether or not to (should) update (step S04 in FIGS. 4 and 7).

For example, referring to FIG. 4, when the IoT device 50, which is a mobile object, exists in a farther area (for example, area C) with respect to the wireless AP 40, the IoT device 50 is immediately out of the wireless radio wave range. (move out of area C) and the possibility of accidentally intruding into the range of radio waves, the update target determination unit 401 determines that the key is not to be updated.

On the other hand, when the IoT device 50 exists in an area closer to the wireless AP 40 (for example, area A), the update target determination unit 401 updates the key with normal priority (low priority). I judge.

Also, when the IoT device 50 exists in an intermediate area (for example, area B), it is unclear whether the IoT device 50 moves to a distant area (area C) or a closer area (area A). Therefore, the update target determination unit 401 determines that the key is updated with a higher priority in order to reliably update the key for the IoT device 50 (the key is updated with a high priority). In the judgments after step S04 shown in FIG. 7, examples of three areas A to C are shown.

The mobile unit management device 30 transmits a key update request to the key management device 10 based on the determination result (key update priority for each IoT device 50) by the update target determination unit 401 (step S05 in FIGS. 4 and 7). ). In this way, the mobile unit management apparatus 30 gives priority to the key update request according to the position of the mobile IoT device 50, and controls the transfer of the key update request according to the priority.

The key update processing unit 201 of the key management apparatus 10 updates the key related to the requested IoT device 50 according to the key update request from the mobile unit management apparatus 30 (step S06 in FIGS. 4 and 8).

When the key update processing unit 201 updates the key in step S06, the key distribution processing unit 202 of the key management device 10 transmits a key distribution request to the key distribution device 20 (steps in FIGS. 5 and 8). S07).

Here, the key distribution processing unit 202 distributes information (for example, a terminal identifier, a MAC (Media Access Control) address, etc.) about the IoT device 50 to be key-distributed and the IoT device 50 communicating with the IoT device 50 to be key-distributed. Generate a key delivery request with

For example, in FIG. 5, when the IoT devices 50-1 and 50-2 communicate with each other, the key distribution device 20 needs to distribute (distribute) updated keys to these devices. Therefore, the key distribution processing unit 202 includes information for specifying the IoT device 50 to which the key is to be distributed in the key distribution request.

Upon receiving the key distribution request from the key management device 10, the key distribution device 20 inquires of the position/time grasping unit 402 of the mobile unit management device 30 about the position of the IoT device 50 to which the key is to be distributed. (Information about the current area; areas A to C) is acquired (step S08 in FIGS. 5 and 9).

The distribution target determination unit 301 of the key distribution device 20 determines whether or not to distribute the key to the mobile IoT device 50 based on the position information of the IoT device 50 acquired from the position/time grasping unit 402 . More specifically, the delivery target determination unit 301 determines the priority of key delivery to the IoT device 50 targeted for key delivery based on the position (in-area) of the IoT device 50 targeted for key delivery. A determination (decision) is made (step S09 in FIGS. 5 and 9).

For example, if the IoT device 50 is located in a farther area than the wireless AP 40 (for example, area C in FIG. 5), the IoT device 50 may immediately move out of the wireless radio coverage range or accidentally Considering the possibility that the remote IoT device 50 has intruded into the reachable range of radio waves, the delivery target determination unit 301 determines that the priority of the distant IoT device 50 will be increased (high priority) and the key will be delivered.

When the mobile IoT device 50 is located in an area closer to the wireless AP 40 (for example, area A in FIG. 5), the distribution target determination unit 301 immediately determines that the target IoT device 50 It judges that it will not go outside the range of wireless radio waves (areas A to C), lowers the priority (low priority), and decides to distribute the key.

When the IoT device is located in an intermediate area (for example, area B in FIG. 5), it is unclear whether the target IoT device 50 moves to a distant area or a closer area. The distribution target determination unit 301 determines that the IoT device 50 will not immediately deviate from the radio wave reachable range (areas A to C), and determines that the key will be distributed with normal priority (medium priority). do.

The key distribution unit 302 of the key distribution device 20 distributes the keys to the agents of the mobile IoT devices 50 in order of priority based on the determination result (key distribution priority) of the distribution target determination unit 301 (FIGS. 5 and 5). 9 step S10). In this way, the key distribution device 20 performs the operation for distributing the key distribution request to the IoT device 50 that is the target of the key distribution request according to the position of the IoT device 50 that is the target of the key distribution request. Control. At that time, the key distribution device 20 gives priority to the key distribution request according to the position of the IoT device 50, and controls distribution regarding the key distribution request according to the priority.

The agent of the mobile IoT device 50 stores the distributed key (step S11 in FIGS. 5 and 6).

FIG. 10 summarizes the relationship between the position (area) and priority of the IoT device 50 by the mobile unit management device 30 and the key distribution device 20 . FIG. 10(a) is a diagram summarizing the relationship between the area and the priority regarding processing of a key update request by the mobile management apparatus 30. FIG. FIG. 10(b) is a diagram summarizing the relationship between the area and the priority regarding the processing of the key distribution request by the key distribution device 20. As shown in FIG.

As described above, in the first embodiment, handling of requests related to keys (key update requests, key distribution requests) is changed according to the location of the IoT device 50 . That is, in the first embodiment, the key is not updated in a situation where the key update process is meaningless, and the key is delivered quickly in a situation where the key must be delivered immediately. As a result, the location information of the IoT device 50 can increase the success rate of key update, so the availability of key update based on the location information of the IoT device 50 can be determined.

In addition, the method of grasping the position information disclosed in the present application requires identification of the wireless communication protocol and changing the acquisition method of the radio wave intensity information according to the protocol, but there are no restrictions due to the protocol. That is, it is possible to perform processing according to the protocol, and key management is possible for various mobile IoT devices 50 .

Further, the key update method performed by the key management device 10 disclosed in the present application follows the existing technology. Therefore, the key can be managed independently of the type of the IoT device 50, and both the IoT device and the fixedly arranged IoT device can be managed.

[Modification]
Note that the configuration, operation, and the like of the key management system described in the above embodiment are examples, and are not meant to limit the configuration and the like of the system. For example, as shown in FIG. 2, the system may include the key management device 10, the key distribution device 20, and the mobile device management device 30 as separate devices, or all or part of the above devices may be integrated. Also good. Alternatively, functions such as the key management device 10 may be implemented in the wireless AP 40 .

In the above embodiment, the key update request from the IoT device 50 located in an area (area C) far from the wireless AP 40 is discarded. However, as described above, it is possible to cope with the IoT device 50 existing in a distant area by adding the condition determination in the update target determination unit 401 and the distribution target determination unit 301 (see FIG. 11).

Here, a case will be described where there is an IoT device 50 that stays in the farthest area C for a certain period of time and intentionally wants to update the key at that position. The position/time grasping unit 402 of the mobile object management apparatus 30 grasps the time during which the IoT device 50 stays in each area A to C from the position information of the IoT device 50 . Therefore, by adding the condition of "staying for a certain period of time or more" as the condition determination of the update target determination unit 401 and the distribution target determination unit 301 and the processing (behavior) when this condition is met, intentionally as described above Key management of the IoT devices 50 staying in the area C can be handled.

FIG. 12(a) is a diagram summarizing the relationship between the area and the priority regarding the processing of the key update request. FIG. 12(b) is a diagram summarizing the relationship between the area and the priority regarding the processing of the key distribution request. As shown in FIG. 12, when the IoT device 50 reaches area C and stays in area C for a certain period of time or more, the update target determination unit 401 and the like increase the priority of key update and distribution. is possible.

As described above, the mobile unit management apparatus 30 gives priority to key update requests based on the location of the IoT device 50 and the length of stay in the divided area. Further, the key distribution device 20 gives priority to the key distribution request based on the position of the IoT device 50 and the time spent in the divided area.

As shown in FIG. 13, if there is a non-communicable area in a part of the wireless area where the wireless AP 40 can communicate, it is possible not to update or distribute the key. This is because the position/time grasping unit 402 performs area division based on the radio wave intensity of the wireless AP 40 .

[Hardware configuration]
Next, hardware configurations of various devices that constitute the key management system according to the above embodiment will be described. FIG. 14 is a block diagram showing an example of the hardware configuration of the mobile management apparatus 30 according to the first embodiment.

The mobile body management device 30 can be configured by an information processing device (computer), and has a configuration illustrated in FIG. 14 . For example, the mobile unit management apparatus 30 includes a CPU (Central Processing Unit) 31, a memory 32, an input/output interface 33, a communication means such as a NIC (Network Interface Card) 34, and the like, which are interconnected by an internal bus.

However, the configuration shown in FIG. 14 is not intended to limit the hardware configuration of the mobile management apparatus 30. FIG. The mobile unit management device 30 may include hardware (not shown), and may not have the input/output interface 33 if necessary. Also, the number of CPUs included in the mobile body management apparatus 30 is not limited to the example shown in FIG.

The memory 32 is a RAM (Random Access Memory), a ROM (Read Only Memory), or an auxiliary storage device (such as a hard disk).

The input/output interface 33 is means that serves as an interface for a display device and an input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device such as a keyboard or mouse that receives user operations.

The functions of the mobile management apparatus 30 are realized by the various processing modules described above. The processing module is implemented by the CPU 31 executing a program stored in the memory 32, for example. Also, the program can be downloaded via a network or updated using a storage medium storing the program. Furthermore, the processing module may be realized by a semiconductor chip. That is, it is sufficient if there is means for executing the functions performed by the processing module by some kind of hardware and/or software.

Note that the key management device 10 and the like can also be configured by an information processing device in the same way as the mobile management device 30, and the basic hardware configuration thereof is the same as that of the mobile management device 30, so a description thereof will be omitted.

Some or all of the above embodiments may also be described in the following additional remarks, but are not limited to the following.
[Appendix 1]
This is the same as the key management system according to the first viewpoint described above.
[Appendix 2]
Preferably, according to appendix 1, the mobile body management device gives priority to the key update request according to the location of the mobile body, and controls transfer of the key update request according to the priority. key management system.
[Appendix 3]
further comprising an access point providing wireless connectivity to the mobile;
3. Preferably, the key management system according to attachment 1 or 2, wherein the mobile body management device grasps the position of the mobile body based on the strength of radio waves received by the mobile body from the access point.
[Appendix 4]
Preferably, the key management system according to appendix 3, wherein the mobile object management device divides a reach of radio waves emitted by the access point into a plurality of areas and manages the position of the mobile object by the divided areas. .
[Appendix 5]
further comprising a key distribution device that receives a key distribution request transmitted from the key management device to at least the mobile unit that transmitted the key update request;
The key distribution device controls an operation when distributing the key distribution request to the mobile body that is the target of the key distribution request according to the position of the mobile body that is the target of the key distribution request. Preferably, the key management system according to any one of Appendices 1 to 4.
[Appendix 6]
Preferably, the key according to appendix 5, wherein the key distribution device gives priority to the key distribution request according to the position of the mobile body, and controls distribution regarding the key distribution request according to the priority. management system.
[Appendix 7]
Preferably, the key management system according to appendix 4, wherein the mobile management device gives priority to the key update requests based on the location of the mobile and the time spent in the divided area.
[Appendix 8]
The key distribution device gives priority to the key distribution request based on the position of the mobile body and the time spent in the divided area, preferably the key according to appendix 4, preferably the key according to appendix 5 management system.
[Appendix 9]
Receiving a key update request from a mobile object to a key management device that manages keys used by the mobile object, and controlling an operation when transferring the key update request to the key management device according to the location of the mobile object. , mobile management equipment.
[Appendix 10]
A device for receiving a key distribution request transmitted to a mobile object from a key management device that manages keys used by the mobile object,
A key distribution device that controls an operation when distributing the key distribution request to the mobile object that is the target of the key distribution request according to the position of the mobile object that is the target of the key distribution request.
[Appendix 11]
This is the same as the key management method according to the second viewpoint described above.
[Appendix 12]
It is as the program related to the above-mentioned third viewpoint.

It should be noted that the respective disclosures of the cited patent documents are incorporated herein by reference. Within the framework of the full disclosure of the present invention (including the scope of claims), modifications and adjustments of the embodiments and examples are possible based on the basic technical concept thereof. Also, various combinations or selections of various disclosure elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) within the framework of the full disclosure of the present invention (including partial deletion) is possible. That is, the present invention naturally includes various variations and modifications that can be made by those skilled in the art according to the entire disclosure including claims and technical ideas. In particular, any numerical range recited herein should be construed as specifically recited for any numerical value or subrange within that range, even if not otherwise stated.

10, 101 Key management device 20 Key distribution device 30, 102 Mobile object management device 31 CPU (Central Processing Unit)
32 memory 33 input/output interface 34 NIC (Network Interface Card)
40 Wireless APs
50, 50-1, 50-2 IoT device 201 Key update processing unit 202 Key distribution processing unit 301 Distribution target determination unit 302 Key distribution unit 401 Update target determination unit 402 Location/time grasping unit 403 Key update reception unit

Claims (10)

a key management device that manages keys used by mobile devices;
a mobile unit management device that receives a key update request from the mobile unit to the key management unit and controls an operation when transferring the key update request to the key management unit according to the location of the mobile unit;
A key management system, including 2. The key according to claim 1, wherein said mobile body management device gives priority to said key update request according to the location of said mobile body, and controls transfer of said key update request according to said priority. management system. further comprising an access point providing wireless connectivity to the mobile;
3. The key management system according to claim 1, wherein said mobile body management device grasps the position of said mobile body based on the intensity of radio waves received by said mobile body from said access point. 4. The key management system according to claim 3, wherein said mobile body management device divides a reach of radio waves emitted by said access point into a plurality of areas, and manages the position of said mobile body by said divided areas. further comprising a key distribution device that receives a key distribution request transmitted from the key management device to at least the mobile unit that transmitted the key update request;
The key distribution device controls an operation when distributing the key distribution request to the mobile body that is the target of the key distribution request according to the position of the mobile body that is the target of the key distribution request. A key management system according to any one of claims 1 to 4. 6. The key management according to claim 5, wherein said key distribution device gives priority to said key distribution request according to the position of said mobile body, and controls distribution regarding said key distribution request according to said priority. system. 5. The key management system according to claim 4, wherein said mobile body management device gives priority to said key update request based on the location of said mobile body and the time spent in said divided area. 6. The key management system according to claim 5, wherein said key distribution device gives priority to said key distribution requests based on the position of said mobile body and the time spent in said divided area. . In a key management system including a key management device that manages keys used by mobile devices,
receiving a key update request from the mobile object to the key management device;
a step of controlling an operation when transferring the key update request to the key management device according to the location of the mobile body;
Key management methods, including a process of accepting a key update request from a mobile object to a key management device that manages keys used by the mobile object;
a process of controlling an operation when transferring the key update request to the key management device according to the position of the mobile body;
A program that makes a computer run

Images