Remote support management device, remote support management method, and remote support management program

Abstract

To reduce the processing load on a remote support management device for allocation of a remote supporter and a remote support terminal, and perform the allocation appropriately.SOLUTION: A remote support management device includes one or more processors that, in response to a request for remote support from one or more of a plurality of mobilities, perform allocation processing of allocating at least one of a remote supporter and a remote support terminal to the mobilities that have made the request. The one or more processors acquire a score serving as a basis of the allocation processing from the one or more of the plurality of mobilities, acquire surroundings information indicating a status of an area by communicating with one or more infrastructure sensors installed in the area where an update target mobility that has transmitted the score moves, calculate an additional score of the update target mobility on the basis of the acquired surroundings information, and update the score by reflecting the additional score in the score transmitted from the update target mobility.SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] The present disclosure relates to remote support for mobility.

Background Art

[0002] Patent Document 1 discloses a control device that manages remote control of an autonomous vehicle. The control device determines a processing order, which is an order to execute remote control on a vehicle to be remotely controlled, and assigns the work of remote control to an operator according to the determined processing order. The processing order is determined based on the calculation results of the working time and priority of the remote control of the vehicle to be targeted. The priority is calculated based on various information such as the traffic conditions around the vehicle to be targeted.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] According to the technique described in Patent Document 1, the control device calculates the priority used for operator assignment based on various information. For this reason, the processing load of the control device regarding operator assignment becomes large. More specifically, as the number of vehicles to be remotely controlled that request remote control during the same period increases, the processing load of the control device increases.

[0005] One object of the present disclosure is to provide a technique capable of appropriately performing the assignment while reducing the processing load of a remote support management device regarding the assignment of at least one of a remote supporter and a remote support terminal to a mobility that requests remote support.

Means for Solving the Problems

[0006] The remote support management device according to the present disclosure manages remote support for a plurality of mobilities. The remote support management device includes one or more processors that execute an allocation process of allocating at least one of a remote supporter and a remote support terminal used by the remote supporter to the mobility that made the request in response to a remote support request from one or more of the plurality of mobilities. The one or more processors acquire a score that is the basis for the allocation process from one or more of the plurality of mobilities, communicate with one or more infrastructure sensors installed in the area where the update target mobility that transmitted the score moves, acquire peripheral situation information indicating the situation of the area, calculate an additional score for the update target mobility based on the acquired peripheral situation information, and update the score by reflecting the additional score in the score transmitted from the update target mobility.

[0007] The remote support management method according to the present disclosure is a method for managing remote support for a plurality of mobilities, which is executed by a computer. The remote support management method includes executing an allocation process of allocating at least one of a remote supporter and a remote support terminal used by the remote supporter to the mobility that made the request in response to a remote support request from one or more of the plurality of mobilities; acquiring a score that is the basis for the allocation process from one or more of the plurality of mobilities; communicating with one or more infrastructure sensors installed in the area where the update target mobility that transmitted the score moves, and acquiring peripheral situation information indicating the situation of the area; calculating an additional score for the update target mobility based on the peripheral situation information; and updating the score by reflecting the additional score in the score transmitted from the update target mobility.

[0008] The remote support management program according to the present disclosure is a program executed by a computer for managing remote support for multiple mobilities. The remote support management program responds to a remote support request from one or more of the multiple mobilities, and performs an allocation process of allocating at least one of a remote supporter and a remote support terminal used by the remote supporter to the mobility that made the request, obtains a score that is the basis for the allocation process from one or more of the multiple mobilities, communicates with one or more infrastructure sensors installed in the area where the mobility to be updated that sent the score moves, obtains peripheral situation information indicating the situation of the area, calculates an additional score for the mobility to be updated based on the peripheral situation information, and updates the score by reflecting the additional score in the score sent from the mobility to be updated, and causes the computer to execute these operations.

Effect of the Invention

[0009] According to the present disclosure, the remote support management device obtains a score that is the basis for the allocation of at least one of a remote supporter and a remote support terminal from a mobility (mobility to be updated) that requests remote support. Thereby, compared with an example in which the remote support management device performs all of the processes related to the calculation of the score, the processing load of the remote support management device related to the allocation can be reduced. And the remote support management device calculates an additional score based on the peripheral situation information from one or more infrastructure sensors, and updates the score by reflecting the additional score in the score sent from the mobility to be updated. Thereby, it becomes possible to appropriately determine the score by using peripheral situation information that cannot be obtained by the sensors mounted on the mobility. Thus, according to the present disclosure, it becomes possible to appropriately perform the above allocation while reducing the processing load of the remote support management device related to the allocation.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Embodiments for Carrying Out the Invention

[0011] Embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0012] 1. Overview of the Remote Support System FIG. 1 is a conceptual diagram for explaining the overview of the remote support system 1 according to the present embodiment. The remote support system 1 is a system for remote support of the mobility 100. Remote support is a concept including remote operation, remote assistance, and remote monitoring. And remote operation is a concept including remote driving. The remote support system 1 includes the mobility 100, the remote support terminal 200, and the remote support management device 300. Also, as shown in FIG. 1, the remote support system 1 may further include one or more infrastructure sensors 400.

[0013] The mobility 100 is a movable moving body. The mobility 100 may be manually operated by an operator on board the mobility 100. The mobility 100 may be provided with an autonomous movement function. In any case, the mobility 100 is configured to be remotely operable as needed. That is, the mobility 100 is the target of remote support by the remote support system 1. The mobility 100 receives remote support via the management device 300.

[0014] The types of mobility 100 that are the targets of remote support are not limited to one, and there may be multiple. For example, the mobility 100 is a vehicle traveling on a public road (e.g., a passenger car, a truck, a bus, a MaaS vehicle, an autonomous vehicle, etc.). As another example, the mobility 100 may be a vehicle used in a factory (e.g., a forklift, a factory cart, etc.). As yet another example, the mobility 100 may be a special small vehicle (e.g., a golf course cart, a personal mobility, an electric wheelchair, etc.). As yet another example, the mobility 100 may be a construction machine (e.g., a power shovel, a bulldozer, etc.). As yet another example, the mobility 100 may be a robot (e.g., a logistics robot, a working robot, etc.). As yet another example, the mobility 100 may be an aircraft (e.g., a drone, etc.). As yet another example, the mobility 100 may be a ship (e.g., a small ship, a large cruiser, etc.). As yet another example, the mobility 100 may be a ride in an amusement park (e.g., a cart, an attraction, etc.).

[0015] Figure 2 shows examples of various remote support contents required for various mobilities 100. As illustrated in Figure 2, the mobilities 100 are diverse, and the required remote support contents are also diverse. More specifically, the examples shown in Figure 2 are all examples of remote operations. Note that the remote support may be requested from the mobility 100 itself, or may be requested from a service provider that is in partnership with the remote support system 1. In the latter case, the content of the remote support can also be said to be the content of the service provided by the service provider. Also, in addition to the examples shown in Figure 2, examples of the content of the remote support (service content) include the distribution of shared cars, home delivery, transportation of goods, movement of personal mobility, operation substitution of amusement park attractions, landing of drones, etc.

[0016] The remote support terminal 200 is a terminal device used when the remote supporter X remotely supports the mobility 100. That is, the remote support terminal 200 is configured to be used by the remote supporter X for the remote support of the mobility 100. Examples of the remote support terminal 200 include a cockpit-type terminal, a PC, a tablet, a smartphone, etc. A single remote support terminal 200 may be configured to support the remote support of various types of mobility 100. Alternatively, a single remote support terminal 200 may be dedicated to the remote support of a specific mobility 100. Also, the combination of the remote supporter X and the remote support terminal 200 may be predetermined or may be freely changeable. That is, a single remote support terminal 200 may be used only by a specific remote supporter X, or may be used in turn by various remote supporters X.

[0017] The remote support management device (or simply the management device) 300 manages the remote support system 1. The management device 300 may be composed of a plurality of servers that perform distributed processing. For example, the management device 300 manages a plurality of remote supporters X and a plurality of remote support terminals 200. Also, the management device 300 allocates the remote supporter X and the remote support terminal 200 to the remote support of the mobility 100 in response to a remote support request. Further, the management device 300 may manage the state of the mobility 100 during remote support. Details of the management device 300 will be described later.

[0018] The mobility 100, the remote support terminal 200, and the management device 300 can communicate with each other via a communication network. For example, the mobility 100 can wirelessly communicate with the remote support terminal 200 and the management device 300 via a wireless communication network. The remote support terminal 200 and the management device 300 can communicate with each other via a wired communication network or a wireless communication network. The mobility 100 and the remote support terminal 200 may communicate via the management device 300, or may communicate directly without going through the management device 300.

