JP4117210B2 - DSRC OBE setup system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a DSRC OBE setup system for setting up a DSRC OBE.
[0002]
[Prior art]
DSRC (Dedicated Short Range Communication) is a wireless communication technology for use in an extremely narrow area of about 3 m to 30 m.
FIG. 10 is a diagram showing road-to-vehicle communication by DSRC.
In FIG. 10, the DSRC on-vehicle device 1 is attached to a vehicle 50. The roadside device 51 includes an antenna 52 and performs road-to-vehicle communication with the DSRC on-vehicle device 1. At this time, there is a covered area 53 in which road-to-vehicle communication is possible. In road-to-vehicle communication, while the vehicle 50 stays in the covered area 53, wireless communication is performed between the antenna 52 connected to the roadside device 51 and the DSRC in-vehicle device 1. Is possible.
An example of a service for road-to-vehicle communication using DSRC is ETC (Electronic Toll Collection), which collects automobile fees on toll roads. In the ETC service, by communicating wirelessly between the ETC on-board unit (DSRC on-board unit 1 for ETC) attached to the vehicle 50 and the roadside unit 51 installed at the toll gate, the necessary information is exchanged. Toll collection is processed. An IC card (ETC card) is used for settlement of tolls, which is inserted into a card slot provided in the ETC on-board device.
[0003]
In order to use the ETC service, setup is required at the stage of attaching the ETC on-vehicle device to the vehicle 50. The setup is an operation for taking vehicle information necessary for the ETC service provided by the operator of the expressway into the vehicle-mounted device. If this setup is not completed, the ETC service cannot be used even if the ETC in-vehicle device is attached to the vehicle 50.
In order to set up the ETC on-board unit, it is first necessary to apply to ORSE (Road System Advancement Promotion Organization). Since setup requires vehicle information, vehicle-mounted device information, and user information, submit an application form with necessary information and a copy of vehicle verification to ORSE for application. When ORSE accepts the application, it issues an IC card (setup card) dedicated to setup. On-board device information and key information necessary for security are written in the setup card.
[0004]
Setup is executed by inserting the setup card into the card slot of the ETC on-board unit. First, the ETC on-vehicle device reads the information on the setup card, and checks whether the setup card is correct or whether the information on the on-vehicle device and the setup card match. When it is determined that the setup card is correct, information necessary for receiving the ETC service is read from the setup card and registered in the nonvolatile memory of the ETC on-vehicle device.
Since the ETC service is premised on the use of an IC card, the ETC in-vehicle device has a function of accessing the IC card. However, other DSRC application services other than ETC may be those that do not require IC card payment. Therefore, there may be a DSRC in-vehicle device that does not have an IC card interface. For example, Patent Document 1 discloses a “communication system, in-vehicle device, and recording medium” as a method that enables setup even in a DSRC in-vehicle device that does not have the IC card interface 1.
[0005]
In Patent Document 1, when a vehicle 50 equipped with the DSRC vehicle-mounted device 1 goes to a service providing place by DSRC and tries to receive the service, an application for receiving the service is not set up in the DSRC on-vehicle device 1 If this is the case, the method of setting up the application at this point is shown.
In the conventional DSRC in-vehicle device setup system disclosed in Patent Document 1, the microcomputer controls a road-to-vehicle communication control unit, an IC card interface, and an HMI (Human Machine Interface). An IC card can be inserted into the IC card interface. In addition, the HMI has a function of displaying information to the user such as display and voice output, and a function of determining the intention of the user. A car navigation system, a display, a voice unit, or the like can be connected to the HMI as an external device.
[0006]
In communication between the roadside device and the in-vehicle device, first, link establishment is performed according to the DSRC communication standard. Thereafter, the process of the in-vehicle device when entering the setup process is performed as follows.
As a pre-stage for executing the setup process, the in-vehicle device checks whether there is a setup request. It is assumed that the setup request is issued by communication from a roadside machine and is issued from a recording medium such as an IC card.
Next, when it is determined that there is a setup request, the in-vehicle device displays a setup screen using a car navigation system or a display. Next, the user sets functions and private information according to the application according to the procedure displayed on the setup screen. Further, an application program or the like is downloaded as system information settings. Subsequently, the in-vehicle device determines whether or not the setup has been completed. When the setup is completed, the in-vehicle device records setup information in an EEPROM or the like built in the microcomputer. Through the above processing, the in-vehicle device can execute the application.
[0007]
[Patent Document 1]
JP 2001-29897A (pages 4-7, FIG. 1)
[0008]
[Problems to be solved by the invention]
The conventional ETC OBE setup requires a setup card, so it is assumed that it will be used for DSRC application services that do not support payments. When setting up a DSRC OBE that does not have an IC card slot, use a setup card. There was a problem that could not be done.
In addition, since one setup card has been issued for the DSRC application service provided by a single service provider, in order to receive a plurality of services with different service providers with one DSRC OBE, It was necessary to set up each service provider or each service individually, which was troublesome.
In addition, in the method of setting up applications using road-to-vehicle communication at the service provision location, operations such as display and selection of selection items during setup and confirmation display of setting information are required. There was a restriction that a means and an input means had to be provided.
[0009]
The present invention has been made in order to solve the above-described problems. Even if the vehicle-mounted device does not include components such as an IC card interface, a display unit, and an input unit, a setup for receiving a DSRC application service can be performed. It is a first object to obtain a DSRC OBE setup system that enables this.
In addition, when a plurality of setups are performed in order for a service provider to receive a plurality of different services, a second object is to obtain a DSRC OBE setup system that can be efficiently executed at one time.
[0010]
[Means for Solving the Problems]
  In the DSRC OBE setup system according to the present invention, the DSRC OBE setup system that sets up the DSRC OBE to receive a service by road-to-vehicle communication with the DSRC roadside device is arranged in the service provider that provides the service. And having a database in which user information is registered, a setup server connected to the network, and a setup contractor that performs setup,Connected to DSRC OBESetup terminal connected to the networkThisMeans to input information required for setup to the setup terminalAnd a service server connected to the network and connected to a DSRC roadside machine that performs road-to-vehicle communication with the on-board DSRC device, and controls services provided by the DSRC roadside machineWith
