JP5056441B2 - In-vehicle system, in-vehicle device, terminal, and program - Google Patents

Description

  The present invention relates to an in-vehicle device that performs data processing for collecting charges and the like via wireless communication.

  An ETC system that automatically passes data tolls for toll roads such as expressways by wireless communication between in-vehicle devices and roadside devices, allowing non-stop passing through toll booths It has become. This ETC system is becoming more and more popular in recent years, and the movement to make ETC system in-vehicle devices available for shopping at fast food shops and entrance / exit management of parking lots is becoming more concrete. Is expected to expand further.

  In the ETC system currently in practical use, when the user passes through the toll gate of the ETC system, the user needs to insert an ETC card storing information necessary for payment of the fee into the in-vehicle device. . Therefore, when the user pulls out the ETC card from the in-vehicle device in a service area or the like, the user has to perform an operation of inserting the ETC card into the in-vehicle device again before passing through the toll gate.

  Therefore, the card information is registered in the in-vehicle device by storing the card information in the in-vehicle device using the IC card, and the charge is calculated based on the registered card information even if the IC card is not connected to the in-vehicle device. An in-vehicle device capable of performing data processing for settlement has been proposed. By using such an in-vehicle device, the user does not need to perform an operation of inserting an IC card into the in-vehicle device before passing through the toll gate of the ETC system.

  By the way, when the fee is settled by the ETC system, a fee settlement record which is a record relating to the settlement of the fee is generated. Since this fee settlement record is not information that should be disclosed to others without restriction, the generated fee settlement record is inserted in an in-vehicle device that performs data processing for fee settlement with an IC card inserted. By storing the information in the IC card, the charge settlement record is prevented from being transferred to another person's hand. However, when performing data processing for fee settlement based on the card information registered in the in-vehicle device as in the proposed in-vehicle device, the fee settlement record cannot be stored in the IC card. In this way, it is a problem whether to prevent the charge settlement information from reaching another person's hand.

Patent Document 1 describes an invention that can solve the above-described problems. In the vehicle-mounted device described in Patent Document 1, the identification information of the IC card and the information related to toll collection are stored in association with each other. The on-vehicle device acquires identification information from the IC card when transmitting information related to fee collection to the IC card, and transmits information related to fee collection stored in association with the acquired identification information to the IC card. .
JP 2007-108930 A

  According to the vehicle-mounted device described in Patent Document 1, information related to fee collection can be written without error to an IC card that is a registration source of card information used for fee collection. Can be prevented.

  However, in the in-vehicle device of Patent Document 1, it is necessary to transmit the identification information from the IC card to the on-vehicle device every time information related to toll collection is written to the IC card, there is a possibility that the identification information of the IC card leaks. . Therefore, when the card ID is used as the identification information of the IC card, valuable personal information is leaked due to leakage of the identification information. Similarly, when the card information is registered in the in-vehicle device using the function as the non-contact type IC card of the mobile phone and the phone number of the mobile phone is used as the identification information, Leakage will leak valuable personal information.

  In the technique described in Patent Document 1, it is possible to assume a case where card information is registered from one IC card to a plurality of vehicle-mounted devices. In such a case, a common identification is used in these vehicle-mounted devices. Information will be used. Therefore, when the identification information is transferred to another person's hand, the other person can read out information related to toll collection stored in the plurality of vehicle-mounted devices.

  The present invention has been made to solve the above-mentioned problem, and more safely transfers various information from an in-vehicle device that performs data processing for settlement of charges based on registered card information to a terminal. An object of the present invention is to provide an in-vehicle system that can be used.

  The in-vehicle system according to claim 1, which has been made in order to solve the above-described problem, performs data processing for settlement of charges based on activated card information out of one or more registered card information. It is comprised from the vehicle-mounted apparatus to perform and the terminal which registers card information in a vehicle-mounted apparatus. And the terminal side storage which memorize | stores the identification information which is the information comprised by the terminal side communication means which communicates with a vehicle-mounted apparatus, and the random value newly produced | generated each time card information is registered into a vehicle-mounted apparatus. Means. The in-vehicle device includes an in-vehicle device side communication unit that communicates with the terminal, an in-vehicle device side storage unit that associates and stores identification information and various information, and an identification received from the terminal via the in-vehicle device side communication unit. In-vehicle device-side control means for executing information transmission processing for transmitting predetermined information stored in the in-vehicle device-side storage means in association with information to the terminal that is the transmission source of the identification information via the in-vehicle device-side communication means With.

  Here, the terminal may be a contact type IC card or a non-contact type IC card. Further, for example, a mobile phone having a non-contact type IC card function may be used.

  This eliminates the need to transmit personal information such as a card ID and a mobile phone number to the in-vehicle device when reading information stored in the in-vehicle device from the terminal. In addition, for example, even when card information is registered in a plurality of in-vehicle devices using a single terminal, new identification information is generated each time card information is registered. The occurrence of a situation in which information is read out from a plurality of in-vehicle devices can be prevented by passing on the hands of others. Therefore, the information stored in the in-vehicle device can be read from the terminal more safely.

