JP4998181B2 - In-vehicle device and portable terminal - Google Patents

Description

  The present invention relates to an in-vehicle device capable of executing billing processing such as a toll and a product purchase price, and a portable terminal used in combination with the in-vehicle device.

  In recent years, ETC systems have become widespread. However, since the current ETC system is a type in which a contact type IC card is inserted into an in-vehicle device, a contact failure between the IC card and the in-vehicle device occurs or the driver forgets to insert the IC card. As a result, an event has occurred in which the vehicle cannot normally pass through the entrance gate and the exit gate of the ETC system.

  Therefore, in order to solve such a problem, the applicant of the present application copies the card information from the IC card to the in-vehicle device in advance, and uses the copied card information when passing through the gate. An invention was first filed that allows the passage of the gate without the need (see Prior Application 1).

  In addition, in order to keep the security of card information copied to the in-vehicle device above a predetermined level, the invention prevents the card information from being used unless the card information is activated (validated) using a predetermined portable terminal. Also filed earlier (see Prior Application 2).

[Prior Application 1] Japanese Patent Application No. 2006-313377 [Prior Application 2] Japanese Patent Application No. 2007-126934
JP

  However, if the predetermined portable terminal is not actually present, the card information cannot be activated. For example, if the card information can be activated only with a mobile terminal owned by one family member, the card information cannot be activated after the family gets off, which is inconvenient.

  The present invention has been made in view of such a problem, and an object thereof is to provide an in-vehicle apparatus and the like that improve usability while maintaining security.

  The in-vehicle device according to claim 1, which has been made to solve the above problem, includes a billing destination specifying information storage unit, a billing process execution unit, a setting unit, a determination information storage unit, a registration unit, and a change unit. Is provided. The billing destination identification information storage means stores billing destination identification information that is information stored based on a command from the mobile terminal and that can identify a billing destination (credit card account, deposit account, individual, corporation, etc.). The charging processing execution means stores the charging destination specifying information stored in the charging destination specifying information storage means, and communicates with the roadside device to execute the charging processing. In addition, the setting unit may be in an activated state where the charging destination identification information stored in the charging destination identification information storage unit is in an available state or an inactive state in which it is unavailable. The state is set, and the determination information storage unit stores determination information used when determining whether or not the charging destination identification information is an activatable terminal capable of changing from the inactive state to the active state. It is a possible means. Further, the registration unit is different from the first portable terminal or the first portable terminal based on a storage command from the first portable terminal that stores the billing destination identification information in the billing destination identification information storage unit. The determination information of the second portable terminal is stored in the determination information storage means. In addition, when the change unit receives a change command for changing the billing destination identification information from the deactivated state to the activated state from the portable terminal, the determination unit stores whether the portable terminal is an activatable terminal. The determination is made using the stored determination information, and only when the determination is affirmative, the billing destination specifying information is changed from the inactivated state to the activated state.

  According to such an in-vehicle device, not only the first mobile terminal that stores the billing destination identification information in the in-vehicle device, but also the second mobile terminal registered in the in-vehicle device via the first mobile terminal, It becomes possible to activate the billing destination specifying information stored in the in-vehicle device. Therefore, for example, if the owner of the second mobile terminal gets on the vehicle even after the owner of the first mobile terminal gets off the vehicle, the billing destination identification information can be arbitrarily activated. become. That is, usability is improved. Moreover, since the second portable terminal is not registered in the in-vehicle device as a terminal that can activate the billing destination identification information unless it is based on the first portable terminal, it is considered that the security can be sufficiently maintained.

  However, in order to further improve security, the first portable terminal may be authenticated when the second portable terminal is registered in the in-vehicle device as an activatable terminal. In other words, as in the in-vehicle device according to claim 2, the registration unit matches the determination information sent from the first portable terminal with the determination information about the first portable terminal stored in the determination information storage unit. The storage command from the first portable terminal may be executed on the condition that it has been done.

If it becomes like this, the legitimacy of a 1st portable terminal will increase and security will improve.
By the way, the activation by the second portable terminal may be performed unconditionally, but there may be a condition. That is, as in the in-vehicle device according to claim 3, the registration means further receives the execution condition of the change command from the second portable terminal that is the activatable terminal from the first portable terminal and stores the determination information. The change means is configured to determine whether or not to execute a change command from the second portable terminal that is an activatable terminal, in addition to the execution condition stored in the determination information storage means. It may be.

