Remote support system and management device

Abstract

To provide a technique that allows a configuration related to communication between a vehicle and a remote support terminal to be flexibly changed according to the scale of a remote support system.SOLUTION: A remote support system for remote support to a mobile body includes a management device and a relay device different from the management device. The management device receives a support request transmitted from the mobile body, and selects support resources necessary for remote support. The relay device relays data communication between the mobile body and the remote support terminal performed during remote support.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a remote support system for a mobile object and a management device used for remote support for a mobile object. [Background technology]

[0002] Patent Document 1 discloses a method for remotely controlling a vehicle. The method disclosed in Patent Document 1 performs remote control via a dispatcher that receives assistance requests from the vehicle and a control center that allocates resources required for remote control. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-205037 Summary of the Invention [Problem to be solved by the invention]

[0004] Consider the communication between a vehicle receiving remote support and a remote support terminal in a remote support system. Patent Document 1 does not mention a method for communication between the vehicle and the remote control terminal while remote control is being performed.

[0005] An object of the present disclosure is to provide a technology that allows the configuration relating to communication between a vehicle and a remote support terminal to be flexibly changed according to the scale of the remote support system. [Means for solving the problem]

[0006] The first aspect relates to a remote support system for remotely supporting a mobile object. The remote support system A management device; One or more relay devices that are different from the management device Equipped with. The management device receiving a support request transmitted from the mobile device; Identify the support resources needed for remote support. The one or more relay devices relay data communication between the mobile object and the remote support terminal during the remote support.

[0007] The second aspect relates to a management device used for remote support of a mobile object. The management device receiving a support request transmitted from the mobile device; Select the support resources required for remote support, Unlike the management device, one or more relay devices that relay data communication between the mobile body and the remote support terminal are selected from a plurality of relay device candidates. [Effects of the Invention]

[0008] According to a first aspect, a remote support system comprises a management device and a relay device, each with different functions. That is, the management device transmits and receives support requests and selects support resources, while the relay device relays communications between mobile units and remote support terminals. This feature makes it possible to select either the management device or the relay device depending on the required functions when the scale of the remote support system changes. This can be said to improve the scalability of the remote support system in response to changes in scale.

[0009] According to the second aspect, the management device selects one or more relay devices from among a plurality of relay device candidates. As a result, even if some of the plurality of relay device candidates are not functioning due to a malfunction or maintenance, a relay device can be selected from the relay device candidates that are functioning normally. Therefore, the functionality of the remote support system 1 as a whole is maintained, and as a result, the functional continuity of the remote support system is improved. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an overview of remote support for a vehicle. [Figure 2] FIG. 10 is a schematic diagram illustrating an example of a data recording process. [Figure 3] FIG. 10 is a schematic diagram illustrating an example of relay device selection. [Figure 4] FIG. 10 is a schematic diagram for explaining the priority of relay device selection. [Figure 5] FIG. 1 is a block diagram showing an example of the configuration of a vehicle. [Figure 6] FIG. 2 is a block diagram illustrating an example of the configuration of a management device. [Figure 7] FIG. 2 is a block diagram illustrating an example of the configuration of a relay device. [Figure 8] FIG. 2 is a block diagram illustrating an example of the configuration of a remote support terminal. [Figure 9] FIG. 1 illustrates a large-scale implementation of a remote support system. DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of the present disclosure will be described with reference to the accompanying drawings. In this embodiment, the description will be based on an example in which the "moving body" is a "vehicle." The technology of the present disclosure can be applied even if the "vehicle" described below is replaced (or generalized) with "moving body." In addition to vehicles, moving bodies include drones, robots, ships, etc.

[0012] 1. Remote support system FIG. 1 is a diagram showing an overview of remote support for a vehicle 100. The remote support is performed by a remote support system 1. The remote support system 1 includes a vehicle 100, a remote support terminal 200, a management device 300, and one or more relay devices 400. The vehicle 100, the remote support terminal 200, the management device 300, and the one or more relay devices 400 can communicate with each other via a communication network. Hereinafter, the one or more relay devices 400 will be simply referred to as a "relay device 400."

[0013] Vehicle 100 is a target for remote support. Vehicle 100 may be an autonomous vehicle. Here, autonomous driving is assumed to be one that does not necessarily require the driver to concentrate 100% on driving (so-called autonomous driving at level 3 or higher). Vehicle 100 may also be an autonomous vehicle at level 4 or higher that does not require a driver. Vehicle 100 is equipped with various sensors including a camera. For example, the camera photographs the situation around vehicle 100 and acquires an image showing the situation around vehicle 100. Vehicle 100 performs autonomous driving using various sensors.

