One-time code generator

Abstract

To enable efficient generation of highly secure one-time codes.SOLUTION: A one-time code generation device is provided, comprising an acquisition unit 180 provided on a host vehicle 1 and configured to acquire information on at least either of nearby vehicles and roadside devices located in the surroundings of the host vehicle, and a one-time code generation unit 150 configured to generate a one-time code using the information acquired by the acquisition unit.SELECTED DRAWING: Figure 2

Description

Technical Field

[0004] , , , , ,

[0005] , , ,

[0003] , , ,

[0001] The present invention relates to a one-time code generation device.

Background Art

[0002] Patent Document 1 describes an authentication system including an authentication server, a user terminal, and a device, and performing authentication for controlling the device by the user terminal. In this authentication system, the authentication server and the device generate a common one-time password based on time, the authentication server transmits the one-time password generated by itself to the user terminal, the user terminal transmits the one-time password received from the authentication server to the device, and the device accepts control by the user terminal when the one-time password received from the user terminal matches the one-time password generated by itself.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] For the generation of one-time codes, for security reasons, complex equations or pseudo-random numbers may be adopted, but there is a problem that consideration and secrecy of such equation or pseudo-random number generation methods are required. Further, in a method that depends on a mathematical method such as prime factorization and can logically calculate an answer that is always uniquely determined (although a huge amount of calculation is required), it is difficult to ensure security when the computing power is significantly improved such as in quantum computing.

[0005] In view of such a situation, an object of the present invention is to efficiently generate a highly secure one-time code. <000DA029>[Means for solving the problem]

[0006] To achieve the above objective, the one-time code generation device according to the present invention is installed on the vehicle itself and is located around the vehicle and on surrounding vehicles and roadside units. Through communication with the surrounding vehicles and the roadside unit An acquisition unit that acquires information, A vehicle information management unit manages static information of the vehicle that does not change through the use of the vehicle, and a driving information management unit manages dynamically changing driving information of the vehicle. The information acquired by the acquisition unit The static information managed by the vehicle information management unit and the driving information managed by the driving information management unit It includes a one-time code generation unit that generates a one-time code using [a specific method / tool]. [Effects of the Invention]

[0007] According to the present invention, highly secure one-time codes can be efficiently generated. [Brief explanation of the drawing]

[0008] [Figure 1] This is an explanatory diagram illustrating a one-time code system. [Figure 2] This is a block diagram showing the functional parts of a vehicle. [Figure 3] This is a block diagram showing the functional section of the information management server. [Figure 4] This is a flowchart illustrating the process of generating a one-time code. [Figure 5] This is a flowchart showing how to use the generated one-time code. [Figure 6] This is an explanatory diagram showing other forms. [Figure 7] The processing flow for other forms is shown. [Figure 8] This is a block diagram showing examples of computer hardware configurations. [Modes for carrying out the invention]

[0009] The present invention will be described below based on the illustrated embodiments. However, the present invention is not limited to the embodiments described below.

[0010] As shown in Figure 1, the one-time code generation system S comprises the vehicle itself 1, other vehicles 2a to 2e, a roadside unit 3 which is a smart infrastructure component, and an information management server 4. The vehicle itself 1 has a one-time code generation device that generates one-time codes. These one-time codes are used to verify the authenticity of communication between the vehicle itself 1 and the information management server 4.

[0011] Vehicle 1 and vehicles 2a-2e are connected cars. Vehicle 1 is configured to communicate with vehicles 2a-2e via vehicle-to-vehicle communication (V2V communication) when those vehicles are located in its vicinity. Vehicle 1 is also configured to communicate with roadside unit 3 via vehicle-to-infrastructure communication (V2I communication) when that unit is located in its vicinity. Furthermore, Vehicle 1 is configured to communicate with information management server 4 via base station BS and network NW.

[0012] The roadside unit 3 is configured to communicate with the information management server 4 via the roadside unit management server IS and the network NW that manages the roadside unit 3.

[0013] Furthermore, Vehicle 1 and Vehicles 2a-2e are configured to determine their current position based on signals transmitted from the Global Navigation Satellite System (GNSS) positioning satellites PS.

[0014] As shown in Figure 2, the one-time code generation device installed in the vehicle 1 comprises a vehicle information management unit 110, a driving information management unit 120, a surrounding vehicle information management unit 130, a surrounding vehicle information selection unit 140, a one-time code generation unit 150, a one-time code management unit 160, a one-time code execution unit 170, and an in-vehicle communication unit 180.

