Control device and control method
By obtaining vehicle location information to set the scope of remote operation permission and restricting operations beyond that scope, the problem of residual remote operation permissions after vehicle resale is solved, improving vehicle safety and the convenience of public transportation.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- HONDA MOTOR CO LTD
- Filing Date
- 2023-08-17
- Publication Date
- 2026-06-23
Smart Images

Figure CN117774886B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to a control device and a control method. Background Technology
[0002] Previously, devices and systems were known for instructing a vehicle to perform a requested operation based on a remote operation request from a vehicle user. Patent Document 1 discloses a technique for determining whether remote operation is permitted or not based on the parking position, thereby preventing inappropriate remote operations from being performed according to the current state of the vehicle.
[0003] Existing technical documents
[0004] Patent documents
[0005] Patent Document 1: Japanese Patent No. 4403985 Summary of the Invention
[0006] The problem that the invention aims to solve
[0007] However, the technology described in Patent Document 1 has the following problem: for example, in cases where the vehicle is resold or a malicious user transfers ownership of the vehicle to another person, the remote operation rights remain with the original user.
[0008] Therefore, the object of this invention is to appropriately limit the authority for remote operation of vehicles. Furthermore, this invention specifically considers the needs of vulnerable groups, women, children, people with disabilities, and the elderly, and provides a safe, affordable, and easily accessible sustainable transportation system for all by improving traffic safety through the expansion of public transportation and other means.
[0009] Solution for solving the problem
[0010] According to the present invention, a control device is provided, characterized in that it comprises:
[0011] The first acquisition component acquires the vehicle's location information;
[0012] A setting component that sets the remote operation permission range of the vehicle based on the vehicle's movement information during a first predetermined period, which is derived from the location information.
[0013] The second acquisition component acquires information indicating that a specific operation is to be performed, the specific operation being used for remote operation input of the vehicle from a user terminal; and
[0014] The limiting component restricts remote operation input from the user terminal to the vehicle if the vehicle's location is outside the remote operation permission range when the information is obtained.
[0015] The mobility information includes the vehicle's location information and the status of visits to the location during the first predetermined period.
[0016] Furthermore, according to the present invention, a control method is provided, characterized in that it includes:
[0017] The steps to obtain vehicle location information;
[0018] The step of setting the remote operation permission range of the vehicle based on the vehicle's movement information during a first predetermined period, which is based on the location information;
[0019] The steps of obtaining information indicating that a specific operation needs to be performed, said specific operation being used as a remote operation input from a user terminal to the vehicle; and
[0020] If the vehicle's location is outside the remote operation permission range when the information is obtained, the steps for remote operation input of the vehicle from the user terminal are restricted.
[0021] The movement information includes the vehicle's location information and the visitation status of the location during the first predetermined period.
[0022] The effects of the invention
[0023] According to the present invention, the authority to remotely operate a vehicle can be appropriately restricted. Attached Figure Description
[0024] Figure 1 This is a diagram illustrating an example of the system architecture providing the remote operation service of the present invention.
[0025] Figure 2 This is a diagram illustrating an example of the structure of a control device.
[0026] Figure 3 This is a diagram showing an example of data stored in a database.
[0027] Figure 4 This is a diagram illustrating an example of the hardware structure of a vehicle's onboard device.
[0028] Figure 5 This is a diagram illustrating an example of the hardware structure of a user terminal.
[0029] Figure 6 This is a diagram showing an example of the initial GUI settings in a vehicle and a user terminal.
[0030] Figure 7 This is a diagram illustrating an example of a GUI in a user terminal when a remote operation service is being executed.
[0031] Figure 8 This is a flowchart illustrating an example of a remote operation permission range setting process according to one embodiment.
[0032] Figure 9 This is a flowchart illustrating an example of a remote operation input restriction processing according to one embodiment.
[0033] Figure 10 It is a diagram used to illustrate the positional status of a vehicle when remote operation inputs are restricted.
[0034] Explanation of reference numerals in the attached figures
[0035] 201: Processing Department; 202: Storage Department; 203: Communication Department. Detailed Implementation
[0036] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Furthermore, the following embodiments are not intended to limit the scope of the claims, and the present invention does not require a combination of all the features described in the embodiments. Alternatively, two or more features from the plurality of features described in the embodiments may be arbitrarily combined. Additionally, the same or identical structures will be given the same reference numerals, and repeated descriptions will be omitted.
[0037] An embodiment of the present invention relates to a control device that acquires the location information of a vehicle and sets a remote operation permission range for the vehicle based on the vehicle's movement information during a first predetermined period, which is derived from the location information. Then, the control device acquires information indicating a specific operation to be performed, which is used for remote operation input from a user terminal to the vehicle. If the vehicle's location information is outside the remote operation permission range when this information is acquired, remote operation input from the user terminal to the vehicle is restricted. Here, the movement information includes the vehicle's location information during the first predetermined period and the visitation status of that location. Specifically, this control device is used for remote operation of the vehicle. In this embodiment, the control device is described as a server communicating with the vehicle and the user terminal; however, this is just an example, and the structure is not limited if the same control can be performed by an in-vehicle device or similar functional component.
[0038] [system]
[0039] Figure 1 This is a system diagram illustrating an example of the structure of a remote operation service including a control device 100 for remotely operating a vehicle 110 according to this embodiment. The control device 100 according to this embodiment is a server as described above, capable of communicatively connecting to the vehicle 110 and the user terminal 120 via a network 130. Figure 1In the example, a vehicle 110 and a user terminal 120 are described, but their number is not specifically limited. Moreover, in the following, the vehicle's on-board equipment is also included and referred to as "vehicle".
[0040] In the remote operation service described in this embodiment, the control device 100 controls the vehicle 110 based on remote operation input in the user terminal 120. In this embodiment, there are corresponding user terminals associated with the vehicle 110, and the vehicle 110 is controlled according to the remote operation input sent to the corresponding user terminal.
[0041] As a remote operation input, it can be used for things like unlocking vehicle 110 or starting the vehicle (power supply), but is not particularly limited to these. For example, user terminal 120 can use, as described later... Figure 7 The GUI (Graphical User Interface) shown can handle remote operation inputs such as starting the air conditioner or facilitating vehicle location (e.g., turning on the headlights) to control in-vehicle equipment, and can also handle remote operation inputs related to other functions of the vehicle 110. In this embodiment, the user terminal 120 handles the user's remote operation inputs via dedicated application software that controls the remote operation service, and the control device 100 controls the vehicle 110 via the network 130. Hereinafter, when referred to as "application software," it refers to the application software that controls the aforementioned remote operation service.
[0042] This embodiment describes an example of the operation of the application software involved. The control device 100 of this embodiment associates the vehicle 110 with the user terminal 120. Here, when the vehicle 110 is started, identification information is displayed on a display unit inside the vehicle 110. When the user terminal 120 receives input of this identification information, the vehicle 110 and the user terminal 120 can be associated accordingly. For example, a PIN (Personal Identification Number) code, represented by a four-digit number, is used as the identification information. The vehicle 110 performs various actions such as unlocking the doors or starting the power according to remote operation input via the application software in the user terminal 120.
[0043] Furthermore, in this embodiment, the control device 100 controls the vehicle 110 based on the remote operation input in the user terminal 120. However, it is also possible for the user terminal 120 to communicate directly with the vehicle 110 and perform partial or complete control. For example, the user terminal 120 can connect to the vehicle 110 via short-range wireless communication to control the vehicle 110. For example, when the user terminal 120 is initially associated with the vehicle 110 by inputting identification information, the control device 100 controls the vehicle 110. Alternatively, when the user terminal 120 is associated with the vehicle 110 and remote operations such as unlocking the vehicle 110 are performed during a predetermined period (e.g., two months), communication can be used to remotely operate the vehicle 110 from the user terminal 120 without going through the control device 100. In this case, when the control device 100 restricts remote operation input from the user terminal 120 by performing the processing described later, the control device 100 restricts remote operation communication of short-range wireless communication from the user terminal 120 to the vehicle 110.
[0044] In this embodiment, vehicle 110 is described as a four-wheeled car, but it could also be a two-wheeled vehicle or other types of vehicle. User terminal 120 is a portable terminal such as a smartphone, which accepts user input, including remote operation input. The user terminal 120 in this embodiment can function as a digital key, unlocking the vehicle 110 by inputting information via application software.
[0045] Figure 2 This is a block diagram illustrating an example of the hardware structure of the control device 100 according to this embodiment. The control device 100 includes a processing unit 201, a storage unit 202, and a communication unit 203. The processing unit 201 is a processor, typically a CPU (Central Processing Unit), that executes programs stored in the storage unit 202. The storage unit 202 is a storage device such as RAM (Random Access Memory), ROM (Read Only Memory), or a hard disk. The communication unit 203 includes a wired or wireless communication interface capable of communicating with the vehicle 110 or the user terminal 120 via a communication network.
[0046] In the storage unit 202, in addition to the program executed by the storage processing unit 201, various types of data are also stored. Alternatively, the program can be installed on the control device 100 from a storage medium such as a CD-ROM (Compact Disc Read Only Memory). Figure 2In the example, databases (DB) 211 to 212 are shown as data stored in storage unit 202. Here, DB 211 is a database that stores information that associates vehicles with corresponding user terminals. DB 212 is a database that stores information representing user terminals and user terminals associated with those user terminals (e.g., registered as a household). Moreover, DB 211 and DB 212 can be separate databases or combined into one database. In this embodiment, the databases are described separately for convenience, but it is not limited to each existing as a separate database. Figure 3 This is a simple diagram illustrating these DBs.
[0047] DB 211 stores records for each user terminal 120, registering information including the user terminal, the vehicles associated with that user terminal, and the duration (validity period) of that association. Additionally, in this embodiment, DB 211 stores information for each user terminal indicating the scope of remote operation permissions set for that user terminal, and information on whether remote operation input is restricted by the control device 100 (restriction information). For example... Figure 3 As illustrated in example (a), the records stored in DB 211 include a user ID 301 corresponding to the user terminal, a vehicle ID 302 corresponding to the vehicle, a remote operation permission range 303, a restriction status 304, and a validity period 305. Here, the remote operation permission range 303 is represented by the coordinates of the center used to set the remote operation permission range. The validity period 305 is stored as the date when the association between the vehicle 110 and the user terminal 120 is to be terminated, but it could also be represented in other ways, such as storing information indicating the remaining period. Furthermore, in this embodiment, the remote operation permission range (as the remote operation permission range of the vehicle associated with the user terminal) is associated with each user terminal 120 and registered, but it could also be registered with the remote operation permission range associated with each vehicle 110.
[0048] DB 212 stores a record for each user terminal 120, and registers the user terminal and the user terminals associated with that user terminal. For example... Figure 3 As illustrated in example (b), the records stored in DB 212 include the user ID 301 corresponding to the user terminal and the associated user ID 306 corresponding to the associated user terminal. Here, multiple user terminals can be registered on a single user terminal, and the number is not limited. Furthermore, in Figure 3 In example (b), user terminals associated with each user terminal are registered and managed, and a group of associated user terminals is registered, thereby information related to the same association is stored in DB 212.
[0049] Alternatively, the control device 100 may assign a user ID to the user terminal 120 based on information obtained from the user terminal 120 via communication. However, it may also assign a user ID to an ID generated using information input by the user via application software, for example.
[0050] Figure 4 This is a block diagram illustrating an example of the hardware structure of the vehicle-mounted device of the vehicle 110 according to this embodiment. The vehicle 110 includes a processing unit 401, a storage unit 402, a communication unit 403, an input unit 404, a notification unit 405, and a GPS (Global Positioning System) sensor 406. The processing unit 401 is a processor, such as a CPU, that executes programs stored in the storage unit 402. The storage unit 402 is a storage device such as RAM or ROM. The programs stored in the storage unit 402 also include application software for enjoying the services of this embodiment.
[0051] The communication unit 403 is a communication device for communicating with external devices. For example, the communication unit 403 includes a wireless communication device capable of communicating with the control device 100 via a communication network. Alternatively, the communication unit 403 may include a wireless communication device capable of communicating with the user terminal 120 via short-range wireless communication. The input unit 404 is a device for receiving user input. The notification unit 405 is a notification device inside the vehicle 110, for example, displaying information to the user on a monitor. In this embodiment, the input unit 404 and the notification unit 405 may form a touch panel display, enabling touch input; alternatively, they may be operated using a mechanical switch or a rotary switch. The GPS sensor 406 is a sensor that acquires vehicle location information indicating the current location of the vehicle 110 and transmits this information to the control device 100 via the communication unit 403. As described above, the notification unit 405 in this embodiment can notify the user of identification information such as a PIN code when the vehicle 110 is started. The notification can be displayed on a screen or delivered by sound; the method is not particularly limited as long as it can be delivered to the user. The following describes how the notification unit 405 displays the notification on a screen.
[0052] Here, the notification unit 405 notifies the user of identification information when the vehicle 110 is unlocked. Alternatively, the notification may be made when the vehicle 110 is started. Initially (before the user terminal 120 registers with the vehicle 110), if the vehicle 110 is unlocked without using the user terminal 120 (e.g., with a physical key), the notification device inside the vehicle 110 notifies the user of identification information. This notification of identification information to the appropriate (unlockable) user allows for the appropriate initial association between the vehicle 110 and the user terminal 120. In this embodiment, the control device 100, upon confirming that the user terminal has input the identification information displayed by the notification unit 405, registers the user terminal as the corresponding user terminal for the vehicle 110 (e.g., using a physical key). Figure 3 (as shown in (a)). Refer to Figure 6 (a) is described later as an example of inputting identification information in user terminal 120.
[0053] Additionally, the communication unit 403 can detect user terminals inside the vehicle 110 via short-range wireless communication. Alternatively, the communication unit 403 can generate information (represented by a user ID) indicating the presence of user terminals 120 inside the vehicle 110 when the vehicle 110 is parked, and send it to the control device 100.
[0054] Figure 5 This is a block diagram illustrating an example of the hardware structure of the user terminal 120 according to this embodiment. The user terminal 120 has functional units capable of performing essentially the same functions as the vehicle 110, therefore repeated descriptions are omitted.
[0055] It should be noted that the location information of the vehicle 110 (vehicle location information) and the location information of the user terminal 120 (terminal location information) involved in this embodiment are location information relative to the map information obtained by the GPS sensor, and are acquired and updated at each predetermined interval. However, it is also possible that, for example, an external device sends the location information of the vehicle 110 or the user terminal 120 to the control device 100, and the control device 100 acquires the location information in a different order.
[0056] [Remote Operation Service]
[0057] The following describes in detail the processing performed by the control device 100 in the remote operation service according to this embodiment. The processing unit 201 of the control device 100 performs the following processing.
[0058] The control device 100 acquires the location information of the vehicle 110 and sets a remote operation permission range for the vehicle 110 based on the movement information of the vehicle 110 during a first predetermined period, which is based on the location information. The remote operation permission range in this embodiment is set in such a way that if the location of the vehicle 110 is outside the remote operation permission range when information indicating that a specific operation is to be performed on the user terminal 120 is acquired, remote operation input from the user terminal 120 is restricted, as will be described in detail later. The first predetermined period in this embodiment can be arbitrarily set, for example, a predetermined number of days (such as the last 30 days). Here, (including the second predetermined period described below) the predetermined number of days refers to exceeding and passing a predetermined time in a day (e.g., 0:00), that is, calculated based on the number of days spanned. However, it can also be calculated based on 24 hours. If used as an indicator of the number of days, the number of days can also be calculated using other methods.
[0059] The movement information of vehicle 110 includes the vehicle's visitation status to a certain location during a first predetermined period. Here, the visitation status includes the number of times vehicle 110 visits a certain location or the duration of its stop. Alternatively, the control device 100 according to this embodiment may, for example, set a range based on a location as a remote operation permitted range, wherein the stop period of vehicle 110 at that location spans the second predetermined period described below. Alternatively, for example, the control device 100 may set a range based on a location as a remote operation permitted range, wherein the number of times vehicle 110 visits (stops) at that location is a predetermined number or more. Hereinafter, an example of the remote operation permitted range setting process of the control device 100 will be described.
[0060] For example, the control device 100 may set a remote operation permitted range based on a location where the vehicle 110 remains stationary at that location for a second predetermined period within a first predetermined period. In this case, the remote operation permitted range may be set as a predetermined range (e.g., a radius of 100 meters) centered on the location where the vehicle remains stationary for the second predetermined period (taking into account deviations in location information, deviations in stationary position, etc.). The second predetermined period may be arbitrarily set as a predetermined number of days, such as 3 days. Alternatively, the vehicle may be stationary at the same location if it remains at the same coordinates obtained from the GPS sensor (with a margin that can be set), or it may be stationary at the same location if it remains at the same facility (e.g., a parking lot, etc.) on a map.
[0061] Alternatively, for example, the control device 100 may set a remote operation permitted range based on a location where the vehicle stops (visits) at that location a predetermined number of times or more within a first predetermined period. In this case, the remote operation permitted range can be set, for example, to a predetermined range centered on a location (e.g., a radius of 100 meters) where the vehicle is started and stopped at that location a predetermined number of times or more within the first predetermined period. Here, the predetermined number of times is, for example, 4 times, and can be arbitrarily set according to the conditions required by the user of the control device 100.
[0062] Alternatively, for example, the control device 100 may determine the area through which the vehicle has passed a predetermined number of times or more during a first predetermined period, and set a predetermined range based on that area as the remote operation permitted range. In this case, for example, the control device 100 may directly detect the area through which the predetermined number of times or more has been passed, or it may detect multiple locations through which the predetermined number of times or more has been passed, and determine the area through which the predetermined number of times or more has been passed based on them. Here, the remote operation permitted range may be, for example, a range centered on the area through which the predetermined number of times or more has been passed, plus a predetermined width (e.g., 20 meters), or it may be a group of areas each at a predetermined distance (e.g., a radius of 100 meters) from the locations through which the predetermined number of times or more has been passed. The predetermined number of times or more may be, for example, 4 times or more, and can be arbitrarily set according to the conditions required by the user of the control device 100.
[0063] Alternatively, the control device 100 may set a remote operation permitted range based on a location, wherein the number of times a specific operation for remote operation input of the vehicle is performed at the user terminal 120 at that location during a first predetermined period is a predetermined number of times or more. In this case, the remote operation permitted range may be set as a predetermined range centered on a location (e.g., a radius of 100 meters), wherein the number of times a specific operation is performed at that location during the first predetermined period is a predetermined number of times or more. The predetermined number of times is, for example, 4 times, and can be arbitrarily set according to the conditions required by the user of the control device 100. Moreover, in this embodiment, "specific operation" refers to operations for activating user input, including, for example, operations such as launching the application software of the user terminal 120, logging into the application software, and performing remote operation input on the application software.
[0064] Alternatively, the control device 100 in this embodiment can set the remote operation permission range based on the vehicle's location information and the user terminal's location information during a first predetermined period. Here, the control device 100 can set the remote operation permission range based on the vehicle's location information during the first predetermined period, as described above, as the actually used remote operation permission range, and it can also set a range that includes the remote operation permission range set based on the user terminal's location information as the actually used remote operation permission range. Here, the remote operation permission range set based on the user terminal's location information can, for example, be a range set based on a location where a specific operation is performed a predetermined number of times or more, as described above.
[0065] These processes are used to set the scope of remote operation permission, thereby defining the areas where the vehicle is used most frequently as the scope of remote operation permission. There is a risk of abuse if the vehicle is entered with operations for remote operation outside of this scope, so remote operation input can be restricted.
[0066] The remote operation permission range is updated when predetermined conditions are met. For example, if the control device 100 detects a new location during a first predetermined period, the range set based on the newly detected location is updated to a new remote operation permission range, wherein the period during which the vehicle 110 has been stopped at the newly detected location is longer than the period during which the vehicle 110 was stopped at the location used to set the remote operation permission range in the previous update. For example, if the control device 100 sets a range based on a location that has been continuously stopped for a second predetermined period during the first predetermined period as a remote operation permission range, and a new location is detected, the predetermined range centered on the newly detected location can be updated and set as the next remote operation permission range, wherein the vehicle 110 has been stopped at the newly detected location for a second predetermined period or longer. Additionally, for example, if the control device 100 sets a range based on a location where the vehicle stops a predetermined number of times or more during a first predetermined period as the remote operation permission range, and a new location is detected, the predetermined range centered on the newly detected location can be updated and set as the next remote operation permission range, wherein the vehicle 110 stops a predetermined number of times or more at the newly detected location during the first predetermined period.
[0067] Alternatively, the remote operation permission range can be updated daily, or it can be updated at predetermined intervals (e.g., monthly). Based on this processing, if the vehicle 110 remains continuously stopped at locations other than those with high stopping frequency, the remote operation permission range can be set to restrict remote operation input.
[0068] Alternatively, if the control device 100 updates the remote operation permission scope, it may restrict remote operation input until a predetermined operation is performed on the user terminal 120 associated with the vehicle. Alternatively, if the remote operation permission scope is updated, the application software on the user terminal 120 may be logged out, preventing remote operation input until a predetermined operation is performed.
[0069] Alternatively, the remote operation license scope update process may involve setting only the newly set remote operation license scope as the next remote operation license scope. Alternatively, the remote operation license scope update process may involve setting all newly set remote operation license scopes within the most recent first predetermined period from the current time as the new remote operation license scope.
[0070] Alternatively, during the update process, all user terminals 120 associated with the vehicle 110 can be delogged out. If a user terminal identical to the one that logged in during the previous update logs in, both the previous remote operation permission scope and the new remote operation permission scope are set as the updated remote operation permission scope. Alternatively, after delogging out, if a user terminal different from the one that logged in during the previous update logs in, only the new remote operation permission scope is set as the updated remote operation permission scope.
[0071] If the vehicle 110 is outside the remote operation permission range when it receives information indicating that a specific operation needs to be performed, the control device 100 restricts remote operation input from the user terminal 120. Here, the control device 100 receives information indicating that a specific operation needs to be performed when the user terminal 120 performs an operation to launch application software, log in to the application software, or perform a remote operation input operation on the application software.
[0072] For example, the control device 100 could invalidate remote operation input from the user terminal 120, thereby restricting remote operation input. That is, if a remote operation is input via application software in the user terminal 120, the control device 100 would not transmit the content of that remote operation to the vehicle 110. Alternatively, if the remote operation input from the user terminal 120 is transmitted to the vehicle 110 via short-range wireless communication, the control device 100 could prevent the application software of the user terminal 120 from transmitting the input to the vehicle 110, or even if the vehicle 110 receives the instruction, it would not execute it.
[0073] Alternatively, for example, the control device 100 may stop remote operation input from the user terminal 120, thereby restricting remote operation input. That is, the control device 100 may also stop processing for remote operation input, such as login or startup of application software in the user terminal.
[0074] Furthermore, if remote operation input is made while the vehicle 110 is in motion, executing such input may pose a danger. In particular, remote operation input from a user terminal 120 not present in the vehicle 110 is highly likely to be inconsistent with the operating conditions of the vehicle 110 while it is in motion. Based on that viewpoint, if remote operation input from a user terminal 120 not present in the vehicle 110 is input while the vehicle 110 is in motion, the control device 100 may also restrict such remote operation input.
[0075] Furthermore, even when remote operation input is made while the vehicle 110 is in motion, the remote operation input made by the user terminal 120 stored in the vehicle 110 may be consistent with the operating status of the vehicle 110 while it is in motion. Therefore, if a remote operation input from the user terminal 120 stored in the vehicle is input while the vehicle 110 is in motion, the control device 100 may decide whether to restrict the remote operation input based on its type. For example, if the remote operation input input while in motion is related to a function that affects the driving status of the vehicle 110, the control device 100 may restrict the remote operation input. Functions affecting the driving status include, for example, unlocking the vehicle 110, turning the defroster on or off, or opening and closing the windows. On the other hand, if the remote operation input input while in motion is related to a function that does not affect the driving status, the control device 100 may not restrict the remote operation input in this case. Functions that do not affect the driving status include, for example, turning the air conditioner on or off, playing music or video, or turning the seat heaters on or off—functions that do not directly affect driving. These functions are just one example; it's also possible that, depending on the application software designer's judgment, each function may or may not affect the driving status. For example, adjusting the air conditioning could be set as a function that affects the driving status. By restricting remote operation inputs related to functions affecting the driving status of vehicle 110 while the vehicle is in motion, it's possible to prevent interference with driving and to prevent potential hazards. Furthermore, by restricting such remote operation inputs while driving, operations can be rejected without logging out of the user terminal 120, eliminating the hassle of logging in again and improving convenience.
[0076] Figure 6 as well as Figure 7This is a diagram showing an example of the GUI displayed in the vehicle 110 and user terminal 120 according to this embodiment. Figure 6 This example shows a GUI initially configured to input identification information notified by the notification unit 405 of vehicle 110 into the user terminal 120. Figure 6 (a) illustrates an example of a screen 610 displaying a PIN code on the notification unit 405, i.e., the display, of vehicle 110. Figure 6 (b) illustrates an example of screen 600 for entering a PIN code in user terminal 120.
[0077] Screen 600 is the screen displayed when the vehicle 110 is unlocked, showing PIN code 601 and message 602. When the user terminal 120 confirms the PIN code input, the identification information notification ends, and the display returns to normal. Here, the notification unit 405 is the display for the in-vehicle equipment; therefore, when screen 600 ends, it switches to a general display screen such as a car navigation screen or a music playback management screen.
[0078] Screen 610 is the PIN code input screen displayed when the application software starts (especially on first launch), showing a PIN code input box 611 and a PIN code sending button 612. After entering the PIN code, the vehicle 110 and user terminal 120 are associated, as follows: Figure 3 The information shown in (a) is recorded in the database.
[0079] Figure 7 This is a diagram illustrating an example of a GUI on the user terminal 120 for remote operation input after the association between the vehicle 110 and the user terminal 120 is completed. Figure 7 In the display screen 700, buttons corresponding to remote operations are shown, allowing the user to input inputs to send remote operation instructions to the vehicle 110 via the control device 100. The display screen 700 also shows an unlock button 701 for unlocking the vehicle 110, a start button 702 for starting the vehicle, an air conditioning button 703 for starting the air conditioning unit, and a search button 704 for easily locating the vehicle.
[0080] The user presses the unlock button 701, thereby unlocking the vehicle 110. Alternatively, while the vehicle 110 is unlocked, the unlock button 701 can be replaced by a lock button (not shown) to lock the vehicle 110. Additionally, the user presses the start button 702, thereby turning on the vehicle's power (e.g., turning on the ignition). This turns on the vehicle's power, allowing the user to drive the vehicle 110.
[0081] When the user presses the air conditioning button 703, the air conditioning system of vehicle 110 is activated. Alternatively, upon pressing the air conditioning button 703, the user terminal 120 can move screen 700 to a guide screen (not shown) for controlling the air conditioning system, such as temperature setting or fan speed adjustment. Furthermore, pressing the search button 704 allows the user to easily locate vehicle 110 by controlling the status changes of vehicle 110. Here, pressing the search button 704 causes the vehicle 110's lights to flash for a predetermined period (e.g., 15 seconds), but the status change of vehicle 110 can also be achieved by other means, such as outputting sound from the vehicle 110's horn.
[0082] Alternatively, from the perspective of improving safety, when a predetermined button such as the start button 702 is pressed, an authentication code is displayed on the vehicle's notification unit 405, and the authentication code is entered into the user terminal, thereby sending the instruction corresponding to the pressed button to the vehicle 110.
[0083] Alternatively, screen 700 can display information other than the buttons used for the aforementioned remote operations. For example, user terminal 120 can display information indicating the remaining fuel and remaining driving range of vehicle 110, whether vehicle 110 is unlocked, or the interior temperature (or exterior temperature) of vehicle 110. Furthermore, user terminal 120 does not need to display all the remote operation buttons shown on screen 700; it can only remotely operate the functions desired by the application software designer. Also, instead of displaying all buttons on a single screen as shown on screen 700, objects including the buttons can be distributed across multiple screens.
[0084] Figure 10 This diagram illustrates the control processing corresponding to the remote operation permission range and the vehicle's location regarding the remote operation service involved in this embodiment. Figure 10 (a) and Figure 10 In (b), the control device 100 sets the remote operation permission range 1001 in the map 1000 based on the vehicle's movement information.
[0085] exist Figure 10 In (a), a stop position 1002 is detected based on the vehicle's location information, and the stop position 1002 exists within the remote operation permission range 1001. Here, even if the vehicle has been at the stop position 1002 for a first predetermined period, since the stop position is within the remote operation permission range 1001, no restriction is imposed on remote operation input.
[0086] On the other hand, Figure 10In (b), a stopping position 1003 is detected based on the vehicle's location information. The stopping position 1003 is outside the remote operation permission range 1001. If the vehicle remains at the stopping position 1003 for a first predetermined period, the vehicle may be misused such as being resold. Therefore, the control device 100 according to this embodiment restricts the remote operation input.
[0087] The following is for reference Figure 8 as well as Figure 9 This describes an example of how the control device 100 restricts remote operation input for the user terminal of the processing object in a remote operation service involved in this embodiment. Figure 8 This is a flowchart illustrating an example of the process by which the control device 100 sets a remote operation permission range. In S801, the control device 100 sets vehicle 110 as the processing object to which the remote operation permission range is to be set. Here, for example, the control device 100 may select vehicle 110 that meets the predetermined conditions for updating the remote operation permission range as the processing object, or it may randomly select one of the vehicles registered in DB 211 as the processing object. The method of setting the processing object is not particularly limited.
[0088] In S802, the control device 100 acquires the movement information of the vehicle 110, which is the object of processing, during a first predetermined period. Here, as movement information, the historical movement history of the vehicle 110 during the first predetermined period can also be stored in DB 211, as can information indicating the location where the vehicle 110 remains stationary during a second predetermined period. In S803, the control device 100 sets (updates) the remote operation permission range based on the information acquired in S801 and ends the processing. The update process is performed as described above, and its explanation is omitted here. Alternatively, the control device 100 may additionally acquire the location information of the user terminal 120 in S802, and also set the remote operation permission range in S803 based on this location information.
[0089] Figure 9 This is a flowchart illustrating an example of the setting process for the remote operation permission range, performed by the processing unit 401 of the control device 100, according to this embodiment. Figure 9 When the relevant processing is completed, if unrestricted remote operation input is entered, an instruction is sent to vehicle 110 to execute the remote operation.
[0090] In S901, the control device 100 sets a user terminal 120 as the processing target to determine whether remote operation input is restricted. Here, the control device 100 sets the user terminal 120 that sends information indicating a specific operation to the control device 100 as the processing target. However, it is also possible to set a user terminal that exists inside the vehicle 110 when the vehicle 110 is stopped as the processing target, for example. The method of setting the user terminal as the processing target in S901 is not particularly limited. For example, the control device 100 may randomly set one of the user terminals registered in DB 211 as the processing target.
[0091] In S902, the control device 100, referring to DB 211, obtains information indicating the vehicle 110 associated with the user terminal 120 being processed. In S903, the control device 100 obtains the remote operation permission range for the vehicle 110 for which information was obtained in S902. Here, the remote operation permission range is... Figure 8 The process shown is set and stored in DB 211, so the control device 100 refers to DB 211 to obtain the scope of remote operation permission.
[0092] In S904, the control device 100 determines whether the vehicle is stopped. Here, the control device 100 obtains information from the vehicle 110 regarding whether the vehicle's power is on, thereby determining whether the vehicle is stopped. If the vehicle is stopped, the process proceeds to S905; otherwise, the process proceeds to S908.
[0093] In S905, the control device 100 obtains the current position of the vehicle 110. Here, the control device 100 can set the position of the vehicle 110 at the last point when the power was cut off as the current stopping position, or it can obtain the current position information from the vehicle 110. Alternatively, the control device 100 can associate the position information with the vehicle 110 in DB 211 and store it, referring to this information in S906.
[0094] In S906, the control device 100 determines whether to restrict remote operation input from the user terminal 120 based on the remote operation permission range set in S903 and the current location information of the vehicle 110 obtained in S905. Here, if the vehicle's location is within the remote operation permission range, the control device 100 does not restrict the remote operation input; otherwise, it restricts the remote operation input. If the remote operation input is not restricted, the process ends; if the remote operation input is restricted, the process proceeds to S907.
[0095] In S907, the control device 100 restricts remote operation input to the user terminal 120, which is the target of the processing. Here, the control device 100 invalidates remote operation input from the user terminal 120 or stops remote operation input from the user terminal, thereby restricting remote operation input. In this embodiment, remote operation input may be restricted only to the user terminal 120, which is the target of the processing, or all user terminals associated with the vehicle 110 corresponding to the user terminal 120, which is the target of the processing, may have their remote operation input restricted. When S907 ends, the processing concludes.
[0096] In S908, the control device 100 acquires information indicating whether the user terminal 120, the object to be processed, exists within the vehicle 110. Here, if the vehicle 110 and the user terminal 120 can communicate via short-range wireless communication, the user terminal 120 is assumed to exist within the vehicle 110; otherwise, it is assumed not to exist within the vehicle 110. In S909, the control device 100 determines whether the user terminal 120 exists within the vehicle 110 based on the information acquired in S908. If the user terminal 120 exists within the vehicle 110, the process proceeds to S910; otherwise, the process proceeds to S907.
[0097] In S910, the control device 100 determines whether the remote operation input from the user terminal 120 is a remote operation input related to a function affecting the driving state of the vehicle 110. If it is a remote operation input related to a function affecting the driving state, the process proceeds to S907; otherwise, the process ends.
[0098] Based on this structure, a remote operation permission range can be set based on the location information of vehicle 110, and it can be determined whether to restrict remote operation input from user terminal 120 based on the stopping position of vehicle 110 and the remote operation permission range. In particular, if the stopping position is outside the remote operation permission range and specific input for remote operation of the vehicle is made, remote operation input from user terminal 120 to vehicle 110 can be restricted. Therefore, it is possible to prevent malicious users from reserving remote operation rights for the original user, for example, even if vehicle 110 has been resold.
[0099] Furthermore, as shown in database 212, when user terminals are interconnected, restricting remote operation input for all user terminals in a group formed by interconnecting these user terminals is more efficient than restricting remote operation input for one of them. Therefore, when the control device 100 determines that remote operation input for a particular user terminal needs to be restricted, it can further restrict remote operation input from user terminals connected to that user terminal. By performing this processing, even if remote operation input is restricted due to a user potentially reselling their property, it is possible to restrict remote operation input for user terminals registered as close users, such as family members of that user. Therefore, remote operation restriction management can be performed more efficiently.
[0100] Furthermore, while this embodiment sets the permitted parking area based on the movement information of vehicle 110, scenarios such as stopping vehicle 110 at locations like airports where it might be parked for several days even for normal purposes are also considered. Based on that viewpoint, the control device 100 could also set the permitted parking area by removing a predetermined area based on map information. This predetermined area based on map information could be, for example, an area on a map where the user intends to park their vehicle for an extended period, such as an airport or port, and could be arbitrarily set by the application software designer.
[0101] Furthermore, consider the following scenario: even if the vehicle is parked outside the remote operation permission range, it is only a temporary stop and not a resale. Based on that viewpoint, the control device 100 could obtain the location of a user terminal located inside the vehicle 110 after alighting, and if that location remains within a predetermined range of the vehicle 110, the remote operation input of that user terminal could not be restricted.
[0102] Furthermore, considering a scenario where a user possesses a key that allows them to unlock the vehicle 110 without using the user terminal 120, the user holding the user terminal 120 is considered a legitimate user of the vehicle 110. Therefore, the control device 100 may determine whether the user terminal 120 can communicate with the aforementioned key (e.g., via short-range wireless communication), and if communication is possible, determine that remote operation input is not restricted.
[0103] Furthermore, in this embodiment, remote operation input is restricted when the vehicle's location is outside the remote operation permission range. However, cases where the vehicle's location information at that time cannot be obtained due to communication problems are also considered. In such cases, the control device 100 may use the location information of a user terminal located within the vehicle and acquired at the same time interval, instead of using the vehicle 110's location. Alternatively, if the vehicle 110 is connected to external facilities or devices such as a charging station or Wi-Fi, location information acquired based on these external facilities or devices may be used as the vehicle 110's location information.
[0104] Furthermore, in this embodiment, the decision on whether to restrict remote operation input is based on the vehicle's location information when a specific operation is performed, i.e., when remote operation is performed. Therefore, for example, if vehicle 110, with the ignition power off, is moved outside the remote operation permitted range by a tow truck or the like, and then vehicle 110 returns to the remote operation permitted range, and then remote operation input is performed, no restriction on remote operation input is imposed.
[0105] Additionally, consider the scenario where vehicle 110 is used as a shared vehicle, where users other than the primary owner cannot remotely operate the vehicle by unlocking it with a physical key and stopping it outside the permitted stopping area for the primary owner's normal use. Even in this case, if the user finishes using the vehicle and returns it to the permitted stopping area, and the primary owner then performs remote operation input, no restriction is imposed on remote operation input.
[0106] [Summary of Implementation Methods]
[0107] The above embodiments disclose at least the following control devices, control methods, and procedures.
[0108] 1. The control device (e.g., 100) of the above embodiment includes:
[0109] The first acquisition component (e.g., 203) acquires the vehicle's location information;
[0110] A setting component (e.g., 201) sets the remote operation permission range of the vehicle based on the vehicle's movement information during a first predetermined period, which is based on the location information.
[0111] A second acquisition component (e.g., 203) acquires information indicating a specific operation to be performed, the specific operation being used for remote operation input of the vehicle from a user terminal; and
[0112] A limiting component (e.g., 201) restricts remote operation input to the vehicle from the user terminal when the vehicle's location is outside the remote operation permission range at the time the information is acquired.
[0113] The movement information includes the vehicle's location information and the visitation status of the location during the first predetermined period.
[0114] According to this implementation, the permissions for remote operation of the vehicle can be appropriately restricted.
[0115] 2. In the control device of the above-described embodiment,
[0116] It also includes a third acquisition component, which acquires the location information of the user terminal.
[0117] The setting component sets the remote operation permission range based on the location information of the vehicle and the location information of the user terminal during the first predetermined period.
[0118] According to this implementation, the scope of remote operation permission can be set based on both the location of the vehicle and the location of the user terminal.
[0119] 3. The control device in the above embodiments further includes:
[0120] The notification component, when the vehicle is in the unlocked state, causes the notification unit inside the vehicle to notify the identification information; and
[0121] The registration component, upon confirming that the identification information has been entered into the user terminal, registers the user terminal as the corresponding user terminal associated with the vehicle.
[0122] According to this implementation, in the case of initial setup, user terminals corresponding to the vehicle are registered for users who can unlock the vehicle without using remote operation.
[0123] 4. In the control device of the above-described embodiment,
[0124] The setting component sets the remote operation permission range for each user terminal for the vehicle corresponding to that user terminal.
[0125] According to this implementation, based on the remote operation permission range set for each user terminal, it is possible to determine whether to restrict the remote operation input of the user terminal.
[0126] 5. In the control device of the above-described embodiment,
[0127] The setting component sets the remote operation permission range to a predetermined range centered on a location where the vehicle remains stationary for a second predetermined period during the first predetermined period.
[0128] According to this embodiment, remote operation input can be restricted when the vehicle's parking position is continuously outside the normally envisioned range.
[0129] 6. In the control device of the above embodiment,
[0130] The second predetermined period is a predetermined number of days, calculated by the number of days spanned.
[0131] According to this implementation, the vehicle's downtime can be evaluated based on the number of days that cross over.
[0132] 7. In the control device of the above embodiment,
[0133] The setting component sets the remote operation permission range to a predetermined range centered on a location where the number of times the operation stops at that location during the first predetermined period is more than a predetermined number.
[0134] According to this embodiment, the stopping period of a vehicle can be evaluated based on the number of times the vehicle stops.
[0135] 8. In the control device of the above embodiment,
[0136] The setting component sets the remote operation permission range to a predetermined range centered on a location where the number of times the operation stops at that location during the first predetermined period is more than a predetermined number.
[0137] According to this embodiment, the stopping period of a vehicle can be evaluated based on the number of times the vehicle stops.
[0138] 9. In the control device of the above embodiment,
[0139] The first setting component sets the remote operation permission range to a predetermined range based on the area where the number of times the area is traversed during the first predetermined period is more than a predetermined number.
[0140] According to this implementation, areas frequently used by users can be designated as remote operation permitted areas.
[0141] 10. In the control device of the above-described embodiment,
[0142] The specific operation includes launching an application software for remotely operating the vehicle or inputting remote operations on the vehicle within the application software.
[0143] According to this embodiment, it is possible to determine whether to restrict remote operation input based on the operation used to input application software in the user terminal.
[0144] 11. In the control device of the above-described embodiment,
[0145] The first setting component sets the remote operation permission range by removing a predetermined range based on map information.
[0146] According to this implementation, it is envisioned that when a vehicle is parked in a predetermined area such as an airport where it would be parked for a long time even if it is normally used, it is possible to avoid unnecessarily restricting remote operation input.
[0147] 12. In the control device of the above embodiment,
[0148] It also includes a determination component that determines whether the user terminal can communicate with the key that can unlock the vehicle.
[0149] If the determining component determines that the user terminal can communicate with the key that can unlock the vehicle, the limiting component does not restrict the remote operation input.
[0150] According to this implementation, if it is determined that the user terminal is a terminal held by a legitimate user of the vehicle, it can be determined that remote operation input is not restricted.
[0151] 13. In the control device of the above-described embodiment,
[0152] It also includes a fourth acquisition component, which acquires information indicating whether the user terminal is present in the vehicle.
[0153] If, while the vehicle is in motion, a remote operation input is received from a user terminal not present in the vehicle, the limiting component restricts the remote operation input.
[0154] According to this embodiment, it is possible to limit remote operation inputs from outside the vehicle while the vehicle is in motion, thereby ensuring safety.
[0155] 14. In the control device of the above embodiment,
[0156] It also includes a fourth acquisition component, which acquires information indicating whether the user terminal is present in the vehicle.
[0157] When the vehicle is in motion and a remote operation input is received from a user terminal located within the vehicle, the limiting component determines whether to restrict the remote operation input based on the type of the remote operation input.
[0158] According to this implementation, for remote operation inputs made from inside the vehicle while the vehicle is in motion, it is possible to determine whether to restrict the input based on whether it affects driving.
[0159] 15. In the control device of the above-described embodiment,
[0160] When the remote operation input is an input related to a function affecting the driving state of the vehicle, the limiting component restricts the remote operation input.
[0161] According to this embodiment, it is possible to limit the inputs for remote operations that affect the driving status of the vehicle, thereby improving safety.
[0162] 16. In the control device of the above-described embodiment,
[0163] If the first acquisition component cannot obtain the location information of the vehicle from the vehicle, it acquires the location information of the user terminal that performed the specific operation as the location information of the vehicle.
[0164] According to this implementation, user location information can be used instead when the vehicle's location cannot be obtained.
[0165] 17. The control method of the above-described embodiments includes:
[0166] The steps to obtain vehicle location information;
[0167] The step of setting the remote operation permission range of the vehicle based on the vehicle's movement information during a first predetermined period, which is based on the location information;
[0168] The steps of obtaining information indicating that a specific operation is to be performed, said specific operation being used as remote operation input for the vehicle from a user terminal; and
[0169] If the vehicle's location is outside the remote operation permission range when the information is obtained, the steps for remote operation input of the vehicle from the user terminal are restricted.
[0170] The movement information includes the vehicle's location information and the visitation status of the location during the first predetermined period.
[0171] According to this implementation, the permissions for remote operation of the vehicle can be appropriately restricted.
[0172] 18. The program of the above embodiments enables the computer to function as a component of the control device according to any one of 1 to 16 above.
[0173] According to this implementation, the permissions for remote operation of the vehicle can be appropriately restricted.
[0174] The above describes the implementation of the invention, but the invention is not limited to the above implementation. Various modifications and alterations can be made within the scope of the invention's intent.
Claims
1. A control device, characterized in that, have: The first acquisition component acquires the vehicle's location information; A setting component that sets the remote operation permission range of the vehicle based on the vehicle's movement information during a first predetermined period, which is derived from the location information. The second acquisition component acquires information indicating that a specific operation is to be performed, the specific operation being used for remote operation input of the vehicle from a user terminal; as well as The limiting component restricts remote operation input to the vehicle from the user terminal if the vehicle's location is outside the remote operation permission range when the information is obtained. The movement information includes the vehicle's location information and the visitation status of the location during the first predetermined period.
2. The control device according to claim 1, characterized in that, It also includes a third acquisition component, which acquires the location information of the user terminal. The setting component sets the remote operation permission range based on the location information of the vehicle and the location information of the user terminal during the first predetermined period.
3. The control device according to claim 1, characterized in that, It also has: The notification component, when the vehicle is in the unlocked state, causes the notification unit inside the vehicle to notify the identification information; as well as The registration component, upon confirming that the identification information has been entered into the user terminal, registers the user terminal as the corresponding user terminal associated with the vehicle.
4. The control device according to claim 1, characterized in that, The setting component sets the remote operation permission range for the vehicle corresponding to each user terminal.
5. The control device according to claim 1, characterized in that, The setting component sets the remote operation permission range to a predetermined range centered on a location where the vehicle remains stationary for a second predetermined period within the first predetermined period.
6. The control device according to claim 5, characterized in that, The second predetermined period is a predetermined number of days, calculated by the number of days spanned.
7. The control device according to claim 1, characterized in that, The setting component sets the remote operation permission range to a predetermined range centered on a location where the number of times the operation stops at that location during the first predetermined period is more than a predetermined number.
8. The control device according to claim 1, characterized in that, The setting component sets the remote operation permission range to a predetermined range based on a region that is a region through which a predetermined number of times are passed during the first predetermined period.
9. The control device according to claim 1, characterized in that, The setting component sets the remote operation permission range to a predetermined range based on a region where the number of times the specific operation from the user terminal is performed by the user terminal during a first predetermined period is more than a predetermined number.
10. The control device according to claim 1, characterized in that, The specific operation includes launching an application software for remotely inputting operations to the vehicle, or inputting remote operations to the vehicle within the application software.
11. The control device according to claim 1, characterized in that, The setting component sets the remote operation permission range by removing a predetermined range based on map information.
12. The control device according to claim 1, characterized in that, It also includes a determination component that determines whether the user terminal can communicate with the key that can unlock the vehicle. If the determining component determines that the user terminal can communicate with the key that can unlock the vehicle, the limiting component does not restrict the remote operation input.
13. The control device according to claim 1, characterized in that, It also includes a fourth acquisition component, which acquires information indicating whether the user terminal is present in the vehicle. If, while the vehicle is in motion, a remote operation input is received from a user terminal not present in the vehicle, the limiting component restricts the remote operation input.
14. The control device according to claim 1, characterized in that, It also includes a fourth acquisition component, which acquires information indicating whether the user terminal is present in the vehicle. When the vehicle is in motion and a remote operation input is received from a user terminal located within the vehicle, the limiting component determines whether to restrict the remote operation input based on the type of the remote operation input.
15. The control device according to claim 14, characterized in that, When the remote operation input is an input related to a function affecting the driving state of the vehicle, the limiting component restricts the remote operation input.
16. The control device according to claim 1, characterized in that, If the first acquisition component cannot obtain the location information of the vehicle from the vehicle, it acquires the location information of the user terminal that performed the specific operation as the location information of the vehicle.
17. A control method, characterized in that, include: The steps to obtain vehicle location information; The step of setting the remote operation permission range of the vehicle based on the vehicle's movement information during a first predetermined period, which is based on the location information; The step of obtaining information indicating that a specific operation is to be performed, the specific operation being used as a remote operation input for the vehicle from a user terminal; as well as If the vehicle's location is outside the remote operation permission range when the information is obtained, the steps for remote operation input of the vehicle from the user terminal are restricted. The movement information includes the vehicle's location information and the visitation status of the location during the first predetermined period.
18. A non-volatile computer-readable storage medium for storing a program that, when executed, causes a computer to perform the control method according to claim 17.