Information processing device

Abstract

To provide an information processing device which improves security when a vehicle is authenticated.SOLUTION: In an authentication system, a user terminal 100, an authentication server 200, and a management server 300 are mutually connected with each other by a network. The authentication server 200 for providing information on a vehicle includes a control section 201 for implementing processes of: receiving a frame number and a registration number of the vehicle from the user terminal 100; determining whether a correspondence between the received frame number and registration number is correct; and authenticating the frame number as a legitimate number when the correspondence between the frame number and the registration number is determined to be correct.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to an information processing device. [Background technology]

[0002] Patent Document 1 discloses a method for providing an estimated price for a vehicle inspection service or a checkup service, which utilizes an information processing device and an information terminal owned by a user, both of which are capable of two-way communication via a communication line. In the method for providing an estimated price disclosed in Patent Document 1, the estimated price for the vehicle inspection service or the checkup service that can be provided by a dealer is stored in a storage device. In addition, in the method for providing an estimated price, the storage device is referenced in response to a user's request operation on the information terminal accessing the information processing device, thereby determining an estimated price for the vehicle inspection service or the checkup service, and providing the determined estimated price to the information terminal. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2003-132247 A Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure aims to improve security during vehicle authentication. [Means for solving the problem]

[0005] The information processing device according to the present disclosure includes: accepting a vehicle identification number and a vehicle registration number of the vehicle; determining whether the received vehicle identification number and the vehicle registration number correspond correctly; If it is determined that the correspondence between the chassis number and the vehicle registration number is correct, authenticating that the chassis number is a genuine number; The control unit is configured to: Effect of the Invention

[0006] The present disclosure can improve security during vehicle authentication. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing a schematic configuration of an authentication system. [Diagram 2] FIG. 2 is a block diagram illustrating an example of a functional configuration of the authentication server and the management server. [Diagram 3] FIG. 3 is a diagram showing an example of a table configuration of information held in the vehicle information database. [Figure 4] FIG. 4 is a diagram showing an example of a table configuration of user information held in the user information database. [Diagram 5] FIG. 5 is a flowchart of the process executed by the control unit in the first embodiment. [Figure 6] FIG. 6 is a flowchart of the process executed by the control unit in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] It is assumed that the information processing device receives a vehicle identification number for vehicle authentication. In such a case, the accepted chassis number may be incorrect. In that case, there is a risk that information processing will be performed on a vehicle with an incorrect chassis number. The information processing device according to the present disclosure solves such a problem.

[0009] A control unit of an information processing device according to the present disclosure receives a chassis number and a vehicle registration number of the vehicle. The control unit of the information processing device determines whether the received chassis number and vehicle registration number correspond correctly. If the control unit determines that the chassis number and vehicle registration number correspond correctly, it authenticates that the chassis number is a legitimate number.

[0010] If the correspondence between the chassis number and the vehicle registration number is incorrect, it is assumed that there is an error in the chassis number. Therefore, if the correspondence between the chassis number and the vehicle registration number is incorrect, the information processing device determines that the received chassis number is not a legitimate number. Also, if the correspondence between the chassis number and the vehicle registration number is correct, the information processing device determines that the received chassis number is a legitimate number. In this way, it is possible to increase security during vehicle authentication.

[0011] Specific embodiments of the present disclosure will be described below with reference to the drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, and the like described in each embodiment are not intended to limit the technical scope of the disclosure to only those.

[0012] First Embodiment (System Overview) An authentication system 1 in the present disclosure will be described with reference to Fig. 1. Fig. 1 is a diagram showing a schematic configuration of the authentication system 1. The authentication system 1 includes a user terminal 100, an authentication server 200, and a management server 300. In the authentication system 1, the user terminal 100, the authentication server 200, and the management server 300 are connected to each other via a network N1. The network N1 may be, for example, a WAN (Wide Area Network), which is a global public communication network such as the Internet, or a telephone communication network such as a mobile phone.

[0013] (User terminal) The user terminal 100 is a terminal related to the user 10. The user terminal 100 is, for example, a computer or a mobile information terminal used by the user 10. It is assumed that the user 10 receives authentication of the chassis number of the vehicle used by the user 10 (hereinafter, sometimes referred to as the "user vehicle") from the authentication server 200, thereby acquiring vehicle information about the user vehicle from the authentication server 200. At this time, the user 10 manually inputs the chassis number of the user vehicle into the user terminal 100. Then, the user terminal 100 transmits information indicating that the user 10 has requested acquisition of vehicle information (hereinafter, sometimes referred to as the "request information") to the authentication server 200 via the network N1. Here, the request information includes the chassis number of the user vehicle.

