Remote control device and control method thereof

Abstract

To apply an operation authority of a remote operation with a simple method.SOLUTION: A remote operation device for operating a vehicle from a remote site, comprises: an acquisition part that acquires identification information associated with a user terminal in the vehicle; an authority management part that applies an operation authority for operating the vehicle from the remote site to the user terminal associated with the acquired identification information; and an operation part that operates the vehicle from the remote site in accordance with an operation instruction transmitted from the user terminal with the operation authority.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a remote control device and a control method thereof. [Background technology]

[0002] In recent years, efforts to provide access to sustainable transportation systems that take into consideration vulnerable transport participants have been gaining momentum. To achieve this, efforts are being made to further improve transportation safety and convenience through research and development into sharing. In addition, Patent Document 1 proposes technology that allows users to remotely control vehicles using a user terminal. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-231964 Summary of the Invention [Problem to be solved by the invention]

[0004] If remote control operation authority can be granted in a simple manner, vehicle sharing can be promoted. Some aspects of the present invention aim to provide a technology for granting remote control operation authority in a simple manner. Furthermore, some aspects of the present invention contribute to the development of sustainable transportation systems. [Means for solving the problem]

[0005] According to some embodiments, there is provided a remote control device for remotely operating a vehicle, comprising: When the power supply to the vehicle is stoppedA remote control device is provided that includes an acquisition means for acquiring identification information associated with a user terminal inside the vehicle, an authority management means for granting operation authority to the user terminal associated with the acquired identification information to remotely operate the vehicle, and an operation means for remotely operating the vehicle in accordance with operation instructions transmitted from the user terminal having the operation authority. [Effects of the Invention]

[0006] According to some embodiments, remote control operation authority can be granted in a simple manner. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a schematic diagram illustrating an example of the configuration of a system that provides a remote operation service according to some embodiments. [Figure 2] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a remote control device according to some embodiments. [Figure 3] FIG. 2 is a block diagram illustrating an example hardware configuration of a vehicle according to some embodiments. [Figure 4] FIG. 2 is a block diagram illustrating an example of the hardware configuration of a user terminal according to some embodiments. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of the operation of a system that provides a remote operation service according to some embodiments. [Figure 6] 10A and 10B are schematic diagrams illustrating an example of a screen displayed on a user terminal according to some embodiments. [Figure 7] FIG. 10 is a diagram illustrating an example of rights management information according to some embodiments. [Figure 8] FIG. 10 is a flow diagram illustrating an example of the operation of a user terminal according to some embodiments. [Figure 9] FIG. 10 is a flow diagram illustrating an example of the operation of the remote control device according to some embodiments. [Figure 10] FIG. 4 is a flow diagram illustrating an example of the operation of a vehicle according to some embodiments. [Figure 11] FIG. 10 is a flow diagram illustrating another example of the operation of the user terminal of some embodiments. [Figure 12]FIG. 10 is a flowchart illustrating another example of the operation of the remote control device according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all combinations of features described in the embodiments are necessarily essential to the invention. Two or more of the features described in the embodiments may be combined in any desired manner. Furthermore, the same reference numerals are used to designate identical or similar components, and redundant descriptions will be omitted.

[0009] Referring to Fig. 1, an example configuration of a system including a remote control device 100 according to some embodiments will be described. The remote control device 100 provides a user with a service for remotely controlling a vehicle 110 using a user terminal 120. Hereinafter, a service for remotely controlling a vehicle 110 using the user terminal 120 will be referred to as a remote control service. Remote control may be performed not only from a location remote from the vehicle 110, but also near or inside the vehicle 110.

[0010] In the remote control service, the remote control device 100 remotely controls the vehicle 110 in accordance with operation instructions transmitted from the user terminal 120. The remote control device 100 may be capable of providing the remote control service to multiple users, each having their own individual user terminal 120. Although only two user terminals 120 are shown in FIG. 1, the remote control device 100 may provide the remote control service to three or more users. Furthermore, the remote control device 100 may be capable of remotely controlling multiple vehicles 110. Although only two vehicles 110 are shown in FIG. 1, the remote control device 100 may be capable of remotely controlling three or more vehicles 110.

[0011] The remote control device 100, the vehicle 110, and the user terminal 120 are each connected to a wide area network 130, such as the Internet. The remote control device 100 may be connected to the wide area network 130 through a local area network (LAN) (not shown). The vehicle 110 may be connected to the wide area network 130 through a cellular network (not shown). The user terminal 120 may be connected to the wide area network 130 through a cellular network (not shown) or through a LAN (not shown). The remote control device 100 and the vehicle 110 can communicate with each other through the wide area network 130. The remote control device 100 and the user terminal 120 can communicate with each other through the wide area network 130. The vehicle 110 and the user terminal 120 may also be able to communicate with each other through the wide area network 130. Alternatively or additionally, the vehicle 110 and the user terminal 120 may be able to communicate with each other directly through short-range communication such as Bluetooth (registered trademark).

[0012] An example of the hardware configuration of the remote control device 100 will be described with reference to Fig. 2. The remote control device 100 may have the components shown in Fig. 2. The remote control device 100 may also have components not shown in Fig. 2. As described above, the remote control device 100 is a device for remotely operating the vehicle 110.

[0013] The processor 201 is a general-purpose integrated circuit for executing operations by the remote operation device 100. The processor 201 may be configured, for example, by a central processing unit (CPU). The memory 202 is an integrated circuit for storing programs that define operations by the remote operation device 100 or temporary data used in the operations. The memory 202 may be configured, for example, by a random access memory (RAM) or a read-only memory (ROM). Operations by the remote operation device 100 may be realized by the processor 201 executing a computer program loaded into the memory 202. Alternatively, some or all of the operations by the remote operation device 100 may be realized by a dedicated integrated circuit such as an application-specific integrated circuit (ASIC). The remote operation device 100 may have only one processor 201 or may have multiple processors 201. If the remote operation device 100 has multiple processors 201, the operations by the remote operation device 100 may be realized by cooperation between these processors 201.

[0014] The input device 203 is a device for receiving instructions from a user of the remote operation device 100 (e.g., an operator of a remote operation service). The input device 203 may be configured, for example, by a keyboard, a mouse, a microphone, etc. The output device 204 is a device for presenting information to the user of the remote operation device 100. The output device 204 may be configured, for example, by a display (display device), a speaker, etc.

[0015] The communication device 205 is a device that enables the remote control device 100 to communicate with an external device (for example, a router or a base station). The communication device 205 may be configured, for example, as a network card. The communication device 205 may perform wireless communication or wired communication.

[0016] The storage device 206 is a device for storing information and software used for the operation of the remote control device 100. The storage device 206 may be configured with a hard disk drive (HDD) or a solid state drive (SSD). The storage device 206 stores, for example, authority management information 207. The authority management information 207 is information for managing the authority to execute remote control of the vehicle 110. The authority to execute remote control of the vehicle 110 will be referred to as operation authority below. Specific examples of the authority management information 207 will be described later.

