Patent Description:
Vehicle keys used for locking the doors of vehicles or other purposes have recently been transitioning to electronic keys, which have been developed from conventional mechanical keys. For example, the driver, holding an electronic key inside a pocket, approaches the vehicle. The door to the driver's seat is then automatically unlocked. In more advanced forms, such an electronic key is incorporated in a portable terminal apparatus such as a so-called smartphone. That is, it is unnecessary for the driver to carry a vehicle key separately from a portable terminal apparatus.

Besides electronic keys, valet parking has recently been spread mainly overseas, and is also being put into practical use in Japan. In the valet parking, a driver completely entrusts an employee of the parking lot to drive the vehicle into the parking lot or out of the parking lot. Assume for example that a guest of a hotel has driven a vehicle and arrived at the entrance of the hotel. Then, the guest temporarily pulls over the vehicle at the entrance and requests the employee of the hotel to park the vehicle. The employee drives the vehicle of the guest from the entrance to the parking lot and parks the vehicle in an appropriate space. When the guest is about to depart from the hotel, the guest requests the employee of the hotel to drive the vehicle out of the parking lot. Upon receiving the request, the employee of the hotel drives the vehicle of the guest from the parking lot to the entrance and temporarily pulls over the vehicle at the entrance. Then, the guest drives the vehicle toward the next destination.

In the valet parking, the management of a vehicle of a guest is entrusted to a hotel for a time period from when the guest arrives at the hotel to when the guest departs from the hotel. For example, an employee of a hotel moves vehicles to the parking lot one by one every time when a guest arrives with a vehicle, or all at once when a certain number of vehicles have arrived. In some cases, an employee moves a vehicle of a long-stay guest within a parking lot. In many cases, an employee of a hotel uses a portable terminal apparatus carried by the employee as a temporal electronic key for a vehicle during a period while the guest of the vehicle stays in the hotel. In such case, it is necessary to additionally allocate a portable terminal apparatus as an electronic key to a certain vehicle and release the allocation in series, and techniques for such application are increasingly spreading these days.

In addition, with recent advancements of automated driving technologies, automated valet parking has been attracting attention, which allows a vehicle capable of automated driving to travel within a parking lot to be moved into or out of a parking space. In the automated valet parking, in accordance with an instruction from an owner of a vehicle who carries a portable terminal apparatus temporarily or permanently permitted as an electronic key for the vehicle or from an employee of a hotel who is entrusted by the owner (someone who is allowed to instruct the vehicle), the vehicle moves into or out of a parking spot by itself. The moving of the vehicle into or out of a parking spot needs to be triggered by an instruction from someone who is permitted to instruct the vehicle. For this reason, there is a demand for a technique of associating a portable terminal apparatus of someone who is permitted to instruct a vehicle with the corresponding vehicle.

In <CIT>, the owner of a vehicle issues a password to a non-owner (corresponding to an employee of a hotel). The non-owner inputs identification information on the portable terminal apparatus of the non-owner and the password to a server. Then, the server starts management by linking the identification information on the portable terminal apparatus of the non-owner with identification information on a portable terminal apparatus of the owner. In <CIT>, a user of a car sharing service notifies a server of identification information on a portable terminal apparatus of the user, identification information on a vehicle the user requests, and duration of usage. When the vehicle is available in the duration of usage, the server transmits electronic key information to the portable terminal apparatus of the user.

However, in <CIT>, if the owner fails to frequently update the password, the password propagates from a permitted third party to a non-permitted third party, enabling the non-permitted third party to use a desired portable terminal apparatus as the electronic key. In <CIT>, anyone who has happened to obtain identification information on a vehicle can use a desired portable terminal apparatus as the electronic key. In either case, there remains a security problem that a portable terminal apparatus whose owner is unknown can be used as an electronic key of a vehicle.

<CIT>discloses a vehicle security system having an authentication server in communication with a portable device in a vehicle, which in turn is in communication with vehicle components.

<CIT> discloses an electronic key system in which an electronic key server makes settings in accordance with input information.

<CIT> discloses vehicle installations having first and second authentication means for allowing the use of a vehicle.

In view of this, the present invention has an object to provide a terminal-vehicle linking apparatus and a related computer-readable medium capable of securely linking plural portable terminal apparatus with a registered vehicle.

This object is accomplished by the features of the independent claims.

A terminal-vehicle linking apparatus has the features of claim <NUM>. A terminal-vehicle linking method includes: receiving registration of a portable terminal apparatus to be used to drive a vehicle or instruct the vehicle; receiving registration of an in-vehicle apparatus mounted in the vehicle; and when authentication information received from the portable terminal apparatus of which the registration has been received coincides with authentication information transmitted in advance to the in-vehicle apparatus of which the registration has been received, determining that it is possible to drive the vehicle or instruct the vehicle on operation by using the portable terminal apparatus.

Other means will be described in the DETAILED DESCRIPTION OF THE EMBODIMENTS.

According to the present invention, it is possible to securely link a registered portable terminal apparatus with a registered vehicle.

Hereinafter, an embodiment for implementing the present invention (referred to as "the present embodiment") will be described in detail with reference to the drawings and the like. The present embodiment is an example where when an owner of a vehicle capable of automated driving or an employee of a facility who is permitted to instruct or drive the vehicle by the owner of the vehicle (for example, an employee of a hotel, or the like) instructs the vehicle using his/her own portable terminal apparatus (indicating a portable terminal apparatus of the owner when the owner instructs the vehicle or a portable terminal apparatus of the employee when the employee instructs the vehicle) as an electronic key, the electronic key is associated with the vehicle to be driven. However, the range of application of the present invention is not limited to this. The present invention can be applied for example to a case where a certain vehicle is driven by a plurality of people on a daily basis, like car sharing.

The vehicle is a private or business automobile including a four-wheeled vehicle and a two-wheeled vehicle.

The electronic key is a key for a vehicle, and generally has any shape such as a card-type, biscuit-type, or cigarette case-type shape. A medium such as an IC chip embedded inside the key stores electronic information necessary for the operation of the vehicle.