[0014] Remote support refers to general intervention in the vehicle 100 performed via communication by a remote supporter S located away from the vehicle 100. Remote support is a concept that includes remote monitoring, remote assistance, and remote driving. Remote monitoring includes monitoring the environment around the vehicle 100, the vehicle status of the vehicle 100, and the status of the occupants of the vehicle 100, etc. Remote assistance refers to the remote supporter S providing instructions regarding the driving of the vehicle 100 upon a request from the vehicle 100. For example, if the vehicle 100, which is an autonomous vehicle, is unable to determine the appropriate timing for starting, changing lanes, turning right or left, etc., it sends an assistance request to the remote support system 1. The remote supporter S, upon receiving the assistance request, instructs the autonomous vehicle on the appropriate timing. Remote driving refers to the remote supporter S controlling the driving of the vehicle 100 based on operations input into the remote support terminal 200.

[0015] The remote support terminal 200 is a terminal device used by the remote supporter S when providing remote support to the vehicle 100. The remote support terminal 200 can also be called a remote support HMI (Human Machine Interface).

[0016] The management device 300 manages remote support. The management device 300 can communicate with the vehicle 100, the remote support terminal 200, and the relay device 400 via a communication network. Typically, the management device 300 is a management server on the cloud. The management server may be configured with multiple servers that perform distributed processing.

[0017] The relay device 400 relays data communication between the vehicle 100 and the remote support terminal 200 during remote support for the vehicle 100.

[0018] When the vehicle 100 is an autonomous driving vehicle, the vehicle 100 executes various vehicle processes. Typical vehicle processes during autonomous driving include the following.

[0019] (1) Recognition process: The vehicle 100 uses a recognition sensor to recognize the situation around the vehicle 100. For example, the vehicle 100 uses a camera to recognize the signal display of a traffic light (e.g., green light, yellow light, red light, right turn signal, etc.). (2) Action Determination Process: Based on the result of the recognition process, the vehicle 100 determines whether or not to perform an action. Examples of actions include starting, stopping, turning right, turning left, and changing lanes. (3) Timing determination process: The vehicle 100 determines the timing to perform the above-mentioned action.

[0020] Typically, situations where remote support by the remote supporter S is necessary are situations where autonomous driving is difficult. For example, remote support may be necessary when the camera of the vehicle 100 cannot recognize the color of a traffic light at an intersection or when the vehicle 100 cannot determine the timing to change lanes.

[0021] When the vehicle 100 determines that remote support is necessary, the vehicle 100 requests remote support. Specifically, the vehicle 100 transmits a support request REQ to the management device 300.

[0022] It should be noted that the vehicle 100 according to this embodiment is not limited to an autonomous vehicle. The remote support system 1 is also applicable to cases where a driver or passenger who is (manually) driving the vehicle 100 needs remote support. In this specification, the expression "the vehicle 100 requests remote support" also includes cases where a driver or passenger on board the vehicle 100 requests remote support. A driver or passenger on board the vehicle 100 who requests remote support will be referred to as a "support requester 10" hereinafter.

[0023] After receiving the support request REQ sent from the vehicle 100, the management device 300 selects support resources necessary for remote support of the vehicle 100. The support resources refer to the equipment and personnel necessary for remote support, and include the remote supporter S, the remote support terminal 200, and the relay device 400. The process of selecting support resources to be used for remote support is hereinafter referred to as "resource selection."

[0024] The management device 300 transmits a notification including the support request REQ and information about the vehicle 100 to the remote support terminal 200. The remote support terminal 200 presents the notification to the remote supporter S. The remote supporter S recognizes that he or she has been assigned to the vehicle 100, and starts remote support for the vehicle 100.

[0025] During remote support, the vehicle 100 and the remote support terminal 200 communicate various data via the relay device 400. During remote support, the vehicle 100 and the remote support terminal 200 may communicate various data via the relay device 400 without going through the management device 300. The vehicle 100 transmits vehicle information VCL to the relay device 400. The vehicle information VCL includes the status of the vehicle 100, images of the surroundings of the vehicle 100 obtained by a camera, results of vehicle processing, etc. The relay device 400 transmits the received vehicle information VCL to the remote support terminal 200. The remote support terminal 200 presents the vehicle information VCL received from the vehicle 100 to the remote supporter S.

[0026] The remote supporter S checks the presented vehicle information VCL, recognizes the situation around the vehicle 100, and provides remote support to the vehicle 100. For example, the remote support supports at least one of the above-mentioned recognition processing, action determination processing, and timing determination processing. The supporter instruction INS is an instruction to the vehicle 100 input by the remote supporter S. For example, the supporter instruction INS instructs the vehicle 100 to start. The remote support terminal 200 accepts input of the supporter instruction INS from the remote supporter S and transmits the input supporter instruction INS to the relay device 400. The relay device 400 transmits the received supporter instruction INS to the vehicle 100. The vehicle 100 controls the vehicle in accordance with the supporter instruction INS received from the relay device 400.