[0019] The general flow of information during the remote support of Mobility 100 is as follows.

[0020] Mobility 100 is equipped with various sensors including a camera. The camera captures the surrounding situation of Mobility 100. A video showing the surrounding situation of Mobility 100 is obtained by the camera. Mobility information MOV is information obtained by various sensors and includes at least the video captured by the camera. Mobility information MOV may include the position and state (e.g., speed, steering angle, etc.) of Mobility 100. Mobility 100 transmits the mobility information MOV to the remote support terminal 200.

[0021] The remote support terminal 200 receives the mobility information MOV transmitted from Mobility 100. The remote support terminal 200 presents the mobility information MOV to the remote supporter X. Specifically, the remote support terminal 200 is equipped with a display device and displays the video, etc. on the display device. The remote supporter X recognizes the surrounding situation of Mobility 100 by looking at the displayed information and performs remote support for Mobility 100. The remote support information SUP is information regarding the remote support by the remote supporter X. In the example of remote operation, the remote support information SUP includes, for example, the operation amount input by the remote supporter X. Therefore, in the example of remote operation, it can be said that the remote support information SUP (i.e., the remote operation information) is information that reflects the degree of remote operation by the remote supporter X. In the example of remote assistance, the remote support information SUP includes the instructions input by the remote supporter X. The remote support terminal 200 transmits the remote support information SUP to Mobility 100.

[0022] Mobility 100 receives the remote support information SUP transmitted from the remote support terminal 200. For example, Mobility 100 performs mobility control according to the received remote support information SUP. In this way, the remote support of Mobility 100 is realized.

[0023] FIG. 3 is a conceptual diagram showing a configuration example of the remote support system 1. In the example shown in FIG. 3, the remote support management center is provided within a predetermined site or a predetermined building. Then, the management device 300 and a plurality of remote support terminals 200 (200-1 to 200-N: N is an integer of 2 or more) are installed within the remote support management center. Also, a plurality of remote supporters X work within the remote support management center. The management device 300 monitors and manages the states of the plurality of remote support terminals 200 within the remote support management center. Also, the management device 300 monitors and manages the states of the plurality of remote supporters X within the remote support management center.

[0024] 2. Configuration Example 2-1. Configuration Example of Mobility FIG. 4 is a block diagram showing a configuration example of the mobility 100. The mobility 100 includes a communication device 110, a sensor group 120, one or more actuators 130, and a control device 140.

[0025] The communication device 110 performs wireless communication with the outside of the mobility 100. For example, the communication device 110 performs wireless communication with the remote support terminal 200 and the management device 300.

[0026] The sensor group 120 includes a recognition sensor, a mobility state sensor, a position sensor, etc. The recognition sensor recognizes (detects) the situation around the mobility 100. Examples of the recognition sensor include a camera C, LIDAR (Laser Imaging Detection and Ranging), a radar, etc. The mobility state sensor detects the state of the mobility 100. The mobility 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 mobility 100. For example, the position sensor includes a GNSS (Global Navigation Satellite System) receiver.

[0027] Actuator 130 moves mobility 100. For example, actuator 130 includes a longitudinal movement actuator for moving mobility 100 forward and backward (accelerating and decelerating). As another example, actuator 130 may include a lateral movement actuator for moving mobility 100 laterally. As yet another example, if mobility 100 includes an arm, actuator 130 may include an arm actuator for moving the arm.

[0028] For example, when mobility 100 is a general vehicle, actuator 130 includes a steering device, a driving device, and a braking device. The steering device steers the wheels. For example, the steering device includes an electric power steering (EPS) device. The driving device is a power source that generates a driving force. Examples of the driving device include an engine, an electric motor, an in-wheel motor, etc. The braking device generates a braking force.

[0029] The control device 140 is a computer that controls the mobility 100. The control device 140 includes one or more processors 150 (hereinafter simply referred to as the processor 150) and one or more storage devices 160 (hereinafter simply referred to as the storage device 160). The processor 150 executes various processes. Examples of the processor 150 include a general-purpose processor, an application-specific processor, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), an integrated circuit, a conventional circuit, and / or a combination thereof. The processor 150 can also be referred to as circuitry or processing circuitry. Circuitry is hardware programmed to implement the described functions or hardware that executes the functions. The storage device 160 stores various information. Examples of the storage device 160 include a volatile memory, a non-volatile memory, an HDD (Hard Disk Drive), an SSD (Solid State Drive), and the like.

[0030] The control program PROG1 is a computer program executed by the processor 150. The functions of the control device 140 may be realized by the cooperation of the processor 150 and the storage device 160 that execute the control program PROG1. The control program PROG1 is stored in the storage device 160. Alternatively, the control program PROG1 may be recorded on a computer-readable recording medium.

[0031] The control device 140 acquires mobility environment information ENV indicating the mobility environment of the mobility 100 (e.g., the driving environment of a vehicle). The mobility environment information ENV is stored in the storage device 160.

[0032] The mobile environment information ENV includes surrounding situation information indicating the recognition results by the recognition sensors. For example, the surrounding situation information includes the video captured by the camera C. Also, the surrounding situation information may include object information regarding the objects around the mobility 100. Examples of the objects around the mobility 100 include pedestrians, other vehicles (preceding vehicles, parked vehicles, etc.), white lines, stop lines, traffic lights, signs, roadside structures, etc. The object information indicates the relative position and relative speed of the object with respect to the mobility 100. For example, by analyzing the video obtained by the camera C, the object can be identified and its relative position can be calculated. Also, based on the point cloud information obtained by the LIDAR, the object can be identified and its relative position and relative speed can be acquired.

[0033] Also, the mobile environment information ENV may include mobility state sensor information indicating the detection results by the mobility state sensors. The mobility state sensor information indicates the speed, acceleration (longitudinal acceleration, lateral acceleration), yaw rate, steering angle, etc. of the mobility 100.

[0034] Furthermore, the mobile environment information ENV may include position information indicating the position and moving direction (azimuth) of the mobility 100. The position information is obtained by the position sensor. High-precision position information may be acquired by self-position estimation processing (Localization) using the map information and the surrounding situation information (object information).

[0035] The control device 140 executes movement control for controlling the movement of the mobility 100. The movement control includes forward / backward movement control and lateral movement control. The control device 140 executes the movement control by controlling the actuator 130.

[0036] The control device 140 may execute autonomous movement control based on the movement environment information ENV. More specifically, the control device 140 generates a movement plan for the mobility 100 based on the movement environment information ENV. Further, the control device 140 generates a target trajectory necessary for the mobility 100 to travel according to the movement plan based on the movement environment information ENV. The target trajectory includes a target position and a target speed. Then, the control device 140 performs movement control so that the mobility 100 follows the target trajectory.

[0037] When remote support for the mobility 100 is performed, the control device 140 communicates with the remote support terminal 200 via the communication device 110.

[0038] The control device 140 transmits the mobility information MOV to the remote support terminal 200. The mobility information MOV is information necessary for remote support of the mobility 100 by the remote supporter X and includes at least a part of the above-described movement environment information ENV. In particular, the mobility information MOV includes the video captured by the camera C. The mobility information MOV may include other peripheral situation information. The mobility information MOV may include mobility state sensor information. The mobility information MOV may include position information.

[0039] Also, the control device 140 receives the remote support information SUP from the remote support terminal 200. In the example of remote operation, the remote support information SUP is information regarding remote operations (steering operation, acceleration operation, deceleration operation, forward and backward movement operation, lateral movement operation, etc.) by the remote supporter X and includes the operation amount input by the remote supporter X. The control device 140 performs movement control according to the received remote support information SUP (i.e., remote operation information).

[0040] 2-2. Configuration example of remote support terminal FIG. 5 is a block diagram showing a configuration example of the remote support terminal 200. The remote support terminal 200 includes a communication device 210, a display device 220, an input device 230, and a control device 240.

[0041] The communication device 210 communicates with the mobility 100 and the management device 300.

[0042] The display device 220 displays various types of information to the remote supporter X that performs remote support. In other words, the display device 220 presents various types of information to the remote supporter X by displaying the various types of information. Typically, the display device 220 is a display (monitor) such as a liquid crystal display or an organic EL display. The display device 220 may be a touch panel.

[0043] The input device 230 receives an input from the remote supporter X. For example, the input device 230 may include a remote operation member that is operated when the remote supporter X remotely operates the mobility 100. Examples of the remote operation member include a steering wheel, an accelerator pedal, a brake pedal, a direction indicator, a joystick, a cross key, a switch, and the like. The remote operation member may be a touch panel. The input device 230 may include a keyboard, a mouse, a touch panel, etc. other than the remote operation member.