[0014] (Authentication Server) The authentication server 200 is a server device that provides information about vehicles (hereinafter, sometimes referred to as "vehicle information"). The authentication server 200 receives request information from the user terminal 100 via the network N1. The authentication server 200 then provides vehicle information about the vehicle having the chassis number included in the request information. At this time, the chassis number of the user's vehicle included in the request information may be incorrect because the user 10 manually inputs an incorrect chassis number into the user terminal 100. In that case, there is a risk that the authentication server 200 will output to the user terminal 100 vehicle information about a vehicle having a chassis number different from the chassis number of the user's vehicle.

[0015] Therefore, the authentication server 200 acquires the vehicle registration number (number written on the license plate) of the user vehicle together with the vehicle identification number of the user vehicle. Specifically, the authentication server 200 receives request information including the vehicle identification number and the vehicle registration number from the user terminal 100. That is, when the user 10 attempts to acquire vehicle information about the user vehicle, the user 10 inputs the vehicle registration number together with the vehicle identification number into the user terminal 100. Then, the authentication server 200 judges whether or not the vehicle identification number and the vehicle registration number of the user vehicle included in the request information correspond correctly. At this time, when the authentication server 200 judges that the vehicle identification number and the vehicle registration number of the user vehicle included in the request information correspond correctly, it authenticates that the vehicle identification number of the user vehicle included in the request information is a legitimate number. The method by which the authentication server 200 judges whether or not the vehicle identification number and the vehicle registration number of the user vehicle included in the request information correspond correctly will be described later in detail.

[0016] The authentication server 200 includes a computer having a processor 210, a main memory unit 220, an auxiliary memory unit 230, and a communication interface (communication I / F) 240. The processor 210 is, for example, a CPU (Central Processing Unit) or a DSP (Digital Signal Processor). The main memory unit 220 is, for example, a RAM (Random Access Memory). The auxiliary memory unit 230 is, for example, a ROM (Read Only Memory). The auxiliary memory unit 230 is, for example, a HDD (Hard Disk Drive) or a disk recording medium such as a CD-ROM, a DVD disk, or a Blu-ray disk. The auxiliary memory unit 230 may be a removable medium (portable storage medium). Here, examples of the removable medium include a USB memory or an SD card. The communication I / F 240 is, for example, a LAN (Local Area Network) interface board, or a wireless communication circuit for wireless communication.

[0017] In the authentication server 200, the auxiliary storage unit 230 stores an operating system (OS), various programs, various information tables, and the like. In the authentication server 200, the processor 210 can load the programs stored in the auxiliary storage unit 230 into the main storage unit 220 and execute them to realize various functions as described below. However, some or all of the functions of the authentication server 200 may be realized by a hardware circuit such as an ASIC or an FPGA. Note that the authentication server 200 does not necessarily have to be realized by a single physical configuration, and may be configured by multiple computers that cooperate with each other.

[0018] (Management Server) The management server 300 is a server device that manages the chassis numbers and vehicle registration numbers of multiple vehicles. The management server 300 is also a server device that holds vehicle information. The management server 300 is configured so that the authentication server 200 can access a database that holds the chassis numbers and vehicle registration numbers via the network N1. The management server 300 also transmits vehicle information to the authentication server 200 via the network N1. The management server 300 is, for example, a server device that manages the vehicle inspection certificates of multiple vehicles. Like the authentication server 200, the management server 300 is configured to include a computer.

[0019] In this embodiment, the authentication server 200 accesses the database in the management server 300 and determines whether the correspondence between the chassis number and the vehicle registration number included in the request information matches the correspondence between the chassis number and the vehicle registration number included in the database. In this way, the authentication server 200 determines whether the correspondence between the chassis number and the vehicle registration number of the user's vehicle included in the request information is correct. However, the authentication server 200 does not store the chassis number and the vehicle registration number in the management server 300. It is not necessary for the management server 300 to access a database that stores the chassis number and the vehicle registration number. For example, the authentication server 200 may have a database that stores the chassis number and the vehicle registration number instead of the management server 300. In other words, the authentication server 200 may independently determine whether the chassis number and the vehicle registration number of the user's vehicle included in the request information correspond correctly.

[0020] (Functional configuration) Next, the functional configurations of the authentication server 200 and the management server 300, which configure the authentication system 1, will be described with reference to Fig. 2 to Fig. 4. Fig. 2 is a block diagram showing an example of the functional configuration of the authentication server 200 and the management server 300.