[0017] An example of the hardware configuration of vehicle 110 will be described with reference to Fig. 3. Vehicle 110 may have the components shown in Fig. 3. Vehicle 110 may also have components not shown in Fig. 3. For example, components related to the running of vehicle 110 (such as an engine and brakes) are omitted from Fig. 3. Vehicle 110 may be a four-wheeled vehicle, a two-wheeled vehicle, or another type of vehicle.

[0018] The processor 301 is a general-purpose integrated circuit for executing operations by the vehicle 110. The processor 301 may be configured by, for example, a CPU. The memory 302 is an integrated circuit for storing programs that define operations by the vehicle 110 or temporary data used in the operations. The memory 302 may be configured by, for example, a RAM, a ROM, etc. The operations by the vehicle 110 may be realized by the processor 301 executing a computer program loaded into the memory 302. Alternatively, some or all of the operations by the vehicle 110 may be realized by a dedicated integrated circuit such as an ASIC. The vehicle 110 may have only one processor 301 or may have multiple processors 301. When the vehicle 110 has multiple processors 301, the operations by the vehicle 110 may be realized by cooperation between these processors 301. The processor 301 and the memory 302 may be provided as an electronic control unit (ECU).

[0019] The input device 303 is a device for receiving instructions from a user of the vehicle 110 (e.g., a driver of the vehicle 110). The input device 303 may be configured, for example, by a button, a touchpad, a joystick, a microphone, etc. The output device 304 is a device for presenting information to the user of the vehicle 110. The output device 304 may be configured, for example, by a display, a speaker, etc. The touchpad and the display may be combined to form a touchscreen. The output device 304 may be used to provide a navigation function.

[0020] The cellular communication device 305 is a device that allows the vehicle 110 to communicate wirelessly with an external device (e.g., a base station) that is part of a cellular network. The cellular communication device 305 may be configured, for example, with an antenna and a baseband chip. The short-range communication device 306 is a device that allows the vehicle 110 to communicate directly wirelessly with an external device (e.g., a user terminal 120). The short-range communication device 306 may be configured, for example, with an antenna and a baseband chip. The short-range communication device 306 may be compliant with, for example, the Bluetooth standard or other communication standards.

[0021] The positioning sensor 307 is a sensor for measuring the geographic position of the vehicle 110. The positioning sensor 307 may be, for example, a Global Navigation Satellite System (GNSS) sensor. The wheel speed sensor 308 is a sensor for measuring the rotational speed of the wheels of the vehicle 110. The processor 301 can measure the speed of the vehicle 110 and the distance traveled by the vehicle 110 based on the output from the wheel speed sensor 308. The door sensor 309 is a sensor for detecting the state of a door of the vehicle 110 (i.e., whether it is open or closed).

[0022] The power management device 310 is a device for managing the supply of power from a battery (not shown) of the vehicle 110 to each component of the vehicle 110. The power state of the vehicle 110 may include an off state, an accessory power on state, and an ignition power on state. When the power of the vehicle 110 is in the off state, the power management device 310 supplies power to only some of the components, including the processor 301, the memory 302, the cellular communication device 305, and the short-range communication device 306. This allows the cellular communication device 305 and the short-range communication device 306 to communicate even when the power of the vehicle 110 is off. When the power of the vehicle 110 is in the accessory power on state, the power management device 310 supplies additional power to some of the components. When the power of the vehicle 110 is in the ignition power on state, the power management device 310 supplies additional power to some of the components.

[0023] An example of the hardware configuration of the user terminal 120 will be described with reference to Fig. 4. The user terminal 120 may have the components shown in Fig. 4. The user terminal 120 may also have components not shown in Fig. 4. The user terminal 120 is a device used by a user. The user terminal 120 may be a mobile device such as a smartphone.

[0024] The processor 401 is a general-purpose integrated circuit for executing operations by the user terminal 120. The processor 401 may be configured, for example, by a CPU. The memory 402 is an integrated circuit for storing programs that define operations by the user terminal 120 or data used in the operations. The memory 402 may be configured, for example, by RAM, ROM, etc. The operations by the user terminal 120 may be realized by the processor 401 executing a computer program loaded into the memory 402. Alternatively, some or all of the operations by the user terminal 120 may be realized by a dedicated integrated circuit such as an ASIC. The user terminal 120 may have only one processor 401 or may have multiple processors 401. If the user terminal 120 has multiple processors 401, the operations by the user terminal 120 may be realized by these processors 401 working together.

[0025] The input device 403 is a device for receiving instructions from a user of the user terminal 120. The input device 403 may be configured, for example, by a button, a touchpad, a microphone, etc. The output device 404 is a device for presenting information to the user of the user terminal 120. The output device 404 may be configured, for example, by a display, a speaker, a vibrator, etc. The touchpad and the display may be integrated to form a touch screen.

[0026] The cellular communication device 405 is a device for wireless communication between the user terminal 120 and an external device (e.g., a base station) that constitutes part of a cellular network. The cellular communication device 405 may be composed of, for example, an antenna and a baseband chip. The short-range communication device 406 is a device for direct wireless communication between the user terminal 120 and an external device (e.g., a vehicle 110). The short-range communication device 406 may be composed of, for example, an antenna and a baseband chip. The short-range communication device 406 may be compliant with, for example, the Bluetooth standard, or may be compliant with other communication standards.

[0027] The positioning sensor 407 is a sensor for measuring the geographical position of the user terminal 120. The positioning sensor 407 may be, for example, a GNSS sensor. The vehicle 110 may also be equipped with a positioning sensor to measure the geographical position of the vehicle 110. The user terminal 120 can ascertain the geographical position of the vehicle 110 by receiving the geographical position of the vehicle 110 measured by the positioning sensor of the vehicle 110 and recording this geographical position in the storage device 408. Furthermore, when it is detected that a user is on board the vehicle 110, the vehicle 110 may estimate the geographical position of the user terminal 120 as the geographical position of the vehicle 110. The storage device 408 is a device for storing information and software used in the operation of the remote control device 100. The storage device 408 may be configured, for example, by an electrically erasable read only memory (EEPROM). The storage device 408 stores, for example, a remote control application 409. The remote control application 409 is an application for providing a remote control service for the vehicle 110 to the user. The operations of the user terminal 120 described below may be performed by the user operating the remote control application 409 .

[0028] An example of the operation of a system including a remote operation device 100 according to some embodiments will be described with reference to Fig. 5. Before this operation is performed, it is assumed that the user has registered an account for using the remote operation service with the remote operation device 100 and has installed a remote operation application 409 on the user's user terminal 120. It is also assumed that the user has registered the user ID of the account for using the remote operation service in the remote operation application 409.

[0029] In S501, the user pairs the short-range communication device 306 of the vehicle 110 with the short-range communication device 406 of the user terminal 120. This enables the short-range communication device 306 of the vehicle 110 and the short-range communication device 406 of the user terminal 120 to communicate with each other. The user terminal 120 may acquire the vehicle ID of the vehicle 110 during pairing, and may transmit this vehicle ID to the remote operation device 100 together with its own terminal ID or a user ID registered in the remote operation application 409. The remote operation device 100 may store this vehicle ID as the vehicle ID of the vehicle to be remotely operated by the user terminal 120 (in column 703 of the authority management information 207, which will be described later).