[0044] The control device 240 controls the remote support terminal 200. The control device 240 includes one or more processors 250 (hereinafter simply referred to as the processor 250) and one or more storage devices 260 (hereinafter simply referred to as the storage device 260). The processor 250 executes various processes. Examples of the processor 250 include a CPU, a GPU, an ASIC, an FPGA, etc. The storage device 260 stores various information. Examples of the storage device 260 include a volatile memory, a non-volatile memory, an HDD, an SSD, etc. The processor 250 executes various processes. Examples of the processor 250 include a general-purpose processor, an application-specific processor, a CPU, a GPU, an ASIC, an FPGA, an integrated circuit, a conventional circuit, and / or a combination thereof. The processor 250 can also be referred to as circuitry or processing circuitry. Circuitry is hardware programmed to realize the described functions or hardware that executes the functions. The storage device 260 stores various information. Examples of the storage device 260 include a volatile memory, a non-volatile memory, an HDD, an SSD, etc.

[0045] The remote support program PROG2 is a computer program executed by the processor 250. The functions of the control device 240 may be realized by the cooperation of the processor 250 and the storage device 260 that execute the remote support program PROG2. The remote support program PROG2 is stored in the storage device 260. 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.

[0046] The control device 240 communicates with the mobility 100 via the communication device 210. The control device 240 receives the mobility information MOV transmitted from the mobility 100. The control device 240 presents the mobility information MOV to the remote supporter X by displaying the mobility information MOV including video on the display device 220. The remote supporter X can recognize the state of the mobility 100 and the surrounding situation based on the mobility information MOV displayed on the display device 220.

[0047] In the example of remote operation, the remote supporter X operates the remote operation member of the input device 230. The operation amount of the remote operation member is detected by a sensor installed in the remote operation member. Also, in the example of remote support, the remote supporter X issues various instructions (e.g., start instruction) via the input device 230. The control device 240 generates remote support information SUP including the operation amount or instruction input by the remote supporter X. Then, the control device 240 transmits the remote support information SUP to the mobility 100 via the communication device 210.

[0048] 2-3. Configuration Example of Remote Support Management Device FIG. 6 is a block diagram showing a configuration example of the remote support management device 300. The management device 300 includes a communication device 310 and a control device 320.

[0049] The communication device 310 communicates with the mobility 100, the remote support terminal 200, and the infra sensor 400 (see FIG. 1).

[0050] The control device 320 controls the management device 300. The control device 320 includes one or more processors 330 (hereinafter simply referred to as the processor 330) and one or more storage devices 340 (hereinafter simply referred to as the storage device 340). The processor 330 executes various processes. Examples of the processor 330 include general-purpose processors, application-specific processors, CPUs, GPUs, ASICs, FPGAs, integrated circuits, conventional circuits, and / or combinations thereof. The processor 330 can also be referred to as circuitry or processing circuitry. Circuitry is hardware programmed to implement the described functions or hardware that executes the functions. The storage device 340 stores various information. Examples of the storage device 340 include volatile memory, non-volatile memory, HDDs, SSDs, etc.

[0051] The remote support management program PROG3 is a computer program executed by the processor 330. The functions of the control device 320 may be realized by the cooperation of the processor 330 and the storage device 340 that execute the remote support management program PROG3. The remote support management program PROG3 is stored in the storage device 340. Alternatively, the remote support management program PROG3 may be recorded on a computer-readable recording medium. The remote support management program PROG3 may be provided via a network.

[0052] The memory device 340 further stores mobility management information MGT-M, supporter management information MGT-S, and terminal management information MGT-T. The mobility management information MGT-M is information for managing a plurality of mobilities 100. For example, the mobility management information MGT-M indicates, for each mobility 100, a mobility ID, an allocation status, a remote support history, and the like. The supporter management information MGT-S is information for managing a plurality of remote supporters X. For example, the supporter management information MGT-S indicates, for each remote supporter X, a supporter ID, a held license, an availability, an allocation status, a work history, and the like. The terminal management information MGT-T is information for managing a plurality of remote support terminals 200. For example, the terminal management information MGT-T indicates, for each remote support terminal 200, a terminal ID, specifications, an availability, an allocation status, an operation history, and the like.

[0053] The control device 320 communicates with the mobility 100 and the remote support terminal 200 via the communication device 310. The control device 320 may relay communication between the mobility 100 and the remote support terminal 200. That is, the control device 320 may relay at least one of the mobility information MOV and the remote support information SUP between the mobility 100 and the remote support terminal 200.

[0054] Further, the control device 320 communicates with the infrastructure sensor 400 via the communication device 310. The infrastructure sensor 400 is installed in a target area where the mobility 100 moves. The target area is not particularly limited, and examples thereof include a street, a parking lot, a factory site, and the like. The infrastructure sensor 400 is a recognition sensor (e.g., a camera, LIDAR, etc.) that recognizes the situation of the target area.

[0055] In the following description, the infrastructure sensor 400 is, as an example, a camera. In the example of the camera, the infrastructure sensor 400 captures the target area and acquires a video IMG indicating the situation of the target area. Then, the infrastructure sensor 400 transmits the acquired video IMG to the management device 300. The management device 300 collects and manages the video IMG captured by the infrastructure sensor 400. Also, for presentation to the remote supporter X, the management device 300 may transmit the video IMG captured by the infrastructure sensor 400 to the remote support terminal 200.

[0056] 3. Assignment Based on Score SC In the remote support system 1, in response to a remote support request from the mobility 100, the management device 300 executes an "assignment process" of assigning the remote supporter X and the remote support terminal 200 used by the remote supporter X to the mobility 100.

[0057] If the management device 300 needs to acquire a large amount of information or calculate a large number of metric values for the above assignment process, the processing load of the management device 300 will increase. More specifically, the greater the number of mobilities requesting remote support at the same time, the greater the processing load of the management device 300. Also, if the amount of information that the management device 300 acquires from the mobility 100 for the assignment process is large, the load of data communication between the mobility 100 and the management device 300 will increase. That is, for the mobility 100, the amount of data transmitted to the management device 300 will increase. On the other hand, for the management device 300, the amount of data received from the mobility 100 will increase.

[0058] Therefore, in the present embodiment, the mobility 100 that requests remote support calculates (generates) a score SC and transmits the calculated score SC to the management device 300. The score SC is information that serves as the basis for the allocation process executed by the management device 300. More specifically, the score SC used as the basis for the allocation process is the normal score SC calculated when the remote support function described later is normal, excluding the abnormal values described later. Hereinafter, the score SC described in relation to the allocation process refers to the normal score SC.

[0059] Specifically, the score SC is a quantitative parameter indicating the urgency of the remote support request from the mobility 100. For example, the score SC is calculated in the range of 0 to 100. The higher the score SC, the higher the urgency of the remote support request.

[0060] The management device 300 that has received the score SC executes an allocation process based on the score SC. That is, the management device 300 allocates the remote support device X and the remote support terminal 200 used by the remote support device X to the mobility 100 based on the score SC. Note that the transmission of the score SC may also serve as the transmission of information indicating a remote support request from the mobility 100 to the management device 300. Alternatively, the mobility 100 may generate information indicating a remote support request separately from the score SC and transmit the generated information to the management device 300.

[0061] 3-1. Processing on the Mobility Side FIG. 7 is a block diagram showing a specific configuration example of the control device 140 shown in FIG. 4. In this example, the control device 140 is configured as a combination of a plurality of electronic control units (ECUs). As shown in FIG. 7, the plurality of ECUs include a first ECU 141 and a second ECU 142 that communicate with each other. The first ECU 141 executes various processes related to the above-described autonomous movement control (e.g., automatic driving control of a vehicle). The second ECU 142 executes various processes related to remote support. Each of the first ECU 141 and the second ECU 142 includes a processor 150 and a storage device 160.

[0062] 3-1-1. First Specific Example FIG. 8 is a flowchart showing a first specific example of the processing on the mobility 100 side. The processing of this flowchart is executed by the control device 140 (processor 150) of the mobility 100. As an example, the processing of this flowchart may be executed by the cooperation of the first ECU 141 and the second ECU 142 as follows. The processing of this flowchart may be executed, for example, in response to the establishment of a predetermined condition (support request condition) that the mobility 100 requires remote support. The presence or absence of the establishment of this support request condition is determined, for example, by the second ECU 142.