[0015] The vehicle information management unit 110 is a functional unit that manages and records static information that does not change through the use of the vehicle. The vehicle information management unit 110 includes a frame number recording unit 111 in which the frame number (chassis number) is recorded, a sales store information unit 112 in which information on the store where the vehicle was sold is recorded, a vehicle inspection certificate registration information unit 113 in which the registration information of the vehicle inspection certificate is recorded, and a shipment information unit 114 in which the mileage immediately after factory shipment is recorded.

[0016] The driving information management unit 120 is a functional unit that manages information that changes dynamically, such as the driving speed of the vehicle and the current position of the vehicle, in association with time. Such information can be transmitted to the server after a one-time code is generated and not recorded in the vehicle. The driving information management unit 120 includes a positioning unit 121 that communicates with the positioning satellite PS to determine the current position, and a navigation, clock, and calendar 122. The navigation, clock, and calendar 122 is an aggregate of a car navigation system, a radio clock, and an electronic calendar. The driving information management unit 120 further includes a meter unit 123 that records the vehicle speed, a battery recording unit 124 that records the remaining battery level of the vehicle, a steering wheel recording unit 125 that records the movement of the steering wheel of the vehicle, a brake recording unit 126 that records the operation amount of the brake of the vehicle, an accelerator recording unit 127 that records the operation amount of the accelerator of the vehicle, and a residual value loan management unit 128 that manages the residual value loan of the vehicle.

[0017] The surrounding vehicle information management unit 130 is a functional unit that manages information on surrounding vehicles located around the vehicle. Such information is only used for the generation of a one-time code and can be deleted after the one-time code is generated. The surrounding vehicle information selection unit 140 is a functional unit that selects information to be used for the generation of a one-time code from the set of information on surrounding vehicles managed by the surrounding vehicle information management unit 130. The one-time code generation unit 150 is a functional unit that generates a one-time code based on the information selected by the surrounding vehicle information selection unit 140 and the one-time code generation rule table 151. The one-time code management unit 160 is a functional unit that manages the one-time code generated by the one-time code generation unit 150. The one-time code execution unit 170 is a functional unit that uses the one-time code managed by the one-time code management unit 160. The in-vehicle communication unit 180 is a functional unit that communicates with other vehicles. The in-vehicle communication unit 180 can also be referred to as an acquisition unit that acquires information from other vehicles.

[0018] Note that vehicles 2a to 2e also have the same functional units as the host vehicle 1.

[0019] As shown in FIG. 3, the information management server 4 includes a communication unit 410, an information management unit 420, and a one-time code verification unit 430. The communication unit 410 is a functional unit that communicates with vehicles. The information management unit 420 is a functional unit that manages the information sent from all the vehicles 1 and 2a to 2e connected cars. The one-time code verification unit 430 is a functional unit that verifies the one-time code.

[0020] FIG. 4 shows the flow of generating the one-time code. First, in step ST11, the surrounding vehicle information management unit 130 acquires the surrounding vehicle information through the in-vehicle communication unit 180. In step ST12, the surrounding vehicle information selection unit 140 selects the surrounding vehicle information to be used for generating the one-time code. In step ST13, the one-time code generation unit 150 selects the vehicle information of the host vehicle to be used for generating the one-time code. This vehicle information can be acquired from the vehicle information management unit 110. As the vehicle information, the license plate number, the driving history of the vehicle, etc. may be used. In step ST14, the one-time code generation unit 150 acquires the position information of the host vehicle to be used for generating the one-time code. This position information can be acquired from the positioning unit 121. In step ST15, the one-time code generation unit 150 acquires the vehicle's driving information (including location information and time) to be used for generating the one-time code. This driving information can be obtained from the driving information management unit 120. In step ST16, the one-time code generation unit 150 generates a one-time code based on one of the rules listed in the one-time code generation rule table 151, using surrounding vehicle information, vehicle information of its own vehicle, and driving information of its own vehicle. Table 151 of the one-time code generation rules contains a set of predefined rules for generating one-time codes, specifying which digits to combine and in what order from among the vehicle's mileage, date and time, latitude, longitude, altitude, frame number, residual value of the residual value loan, registration year, latitude order of the sales store, and postal code of the address where the vehicle is registered. These one-time code generation rules may be shared with the information management server 4 at the time of shipment of the vehicle, or they may not be shared, and the information management server 4 may perform a brute-force search or look up past vehicle information. In step ST17, the one-time code management unit 160 saves the one-time code generated in step ST16.