[0030] Next, in S502 to S506, the user acquires operation authority to execute remote operation. Specifically, in S502, the user uses the remote operation application 409 to request the remote operation device 100 to issue a usage code. The usage code is information that needs to be sent to the remote operation device 100 to acquire operation authority to execute remote operation.

[0031] In S503, the remote control device 100 generates a usage code in response to the user's request and transmits it to the vehicle 110. The remote control device 100 may, for example, randomly generate a four-digit number as the usage code. The remote control device 100 associates the generated usage code with the identification information of the user terminal 120 that requested the issuance of the usage code and stores them in the storage device 206 for use in a later step.

[0032] In S504, the vehicle 110 presents the usage code using the output device 304 in accordance with a user operation performed using the input device 303. The presentation of the usage code may be by displaying the usage code on a display device, by playing a sound representing the usage code from a speaker, or by a combination of these. Presentation of the usage code requires operation of the input device 303. Therefore, the user needs to unlock the vehicle 110 using the key of the vehicle 110 to obtain the usage code. Instead of presenting the usage code in accordance with a user operation performed using the input device 303, the vehicle 110 may present the usage code in accordance with an operation from the user terminal 120, or may present the usage code in response to the in-vehicle device detecting an occupant.

[0033] In S505, the user uses the remote operation application 409 to transmit the usage code presented by the output device 304 to the remote operation device 100. In S506, the remote operation device 100 grants the user terminal 120 operation authority to perform remote operation, on the condition that the usage code transmitted in S505 matches the usage code created in S503, and that the usage code is received in S505 within a predetermined time (for example, within five minutes) after the usage code is generated in S503. As will be described later, a validity period may be set for the operation authority.

[0034] The remote operation device 100 may grant operation authority to individual user terminals 120, or may grant operation authority to user terminals 120 on a user-by-user basis. Assume that a user has multiple user terminals 120. In this case, the remote operation device 100 may grant operation authority to the user terminal 120 used to transmit the usage code, among the multiple user terminals 120, and not grant operation authority to the other user terminals 120. The remote operation device 100 may grant operation authority to not only the user terminal 120 used to transmit the usage code, but also the other user terminals 120, among the user's multiple user terminals 120. In this case, it may be considered that the remote operation device 100 grants operation authority to the user. In the following description, a user terminal 120 that has been granted operation authority may be referred to as a user terminal 120 having operation authority. Furthermore, a user of a user terminal 120 that has been granted operation authority may be referred to as a user having operation authority. In the following description, a case will be described in which operation authority is granted to an individual user terminal 120, but instead, operation authority may be granted to a user of an individual user terminal 120. As in granting operation authority, the remote operation device 100 may revoke the operation authority of an individual user terminal 120, or may revoke the operation authority of the user terminal 120 on a user-by-user basis.

[0035] In S507, the user uses the remote control application 409 of the user terminal 120 for which the user has operation authority to send an operation instruction for the vehicle 110 to the remote control device 100. Specific examples of operation instructions will be described later. In S508, the remote control device 100 verifies that the user terminal 120 that sent the operation instruction has operation authority.

[0036] At S509, the remote control device 100 transmits an operation instruction to the vehicle 110 in order to remotely operate the vehicle 110 according to the operation instruction from the user. At S510, the vehicle 110 executes the operation instructed by the remote control device 100. By repeating the operations of S507 to S510, the user can repeatedly instruct remote operation as long as the operation authority is valid.

[0037] In S511, the remote operation device 100 cancels the operation authority granted to the user terminal 120 in response to the expiration of the validity period of the operation authority. By periodically canceling the operation authority in this manner, it is possible to prevent unauthorized use of the remote operation service. The remote operation device 100 may update the validity period of the operation authority when S502 to S506 are executed within the validity period.

[0038] 6, an example of a screen displayed on the output device 404 (specifically, a display) of the user terminal 120 by the remote control application 409 will be described. In addition to the screens 600 and 610 described below, the output device 404 may also display a menu screen for transitioning to these screens.

[0039] 6(a) shows an example of a screen 600 used to issue and transmit a usage code. The screen 600 includes a button 601 for requesting the issuance of a usage code in S502 described above. When the user selects (e.g., presses) the button 601 using the input device 403, a request to issue a usage code is transmitted to the remote operation device 100. The address of the remote operation device 100 may be set in advance in the remote operation application 409.

[0040] The screen 600 further includes a field 602 for inputting a usage code, and a button 603 for transmitting the usage code inputted in the field 602 to the remote operation device 100. When the user inputs the usage code in the field 602 using the input device 403 and selects (e.g., presses) the button 603, the usage code inputted in the field 602 is transmitted to the remote operation device 100. In the example of FIG. 6(a), the button 601, the field 602, and the button 603 are included in the same screen 600, but these objects may be distributed and arranged on multiple screens.

[0041] 6(b) shows an example of a screen 610 used to remotely control the vehicle 110. The screen 610 includes a button 611 for unlocking the vehicle 110. The vehicle 110 is unlocked when the user selects (e.g., presses) the button 611 using the input device 403.

[0042] The screen 610 further includes a button 612 for turning on the power of the vehicle 110. When the user selects (e.g., presses) the button 612 using the input device 403, the power of the vehicle 110 is turned on (e.g., the ignition power is turned on). This allows the user to start the vehicle 110. To further improve security, the remote control application 409 may require the user to enter an activation code presented by the output device 304 of the vehicle 110 after the button 612 is pressed.

[0043] The screen 610 further includes a button 613 for starting the air conditioner of the vehicle 110. The air conditioner of the vehicle 110 is started by the user selecting (e.g., pressing) the button 613 using the input device 403. The remote control application 409 may provide remote control for changing the settings (e.g., temperature) of the air conditioner of the vehicle 110.

[0044] Screen 610 further includes buttons 614 for changing the state of vehicle 110 to make vehicle 110 easier to find. When the user selects (e.g., presses) button 614 using input device 403, for example, the lights of vehicle 110 flash for a predetermined period of time.

[0045] As described above, when the remote control application 409 includes an unlock operation and a power-on operation as remote operations, the user can use the user terminal 120 instead of a key for the vehicle 110 to start the vehicle 110. Therefore, the user terminal 120 can function as a digital key. The remote control application 409 may include operations other than those described in FIG. 6(b) as remote operations, or may not include some or all of the operations described in FIG. 6(b). In the example of FIG. 6(b), buttons 611 to 614 are included on the same screen 610, but these objects may be distributed across multiple screens.

[0046] An example of the authority management information 207 will be described with reference to Fig. 7. In Fig. 7, the operation authority of each user is managed in a table format. Alternatively, the operation authority of each user may be managed in another format. In the authority management information 207, a record is generated for each user who has registered an account for using the remote operation service in the remote operation device 100.

[0047] Column 700 (user ID) represents identification information (i.e., user ID) for uniquely identifying a user. The user ID may be the account name of an account for the user to use the remote operation service. The account name may be a character string specified by the user (e.g., an email address), or may be a unique character string generated by the remote operation device 100. When a user registers an account, the remote operation device 100 adds a record to the authority management information 207 and registers the user ID in column 700 of that record.