[0063] First, in step S11, the first ECU 141 determines whether there is an abnormality in the remote support function of the mobility 100. The "abnormality of the remote support function" mentioned here includes, for example, an abnormality of the second ECU 142 that executes processing related to remote support. The second ECU 142 is equipped with a self-diagnosis function, and can obtain a self-diagnosis result (normal, warning, abnormal) using this self-diagnosis function. The first ECU 141 communicates with the second ECU 142 and obtains the self-diagnosis result of the second ECU 142. Then, the first ECU 141 determines the presence or absence of an abnormality in the second ECU 142, that is, the presence or absence of an abnormality in the remote support function, based on the obtained self-diagnosis result of the second ECU 142.

[0064] If there is an abnormality in the remote support function of the mobility 100 (step S11; Yes), the processing proceeds to step S12. In step S12, the first ECU 141 sets a predetermined abnormal value (e.g., 999) as the score SC. Additionally, the abnormal value of the score SC is a value that can be clearly distinguished from the value of the score SC in the normal state described later.

[0065] Next, in step S13, the first ECU 141 transmits the score SC (abnormal value) set in step S12 to the management device 300 via the communication device 110. In other examples, the score SC may be transmitted to the management device 300 via a service provider that is in partnership with the remote support system 1.

[0066] According to the processing of steps S11 to S13, the mobility 100 can notify the management device 300 that an abnormality has occurred in the remote support function by using the information of the score SC that is originally used for the allocation process. Then, the mobility 100 can use this notification to request the management device 300 to rescue itself. When requesting rescue, the mobility 100 may transmit the position information of the mobility 100 to the management device 300 together with the score SC (abnormal value).

[0067] In addition, the information of the score SC (abnormal value) transmitted to the management device 30 may be used by the management device 300 as follows. That is, for example, a staff member of the remote support management center who has seen the score SC (abnormal value) transmitted to the management device 300 requests an external service provider that provides a mobility rescue service to rescue the mobility 100. Alternatively, for example, the management device 300 that has received the score SC (abnormal value) automatically executes a process of requesting an external service provider to rescue the mobility 100.

[0068] On the other hand, when there is no abnormality in the remote support function of the mobility 100 (step S11; No), that is, when remote support can be requested, the process proceeds to step S14. In step S14, the second ECU 142 executes a "score calculation process" for calculating the score SC (more specifically, the score SC when the remote support function is normal). Specifically, the score calculation process includes, for example, the processes of the following steps S14-1, S14-2, and S14-3.

[0069] In step S14-1, the second ECU 142 calculates a score SC1 based on the mobility state information. The mobility state information is information indicating the state of the mobility 100. That is, the state of the mobility 100 is quantified in the form of "score SC1".

[0070] FIG. 9 shows an example of the mobility state information and the score component SC1-i. The score SC1 is composed of, for example, three score components SC1-1, SC1-2, and SC1-3.

[0071] In the example shown in FIG. 9, the mobility state information includes "information on the remaining travelable distance D of the mobility 100 (in other words, the remaining driving distance)". In the example of the mobility 100 powered by the electric power stored in the battery, the remaining travelable distance D can be calculated based on, for example, the remaining battery level and the average power consumption. The remaining battery level is detected by a remaining battery level sensor included in the sensor group 120. The average power consumption of the mobility 100 is stored in the storage device 160. Also, in the example of the mobility 100 powered by fuel, the remaining travelable distance D can be calculated based on, for example, the remaining fuel level and the average fuel consumption. The remaining fuel level is detected by a remaining fuel level sensor included in the sensor group 120. The average fuel consumption of the mobility 100 is stored in the storage device 160. The second ECU 142 calculates the score component SC1-1 based on the remaining travelable distance D that can be obtained in this way. As shown in FIG. 9, the score component SC1-1 increases as the remaining travelable distance D becomes shorter. Note that the score component SC1-1 corresponds to an example of the "first score component" according to the present disclosure.

[0072] Also, in the example shown in FIG. 9, the mobility state information includes "information on the communication state CS of Mobility 100". Examples of the communication state CS include communication speed (throughput), communication delay, and the like. The control device 140 of Mobility 100 can measure the communication speed, communication delay, etc. based on the reception state of the data received from the communication partner. As another example, the control device 140 can measure the communication speed, communication delay, etc. based on the data transmitted to the communication partner and the feedback from the communication partner. The second ECU 142 calculates the score component SC1-2 based on the communication state CS that can be obtained in this way. As shown in FIG. 9, the score component SC1-2 increases as the communication state CS of Mobility 100 deteriorates. Note that the score component SC1-2 corresponds to an example of the "second score component" according to the present disclosure.

[0073] Also, in the example shown in FIG. 9, the mobility state information includes "information on the degree of abnormality of the control device (e.g., the first ECU 141) that performs the above-described autonomous movement control". For example, the first ECU 141 is equipped with a self-diagnosis function. The first ECU 141 uses this self-diagnosis function to obtain a self-diagnosis result (normal, warning, abnormal). The self-diagnosis result indicates the degree of abnormality of the first ECU 141. The second ECU 142 communicates with the first ECU 141 and obtains the self-diagnosis result of the first ECU 141. Then, the second ECU 142 calculates the score component SC1-3 based on the obtained self-diagnosis result of the first ECU 141, that is, the degree of abnormality. As shown in FIG. 9, the score component SC1-3 increases as the degree of abnormality of the control device (the first ECU 141) that performs the autonomous movement control increases. Note that the score component SC1-3 corresponds to an example of the "third score component" according to the present disclosure.

[0074] The second ECU 142 calculates the score SC1 based on the mobility state information, for example, by adding up the above-described score component SC1-1, score component SC1-2, and score component SC1-3. Alternatively, the second ECU 142 may calculate any one of these three score components as the score SC1, or may calculate the score SC1 by adding up any two of these three score components.

[0075] Additionally, the second ECU 142 acquires mobility state information in real time. Then, the second ECU 142 calculates a score SC1 in real time based on the mobility state information.

[0076] In step S14-2, the second ECU 142 calculates a score SC2 based on user / service state information. Here, the user / service state information indicates a combination of user state information and service state information. The user state information is information indicating the state of the user of the mobility 100 (in other words, the passenger), and the service state information is information indicating the state of the remote support service for the user. That is, the state of the user and the state of the service are quantified in the form of "score SC2".

[0077] FIG. 10 shows an example of user / service state information and score component SC2-i. The score SC2 is composed of, for example, three score components SC2-1, SC2-2, and SC2-3.

[0078] In the example shown in FIG. 10, the user / service state information includes "information on the health state of the user (passenger)", which is an example of user state information. The second ECU 142 may obtain the health state of the user based on information reported by a user who operates an operating device 180 (e.g., touch panel) mounted on the mobility 100 or the user's own mobile terminal (e.g., smartphone). As another example, a biological sensor that detects the biological information of the user may be used to detect the health state of the user. The biological sensor may be included in the sensor group 120 (see FIG. 4) of the mobility 100, or may be included in a mobile terminal (e.g., smartphone) owned by the user. Examples of the biological information include body temperature, heart rate, blood pressure, sweating amount, etc. The second ECU 142 may obtain the biological information detected by the biological sensor and obtain the health state of the user based on the obtained biological information. For example, the health state can be obtained from the biological information by using a machine learning model. The second ECU 142 calculates the score component SC2-1 based on the health state of the user thus obtained. As shown in FIG. 10, the score component SC2-1 increases as the health state of the user deteriorates. Note that the score component SC2-1 corresponds to an example of the "fourth score component" according to the present disclosure.

[0079] Also, in the example shown in FIG. 10, the user / service state information includes "information on the delay time until the start of the remote support service for the user (service delay time)", which is an example of the service state information. In other words, the service delay time is the waiting time for the user to wait for the start of the remote support of mobility 100. In an example where the service provider acquires the service delay time from the management device 300, the second ECU 142 may communicate with the service provider and acquire the service delay time from the service provider. Alternatively, the second ECU 142 may communicate with the management device 300 and directly acquire the service delay time from the management device 300. The second ECU 142 calculates the score component SC2-2 based on the acquired service delay time. As shown in FIG. 10, the score component SC2-2 increases as the service delay time becomes longer. Note that the score component SC2-2 corresponds to an example of the "fifth score component" according to the present disclosure.