[0027] Relaying data communication by the relay device 400 is effective in maintaining high-speed communication during remote support. High-speed communication is required for communication between the vehicle 100 and the remote support terminal 200. This is because, during remote support, information such as vehicle information VCL and supporter instruction INS is constantly transmitted and received between the vehicle 100 and the remote support terminal 200. For example, the remote supporter S determines the content of the supporter instruction INS by viewing the image output on the remote support terminal 200. If the supporter instruction INS is not transmitted in a timely manner due to communication delays or the like, this could lead to serious problems. Accordingly, it is desirable for the relay device 400 to have high processing performance. This is because the relay device 400 needs to quickly transmit the information it receives. On the other hand, the management device 300, which is responsible for transmitting and receiving support requests REQ and selecting resources, does not require processing performance equivalent to that of the relay device 400.

[0028] 2.Relay device 2-1. Recording by relay device In addition to relaying data communication between the vehicle 100 and the remote support terminal 200 during remote support, the relay device 400 may also temporarily record at least a portion of the data received via the data communication. Hereinafter, the data recording performed by the relay device 400 will be referred to as the "data recording process," and the data that is the subject of the data recording process will be referred to as the "recording data RD." The recording data RD includes at least a portion of the vehicle information VCL and the supporter instructions INS. The recording data RD is stored, for example, in a storage area provided in the relay device 400 (for example, the storage device 470, described below).

[0029] 2 is a schematic diagram showing another example of data recording processing. The relay device 400 transfers the recording data RD to one or more external storage devices 500 (hereinafter simply referred to as "external storage devices 500") different from the relay device 400. The recording data RD is stored in the external storage devices 500. After transferring the recording data RD, the relay device 400 deletes the recording data RD from the relay device 400.

[0030] 2-2. Overview of relay device selection Consider a case where the remote support system 1 includes a plurality of relay device candidates 400c. Each of the plurality of relay device candidates 400c has the same configuration and functions as the relay device 400 described above. In this case, the management device 300 selects a relay device 400 that will actually be used to provide remote support to the vehicle 100 from the plurality of relay device candidates 400c. This process will be referred to as "relay device selection" hereinafter.

[0031] FIG. 3 is a schematic diagram showing an example of relay device selection. In (A) of FIG. 3, the management device 300 selects a relay device 400 from multiple relay device candidates 400c through relay device selection. As shown in (B) of FIG. 3, the management device 300 may select multiple relay devices 400 through relay device selection. In (B) of FIG. 3, a first relay device 400-1 and a second relay device 400-2 are selected. In this case, for example, data (e.g., vehicle information VCL) from the vehicle 100 to the remote support terminal 200 is relayed by the first relay device 400-1, and conversely, data (e.g., supporter instructions INS) from the remote support terminal 200 to the vehicle 100 is relayed by the second relay device 400-2. In other words, multiple relay devices 400 can be used appropriately. Details of the process associated with relay device selection will be described later.

[0032] 2-3.Effects The remote support system 1 includes a management device 300 and a relay device 400, each with a different role. Specifically, the management device 300 transmits and receives support requests REQ and selects resources, while the relay device 400 relays communications between the vehicle 100 and the remote support terminal 200. This feature improves scalability when the scale of the remote support system 1 changes. For example, consider a case where the roles of the management device 300 and the relay device 400 are combined into a single device (a management relay device). In this case, as the number of vehicles using remote support increases, it becomes necessary to add more management relay devices. On the other hand, the remote support system 1 of the present disclosure can accommodate this by adding more relay devices 400, which have a higher processing load, while keeping the number of management devices 300, which have a relatively light processing load, unchanged. An example of a case where the remote support system 1 becomes larger in scale will be described in Section 5.

[0033] Furthermore, the recording data RD recorded when the relay device 400 performs a data recording process is useful as a "fair" record. That is, the recording data RD is the information transmitted and received during the remote support and is not provided arbitrarily by the support requester 10 or the remote supporter S. For example, if a problem occurs during remote support, the recording data RD can be used as evidence provided by a third party (such as an image from an in-vehicle camera or a signal transmitted from the remote support terminal 200). Furthermore, when the relay device 400 transfers the recording data RD to the external storage device 500, each device has a different role, further improving scalability. Furthermore, when the relay device 400 transfers the recording data RD to the external storage device 500, it is possible to prevent a situation in which the storage capacity of the relay device 400 is used up and new recording data RD cannot be recorded.

