JP2009110315A - User registration system and user registration method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a user registration system and a user registration method that can reduce a user's labor required for application on service using an on-vehicle apparatus and reduce cost charged to a service company. <P>SOLUTION: A granted use vehicle number granted from an apparatus number manager corresponding to an on-vehicle apparatus management number notified by the user is stored in a contractor database 11. When the user's vehicle 4 uses an account settlement service at a road side store, a communication part 21 of a road side device 2 receives an apparatus number from the on-vehicle apparatus 41, a conversion part 22 converts it into a collection use vehicle number, and a temporary ID generating part 23 generates a temporary ID. When the collection use vehicle number does not coincide with the granted use vehicle number in the contractor database 11, a temporary ID issuing part 24 issues a temporary ID to the user. The authentication of the user is performed with the temporary ID, and when the vehicle information notified by the user coincides with vehicle information acquired from an apparatus number database 3, the collection use vehicle number is written in the contractor database 11. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a system that provides a service other than the collection of road tolls using an in-vehicle device, and more particularly to a user registration system and a user registration method for registering a user in this type of service.

In recent years, ETC (Electric Toll) has been used to collect tolls on toll roads.
Collection system (registered trademark) is being introduced. The ETC is a system that performs two-way wireless communication between a roadside device installed at a toll booth and an in-vehicle device mounted on a vehicle, and transmits and receives information necessary for payment of a toll. According to ETC, the vehicle can pass through the toll gate non-stop without stopping for toll collection as in the prior art. As a result, various advantages such as elimination of congestion at the toll gate, improvement of user convenience, simplification of the facility at the toll gate, and the like can be obtained. For this reason, ETC support for toll roads is progressing, and vehicles equipped with in-vehicle devices are also increasing.

  Vehicle information such as a vehicle type and a vehicle registration number is stored in the in-vehicle device of the ETC. Further, an IC card is inserted into the vehicle-mounted device, and settlement information is stored in this IC card. The ETC is configured to calculate a toll based on vehicle information and travel information transmitted from the vehicle-mounted device to the roadside device, and to settle the toll based on the settlement information. The ETC bidirectional wireless communication uses a DSRC (Dedicated Short Range Communication) system that conforms to the ARIB (Radio Industry Association) standard.

  The device number uniquely assigned is stored in the on-board device of the ETC, and the roadside device can receive the device number. The device number is uniquely assigned to the vehicle-mounted device and is associated with vehicle information such as the vehicle-mounted device management number notified to the user when setting up the vehicle-mounted device, the type of vehicle in which the vehicle-mounted device is mounted, the vehicle registration number, etc. ing. The equipment number and vehicle information related to the equipment number are centrally managed by the equipment number manager ORSE (Road System Advancement Promotion Organization).

  Recently, it has been considered to open up some of the functions of the in-vehicle device for private use. Using the in-vehicle device, settlement of the product price at the roadside store, entrance / exit management of the parking lot, and car type It is expected to provide various services such as the distribution of traffic information in response. A service provider who performs such a service manages the identification information of the vehicle-mounted device in order to authenticate the vehicle-mounted device when providing the service. Here, if a device number is used as identification information, if one service provider leaks identification information, it will affect other service businesses and ETC payment services, making it difficult to ensure security. .

  Then, the authentication system which ensures security by using a different use vehicle number for every service provider as identification information of onboard equipment is proposed (refer nonpatent literature 1). According to this authentication system, a plurality of service providers manage different use vehicle numbers as identification information. Therefore, even if a certain service provider leaks identification information, it is possible to prevent other services and ETC payment services from being affected.

In this authentication method, when the user applies for the service, the OBE management number notified when the OBE is purchased is reported to the service provider. The service provider notifies the device number manager of the vehicle-mounted device management number, and a corresponding vehicle number is issued, and a database is constructed by associating the personal information of the user with the vehicle number. The roadside device installed by the service provider introduces a conversion function for converting the equipment number into the vehicle number used. The roadside device converts the device number received from the vehicle-mounted device into a use vehicle number, and queries the service provider's database for the presence or absence of the use vehicle number to authenticate the on-vehicle device.
JP 2002-216251 A Study Group on Utilization of ETC Related Technology, “About Utilization of ETC On-board Device Number”, [online], Internet <URL: http://www.mlit.go.jp/road/press/press06/20060317/32. pdf>

  However, in the authentication method using the vehicle number used, if there is an error in the vehicle-mounted device management number reported by the user, an incorrect vehicle number that does not correspond to the user vehicle-mounted device is stored in the database. An error in the use vehicle number in the database becomes apparent only when authentication fails when the vehicle-mounted device and the roadside device communicate with each other to receive service. Thereafter, the user needs to perform the application procedure again, and there is an inconvenience that the user is burdened.

  Further, when the user applies for the service, if the on-vehicle device management number is lost, it is necessary to read the on-vehicle device management number from the on-vehicle device, which is troublesome. In other words, the OBE control number is written on the product slip affixed to the OBE, but the product slip is affixed to the bottom of the housing of the OBE, so remove the OBE from the vehicle It is necessary to visually check. Moreover, when the onboard equipment management number cannot be visually recognized for some reason, it is necessary to read the onboard equipment management number using the onboard equipment reading device which has a communication function. In order to perform such work, the user needs to bring the vehicle to a predetermined service window, which is inconvenient in that the burden on the user is heavy. In addition, the service provider needs to install a service window with work facilities, which is inconvenient in that the cost burden is high.

  Accordingly, an object of the present invention is to provide a user registration system and a user registration method that can reduce the burden on the user when applying for a service using the vehicle-mounted device and reduce the cost on the service provider. It is in.