[0080] Also, in the example shown in FIG. 10, the user / service state information includes "information on the amount charged to the user for the remote support service", which is another example of the service state information. The second ECU 142 may acquire the information on the amount charged, for example, based on the information input by the user operating the operator 180 (e.g., touch panel) mounted on the mobility 100 or the user's own mobile terminal (e.g., smartphone). Alternatively, in an example where a service provider is interposed between the mobility 100 and the management device 300, the second ECU 142 may communicate with the service provider and acquire the information on the amount charged from the service provider. The second ECU 142 calculates the score component SC2-3 based on the amount charged that can be acquired in this way. As shown in FIG. 10, the score component SC2-3 increases as the amount charged increases. Note that the score component SC2-3 corresponds to an example of the "sixth score component" according to the present disclosure.

[0081] The second ECU 142 calculates the score SC2 based on the user / service state information, for example, by adding up the above-mentioned score components SC2-1, SC2-2, and SC2-3. Alternatively, the second ECU 142 may calculate any one of these three score components as the score SC2, or may calculate the score SC2 by adding up any two of these three score components.

[0082] In addition, the second ECU 142 acquires the user / service state information in real time. Then, the second ECU 142 calculates the score SC2 in real time based on the user / service state information.

[0083] Also, in step S14-2, the user state information and the service state information are comprehensively treated as the user / service state information. In other examples, the score SC2 may be calculated based on only one of the user state information and the service state information.

[0084] In step S14-3, the second ECU 142 calculates the final score (integrated score) SC by integrating the scores SC1 and SC2 calculated in steps S14-1 and S14-2 respectively. That is, the score SC reflects the score SC1 based on the mobility state information and the score SC2 based on the user / service state information.

[0085] Specifically, in step S14-3, the second ECU 142 calculates the average value (arithmetic mean) of the score SC1 and the score SC2. If this average value is less than a predetermined maximum value (e.g., 100) of the score SC, the average value is used as the score SC. On the other hand, if the average value is greater than or equal to the maximum value, the score SC is uniformly set to the maximum value.

[0086] Alternatively, the integration of scores SC1 and SC2 may be performed as follows, for example. That is, instead of the above arithmetic mean value, the second ECU 142 may calculate a weighted average value of score SC1 and score SC2 as score SC. More specifically, for example, a weight value (weight coefficient) W2 multiplied by score SC2 based on user / service state information (more specifically, at least one of user state and service state information) may be set larger than a weight value W1 multiplied by score SC1 based on mobility state information. Thereby, a score SC in which at least one of the state of the user of mobility 100 such as a customer and the state of the remote support service provided to the user is reflected preferentially over the state of mobility 100 can be calculated. This leads to the fact that, compared with the example using the arithmetic mean, a request for remote support in which consideration for the user is more appropriately reflected can be transmitted from mobility 100 to the management device 300. Conversely, the weight value W1 may be set larger than the weight value W2 in this example. In addition, also in the example using the weighted average, the score SC is set so as not to exceed the above maximum value.

[0087] In step S15 following step S14, the second ECU 142 transmits the score SC calculated in step S14 to the management device 300 via the communication device 110. In other examples, the score SC may be transmitted to the management device 300 via a service provider.

[0088] In the processing of the flowchart shown in FIG. 8 described above, the score SC is calculated based on both the mobility state information and the user / service state information. In other examples, either one of the score SC1 based on the mobility state information and the score SC2 based on the user / service state information may be calculated as the score SC.

[0089] As described above, the processing of the flowchart shown in FIG. 8 may be executed when a predetermined support request condition is satisfied. Thereby, the calculation of the score SC is executed only when the mobility 100 actually requests remote support, so that the processing load on the control device 140 of the mobility 100 can be reduced. However, the processing of the flowchart shown in FIG. 8 may be executed periodically, that is, every predetermined time. According to this example, since steps S11 to S13 are executed even when the support request condition is not satisfied, an abnormality of the remote support function described later can be detected at an early stage and notified to the management device 300. Additionally, in this example, the control device 140 periodically executes the calculation of the score SC (see step S14) when the remote support function is normal. Therefore, the control device 140 (e.g., the second ECU 142) may determine whether or not the support request condition is satisfied based on whether or not the score SC calculated periodically in this way is equal to or greater than a predetermined threshold value.

[0090] 3-1-2. Second Specific Example FIG. 11 is a flowchart showing a second specific example of the processing on the mobility 100 side. The processing of this flowchart is different from the processing of the flowchart shown in FIG. 8 in that the processing of steps S21 and S22 is added.

[0091] In FIG. 11, when there is no abnormality in the remote support function (step S11; No), the processing proceeds to step S21. In step S21, the control device 140 (more specifically, for example, the second ECU 142) determines whether or not the user riding on the mobility 100 has operated an operator to request remote support. The operator is, for example, an operator 180 (e.g., a touch panel, a push button, etc.) mounted on the mobility 100 or the user's mobile terminal (e.g., a smartphone).

[0092] When there is no request for remote support from the user (rider) (step S21; No), the process proceeds to step S14. On the other hand, when there is a request for remote support from the user (step S21; Yes), the process proceeds to step S22. In step S22, the second ECU 142 sets the highest value (e.g., 100) when the remote support function is normal as the score SC. This highest value is an example of "a predetermined value indicating a high urgency of the request for remote support". Additionally, setting the highest value as the predetermined value corresponds to giving the highest priority to the request for remote support directly issued by the user. After that, the process proceeds to step S15.

[0093] 3-1-3. Example of calculating the score considering the type of mobility As illustrated with reference to FIG. 2, in the remote support system 1, multiple types of mobility 100 can be the target of remote support. When multiple types of mobility 100 are the target of remote support, the meaning of the numerical value indicating the above-described mobility state information can vary depending on the type of mobility 100. For example, even if the remaining travelable distance D, which is the mobility state information, has the same numerical value among multiple mobilities 100, if the maximum travelable distance Dmax of each individual type of mobility 100 is different, the meaning of the same numerical value of the remaining travelable distance D will be different.

[0094] Therefore, as in the example described here, at least one of the mobility state information, the following normalized mobility state information may be used for calculating the score SC. That is, the control device 140 (e.g., the second ECU 142) of the mobility 100 may calculate the score SC based on the normalized mobility state information based on a predetermined "calculation rule" shared among multiple mobilities 100. More specifically, in an example where another score (e.g., score SC2 based on user / service state information) is used for calculating the score SC together with the score SC1 based on the mobility state information, the control device 140 may calculate the score component SC1-i based on the normalized mobility state information.

[0095] Figure 12 shows an example of the normalized mobility state information and the score component SC1-i. In Figure 12, as the mobility state information to be normalized, the available travel distance D and the communication state CS are exemplified. The normalized available travel distance Dn and the normalized communication state CSn are calculated according to, for example, the following calculation rules.

[0096] First, in the example of the available travel distance D, the normalized available travel distance Dn is obtained by multiplying the value obtained by dividing the current available travel distance D (that is, the remaining travel distance) by the maximum available distance Dmax by 100. The 100 by which the value is multiplied corresponds to 100 which is an example of the highest value of the score SC. Additionally, the maximum available distance Dmax is the distance that the mobility 100 can travel without replenishing at least one of power and fuel, and is a known value for each mobility 100.

[0097] Similarly, in the example of the communication state CS, the normalized communication state CSn is obtained by multiplying the value obtained by dividing the current communication state CS (e.g., communication speed (Mbps)) by the highest communication state (e.g., highest communication speed (theoretical value)) CSmax by 100. Additionally, the highest communication state CSmax is a known value for each mobility 100 (of the communication device 110).

[0098] The sharing of the calculation rules among a plurality of mobilities 100 can be realized, for example, by the following method. That is, the calculation rules are shared by storing, in the storage device 160 of each mobility 100, information indicating the relationship between the normalized mobility state information and the score SC (score component SC1-i) as shown in Figure 12. Additionally, the information indicating the relationship may be provided from the management device 300 to each mobility 100, for example. Alternatively, in an example where a service provider intervenes between the two, the information indicating the relationship may be provided to each mobility 100 via the service provider.

[0099] 3-1-4. Effect of Mobility As described above, according to the present embodiment, the score SC that serves as the basis for the assignment of at least one of the remote supporter X and the remote support terminal 200 is calculated on the side of the mobility 100 that requests remote support. Thereby, the processing load on the management device 300 regarding the assignment can be reduced. More specifically, the processing load on the management device 300 can be reduced as compared with an example in which the management device 300 performs all of the processes related to the calculation of the score SC. This leads to a reduction in the time required for the assignment. In addition, since the score SC is calculated on the side of the mobility 100 and transmitted to the management device 300, the management device 300 does not need to acquire a lot of information necessary for the assignment from each mobility 100. Therefore, the communication volume between each mobility 100 and the management device 300 can also be reduced.