[0048] Column 701 (terminal ID) represents identification information (i.e., terminal ID) for uniquely identifying the user terminal 120 used by the user. The terminal ID may be, for example, the address of the short-range communication device 406 (BD address in the case of Bluetooth). The terminal ID may also be the serial number of the user terminal 120. The terminal ID may also be a character string uniquely assigned to the user terminal 120 by the remote operation device 100. When the user inputs an account name, the remote operation application 409 of the user terminal 120 may transmit the user ID of the user terminal 120 to the remote operation device 100. The remote operation device 100 registers the received terminal ID in column 701. When the remote operation device 100 assigns a terminal ID to the user terminal 120, the remote operation device 100 registers the terminal ID in column 701 and transmits the terminal ID to the user terminal 120. The user terminal 120 stores the received terminal ID for use in subsequent processing.

[0049] In some embodiments, one user may be able to register only one user terminal 120 to be used for remote control, or may be able to register multiple user terminals 120. When one user registers multiple user terminals 120, multiple terminal IDs are registered in column 701.

[0050] Column 702 (Vehicle ID) shows identification information (i.e., vehicle ID) for uniquely identifying the vehicle that the user remotely controls. The vehicle ID may be, for example, an IP address assigned to the cellular communication device 305 of the vehicle 110. The vehicle ID may be stored in the vehicle 110. The user terminal 120 may obtain the vehicle ID from the vehicle 110 when performing pairing in S501 of FIG. 5, and may transmit this vehicle ID to the remote control device 100 together with a request for issuing a usage code in S502. The remote control device 100 registers the received vehicle ID in column 702.

[0051] In some embodiments, one user may be able to register only one vehicle 110 to be remotely controlled, or may be able to register multiple vehicles 110. When one user registers multiple vehicles 110, multiple vehicle IDs are registered in column 702. When multiple vehicle IDs are registered, the remote control device 100 may acquire the vehicle ID of the vehicle to be remotely controlled along with a remote control instruction.

[0052] Column 703 (operation authority) represents the operation authority for a user to perform remote operation. In some embodiments, the operation authority may include three types of operation authority: regular authority, temporary authority, and specified number of times authority. For example, a user with user ID "U1" has regular authority to remotely operate vehicle "V1." A user with user ID "U2" has temporary authority to remotely operate vehicle "V1." A user with user ID "U3" has specified number of times authority to remotely operate vehicle "V1." A user with user ID "U4" does not have operation authority to remotely operate vehicle "V1."

[0053] As described in FIG. 5, authorized authority is an operating authority granted to the user terminal 120 or its user when the user transmits a usage code to the remote operation device 100 using the user terminal 120. Authorized authority has a relatively long validity period (e.g., 50 days). After being granted authorized authority, the user can repeatedly remotely operate the vehicle 110 within the validity period without transmitting a usage code to the remote operation device 100. The remote operation device 100 cancels the authorized authority when the validity period has elapsed since the authorization was granted. Thereafter, the user must obtain operating authority again to perform a new remote operation.

[0054] In some embodiments, the remote control device 100 grants the user terminal 120 permission to operate the vehicle 110 based on the user terminal 120 being located within the vehicle 110. In such a case, the remote control device 100 may grant temporary permission. The temporary permission has a relatively short validity period (e.g., two days). That is, the validity period of the temporary permission may be shorter than the validity period of the regular permission. The remote control device 100 cancels the temporary permission based on the expiration of the validity period after granting the temporary permission. The types of remote operations that can be performed by a user terminal 120 with temporary permission may be the same as, less than, or more than the types of remote operations that can be performed by a user terminal 120 with regular permission. When there are multiple user terminals 120 within the vehicle 110, the remote control device 100 may grant temporary permission to each of the multiple user terminals 120.

[0055] A scenario in which granting operation authority based on the user terminal 120 being located in the vehicle 110 is advantageous will be described. The user unlocks the vehicle 110 using the user terminal 120 for which the operation authority is granted and starts driving. Suppose that the user then parks the vehicle 110 and, while shopping outside the vehicle, the operation authority expires and is revoked. In this case, conventionally, the user would not be able to unlock the vehicle 110 unless he or she had the key, and therefore would not be able to send the usage code. However, because the operation authority is granted based on the user terminal 120 being located in the vehicle 110, the user can unlock the vehicle 110 using the user terminal 120. In this way, user convenience is improved.

[0056] Another scenario in which it is advantageous to grant operation authority based on the user terminal 120 being in the vehicle 110 will be described. Suppose a husband and wife are going to a shopping center in the vehicle 110. Each husband and wife has their own user terminal 120 with the remote operation application 409 installed. The husband has regular authority to use the vehicle 110, while the wife does not have authority to operate the vehicle 110. Later, the husband and wife go shopping together at the shopping center. In this case, if the wife's user terminal 120 is granted operation authority (temporary authority) for the vehicle 110, the wife can use her own user terminal 120 to remotely operate the vehicle 110 (for example, unlock or power on), thereby improving convenience.

[0057] The user terminal 120 located within the vehicle may include a user terminal 120 that traveled together with the vehicle 110. In some embodiments, the remote operation device 100 may grant temporary authority to the vehicle 110 for the user terminal 120 based on the fact that the user terminal 120 traveled together with the vehicle 110. The user terminal 120 that traveled together with the vehicle 110 may include a user terminal 120 that was located within the vehicle 110 when the vehicle 110 was deactivated. The deactivation of the vehicle 110 may refer to the power being turned off to the vehicle 110. For example, the vehicle 110 may identify the user terminal 120 located within the vehicle 110 when the vehicle 110 was deactivated and determine that the user terminal 120 traveled together with the vehicle 110. The fact that the user terminal 120 is located within the vehicle 110 may be determined based on, for example, whether the vehicle 110 and the user terminal 120 are capable of communicating via short-range communication (e.g., Bluetooth). Alternatively or additionally, the presence of the user terminal 120 in the vehicle 110 may be determined based on a comparison of the historical geographical location measured by the positioning sensor 307 of the vehicle 110 with the historical geographical location measured by the positioning sensor 407 of the user terminal 120.

[0058] The user terminal 120 traveling together with the vehicle 110 may include a user terminal 120 that is inside the vehicle 110 when the door of the vehicle 110 is opened. The vehicle 110 can detect that the door of the vehicle 110 has been opened using a door sensor 309. By including such a user terminal 120, operation authority (e.g., temporary authority) can also be granted to the user terminal 120 of a user who gets out of the vehicle 110 before the vehicle 110 stops operating.

[0059] The conditions for the remote operation device 100 to grant temporary authority to the user terminal 120 may include whether the distance traveled by the vehicle 110 and the user terminal 120 together is equal to or greater than a threshold. That is, the remote operation device 100 may grant temporary authority to the user terminal 120 when the distance traveled by the vehicle 110 and the user terminal 120 together is equal to or greater than a threshold (e.g., 20 km). On the other hand, the remote operation device 100 may not grant temporary authority to the user terminal 120 when the distance traveled by the vehicle 110 and the user terminal 120 together is less than the threshold. This makes it possible to prevent operation authority from being granted in unnecessary situations, such as during a test drive at a dealership.