The driver encompasses not only a person who drives a vehicle but also a person who gives instruction including driving to a vehicle. The person who drives a vehicle includes not only an owner who owns an automobile (including a person who is permitted to drive the vehicle by an owner of an automobile) but also a non-owner who is in position to be temporarily entrusted with a vehicle of another person. Note that a typical example of the non-owner is an employee of a hotel. An employee of a hotel, in addition to driving a vehicle within the property (a parking lot, a road, and the like) of the hotel, sometimes enters the inside of the vehicle to conduct cleaning, inspection, and the like. The owner can instruct the vehicle and the non-owner basically cannot instruct any vehicles. However, if the non-owner is given the rights to instruct the vehicle from the owner for some reason, the non-owner is also allowed to instruct the vehicle.

The portable terminal apparatus is a portable computer for use in taking, transmission and reception of e-mails, and other purposes as a "smartphone" and the like, in general. The portable terminal apparatus of the present embodiment has the same function as an electronic key. The owner instructs the vehicle while carrying his/her own portable terminal apparatus, and drives the vehicle under a certain circumstance. The non-owner also temporarily drives the vehicle while carrying his/her own portable terminal apparatus.

The in-vehicle apparatus is a computer to be mounted in a vehicle, and controls at least the locking of the door of the vehicle and the start and stop of the engine. More specifically, once detecting that the portable terminal apparatus is present around the in-vehicle apparatus itself (within a close range of approximately <NUM> meter), the in-vehicle apparatus acquires the identifier of the portable terminal apparatus from the medium in the portable terminal apparatus. The in-vehicle apparatus then inquires of a terminal-vehicle linking apparatus (which will be described later soon) whether the acquired identifier is genuine. Upon receipt of a reply saying that the identifier is genuine, the in-vehicle apparatus permits the driver to carry out the unlocking of the door of the vehicle, the starting of the engine, and the like. The terminal-vehicle linking apparatus is a computer that stores the identifier of the in-vehicle apparatus while linking the identifier of the in-vehicle apparatus with the identifier of the portable terminal apparatus capable of functioning as the electronic key of the vehicle.

The configuration of a terminal-vehicle linking apparatus <NUM> and the like will be described along <FIG>. The terminal-vehicle linking apparatus <NUM> is operated by a manager of a parking lot or a person who is entrusted by the manager of the parking lot (hereinafter, collectively referred to as the manager of the parking lot). The manager of a parking lot often is a hotel, a large-scale commercial facility, a multi-family building, a rail station, an airport terminal building, or the like, but also may be a car sharing company, a taxi company, a parcel delivery company, or the like. The terminal-vehicle linking apparatus <NUM> is normally installed in an office space near the parking lot. Alternatively, it is also possible to configure a terminal-vehicle linking function as an application on a cloud computing system, for example. In this case, the terminal-vehicle linking function can be disposed at any desired position as long as communications are possible for example on the Internet.

The terminal-vehicle linking apparatus <NUM> includes a central control device <NUM>, an input device <NUM>, an output device <NUM>, a main storage device <NUM>, an auxiliary storage device <NUM>, and a communication device <NUM>. These devices are connected together through a bus. The auxiliary storage device <NUM> stores linkage information <NUM>, terminal apparatus information <NUM>, and vehicle information <NUM>. In the main storage device <NUM>, a terminal-vehicle registering unit <NUM> and a terminal-vehicle linking unit <NUM> are programs. In the following description, when the acting subject is mentioned like "the OO unit do something ", this means that the central control device <NUM> reads out the OO unit from the auxiliary storage device <NUM> and loads the OO unit into the main storage device <NUM>, and then implements the function of the OO unit (described in detail later). The terminal-vehicle linking apparatus <NUM> can be connected to one or a plurality of in-vehicle apparatuses <NUM> and one or a plurality of portable terminal apparatuses <NUM> through a network <NUM>.

The in-vehicle apparatus <NUM> includes a central control device <NUM>, an input and output device <NUM> having a display and a touch panel, an auxiliary storage device <NUM>, and a communication device <NUM>. These devices are connected together through a bus. In the following description, when the acting subject is mentioned like "the in-vehicle apparatus <NUM> do something", this means that the central control device <NUM> reads out a predetermined program (not illustrated) from the auxiliary storage device <NUM> and loads the program into a main storage device (not illustrated), and then implements the function of the program. Separately from this, the terminal-vehicle registering unit <NUM> and the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> also can serve as the acting subject of the in-vehicle apparatus <NUM> (such as causing the in-vehicle apparatus <NUM> to display specific information). The auxiliary storage device <NUM> stores an in-vehicle apparatus ID (identifier) <NUM>, which is an identifier that uniquely identifies the in-vehicle apparatus <NUM>. In the present embodiment, the vehicle and the in-vehicle apparatus <NUM> correspond to each other in a one-to-one relationship. Hence, the in-vehicle apparatus ID <NUM> is also an identifier that identifies the vehicle.

The portable terminal apparatus <NUM> includes a central control device <NUM>, an input and output device <NUM> having a display and a touch panel, an auxiliary storage device <NUM>, and a communication device <NUM>. These devices are connected together through a bus. In the following description, when the acting subject is mentioned like "the portable terminal apparatus <NUM> do something", this means that the central control device <NUM> reads out a predetermined program (not illustrated) from the auxiliary storage device <NUM> and loads the program into a main storage device (not illustrated), and then implements the function of the program. Separately from this, the terminal-vehicle registering unit <NUM> and the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> also can serve as the acting subject of the portable terminal apparatus <NUM> (such as causing the portable terminal apparatus <NUM> to display specific information). The auxiliary storage device <NUM> stores a terminal apparatus ID <NUM>, which is an identifier that uniquely identifies the portable terminal apparatus <NUM>. In the present embodiment, the driver and the portable terminal apparatus <NUM> correspond to each other in a one-to-one relationship. Hence, the terminal apparatus ID <NUM> is also an identifier that identifies the driver.