[0100] More specifically, according to the present embodiment, the score SC that indicates the urgency of the remote support request from each mobility 100 and serves as the basis for setting the assignment order ORD is calculated on the side of the mobility 100 that requests remote support. Thereby, while reducing the processing load on the management device 300 regarding the assignment according to the assignment order ORD, the assignment can be appropriately performed so that the mobility 100 with a higher urgency is prioritized using the score SC.

[0101] Also, according to the present embodiment, the score SC can be appropriately calculated based on the mobility state information. Thereby, for example, the assignment can be performed so that the mobility 100 with a short remaining travelable distance D is prioritized. Also, for example, the assignment can be performed so that the mobility 100 with a poor communication state CS is prioritized. Furthermore, for example, the assignment can be performed so that the mobility 100 with a high degree of abnormality of the control device that performs autonomous movement control such as automatic driving control of the vehicle is prioritized.

[0102] Further, according to the present embodiment, the score SC can be appropriately calculated based on at least one of user state information and service state information. As a result, for example, it becomes possible to perform an assignment so that the mobility 100 in which a user with a poor health condition is riding is prioritized. Also, for example, it becomes possible to perform an assignment so that the mobility 100 of a user with a long delay time until the start of a remote support service is prioritized. Further, for example, it becomes possible to perform an assignment so that the mobility 100 of a user with a high charging amount for a remote support service is prioritized.

[0103] Also, according to the present embodiment, when a user riding on the mobility 100 operates an operating device (e.g., operating device 180) to request remote support, a predetermined value (e.g., the above maximum value) indicating a high urgency is set as the score SC. As a result, the request of a user who requests early remote support can be reflected in the assignment order ORD by using the score SC.

[0104] Furthermore, according to the present embodiment, the score SC is calculated based on the mobility state information normalized based on the calculation rules shared among multiple types of mobility 100. As a result, the score SC can be calculated more appropriately in consideration of the differences in the types of mobility 100 that are the targets of remote support.

[0105] 3-2. Processing on the Remote Support Management Device Side 3-2-1. Specific Example FIG. 13 is a flowchart showing a specific example of the processing (assignment processing) on the management device 300 side. The processing of this flowchart is repeatedly executed by the control device 320 (processor 330) of the management device 300.

[0106] The management device 300 receives the score SC from a plurality of mobility 100 that request remote support. In other words, the management device 300 acquires the score SC from a plurality of mobility 100 in real time. The acquired score SC is stored in the storage device 340.

[0107] In step S31, the control device 320 determines whether a new score SC is newly received from a certain mobility 100 via the communication device 310. As a result, if a new score SC is not acquired (step S31; No), the control device 320 continues to accept the new score SC. On the other hand, if a new score SC is acquired (step S31; Yes), the control device 320 continues to accept new score SCs from other mobilities 100 while executing the processes after step S32 in parallel.

[0108] In step S32, the control device 320 updates the "assignment order ORD" in a form that reflects the newly received score SC. The assignment order ORD indicates, for example, the order of assignment of the remote supporter X and the remote support terminal 200 to one or more mobilities 100 for which the assignment has not been completed.

[0109] FIG. 14 is a diagram showing an example of the update of the assignment order ORD in step S32. The mobility management information MGT-M (see FIG. 6) stored in the storage device 340 includes the assignment order ORD. The assignment order ORD is specified, for example, in the form of a mobility list as shown in FIG. 14. The mobility list includes, for each unassigned mobility 100, the mobility ID, the score SC, and the rank of the waiting time. According to the rank of the waiting time, the mobility 100 with an earlier time (i.e., a longer waiting time) when remote support was requested by transmitting the score SC is ranked higher. In this mobility list, the mobilities 100 with an earlier assignment order ORD are listed in order from the top. Note that the storage device 340 stores the time when the score SC was received from each mobility 100 as the request time.

[0110] The "before update" mobility list in FIG. 14 corresponds to the mobility list read from the storage device 340 when the process proceeds to step S32, with the mobility 100 (mobility B with the 4th rank in waiting time in FIG. 14) for which the acquisition of the score SC was confirmed in the most recent step S31 added thereto.

[0111] In step S32, the control device 320 updates (determines) the assignment order ORD so that the mobility 100 with a high score SC moves to the upper position. That is, the assignment order ORD is sorted in descending order of the score SC (in other words, in descending order of the priority of assignment). For example, in the "after update" mobility list in FIG. 14, the assignment order ORD is updated so that mobility B having a score SC of "100" comes earlier than mobilities A and D both having a score SC of "10". Thus, the score SC serves as the basis for setting the assignment order ORD.

[0112] Also, in the example shown in FIG. 14, the score SC of mobility B is the same as the score SC of mobility C. When there are a plurality of mobilities 100 having the same score SC in this way, the assignment order ORD is updated so that the mobility C with the earlier waiting time rank (that is, the longer waiting time) is in the upper position. This is also the same in the relationship between mobility A and mobility D. The mobility list with the assignment order ORD updated as described above is stored in the storage device 340.

[0113] Next, in step S33, the control device 320 updates the "assignment relationship REL" according to the assignment order ORD updated in step S32. The assignment relationship REL here refers to, for example, the assignment relationship of the remote support terminal 200 to the mobility 100.

[0114] FIG. 15 is a diagram showing an example of updating the allocation relationship REL in step S33. The mobility management information MGT-M (see FIG. 6) stored in the storage device 340 includes, for example, the allocation relationship REL. In this example, the allocation relationship REL is specified in the form of the relationship between the mobility list and the support terminal list as shown in FIG. 15. The mobility list is as described with reference to FIG. 14. The control device 320 extracts a plurality of remote support terminals 200 that are candidates for allocation to the mobilities A to D included in the mobility list based on the terminal management information MGT-T (see FIG. 6). The support terminal list shown in FIG. 15 identifies the four remote support terminals 200 thus extracted by their respective IDs. In the support terminal list, each remote support terminal 200 is represented in order from the top in descending order of priority based on a predetermined rule. The order of each of these remote support terminals 200 is determined in advance by the control device 320 based on the terminal management information MGT-T.

[0115] As shown in FIG. 15, the control device 320 determines the allocation relationship REL such that the remote support terminals 200 with higher priority are allocated in order from the mobility 100 with the earlier allocation order ORD. In an example where a single remote support terminal 200 is used only by a specific remote supportor X, by determining the remote support terminal 200 allocated to the mobility 100 in this way, the combination of the remote support terminal 200 allocated to the mobility 100 and the remote supportor X is specified. On the other hand, in an example where a single remote support terminal 200 is used by various remote supportors X, the control device 320 further executes a process of determining, based on the supportor management information MGT-S, the remote supportor X that uses the remote support terminal 200 to which the mobility 100 is allocated.

[0116] FIG. 16 is a diagram showing another example of the update of the allocation relationship REL in step S33. In the example shown in FIG. 15, the control device 320 allocates a "remote support terminal 200" to each of the plurality of mobilities 100 according to the allocation order ORD. In contrast, in the example shown in FIG. 16, the control device 320 uses the supporter management information MGT-S (see FIG. 6) to allocate a "remote supporter X" to each of the plurality of mobilities 100 according to the allocation order ORD. That is, in this example, the allocation relationship REL updated according to the allocation order ORD is the relationship of the allocation of the remote supporter X to the mobility 100.

[0117] In the example shown in FIG. 16, the allocation relationship REL is specified in the form of the relationship between the mobility list and the supporter list. The mobility list is as described with reference to FIG. 14. The control device 320 extracts a plurality of remote supporters X that are candidates for allocation to the mobilities A to D included in the mobility list based on the supporter management information MGT-S. The support terminal list shown in FIG. 16 identifies the four remote supporters X thus extracted by their respective IDs. In the supporter list, each remote supporter X is represented in order from the top in descending order of priority based on a predetermined rule. The order of each remote supporter X is determined in advance by the control device 320 based on the supporter management information MGT-S.

[0118] As shown in FIG. 16, the control device 320 determines an assignment relationship REL such that the remote supporter X with a higher priority is assigned in order from the mobility 100 with the earlier assignment order ORD. In an example where a single remote support terminal 200 is used only by a specific remote supporter X, by determining the remote supporter X assigned to the mobility 100 in this way, the combination of the remote supporter X assigned to the mobility 100 and the remote support terminal 200 is specified. On the other hand, in an example where a single remote support terminal 200 is used by various remote supporters X, the control device 320 further executes a process of determining the remote support terminal 200 used by the remote supporter X to which the mobility 100 is assigned, based on the terminal management information MGT-T.