[0060] The remote control device 100 may revoke the temporary authority of the user terminal 120 when an operation instruction is transmitted from the user terminal 120 located at a location that is a threshold distance (e.g., 300 km) or more away from the current or past location of the vehicle 110 within a threshold time (e.g., one day) after the temporary authority was granted. As described above, temporary authority is useful in a scenario in which operation authority is granted to the user terminal 120 of a user who stays near the vehicle 110 for a short period of time. Therefore, security can be improved by not granting operation authority in situations that do not match such a scenario.

[0061] The remote control device 100 may determine the current position of the vehicle 110 based on the measurement results of the positioning sensor 307 of the vehicle 110. The past position of the vehicle 110 may be the position at the time when the user terminal 120 finished traveling together with the vehicle 110. In other words, the past position of the vehicle 110 may be the position where the user terminal 120 was last located inside the vehicle 110. For example, this position may be the position where the power of the vehicle 110 was turned off. The remote control device 100 may determine the past position of the vehicle 110 based on the measurement results of the positioning sensor 307 of the vehicle 110, or based on the measurement results of the positioning sensor 407 of the user terminal 120.

[0062] The remote control device 100 may cancel the temporary authority based on the fact that the vehicle 110 is started after the temporary authority has been granted. The activation of the power source of the vehicle 110 may be based on the fact that the power source of the vehicle 110 has changed to an ignition power-on state. As described above, the temporary authority is useful in a scenario in which operation authority is granted to the user terminal 120 of a user who is staying near the vehicle 110 for a short period of time. In such a scenario, when the vehicle 110 is started and a new movement is started, the temporary authority granted up to that point ceases to serve its purpose. Therefore, security can be improved by canceling the temporary authority based on the fact that the vehicle 110 is started. Unlike the temporary authority, the legitimate authority is operation authority intended to be used for a relatively long period of time. Therefore, the remote control device 100 may maintain the legitimate authority when the power source of the vehicle 110 is started. In other words, the remote control device 100 does not need to cancel the legitimate authority when the power source of the vehicle 110 is started.

[0063] In some embodiments, the remote operation device 100 may grant operation authority to a user terminal 120 or a user designated by a user with authorized authority. In such a case, the remote operation device 100 may grant a number-designated authority instead of granting authorized authority. The number-designated authority is an operation authority that allows remote operation to be performed a predetermined number of times (e.g., 20 times). The validity period of the number-designated authority may be a time period designated by a user with authorized authority. The types of remote operations that can be performed by a user terminal 120 with number-designated authority may be the same as, or may be more than, or less than the types of remote operations that can be performed by a user terminal 120 with authorized authority. For example, the stroke-designated authority may allow only unlocking and power-on remote operations.

[0064] An example of a scenario in which a designated number of times of operation authority is granted will be described. For example, suppose that the vehicle 110 is used as a shared car. If the owner of the shared car can grant the operating authority (designated number of times of operation authority) to the renter, the owner can allow the renter to drive the vehicle 110 without handing over the key to the renter. Therefore, in some embodiments, the remote operation device 100 grants the operating authority to a user terminal or user designated by a user of the user terminal 120 who has proper authorization. The operating authority granted here may be a designated number of times of operation authority.

[0065] When the remote operation device 100 grants operation authority to the user terminal 120, it registers the type of operation authority in column 703. When the remote operation device 100 cancels the operation authority of the user terminal 120, it deletes column 703.

[0066] Column 704 (Expiration Date) indicates the expiration date of the operation authority. The remote operation device 100 calculates the expiration date based on the date and time when the operation authority is granted to the user and the validity period according to the type of the operation authority, and registers this expiration date in column 704.

[0067] When multiple types of operation authority are granted to the user terminal 120, the remote operation device 100 may manage the multiple types of operation authority separately. For example, suppose that both regular authority and temporary authority are granted to one user terminal 120. In this case, if the conditions for releasing the temporary authority are met, the remote operation device 100 may release the temporary authority but not the regular authority. Furthermore, if the conditions for releasing the regular authority are met, the remote operation device 100 may release the regular authority but not the temporary authority.

[0068] An example of an operation performed by the user terminal 120 will be described with reference to Fig. 8. Each step in Fig. 8 may be performed by the processor 401 executing a computer program loaded into the memory 402. Alternatively, some or all of the steps in Fig. 8 may be performed by a dedicated integrated circuit such as an ASIC. In such a case, the dedicated integrated circuit may operate as a functional unit for performing each step. The operation in Fig. 8 may be repeatedly performed during operation of the user terminal 120.

[0069] In S801, the user terminal 120 determines whether the user has started using the remote control application 409. If it is determined that the user has started using the remote control application 409 ("YES" in S801), the user terminal 120 transitions the process to S802, and otherwise ("NO" in S801), repeats S801. The user terminal 120 may determine that the user has started using the remote control application 409 when the remote control application 409 is launched or when the remote control application 409 is changed from background to active.

[0070] In S802, the user terminal 120 sends an inquiry to the remote operation device 100 as to whether the user terminal 120 has operation authority. In S803, the user terminal 120 determines whether the user terminal 120 has operation authority based on the result of the inquiry. If the user terminal 120 determines that the user terminal 120 has operation authority ("YES" in S803), the user terminal 120 transitions the process to S804, and otherwise ("NO" in S803), the process transitions to S807. The operation authority may be regular authority, temporary authority, or number-of-times-designated authority.

[0071] If the user terminal 120 has the operation authority, the user terminal 120 performs remote operation of the vehicle 110 through steps S804 to S806. In step S804, the user terminal 120 uses the output device 404 to display a screen for performing remote operation (for example, screen 610 in FIG. 6(b)).

[0072] In S805, the user terminal 120 determines whether an operation instruction has been acquired from the user using the input device 403. If it is determined that an operation instruction has been acquired from the user ("YES" in S805), the user terminal 120 transitions the process to S805, and otherwise ("NO" in S805), repeats S805. The operation instruction may be, for example, pressing any of the buttons 611 to 614 in FIG. 6(b). In S806, the user terminal 120 transmits the operation instruction acquired from the user to the remote operation device 100.

[0073] If the user terminal 120 does not have the operation authority, the user terminal 120 acquires the operation authority of the vehicle 110 through steps S807 to S811. In step S807, the user terminal 120 uses the output device 404 to display a screen (for example, screen 600 in FIG. 6(a)) for requesting the issuance of a usage code.

[0074] In S808, the user terminal 120 determines whether an issuance instruction has been received from the user using the input device 403. An issuance instruction is an instruction to request the issuance of a usage code. If it is determined that an issuance instruction has been received from the user ("YES" in S808), the user terminal 120 transitions the process to S809, and otherwise ("NO" in S808), repeats S808. The issuance instruction may be, for example, pressing the button 601 in FIG. 6(a). In S809, the user terminal 120 transmits a request to issue a usage code to the remote operation device 100.