Further, the in-vehicle device may transmit the fee settlement record to the terminal that is the transmission source of the terminal-side authentication information corresponding to the in-vehicle device-side authentication information stored in the in-vehicle device-side storage unit.
That is, in the in-vehicle system according to claim 2, the in-vehicle device-side storage unit associates the identification information with a fee settlement record that is a data processing record for the fee settlement based on the card information related to the identification information. One of the predetermined information transmitted in the information transmission process may be a charge settlement record.

By doing so, it is possible to improve the safety when the charge settlement record stored in the in-vehicle device is read from the terminal.
By the way, when data processing for fee settlement is performed in the in-vehicle device, there is a demand for the in-vehicle device to execute processing based on setting information corresponding to activated card information. And when implement | achieving such an in-vehicle apparatus, it is convenient if this in-vehicle apparatus has the following structures.

  In the in-vehicle system according to the third aspect, the in-vehicle device is configured to perform various processes based on the setting information corresponding to the activated card information. And the in-vehicle device side control means sets the setting information corresponding to the card information related to the identification information received from the terminal based on the information received from the terminal via the in-vehicle device side communication means, and the set setting information, The identification information related to the card information corresponding to the setting information is associated with and stored in the in-vehicle device side storage means.

  In this way, for example, setting information can be generated or updated only from a specific terminal such as a terminal that is a registration source of card information corresponding to the setting information. It is possible to prevent such a situation that the setting information is generated.

Further, by having the following configuration, it becomes easy to update the setting information from the terminal.
In the in-vehicle system according to claim 4, one of the predetermined information transmitted in the information transmission process is setting information.

  By doing so, the terminal can notify the user of the setting information received from the in-vehicle device, so that the user can easily update the setting information via the terminal. Therefore, the convenience of the in-vehicle system can be improved.

  By the way, the in-vehicle device of the in-vehicle system according to any one of claims 1 to 4 may be configured as a single unit and distributed in the market. Further, the in-vehicle system terminal according to any one of claims 1 to 4 may be configured as a single unit and distributed in the market. Even if the vehicle-mounted device or terminal according to any one of claims 1 to 4 is configured as a single unit, the above-described effects can be obtained by combining with the corresponding vehicle-mounted device or terminal.

  Further, as described in claim 7, even if the program for causing the vehicle-mounted device according to claim 5 to function as the vehicle-mounted device-side control means is executed by a computer built in the vehicle-mounted device. good.

  According to the seventh aspect, for example, a program is recorded on a computer-readable recording medium such as a magneto-optical disk, a CD-ROM, a hard disk, a ROM, and a RAM, and the program is recorded as necessary. It can be made to function as a vehicle-mounted device by being loaded into a computer and starting up. Further, since the program can be distributed using a network, the function of the in-vehicle device can be easily improved.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiments of the present invention are not limited to the following embodiments, and various forms can be adopted as long as they belong to the technical scope of the present invention.

[Description of configuration]
FIG. 1 is a block diagram showing the configuration of the in-vehicle system 10. The in-vehicle system 10 includes an in-vehicle device 100 mounted on a vehicle and a mobile phone 200 that can be carried by a user. This mobile phone 200 stores card information. In addition, the mobile phone 200 can communicate with the vehicle-mounted device 100 via short-range wireless communication, and can communicate with the information center 30 via the wireless public network 20 provided by a mobile phone company or the like.

  The information center 30 includes a server 300 and a customer information database 400. Server 300 communicates with mobile phone 200 via wireless public network 20, generates an in-vehicle device card ID based on the card ID received from mobile phone 200, and transmits it to mobile phone 200. The mobile phone 200 registers the in-vehicle device card ID in the in-vehicle device 100 by storing the in-vehicle device card ID generated in the information center 30 in the in-vehicle device 100 (the in-vehicle device card ID is registered in the in-vehicle device 100). Will be described later). The customer information database 400 is a database in which customer information of the holder of the card information stored in the mobile phone 200 is recorded.

  Next, the details of the in-vehicle device 100 will be described using the block diagram shown in FIG. The in-vehicle device 100 wirelessly communicates with a roadside device (not shown) installed at a toll gate or the like of the ETC system, and for settlement of charges based on the in-vehicle device card ID registered via the mobile phone 200. It is a device that performs the data processing. The in-vehicle device 100 includes a radio antenna 110, a DSRC unit 120, a SAM 130, a non-contact communication I / F 140, a control unit 150, an HMI 160, and a storage unit 170.