[0034] Furthermore, when the management device 300 selects a relay device, it is possible to improve the continuity of the functions of the remote support system 1. For example, even if some of the multiple relay device candidates 400c are not functioning due to a malfunction or maintenance, it is possible to select a relay device 400 from the multiple relay device candidates 400c that are functioning normally. As a whole, the functions of the remote support system 1 are maintained.

[0035] 3. Details of relay device selection The relay device selection may be performed based on a priority set for each of the multiple relay device candidates 400c. Fig. 4 is a schematic diagram for explaining the priority of the relay device selection. The management device 300 stores relay device information RDI, which is information related to each of the multiple relay device candidates 400c. The relay device information RDI includes location information, processing load, communication load, etc., for each of the multiple relay device candidates 400c.

[0036] The priority may be set based on the communication distance between the vehicle 100 and the remote support terminal when a communication route passes through each of the plurality of relay device candidates 400c. In this case, the management device 300 holds location information of the vehicle 100, the remote support terminal 200, and each of the plurality of relay device candidates 400c. The location information of the remote support terminal 200 and the plurality of relay device candidates 400c is known information and is provided to the management device 300 in advance. The location information of the vehicle 100 is acquired by a Global Navigation Satellite System (GNSS) or the like installed in the vehicle 100, and is provided from the vehicle 100 to the management device 300. The location information of the vehicle 100 may be provided periodically or may be included in a REQ when requesting assistance. The management device 300 calculates the geographical distance (relay distance) from the vehicle 100 to the remote support terminal 200 via each of the multiple relay device candidates 400c. The shorter the obtained relay distance, the higher the priority is set. That is, the management device 300 selects a relay device 400 from the multiple relay device candidates 400c so as to shorten the communication distance. In addition to the geographical distance, the distance on the network may also be referred to as the communication distance.

[0037] Furthermore, the priority may be determined based on the load (network load) occurring on the network used by each of the multiple relay device candidates 400c. For example, the management device 300 calculates the bandwidth usage rate of the network bandwidth used by each of the multiple relay device candidates 400c. The bandwidth usage rate is used as one measure of the network load. The smaller the obtained network load, the higher the priority is set. In other words, the management device 300 preferentially selects, as the relay device 400, the relay device candidate 400c with the smaller network load.

[0038] Furthermore, the priority may be the processing load (relay device load) occurring in each of the multiple relay device candidates 400c. For example, the management device 300 calculates the ratio (CPU utilization rate) of the time that the CPU (Central Processing Unit) of each of the multiple relay device candidates 400c is executing some kind of processing to a unit time. Alternatively, the CPU utilization rate may be transmitted from each of the multiple relay device candidates 400c to the management device 300. The CPU utilization rate is used as one measure of the relay device load. The priority is set higher as the relay device load decreases. In other words, the management device 300 preferentially selects, as the relay device 400, one of the multiple relay device candidates 400c with a smaller processing load.

[0039] <Effects> When a relay device is selected with priority given to a short communication distance, communication delays are less likely to occur. Furthermore, the possibility of network trouble occurring between the vehicle 100 and the remote support terminal 200 is reduced. When a relay device is selected with priority given to a network load or a relay device load, a relay device 400 is selected that reduces the network load or the relay device load. As a result, the load distribution throughout the remote support system 1 is leveled.

[0040] Furthermore, the management device 300 may calculate an evaluation score that combines the priorities exemplified in this section, and select a relay device based on the evaluation score.

[0041] 4.Configuration example 4-1.Vehicles 5 is a block diagram showing an example of the configuration of the vehicle 100. The vehicle 100 includes a communication device 110, a sensor group 120, a driving device 130, and a control device 150.

[0042] The communication device 110 communicates with the outside of the vehicle 100. For example, the communication device 110 communicates with the management device 300 and the relay device 400.

[0043] The sensor group 120 includes a recognition sensor, a vehicle state sensor, a position sensor, etc. The recognition sensor recognizes (detects) the situation around the vehicle 100. Examples of the recognition sensor include a camera, a LIDAR (Laser Imaging Detection and Ranging), a radar, etc. The vehicle state sensor detects the state of the vehicle 100. The vehicle state sensor includes a speed sensor, an acceleration sensor, a yaw rate sensor, a steering angle sensor, etc. The position sensor detects the position and orientation of the vehicle 100. For example, the position sensor includes a GNSS.

[0044] The traveling device 130 includes a steering device, a drive device, and a braking device. The steering device steers the wheels. For example, the steering device includes an electric power steering (EPS) device. The drive device is a power source that generates driving force. Examples of the drive device include an engine, an electric motor, and an in-wheel motor. The braking device generates braking force.