The linkage information <NUM> will be described along <FIG>. In the linkage information <NUM>, while being linked with the terminal apparatus ID stored in the terminal apparatus ID column <NUM>, the in-vehicle apparatus ID is stored in the in-vehicle apparatus ID column <NUM>, the linkage date and time in the linkage date and time column <NUM>, the release date and time in the release date and time column <NUM>, the determination flag in the determination column <NUM>, and the owner flag in the owner column <NUM>.

The terminal apparatus ID in the terminal apparatus ID column <NUM> is the aforementioned terminal apparatus ID (reference sign <NUM> in <FIG>). Note that to the "first identifier", the terminal apparatus ID corresponds. In the present embodiment, the terminal apparatus IDs identify the portable terminal apparatuses used by the owner and the non-owner.

The in-vehicle apparatus ID in the in-vehicle apparatus ID column <NUM> is the aforementioned in-vehicle apparatus ID (reference sign <NUM> in <FIG>). Note that to the "second identifier", the in-vehicle apparatus ID corresponds.

The linkage date and time in the linkage date and time column <NUM> is the year, month, day, hour, minute, and second when the terminal-vehicle linking apparatus <NUM>, after issuing expiration-dated authentication information and performing authentication (described in detail later), fixedly linked the terminal apparatus ID and the in-vehicle apparatus ID with each other and registered them as one record (row) in the linkage information <NUM>. Here, the "fixedly" or "fixed" means that it is supported by the correspondence of the expiration-dated authentication information (described in detail later).

The release date and time in the release date and time column <NUM> is the year, month, day, hour, minute, and second when the terminal-vehicle linking apparatus <NUM> released the linkage between the terminal apparatus ID and the in-vehicle apparatus ID.

Note that "NULL" indicates that no data is stored in that column of the corresponding record in the terminal apparatus ID column <NUM> to the release date and time column <NUM>.

The determination flag in the determination column <NUM> takes one of "NULL", "<NUM>", "<NUM>", and "<NUM>". The determination flag "NULL" indicates that only the terminal apparatus ID is stored (as information other than "NULL") in the corresponding record. Such a record is hereinafter referred to also as "standby record".

The determination flag "<NUM>" indicates that the terminal apparatus ID and the in-vehicle apparatus ID are stored but the linkage date and time and the release date and time are not stored (which are "NULL") in the corresponding record. In this state, the terminal apparatus ID and the in-vehicle apparatus ID have not been fixedly linked yet. Such a record is hereinafter referred to also as "temporarily linked record".

The determination flag "<NUM>" indicates that the terminal apparatus ID, the in-vehicle apparatus ID, and the linkage date and time are stored but the release date and time is not stored (which is "NULL") in the corresponding record. In this state, the terminal apparatus ID and the in-vehicle apparatus ID are fixedly linked. Such a record is hereinafter referred to also as "fixedly linked record". At a certain point of time, the non-owner can drive the vehicle by using his/her own portable terminal apparatus <NUM> only when the terminal apparatus ID of the portable terminal apparatus <NUM> and the in-vehicle apparatus ID which identifies the in-vehicle apparatus mounted in the vehicle are stored in the fixedly linked record at this certain point of time. Note that to the "information indicating that the linkage is fixed", the determination flag "<NUM>" here corresponds.

The determination flag "<NUM>" indicates that the terminal apparatus ID, the in-vehicle apparatus ID, the linkage date and time, and the release date and time are stored in the corresponding record. In this state as well, the terminal apparatus ID and the in-vehicle apparatus ID are fixedly linked, but this is limited to the past history. Such a record is hereinafter referred to also as "released record". The transition of the determination flag on the time axis will be described later. The owner flag is an identifier indicating that it is the owner of the vehicle corresponding to the corresponding in-vehicle apparatus ID. The "<NUM>" indicates that it is a non-owner while "<NUM>" indicates that it is the owner.

The expiration-dated authentication information is authentication information having an expiration time. The authentication information is information for fixedly linking the terminal apparatus ID of the portable terminal apparatus <NUM> of the non-owner with the in-vehicle apparatus ID, and is a character string, a number string or a combination thereof, which is generated at random by terminal-vehicle linking apparatus <NUM> using a random number table or the like every time. Then, the expiration time is a time limit by which the terminal apparatus ID of the portable terminal apparatus <NUM> of the non-owner can be fixedly linked with the in-vehicle apparatus ID. This time limit is a certain constant time by which the input can be considered to be made using the portable terminal apparatus <NUM> after the authentication information is sent to the in-vehicle apparatus <NUM>, for example. Although described in detail later, when the expiration-dated authentication information which the terminal-vehicle linking apparatus <NUM> has received from the portable terminal apparatus <NUM> coincides with the expiration-dated authentication information which the terminal-vehicle linking apparatus <NUM> has transmitted toward the in-vehicle apparatus <NUM>, the terminal-vehicle linking apparatus <NUM> determines that the portable terminal apparatus <NUM> can function as the vehicle key of the corresponding vehicle.

Although some of the above description is repeated, the transition of the determination flag (the column <NUM> in <FIG>) on the time axis will be described as follows in relation with the expiration-dated authentication information.

Referring to the linkage information <NUM> shows the followings for example.

The terminal apparatus information <NUM> will be described along <FIG>. In the terminal apparatus information <NUM>, while being linked with the terminal apparatus ID stored in the terminal apparatus ID column <NUM>, the telephone number is stored in the telephone number column <NUM>, the e-mail address in the e-mail address column <NUM>, the registration date in the registration date column <NUM>, and the driving skill level in the driving skill level column <NUM>.

The terminal apparatus ID in the terminal apparatus ID column <NUM> is the aforementioned terminal apparatus ID (reference sign <NUM> in <FIG>).

The telephone number in the telephone number column <NUM> is a telephone number when the portable terminal apparatus <NUM> is used as a cell phone.

The e-mail address in the e-mail address column <NUM> is an e-mail address when the portable terminal apparatus <NUM> is used as a transmitter and receiver for e-mails.

The registration date in the registration date column <NUM> is the year, month, and day when the record (row) was stored in the terminal apparatus information <NUM>.