In this case, activation by the second portable terminal can be restricted, and as a result, charging processing caused by activation by the second portable terminal can be restricted.
As an example of the execution condition, it is conceivable to specify billing destination specifying information that can be changed to the activated state. In other words, it is assumed that the billing destination specifying information storage unit stores a plurality of billing destination specifying information, and the registering unit stores the billing destination specifying information stored in the billing destination specifying information storing unit as one of the execution conditions. Specific information for specifying at least one is stored in the determination information storage unit in association with the activatable terminal, and the changing unit executes the change command only for the billing destination specifying information specified by the specific information. (Claim 4).

  If it becomes like this, since it can be activated by the 2nd portable terminal only about specific billing destination specific information, the owner of the 1st portable terminal is more positive in the 2nd portable terminal. Is registered in the in-vehicle device.

  In addition, as an example of the execution condition, it is conceivable to use a charging limit related to the charging destination specifying information as a condition. In other words, the registration unit stores the charging limit amount related to the charging destination specifying information in the determination information storage unit as one of the execution conditions, and the changing unit determines that the current charging amount related to the charging destination specifying information targeted for the change command is the charging limit. Only when it is within the forehead, the change command may be executed (claim 5).

  If this is the case, the owner of the first portable terminal is more proactive in order to not activate the billing destination identification information when the current billing amount exceeds the billing limit. Mobile terminals will be registered in the in-vehicle device.

  Further, as an example of the execution condition, it is conceivable that a chargeable period related to the charge destination specifying information is used as a condition. That is, the registration unit stores the billable period related to the billing destination identification information in the determination information storage unit as one of the execution conditions, and the change unit executes the change command only when the current time is within the billable period. (Claim 6).

  In this case, since the billing destination identification information is not activated when the current time is outside the billable period, the owner of the first mobile terminal more actively uses the second mobile terminal. It will be registered in the in-vehicle device.

  By the way, when the history information of the billing process is stored, it can be determined later by which mobile terminal the billing process was executed when activated. Good. That is, when the in-vehicle device further includes history information storage means for storing the history information of the charging process, the charging process execution means displays history information about the charging process as history information storage means when performing the charging process. And the activation execution terminal information, which is information that can identify the mobile terminal in which the charging destination specifying information used for the charging process is activated, is stored in the history information storage unit in association with the charging process. It is good to be (Claim 7).

  If this is the case, the owner of the first mobile terminal can more positively determine which mobile terminal has activated the billing process later, so that the owner of the first mobile terminal is more proactive. Mobile terminals will be registered in the in-vehicle device.

  The first portable terminal according to claim 8, which has been made to solve the above-described problem, includes a billing destination specifying information storage control unit that stores billing destination specifying information that is information capable of specifying a billing destination in the in-vehicle device, Change command transmission means for transmitting to the in-vehicle device a change command for changing the charging destination specifying information stored in the in-vehicle device from the inactive state to the active state, and the charging destination specifying information from the inactive state to the active state Storage command transmission means for transmitting to the in-vehicle device a storage command for storing determination information used in determining whether the terminal is an activatable terminal that can be changed to the in-vehicle device. Then, based on a request from another mobile terminal, the storage command transmission means transmits a command for storing the determination information of the mobile terminal in the in-vehicle device to the in-vehicle device as a storage command.

  According to such a first portable terminal, not only the first portable terminal that stores the billing destination specifying information in the in-vehicle device, but also the second portable terminal in which the determination information is stored via the first portable terminal. The terminal can also activate the billing destination identification information stored in the in-vehicle device. If the second mobile terminal can also activate the billing destination identification information stored in the in-vehicle device, for example, even after the owner of the first mobile terminal gets off the vehicle, the owner of the second mobile terminal If the vehicle is in the vehicle, the billing destination identification information can be activated arbitrarily, so that the in-vehicle device is easy to use. Moreover, since the second portable terminal is not registered in the in-vehicle device as a terminal that can activate the billing destination identification information unless it is based on the first portable terminal, it is considered that the security can be sufficiently maintained.

  The second portable terminal according to claim 10, which has been made to solve the above problem, is configured to deactivate charging destination identification information that is information stored in the in-vehicle device and that can identify a charging destination from an inactive state. A change command transmission means for transmitting a change command for changing to the activated state to the in-vehicle device, and whether or not the terminal is an activatable terminal capable of changing the billing destination identification information from the deactivated state to the activated state Storage request means for storing the determination information used when determining whether or not the in-vehicle device is stored via the portable terminal storing the charging destination identification information in the in-vehicle device.

  According to such a second portable terminal, not only the first portable terminal that stores the billing destination specifying information in the in-vehicle device, but also the second portable terminal in which the determination information is stored via the first portable terminal. The terminal can also activate the billing destination specifying information stored in the in-vehicle device. If the second mobile terminal can also activate the billing destination identification information stored in the in-vehicle device, for example, even after the owner of the first mobile terminal gets off the vehicle, the owner of the second mobile terminal If the vehicle is in the vehicle, the billing destination identification information can be activated arbitrarily, so that the in-vehicle device is easy to use. Moreover, since the second portable terminal is not registered in the in-vehicle device as a terminal that can activate the billing destination identification information unless it is based on the first portable terminal, it is considered that the security can be sufficiently maintained.

  In addition, you may implement | achieve the function as each means of the 1st portable terminal mentioned above and a 2nd portable terminal by a program (Claims 9 and 11). If such a program is executed by a computer built in the portable terminal, the portable terminal has the same operations and effects as the portable terminal of the present invention described above. Further, the program can be distributed using a network or the like, and the replacement of the program in the portable terminal is easier than the replacement of the parts. Therefore, it is possible to easily improve the function of the mobile terminal.

  Embodiments to which the present invention is applied will be described below with reference to the drawings. The embodiment of the present invention is not limited to the following embodiment, and can take various forms as long as they belong to the technical scope of the present invention.

[Description of configuration]
(1) Overall Configuration FIG. 1 is a block diagram showing the overall configuration of the ETC system 10. The ETC system 10 includes an in-vehicle device 20 mounted on a vehicle, a first portable terminal 30 that can be carried by the user, a second portable terminal 40 that can also be carried by the user, and a roadside installed at a toll gate or the like. Provides information for setting a storage area (area) in the device 53, a mobile terminal site server 55 that provides a Web site, and a storage medium (a storage unit 36 to be described later) provided in the first mobile terminal 30 This is a system including an area issuing server 57 and a card center server 59 installed in a credit card company. Although only one of these is illustrated in FIG. 1, there are usually a plurality of these. The in-vehicle device 20 and the roadside device 53 communicate with each other by DSRC (Dedicated Short Range Communication). Communication between the in-vehicle device 20, the first mobile terminal 30, and the second mobile terminal 40 is performed by short-range wireless communication. The first portable terminal 30 and each server (portable terminal site server 55, area issuing server 57, and card center server 59) communicate via the wireless public network 51. However, the first portable terminal 30 and the wireless public network 51 are connected by radio, but each server and the wireless public network 51 are connected by wire. The second portable terminal 40 can also be connected to the wireless public network 51, but is not allowed to communicate with the servers.

(2) On-vehicle device 20
Next, details of the in-vehicle device 20 will be described with reference to the block diagram of FIG. The in-vehicle device 20 includes a wireless antenna 21, a DSRC unit 22, an HMI 23, a SAM 24, a non-contact communication interface 25, a storage unit 26, and a control unit 27.

The wireless antenna 21 is a DSRC antenna.
The DSRC unit 22 is a part that transmits and receives information by DSRC via the wireless antenna 21. The communication target is the roadside device 53.

  The HMI 23 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 SAM 24 performs encryption / decryption of communication information with the roadside device 53 and encryption / decryption of in-vehicle device specific information (management number, type registration number, vehicle number, etc.). In addition, encryption / decryption of card information for in-vehicle devices described later is also performed.

  The non-contact communication interface 25 is an interface for performing non-contact short-range wireless communication (for example, communication using ISO 14443 TYPE C, Bluetooth, or the like) with the first mobile terminal 30 and the second mobile terminal 40. The communication partner is not limited to the first portable terminal 30 and the second portable terminal 40, and can communicate with a non-contact type IC card. A contact type communication interface may be used.