[0045] The control device 150 is a computer that controls the vehicle 100. The control device 150 includes one or more processors 160 (hereinafter simply referred to as processors 160) and one or more storage devices 170 (hereinafter simply referred to as storage devices 170). The processor 160 can also be called a processing circuit. The processor 160 executes various processes. For example, the processor 160 includes a CPU. The storage device 170 stores various information required for processing by the processor 160. Examples of the storage device 170 include a volatile memory, a non-volatile memory, an HDD, an SSD, etc. The control device 150 may include one or more ECUs (Electronic Control Units).

[0046] The vehicle control program PROG1 is a computer program executed by the processor 160. The functions of the control device 150 are realized by the processor 160 executing the vehicle control program PROG1. The vehicle control program PROG1 is stored in the storage device 170. Alternatively, the vehicle control program PROG1 may be recorded on a computer-readable recording medium.

[0047] The control device 150 uses the sensor group 120 to acquire driving environment information ENV that indicates the driving environment of the vehicle 100. The driving environment information ENV is stored in the storage device 170.

[0048] The driving environment information ENV includes surrounding situation information indicating the recognition results of the recognition sensor. For example, the surrounding situation information includes images captured by a camera. The surrounding situation information may include object information regarding objects around the vehicle 100. Examples of objects around the vehicle 100 include pedestrians, other vehicles (preceding vehicles, parked vehicles, etc.), white lines, traffic lights, signs, roadside structures, etc. The object information indicates the relative position and relative speed of the object with respect to the vehicle 100.

[0049] The driving environment information ENV also includes vehicle state information indicating the vehicle state detected by the vehicle state sensor.

[0050] Furthermore, the driving environment information ENV includes vehicle position information indicating the position and direction of the vehicle 100. The vehicle position information is obtained by a position sensor. Highly accurate vehicle position information may be obtained by a self-position estimation process (localization) using map information and surrounding situation information (object information).

[0051] The control device 150 executes vehicle driving control to control the driving of the vehicle 100. The vehicle driving control includes steering control, drive control, and braking control. The control device 150 executes vehicle driving control by controlling the driving device 130 (steering device, drive device, and brake device).

[0052] The control device 150 may perform automatic driving control based on the driving environment information ENV. More specifically, the control device 150 generates a driving plan for the vehicle 100 based on the driving environment information ENV. Furthermore, the control device 150 generates a target trajectory required for the vehicle 100 to drive according to the driving plan based on the driving environment information ENV. The target trajectory includes a target position and a target speed. Then, the control device 150 performs vehicle driving control so that the vehicle 100 follows the target trajectory.

[0053] The control device 150 transmits a support request REQ to the management device 300 as necessary. During remote support, the control device 150 communicates with the remote support terminal 200 via the relay device 400.

[0054] 4-2.Management device 6 is a block diagram showing an example of the configuration of the management device 300. The management device 300 includes a communication device 310 and a control device 350.

[0055] The communication device 310 communicates with the vehicle 100 , the remote support terminal 200 , and the relay device 400 .

[0056] The control device 350 controls the management device 300. The control device 350 includes one or more processors 360 (hereinafter simply referred to as processors 360) and one or more storage devices 370 (hereinafter simply referred to as storage devices 370). The processor 360 can also be called a processing circuit. The processor 360 executes various processes. For example, the processor 360 includes a CPU (Central Processing Unit). The storage device 370 stores various information required for processing by the processor 360. Examples of the storage device 370 include volatile memory, non-volatile memory, HDD (Hard Disk Drive), SSD (Solid State Drive), etc.

[0057] The management program PROG3 is a computer program executed by the processor 360. The functions of the control device 350 are realized by the processor 360 executing the management program PROG3. The management program PROG3 is stored in the storage device 370. Alternatively, the management program PROG3 may be recorded on a computer-readable recording medium. The management program PROG3 may be provided via a network.

[0058] The storage device 370 further includes a resource database RDB. The resource database RDB stores and manages information about support resources required for remote support. The resource database RDB includes supporter information SI, which is information about the remote supporter S, and terminal information TI, which is information about the remote support terminal 200. Examples of the supporter information SI include availability, experience in remote support, license information, etc. The terminal information TI includes information such as availability, the number of displays provided, and the performance of input / output devices. When the management device 300 selects a relay device, the resource database RDB includes relay device information RDI.

[0059] The control device 350 communicates with the vehicle 100 , the remote support terminal 200 , and the relay device 400 via the communication device 310 .

[0060] The control device 350 receives a support request REQ transmitted from the vehicle 100. The support request REQ is stored in the storage device 370. The control device 350 refers to the resource database RDB and performs resource selection to allocate specific support resources to the vehicle 100.