The driving skill level in the driving skill level column <NUM> represents the driving skill level of a person who possesses the terminal apparatus ID. When the terminal apparatus ID is of an owner, NULL is permitted, while when the terminal apparatus ID is of a parking lot manager, NULL is not permitted but the driving skill level of the parking lot manager needs to be inputted in the driving skill level column <NUM>. This item is used for judgment in allocating an appropriate one out of people in charge in the parking lot manager as the driver when the vehicle which has become incapable of automated drive within the parking lot is to be manually driven temporarily.

In the terminal apparatus information <NUM>, it is necessary that at least an identifier which uniquely identify the portable terminal apparatus <NUM> and a registration date should be stored. The telephone number and the e-mail address also can be said to be such identifiers. Accordingly, it is enough that at least one of the telephone number, the e-mail address, and terminal apparatus ID other than these (for example, a number automatically given by the terminal-vehicle linking apparatus <NUM>) be stored in the terminal apparatus information <NUM>. Moreover, the terminal-vehicle linking apparatus <NUM> may use the serial number, the IMEI (International Mobile Equipment Identifier), or the like of the portable terminal apparatus <NUM> instead of newly numbering the terminal apparatus ID.

The vehicle information <NUM> will be described along <FIG>. In the vehicle information <NUM>, while being linked with the in-vehicle apparatus ID stored in the in-vehicle apparatus ID column <NUM>, the vehicle type is stored in the vehicle type column <NUM>, the length in the length column <NUM>, the width in the width column <NUM>, the registration date in the registration date column <NUM>, and the automated driving technology level in the automated driving technology level column <NUM>.

The in-vehicle apparatus ID in the in-vehicle apparatus ID column <NUM> is the aforementioned in-vehicle apparatus ID (reference sign <NUM> in <FIG>).

The vehicle type in the vehicle type column <NUM> is the type of the vehicle. The type of the vehicle may be a size category such as a small vehicle or a large vehicle, or may be a use category such as a passenger vehicle or a truck, or may be a license category required for driving the vehicle.

The length in the length column <NUM> is a longitudinal length of the vehicle (unit: cm).

The width in the width column <NUM> is the width of the vehicle (unit: cm).

The registration date in the registration date column <NUM> is the year, month, and day when the corresponding record (row) was stored in the vehicle information <NUM>.

The automated driving technology level in the automated driving technology level column <NUM> is the capability of the automated drive (the technology level of the automated drive).

Depending on the structure of the parking lot, the parking space for a large vehicle, for example, is limited. In addition, depending on the vehicle type, it is sometimes required for a non-owner to have a sophisticated driving skill. Moreover, depending on the automated drive function of an automated vehicle, there could be a case where the automated vehicle can be parked in only a particular garage. Accordingly, it is possible to store various kinds of information that are useful for determining the easiness in parking, such as the non-owner who drives the vehicle and the selecting of a space for parking the vehicle, instead of or in addition to the vehicle type and the lengths.

The procedures for a terminal registering process will be described along <FIG>.

In Step S201, the portable terminal apparatus <NUM> of the owner transmits a terminal registering request. Specifically, the portable terminal apparatus <NUM> transmits the terminal registering request together with the terminal apparatus ID (reference sign <NUM> in <FIG>), the telephone number, and the e-mail address of the portable terminal apparatus <NUM>, and information that identifies whether it is the owner registration, to the terminal-vehicle linking apparatus <NUM>. Although the portable terminal apparatus of the owner is described as an example here, the portable terminal of a non-owner can also be registered in the same manner.

In Step S202, the terminal-vehicle registering unit <NUM> of the terminal-vehicle linking apparatus <NUM> receives the terminal registering request. Specifically, the terminal-vehicle registering unit <NUM> receives the terminal registering request together with the terminal apparatus ID, the telephone number, the e-mail address, and the information that identifies whether it is the owner registration, from the portable terminal apparatus <NUM>.

In Step S203, the terminal-vehicle registering unit <NUM> of the terminal-vehicle linking apparatus <NUM> registers the portable terminal apparatus <NUM>. Specifically, first, the terminal-vehicle registering unit <NUM> create a new record for linkage information <NUM> (<FIG>), and stores the terminal apparatus ID, received in Step S202, into the terminal apparatus ID column <NUM>. Then, the terminal-vehicle registering unit <NUM> stores "NULL" into the in-vehicle apparatus ID column <NUM>, the linkage date and time column <NUM>, the release date and time column <NUM>, and the determination column <NUM> of the new record. The terminal-vehicle registering unit <NUM> registers "<NUM>" in the owner flag in the case of the owner registration or "<NUM>" in the other cases. The record created here is a standby record.

Secondly, the terminal-vehicle registering unit <NUM> creates a new record for the terminal apparatus information <NUM> (<FIG>), and stores the terminal apparatus ID, the telephone number, and the e-mail address, received in Step S202, into the terminal apparatus ID column <NUM>, the telephone number column <NUM>, and the e-mail address column <NUM>. Then, the terminal-vehicle registering unit <NUM> stores the current year, month, and day into the registration date column <NUM> of the new record.

In Step S204, the terminal-vehicle registering unit <NUM> of the terminal-vehicle linking apparatus <NUM> transmits a result of registration. The result of registration is a result of whether the terminal-vehicle linking apparatus <NUM> has been successfully registered in the terminal apparatus information and the linkage information of the record.

In Step S205, the portable terminal apparatus <NUM> receives the result of registration. Specifically, first, the portable terminal apparatus <NUM> receives the result of registration from the terminal-vehicle linking apparatus <NUM>.

Secondly, the portable terminal apparatus <NUM> displays the result of registration on the input and output device <NUM>, and thereafter ends the procedures for a terminal registering process.

The procedures for a vehicle registering process will be described along <FIG>. The owner requests the terminal-vehicle linking apparatus <NUM> to issue the in-vehicle apparatus ID by using the portable terminal apparatus <NUM> of the owner.

In Step S211, the portable terminal apparatus <NUM> (of the owner) transmits an in-vehicle apparatus ID issue request. Specifically, the portable terminal apparatus <NUM> transmits the in-vehicle apparatus ID issue request to the terminal-vehicle linking apparatus <NUM>.