The wireless antenna 110 is an antenna for DSRC.
The DSRC unit 120 is a part that performs transmission / reception of information by the DSRC with the roadside device via the wireless antenna 110.

The SAM 130 is a part that encrypts and decrypts communication information with the roadside device.
The contactless communication I / F 140 is an interface for performing contactless short-range wireless communication with the mobile phone 200. A contact-type interface may be used.

  The control unit 150 includes a CPU, a ROM, a RAM, an I / O, and the like, and is a part that comprehensively controls each part of the in-vehicle device 100. The control unit 150 performs various processes based on programs stored in the ROM. In addition, the control unit 150 performs short-range wireless communication with the mobile phone 200 via the non-contact communication I / F 140.

  The HMI 160 is a part that provides an interface (Human Machine Interface) for communication between a person and a device. Specifically, it is composed of operation buttons, LEDs, speakers, and the like.

  The storage unit 170 includes a device (for example, a flash memory) that does not require a storage holding operation, and can store various types of information. The storage unit 170 stores one or more in-vehicle device card IDs, which are information necessary for the payment of the fee. When the in-vehicle device 100 performs data processing for fee settlement, Of the in-vehicle device card ID, the activated in-vehicle device card ID is transmitted to the roadside device. In addition, the storage unit 170 stores an in-vehicle device number that is information for specifying the in-vehicle device 100 including the storage unit 170.

  Next, details of the mobile phone 200 will be described with reference to the block diagram of FIG. The mobile phone 200 includes a wireless antenna 210, a public communication unit 220, an HMI 230, a non-contact communication I / F 240, a control unit 250, and a storage unit 260.

The wireless antenna 210 is an antenna for wireless connection to the wireless public network 20.
The public communication unit 220 is a part that performs wireless communication (for example, communication such as CDMA) via the wireless antenna 210 and transmits / receives information to / from the information center 30 via the wireless public line network 20.

  The HMI 230 is a part that provides an interface (Human Machine Interface) for communication between a person and a device. Specifically, it is composed of operation buttons, an LCD, a speaker, and the like.

The non-contact communication I / F 240 is an interface for performing non-contact short-range wireless communication with the in-vehicle device 100. A contact-type interface may be used.
The control unit 250 includes a CPU, a ROM, a RAM, an I / O, and the like, and is a part that comprehensively controls each part of the mobile phone 200. The control unit 250 performs various processes based on a program stored in the ROM. The control unit 250 is connected to the wireless public network 20 via the public communication unit 220. In addition, the control unit 250 performs short-range wireless communication with the in-vehicle device 100 via the non-contact communication I / F 240.

  The storage unit 260 includes a device (for example, a flash memory) that does not require a storage holding operation, and can store various types of information. The storage unit 260 stores card information, which is information necessary for payment of charges. Details of the information stored in the storage unit 260 will be described later.

[Description of information stored in each device]
Next, contents of information stored in the storage unit 170 included in the in-vehicle device 100 and information stored in the storage unit 260 included in the mobile phone 200 will be described.

  FIG. 4 is a block diagram for explaining information stored in the storage unit 170 included in the in-vehicle device 100. The storage unit 170 stores an in-vehicle device number 171 and card A related information 172, card B related information 173, and card C related information 174, which are information related to predetermined card information.