[0061] The control device 350 transmits an allocation notice including a support request REQ and information about the vehicle 100 to the remote support terminal 200. In response to the allocation notice, the remote supporter S starts remote support for the vehicle 100.

[0062] 4-3.Repeater 7 is a block diagram showing an example of the configuration of the relay device 400. The relay device 400 includes a communication device 410 and a control device 450.

[0063] The communication device 410 communicates with the vehicle 100 and the remote support terminal 200. When the relay device 400 performs data recording processing, the communication device 410 may also communicate with the external storage device 500.

[0064] The control device 450 controls the relay device 400. The control device 450 includes one or more processors 460 (hereinafter simply referred to as processors 460) and one or more storage devices 470 (hereinafter simply referred to as storage devices 470). The processor 460 can also be called a processing circuit. The processor 460 executes various processes. For example, the processor 460 includes a CPU (Central Processing Unit). The storage device 470 stores various information required for processing by the processor 460. Examples of the storage device 470 include a volatile memory, a non-volatile memory, an HDD (Hard Disk Drive), an SSD (Solid State Drive), etc.

[0065] During remote support, the control device 450 receives vehicle information VCL from the vehicle 100. The control device 450 transmits the received vehicle information VCL to the remote support terminal 200. The control device 450 receives a supporter instruction INS transmitted from the remote support terminal 200. The control device 450 transmits the received supporter instruction INS to the vehicle 100.

[0066] When performing the above-described data recording process, the control device 450 may store the recording data RD in the storage device 470 within the control device 450. The control device 450 may also transfer the recording data RD to the external storage device 500 via the communication device 410. The external storage device 500 stores the received recording data RD in a storage area.

[0067] 4-4.Remote support terminal 8 is a block diagram showing an example of the configuration of the remote support terminal 200. The remote support terminal 200 includes a communication device 210, an output device 220, an input device 230, and a control device 250.

[0068] The communication device 210 communicates with the vehicle 100, the management device 300, and the relay device 400. For example, the communication device 210 receives a notification (assignment notification) from the communication device 310 indicating that the communication device 210 has been assigned to remote support. If the remote supporter S owns his / her own remote support terminal 200, the remote supporter S confirms the assignment notification displayed on the output device 220 and recognizes that he / she is the remote supporter S.

[0069] The allocation notification to the remote supporter S may be performed as a separate process from the remote support terminal 200. In this case, the remote supporter S receives the allocation notification from the communication device 310 or the communication device 210. Specifically, a communication device (smartphone, tablet, PC, etc.) owned by the remote supporter S receives the allocation notification. The allocation notification includes information about the remote support terminal 200 (for example, a management number), allowing the remote supporter S to access the remote support terminal 200.

[0070] The output device 220 outputs various types of information. For example, the output device 220 includes a display device. The display device displays the various types of information to present the various types of information to the remote supporter S. As another example, the output device 220 may include a speaker.

[0071] The input device 230 accepts input from the remote supporter S. For example, the input device 230 includes a touch panel, a keyboard, a mouse, a button, etc. The remote supporter S can use the input device 230 to input supporter instructions INS.

[0072] The control device 250 controls the remote support terminal 200. The control device 250 includes one or more processors 260 (hereinafter simply referred to as processors 260) and one or more storage devices 270 (hereinafter simply referred to as storage devices 270). The processors 260 execute various processes. The processors 260 can also be called processing circuits. For example, the processor 260 includes a CPU. The storage devices 270 store various information required for processing by the processors 260. Examples of the storage devices 270 include volatile memory, non-volatile memory, HDD, SSD, etc.

[0073] The remote support program PROG2 is a computer program executed by the processor 260. The functions of the control device 250 are realized by the processor 260 executing the remote support program PROG2. The remote support program PROG2 is stored in the storage device 270. Alternatively, the remote support program PROG2 may be recorded on a computer-readable recording medium. The remote support program PROG2 may be provided via a network.

[0074] The control device 250 communicates with the management device 300 via the communication device 210 and with the vehicle 100 via the relay device 400. The control device 250 receives a support request REQ and vehicle information VCL transmitted from the vehicle 100. The control device 250 presents the vehicle information VCL to the remote supporter S by displaying the vehicle information VCL on a display device. The remote supporter S can recognize the state of the vehicle 100 and the surrounding circumstances based on the vehicle information VCL. The remote supporter S inputs a supporter instruction INS using the input device 230. The control device 250 transmits the input supporter instruction INS to the vehicle 100 via the relay device 400.