In Step S212, the terminal-vehicle registering unit <NUM> of the terminal-vehicle linking apparatus <NUM> receives the in-vehicle apparatus ID issue request. Specifically, the terminal-vehicle registering unit <NUM> receives the in-vehicle apparatus ID issue request together with the terminal apparatus ID from the portable terminal apparatus <NUM>.

In Step S213, the terminal-vehicle registering unit <NUM> of the terminal-vehicle linking apparatus <NUM> issues the in-vehicle apparatus ID. At this time, the terminal-vehicle registering unit <NUM> newly creates a unique identifier. Of course, the terminal-vehicle registering unit <NUM> may use an existing vehicle identification number such as a license plate number as the in-vehicle apparatus ID. However, from the viewpoint of ensuring the security, it is more desirable that the terminal-vehicle registering unit <NUM> should create a random character string or the like by using a random number table or the like.

In Step S214, the terminal-vehicle registering unit <NUM> of the terminal-vehicle linking apparatus <NUM> registers the in-vehicle apparatus ID. Specifically, first, the terminal-vehicle registering unit <NUM> acquires a record that corresponds to the terminal apparatus ID received in Step S212 from the linkage information <NUM> (<FIG>).

Secondly, the terminal-vehicle registering unit <NUM> confirms that the owner flag of the received record is "<NUM>" and then sets the determination flag to "<NUM>".

Thirdly, the terminal-vehicle registering unit <NUM> acquires the standby record in which the owner flag is "<NUM>" from the linkage information <NUM> (<FIG>). Then, the terminal-vehicle registering unit <NUM> stores the in-vehicle apparatus ID created in Step S213 into the in-vehicle apparatus ID column <NUM> of the standby record and stores "<NUM>" into the determination column <NUM>, thereby changing the standby record to a temporarily linked record.

Fourthly, the terminal-vehicle registering unit <NUM> creates a new record for the vehicle information <NUM> (<FIG>), stores the in-vehicle apparatus ID, issued in Step S213, into the in-vehicle apparatus ID column <NUM>, and further stores the vehicle type and the length of the vehicle, received in Step S212, into the vehicle type column <NUM> and the length column <NUM> as necessary. Then, the terminal-vehicle registering unit <NUM> stores the current year, month, and day into the registration date column <NUM> of the new record.

In Step S215, the terminal-vehicle registering unit <NUM> of the terminal-vehicle linking apparatus <NUM> transmits the in-vehicle apparatus ID. Specifically, the terminal-vehicle registering unit <NUM> transmits the in-vehicle apparatus ID, issued in Step S213, to the portable terminal apparatus <NUM>. In Step S216, the portable terminal apparatus <NUM> receives the in-vehicle apparatus ID. Specifically, the portable terminal apparatus <NUM> receives the in-vehicle apparatus ID, issued in Step S213, from the terminal-vehicle linking apparatus <NUM>.

In Step S217, the portable terminal apparatus <NUM> registers the in-vehicle apparatus ID. Specifically, the portable terminal apparatus <NUM> stores the in-vehicle apparatus ID, received in Step S216, into the auxiliary storage device <NUM>.

In Step S218, the in-vehicle apparatus <NUM> registers the in-vehicle apparatus ID. Specifically, the in-vehicle apparatus <NUM> may receive the in-vehicle apparatus ID through any of the following method <NUM>, method <NUM>, and method <NUM>, for example.

The method <NUM> is a method that imposes a burden on the owner but has a higher security in that the owner has to ride the vehicle and operate the in-vehicle apparatus <NUM>.

In Step S219, the in-vehicle apparatus <NUM> displays a result of registration. Specifically, the in-vehicle apparatus <NUM> displays a result of whether the record created in the "fourthly" section in Step S214 has been successfully registered, on the input and output device <NUM>.

In Step S2201, the in-vehicle apparatus <NUM> transmits information on the specifications of the automobile in which the in-vehicle apparatus <NUM> is mounted to the terminal-vehicle linking apparatus <NUM>. The information on the specifications is the length, width, vehicle type, and the like necessary for the automated valet parking. The information on the specifications to be transmitted is supposed to be set up between the in-vehicle apparatus and the terminal-vehicle linking apparatus in advance. However, it is possible to employ a configuration that limited information such as vehicle type is transmitted, if information necessary for automated valet parking can be acquired from a catalogue spec and the like.

In Step S2202, the terminal-vehicle linking apparatus <NUM> receives the information on the specifications of the automobile from the in-vehicle apparatus <NUM>. The terminal-vehicle registering unit <NUM> of the terminal-vehicle linking apparatus <NUM> stores the received information into the record corresponding to the in-vehicle apparatus ID of the vehicle information <NUM>.

Thereafter, the procedures for a vehicle registering process are ended.

The procedures for a linking process will be described along <FIG>. Here, the description will be made on the assumption that the owner has ridden the vehicle and activated the in-vehicle apparatus <NUM>.

In Step S221, the in-vehicle apparatus <NUM> transmits an authentication information issue request. Specifically, the in-vehicle apparatus <NUM> transmits the authentication information issue request which requests for expiration-dated authentication information together with the in-vehicle apparatus ID received in Step S218 to the terminal-vehicle linking apparatus <NUM>. At this time, the owner operates the input and output device <NUM> of the in-vehicle apparatus <NUM> to transmit the authentication information issue request while driving the vehicle.

In Step S222, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> receives the authentication information issue request. Specifically, the terminal-vehicle linking unit <NUM> receives the authentication information issue request together with the in-vehicle apparatus ID from the in-vehicle apparatus <NUM>.

In Step S223, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> confirms that the in-vehicle apparatus ID is stored in the temporarily linked record. Specifically, the terminal-vehicle linking unit <NUM> searches the linkage information <NUM> (<FIG>) by using the in-vehicle apparatus ID received in Step S222 as a search key, and confirms that the determination flag of the corresponding record is "<NUM>". Here, when the confirmation cannot be made, the terminal-vehicle linking unit <NUM> ends the procedures for a linking process (not illustrated as a flowchart).