[0021] The longer a one-time code is, the more difficult it is to decipher, and the more patterns (number of generation rules) it contains, the more difficult it is to decipher. Even if the one-time code generation rule table 151 is leaked, it will not be possible to obtain the correct one-time code unless the internal state of the vehicle in question at the time of generation and information about surrounding vehicles are known.

[0022] Figure 5 shows the flow of execution and verification of the one-time code. First, in step ST21, the one-time code execution unit 170 requests the execution of the service. This request is sent to the one-time code verification unit 430 via the vehicle's onboard communication unit 180 and the communication unit 410 of the information management server 4. In step ST22, the one-time code verification unit 430 requests a one-time code from its own vehicle. This request is sent to the one-time code execution unit 170 via the communication unit 410 of the information management server 4 and the vehicle's onboard communication unit 180. In step ST23, the one-time code execution unit 170 sends the already generated one-time code to the information management server 4 via the in-vehicle communication unit 180. This one-time code is then sent to the one-time code verification unit 430 via the communication unit 410 of the information management server 4. In step ST24, the one-time code verification unit 430 verifies the authenticity of the one-time code sent from vehicle 1. Specifically, the one-time code verification unit 430 determines whether the one-time code can be generated based on the vehicle information (including information on surrounding vehicles) managed by the information management unit 420 and the one-time code generation rule table that has been shared in advance between vehicle 1 and vehicle 1. If the one-time code verification unit 430 determines that the one-time code can be generated, it determines that the one-time code is genuine, and step ST25, described later, proceeds. If the one-time code verification unit 430 determines that the one-time code cannot be generated, it determines that the one-time code is fake, and this process ends. In step ST25, the one-time code verification unit 430 approves the request related to step ST21. In the following step ST26, the information management server 4 provides services to the vehicle, and in step ST27, the vehicle receives services from the information management server 4.

[0023] According to the above embodiment, one-time codes can be generated according to vehicles located around a moving vehicle. In addition, the following effects can be obtained. Since it does not use pseudorandom numbers, there is no need to keep the pseudorandom number generation program code or equations secret. Even if the program or rules for generating one-time codes were leaked, the same one-time code could not be generated unless the surrounding vehicles at a given time were identical. Therefore, it is difficult to reproduce the one-time code retrospectively, making it highly secure. Based on vehicle behavior, there is a possibility that a one-time code identical or similar to one previously generated may be generated when the vehicle is stuck in traffic, parked, or driving in an area with few other connected cars. By not generating a one-time code in such situations, the generation of duplicate one-time codes can be efficiently prevented. • A one-time code can be temporarily shared between nearby vehicles that happen to be gathered at a specific location at a specific time, and have no prior acquaintance or connection to each other. The authenticity and reproduction of one-time codes can only be verified by the information management server that collects information from all connected cars, and it is difficult to verify them by any other means. In other words, it is highly secure. • For a third party to obtain the same one-time code, they would need to be constantly near the vehicle in question. Therefore, it increases the difficulty of obtaining the one-time code for malicious actors, thus enhancing security. - Not only when obtaining the one-time code, but even if a malicious actor manages to steal the one-time code from a moving vehicle, the information management server can prevent the malicious actor from using the one-time code at a location different from the current location information of the legitimate vehicle that generated and used the one-time code. This means that both when obtaining the one-time code from a moving vehicle and when using the one-time code, the malicious actor must be at the same location as the legitimate vehicle. Therefore, the ease of use of the one-time code after it has been stolen by a malicious actor is significantly reduced, thereby enhancing security. The authenticity verification of one-time codes does not necessarily have to be in real time, and the information management server can retrospectively verify past one-time codes. Therefore, if a vehicle can communicate with the information management server, it can generate as many one-time codes as possible, regardless of whether they are needed, as long as the driving environment meets the conditions for generating one-time codes, and use previously generated one-time codes as needed. If someone with malicious intent were to attempt to forge an arbitrary one-time code, they would have to replicate, maintain, and manage a vast amount of vehicle data for all connected cars managed by the system, similar to information management servers, over a very long period from the past to the present, at considerable cost and manpower. In other words, forging a one-time code is expensive and highly secure. While standard one-time codes can be used for general services by entering them into a terminal within a certain time frame, having a driver enter a one-time code into a terminal while driving can interfere with safe driving. This system allows the vehicle to generate its own one-time code and automatically undergo server verification, making it convenient for drivers as it doesn't interfere with driving operations. In other words, instead of the driver entering the one-time code into a terminal for authentication, the server verifies the correctness of the one-time code. Since the driver doesn't manually enter the code, there's greater flexibility in the number of digits in the one-time code (i.e., it can be longer), and it can use characters that are difficult for drivers to input, not just numbers, thus increasing the complexity of the one-time code. Furthermore, using multiple one-time codes generated from combinations of different information can enhance security.