[0075] 5. Large-scale remote support system As mentioned in Section 2-3, the remote support system 1 is particularly effective when operated on a large scale. A large-scale embodiment of the remote support system 1 will be described below with reference to FIG. 9. It is assumed that the remote support system 1 here is operated by a base (which can also be called a "remote support center") to which multiple supporter candidates Sc and multiple terminal candidates 200c belong, and is provided as a service. A person who receives this service is referred to as a user. The support requester 10 mentioned above refers to a user who sends a support request REQ. The remote support system 1 also has multiple registered vehicles 100R registered that can be the target of the service. Of the multiple registered vehicles 100R, the one that sends the support request REQ is the vehicle 100 that actually uses the remote support.

[0076] 5-1. Management device selection When the remote support system 1 is operated on a large scale, the remote support system 1 may include multiple management device candidates 300c. The multiple management device candidates 300c have the same configuration and functions as the management device 300 described above. In this case, the vehicle 100 selects a management device 300 that will actually manage remote support for the vehicle 100 from the multiple management device candidates 300c. This process will be referred to as "management device selection" hereinafter. The actual entity responsible for selecting a management device is the control device 150 included in the vehicle 100.

[0077] The vehicle 100 can access the "management device database MDB." The management device database MDB stores connection information (IP address, location information, etc.) for each of the multiple management device candidates 300c. The management device database MDB may be shared among multiple registered vehicles 100R.

[0078] When remote support begins, the vehicle 100 references the management device database MDB and selects a management device. The vehicle 100 can communicate with each of the multiple management device candidates 300c via the communication device 110. When the vehicle 100 requires remote support, it transmits a support request REQ to the multiple management device candidates 300c in sequence. For example, the vehicle 100 transmits the support request REQ to the management device candidates 300c in order, starting with the candidate closest to the vehicle 100, based on the location information of the multiple management device candidates 300c. When each of the multiple management device candidates 300c receives the support request REQ, it begins operating as a management device 300 to provide remote support to the vehicle 100. Specifically, the management device 300 selects resources and assigns a remote supporter S and a remote support terminal 200 to the vehicle 100. The support request REQ transmitted to the management device selection may include identification information and location information of the vehicle 100, identification information of the support requester 10, the content of the remote support required, etc. After selecting the management device, the management device 300 executes resource selection.

[0079] 5-2. Resource Selection Each of the multiple management device candidates 300c includes a resource database RDB that stores information about support resources. Supporter information SI stored in the resource database RDB includes information about each of the multiple supporter candidates Sc. Similarly, terminal information TI includes information about each of the multiple terminal candidates 200c. The resource database RDB may be shared among the multiple management device candidates 300c. When the management device 300 selects a relay device, the resource database RDB includes relay device information RDI.

[0080] The resource database RDB may store information other than the supporter information SI, the terminal information TI, and the relay device information RDI. For example, information about a plurality of registered vehicles 100R and users may be registered in advance. By storing and managing various information in the resource database RDB, the management device 300 can flexibly select resources.

[0081] 5-2-1. Specific examples of resource selection Below, some specific examples of resource selection will be described.

[0082] <Remote supporter selection> The management device 300 can use the location information of each of the multiple supporter candidates Sc included in the supporter information SI for resource selection. For example, the management device 300 transmits an allocation notification to the multiple supporter candidates Sc in order of proximity to the vehicle 100. If a remote supporter S does not respond to the allocation notification within a certain period of time, the management device 300 may transmit the allocation notification to the next closest remote supporter S.

[0083] The language used by each user and each of the multiple supporter candidates Sc may be registered in the resource database RDB. In this case, a remote supporter S that can speak the language used by the support requester 10 can be assigned. For example, if an English speaker traveling in Japan uses the remote support system 1 as the support requester 10, the management device 300 preferentially assigns a remote supporter S that can speak English.

[0084] Furthermore, the remote support history of each of the multiple supporter candidates Sc may be registered in the resource database RDB. The remote support history includes information such as the total time, number of times, and area of ​​remote support provided. In this case, the management device 300 preferentially assigns to remote support a remote supporter S who has experience in providing remote support in the area where the vehicle 100 is located. Furthermore, the remote supporter S may be selected so that the workload is leveled after calculating the workload based on the total time and number of times of remote support provided.

[0085] The above-mentioned information such as the user's identification information and language used is stored in the resource database RDB as user information UI. Furthermore, information such as the language used and remote support history of multiple supporter candidates Sc is included in supporter information SI.

[0086] <Selecting a remote support device> The management device 300 can use the location information of each of the multiple terminal candidates 200c for resource selection. For example, the management device 300 can assign, as the remote support terminal 200, one of the multiple terminal candidates 200c that is closer to the vehicle 100 with priority.

[0087] Furthermore, instead of the management device 300 selecting the remote support terminal 200, the remote supporter S may access any one of a plurality of available terminal candidates 200c, thereby selecting the remote support terminal 200.