[0021] (Management Server) The management server 300 is configured to include a control unit 301, a communication unit 302, and a vehicle information DB 303. The control unit 301 has a function of performing arithmetic processing for controlling the management server 300. The control unit 301 can be realized by a processor in the management server 300. The communication unit 302 has a function of connecting the management server 300 to the network N1. The communication unit 302 can be realized by a communication I / F in the management server 300.

[0022] The vehicle information DB 303 has a function of holding vehicle information about a plurality of vehicles. The vehicle information DB 303 can be realized by an auxiliary storage unit in the management server 300. Fig. 3 is a diagram showing an example of a table configuration of information held in the vehicle information DB 303.

[0023] As shown in FIG. 3, the information held in the vehicle information DB303 has a user ID field, a chassis number field, a vehicle registration number field, and a vehicle information field. The user ID field stores an identifier (user ID) for identifying a user who uses a vehicle. The chassis number field stores the chassis number of a vehicle used by a user corresponding to the user ID stored in the user ID field. The vehicle registration number field stores the vehicle registration number of a vehicle used by a user corresponding to the user ID stored in the user ID field. The vehicle information field stores vehicle information about a vehicle used by a user corresponding to the user ID stored in the user ID field. The vehicle information includes, for example, information indicating performance specifications of the vehicle. The vehicle information may also include the chassis number or vehicle registration number of the vehicle. Each piece of information stored in the vehicle information DB303 is registered in advance at the time of sale or manufacture of the vehicle.

[0024] The control unit 301 transmits the vehicle information held in the vehicle information DB 303 to the authentication server 200 via the communication unit 302 .

[0025] (Authentication Server) The authentication server 200 includes a control unit 201, a communication unit 202, and a user information DB 203. The control unit 201 has a function of performing arithmetic processing for controlling the authentication server 200. The control unit 201 can be realized by a processor 210 in the authentication server 200. The communication unit 202 has a function of connecting the authentication server 200 to a network N1. The communication unit 202 can be realized by a communication I / F 240 in the authentication server 200.

[0026] The control unit 201 receives request information from the user terminal 100 via the communication unit 202. The control unit 201 acquires the chassis number and vehicle registration number of the user's vehicle included in the request information. The control unit 201 then determines whether the chassis number and vehicle registration number of the user's vehicle included in the request information correspond correctly. Specifically, the control unit 201 accesses the vehicle information DB 303 in the management server 300 via the communication unit 202. The control unit 201 acquires the combination of the chassis number and vehicle registration number of the user's vehicle included in the request information. It is determined whether the combination of the chassis number and the vehicle registration number matches that stored in the vehicle information DB 303.

[0027] If the control unit 201 makes a positive determination, it authenticates that the chassis number of the user's vehicle included in the request information is a legitimate number. If the control unit 201 makes a negative determination, it determines that the chassis number of the user's vehicle included in the request information is an unauthorized chassis number.

[0028] The user information DB 203 has a function of holding user information. The user information DB 203 can be realized by the auxiliary storage unit 230 in the authentication server 200. The user information is information about a vehicle number of a user vehicle that has been accepted in the past and that has been authenticated as a legitimate number by determining that the correspondence between the chassis number and the vehicle registration number is correct. When the control unit 201 determines that the chassis number of the user vehicle included in the request information is a legitimate number, it updates the user information held in the user information DB 203.

[0029] Fig. 4 is a diagram showing an example of a table configuration of user information stored in user information DB 203. As shown in Fig. 4, user information has a user ID field, a chassis number field, and an authentication date and time field. The user ID field stores an identifier (user ID) for identifying a user who uses a vehicle. The chassis number field stores a vehicle number of a user vehicle previously accepted and that has been authenticated as a legitimate number by determining that the chassis number and the vehicle registration number correspond correctly. The authentication date and time field stores information indicating the date and time when the chassis number was authenticated as a legitimate number by determining that the chassis number and the vehicle registration number correspond correctly.

[0030] Here, it is assumed that the user 10 again requests the authentication server 200 to provide vehicle information. At this time, the user 10 uses the user terminal 100 to log in to the system that provides the vehicle information provided by the authentication server 200. Specifically, the user 10 logs in to the system using the user ID and password of the user 10. Then, when the authentication using the user ID and password is completed, the control unit 201 refers to the user information held in the user information DB 203 and acquires the chassis number of the user vehicle as the legitimate chassis number. In other words, the control unit 201 omits the reception of the request information and the determination of whether the correspondence between the chassis number included in the request information and the vehicle registration number is correct, and acquires the chassis number included in the user information held in the user information DB 203. This eliminates the need to receive the request information and perform the process for authenticating the chassis number again for the user vehicle whose chassis number has been authenticated as legitimate.