The storage unit 26 includes a device (for example, a flash memory) that does not require a storage holding operation, and can store various types of information.
The control unit 27 includes a CPU, a ROM, a RAM, an I / O, and the like, and is a part that comprehensively controls the DSRC unit 22, the HMI 23, the SAM 24, the non-contact communication interface 25, and the storage unit 26 based on a program.

(3) First mobile terminal 30
Next, details of the first portable terminal 30 will be described with reference to the block diagram of FIG. The first portable terminal 30 includes a wireless antenna 31, a public communication unit 32, an HMI 33, a non-contact communication interface 35, a storage unit 36, and a control unit 37.

The wireless antenna 31 is an antenna for wireless connection to the wireless public line network 51.
The public communication unit 32 is a part that transmits and receives information by wireless communication (for example, communication such as CDMA) via the wireless antenna 31. The final communication targets are the mobile terminal site server 55, the area issuing server 57, and the card center server 59.

  The HMI 33 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, a liquid crystal display, a speaker, a microphone, and the like.

  The non-contact communication interface 35 is an interface for performing non-contact short-range wireless communication (for example, communication using ISO 14443 TYPE C, Bluetooth, or the like) with the in-vehicle device 20 and the second portable terminal 40. The communication partner is not limited to the in-vehicle device 20 and the second portable terminal 40, and can communicate with other devices that can perform non-contact near field communication. A contact type communication interface may be used.

The storage unit 36 includes a device (for example, a flash memory) that does not require a storage holding operation, and can store various types of information.
The control unit 37 includes a CPU, a ROM, a RAM, an I / O, and the like, and is a part that comprehensively controls the public communication unit 32, the HMI 33, the non-contact communication interface 35, and the storage unit 36 based on a program.

(4) Second mobile terminal 40
Next, details of the second portable terminal 40 will be described with reference to the block diagram of FIG. The second portable terminal 40 includes a wireless antenna 41, a public communication unit 42, an HMI 43, a non-contact communication interface 45, a storage unit 46, and a control unit 47.

The wireless antenna 41 is an antenna for wireless connection to the wireless public line network 51.
The public communication unit 42 is a part that transmits and receives information by wireless communication (for example, communication such as CDMA) via the wireless antenna 41.

  The HMI 43 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, a liquid crystal display, a speaker, a microphone, and the like.

  The non-contact communication interface 45 is an interface for performing non-contact short-range wireless communication (for example, communication using ISO 14443 TYPE C, Bluetooth, or the like) with the in-vehicle device 20 and the first mobile terminal 30. The communication partner is not limited to the in-vehicle device 20 and the first portable terminal 30, and can communicate with other devices that can perform non-contact short-range wireless communication. A contact type communication interface may be used.

The storage unit 46 includes a device (for example, a flash memory) that does not require a storage holding operation, and can store various types of information.
The control unit 47 includes a CPU, a ROM, a RAM, an I / O, and the like, and is a part that comprehensively controls the public communication unit 42, the HMI 43, the non-contact communication interface 45, and the storage unit 46 based on a program.

(5) Roadside device 53
Next, the roadside device 53 will be described. The roadside device 53 has a function of transmitting and receiving information with the in-vehicle device 20 by DSRC, a function of decrypting encrypted information sent from the in-vehicle device 20, a function of encrypting information to be sent to the in-vehicle device 20, and a wired It has a function of communicating with an information center (not shown) through communication. The information center is a center that manages the roadside device 53, and has a function of performing a payment process (billing processing to a card company, etc.) based on the billing process information sent from the roadside device 53.

(6) Site server 55 for mobile terminals
Next, the mobile terminal site server 55 will be described. The mobile terminal site server 55 stores the HTML data for the first mobile terminal 30, the function of storing the setup AP (Application) to be operated on the first mobile terminal 30, the stored data, etc. A function of transmitting to the first portable terminal 30 via the wireless public network 51 is provided.

(7) Area issuing server 57
Next, the area issuing server 57 will be described. The area issuance server 57 stores the information required when the first mobile terminal 30 creates an ETC area in the storage unit 36 (ETC area creation information), ETC area creation information, and the wireless public line network 51. Via the first mobile terminal 30.

(8) Card center server 59
Next, the card center server 59 will be described. The card center server 59 performs a function of communicating with the first portable terminal 30 via the wireless public line network 51, decrypts information encrypted by the in-vehicle device 20, and encrypts information to be sent to the in-vehicle device 20. It has a function, a function of generating card information for in-vehicle devices based on information such as a function and a predetermined ID. The in-vehicle device card information is information that is scheduled to be stored in the in-vehicle device 20, and is information that is read from the in-vehicle device 20 and used for billing as necessary.

[Description of operation]
Next, the operation of the ETC system 10 will be described. However, in the following, the description will focus on the parts related to the present invention, and the charging process executed at the gate of the toll gate (the in-vehicle device card information stored in the in-vehicle device 20 is passed to the roadside device 53 and charged) The description of the processing already disclosed by Japanese Patent Application No. 2006-313377, such as the processing performed), is omitted.

(1) Registration of card information for in-vehicle device to first mobile terminal 30 First, processing for registering card information for in-vehicle device in the first mobile terminal 30 will be described with reference to the explanatory diagram of FIG.

  When the control unit 37 of the first portable terminal 30 accepts a setup AP acquisition request command from the user via the HMI 33 (specifically, an operation button), the portable terminal site server via the wireless public line network 51. An acquisition request for the setup AP is made to 55 (S50).

Receiving this request, the mobile terminal site server 55 transmits the designated setup AP to the first mobile terminal 30 via the wireless public network 51 (S55).
The control unit 37 of the first portable terminal 30 that has received the setup AP starts execution of the setup AP, and requests the area issuing server 57 for ETC area creation information via the wireless public line network 51 ( S60). The “ETC area creation information” here is information for setting a storage area (area) for specific card information in the storage unit 36 of the first portable terminal 30.

  Upon receiving the request for ETC area creation information, the area issuing server 57 generates information (ETC area creation information) necessary for creating an ETC area in the first mobile terminal 30. Then, the generated information is transmitted to the first portable terminal 30 via the wireless public line network 51 (S65).