In Step S224, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> issues authentication information. Specifically, first, the terminal-vehicle linking unit <NUM> determines the expiration time based on the following example.

Secondly, the terminal-vehicle linking unit <NUM> creates a character string, a number string, or a combination thereof at random by using a random number table or the like, as authentication information. Then, the terminal-vehicle linking unit <NUM> adds the expiration time determined in "first" of Step S224 to the authentication information, thereby creating expiration-dated authentication information.

In Step S225, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> transmits the authentication information. Specifically, the terminal-vehicle linking unit <NUM> transmits the expiration-dated authentication information to the in-vehicle apparatus <NUM>.

In Step S226, the in-vehicle apparatus <NUM> receives and displays the authentication information. Specifically, the in-vehicle apparatus <NUM> receives the expiration-dated authentication information from the terminal-vehicle linking apparatus <NUM>. Then, the in-vehicle apparatus <NUM> stores the expiration-dated authentication information into the auxiliary storage device <NUM> and also displays the expiration-dated authentication information on the input and output device <NUM>.

In Step S227, the portable terminal apparatus <NUM> transmits the authentication information. Specifically, the portable terminal apparatus <NUM> transmits the authentication information displayed in Step S226 and the terminal apparatus ID to the terminal-vehicle linking apparatus <NUM>. At this time, the portable terminal apparatus <NUM> may receive the expiration-dated authentication information through any of the following method <NUM>, method <NUM>, and method <NUM>, for example.

The method <NUM> is a method that imposes a burden on the owner but has a higher security in that the owner directly inputs the expiration-dated authentication information into the portable terminal apparatus <NUM>.

In Step S228, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> determines whether the authentication information is valid. Specifically, first, the terminal-vehicle linking unit <NUM> receives the expiration-dated authentication information from the portable terminal apparatus <NUM>.

Secondly, the terminal-vehicle linking unit <NUM> proceeds to Step S229 if the following condition <NUM>, condition <NUM>, and condition <NUM> are simultaneously satisfied ("Yes" in Step S228) or proceeds to Step S230 in the other cases ("No" in Step S228).

In Step S229, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> fixedly links the portable terminal apparatus <NUM> with the in-vehicle apparatus <NUM>. Specifically, the terminal-vehicle linking unit <NUM> stores the current year, month, day, hour, minute, and second into the linkage date and time column <NUM> of the temporarily linked record and stores "<NUM>" into the determination column <NUM>, thereby changing the temporarily linked record to a fixedly linked record.

At this stage, the terminal-vehicle linking unit <NUM> determines that "the owner who uses the portable terminal apparatus <NUM> identified by the terminal apparatus ID of the fixedly linked record may instruct the vehicle on which the in-vehicle apparatus <NUM> identified by the in-vehicle apparatus ID of the fixedly linked record is mounted.

In Step S230, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> transmits a result of the process. Specifically, the terminal-vehicle linking unit <NUM> transmits the following information to the portable terminal apparatus <NUM> as the result of the process.

In Step S231, the portable terminal apparatus <NUM> receives the result of the process. Specifically, the portable terminal apparatus <NUM> receives the result of the process transmitted in Step S230 from the terminal-vehicle linking apparatus <NUM>, and displays the result of the process on the input and output device <NUM>. Thereafter, the portable terminal apparatus <NUM> ends the procedures for a linking process. As long as the fixedly linked record is stored in the linkage information <NUM> (<FIG>), the owner who uses the portable terminal apparatus <NUM> identified by the terminal apparatus ID of the fixedly linked record can drive the vehicle in which the in-vehicle apparatus <NUM> identified by the in-vehicle apparatus ID is mounted or instruct the vehicle for operation. Specifically, when the owner is permitted to drive the vehicle, the owner is given the rights of the electronic key while when the owner is permitted to instruct the vehicle for operation, the owner is given the rights of instruction.

The procedures for a linkage releasing process will be described along <FIG>.

In Step S241, the in-vehicle apparatus <NUM> transmits a linkage release request. Specifically, the in-vehicle apparatus <NUM> transmits the linkage release request which is a request for releasing the linkage between the terminal apparatus ID and the in-vehicle apparatus ID together with the in-vehicle apparatus ID to the terminal-vehicle linking apparatus <NUM>.

In Step S242, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> receives the linkage release request. Specifically, the terminal-vehicle linking unit <NUM> receives the linkage release request together with the in-vehicle apparatus ID from the in-vehicle apparatus <NUM>. At this time, the terminal-vehicle linking unit <NUM> confirms that the linkage release request is from the owner by using the portable terminal apparatus of the owner or the like (not illustrated as a flowchart).

In Step S243, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> determines whether the portable terminal apparatus <NUM> is linked with the in-vehicle apparatus <NUM>. Specifically, if there is a record that simultaneously satisfies the following condition <NUM> and condition <NUM> in the linkage information <NUM> (<FIG>) ("Yes" in Step S243), the terminal-vehicle linking unit <NUM> proceeds to Step S244 while holding the record. In the other cases ("No" in Step S243), the terminal-vehicle linking unit <NUM> proceeds to Step S245.

In Step S244, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> releases the linkage. Specifically, the terminal-vehicle linking unit <NUM> stores the current year, month, day, hour, minute, and second into the release date and time column <NUM> of the record held in Step S243 and stores "<NUM>" into the determination column <NUM> (changing the fixedly linked record to a released record).

In Step S245, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> transmits a result of the process. Specifically, the terminal-vehicle linking unit <NUM> transmits the following information to the in-vehicle apparatus <NUM> as the result of the process.

In Step S246, the in-vehicle apparatus <NUM> receives the result of the process. Specifically, the in-vehicle apparatus <NUM> receives the result of the process transmitted in Step S245 from the terminal-vehicle linking apparatus <NUM> and displays the result of the process on the input and output device <NUM>. Thereafter, the procedures for a linkage releasing process are ended. Note that the procedures for a linkage releasing process may be executed at a timing other than that when the owner departs from the hotel.