[0075] In S810, the user terminal 120 determines whether a code transmission instruction has been received from the user using the input device 403. A code transmission instruction is an instruction to transmit a usage code. If it is determined that a code transmission instruction has been received from the user ("YES" in S810), the user terminal 120 transitions the process to S811, and otherwise ("NO" in S810), the user terminal 120 repeats S810. The usage code instruction may be, for example, pressing the button 603 in FIG. 6(a). In S811, the user terminal 120 transmits the usage code entered in the field 602 to the remote operation device 100.

[0076] The data transmitted from the user terminal 120 to the remote operation device 100 may include identification information associated with the user terminal 120. The identification information associated with the user terminal 120 may be a user ID or a terminal ID. The user ID may be the same type as the user ID described in column 700 of FIG. 7. The terminal ID may be the same type as the terminal ID described in column 701 of FIG. 7.

[0077] An example of an operation performed by the remote operation device 100 will be described with reference to Fig. 9. Each step in Fig. 9 may be performed by the processor 201 executing a computer program loaded into the memory 202. Alternatively, some or all of the steps in Fig. 9 may be performed by a dedicated integrated circuit such as an ASIC. In such a case, the dedicated integrated circuit may operate as a functional unit for performing each step. The operation in Fig. 9 may be repeatedly performed during operation of the remote operation device 100. The remote operation device 100 may perform the operations in Figs. 9(a) to 9(d) in parallel.

[0078] 9(a), the remote operation device 100 responds to an inquiry about operation authority from the user terminal 120. In S901, the remote operation device 100 determines whether or not the inquiry about operation authority transmitted in S802 has been received. If it is determined that the inquiry about operation authority has been received ("YES" in S901), the remote operation device 100 transitions the process to S902, and otherwise ("NO" in S901) repeats S901.

[0079] In S902, the remote operation device 100 refers to the authority management information 207 to confirm whether the user terminal 120 or the user specified based on the identification information (user ID or terminal ID) included in the inquiry has operation authority. In S903, the remote operation device 100 transmits the confirmation result of S902 as a response to the inquiry.

[0080] 9(b), the remote operation device 100 processes an operation instruction from the user terminal 120. In S911, the remote operation device 100 determines whether or not the operation instruction transmitted in S805 has been received. If it is determined that the operation instruction has been received ("YES" in S911), the remote operation device 100 transitions the process to S912, and otherwise ("NO" in S911) repeats S911.

[0081] In S912, the remote control device 100 refers to the authority management information 207 and identifies the vehicle 110 to be operated based on the identification information (user ID or terminal ID) included in the inquiry. Thereafter, the remote control device 100 remotely operates the identified vehicle 110 in accordance with the operation instruction. Specifically, the remote control device 100 transmits the operation instruction to the vehicle 110.

[0082] As described in Fig. 8, the user terminal 120 to which an operation instruction can be sent in S805 is the user terminal 120 determined to have operation authority in S803. Therefore, in the operation shown in Fig. 9(b), the remote operation device 100 does not need to determine whether the user terminal 120 has operation authority. Instead, the remote operation device 100 may determine whether the user terminal 120 has operation authority between S911 and S912. In this case, the remote operation device 100 may execute S912 if the user terminal 120 has operation authority, and may return an error to the user terminal 120 without executing S912 if the user terminal 120 does not have operation authority.

[0083] 9(c), the remote operation device 100 grants operation authority to the user terminal 120. As described above, the remote operation device 100 may grant operation authority to a specific user instead of granting operation authority to a specific user terminal 120.

[0084] In S921, the remote operation device 100 determines whether the specific user terminal 120 satisfies the conditions for granting operation authority (hereinafter referred to as granting conditions). If it is determined that the specific user terminal 120 satisfies the granting conditions ("YES" in S921), the remote operation device 100 transitions the process to S922, and otherwise ("NO" in S921) repeats S921. In S922, the remote operation device 100 grants operation authority to the specific user terminal 120 that is determined to satisfy the granting conditions.

[0085] The granting condition may be any of the granting conditions described above. To reiterate, the granting condition may include receiving the usage code from the user terminal 120 within a predetermined time (e.g., within five minutes) after the remote operation device 100 issues the usage code. In this case, the remote operation device 100 may grant legitimate authority to the user terminal 120.

[0086] The granting condition may be that the user terminal 120 is located inside the vehicle 110. As will be described later, the vehicle 110 transmits identification information (user ID or terminal ID) associated with the user terminal 120 located inside the vehicle 110 to the remote operation device 100. Therefore, the granting condition may include obtaining, from the vehicle 110, identification information associated with the user terminal 120 located inside the vehicle 110. The identification information associated with the user terminal 120 may be the terminal ID of the user terminal 120, or may be the user ID of the user who uses the user terminal 120. The remote operation device 100 may grant temporary authority to the user terminal 120 associated with the identification information obtained in this manner.

[0087] The remote operation device 100 may acquire identification information associated with each of the multiple user terminals 120 from the vehicle 110. In this case, the remote operation device 100 may grant temporary authority to each of the multiple user terminals 120 associated with the acquired identification information. When the remote operation device 100 acquires a terminal ID, the remote operation device 100 may grant temporary authority only to the user terminal 120 identified by the terminal ID, or may grant temporary authority to the user who owns the user terminal 120 identified by the terminal ID. When the remote operation device 100 acquires a user ID, the remote operation device 100 may grant temporary authority to the user identified by the user ID.

[0088] The conditions for granting the number of times may include that the vehicle 110 is a shared car and that a legitimate user of the user terminal 120 has requested that the number of times designation authority be granted to a specific user terminal or user. The legitimate user of the user terminal 120 may make such a request using the remote operation application 409 or a web interface provided by the remote operation device 100. The remote operation device 100 may grant the number of times designation authority to a specific user terminal or user in accordance with such a request.

[0089] 9(d), the remote operation device 100 releases the operation authority of the user terminal 120. As described above, the remote operation device 100 may release the operation authority of a specific user instead of releasing the operation authority of a specific user terminal 120.

[0090] In S931, the remote operation device 100 determines whether the specific user terminal 120 satisfies the condition for releasing the operation authority (hereinafter referred to as the release condition). If it is determined that the specific user terminal 120 has satisfied the release condition ("YES" in S931), the remote operation device 100 transitions the process to S932, and otherwise ("NO" in S931), repeats S931. In S932, the remote operation device 100 releases the operation authority of the specific user terminal 120 that has been determined to have satisfied the release condition.

[0091] The cancellation condition may be any of the cancellation conditions described above. To reiterate, the cancellation condition may include the expiration of the validity period of the operation authority. The remote operation device 100 may cancel the operation authority whose validity period has expired.

[0092] The release condition may include that the vehicle 110 has started up. When the vehicle 110 has started up, the remote control device 100 may release the temporary authority for the vehicle 110. When the vehicle 110 has started up, the remote control device 100 may maintain other types of authority for the vehicle 110 (i.e., regular authority and specified-number authority).

[0093] The cancellation condition may include that the remote operation has been performed a designated number of times from the user terminal 120 to which the number-designating authority has been granted. In such a case, the remote operation device 100 may cancel the number-designating authority.

[0094] The release condition may include a request by a user or an operator of the remote operation device 100 to release the operation authority. The user may make such a request using the remote operation application 409 or a web interface provided by the remote operation device 100. The operator may make such a request using the input device 203. The remote operation device 100 may release the specified operation authority.