The control unit 37 of the first mobile terminal 30 that has received the ETC area creation information generates an ETC area in the storage unit 36 using the received ETC area creation information.
Thereafter, the control unit 37 of the first portable terminal 30 receives a command to acquire in-vehicle device card information to be stored in the in-vehicle device 20 from the user via the HMI 33 (specifically, an operation button). Then, it communicates with the in-vehicle device 20 via the non-contact communication interface 35 to acquire the in-vehicle device specific information (management number, type registration number, vehicle number, etc.) from the in-vehicle device 20 and stores it in the ETC area of the storage unit 36. (S70). Then, the card information for the in-vehicle device is requested to the card center server 59 via the wireless public line network 51 (S75).

  Upon receiving this request, the card center server 59 generates in-vehicle device card information, encrypts the generated in-vehicle device card information, and transmits it to the first portable terminal 30 via the wireless public network 51 ( S80).

The control unit 37 of the first portable terminal 30 that has received the in-vehicle device card information stores the received in-vehicle device card information in the ETC area of the storage unit 36.
The in-vehicle device card information is registered in the first portable terminal 30 by such a procedure. Note that a plurality of types of on-vehicle device card information can be stored in the ETC area of the storage unit 36 of the first portable terminal 30 in the same procedure as described above.

(2) Registration of in-vehicle device card information to in-vehicle device 20 Next, in the processing procedure described above, an instruction to acquire in-vehicle device card information is sent via the HMI 33 (specifically, an operation button). Details of processing after one portable terminal 30 has received (mainly S70 to S80) and processing for registering card information for in-vehicle devices in the in-vehicle device 20 will be described using a ladder chart of FIG.

  When the control unit 37 of the first portable terminal 30 receives an instruction from the user via the HMI 33 (specifically, an operation button) to acquire in-vehicle device card information to be stored in the in-vehicle device 20, In-vehicle device specific information (management number, format registration number, vehicle number, etc.) is requested to the in-vehicle device 20 via the non-contact communication interface 35 (S105).

The control unit 27 of the in-vehicle device 20 that has received the request transmits the in-vehicle device specific information to the first mobile terminal 30 via the non-contact communication interface 25 (S110).
The control unit 37 of the first portable terminal 30 that has received the in-vehicle device specific information stores the received in-vehicle device specific information in the ETC area of the storage unit 36, and further, the card via the wireless antenna 31 and the public communication unit 32. The center server 59 is requested for in-vehicle device card information (S115). The information to be transmitted is not only the information meaning the request, but also the in-vehicle device specific information stored in the ETC area of the storage unit 36 and the card information for the mobile terminal stored in the storage unit 36 in advance. 59. The mobile terminal card information is card information used when the first mobile terminal 30 performs a charging process. The user of the first portable terminal 30 holds the first portable terminal 30 over the dedicated terminal at a convenience store, a restaurant, or the like, so that the card information for the portable terminal is read by the dedicated terminal and the charging process is executed. Is done.

  The card center server 59 that has received a request for in-vehicle device card information from the first mobile terminal 30 determines whether the received mobile terminal card information is valid (S120). Specifically, it is determined whether or not the mobile terminal card information is properly issued card information by referring to a database in which data related to the mobile terminal card information is stored. If it is determined by this determination that the mobile terminal card information is valid, the in-vehicle device card information is generated (S125). This in-vehicle device card information is information that is scheduled to be stored in the in-vehicle device 20, and is information that is read from the in-vehicle device 20 and used for billing as necessary.

When the card center server 59 generates the in-vehicle device card information, the card center server 59 transmits the generated in-vehicle device card information to the first portable terminal 30 (S130).
The control unit 37 of the first portable terminal 30 that has received the card information for the in-vehicle device generates a password (hereinafter also referred to as “password code A”) based on the card information for the portable terminal (S140), and receives it. The in-vehicle device card information and the generated password A are transmitted to the in-vehicle device 20 via the non-contact communication interface 25 (S145). “Generating a code based on card information for portable terminal” means that the card information for portable terminal is encrypted with a predetermined electronic key. This key is also owned by the in-vehicle device 20. The generated password A is stored in the storage unit 36.

  The control unit 27 of the in-vehicle device 20 that has received the in-vehicle device card information and the personal identification code A causes the storage unit 26 to store the received in-vehicle device card information and the personal identification code A (S150). At this time, the in-vehicle device card information is stored in an inactivated state. The “inactive state” means a state in which the card information for the in-vehicle device stored in the storage unit 26 cannot be read, and is determined by the state of the state flag provided in the storage unit 26. It has become. Specifically, the state flag state “OFF” corresponds to the inactivated state, and the state flag state “ON” corresponds to the activated state (readable state). In the inactive state, the card information for the in-vehicle device stored in the storage unit 26 cannot be read (such a lock function is provided).

  When the received in-vehicle device card information and password A are stored in the storage unit 26, the control unit 27 of the in-vehicle device 20 sends a notification that the storage is completed (registration completion notification) to the non-contact communication interface 25. Via the first mobile terminal 30 (S155).

  The control unit 37 of the first portable terminal 30 that has received the registration completion notification displays on the HMI 33 (specifically, a liquid crystal display) that the registration of the card information for the in-vehicle device to the in-vehicle device 20 is completed (S160). ).