The in-vehicle device number 171 is information for specifying the in-vehicle device 100.
The card A related information 172 is information including a vehicle-mounted device card ID registered via the mobile phone 200. The card A related information 172 includes an in-vehicle device card ID 172a, identification information 172b, setting information 172c, a usage history 172d, and the like.

  The in-vehicle device card ID 172a is information used for data processing for payment of charges, and is information generated by the information center 30 based on the card ID stored in the mobile phone 200.

  The identification information 172b is information generated by the mobile phone 200 when the in-vehicle device card ID 172a is registered using the mobile phone 200, and is information composed of random values. Here, the random value is a value having no regularity, and specifically, for example, may be a value generated by the control unit 250 of the mobile phone 200 executing a random number generation function. .

  The setting information 172c is information for determining the operation of the in-vehicle device 100 when the in-vehicle device card ID 172a is activated. Specifically, it is information indicating the volume of a speaker constituting the HMI 160 included in the in-vehicle device 100, the display mode of the LEDs constituting the HMI, and the like.

  The usage history 172d is a record of data processing for settlement of charges performed based on the onboard device card ID 172a. Specifically, for example, the date and time when the data processing was performed, the location, and the amount of settlement And so on. The usage history 172d is generated when the data processing for the settlement of the charge based on the in-vehicle device card ID 172a is first performed after the in-vehicle device card ID 172a is registered in the in-vehicle device 100, and the card A related information 172. Thereafter, each time data processing for fee settlement based on the in-vehicle device card ID 172a is performed, a record of the data processing is added to the usage history 172d.

  The card B related information 173 and the card C related information 174 also have the same configuration as the card A related information 172. The in-vehicle device card IDs included in these pieces of information are IDs registered in the information center 30 via different mobile phones 200, respectively. Needless to say, in this embodiment, information related to three pieces of card information is stored in the storage unit 170, but information related to one or two pieces of card information is stored. Alternatively, information related to four or more pieces of card information may be stored.

  Next, the content of information stored in the storage unit 260 included in the mobile phone 200 will be described. FIG. 5 is a block diagram for explaining information stored in the storage unit 260 included in the mobile phone 200. In the storage unit 260, the card information 261 and the in-vehicle device A related information 262, the in-vehicle device B related information 263, which are information related to the in-vehicle device 100 in which the in-vehicle device card ID is registered via the mobile phone 200, And in-vehicle device C related information 264 are stored.

  The card information 261 is information that can be used for fee settlement. The card information 261 includes a card ID 261a that is information for specifying the card information 261, and nominee information 261b that is information including the name, address, and occupation of the nominee of the card information 261.

  The in-vehicle device A related information 262 is information related to the in-vehicle device 100 in which the in-vehicle device card ID is registered using the mobile phone 200. Specifically, the in-vehicle device A related information 262 includes an in-vehicle device number 262a, an in-vehicle device card ID 262b, identification information 262c, setting information 262d, a usage history 262e, and the like.

The in-vehicle device number 262a is information for specifying the in-vehicle device 100 in which the in-vehicle device card ID 262b registered using the mobile phone 200 is stored.
The in-vehicle device card ID 262 b is an in-vehicle device card ID registered in the in-vehicle device 100 using the mobile phone 200.

  The identification information 262c is information generated by the mobile phone 200 when the in-vehicle device card ID 262b is registered using the mobile phone 200, and is information composed of random values.

  The setting information 262d is information for determining the operation of the in-vehicle device 100 when the in-vehicle device card ID 262b is activated. Specifically, it is information indicating the volume of a speaker constituting the HMI 160 included in the in-vehicle device 100, the display mode of the LEDs constituting the HMI, and the like.

  The usage history 262e is a record of data processing for settlement of charges made based on the in-vehicle device card ID 262b. Specifically, for example, the date and time when the data processing was performed, the location, the amount of settlement, etc. It is information which has. The usage history 262e is information acquired by the mobile phone 200 from the in-vehicle device 100 specified by the in-vehicle device number 262a via short-range wireless communication (a process when acquiring the usage history will be described later). .

  The in-vehicle device B related information 263 and the in-vehicle device C related information 264 also have the same configuration as the in-vehicle device A related information 262. The card IDs for in-vehicle devices included in these pieces of information are IDs registered in different in-vehicle devices 100, respectively. Needless to say, in this embodiment, the storage unit 170 stores information related to the three in-vehicle devices 100, that is, the in-vehicle device A, the in-vehicle device B, and the in-vehicle device C. Information related to one or two in-vehicle devices 100 may be stored, or information related to four or more in-vehicle devices 100 may be stored.

[Explanation about customer information database]
The customer information database 400 is a database in which customer information of a card information holder stored in the mobile phone 200 is recorded. The customer information 410 described in the block diagram of FIG. 6 is one of customer information constituting the customer information database 400. Here, the customer information database 400 will be described by describing the customer information 410.

  The customer information 410 is information related to the in-vehicle device 100 in which the card information 411 stored in the mobile phone 200 and the in-vehicle device card ID generated by the server 300 based on the card ID 411a constituting the card information 411 are registered. Vehicle-mounted device A-related information 412, vehicle-mounted device B-related information 413, vehicle-mounted device C-related information 414, and the like.

  The card information 411 is information that can be used for fee settlement. The card information 411 includes a card ID 411a that is information for identifying the card information 411, and nominee information 411b that is information having the name, address, occupation, and the like of the nominee of the card information 411.