[0095] The cancellation condition may include that an operation instruction is transmitted from a user terminal 120 located at a threshold distance (e.g., 300 km) or more from the current or past location of the vehicle 110 within a threshold time (e.g., one day) after the temporary authority is granted. In such a case, the remote operation device 100 may cancel the temporary authority of the user terminal 120.

[0096] An example of an operation performed by the vehicle 110 will be described with reference to FIG. 10. Each step in FIG. 10 may be performed by the processor 301 executing a computer program loaded into the memory 302. Alternatively, some or all of the steps in FIG. 10 may be performed by a dedicated integrated circuit such as an ASIC. In such a case, the dedicated integrated circuit may operate as a functional unit for performing each step. The operation in FIG. 10 may be repeatedly performed while the vehicle 110 is operating. The vehicle 110 may perform the operations in FIGS. 10(a) to 10(d) in parallel.

[0097] 10(a), the vehicle 110 presents a usage code. In S1001, the vehicle 110 determines whether or not it has received the usage code transmitted from the remote control device 100 in S503. If it is determined that the usage code has been received ("YES" in S1001), the vehicle 110 transitions the process to S1002, and otherwise ("NO" in S1001) repeats S1001. In S1002, the vehicle 110 presents the usage code using the output device 304 in response to the user's operation of the input device 303.

[0098] In the operation shown in FIG. 10(b), the vehicle 110 operates in accordance with a remote control instruction. In S1011, the vehicle 110 determines whether or not it has received the operation instruction transmitted in S912 from the remote control device 100. If it is determined that the operation instruction has been received ("YES" in S1011), the vehicle 110 transitions the process to S1012, and otherwise ("NO" in S1011), the vehicle 110 repeats S1011. In S1012, the vehicle 110 performs an operation in accordance with the operation instruction. For example, if the operation instruction is to unlock the doors, the vehicle 110 unlocks the doors.

[0099] In the operation shown in FIG. 10(c), the vehicle 110 transmits identification information associated with the user terminal 120 inside the vehicle 110 to the remote control device 100. In S1021, the vehicle 110 determines whether it has ended its movement. If it is determined that it has ended its movement ("YES" in S1021), the vehicle 110 transitions the process to S1022, and otherwise ("NO" in S1021), it repeats S1021. The vehicle 110 may determine that its movement has ended based on the fact that the power supply to the vehicle 110 has been turned off. Alternatively or in addition to this, the vehicle 110 may determine that its movement has ended based on the fact that a door of the vehicle 110 has been opened. Alternatively, the vehicle 110 may determine that its movement has ended based on the fact that a door of the vehicle 110 has been opened or the power supply has been turned off after the vehicle 110 has traveled a threshold distance (e.g., 20 km) or more. Furthermore, the vehicle 110 may determine that the user terminal 120 has left the vehicle 110 if the short-range communication device 306 changes from a state in which it can communicate with the short-range communication device 406 of the user terminal 120 to a state in which it cannot communicate with the short-range communication device 406 of the user terminal 120 (for example, if the user terminal 120 moves out of communication range).

[0100] At S1022, the vehicle 110 acquires identification information associated with the user terminal 120 within the vehicle 110. The identification information may be acquired using the short-range communication device 306 of the vehicle 110. The identification information associated with the user terminal 120 may be the terminal ID of the user terminal 120 or the user ID of the user of the user terminal 120. If there are multiple user terminals 120 within the vehicle 110, the vehicle 110 may acquire identification information from each of the multiple user terminals 120. At S1023, the vehicle 110 transmits the identification information acquired at S1022 to the remote operation device 100. This identification information is used in S921 and S922 described above.

[0101] In the above example, the vehicle 110 transmits identification information associated with the user terminal 120 located within the vehicle 110 to the remote control device 100. Alternatively, the user terminal 120 may transmit identification information associated with the user terminal 120 located within the vehicle 110 to the remote control device 100. For example, the user terminal 120 may determine that the user terminal 120 has left the vehicle 110 when the short-range communication device 406 changes from a state in which it can communicate with the short-range communication device 306 of the vehicle 110 to a state in which it cannot communicate with the short-range communication device 306 (e.g., when the user terminal 120 moves out of communication range).

[0102] In the operation shown in FIG. 10(d), the vehicle 110 notifies the remote control device 100 that the vehicle 110 has started up. In S1031, the vehicle 110 determines whether the vehicle 110 has started up. Starting the vehicle 110 may be achieved by changing the ignition power to an on state. If the vehicle 110 determines that the vehicle 110 has started up ("YES" in S1031), the vehicle 110 transitions the process to S1032, and otherwise ("NO" in S1031), repeats S1031. In S1032, the vehicle 110 notifies the remote control device 100 that the vehicle 110 has started up. This notification is used in S921 and S922 described above.

[0103] 11 and 12, a modified example of the operation of the user terminal 120 and the remote operation device 100 described above will be described. In the operation shown in FIG. 8, if the user terminal 120 does not have the operation authority, the user terminal 120 does not display a screen (e.g., screen 610) for issuing an operation instruction. Therefore, the user cannot issue an operation instruction using the user terminal 120 for which the user does not have the operation authority. Instead, in the following modified example, after receiving an operation instruction from the user, it is determined whether the user terminal 120 has the operation authority.

[0104] The user terminal 120 executes the operations shown in Fig. 11 instead of the operations shown in Fig. 8. At S1101, the user terminal 120 displays a screen (for example, screen 610) for issuing an operation instruction in accordance with an instruction from the user. At S1102, the user terminal 120 determines whether an operation instruction has been acquired from the user using the input device 403, as in S805. At S1103, the user terminal 120 transmits the operation instruction acquired from the user to the remote operation device 100, as in S806. The operations of S1101 to S1103 are executed regardless of whether the user terminal 120 has operation authority.

[0105] In S1104, the user terminal 120 determines whether or not it has received a notification from the remote operation device 100 that it cannot perform remote operation because it does not have the operating authority. If it is determined that it has received such a notification ("YES" in S1104), the user terminal 120 transitions the process to S1105, and otherwise ("NO" in S1104), it terminates the process.

[0106] In S1105, the user terminal 120 notifies the user that remote operation cannot be performed because the user does not have the operation authority. After that, the user terminal 120 may automatically display the screen 600.

[0107] The remote operation device 100 executes the operation shown in Fig. 12 instead of the operation shown in Fig. 9(b). In S1201, the remote operation device 100 determines whether or not the operation instruction transmitted from the remote operation device 100 in S1102 has been received, similarly to S911.

[0108] In S1202, the remote operation device 100 determines whether the user terminal 120 has operation authority by referring to the authority management information 207. If it is determined that the user terminal 120 has operation authority ("YES" in S1202), the user terminal 120 transitions the process to S1203, and otherwise ("NO" in S1202), the process transitions to S1204.

[0109] In S1203, the remote control device 100 remotely operates the identified vehicle 110 in accordance with the operation instruction, similar to S912. In S1204, the remote control device 100 notifies the user terminal 120 that the remote control cannot be performed because the remote control device 100 does not have the operation authority.