In order to solve the above problem, the user registration system of the present invention is a user registration system for a service using an on-vehicle device,
A service provider database that stores identification information for identifying the OBE;
Based on the administrator database that stores the unique identification information uniquely assigned to the OBE and the OBE management information corresponding to this unique identification information, the OBE management information reported by the user of the OBE An identification information acquisition unit for acquiring delivery identification information obtained by converting the corresponding unique identification information;
A delivery identification information writing unit for writing the delivery identification information as identification information in the service provider database;
A communication unit that performs two-way wireless communication with the vehicle-mounted device, a conversion unit that converts the unique identification information received from the vehicle-mounted device by the communication unit to generate sampling identification information, and a temporary ID corresponding to the sampling identification information are generated A roadside device having a temporary ID generation unit
A collation unit that collates whether or not identification information that matches the collection identification information exists in the service provider database;
A temporary ID issuing unit for issuing the temporary ID to the user;
A temporary storage unit for storing the collection identification information and the temporary ID;
When the collation result by the collation unit is negative and the temporary ID reported by the user matches the temporary ID stored in the temporary storage unit, the temporary storage unit stores the temporary ID in the service provider database. And a collection identification information writing unit for writing the collected collection identification information as identification information.

  According to the above configuration, the service provider using the vehicle-mounted device stores the delivery identification information issued based on the administrator database as identification information in the service provider database, and receives the service using this identification information. Authenticate the in-vehicle device. A service provider installs a roadside device in a roadside store or a parking lot that provides the service.

  When the user uses the service, two-way wireless communication is performed between the communication unit of the roadside device and the vehicle-mounted device, the unique identification information stored in advance in the vehicle-mounted device is received by the communication unit, and the collected identification information is converted into the conversion unit. Generated by. When there is no identification information that matches the collection identification information in the service provider database, it is possible to confirm the identity of the user by the temporary ID generated by the temporary ID generation unit corresponding to the collection identification information. . That is, the user declares a temporary ID, and performs identity verification based on whether or not the temporary ID matches the temporary ID stored in the temporary storage unit. When the identity verification is successful, the collection identification information actually collected by the roadside device is written as identification information in the service provider database. Therefore, for example, even when unauthorized delivery identification information is registered in the service provider database due to an error in the in-vehicle device management information reported by the user at the time of application, the user declares a temporary ID to the service provider. Thus, the correct collection identification information is rewritten. As a result, since the user can use the service without re-applying the application procedure, the burden on the user can be reduced.

  In addition, since the user can use the service without re-declaring the OBE management information, even if the OBE management information is lost, the user can remove the OBE from the vehicle as before and remove the product slip. It is not necessary to visually check the in-vehicle device management information or to read the in-vehicle device management information from the on-vehicle device by the on-vehicle device reader. Therefore, the burden on the user can be greatly reduced. In addition, since the service provider does not need to set up a window for reading the in-vehicle device management information, the cost burden can be greatly reduced.

  In addition, even when the user has used the roadside device without applying for the service, the temporary ID issued by the roadside device is then applied to make an application, which has already been collected from the vehicle-mounted device. The collection identification information is written in the service provider database. Therefore, the user does not need to report the in-vehicle device management information at the time of application. As a result, the user application procedure can be simplified. In addition, even if the in-vehicle device management information is lost, it is not necessary to read out the in-vehicle device management information, so that the application procedure can be performed with less effort than before.

  In addition, the temporary issuing unit may issue a temporary ID before the verification unit performs authentication based on the collection identification information. For example, when parking lot entry / exit management is performed as a service, by issuing a temporary ID when entering the parking lot, the user declares the temporary ID before leaving the parking lot, and the service application procedure It can be performed. Alternatively, the temporary ID issuing unit may issue a temporary ID when the verification unit performs authentication based on the collection identification information and the verification result is negative.

  Furthermore, according to the user registration system of the present invention, since identification information different for each service provider is used for authentication of the vehicle-mounted device without using the unique identification information, the identification information leaks from one service provider. However, it can prevent other services and road toll settlement services from being affected.

In the user registration system according to an embodiment, vehicle information related to a vehicle on which the vehicle-mounted device is mounted is stored in the manager database in association with the unique identification information.
A vehicle information acquisition unit for acquiring vehicle information corresponding to the unique identification information corresponding to the collection identification information from the administrator database;
The collection identification information writing unit writes the collection identification information in the service provider database when the vehicle information reported by the user matches the vehicle information acquired by the vehicle information acquisition unit.

  According to the above embodiment, when the user uses the service and the authentication based on the collection identification information fails, the temporary ID and vehicle information are reported by the user. If the vehicle information reported by the user matches the vehicle information acquired from the administrator database by the vehicle information acquisition unit in addition to the temporary ID matching the temporary ID stored in the temporary storage unit, the collection identification Information is written in the service provider database as identification information. In this way, since the identity verification is performed with the temporary ID and the vehicle information, unauthorized user registration due to transshipment or impersonation of the vehicle-mounted device can be prevented.

The user registration system according to an embodiment includes a temporary ID issuing unit that issues a temporary ID to a user in response to an application for a user's service.
The service provider database is configured to store the vehicle information reported by the user at the time of applying for the service in association with the identification information, and to identify the temporary ID issued by the temporary ID issuing unit. It is formed to store in association with information and vehicle information,
The collection identification information writing unit has a temporary ID that matches the temporary ID declared by the user in the service provider database, and vehicle information corresponding to the temporary ID in the service provider database is the vehicle information. If the vehicle information acquired by the acquisition unit matches, the collection identification information is written in the service provider database.

  According to the above embodiment, when the user uses the service and the authentication based on the collection identification information fails, the temporary ID and temporary ID are subsequently reported by the user. In addition to the temporary ID matching the temporary ID stored in the temporary storage unit, a temporary ID that matches the temporary ID declared by the user exists in the service provider database, and the vehicle corresponds to this temporary ID. When the information matches the vehicle information acquired from the administrator database by the vehicle information acquisition unit, the collection identification information is written as identification information in the service provider database. Thus, since the user's identity is confirmed with the temporary ID, the temporary ID, and the vehicle information, the identity can be strictly confirmed, and illegal user registration can be effectively prevented.

  The user registration system according to an embodiment includes a dummy information input unit that inputs dummy information as identification information of the service provider database when the vehicle-mounted device management information is not reported from the user at the time of applying for a service.

  According to the above embodiment, when the in-vehicle device management information is not reported from the user due to loss of the in-vehicle device management information or the like, the dummy information input unit inputs the dummy information as identification information into the service provider database. . As a result, when the user uses the service, authentication of the vehicle-mounted device fails, and a temporary ID is issued from the roadside device accordingly. When the user declares the temporary ID, correct identification information is written in the service provider database without performing the application procedure again. Thus, since the user can apply for the service without reporting the vehicle-mounted device management information, the burden on the user can be reduced.

  The dummy information is information other than the identification information and may be information indicating that the in-vehicle device management information is not declared, and various forms such as a blank, a number, a character, or a combination thereof may be used. Can be adopted.

  In the user registration system according to an embodiment, a predetermined expiration date is set for the temporary ID.

  According to the above embodiment, by limiting the validity period of the temporary ID when writing the collection identification information to the service provider database within the predetermined validity period, other persons can be illegally caused by the loss or theft of the issued temporary ID. The inconvenience of performing user registration can be prevented, and as a result, the security of the service provider database can be secured at a high level.

  In the user registration system according to an embodiment, the temporary ID issuing unit is a printing unit that prints the temporary ID.

  According to the above-described embodiment, for example, the printing unit is incorporated into a roadside store register, a parking lot entrance ticketing device, a fee settlement device, or the like, and a temporary ID is printed on a receipt of a product purchase price. An ID can be issued to the user.

  According to another embodiment, the temporary ID issuing unit can be formed by a display device that displays a temporary ID. When the temporary ID issuing unit is formed by the display device, the store ID may be handwritten on the slip or the like by the store staff and handed over to the user.