The procedures for an in-vehicle apparatus ID deleting process will be described along <FIG>. Now, assume that the owner has decided to no longer utilize the valet parking.

In Step S251, the in-vehicle apparatus <NUM> transmits an in-vehicle apparatus ID deleting request. Specifically, the in-vehicle apparatus <NUM> transmits the in-vehicle apparatus ID deleting request, which is a request for deleting the in-vehicle apparatus ID, together with the in-vehicle apparatus ID to the terminal-vehicle linking apparatus <NUM>.

In Step S252, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> receives the in-vehicle apparatus ID deleting request. Specifically, the terminal-vehicle linking unit <NUM> receives the in-vehicle apparatus ID deleting request together with the in-vehicle apparatus ID from the in-vehicle apparatus <NUM>. At this time, the terminal-vehicle linking unit <NUM> confirms that the deleting request is from the owner by using the portable terminal apparatus of the owner or the like.

In Step S253, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> determines whether the in-vehicle apparatus ID has been registered. Specifically, if there is a record containing the in-vehicle apparatus ID received in Step S252 in the linkage information <NUM> (<FIG>) ("Yes" in Step S253), the terminal-vehicle linking unit <NUM> proceeds to Step S254. In the other cases ("No" in Step S253), the terminal-vehicle linking unit <NUM> proceeds to Step S255.

In Step S254, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> deletes the in-vehicle apparatus ID. Specifically, first, the terminal-vehicle linking unit <NUM> deletes the record containing the in-vehicle apparatus ID received in Step S252 from the linkage information <NUM> (<FIG>).

Secondly, the terminal-vehicle linking unit <NUM> deletes the record containing the in-vehicle apparatus ID received in Step S252 from the vehicle information <NUM> (<FIG>).

In Step S255, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> transmits a result of the process. Specifically, the terminal-vehicle linking unit <NUM> transmits the following information to the in-vehicle apparatus <NUM> as the result of the process.

In Step S256, the in-vehicle apparatus <NUM> receives the result of the process. Specifically, the in-vehicle apparatus <NUM> receives the result of the process transmitted in Step S255 from the terminal-vehicle linking apparatus <NUM> and displays the result of the process on the input and output device <NUM>.

In Step S257, the in-vehicle apparatus <NUM> determines whether the in-vehicle apparatus ID was deleted. Specifically, if the result of the process received in Step S256 is the fifth message ("Yes" in Step S257), the in-vehicle apparatus <NUM> proceeds to Step S258. If the result of the process received in Step S256 is the sixth message ("No" in Step S257), the in-vehicle apparatus <NUM> ends the procedures for an in-vehicle apparatus ID deleting process.

In Step S258, the in-vehicle apparatus <NUM> deletes the in-vehicle apparatus ID. Specifically, the in-vehicle apparatus <NUM> deletes the in-vehicle apparatus ID from the auxiliary storage device <NUM>. Thereafter, the in-vehicle apparatus <NUM> ends the procedures for an in-vehicle apparatus ID deleting process. Note that the procedures for an in-vehicle apparatus ID deleting process may be executed at a timing other than that when the owner decided to no longer utilize the valet parking. Such other timing includes a timing when the owner gave up the vehicle.

The procedures for giving the operation rights of the vehicle to a parking lot manager in an emergency will be described along <FIG>. There would be a case where when the vehicle instructed to perform automated valet parking is running within the parking lot, the automated driving becomes difficult due to failure of a device in the vehicle, and the like, and it becomes necessary for the vehicle to be temporarily driven manually by a parking lot manager.

In Step S261, the vehicle itself determines that the automated driving has become difficult to be continued, and notifies the terminal-vehicle linking apparatus <NUM> through the in-vehicle apparatus <NUM>. Specifically, the vehicle notifies the terminal-vehicle linking apparatus <NUM> of the in-vehicle apparatus ID of the auxiliary storage device <NUM> of the in-vehicle apparatus <NUM>.

In Step S262, the terminal-vehicle linking apparatus <NUM> receives the automated driving incapability notification from the vehicle. Specifically, the terminal-vehicle linking apparatus <NUM> receives the in-vehicle apparatus ID identifying the vehicle which has been designated in Step S261.

In Step S263, the terminal-vehicle linking apparatus <NUM> acquires a standby record from the linkage information <NUM>. Specifically, the terminal-vehicle linking apparatus <NUM> acquires a standby record in which the owner flag is "<NUM>" (the portable terminal apparatus of the parking lot manager) from the linkage information <NUM>.

The number of the standby records in which the owner flag is "<NUM>" is not necessarily one because normally a plurality of non-owners exist in a hotel. In view of this, the terminal-vehicle registering unit <NUM> may arrange a plurality of standby records in a certain order and select the leading standby record as a temporarily linked record such that the loads on the non-owners become equal. Alternatively, when giving the operation rights of the vehicle to some non-owners among a plurality of non-owners, the terminal-vehicle registering unit <NUM> may use information on the driving skills of the plurality of non-owner stored in advance to determine a portable terminal apparatus to be given the operation rights. Moreover, when determining a portable terminal apparatus to be given the operation rights, the terminal-vehicle registering unit <NUM> may use any of information on the vehicle type or length of the vehicle to be operated and information on the parking space.

In particular, it is desirable that a non-owner having a low driving skill should not drive a vehicle that is difficult to be driven, or not allocated to park a vehicle at a difficult parking space such as a parallel parking space. In this case, the terminal-vehicle registering unit <NUM> may cross-check the vehicle type and the length of the vehicle received in Step S212 with driving skills of non-owners stored in advance and select a standby record of a non-owner who is most suitable for driving the vehicle as a temporarily linked record. Besides, the difficulty in parking should include dynamic information such as information that an adjacent vehicle is large in size, information that a vehicle is parked to be sticking out, and the like. Accordingly, it is also possible to determine a portable terminal apparatus to be given the operation rights, considering information on a vehicle adjacent to a space to park (such as the vehicle type and the position where the vehicle is parked).