[0119] In still another example, the control device 320 may execute a process of assigning both a "remote support terminal 200" and a "remote supporter X" to each of a plurality of mobilities 100 according to the assignment order ORD, using the terminal management information MGT-T and the supporter management information MGT-S.

[0120] 3-2-2. Score Update by Management Device The management device 30 that has received the score SC calculated on the side of the mobility 100 may update the score SC as in each of the following examples.

[0121] 3-2-2-1. Use of Infrared Sensor Information FIG. 17 is a flowchart showing an example of a process for updating the score SC by the management device 300 that uses infrared sensor information. The process of this flowchart is executed by the control device 320 in response to the reception of the score SC from the mobility 100. More specifically, the mobility 100 (mobility to be updated) for which the management device 300 can acquire "peripheral situation information" using the infrared sensor 400 is the target for updating the score SC by the process of this flowchart.

[0122] In step S41, the control device 320 uses the infrared sensor 400 to obtain the surrounding situation information of the mobility 100 that has transmitted the score SC. Specifically, in the example where the mobility 100 is a vehicle, the control device 320 obtains the surrounding situation information by analyzing, for example, the video IMG received from the infrared sensor 400 via the communication device 310. The surrounding situation information is information indicating the situation of the area where the mobility 100 moves. The obtained surrounding situation information is, for example, information indicating the congestion level of the road ahead of the mobility 100 which is a vehicle.

[0123] Next, in step S42, the control device 320 calculates an additional score SC-A of the mobility 100 based on the obtained surrounding situation information. For example, the control device 320 calculates the additional score SC-A such that it increases as the congestion level of the road due to factors such as traffic jams increases.

[0124] Next, in step S43, the control device 320 updates the transmitted score SC by reflecting the calculated additional score SC-A in the score SC transmitted from the mobility 100. This update can be performed using, for example, the same method as the integration of the scores SC1 and SC2 used in step S14-3 (see FIG. 8). That is, for example, the score SC may be updated by the arithmetic mean value of the transmitted score SC and the additional score SC-A. Alternatively, the score SC may be updated by the weighted mean value of the transmitted score SC and the additional score SC-A.

[0125] In addition, for example, when a service that transports a user with a deteriorated health condition in a vehicle to a hospital is provided by remote support (remote driving), the score SC is updated by the additional score SC-A as described above, and thus, for example, the following effects can be obtained. That is, in consideration of the congestion level of the road ahead of the vehicle that cannot be acquired by the sensors mounted on the vehicle (Mobility 100), the urgency indicated by the score SC related to the request for remote support of the service can be appropriately increased. Further, when using a weighted average value, for example, the weight value multiplied by the additional score SC-A may be set to be larger than the weight value multiplied by the score SC transmitted from the Mobility 100. Thereby, in the example of the service illustrated herein, in consideration of the congestion level of the road, the urgency indicated by the score SC related to the request for remote support of the service can be more appropriately increased.

[0126] 3-2-2-2. Example of score update considering the type of mobility As illustrated with reference to FIG. 2, in the remote support system 1, multiple types of Mobility 100 can be the target of remote support. When multiple types of Mobility 100 are the target of remote support, it may not be very appropriate to handle the scores SC with the same numerical value in the same row regardless of the type of Mobility 100. For example, when the scores SC transmitted from a type of Mobility 100 that is the target of remote support with a relatively high urgency and a type of Mobility 100 that is the target of remote support with a relatively low urgency are the same numerical value, it can be said that it is desirable to handle the former score SC as having a higher urgency.

[0127] FIG. 18 is a flowchart showing an example of the processing on the management device 300 side involving the processing for updating the score SC considering the type of Mobility 100. The processing of this flowchart is different from the processing of the flowchart shown in FIG. 13 in that the processing of steps S51 to S53 is added.

[0128] In FIG. 18, when a new score SC is obtained (step S31; Yes), the process proceeds to step S51. In step S51, the control device 320 of the management device 300 acquires information indicating the type of the mobility 100 that transmitted the current score SC (mobility type information). For example, when the mobility management information MGT-M includes the ID and type of each mobility 100, the control device 320 acquires the mobility type information based on the mobility ID transmitted from the mobility 100 together with the score SC and the mobility management information MGT-M. Alternatively, the mobility type information may be acquired from the mobility 100 together with the score SC, or may be acquired via a service provider.

[0129] Next, in step S52, the control device 320 calculates a weight value (mobility weight value) Wm corresponding to the type of the mobility (update target mobility) 100 that transmitted the score SC based on the mobility type information. Specifically, the weight value Wm is determined in advance for each type of the mobility 100. And information indicating the correspondence relationship between the weight value Wm and the type of the mobility 100 is stored in the storage device 340. The control device 320 calculates the weight value Wm corresponding to the type of the update target mobility 100 based on the information indicating the correspondence relationship and the mobility type information.

[0130] In the information indicating the above correspondence relationship, the weight value Wm may be determined as follows, for example. That is, for example, based on the urgency of remote support pre-evaluated from a global perspective such as the type of the mobility 100 that receives remote support, the weight value Wm is determined such that the mobility 100 of the type that receives remote support with a higher urgency is higher than the mobility 100 of the type that receives remote support with a lower urgency. As an example, the weight value Wm of the mobility 100 that transports people may be set to be larger than the weight value Wm of the mobility 100 that transports goods.

[0131] Next, in step S53, the control device 320 updates the score SC by reflecting the weight value Wm in the score SC received from the mobility 100 to be updated. Specifically, the control device 320 updates the score SC by multiplying the received score SC by the weight value Wm as a weight coefficient, for example. Thereafter, the process proceeds to step S32. Additionally, the maximum value of the score SC obtained by reflecting the weight value Wm in this way may be the same as the maximum value of the score SC calculated on the side of the mobility 100 (e.g., 100), or may be a value larger than the maximum value (e.g., 150).

[0132] 3-2-2-3. Example of score update considering mobility and service types As illustrated with reference to FIG. 2, in the remote support system 1, the types of remote support services provided to one or more mobilities 100 may be plural. In an example where plural types of services are provided, there may be a case where it is not appropriate to handle scores SC with the same numerical value in the same column regardless of the service type. For example, even if the scores SC transmitted from the mobility 100 receiving the service of transporting people and the mobility 100 receiving the service of transporting goods (e.g., mail) have the same numerical value, it may be desirable to handle the former score SC as having a higher urgency.

[0133] FIG. 19 is a flowchart showing an example of the processing on the side of the management device 300 involving the processing related to the update of the score SC considering the types of the mobility 100 and the types of services. The processing of this flowchart is different from the processing of the flowchart shown in FIG. 13 in that the processing of steps S61 to S63 is added. Additionally, in the example shown in FIG. 19, it is assumed that the information of the score SC transmitted from the mobility 100 also includes the information of the numerical values of the scores SC1 and SC2 constituting the score SC.

[0134] In FIG. 19, when a new score SC is obtained (step S31; Yes), the process proceeds to step S61. In step S61, the control device 320 of the management device 300 acquires the mobility type information and the service type information of the mobility 100 that transmitted the current score SC. A specific example of the method for acquiring the mobility type information is the same as the process of step S51. The service type information is information indicating the type of remote support service provided to the mobility 100. The service type information can also be acquired by the same method as the method for acquiring the mobility type information.

[0135] Next, in step S62, the control device 320 calculates a mobility weight value Wm, which is a weight value corresponding to the type of the mobility (update target mobility) 100 that transmitted the score SC, based on the mobility type information. Further, the control device 320 calculates a service weight value Ws, which is a weight value corresponding to the type of service provided to the update target mobility 100, based on the service type information.

[0136] Specifically, the mobility weight value Wm can be calculated using the method described above for step S52. The service weight value Ws is determined in advance for each type of service. And information indicating the correspondence between the service weight value Ws and the type of service is stored in the storage device 340. The control device 320 calculates the service weight value Ws corresponding to the type of service based on the information indicating the correspondence and the service type information.

[0137] In the information indicating the above correspondence relationship, the service weight value Ws may be determined as follows. That is, for example, based on the urgency of each service evaluated in advance, the service weight value Ws may be determined such that a service with a higher urgency has a higher value than a service with a lower urgency. For example, the service weight value Ws of a service for transporting people may be set to be larger than the service weight value Ws of a service for transporting goods. Also, for example, the service weight value Ws of a service for delivering a product by a specified time may be set to be larger than the service weight value Ws of a return service for transporting a rental car to a business office.