The setup terminal transmits the information required for the setup input by the input means to the setup server, acquires the setup data for the DSRC OBE from the setup server, and then sets up the DSRC OBE using the setup data.And
The setup server registers information necessary for setup in the database as user information.Along with distributing user information registered in the database to the service serverIs.
[0011]
DETAILED DESCRIPTION OF THE INVENTION
Embodiment 1 FIG.
FIG. 1 is a system configuration diagram showing a DSRC OBE setup system according to Embodiment 1 of the present invention.
In FIG. 1, the DSRC on-vehicle device 1 is a setup target. The setup terminal 2 is installed at a setup contractor and connected to the input means 3. The setup server 4 is installed in the management center of the service provider and is connected to a database 5 in which user information is registered. The service server 6 is installed at a service providing place and connected to the DSRC roadside device 7. Among the above components, the setup terminal 2, the setup server 4 and the service server 6 are connected to each other via a network.
The setup work is basically performed by a setup contractor. The set-up contractor may be a dedicated contractor, a DSRC on-board equipment manufacturer, or a DSRC on-board equipment sold and attached to a vehicle.
The set-up contractor contracts with the service provider, and performs the setup work of the DSRC OBE 1 by the service provider. For this reason, the setup contractor advances the setup work by accessing the setup server 4 managed by the service provider.
In the first embodiment, it is assumed that the set-up work for the target service is that all work on the management center side of the service provider is processed in real time.
The state of the DSRC on-vehicle device 1 at the start of setup can be a state before being attached to the vehicle at the stage of purchase by the user, or a state already attached to the vehicle. The following description is valid in any case.
[0012]
FIG. 2 is a sequence diagram showing a DSRC OBE setup system according to Embodiment 1 of the present invention.
Hereinafter, the setup work will be described with reference to the sequence diagram of FIG.
The user first selects a service provider desired to be set up and its service type. The user himself or the setup contractor inputs data required for the service provider, service type and setup from the input means 3 to the setup terminal 2 (step S100). Information necessary for the setup depends on the service type, and includes vehicle information, vehicle-mounted device information, user information, and the like. Among these, the information registered inside the vehicle-mounted device can be requested from the setup terminal 2 to the DSRC vehicle-mounted device 1 (step S101) and taken out from the DSRC vehicle-mounted device 1 (step S102).
[0013]
Next, the setup terminal 2 establishes a session with the setup server 4 of the service provider designated by the user, and sets up the DSRC in-vehicle device 1 during this session.
The OBE setup session is established by a connection process (step S103) executed between the setup terminal 2 and the setup server 4. In the connection process (step S103), security technology is used to prevent impersonation, wiretapping, data tampering, and the like.
A processing procedure performed between the connection process of the setup terminal 2 (step S103a) and the connection process of the setup server 4 (step S103b) is, for example, as shown in FIG.
[0014]
FIG. 3 is a sequence diagram showing a connection process of the DSRC OBE setup system according to Embodiment 1 of the present invention.
First, the setup terminal 2 transmits a list of encryption algorithms corresponding to the setup terminal 2 to the setup server 4 in step S120 in order to establish a communication path with the setup server 4. In response to this, the setup server 4 determines and transmits an encryption algorithm from the list received from the setup terminal 2 in step S121.
Subsequently, in step S122, the setup server 4 transmits a server certificate to the setup terminal 2 in order to prove its identity. In step S123, the setup terminal 2 authenticates the setup server 4 by confirming the signature from the server certificate by the certification authority. In step S124, the setup terminal 2 further extracts the server public key from the server certificate. Next, the setup terminal 2 generates random number data in step S125. This random number data is a source for generating a key (session key) used for encrypting data in subsequent communications. This random number data is encrypted with the server public key in step S 126 and transmitted to the setup server 4. The setup terminal 2 generates a session key from the random number data in step S127. On the other hand, the setup server 4 decrypts the received encrypted data to extract random number data in step S128, and generates a session key in step S129.
[0015]
In FIG. 2, after completing the connection process (step S103), encrypted communication is performed between the setup terminal 2 and the setup server 4 using a session key. First, the setup terminal 2 transmits a setup request with information necessary for setup (step S104). The setup server 4 creates setup data from the received information (step S105) and transmits it to the setup terminal 2 (step S106). The setup terminal 2 transfers the received setup data to the connected DSRC on-vehicle device 1. The setup terminal 2 and the setup server 4 end the communication and close the session (step S107).
On the other hand, the DSRC on-vehicle device 1 executes setup from the transferred setup data (step S108). The contents of the setup differ depending on the target service. Examples of the setup process include a process of writing information to a nonvolatile memory mounted on the DSRC on-vehicle device 1 and a process of writing an application in the DSRC on-vehicle device 1 or an external device.
[0016]
When setting up the DSRC OBE 1, the service provider also needs to register as a service providing target in order to manage the DSRC OBE 1 information, user information, vehicle information, and the like. For this reason, after finishing the onboard equipment setup session in FIG. 2, the setup server 4 updates the database 5 (step S109). Next, a service server registration session is executed between the setup server 4 and the service server 6.
[0017]
It is assumed that the service provider providing the service and the contractor managing the DSRC roadside equipment are different. The roadside facility manager and the service provider negotiate the types of services that can be used at each service providing location managed by the roadside facility manager. The roadside facility management contractor may consider contracting with a plurality of service providers, and the services of a plurality of providers can be used at one service providing place.
In the service server registration session, registrant information, vehicle information, vehicle-mounted device information, and the like set up in the service server 6 installed in each service providing place managed by all roadside facility management contractors contracted by the service provider are distributed. This distribution includes a method in which the setup server 4 directly accesses the service server 6 at the service providing location and a method of indirect distribution. In the indirect distribution method, the setup server 4 distributes only to the general server of the roadside facility management company, and distributes from the general server to the service server 6 at each service provision location. Since the session is established on a one-to-one basis, the service server registration session is executed by the number of distribution partners. The service server registration session may be established after the setup server 4 registers one DSRC on-board unit 1 in the database, or may be a method of processing a plurality of cases collectively.
[0018]
In FIG. 1 of the first embodiment, it is assumed that the service provider X sets up the DSRC in-vehicle device 1 so that the service S1 can be used. Service S1 is provided at service providing locations P1 and P2. Note that the roadside facility managers that manage the service providing locations P1 and P2 may be the same or different. In this example, it is assumed that the service provider X directly distributes information to the service servers 6a and 6b installed in P1 and P2, respectively.
In the service server registration session, the setup server 4 first accesses the distribution partner and executes connection processing (step S110). The connection process here is similar to the connection process (step S103) in the in-vehicle device setup session, and by using the security technology, it is possible to prevent spoofing, wiretapping, data tampering, and the like. After the session is established, update information is notified from the database 5 managed by the service provider (step S111). The service server 6 reflects the received update information on the managed data (step S112). At the end of the session, the setup server 4 and the service server 6 disconnect the session (step S113).
[0019]
This completes the setup process on both the vehicle-mounted device side and the service providing side. The DSRC in-vehicle device 1 can use the service S1 by setup, and can receive this service at the service providing locations P1 and P2 in FIG. When the user enters the DSRC roadside machine 7a or 7b coverage at the service providing place P1 or P2 and requests the service S1 by DSRC communication at the service providing place P1 or P2, the user controls the service server 6a or 6b. Thus, the service S1 is provided to the user.
In the process of the service S1, if communication with the service provider X is necessary, the service server 6a or 6b may access a server installed in the management center of the service provider X.
[0020]
According to the first embodiment, as described above, since the DSRC on-vehicle device 1 is set up by connecting to the setup terminal 2 and the input means 3 installed in the setup contractor, the DSRC on-vehicle device displays the IC card interface and the display. It is possible to set up to receive the DSRC application service without providing the components such as the means and the input means.
[0021]
Embodiment 2. FIG.
FIG. 4 is a configuration diagram showing a case where a setup terminal of the DSRC OBE setup system and the DSRC OBE are connected by DSRC according to Embodiment 2 of the present invention.
In FIG. 4, 1 to 3 are the same as those in FIG. The DSRC on-vehicle device 1 is attached to the vehicle 50. The roadside device 51 connected to the setup terminal 2 has an antenna 52 and performs road-to-vehicle communication with the DSRC in-vehicle device 1. This road-to-vehicle communication has a coverage area 53 in which communication is possible.
In the second embodiment, the DSRC in-vehicle device 1 is already attached to the vehicle 50, and the setup terminal 2 controls the roadside device 51 to use the DSRC as a communication means, so that information necessary for the setup is obtained. Among them, the information held in the DSRC onboard device 1 can be captured. In this case, the roadside device 51 is equivalent to the function of the input terminal 3.
[0022]
Also in the second embodiment, since the setup of the DSRC in-vehicle device 1 is performed by communicating with the setup terminal 2 installed at the setup contractor and the roadside device 51 as the input means 3, the in-vehicle system performs the IC card interface, the display means, and the input. A setup for receiving a DSRC application service is possible even without a component such as a means.
In the second embodiment, the case where the DSRC OBE 1 and the setup terminal 2 communicate with each other while the DSRC OBE 1 is attached to the vehicle 50 is shown. However, the DSRC OBE 1 is attached to the vehicle 50. A configuration in which the DSRC in-vehicle device 1 and the setup terminal 2 communicate with each other by DSRC even in a state where the device is not connected can be considered.
[0023]
According to the second embodiment, the setup terminal 2 controls the roadside device 51 and uses the DSRC as a communication means, thereby taking in the information held in the DSRC on-vehicle device 1 among the information necessary for the setup. Even if the in-vehicle system does not include components such as an IC card interface, display means, and input means, setup for receiving DSRC application service is possible.
In addition, even when the DSRC on-vehicle device 1 is not attached to the vehicle 50, the DSRC on-vehicle device 1 and the setup terminal 2 communicate with each other by DSRC, so that the information necessary for the setup is held inside the DSRC on-vehicle device 1. Information can be captured.
[0024]
Embodiment 3 FIG.
FIG. 5 is a configuration diagram showing a case where vehicle information of the DSRC on-board unit setup system according to Embodiment 3 of the present invention is acquired from an electronic license plate.
In FIG. 5, the vehicle 50 has an electronic license plate 54 and an IC chip 55 incorporated in the electronic license plate 54. This IC chip 55 stores items described in the vehicle verification, and can perform wireless communication between the antenna 52 and the IC chip 55 under the control of the roadside device 51 to read out the vehicle verification information.
The setup terminal 2 can take in vehicle information out of information necessary for setup by controlling the roadside device 51 that can communicate with the IC chip 55 on the electronic license plate 54. In this case, the roadside device 51 is equivalent to the function of the input terminal 3.
In the third embodiment, since the setup of the DSRC on-vehicle device 1 is performed by communicating with the setup terminal 2 installed at the setup contractor and the roadside device 51 as the input means 3, the on-vehicle device has an IC card interface, display means, and input. A setup for receiving a DSRC application service is possible even without a component such as a means.
[0025]
According to the third embodiment, the setup terminal 2 can capture the vehicle information among the information necessary for the setup by controlling the roadside device 51 that can communicate with the IC chip 55 on the electronic license plate 54. Even if the in-vehicle system does not include components such as an IC card interface, display means, and input means, it is possible to set up to receive the DSRC application service.
[0026]
Embodiment 4 FIG.
FIG. 6 is a diagram showing an information configuration managed in each of the DSRC OBE, the service provider, and the service providing place in the DSRC OBE setup system according to Embodiment 4 of the present invention, and FIG. 6B is a member information list of the database of the service provider management center, and FIG. 6C is a member list of the service provider of the service server at the service providing location. .
In FIG. 6, it is assumed that the user A performs the setup for using the service S1 of the service provider X at each of the DSRC vehicle-mounted device 1, the service provider, and the service providing place. Although the service S1 can be used in many service providing locations, FIG. 6 shows an example in which only the service providing location P1 is focused.
The registration information set up in the DSRC in-vehicle device 1 by the set-up contractor is held in the nonvolatile memory 8 as shown in FIG. The nonvolatile memory 8 in the DSRC on-vehicle device 1 of the user A is provided with a service registration list area. When this setup is completed, the code 10 indicating the service provider X as the service provider ID, the code 11 indicating the service S1 as the service ID, and the password (P11) 12 for receiving the service are written in the service registration list area. It is assumed that N1 is held in the nonvolatile memory 8 as the vehicle-mounted device ID9. The vehicle-mounted device ID 9 is a unique number given at the time of manufacture in order to identify each DSRC vehicle-mounted device 1.
[0027]
After the setup process is completed in the DSRC on-vehicle device 1, as shown in the first embodiment, new member registration information is written in the database 5 installed in the management center of the service provider X. In the database 5 of FIG. 6B, user information, vehicle information, vehicle-mounted device information, and the like obtained by membership application are registered. In FIG. 6B, as a result of this setup, the vehicle-mounted device ID 13, the member information 14, the service ID 15, and the password 16 are registered.
The newly set up information is distributed from the management center of the service provider X to the service server 6a at the service providing place P1. It is assumed that the service providing place P1 provides the service of the service provider Y in addition to the service provider X. Therefore, the service server 6a manages a member list for the service provider X and a member list for the service provider Y, as shown in FIG. For information distribution related to the service provider X, only the member list for the service provider X is updated. Here, as the setup information of the user A, the vehicle-mounted device ID 17, the service ID 18, and the password 19 are newly registered.
[0028]
Next, when the user A stops receiving the service S1 from the service provider X, it is necessary to delete the information registered at each location. The user A can delete registration information from the DSRC in-vehicle device 1 by inputting registration deletion information at the setup contractor in the same manner as at the time of registration, and applying for registration cancellation using this information. In FIG. 6, only the information 10 to 12 related to the service S1 of the service provider X is deleted from the non-volatile memory 8 in the DSRC on-vehicle device 1 of the user A from the service registration list. In addition, the information 13 to 16 is deleted from the database 5 of the service provider X. Further, the service provider X deletes the registration information 17 to 19 of the user A from the service server 6a at the service providing place P1.
[0029]
Also in the fourth embodiment, the setup registration and deletion of the DSRC OBE 1 uses the setup terminal 2 and the input means 3 installed in the setup contractor, so that the OBE has an IC card interface, a display means, an input means, etc. Registration and deletion for receiving a DSRC application service is possible even if the component is not provided.
[0030]
Embodiment 5 FIG.
FIG. 7 is a sequence diagram of the first stage when the DSRC OBE setup system according to the fifth embodiment of the present invention is set up in the DSRC OBE in two stages.
FIG. 8 is a sequence diagram of the second stage in the case where the DSRC OBE setup system according to the fifth embodiment of the present invention performs the setup to the DSRC OBE in two stages.
[0031]
FIGS. 7 and 8 show a method for performing setup in the DSRC OBE in two stages when setup information cannot be generated and transmitted in real time from the service provider side to the DSRC OBE in response to the setup request.
The first stage setup to the DSRC on-board unit is a stage where a setup contractor writes a setup key (first set-up data) in the nonvolatile memory. In the second stage, the DSRC OBE accesses the service provider's setup server via the service server at the service providing location using the setup key, receives the setup data body (second setup data), and performs the setup. It is a stage to execute.
[0032]
In FIG. 7, steps S130 to S138 are processing until the setup contractor connects the DSRC in-vehicle device 1 to the setup server 4 of the service provider via the setup terminal 2 and receives distribution of the setup key. The processing flow is the same as that up to the on-vehicle device setup session of FIG. 2, but in FIG. 7, the on-vehicle device setup session is replaced with a setup key distribution session.
In the setup key distribution session, connection processing is performed between the setup terminal 2 and the setup server 4 (step S133), and a setup request is issued from the setup terminal 2 to the setup server 4 (step S134). On the other hand, the setup server 4 cannot generate the setup data immediately because offline processing is necessary, so the setup server 4 creates a setup key for the DSRC OBE to capture the setup data later (step S135). This is distributed to the DSRC on-vehicle device 1 (step S136). At this time, either the setup server 4 or the setup terminal 2 delivers the service provider code to be set up to the DSRC in-vehicle device 1 together with the setup key.
Subsequently, a disconnection process is performed between the setup terminal 2 and the setup server 4 (step S137), and the DSRC on-vehicle device 1 writes the service provider code and the setup key in the nonvolatile memory (step S138).
When time elapses and the setup server 4 is able to create setup data, the setup server 4 writes information necessary for providing the service in the database 5 (step S139). Subsequently, a service server registration session is executed between the setup server 5 and the service server 6 as in FIG. 2 (steps S140 to S143).
[0033]
The DSRC OBE 1 actually executes the setup because the setup server 4 can prepare the setup data, and then the user goes to a convenient service providing location and accesses the setup server 4 via the service server 6. It depends. The service server 6 can be connected to the network of the setup server 4 of the service provider that provides the service set up by the user. The process at this stage is shown in FIG.
First, the DSRC vehicle-mounted device 1 performs connection processing with the service server 6 by DSRC (step S144). Next, the DSRC on-vehicle device 1 issues a setup request to the service server 6 (step S145). The setup request includes a service provider code and a setup key. Upon receiving the setup request, the service server 6 connects to the service provider indicated by the service provider code (step S146). Thereby, the connection between DSRC onboard equipment 1-service server 6-setup server 4 is established.
[0034]
Subsequently, the service server 6 transfers the setup request to the setup server 4 (step S147). A setup key is attached to the setup request, and the setup server 4 of the service provider takes out the setup data body prepared in advance using this setup key and transmits it to the DSRC on-vehicle device 1 (step S148). Thereafter, the DSRC between the DSRC vehicle-mounted device 1 and the service server 6 is disconnected (step S149), and the connection between the service server 6 and the setup server 4 is also disconnected (step S150). The DSRC on-vehicle device 1 executes setup from the received setup data body (step S151). When the setup is successful, the DSRC on-vehicle device 1 deletes the service provider code and the setup key (step S152).
[0035]
Also in the fifth embodiment, since the setup registration of the DSRC on-vehicle device 1 uses the setup terminal 2 and the input means 3 installed in the setup contractor, the on-vehicle device includes components such as an IC card interface, a display means, and an input means. Registration for receiving the DSRC application service is possible even if it is not provided.
In the fifth embodiment, the example of the second-stage setup location is a service providing location, but it may be a setup contractor. In this case, the role of the service server 6 can obtain the same effect by the setup terminal 4 acting as a substitute.
[0036]
Embodiment 6 FIG.
FIG. 9 is a sequence diagram in the case where the setup for receiving two types of services provided by the two service providers of the DSRC OBE setup system according to Embodiment 6 of the present invention is executed collectively.
FIG. 9 corresponds to the process up to the database update in the setup server after the on-vehicle device setup session in FIG. 2 in the setup process.
The user desires to receive the service S1 of the service provider X and the service S10 of the service provider Y, and requests the two kinds of setups at the setup contractor. First, using the input means 3, information necessary for setup is input to the setup terminal 2. The input information includes an item for designating a service to be set up. Here, the service S1 of the service provider X and the service S10 of the service provider Y are input (step S153). It is assumed that information necessary for applying for the service S1 and the service S10 includes common and non-common information. When entering information, information common to both services is entered only once.
Next, the setup terminal 2 requests onboard equipment information from the DSRC onboard equipment 1 (step S154), and obtains onboard equipment information from the DSRC onboard equipment 1 (step S155). The setup terminal 2 is divided into an information group A necessary for the application of the services S1 and S10, an information group B necessary for the application of only the service S1, and an information group C necessary for the application of only the service S10 (step S156). ).
[0037]
Thereafter, the process enters an onboard setup session. In this example, since there are two types of service providers that receive the setup, the in-vehicle device setup is performed twice.
The first OBE setup session is a process executed by connecting the DSRC OBE 1 to the setup terminal 2 to the setup server 4 of the service provider X (step S157). The processing sequence in this session is the same as that of the on-vehicle device setup session in FIG. In this session, group A information and group B information are transmitted from the setup terminal 2 to the setup server 4 as information necessary for applying for the service S1 provided by the service provider X. As a result, setup data for receiving the service S1 is transmitted from the setup server 4 to the DSRC in-vehicle device 1. The DSRC on-vehicle device 1 executes setup from the received setup data. After this session, the setup server 4 of the service provider X updates the database 5 (step S158).
[0038]
The second onboard equipment setup session is a process of connecting between the DSRC onboard equipment 1 to the setup terminal 2 to the setup server 4 of the service provider Y (step S159). In this session, group A information and group C information are transmitted from the setup terminal 2 to the setup server 4 as information necessary for applying for the service S10 provided by the service provider Y. As a result, setup data for receiving the service S10 is transmitted from the setup server 4 to the DSRC in-vehicle device 1. The DSRC on-vehicle device 1 executes setup from the received setup data. After this session, the setup server 4 of the service provider Y updates the database 5 (step S160).
[0039]
In the sixth embodiment, the setup terminal 2 installed in the setup contractor accepts applications for batch setup of a plurality of services provided by a plurality of service providers in the same DSRC OBE 1 and is necessary for different setup applications. The common information is acquired once, the necessary information is sorted for each setup application destination, and the necessary information is connected to the setup server 4 of the application destination in order for each setup application destination and the necessary information is transmitted. Thus, when a plurality of setups are performed in order for a service provider to receive a plurality of different services, it can be efficiently executed at a time.
[0040]
In the above-described sixth embodiment, an example in which setup is continuously received from two service providers is shown, but the same applies to the case of three or more service providers. Furthermore, in the above-described sixth embodiment, an example in which the setup is completed in only one stage has been shown. However, when two stages are required, the work in the first stage can be replaced with a form that efficiently performs batch processing.
[0041]
【The invention's effect】
  Since the present invention is configured as described above, the following effects can be obtained.
  In a DSRC OBE setup system for setting up a DSRC OBE so that a service by road-to-vehicle communication with a DSRC roadside device can be received, the DSRC OBE has a database arranged in a service provider that provides the service and registered user information , Located on a networked setup server, set-up contractor performing the setup,Connected to DSRC OBESetup terminal connected to the networkThisMeans to input information required for setup to the setup terminalAnd a service server connected to the network and connected to a DSRC roadside machine that performs road-to-vehicle communication with the on-board DSRC device, and controls services provided by the DSRC roadside machineWith