(3) Flow of registration of second mobile terminal 40 Next, the flow of registration for enabling the card information for in-vehicle devices registered in the in-vehicle device 20 to be activated by the second mobile terminal 40. This will be described with reference to the ladder chart of FIG.

  When the control unit 37 of the first portable terminal 30 receives an instruction from the user to register the second portable terminal 40 in the in-vehicle device 20 via the HMI 33 (specifically, an operation button), the contactless communication is performed. The mobile terminal specific information (for example, terminal ID, mobile phone number, etc.) is requested to the second mobile terminal 40 via the interface 35 (S205).

  Upon receiving the request, the control unit 47 of the second mobile terminal 40 reads the mobile terminal specific information stored in the storage unit 46 and transmits it to the first mobile terminal 30 via the non-contact communication interface 45. (S210).

  The control unit 37 of the first mobile terminal 30 that has received the mobile terminal specific information from the second mobile terminal 40 generates a password (hereinafter also referred to as “password B”) based on the received mobile terminal specific information. It is generated and stored in the storage unit 36 (S215).

  Subsequently, the control unit 37 of the first portable terminal 30 generates activatable terminal information and stores it in the storage unit 36 (S220). The activatable terminal information includes the following information (i) to (iii) (see the data example in FIG. 10A).

(I) On-vehicle device card information specifying information to be permitted This information is an on-vehicle device that permits activation by the second mobile terminal 40 among a plurality of on-vehicle device card information stored in the storage unit 26 of the on-vehicle device 20. This is information for specifying device card information.

(Ii) Charge limit This information is information used when determining whether to permit activation of the card information for in-vehicle devices by the second portable terminal 40. It is determined that new activation is permitted only when the total amount charged in the past by the second mobile terminal 40 is within the charge limit.

(Iii) Chargeable period This information is information used when determining whether to permit activation of the card information for in-vehicle devices by the second portable terminal 40. Note that it is determined that new activation is permitted only when the second mobile terminal 40 is about to be activated within the billable period.

  Subsequently, the control unit 37 of the first mobile terminal 30 makes a request for adding the second mobile terminal 40 as an activatable terminal to the in-vehicle device 20 via the non-contact communication interface 35 (S225).

  Upon receiving this request, the control unit 27 of the in-vehicle device 20 determines whether the first portable terminal 30 is valid or not to the first portable terminal 30 via the non-contact communication interface 25. A password is requested (S230).

  Receiving this request, the control unit 37 of the first portable terminal 30 reads the password code A stored in the storage unit 36 and transmits it to the in-vehicle device 20 via the non-contact communication interface 35 (S235).

  The control unit 27 of the in-vehicle device 20 that has received the personal identification code A determines the validity of the first portable terminal 30 that is the communication partner based on the personal identification code A (S240). Specifically, it is performed by determining whether or not the received password code A matches the password code A stored in the storage unit 26. As a result of the determination, when it is determined that the first portable terminal 30 is valid, the control unit 27 of the in-vehicle device 20 sends the activatable terminal information and the code of the terminal to be registered via the non-contact communication interface 25. Request to the first portable terminal 30 (S245).

  The control unit 37 of the first portable terminal 30 that has received this request sends the personal identification code B generated in S215 and the activatable terminal information generated in S220 to the in-vehicle device 20 via the non-contact communication interface 35. Transmit (S250).

  Receiving these pieces of information, the control unit 27 of the in-vehicle device 20 stores the received information (password code B and activatable terminal information) in the storage unit 26 (S255). Then, the control unit 27 of the in-vehicle device 20 transmits a notification that the storage is completed (registration completion notification) to the first portable terminal 30 via the non-contact communication interface 25 (S260).

  The control unit 37 of the first portable terminal 30 that has received the registration completion notification displays on the HMI 33 (specifically, a liquid crystal display) that the card information for the in-vehicle device has been registered in the in-vehicle device 20 (S265). Then, the code B generated in S215 and the activatable terminal information generated in S220 are transmitted to the second portable terminal 40 via the non-contact communication interface 35 (S270).

  The control unit 47 of the second portable terminal 40 that has received the information stores the received information (password code B and activatable terminal information) in the storage unit 46 (S275). And the control part 47 of the 2nd portable terminal 40 displays on the HMI43 (specifically liquid crystal display) that the 2nd portable terminal 40 was registered into the vehicle-mounted apparatus 20 as an activatable terminal (S280). ).

(4) About Activation Terminal Registration Processing Here, execution is started when the control unit 27 of the in-vehicle device 20 receives an activation terminal addition request (S225 described above) from the terminal via the non-contact communication interface 25. (Activation terminal registration process) will be described more generally using the flowchart of FIG.

  When starting the execution of the activation terminal registration process, the control unit 27 of the in-vehicle device 20 requests a personal identification code via the non-contact communication interface 25 to the terminal that has requested activation terminal addition (S305).

  Subsequently, the control unit 27 of the in-vehicle device 20 receives the password code from the terminal via the non-contact communication interface 25 (S310). Then, based on the received code, it is determined whether or not the terminal that has made the activation terminal addition request is valid (S315). Specifically, whether the received password code matches the password code stored in the storage unit 26 and the terminal (first mobile terminal 30) that stores the card information for the in-vehicle device. This is done by determining whether or not. As a result of the determination, if it is determined that the terminal that has requested activation terminal addition is valid (S315: Yes), the process proceeds to S325, and it is determined that the terminal that has requested activation terminal addition is not valid. In the case (S315: No), the process proceeds to S320.

  In S320, which proceeds when it is determined that the terminal that has requested activation terminal addition is not valid, an error is notified to the terminal that has requested activation terminal addition via the non-contact communication interface 25.

  On the other hand, in S325, which proceeds when it is determined that the terminal that has requested activation terminal addition is legitimate, the terminal is requested for the activatable terminal information and password of the registration target terminal via the non-contact communication interface 25. To do.

  Subsequently, the control unit 27 of the in-vehicle device 20 receives the activation-enabled terminal information and the password code (password code B) of the registration target terminal from the terminal that has requested activation terminal addition via the non-contact communication interface 25. Receive (S330). When the activatable terminal information of the registration target terminal and the code (code B) are received, they are stored in the storage unit 26 (S335). Then, the terminal that has made the activation terminal addition request is notified of the completion of registration through the non-contact communication interface 25 (S340), and this process (activation terminal registration process) is terminated.