In the user registration system according to an embodiment, the roadside device includes a recognition unit that recognizes vehicle license plate information.
A license plate information storage unit that stores the license plate information recognized by the recognition unit of the roadside device in association with the collection identification information,
When the license plate information stored in the license plate information storage unit matches the license plate information in the vehicle information acquired by the vehicle information acquisition unit, the collection identification information writing unit Write the collection identification information in the database.

  According to the said embodiment, the license plate information of a vehicle is recognized by the recognition part of a roadside apparatus, and the vehicle by which onboard equipment is mounted is specified. When the license plate information recognized by the recognition unit and stored in the license plate information storage unit matches the license plate information in the vehicle information acquired by the vehicle information acquisition unit, the on-vehicle device is mounted on a legitimate vehicle. The collection identification information is written in the service provider database. Therefore, it is possible to effectively prevent the inconvenience that unauthorized collection identification information is written in the service provider database due to replacement of the vehicle-mounted device. The recognition unit includes, for example, an imaging unit that captures a license plate of a vehicle and generates image data, and an image processing unit that extracts license plate information from the image data generated by the imaging unit. Can do.

The user registration method of the present invention is a user registration method for a service using an in-vehicle device,
Based on the administrator database that stores the unique identification information uniquely assigned to the OBE and the OBE management information corresponding to this unique identification information, the OBE management information reported by the user of the OBE Obtaining grant identification information obtained by converting the corresponding unique identification information;
Writing the delivery identification information as identification information in the service provider database;
The roadside device performs two-way wireless communication with the vehicle-mounted device to receive unique identification information, converts the received unique identification information to generate collection identification information, and generates a temporary ID corresponding to the collection identification information And steps to
Collating whether or not identification information that matches the collection identification information exists in the service provider database; and
Issuing the temporary ID to the user;
Storing the collection identification information and the temporary ID in a temporary storage unit;
When the identification information that matches the collection identification information does not exist in the service provider database, and the temporary ID reported by the user matches the temporary ID stored in the temporary storage unit, the service provider database And writing the collection identification information stored in the temporary storage unit as identification information.

  According to the above configuration, the service provider using the vehicle-mounted device stores the delivery identification information issued based on the administrator database as identification information in the service provider database, and receives the service using this identification information. Authenticate the in-vehicle device. A service provider installs a roadside device in a roadside store or a parking lot that provides the service.

  When the user uses the service, the roadside device performs two-way wireless communication with the on-vehicle device, receives the unique identification information stored in advance in the on-vehicle device, converts the received unique identification information, and collects the collected identification information. At the same time, a temporary ID corresponding to this collection identification information is generated. When there is no identification information that matches the collection identification information in the service provider database, the identity of the user can be confirmed by the temporary ID corresponding to the collection identification information. That is, the user declares a temporary ID, and identity verification is performed based on whether or not the reported temporary ID matches the temporary ID stored in the temporary storage unit. When the identity verification is successful, the collection identification information actually collected by the roadside device is written in the service provider database as identification information. Therefore, for example, even if the incorrect delivery identification information is registered in the service provider database due to an error in the OBE management information reported by the user at the time of application, the user must declare a temporary ID to the service provider. Thus, the correct collection identification information can be rewritten. As a result, since the user can use the service without re-applying the application procedure, the burden on the user can be reduced.

  In addition, since the user can use the service without re-declaring the OBE management information, even if the OBE management information is lost, the user can remove the OBE from the vehicle as before and remove the product slip. It is not necessary to visually check the in-vehicle device management information or to read the in-vehicle device management information from the on-vehicle device by the on-vehicle device reader. Therefore, the burden on the user can be greatly reduced. In addition, since the service provider does not need to set up a window for reading the in-vehicle device management information, the cost burden can be greatly reduced.

  In addition, even if the user uses the roadside device without applying for the service, the collection identification information already collected from the vehicle-mounted device can be obtained by presenting the temporary ID and then applying. Written to the database. Therefore, the user does not need to report the in-vehicle device management information. As a result, the user application procedure can be simplified. Moreover, even when OBE management information is lost, the effort which reads OBE management information can be reduced.

  In addition, the temporary ID may be issued before authentication based on the collection identification information. For example, when parking lot entry / exit management is performed as a service, by issuing a temporary ID when entering the parking lot, the user declares the temporary ID before leaving the parking lot, and the service application procedure It can be performed. Alternatively, the temporary ID may be issued when the verification by the collection identification information is performed and the collation result is negative.

  Furthermore, according to the user registration method of the present embodiment, the identification information leaks because one service provider uses different identification information for each service provider without using the unique identification information. Even so, it is possible to prevent other services and road toll payment settlement services from being affected.

  As described above, even if the in-vehicle device authentication fails due to an error in the in-vehicle device management information reported by the user, by performing identity verification with the temporary ID presented by the user, The collection identification information actually collected from the vehicle-mounted device can be registered in the service provider database. Therefore, the user can use the service without declaring accurate OBE management information. Therefore, the user can reduce the burden of searching for the lost OBE management information. The business operator does not need to set up a reading window for the in-vehicle device management information, and can reduce the cost burden.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing a user registration system as an embodiment of the present invention. This user registration system is used for registering a user to a provider that provides services using an on-board device of ETC. In the service using the on-board device of ETC, the used vehicle number obtained by converting the device number uniquely assigned to the on-vehicle device is used as identification information. The used vehicle number is given by being converted into a different value for each service by a device number manager who manages the device number of the vehicle-mounted device. By authenticating the vehicle-mounted device using the use vehicle number, the user can receive various services without attaching a settlement IC card as in the prior art. Also, instead of using device numbers uniquely assigned to all in-vehicle devices, by using a different vehicle number for each service, even if one service provider leaks identification information, other operators And the ETC toll payment can be prevented from being affected. Therefore, the security of various services using the vehicle-mounted device can be highly maintained. In this embodiment, a payment service for merchandise prices at roadside stores will be described. However, the present invention is also applicable to other services such as entrance / exit management of parking lots and distribution of traffic information according to vehicle types. Applicable.

  The user registration system according to the present embodiment is roughly configured by an operator server 1 installed in a service provider that provides a service, and a roadside device 2 installed in a roadside store or the like by the service provider. The roadside device 2 and the operator server 1 are connected to each other to transmit and receive information. The business operator server 1 is connected to the device number administrator's administrator server 3 to transmit and receive information to and from each other. In addition, the roadside apparatus 2 may be installed by the provider who cooperates with the service provider. This user registration system is used when a service provider registers a user as the user of the vehicle 4 in which the vehicle-mounted device 41 is installed makes a service application.

  The business operator server 1 is roughly composed of a contractor database 11 as a service business operator database and a business operator processing device 12 connected to the contractor database 11. The contractor database 11 is configured to store a use vehicle number as identification information of the vehicle-mounted device 41, vehicle information of the vehicle 4 on which the vehicle-mounted device 41 is mounted, and user personal information. The vehicle information includes vehicle inspection information such as the type of the vehicle 4, the vehicle registration number, the number of axes, the weight, the body color, and the like. The personal information includes the user's name, address, credit card number, and the like.

  The operator processing device 12 includes a use vehicle number acquisition unit 13 as an identification information acquisition unit that acquires a use vehicle number from the administrator server 3, a database control unit 14 that reads and writes information from and to the contractor database 11, The collation unit 15 that collates the use vehicle number in the contractor database 11, the vehicle information acquisition unit 16 that obtains vehicle information from the administrator server 3, and the collection use vehicle number collected by the roadside device 2 are associated with the temporary ID. And a temporary storage unit 17 for storing. Further, the business entity processing apparatus 12 includes a temporary ID issuing unit 18 that issues a temporary ID at the time of user application. The temporary ID issued by the temporary ID issuing unit 18 is written in the contractor database 11 in association with personal information and vehicle information. Further, the business entity processing apparatus 12 includes a temporary password input unit 19 into which a temporary password set by a user is input when a temporary ID is issued. The temporary password is written in the contractor database 11 in association with the temporary ID. That is, the temporary password storage area of the contractor database 11 functions as a temporary password storage unit.

  The provider processing device 12 is a computer composed of a CPU, a storage device, an input / output device, a communication module, and the like. A program stored in the storage device is executed by the CPU, and the above-described vehicle number acquisition unit 13 is used. , Database controller 14,... Are configured to perform the functions of a temporary password input unit 19. The business operator processing device 12 may be configured by a plurality of computers, and each of the above units may be configured by a circuit. The vehicle number acquisition unit 13 and the vehicle information acquisition unit 16 may each be formed by a transmission / reception device separated from the computer, or may be shared by a single transmission / reception device. The business server 1 can be connected to a credit server 5 of a credit card company.

  The roadside device 2 is installed in a drive-through type roadside store, and a communication unit 21 that communicates with the vehicle-mounted device 41, a conversion unit 22 that converts a device number read from the vehicle-mounted device 41 and generates a use vehicle number, A temporary ID generation unit 23 that generates a temporary ID in accordance with the generation of a use vehicle number by the conversion unit 22, a temporary ID issue unit 24 that issues this temporary ID to the user, and an antenna 25. The communication unit 21 has a DSRC communication control function and is connected to the antenna 25 that transmits and receives 5.8 GHz band radio waves. The communication unit 21, the conversion unit 22, and the temporary ID generation unit 23 are configured by a processing device including a CPU, a storage device, an input / output device, a communication module, and the like. The processing device is connected to a store register, and the temporary ID issuing unit 24 is composed of a receipt printing unit of the register. The receipt printing unit as the temporary ID issuing unit 24 prints the temporary ID on the receipt of the product purchase price. The conversion part 22 is comprised with the same conversion software as what is stored in the use vehicle number production | generation part 33 which the administrator server 3 mentioned later has.

  The operator server 1 and the roadside apparatus 2 having these configurations are installed for each of a plurality of service operators A, B, C..., And the operator server 1 of each service operator is connected to the administrator server 3. ing. In addition, the roadside apparatus 2 may be installed by the provider who cooperates with the service provider.

  The administrator server 3 is roughly composed of a device number database 31 as an administrator database and an administrator processing device 32 connected to the device number database 31. The device number database 31 is provided with a device number as unique identification information uniquely assigned to the vehicle-mounted device 41, a vehicle-mounted device management number as vehicle-mounted device management information corresponding to this device number, and the device number. The vehicle information related to the vehicle 4 on which the vehicle-mounted device 41 is mounted is stored. The vehicle information includes the type of the vehicle 4, the vehicle registration number, the number of axes, the weight, the body color, and the like. These pieces of information are registered in the device number database 31 along with a setup procedure performed when the user installs the vehicle-mounted device 41 in the vehicle 4. The administrator processing device 32 includes a use vehicle number generation unit 33 that converts a device number and generates a use vehicle number in response to a request from the business operator processing device 12. The used vehicle number generation unit 33 generates a used vehicle number for each service provider by converting a device number with conversion software that is different for each service provider. Further, the manager processing device 32 includes a vehicle information output unit 34 that transmits vehicle information to the business operator processing device 12 in response to a request from the business operator processing device 12. The administrator processing device 32 is a computer that includes a CPU, a storage device, an input / output device, a communication module, and the like. A program stored in the storage device is executed by the CPU, and the above-described use vehicle number issuing unit 33 and The vehicle information output unit 34 is configured to function.

  The vehicle-mounted device 41 mounted on the user's vehicle 4 includes a storage unit in which a device number is stored, and a communication unit that performs DSRC communication with the roadside device 2.

  FIG. 2 is a flowchart showing the flow of information exchanged between the operator server 1 and the roadside device 2, the administrator server 3, and the vehicle-mounted device 41 that constitute the user registration system when the user applies for the service. It is. FIG. 3 is a flowchart showing a procedure performed from the user application to the completion of registration among the user, the service provider, and the device number manager. The operation of the user registration system will be described below along the flowchart of FIG.

  First, the user declares the vehicle-mounted device management number given to the vehicle-mounted device 41 at the time of setup, and reports personal information such as name and address, vehicle information such as the type of vehicle 4 and vehicle registration number, and the like. An application is made (S401). The service provider accepts the user application (S101), issues a temporary ID by the temporary ID issuing unit 18, and receives a temporary password setting from the user (S102). The temporary password set by the user is input to the temporary password input unit 19 and stored in the contractor database 11 in association with the temporary ID. The personal information and vehicle information reported by the user are stored in the contractor database 11 in association with the temporary ID. Subsequently, the personal information of the user is transmitted from the business entity processing apparatus 12 to the credit server 5 of the credit card company, and the credit examination of the user is performed (S103). If the result of the credit examination is affirmative, the credit card number is associated with the temporary ID and written in the contractor database 11. Then, the use vehicle number acquisition part 13 transmits the onboard equipment management number which the user reported to the manager processing apparatus 32, and issues a use vehicle number issue request (S104). The administrator processing device 32 accesses the device number database 31 and extracts a device number corresponding to the vehicle-mounted device management number received from the business operator processing device 12 (S201). The extracted device number is converted by the use vehicle number generation unit 33 to generate the use vehicle number (S202). This use vehicle number (hereinafter referred to as a grant use vehicle number) is transmitted from the administrator processing device 32, received by the use vehicle number acquisition unit 13 of the business entity processing device 12, and is then contracted by the contractor database 11 by the database control unit 14. (S105). At this time, the database control unit 14 functions as a delivery identification information writing unit. When registration of the issued vehicle number to the contractor database 11 is completed, the user is notified of the completion of temporary registration (S106).

  The user receives a notification of the completion of temporary registration (S402), and then visits the roadside store with the vehicle 4 and pays for the merchandise purchased at the store using the settlement service of the vehicle-mounted device 41 (S403). In order to start the payment service, the communication unit 21 of the roadside apparatus 2 performs two-way wireless communication with the vehicle-mounted device 41 via the antenna 25, and receives the device number stored in the vehicle-mounted device 41 (S301). Subsequently, the conversion unit 22 converts the device number to generate a collection and use vehicle number (S302), and the temporary ID generation unit 23 generates a temporary ID corresponding to the collection and use vehicle number (S303). The processing device of the roadside device 2 transmits the collection use vehicle number and the temporary ID generated by the conversion unit 22 to the business operator processing device 12. The business entity processing device 12 stores the collected and used vehicle number and temporary ID received from the roadside device 2 in the temporary storage unit 17 (S107), and the collating unit 15 makes a contract for the issued and used vehicle number that matches the collected and used vehicle number. It is verified whether or not the user database 11 exists (S108). If the delivery vehicle number that matches the collected vehicle number does not exist in the contractor database 11, it is determined that the authentication for the service of the in-vehicle device 41 has failed, and the business operator is informed that payment by credit card number is impossible. It transmits to the roadside apparatus 2 from the processing apparatus 12 (step 109). The processing device of the roadside device 2 that has received the disapproval information displays on the display unit of the register that the credit card payment is not possible (S304), and the store clerk viewing this display requests the user to pay with cash. When the user settles with cash (S404), the temporary ID issuance unit 24 constituted by the register printing unit prints the temporary ID on the receipt of the product purchase price (S305), and the receipt is handed to the user. The user acquires a temporary ID (S405). The temporary ID issuing unit may be configured by a mail transmitting unit installed in the processing device of the business processor 12 or the roadside device 2 in addition to the register printing unit. The temporary ID issuing unit configured by the mail transmitting unit transmits an e-mail including the temporary ID to a predetermined mail address with the completion of the user's cash settlement. The e-mail address is set in advance by the user at the time of application. Thereby, a temporary ID can be notified to a user with little effort, while exhibiting a high secret maintenance function.

  Thereafter, the user reports to the service provider that the payment service cannot be used at the roadside store (S406), and the temporary ID described in the receipt, the temporary ID received at the time of application, and the time set at the time of application are set. A temporary password is declared (S407). When the notification by the user and the declaration of temporary ID, etc. are made by telephone or window visit, they are made to the staff of the telephone or window, and the temporary ID or the like is input to the business entity processing apparatus 12 by the staff. Alternatively, the notification that the service is unavailable and the declaration of the temporary ID may be made through the Internet. That is, a user connects a personal computer or a mobile phone to the Internet, connects to a website specified by a URL notified in advance, and writes a temporary ID or the like on this website. The temporary ID written on the website is transmitted to the business operator processing device 12.

  The business entity processing apparatus 12 collates the temporary ID, temporary ID, and temporary password reported by the user with the temporary ID stored in the temporary storage unit 17 and the temporary ID and temporary password stored in the contractor database 11. (S110). If the collation result is affirmative and the identity of the user is confirmed, the collected and used vehicle number associated with the temporary ID is transmitted to the administrator processing device 32 and associated with the device number corresponding to the collected and used vehicle number. Request for provision of vehicle information is requested (S111). In response to a request from the operator processing device 12, the vehicle information output unit 34 of the manager processing device 32 displays vehicle information associated with the device number corresponding to the collection use vehicle number, that is, the vehicle type and vehicle registration number. Extracted from the device number database 31 (S203). Subsequently, the extracted vehicle information is transmitted to the business operator processing device 12 (S204). The business entity processing device 12 receives the vehicle information from the manager processing device 32 (S112), and collates this vehicle information with the vehicle information reported from the user and stored in the contractor database 11 (S113). When both vehicle information matches and the collation result is affirmative, the database control unit 14 writes the collected use vehicle number as the regular use vehicle number in the contractor database 11 (S114). At this time, the database control unit 14 functions as a collection identification information writing unit. If the vehicle information received from the administrator processing device 32 and the vehicle information stored in the contractor database 11 do not match and the collation result is negative, the vehicle-mounted device 41 may be replaced. The user is notified of the re-setup of the vehicle-mounted device 41 (S115). When the collected use vehicle number is written in the contractor database 11 as a regular use vehicle number (S114), the temporary ID and the temporary password of the contractor database 11 are registered as the normal ID and the normal password (S116). When the registration of the regular ID and the regular password is completed, the user is notified that the regular registration has been performed (S117), and the user receives a regular registration notification (S408).

  Thus, according to the user registration system of the present embodiment, the delivery vehicle number that matches the collected vehicle number collected from the vehicle-mounted device 41 does not exist in the contractor database 11 and the authentication of the vehicle-mounted device has failed. Even so, after the user's identity is confirmed by the temporary ID, temporary ID, and temporary password, the collection use vehicle number is written in the contractor database 11. Therefore, even when an unauthorized use vehicle number is registered in the contractor database 11 due to an error in the vehicle-mounted device management information reported by the user, the user gives the temporary ID, temporary ID, and temporary password to the service provider. You can register the correct vehicle number by reporting. Therefore, since the user can use the service without re-applying the application procedure, the burden on the user can be reduced.

  The temporary ID and temporary password do not necessarily need to be set, and the user's identity may be confirmed using only the temporary ID.

  In this embodiment, although the case where the onboard equipment management number was declared by the user at the beginning of reception was described, the user registration system of this embodiment can accept even when the user loses the onboard equipment management number. . That is, in step S401 in FIG. 3, when the user does not declare the vehicle-mounted device management number but declares only the personal information and the vehicle information and applies for the service, the use by the use vehicle number acquisition unit 13 in step S104. Without making a request for issuing a car number, the database control unit 14 writes a dummy number (dummy information) as a used car number in the contractor database 11. At this time, the database control unit 14 functions as a dummy information input unit. If it does so, in Step S108, since the use vehicle number which corresponds with the collection use vehicle number does not exist in contractor database 11, authentication to the service of onboard equipment 41 fails. Thereafter, by performing the same procedure as in the above embodiment, the correct collection and use vehicle number can be written in the contractor database 11. Thus, since it is possible to apply for the service without reporting the in-vehicle device management information, it is possible to reduce the burden on the user.

  Therefore, even when the user loses the OBE management number, the OBE 41 is removed from the vehicle 4 as in the past, and the OBE management number of the product slip is visually recognized. There is no need to read the OBE management number from. As a result, the burden on the user can be greatly reduced. In addition, since the service provider does not need to set up a window for reading out the in-vehicle device management number, the cost burden can be greatly reduced.

  In the flowchart of FIG. 3, the case where the user uses the roadside device 2 while applying for the service has been described. However, the user registration system according to the present embodiment uses the roadside device 2 when the user has not applied for the service. Even when it is used, subsequent user application procedures can be simplified. The procedure in the user registration system in this case will be described with reference to the flowchart of FIG.

  First, a user who has not applied for a service visits a roadside store with the vehicle 4 and tries to pay for a product purchased at the store using the settlement service of the in-vehicle device 41 (S451). In order to start the payment service, the communication unit 21 of the roadside apparatus 2 performs two-way wireless communication with the vehicle-mounted device 41, receives the device number from the vehicle-mounted device 41 (S351), and the conversion unit 22 converts the device number and collects it. A use vehicle number is generated (S352), and the temporary ID generation unit 23 generates a temporary ID corresponding to the collected use vehicle number (S353). The processing device of the roadside device 2 transmits the collection use vehicle number and the temporary ID generated by the conversion unit 22 to the business operator processing device 12. The business processor 12 stores the received collected vehicle number and the temporary ID in the temporary storage unit 17 (S151), and the collating unit 15 stores the issued vehicle number that matches the collected vehicle number in the contractor database 11. It is checked whether or not it exists (S152). Naturally, since there is no delivery use vehicle number that is the same as the collection use vehicle number of the user who has not applied for it, the authentication for the service of the vehicle-mounted device 41 fails. Accordingly, the impossibility information indicating that the credit card payment is impossible is transmitted to the roadside device 2 (S153). The processing device of the roadside device 2 that has received the disapproval information displays on the display unit of the register that the credit card payment is not possible (S354), and the store clerk viewing this display requests the user to pay with cash. When the user settles with cash (S452), the register printing unit (temporary ID issuing unit 24) prints the temporary ID on the receipt (S355), and the receipt is handed over to the user to obtain the temporary ID. (S453).

  Thereafter, the user makes a service application by reporting the temporary ID described in the receipt to the service provider (S454). That is, the user applies for the service by declaring personal information such as name and address and vehicle information such as the type of vehicle 4 and vehicle registration number in addition to the temporary ID. The service provider accepts the application (S154), and stores the personal information and vehicle information reported by the user in the contractor database 11. Subsequently, the personal information of the user is transmitted from the business entity processing device 12 to the credit server 5 of the credit card company, and the credit examination of the user is performed (S155). When the result of the credit examination is affirmative, the business entity processing apparatus 12 collates the temporary ID reported by the user with the temporary ID stored in the temporary storage unit 17 (S156). If the collation result is affirmative and the identity of the user is confirmed, the collected and used vehicle number associated with the temporary ID is transmitted to the administrator processing device 32 and associated with the device number corresponding to the collected and used vehicle number. Request for provision of vehicle information is made (S157). The vehicle information output unit 34 of the manager processing device 32 extracts the vehicle information associated with the device number corresponding to the collection use vehicle number from the device number database 31 in response to a request from the business operator processing device 12 (S251). ), And transmits the extracted vehicle information to the operator processing device 12 (S252). The business entity processing device 12 receives the vehicle information from the manager processing device 32 (S158), and collates this vehicle information with the vehicle information reported from the user and stored in the contractor database 11 (S159). When both vehicle information matches and the collation result is affirmative, the database control unit 14 writes the collected use vehicle number as the regular use vehicle number in the contractor database 11 (S160). When the collation result in step S159 is negative, there is a possibility that the vehicle-mounted device 41 may be replaced, so the user is notified of the re-setup of the vehicle-mounted device 41 (S161). When the collected use vehicle number is written in the contractor database 11 as a regular use vehicle number (S160), a regular ID is issued and a password is set by the user. The regular ID and password are stored in the contractor database 11, the registration is notified to the user (S162), and the user receives a regular registration notification (S408).

  Thus, according to the user registration system of the present embodiment, even when the user uses the roadside device 2 without applying for the service, the temporary ID issued by the roadside device 2 is presented to apply for the service. By performing the registration, it is possible to register for the service using the collection vehicle number already collected from the vehicle-mounted device 41. Therefore, since the user does not need to report the in-vehicle device management number, the user application procedure can be simplified. Further, even when the user loses the OBE management number, the OBE 41 is removed from the vehicle 4 and the product slip is visually recognized, or the OBE management number is read from the OBE 41 by the OBE reader. There is no need to do. Therefore, the burden on the user can be greatly reduced, and the cost burden on the service provider can be greatly reduced.

  In the above embodiment, it is preferable to set an expiration date of, for example, 24 hours from issuance to the temporary ID. That is, in step S305 (or S354), the processing device records the issuance time when the temporary ID issuance unit 24 of the roadside device 2 has issued the temporary ID to the user, and the data indicating the issuance time is stored in the operator processing device 12. Send. In step S407 (or S454), the business entity processing apparatus 12 performs collation in step S110 (or S156) when the time when the temporary ID is reported by the user is within 24 hours from the issue time. Thereby, the security of the contractor database 11 can be maintained at a high level by limiting the opportunity to write the collected and used vehicle number in the contractor database 11 within a predetermined time. The expiration date may be other than 24 hours from the temporary ID issuance time.

  In the above embodiment, when a temporary ID is issued, a password may be set from the user. That is, the roadside device 2 is provided with a password input unit, and in step S405 (or S453), the temporary ID issued by the temporary ID issuing unit 24 is handed to the user, and the user is prompted to input the password to the password input unit. A password input to the password input unit (hereinafter referred to as a temporary password) is transmitted to the business operator processing device 12, and the temporary password is stored in a temporary password storage unit provided in the business operator processing device 12. In step S407 (or step S454), the user declares a temporary password in addition to the temporary ID and the like. In step 110 (or S156), the verification unit stores the reported temporary password and the password storage unit. Check against a temporary password. Thus, in addition to the temporary ID, the temporary ID, and the temporary password, by performing identity verification with the temporary password, it is possible to effectively prevent impersonation of another person and prevent the inconvenience of writing illegal information in the contractor database 11. .

  Moreover, in the said embodiment, the camera which image | photographs the license plate of the vehicle 4 is installed in the roadside apparatus 2, the vehicle registration number of a license plate is recognized from the image image | photographed with this camera, and this vehicle registration number is used. The identity of the user may be verified. That is, as the communication unit 21 starts communication with the vehicle-mounted device 41, the number plate of the vehicle 4 is photographed by the camera. The captured image is transferred to the processing device of the roadside device 2, and an image recognition program stored in the processing device is executed to extract a vehicle registration number as license plate information from the image. The extracted vehicle registration number is transmitted to the business entity processing apparatus 12 in association with the collection use vehicle number. The business entity processing device 12 collates whether or not the extracted vehicle registration number matches the vehicle registration number in the vehicle information output from the vehicle information output unit 34 of the manager processing device 32, and the collation result Is positive, the collection use vehicle number is written in the contractor database 11. Thus, it is possible to confirm that the vehicle-mounted device 41 is mounted on the appropriate vehicle 4 by comparing the registration number of the license plate of the vehicle 4 with the registration number of the device number database 31. As a result, it is possible to detect an unauthorized replacement of the vehicle-mounted device 41, and it is possible to prevent the inconvenience of unauthorized sampling identification information being written in the contractor database 11.

  Further, in the above embodiment, the business operator processing device 12 succeeds in verifying the identity of the user by the temporary ID, temporary ID, and temporary password, and further from the vehicle information stored in the contractor database 11 and the administrator processing device 32. When the collation result with the received vehicle information is affirmative, the collected use vehicle number is written in the contractor database 11 as a regular use vehicle number, but the identity verification is performed only with the temporary ID, and the identity verification is successful. In addition, the collected use vehicle number may be written in the contractor database 11 as a regular use vehicle number.

  Moreover, in the said embodiment, it is collated by the collation part 15 whether the delivery use vehicle number corresponding to a collection use vehicle number exists in the contractor database 11, and temporary ID is obtained when a collation result is negative. Although the issuing unit 24 issued the temporary ID to the user, the temporary ID may be issued before the verification result becomes clear. For example, when performing entrance / exit management of a parking lot and toll collection as a service, a roadside device is installed at a parking lot entry gate, and a communication unit, a conversion unit, a temporary ID generation unit, and a temporary ID are installed in the roadside device. Place an issuer. When the user's vehicle enters the vehicle, the communication unit performs two-way wireless communication with the vehicle-mounted device to receive the unique identification information (device number), and the conversion unit converts this unique identification information to obtain the collected identification information (collection use vehicle). The temporary ID generating unit generates a temporary ID corresponding to the collection identification information, and the temporary ID issuing unit issues a temporary ID to the user. The temporary ID is stored in the temporary storage unit in association with the collection identification information. If the user is not registered in the service at the time of warehousing, the user can make a service application by declaring a temporary ID to the service provider before the warehousing. When a user performs an application procedure with a service provider, the processing unit of the service provider checks whether or not the identification information that matches the collected identification information exists in the service provider database, and a negative verification. Results are obtained. Here, when the temporary ID reported by the user matches the temporary ID stored in the temporary storage unit, the collection identification stored in the temporary storage unit in the service provider database by the collection identification information writing unit. Information is written as identification information, and user registration is completed. As a condition for the collection identification information writing unit to write the collection identification information as identification information, a condition in which the vehicle information reported by the user matches the vehicle information acquired from the administrator database may be added.

  Moreover, in the said embodiment, although the utilization vehicle number was used as identification information, the device number was used as unique identification information, and the onboard equipment management number was used as onboard equipment management information, the said identification information, unique identification information, and onboard equipment management information are It is not restricted to what consists of numbers. That is, as the identification information, unique identification information, and in-vehicle device management information, it is possible to adopt various types of information such as information composed of characters and information composed of a combination of numbers and characters.

  The IDs and passwords may be in various forms such as numbers, letters, and combinations of numbers and letters.