The in-vehicle device A related information 412 includes an in-vehicle device number 412a, an in-vehicle device card ID 412b, and the like.
The in-vehicle device number 412a is information for specifying the in-vehicle device 100 in which the in-vehicle device card ID 412b is registered.

The in-vehicle device card ID 412b is an in-vehicle device card ID registered in the in-vehicle device 100 specified by the in-vehicle device number 412a.
The in-vehicle device B related information 413 and the in-vehicle device C related information 414 also have the same configuration as the in-vehicle device A related information 412. The in-vehicle device card IDs included in these pieces of information are registered in different in-vehicle devices 100, respectively. Needless to say, in this embodiment, the customer information 410 includes information related to the three in-vehicle devices 100, but the customer information 410 is related to one or two in-vehicle devices 100. May be included, or information related to four or more in-vehicle devices 100 may be included. Further, when the on-vehicle device card ID based on the card ID 411 a is not generated by the server 300, the customer information 410 does not have information related to the on-vehicle device 100.

[Description of operation]
Next, the operation of the in-vehicle system 10 will be described.
(1) Processing for registering in-vehicle device card ID The sequence diagram shown in FIG. 7 generates the in-vehicle device card ID based on the card ID stored in the mobile phone 200 in the information center 30; It is a sequence diagram for demonstrating the process at the time of registering in the vehicle equipment. The in-vehicle device 100 transmits a response request via short-range wireless communication at a predetermined cycle after power is turned on. The mobile phone 200 is brought close to the in-vehicle device 100 after receiving an operation for registering the in-vehicle device card ID from the user via the HMI 230, and receives a response request from the in-vehicle device 100. The in-vehicle device 100 is transmitted to the in-vehicle device 100. When the in-vehicle device 100 receives from the mobile phone 200 that the in-vehicle device card ID can be registered, the process shown in FIG. 7 is started. Hereinafter, the specific content of the process illustrated in FIG. 7 will be described.

  In S <b> 505, the control unit 150 of the in-vehicle device 100 is a request for registering the in-vehicle device card ID in the in-vehicle device 100 to the mobile phone 200 by short-range wireless communication via the non-contact communication I / F 140. A registration request and an in-vehicle device number are transmitted. The in-vehicle device number is information corresponding to the in-vehicle device number 171 in the block diagram shown in FIG.

  In the mobile phone 200 that has received the registration request and the in-vehicle device number, the control unit 250 temporarily stores the received in-vehicle device number in the RAM included in the control unit 250 (S510). And the control part 250 transfers a process to S515.

  In S515, the control unit 250 starts communication with the server 300 of the information center 30 via the public communication unit 220, and mutual authentication between the mobile phone 200 and the server 300 is executed. If the result of mutual authentication is normal, the process proceeds to S520. If the result of mutual authentication is abnormal, this process ends.

  In S520, the control unit 250 sends the in-vehicle device card ID generation request, the card ID constituting the card information stored in the storage unit 260, and the in-vehicle device number received from the in-vehicle device 100 in S505 to the public. The data is transmitted to the server 300 of the information center 30 via the communication unit 220. The card ID transmitted through the public communication unit 220 is information corresponding to the card ID 261a in the block diagram shown in FIG.

  The server 300 that has received the in-vehicle device card ID generation request or the like via the wireless public network 20 verifies the card ID received together with the in-vehicle device card ID generation request (S525). Specifically, when the received card ID is included in the customer information constituting the customer information database 400 of the information center 30, it is determined that the card ID is normal. If the card ID is normal, the server 300 shifts the process to S530. If the card ID is not normal, this process ends.

In S530, the server 300 generates an in-vehicle device card ID for the holder of the card ID received in S520, and the process proceeds to S535.
In S535, the server 300 updates the customer information database 400. Specifically, the server 300 newly generates in-vehicle device related information including the in-vehicle device number received in S520 and the in-vehicle device card ID generated in S530, and the generated in-vehicle device related information is In addition to the customer information including the card ID received in S520. Then, the server 300 shifts the process to S540. The in-vehicle device related information generated by the server 300 is information corresponding to the in-vehicle device A related information 412 included in the customer information 410 in the block diagram shown in FIG. The in-vehicle device number and the in-vehicle device card ID included in the in-vehicle device related information are respectively the in-vehicle device number 412a and the in-vehicle device included in the in-vehicle device A related information 412 in the block diagram of FIG. This is information corresponding to the business card ID 412b.