(5) About activation process Next, the activation process which the control part 27 of the vehicle-mounted apparatus 20 performs is demonstrated using the flowchart of FIG. The activation process is started when the power supply to the in-vehicle device 20 is started (for example, when the engine key is turned and the accessory power is supplied).

  When starting the execution of the activation process, the control unit 27 of the in-vehicle device 20 first determines whether or not the entrance information is stored in the storage unit 26 (S405). This entrance information is information indicating which entrance IC has entered the toll road from what month, day, hour and minute.

  As a result of the determination in S405, when it is determined that the entrance information is stored in the storage unit 26 (S405: Yes), the process proceeds to S480, and it is determined that the entrance information is not stored in the storage unit 26 (S405: No), the process proceeds to S410.

  In S410, which proceeds when it is determined that the entrance information is stored in the storage unit 26, an attempt is made to receive a personal identification code from a terminal that can communicate via the non-contact communication interface 25. If any password can be received, it is determined whether or not a terminal that can communicate via the non-contact communication interface 25 is valid as the first portable terminal 30 based on the received password (S415). Specifically, non-contact communication is performed in one or a plurality of password codes stored in the storage unit 26 and in the password code of the terminal (first portable terminal 30) in which the card information for in-vehicle devices is registered. It is checked whether or not there is a password that is the same as the password received via the interface 25. If there is the same password, the terminal determines that the terminal is valid as the first portable terminal 30.

  As a result of the determination in S415, if it is determined that a terminal that can communicate via the non-contact communication interface 25 is valid as the first portable terminal 30 (S415: Yes), the process proceeds to S465, and the first If it is determined that the mobile terminal 30 is not valid (S415: No), the process proceeds to S420.

  If it is determined that the first portable terminal 30 is not valid, the process proceeds to S420, where the terminal that can communicate via the non-contact communication interface 25 is valid as the second portable terminal 40 based on the password received in S410. Determine whether or not. Specifically, the one or a plurality of password codes stored in the storage unit 26 and the same password code received via the non-contact communication interface 25 in the password code of the second portable terminal 40. It is determined whether or not there is a personal identification code. If there is the same personal identification code, the terminal determines that the terminal is valid as the second portable terminal 40.

  As a result of the determination in S420, if it is determined that a terminal capable of communicating via the non-contact communication interface 25 is valid as the second portable terminal 40 (S420: Yes), the process proceeds to S425, and the second If it is determined that the mobile terminal 40 is not valid (S420: No), the process returns to S410. Note that when returning the processing to S410, the user may be notified of the error by the HMI 23 (specifically, an LED or the like).

  On the other hand, in S425, which proceeds when it is determined that the second portable terminal 40 is valid, the control unit 27 reads the activatable terminal information corresponding to the password received in S410 from the storage unit 26. And based on the read-out information, the card | curd information for vehicle-mounted apparatuses activated is specified from the card | curd information for vehicle-mounted apparatuses memorize | stored in the memory | storage part 26 (S430).

  Subsequently, the control unit 27 of the in-car device 20 refers to the activatable terminal information read out in S425 and determines whether or not a charging limit has been set (S435). If it is determined that the charge limit is set (S435: Yes), the process proceeds to S440. If it is determined that the charge limit is not set (S435: No), the process proceeds to S450. To do.

  In S440, which proceeds when it is determined that the charging limit is set, the past charging history information related to the card information for in-vehicle devices activated by the terminal corresponding to the activatable terminal information read in S425 is referred to. Then, it is determined whether or not the sum of the billing amounts is below the billing limit amount (S445). If it is determined that the total charge amount exceeds the charge limit (S445: Yes), the process proceeds to S460, and if it is determined that the total charge amount does not exceed the charge limit (S445: No), the process proceeds to S450.

  In S450, it is determined with reference to the activatable terminal information read in S425 whether or not a chargeable period is set. If it is determined that the chargeable period is set (S450: Yes), the process proceeds to S455. If it is determined that the chargeable period is not set (S450: No), the process proceeds to S465. To do.

  In S455, which proceeds when it is determined that the chargeable period is set, it is determined whether or not the current time is within the chargeable period. If it is determined that the current time is within the chargeable period (S455: Yes), the process proceeds to S465. If it is determined that the current time is not within the chargeable period (S455: No), the process proceeds to S460.

  In S460, an error is notified. That is, the user is informed via the HMI 23 (specifically, LED or speaker) that activation cannot be performed because the charge limit is exceeded, or activation is not possible because it is not a chargeable period. Then, this process (activation process) is terminated.

  In S <b> 480, which proceeds when it is determined that the entrance information is not stored in the storage unit 26 in S <b> 405, the control unit 27 of the in-vehicle device 20 reads the activation setting information. This activation setting information is information stored in a deactivation process to be described later, information for specifying in-vehicle device card information deactivated in the deactivation process, and the in-vehicle device card This is information that identifies the terminal that activated the information (see the data example in FIG. 10B). In S470, which will be described later, the card information for the in-vehicle device is activated based on the activation setting information.

  In S465 that proceeds when the determination is affirmative in S415, a negative determination in S450, or a positive determination in S455, information that identifies the activated terminal is stored. That is, when a terminal communicable via the non-contact communication interface 25 is determined to be valid as the first portable terminal 30 and reaches this step (S465) (S415: Yes), the first portable terminal Information that can identify the terminal 30 (for example, a terminal ID, a mobile phone number, a password A, etc.) is stored in the storage unit 26. Further, when it is determined that a terminal capable of communicating via the non-contact communication interface 25 is valid as the second portable terminal 40 and reaches this step (S465) (S420: Yes), the second portable terminal Information that can identify the terminal 40 (for example, a terminal ID, a mobile phone number, a password B, etc.) is stored in the storage unit 26.

  Subsequently, the control unit 27 of the in-vehicle device 20 activates the in-vehicle device card information (S470). That is, if the determination in S415 is affirmative and S470 is reached, the in-vehicle device card information stored by the first portable terminal 30 is activated, and if the determination in S420 is S4 and S470 is reached, S430 is activated. The card information for in-vehicle devices specified in step S4 is activated. If the determination in S405 is affirmative and S470 is reached, the card information for in-vehicle devices based on the activation setting information is activated in S480.

  Subsequently, the control unit 27 of the in-vehicle device 20 notifies the user that the activation has been completed via the HMI 23 (specifically, an LED or a speaker). Then, this process (activation process) is terminated.