The setup terminal transmits the information required for the setup input by the input means to the setup server, acquires the setup data for the DSRC OBE from the setup server, and then sets up the DSRC OBE using the setup data.And
The setup server registers information necessary for setup in the database as user information.Along with distributing user information registered in the database to the service serverTherefore, even if the DSRC OBE does not have an IC card interface, display means, input means, etc., it is possible to set up to receive DSRC application services.At the same time, it can be efficiently executed at the same time when multiple setups are performed for service providers to receive different services.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram showing a DSRC OBE setup system according to Embodiment 1 of the present invention.
FIG. 2 is a sequence diagram showing a DSRC OBE setup system according to Embodiment 1 of the present invention.
FIG. 3 is a sequence diagram showing a connection process of the DSRC OBE setup system according to Embodiment 1 of the present invention.
FIG. 4 is a configuration diagram showing a case where a setup terminal of a DSRC OBE setup system and a DSRC OBE are connected by DSRC according to Embodiment 2 of the present invention.
FIG. 5 is a configuration diagram showing a case where vehicle information of a DSRC OBE setup system according to Embodiment 3 of the present invention is acquired from an electronic license plate.
FIG. 6 is a diagram showing an information configuration managed in each of the DSRC OBE, the service provider, and the service providing place in the DSRC OBE setup system according to Embodiment 4 of the present invention;
FIG. 7 is a sequence diagram of the first stage in the case where the DSRC OBE setup system according to Embodiment 5 of the present invention performs setup to the DSRC OBE in two stages.
FIG. 8 is a second-stage sequence diagram in the case where the DSRC OBE setup system according to Embodiment 5 of the present invention is set up in two stages in the DSRC OBE.
FIG. 9 is a sequence diagram when a setup for receiving two types of services provided by two service providers of a DSRC OBE setup system according to Embodiment 6 of the present invention is executed collectively.
FIG. 10 is a diagram showing road-to-vehicle communication by general DSRC.
[Explanation of symbols]
1 DSRC OBE, 2 setup terminal, 3 input means,
4 setup server, 5 database, 6 service server,
7 DSRC roadside unit, 8 Non-volatile memory.