In S540, the server 300 transmits the in-vehicle device card ID generated in S530 to the mobile phone 200 via the wireless public network 20.
In the mobile phone 200 that has received the in-vehicle device card ID via the wireless public network 20, the control unit 250 generates setting information based on an operation received from the user via the HMI 230 (S545). The setting information is information that determines the operation of the in-vehicle device 100 when the in-vehicle device card ID received in S540 is activated in the in-vehicle device 100. And the control part 250 transfers a process to S550.

In S550, the control unit 250 generates identification information that is information composed of random values, and the process proceeds to S555.
In S555, the control unit 250 uses the in-vehicle device card ID received in S540, the setting information generated in S545, the identification information generated in S550, and the in-vehicle device number stored in the RAM in S510. Is generated and stored in the storage unit 260. And the control part 250 transfers a process to S560. The in-vehicle device related information generated by the control unit 250 is information corresponding to the in-vehicle device A related information 262 in the block diagram illustrated in FIG. Further, the in-vehicle device number, the in-vehicle device card ID, the identification information, and the setting information are respectively the in-vehicle device number 262a and the in-vehicle device card constituting the in-vehicle device A related information 262 in the block diagram shown in FIG. Information corresponding to ID 262b, identification information 262c, and setting information 262d.

  In S560, the control unit 250 receives the in-vehicle device card ID received in S540 via the non-contact communication I / F 240, the setting information generated in S545, and the identification information generated in S550. It transmits to the vehicle equipment 100. And the control part 250 transfers a process to S565.

  In the in-vehicle device 100 that has received the in-vehicle device card ID or the like via short-range wireless communication, the control unit 150 is configured by the in-vehicle device card ID and the setting information and identification information received together with the in-vehicle device card ID. Card-related information is generated and stored in the storage unit 170 (S565). The card related information is information corresponding to the card A related information 172 in the block diagram shown in FIG. The in-vehicle device card ID, the identification information, and the setting information received via the short-range wireless communication are the in-vehicle device card ID 172a, the identification information 172b, and the setting information 172c that constitute the card A related information 172, respectively. It is information corresponding to.

(2) Processing when Confirming Usage History with the Mobile Phone 200 The sequence diagram shown in FIG. 8 shows the usage history of the in-vehicle device card ID registered in the in-vehicle device 100 as the in-vehicle device card ID. FIG. 7 is a sequence diagram for explaining processing when confirming via mobile phone 200 that has registered the setting information corresponding to card ID for in-vehicle device via mobile phone 200. The in-vehicle device 100 transmits a response request via short-range wireless communication at a predetermined cycle after power is turned on. The mobile phone 200 is brought close to the in-vehicle device 100 after receiving an operation for confirming a usage history of a predetermined in-vehicle device card ID registered using the mobile phone 200 from the user via the HMI 230. When a response request is received from the in-vehicle device 100, the process illustrated in FIG. 8 is started. Hereinafter, the specific content of the process illustrated in FIG. 8 will be described.

  In step S <b> 605, the control unit 250 of the mobile phone 200 uses the in-vehicle device via the non-contact communication I / F 240 to store the identification information stored in association with a predetermined on-vehicle device card ID registered through the mobile phone 200. To 100. The in-vehicle device card ID and the identification information are information corresponding to the in-vehicle device card ID 262b and the identification information 262c included in the in-vehicle device A related information 262 in the block diagram illustrated in FIG. .

  In the in-vehicle device 100 that has received the identification information via the short-range wireless communication, the control unit 150 determines whether or not the card-related information including the same identification information as the received identification information is stored in the storage unit 260. (S610). When the card related information including the same identification information is stored in the storage unit 260 (S610: Yes), the process of S615 is executed. When card-related information including the same identification information is not stored in the storage unit 260 (S610: No), this process ends. The card related information corresponds to the card A related information 172 in the block diagram shown in FIG. 4, and the identification information received via the short-range wireless communication is the identification information constituting the card A related information 172. This information corresponds to 172b.

  In S615, the control unit 150 transmits the setting information and the use history included in the card related information including the same identification information as the received identification information to the mobile phone 200 via the non-contact communication I / F 140, and the process in S620 To migrate. The setting information and the usage history are information corresponding to the setting information 172c and the usage history 172d included in the card A related information 172 in the block diagram shown in FIG.

  In mobile phone 200 that has received the setting information and usage history via short-range wireless communication, control unit 250 is included in the in-vehicle device related information including the identification information transmitted in S605 based on the usage history received in S615. The used usage history is updated (S620). When the usage history is not included in the in-vehicle device related information, the usage history received in S615 is newly added to the in-vehicle device related information. At this time, the control unit 250 may notify the user of the contents of the usage history received in S615 via the HMI 230. And the control part 250 transfers a process to S625. The usage history is information corresponding to the usage history 262e included in the in-vehicle device A related information 262 in the block diagram shown in FIG.

  In S625, the control unit 250 notifies the user of the contents of the setting information received in S615 via the HMI 230, accepts an operation for changing the contents of the setting information, and shifts the process to S630.

  In S630, the control unit 250 updates the setting information included in the in-vehicle device related information including the identification information transmitted in S605 based on the operation to change the contents of the setting information received in S625, and the process proceeds to S635. Migrate processing. The setting information is information corresponding to the setting information 262d included in the in-vehicle device A related information 262 in the block diagram illustrated in FIG.