(6) Deactivation Process Next, the deactivation process executed by the control unit 27 of the in-vehicle device 20 will be described with reference to the flowchart of FIG. The deactivation process is started when the main power supply to the in-vehicle device 20 is cut off (for example, when the supply of accessory power is cut off by turning the engine key). . The power necessary for executing the deactivation process is always provided by the supplied power.

  When starting the execution of the deactivation process, the control unit 27 of the in-vehicle device 20 first determines whether or not entrance information is stored in the storage unit 26 (S505). When it is determined that the entrance information is stored in the storage unit 26 (S505: Yes), the process proceeds to S510, and when it is determined that the entrance information is not stored in the storage unit 26 (S505: No). , The process proceeds to S515.

  In S510 that proceeds when it is determined that the entrance information is stored in the storage unit 26, information for specifying the card information for the in-vehicle device that is currently activated and the card information for the in-vehicle device are activated as the activation setting information. Information (for example, terminal ID, mobile phone number, password A, etc.) that can identify the converted terminal is stored in the storage unit 26. Then, the process proceeds to S520.

  On the other hand, if it is determined that the entrance information is not stored in the storage unit 26, the process proceeds to S515. If the activation setting information is currently stored in the storage unit 26, the activation setting information is deleted. If information specifying the converted terminal is stored in the storage unit 26, the information is deleted. Then, the process proceeds to S520.

In S520, the card information for in-vehicle devices in the activated state is deactivated. Then, this process (deactivation process) is terminated.
(7) Accounting history writing process Next, the accounting history writing process executed by the control unit 27 of the in-vehicle device 20 will be described with reference to the flowchart of FIG. The billing history writing process uses the card information for the in-vehicle device in the activated state, and billing processing (the processing in which the card information for in-vehicle device stored in the in-vehicle device 20 is passed to the roadside device 53 and charged) Execution starts immediately after the completion of.

  When starting the execution of the charging history writing process, the control unit 27 of the in-vehicle apparatus 20 specifies the terminal that has activated the in-vehicle apparatus card information used in the charging process (S555). This is specified based on the information stored in the storage unit 26 in S465 of the activation process described above or the activation setting information stored in the storage unit 26 in S510 of the deactivation process described above.

  Then, the billing information including the information specifying the terminal that activated the in-vehicle device card information is stored in the billing history table (S560). Then, this process (billing history writing process) is terminated.

  Here, an example of the accounting history table stored in the storage unit 26 will be described with reference to FIG. As shown in FIG. 10 (c), each record (billing information) is composed of passage processing record information including an entrance number, an exit number, and a passage date and time, and payment information including a vehicle type, an amount, a billing card, and an activation terminal. Become. The entrance number is a number that can identify the entrance that has entered the toll road. The exit number is a number that can identify the exit from the toll road. The passage date and time is the date and time when the billing process was performed. The vehicle type is information indicating the type of vehicle (light vehicle, ordinary vehicle, large vehicle, etc.) on which the in-vehicle device 20 is mounted. The amount is the amount of the toll on the toll road. The billing card is information (card ID) that can specify the card information for in-vehicle devices used for payment of tolls (billing processing). The activation terminal is information (telephone number) that can identify the terminal that has activated the card information for in-vehicle devices used for payment of tolls (billing processing).

A record composed of such information is created and added to the charging history table every time the charging process is completed.
[Effect of the embodiment]
According to the ETC system 10 of the above-described embodiment, not only the first mobile terminal 30 that stores the card information for in-vehicle device in the in-vehicle device 20 but also registered in the in-vehicle device 20 via the first mobile terminal 30. The second mobile terminal 40 can also activate the card information for in-vehicle devices stored in the in-vehicle device 20. Therefore, for example, if the owner of the second portable terminal 40 gets on the vehicle even after the owner of the first portable terminal 30 gets off the vehicle, the card information for the in-vehicle device is arbitrarily activated. be able to. That is, usability is improved. Moreover, since the second portable terminal 40 is not registered in the in-vehicle device 20 as a terminal that can activate the card information for the in-vehicle device unless the first portable terminal 30 is used, it is considered that the security can be sufficiently maintained. .

  In addition, when the second portable terminal 40 is registered in the in-vehicle device 20 as an activatable terminal, the first portable terminal 30 is authenticated (S305 to S315), so the first portable terminal 30 has high legitimacy and security.

  The in-vehicle device 20 has a condition for activation by the second portable terminal 40. Specifically, the conditions are card information for in-vehicle devices that can be activated, a charge limit at that time for determining whether or not activation is permitted, and a period for which activation is permitted. Since such conditions are provided for activation by the second portable terminal 40, the owner of the first portable terminal 30 more actively registers the second portable terminal 40 in the in-vehicle device 20. Will come to let you.

  In addition, information that can identify the terminal that activated the card information for in-vehicle devices used in the billing process is stored as one of the history information of the billing process (item in FIG. 10C). (See “Activated Terminal”). For this reason, the owner of the first mobile terminal 30 can determine later by which mobile terminal the charging process has been executed by using the card information for the in-vehicle device triggered by the activation. Therefore, the owner of the first portable terminal 30 more actively registers the second portable terminal 40 in the in-vehicle device 20.

[Correspondence with Claims]
The correspondence between the terms used in the description of the embodiment and the terms described in the claims is shown.
(1) On-vehicle device The storage unit 26 corresponds to charging destination specifying information storage unit, determination information storage unit, and history information storage unit, and the control unit 27 corresponds to charging process execution unit, setting unit, registration unit, and change unit. The in-vehicle device card information corresponds to the billing destination specifying information. In addition, starting from the request for additional registration of the activatable terminal from the first portable terminal 30 in S225 described above, the control is performed to store the code B and the activatable terminal information in the storage unit 26 in S255 described above. A command issued by the unit 27 to the storage unit 26 corresponds to a storage command. In addition, the password code transmitted from the terminal in S410 described above corresponds to a change command and determination information. Further, the password A received in S235 described above also corresponds to the determination information. The activatable terminal information corresponds to the execution condition. Further, each piece of information stored in the charging history table corresponds to history information, and in particular, information stored as an activation terminal among them corresponds to activation execution terminal information.

(2) First mobile terminal The control unit 37 corresponds to a billing destination specific information storage control unit, a change command transmission unit, and a storage command transmission unit.