Claims (8)

In a DSRC OBE setup system for setting up a DSRC OBE so that a service by road-to-vehicle communication with a DSRC roadside device can be received, the DSRC OBE has a database arranged in a service provider that provides the service and having user information registered therein together, up server connected to the network, is arranged to set up skill to perform the setup, the DSRC OBE setup terminal connected to the network is connected, the information required for the set up this setup terminal input means for inputting, and is connected to the DSRC roadside device performing road-vehicle communication between the vehicle DSRC apparatus includes a service server connected to the network controls the services provided by the DSRC roadside equipment
The setup terminal transmits information necessary for setup input by the input means to the setup server, obtains setup data for the DSRC OBE from the setup server, and then uses the setup data to obtain the setup data. Set up a DSRC car-mounted equipment,
The DSRC OBE setup system, wherein the setup server registers information necessary for the setup in the database as user information and distributes the user information registered in the database to the service server . The DSRC OBE is attached to a vehicle, and the setup terminal acquires information held by the DSRC OBE by road-to-vehicle communication between the DSRC onboard device on the vehicle and the DSRC roadside unit, and the setup claim 1 Symbol placement DSRC OBE setup system is characterized in that a part of the information required. The setup terminal acquires information held by the IC chip through road-to-vehicle communication between the IC chip attached to the vehicle and the DSRC roadside machine, and uses the information as part of the information necessary for the setup. claim 1 Symbol placement DSRC OBE setup system is. When canceling the service set up in the DSRC OBE, the registration cancellation information of the service is input by the input means, and the setup terminal uses the registration cancellation information to set up the DSRC OBE. the deregistration information transmitted to the set-up server while releasing the setup of the service, the setup server claims 1 to 3 and deletes the user information of the database based on the deregistration information The DSRC OBE setup system according to any one of the above. The setup data is divided into first setup data and second setup data. The setup data transmitted by the setup server is the first setup data and the first setup data. The setup data is stored in the DSRC OBE, and the DSRC OBE acquires the second setup data by using the first setup data, and is set up by the second setup data. The DSRC OBE setup system according to any one of claims 1 to 4 , wherein 6. The DSRC OBE setup system according to claim 5 , wherein the DSRC OBE obtains the second setup data via the DSRC roadside device. The DSRC OBE setup system according to claim 5 or 6, wherein the first setup data is a setup key for taking in the second setup data. A plurality of setup servers are connected to the network, and the setup terminal is required for a setup common to the plurality of setup servers when performing setup for a plurality of services provided by the plurality of setup servers. prepare information and information necessary for individual setup, and sequentially transmitted to the plurality of set-up server of claim 1 to claim 7, characterized in that to receive the setup data from the plurality of setup servers DSRC OBE setup system in any one.

Images