[0110] In the above-described operation, the remote operation device 100 determines whether the user terminal 120 has operation authority. Alternatively, the user terminal 120 may determine whether the user terminal 120 has operation authority in S1104 in the same manner as in S802 to S803. Alternatively, the user terminal 120 may determine whether the user terminal 120 has operation authority before displaying the operation screen in S1101. If the user terminal 120 does not have operation authority, the user terminal 120 may indicate on the operation screen (for example, screen 610) that the user terminal 120 does not have operation authority, i.e., that remote operation cannot be performed. For example, the user terminal 120 may gray out buttons 611 to 614 for performing remote operation.

[0111] <Summary of the embodiment> [Item 1] A remote control device (100) for remotely controlling a vehicle (110), an acquisition means for acquiring identification information (700, 701) associated with a user terminal (120) located within the vehicle; an authority management means for granting an operation authority for remotely operating the vehicle to a user terminal associated with the acquired identification information; an operation means for remotely operating the vehicle in accordance with an operation instruction transmitted from the user terminal having the operation authority; A remote control device comprising: According to this item, remote operation authority can be granted in a simple manner, improving convenience. [Item 2] Item 1. The remote control device according to item 1, wherein the user terminal located within the vehicle includes a user terminal located within the vehicle when the vehicle's startup state is stopped. This item allows the user terminal that traveled together with the vehicle to be appropriately identified. [Item 3] When a plurality of user terminals are present in the vehicle, the acquisition means acquires the identification information for each of the plurality of user terminals; Item 2. The remote control device according to item 1, wherein the authority management means grants the operation authority to each of a plurality of user terminals associated with the acquired identification information. According to this item, operation authority can be given not only to the driver but also to passengers, improving convenience. [Item 4] 2. The remote control device according to claim 1, wherein the authority management means does not grant the operation authority to the user terminal if the distance traveled by the vehicle and the user terminal together is less than a threshold value. This item makes it possible to restrict the granting of operating authority for short-term rides such as test drives, thereby improving security. [Item 5] The remote control device described in item 1, wherein the authority management means revokes the operation authority of the user terminal when the operation instruction is sent from a user terminal located at a position more than a threshold distance from the current or past position of the vehicle within a threshold time after the operation authority is granted. According to this item, the operating authority of a user terminal that has performed suspicious remote control can be revoked, thereby improving security. [Item 6] Item 2. The remote control device according to item 1, wherein the authority management means revokes the operation authority based on the vehicle being started after the operation authority has been granted. According to this item, temporary operating authority can be granted to a user who travels with the vehicle, thereby improving security. [Item 7] the operating authority is a first operating authority; the authority management means grants a second operation authority to the user terminal that transmitted the usage code presented in the vehicle; Item 7. The remote control device according to item 6, wherein the authority management means maintains the second operating authority when the vehicle's power source is turned on. According to this item, the operating authority of the user who inputs the usage code can be maintained, thereby improving convenience. [Item 8] The authority management means Releasing the first operation authority based on the fact that a first validity period has elapsed since the first operation authority was granted; Releasing the second operation authority based on the fact that a second validity period has elapsed since the second operation authority was granted; 8. The remote control device according to item 7, wherein the first validity period is shorter than the second validity period. According to this item, short-term operation authority can be granted to users who travel with the vehicle, thereby improving security. [Item 9] The vehicle is a shared car, The remote control device described in item 7, wherein the authority management means grants a third operation authority to a user terminal or user designated by a user of a user terminal having the second operation authority, enabling the user to perform remote operations a predetermined number of times. This provision allows a Share Car owner to lend the vehicle to a borrower without handing over the keys. [Item 10] Item 1. The remote control device according to item 1, wherein the user terminal located within the vehicle includes a user terminal that has traveled with the vehicle. According to this item, it is possible to grant operation authority to user terminals that travel together with the vehicle. [Item 11] A computer program for causing a computer to function as each means of the remote control device described in any one of items 1 to 10. According to this item, the above items are provided in the form of a program. [Item 12] A control method for a remote control device (100) that remotely controls a vehicle (110), comprising: acquiring identification information associated with a user terminal (120) located within the vehicle; an authority management step of granting an operation authority for remotely operating the vehicle to a user terminal associated with the acquired identification information; an operation step of remotely operating the vehicle in accordance with an operation instruction transmitted from the user terminal having the operation authority; A control method comprising: According to this item, remote operation authority can be granted in a simple manner, improving convenience.

[0112] The invention is not limited to the above-described embodiment, and various modifications and variations are possible within the scope of the gist of the invention. [Explanation of symbols]

[0113] 100 remote control device, 110 vehicle, 120 user terminal

Claims

1. A remote control device for remotely operating a vehicle, an acquisition means for acquiring identification information associated with a user terminal located within the vehicle when the power supply of the vehicle is turned off; an authority management means for granting an operation authority for remotely operating the vehicle to a user terminal associated with the acquired identification information; an operation means for remotely operating the vehicle in accordance with an operation instruction transmitted from the user terminal having the operation authority; A remote control device comprising:

2. When a plurality of user terminals are present in the vehicle, the acquisition means acquires the identification information for each of the plurality of user terminals; The remote control device according to claim 1 , wherein the authority management means grants the operation authority to each of a plurality of user terminals associated with the acquired identification information.

3. The remote control device according to claim 1 , wherein the authority management means does not grant the operation authority to the user terminal when a distance traveled by the vehicle and the user terminal together is less than a threshold value.

4. The remote control device according to claim 1, wherein the authority management means revokes the operation authority of the user terminal when the operation instruction is transmitted from a user terminal located at a position that is more than a threshold distance away from the current or past position of the vehicle within a threshold time after the operation authority is granted.

5. The remote control device according to claim 1 , wherein the authority management unit cancels the operation authority when the power source of the vehicle is turned on after the operation authority has been granted.

6. the operation authority is a first operation authority, the authority management means grants a second operation authority to the user terminal that transmitted the usage code presented in the vehicle; The remote control device according to claim 5 , wherein the authority management means maintains the second operating authority when the power source of the vehicle is turned on.

7. The authority management means Releasing the first operation authority based on the fact that a first validity period has elapsed since the first operation authority was granted; Releasing the second operation authority based on the fact that a second validity period has elapsed since the second operation authority was granted; The remote control device according to claim 6 , wherein the first validity period is shorter than the second validity period.

8. The vehicle is a shared car, The remote control device according to claim 6, wherein the authority management means grants a third operation authority to a user terminal or user designated by a user of a user terminal having the second operation authority, the third operation authority enabling the user to perform remote operations a predetermined number of times.

9. The remote control device of claim 1 , wherein the user terminal in the vehicle includes a user terminal that travels with the vehicle.

10. A computer program for causing a computer to function as each of the means of the remote control device according to any one of claims 1 to 9.

11. A control method for a remote control device that remotely controls a vehicle, comprising: acquiring identification information associated with a user terminal located within the vehicle when the vehicle is powered off; an authority management step of granting an operation authority for remotely operating the vehicle to a user terminal associated with the acquired identification information; an operation step of remotely operating the vehicle in accordance with an operation instruction transmitted from the user terminal having the operation authority; A control method comprising:

Images