[0031] It is also assumed that a time period during which the authentication server 200 can access the management server 300 (hereinafter, sometimes referred to as an "access time period") is determined in advance. At this time, the authentication server 200 accepts request information from the management server 300 during the access time period. Furthermore, the authentication server 200 does not accept request information during time periods other than the access time period to the management server 300. In this way, by not accepting request information during time periods when the management server 300 cannot be accessed, it is possible to prevent the user 10 from inputting unnecessary information into the user terminal 100.

[0032] (flowchart) Next, the process executed by the control unit 201 in the authentication server 200 in the authentication system 1 will be described with reference to Fig. 5. Fig. 5 is a flowchart of the process executed by the control unit 201 in this embodiment. This process is a process of transmitting vehicle information to the user terminal 100. This process is repeatedly executed at predetermined intervals.

[0033] In the process shown in FIG. 5, first, in S101, a login by the user 10 is received. The authentication server 200 acquires the user ID of the user 10 from the user terminal 100. Next, in S102, the user information stored in the user information DB 203 is referenced to determine whether the chassis number of the user's vehicle has been authenticated as a legitimate number in the past. If a positive determination is made in S102, the chassis number in the user information is a number that has already been authenticated as a legitimate number. Therefore, in S109, vehicle information is acquired from the management server 300 using the chassis number acquired from the user information, and output (transmitted) to the user terminal 100. Then, the processing shown in FIG. 5 is temporarily terminated.

[0034] If a negative determination is made in S102, then in S103 it is determined whether or not the current time falls within the access time period. If a negative determination is made in S103, the authentication server 200 cannot access the management server 300. Therefore, the process shown in Fig. 5 is temporarily terminated. That is, in this case, the request information is not accepted, the chassis number is not authenticated, and the vehicle information is not sent.

[0035] If a positive determination is made in S103, the request information is accepted in S104. Next, in S105, the chassis number and vehicle registration number included in the request number are acquired. Next, in S106, the vehicle information DB 303 in the management server 300 is accessed. Next, in S107, it is determined whether or not the combination of the chassis number and vehicle registration number of the user vehicle included in the request information matches the combination of the chassis number and vehicle registration number stored in the vehicle information DB 303. In this way, it is determined whether or not the correspondence between the chassis number and the vehicle registration number included in the request information is correct. If a negative determination is made in S107, the chassis number included in the request information is not a regular number. Therefore, the process shown in FIG. 5 is temporarily terminated.

[0036] If a positive determination is made in S107, the chassis number included in the request information is authenticated as being a legitimate number and acquired in S108. Therefore, in S109, vehicle information about the user's vehicle is acquired from the management server 300 using the chassis number included in the request information, and transmitted to the user terminal 100. Then, the process shown in FIG. 5 is temporarily terminated.

[0037] As described above, in the authentication system 1, the authentication server 200 accepts two numbers, the chassis number and the vehicle registration number. At this time, if the correspondence between the chassis number and the vehicle registration number is incorrect, it is assumed that the accepted chassis number contains an error. Therefore, if the correspondence between the chassis number and the vehicle registration number is incorrect, the authentication server 200 determines that the accepted chassis number is not a legitimate number. Also, if the correspondence between the chassis number and the vehicle registration number is correct, the authentication server 200 determines that the accepted chassis number is a legitimate number. In this way, it is possible to increase security during vehicle authentication.

[0038] <Second embodiment> In the first embodiment, the authentication server 200 does not accept request information during time periods other than the access time period. In other words, the authentication server 200 does not accept chassis numbers and vehicle registration numbers during time periods other than the access time period, and does not output vehicle information. In this embodiment, the authentication server 200 accepts request information and outputs vehicle information during the access time period, and if request information is accepted during time periods other than the access time period, it suspends access to the management server 300 until the access time period. Then, the authentication server 200 acquires vehicle information from the management server 300 during an accessible time period, and outputs it to the user terminal 100. Only the differences from the first embodiment will be explained below.

[0039] (flowchart) FIG. 6 is a flowchart of the process executed by the control unit 201 in this embodiment. This process is a process of authenticating the vehicle identification number of the user's vehicle when request information is received from the user terminal 100, and transmitting vehicle information to the user terminal 100. This process is repeatedly executed at predetermined intervals.