[0024] Furthermore, the above-described embodiment has the advantage that it relies on the one-time encounter (chance) between vehicles, and the code is not determined solely by logical calculations. To bypass the code obtained in this way requires not only computing power but also a data storage capacity at least equivalent to that of the information management server 4, making it costly to bypass. In other words, the code obtained by the above-described embodiment is highly secure.

[0025] One-time codes used during communication become invalid after a certain period of time, even if unused, or after a single use, thus enhancing security. If pseudo-random numbers or mathematical equations are used to generate one-time codes, measures must be taken to prevent the same random numbers from being generated multiple times by chance, and the equations and program code must be kept confidential. If the server generating the one-time codes is hacked, or if the program code is leaked, it becomes easy to obtain the same one-time code.

[0026] In the above embodiment, by using multiple vehicles equipped with V2V functionality, a one-time code is generated in a vehicle while it is in motion (including when it is stopped) based on constantly changing information about surrounding vehicles. The entity with which the vehicle communicates is not limited to other vehicles or moving objects, but may also be smart infrastructure with V2I functionality fixed near the vehicle's travel route (such as power poles, telephone poles, traffic lights, streetlights, surveillance cameras, ETC devices, etc.). [Other embodiments] The vehicle information used to generate the one-time code is not limited to the frame number; it may also include information that changes depending on the vehicle owner, such as the insurance policy number or license plate number. Any information that can be collected by both the vehicle 1 and the information management server 4 can be used to generate the one-time code for the vehicle 1.

[0027] Vehicle information used to generate one-time codes may include the vehicle's driving history (mileage, date and time, latitude, longitude, and altitude). In this case, the driving history (mileage, date and time, latitude, longitude, and altitude) immediately after the vehicle leaves the factory is not recorded on any computer other than the vehicle itself and the information management server, and is not recorded or modified outside the managed factory premises, making it relatively confidential information. Therefore, when exchanging one-time codes between the vehicle and the information management server, using the driving history (mileage, date and time, latitude, longitude, and altitude) immediately after the vehicle leaves the factory eliminates the need to transmit all one-time codes, thus enhancing the confidentiality of the one-time codes. The driving history (mileage, date and time, latitude, longitude, and altitude) recorded immediately after the vehicle leaves the factory is recorded before shipment, in a state where it is unknown who will purchase which car. In particular, if a malicious actor attempts to forge a one-time code targeting a specific person's vehicle, in addition to knowing the one-time code mentioned above, they would need to know all the driving history (mileage, date and time, latitude, longitude, and altitude) recorded immediately after the vehicle left the factory for any vehicle that the specific person might potentially purchase, making this an effective security measure.

[0028] As mentioned above, the mileage immediately after leaving the factory is shared between the vehicle and the information management server before it reaches the buyer. This mileage can be considered similar to a shared key exchanged in advance. As an example of how the mileage immediately after leaving the factory can be used, for example, when communicating a one-time code after the vehicle is sold, some operation based on the mileage immediately after leaving the factory can be applied to a part of the one-time code (excluding parts that identify the vehicle, such as the frame number), and this is also recorded in the rule sheet. The information management server can easily decrypt the code based on the rule sheet, since the mileage immediately after leaving the factory for that vehicle is recorded in advance, as long as the vehicle can be identified. For a malicious actor, not only would they not be able to recognize that "some processing based on the mileage immediately after leaving the factory has been applied to a part of a one-time code they obtain," but when trying to obtain individual vehicle information at a certain time and generate a one-time code, they would need to somehow obtain the mileage immediately after leaving the factory, which differs for each individual vehicle, as well as the rule sheet, and apply the correct processing. The mileage immediately after leaving the factory, like the rule sheet, does not necessarily need to be communicated, making it difficult to obtain after it has been shipped, thus increasing the security of the one-time code.

[0029] The selection criteria for surrounding vehicles do not have to be based on the lowest digit of the frame number. For example, vehicles can be selected based on the clockwise order of their position coordinates, the longest mileage, the fastest speed, the highest residual value of their residual value loans, the oldest registration year, the latitude of the dealership where the vehicle was sold, or the postal code of the address where the vehicle is registered. Selection can be made based on information managed on the information management server. Furthermore, security can be enhanced by changing the vehicle selection criteria each time a one-time code is generated.