(3) Second mobile terminal The control unit 47 corresponds to a change command transmission unit and a storage request unit.

It is a block diagram which shows the whole structure of an ETC system. It is a block diagram which shows schematic structure of a vehicle-mounted apparatus and a 1st portable terminal. It is a block diagram which shows schematic structure of a 2nd portable terminal. It is explanatory drawing for demonstrating the flow in which card information for vehicle equipment is registered into the 1st portable terminal. It is a ladder chart for demonstrating the flow that the card information for vehicle equipment is registered into a vehicle equipment. It is a ladder chart for demonstrating the flow in which a 2nd portable terminal is registered into a vehicle-mounted apparatus. It is a flowchart for demonstrating the activation terminal registration process performed with a vehicle-mounted apparatus. It is a flowchart for demonstrating the activation process performed with a vehicle-mounted apparatus. It is a flowchart for demonstrating the inactivation process and charging log | history write-in process which are performed with a vehicle-mounted apparatus. It is explanatory drawing for demonstrating activatable terminal information, activation setting information, and a charge history table.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... ETC system, 20 ... In-vehicle apparatus, 21 ... Radio antenna, 22 ... DSRC part, 23 ... HMI, 24 ... SAM, 25 ... Non-contact communication interface, 26 ... Storage part, 27 ... Control part, 30 ... First Mobile terminal, 31 ... wireless antenna, 32 ... public communication unit, 33 ... HMI, 35 ... non-contact communication interface, 36 ... storage unit, 37 ... control unit, 40 ... second mobile terminal, 41 ... wireless antenna, 42 ... Public communication unit 43 ... HMI 45 ... Non-contact communication interface 46 ... Storage unit 47 ... Control unit 51 ... Wireless public network 53 ... Roadside device 55 ... Site server for portable terminal 57 ... Area issue server 59 ... Card center server.

Claims (11)

Charging destination specifying information storage means for storing charging destination specifying information which is information stored based on a command from the portable terminal and is information that can specify a charging destination;
Billing processing execution means for performing billing processing by communicating with the roadside device using the billing destination specifying information stored in the billing destination specifying information storage means;
The charging destination specifying information stored in the charging destination specifying information storage unit is set to either an activated state that is available or an inactive state that is not available. Setting means;
Determination information storage means capable of storing determination information for use in determining whether or not the charging destination identification information is an activatable terminal capable of changing from the inactive state to the active state;
The first portable terminal or the second portable terminal different from the first portable terminal based on the storage command from the first portable terminal that stores the charging destination identification information in the charging destination identification information storage means Registration means for storing the determination information in the determination information storage means;
When the change instruction for changing the billing destination specifying information from the inactive state to the active state is received from the mobile terminal, whether or not the mobile terminal is an activatable terminal is stored in the determination information storage unit A changing means for making a determination using the determination information and causing the setting means to change the billing destination specifying information from an inactivated state to an activated state only when the determination is affirmative;
A vehicle-mounted device comprising: The in-vehicle device according to claim 1,
The registration unit is configured on the condition that the determination information sent from the first portable terminal matches the determination information about the first portable terminal stored in the determination information storage unit. Executing the storage command from the portable terminal of
In-vehicle device characterized by In the in-vehicle device according to claim 1 or 2,
The registration means further receives an execution condition of the change command from the second portable terminal that is the activatable terminal from the first portable terminal, and stores it in the determination information storage means,
The change means determines whether or not to execute the change command from the second portable terminal that is the activatable terminal, in addition to the execution condition stored in the determination information storage means. ,
In-vehicle device characterized by The in-vehicle device according to claim 3,
The charging destination specifying information storage means stores a plurality of charging destination specifying information,
The registration unit associates, as one of the execution conditions, specific information for specifying at least one of the charging destination specifying information stored in the charging destination specifying information storage unit with the activatable terminal. Memorize it in the judgment information storage means,
The changing means executes the change command only for the billing destination specifying information specified by the specifying information;
In-vehicle device characterized by In the in-vehicle device according to claim 3 or claim 4,
The registration unit stores a charging limit relating to the charging destination specifying information in the determination information storage unit as one of the execution conditions,
The change means executes the change command only when a current charge amount related to the charge destination identification information targeted for the change command is within the charge limit amount;
In-vehicle device characterized by In the in-vehicle device according to any one of claims 3 to 5,
The registration unit stores, as one of the execution conditions, a billable period related to the billing destination specifying information in the determination information storage unit,
The change means executes the change command only when the current time is within the billable period,
In-vehicle device characterized by In the in-vehicle device according to any one of claims 1 to 6,
History information storage means for storing the history information of the accounting process,
When the charging process is performed, the charging process execution unit stores history information about the charging process in the history information storage unit, and the charging destination specifying information used for the charging process is activated. Storing the activation execution terminal information, which is information that can identify the terminal, in the history information storage unit in association with the accounting process;
In-vehicle device characterized by Charging destination specifying information storage control means for storing charging destination specifying information, which is information capable of specifying the charging destination, in the in-vehicle device;
A change command transmitting means for transmitting to the in-vehicle device a change command for changing the billing destination specifying information stored in the in-vehicle device from an inactive state to an activated state;
A storage command for storing determination information used when determining whether or not the charging destination identification information is an activatable terminal capable of changing the inactive state from the inactive state to the active state. Storage command transmission means for transmitting to the in-vehicle device;
With
The storage command transmission means transmits, based on a request from another mobile terminal, a command to store the determination information in the in-vehicle device regarding the mobile terminal as the storage command to the in-vehicle device,
The first portable terminal characterized by this.   The program for functioning a computer as said each means of the 1st portable terminal of Claim 8. Change command transmitting means for transmitting to the in-vehicle device a change command for changing charging destination specifying information, which is information stored in the in-vehicle device and is information that can specify a charging destination, from an inactive state to an activated state; ,
Storing in the in-vehicle device determination information used when determining whether or not the charging destination identification information is an activatable terminal that can be changed from an inactivated state to an activated state. A storage requesting means for performing the billing destination specifying information via the portable terminal storing the in-vehicle device;
A second portable terminal comprising:   The program for functioning a computer as said each means of the 2nd portable terminal of Claim 10.

Images