In S635, the control unit 250 transmits the setting information updated in S630 to the in-vehicle device 100 via the non-contact communication I / F 240.
In the in-vehicle device 100 that has received the setting information via the short-range wireless communication, the control unit 150 displays the setting information included in the in-vehicle device related information including the identification information received in S605 based on the received setting information. Update (S640).

[effect]
In the in-vehicle system 10 of the present embodiment, when registering the in-vehicle device card ID in the in-vehicle device 100 via the mobile phone 200, the mobile phone 200 generates identification information that is information composed of random values. (S550). Then, the in-vehicle device 100 associates the identification information generated by the mobile phone 200 with the in-vehicle device card ID and the setting information and stores them in the storage unit 170 (S565). Based on this identification information, the in-vehicle device 100 determines whether or not the mobile phone 200 is the registration source of the card ID for in-vehicle devices (S610), and the setting information for the mobile phone 200 that is the registration source is determined. And a usage history that is a record of data processing for the payment of the fee based on the card ID for in-vehicle device is transmitted (S615).

  Thus, in the in-vehicle system 10, since the card ID and the mobile phone number are not used when identifying whether the mobile phone 200 is the registration source of the card ID for the in-vehicle device, the in-vehicle device is used in the mobile phone 200. It is not necessary to transmit precious personal information such as a card ID or a mobile phone number to the in-vehicle device 100 when acquiring the usage history of the card ID for use. In addition, for example, even when in-vehicle device card IDs are registered in a plurality of in-vehicle devices 100 using one mobile phone 200, new identification information is generated each time the in-vehicle device card ID is registered. Since it is generated, it is possible to prevent the occurrence of a situation in which information such as usage histories is read from the plurality of in-vehicle devices 100 by passing one piece of identification information to another person's hand. Therefore, information such as a usage history stored in the in-vehicle device 100 can be read from the mobile phone 200 more safely.

  Further, when registering the in-vehicle device card ID in the in-vehicle device 100, the user can set the setting information related to the registered in-vehicle device card ID via the registration source mobile phone 200 (S545). . The in-vehicle device 100 determines whether or not the mobile phone 200 is the registration source of the in-vehicle device card ID based on the identification information (S610), and the setting information for the mobile phone 200 that is the registration source. Is transmitted (S615). Then, the setting information setting can be changed via the mobile phone 200 that has received the setting information (S625, S640).

  Therefore, since the setting information can be easily generated and updated only from the mobile phone 200 that is the registration source of the card ID for the in-vehicle device corresponding to the setting information, the convenience of the in-vehicle system 10 can be improved, It is possible to prevent the setting information from being updated by others.

[Other Embodiments]
(1) In the present embodiment, when the in-vehicle device card ID is registered in the in-vehicle device 100 via the mobile phone 200, the mobile phone 200 generates identification information. However, when the card ID for in-vehicle device is registered in the in-vehicle device 100, the in-vehicle device 100 may generate identification information. Even if it has such a structure, there can exist the same effect.

  (2) The mobile phone 200 may notify the user of the usage history stored in the storage unit 260 via the HMI 230 in response to an operation from the user. By doing so, usability of the mobile phone 200 is improved.

  (3) In the present embodiment, as an example, the processing in the case of performing registration of the in-vehicle device card ID, acquisition of the usage history, and the like via the mobile phone 200 has been described. However, a mobile information terminal capable of short-range wireless communication with the in-vehicle device 100 or wireless communication with the information center 30 may be used instead of the mobile phone 200. Even if it has such a structure, there can exist the same effect.

[Correspondence with Claims]
The correspondence between the terms used in the description of the above embodiment and the terms used in the description of the claims is shown.