[0030] In addition to information on surrounding vehicles, the vehicle may also perform vehicle-to-infrastructure (V2I) communication with roadside devices (smart infrastructure) or smartphones that it will temporarily pass by, and generate a one-time code using information stored in the smart infrastructure (utility pole management number, age of construction, date of last maintenance, power consumption, power generation amount, and latitude and longitude of installation). Unlike information on vehicles managed and sold by individuals, infrastructure information is managed by a specific entity different from the vehicle and information management server, making it difficult for malicious external parties to tamper with the information. This further enhances security.

[0031] Even in rural areas with relatively low vehicle density, if sufficient smart infrastructure is available, one-time codes can be generated using information from such smart infrastructure.

[0032] If a vehicle cannot immediately connect to the information management server in an area outside the range of a mobile phone network, a wired network connection may be used for purposes such as smart infrastructure management.

[0033] If a smart infrastructure is included among those who share the generated one-time code, the smart infrastructure, provided it is sufficiently secure, may store the shared one-time code. If the smart infrastructure participates in a blockchain or similar and operates a managed ledger, storing the one-time code on the blockchain ledger has the advantage of making it more difficult to tamper with the one-time code, thereby increasing security.

[0034] As shown in Figure 6, the generated one-time code can also be used on network-connected devices within the smart home H, which is connected to vehicle 1 and information management server 4. For example, the generated one-time code can be used to lock door H1, lock safe H2, or log in to personal computer H3, and its authenticity can be verified by the information management server. This allows locking and unlocking network-connected devices before returning home. This has the advantage of managing device usage even before returning home and preventing unnecessary use. Alternatively, the generated one-time code may be used on network-connected devices via smart infrastructure 3 before vehicle 1 connects to smart home H.

[0035] Figure 7 shows another example of one-time code execution and verification. First, in step ST31, the one-time code execution unit 170 requests the unlocking of door H1. This request is sent to the one-time code verification unit 430 via the vehicle's onboard communication unit 180 and the communication unit 410 of the information management server 4. In step ST32, the one-time code verification unit 430 requests a one-time code from its own vehicle. This request is sent to the one-time code execution unit 170 via the communication unit 410 of the information management server 4 and the vehicle's onboard communication unit 180. In step ST33, the one-time code execution unit 170 sends the already generated one-time code to the information management server 4 via the in-vehicle communication unit 180. This one-time code is then sent to the one-time code verification unit 430 via the communication unit 410 of the information management server 4. In step ST34, the one-time code verification unit 430 verifies the authenticity of the one-time code sent from vehicle 1. Specifically, the one-time code verification unit 430 determines whether the one-time code can be generated based on the vehicle information managed by the information management unit 420 (including information on surrounding vehicles) and the one-time code generation rule table that has been shared in advance between vehicle 1 and vehicle 1. If the one-time code verification unit 430 determines that the one-time code can be generated, it determines that the one-time code is genuine, and step ST35, described later, proceeds. If the one-time code verification unit 430 determines that the one-time code cannot be generated, it determines that the one-time code is fake, and this process ends. In step ST35, the one-time code verification unit 430 approves the request related to step ST31. In the following step ST36, the information management server 4 sends a command to door H1 via the network NW and the smart home H network to unlock the door, and in step ST37, the door H1 is unlocked.

[0036] One-time codes can also be generated on smartphones or other devices while they are in transit, even if the vehicle is not in motion.

[0037] Figure 8 shows an example of the computer hardware configuration of a one-time code generation device installed in the vehicle 1. This device comprises a CPU 191, an interface device 192, a display device 193, an input device 194, a drive device 195, an auxiliary storage device 196, and a memory device 197, which are interconnected by a bus 199.

[0038] The program that enables the functions of this device is provided on a recording medium 198 such as a CD-ROM. When the recording medium 198 containing the program is set in the drive device 195, the program is installed from the recording medium 199 to the auxiliary storage device 196 via the drive device 195. Alternatively, the program installation does not necessarily have to be done via the recording medium 199, but can also be done via a network. The auxiliary storage device 196 stores the installed program as well as necessary files and data.

[0039] The memory device 197 reads and stores a program from the auxiliary storage device 196 when a program startup command is received. The CPU 191 implements the functions of the one-time code generator according to the program stored in the memory device 197. The interface device 192 is used as an interface for connecting to other computers via a network. The display device 193 displays a GUI (Graphical User Interface) etc., generated by the program. The input devices 194 include a keyboard, mouse, and touch panel.