It is a figure which shows the user registration system as embodiment of this invention. It is a flowchart which shows the flow of the information exchanged between a provider server, a roadside apparatus, an administrator server, and onboard equipment. It is a flowchart which shows the procedure performed between a user, a service provider, and an apparatus number manager. It is a flowchart which shows the other procedure performed between a user, a service provider, and an apparatus number manager.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Operator server 2 Roadside device 3 Manager server 4 Vehicle 5 Credit server 11 Contractor database 12 Operator processing device 13 Use vehicle number acquisition part 14 Database control part 15 Verification part 16 Vehicle information acquisition part 17 Temporary storage part 18 Temporary ID Issuing unit 19 Temporary password input unit 21 Communication unit 22 Conversion unit 23 Temporary ID generation unit 24 Temporary ID issuing unit 25 Antenna 31 Device number database 32 Administrator processing device 41 On-board unit

Claims (8)

A user registration system for services using on-vehicle equipment,
A service provider database that stores identification information for identifying the OBE;
Based on the administrator database that stores the unique identification information uniquely assigned to the OBE and the OBE management information corresponding to this unique identification information, the OBE management information reported by the user of the OBE An identification information acquisition unit for acquiring delivery identification information obtained by converting the corresponding unique identification information;
A delivery identification information writing unit for writing the delivery identification information as identification information in the service provider database;
A communication unit that performs two-way wireless communication with the vehicle-mounted device, a conversion unit that converts the unique identification information received from the vehicle-mounted device by the communication unit to generate sampling identification information, and a temporary ID corresponding to the sampling identification information are generated A roadside device having a temporary ID generation unit
A collation unit that collates whether or not identification information that matches the collection identification information exists in the service provider database;
A temporary ID issuing unit for issuing the temporary ID to the user;
A temporary storage unit for storing the collection identification information and the temporary ID;
When the collation result by the collation unit is negative and the temporary ID reported by the user matches the temporary ID stored in the temporary storage unit, the temporary storage unit stores the temporary ID in the service provider database. And a collection identification information writing unit for writing the collected identification information as identification information. In the user registration system according to claim 1,
In the manager database, vehicle information related to the vehicle on which the vehicle-mounted device is mounted is stored in association with the unique identification information,
A vehicle information acquisition unit for acquiring vehicle information corresponding to the unique identification information corresponding to the collection identification information from the administrator database;
The collection identification information writing unit writes the collection identification information in the service provider database when the vehicle information reported by the user matches the vehicle information acquired by the vehicle information acquisition unit. Registration system. In the user registration system according to claim 2,
A provisional ID issuing unit that issues a temporary ID to the user in response to the application for the user's service;
The service provider database is configured to store the vehicle information reported by the user at the time of applying for the service in association with the identification information, and to identify the temporary ID issued by the temporary ID issuing unit. It is formed to store in association with information and vehicle information,
The collection identification information writing unit has a temporary ID that matches the temporary ID declared by the user in the service provider database, and vehicle information corresponding to the temporary ID in the service provider database is the vehicle information. A user registration system, wherein the collection identification information is written in the service provider database when the vehicle information is acquired by the acquisition unit. In the user registration system according to claim 1,
A user registration system comprising: a dummy information input unit for inputting dummy information as identification information of the service provider database when OBE management information is not declared by a user at the time of applying for a service. In the user registration system according to claim 1,
A user registration system in which a predetermined expiration date is set for the temporary ID. In the user registration system according to claim 1,
The temporary ID issuing unit is a printing unit that prints the temporary ID. In the user registration system according to claim 2,
The roadside device has a recognition unit that recognizes license plate information of a vehicle,
A license plate information storage unit that stores the license plate information recognized by the recognition unit of the roadside device in association with the collection identification information,
When the license plate information stored in the license plate information storage unit matches the license plate information in the vehicle information acquired by the vehicle information acquisition unit, the collection identification information writing unit A user registration system, wherein the collection identification information is written in a database. A service user registration method using an in-vehicle device,
Based on the administrator database that stores the unique identification information uniquely assigned to the OBE and the OBE management information corresponding to this unique identification information, the OBE management information reported by the user of the OBE Obtaining grant identification information obtained by converting the corresponding unique identification information;
Writing the delivery identification information as identification information in the service provider database;
The roadside device performs two-way wireless communication with the vehicle-mounted device to receive unique identification information, converts the received unique identification information to generate collection identification information, and generates a temporary ID corresponding to the collection identification information And steps to
Collating whether or not identification information that matches the collection identification information exists in the service provider database; and
Issuing the temporary ID to the user;
Storing the collection identification information and the temporary ID in a temporary storage unit;
When the identification information that matches the collection identification information does not exist in the service provider database, and the temporary ID reported by the user matches the temporary ID stored in the temporary storage unit, the service provider database And a step of writing the collection identification information stored in the temporary storage unit as identification information.

Images