[0040] In the process shown in FIG. 6, in S201, a login by the user 10 is accepted. The authentication server 200 acquires the user ID of the user 10 from the user terminal 100. Next, in S202, the user information stored in the user information DB 203 is referenced to determine whether or not the chassis number of the user vehicle has been authenticated as a genuine number in the past. If a positive determination is made in S202, the chassis number in the user information is a number that has already been authenticated as a genuine number. Then, in S210, a determination is made as to whether or not the current time is within the access time period. If a negative determination is made in S210, the process of S210 is repeatedly executed. If a positive determination is made in S210, in S209, vehicle information is acquired from the management server 300 using the chassis number acquired from the user information, and output (transmitted) to the user terminal 100. That is, if a positive determination is made in S202, vehicle information is acquired from the management server 300 during the access time period. Then, the process shown in FIG. 5 is temporarily terminated.

[0041] Also, if a negative determination is made in S202, the request information is accepted in S203. Next, in S204, the chassis number and the vehicle registration number included in the request information are acquired. Next, in S205, it is determined whether or not the current time is within the access time period. If a positive determination is made in S205, the authentication server 200 can access the management server 300, so in S206, the vehicle information DB 303 in the management server 300 is accessed. Then, in S207, it is determined whether or not the combination of the chassis number and the vehicle registration number of the user vehicle included in the request information matches the combination of the chassis number and the vehicle registration number stored in the vehicle information DB 303. Also, if a negative determination is made in S205, the authentication server 200 cannot access the vehicle information DB 303, so the chassis number and the vehicle registration number included in the request information are temporarily stored, and the process of S205 is repeatedly executed until the current time is within the access time period. If the determination in S205 is affirmative, the process in S206 is executed, and the process in S207 is executed using the chassis number and the vehicle registration number included in the temporarily stored request information. Then, the processes in S208-S209 are executed, and the process shown in FIG. 6 is temporarily terminated.

[0042] As described above, in this embodiment, request information is accepted and vehicle information is output during the access time period, and if request information is accepted outside the access time period, access to the management server 300 is suspended until the access time period. Thereafter, the authentication server 200 acquires the vehicle information from the management server 300 during an accessible time period and outputs it to the user terminal 100. This allows the user 10 to acquire vehicle information about the user vehicle even outside the access time period. At that time, security during authentication of the user vehicle can be improved.

[0043] <Other embodiments> The above-described embodiment is merely an example, and the present disclosure may be modified as appropriate without departing from the spirit and scope of the present disclosure. Furthermore, the processes and means described in the present disclosure may be freely combined and implemented as long as no technical contradiction occurs.

[0044] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by one device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0045] The present disclosure can also be realized by supplying a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. The non-transitory computer-readable storage medium includes any type of medium suitable for storing electronic instructions, such as, for example, a magnetic disk (such as a floppy disk or a hard disk drive (HDD)), an optical disk (such as a CD-ROM, a DVD disk, or a Blu-ray disk), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, or an optical card. [Explanation of symbols]

[0046] 1. Authentication system 10 Users 100 User terminals 200 Authentication Server 201 Control section 202 Communications Department 203 User information DB 300 Management Server 301 Control section 302 Communications Department 303 Vehicle information DB

Claims

1. accepting a vehicle identification number and a vehicle registration number of the vehicle; determining whether the received vehicle identification number and the vehicle registration number correspond correctly; If it is determined that the correspondence between the chassis number and the vehicle registration number is correct, authenticating that the chassis number is a genuine number; A control unit configured to execute Information processing device.

2. The control unit is outputting vehicle information about the vehicle if the vehicle identification number is authenticated as a genuine number; and further configured to perform The information processing device according to claim 1 .

3. The receiving of the chassis number and the vehicle registration number is executed during a time period when a server device that is a source of the vehicle information can be accessed; The control unit is not accepting the chassis number and the vehicle registration number during times other than the accessible times; It is configured as follows: The information processing device according to claim 2 .

4. Outputting the vehicle information includes: the server device that is the source of the vehicle information is accessible during a time period in which the server device is accessible, and when the vehicle identification number and the vehicle registration number are received during a time period other than the accessible time period, the server device suspends access until the accessible time period; Acquiring the vehicle information from the server device during the accessible time period; and outputting the acquired vehicle information; Including, The information processing device according to claim 2 .

5. a database that stores a correspondence between the chassis number that has been accepted in the past and that has been authenticated as a genuine number by determining that the correspondence between the chassis number and the vehicle registration number is correct, and an identifier for identifying a user of the vehicle; The control unit is obtaining said identifier; and further configured to perform When the correspondence between the identifier and the chassis number is stored in the database, omitting a determination as to whether the correspondence between the chassis number and the vehicle registration number is correct, and acquiring the chassis number stored in the database as a genuine number. The information processing device according to claim 1 .

Images