In Step S264, the terminal-vehicle linking apparatus <NUM> acquires the terminal apparatus ID that satisfies the driving skill level of the terminal apparatus information <NUM> from terminal apparatus IDs of the standby records acquired in Step S263.

In Step S265, the terminal-vehicle linking apparatus <NUM> searches the terminal apparatus information <NUM> using a terminal apparatus ID <NUM> subjected to the linking process as a key, thereby acquiring the telephone number <NUM> and the e-mail address <NUM>.

In Step S266, the terminal-vehicle linking apparatus <NUM> notifies the portable terminal apparatus <NUM> (of the non-owner) that the standby record has been linked with the vehicle through the telephone number and the e-mail address acquired in Step S263.

In Step S267, the portable terminal apparatus <NUM> of the parking lot manager receives the e-mail saying that the linking process has been completed. Thereafter, the procedures for temporarily giving the rights to a portable terminal apparatus are ended. The ending enables an instruction to unlock the doors of the vehicle to be sent.

When the manager of the parking lot is temporarily given the operation rights in this process, a process for sending a request to give the rights may be performed to the terminal of the owner (not illustrated as a flowchart).

Procedures for releasing the operation rights temporarily linked with the parking lot manager will be described using <FIG>.

In Step S271, a linkage release request is transmitted from the portable terminal apparatus <NUM> (of the owner) to the terminal-vehicle linking apparatus <NUM>. Specifically, the terminal apparatus ID <NUM> of the portable terminal apparatus <NUM> is transmitted.

In Step S272, the terminal-vehicle linking apparatus <NUM> receives the linkage release request. Specifically, the terminal-vehicle linking apparatus <NUM> receives the terminal apparatus ID <NUM> of the portable terminal apparatus <NUM> transmitted from the portable terminal apparatus <NUM> (of the owner).

In Step S273, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> determines whether the portable terminal apparatus (of the non-owner) has been linked with the in-vehicle apparatus. Specifically, if there is a record that simultaneously satisfies the following condition <NUM> and condition <NUM> in the linkage information <NUM> (<FIG>) ("Yes" in Step <NUM>), the terminal-vehicle linking unit <NUM> proceeds to Step S274 while holding the corresponding record. In the other cases ("No" in Step S273), the terminal-vehicle linking unit <NUM> proceeds to Step S275.

In Step S274, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> releases the linkage. Specifically, the terminal-vehicle linking unit <NUM> stores the current year, month, day, hour, minute, and second into the release date and time column <NUM> of the record held in Step S273 and stores "<NUM>" into the determination column <NUM> of the record (changes the fixedly linked record to the released record).

In Step S275, the terminal-vehicle linking unit <NUM> of the terminal-vehicle linking apparatus <NUM> transmits a result of the process. Specifically, the terminal-vehicle linking unit <NUM> transmits the following information to the in-vehicle apparatus <NUM> as the result of the process.

In Step S276, the portable terminal apparatus <NUM> (of the owner) receives the result of the process. Specifically, the portable terminal apparatus <NUM> receives the result of the process transmitted in Step S275 from the terminal-vehicle linking apparatus <NUM> and displays the result of the process on the input and output device <NUM>.

Thereafter, the procedures for releasing the rights temporarily given to a portable terminal apparatus are ended. Note that these procedures can be executed at a desired timing by the owner but are received after the manual driving by the non-owner is completed (not illustrated as a flowchart).

The above description has been made on the premise that the vehicle is every time instructed to operate based on the instruction from the owner. However, it is also possible to register a predetermined operation in the terminal-vehicle linking apparatus <NUM>. Now, assume that a record on the first row has already been stored in linkage information <NUM> (<FIG>). The owner gets off the vehicle in which the in-vehicle apparatus C001 is mounted at the entrance of a hotel and enters a guest room while carrying the portable terminal apparatus M001.

The portable terminal apparatus M001 receives the following information (hereinafter referred to also as "departure preparation information") inputted by the owner through the input and output device <NUM>. Note that "#" represents a different number in an omitted manner.

Next, the portable terminal apparatus M001 transmits the departure preparation information to the terminal-vehicle linking apparatus <NUM>. The terminal-vehicle linking apparatus <NUM> stores the departure preparation information while linking the departure preparation information with the record on the first row of the linkage information <NUM>. Thereafter, the terminal-vehicle linking apparatus <NUM> establishes communications with the in-vehicle apparatus C001 through the network <NUM> and transmits a control signal for implementing a designated operation at a designated timing in the departure preparation information to the in-vehicle apparatus C001.

The effects of the terminal-vehicle linking apparatus according to the present embodiment are as described below.

Note that the present invention is not limited to the above-described embodiment, but encompasses various modifications. For example, the above-described embodiment has been described in detail for explaining the present invention in an easily understandable manner, and the present invention is not necessarily limited to an embodiment including all the configurations described above. In addition, part of the configurations of a certain embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of a certain embodiment. Moreover, addition, deletion, and replacement of another configuration can be made on part of the configuration of each embodiment.

Claim 1:
A terminal-vehicle linking apparatus (<NUM>) comprising:
a communication device (<NUM>) for communicating with portable terminal apparatuses (<NUM>) and with in-vehicle apparatuses (<NUM>),
a terminal-vehicle registering unit (<NUM>) adapted to receive and register registration information of a first portable terminal apparatus (<NUM>) to be used to permit driving a vehicle or instruct the vehicle and adapted to receive and register registration information of an in-vehicle apparatus (<NUM>) mounted in the vehicle; and
a terminal-vehicle linking unit (<NUM>) adapted to determine, when authentication information received from the first portable terminal apparatus of which the registration information has been received coincides with authentication information transmitted in advance to the in-vehicle apparatus (<NUM>) of which the registration information has been received, that it is possible to permit driving the vehicle or instruct the vehicle through the first portable terminal apparatus,
wherein the terminal-vehicle registering unit (<NUM>) is adapted to receive a first identifier from a second portable terminal apparatus used by a person other than a person who is permitted to drive the vehicle in which the in-vehicle apparatus identified by an issued second identifier is mounted, and
wherein the authentication information has an expiration time.