[0088] <Relay device selection> The management device 300 can select a relay device 400 from a plurality of relay device candidates 400c by relay device selection. Details of relay device selection are as described above.

[0089] Effects The remote support system 1 provides the following effects that are important for expanding services to a larger scale.

[0090] The remote support system 1 can flexibly respond to changes in the scale of services. In the remote support system 1, information on support resources is aggregated in a resource database RDB. As the scale of services increases, the amount of support resources required increases and the geographic locations of the resources also become more dispersed. The remote support system 1 can manage information on the increased number of support resources using the resource database RDB, and can flexibly respond to geographical expansion by adding management devices 300 and support resources as needed.

[0091] Furthermore, the remote support system 1 has high service continuity. Multiple registered vehicles 100R can access multiple management device candidates 300c via the management device database MDB. Therefore, even if some of the multiple management device candidates 300c stop functioning, service can be continued without problems by accessing an alternative device. Furthermore, the management device 300 selects support resources via the resource database RDB. Therefore, even if some of the support resources are unavailable, alternative resources can be selected.

[0092] Furthermore, the remote support system 1 can select a remote supporter S taking into consideration regional characteristics and language. It is desirable that the remote supporter S fully understands the traffic laws and customs of the area where the vehicle 100 is located. Furthermore, if a support requester 10 is present, it is desirable that the remote supporter S can understand the language of the support requester 10. These points are important from the perspective of the safety of the remote support and the sense of security of the support requester 10.

[0093] The effect of the division of roles between the management device 300 and the relay device 400 described in Section 2-3 and the effect of the relay device selection described in Section 3 are also exerted when the remote support system 1 is operated on a large scale. [Explanation of symbols]

[0094] 1: Remote support system 10: Support requester 100: Vehicle 100R: Registered vehicle 200: Remote support terminal 200c: Terminal candidate 300: Management device 300c: Management device candidate 400: Relay device 400c: Relay device candidate 500: External storage device INS: Supporter instructions MDB: Managed Device Database RD: Recording data RDB: Resource database REQ: Support request S: Remote supporter Sc: Supporter candidate

Claims

1. A remote support system for remote support of a moving object, comprising: A management device; one or more relay devices different from the management device; Equipped with The management device receiving a support request transmitted from the mobile device; Selecting support resources necessary for said remote support; The one or more relay devices relay data communication between the mobile object and the remote support terminal during the remote support. Remote support system.

2. 2. The remote support system according to claim 1, The one or more relay devices at least temporarily record at least a portion of the data received via the data communication during the remote support. Remote support system.

3. 3. The remote support system according to claim 2, further comprising one or more storage devices different from the one or more relay devices; The one or more relay devices further include: transferring the recorded data to the one or more storage devices; After transferring the data, the data is deleted from the one or more relay devices. Remote support system.

4. 2. The remote support system according to claim 1, The management device selects the one or more relay devices from a plurality of relay device candidates.

5. 5. The remote support system according to claim 4, The management device setting a priority for each of the plurality of relay device candidates; The one or more relay devices are selected from the plurality of relay device candidates based on the priority. Remote support system.

6. 6. The remote support system according to claim 5, The priority is: is set based on a communication distance between the mobile object and the remote support terminal via each of the plurality of relay device candidates, The shorter the communication distance, the higher the Remote support system.

7. 6. The remote support system according to claim 5, The priority is: is set based on a network load occurring on a network connecting the mobile object and the remote support terminal via each of the plurality of relay device candidates, The smaller the network load, the higher Remote support system.

8. 6. The remote support system according to claim 5, The priority is: The relay device candidate is set based on a processing load occurring in each of the plurality of relay device candidates, The smaller the processing load, the higher Remote support system.

9. A management device used for remote support of a mobile object, receiving a support request transmitted from the mobile device; Selecting support resources necessary for said remote support; One or more relay devices, different from the management device, that relay data communication between the mobile unit and the remote support terminal are selected from among a plurality of relay device candidates. Management device.

10. 10. The management device according to claim 9, setting a priority for each of the plurality of relay device candidates; The one or more relay devices are selected from the plurality of relay device candidates based on the priority. Management device.

11. The management device according to claim 10, The priority is: is set based on a communication distance between the mobile object and the remote support terminal via each of the plurality of relay device candidates, The shorter the communication distance, the higher the Management device.

12. The management device according to claim 10, The priority is: is set based on a network load occurring on a network connecting the mobile object and the remote support terminal via each of the plurality of relay device candidates, The smaller the network load, the higher Management device.

13. The management device according to claim 10, The priority is: The relay device candidate is set based on a processing load occurring in each of the plurality of relay device candidates, The smaller the processing load, the higher Management device.

Images