The non-contact communication I / F 240 corresponds to the terminal side communication means, and the storage unit 260 corresponds to the terminal side storage means.
Further, the mobile phone 200 corresponds to the terminal, the non-contact communication I / F 140 corresponds to the in-vehicle device side communication means, the control unit 150 corresponds to the in-vehicle device side control means, and the storage unit 170 corresponds to the in-vehicle device side storage means.

  Further, S615 in the sequence diagram shown in FIG. 8 corresponds to the information transmission process, and the usage history corresponds to the charge settlement record.

1 is a block diagram illustrating a configuration of an in-vehicle system 10. FIG. 2 is a block diagram illustrating a configuration of an in-vehicle device 100. FIG. 2 is a block diagram showing a configuration of a mobile phone 200. FIG. 4 is a block diagram for explaining information stored in a storage unit 170 of the in-vehicle device 100. FIG. 4 is a block diagram for explaining information stored in a storage unit 260 of the mobile phone 200. FIG. It is a block diagram for demonstrating the customer information which comprises the customer information database 400. FIG. It is a sequence diagram for demonstrating the process at the time of registering card ID for vehicle equipment. FIG. 11 is a sequence diagram for explaining processing when confirmation of usage history or the like is performed with mobile phone 200;

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... In-vehicle system, 20 ... Wireless public network, 30 ... Information center, 100 ... In-vehicle apparatus, 110 ... Wireless antenna, 120 ... DSRC part, 130 ... SAM, 140 ... Non-contact communication I / F, 150 ... Control part, 160 ... HMI, 170 ... storage unit, 171 ... vehicle device number, 172 ... card A related information, 172a ... card ID for vehicle device, 172b ... identification information, 172c ... setting information, 172d ... usage history, 173 ... card B related Information, 174 ... Card C related information, 200 ... Mobile phone, 210 ... Wireless antenna, 220 ... Public communication unit, 230 ... HMI, 240 ... Non-contact communication I / F, 250 ... Control unit, 260 ... Storage unit, 261 ... Card information, 261a ... Card ID, 261b ... Nominee information, 262 ... In-vehicle device A related information, 262a ... In-vehicle device number, 262b ... In-vehicle device Placement card ID, 262c ... identification information, 262d ... setting information, 262e ... usage history, 263 ... in-vehicle device B related information, 264 ... in-vehicle device C related information, 300 ... server, 400 ... customer information database, 410 ... customer information 411 ... Card information, 411a ... Card ID, 411b ... Nominee information, 412 ... In-vehicle device A related information, 412a ... In-vehicle device number, 412b ... Card ID for in-vehicle device, 413 ... In-vehicle device B related information, 414 ... In-vehicle Device C related information.

Claims (7)

An in-vehicle device that executes data processing for payment of a fee based on the activated card information among one or more registered card information, and a terminal that registers the card information in the in-vehicle device An in-vehicle system comprising:
The terminal
Terminal-side communication means for communicating with the in-vehicle device;
Terminal-side storage means for storing identification information, which is information composed of random values newly generated each time the card information is registered in the in-vehicle device,
The in-vehicle device is
On-vehicle device side communication means for communicating with the terminal;
On-vehicle device side storage means for storing the identification information and various information in association with each other;
Predetermined information associated with the identification information received from the terminal via the in-vehicle device side communication means and stored in the in-vehicle device side storage means is sent to the in-vehicle device that is the transmission source of the identification information. A vehicle-mounted device side control means for executing information transmission processing to be transmitted via the device side communication means,
In-vehicle system characterized by The in-vehicle system according to claim 1,
The in-vehicle device-side storage means stores the identification information in association with a charge settlement record that is a record of the data processing for a settlement of a charge based on the card information related to the identification information, and the information One of the predetermined information transmitted in the transmission process is the charge settlement record,
In-vehicle system characterized by In the in-vehicle system according to claim 1 or claim 2,
The in-vehicle device is configured to perform various processes based on setting information corresponding to the activated card information,
The in-vehicle device side control means sets and sets the setting information corresponding to the card information related to the identification information received from the terminal based on information received from the terminal via the in-vehicle device side communication means The setting information and the identification information related to the card information corresponding to the setting information are associated with each other and stored in the in-vehicle device side storage means,
In-vehicle system characterized by The in-vehicle system according to claim 3,
One of the predetermined information transmitted in the information transmission process is the setting information;
In-vehicle system characterized by   The vehicle-mounted apparatus provided with the means described about the said vehicle-mounted apparatus in the vehicle-mounted system in any one of Claims 1-4.   The terminal provided with the means described about the said terminal in the vehicle-mounted system in any one of Claims 1-4.   The program for functioning a computer as the said vehicle equipment side control means of the vehicle equipment of Claim 5.

Images