[0138] Next, in step S63, the control device 320 updates the score SC of the update target mobility 100 based on the score (mobility score) SC1 of the update target mobility 100 in which the mobility weight value Wm is reflected and the score (service score) SC2 of the update target mobility 100 in which the service weight value Ws is reflected. Specifically, the control device 320 updates the score SC, for example, by the sum of the product obtained by multiplying the mobility score SC1 by the weight value Wm as a weighting factor and the product obtained by multiplying the service score SC2 by the weight value Ws as a weighting factor. Alternatively, similar to the process of step S14-3 (see FIG. 8), the control device 320 may update the score SC by the average value of the product of the mobility score SC1 and the weight value Wm and the product of the service score SC2 and the weight value Ws. Thereafter, the process proceeds to step S32.

[0139] When added, the service score SC2 used in the process shown in FIG. 19 only needs to be based on the above-described service state information, and may also be based on user information together with the service state information calculated in step S14-2 (see FIG. 8). Also, the maximum value of the score SC updated by the process of step S63 may be the same as the maximum value of the score SC calculated on the mobility 100 side (e.g., 100), or may be a value larger than the maximum value (e.g., 150). Further, the process shown in FIG. 19 is also applicable to an example of a remote support system in which a plurality of types of mobility 100 receive the provision of a plurality of types of remote support services. In this example, the mobility weight value Wm as a weight coefficient may be set to 1.

[0140] 3-2-3. Effects of the Remote Support Management Device As described above, according to the present embodiment, the remote support management device 300 acquires the score SC from the mobility 100 that requests remote support. Thereby, compared with an example in which the management device 300 performs all the processes related to the calculation of the score SC, the processing load of the management device 300 related to allocation can be reduced. Then, the management device 300 calculates an additional score SC-A based on the surrounding situation information from one or more infrastructure sensors 400, and updates the score SC by reflecting the additional score SC-A in the score SC transmitted from the mobility 100. Thereby, the score SC can be appropriately determined using the surrounding situation information that cannot be acquired by the sensors mounted on the mobility 100. For example, when the mobility 100 is a vehicle, the surrounding situation information (e.g., the congestion level of the road in front of the vehicle) that cannot be acquired by the vehicle's camera can be acquired from the infrastructure sensor 400. Thereby, compared with the case of using traffic jam information from an external traffic information center, the change in the traffic situation in front of the vehicle can be acquired more quickly and accurately.

[0141] Thus, according to the present disclosure, it becomes possible to appropriately perform the above-described allocation while reducing the processing load of the management device 300 related to the allocation.

[0142] More specifically, according to this embodiment, the management device 300 acquires from each mobility 100 a score SC that indicates the urgency of a remote support request and serves as a basis for setting the assignment order ORD. Thereby, while reducing the processing load of the management device 300 regarding the assignment according to the assignment order ORD, the assignment can be appropriately performed using the score SC so that the mobility 100 with a higher urgency is prioritized.

[0143] Further, the management device 300 may update the score SC transmitted from each mobility 100 so as to reflect a weight value Wm corresponding to the type of the mobility 100. Thereby, the assignment process can be performed using the score SC determined more appropriately in consideration (reflection) of the difference in the types of the mobility 100. Additionally, also in this example, the basic calculation of the score SC is performed on the side of each mobility 100. Therefore, while reducing the processing load of the management device 300, the score SC can be appropriately updated by the management device 300 that manages a plurality of mobilities 100. For example, the score SC of the mobility 100 with a higher urgency of the remote support request can be more appropriately determined to be higher from the perspective of the type of the mobility 100. And in an example where the assignment order ORD is set based on the score SC, it becomes possible to appropriately increase the priority of the assignment of the mobility 100.

[0144] Further, the management device 300 may update the score SC transmitted from the mobility 100 based on a mobility score SC1 in which a mobility weight value Wm corresponding to the type of the mobility 100 is reflected and a service score SC2 in which a service weight value Ws corresponding to the type of the service is reflected. Thereby, the assignment process can be performed using the score SC determined more appropriately in consideration (reflection) of the difference in the types of the mobility 100 and the difference in the types of the service. Additionally, also in this example, the basic calculation of the score SC is performed on the side of each mobility 100. Therefore, while reducing the processing load of the management device 300, the score SC can be appropriately updated by the management device 300 that manages a plurality of mobilities 100.

[0145] Also, according to the present embodiment, when there are a plurality of mobilities 100 having the same score SC, the assignment order ORD is updated so that the mobility 100 with the earlier time when remote support was requested is ranked higher. Thereby, even when the scores SC of the plurality of mobilities 100 are the same value, the priority order of assignment can be appropriately determined using the score SC.

[0146] Note that the "score SC" according to the present disclosure only needs to be the basis of the above-described assignment process, and is not necessarily limited to being used for setting the assignment order ORD. That is, the score SC may be used as follows. For example, when the management device 300 receives the score SC from two mobilities 100, there are candidates for two or more remote supporters X waiting, and there is room in two or more remote support terminals 200, the management device 300 may execute an assignment process to assign a highly skilled person among the candidates for two or more remote supporters X to the mobility 100 having a high score SC (that is, a high degree of urgency).

Description of Reference Numerals

[0147] 1 Remote support system, 100 Mobility, 200 Remote support terminal, 300 Remote support management device, 400 Infrared sensor

Claims

1. A remote support management device for managing remote support for a plurality of mobilities, in response to a request for remote support from one or more of the plurality of mobilities, comprising one or more processors that execute an assignment process of assigning at least one of a remote supporter and a remote support terminal used by the remote supporter to the mobility that made the request, the one or more processors obtain a score that is the basis for the assignment process from one or more of the plurality of mobilities, communicate with one or more infrastructure sensors installed in an area where the update target mobility that transmitted the score moves, and obtain peripheral situation information indicating the situation of the area, calculate an additional score for the update target mobility based on the obtained peripheral situation information, update the score by reflecting the additional score in the score transmitted from the update target mobility configured as a remote support management device.

2. The remote support management device according to claim 1, wherein the score indicates the urgency of the request, and the assignment process includes assigning at least one of a remote supporter and a remote support terminal to each of the plurality of mobilities according to an assignment order based on the score received from the one or more processors of each of the plurality of mobilities a remote support management device.

3. The remote support management device according to claim 1 or 2, wherein there are a plurality of types of the plurality of mobilities, when receiving the score from one or more of the plurality of mobilities, the one or more processors update the score of the update target mobility by reflecting a weight value corresponding to the type of the update target mobility that transmitted the score in the score received from the update target mobility, and execute the assignment process based on the updated score configured as a remote support management device.

4. The remote support management device according to claim 1 or 2, wherein there are a plurality of types of services of the remote support provided to the plurality of mobilities, The score includes a mobility score that is a score based on mobility state information indicating the state of the mobility, and a service score that is a score based on service state information indicating the state of the remote support service for the user of the mobility. When the one or more processors receive the score from one or more of the plurality of mobilities, based on the mobility score of the mobility to be updated, in which a mobility weight value corresponding to the type of the mobility to be updated that transmitted the score is reflected, and the service score of the mobility to be updated, in which a service weight value corresponding to the type of the service provided to the mobility to be updated is reflected, the score of the mobility to be updated is updated. Execute the allocation process based on the updated score configured to Remote support management device.

5. The remote support management device according to claim 2, when there are a plurality of mobilities having the same value of the score, the one or more processors update the allocation order so that the mobility with the earlier time when the remote support was requested is ranked higher. Remote support management device.

6. A remote support management method executed by a computer for managing remote support for a plurality of mobilities, in response to a request for remote support from one or more of the plurality of mobilities, performing an allocation process of allocating at least one of a remote support device and a remote support terminal used by the remote support device to the mobility that made the request. obtaining a score that is the basis of the allocation process from one or more of the plurality of mobilities. communicating with one or more infrastructure sensors installed in an area where the mobility to be updated that transmitted the score moves, and obtaining peripheral situation information indicating the situation of the area. calculating an additional score for the mobility to be updated based on the peripheral situation information. updating the score by reflecting the additional score in the score transmitted from the mobility to be updated. including Remote support management method.

7. A remote support management program executed by a computer for managing remote support for a plurality of mobilities, In response to a request for remote support from one or more of the plurality of mobilities, execute an allocation process for allocating at least one of a remote supporter and a remote support terminal used by the remote supporter to the mobility that made the request. Obtain a score that is the basis for the allocation process from one or more of the plurality of mobilities. Communicate with one or more infrastructure sensors installed in the area where the update target mobility that transmitted the score moves, and obtain peripheral situation information indicating the situation of the area. Calculate an additional score for the update target mobility based on the peripheral situation information. Update the score by reflecting the additional score in the score transmitted from the update target mobility. Cause the computer to execute Remote support management program.

Images