[0040] Furthermore, the surrounding vehicles 2a-2e, smart infrastructure 3, information management server 4, and smart infrastructure management server IS also have the same computer hardware configuration as the one-time code generation device.

[0041] The following additional information is disclosed regarding the embodiments described above. [Note 1] A one-time code generation device installed in the vehicle, An acquisition unit that acquires information on at least one of surrounding vehicles and roadside equipment located around the vehicle itself, A one-time code generation unit generates a one-time code using the information acquired by the acquisition unit. A one-time code generation device equipped with the following features. [Effect 1] The movement of one's own vehicle is likely to change the surrounding vehicles. Even if the rules for generating one-time codes are leaked to a third party, it is difficult to retrospectively reproduce the constantly changing situation around the vehicle. Therefore, it is possible to easily generate highly secure one-time codes. [Note 2] A one-time code management unit manages each of the multiple one-time codes generated by the one-time code generation unit in association with the time each of the multiple one-time codes was generated. A one-time code execution unit that uses at least one of the multiple one-time codes managed by the aforementioned one-time code. A one-time code generation device as described in Appendix 1, further comprising the features described in Appendix 1. [Effect 2] Security can be further enhanced by using pre-generated and stored unused one-time codes, or by combining multiple pre-generated and stored unused one-time codes, rather than using the generated one-time codes in real time. [Note 3] The one-time code generation device according to Appendix 2, wherein if the total number of surrounding vehicles and roadside units that are within a predetermined range of the vehicle and capable of communicating with the vehicle is less than or equal to a predetermined number, the one-time code execution unit uses at least one of the multiple one-time codes that have been pre-generated by the one-time code generation unit and managed by the one-time code management unit. [Effect 3] In situations where it is difficult to generate a one-time code that does not overlap with previously generated one-time codes, it is possible to choose not to generate a one-time code and instead use an unused one-time code that has been generated in the past. [Note 4] The one-time code generation device according to Appendix 2 or 3, wherein, when the speed of the vehicle is below a predetermined value, the one-time code execution unit uses at least one of the multiple one-time codes that have been pre-generated by the one-time code generation unit and managed by the one-time code management unit. [Effect 4] If the vehicle's speed is below a predetermined value, there is a possibility that a one-time code that has been generated in the past may be generated. Therefore, in such situations, it is possible to use an unused one-time code that has been generated in the past without generating a new one-time code.

[0042] Although embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above, and various modifications and changes are possible based on the technical concept of the present invention. [Explanation of Symbols]

[0043] S One-Time Code Generation System 1. Your own vehicle 110 Vehicle Information Management Department 120 Driving Information Management Department 130 Surrounding Vehicle Information Management Department 140 Surrounding Vehicle Information Selection Department 150 One-Time Code Generation Unit 160 One-Time Code Management Department 170 One-Time Code Execution Unit 180 In-vehicle communications unit 2a~2e Surrounding vehicles 3 Roadside unit 4. Information Management Server 410 Communications Department 420 Information Management Department 430 One-Time Code Verification Department

Claims

1. A one-time code generation device installed in the vehicle, An acquisition unit that acquires information on surrounding vehicles and roadside units located around the vehicle by communicating with the surrounding vehicles and roadside units, A vehicle information management unit manages static information of the vehicle that does not change through the use of the vehicle, A driving information management unit manages the dynamically changing driving information of the vehicle, A one-time code generation unit generates a one-time code using the information acquired by the acquisition unit, the static information managed by the vehicle information management unit, and the driving information managed by the driving information management unit. A one-time code generation device equipped with the following features.

2. A one-time code management unit manages each of the multiple one-time codes generated by the one-time code generation unit in association with the time each of the multiple one-time codes was generated. A one-time code execution unit that uses at least one of the multiple one-time codes managed by the aforementioned one-time code. The one-time code generation device according to claim 1, further comprising:

3. The one-time code generation device according to claim 2, wherein if the total number of surrounding vehicles and roadside units that are within a predetermined range of the vehicle and capable of communicating with the vehicle is less than or equal to a predetermined number, the one-time code execution unit uses at least one of the multiple one-time codes that have been pre-generated by the one-time code generation unit and managed by the one-time code management unit.

4. The one-time code generation device according to claim 2 or 3, wherein, when the speed of the vehicle is below a predetermined value, the one-time code execution unit uses at least one of the multiple one-time codes that have been pre-generated by the one-time code generation unit and managed by the one-time code management unit.

Images